Skip to content

Configure Wall Works Hardscape site from template#1

Open
Crypto-Goatz wants to merge 2 commits into
mainfrom
claude/setup-wall-works-repo-JoZAE
Open

Configure Wall Works Hardscape site from template#1
Crypto-Goatz wants to merge 2 commits into
mainfrom
claude/setup-wall-works-repo-JoZAE

Conversation

@Crypto-Goatz
Copy link
Copy Markdown
Member

Summary

Customize the Rocket Client Template for Wall Works Hardscape by introducing a centralized client configuration system and updating all references throughout the codebase to use Wall Works branding, contact information, and styling.

Key Changes

  • New config/client.config.ts: Created a single source of truth for all client-specific configuration (business name, contact info, colors, taglines, storage keys, etc.). This file is marked as protected from template updates.

  • Updated config/site.config.ts: Modified to read default values from CLIENT config instead of hardcoded placeholders, ensuring the entire site reflects client settings.

  • Centralized branding: Updated all components and utilities to import and use CLIENT config:

    • components/site/Footer.tsx: Uses CLIENT.footerText instead of generic copy
    • components/admin/Sidebar.tsx: Uses CLIENT.adminTitle and CLIENT.adminSubtitle
    • app/layout.tsx: Uses CLIENT.seoTitle and CLIENT.seoDescription as fallbacks
    • app/admin/setup/components/SetupWizard.tsx: Uses CLIENT.storagePrefix and color defaults
    • lib/setup/site-importer.ts: Uses CLIENT.name and CLIENT.url in User-Agent header
  • Environment variables: Updated .env.example with Wall Works-specific values (domain, business name, colors, contact info)

  • Documentation updates:

    • README.md: Changed from generic template description to Wall Works-specific content
    • DEPLOY.md: Updated with Wall Works deployment instructions
    • UPDATING.md: Removed Rocket+ branding references
    • package.json: Updated package name to wall-works-hardscape
  • UI refinement: Changed completion step icon from Rocket to PartyPopper for better visual fit

  • Footer branding: Removed "Powered by Rocket+" attribution link

Implementation Details

The CLIENT config is exported as a const object with as const assertion, providing type safety via ClientConfig type. This allows the setup wizard and other components to reference client-specific values while maintaining the ability to override them via environment variables or Google Sheets at runtime.

All client-specific customizations are now isolated in config/client.config.ts, making it easy to clone this template for future clients by simply updating that single file.

https://claude.ai/code/session_01Xoj8y4GAFiC1vMbm3mNGQr

Duplicate rocket-client-template for Wall Works — retaining walls & masonry
in Westmoreland County. Includes complete onboarding flow (7-step setup wizard),
CRO9 analytics integration, and SXO behavioral tracking panel.

- Update branding defaults to Wall Works (name, tagline, domain, colors)
- Apply black/white/red gradient color scheme (#1a1a1a, #ffffff, #dc2626)
- Replace Rocket platform branding with Wall Works throughout
- Update .env.example, site.config.ts, and deployment docs
- Verify all onboarding steps, CRO9 analytics, and SXO panel intact

https://claude.ai/code/session_01Xoj8y4GAFiC1vMbm3mNGQr
Add a single source of truth for all client-specific values (name, phone,
email, domain, tagline, colors, footer text, admin title, SEO fallbacks).
All other files now import from CLIENT config instead of hardcoding strings.

For future client clones: update only config/client.config.ts and .env.example
to rebrand the entire site universally.

https://claude.ai/code/session_01Xoj8y4GAFiC1vMbm3mNGQr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants