Content shaped by files
Collections, blueprints and fieldtypes declared in YAML, entries checked against them, edited in a control panel and rendered on the server by a Vue theme.
The road ahead
Nothing here has a date on it. Behind the pin is what has shipped, each with its release. Past it is what is being built, and what is being weighed up.
- Shipped 15
- Being built 1
- Next up 1
- Considering 2
A folder of Markdown is a collection
Name a folder in a collection's schema, and the Markdown files in it are its pages.
Feeds and landing pages
A collection can have a feed and a landing page of its own, and a visitor's light or dark choice survives the first paint.
A public home
The code is on GitHub, and the project lives at nibble.ink.
Markdown served straight from its folder
A collection written as files is read from the files themselves, with no database copy to keep in step.
Installed and upgraded as one folder
Nibble lives in `vendor/nibble` and loads as a Rails engine; an upgrade replaces that folder and leaves the rest to the site.
Search, updates and emails, tidied
Search that filters by collection and leaves out what you mark, updates that page in ten at a time, and emails with a design a site can make its own.
Plain Rails, and the Control Plane at /cp
Every Rails setting where a Rails developer looks, none of the names Rails generates taken, and an idle session that ends on the server.
AI apps work on a site as the people who connect them
Claude, ChatGPT, Codex and Cursor connect over MCP, and the `nibble` command from a terminal. None can do more than the person it acts for, and an app waits for that person before anything goes live.
A site runs its own chores on a schedule
Fetch figures from an API, import a feed of jobs or call your own Ruby every few hours, and carry a package's images and files with its content.
Approving an app's change makes it
Each connection chooses whether to ask first, and its access can be changed after it is connected.
Forms that calculate, hold and report
A public form can total a quote, open and close itself, catch spam and notify the right people, and its submissions are handled in the Control Plane like any other work.
Menus that do more, and blocks you add instead of copy
Menus gain headings, fields and kinds of their own, lists that fill themselves and show dates; a theme adds blocks to Nibble's standard ones; and crumbs, the theme every site starts from, uses all of it.
Change what a site already holds, safely
A content migration can replace a shipped value where editors haven't changed it, and this release fixes the deploy of a site whose form emails a site setting.
One way to bring content in, wherever a page needs it
The queries a view's sidecar runs now work for layouts, for the page's own linked records, and for a form's choices.
You are here Everything above has shipped.
Being built
Contributing on GitHub
CI on every pull request, issue forms, a security policy and a support guide, so help has somewhere to go.
Next up
Extensions
Fieldtypes, query sources and Control Plane screens packaged together, installed as one, with a version of their own.
Considering
Versioned documentation
One set of pages per release, or one set that always describes the newest.
Considering
Search beyond SQLite
The same search on databases other than SQLite.
Something you need that isn't on the road? Say so in an issue. The next stops come from real sites.
Suggest a stop