Anatomy of a Block
You can think of your Repository as a tree of Blocks. Let's explore how this works.
Similar to Notion’s data model, every piece of content in BaseHub is a Block. You can think of your Repository as a tree of Blocks. It all starts with the Root Block—although you won’t see it—, which has nested Blocks within.
We conceptually split Blocks into two categories: Layout, and Primitive Blocks. In the next sections, you’ll read more about them.
Blocks contain schema and content. In contrast to other CMSs, where developers define a schema and then add the content, in BaseHub, this can happen at the same time due to how flexible our data model is.
As you add new Blocks and nest and reorder them, you’ll be altering your Repo’s Schema. That is, the structure that will be then distributed via GraphQL and into your website. Schemas become composable with a special Block called “Component”. Read more about it here.
UI
This is how Blocks get rendered.
Zoom into a specific Block
In this case, a Text Block.
Slash command
To add new blocks.
Sidebar
Makes it easy to get around your Repo.
Tabs
Shows active Blocks.
