What step do you think is the most important when it comes to Content Modeling?


Userlevel 3

What step do you think is the most important when it comes to Content Modeling?


46 replies

Badge +1

Analyze the webpage design is the most important step. That’s the time you are looking at the content as a whole and can make the best decisions so you don’t need to change anything in the future.

Userlevel 1
Badge +1

Agreeing with @AmirNo1 here! Whenever the wireframes come in, ensure to analyze this not only as a developer but also with the content team itself. Whenever you slip up it will cause overhead later on in the implementation phase, and that's something you don't want.

Userlevel 1
Badge +1

For me the most important step is the analysis of the requirements. Is where all the information is gathered to guarantee the quality and the work made afterwards is correct and on point with the expectations about the product to build. If this step is done wrong, most likely everything else will be wrong.

Badge +1

The process of modeling content in Contentstack begins as soon as the designs (or even design wireframes) are finalized. Based on the designs, site managers/developers need to identify the structure of content types that need to be created in Contentstack. Developers can then start by actually creating the content type by adding relevant fields

 

Each section/component of your website or mobile app should have an appropriate content model in place. Content types, and thus the actual content, should then be created accordingly for each component. In the next section, we will understand the process of creating a robust content model and looking at creating one.

Userlevel 1
Badge +1

For me, the most important is to make sure the model is well defined at the beginning, based on the designs, by getting it reviewed and validated together between developers and final users (site managers, editors, ...). Any error introduced during the modeling will affect the implementation later.

Badge +1

Agreed with @AmirNo1 . Starting the content modelling exercise at design is crucial. It’s also important to collaborate with your colleagues/team members to ensure they all agreed with the proposed structure.

Badge +1

Like when designing a database with it’s tables and fields, it’s important that in the early phase of the development and in this case of the content modeling, the requirements are clear and the correct content types are implemented as future modifications can be detrimental since the loss of data can happen.

Badge +1

In my opinion, analyzing the requirements is the most important step in content modelling as it forms the basis of content structure. It is important to perform page tackling at the earliest phase to get an idea of each and every field that needs to be a part of the structure. Every minute detail should be discussed at this stage to prevent errors in the future.

Badge +1

In my opinion, finalizing the design requirement is the most important step, as it reduces the chance of overlooking and/or missing a step in content modeling and creation which could cause overwork trouble or worse, lost of data. 

Finalizing a design can make sure different teams (development, product, stakeholders) set expectations that align with the actual scope, which helps them to better organize the content to make the most out of the modeling. 

Badge +1

Making sure that the creator understands how the design flows. If there is no understanding of what fields are needed, a lot of backtracking would ensue.

Badge +1

The most important step is to understand the design and what aspects should be translated to content models in CS.  

Badge +1

Agree with @nagesh , we should also look at the relationships of the content so that we can reuse it via reference content. Understand which content will be displayed on its own as pages or just referenced through other pages. 

Badge +1

Totally agree with @jajimene, the design part is really important and we must take care about it. Changes on the models may cause inconsistencies in the entries and may cause data loss. However, it should be noted that new requirements may appear in the future that may change the modelling, Even so, it should be borne in mind that new requirements may arise in the future that may change the modelling, Even so, it should be noted that new requirements may appear in the future that may change the modelling, so our models should be open to extensions but closed to modifications.

Badge +1

Agree with @dario.rodrigon, we have to be very careful when designing the models but keep in mind as Dario said, that new changes could come and thus, the design might change from the initial one.

Badge +1

I feel the most important parts of content modeling are the evaluation of current Content Author content editing requirements and accounting for any future content updates and new content layouts that will be created.

Every digital product (website, landing page, Mobile app) will go through a natural content lifecycle as new information is curated for display. The best way to mitigate this is to start with a basic set of “Author Tools” / Content Types that clearly describe each layout and establish a naming convention for the variations displayed.

Badge +1

For me the most important step is naming the uid, because you can't change it afterwards. Design needs to follow content, modeling the content is the first step.

Definitely it worth to divide data into groups for maximum reuse. Also it is better to divide data into business valuable and visualisation valuable in order to use them in different channels (web, mobile, iot...)

Badge +1

The most important part is seeing the design and divide its data intro groups to define its type.

Maybe in the future some new features could appear, so we need to think about making our content non-modifiable, but usable and allow the use of extensions.

Badge +1

The most important steps are Identifying structure and Establishing relationships. Perfect Content Types and structure created at initial stage avoids lot of reworks and duplicate fields thus saves time and effort.

Badge

Identifying project requirements, field types, design specs and the styling of the content. 

Badge

For me, the most important is to make sure the model is well defined at the beginning, based on the designs, by getting it reviewed and validated together between developers and final users (site managers, editors, ...). Any error introduced during the modeling will affect the implementation later.


Hi to everyone, realy I am agree with @jajimene , because I had this issues when start explore ContentStack and modeling, definitely it is true, you should before developing discuss all modeling in order to avoid any errors in implementation

Badge

Building a content model typically ends up in the hands of a technical team member like a developer or a content manager. 

However, it’s important for the whole team (e.g., content strategists, content creators, content marketing professionals, and other stakeholders whose jobs impact content management) to understand how and where their content is used.

Content modelling can also help you see the gaps in your existing content. As you can visualize how web pages and other pieces of content work together, you’ll start to see areas where you can improve content production to fill in the gaps, answer FAQs, and improve SEO.

Badge +1

The most important step is to define your content types based on the pages which we are going to build. It breaks content types down into their component parts, describes them in detail, and maps out how they relate to one another. A content model is an important step in working out the finer details and practicalities of how you write and manage your content, and how you will present it on the page.

Badge

The design and mapping are possibly the most important steps to be able to create the right content models.

If you get the design right, you can map out the right components for the content types, and work out which models can be broken down into more reusable parts too, making the content models more robust and more easily changed in the future

I think models should be agreed upon with the designer and the product owner first before starting to Contentstack. Everything will be much easier if they will be planned ahead.

Reply