Home/Blog/How to Write a Contentful Content Model from a Content Brief
Blog

How to Write a Contentful Content Model from a Content Brief

P
promptstudio
How to Write a Contentful Content Model from a Content Brief

Contentful specs invent blog-space and a fake Web app navbar. The brief named Card with heading, image, and summary. Body NOT IN INPUTS.

The matching generator is the Contentful Content Model from a Content Brief (No Fake UI Screenshots) (Contentful Content Model From A Content Brief No Fake Ui Screenshots) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Lock content-type fields before you name a type

Write a Contentful content model from a content brief. No fake UI screenshots or invented slugs. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Content brief I lock (type names, fields I allow): [Brief]
Space I lock (or UNKNOWN): [Space]
Environment I lock (or UNKNOWN): [Env]
Words I must not use: [Banned]
What I must never invent (slugs, extra fields, fake UI screenshots): [Never]
Output format: [Format]
Language: [Lang]
Rich-text fields I allow (or NONE): [Rich]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Bind fields only to names in the brief

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: Brief types and fields, Space, Env, Rich, Lang. Forbidden: invented slugs, extra fields, fake UI.
  2. Field table: each field in Brief quoted with type if Brief named a type. Types not listed stay TYPE UNKNOWN.
  3. Model: content types only from Brief. Fields only from Brief. Space from Space or SPACE UNKNOWN.
  4. Rich text: quote Rich or write NONE. Do not add a rich-text field named Body if Brief omitted it.
  5. Refuse list: Sanity defineType, Strapi schema.json, Webflow CMS dump, screenshot mockups, invented /blog slugs.
  6. Env: quote Env or write ENV UNKNOWN.
  7. Never: do not draw a fake Web app navbar. Do not invent sys.id values.
  8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Refuse Sanity dumps and screenshot mocks

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Contentful content model from Brief only. Not Sanity and not a screenshot.
  • Never invent slugs, extra fields, or fake UI.
  • Rich-text only if pasted.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Keep rich-text NONE if the brief omitted it

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (contentful content model, content brief lock, no fake ui screenshots) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.