---
title: How do I create a Home Page mockup?
description: This SOP outlines the step-by-step process for designing website mockups and developing service pages. It ensures consistency, brand alignment, and SEO optimization while streamlining collaboration between team members.
---

[Skip to content](https://grow.dentalmarketing.com/university/how-do-i-create-a-mockup-for-home-page-and-service-page#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 create a Home Page mockup?

## Step-by-step process for designing a client's Home Page mockup in Claude, from the template to QA.

The Home Page mockup is the first design the client sees. It is designed in Claude from our **Homepage Mockup Template**, published to the client's preview link, and reviewed by the client in BugHerd.

Tick off each step in the client's **Build Out To Do List** (Mockup tab) as you go. The link is in the HubSpot ticket's **Buildout To Do List** field.

### **What happens automatically**

When a Mockup Design ticket is set up, the system creates:

- The client's GitHub repository and preview site.
- The client's BugHerd project, for client feedback on the preview link.
- The client's copy of the Build Out To Do List, linked on the ticket.

When your design is finished and its link is on the ticket, it is published to the preview link with the BugHerd sidebar.

### **Before you start**

1. Read the HubSpot ticket and the company notes for any requests from the team or the client.
2. Collect the brand guide, logo (regular and white, SVG), favicon, fonts and the homepage copy brief. Ask the Account Manager for anything missing before you start designing.
3. Check the client's Google Drive folder and use every asset in it (photos, videos, headshots, team photos) before any stock photos.
4. Check the client type: startup, multi-location, or redesign of a current site. It changes the buttons, phone and location sections.
5. Look at the current website, if any, and note sections the client wants to keep.
6. Check the demographics in HubSpot before choosing stock photos.

### **Step 1: Set up**

1. In Claude, open the Artifacts tab and duplicate [Homepage Mockup Template | Dental Practice - ID](https://claude.ai/artifact/RuMivKhdYy6a3H57PQtj4w).
2. Rename the copy with the practice name and its HubSpot company ID, for example *Homepage Mockup Template | Smith Family Dental - 12345678901*.
3. Upload the brand guide PDF, the logo SVGs, the homepage copy brief and the photos from the Drive folder.

### **Step 2: Apply the brand**

- Ask Claude to build the homepage mockup from the template using the brand guide. It sets the colors, fonts and logo versions (color, white, single-color).
- Ask it to add the logo to the header and footer.
- Try a different headline font if needed, for example "try Syne".
- Add the Typekit kit ID if the brand font is an Adobe font.

### **Step 3: Content rules**

- Use the real practice name, phone, address and hours from HubSpot. No placeholder info. The only exception: if the practice has no phone number yet, use (000) 000-0000.
- The H1 includes the city and state. The hero buttons are **Book** and **Location**.
- Startups only: the buttons say "Follow Us", and there is no phone or reviews section.
- Buttons have a visible hover state, and the button text is the same everywhere.

### **Step 4: Refine the layout**

Give feedback one section at a time and keep it specific, for example "make this 60/40", "remove the boxes" or "make the icons circular".

### **Step 5: Add imagery**

- Use the practice photoshoot if there is one. If not, use stock photos that match the demographics.
- Place real photos in the hero, office tour, doctor portrait, services and Connect sections.
- For background textures, ask Claude for an image-generation prompt, generate the image, upload it and ask Claude to place it.
- Optional: use the brand monogram or a city outline as a watermark.

### **Step 6: Polish**

- Paste the **Final UI/UX Polish** prompt (at the end of this SOP) to add motion, hover and focus states, accessibility fixes and faster image loading.
- Ask for a mobile/responsive audit. It checks 320, 390, 768 and 1024px widths.

### **Step 7: Double-check**

- No lorem ipsum, typos or em dashes.
- On desktop and mobile: the hero fills the screen, spacing is even, and nothing overlaps or is cut off.
- Images are sharp and no heads are cropped.

### **Step 8: Hand off and send to QA**

1. Paste the link to your mockup in Claude in the ticket's **Home Page Mockup Project Link** field, so it can be published to the preview link.
2. Once it's published, check that the preview link opens straight to the Home Page and the BugHerd sidebar shows. In the BugHerd project, click "I've done this" on the install-script step.
3. Paste the preview link on the HubSpot ticket.
4. Send it to QA for review.
5. Update your task in Monday. On the Projects board, update the project's person and status.

### **Final UI/UX Polish prompt**

Copy everything below into Claude in Step 6.

Act as a Staff Front-End Engineer and Interaction Designer from Apple. Perform a final production-quality polish pass on this landing page.

Treat the current design direction as approved. Do not redesign the page, change the brand direction, or replace the existing visual concept. Instead, elevate the execution until the experience feels refined, cohesive, premium, responsive, and intentional.

Make the changes directly in the codebase. Do not explain your reasoning unless you encounter a meaningful tradeoff, a potentially destructive change, or something that requires my approval.

The goal is for the finished page to feel exceptionally polished without appearing overdesigned.

**1. Audit the Existing Page**

Review the entire page before making changes.

Identify and improve:

- Inconsistent spacing
- Weak visual hierarchy
- Uneven alignment
- Awkward typography
- Excessive line lengths
- Poorly balanced sections
- Inconsistent buttons
- Inconsistent borders, shadows, and corner radii
- Unclear interactive states
- Sections that feel visually unfinished
- Elements that do not appear to belong to the same design system

Preserve the existing brand identity, copy, content hierarchy, and overall design direction.

**2. Responsive Behavior**

Audit and refine the page across all major viewport sizes:

- Small mobile devices starting at 320px
- Standard mobile devices
- Tablet
- Laptop
- Desktop
- Large and ultrawide screens

Ensure that:

- There is no horizontal overflow
- Content stacks naturally
- Text remains readable
- Typography scales appropriately
- Images remain properly cropped and proportioned
- Grids and cards collapse elegantly
- Navigation works cleanly on mobile
- Buttons remain appropriately sized
- Touch targets are comfortable
- Section padding adapts to each viewport
- Nothing feels cramped, stretched, oversized, or visually empty
- Decorative elements do not interfere with content
- Fixed or sticky elements behave correctly

Do not merely make the page technically responsive. Make every breakpoint feel intentionally designed.

**3. Motion and Micro-Interactions**

Add subtle, high-quality motion where it improves the experience.

Potential enhancements include:

- Elegant scroll-reveal animations
- Controlled staggered entrances
- Fade and translate transitions
- Smooth hover states
- Button press feedback
- Card lift or depth changes
- Subtle image scaling
- Animated navigation indicators
- Refined accordion transitions
- Modal entrance and exit animations
- Smooth anchor scrolling
- Icon movement
- Loading transitions
- Section-to-section pacing

Use restraint.

Do not animate every element. Avoid repetitive effects where every section enters in exactly the same way. Motion should support hierarchy, guide attention, and make the interface feel responsive.

Favor subtlety over spectacle.

**4. Scrolling Experience**

Refine the scrolling experience so the page feels fluid and deliberate.

Review:

- Reveal timing
- Animation duration
- Animation easing
- Stagger timing
- Section pacing
- Scroll-trigger thresholds
- Sticky elements
- Anchor navigation
- Parallax or depth effects, only where appropriate

Avoid excessive parallax, scroll hijacking, long delays, or animations that make the user wait for content.

Content should remain immediately understandable and usable even when animations are disabled.

**5. Interaction States**

Review every interactive element and ensure it has appropriate states.

Check:

- Default
- Hover
- Focus
- Active
- Pressed
- Selected
- Disabled
- Loading
- Success
- Error
- Empty

Test all:

- Buttons
- Links
- Forms
- Navigation
- Menus
- Accordions
- Tabs
- Carousels
- Sliders
- Modals
- Tooltips
- Dropdowns
- Calls to action
- Interactive cards

Every interaction should feel deliberate and complete.

**6. Accessibility**

Perform an accessibility pass without compromising the visual design.

Verify:

- Semantic HTML
- Logical heading hierarchy
- Keyboard navigation
- Visible focus states
- Sufficient color contrast
- Accessible forms and labels
- Correct button and link semantics
- Appropriate ARIA attributes
- Screen-reader compatibility
- Accessible error messaging
- Accessible modal behavior
- Proper alt text
- Sensible tab order
- Adequate touch-target sizes

Respect prefers-reduced-motion and provide a reduced-motion experience that remains polished and functional.

Do not rely on hover alone to communicate important information.

**7. Performance**

Keep all enhancements lightweight and production-ready.

Prioritize:

- Smooth 60fps motion
- GPU-friendly transforms
- Animating transform and opacity where possible
- Minimal layout recalculation
- No unnecessary scroll listeners
- No layout thrashing
- No cumulative layout shift
- Proper image dimensions
- Responsive image loading
- Lazy loading for non-critical media
- Efficient font loading
- Reduced JavaScript overhead
- Minimal DOM complexity
- Clean event handling
- Proper component cleanup

Do not add heavy libraries when native CSS, the current framework, or an existing dependency can accomplish the same result.

**8. Code Quality**

Refactor only where it improves reliability, clarity, consistency, or maintainability.

Review for:

- Duplicate logic
- Repeated styles
- Dead code
- Unused imports
- Inconsistent naming
- Overly complex components
- Hardcoded values that should use shared tokens
- Inconsistent breakpoints
- Inconsistent animation values
- Console warnings
- Runtime errors
- Missing keys
- Broken event listeners
- Hydration issues
- Invalid markup

Preserve the existing architecture unless there is a clear reason to improve it.

Do not perform a broad rewrite simply for stylistic preference.

**9. Design-System Consistency**

Standardize the page so all elements feel related.

Review and normalize:

- Color usage
- Typography
- Font weights
- Line heights
- Letter spacing
- Spacing scale
- Grid behavior
- Border treatments
- Corner radii
- Shadows
- Button styles
- Form controls
- Icons
- Animation durations
- Easing curves
- Hover behavior
- Focus behavior
- Section widths
- Container widths

Reuse existing design tokens where available. Create shared tokens only when doing so meaningfully improves consistency.

**10. Content Presentation**

Do not rewrite the page copy unless correcting an obvious typo, grammar issue, formatting problem, or broken line break.

You may improve how the content is presented by adjusting:

- Width
- Spacing
- Alignment
- Hierarchy
- Emphasis
- Line length
- Text wrapping
- Responsive behavior

Do not alter the intended message.

**11. Final QA Pass**

After completing the changes, review the entire page again from top to bottom.

Test at minimum:

- Small mobile
- Standard mobile
- Tablet
- Laptop
- Desktop
- Large desktop

Confirm that:

- The layout is visually cohesive
- The page feels intentionally designed at every breakpoint
- The mobile experience is not a simplified afterthought
- All interactions work
- Hover, focus, and pressed states are present
- Animations are subtle and consistent
- Reduced-motion behavior works
- There is no horizontal overflow
- Images do not distort
- Text does not clip
- Sticky and fixed elements behave correctly
- Forms work correctly
- There are no console errors
- There are no obvious accessibility issues
- There are no unnecessary performance regressions
- No section feels unfinished
- No element feels visually disconnected from the rest of the page

**Constraints**

- Do not redesign the page
- Do not change the brand identity
- Do not change the core layout without a clear usability reason
- Do not rewrite the copy unnecessarily
- Do not add motion merely for decoration
- Do not overuse glass effects, gradients, shadows, blur, or parallax
- Do not introduce unnecessary dependencies
- Do not sacrifice accessibility for aesthetics
- Do not sacrifice performance for animation
- Do not stop after a single superficial pass

Work through the page in multiple passes:

- Audit
- Responsive refinement
- Interaction and motion polish
- Accessibility and performance review
- Final visual QA

Continue refining until no obvious, meaningful improvements remain.

Make the changes directly. At the end, provide only a concise summary of what was changed, any important tradeoffs, and any items that still require manual review.

- [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