Skip to content

Maintainer Guide

docs-bot edited this page Oct 26, 2026 · 1 revision

๐Ÿงฐ Maintainer guide

Every job a maintainer does, one page each, with the steps in order. Start here when something needs changing.


๐Ÿ—บ๏ธ The whole system on one picture

flowchart LR
  subgraph W["โœ๏ธ Write"]
    PC["๐Ÿ–‹๏ธ Pages CMS<br/>(browser)"]
    GH["๐Ÿ™ GitHub editor<br/>or your own editor"]
  end
  subgraph R["๐Ÿ™ Repository ยท master"]
    C["๐Ÿ“˜ content/ pages"]
    N["๐Ÿงญ nav.yml ยท home.md"]
    WS["๐Ÿ—บ๏ธ workspaces.yml"]
    I["๐Ÿ–ผ๏ธ images/"]
    J["๐ŸŽ›๏ธ webflow/*.js scripts"]
  end
  subgraph A["๐Ÿค– GitHub Actions"]
    B["๐Ÿ–ผ๏ธ image bot ยท โœ… checks ยท ๐Ÿ‘€ preview"]
    S["๐ŸŒ sync.py"]
    P["๐Ÿ“ฆ GitHub Pages<br/>nav.json ยท search.json ยท scripts"]
  end
  subgraph F["๐ŸŒ Webflow"]
    ST["bforartists.webflow.io<br/>(staging)"]
    LV["bforartists.co<br/>(live)"]
  end
  PC --> C
  GH --> C
  C --> B
  N --> B
  WS --> B
  I --> B
  B -->|"merge into master"| S
  S --> ST
  S --> P
  J --> P
  P -->|"read by the page scripts"| ST
  ST -->|"๐Ÿ‘ค maintainer's click"| LV
Loading

Three rules hold everything together

Rule
๐Ÿ™ GitHub is the truth. Never edit a docs page in the Webflow Designer or CMS; the next sync would skip it (Troubleshooting).
๐ŸŒฟ Every change goes through a pull request into master. The checks and the preview run on it; merging publishes staging.
๐Ÿšฆ Live is a separate click. Nothing the robots do ever publishes bforartists.co.

๐Ÿ™‹ "I want toโ€ฆ"

I want toโ€ฆ Who Page
โœ๏ธ Fix a typo, rewrite a section, add a screenshot Anyone Editing the docs online
๐Ÿ“„ Add, move, rename or remove a page Maintainer Structure and navigation
๐Ÿ  Change the Docs home (popular links, teaser, workspace) Maintainer Structure and navigation
โœ… Mark pages as in review or reviewed Reviewer Structure and navigation
๐Ÿ—บ๏ธ Change a workspace map, re-shoot the workspaces Maintainer Workspace maps
๐ŸŽ›๏ธ Change how the docs look or behave on the website Maintainer Site scripts
๐Ÿš€ Update the manual for a new Bforartists release Maintainers Release update
๐ŸŒ Publish the docs on the live site Lead maintainer Release update
๐Ÿฉบ Something looks wrong on the website Maintainer Troubleshooting

๐Ÿ‘ฅ Who does what

Role Can Usually does
โœ๏ธ Writer Edit pages in Pages CMS or GitHub, open pull requests Fixes and new text, screenshots
๐Ÿ‘€ Reviewer Approve pull requests, change page status Checks text against Bforartists, marks pages reviewed
๐Ÿงฐ Maintainer Merge into master, edit tools, scripts and structure Structure, scripts, workspace maps, releases
๐Ÿšฆ Lead maintainer Publish the live site, hold the Webflow and GitHub secrets Go-live clicks, tokens, access

๐Ÿ—“๏ธ Rhythm

When What Page
๐Ÿ” Every merge Staging updates by itself; glance at the Actions summary Website sync
๐Ÿ“… Weekly Merge open writer pull requests; check the review progress card on the Docs home Branches and review
๐Ÿš€ Each Bforartists release Version, screenshots, workspace maps, Blender mentions, publish live Release update

โœ๏ธ Edit this page

The Edit this page button at the foot of every page opens GitHub's editor on the current docs branch (master, set as BRANCH in docs-layer.js). GitHub makes your own branch and a pull request for you, so every edit starts from the latest docs and goes through the checks. Pages CMS still works for longer sessions: pick the docs branch there.

Clone this wiki locally