All engineering work03 / Community website
2 min readBilingual Theater Website
I co-designed, developed, and deployed a bilingual website that organizes productions and current information for a real theater organization.
Problem
Make current productions, participation information, and the theater's archive accessible to bilingual audiences.
My contribution
Co-design, development, and deployment, including structured content, bilingual routes, and metadata.
Engineering focus
Content organization and validation that help keep an evolving community website maintainable.
Useful information across languages and seasons
The website serves UW Chinese Theatre Club, also known as May Drama. Audiences need current production information; prospective members need participation details; the organization also needs a place for its past work.
The project is collaborative. I co-designed, developed, and deployed the site, and implemented structured production data, bilingual routing, SEO metadata, and automated content validation. This is not a claim of sole authorship of the site's design or the theater's content.
Treat productions as structured content
Production records provide a consistent way to organize the archive and its detail pages. That structure makes titles, media, and related information easier to maintain across pages.
The engineering work focuses on predictable content structure as the archive grows. The public site lets visitors move from the archive to individual productions and switch between Chinese and English routes.
Check the connections between pages
I added automated validation for internal links, media assets, and metadata. These checks address common content-update failures: a page can look complete while a linked destination or referenced image is missing.
Bilingual routes and page metadata are part of the implementation, alongside the responsive presentation. They support access to the content beyond a single homepage visit.
Evidence and maintenance boundaries
The live website demonstrates the production archive, language routes, and current organization information. The technology and implementation summary here describes the project version in my engineering experience.
No test count, traffic result, or conversion claim is included. This overview does not imply a non-technical CMS, administrative dashboard, or one-click editorial workflow. It also does not assign other collaborators' responsibilities to me.
Next project
