Skip to content

fig. Pconference · 2025

VLSID 2026 A case study by Mayank Panchal

39th International VLSI Design Conference

Last year’s conference site for the 39th VLSI Design and 25th Embedded Systems editions - a dual-venue programme in Pune, January 2026.

Visit live All projects
VLSID 2026 - 39th International VLSI Design Conference: homepage screenshot of the conference platform built by Mayank Panchal
Role
Web Developer
Client
VLSI Society of India, Pune
Year
2025
Category
Conference

Overview

For VLSID 2026 we shipped the official site for Global Synergy in Silicon - VLSI and Embedded AI for next-gen electrified mobility. The programme split across MIT World Peace University (tutorials, 3–4 January) and JW Marriott Pune (main conference, 5–7 January), with 2,000+ attendees, keynotes, partners from Cadence, Intel, Qualcomm, Siemens, AMD, and a full author/forum stack. The build had to present two venues, a dense speaker roster, and sponsor tiers without burying Call for Papers, registration, or travel.

Highlights

  1. 01

    Dual-venue programme (MIT WPU tutorials + JW Marriott main conference)

  2. 02

    Keynote, leader, and partner grids for a 2,000+ attendee edition

  3. 03

    Author tracks: papers, tutorials, design contest, tape-out, fellowship

  4. 04

    Sponsorship, exhibitor, and registration flows for VSI’s sister-DAC event

fig. P.2system design

How it’s built.

The same content-modelled approach stretched across two venues: tutorials at one, the main conference at another, with keynotes, partners and author tracks all driven from structured fields and served from cache.

fig. P.2 — architecture · vlsid 2026
Dual-venue conference CMS
01 · Client02 · Edge03 · Application04 · Modules05 · Data06 · PlatformVisitorsauthors · attendeesEditorsorganisersPage cacheHTML · assetsWordPresscustom themeProgrammetwo venues · keynotesEnquiry formsvalidated · routedMySQLposts · fieldsMedia libraryresponsive imagesDesk routingregistration · sponsorsPHP hostbackups · TLS
  • Client
  • Edge / proxy
  • Service
  • Database
  • Third party
  • Platform
  • async

Flow · Read a page

Attendees check the schedule repeatedly on conference days.

01 / 05

Design decisions

  1. 01Two venues, one schedule

    Venue and day as fields on each session.

    Every view of the programme - by venue, by day, by track - is a filter, not a separate page to maintain.

    Trade-off · Editors must tag sessions consistently; the templates enforce the fields.

  2. 02Sponsor tiers

    Partners as data with a tier field.

    Grids for Cadence, Intel, Qualcomm and the rest sort and group themselves.

    Trade-off · Logo assets need a consistent format, checked on upload.

Concepts in this system