Once the base data structure has been defined and published, the base owner and guests with Content editing permission will be able to add, edit, and remove content from that base.
All of this is done via the Content tab.
Making base content available to experiences
Content added to Group or Collection is not visible to experiences until that content is published. Before publishing, the data is hidden from the experiences using that base.
To make content visible to experiences, follow the H-CMS publication workflow.
Using component images to convey the target user interface
If the structure editors and content editors are different people, it can be a good practice to include labels in the image you can assign a component, labels illustrating how the component properties map to UI elements in the final project. In the following example, the component named "General Settings" has been assigned an image identifying each UI element:
Of course, this mock-up image is not a requirement. In fact, nothing prevents the use of Headless CMS before a user interface exists.
Content stored in a well-formatted CSV file can be imported into a selected Collection.
In the planning stages is the use of a dedicated API to sync an H-CMS base with a third-party enterprise data management system. Stay tuned!
Article is closed for comments.