Private / redacted

Tactical Tech Platform Modernisation

Frontend delivery and modernisation across public-facing platforms for research, education, and civil-society audiences.

Role: As Front-End Developer, owned frontend delivery and modernisation decisions across 5+ public-facing platforms and partnered with product, design, research, and editorial teams.
Result: Migrated three legacy applications while improving initial loads and editorial workflows.
Stack: React · Vue.js · Next.js · Nuxt.js · TypeScript · Decap CMS

System architecture

The building blocks in view

Read the system as text

EditorsEditorial users manage public content.Connects to Decap CMS (manages).
Decap CMSGit-backed editorial interface.Connects to Git-backed content (commits).
Git-backed contentMarkdown and frontmatter form the shared source material.Connects to REST Content API (serves).
REST Content APIProject namespaces expose content and search queries.Connects to Next.js and Nuxt.js sites (content queries), Central search (search queries).
Next.js and Nuxt.js sitesPublic applications consume shared content.Connects to Visitors (public content).
Central searchQueries selected API namespaces.Connects to Visitors (search results).
VisitorsUse public sites and search to reach project content.

Key decisions

Reason: Allowed publishing to continue while legacy applications moved to modern frameworks.
Trade-off: Old and new application structures coexisted during migration.

Reason: Addressed repeated editorial work at the content boundary instead of only in the frontend.
Trade-off: Required coordinated changes across content and application structures.

Reason: Applied code splitting and lazy loading where they improved initial loading.
Trade-off: Introduced more intentional loading boundaries.

Outcome

30%

Code splitting, lazy loading, and frontend optimisation.

50%+

Refactored Decap CMS content architecture.