Overview

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.

Adding new items into a Group

On the Content tab, select the desired Group in the left-hand components column. Then, on the right, fill out each of the fields assigned to this group. In the following image, the "Title" and "Logo" fields need to be completed.

Adding new items into a Collection

On the Content tab, select the desired Collection in the left-hand components column. Then, to add a new item, choose from one of two options:

• Click the "Add New Item" button.
  With this method, a new item is added to the end of the list.
  
  
  OR
  
  
• Hover your mouse above the separator between two existing items and click the + button that appears.
  With this method, a new item is inserted between the two existing items.
  

Making new items visible to experiences

Content added to Groups or Collections is not visible to experiences until the updated bases are published. Before publishing, the new content is hidden from experiences using the base.

To make new content visible to experiences, follow the H-CMS publication workflow.

Importing content into a Collection

Content stored in a well-formatted CSV file can be imported into a selected Collection.

The use of a dedicated API to sync an H-CMS base with a third-party enterprise data management system is in the planning stages. Stay tuned!

Tip: Using the 'component image' to convey the target user interface

If the Structure editors and Content editors are different people, it is a good practice to include labels in the image you can assign a component in the Structure view. These labels would illustrate how the component properties map to UI elements in the final project.

In the following example, the component named "General Settings" has 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.