Templates
Any editor can mark an app as a template: open its Settings and turn on Offer as a template, or:
curl -X PATCH https://bunker.example.com/api/v1/sites/expense-form \ -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \ -d '{"isTemplate": true}'Templates are listed for everyone at GET /api/v1/sites?filter=templates, sorted by title.
Using a template
Section titled “Using a template”- Open Templates in the dashboard sidebar, or list them with
bunker sites ls --filter templates. - Click Use this template. Bunker copies the published files, not the data, into a new app that you own.
From a script, that’s sites.create with a template:
bunker api sites.create --title "Design team board" --template template-trackercurl -X POST https://bunker.example.com/api/v1/sites \ -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \ -d '{"title": "Design team board", "template": "template-tracker"}'To copy an app that isn’t a template, editors use sites.duplicate (POST /api/v1/sites/{site}/duplicate). It copies the working files, including the draft.
Built-in templates
Section titled “Built-in templates”Bunker ships sixteen starter templates. Each is created once, and everyone signed in can open them and Use this template.
| Template | Address | What it does | Uses |
|---|---|---|---|
| ✅ Requests & approvals | template-requests |
A request form with an approvers group, clear statuses and a full history | bunker.db (requests, decisions) |
| 🗂️ Team tracker | template-tracker |
A live kanban board: drag cards between columns, see changes instantly | bunker.db (cards), bunker.room |
| 📝 Sign-up sheet | template-signup |
Slots with limits for events, shifts or volunteering. No double booking | bunker.db (signups) |
| 💬 Feedback collector | template-feedback |
Ratings and comments with live results and an AI summary | bunker.db (feedback), bunker.ai |
| 📊 Quick poll | template-poll |
One question, one vote each, results update live | bunker.db (votes) |
| 📈 Simple dashboard | template-dashboard |
KPIs and charts from a CSV, a SharePoint list or sample data | Inline SVG charts, CSV, optional bunker.m365 |
| 👋 Team directory & who’s out | template-directory |
Profiles, skills and a shared calendar of time away | bunker.db (people, away) |
| 🗒️ Meeting notes & decisions | template-meetings |
Notes, decisions and action items you can find again later | bunker.db (meetings), bunker.ai |
| 💻 Equipment check-out | template-assets |
Laptops, cameras and kit: who has what, until when, with a full history and CSV export | bunker.db (assets read, loans) |
| 🗓️ Room & desk booking | template-booking |
A day grid of rooms and desks; book a slot in two taps, double bookings are refused | bunker.db (rooms read, bookings) |
| 📦 Inventory & stock count | template-inventory |
Stock levels, low-stock highlighting, quick +/− counts, a change log and CSV export | bunker.db (items open, stocklog), bunker.download |
| 🚨 Incident & issue log | template-incidents |
Report issues by severity, follow a live timeline and alert the on-call group | bunker.db (incidents open, updates), bunker.notify |
| 🧭 Onboarding checklist | template-onboarding |
A first-weeks checklist each new starter ticks off privately; editors see everyone’s progress | bunker.db (tasks read, progress private) |
| 🎯 Goals & OKRs | template-okrs |
Quarterly objectives with key results, owners, progress bars and check-ins | bunker.db (objectives open) |
| 🙌 Kudos wall | template-kudos |
Public thank-yous with company values, live reactions and a monthly leaderboard | bunker.db (kudos, reactions) |
| 🥪 Lunch orders | template-lunch |
A weekly menu, one order per person per day, a cut-off time and live tallies | bunker.db (menu read, orders), bunker.download |
Each is a single index.html written to the SDK and the sandbox rules, so they are good examples to learn from. Opened outside Bunker, they run in a demo mode with in-memory data.
The Uses column names each template’s collections and, where it isn’t the default own, the data rule it starts with (read: only editors change it, open: anyone with access can change anything, private: people see only their own). A copy starts with the same rules, so it works for your team straight away; editors can change them in the app’s Data tab (Access). In templates with a read collection (rooms, equipment, the checklist, the menu), the people who can edit the app manage that list and everyone else uses it.
The incident log alerts a group called On-call (change ONCALL_GROUP at the top of the page). Share the app with that group so its members get the alert.
How they’re managed
Section titled “How they’re managed”- They are owned by a disabled system account called Bunker and shared with everyone as viewers.
- Bunker seeds each one once, by its address. If an admin edits or deletes one, it stays that way after upgrades.
- When an upgrade adds new built-in templates, they are added on the next start; existing templates are never overwritten.
- If any template already exists when Bunker first starts, nothing is seeded on that start (later releases still add their new templates).
- To skip them, set
BUNKER_NO_TEMPLATES=true. Bunker then seeds nothing on start.