Theme Studio
Apply public-site themes consistently
Theme Studio controls the look of the guest-facing public pages. Recent fixes make it more important that one theme choice applies consistently across index.html, registry.html, our-story.html, details.html, and guest-facing pages, with readable opposite-color text when a light or dark background is selected.
Public theme
Preview
Readable contrast
How to use Theme Studio
- Pick a theme/background direction first: light, dark, photo-based, or color-forward.
- Use the preview to judge the public page look, not the planner admin look.
- Apply the theme, then open multiple public pages.
- Check top navigation links, page titles, section cards, form fields, and button text.
- Adjust if any page has low contrast or leftover off-theme background panels.
Pages to verify together
| Page | What to check |
|---|
| Home / index.html | Hero, nav, page title, CTA buttons, background. |
| Details / details.html | Timeline cards, text blocks, venue details. |
| Our Story / our-story.html | Story text and photo sections. |
| Registry / registry.html | Gift link cards and header text. |
| Guest portal / RSVP | Forms, summary sections, schedule, lodging, and media areas. |
Light vs dark rule
Contrast must winIf the couple chooses a light background, text and headers must switch dark enough to read. If they choose a dark/photo background, text should remain light or protected by overlays. Do not accept a pretty theme that guests cannot read.
Planner admin appearance is separate
- Planner light/dark mode is for admin usability.
- Public-site theme is for guest pages.
- Do not let planner admin appearance unintentionally restyle public pages unless that is explicitly the public theme choice.
Current known focus
- Preview should actually reflect the theme being applied.
- Background colors should not remain inconsistent across public pages.
- Top-level menu/header text must remain visible on light themes.
Need more help?
If you have tried the checks on this page and the issue still is not resolved, open a support ticket with the couple/site name, the page you were using, and what you expected to happen.