Privacy choices
This site may send the owner a minimal page-visit notice with page, browser, device type, and resolution. If you accept analytics, it can also remember an anonymous visit/session ID and collect richer engagement signals.
Read the privacy noticeUsed in: alex-cms-project
Designing configurable content types, fields, relationships and permalinks.
Designing configurable content types, fields, relationships and permalinks.
This CMS's entire content-type registry — including Expertise and Skills.
This CMS's entire content-type registry — including Expertise and Skills.
Alex uses dynamic content modeling to define every content type, field, and relationship in a CMS at configuration time — no hardcoded models required.
Dynamic Content Modeling
Designing configurable content types, fields, relationships, and permalinks. This skill sits in CMS architecture and is actively in use — confidence level: practical, with real production application.
Where it's applied
This skill drives the entire content-type registry in Alex's CMS project — including the Expertise and Skills entries you're browsing right now. The registry is fully dynamic: no post models are hardcoded anywhere in the codebase.
What this means in practice
Rather than writing a new model for each content type, Alex configures types, fields, and relationships through a registry layer. The Alex CMS project — built on Next.js — demonstrates this end-to-end, and the Dynamic CMS Architecture expertise covers the broader design approach behind it.