Sitecore Content Hub Best Practices – Part I

In this blog post, Gaurav Agarwal, a seasoned Sitecore Solutions Architect and MVP, shares his insights on Sitecore best practices, particularly for Sitecore Content Hub development and implementation, highlighting how to refine schema, taxonomy, and flags for optimal architecture and performance.

Learn what is Sitecore Content Hub on this introductory article that overs DAM, Operation, and One Features.

Illustrations depicting Sitecore Content Hub Best Practices

Best Practices for Sitecore Content Hub Architecture, Development, and Implementation

The Importance of Schema and Taxonomy in Content Hub

The Impact of Complex Structures on Graph

If we create complex structures and taxonomies without knowing the actual requirements, it may lead to a lot of pressure on Graph. The Graph is responsible for indexing entities and we should not load it by creating unnecessary relations and entities.

Key Considerations While Creating Schema

When creating schema, there are a few things to keep in mind:

  • Analyze field structure
  • Create a more numeric, Boolean field
  • Create more option list
  • Create less taxonomies
  • Create taxonomies if security is needed on the Content Hub side
  • Create less member groups in the Content Hub schema
  • Apply fewer conditions on fields and member groups
  • Review the cardinality of relations
  • Create less self-relation
  • Create a page for conditions for fields and member group

Focused male programmer coding on a laptop with a monitor displaying code in the background in a modern workspace.

Understanding the Role of Flags in Schema

Specific Flags and Their Functionalities

Taxonomy Flags

When we create a taxonomy field in any schema, it comes with many flags, and it’s important to know which flags can be disabled if we are no longer using their functionality. Below are some flags and their respective functionalities:

  • Inherits security – The entity inherits security settings from its ancestors, which determines access to that entity. For performance reasons, we recommend the inherits security switch is turned off when there are more than two levels of inheritance.
  • Content copied – This option determines whether or not the full-text content is inherited through the relation. It’s important to note that inheritance only goes from parent to child.
  • Completion copied – This option determines whether or not the auto-completion content is inherited through the relation. It’s important to note that inheritance only goes from parent to child.
  • Secured – This option indicates whether or not the relation is visible to all users or to only those with sufficient access rights.

Sitecore content hub - edit member view

Path relation – This allows you to see the parent on the UI. When this option is set to true, the system will create breadcrumbs for the specific relation.

Sitecore Content Hub - Path Relation Flag

For example, the relation between the asset entity and the hierarchical geography entity allows us to see the full geography path.

Sitecore Content Hub - Full Geography Path

Insights into Taxonomy Entity Flags

Navigating to Taxonomy Settings

It’s important to disable the above flags if we’re not using their functionalities. For example, if we are not using these in search, we are not applying any security to these fields. Removing these flags can improve Content Hub performance.

Taxonomy Entity Flags – There are some more flags on the taxonomy side. Taxonomy can be created by going into Settings > Taxonomy.

Main Section and its Flags

After that, when we click on Show Definition inside taxonomy we can see “main” section, which has fields like TaxonomyName, TaxonomyLabel, etc. These also have flags that can be disabled if their functionality is no longer being used.

Sitecore Content Hub - Taxonomy Management

  • Boost – This option is meant to boost particular fields in the search result, such as Solr, Coveo, etc.
  • Include in content – This option determines whether or not the full-text content can be searched.
  • Include in autocomplete – This option determines whether or not the auto-completion content.
  • Secured – This option indicates  the relation is visible to all users or to only those with sufficient access rights.

Sitecore Content Hub - Secured

Work with Top-Rated Sitecore Agency

Is your business looking for guidance with your Sitecore projects? Reach out to Americaneagle.com to discover more about our expert Sitecore development services and learn how we can help your business grow and succeed. As certified Sitecore implementation partners, we have the knowledge and expertise to provide you with a variety of services, including enterprise implementations and integrations, solution audits, version upgrades, training, and more. Check out our Sitecore website examples to learn more about our extensive range of services. 

For more best practices, check out part two of the series: Sitecore Content Hub Best Practices - Part II


About Author

Gaurav Agarwal, Sitecore MVP
Gaurav Agarwal is Sitecore Solutions Architect and four-time Sitecore MVP. Gaurav has several years of experience implementing Sitecore solutions and integrations, he also has experience with Sitecore Commerce as well. In his initial job time, he used to work as a full-stack developer.


Featured Posts