Update trust-building homepage copy - #8
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the Memorialize homepage and supporting JSON-driven content to replace demo/portfolio language with customer-facing, trust-building service messaging (approval workflows, production care, packaging, and support), while relocating implementation/demo notes into the repository README.
Changes:
- Refresh homepage copy and section subtitles to emphasize customer-ready service positioning.
- Rewrite
brand.jsonandhome.jsoncontent (metrics, how-it-works, pricing, testimonials, FAQ) around approval-led and production-care language. - Update
assets/js/main.jsUI labels/toasts/hints to reinforce the new service-oriented narrative and move demo notes intoREADME.md.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds “Demo implementation notes” to keep implementation details out of customer-facing pages. |
| index.html | Updates homepage headings/subtitles to remove demo-facing language and emphasize service trust signals. |
| data/home.json | Replaces how-it-works, pricing features, testimonials, and FAQ with approval/production/packaging/support-focused copy. |
| data/brand.json | Updates hero subtitle, values, and metrics to service-oriented trust signals (quality checkpoints, approval-linked dispatch window, design review). |
| assets/js/main.js | Adjusts rendered labels/toasts/hints to align UI framing with approval workflows and service packaging cues. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| renderList('testimonialsGrid', data.home.testimonials, (t) => ` | ||
| <article class="item testimonial"> | ||
| <p>“${escapeHtml(t.quote)}”</p> | ||
| <h3>${escapeHtml(t.name)}</h3> | ||
| <div class="kicker">${escapeHtml(t.location)}</div> | ||
| <div class="kicker">${escapeHtml(t.location)} · verified service feedback</div> | ||
| </article> |
| <section id="categories" class="section"> | ||
| <div class="section-heading"><div><h2>Gift categories</h2><p class="sub">Personal, emotional, and corporate gifting formats powered by JSON mock data.</p></div></div> | ||
| <div class="section-heading"><div><h2>Gift categories</h2><p class="sub">Personal, emotional, and corporate gifting formats with thoughtful design review and finishing options.</p></div></div> | ||
| <div class="grid-2" id="categoriesGrid"></div> |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bd5fde491
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| form.addEventListener('submit', (e) => { | ||
| e.preventDefault(); | ||
| form.reset(); | ||
| showToast('Subscribed in mock mode. No backend call was made.'); | ||
| showToast('Subscribed. Founder notes and gifting updates will be shared here.'); |
There was a problem hiding this comment.
In the static deployment this handler calls preventDefault(), clears the form, and never sends or stores the submitted email; after this copy change, the visitor is told they are subscribed and will receive updates. Anyone using the footer newsletter on the live static site has their address silently dropped, so either wire the form to a real persistence path or keep the success text framed as a preview.
Useful? React with 👍 / 👎.
Motivation
README.mdto avoid customer-facing infrastructure disclosures.Description
data/brand.jsonto replace mock stats with service metrics (Quality checkpoints,Dispatch window after approval,Dedicated design review) and extendheroSubtitleandabout.valueswith approval and production-care language.data/home.jsonto provide approval-ledhowItWorkssteps, more service-specificpricingfeatures, concretetestimonials, and FAQ entries focused on approval, production, packaging, and support.assets/js/main.jsrendering and copy to reinforce approval workflows and packaging cues, change toast/login/profile hint texts to be customer-facing, and mark metrics/testimonials/pricing UI with service-oriented labels.index.htmland add a non-customer README sectionDemo implementation notesto document the static/demo implementation for contributors.Testing
python -m json.tool data/brand.json >/tmp/brand.json && python -m json.tool data/home.json >/tmp/home.jsonwhich completed successfully.git diff --checkwhich returned no issues.python -m http.server 8080and verifiedcurl -I http://127.0.0.1:8080/index.htmlreturned200 OK.MODULE_NOT_FOUND).Codex Task