How to use & edit this wiki

This wiki is the single source of truth for how we run the glass business — SOPs, best practices, and flowcharts. It lives at wiki.bcbautoglass.com and is generated from a Git repository, so every change is versioned and nothing gets lost.

How it works

• The wiki is a static site (Astro Starlight) in the bcb-wiki-new GitHub repo under the OwnerOperated organization.
• Pages are plain Markdown files under src/content/docs/.
• Pushing to main automatically rebuilds and publishes the site (Cloudflare Pages, ~60 seconds).
• Flowcharts are written as Mermaid code blocks right inside the Markdown — they render as diagrams on the page.

Editing pages (no coding required)

Option 1 — Pages CMS (quick browser edits):

1. Go to app.pagescms.org and log in with GitHub.
2. Open the bcb-wiki-new repo. You’ll see every wiki page listed.
3. Edit in the visual editor and hit Save — it commits for you, and the site republishes in about a minute.

Anyone who should edit the wiki needs a (free) GitHub account with access to the repo. Add people under the repo’s Settings → Collaborators.

Option 2 — “Edit page” link: every page has an Edit page link in the footer that opens the file on GitHub — edit and commit right in the browser.

Option 3 — Claude assistants (the dedicated editor’s workflow):

For team members editing the wiki regularly, we have a guided workflow:

• The BCB Wiki Assistant Claude Project (on claude.ai) interviews you about the change, drafts the markdown in the correct format, and produces a handoff block.
• Claude Code, running locally in your BCBWIKI/bcb-wiki/ folder with a CLAUDE.local.md safety-rail file, saves the change and pushes it.
• The safety rails restrict edits to src/content/docs/ — config, components, and site structure cannot be touched.

If you want this setup, ask your tech contact. They’ll clone the repo to your machine, install Claude Code, drop the safety-rail file in place, and hand you a HANDOFF.md with the daily workflow.

Adding a page

Create a new .md file in the right section folder (via Pages CMS, GitHub, or the Claude workflow):

Section	Folder
Start Here	src/content/docs/start-here/
Lead Flow	src/content/docs/leads/
Marketing Websites	src/content/docs/websites/
Ops Dashboard	src/content/docs/ops-dashboard/
Google Business Profile	src/content/docs/google-business-profile/
Best Practices	src/content/docs/best-practices/

Every page needs this at the top (Pages CMS fills it in for you):

---
title: My page title
description: One line that shows up in search.
---

New pages appear in the sidebar automatically. To add a whole new section, create the folder and add one line to the sidebar list in astro.config.mjs — this is a developer task, not a wiki-editor task.

Adding a flowchart

Add a fenced code block with the language mermaid:

```mermaid
flowchart TD
  A[Customer submits form] --> B[Email + text goes out]
  B --> C{Booked?}
  C -- Yes --> D[Schedule the job]
  C -- No --> E[Follow up]
```

That renders as:

flowchart TD
  A[Customer submits form] --> B[Email + text goes out]
  B --> C{Booked?}
  C -- Yes --> D[Schedule the job]
  C -- No --> E[Follow up]

House rules

• No passwords or API keys on this wiki, ever. Credentials live in the server .env, encrypted in the dashboard DB, or in a gitignored CLAUDE.local.md — never here.
• Keep pages task-shaped: someone should be able to follow a page top-to-bottom and get the job done.
• If you fix a process, fix the wiki page in the same sitting.