Freeframe

Documentation

Soiree

v1.0.0Updated Nov 15, 2026An editorial wedding and event planner website with a budget estimator and venue guide.

Overview#

Soiree is an editorial, magazine-style website for wedding and event planners, built as a WordPress block theme. The demo brand is Ivy & Ash Events, a fictional planning studio at 112 Church Street in Charleston, South Carolina, that offers full planning, partial planning and day-of coordination for weddings, corporate events and private parties. It uses US spelling and US dollars and works out its dates in Eastern time (America/New_York). The theme has a magazine-cover home page, a services page with a comparison table and questions, a budget estimator, a portfolio with a case-study dialog, a seven-step process with a date checker, a venue guide with a saved shortlist, a journal, an inquiry form and a 404 page. It is version 1.0.0 (see template.json and style.css), works with WordPress 7.1 and PHP 7.4 or newer, and is the WordPress version of the HTML template of the same name. See it live at freeframe.dev/templates/soiree.

Headings, copy, lists, cards, quotes, buttons, the process steps and the questions are core WordPress blocks arranged in block patterns, so you edit them in the block editor without touching code. The parts that are worked out in the browser (the budget estimator and its result, the portfolio filters, grid and dialog, the date checker, the venue filters and list, and the inquiry form with its confirmation) work as in the HTML version: they are Custom HTML blocks driven by assets/js/main.js, which reads the studio's prices, celebrations and venues from assets/js/data.js. The two tables are Custom HTML blocks too. Colors, fonts and font sizes are design tokens in theme.json: change them in Appearance > Editor > Styles and the whole site follows.

The look is a printed magazine: ink on cream paper with one blush and rose accent, fine double rules, a high-contrast serif (Playfair Display) over a quiet sans (Mulish) and line-art drawings. It has a light color scheme only.

Quick start#

Requirements: WordPress 7.1 or newer and PHP 7.4 or newer. No plugins are needed.

  1. Download soiree.zip from freeframe.dev/templates/soiree (the WordPress tab).
  2. In your WordPress admin go to Appearance > Themes > Add New Theme > Upload Theme, choose the zip and click Install Now, then Activate. The theme is listed as Freeframe Soiree.
  3. Go to Appearance > Soiree setup and click Create the demo pages. This creates the Home, Services & packages, Budget estimator, Portfolio, Our process, Charleston venue guide, Journal and Inquire pages from the theme's page patterns, sets Home as the front page (Settings > Reading) and creates the header menu. Pages that already exist with the same slug are left alone, so it is safe to click it again.
  4. Set the site title and tagline in Settings > General ("Ivy & Ash Events" and "Wedding and event planners in Charleston, SC" in the demo): they make up the browser titles.
  5. Visit your site. Edit any page in Pages, and the header, footer and templates in Appearance > Editor.

You can also try the theme without installing anything: the Try it in WordPress button on freeframe.dev opens it in WordPress Playground (WordPress running in your browser) with the demo pages already set up.

To work on the theme's files locally you need Node.js 24 and pnpm; WordPress itself runs in WordPress Playground, so there is no PHP, web server or database to install:

sh
pnpm install
pnpm dev     # builds the CSS, then starts WordPress with the theme at http://127.0.0.1:9400

pnpm dev signs you in as admin (password password) and creates the demo pages. The site is rebuilt from scratch every time you start it; your edits to theme files are live, edits made in the WordPress admin are not kept.

Pages#

Each page is a page pattern (in Patterns > Soiree pages) made of section patterns. Every section is also offered on its own in the block inserter under Patterns > Soiree.

