← Back to case studies

Content system for the blog

2025-12-23 • content, system, mdx

Built a consistent content structure for blog posts and case studies to ship faster with predictable quality.

Content system case hero image.

Rebuilt the content layer so releases are faster and RU/EN pages stay aligned.

Role
Product Designer
Time
3 weeks
Team
Solo
Stack
Next.js, Tailwind, MDX

Context

The site evolved into a system of notes and case studies. Consistency and speed became critical.

Problem

Content was assembled by hand, structure drifted across pages, and publishing took too long.

Constraints

No external CMS (MDX in repo).RU/EN content parity.Simple structure that works without documentation.

Process

01
Define structure
Lock the required metadata and case blocks.
02
Extract blocks
Turn repeated sections into components.
03
Validate pipeline
Keep build and content validation green.

Solution

I defined a single meta schema and extracted reusable case blocks into components. That made publishing faster and the layout consistent across pages.

Gallery

Content system supporting screenshot.

Results

-40%
Publishing time
Average across two releases
8
Reusable blocks
Core sections
0
Build errors
After alignment
  • A single template for new content.
  • Lower risk of layout regressions.
  • Consistent look for posts and cases.

Learnings

  • Less flexibility, more speed.
  • Components help both dev and editing.
  • Meta fields keep content disciplined.