60-second pitch
I rebuilt my Capace internship portfolio so content editors can use WordPress while visitors get a fast Next.js site — without rewriting the original frontend queries.
About the project
This is my main internship deliverable from Capace (Malmö). The first version connected a Next.js frontend to WordPress via WPGraphQL and ACF. In 2026 I modernized the runtime (null-safety, clearer data layer, Vercel deploy) and added a compatibility mu-plugin so legacy GraphQL fields still work.
Outcome
Live portfolio on Vercel, CMS on AwardSpace, and a case-study flow (filter → project page → live deploy). The 2026 refresh used AI-assisted tooling; I verified builds, GraphQL, and deploys myself.
What I focused on
- Headless architecture: WordPress admin, Next.js public site
- Custom `portfolio-cms.php` GraphQL compatibility for legacy fields
- Topic-pill filtering and internal case studies before external links
What I learned
- How to separate content (CMS) from presentation (Next.js) in a real project
- Why compatibility layers matter when you must not break existing queries
- Deploying and debugging a split frontend + CMS setup on free hosting tiers
Tech stack
Next.js 14TypeScriptWordPressWPGraphQLACF
