Google Drive links — where each built asset lives¶
Every built asset is mirrored to the shared Google Drive folder for reviewing and sharing. This page is the index: one row per Drive folder, with the link to open it.
Sagar: after uploading a new build (extract the zip into the Drive folder), paste each folder's share link over its
_paste link_placeholder below. Everything else on this page maintains itself — the folder structure matchesstage-for-drive.sh.
Root folder: paste link to "SnowOps — Client-Facing Assets"
| Drive folder | What's inside | Link |
|---|---|---|
| 1 — Brand kit | Logo files, brand system, master templates | paste link |
| ↳ Logo | All logo variants (SVG + PNG) | paste link |
| ↳ Masters | Deck master (.pptx) + document masters (.docx) | paste link |
| 2 — Land | Capabilities deck + all one-pagers | paste link |
| ↳ One-pagers (PA04) | Finished PDFs — Letter + A4 | paste link |
| ↳ One-pagers — editable Word (PA04) | Same three, as editable .docx | paste link |
| ↳ One-pagers — industry verticals (PA05) | SaaS / FinTech / HealthTech .docx | paste link |
| 3 — Audit | Sample audit — PDF, web, and editable Word | paste link |
| 4 — Close | Proposals, coverage matrix, pricing, case study, contracts | paste link |
| ↳ Proposals (PA10) | Quick-Win / Baseline / Advanced + findings-to-roadmap | paste link |
| ↳ Contract pack (PA16) | NDA / MSA / SOW / DPA / cloud-access — counsel review required | paste link |
| 5 — Deliver | Kickoff deck + client handover guides | paste link |
| ↳ Handover guides (PA19) | Six operating guides handed to clients per milestone | paste link |
Not in Drive (on purpose)¶
- Assets not built yet — website, LinkedIn kit, email signature, call agenda, reference-architecture diagrams, onboarding guide, and the retain-stage assets. See the state tracker for what's next.
- Build sources (
src/folders, generators) — they only matter inside the repo.
Keeping this honest¶
Drive is a one-way mirror: the repo builds it, uploads replace it. If a document in Drive disagrees with the site, the site is right. Comments in Drive are welcome — that's what it's for — but wording fixes must land in the repo source to survive the next upload.