Products
Team projects
CJ ENM event pages and page builder
I designed the cache policy for the 2025 MAMA event pages and built a page builder so operators could edit and publish seasonal pages themselves.
- Period
- 2025.08 ~ 2025.12
- Organization
- CJ ENM
- Role
- Cache policy and page builder design and build
- Key features
- Operators could assemble event pages in the builder, preview and publish them, and restore earlier versions.
- Work and results
- Separate cache policies for static page content and live voting data
- Operators handle everything from editing to rolling back to an earlier version in one flow
- Builder extended by registering new page blocks
- Tech stack
- CDN
- JSON Schema
Context
For the 2025 MAMA event pages, I designed how content and voting data were delivered. The page body could be prepared in advance, while voting and award results needed timely updates.
New seasonal pages, and even copy or design changes, required developer deployments. I also built a page builder so operators could edit and publish pages themselves.
Decisions and implementation
- 2025 MAMA event page: I made the page body static so the CDN could answer quickly, and refreshed the cache only at the moment award results changed.
- Voting and real-time data went through a separate path that bypassed the cache, with safeguards that blocked abnormal requests.
- I deployed every language at once and split the meta tags by language so search engines indexed each version correctly.
- Low-code page builder: I separated content definition (a JSON schema) from rendering (components), so what was edited in the builder appeared unchanged on the live page.
- I cataloged the web builder’s components in three layers (sections, layouts, and blocks), so operators could assemble a page by dragging and preview it exactly as the live service would show it.
- I added a JSON runtime that lets the live page read the builder’s schema directly, so a new component needed only registration, with no other code change. Editing, preview, deployment, and version rollback became one flow.