Catalogue Table of Contents with the New UI

overview in the new ui, we have set out to reorganize the content hierarchy to improve the way we present content so that it is more consistent and easier for the user to comprehend this is done through a set of guidelines specified in extension content docid\ k9e w3zzkehm38jtvqkyu and reference catalogue ui levels docid ldaupnkv7qcfm3knmhms that laid down the framework of content architecture in general, most of the ui work in catalogue driven extensions is already handled by core, so the bulk of the work will be on ensuring that the data is clean and structured correctly this article is a primer on the new table of content based toolbox (toc toolbox) structure in catalogue creator, for anyone looking into adopt the new look for their data driven catalogue extensions we will cover both pure data driven use cases and hybrid (code and data driven) use cases the old approach in catalogue creator, traditionally ui levels are used to define product levels in the table of contents, and it must be used in conjunction with the drag and drop visual builder interface of the old component tab creator but there are significant amount of use case gaps with the old system, such as finding ways to have more than 3 depth product levels (i e "chair" section > "swivel" section > " number of wheels " subsection > " product line name " subsection > etc ) can technically have an infinitely deep product level tree, however it is problematic from a ui/ux perspective as well as how well cet has supported it user confusion with how the section/subsections/icons/none ui levels behaved and interacted with each other trying to build libraries that break conventional ui/ux norms table of content driven toolboxes we have added a new checkbox in catalogue creator that allows you to opt in to the new behavior which will build the toolbox based on the table of content structure this disables the old component tab creator feature this allows you to have ui levels that are standardized according to our ui/ux guidelines have an increased and reasonable amount of product level depth easy to find out invalid configurations, imparting guidelines for properly arranging the table of contents we have added a new presentation configurator to configure how buttons will look, catalogue table of contents with the new ui /#ui level validation and a catalogue table of contents with the new ui /#previews in cet find out more in the catalogue table of contents with the new ui /#new features section new table of content structure we have updated the definitions of the product level's ui level to make them more consistent with how it works for traditionally programmed extensions use card, tab, tool groups ui levels to add more levels to the table of contents read more at reference catalogue ui levels docid ldaupnkv7qcfm3knmhms migration migration effort depends on how your library is implemented, as it varies whether your library is a "pure" or "hybrid" catalog library here are some references "pure" catalog library "pure" catalog libraries are ones created in the component tab creator and then made visible in catalog explorer as described in this support article you can follow tutorial structuring your table of contents for data driven catalogues docid 8agivqykiirq5mtadudq if yours is a "pure" catalog library "hybrid" catalog library these libraries refer to ones created using a combination of cm coding and data driven catalogue work in code, we reference the specific catalog of our needs, which is then used to assist the system in the automatic creation of a library there can be varying degrees of "hybrid" depending on how much is done through code please refer to tutorial facelifting hybrid catalog libraries docid 2ar9 c7l1elrgbl81vbib future plans with the introduction of the new toc structure, we will be deprecating the following two features in a future release component tab creator old ui level structure we aim to deprecate the above two features sometime in late 2025 this will remove the use toc toolbox checkbox, and automatically have it always enabled by default all customers using the old component tab creator are encouraged to migrate to take advantage of the new features streamlining development efficiency and adhering to the new ui standards new features new ui levels you can now add cards, tabs, subsections, and tool groups in the toc read more at reference catalogue ui levels docid ldaupnkv7qcfm3knmhms presentation configurator presentation configurator allows you to configure the visual layout and arrangement of your toolboxes generated from toc, without writing code these ui levels and properties can be configured cards icon, banner image (coming soon), schemes (coming soon) sections / subsections product button sizes, label variants ui level validation with so many extra ui levels, along with its rules (i e a section cannot be inside a tool group), we have added validation on the fly when organizing your toc notice when you first press the use toc toolbox check, the ui level column will show red on each product level cell that are invalid when you hover onto an invalid ui level cell, a tooltip will show, listing down all the reasons it is invalid if you need more guidance on how to resolve these go to the validation tab enable product catalog table of contents hit the run validation(s) button select the product catalog table of contents in tasks the results will give your a more detailed explanation and guidance in solving invalid product levels previews in cet changes done in the table of contents will show as a preview in cet the preview will immediately update when any changes are done on the toc