These docs assume you have access to Github, Vercel, DatoCMS, Figma and preferably 1password. If you don’t yet, ask around on Slack.

Preparing models

Before any implementation of either code or CMS models starts, we want to have a clear path forward. Once the design is shaping up, the lead on the project or the team together looks at the design prototype and starts thinking about the requirements for the data behind it all. Any new blocks required? Any niché business-specific models needed?

Creating a schema graph

Once there has been an established plan for what shape the project will take, we can start making a graph. This can be somewhat high-level. Doesn’t need to be a full on UML database relational diagram, but just some way of visualising the project data structure.

Use Figma, FigJam or some other diagram graphing tool.

Example

Preparing Forge

At this stage, we also want to think about what features, models, blocks, plugins or other things we may want to generalize by putting into the Forge template repository and Forge DatoCMS project. This is worth doing before creating the project git repo and Dato project.

Setting up Git repo

• Open up the Fully Studios organisation in Github
• Navigate to create a new repository
• Make sure you use the fullystudios/forge template if applicable to the project
• Select the fullystudios organisation namespace
• Name the project in the same manner earlier project are named. Lower case letters, dash-separated words, concise and clear, avoid using abbreviations.

Creating models

When graphs and following discussions are done, we begin in the CMS. Before anything, the DatoCMS project needs to be created, if it hasn’t been already. Create a copy of the Forge template project in Dato.

Once that is done, create the models and add their fields. Iterate early here, to find a good balance between CMS UX and code DevX. Keep in mind that not everything needs to be dynamic or editable via CMS.