How to author schema-driven structured content and consume it across channels

This demo showcases how Structured Content in Document Authoring (DA) enables schema-driven, form-based content editing that powers EDS blocks — and exposes the same data as a JSON API for headless consumption on any channel.

For detailed setup and configuration, see the official documentation at https://docs.da.live/developers/guides/structured-content

Setup & Configuration

• Review the FAQ JSON schema for your content in the Schema Editor at https://da.live/apps/schema#/scdemos/demo — with fields, types, enums, and nested objects.

• Review sample FAQs in the configured faqs content folder and preview/publish them: https://da.live/#/scdemos/demo/faqs
• Review the DA Config for the faqs folder to use the Structured Content: https://da.live/config#/scdemos/

• Review the index for the faqs using the Index Admin tool at Index Admin

Demo

This demo takes you through a journey from an author's view to:

1. Browse the /faqs/ folder in DA and open an existing FAQ in the form editor: https://da.live/#/scdemos/demo/faqs
2. Navigate to the demo site to see the FAQ block rendering on a page, filtered by category Getting Started: https://main--demo--scdemos.aem.page/drafts/sagar/faq-getting-started
3. Review the DA Author page for the same: https://da.live/edit#/scdemos/demo/drafts/sagar/faq-getting-started
4. Author a new FAQ live in the form editor — fill in fields, select the category Getting Started from the dropdown, add a related link
5. Preview and publish the FAQ
6. Refresh the https://main--demo--scdemos.aem.page/drafts/sagar/faq-getting-started and the newly authored FAQ shows up automatically
7. Open the da-sc JSON endpoint in the browser to show the same content available as a headless API: https://da-sc.adobeaem.workers.dev/preview/scdemos/demo/faqs/faq-6

How it works

• Structured Content stores each document in DA — authored through a form editor backed by a JSON Schema definition.

• The schema enforces structure: required fields, category enums, and typed arrays for related links — so authors can't go off-model.

• The Index Admin tool indexes the /faqs/ folder using CSS selectors, extracting question, answer, and category — making content queryable at /faq-index.json.

• The FAQ block fetches this index, filters by author-specified categories in the block table, and renders an accessible accordion — no backend, no build step.

• The same structured content is independently available as raw JSON via the da-sc endpoint, making it consumable by any channel: mobile apps, partner sites, chatbots.

Note: FAQ block source code at github.com/scdemos/demo/tree/main/blocks/faq

Key Points

• Structured content documents are indexed like any EDS page — no special pipeline or custom tooling needed beyond the index configuration.

• The same JSON is available headlessly via the da-sc worker endpoint — any channel can consume it without touching the EDS site.

• Schema changes don't require code changes in the block — the block reads whatever fields the index exposes.

• Authors work in a guided form UI with dropdowns, validation, and structured fields — no freeform document editing, no risk of breaking the layout.

Related Articles