Blueprints
A blueprint is a whole application, in its own repository, built with Grit. Not something you install: something you clone and work from. A plugin adds a feature to your project; a blueprint is a project.
grit blueprint listgrit blueprint info whatsapp
Why they exist
Two reasons, and the second one is the one that matters to you even if you never open one.
The first is a starting point. If you are building a storefront, starting from a storefront beats starting from an empty project and a tutorial.
The second is that each blueprint is a load test for the framework. Building a real application finds things a test suite does not, and every gap a blueprint finds is fixed in Grit first, released, and then the blueprint runs grit upgrade into it. Its code stays Grit's own rather than drifting into a fork. The storefront alone found five framework bugs in one sitting, and those fixes shipped to everybody.
Available now
whatsappRealtime chat across web, mobile and desktop, on one Go API
web, admin, mobile, desktop
What you open it for
- One conversation model reaching four clients without four implementations
- Message delivery and read state over the domain event bus
- Attachments through the same storage the rest of the app uses
- An Expo app and a Wails desktop app against the same shared types
instagramPhoto and video feed with an Expo app
web, admin, mobile
What you open it for
- Image and video processing on upload, and what to do off the request
- A feed that paginates without drifting as new posts arrive
- Mobile capture and upload from Expo
Kaya Goods
MembershipstorefrontA shop: products, variants, cart and Stripe checkout
web, admin
What you open it for
- Product variants, and the option matrix that generates them
- A cart that survives sign-in, and a checkout that survives a retry
- Stripe webhooks that are idempotent when Stripe redelivers
On the list
Announced, not built yet. Listed because "is there a Linear blueprint?" is better answered with "not yet" than with silence.
Stripe dashboard
Payments, subscriptions and revenue reporting
Uber
Live tracking on a map, with PostGIS
Linear
An issue tracker built for the keyboard
Blueprints and examples are different things
The Grit repository also carries examples/: complete applications checked into the repo and built on every CI run. Those are free and they are there to prove the framework works and to be read.
A blueprint is a bigger, designed product in a repository of its own, kept current against new releases. Both are real applications; the difference is scope and where they live.