🗞️ Around Town

Overview

LiveAgent id still aroundsummerlindev

aroundsummerlin.com aroundhenderson.com aroundcarsoncity.com aroundpahrump.com

App features

• Landing page — masthead from town.config.json (site name, city/state, tagline), weekly date, subscribe form, past-issues search/archive, advertise CTA, privacy/terms footer.
• Issue reader — /issue.html?slug=… fetches one published issue (cover, volume/issue, body HTML).
• Legal — privacy.html / terms.html tokenized with the town name and domain.
• Subscribe — POST /api/subscribe → CRM contacts (201 / 400 / 502).
• Advertise — POST /api/advertise → CRM advertiser leads.
• Issues API — GET /api/issues and GET /api/issues/[slug] proxy published issues from CRM.
• GA stub — gtag loads only when GA_MEASUREMENT_ID is set.
• Four towns, one brand system — Around Summerlin / Henderson / Carson City / Pahrump. Copy is config, not hardcoded in shared templates.

Operations playbook

The weekly run book — how issues get created, sent, and paid for. All steps verified live September 7–8, 2026.

1 · Create the weekly newsletter

1. Research — scan local sources (summerlin.com events calendar, Review-Journal, library district calendar, community calendars) for the week's stories.
2. Write — 6–8 sections, flexible per week, each headed with its icon. Structure stories EDH Insider–style: The Gist + Why It Matters.
3. Illustrate — generate one flat-vector editorial illustration per major section (no copyrighted photos), upload to the headquarters Pages host, embed via <img>.
4. Create draft in CRM — POST /api/newsletter-issues with title, slug, summary, bodyHtml, volume/issueNumber, status: "draft". Drafts are invisible to the public site (verified: 404 + not in archive).
5. Review — CRM → Newsletter page → Review full issue expander shows the rendered body.
6. Publish — flip status to published (button in CRM). Issue appears instantly in the site archive and renders at /issue.html?slug=….

Section menu (rotate 6–8 per issue): 🏛️ Lead · 🏗️ Growth & Development · 🍽️ Dining · ⚾ Sports · 🎭 Culture & Arts · 🏡 Real Estate · 🛍️ Business Spotlight · 👨‍👩‍👧 Family & Kids · 🌄 Outdoors · 💼 Business News · ✉️ Reader Mail · ☀️ Week Ahead · 📅 Mark Your Calendar · 🔁 Every Week staples · 🍂 Seasonal notes. Always close with the calendar + recurring staples.

2 · Send the newsletter (sender.net)

After publishing, the issue goes to all subscribers via sender.net using scripts/sender-newsletter.ps1 (in the aroundsummerlindev workspace):

# One-time per town setup (dashboard):
#   verify sending domain (SPF/DKIM records → Vercel DNS),
#   create a group per town, generate API token (masked entry / .env.sender)

# Weekly send:
pwsh scripts/sender-newsletter.ps1 sync -Site <siteId> -GroupId <groupId>   # CRM subscribers → sender.net (excludes test contacts)
pwsh scripts/sender-newsletter.ps1 send -IssueId <id> -Site <siteId>        # build email HTML + POST campaign

# Both support -DryRun; `build` writes the email HTML for inspection first.

The email renders cover image → title → summary → full body with illustrations, plus an archive link and unsubscribe slot. Subscribers added later are picked up by the next sync. Status: pipeline built + dry-run verified; awaiting sender.net API token to go live.

3 · Sell, create, and bill ads

1. Lead arrives — advertiser fills the Advertise section on the site → POST /api/advertise → CRM advertisers record with status lead (tested: 201 Created, lead visible instantly).
2. Qualify — agree on package (e.g. Founding Local — sidebar spot + mid-issue mention, $299/mo), flip the record to active with the package name.
3. Bill — create an advertiser-payments record (amountCents, description, method: "manual"|"stripe", status pending). Manual: mark paid when collected. Stripe: POST /api/advertiser-payments/checkout returns a payment link; the checkout.session.completed webhook auto-marks it paid. Stripe needs STRIPE_SECRET_KEY + STRIPE_WEBHOOK_SECRET on the crm project — pending.
4. Create the ad — the agent writes the spotlight copy in the newsletter's voice and generates matching illustration art from the CRM record (or hosts advertiser-supplied creative). Sponsors are embedded mid-issue after the Lead and mid-calendar, plus a flowing sidebar-styled spot.
5. Approval — sponsor blocks appear in the issue review before publishing; Mike signs off there.

Flow

Build

town.config.json  +  packages/newsletter-core templates
        │
        ▼
  apps//build.mjs   →  dist/  (no leftover {{TOKENS}})
        │
        ▼
  Vercel static outputDirectory = dist
  Vercel functions = apps//api/*  (re-export core handlers)

Runtime request

