cd ../work
The university's site, front and back
A university site editors build from blocks and visitors get fast, on a phone first.
30
page blocks editors combine
16
custom Drupal modules
2/3
loop stages owned
01 Context
The university's own research (interviews, focus groups, surveys and analytics) said the new site had to be more accessible, work well on a phone and be easy to get around. Editors across the university had to keep publishing without a developer.
02 /build
We kept Drupal for the editors and moved the front end to Next.js, reading content over GraphQL.
- 8 content types, 30 paragraph types and 9 media types for editors
- donations with Mercado Pago, plus Salesforce and the events system
- editor sign-in with Google and per-department permissions
- launched in Pantheon's early-access program for decoupled sites
03 /run
We run it in production, from the platform to the code.
- move to Pantheon's new Next.js platform, with releases promoted by tag
- Drupal 9 to 10, after the university's security audit
- an intermittent 404 traced from an empty GraphQL field, through incremental rendering, to the CDN cache
- A/B tests for marketing, loaded only on the pages under test
Promote merges into test and live to Pantheon Next.js via tags
Mirror Pantheon deploys to UdeSA GitLab
Load VWO only on pages with an active test
Bump next to 15.5.28 04 /automate
Next: AI for the editors, for the people who visit the site and for the marketing team. The site already publishes an llms.txt for AI assistants.