Freeframe

Documentation

Tally

v1.0.1Updated Nov 18, 2026A calm, trustworthy fintech SaaS website for invoicing and bookkeeping software, with a live invoice in the hero and a late-payment calculator.

Overview#

Tally is a marketing website template for a SaaS or fintech product: invoicing, expenses and simple bookkeeping software for freelancers and small studios. The fictional company is Tally Software, Inc., based on Ionia Avenue in Grand Rapids, Michigan, so prices are in US dollars, exclude sales tax, and the copy uses American spelling. Times are Eastern (America/Detroit). This is the Nuxt version: Nuxt 4, Vue 3 single-file components, TypeScript and Tailwind CSS v4, generated as a fully static site, with the same pages, design and interactions as the HTML version. This guide covers version 1.0.1. See the live demo at freeframe.dev/templates/tally.

Money and tax copy in the template is deliberately general ("not tax advice", no guaranteed savings). If you use it for a real product, have your own figures and claims checked.

The 6% sales tax in the hero invoice and the pricing toggle is a sample: it is Michigan’s state rate, but what is taxable varies by state and by item, and many services and hosted software aren’t taxed in Michigan. Set VAT_RATE and the wording to what applies to you. Some internal names (VAT_RATE, data-vat, data-vat-toggle, the saved vat value, #gdpr-title) keep their original spelling so they match the HTML version.

The site is a front end only: the forms don't send anything until you connect your own service (see Forms).

Quick start#

Requirements: Node.js 24 or newer and pnpm (npm works too).

sh
pnpm install
pnpm dev          # http://localhost:3000

Other scripts:

Script What it does
pnpm generate The static site in .output/public/
pnpm build A Node.js server build in .output/ (pages are still prerendered)
pnpm preview Serve the last build
pnpm lint ESLint
pnpm typecheck nuxt prepare and vue-tsc
pnpm build:demo Build for freeframe.dev under /demos/nuxt/tally into demo/

The fonts are bundled, so nothing loads from the internet.

Pages#

Route File Purpose and features
/ app/pages/index.vue Live invoice hero (edit quantities, simulate payment), customer wordmarks, three product cards, dark dashboard band with an SVG cash flow chart, set-up steps, testimonials, calculator and pricing teasers, call to action
/features app/pages/features.vue Product tour in ARIA tabs (invoicing, expenses, bookkeeping, reports), reminder email writer, grid of smaller features
/pricing app/pages/pricing.vue Monthly / annual switch, sales tax toggle, three plan cards, comparison table with a sticky header, billing and sales tax FAQ
/calculator app/pages/calculator.vue Late-charge calculator (interest from your terms plus a flat late fee) with an SVG chart, time-saved estimate
/integrations app/pages/integrations.vue Category filters, search, result count, empty state, bank feed notes, API code sample
/customers app/pages/customers.vue Featured story with before/after bars, six stories filterable by business type
/security app/pages/security.vue Key facts, six security practices, privacy notes, sub-processor table, responsible disclosure FAQ
/changelog app/pages/changelog.vue Updates filterable by type (new, improved, fixed)
/contact app/pages/contact.vue Validated demo request form, live office hours in Eastern time, next steps, address
404 app/error.vue A "reconciliation" card and links to the main pages (generated as 404.html)

Project structure#

tally/
  nuxt.config.ts            base path, <head> defaults, SITE_URL, the list of pages, Tailwind
  app/
    app.vue                 layout + page; keys the page so it can start over
    error.vue               the 404 page
    router.options.ts       query strings as written, and where the window scrolls after a link
    layouts/default.vue     skip link, header, the page, footer, live region, back-to-top button
    pages/                  one file per page (index.vue is the home page)
    components/
      SiteHeader.vue        sticky header, phone menu
      SiteFooter.vue        footer with the sign-up, link columns and the copyright year
      TallyLogo.vue         the tally mark and wordmark
      InvoiceDemo.vue       the hero invoice
      CountUp.vue           numbers that count up once
      ReminderWriter.vue    the reminder email preview
      BillingSwitch.vue     billing period buttons and the sales tax toggle
      PlanCards.vue         the three plan cards
      FilterPills.vue       filter buttons with counts
      FaqList.vue           questions and answers as <details>
      DemoForm.vue          the demo request form
      NewsletterForm.vue    the footer sign-up
      SuccessBox.vue        the confirmation that replaces a sent form
      OfficeHours.vue       live office hours on the contact page
      CheckIcon.vue         the check mark in plan lists, the table and the invoice
      BackToTop.vue         the back-to-top button
    composables/
      useTabs.ts            the product tour tabs
      usePricing.ts         billing period and sales tax state
      useCalculator.ts      both calculators and the chart
      useDirectory.ts       filters, search and counts
      useValidation.ts      inline form validation
      useDue.ts             the sample invoice's due date
      useCurrentPage.ts     aria-current for menu links
      usePageSeo.ts         title, description, canonical and Open Graph tags
    data/
      nav.ts                header, phone menu and footer links
      invoice.ts            hero invoice lines, limits, notes, the sample tax rate and INVOICE_DUE
      reminders.ts          reminder emails per tone and stage
      pricing.ts            plans, comparison table, billing FAQ
      calculator.ts         calculator rules, field ranges, lateClaim()
      integrations.ts       integration categories and the directory
      customers.ts          customer stories
      changelog.ts          product updates
      contact.ts            the demo form's choices and message length
      office.ts             office hours and time zone
      security.ts           LAST_TEST, the month of the last security test
    utils/
      format.ts             money(), num(), plural(), hasOwn()
      dates.ts              the rolling due date and test month
      safeStorage.ts        localStorage with an in-memory stand-in, saved data keys
      url.ts                reading and writing URL parameters
      announce.ts           announce() for the live region
    plugins/
      reveal.client.ts      scroll reveals
      same-page.client.ts   starts a page over when a link opens the page already showing
      keep-url.client.ts    keeps the query and #hash in the address as they were opened
      stable-build.server.ts  the same source always generates the same files
    assets/css/main.css     Tailwind entry: fonts, design tokens (@theme) and components
    assets/fonts/           the woff2 files and their license texts
  public/img/               favicon.svg, og-image.png and its source og-image.svg
  package.json              scripts and dependencies
  README.md                 short introduction
  DOCS.md                   this guide
  CHANGELOG.md              version history
  LICENSE.txt               MIT license

Components, composables, utilities and Vue's own functions are auto-imported, so files use money(), useTabs() or <PlanCards /> without an import line. Data files are imported by path (import { PLANS } from "~/data/pricing").

Customizing#

Brand and colors#

All design tokens are in the @theme block near the top of app/assets/css/main.css. The ones that matter most:

Token Default Used for
--color-paper #f7f6f1 Page background
--color-paper-2 #efede5 Alternate sections and table group rows
--color-line / --color-line-strong #dcd9ce / #c4c0b2 Hairlines, card and input borders
--color-ink #0d1f1b Text, primary buttons, dark bands and footer
--color-ink-soft / --color-ink-faint #3c4a45 / #59655f Secondary text and captions (AA on paper and white)
--color-fog #a9bab3 Secondary text on ink backgrounds
--color-mint-400 / --color-mint-500 #45d99b / #1fc786 The accent: fills with ink text on top, chart bars
--color-mint-700 / --color-mint-800 #0a6e4c / #08573d Accent text and links on light backgrounds
--color-amber-*, --color-rose-*, --color-sky-* Invoice status chips (due, late, sent)

To change the accent, edit the mint scale; the dev server picks it up at once:

css
--color-mint-400: #7cc4ff;  /* fills */
--color-mint-700: #1d5f99;  /* text on paper */

Keep the 700/800 shades dark enough for AA contrast on --color-paper. A few SVGs (the logo in app/components/TallyLogo.vue, the charts in the pages, public/img/favicon.svg, the social image) and the calculator chart in app/pages/calculator.vue use hex colors directly; search for #45d99b and #0d1f1b to update them too. theme-color is in nuxt.config.ts.

Typography#

Two fonts, self-hosted from app/assets/fonts/ and declared with @font-face at the top of app/assets/css/main.css:

  • Mona Sans (variable weight 300–800 and width 75–125%) for everything. Headings use font-stretch: 112% (set in main.css for h1–h3), and the whole body uses font-variant-numeric: tabular-nums so figures line up in invoices and tables.
  • Azeret Mono (weight 400–600) for small labels (.eyebrow, invoice numbers, chart axes).

Each family has a latin and a latin-ext file with its own unicode-range, and keeps its plain family name, so the CSS and the inline SVG text can say "Mona Sans" directly. To swap a font, replace the woff2 files, update the @font-face rules (font-family, src, font-weight), and change --font-sans or --font-mono in the @theme block. If the new family has no width axis, remove the font-stretch rules or they are simply ignored.

Content#

Page copy lives in the files under app/pages/. Lists and settings live in app/data/:

Where What it holds
app/utils/format.ts LOCALE and CURRENCY ("en-US", "USD"), used by money() to format every amount
app/data/invoice.ts VAT_RATE (0.06, the sample sales tax rate), INVOICE_LINES (name, price, starting quantity), INVOICE_DEMO (quantity limits 1–9, stage names, the notes under the invoice) and INVOICE_DUE, the due date of the sample invoice INV-0142 ("YYYY-MM-DD"). null (the default) is a rolling demo date: the Friday 7 to 13 days from today, so the demo invoice is never overdue
app/data/security.ts LAST_TEST, the month of the last independent security test on /security ("August 2026"). null (the default) is a rolling demo date: the most recent August that is over, so the yearly test never looks overdue
app/data/reminders.ts REMINDER_SAMPLE and REMINDER_TONES: the reminder emails per tone (friendly, neutral, firm) and stage (before, due, late), with the button labels in REMINDER_TONE_LABELS and REMINDER_STAGE_LABELS
app/data/pricing.ts PLANS (solo, studio, practice: name, monthly and annual prices in US dollars excluding sales tax, summary, feature list), BILLING_PERIODS, DEFAULT_BILLING, COMPARE (the comparison table) and PRICING_FAQ
app/data/calculator.ts LATE_PAYMENT (points added to the rate entered, days in a year, flat late-fee tiers), TIME_ASSUMPTIONS, CALC_FIELDS (default, minimum and maximum of every input) and CALC_URL_PARAMS
app/data/integrations.ts INTEGRATION_CATEGORIES (also the keys accepted from /integrations?category=) and INTEGRATIONS
app/data/customers.ts STORY_TYPES and STORIES
app/data/changelog.ts UPDATE_TYPES and UPDATES
app/data/contact.ts TEAM_SIZES, DEMO_TOPICS, CALL_TIMES and MESSAGE_MAX for the demo request form
app/data/office.ts OFFICE: timeZone: "America/Detroit", weekdays 1–5, 9 a.m. to 5:30 p.m.
app/data/nav.ts NAV, MOBILE_NAV and FOOTER_NAV
app/utils/safeStorage.ts STORAGE_KEYS (see Saved data)

Changing a price. Edit PLANS. Annual is ten months for twelve, so keep annual = monthly × 10 if you want the "2 months free" label and the FAQ to stay true:

ts
export const PLANS: Record<PlanKey, Plan> = {
  solo: { name: "Solo", monthly: 12, annual: 120, summary: "For freelancers working on their own.", features: [/* ... */] },
  // ...
};

The cards, the savings and the demo form's plan list all follow PLANS. The "from $10 a month" copy on the home page and the figures in the FAQ are plain text; change them to match.

Adding an integration. Add an entry to INTEGRATIONS; the counts on the filter buttons are worked out for you:

ts
{ name: "Kittiwake Pay", category: "payments", initials: "KP", color: "#1f4f86", builtByTally: false, description: "Card payments for clients in Canada." },

A new category is a new key in INTEGRATION_CATEGORIES (it becomes a filter button and an accepted ?category= value). Customer stories (STORIES) and changelog entries (UPDATES, newest first, each with its own date) work the same way.

Hero invoice lines. Edit INVOICE_LINES (unit price excluding sales tax, starting qty); totals are worked out from them. The "$5,766.40" in the reminder writer (REMINDER_SAMPLE.amount and the "Pay" button in ReminderWriter.vue) is plain text: update it if you change the lines.

Images and artwork#

There are no photos. The logo, customer wordmarks, integration tiles, avatars and charts are inline SVG, and the invoice, dashboard and receipts are HTML. If you replace an avatar with a photo, keep it square (40×40 on the home page, 56×56 on the contact page) and put the file in public/img/ (write its address with the base path: `${$config.app.baseURL}img/noelle.jpg`). The social image is public/img/og-image.png (1200×630), used by every page; its source is public/img/og-image.svg: edit the SVG and export a new PNG with any SVG editor. The favicon is public/img/favicon.svg.

app/components/SiteHeader.vue and SiteFooter.vue render the links in app/data/nav.ts. To add a page, create app/pages/<route>.vue (call usePageSeo() in it, and keep <main id="main"> as its root element), add the route to routes in nuxt.config.ts so it is generated, and add it to NAV (the desktop menu, six links), MOBILE_NAV (the phone menu, which adds Changelog) or FOOTER_NAV. The link to the current page gets aria-current="page" by itself in the header and the phone menu.

In the HTML version every link is a page load. app/plugins/same-page.client.ts keeps that behavior where it matters: a link to the page already showing (Pricing in the header while on /pricing, "Book a demo" after sending the form) scrolls to the top and starts the page over, so filters, tabs, the FAQ and sent forms reset and the page reads the address and saved data again. A link that only adds a #section to the address showing is a jump within the page and keeps its state.

Features#

Hero invoice demo#

app/components/InvoiceDemo.vue, on the home page (#invoice-demo). The minus and plus buttons change a line's quantity between INVOICE_DEMO.minQty and maxQty; the subtotal, sales tax (VAT_RATE, rounded to the cent) and total update and the total briefly flashes. Simulate payment moves the invoice from Viewed to Paid: the chip turns green, the progress track completes, a "Payment received" card appears and the quantities lock. The button then reads Reset demo. With the starting quantities the total is $5,766.40 ($5,440.00 + $326.40 sales tax). Changes are announced in a polite live region; the progress list marks the current stage with aria-current="step".

The "Due" date is a rolling demo date; see Rolling demo dates.

Product tour tabs#

app/composables/useTabs.ts, used in app/pages/features.vue: useTabs(panelIds) owns the selection and gives each tab button its aria-selected and tabindex; the panels are hidden with :hidden. Standard ARIA tabs: arrow keys, Home and End move between tabs. The panel ids are invoicing, expenses, books and reports (TOUR in features.vue), and the selected one is kept in the address, so /features#expenses opens that tab (only ids of the tab panels are accepted). The pill links at the top of the page (data-tab-link) select a tab and scroll to it. Without JavaScript every panel shows.

Reminder writer#

app/components/ReminderWriter.vue, at /features#reminders. Tone buttons (data-tone, aria-pressed) and stage radios (name="reminder-stage") choose one of the nine emails in REMINDER_TONES; {invoice}, {amount} and {client} are filled from REMINDER_SAMPLE, and {due} ("Friday, October 30") and {dueDay} ("Friday") from the sample invoice's due date, like the "Due" date on the hero invoice. The preview card is a polite live region.

Pricing switch and sales tax toggle#

app/composables/usePricing.ts holds the state: app/pages/pricing.vue starts it with providePricing(), and BillingSwitch.vue (the control in the hero) and PlanCards.vue (the three cards) share it with usePricing(). The billing buttons (data-billing) show either the monthly price or the annual price divided by twelve, with "Billed $300 yearly" or "Billed monthly" underneath. The saving is monthly × 12 − annual per plan: $24, $60 and $120 a year. The checkbox data-vat-toggle multiplies everything by 1 + VAT_RATE (Studio monthly becomes $31.80) and changes the tax note. Whole dollar amounts drop the cents (money(n, true)). The choice is saved (see below) and ?billing=monthly or ?billing=annual in the address overrides it; clicking a billing button updates the address. A status line announces the change to screen readers. The comparison table (COMPARE) has a header that is sticky below the site header.

Late-payment calculator#

app/composables/useCalculator.ts (used in app/pages/calculator.vue) with the rules in app/data/calculator.ts (lateClaim()). Inputs: amount ($1 to $1,000,000), days overdue (1 to 365, a slider) and the annual interest rate in your terms (0 to 36%). The US has no single late-payment rate for businesses, so the calculator uses what the visitor’s own terms say. The rules:

  • annual rate = rate entered + LATE_PAYMENT.margin (0 points);
  • interest = amount × annual rate ÷ 100 × days ÷ 365, rounded to the cent;
  • flat late fee (an example; set your own in LATE_PAYMENT.compensation) = $25 under $1,000, $50 from $1,000 to under $10,000, $100 from $10,000.

With the defaults ($2,400, 45 days, 12%) the result is $85.51: 12.00%, $35.51 interest, $0.79 a day, $50 late fee. /calculator?amount=12000&days=1 gives $103.95. The chart is inline SVG whose shapes are worked out in useCalculator() (calc.late.chart): the late fee as a flat band, interest on top, a marker at the chosen day, over 90 days or the next multiple of 30. Its text description (data-chart-desc) is rewritten each time. An out-of-range number marks its input aria-invalid and turns its hint red, and the figures keep using the field's last valid value, so they always match the slider and each other. When a change to the amount or the days is finished (on leaving the field or releasing the slider) the address follows, with the value the figures show, so the page can be shared as a link. Reset to the example restores the defaults, clears the saved values and removes the URL parameters. Change the default rate in CALC_FIELDS.rate.def (and the value of the field in calculator.vue) to match your own terms; state limits vary, so check them first.

Time-saved estimate#

The second form in app/pages/calculator.vue (calc.time in useCalculator()), at /calculator#time-saved. Minutes today = invoices × minutes per invoice + late invoices × chasing minutes. With Tally = invoices × TIME_ASSUMPTIONS.minutesPerInvoice + late invoices × chasing × (1 − chaseReduction). The defaults give 6.7 hours today, 1.3 hours with Tally and 5.4 hours saved, worth $322 at $60 an hour. Hours read "1 hour" or "2.5 hours". The four sliders are listed in SLIDERS in calculator.vue.

app/composables/useDirectory.ts, used on /integrations, /customers and /changelog. useDirectory({ items }) owns the filter and says which items show; FilterPills.vue renders the buttons (data-filter, aria-pressed, with counts), each entry is a data-integration item with data-category, and the count is a live "1 story" / "6 stories". The integrations page adds a search box (data-search, matches the words on the card), an empty state with Clear filters, and urlParam: "category", which reads ?category=banking (checked against INTEGRATION_CATEGORIES with an own-key check) and keeps the address in step with the buttons.

Rolling demo dates#

Two dates are worked out from today so the demo never looks out of date. Set either constant to show a fixed date on a real site:

Constant Shown in Rule while null Fixed value
INVOICE_DUE in app/data/invoice.ts The hero invoice (time[data-invoice-due]), {due} and {dueDay} in the reminder writer The Friday 7 to 13 days from today "2026-10-30"
LAST_TEST in app/data/security.ts Every [data-test-month] on /security (key facts and the first FAQ answer) The most recent August that is over: August of this year from September on, otherwise last year's "August 2026"
ts
export const INVOICE_DUE: string | null = "2026-10-30";

The pages are generated with the dates the template was written with (WRITTEN_DUE, WRITTEN_TEST); the browser works out the real ones when the page starts (useDue(), and lastTestMonth() in app/utils/dates.ts). The copyright year in the footer is always the current year. Changelog entries, customer figures and the survey year are history and keep their real dates.

Office hours#

app/components/OfficeHours.vue with officeState() and officeText() in app/data/office.ts. The time is worked out in OFFICE.timeZone (America/Detroit) whatever the visitor's time zone, and refreshed every minute. Inside Monday–Friday, 9 a.m. to 5:30 p.m., it reads "It’s 10:42 a.m. in Grand Rapids and we’re in the office"; outside, it says when the team replies ("after 9 a.m. this morning", "tomorrow" or "on Monday"). The generated page shows the plain hours until the browser knows the time.

Header, menu, reveals and back to top#

The header gains a shadow once you scroll. Below 1024px a menu button (aria-expanded, aria-controls) opens the phone menu; Esc closes it. Elements with .reveal fade in when scrolled into view (app/plugins/reveal.client.ts; off with reduced motion). Don't put .reveal on an element that also has a :class binding: Vue would drop the class that shows it. <CountUp :end="4200" /> counts up once. The back-to-top button is BackToTop.vue; remove its tag from app/layouts/default.vue and delete the .back-to-top styles to drop it.

Forms#

Two forms, both using useValidation() from app/composables/useValidation.ts: errors show under each field, linked with aria-describedby and aria-invalid, and focus moves to the first problem. After the first submit, fields are checked again as they are fixed.

Form Where Validates
Newsletter (data-form="newsletter") app/components/NewsletterForm.vue, footer of every page Email required and well formed
Demo request (data-form="demo") app/components/DemoForm.vue, /contact Name, work email, team size (radio group) and consent required; message up to 500 characters with a counter

A required field needs required and an id, takes :aria-invalid="v.invalid('its-id')" and :aria-describedby="v.describedBy('its-id')", and is followed by <p v-if="v.errors['its-id']" id="its-id-error" class="field-error">; data-label names it in the message ("Your name is required."). A radio group is a <fieldset data-required-group data-label="Team size" data-error-id="d-size">.

/contact?plan=studio (or solo, practice) preselects the plan; the plan buttons on the pricing page link there. On success each form is replaced by an in-world confirmation: the newsletter asks the visitor to look out for a confirmation email, and the demo request thanks them by first name, says Noelle will email times for a call (within two business hours, as the office-hours note promises) and shows a short reference (TA- and four characters, made in the browser by makeRef(); use your form service's own reference instead if it returns one). The forms send nothing until you connect them; if your reply times differ, change the message and the office-hours note together.

To connect a form service such as Formspree, change send() in DemoForm.vue, which the form calls once every field is valid (@submit="v.submit($event, send)"):

ts
async function send(form: HTMLFormElement) {
  const data = new FormData(form);
  const res = await fetch("https://formspree.io/f/your-id", {
    method: "POST",
    body: data,
    headers: { Accept: "application/json" },
  });
  if (!res.ok) return; // show an error message here, for example in [data-form-status]
  const planKey = String(data.get("plan") || "");
  const topics = data.getAll("topics").length;
  sent.value = {
    first: String(data.get("name") || "").trim().split(/\s+/)[0]!,
    about: (hasOwn(PLANS, planKey) ? " about the " + PLANS[planKey as PlanKey].name + " plan" : "") + (topics ? " covering the " + plural(topics, "topic", "topics") + " you picked" : ""),
    reference: makeRef("TA"),
  };
}

Every field has a name, so FormData includes it. The newsletter works the same way in NewsletterForm.vue (replace done.value = true in its send()). If you deploy the Node.js server build instead of the static site (see Building and deploying), you can post to a server route of your own instead (server/api/demo.post.ts with export default defineEventHandler(...)).

Saved data (localStorage)#

All access goes through safeStorage in app/utils/safeStorage.ts: localStorage when available, an in-memory stand-in when the browser blocks it (sandboxed iframes, strict privacy settings) or it is full, so features keep working for the visit. store in the same file reads and writes JSON on top of it.

Key Shape Validation on read
tally:pricing { "billing": "annual", "vat": false } billing must be an own key of BILLING_PERIODS, vat a boolean; anything else falls back to annual without sales tax
tally:calculator { "amount": 2400, "days": 45, "rate": 12, "invoices": 12, "minutes": 20, "late": 30, "chase": 45, "hourly": 60 } Each field must be an own key of CALC_FIELDS and a number within its range; invalid fields keep their defaults

URL parameters win over saved values: /pricing?billing=, /calculator?amount=&days=. Other URL parameters are /integrations?category= and /contact?plan=; every one is checked with Object.prototype.hasOwnProperty.call(...) (hasOwn() in app/utils/format.ts) or a range check, so values like ?plan=constructor are ignored. The generated pages show the defaults; saved values and the address apply once the page is running in the browser (in onMounted()).

To reset, use Reset to the example on the calculator, or run localStorage.removeItem('tally:pricing') in the browser console. To stop saving, remove the store.set(...) calls in usePricing.ts and useCalculator.ts.

SEO and sharing#

Each page sets its title and description with usePageSeo() from app/composables/usePageSeo.ts, which also writes the Open Graph tags, the canonical link and <body data-page>; lang="en-US", theme-color and the favicon are set in nuxt.config.ts. The social image is public/img/og-image.png; set SITE_URL when building so its URL and the canonical links are absolute (runtimeConfig.public.siteUrl in nuxt.config.ts):

sh
SITE_URL=https://www.tally.example pnpm generate

Add public/robots.txt and a sitemap if you want them (a static public/sitemap.xml, or the @nuxtjs/sitemap module), and set 404.html as your host's not-found page. There is no structured data; SoftwareApplication with offers is a good fit for a product like this.

Accessibility#

  • Skip link, landmarks (header, nav with labels, main, footer), one <h1> per page and a logical heading order.
  • Visible focus outlines in the accent color, AA contrast on every surface, prefers-reduced-motion respected (reveals, chart animation, count-up and smooth scrolling are off).
  • ARIA patterns: tabs, pressed buttons for filters and billing, aria-current for navigation and invoice stage, live regions for totals, counts, calculator results and the pricing status.
  • Charts have text alternatives (aria-label or a <desc> that is updated with the numbers); tables have captions and header scopes.
  • A sent form is replaced by a role="status" box that takes focus.

When editing, keep one <h1> per page, give new inputs a <label>, and make sure every aria-controls, aria-labelledby and aria-describedby points at an id that exists.

Building and deploying#

sh
pnpm generate     # static site in .output/public/
pnpm preview      # serve it locally

nuxt.config.ts lists every page in routes, which nuxt generate writes as pricing.html, contact.html and so on, plus 404.html; add new pages there. Deploy .output/public/ to any static host (Netlify, Cloudflare Pages, GitHub Pages, S3) with URLs without .html ("clean URLs" or "pretty URLs" on most hosts), or import the repository into Vercel or Netlify, which detect Nuxt. For a sub-folder, build with the base path: DEMO_BASE_PATH=/tally pnpm generate. demo/ is the freeframe.dev demo build and can be deleted. To use server features (server routes under server/), run pnpm build and deploy .output/ to a Node.js host or a platform that runs Nuxt.

Troubleshooting#

  • Prices or the calculator don't remember choices. The browser is blocking storage (private mode or a sandboxed preview), so choices last only for the visit. That's expected.
  • A shared pricing link opens on the wrong period. ?billing= overrides the saved choice; remove it from the link.
  • The page shows the example for a moment before my saved numbers. The generated page is built with the defaults; saved values and URL parameters apply when the page starts in the browser.
  • The office hours text looks wrong. It uses Eastern time (OFFICE.timeZone); change the time zone and hours in app/data/office.ts for another location.
  • A Tailwind class written in a template string has no effect. Keep class names as whole strings (open ? 'hidden h-5 w-5' : 'h-5 w-5'); Tailwind can't find a class glued to a ${...} expression.
  • A form shows its confirmation but nothing arrives. It sends nothing until you connect it; see Forms.
  • Fonts fall back to the system font. Check that app/assets/fonts/ still has the woff2 files named in the @font-face rules of app/assets/css/main.css.
  • Links or the social image break under a sub-folder. Build with DEMO_BASE_PATH set to that folder, and SITE_URL set to your domain.
  • pnpm lint or pnpm typecheck can't find .nuxt/. Run pnpm install first; it runs nuxt prepare, which writes the generated types and the ESLint config.
  • A new page works in pnpm dev but is missing from the generated site. Add its route to routes in nuxt.config.ts.

License#

MIT. The code and all included artwork (logo, wordmarks, integration tiles, avatars, charts, mock-ups and social image) are free for personal and commercial use; see LICENSE.txt in the download.

Mona Sans and Azeret Mono are licensed under the SIL Open Font License (see app/assets/fonts/).

Tally, Tally Software, Inc. and every business, person and integration named in the template are fictional placeholders.

Search documentation

Search the guides and every template's documentation