Skip to main content

Software with a long life.

business@kashvish.com
Software with a long life.

Higher education · Punjab · case study

One codebase, fourteen regional sites

Fourteen microsites rebuilt as one distribution, with room for each campus to be itself.

  • Drupal 11
  • Config split
  • Composer
  • Twig
  • Automated deployment

Each campus had its own site, built when its own dean wanted one. Over a decade that became fourteen copies of the same navigation, four different calendars, and a security update that had to be repeated by hand fourteen times.

What we did

We kept the sites separate where the identity genuinely differed and merged everything else: one theme, one set of content types, one deployment. Config split carries the per-campus overrides, so a campus colour is a configuration change rather than a fork.

What it took

Twelve weeks to the first three campuses, then a repeatable migration per site of about a week each. The pattern mattered more than the deadline: after the fourth campus, the remaining ten were unremarkable.

Your next chapter

Let’s start something that outlives the project.