Presenter notes and developer handoff
Internal only. Not shown on concept pages.
Section rationale
| Section | Patient question | Requirement | Position (A / B / C) | Still needed |
|---|---|---|---|---|
| hero | Is this the right dentist for me, here in Peterborough? | Opening: explain the practice and local relevance, one primary action. | 1 / 2 / 1 | Headline approval, authentic photo. |
| emergencyBar | I am in pain. How do I reach someone now? | Emergency phone access near the beginning (Concept B). | none / 1 / none | Phone activation approval. |
| pathways | Where do I go for what I need? | Patient pathways in normal content, not a carousel. | 4 / none / 5 | Confirm priority services. |
| serviceExplainer | What does treatment actually involve? | Service explanation and consultation guidance (Concept C). | none / none / 2 | Provider details per service. |
| why | Why choose this practice over another? | Small number of supportable distinctions. | 3 / 5 / 7 | Owner confirmation of each point. |
| dentists | Who will I see? | Approved names and roles only. No invented bios. | 2 / 4 / 3 | Photographs, optional approved bios. |
| firstVisit | What happens after I ask for an appointment? | Request, office confirmation, preparation, next steps. | 5 / 3 / 4 | Confirm actual office process. |
| trust | Can I trust what I am reading? | Attributable evidence only. No invented reviews. | 6 / 7 / 8 | Approved testimonials or affiliations. |
| faq | Practical questions before calling. | Every answer addresses its question. | 7 / 6 / 6 | Office review of answers. |
| location | Where are you and when are you open? | Approved practical details and closing action. | 8 / 8 / 9 | Confirm hours and access wording. |
Position reflects the order on each homepage and why it sits there: A puts people first for reassurance, B puts the task first for speed, C puts treatment understanding first for confidence.
Route from entry to request or phone
- A: Opening, Request an Appointment button, or Meet our dentists, then pathway card, service page, Request with service filled in.
- B: Emergency strip phone (inactive) or pathway tile in the opening, service page, Request with service filled in.
- C: Treatment explainer, service page with provider and first step, Request with service filled in.
- All: header Request button on every page; phone in mobile menu and every Location block.
What the client is selecting
A content priority and section order, plus a general visual direction. The supplied sailboat logo is in use. Final colours, authentic photography, page inventory, production platform, and URLs are later production decisions.
Content and asset register
| Item | Status | Source |
|---|---|---|
| Dentist photographs | Missing. No approved photos supplied. | Practice |
| Dentist biographies and credentials | Not published. Names and ownership only. | Our Team page |
| Hygienist and staff names | Not supplied. | Practice |
| Logo and brand colours | Supplied sailboat logo in use. Concept palettes remain provisional. | Practice |
| Office and team photography | Authentic photos not supplied. Clearly labelled illustrative photographs shown. | Practice |
| Business hours | Published on Contact page. Confirm before launch. | Contact page |
| Same-day emergency and drop-in wording | Published but not assumed. Copy says 'may be possible, call'. | Home page |
| CDCP participation | Unconfirmed. Page held as pending. | Practice |
| Implant provider and referral process | Unconfirmed. | Practice |
| 0% financing and student discounts | Published on Contact page. Excluded until approved. | Contact page |
| New Patient Promotion | Image on live site. Excluded, terms unknown. | Home page |
| Patient testimonials and reviews | Not reviewed or approved. Trust section uses facts only. | Testimonials page |
| Phone and email activation | Inactive in concept until approved. | Project brief |
| Actual appointment-request process | Assumed: request, office confirms by phone or email. Confirm. | Practice |
| Proposed headline and supporting copy | Draft, pending approval. | Strategy brief |
Developer handoff
- Shared components: ConceptShell (notice bar, upper contact strip, logo header, mobile menu, footer), RequestLink, InactivePhone, illustrative AssetSlot, PhotoHero, and shared home sections. Concept B has a three-photo scrolling carousel with previous, next, pause, and play controls; automatic movement pauses on interaction and honours reduced motion.
- Content model: one practice file holds facts, services, pathways, FAQ, and the register. Concepts only change order, hero variant, and theme tokens.
- Routes (demo only): /, /notes, /concept/a|b|c, /services, /services/[family-general, emergency, restorative, cosmetic, dental-implants, cdcp], /team, /contact, /request. Production URLs must follow the accepted inventory and redirect plan.
- Conditional content: emergency pages lead with phone and label the request as not for urgent pain; CDCP shows a pending notice until participation is confirmed.
- Form behaviour: ?service= preselects the visit type and remains editable. Client-side validation only. Nothing is transmitted, stored, emailed, or sent to analytics. Success shows the fixed concept response.
- Responsive: header collapses to Request button plus menu below 768px; grids stack to one column; tables scroll horizontally inside their own container.
- Production needs: approved phone and email activation, a real form handler with privacy review, authentic approved photography and brand colours, confirmed hours and service facts. Illustrative photos are labelled and do not represent named dentists or the real office.
- Known constraints: no practice-management integration, real-time scheduling, call tracking, or export method has been built or tested.