01
What it is
A page builder that lives inside your codebase.
You define blocks, schemas, effects, and rendering. Authors arrange valid data. Nubbin compiles it into an artifact.
Nubbin for developers
Your code.
Your pages.
Do whatever the @!*# you want with it. We’ll be here, or not.
02
What it does
It gives you contracts and the means to use them.
Edit, validate, compile, publish, resolve, and render. Nothing in that list requires a Nubbin account or production API call.
03
What you own
Everything with consequences.
Your components. Your storage. Your routes. Your authentication. Your permissions. Your deployment. Nubbin calls the functions you provide.
The mechanism
Data goes in.
Your code renders it.
documentmutable block datacompile()validate the contractartifactimmutable outputrender()your componentsStorage is a callback. Publishing is a callback. Authentication is your problem. That’s intentional.
Start here
Install it. Inspect it. Change it.
Start with the filesystem adapter. Replace it when you have a reason.
pnpm add @nubbin/core @nubbin/react
pnpm add @nubbin/next @nubbin/store-fs
pnpm add -D @nubbin/cli
pnpm nubbin doctorPick your boundary
What do you bring to the table?
I already have a React or Next.js application.I want the editor locally and delivery somewhere else.I want hosted Studio and my own publishing infrastructure.I want content changes to trigger a static rebuild.I want Nubbin outside the production request path.I want several applications to consume the same content.I want to hand editing to a client.I want to build my own editor.I want to replace the artifact store.
Packages
Take what you need.
@nubbin/core- Contracts, validation, and compilation.
@nubbin/react- Render artifacts with your React components.
@nubbin/next- Resolve routes, previews, and artifacts in Next.js.
@nubbin/studio- Editor contracts and transports. Bring your own UI if you want.
@nubbin/studio-ui- The assembled editor UI. Use it, replace it, or ignore it.
@nubbin/cli- Check, compile, publish, and roll back.