04 / 15 · Content & conversion links

Content and conversion links

Start with src/config/site.ts. It is the single entry point for shared product branding, logo paths, accent colors, product media, feature/gallery settings, testimonial identities, prices, social links, CTA destinations and newsletter configuration. sections.ts and preview.ts define types; you do not edit them for ordinary customization.

Visible text stays in two clearly named files: src/content/primary.ts and src/content/secondary.ts. This avoids duplicating shared prices or URLs and keeps both language versions readable. Choose the pair in Languages, customize assets in Appearance, and connect signup in Email signup and Kit.

Examples below edit fields inside existing objects, not entire files. Preserve neighboring settings, commas, quotation marks and type checks. Make one change, save and inspect both language pages before continuing.

A complete branding pass

In siteSettings, change:

name: 'Orbit',

Configure brand.logo, brand.colors.light and .dark, brand.favicon and brand.socialImage in this same file. Put your own assets in public/; /logo.svg refers to public/logo.svg. See Appearance for exact logo and color examples.

In both content files, replace the top-level metadata and the hero copy. For example, inside primaryContent:

title: '{name} — a clearer way to launch',
description: 'Bring your product story, features and next steps into one clear place.',

Inside its existing hero object:

badge: 'Built for your next launch.',
title: 'Give your product',
emphasis: 'a clearer introduction.',
description: 'Show what matters and help visitors take the next step.',
note: 'Explore the product overview below.',

Expected result: both pages use Orbit wherever {name} inserts the shared name. The primary page has the new browser title and headline; its title and emphasis combine into one main heading. Edit the secondary translation separately. Literal references to an old name must be replaced yourself.

Complete the pass by updating all section, footer, demo-access dialog, newsletter and preview copy in both languages, replacing sample media/testimonials and setting the real public origin before building. A product name alone does not replace every claim or image.

Shared destinations and translated labels

Each action is either a normal link or the optional getting-started dialog:

{ kind: 'link', href: 'https://app.your-domain.example/signup' }

For the optional getting-started dialog, use { kind: 'demo' }.

kind: 'link' normally navigates to its configured destination. kind: 'demo' opens the independent name/email demo-access scenario described below. Exact #newsletter CTA/navigation links open newsletter signup when an enabled newsletter has placement: 'dialog'; they scroll to the section with placement: 'section'. Newsletter placement does not change a demo action. Its separate preview mode shows an explicitly labelled local confirmation, sends nothing and creates no subscription. See Email signup and Kit for real collection.

LocationDestination in siteSettingsLabel in each content file
Header and mobile-menu CTAheaderActionheader.actionLabel
Main heroheroPrimaryActionhero.primaryActionLabel
Secondary heroheroSecondaryActionhero.secondaryActionLabel
Pricing plansections.pricing.plans[].actionsections.pricing.plans[].actionLabel
Optional yearly plan actionsections.pricing.plans[].annualActionsections.pricing.plans[].annualActionLabel
Final CTAsections.cta.actionsections.cta.actionLabel
Demo confirmation linkdialogActiondialog.actionLabel

The supplied header uses { kind: 'demo' }. Its destination and label are shared with the CTA at the bottom of the mobile menu; edit headerAction and header.actionLabel once for both. Hero links target #product and #workflow; pricing and final signup links target #newsletter, which remains non-collecting until configured. To make the header open newsletter signup in dialog placement, deliberately set headerAction: { kind: 'link', href: '#newsletter' }. Other destinations, including monthly/yearly checkout links, remain independent; review them all before launch.

Get started demo-access scenario

The supplied header opens a small, theme-matched popup with name and email fields. The default demoAccess.mode: 'preview' demonstrates a local access flow; it creates no account, subscription or protected demo. The product preview remains directly accessible on the page. An optional Kit connection for this same Forma-styled popup is described below; it still does not provide authentication.

Try a sample name and you@example.com. Both fields are required; a name containing only spaces and an empty or invalid email must not continue. Valid input clears the fields and shows an explicitly labelled demo confirmation. Its link uses siteSettings.dialogAction, supplied as:

