The problem
Not every page a registrant needs is a large dashboard build. This university’s Swoogo site also needed a plain way to browse upcoming events, and a way for students to find and download the course materials tied to their own sessions. Small requirements, but ones a generic Swoogo page template wasn’t quite shaped for.
The approach / solution
- Built an event-directory listing page in two layouts: one with thumbnail images per event card, one text-only for pages where imagery didn’t fit. Same event data, two presentations.
- Built a PDF list-and-download widget so registrants can browse and pull the course or session PDFs tied to their own record.
- Both delivered directly inside Swoogo’s native Twig templating system, the same page-builder-native approach used across this client’s larger widget set.
- The PDF widget’s document list is kept current by a backend PDF file-management module built for this client, part of the same platform work covering its Banner and MS Dynamics syncs.
Outcome / result
Two small, working pieces of a bigger registrant experience for this client: an event directory in whichever layout a given page calls for, and a course-materials list that pulls straight from the client’s own document management. Neither is the flagship build on this account — that’s the 1,300-line self-service dashboard covered separately — but both are in daily use alongside it.
Why it matters for enterprise event-tech
Not every deliverable on an account is the headline feature. Being able to turn around a straightforward listing page or a document widget at the same quality bar as the larger builds, on the same Twig-native foundation, is what keeps an account’s smaller requests from becoming their own separate mess of one-off patches.