Page Slug Page pattern Sections (pattern files in patterns/)
Home / page-home.php home-hero, in-this-issue, press, founder-letter, home-services, home-quote, recent-celebrations, home-process, estimator-and-journal
Services & packages /services/ page-services.php services-hero, package-full (#full), package-partial (#partial), package-dayof (#dayof), compare-packages (#compare, a table), beyond-weddings, add-ons, questions
Budget estimator /estimator/ page-estimator.php estimator-hero, estimator (the form and its result), estimator-method
Portfolio /portfolio/ page-portfolio.php portfolio-hero, celebrations (filters and the grid from celebrations), kind-words, case-dialog
Our process /process/ page-process.php process-hero, where-to-start (the date checker), steps, promise
Charleston venue guide /venues/ page-venues.php venues-hero, venue-guide (filters and the list from venues)
Journal /journal/ page-journal.php journal-hero, journal-articles (contents, four articles with #real-cost, #rain-plan, #thursday and #tipping, and #press)
Inquire /inquire/ page-inquire.php inquire-hero, inquiry (the form and "What happens next")
404 any missing URL templates/404.html 404

WordPress posts use templates/single.html; the blog, archives and search results use templates/index.html, templates/archive.html and templates/search.html. A page that should show its title above plain content can use the Page with title template.

Project structure#

freeframe-soiree/
  style.css                 theme header (name, version, requirements, license); no styles
  theme.json                design tokens: palette, fonts, font sizes, spacing, layout widths, button
  functions.php             loads the files in inc/
  inc/setup.php             stylesheet and scripts (with the script's strings, page and artwork URLs),
                            editor styles, the `js` class script, theme color and favicon, page titles,
                            the header's menus and the markup blocks can't store, pattern categories
  inc/icons.php             registers assets/icons/*.svg for the Icon block
  inc/icon-labels.php       the icons' names shown in the editor
  inc/block-styles.php      button block styles
  inc/site-setup.php        Appearance > Soiree setup: creates the demo pages and the menu
  templates/                page.html (pages), page-with-title.html, single.html, index.html,
                            archive.html, search.html, 404.html
  parts/                    header.html and footer.html (they show the header and footer patterns)
  patterns/                 every section and page (PHP files with block markup)
  assets/css/theme.css      the compiled stylesheet (do not edit: built from src/)
  assets/css/editor.css     the same for the block editor (generated by src/editor-css.mjs)
  assets/js/data.js         the studio's content (window.SOIREE): packages, seasons, add-ons,
                            venues, celebrations
  assets/js/main.js         every interaction (the HTML version's script plus a WordPress adapter)
  assets/icons/             the icon used by Icon blocks (arrow-right)
  assets/img/               hero-piazza.svg, art-*.svg, favicon.svg and the social image
  assets/fonts/             Playfair Display and Mulish, with their licenses
  src/theme.css             the Tailwind CSS source of assets/css/theme.css
  src/icons.css             icons drawn before or after text with CSS (generated)
  src/editor-css.mjs        writes assets/css/editor.css after each build
  languages/                freeframe-soiree.pot, the template for translations
  blueprint.json            WordPress Playground setup used by `pnpm dev`
  screenshot.png            the picture shown in Appearance > Themes
  package.json              the CSS build and the local WordPress (Node.js tooling)
  readme.txt, README.md, DOCS.md, CHANGELOG.md, LICENSE.txt

Customizing#

Brand and colors#

The palette is in theme.json (settings.color.palette) and shows in Appearance > Editor > Styles > Colors. The stylesheet maps every Tailwind color to these presets (--color-rose: var(--wp--preset--color--rose) in src/theme.css), so changing Rose in Styles changes every kicker, italic, marker and focus ring that uses rose.

Color Value Tailwind name Used for
Base (Cream) #f4ede1 cream Page background
Contrast (Ink) #16130f ink Text, rules, dark sections, buttons
Ink soft #2a251f ink-soft Body copy
Paper #fbf7ef paper Cards, form fields, alternate sections
Bone / Rule #ebe2d3 / #cdbfa8 bone / rule Fine rules and dividers
Muted #5f574d muted Secondary text
Blush / Blush soft #e8cfc3 / #f3e3db blush / blush-soft The accent surfaces
Rose / Rose deep #8f4c3e / #763c30 rose / rose-deep Accent text, italics, focus rings, bars / button hover
Gold / Champagne #a88654 / #d9c39a gold / champagne Link underlines, line-art details / accents on ink

To change the accent, set Rose, Rose deep, Blush and Blush soft in Styles (or in theme.json). Keep Rose dark enough for text on cream (at least 4.5:1). The illustrations in assets/img/ have their colors written into the SVG files; search and replace #8f4c3e, #a88654 and #f3e3db there too. A few one-off tints are written as hex values in the patterns (text-[#d8cfc1] and text-[#b9ab97] on ink, #a2231a for form errors).

The repeated pieces are classes in src/theme.css: .wrap (the page width), .display, .headline, .kicker, .smallcaps, .folio, .lead, .pull-quote, .dropcap, .prose-mag (article text), .rule-double, .frame and .art (picture frames), .link, .more (the small "read on" links), .on-ink (a dark band) and the form classes (.label, .field, .hint, .field-error, .option). Add them to any block under Advanced > Additional CSS class(es).

Typography#

Two families are bundled in assets/fonts/ and declared in theme.json (no requests to Google), the same files Google Fonts serves to the HTML version:

  • Playfair Display (font-display, the display serif; a variable font with weights 400–700 and italics). Headings use the display, headline, pull-quote and font-display classes.
  • Mulish (font-sans, the body font; a variable font with weights 400–800, italic 400–600). Small uppercase labels use kicker and smallcaps.

Swap a family in Styles > Typography, or add your own fontFace files to theme.json. The font sizes (text-sm to text-9xl) are presets too (Styles > Typography > Font sizes).

Content#

Page copy (headings, paragraphs, the packages, the press names, the founder's letter, the questions, the journal articles) is in the pages: edit it in the block editor. Data that the script renders or calculates with lives in assets/js/data.js, on the window.SOIREE object, as in the HTML version:

Name Shape Used by
timeZone 'America/New_York' Date checks on Process and Inquire, the years in the header and footer
packages { full, partial, dayof } each { name, base, perGuest, blurb } Estimator fee
eventTypes { wedding, corporate, private } each { name, perGuest } Estimator vendor spend
seasons { peak, summer, winter } each { name, months, feeFactor, spendFactor } Estimator
addons { welcome, rehearsal, brunch, transport, design } each { name, price } Estimator fee
breakdown [{ name, share }], shares adding up to 1 Estimator breakdown
guestLimits { min: 20, max: 400, step: 10, initial: 120 } Estimator guests
spread { fee: [0.95, 1.1], spend: [0.85, 1.2] } Low and high ends of each range
areas { downtown, 'mount-pleasant', islands, rural, north } → label Venue filter
settings { indoor, outdoor, both } → label Venue labels
venues [{ id, name, area, setting, min, max, priceFrom, art, note }] Venue guide, inquiry shortlist
eventTypeLabels { wedding, corporate, private } → label Portfolio filter and labels
celebrations [{ id, title, type, date, venue, guests, pkg, art, headline, summary, story, details, quote, by }] Portfolio grid and dialog

To add a venue, append an object to venues (its art is the middle of an assets/img/art-*.svg file name):

js
{ id: 'magnolia-hall', name: 'Magnolia Hall', area: 'downtown', setting: 'indoor', min: 40, max: 180,
  priceFrom: 7200, art: 'loft', note: 'A restored 1890s meeting hall with a sprung dance floor.' }

Use a new, URL-safe id, an area that exists in areas and a setting that exists in settings. If you add an area, also add an <option> to the Area select in the venue guide's filters (a Custom HTML block on the Charleston venue guide page). Celebrations work the same way; their type must be a key of eventTypeLabels. Package prices are also written in the pages (home, services and estimator pages and the comparison table): update both when you change packages. The counts on the portfolio filter buttons ("All 8") are worked out by the script.

Edit data.js in a child theme (see Child themes) so an update doesn't overwrite it.

Images and artwork#

All artwork is SVG line art drawn for this template, in assets/img/: hero-piazza.svg (480 x 600) on the home page and eight art-*.svg files (400 x 500, a 4:5 ratio) for celebrations, venues and packages. In the pages they are Image blocks inside a frame or art Group, which crops them with object-fit: cover: select an image and Replace to use a photo (keep a similar 4:5 portrait ratio). Decorative images have an empty alt text; give real photos a meaningful one.

Two classes on an Image block carry attributes the block can't store, and freeframe_soiree_image_attributes() in inc/setup.php writes them on the <img>: [&_img]:ff-size-400x500 becomes width="400" height="500" (the picture's own size) and [&_img]:ff-lazy becomes loading="lazy". Change the numbers, or remove the classes, when you replace a picture.

The portfolio cards, the case-study dialog and the venue guide take their pictures from the art value in data.js: art: 'garden' shows assets/img/art-garden.svg. Add a file named art-<name>.svg to that folder and it is available (freeframe_soiree_art_urls() lists the folder for the script).

The social image is assets/img/og-image.png (1200 x 630, source og-image.svg); the favicon assets/img/favicon.svg is used until you set a Site Icon in Settings > General.

The header and footer are template parts (parts/header.html, parts/footer.html) showing the header and footer patterns. Edit them in Appearance > Editor > Patterns > Header / Footer.

The header has three Navigation blocks showing the same menu: one left of the wordmark, one right of it (both from 1024 px) and the full-screen mobile menu (#mobile-menu). Edit the menu once in Appearance > Editor > Navigation (the setup creates "Main menu": Home, Services, Estimator, Portfolio, Process, Venues, Journal and Inquire). freeframe_soiree_header_nav() in inc/setup.php gives each block its links from the links' classes (a link's Advanced > Additional CSS class(es)):

Class on the link Where it shows
none Left of the wordmark, and in the mobile menu
ff-nav-secondary Right of the wordmark, and in the mobile menu
ff-mobile-only Only in the mobile menu (Home and Inquire: the wordmark links home and the header has its own Inquire button)

The mobile menu numbers its links ("01", "02"...) in menu order. WordPress marks the current page's link with aria-current="page", and freeframe_soiree_header_current() marks the header's Inquire button the same way on the inquiry page. A Navigation block that doesn't point at a menu shows the most recently created one; to pin a menu, select the Navigation block and choose it in the block settings, for all three blocks.

The wordmark is a paragraph with a link (the name and the line under it); the footer's page links are a List block: click a link to change it, press Enter to add one. The address, phone number and email appear in the footer, in the mobile menu and on the inquiry page; search for them when you change them.

The years in the top line ("Now booking 2027 & 2028") and the footer copyright are written by PHP when the page is made, and filled in again by assets/js/main.js from today's date in Charleston: <span data-year> shows this year and <span data-year-ahead="1"> / data-year-ahead="2" show next year and the year after, so the site never advertises a season that has passed. To show fixed years, replace the spans with plain text (edit the paragraph as HTML).

Features#

Budget estimator#

Budget estimator page (estimator pattern), code under "Budget estimator" in assets/js/main.js. The visitor picks an event type, guest count, season, package and add-ons; the panel updates at once.

  • Planning fee = (base + perGuest x guests above 50) x season feeFactor + add-on prices. The range is the fee times spread.fee, rounded to $100.
  • Vendor spend = guests x event type perGuest x season spendFactor. The whole-celebration range is spend times spread.spend plus the fee range, rounded to $500. The per-guest figure is the midpoint divided by guests, rounded to $10.
  • The breakdown multiplies the spend range by each breakdown share.
  • "Full design and styling" is part of full planning, so it is checked and disabled for that package.
  • With the defaults (wedding, 120 guests, spring or fall, full planning, no add-ons) it shows $18,100 – $20,900 for the fee and $50,500 – $67,000 for the whole celebration, about $490 per guest.
  • ?package=full|partial|dayof (used by the Services page) selects a package. Choices are saved under soiree-estimate. "Start over" restores the defaults and clears the saved value.
  • "Send this with an inquiry" links to the Inquire page with ?package=…&guests=…&type=…. The script turns the HTML file name inquire.html into your WordPress page URL with freeframe_soiree_page_urls() in inc/setup.php.
  • window.SOIREE_ESTIMATE(state) returns the calculation, for testing or reuse.

Every figure is labeled as an estimate only, not a quote. Accessibility: native radio buttons and checkboxes in fieldsets with legends; the slider and number field are labeled; a polite live region announces the new ranges half a second after the last change.

Portfolio filter and case studies#

Portfolio page (celebrations and case-dialog patterns), code under "Portfolio" in main.js. Cards are rendered from celebrations in a staggered seven/five column grid. The filter buttons (data-filter) use aria-pressed, show counts and update a polite status ("Showing 2 celebrations"). The filter is kept in the URL as ?type=wedding|corporate|private.

Each card title is a button that opens a native <dialog> with the full story. ?case=<id> opens a story directly (if it's hidden by the filter, the filter resets to All). In the dialog, previous/next buttons and the Left/Right arrow keys move through the visible stories, Esc or a click on the backdrop closes it, and focus returns to the story's card. "Plan something like this" links to the Inquire page with ?type=<type>.

Venue guide and shortlist#

Charleston venue guide page (venue-guide pattern), code under "Venue guide" in main.js. Filters: Area (?area= in the URL), Setting, Guests (venues whose minimum and maximum include the number) and Sort (name ignoring a leading "The", lowest price, largest capacity). "Shortlist only" (aria-pressed) shows saved venues. Each "Save" button is a toggle with aria-pressed and a toast confirms the change. When nothing matches, an empty state offers "Clear filters". The shortlist is saved under soiree-shortlist and appears on the inquiry form.

Where would you start?#

Our process page (where-to-start and steps patterns), code under "Process" in main.js. The visitor enters an event date; the script works out the whole months between today in Charleston (America/New_York) and that date, then marks the first step whose months-ahead threshold is at or below it with "Start here" (is-current), dims earlier steps (is-past) and explains the result ("Your date is 14 months away: perfect timing."). Dates must be after today and within three years.

Each step is a list item Group with the classes ffd-step--1 and ffd-from--12, which become data-step="1" and data-from="12" (the step's number and its threshold in months): change the number after ffd-from-- to move a threshold. The "Start here" badge is the step-badge span in each step's first line.

Questions#

Services & packages page (questions pattern). Each question is a Details block with the class faq: the question is its summary and the answer the blocks inside. They start closed and open and close on their own, as <details> elements do. freeframe_soiree_faq_icon() in inc/setup.php adds the "+" at the end of each question; it turns into a cross while the answer is open.

Header, reveals and back to top#

The mobile menu button (data-menu-toggle) uses aria-expanded and aria-controls, Esc closes the menu and returns focus, and it closes when the screen grows to desktop width. The header gets a soft shadow once the page scrolls. Blocks with the class reveal fade in on scroll (IntersectionObserver); a class such as [--d:80ms] delays one (the stylesheet has 60, 80, 120, 140, 160 and 220 ms), and everything shows at once with reduced motion. The back-to-top button is created by the last block of main.js and styled by the .back-to-top rules in src/theme.css; delete both to remove it.

Keeping the demo current#

Nothing dated goes stale. Everything a visitor reads as current is worked out from today in Charleston (timeZone in data.js):

Content Rule
"Now booking" years in the top line Next year and the year after (data-year-ahead)
Copyright year The current year (data-year), written by PHP and filled again by the script
Date limits on Process and Inquire From tomorrow to three years from today
The example date in error messages May 15 of next year

Journal articles, press quotes and the celebrations' dates in data.js are past content and keep their real dates.

Block styles and helper classes#

In the block settings' Styles panel:

Block Styles
Button Fill (default, the ink button), Line, Cream (on ink)

The class is-small on a Button block makes it the header's compact size. The arrow after a button's or a link's text is drawn with CSS (icon-after-arrow-right, from src/icons.css).

Blocks store classes, not other attributes, so a few classes stand for the HTML version's attributes:

Class Becomes
ffd-<name>--<value> data-<name>="<value>" (the steps, the status lines the script fills)
ffa-<name>--<value> role, tabindex or an aria-* attribute (ffa-aria-live--polite, ffa-aria-hidden--true)
ff-hidden the hidden attribute (the mobile menu, which the script opens)
ff-labelledby aria-labelledby pointing at the Group's first heading, written by freeframe_soiree_labelledby()
ff-dl the Group is written as a <dl> and the pairs inside it as <dt> and <dd> (the studio's figures on the home page), by freeframe_soiree_definition_list()

The first three are written as attributes by freeframe_soiree_block_attributes() in inc/setup.php when WordPress renders the block (the adapter at the top of main.js does the same for markup that didn't pass through it). Keep these classes when you edit those blocks.

Forms#

Inquiry form#

Inquire page (inquiry pattern, a Custom HTML block), code under "Inquiry form" in main.js. It validates when submitted, then live as the visitor corrects fields:

Field Rule
Your name Required
Email Required, name@domain.tld shape
Phone Optional; if filled, at least 10 digits
Type of event Required (wedding, corporate or private)
Event date A real date after today and within three years, in Charleston time; may be empty if "Our date is flexible" is checked
Guest count Required whole number from 10 to 500
Overall budget Required band
Message At least 20 characters (2,000 maximum, with a counter)

Errors appear under each field (aria-invalid and aria-describedby) and in an error summary that takes focus and links to each field. The form reads ?package=, ?guests= and ?type= from the URL (validated against the data), shows a note when it came from the estimator, and lists shortlisted venues as checked checkboxes. On success it shows a reference (IA- and four characters, made in the browser by makeRef()), the reply promise from the "What happens next" list and a summary of the inquiry.

Connecting a real backend#

The form doesn't send anything until you connect it, although its confirmation reads as if it had. With a service such as Formspree, add the endpoint to the form: open the Inquire page, select the form's Custom HTML block and change its first line:

html
<form class="grid gap-9" data-inquiry-form action="https://formspree.io/f/your-id" method="POST" novalidate>

Then, in assets/js/main.js (in a child theme), find the comment "Connect your form here" and send the data before showing the success block:

js
fetch(form.action, { method: 'POST', body: new FormData(form), headers: { Accept: 'application/json' } })
  .then(function (res) { if (!res.ok) throw new Error('Send failed'); /* show the success block */ })
  .catch(function () { /* show an error message and keep the form */ });

You can also replace the form's Custom HTML block with a form plugin's block; add the classes label, field and btn btn-ink to its labels, fields and button so it matches. The prefill from the estimator and the venue shortlist belong to the theme's own form.

The date checker on the process page and the venue filters are not form submissions and send nothing.

Saved data (localStorage)#

Key Shape Validation on read Reset
soiree-estimate { type, guests, season, pkg, addons: [] } Each value checked with an own-key lookup against eventTypes, seasons, packages and addons; guests rounded and clamped to 20–400; duplicate or unknown add-ons dropped; invalid JSON removed "Start over" on the estimator
soiree-shortlist ["venue-id", ...] Must be an array; unknown or duplicate ids are dropped and the cleaned list saved back Unsave venues, or localStorage.removeItem('soiree-shortlist')

These are the HTML version's keys. All storage goes through one safeStorage object in main.js. When the browser blocks localStorage (a sandboxed iframe or strict privacy settings), it uses an in-memory stand-in, so the estimator and shortlist still work for the rest of the page view. Values read from the URL are checked with own-key lookups too, so ?package=toString is ignored.

SEO and sharing#

Page titles come from WordPress: the page title, a middle dot and the site title (for example "Our process · Ivy & Ash Events"); the home page shows the site title and the tagline ("Ivy & Ash Events · Wedding and event planners in Charleston, SC", Settings > General). freeframe_soiree_title_separator() and freeframe_soiree_title_parts() in inc/setup.php set that shape. The theme doesn't output meta descriptions or Open Graph tags; use an SEO plugin such as Yoast SEO, Rank Math or The SEO Framework, and give it assets/img/og-image.png (or your own 1200 x 630 image) as the default social image. WordPress already generates a sitemap at /wp-sitemap.xml. Consider LocalBusiness structured data with your address and phone number; most SEO plugins can add it.

Accessibility#

Built in: a skip link to the main content (added by WordPress, styled by the theme), landmarks (header, labeled navigation, main, footer), one h1 per page and a logical heading order, sections labeled by their headings, visible focus rings (rose on light, champagne on ink), AA contrast for text, toggle buttons with aria-pressed, the menu button with aria-expanded, status text in polite live regions, a native modal <dialog> with focus return for the case studies, form fields with labels, hints and errors linked with aria-describedby, radio groups in fieldsets, tables that scroll inside a labeled, focusable region on small screens, and no scroll reveals, dialog animation or smooth scrolling with prefers-reduced-motion. The demo passes axe (WCAG 2.1 A and AA) in its checks.

When you edit: keep one Heading 1 per page, give images alt text (or leave it empty for decoration), label every field you add, and keep body text at the Muted color or darker on cream.

Building and deploying#

You only need this if you change the theme's files. The stylesheet assets/css/theme.css is compiled with Tailwind CSS from src/theme.css and the classes used in patterns/, parts/, templates/, inc/ and assets/js/:

sh
pnpm install
pnpm build   # compile assets/css/theme.css and assets/css/editor.css
pnpm watch   # recompile assets/css/theme.css on every change (run pnpm build before you commit)

Run pnpm build after adding a utility class to a pattern, template or the script's markup, otherwise the class has no style; keep each class name whole in the script (not built from pieces). Classes you type in the editor's Additional CSS class(es) field are only styled if the stylesheet already contains them.

To deploy, zip the theme folder (named freeframe-soiree, without node_modules/) and upload it in Appearance > Themes, or copy the folder to wp-content/themes/ on your server. Use HTTPS, and connect the inquiry form before you go live.

Translations#

The theme is translation-ready with the text domain freeframe-soiree. All text in patterns, templates and PHP goes through WordPress's translation functions; the script's labels, messages and sentences (validation errors, the menu button, status lines, the estimate summary) are translated in PHP (freeframe_soiree_script_strings() in inc/setup.php). Amounts and dates are formatted for US English in main.js (money() and longDate()); the studio's content in assets/js/data.js is edited there directly. Create a translation with Loco Translate, or with WP-CLI and Poedit:

sh
wp i18n make-pot wp-content/themes/freeframe-soiree wp-content/themes/freeframe-soiree/languages/freeframe-soiree.pot

Save freeframe-soiree-es_ES.mo (for example) in wp-content/languages/themes/ or in the theme's languages/ folder. Page content created by Soiree setup is copied into your pages in the site's language at that moment; translate it in the editor like any other content.

Child themes#

Use a child theme for changes you want to keep when Soiree is updated (your prices, venues and celebrations in particular). Create wp-content/themes/soiree-child/style.css:

css
/*
Theme Name: Soiree Child
Template: freeframe-soiree
*/

Templates, parts, patterns and theme.json in the child theme override the parent's files of the same name. To use your own data.js, replace the parent's data script (freeframe-soiree-data) under the same handle in the child's functions.php:

add_action( 'wp_enqueue_scripts', function () {
	wp_deregister_script( 'freeframe-soiree-data' );
	wp_register_script( 'freeframe-soiree-data', get_stylesheet_directory_uri() . '/data.js', array(), '1.0', array( 'in_footer' => true, 'strategy' => 'defer' ) );
}, 15 );

Do the same for assets/js/main.js (handle freeframe-soiree), keeping the inline window.freeframeSoiree strings and URLs. The parent's stylesheet only contains the classes the parent uses: if your child theme uses new utility classes, compile a stylesheet for the child (copy package.json and src/theme.css, point the @source lines at the child's folders) and enqueue it.

