Reuse approved content through a contract consumers can depend on.
Should the same information serve your website and another digital channel? ImbaHub can develop a bounded read interface with explicit field contracts and tests against named consumers. This is a separate development scope rather than a claim about a standard Imba CMS feature.
- Approved source
Only the agreed version and fields may be delivered.
- Contract
Types, languages, empty values and version are explained.
- Consumer
Each named view can handle delivery and failures.
Reuse needs shared meaning as well as valid JSON.
A new field is optional, but the older consumer rejects unknown properties. Compatible?
Not without a change or a separate contract route. Test the old consumer before changing delivery.
Choose the content and real consumers
Start with one information group and the systems that will actually read it. Establish the authoritative source and required publishing approval. Information in an editor's workspace is not automatically intended for every channel.
A fictional training provider might reuse approved course titles and summaries in a website view and a separate catalog. Internal comments, drafts and private fields do not automatically belong in that delivery. Each consumer needs a defined selection.
Write the field contract before connecting systems
Define each field's meaning, type, language, source and whether it may be absent. Missing values, empty strings and explicit null can mean different things. A content or product identifier should not change identity when a heading is translated.
Also define lists, references and deleted records. The receiving channel's support determines which formats need testing. A valid schema does not establish that the content will be understandable or correctly presented.
| Part | Decision | Consumer test |
|---|---|---|
| Identity | Stable key and language rule | Record recognized after a text change |
| Fields | Type, meaning and required content | Missing and null follow the contract |
| Publishing | Which version may leave the source? | Drafts do not leak accidentally |
| Lists | Order, boundaries and completeness | Consumer does not miss the next part |
| Change | Version and compatibility ownership | Old consumer tested before switching |
Bound access and failure outcomes
Decide which deliveries are public and which need authenticated access. Do not place an access key in public browser code and treat it as a secret. Exclude private fields from the delivery rather than merely hiding them in the receiving interface.
Test unavailable sources, incomplete lists and deleted references. An empty response should not silently imply that the business has no services when a technical fault caused it. Agreed fallback behavior and freshness feedback need explicit conditions.
Hand over a contract and tested consumer route
A first scope can cover one content type, one source and one or two receiving views. Test approved delivery, draft exclusion, languages, failures and an agreed contract change. A tailored proposal follows access review and actual consumer needs.
The delivery documents fields, fictional examples, version, failure model and ownership when a consumer changes. Write workflows, automated translation and extra channels are separate scopes. We do not invent existing integrations or results already achieved.
Sources and further reading
Questions, answered
Is this API automatically included in Imba CMS?
No. This page describes a separate development scope. The actual installation and product support need review.
Is a new optional field always safe?
Not for every consumer. A strict client may reject unknown fields; test its actual behavior.