Design a JSON content contract that travels
Define field meaning, ownership, body formats, validation, and versioning before connecting content to multiple destinations.
7 MIN READRead the guide
FOLLOW A THREAD / 3 ARTICLES
Content models
Make content understandable before making it portable. Explore fields, record ownership, prompt inputs, and the transformations required by a CMS.
A connected reading path
Begin with the JSON contract guide to distinguish content revisions from schema versions. Then use the WordPress and prompt-library articles as practical examples of where that contract meets another system. Keep valid and invalid examples beside the documentation. Those fixtures help editors and developers discuss meaning instead of guessing from the last payload that happened to work.
Make this useful to your project
Choose the article closest to the decision you are making today. Note the source record, approval boundary, destination, and verification method it proposes. Compare those assumptions with the system you actually operate. Keep unresolved questions visible, and follow the related topic links when you need to examine a specific platform or implementation layer in more detail.
WordPress REST API: start with a draft
Map a complete post, preserve its destination identity, preview the theme, and make publication a deliberate editorial step.
7 MIN READRead the guide
Build a prompt library your editors can trust
Organize prompts around real editorial jobs, bounded evidence, reviewable outputs, and repeatable comparisons.
7 MIN READRead the guide