Files
acobham 5eb4426d30 Update SOPs: consolidate index, clean client data, set Imagen as default
- README: rewrite index to reflect actual files (STACK/CONTENT/OPTIMIZATION);
  remove 15 dead links to old numbered SOPs; add subdirectory table; update
  image gen to Google Imagen as default
- STACK: fix wp-divi-pipeline script paths; genericize vibrantyou/domain
  examples; strip pre-existing em dashes throughout
- CONTENT: update image generation default to Google Imagen API with allotted quota
- image-gen-workflow: remove client-specific cobhamtech data; generalize
  brand palette step; update date
- wp-divi-pipeline-to-am-stack: remove vibrantyou.yoga client data block;
  fix Related SOPs links to current files
2026-06-09 18:54:57 +02:00

82 lines
3.6 KiB
Markdown

# Arising Media Web Design SOPs
Standard operating procedures for building, migrating, and deploying websites the Arising Media way. Reference `stack-selector.json` FIRST to pick the correct stack before touching any other SOP.
## Stack selector (read this first)
`stack-selector.json`: machine-readable + human-readable decision guide. Covers all three stacks, approved colors, section types, DB guidance, hot-copy commands.
## Primary SOP files
| File | Covers |
|------|--------|
| `STACK.md` | Architecture, project structure, build pipeline, WP migration, Docker/nginx deployment, cPanel deployment, DNS/email, form handling, PHP app stack |
| `CONTENT.md` | Writing standards, tone by sector, healthcare credential rules, copy structure, image standards, image generation, prompt engineering |
| `OPTIMIZATION.md` | Mobile responsive, breakpoints, SEO meta, schema.org, robots.txt, sitemap, testing/verification, performance standards |
## Three stacks (2026-05-21 standard)
### Stack A: PHP Router + SQLite (50+ page sites)
Reference: `arisingmedia.us`. 10,000+ pages, single router, SQLite content DB.
Edit one template and all pages in that class update instantly.
Build standard: `arisingmedia.us/.planning/WEBSITE_BUILD_STANDARD.md`
Stack A uses raw docker commands only. No docker compose.
### Stack B: Static HTML (fewer than 50 pages)
Reference: `lahrcarpetcleaning.com`. Universal Docker + cPanel deployment.
Every page is an HTML file on disk. Simple, portable, no server-side requirements.
### Stack C: PHP App (file processing, auth, payments)
Reference: `quickconvert.us`
See STACK.md PHP App Stack section.
## Subdirectories
| Directory | Purpose |
|-----------|---------|
| `local-image-generation/` | Full local pipeline: ComfyUI setup, FLUX.1 Schnell images, Wan 2.2 video, prompt guide, quality levers |
| `image-gen-workflow/` | Cloud API workflow (Google Imagen 4). Paid client budgets only. |
| `wp-divi-pipeline-to-am-stack/` | End-to-end pipeline: .wpress archive to Stack A deployment |
| `tools/` | Shared scripts (verify-protection.sh, etc.) |
| `build/` | Build utilities |
## Image generation
Default: Google Imagen API (imagen-4.0-generate-001) with allotted quota per project.
See `image-gen-workflow/` for the workflow, model selection, and prompt patterns.
All output: `.webp` only in production.
## Universal project file checklist
Every project must include ALL of these before first deploy:
```
Dockerfile Docker/VPS: nginx web container
docker-compose.yml Stack B/C only. Stack A uses raw docker commands.
nginx.conf Docker/VPS: routing, security headers, gzip
.htaccess cPanel/Apache: clean URLs, deny sensitive files
.cpanel.yml cPanel Git: copy files to webroot on deploy
.dockerignore keeps secrets and tools out of Docker image
.gitignore keeps .env and secrets out of git
robots.txt both paths
sitemap.xml both paths
llms.txt both paths. AI crawler documentation (see OPTIMIZATION.md)
404.html both paths
500.html both paths
```
## Reference projects
- `lahrcarpetcleaning.com`: primary reference. Universal deployment, directory-style URLs, WebP images, cPanel Git, mobile nav, FLUX image generation.
- `arisingmedia.us`: Stack A reference. PHP router, SQLite, 10,000+ pages.
- `quickconvert.us`: Stack C reference. PHP app, Stripe, encryption, auth.
## When to deviate
These SOPs are the default. Deviate only when:
- The client explicitly requires a different stack (CMS-managed editing, e-commerce, etc.)
- A required feature cannot be done with this stack
Document the deviation in the project's own `README.md`.