Skip to content

fig. Pconference · 2026

VLSID 2027 A case study by Mayank Panchal

40th International VLSI Design Conference

Official digital platform for the 40th International Conference on VLSI Design and the 26th International Conference on Embedded Systems - Bengaluru, January 2027.

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

Overview

VLSID is India’s flagship VLSI and embedded-systems conference, a sister event of the Design Automation Conference and sponsored by the VLSI Society of India. For the 40th edition (2–6 January 2027, Sheraton Grand Whitefield, Bengaluru) we built the public site around the year’s theme - Artificial Intelligence to Physical Intelligence - covering call for papers, tutorials, SRF/PhD forum, tapeout contest, committee, archives, sponsorship, and registration. The platform has to carry 2,000+ engineers, faculty, industry, and government visitors through a dense programme without feeling like a brochure.

Highlights

  1. 01

    Conference CMS for papers, tutorials, forums, and registration CTAs

  2. 02

    Editorial homepage for the 40th-edition AI → Physical Intelligence theme

  3. 03

    Committee, speakers, partners, and archive modules the organisers can update

  4. 04

    Enquiry routing for general, sponsorship, TPC, and registration desks

fig. P.2system design

How it’s built.

A custom WordPress theme where committees, speakers, tracks, partners and archives are structured data, a cache in front for the traffic spikes around deadlines, and enquiry routing that sends each question to the desk that owns it.

fig. P.2 — architecture · vlsid 2027
Content-modelled CMS for a 2,000+ attendee conference
01 · Client02 · Edge03 · Application04 · Modules05 · Data06 · PlatformVisitorsauthors · attendeesEditorsorganising committeePage cacheHTML · assetsWordPresscustom themeProgrammetracks · speakers · committeeEnquiry formsvalidated · routedMySQLposts · fieldsMedia libraryresponsive imagesDesk routinggeneral · TPC · sponsorsPHP hostbackups · TLS
  • Client
  • Edge / proxy
  • Service
  • Database
  • Third party
  • Platform
  • async

Flow · Read a page

Deadline week: thousands of authors read the same pages at once.

01 / 05

Design decisions

  1. 01Content as data

    Custom post types for speakers, committee, tracks and partners.

    The programme changes daily before the event; structured fields let organisers update it without breaking layouts.

    Trade-off · Each new kind of content needs a type and a template up front.

  2. 02Deadline spikes

    Full-page caching with purge on publish.

    Traffic concentrates around submission deadlines - the cache absorbs the spike, not the database.

    Trade-off · Editors see a short delay between publish and purge on rare cache misses.

  3. 03Enquiry routing

    One form system, routed by desk.

    General, sponsorship, TPC and registration questions each reach the people who can answer them.

    Trade-off · Routing rules must be kept in sync with who staffs each desk.

Concepts in this system