feat: complex content exploration

[nperez0111]

This PR explores the possibility of introducing more complex custom content types.

Summary

Taking a table as an example:

[
  {
    "id": "abc",
    "type": "table",
    "content": {
      "type": "tableContent",
      "rows": [
        {
          "cells": [
            {
              "type": "tableCell",
              "content": [
                {
                  "type": "text",
                  "text": "a",
                  "styles": {}
                }
              ]
            }
          ]
        },
        {
          "cells": [
            {
              "type": "tableCell",
              "content": [
                {
                  "type": "text",
                  "text": "b",
                  "styles": {}
                }
              ]
            }
          ]
        }
      ]
    },
    "children": []
  }
]

What would happen if we decided to make this pattern more generic & exposed to the end developer? It could maybe look something like this:

createBlockSpec({
	type: 'table',
	content: c.customContentType('tableContent', c.record({
		rows: c.arrayOf(c.customContentType('tableCell', c.record({
			content: c.inline()
		})))
	}))
})

This sort of a structure would allow for representing arbitrarily complex relationships and enables multiple "slots" for content to be inserted within.

This is very powerful, but presents several challenges:

• This would require creating intermediate prosemirror nodes, and their shapes and configuration should be cleanly defined (hopefully without exposing that complexity to the API)
• There will be many edge cases with how this works UX-wise, this will inevitably force us to expand to a much more complex API surface than we currently expose
• This encourages divergent schemas where no two editors have the same schema, hurting interoperability

Rationale

I explored a few different approaches for this, and none were satisfying to me. It felt like we were simple re-packaging what ProseMirror can represent, and drifting away from the benefits that BlockNote touts.

Some more exploration would be needed for this to actually be considered a viable solution for BlockNote. It simply is largely in contradiction of the goals of BlockNote.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blocknote	Ready	Preview	May 5, 2026 0:50am
blocknote-website	Error		May 5, 2026 0:50am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 73cbafd7-5725-41f6-bc5c-d22666d7125d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/content-schemas

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}