SOP: editing a marketing site

Changing business info (phone, hours, address, service areas)

On a standard site, one file holds everything: src/config/site.ts.

1. Open the site’s repo, switch to the staging branch.
2. Edit the value in src/config/site.ts — phone, address, hours, service areas, brand colors, webhook URLs, TrustIndex IDs, Maps embed all live there.
3. Never hardcode a phone number or address in a component — if you find one hardcoded, that’s a bug; move it to site.ts.
4. Push staging, check the preview URL, then follow the deploy SOP to promote to main.

The exceptions

• bsag-astro — there is no site.ts. Edit the .astro files directly (src/pages/index.astro, src/layouts/Base.astro, src/components/QuoteForm.astro).
• agla-website-astro — edit site.ts and check the pre-generated HTML snapshot pages, which keep a baked-in copy of business data in their inner blob.
• bcbautoglass — plain index.html, edit directly.

Changing page copy or sections

• Homepage sections: src/components/sections/*.astro — one file per section.
• Legal pages: src/components/pages/ + src/pages/.
• Header/footer/site-wide chrome: src/layouts/BaseLayout.astro.

Images & assets

Put files in public/ and reference them by absolute path (/images/...). Compress before committing — these are marketing sites; page speed matters for Ads quality score.

Quote form / lead delivery changes

Anything touching the quote form or notify Function must preserve the canonical lead flow — one-line name, first-name-only Podium text, no Slack. Test on the staging preview with a real submission before promoting, then delete your test lead from the dashboard.

Golden rules

• Local first — never edit anything on production servers directly.
• Work on staging, verify the preview, promote to main. Those are the only two branches — never create others.
• Never build or commit dist/ or node_modules/ — Cloudflare builds from source.