Power Productivity: How to optimize your composable stack for large-scale organizations and deployments

"Setting up the system and determining the general content model primarily rests with the developers, who are tasked with architecting the content. They consider different omnichannel avenues for delivery, the composability of their content and its reusability across various channels. This forms a crucial part of the overall content architecture. Developers initiate this process when they create content models within Contentstack. It's a collaborative effort involving developers, content managers and editors. They work together to define the structure for delivering content to diverse audiences and manage how this content is presented and handled."

"There are challenges for users managing large volumes of diverse content types. One issue is the sheer amount of content to sift through. Another is content modeling in headless CMS, where the structure around content types might not align with how editors perceive their content organization. Editors often think in terms of topics, categories or how a site map might look rather than a direct one-to-one mapping. This requires them to consider the architecture of content, which can be challenging. Content types might include elements like headers, footers or body sections within a page. A single content type could encompass all these elements, facilitating data reference and reuse across different pages, but this might be confusing for editors who are accustomed to page-level navigation. Therefore, content types within a content type are a possibility.”

"Currently, our customers navigate their content using content types and labels, which help create a hierarchical structure. Content types and labels are the existing methods for navigating content. We are introducing Taxonomy as an additional method for organizing and categorizing content, transcending multiple content types. This approach doesn't require users to know exactly where all their content is; instead, it focuses on how they want to organize it, potentially mirroring their site maps. This hierarchical structure is familiar to most customers in managing their web properties. Taxonomy will enable the categorization and organization of large content volumes. While filtering by content type is still an option, Taxonomy will simplify navigation and may reduce the need for such detailed filtering."

"Our current editor views segments content by type, such as different articles and labels. The introduction of Taxonomy allows content to be segmented and categorized in a more readable format. For example, our site map allows navigation through homepages and different landing pages, and regional segmentation, like for Europe, is more accessible. Previously, finding specific content required searching and navigating through various labels and content types. Taxonomy simplifies navigation, addressing customer pain points and providing a familiar file-like hierarchical structure. Previously, we had a feature called tags, which was more freeform. Our customers expressed a need for a well-defined categorization method. Now, they can create multiple taxonomies, like those in our site map, or hierarchical structures for different regions. As content grows, so will Taxonomy, offering an efficient way to manage terminologies and categorize content."

"In our headless CMS, developers have control over how content appears and displays while maintaining governance. I want to illustrate how the site map mimics web properties, easing the job for editors. Developers can control where taxonomies are applied. For instance, in the homepage content type, there's a new field for taxonomies where you can specify which can categorize this content. We're adding the site map here. There's also flexibility to make this Taxonomy field optional or required, ensuring that editors categorize every new entry. Once added, this Taxonomy field appears for editors in their homepage view. They can see all the terms created, making it clear what categorization applies to the content. This feature aids editors in easily navigating back to their content from the site app."

"Managing permissions as they onboard more users is essential for larger organizations with complex permission structures. Currently, this process is manual, involving provisioning or de-provisioning permissions for individual users. We are developing a new Teams feature, which will allow bulk addition of permissions to a user. For instance, a group of editors working on specific content will always have the necessary permissions within their team, and users can be easily added as team members. This feature will facilitate managing various permission sets and efficiently provision permissions to all users. Concerning team size, it can involve hundreds of users, possibly across different stacks, each with access to distinct content types. We are also exploring permissions for different regions, like languages, and plan to include taxonomies as another way to control content access."

"The suitability of Teams and Taxonomy for an organization varies. Teams is particularly beneficial for enterprise customers with many teams and large content volumes. Smaller customers, such as a team of five, might not find Teams immediately useful, but it remains a viable option as they grow and scale. The number of users that becomes challenging to manage is a key factor. For Taxonomy, the benefits also range widely. While enterprise customers gain significant advantages in organizing large content groups, smaller customers find it improves content navigation. They may not utilize all Taxonomy applications, but it simplifies their content management."

"To gain early access, reach out to us, and we'll enable it within your organization. In early 2024, we will offer general access to all our customers. Once released, you'll see new Taxonomy settings, and you can begin creating taxonomies. …Both Teams and Taxonomy will be available within the Developer Fastrack program as well."