dialogAction: { kind: 'link', href: '#product' },

Use a normal link to your chosen section, real demo URL or existing route. Keep dialogAction as kind: 'link', rather than reopening the same popup. Change labels, validation, notices, confirmation and link text under dialog in both content files. Preserve the supplied non-collecting explanation for preview mode; the separate kitFormNote and kitSuccessDescription describe optional real mailing-list collection. Rebuild after editing.

Invalid input shows theme-matched inline wording from dialog.nameError and dialog.emailError. The first invalid field receives focus after its message is available, and the message clears when that field is corrected. Email validity follows the browser's type="email" rules; the name also rejects spaces-only input. Keep these error strings in both dictionaries when replacing a language.

The form mounts only after opening the popup. In the default preview mode, it uses no network submission, saves/transmits no name or email and has no marketing checkbox. Closing with the close control, Escape or backdrop resets its fields and confirmation. Valid input moves focus to the confirmation heading; closing returns it to the opening control, or the menu button when opened from the mobile menu. Without JavaScript the popup cannot open. If Kit mode is configured, only selecting the separate marketing choice submits to Kit; closing cannot cancel a request already sent.

For a real account-registration or protected-demo service, link to your own implementation. Changing text or adding Kit does not create authentication. Newsletter signup can also use the shared popup as a separate purpose; choose its #newsletter action deliberately, as shown below.

Get started without the popup

A popup is not required. Set headerAction to a normal link:

headerAction: {
  kind: 'link',
  href: 'https://app.your-domain.example/signup',
},

Then edit header.actionLabel in both dictionaries, for example Start your trial and its translation. Set other signup actions independently to your own service. To use a newsletter page section without a popup, keep newsletter.placement: 'section' and use #newsletter after configuring real signup.

Expected result: the header navigates directly to your destination in both languages without opening a dialog. Restore headerAction: { kind: 'demo' } for demo access, independently of newsletter placement. Configure its continuation through dialogAction as a normal link.

Kit signup in the Get started popup

Choose between two different flows. Both are optional, and neither adds authentication or an affiliate link to the popup.

Demo access with optional mailing-list signup: keep headerAction: { kind: 'demo' } and follow the complete demo-access Kit configuration. Set demoAccess.mode: 'kit' with your published public Form values and numeric metadata in both language slots. Use a separate Form from any active newsletter Kit Form. The popup retains Forma's name/email fields and Access the demo action, adding an initially unchecked, optional marketing choice. Unchecked continues without a Kit signup request. Checked sends name/email and the permission tag in the background, while the public demo continuation remains available independently. Set newsletter.privacyPolicyHref to your actual policy. Translate dialog.kitFormNote, kitSuccessDescription and the newsletter consent/status text in both dictionaries. A received request is not confirmation of subscription.

Newsletter signup instead of a demo-access action: configure the existing newsletter for the presentation you want:

mode: 'kit-native', // Forma fields; use 'kit' for the Kit-designed embedded Form.
placement: 'dialog',

Preserve the other newsletter settings and supply the public values required by the chosen mode; the copy-and-paste examples show the complete shape. Then set the header's shared action explicitly:

headerAction: { kind: 'link', href: '#newsletter' },

Use newsletter.eyebrow, title, description and closeLabel in both languages for the signup popup. It collects only newsletter permission and has no demo continuation. Native mode shows Forma's email/required-checkbox fields immediately and loads Kit only on a valid consented submission. Embedded mode loads the actual Kit Form automatically on opening; set kitLoad: 'interaction' if a separate Load signup form step is wanted. Kit-designed fields and confirmation remain configured in Kit.

Newsletter content stays mounted when that popup closes and reopens in the same page visit. Opening demo access in the shared dialog replaces it and resets that newsletter instance. Refreshing, leaving or changing language also resets the interface. No newsletter entries are saved by Forma to browser storage, and closing cannot unload provider code, revoke its storage or unsubscribe an address. Use placement: 'section' to show newsletter signup on the page; a kind: 'demo' action always remains independent. Rebuild and test both purposes after changes.