Troubleshooting#

  • The pages look unstyled or new classes do nothing. The stylesheet only contains classes it found when it was built. Run pnpm build after editing patterns, then reload.
  • "This block contains unexpected or invalid content". A pattern or page was edited by hand with markup that doesn't match the block. Click Attempt recovery, or re-insert the section from Patterns > Soiree.
  • The estimator keeps old choices. They're saved under soiree-estimate; press "Start over" or clear the site's storage.
  • A shortlisted venue disappeared after editing data.js. Saved ids that no longer exist in venues are dropped. Keep ids stable when renaming venues.
  • A date is rejected as "after today" near midnight. Dates use Charleston time (America/New_York). Change timeZone in data.js if your business is elsewhere.
  • "Send this with an inquiry" goes to the wrong page. The script links to /inquire/. If you renamed the page, change its URL in freeframe_soiree_page_urls() in inc/setup.php.
  • A menu link shows on the wrong side of the wordmark, or twice. Check the link's class in the menu (ff-nav-secondary for the right side, ff-mobile-only for the mobile menu only); see Navigation, header and footer.
  • The inquiry form says it's done but no email arrives. It sends nothing until connected; follow Connecting a real backend.
  • Portfolio or venue lists are empty. They are rendered by JavaScript from data.js; check the browser console for a syntax error after editing the data.
  • Soiree setup says the pages exist, but they are empty. It never overwrites existing pages. Delete (and empty the trash of) the pages with those slugs, or open each page and insert its page pattern from Patterns > Soiree pages.

License#

MIT, which is compatible with the GPL that WordPress requires. See LICENSE.txt in the theme folder.

The code and all included artwork are free for personal and commercial use.

Fonts: Playfair Display and Mulish are licensed under the SIL Open Font License 1.1 (OFL.txt in each folder of assets/fonts/).

Ivy & Ash Events, its people, clients, venues and publications are fictional placeholders.

Search documentation

Search the guides and every template's documentation