The Structure panel enables you to define what kind of content you want to use in your experience and how you want it to be organized.
You can add as many Components to your base data structure as you'd like. A Component can be
- a Group: a single instance of related properties. You can use a group for general information or content that may be used across your entire experience, or you could create one group per scene. It all depends on your experience structure and organization.
- a Collection: a list of items that will share the same set of properties. An H-CMS collection can be used as a data source for the like-named Collection in Intuiface Composer.
You can also define Variants in this panel, which will be detailed in this article.
What should you put in the base structure?
When starting to build an Intuiface experience, you might at first go back and forth between Composer and the H-CMS, figuring out what should be defined on one side or the other. Here are some best practices and examples to help you make that decision.
Note: The word "content" below can be any type of property that you can define in the H-CMS. See all H-CMS property types here.
- How often will the content change?
- Never: Set this content directly in Composer rather than use the H-CMS. Examples include title text and a background image.
- Several times a year or more: Set this content in the H-CMS so it's easier to update. Examples include "Employee of the Month", "Seasonal Sales Promotions", etc.
- Who will update this content?
- You and/or teammates using Composer (e.g. the experience creators): If the content is supposed to change on a regular basis, it's ok to define it in Composer, unless you want to make your life easier in the future.
- A non-Composer user (e.g. colleague / partner / customer / content provider): It's a good idea to define this content in the H-CMS as it eliminates the need to understand or use Composer. You will be providing them with easy access, through a web browser, for making updates.
- How many items are you going to present with a similar layout, a.k.a how many copy & paste actions are you preparing to take? The threshold is a personal feeling, but as a rule of thumb:
- Less than 5 instances: You might consider building one scene per item in Composer and handle the copy & paste, especially if you are sure the number of items won't grow and their content won't change in the future.
- More than 5 instances, or if you are unsure of the final number of items or how often they will be updated: You should consider creating a collection in the H-CMS, then use the data template mechanism in Composer.
Publish your data structure
All changes are automatically saved but won't be published until you click the "Publish structure changes" button. Until then, your new structure components or modifications won't be visible in the Content panel.