---
title: How do I implement a website?
description: This process outlines the design steps for build-outs, enabling web designers in the company to adopt it faster and work more efficiently. It promotes consistency, effective collaboration, and meets client requirements while adhering to industry-best
---

[Skip to content](https://grow.dentalmarketing.com/university/how-do-i-implement-a-website-design#main-content)

English

Show submenu for translations

[Customer portal](https://grow.dentalmarketing.com/tickets-view?hsLang=en)

![DentalMarketing-Logo2-White copy-1.png\]](https://grow.dentalmarketing.com/hs-fs/hubfs/DentalMarketing-Logo2-White%20copy-1.png?height=40&name=DentalMarketing-Logo2-White%20copy-1.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://grow.dentalmarketing.com/tickets-view)
- [Don't see the SOP you're looking for? Submit your suggestion here.](https://share.hsforms.com/1Fk5_GHeGTTqeJyg4BwR0CAdihez)

[Don't see the SOP you're looking for? Submit your suggestion here.](https://share.hsforms.com/1Fk5_GHeGTTqeJyg4BwR0CAdihez)

 Welcome! What article can we help you find?

- There are no suggestions because the search field is empty.

1. [Internal](https://grow.dentalmarketing.com/university?hsLang=en)
2. [Creative Team SOPs](https://grow.dentalmarketing.com/university/creative-team-sops?hsLang=en)

# How do I implement a website?

## Turn the approved Home Page and Core Pages mockups into the client's website with the website buildout prompt, then review it with the Build Out To Do List.

During **Website Production**, the approved **Home Page** and **Core Pages** mockups become the client's full website. Claude builds it in the client's GitHub repository from the **website buildout prompt**. The Web Designer then reviews and finishes it, following the **Website** tab of the client's Build Out To Do List (linked in the HubSpot ticket's **Buildout To Do List** field), and sends it to QA.

### **Before you start**

1. Read the HubSpot ticket, the company notes and the handoff document (handoff.md in the repository).
2. Check the repository has what the build needs: **mockup-home** and **mockup-core** in the Design folder, and the **content brief**, **reviews** and, for redesigns, the **SEO sheet** in the Intake folder. If anything is missing, ask the Creative Lead before running the build.
3. Check the client's Google Drive folder and use every asset in it (photos, videos, headshots, team photos) before any stock or library photos.
4. First time? Follow the *Github: Initial Setup* tab of [Creative Buildouts SOPs + Guides](https://docs.google.com/document/d/1ncvTH69_MkbiloWKmJvXZwANYSk7f4-xZkSeyXyJ-UA/edit?tab=t.0) to get the repository on your computer.

### **Step 1: Run the build**

1. Open the client's repository on the **development** branch.
2. Copy the **project block** below, fill in the links, and paste it into Claude followed by the **system prompt**. Use the system prompt as is. Don't edit its design instructions.
3. Go through every flag and question in Claude's report. Don't guess: anything you can't answer goes in the handoff document.

The latest version of both prompts lives in the [Buildouts tab of Creative Buildouts SOPs + Guides](https://docs.google.com/document/d/1ncvTH69_MkbiloWKmJvXZwANYSk7f4-xZkSeyXyJ-UA/edit?tab=t.x3adjakd2e0g). If it differs from the copies below, use that one.

#### **Project block (fill in per client)**

```
Please run the website buildout for this client.

Start here: Before anything else, read handoff.md for relevant info about this client and build.

Links
- HubSpot company: [company record link]
- HubSpot ticket: [ticket record link]
- Approved home page mockup feedback: [link]
- Approved core pages mockup feedback: [link]
- Client Slack channel: [link]. Read it for any recent decisions or requests about the site.
```

#### **System prompt (use as is)**

```
Files: Everything you need is in the Design and Intake folder. The approved designs are the mockup-core and mockup-home files, and they already have HTML and CSS structure.

Design fidelity is the top priority. Past buildouts have had big gaps between the build and the approved design. The finished site should match mockup-core and mockup-home as close to 100% as possible:
- Use the mockups' HTML and CSS as the source of truth for layout, spacing, typography, colors, images and section order. Don't change or "improve" the design.
- Read the feedback on both approved mockups and apply every requested change. If the feedback conflicts with the mockup, follow the feedback and tell me where.
- If something in the mockups can't be built exactly, tell me what and why. Don't quietly swap in something else.

Before you say you're done:
1. Compare every page of the build side by side with the mockup at desktop, tablet and mobile widths.
2. List every difference you find, fix it, and compare again.
3. Go through the feedback on both mockups and confirm each item is done.
4. Give me a short summary of what you built, any differences you couldn't fix, and anything you need from me.

If anything is unclear or missing, ask me before you start.
```

If Claude isn't available, don't build the site by hand. Tell the Creative Lead.

### **Step 2: Review the build**

1. **Match the mockups:** compare each page with the mockup side by side: section order, spacing, type, colors and photos. Claude's comparison catches size and spacing differences, not a section in the wrong order or a photo in the wrong spot.
2. **Feedback:** every change in the mockup feedback is on the site. Where Claude said the feedback conflicted with the mockup, the feedback was followed.
3. **Images:** each photo fits its spot, service photos show that service, doctor photos sit next to their own bio, and nothing is blurry or cropped badly. Use the photoshoot over library photos when there is one. See [How do I choose photos for a website?](https://grow.dentalmarketing.com/university/how-do-i-implement-the-photography-and-graphics-to-a-web-project?hsLang=en) for the photo rules.
4. **Demographics:** the demographics in practice.ts match the HubSpot Demographics field, and stock photo faces fit the community. If HubSpot has no Demographics, flag it in the handoff.
5. **Empty photo slots:** fill the ones the build left empty or flagged.
6. **Read every page as a visitor would:** the copy reads well, nothing is cut off, and the sections the client wanted to keep from the old site are there.
7. **Devices:** check desktop, tablet and mobile: menu, hover states, animations and Typeform styling.
8. **Don't force it:** don't change approved colors to pass a contrast check, and if the mockup needs something the template can't do, don't force it. List both for the Creative Lead.

### **Step 3: Before QA**

1. Run **/qa-buildout** in Claude. Fix every launch blocker and confirm each warning is on purpose. No Place ID yet is OK (the map and address work without it), but add "Add the Place ID to turn on the rating badge" to the handoff.
2. Add the client's Basin form links to practice.ts: the **Website Booking Form** (bookingFormEndpoint) and the **Website RM Widget Form** (rmWidget.feedbackFormEndpoint). Add the RM link even if the design doesn't show the widget yet. Ask the Creative Lead if either link is missing.
3. Submit each form once on staging and confirm it goes to the Thank You page.
4. Push **development** to **staging** and check that the staging link shows the latest work. **Never push to main:** a push to main goes live.
5. The BugHerd sidebar shows on the staging link only, not on the live site. In the BugHerd project, click "I've done this" on the install-script step.
6. Check the favicon and the Open Graph (share) image.
7. Update the handoff document with anything still open: questions you couldn't answer, and anything you need from QA, the client or the Onboarding Lead/Specialist. Say who each item is for.

### **Step 4: Send to QA**

1. Put the staging link and the BugHerd link on the HubSpot ticket, and send it to QA.
2. Update your task in Monday. On the Projects board, update the project's person and status.

QA then follows *How do I perform Content & UX QA for a New Website (Full Site and Start-Up)?*

- [Paid Media SOPs](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#main-content)

    - [Account Management & Updates](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#account-management-updates)
    - [Facebook Ads](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#facebook-ads)
    - [Google Ads](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#google-ads)
    - [Microsoft Ads](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#microsoft-ads)
    - [GMB](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#gmb)
    - [SEO](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#seo)
    - [Optmyzr](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#optmyzr)
    - [Google Analytics](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#google-analytics)
    - [Google Tag Manager](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#google-tag-manager)
    - [Google Ads Editor](https://grow.dentalmarketing.com/university/paid-media-sops?hsLang=en#google-ads-editor)
- [Creative Team SOPs](https://grow.dentalmarketing.com/university/creative-team-sops?hsLang=en#main-content)

    - [Mail LP](https://grow.dentalmarketing.com/university/creative-team-sops?hsLang=en#mail-lp)
    - [Lost Client](https://grow.dentalmarketing.com/university/creative-team-sops?hsLang=en#lost-client)
- [Client Success SOPs](https://grow.dentalmarketing.com/university/client-success-sops?hsLang=en#main-content)

    - [Photoshoot](https://grow.dentalmarketing.com/university/client-success-sops?hsLang=en#photoshoot)
    - [Claude Design Landing Pages](https://grow.dentalmarketing.com/university/client-success-sops?hsLang=en#claude-design-landing-pages)
- [Technology SOPs](https://grow.dentalmarketing.com/university/technology-sops?hsLang=en#main-content)

    - [Dashboard](https://grow.dentalmarketing.com/university/technology-sops?hsLang=en#dashboard)
    - [ChatGPT](https://grow.dentalmarketing.com/university/technology-sops?hsLang=en#chatgpt)
    - [HubSpot](https://grow.dentalmarketing.com/university/technology-sops?hsLang=en#hubspot)
    - [Other](https://grow.dentalmarketing.com/university/technology-sops?hsLang=en#other)
- [Company Information SOPs](https://grow.dentalmarketing.com/university/company-information-sops?hsLang=en)
- [Direct Mail SOPs](https://grow.dentalmarketing.com/university/direct-mail-sops?hsLang=en)
- [Organic Social Media SOPs](https://grow.dentalmarketing.com/university/organic-social-media-sops?hsLang=en#main-content)

    - [Content Creation](https://grow.dentalmarketing.com/university/organic-social-media-sops?hsLang=en#content-creation)
    - [OB Process](https://grow.dentalmarketing.com/university/organic-social-media-sops?hsLang=en#ob-process)
- [Compliance Team SOPs](https://grow.dentalmarketing.com/university/compliance-team-sops?hsLang=en#main-content)

    - [WhatConverts](https://grow.dentalmarketing.com/university/compliance-team-sops?hsLang=en#whatconverts)
    - [Tickets](https://grow.dentalmarketing.com/university/compliance-team-sops?hsLang=en#tickets)
    - [Edits](https://grow.dentalmarketing.com/university/compliance-team-sops?hsLang=en#edits)
    - [Websites](https://grow.dentalmarketing.com/university/compliance-team-sops?hsLang=en#websites)
- [Onboarding SOPs](https://grow.dentalmarketing.com/university/onboarding-sops?hsLang=en)
- [Content Creation SOPs](https://grow.dentalmarketing.com/university/content-creation-sops?hsLang=en)
- [Creative Support](https://grow.dentalmarketing.com/university/creative-support?hsLang=en#main-content)

    - [Ticket Creation](https://grow.dentalmarketing.com/university/creative-support?hsLang=en#ticket-creation)

# Dentalmarketing.com

dentalmarketing.com Help Center

Copyright © 2026, Dentalmarketing.com