1. Browser hits apex domain (Vercel project for that town).
2. HTML/CSS/JS served from dist/.
3. Forms/API calls go to same origin /api/* (serverless).
4. Handlers use @townnews/core factories → CRM REST with env CRM_API_URL / tenant / site.
5. CRM down → 502 is expected and acceptable in local/dev verification.

Deploy

Push to main (paths apps/**, packages/**, or the workflow file) or workflow_dispatch. Matrix job per app: vercel link --project $APP, PATCH rootDirectory to apps/$APP, vercel deploy --prod. Full monorepo is uploaded so workspace:* resolves. Not Vercel git integration.

Tech

apps//
  town.config.json
  build.mjs
  api/          # subscribe, advertise, issues, issues/[slug]
  vercel.json
  .env.example  # CRM_* and optional GA_MEASUREMENT_ID
packages/newsletter-core/

🗂️ Roadmap

• ☐ #6 sender.net: create account + verify sending domain (SPF/DKIM)
• ☐ #8 Securely provide SENDER_API_TOKEN to the agent
• ☐ #7 sender.net: create 4 town groups + per-town sender identities
• ☐ #9 Wire Stripe keys on crm project + $1 test checkout
• ☐ #10 Refresh GitHub token in .env.github (PR creation 401s)
• ☐ #11 Launch issue: Around Henderson Vol 1 Issue 1
• ☐ #12 Launch issue: Around Carson City Vol 1 Issue 1
• ☐ #14 Sync subscribers + test send for each town (sender.net)
• ☐ #13 Launch issue: Around Pahrump Vol 1 Issue 1
• ☐ #15 First real send: all 4 towns
• ☐ #17 Polish: Discord ping on new advertiser leads + weekly auto-draft automation
• ☐ #20 Rename agent id aroundsummerlindev → something aroundtown-shaped (Discord bot nick can stay AS Dev).
• ☐ #21 preview-alias.yml is still Summerlin-only (preview.aroundsummerlin.com).
• ☐ #22 Optional www → apex redirects if we want them explicit.
• ☐ #23 Work through remaining checkboxes in docs/TEST_PLAN.md (browser matrix, error cases, CRM payload shapes).
• ☐ #26 [pair-test A3] Issue detail pages fail: /api/issues/<slug> returns Vercel 404, page shows raw JSON parse error
• ☐ #27 [pair-test A1] Footer social icons link to # (Facebook/Instagram stubs, empty link text)
• ☐ #28 [pair-test A2] Issues grid: 4th card orphans onto an uneven second row
• ☐ #29 [pair-test A2] Two published issues both numbered Vol. 1, Issue 4
• ☐ #30 [pair-test A3] Issue page error state hides 'Back to archive' and shows raw JSON parse error
• ☐ #31 [pair-test A5] No welcome email after subscribing
• ☐ #32 [pair-test A8] Issue page: no right padding on top-bar nav and content at 390px
• ☐ #33 [pair-test B1] CRM has no authentication[pair-test B1] CRM has no authentication
• ☐ #34 [pair-test A6] Re-subscribing the same email creates duplicate CRM contacts
• ☐ #35 [pair-test B3] Remove manual 'create issue' form from the CRM newsletter page
• ☑ #24 Per-town CRM workspaces + Vercel env for Henderson / Carson City / Pahrump — done 2026-09-07 (sites created, env vars set, subscribe verified 201 on all three). — done 2026-10-20
• ☑ #16 Test-data cleanup before launch (contacts + test advertiser) — done 2026-09-27

Live roadmap, managed as GitHub issues (aroundtown issues). Add or close items on GitHub — ☑ = done, close as “not planned” to remove.

Test results

Canonical checklist: docs/TEST_PLAN.md (static UI, subscribe, advertise, issues API, CRM, deploy, four-town branding).

🧪 Pair test plan — projects/aroundtown-test-plan.html: the live two-tester walkthrough (customer / admin / newsletter send / advertiser / billing) we execute together, with the results-and-issue log filled in as we go.

2026-09-04 — rename + four-domain cutover

• pnpm build — 4/4 apps, 0 unresolved {{TOKEN}}s in built index.html.
• GitHub Actions Deploy Vercel Frontends — all four matrix jobs success (had been failing since 2026-08-21; root package.json was missing turbo / packageManager / per-app dev scripts).
• Apex HTTP 200 + correct document title after clearing gitBranch on the three new domains:
  • Around Summerlin - All the highlights without the noise.
  • Around Henderson - All the highlights without the noise.
  • Around Carson City - All the highlights without the noise.
  • Around Pahrump - All the highlights without the noise.
• Visual: desktop screenshots of all four homepages captured 2026-09-04 (Henderson example fully rendered, no leftover tokens).

Manual UI / CRM happy-path boxes in TEST_PLAN are not fully ticked yet — treat this cutover as deploy + branding verification, not a full QA pass.

2026-09-07/08 — operations verified live (Summerlin)

• Subscribe flow: real submission → contact in CRM on the Summerlin site (Newsletter Subscriber, lowercased email).
• CRM UX shipped: tenant/site switcher in the dashboard header; newsletter "Review full issue" expander + "View on site" links.
• Issue 4 ("A parade worth planning for, 354 new neighbors, and the Aviators' last call") — researched, written (6 sections, Gist/Why-It-Matters), illustrated (5 flat-vector images), reviewed in CRM, published; renders with all art at /issue.html?slug=latin-heritage-parade-september-summerlin.
• Advertiser flow: site form → 201 → CRM lead → active → $299 payment recorded paid (manual). Stripe checkout pending keys.
• Email pipeline: sender.net sync/build/send dry-run verified (test contacts correctly excluded); live send awaiting API token.