CTA destinations can be a nonempty section anchor (#pricing), root-relative path (/contact/), absolute HTTP/HTTPS URL, or mailto: address. Root-relative paths need real routes on your host; Forma does not generate a contact, checkout or privacy page. They are not automatically prefixed with the current language.

The helper rejects unsafe or malformed destinations such as javascript:, data:, file:, bare relative paths, protocol-relative // URLs, embedded credentials, literal whitespace and backslashes. Encode spaces in email-link parameters; do not disable validation to work around an error.

Links use the current tab. Add newTab: true only when needed; runtime links receive the translated new-tab notice and noopener noreferrer. Shared URLs are identical across languages. Separate translated checkout destinations require a deliberate integration.

Footer social links are in siteSettings.socialLinks:

socialLinks: [
  { label: 'LinkedIn', href: 'https://www.linkedin.com/company/your-company/', newTab: true },
  { label: 'Contact', href: 'mailto:hello@your-domain.example' },
],

Replace every example with a working destination. An empty array hides the social-link group. Keep labels clear for keyboard/screen-reader users.

The demo's See how it works link uses #workflow. You may point it to a real public documentation URL or an existing route on your own host. Offline buyer guides are not automatically deployed as public pages; a link to a nonexistent /docs/ route will not work.

Edit numeric prices, currency and plan destinations in siteSettings.sections.pricing. Currency formatting uses the active language's formatLocale in languages.ts. For example:

currency: 'EUR',

For a plan, edit its existing shared entry:

{
  monthlyPrice: 16,
  annualMonthlyPrice: 12,
  perSeat: true,
  featured: true,
  action: { kind: 'link', href: 'https://checkout.your-domain.example/pro-monthly' },
  annualAction: { kind: 'link', href: 'https://checkout.your-domain.example/pro-yearly' },
},

The matching plan in each content file supplies its translated copy:

{
  name: 'Pro',
  description: 'For growing teams.',
  actionLabel: 'Choose Pro',
  annualActionLabel: 'Choose Pro yearly',
  features: ['Shared projects', 'Team tools', 'Priority support'],
},

Expected result: Monthly shows 16 EUR per seat/month; Yearly shows an effective 12 EUR per seat/month and a 144 EUR annual total. The yearly button uses annualAction. Without it, both periods use action; Forma does not add a billing-period parameter automatically.

annualMonthlyPrice is the effective monthly price, not the annual total; the component multiplies it by 12. perSeat: false describes a whole-plan price. featured highlights a plan. Zero prices use the free-plan presentation. Keep shared and translated plans in matching count/order.

The buttons can lead to your own checkout, your existing application's signup/billing flow, or an external marketplace checkout, such as a Lemon Squeezy product checkout. Paste the real URL supplied by that service. Forma does not create a checkout, process payments, calculate taxes, manage subscriptions or synchronize displayed prices with a provider. If building your own checkout, that is a separate backend/payment integration.

Preserve {total} and {seat} in sections.pricing.annualBillingLabel. The supplied FAQ may refer to {proAnnual} and {businessAnnual} for the second and third sample plan totals. Replace those examples if your plan structure changes. Savings claims, free-form price mentions, checkout charges and local displayed prices must agree; they are not automatically synchronized.

Update sections.pricing.footnote, the final CTA note and relevant FAQ answers in both dictionaries. Test every plan button in both billing periods. Publish promises only when the connected product or service actually provides them.

Product screenshots and video

The product preview uses siteSettings.preview; captions, alternative text and labels use preview in each dictionary. The supplied video and images illustrate a fictional product. The displayed WebP files have editable SVG originals alongside them in public/product/. Replacing configured media does not require editing the component.

Video mode is the supplied default. To show the screenshot gallery instead, change only the existing preview.mode value to 'images' in siteSettings, keep the shared images entries and their matching translations, then rebuild. Restore 'video' to show the configured clip again. These are alternative presentations of the same product section; they do not mount two players at once.

The supplied preview.video settings are:

video: {
  frameStyle: 'window',
  src: '/product/demo.mp4',
  poster: '/product/overview.webp',
  width: 1280,
  height: 720,
  captionsSrc: '/product/demo.vtt',
  captionsLanguage: 'en',
  captionsLabel: 'English',
},

public/product/demo.mp4 is an original silent H.264 MP4, approximately 11.9 seconds, 1280 × 720 (16:9) and 881,685 bytes. It shows three fictional product views with gentle crossfades and no zoom or pan, not a working SaaS application. All three supplied screenshot WebPs and their editable SVG originals use the same 16:9 canvas. The poster is overview.webp, a 30,848-byte compressed copy of overview.svg. The clip has no audio track, so its sound controls do not produce audible sound. Its three descriptive WebVTT cues are English and remain English on both supplied page languages; review or replace this shared track for your audience. Your own authorized clip may include audio, with appropriate captions/descriptive alternatives and target-browser checks.

Choose the video frame style.

In the existing video object in src/config/site.ts, set frameStyle: 'window' to keep the decorative browser header and bottom descriptive caption bar. Set frameStyle: 'minimal' to remove the header's three dots, product name/top label and the bottom descriptive text bar, then rebuild. Both options keep the same rounded outer frame, outline, ring and shadow, with the existing responsive sizing and playback controls. Omitting frameStyle has the same effect as 'window', so existing configurations continue to look the same. Use one of these quoted values.

With frameStyle: 'minimal', the descriptive videoCaption stays available to screen readers but its bottom bar is not visible. The separate sample-media disclaimer below the preview remains visible. Playback controls, loaded video-track captions, keyboard access and native/error fallback remain available; an actual playback-error message still appears on failure. The setting does not remove or crop a border already included in your video or poster file, and it does not change image-gallery mode. Review both themes and phone widths against your own media; see Appearance.

For one screenshot entry:

{
  id: 'overview',
  src: '/product/my-overview.webp',
  darkSrc: '/product/my-overview-dark.webp',
  width: 1280,
  height: 720,
},

Place those files in public/product/. darkSrc is optional; omit it when one asset works in both themes. In each content file, replace the entry at the same position:

{ alt: 'Product overview showing the main controls', caption: 'Product overview' },

Add or remove matching image entries in all three locations: shared settings, primary text and secondary text. Use a stable unique id for each shared image. With multiple images, the preview offers thumbnails and previous/next controls; it does not autoplay screenshots. One image hides the gallery controls.

The first image's width/height reserves the stage ratio. Other images fit inside it without being stretched. Prefer a consistent image ratio and dimensions that describe the actual asset. Resize and compress screenshots before adding them; WebP is a useful default, and SVG remains supported. Static hosting supplies no server image optimizer. See Appearance.

The displayed screenshot loads eagerly with high priority. The landing document also preloads the first configured screenshot when it has no darkSrc; in video mode it preloads the configured poster instead. These paths follow the shared settings automatically. Later feature/workflow images and gallery thumbnails remain lazy-loaded. Keep the first image or poster lightweight, and verify your replacement files in the production network panel.

To replace the local clip, keep preview.mode: 'video' and edit the existing video setting. For example:

mode: 'video',
video: {
  frameStyle: 'minimal',
  src: '/product/product-tour.mp4',
  poster: '/product/product-tour-poster.webp',
  width: 1280,
  height: 720,
  captionsSrc: '/product/product-tour-en.vtt',
  captionsLanguage: 'en',
  captionsLabel: 'English captions',
},

Put those files in public/product/, and edit preview.videoCaption/videoLabel in both dictionaries. The example paths are replacements, not supplied files. Keep the shared image entries and their translations for a later switch back to image mode. Video uses inline playback, does not autoplay and uses preload="none"; optimize the poster as well as the clip. Provide appropriate captions and audio/video alternatives. The optional WebVTT track is shared configuration, so review its language for both audiences; switching the page language does not translate a video or its track.

Replace the sample track when it no longer describes your clip. If your video has no configured track, remove captionsSrc, captionsLanguage and captionsLabel together from the shared video object; do not leave the sample demo.vtt attached to unrelated media. The captions button then stays absent. This configuration choice does not supply an accessible alternative by itself; provide appropriate captions/descriptions for your actual content before publishing.

Once the page is interactive, click or tap the video itself to play or pause. Keyboard users can focus the video surface with Tab and press Enter or Space; focus stays on that control so it can pause playback too. A violet Play or Pause icon briefly confirms the change, then disappears. The icon does not prevent another click or tap. The centered Play affordance returns when paused. At widths of 600 px or less, it hides while the floating bar is visible so you can use that bar's Play button, then returns when the paused bar hides; brief feedback appears above the bar.

A theme-matched control bar floats inside the video's lower edge. Visitors can reveal it with a mouse, touch or keyboard:

  • Mouse or pen: entering or moving over the video reveals the bar. In the page, hovering keeps it visible while paused or ended; leaving hides it even when stopped. During in-page playback, it also fades after about three seconds of inactivity. In fullscreen, it fades after about two seconds of inactivity whether playing, paused or ended, even if the pointer remains over the video. Clicking a control alone does not keep it visible indefinitely.
  • Touch: tapping the video toggles playback and reveals the bar for about three seconds in the page, or two seconds in fullscreen. Lifting a finger does not hide it immediately, and swiping across the video surface does not open it. Holding or dragging a control keeps the bar visible; releasing or cancelling the interaction restarts its normal visibility behavior.
  • Keyboard: use Tab to reach the controls and Enter or Space to activate a button. Keyboard focus keeps the bar visible.

Entering fullscreen reveals the bar and starts its two-second idle timer. Mouse/pen movement, a tap or finishing a held control interaction restarts that timer. Returning to the page restores the in-page behavior above. These timings apply to Forma's enhanced controls; browser-native fallback controls follow the browser's own behavior.

The bar includes Play/Pause, seeking, elapsed/total time and mute, plus a volume slider above phone widths. At 600 px and below, seeking and elapsed/total time share the 24 px-high first row. The available 44 px control buttons stay grouped at the start of the second row with 8 px gaps, rather than spreading across the bar. An absent captions or fullscreen button leaves no reserved empty slot. The volume slider is hidden; phone sound levels may be controlled by the device. Review the bar at 320 px with both loaded captions and supported fullscreen so all available buttons fit without creating extra rows.

A captions button appears only after a configured track loads successfully. Where supported by the browser, automatically positioned bottom captions move above the visible bar and return to their original placement when it hides. Explicit positions authored in your WebVTT file are preserved. Review your own captions with the bar visible and hidden, especially on phones and in fullscreen; browser positioning and caption preferences vary. Fullscreen appears when the browser supports the standard Fullscreen API; a denied request leaves playback in the page. There is no duplicate Play/Pause button beside the caption.

On playback failure, the translated error appears below the player and native controls return. The custom bar moves below the video, leaving native controls unobstructed, with its Play button available to retry. If focus was on the enhanced video surface, it moves to that retry control. Before the JavaScript enhancement is ready, and when JavaScript is unavailable, the video retains native controls. Browser-native controls and supported media formats vary by browser; no external player library is required. Theme colors, brief playback feedback and the lightweight playback glow are described in Appearance.

Translate these fields inside preview in both content files:

FieldPurpose
videoCaption, videoLabelDescriptive caption and accessible video description.
videoPlayLabel, videoPauseLabel, videoErrorLabelPlayback controls and failure message.
videoControlsLabel, videoSeekLabelControl group and seek slider.
videoMuteLabel, videoUnmuteLabel, videoVolumeLabelSound controls.
videoCaptionsLabelCaptions toggle, with its pressed state indicating visibility.
videoFullscreenLabel, videoExitFullscreenLabelEnter/exit fullscreen controls where supported.

Use Tab to reach the video surface, buttons and sliders, Enter or Space to activate a focused button, and the range input's arrow keys to seek or change volume. Seek becomes available after media duration is known. Test Play and Pause from both the video surface and bottom bar, brief feedback, keyboard focus, seeking and replay after the video ends, plus your actual sound, track and fullscreen behavior in target browsers, both themes and language pages. If playback fails, check that the video URL exists in the built export and that the browser supports its format. The Launch checklist includes error and native-control fallback checks.

The image panels use siteSettings.sections.workflow.steps for media and sections.workflow.steps in both content files for captions. Their text/images are configurable, without nested fake task cards. The grid uses three columns on a wide screen, two on tablets and one on phones.

Screenshots have a subtle alternating static tilt inside centered, padded panels; the colored panels and captions remain level. The tilt is smaller on phones, and images fit without cropping. This is styling rather than an extra media setting. Appearance identifies the stylesheet rules and how to use level screenshots instead. You still replace an image through configuration and its local asset path.

To add three more panels below the supplied three:

  1. Add your three optimized image files to public/product/.
  2. Append these three entries to the existing shared steps array, after its current third entry:
{ id: 'integrate', image: { src: '/product/integrate.webp', width: 1280, height: 720 } },
{ id: 'measure', image: { src: '/product/measure.webp', width: 1280, height: 720 } },
{ id: 'improve', image: { src: '/product/improve.webp', width: 1280, height: 720 } },
  1. Append matching text to sections.workflow.steps in both dictionaries, translating the secondary entries:
{ title: 'Connect your tools', description: 'Bring useful services into your workflow.', imageAlt: 'Product integration screen' },
{ title: 'Review the results', description: 'See the information that matters to your team.', imageAlt: 'Product reporting screen' },
{ title: 'Keep improving', description: 'Use what you learn to shape the next step.', imageAlt: 'Product improvement screen' },
  1. Run npm run format and npm run check, then review phone/tablet/desktop widths in both themes and languages.

Expected result: six panels appear in shared array order, with a second three-panel row on wide screens. No component or CSS change is needed. The example filenames must exist and the example claims must describe your own product. Each panel supports an optional image.darkSrc too.

General feature cards

Shared cards are in siteSettings.sections.features.cards; text is in each dictionary's sections.features.cards. Add or remove matching entries in these three places. Cards flow through the responsive grid rather than requiring exactly four fixed illustrations.

For a text-focused shared card:

{ id: 'exports', icon: 'arrow' },

Its matching translated entry can be:

{
  title: 'Take your work with you',
  description: 'Export the information you need in a useful format.',
  bullets: ['Easy-to-read exports', 'A clear handover', 'Your own workflow'],
},

Supported icon names are check, arrow, spark, shield, link and plus. An optional shared image: { src, darkSrc?, width, height } adds an image; supply its meaningful imageAlt in both translated cards. Omit image/bullets when unnecessary. The card remains a presentation of your features, not an implemented integration or a product capability.

To turn an existing image card into a text-only card, remove that card's image property from the shared settings. Remove its now-unused imageAlt from both translated entries, then edit the title, description and optional bullets. Its image frame disappears automatically; the surrounding card keeps the same design. You can also keep an image alongside the text and bullets.

To add more cards of either type, append entries to the existing shared cards array. For example, append one text card and one image card:

{ id: 'handover', icon: 'check' },
{
  id: 'insights',
  icon: 'spark',
  image: { src: '/product/insights.webp', width: 1280, height: 720 },
},

Append their matching entries to sections.features.cards in both dictionaries, translating the secondary copy:

{
  title: 'A clearer handover',
  description: 'Keep useful context close to the work.',
  bullets: ['Clear next steps', 'Useful notes'],
},
{
  title: 'See the useful details',
  description: 'Show the information your audience needs.',
  imageAlt: 'Your product insights screen',
},

Add your actual optimized insights.webp file to public/product/. Preserve matching card count and order across the shared array and both dictionaries, and give each shared card a unique id. Expected result: both new cards appear after the existing cards, with extra grid rows added automatically. You can repeat this pattern for more text, image or combined cards without changing the component or CSS. Run npm run format and npm run check, then inspect both languages at phone, tablet and desktop widths.

Testimonials and autoplay

Shared identities/settings are in siteSettings.sections.story. Quotes and roles are in each dictionary's sections.story.testimonials. Add or remove entries in all three matching arrays:

{ id: 'customer-one', name: 'Approved customer name', initials: 'AC', avatarSrc: '/customers/customer-one.webp' },
{ quote: 'An approved quotation about your actual product.', role: 'Customer role or company' },

avatarSrc is optional; otherwise initials are shown. Use an authorized image and quotation. Keep sampleLabel and note explicit while using sample quotes; replace them with accurate headings/context only when you publish genuine approved testimonials.

With multiple testimonials, previous/next controls and a pause/play control are available. autoplay: true and intervalMs: 7000 are the supplied settings. Use an interval of at least 5000 milliseconds; smaller values fail configuration validation. Set autoplay: false to start with automatic rotation off; visitors can use Play when reduced motion is not enabled. Hover, keyboard focus and a hidden browser tab pause it; reduced-motion preferences disable autoplay. Manual navigation stops rotation until Play is selected. A single testimonial hides the controls; an empty matching collection hides the section. The layout reserves the tallest quote's height to reduce shifts; keep quotes reasonably concise and test your actual translations.

Edit FAQ items in sections.faq.items in both dictionaries. Add matching translated items and retain truthful answers. Other visible UI copy includes ui, appearance, dialog, newsletter, notFound, footer, cookies and languageSwitcher. Keep required keys/placeholders; Languages explains their validation.

Edit shared section destinations in siteSettings.navigation in src/config/site.ts and their labels in the top-level navigation arrays in both content dictionaries. Keep the same entry count and order in all three arrays; the header, mobile menu and footer share these entries. A count mismatch fails validation. Footer FAQ uses footer.faqLabel; the preference button uses cookies.settingsLabel. Keep anchors pointed at real sections, and retain the preference button while the manager is enabled so visitors can change their choice.

Whole footer links can wrap to another row; do not insert manual line breaks for one width. Review both languages on phone, tablet and desktop. landing-page.tsx controls overall page order and landing-sections.tsx composes feature/gallery/testimonial/pricing/FAQ sections. Removing a section also requires removing its navigation links and preserving heading order; it is a source edit rather than a general configuration toggle.

Email collection and privacy

Use Email signup and Kit for complete preview, disabled, kit, kit-native and endpoint settings, plus independent demoAccess setup. Preview is explicitly non-collecting. kit-native keeps Forma's email/required-choice design and sends a valid consented signup through Kit's public Form handler; kit embeds your provider-designed Form. Native Kit setup needs the issued numeric Form/tag values, exact name mapping, reCAPTCHA flag and hosted fallback as well as UID/script values. Endpoint mode posts to your compatible receiver, which must validate, record, protect and respond. No private keys, account authentication, database or receiving backend are included. A native request-received status is separate from confirmed subscription and delivery.

Preview, native Kit and endpoint newsletter fields use translated inline errors after JavaScript loads: newsletter.emailError and newsletter.consentError. Preserve required constraints, focus and invalid-field descriptions. Endpoint retains native validation/POST without JavaScript; preview and native newsletter controls remain disabled. Native Kit includes a hosted fallback; embedded Kit validation is provider-owned. Translate the native notices, pending/received/error/unknown messages and verification title too; see Languages.

Newsletter consent is separate from theme/language storage permission. The cookie-preference manager does not unsubscribe emails or manage all third-party scripts. Set real policy links and test provider/storage behavior before launch.

After edits, run npm run format, review its changes, then npm run check. Use the Launch checklist on both language pages, billing periods and themes, with keyboard and responsive review.