../micro-bootstrap/
Build Awesome
Micro-Starter[s]
Modern 11-in-1 micro-starter showcasing Build Awesome Kit for:
| [1] Blades CSS |  |
|---|---|
| [2] Pico CSS |  |
| [3] Bootstrap CSS |  |
| [4] Web Awesome |  |
| [5] Sveltia CMS | |
| [6] Liquid (templates) | |
| [7] Tailwind CSS |  |
| [8] Shotpipe (OG images) |  |
| [9] Content-First 🔥 |  |
| [10] Bare Build Awesome Kit (plugin) | |
| [11] Bare Build Awesome Kit (scripts) |
Local development #
As simple as:
cd micro/
npm install # dependencies
npm start # development
npm run stage # serve production version locally
# ready to deploy! 🚀
Micro multi-site starter #
micro/ starter is multi-site — meaning you can switch its input folder via IN= environment variable like this:
IN=../micro-bootstrap/ npm start
-
Sveltia CMS starter
micro-sveltia-cms/ -
Web Awesome starter
micro-webawesome/Click Web Awesome Button!
Shotpipe (OG images) starter #
Dynamic Open Graph images for your Eleventy starter, via Shotpipe — the og:image most 11ty starters skip.
Share any page of this site on X, Slack, or Discord and it renders a real social card instead of a bare link. The card's URL is signed locally at build time (one HMAC, no network call, no Chromium in CI), and the image renders lazily the first time a crawler fetches it — so your build stays exactly as fast as it was.
Enable it: #
cd shotpipe-og-images/
npm i
npx shotpipe-init # free key, no signup — writes it to .env
npm start
With no key set, the site still builds — the card is simply omitted until you run npx shotpipe-init. Nothing breaks, which is what makes it safe to ship in a starter.
How it works: #
- at build time — the plugin signs the template parameters into a URL. No network, no headless browser.
- in your
<head>— the URL waits in<meta property="og:image">, doing nothing. - on first share — when a crawler fetches it, Shotpipe renders the template and caches the PNG forever.