Files
phoenix-website-hallmark/README.md
T

4.9 KiB
Raw Blame History

Phoenix Website · Hallmark Redesign

Repo: Tony_tech/phoenix-website-hallmark
Live site (unchanged): phoenixcameronpark.com
Business: Phoenix Salon + Spa · Cameron Park, CA (Ashley Thornhill, founder + lead esthetician)
Status: Prototype only — not deployed live. No auto-publish.


What this project is

A redesign track for the Phoenix Salon + Spa website, starting from a full Hallmark (anti-AI-slop) design audit of the live homepage and a local recreation that keeps real business content while replacing the template skeleton.

In this repo

Path Purpose
README.md This file — project definition and why
docs/PROJECT.md Goals, non-goals, constraints, success criteria
docs/hallmark-audit-2026-07-16.md Full Hallmark audit of the live site
prototype/ Self-contained Hallmark homepage prototype (index.html, tokens.css, styles.css)
docs/decision-log.md One-change-one-entry decisions for this project

Not this project

  • Not a full multi-page production rewrite (yet)
  • Not social content, Instagram, or OpenMontage clip factory (see personal-agent-os/projects/salon-social-media-system)
  • Not competitive audits of other salons (see Tony_tech/salon-digital-intel)
  • Not live deploy to production without explicit user approval

Why we are doing it

The problem

The live site (phoenixcameronpark.com) carries real value — Ashleys expertise, memberships, reviews, address, photography — but ships inside a Lovable / AI-default local-business layout:

  • Centred hero + equal service cards + “Learn More →” factory
  • Three equal “STEP” onboarding cards
  • Eyebrow labels on every section
  • Inter + pure white SaaS tokens under a warm cream varnish
  • Entry modal + awards banner + awards section competing with Book
  • Voice collision: title says luxury, H1 says “Hey bestie”, body says “Elevated Beauty”

That reads as generic AI template, not as Phoenix / Ashley / Cameron Park. For a service business that wins on trust and taste, the sites skeleton undercuts the craft in the treatment room.

The opportunity

Hallmark (Nutlope / Together AI skill, installed into Leonard) encodes anti-slop rules: structural variety, honest copy, token discipline, sparse nav/footer, photographic split layouts. We use it to:

  1. Diagnose the live site with a named punch list (audit).
  2. Prove a better shape with a local prototype (no risk to production).
  3. Iterate with Tony/Ashley before any live cutover.
  4. Compound a reusable pattern for other local businesses later (search-velocity / digital presence work).

Why now

  • Hallmark was integrated into Leonard (2026-07-16) specifically for non-slop design work.
  • Phoenix is the flagship local brand for Tony + Ashley; the website is the front door for booking and memberships.
  • Prototype-first avoids the past failure mode of patching live surfaces without approval.

Design direction (prototype v1)

Axis Choice
Macrostructure Split Studio (photo / text diptychs)
Genre Editorial · warm studio
Theme Custom — warm oat paper, deep ink, small teal accent
Type Cormorant Garamond + IBM Plex Sans + Source Serif 4 (quotes)
Nav Sparse (Services · Memberships · Ashley · Reviews · Visit + Book)
Footer Statement close, not multi-column SaaS dump
Voice Treatment-room honesty — not bestie / not elevated-marketing cliché

Content kept: services, Glow $70, tans from $95, Ashley bio, client quotes, address, phone, email, live CDN photos.
Cut: modal, 3-step cards, equal card factory, Inter, pure white paper, awards as full section (kept as one ribbon line).


Operating rules (binding)

  1. Gitea is the archive for this projects artifacts.
  2. No live deploy without explicit “publish / deploy / ship to production” from Tony.
  3. Preview before publish — show local or staged result; get approval.
  4. One change = one commit = one decision-log entry when we start mutating production paths.
  5. Ashley voice accuracy is top priority; no invented metrics or overclaims.

How to view the prototype

Local (VPS path used during build):

/home/vpsadmin/phoenix-hallmark-prototype/index.html

Or open the files under prototype/ in this repo after clone.

Book / membership links still point at the live site; forms in the prototype are inert demos.


Next steps (not started until asked)

  • Tony/Ashley review of prototype v1 (likes / dislikes)
  • Section-level revisions
  • Multi-page shell (services, membership, contact) still local
  • Only after approval: staged deploy plan for production

Initialized 2026-07-16 by Leonard (Hermes) on Tonys direction: audit live site → Hallmark recreation → persist to Gitea with project definition.