Recently active topics
Hello dear all, Could you help me to figure out the following/any best practices you use, as well as, risks/limitations? Modular block/Global typesUse case: We are about to have 7 page content types which will include modular block. Each page has different modular block (with different set of elements/blocks in it). However, elements within the blocks will be repeating themselves (in terms of structure, not content).Question: What is the best practice to organize modular blocks?a) Should there be content types for each of the element that is in modular block if the content is not consider as repetitive for other pages? Could here be a good place to use global data?b) Should there be created a structure for each element of modular block + one block that is reference which will allow to reference any of allow content types for this block in case of reusable content 1.1. Should we consider any naming convention for the modular blocks? Thank you.
We are excited to announce the general availability of Automation Hub, an integrated automation and streamlining tool for the Contentstack platform. As we transition out of our Early Access phase, customers who were previously beta testing Automation Hub will be moved to our Explorer Plan, which offers up to 200 executions at no cost each month. Since Contentstack does not count additional usage for multi-step automations or charge extra for premium connectors, 200 executions is a generous allotment that can be used in production to help with critical but lower-frequency business tasks. Also, paid plans are available for those interested in additional usage of this valuable streamlining tool.Some highlights for the release include:The new JSON RTE Formatter connector streamlines the output of JSON RTE fields to work more efficiently with third-party integrations. Improved connector actions enable additional functionality. New actions to several connectors, such as publishing assets an
The January release of Automation Hub is a game-changer. With a host of new features and improvements, this release will make it easier than ever to create and manage automated workflow processes to streamline your integrations and workflows. What's new in this release: New actionable step outline toolThis new outline will display the automation flow of steps, and a user can easily jump into any step and edit it just by clicking on the step within the step outline tool. The outline is a visual display of the full automation process and logic. This feature is designed to make it easy to build and maintain complex automations with ease.In addition, the step outline now features a search capability that, as you’re typing a query, will automatically filter results to display the search term. Automation Hub’s new Step Outline. Each step is displayed in a new, easy-to-read vertical displayNext, after clicking on a step in the step outline, we have a step wizard on the right side of the page
As a former marketer, software developer, and now software architect at Levi Strauss & Co, Zach Crittendon details the psychology behind tech strategies that make marketing teams more autonomous.Listen here: People Changing Enterprises Podcast - EP 17: Carrots, not sticks: building tech for autonomous teams, with Levi’s Zach Crittendon
Software architect Zach Crittendon of Levi's implemented some of the company’s first composable retail technology and has acted as an advisor to many brands in helping them navigate this new space.In this episode of People Changing Enterprises, hear how Levi's has leveraged composability to achieve unparalleled success—and learn how your team can do the same.Listen here: People Changing Enterprises - EP 16: Moving to a composable architecture, with Levi's Zach Crittendon
I’ve noticed that relationships are not show in the CT Visualizer Dev dashboard (available with the Content Type Visualizer app) when these relationships are established through a global field or through a modular block.Does this mean that a relationship established through a global field is lesser in any way? Is there any difference in functionality when doing API calls, for example? I would expect these relationships to be exactly the same, and for them to also be displayed in the visualizer.What about a relationship established through a modular block? It would be great if these could still be displayed, but maybe with a dashed line instead of a solid line, to show that the possibility of a relationship more strictly depends on the entry than the model itself.
I find the seemingly interchangeable "content models" / "content types" terminology confusing.It might make more sense if "Content Models" were singular ("Content Model"): It would make it clearer to users that their content model comprises one or more content types (of which global fields are one kind). In this case, there is a clear distinction: the content type is part of the content model but not vice versa.Or am I missing something?
Login to the community
No account yet? Create an account
Contentstack LoginLog in with Contentstack
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.