Updates and changelog
Keep a copy of your purchased release and your customized source. Updates should be compared and applied deliberately; overwriting an edited folder can erase your branding or integrations.
Paid purchases under the included Kitee licence v1.1 receive 12 months of template support and access to Forma updates Kitee releases during that period, starting on the paid purchase date. There is no fixed release schedule or automatic updating of your website. Applying and testing updates in your customized project is your responsibility; custom integration work is separate. Licensed use of your purchased version and updates received under its licence continues after the included period. Earlier purchases keep their applicable terms, and legally required updates and remedies remain unaffected. See Support and updates and the complete licence.
On this page
- Toolchain and compatibility
- Apply a template update safely
- Updating from Forma 1.5.3 to 1.6.0 — 20 October 2026
- Updating from Forma 1.5.2 to 1.5.3 — 16 October 2026
- Updating from Forma 1.5.1 to 1.5.2 — 16 October 2026
- Updating from Forma 1.5.0 to 1.5.1 — 16 October 2026
- Updating from Forma 1.4.26 to 1.5.0 — 16 October 2026
- Updating from Forma 1.4.25 to 1.4.26 — 16 October 2026
- Updating from Forma 1.4.24 to 1.4.25 — 16 October 2026
- Updating from Forma 1.4.23 to 1.4.24 — 15 October 2026
- Updating from Forma 1.4.22 to 1.4.23 — 15 October 2026
- Updating from Forma 1.4.21 to 1.4.22 — 15 October 2026
- Updating from Forma 1.4.20 to 1.4.21 — 14 October 2026
- Updating from Forma 1.4.19 to 1.4.20 — 14 October 2026
- Updating from Forma 1.4.17 to 1.4.19 — 14 October 2026
- Updating from Forma 1.4.16 to 1.4.17 — 14 October 2026
- Updating from Forma 1.4.15 to 1.4.16 — 14 October 2026
- Updating from Forma 1.4.14 to 1.4.15 — 14 October 2026
- Updating from Forma 1.4.12 to 1.4.14 — 14 October 2026
- Updating from Forma 1.4.11 to 1.4.12 — 14 October 2026
- Updating from Forma 1.4.10 to 1.4.11 — 14 October 2026
- Updating from Forma 1.4.9 to 1.4.10 — 14 October 2026
- Updating from Forma 1.4.8 to 1.4.9 — 14 October 2026
- Updating from Forma 1.4.7 to 1.4.8
- Updating from Forma 1.4.6 to 1.4.7
- Updating from Forma 1.4.5 to 1.4.6
- Updating from Forma 1.4.4 to 1.4.5
- Updating from Forma 1.4.2 to 1.4.4
- Updating from Forma 1.4.1 to 1.4.2
- Updating from Forma 1.4.0 to 1.4.1
- Migrating from Forma 1.3.x to 1.4.0
- Version 1.3.1: hero typography
- Migrating from Forma 1.2.0 to 1.3.0
- Migrating from Forma 1.1.x to 1.2.0
- Migrating from Forma 1.0.3 to 1.1.0
- Changelog
- Regenerate the documentation
Toolchain and compatibility
The supplied lockfile records Next.js 16.4.0, React/React DOM 19.3.0 and TypeScript 5.9.3. Supported runtime versions are declared in package.json: Node.js 22.13+ within version 22, or Node.js 24+, and npm 10+.
Use npm ci to reproduce the delivered dependencies. Do not automatically upgrade framework packages during first installation. Future major releases may need code changes and separate checks; the purchase does not guarantee compatibility with every future framework version.
Apply a template update safely
- Back up your working source, lockfile and deployed export. Keep any private environment file separately and securely.
- Extract the new release into a different folder. Read its changelog and compare it with the version you use.
- Install and check the new unmodified copy using its guide. This confirms it works independently of your edits.
- Compare changed source files with your customized versions. Reapply your content, actions, assets and integrations rather than copying old files blindly over new ones.
- Keep the new release's matching
package.jsonandpackage-lock.jsontogether unless you intentionally maintain a different reviewed dependency set. - Run
npm run formatandnpm run check, inspect the production preview and repeat the launch checklist. - Build with your production site URL and deploy only after verifying the customized version. Keep the previous export available for rollback.
Version control is useful for tracking your own edits. The update process does not require a paid service or an automated migration tool.
Updating from Forma 1.5.3 to 1.6.0 — 20 October 2026
Version 1.6.0 adds build-generated Content Security Policy and HSTS header artifacts without changing Forma's static-export model or adding dependencies. Adopting these files does not apply your production hosting settings automatically: configure and verify the actual HTTPS host as described below. COOP and Trusted Types are outside this update's scope.
The build records document digests and inline-script SHA-256 hashes in out/forma-security.json, and emits a static-host recipe in out/_headers. The local production preview checks requested HTML against its recorded digest and enforces that document's CSP; HTTP localhost deliberately sends no HSTS. It serves the existing build rather than checking edited source settings or the entire header recipe at startup. npm run security:check compares exported HTML, current settings and both generated artifacts. The default production HSTS recipe uses 30 days, no subdomain coverage and no preload. Edit src/config/security.ts, rebuild, then follow Build and deploy for host-specific configuration and verification.
Active Kit modes and endpoint destinations inform the generated policy; preview defaults remain non-collecting and add no external Kit destinations. Configured external image/media URLs add exact origins, with no blanket HTTPS permission. Conditional reCAPTCHA permissions are path-limited; custom Kit fonts/analytics and other extra services need reviewed exact HTTPS origins and another build. Workers are blocked. This does not change Kit's pending clarification for the advanced background adapter, provider attribution, marketing permission or the site's spam-protection responsibilities, nor establish an end-to-end real-provider test. Existing source customizations must be compared before adopting the security configuration and build/preview helpers together. Do not copy generated hashes from an older build or edit a frozen buyer ZIP.
The update also adds a shared Kit request safeguard across the Kit-designed embed and Forma-styled newsletter/demo forms. A second signup is stopped while another request is pending or unknown, preventing overlapping provider verification flows. Actual completion or provider errors release that request; closing a view or reaching the timeout does not. Public demo continuation remains available independently. Merge src/lib/kit-request-lock.ts with the matching adapter and component changes, and translate the new newsletter.requestBusyMessage in both content files. This coordination applies to the current page, not other tabs or a backend. See Email signup and Kit for the exact behavior and remaining provider checks.
Both Kit integration styles now share src/lib/kit-provider-guards.ts to keep the provider's actual verification controls usable above Forma's signup popup. Preserve this helper with the request and component changes; it does not replace or bypass provider verification.
Updating from Forma 1.5.2 to 1.5.3 — 16 October 2026
Version 1.5.3 expands the distributed third-party notices to include framework helper and polyfill code identified in the compiled export. Replace NOTICE.txt and docs/THIRD-PARTY-NOTICES.txt in your editable project, rebuild, and retain the generated notice files beside the deployed assets. If you publish a prebuilt export manually, deploy its updated notice files as well as its matching application files. The Kitee commercial licence, support/update period, font rights and dependency versions are unchanged.
The cookie preferences dialog now keeps its explanation about email consent when the newsletter section is disabled but optional Kit signup during demo access is enabled. No new collection mode or permission is added. The non-collecting defaults remain unchanged, and the custom Kit background adapter still awaits Kit's written clarification before production use or commercial approval claims.
Updating from Forma 1.5.1 to 1.5.2 — 16 October 2026
Version 1.5.2 restores the original transitive dependency range in the supplied lockfile. Resolved dependency versions, assets, licence and support terms are unchanged. Keep the matching package and lockfile together when updating.
The email and agent guides clarify that native newsletter/demo forms always retain their provider-issued Built with Kit badge, including demo response views. No native branding-removal switch is provided. Eligible paid-plan removal belongs to the standard Kit-designed embed's own Kit settings. Editable frontend source is not tamper-proof, and buyers remain responsible for provider terms. The custom adapter still awaits provider clarification; the default bundle stays non-collecting.
Updating from Forma 1.5.0 to 1.5.1 — 16 October 2026
Version 1.5.1 retains the provider-issued Built with Kit text badge/link in native newsletter and real demo-access forms, including their response view. It documents free-plan branding requirements and marks the advanced custom adapter as pending provider clarification before production use. The documented Kit-designed embed remains available; affiliate membership is not technical approval of a custom integration.
The email and agent guides explicitly assign spam/abuse-protection setup to the buyer/site operator for this frontend-only release. Frontend checks and double opt-in alone do not prevent automated requests. Root agent instructions retain server-side spam/abuse protection as a requirement if a backend is commissioned later, without promising a future backend release. Existing non-collecting defaults, dependencies, assets, licence and support/update terms remain unchanged.
Updating from Forma 1.4.26 to 1.5.0 — 16 October 2026
- Header navigation now switches to its compact menu at 1050 px, keeping the configured Get started action reachable at intermediate tablet widths. Merge the matching header CSS and
landing-page.tsxresize query together; the main layout's 800 px breakpoint is unchanged.
Version 1.5.0 adds Forma-styled Kit signup (newsletter.mode: 'kit-native') alongside the existing Kit-designed embed (mode: 'kit'). Native fields appear immediately; a valid submission with checked marketing consent loads Kit's public handler and submits in the background. Responses distinguish request received, error and unknown outcome; they never claim confirmed subscription. Kit still owns confirmation, delivery, verification and unsubscribe. There is no new backend, private API credential or dependency.
The new independent demoAccess configuration defaults to preview. Its optional mode: 'kit' keeps name/email demo access with a separate unchecked marketing choice. Unchecked grants the configured demo continuation without a Kit request. Checked sends name/email and the configured permission tag to a separate Kit Form while demo continuation remains available. This is a public demo, not account authentication. The newsletter stays mailing-list-only. Use distinct provider Forms when enabling both real purposes.
Review action routing when upgrading: { kind: 'demo' } now always opens demo access, independent of newsletter placement. Exact #newsletter actions open newsletter signup when its placement is dialog. If you previously used Get started to open newsletter signup, set headerAction: { kind: 'link', href: '#newsletter' }. Other checkout/CTA links keep their configured destinations.
Embedded kit now defaults to kitLoad: 'automatic': the actual Form loads when its section mounts or newsletter popup first opens, without a Load or ready button. To retain explicit click-to-load behavior, set kitLoad: 'interaction'. In that mode the Load control disappears after the Form renders, with conditional focus transfer. Automatic loading can initialize provider requests/storage before marketing consent; review your site's disclosures and chosen loading policy. Native forms load the handler only after a valid, consented submission.
Merge src/lib/newsletter.ts, kit-native.ts, actions.ts, the affected signup/action/dialog components and settings together. Add demoAccess, the chosen kitLoad policy and, for native requests, the public native.formId, consentTagId, firstNameField and recaptcha metadata with a hosted fallback. Fill both language slots. See the copy-and-paste examples in Email signup and Kit. Update the shared content type, both dictionaries and replacement languages with dialog.kitFormNote, kitSuccessDescription, and newsletter.nativeNotice, submitPendingLabel, requestReceivedMessage, requestUnknownMessage, submissionErrorMessage, guardTitle. The German replacement example includes them.
The guides explain current builder settings, optional Clare CSS, confirmation/tag checks, embedded/native loading, request outcomes and separate demo access. The current public-handler adapter depends on provider initialization/completion details and needs retesting if Kit changes them. Test consent, duplicate submission, unknown/error fallback, provider verification, confirmation/unsubscribe, keyboard focus and both languages/themes before publishing your connection. The default release remains non-collecting. Assets, dependency resolutions, licence and support/update terms are unchanged. Run the full release check and measure your production export; this update does not certify field Core Web Vitals.
Updating from Forma 1.4.25 to 1.4.26 — 16 October 2026
Version 1.4.26 improves the buyer guides on narrow screens. Long slash-separated terms, links and other unbroken text can wrap within the article rather than pushing the page sideways. Code blocks and wide tables retain their own horizontal scrolling, so examples stay readable without widening the page.
Compare scripts/docs.mjs if you customized the documentation renderer, then run npm run docs to regenerate the HTML guides from their Markdown originals. The application, product design, settings, assets, dependencies, licence and support/update terms are unchanged. This documentation correction does not establish a new application performance result.
Updating from Forma 1.4.24 to 1.4.25 — 16 October 2026
Version 1.4.25 includes the language switcher's visible abbreviation in its accessible name, alongside the native language name and translated action label. This aligns the name used by assistive technology and voice control with the visible control. The layout, two-language configuration and existing content fields are unchanged.
When merging customized source, compare src/components/language-controls.tsx and keep the accessible name aligned with the displayed abbreviation. Rebuild and check the control's name, keyboard operation and navigation in both languages. No new configuration, translation field, dependency or visual change is introduced.
New purchases supplied under commercial licence v1.1 include the 12-month support and update entitlement described above. Keep the complete matching licence and purchase terms with your delivery. This release does not automatically replace terms from an earlier purchase, install updates on a customer's site or promise a release cadence or lifetime access to future releases. The label correction and purchase terms do not establish a new performance result; measure the production export using the Launch checklist.
Updating from Forma 1.4.23 to 1.4.24 — 15 October 2026
Version 1.4.24 gives the enhanced video toolbar a two-second fullscreen inactivity delay, including paused or ended playback. Entering fullscreen starts a fresh reveal window. Pointer movement or another interaction reveals it again; keyboard navigation keeps focused controls available. Holding a seek or volume control keeps the bar visible until release, then restarts the appropriate idle delay. A pointer click's leftover browser focus no longer prevents hiding.
Merge src/components/product-video.tsx with its visibility rule in src/styles/marketing.css. Keep the pointer/keyboard distinction, fullscreen-change handling, held-pointer release/cancel/blur cleanup and timer cleanup together. Normal page playback retains its three-second pointer/touch delay and paused mouse-hover behavior; the compact portrait layout remains unchanged. Native browser controls and browsers without standard fullscreen retain their existing fallback. Rebuild and check fullscreen entry/exit, idle playing/paused/ended states, keyboard return, seeking and control release in your target desktop and mobile browsers. No new settings, translations, dependencies, media, licence or support-policy changes are required.
Updating from Forma 1.4.22 to 1.4.23 — 15 October 2026
Version 1.4.23 tightens the video toolbar in the normal portrait phone view. At 600 px and below, seeking and elapsed/total time fill the first row; available Play/Pause, mute, captions and fullscreen buttons sit together with 8 px gaps on the second row. Missing optional buttons leave no reserved empty slots. The buttons retain their 44 px touch targets. The desktop layout and playback behavior are unchanged.
Merge the .forma-video-progress wrapper in src/components/product-video.tsx together with the matching rules in src/styles/marketing.css. Above the phone breakpoint the wrapper uses display: contents to preserve the desktop layout. Keep the visible-control observers, keyboard/focus rules, caption positioning, native fallback and device-volume behavior. Rebuild and check 320 px and larger phone widths with captions loaded, both themes and languages, seeking, mute and auto-hiding controls. No configuration, translation, asset, dependency, licence or support-policy change is required.
Updating from Forma 1.4.21 to 1.4.22 — 15 October 2026
Version 1.4.22 adds translated, theme-matched inline validation to the local demo-access form and newsletter preview/endpoint forms. Invalid submission identifies each affected field, focuses the first invalid control after its message appears and clears an error when that field is corrected. Email checks use the browser's validity rules; demo names also reject spaces-only input. The real newsletter checkbox follows the site theme, keeps visible keyboard focus and restores native appearance in forced-colors mode. Endpoint mode retains native validation and POST without JavaScript; preview remains disabled without JavaScript. Kit-managed fields and validation are unchanged.
When merging customized source, keep src/lib/form-validation.ts, its focused tests, the updated demo-access/newsletter components and src/styles/newsletter.css together. Add dialog.emailError, newsletter.emailError and newsletter.consentError to both content dictionaries and their common type; keep dialog.nameError. Translate these required strings in any replacement language too. The German replacement example includes all fields. Test empty/invalid/valid input and correction, button/Enter submission, focus, both placements, both languages/themes and the endpoint's no-JavaScript path. The local demo confirmations still send and save nothing; real collection still needs your own tested provider or receiver.
The supplied illustrative video, poster and screenshot assets now use a consistent 1280 × 720 (16:9) canvas, with editable SVG originals and optimized WebP copies. Preserve your own authorized media when updating. Adopt the sample only if wanted, and keep each configured width/height aligned with its actual file; do not change custom asset dimensions just to match the sample. The optional Window/Minimal frame setting and shared English sample track remain available.
Phone video controls now use a compact two-row grid at 600 px and below: seeking and elapsed/total time share the first row, while the available Play/Pause, mute, captions and fullscreen buttons keep their 44 px targets on the second row. This prevents extra wrapping at 320 px without removing controls or changing native fallback. Keep the updated responsive rules in src/styles/marketing.css, then check the smallest width with captions loaded, fullscreen supported and your own media aspect ratio. Desktop volume remains available; phone volume stays under device control with the slider hidden.
The player's independent control-height observer now starts only while the floating controls are visible. Keep this guard with the existing loaded-cue/visible-control caption handling in src/components/product-video.tsx. It avoids unnecessary hidden-bar measurement while preserving the native fallback, captions and visible control layout. The localFont declaration in src/components/document-frame.tsx now includes the supplied Latin file's actual unicode-range, allowing uncovered scripts to use their fallback directly. The font file and licence are unchanged. If you supply a font with different coverage, update or remove that range; see Appearance. Measure your own production page using the Launch checklist; these changes do not certify field Core Web Vitals.
The new agent customization manual is written for a coding agent configuring a licensed client project. Give it the client's brief and retain the supplied root AGENTS.md entry point. If you maintain packaging, keep the new guide in the scripts/docs.mjs catalog and AGENTS.md in the scripts/package.mjs source allowlist, then regenerate offline HTML. Shared settings, language slots, static hosting, dependencies, licence and support terms remain the same.
Updating from Forma 1.4.20 to 1.4.21 — 14 October 2026
Version 1.4.21 removes unnecessary initial rendering work. Video-caption positioning starts only while the floating controls are visible and a track has loaded cues. Hiding the controls restores the original cue positions, including authored placement; load and resize handling remains active when needed. Theme synchronization avoids rewriting unchanged document attributes while preserving the existing before-paint initialization, preference storage and consent rules.
When merging customized source, compare src/components/product-video.tsx and src/components/theme-controls.tsx. Keep the caption effect's cleanup and its control-visibility dependency together, and preserve your own media, labels and theme settings. No configuration or translation fields changed. Rebuild, then check video captions with controls visible and hidden, pointer/keyboard playback, native fallback and theme switching with permission allowed, declined and withdrawn. Use the Launch checklist to measure your own production export; these targeted changes do not guarantee field Core Web Vitals on every host or device. Dependencies, assets, licence and support terms are unchanged.
Updating from Forma 1.4.19 to 1.4.20 — 14 October 2026
Version 1.4.20 reviews and clarifies the buyer guides without changing the landing-page implementation, configuration shape, dependencies, media, licence or support terms. It distinguishes the default Get started demo-access popup from the separate newsletter preview, maps all four source stylesheets, identifies the actual social-image settings, explains matching navigation arrays, and aligns alternative-text guidance with content validation.
The email guide adds accepted receiver paths and field-name rules, distinguishes endpoint metadata from Kit-managed fields, and explains Kit account readiness and repeated confirmation testing. The optional packaging instructions now state that the ZIP copies the current out/ rather than rebuilding or resetting it. The support-report example asks for the buyer's actual installed Forma version.
Use the refreshed HTML guides and Markdown sources together, and preserve your own content/integrations. Keep the matching release manifests if updating the complete source package. There are no new component, content or settings fields to merge; the Window/Minimal video-frame and local demo-access instructions below still apply. Your own Kit delivery and unsubscribe journey must still be tested with your account; this documentation review is not a completed provider-account test.
Updating from Forma 1.4.17 to 1.4.19 — 14 October 2026
Version 1.4.19 adds the optional siteSettings.preview.video.frameStyle setting. The supplied value is 'window'; omitting it also preserves the existing presentation. Set it to 'minimal' to remove the browser header's three dots, product name/top label and the bottom descriptive text bar while keeping the rounded outer frame, outline, ring and shadow. The caption remains available to screen readers, and the separate sample-media disclaimer stays visible. Playback controls and loaded video-track captions remain available, with a visible status on playback failure. It does not crop a border already baked into your media or affect image-gallery mode.
Merge the optional field in src/config/preview.ts, its default in src/config/site.ts, the presentation wiring in src/components/product-preview.tsx, the descriptive-caption class in src/components/product-video.tsx and the matching rules in src/styles/marketing.css. Preserve your own media and translated labels. No new content dictionary field is required. Rebuild and compare both presentations at phone, tablet and desktop widths in both themes. Repeat keyboard playback, caption and native/error fallback checks in the Launch checklist; the player controls and behavior are unchanged. This option adds no dependency, backend, licence or support-policy change.
Updating from Forma 1.4.16 to 1.4.17 — 14 October 2026
Version 1.4.17 restores a local name/email demo-access scenario in the header's Get started popup. The supplied headerAction changes from a #newsletter link to { kind: 'demo' }; dialogAction becomes a normal link to #product. Desktop and mobile-menu Get started now share headerAction and header.actionLabel; the hero action remains independently configured. Preserve your own real conversion destinations when merging rather than replacing them with the sample defaults.
Merge src/components/demo-access-form.tsx, its matching dialog styles and the popup wiring in landing-page.tsx. Add the new dialog text fields from src/content/types.ts to both content dictionaries, including any languages you supplied yourself. The complete German content example is updated to match. Keep the explicit demo explanation in the form and success step; it does not create an account, send an email, save/transmit input or protect access to a destination. Keep dialogAction as a normal link.
The form mounts after opening and uses method="dialog", so its native submission cannot make a network request. Both fields are required; a spaces-only name must also be rejected. Valid submission clears the fields, reveals the demo confirmation and focuses its heading. Closing clears the scenario so reopening starts fresh. There is no marketing-consent checkbox because this is not newsletter collection. Test button and Enter submission, validation, the configured access link, close/Escape/backdrop, return focus and narrow/zoomed layouts in both languages and themes.
The separate newsletter section remains the default. With an enabled newsletter and placement: 'dialog', Get started instead presents the existing configured newsletter, retaining preview, Kit and endpoint modes. Exact #newsletter signup links continue to open that presentation; external checkout links remain ordinary links. Preserve the newsletter Form's existing retained state after first opening, its explicit Kit loading choice and its provider/receiver-managed real responses. See Customization and Email signup and Kit. No dependency, backend, licence or support-policy change is required.
Keep the updated outer-dialog close handling with the mobile-menu wiring. Closing returns focus to the visible opening control, or to the menu button when the opening menu item has become hidden. Closing an inner newsletter preview confirmation must not trigger the outer dialog's reset or focus handling. Repeat both desktop and mobile journeys, including Escape and the nested newsletter confirmation.
Updating from Forma 1.4.15 to 1.4.16 — 14 October 2026
Version 1.4.16 makes the default newsletter preview interactive when JavaScript is available. It uses the existing form styling and native required email/unchecked-checkbox validation. A valid local submission resets the form and opens a clearly labelled demo confirmation: no email is sent, no subscription is created and Forma does not save or transmit the entered details. Preview controls remain disabled without JavaScript to prevent a native fallback submission.
Merge src/components/newsletter.tsx with its matching rules in src/styles/newsletter.css. Add previewConfirmationLabel, previewSuccessTitle, previewSuccessDescription, previewCloseLabel and previewDoneLabel to the newsletter type and both content files, and retain the updated previewNote. If you replaced either example language, translate these fields too. Keep the explicit demo and non-collection explanation when adapting the messages; do not present this popup as actual email delivery or a stored consent grant.
Test both placements, languages and themes. Empty/invalid email or an unchecked required box must not show success. A valid submission must reset the fields, show the demo explanation and allow closing with its close control, Got it or Escape, returning focus to submit. When signup is already in the Get started popup, closing the confirmation must leave that original popup open. Verify phone/tablet layout, keyboard submission and no POST/provider request or preview input storage. Repeat with JavaScript disabled and confirm the preview cannot submit.
The simulated confirmation is exclusive to preview mode. Preserve Kit's click-to-load provider flow and its real confirmation settings, and endpoint mode's normal HTML POST and receiver-managed response. The change adds no service, subscriber database, backend or dependency. Licence and support terms remain unchanged. See Email signup and Kit and the Launch checklist.
Updating from Forma 1.4.14 to 1.4.15 — 14 October 2026
Version 1.4.15 uses optimized WebP copies of the supplied product illustrations for displayed samples and the video poster. Their original editable SVG files remain in public/product/. Landing documents preload the configured video poster, or the first product image when it has no darkSrc; the selected screenshot loads eagerly with high priority, while later feature/workflow images and thumbnails stay lazy-loaded. The clip still does not autoplay and uses preload="none".
When merging, compare the media paths in src/config/site.ts, add the supplied WebP assets, and keep the matching document-frame.tsx, landing-layout wiring and media-preview.tsx changes. Preserve your own media choices instead of replacing them with sample paths. Distinct dark-image variants remain supported; ordinary images no longer need a theme-change observer when they have no different dark asset.
An unused nested locale provider was removed from the missing-page content; its outer/global context is retained. The ordinary home link removes redundant navigation work. Unused legacy dashboard icon paths and stylesheet rules have been removed; all six configurable feature-card icon names remain available. If you customized these areas, compare your missing-page content, shared icon component and styles before merging so your own deliberate additions are retained.
Keep the offscreen-section rules at the beginning of src/styles/marketing.css together with their 800 px and print overrides. Seven later sections use CSS content-visibility: auto and --section-estimate height placeholders; hero, product preview and footer are excluded. The content remains in the document, and unsupported browsers render normally. If your customized sections are much longer or shorter, review those estimates rather than restoring values blindly. Repeat direct-anchor, scrolling, keyboard, browser Find, assistive-technology and print-preview checks described in Appearance. No JavaScript scroll observer is added.
The local production preview now negotiates gzip for useful text responses while preserving video byte ranges and the existing security/cache headers. Merge scripts/serve.mjs together with the new scripts/text-response.mjs, retain scripts/media-range.mjs, and include tests/text-response.test.ts. Copying the new server without its imported helpers causes a missing-module failure. If you maintain the buyer-packaging script, keep the new helper in the scripts/package.mjs allowlist. This local transport change does not configure compression or caching on a production host; see Build and deploy.
Merge scripts/site-files.mjs with its new imported scripts/font-preload.mjs, plus tests/font-preload.test.ts and the updated fixture in tests/site-files.test.ts. Keep font-preload.mjs in the buyer-packaging allowlist too. The post-build helper derives the generated font URL only when there is exactly one safe exported WOFF2, adding a missing preload to known root, language and missing-page documents while preserving matching existing preloads. With no font or multiple candidates it leaves the pages alone. Copying site-files.mjs without its helper causes a missing-module build failure. The supplied local font, its configuration and licence remain unchanged; rebuild and verify early loading without duplicate font transfers as described in Appearance.
next.config.mjs enables the experimental inlineCss: true production option. Editable styles stay in their separate source CSS files, while each generated document includes its required styles, preserving styling without JavaScript. HTML becomes larger and the inlined styles are not independently cached across visits. Keep the other configuration when merging; if separate stylesheet caching better suits your site, change only inlineCss to false, rebuild and compare. Repeat both-language/theme, missing-page, no-JavaScript video and print checks; see Appearance.
Rebuild and repeat the Launch checklist for both language pages, themes and a missing-page URL. Measure the production export on comparable mobile and desktop profiles, check the initial poster/image request and test video playback separately. These changes do not guarantee field Core Web Vitals on every host or device. There are no new dependencies, backends, buyer content fields, licence or support-policy changes.
Updating from Forma 1.4.12 to 1.4.14 — 14 October 2026
Version 1.4.14 corrects a build mismatch: an origin supplied through .env.local now reaches the generated sitemap and robots.txt, as well as the page metadata. Previously those two files could retain localhost URLs when Next.js had loaded the real origin from a file. Standard production environment-file priority applies; an explicit terminal or host build variable takes priority.
Merge scripts/site-files.mjs together with the clearer build-failure message in scripts/next.mjs. Keep your public origin setting, then rebuild and verify both language pages' canonical URLs, out/sitemap.xml and out/robots.txt against your intended domain. If you use the buyer-packaging script, scripts/package.mjs also updates the outer README's description of email signup.
The guides clarify the optional Kit share URL, show a directly usable dialog action value, separate the player instructions by input method and distinguish an older release's defaults from the current ones. Five regression test groups cover environment-file loading, metadata agreement, priority, localhost fallback and invalid origins. Visual design, template features, dependencies, licence and support terms are unchanged.
Updating from Forma 1.4.11 to 1.4.12 — 14 October 2026
Version 1.4.12 refines touch gestures: a tap on the video reveals the floating bar and toggles playback, while swiping across the video does not open the bar. Keyboard access continues to keep controls visible while focused.
Merge the updated src/components/product-video.tsx, preserving your existing media, labels and styling. Rebuild and test touch taps, page scrolling over the video, bar controls and keyboard playback in your target browsers. Layout, configuration, dependencies, hosting, licence and support terms are unchanged; the 1.4.11 floating-control instructions below still apply.
Updating from Forma 1.4.10 to 1.4.11 — 14 October 2026
Version 1.4.11 moves the themed controls into a floating bar inside the video, visible with pointer activity or keyboard-visible focus. Mouse/pen hovering keeps the bar visible while paused or ended; leaving hides it even when stopped. During playback it also hides after about three seconds of pointer inactivity. A touch tap gives about three seconds of visibility whether playing or paused; lifting a finger does not hide it immediately. Keyboard navigation/focus keeps controls available, but a mouse click on a control alone does not prevent hiding after leaving. Surface click/tap and Enter/Space playback with brief Play/Pause feedback remain available.
Merge the updated src/components/product-video.tsx together with its player and responsive rules in src/styles/marketing.css. Preserve the control visibility/focus handling and caption adjustment when comparing customized versions. At 600 px and below, the paused centered Play icon hides while the bar is visible and returns when the paused bar hides; brief feedback sits above the bar, seeking uses a 24 px-high row, buttons remain 44 px high and volume stays hidden. No new configuration fields or translated labels are required.
Where supported, automatically positioned bottom WebVTT cues move above the visible bar and return when it hides. Explicit authored positions are preserved; review your own track with controls visible and hidden at phone widths, fullscreen and 200% zoom. On media failure, the custom retry bar returns below the video so native controls remain unobstructed. Native playback before enhancement and without JavaScript is unchanged.
Rebuild and repeat the Launch checklist, including pointer-idle hiding, keyboard access, captions, playback failure and both themes/language pages. Media settings, no autoplay, preload="none", dependencies, static hosting, licence and support terms remain unchanged.
Updating from Forma 1.4.9 to 1.4.10 — 14 October 2026
Version 1.4.10 lets visitors click or tap the video surface to play or pause, with equivalent Enter/Space keyboard controls. A centered Play or Pause icon briefly confirms successful playback changes, then hides during playback; the paused Play affordance returns after feedback. Keyboard focus stays on the surface during playback, so the same control can pause it. Reduced-motion preferences keep the brief feedback static.
Merge the updated src/components/product-video.tsx together with the player rules in src/styles/marketing.css. Keep your existing media settings, assets and translated labels. Rebuild and test surface and bottom-bar playback, repeated clicks, keyboard focus, replay and native/error fallback in both themes, language pages and target browsers. See Customization and the Launch checklist.
The bottom controls, no-autoplay behavior, preload="none" and native fallback remain. There are no new settings, dependencies, hosting, licence or support-policy changes.
Updating from Forma 1.4.8 to 1.4.9 — 14 October 2026
Version 1.4.9 makes workflow gallery screenshots slightly larger inside their existing colored panels. Panel padding changes to 20 px on larger screens and 18 px at widths of 800 px or less. The alternating tilt, image proportions and fitting without cropping remain the same.
When merging your customized project, compare the .forma-workflow-image padding and its responsive overrides in src/styles/marketing.css. Keep your existing gallery settings, assets and translated captions, then rebuild and review phone, tablet and desktop widths. See Appearance for the styling rules.
There are no new settings or dependency, hosting, licence or support-policy changes.
Updating from Forma 1.4.7 to 1.4.8
Version 1.4.8 includes the required scripts/media-range.mjs helper in the buyer archive and checks that every script is present in the reviewed packaging allowlist before creating a ZIP. Keep this helper with scripts/serve.mjs when merging an update. If you add buyer scripts, review and list them in scripts/package.mjs; private scripts belong outside buyer source.
The video player, sample media, styling and configuration remain the same as 1.4.7. There are no dependency, licence or support-policy changes.
Updating from Forma 1.4.6 to 1.4.7
Version 1.4.7 replaces the caption-row Play/Pause button with a theme-matched bar below the video: playback, seeking, elapsed/total time, mute, desktop volume, loaded captions and supported fullscreen. The centered paused Play overlay remains. A subtle CSS halo runs around the playback button while playing and respects reduced motion. Native controls remain the fallback before the enhancement, without JavaScript and after playback failure. Video still has no autoplay and uses preload="none".
- Merge
src/components/product-video.tsxtogether with the updated player styles and responsive rules insrc/styles/marketing.css. Preserve the existing reduced-motion rule insrc/app/globals.css, media-event handling and native fallback; do not restore the duplicate caption-row button. - Add these eight
previewfields to both content dictionaries:videoControlsLabel,videoSeekLabel,videoMuteLabel,videoUnmuteLabel,videoVolumeLabel,videoCaptionsLabel,videoFullscreenLabelandvideoExitFullscreenLabel. Retain the existingvideoPlayLabel,videoPauseLabelandvideoErrorLabel. Keep the matching preview/content type updates; the supplied English/Greek dictionaries and German replacement example include the labels. - The new sample defaults to a short original silent video. Preserve your deliberate
preview.mode, authorized custom media, dimensions and translated copy when merging; adopting the new sample video is optional. Keep your matching image entries/translations if you use or may return to'images'mode. Customization identifies the supplied assets and both modes. - Rebuild and review pointer/keyboard playback, seeking, replay, errors, native fallback, target-browser sound/captions/fullscreen, both languages/themes and phone widths. The phone volume slider is intentionally hidden at 600 px and below; captions depend on a successfully loaded configured track and fullscreen on browser support.
- Keep the updated
scripts/serve.mjstogether with its new importedscripts/media-range.mjshelper. The pair adds HTTP byte-range responses for local production video review; copying onlyserve.mjsleaves a missing-module error. Your production static host must serve the configured media with appropriate response types and byte-range support too; test actual forward/backward seeking rather than only Play. See Build and deploy. This hosting requirement does not turn the static export into a Node.js server application.
No playback library, dependency, streaming service or backend is added. The original supplied clip/track are covered by the existing commercial template licence; licensing, support, two-language routing, cookie preferences and static hosting remain unchanged. Review the Launch checklist for the actual media and integrations you publish.
Updating from Forma 1.4.5 to 1.4.6
Version 1.4.6 completes two documentation details: the project map now identifies src/components/product-video.tsx, and the launch checklist explicitly covers the branded Play/Pause controls, keyboard focus, replay, translated playback errors and native controls without JavaScript.
This is a documentation-only patch. Keep your existing application configuration and assets; there are no component, stylesheet, dependency, hosting, licence or support-policy changes. The video and gallery customization instructions introduced in the preceding releases remain current.
Updating from Forma 1.4.4 to 1.4.5
Version 1.4.5 gives workflow screenshots a subtle alternating static tilt and centers them inside panels with more even padding. The colored outer panels remain level, and screenshots preserve their ratio without cropping. Phone layouts use a smaller tilt.
When merging your customized project, compare the .forma-workflow-image rules and their responsive overrides in src/styles/marketing.css. Retain the updated fitting, padding and tilt rules together; see Appearance if you prefer level screenshots. Your existing gallery configuration, image paths, dimensions and translated captions remain compatible. Review your own media at phone, tablet and desktop widths after rebuilding.
There are no new settings or dependency, hosting, licence or support-policy changes.
Updating from Forma 1.4.2 to 1.4.4
Version 1.4.4 gives the optional local video preview a branded Play button over the paused video and a Play/Pause button beside its caption. Browser controls still handle seeking, sound, captions and fullscreen. There is no autoplay; media retains preload="none".
- Keep the new
src/components/product-video.tsxtogether with the updatedproduct-preview.tsx, preview/content types andsrc/styles/marketing.csswhen merging your customized project. Existing image galleries and media settings remain compatible. - Add
preview.videoPlayLabel,preview.videoPauseLabelandpreview.videoErrorLabelto both language dictionaries. The supplied English/Greek dictionaries and German replacement example include these fields. - Retain your authorized local video, poster and optional caption tracks. Check Play, Pause, playback completion, keyboard access and native controls in your target browsers. A blocked or failed play attempt displays the translated error message and leaves browser controls available.
There were no dependency, hosting, licence or support-policy changes in 1.4.4. At that version, image mode remained the default and no video asset was supplied. No streaming service or playback backend was included.
Updating from Forma 1.4.1 to 1.4.2
Version 1.4.2 clarifies the buyer-owned Kit setup and tightens validation of its optional hosted fallback. The page design, dependencies, licence and support terms are unchanged.
- Retain the updated newsletter URL validator and tests when merging a customized project. A nonempty
shareUrlmust be a complete HTTPS URL; legitimate custom domains remain supported. Use''to omit the fallback. - Follow Email signup and Kit to save/publish the inline Forms, configure both language slots and set return visitors to Continue to show the same Form. Other provider return states can produce a false loading timeout.
- Review the tagged consent choice, confirmation settings and marketing audience filters. An accepted signup alone does not establish the permission to send marketing.
- Repeat the actual Form, returning-visitor, popup reopen, confirmation and unsubscribe tests using your own account. This patch does not connect an account or certify email delivery.
Updating from Forma 1.4.0 to 1.4.1
Version 1.4.1 adds newsletter placement in the existing Get started popup while keeping the page section as the default. No dependency, hosting, licence or support-policy change is required.
- Keep the updated newsletter component, action/navigation handling, dialog styling and settings type together when merging a customized project.
- Add
placement: 'section'inside your existingsiteSettings.newslettersettings to preserve the page section. Change it todialogonly when you want signup in the popup. Exact#newsletterCTA/navigation destinations then open it; unrelated links keep their destinations. - Add the supplied
newsletter.closeLabelfield to both translations, including any replacement language example. The signup popup uses newsletter heading/description copy; the default information panel still usesdialogcopy. - Preserve your existing mode, privacy policy and Kit/endpoint settings. In Kit mode, use the same buyer-owned Inline Form setup and explicit Load signup form control. Do not add Kit's own modal on top of Forma's popup.
- Build and repeat signup, keyboard, phone, close/Escape and reopen tests with your own Form. After first opening, the same Form remains mounted when the dialog is hidden; unfinished entries and any loaded Kit Form survive reopening for that page visit. Forma does not store those entries in browser preferences. Closing does not unload Kit, unsubscribe or revoke provider-managed storage. Read Email signup and Kit.
Migrating from Forma 1.3.x to 1.4.0
Version 1.4.0 makes Forma a more reusable landing template: real configurable media replaces the simulated workspace, cards/gallery/testimonials use flexible arrays, and newsletter collection connects to your own provider or receiver. The old configuration/content objects are not drop-in replacements.
| 1.3.x location or behavior | 1.4.0 equivalent |
|---|---|
Shared sectionsContent settings in sections.ts | siteSettings.sections in the central site.ts file |
Workspace identities/tasks in preview.ts | siteSettings.preview image/video configuration |
| Fixed workspace/task/board/timeline translated copy | preview image captions and accessibility labels in each dictionary |
| Fixed feature illustrations and three workflow mockups | Configurable cards and workflow image entries with matching translations |
| One sample customer story | sections.story.testimonials and shared identity/autoplay settings |
| Hardcoded visible logo and accent edits | siteSettings.brand.logo and .colors.light/.dark |
dialogSuccessAction and local form success | dialogAction and an optional information dialog; no fake signup state |
| No receiving form service | Optional newsletter preview, disabled, kit or endpoint mode |
- Keep your original release and customized source/export. Start from the new
site.tsand both content files; reapply your brand, prices, URLs and text deliberately.sections.ts/preview.tsnow define types instead of additional editable settings objects. - Copy authorized optimized screenshots/video into
public/, configure their paths/dimensions and translate captions/alt text. Remove old task/activity content that no longer describes a visible component. - Reapply feature/gallery/testimonial changes as matched shared/primary/secondary array entries. Replace placeholder testimonials only with approved actual quotations. Review the three-to-six gallery example and pause/reduced-motion behavior.
- Choose direct-link CTAs or the optional information dialog. Review every plan action in both billing periods; displayed prices do not connect a payment backend.
- Keep email in non-collecting preview or disabled mode until you have your own policy and receiving service. For Kit, use published inline JavaScript Forms for the two language slots; configure consent/confirmation inside Kit. For endpoint mode, test the receiving backend's validation, records and responses separately. Read Email signup and Kit.
- Preserve the existing language routes, metadata and version-2 theme/language preference controls. Newsletter consent is separate; do not widen a previous appearance-storage grant to unrelated provider purposes.
- Regenerate docs after guide edits, run format/check and repeat browser/launch tests on your actual production build. Rebuild with the correct public origin before publishing a complete clean export.
The static-export hosting model, runtime dependency versions, Kitee commercial licence and included support period remain the same. No subscriber database, payment system, email delivery backend or automatic host/provider setup is added.
Version 1.3.1: hero typography
The hero heading uses slightly looser, font-relative letter spacing, with normal tracking for the Greek heading's system fallback font. This keeps English and Greek visually balanced at desktop and phone sizes. Font sizes, weights and line heights are unchanged. There are no configuration, dependency or licence changes; the 1.3.0 language setup below still applies.
Migrating from Forma 1.2.0 to 1.3.0
Version 1.3.0 separates translated text from shared settings and adds exactly two configurable static language pages. The old 1.2.0 configuration objects are not drop-in replacements. Keep the new files and reapply your edits deliberately:
| 1.2.0 location | 1.3.0 location |
|---|---|
site.name | siteSettings.name in src/config/site.ts |
site.language | Pair, direction, formatting and default in src/config/languages.ts |
| Metadata, hero, navigation labels, UI/dialog/footer text | src/content/primary.ts and secondary.ts |
| Labelled header/hero/dialog action objects | Shared destinations in siteSettings, translated action labels in each dictionary |
| Section/FAQ/plan text | Each dictionary's sections object |
| Prices/currency/plan actions and illustration numbers/identities | Shared sectionsContent in src/config/sections.ts |
| Pricing locale | Language entry's formatLocale |
| Workspace labels | Each dictionary's preview object |
| Workspace identities/initial task state | Shared previewContent in src/config/preview.ts |
Cookie content object | Each dictionary's cookies object |
| Cookie enabled/privacy/storage settings | src/config/cookies.ts |
| Page metadata in layout | src/lib/metadata.ts plus language page/root metadata |
- Back up your old source/export. Start from the new language/config/content files and reapply your shared settings and translated text using Customization and Languages.
- Preserve the new localized content provider, routes, metadata, switcher, language helpers and before-paint setup when comparing customized components. Keep stable
primary.ts/secondary.tsnames and matching exports. - Keep version 2 of the preference decision. It adds optional language memory; v1 permission is not silently expanded. Review translated inventory and privacy disclosures, then test old decisions, new choices, withdrawal and blocked access.
- Build both language pages. With the final origin configured, verify canonical/alternate/sitemap URLs and refresh/direct visits on your static host.
- Deploy a complete clean export. If public URLs change, plan any old-to-new redirects separately in your existing hosting setup; stale output directories should not remain public.
Language switching works without storing the choice; explicit URLs win. No translation service, backend, database or new runtime dependency is required. The commercial licence, support scope and static-export hosting model remain in place.
Migrating from Forma 1.1.x to 1.2.0
Version 1.2.0 adds optional appearance-storage permission. Earlier releases read and wrote forma.theme directly. A saved theme alone is not treated as permission: without a valid new allow decision, the new initialization starts with System and attempts to clear the stored theme. Browser access restrictions can prevent physical removal; the value is not used without valid permission.
- Keep the new
src/config/cookies.ts,src/lib/cookies.tsandsrc/components/cookie-controls.tsxfiles, and compare the updated theme helpers, controls, layout and footer with any customization you made. - Reapply your appearance labels and CSS changes without restoring unconditional local-storage access. Keep the before-paint initialization aligned with the controls.
- Translate preference copy if needed and set the optional privacy-policy link to your own accurate page. Do not add an analytics category unless you also implement and test the corresponding service controls.
- Test Necessary only, allow, withdrawal, reload, old-version/expired decisions and unavailable browser storage on the new production build.
Light/Dark/System remains usable without storing the choice. The default decision cookie lasts 180 days; existing visitors are asked to choose under the new feature. Review Cookies and preferences for the exact inventory and configuration.
The licence, included support period, frontend-only scope and static-export hosting model remain the same. No dependency or backend service is required for the preference feature.
Migrating from Forma 1.0.3 to 1.1.0
Release 1.1.0 changes the editable CTA API and moves more interface content into configuration. Existing 1.0.3 configuration files are not drop-in replacements for the new files.
| Earlier configuration or location | Forma 1.1.0 equivalent |
|---|---|
hero.primaryCta and hero.primaryHref | hero.primaryAction: { label, kind: 'link', href } |
hero.secondaryCta and hero.secondaryHref | hero.secondaryAction: { label, kind: 'link', href } |
| Header button hardcoded in the component | site.header.action |
Pricing plan action string | Plan action object with label and kind plus href for links |
Final CTA action string | cta.action object |
| Pricing action shared across billing periods | action plus optional annualAction for a separate yearly destination |
Workspace task/tab data in product-preview.tsx | previewContent in src/config/preview.ts |
| Benefit, dialog, footer and appearance copy in components | Grouped fields in src/config/site.ts |
| Hardcoded page language in layout | site.language |
For a former hero link, convert:
primaryCta: 'Explore the product',
primaryHref: '#product',
to the new hero field:
primaryAction: {
label: 'Explore the product',
kind: 'link',
href: '#product',
} satisfies CallToAction,
The new site.ts already imports CallToAction; keep that import and its existing type checks. Use { label: 'Explore the preview', kind: 'demo' } for the local dialog. Review all destinations instead of assuming a prior component modification carries forward.
If you customized landing-page.tsx, landing-sections.tsx, product-preview.tsx or theme-controls.tsx, compare those changes carefully: 1.1.0 reads more copy from config and uses the shared action component. Layout styling and the frontend-only static-export model remain the same.
Changelog
1.6.0 — 20 October 2026
- Generate CSP script hashes, document digests and static-host header artifacts from the actual build; add a security consistency check and enforce document-specific CSP in the local production preview.
- Provide a 30-day HTTPS HSTS recipe without subdomain coverage or preload, with buyer and agent deployment instructions.
- Coordinate pending and unknown Kit requests across embedded and native forms, and keep actual provider verification usable above Forma's popups.
- Update setup, merging, security and troubleshooting guides. Keep Kit disconnected by default, preserve required attribution and the custom adapter's pending production-approval boundary.
- Preserve the design, media, dependency resolutions, licence and 12-month support/update terms. Host configuration and real-world performance still require deployment-specific verification.
1.5.3 — 16 October 2026
- Include the additional third-party notices required by helper and polyfill code distributed in the compiled export; preserve independent open-source permissions and the existing commercial licence.
- Keep the cookie dialog's email-consent explanation available for independent demo-only Kit signup.
- Preserve default preview forms, assets, dependencies, support/update terms and the pending custom Kit approval boundary.
1.5.2 — 16 October 2026
- Restore the original lockfile dependency range while preserving resolved packages and all form behavior.
1.5.1 — 16 October 2026
- Retain the provider-issued Kit attribution in native forms and explain branding/service terms and the custom adapter's pending approval boundary.
- Add the explicit buyer/operator anti-spam responsibility and future-backend engineering requirement.
- Preserve preview defaults, static hosting, dependencies, assets and commercial terms.
1.5.0 — 16 October 2026
- Add immediately visible Forma-styled Kit newsletter signup with required consent, background submission, honest request states and hosted fallback; retain the Kit-designed embed option.
- Add independent demo-access Kit settings with optional unchecked marketing consent, separate provider Form and public demo continuation without signup.
- Default embedded loading to automatic with an optional interaction gate; remove the redundant ready button and preserve conditional focus transfer.
- Defer optional native newsletter and demo-access component code until those interfaces render, preserving native newsletter server markup and the public static export.
- Update both dictionaries, configuration validation, focused tests, buyer/agent guides and copy-and-paste setup examples. Preserve non-collecting defaults, assets, dependencies, licence and support/update terms.
1.4.26 — 16 October 2026
- Allowed long prose terms and links to wrap within buyer documentation articles on narrow screens, while keeping code blocks and wide tables locally scrollable.
- Regenerated the offline HTML guides from the shared renderer. No application behavior, design, configuration, media, dependency, licence or support/update-policy change is introduced.
1.4.25 — 16 October 2026
- Included the language switcher's visible abbreviation in its accessible name, preserving its native language name, translated action label, appearance and navigation.
- Added commercial licence v1.1 for new purchases: 12 months of template support and access to Forma updates Kitee releases during that period, starting on the paid purchase date. No fixed release cadence, automatic website updates or custom integration work is included; licensed use continues after the period, and earlier purchase terms and mandatory rights remain preserved.
- Aligned the support, licensing, update and README wording. No new settings, translations, dependencies, visual feature or performance improvement is claimed by this release.
1.4.22 — 15 October 2026
- Added translated inline form errors, first-invalid-field focus and correction behavior for the local demo-access and preview/endpoint newsletter forms; retained native validity, endpoint no-JavaScript fallback and separate Kit validation.
- Styled the real newsletter checkbox with theme/focus states and a native forced-colors fallback.
- Refreshed the fictional sample media to a consistent 1280 × 720, 16:9 canvas while retaining editable originals and local optimized assets.
- Kept phone video controls in a compact two-row grid at narrow widths, preserving 44 px buttons, seek/time, optional captions/fullscreen and native fallback.
- Gated hidden playback-control height observation and measurement on actual control visibility.
- Declared the bundled local font's actual Latin character coverage; documented updating or removing that range when replacing the file, without changing the font or its licence.
- Added a buyer coding-agent manual and root instruction entry point; expanded the offline guides and complete German content example.
1.4.19 — 14 October 2026
- Added an optional video frame style setting. Minimal mode removes the header's three dots, product name/top label and bottom descriptive text bar while keeping the rounded frame, outline, ring and shadow; the supplied and omitted defaults retain the window presentation with both decorative bars.
- Kept the descriptive caption available to screen readers, the separate sample-media disclaimer visible, and the themed playback controls, loaded track captions, visible error status, native fallback, keyboard access and image-gallery mode available.
- Updated buyer customization, appearance, launch and upgrade guidance. Dependencies, licence and support terms remain unchanged.
1.4.17 — 14 October 2026
- Restored a theme-matched Get started popup with a local name/email demo-access scenario, native validation and an explicitly labelled confirmation linking to a configurable normal destination.
- Kept the scenario non-collecting, with no network submission, account or marketing-consent record. Fields and success state reset on close; success and closing preserve keyboard focus behavior.
- Preserved the separate newsletter section and the optional existing Kit/endpoint/preview signup presentation in the popup. Direct conversion and checkout links remain configurable.
- Shared the Get started action between desktop and mobile navigation, with visible-trigger/menu-button focus restoration and independent nested-confirmation closing.
- Updated buyer setup, customization, privacy, source-map, troubleshooting and launch instructions without changing dependencies, licence or support terms.
1.4.16 — 14 October 2026
- Enabled the non-collecting newsletter preview after JavaScript loads, with native email/required-checkbox validation and a form reset after valid demo submission. Controls remain disabled without JavaScript.
- Added a theme-matched, translated confirmation popup that explicitly identifies the result as a demo, with no actual send, subscription or saved/transmitted details. Close, Got it and Escape return focus to submit; both newsletter placements are supported.
- Updated buyer customization, privacy, setup, troubleshooting and launch instructions. Kit and endpoint responses, dependencies, licence and support terms remain unchanged.
1.4.15 — 14 October 2026
- Added optimized WebP copies of the original sample artwork, configuration-driven preview priority and a missing-font-preload safeguard for static export. Editable SVG originals remain included.
- Deferred rendering of later sections with responsive height estimates and print overrides. Enabled production CSS inlining and added gzip text responses to the local production preview; actual hosting still needs its own compression and cache settings.
- Removed unused dashboard icons, orphaned stylesheet rules and redundant missing-page content serialization. Retained all documented feature-card icons and conditional template options.
- Added focused font-preload and transport checks and updated customization, appearance, deployment, licensing and launch guidance. Dependencies, licence and support terms remain unchanged.
1.4.14 — 14 October 2026
- Corrected production environment-file loading for generated sitemap/robots URLs and added five focused regression test groups.
- Clarified setup, conversion-action examples, optional Kit settings, player instructions and historical defaults. Verified the current buyer ZIP filename in the README.
- Preserved the visual template, dependencies, licence and support terms. Version 1.4.13 was an intermediate local documentation-review archive.
1.4.12 — 14 October 2026
- Refined touch handling so a video tap reveals the floating bar and toggles playback, while swiping across the video does not open it. Touch slider dragging keeps controls available during adjustment.
- Kept keyboard playback tied to focus visibility and retained the existing floating-bar layout, configuration, dependencies, hosting, licence and support terms.
1.4.11 — 14 October 2026
- Moved themed video controls into an inset floating bar with pointer activity/keyboard visibility, playback idle hiding and immediate mouse/pen-leave hiding even when paused or ended. Touch taps give a three-second window without immediate hiding when the finger lifts; keyboard focus keeps controls available.
- Kept surface Play/Pause and brief feedback, returning the paused centered Play icon on phones when the bar hides and keeping brief feedback above it. Phone seeking uses a separate 24 px-high row; control buttons remain 44 px high.
- Moved supported automatic bottom captions above the visible bar while preserving authored cue positions; restored the custom retry bar below native controls on failure.
- Updated buyer customization, appearance, launch and upgrade guidance. Existing media settings, no autoplay,
preload="none", dependencies, hosting, licence and support terms remain unchanged.
1.4.10 — 14 October 2026
- Added click/tap Play/Pause across the video surface, with Enter/Space keyboard access and retained focus during playback.
- Added brief centered violet Play/Pause feedback after successful playback changes, with static feedback for reduced motion and the paused Play affordance returning afterward.
- Updated buyer customization, appearance, launch and upgrade guidance. Retained the bottom controls, native/error fallback, no autoplay,
preload="none", existing media configuration, dependencies, licence and support terms.
1.4.9 — 14 October 2026
- Enlarged workflow gallery screenshots by reducing panel padding to 20 px on larger screens and 18 px on tablet/phone widths.
- Preserved the alternating tilt, image proportions and fitting without cropping, and updated the appearance guide.
1.4.8 — 14 October 2026
- Included the required video byte-range helper in the buyer source archive.
- Added an early packaging check for scripts omitted from the reviewed allowlist.
- Retained the 1.4.7 player, sample media, styling, dependencies, licence and support terms.
1.4.7 — 14 October 2026
- Added a theme-matched bottom video bar with violet Play/Pause, seeking, elapsed/total time, mute, desktop volume, loaded captions and supported fullscreen; removed the duplicate caption-row control.
- Added a small playback halo that pauses with playback and respects reduced-motion preferences, with compact phone controls and native fallback before enhancement, without JavaScript and after media failure.
- Made an original short silent product clip the sample default, retaining configurable screenshot-gallery mode and optimized local poster/media.
- Added eight translated control labels to both supplied dictionaries and the German replacement example; updated buyer media, accessibility, deployment, troubleshooting, licence-material and upgrade guidance.
- Added video byte-range handling to the local production-preview helper and documented compatible static-host responses for reliable seeking and metadata loading.
- Retained no autoplay,
preload="none", existing dependencies, commercial licence, support, cookies, languages and static-export hosting.
1.4.6 — 14 October 2026
- Added the reusable video component to the buyer project map.
- Expanded the launch checklist for branded video controls, keyboard focus, replay, translated errors, both themes/languages and native playback without JavaScript.
- Retained the existing video, gallery, feature-card and newsletter customization instructions. Application behavior, dependencies, licence and support remain unchanged.
1.4.5 — 14 October 2026
- Added a subtle alternating static tilt to workflow screenshots while keeping their colored panels level.
- Centered gallery images with more even responsive padding and contained fitting that preserves their ratio without cropping.
- Documented the gallery styling and corrected the stylesheet map to include
src/styles/marketing.cssalongside base styling. - Existing media configuration, language/theme behavior, dependencies, licence and support remain unchanged.
1.4.4 — 14 October 2026
- Finalized video control focus handling and playback-completion behavior, with a mobile caption-spacing correction.
- Clarified buyer instructions for video customization and adding mixed image/text feature cards.
- Superseded the interim 1.4.3 snapshot; use 1.4.4 or a later release for these video controls.
1.4.3 — 14 October 2026
- Added a branded centered Play button to the paused local video preview and an accessible Play/Pause button beside its caption, with colors from the existing light/dark theme.
- Added translated playback labels and a play-error message to both dictionaries and the German replacement example.
- Preserved browser-native seeking, sound, captions and fullscreen, with no autoplay and
preload="none". - Updated buyer video customization and troubleshooting instructions. Image mode, dependencies, licence and support remain unchanged.
1.4.2 — 14 October 2026
- Clarified Kit inline Form creation, Save & Publish, both language slots, optional HTTPS Share URLs and compatible return-visitor behavior.
- Added practical checkbox/tag setup and confirmed/permission-filtered audience checks, with explicit treatment of accepted unchecked Kit signups.
- Expanded the buyer checklist for returning visitors, popup reopening, confirmation and unsubscribe in the buyer's own account; no provider account or actual subscription is supplied or asserted as tested.
- Restricted nonempty Kit share fallbacks to HTTPS, retaining custom domains and the option to omit the link. Page design, dependencies, licence and support remain unchanged.
1.4.1 — 14 October 2026
- Added one newsletter placement setting for a page section or the Get started popup, reusing preview, Kit and endpoint modes without mounting two copies at once.
- Kept exact
#newsletterCTA/navigation links working in popup placement and preserved ordinary external signup/checkout destinations. - Added translated signup-popup close labels and retained explicit Kit loading, consent/confirmation responsibilities, error/retry and hosted fallback behavior.
- Updated buyer customization, email, cookie, language, deployment, troubleshooting and launch instructions, plus the marketing preview. Affiliate links remain exclusively in the optional buyer setup guide.
- Retained default section placement, existing dependencies, static export, licence and support terms.
1.4.0 — 14 October 2026
- Replaced the simulated workspace with reusable configurable product screenshots or native local video, with editable captions and optional dark media.
- Centralized shared branding, logo, accent colors, media, cards, prices, social links, destinations and signup settings in
src/config/site.ts. - Generalized feature cards and replaced the inner workflow mockups with a flexible responsive image gallery, including a documented three-to-six-panel recipe.
- Added editable sample testimonial navigation and optional autoplay with pause, focus/hover/hidden-tab and reduced-motion handling.
- Kept direct configurable signup/checkout links and simplified the optional getting-started dialog into information with a real link; removed fake signup success.
- Added a non-collecting newsletter preview, optional click-to-load Kit inline JavaScript Form integration and a standard POST mode for a buyer-owned receiver. Added consent/confirmation/record-responsibility guidance and an optional disclosed Kit referral/direct-link choice in buyer documentation only.
- Added correct local preview response types for MP4/WebM video, WebVTT captions and WebP/AVIF/JPEG images so the documented media setup can be reviewed in production preview.
- Updated all affected customization, assets, language, cookie, SEO, deployment, troubleshooting and launch guides, plus the marketing preview.
- Retained two-language static pages, Light/Dark/System preferences, existing SEO model, runtime dependencies, commercial licence and support terms.
1.3.4 — 14 October 2026
- Expanded customization guidance for hero tracking, header sizing, footer labels and responsive wrapping.
- Clarified refreshing the built preview and the difference between a hidden preference banner and the persistent footer control.
- Documented the optional language-cookie duration limit and compact labels for regional language pairs, and clarified when canonical/alternate links are generated.
- Added the missing 1.3.1 changelog entry. No application, dependency, licence or hosting changes.
1.3.3 — 13 October 2026
- Aligned the footer navigation labels vertically with Cookie preferences while retaining 44 px minimum link heights.
- Allowed complete footer links to wrap at narrower widths instead of squeezing longer labels inside the row.
- Preserved the existing cookie button, preference dialog and storage behaviour.
1.3.2 — 13 October 2026
- Aligned the theme, language and menu controls with consistent 44px outer heights, including phone and tablet layouts.
- Kept the compact theme-control width and made its dropdown offset follow the resized trigger.
- Retained the 1.3.1 hero typography, language configuration, dependencies and licence.
1.3.1 — 13 October 2026
- Changed hero letter spacing to scale with font size and used normal tracking for the supplied Greek heading's system fallback.
- Kept existing heading sizes, weights and line heights, with no configuration, dependency or licence changes.
1.3.0 — 13 October 2026
- Added exactly two configurable languages, supplied with complete English/Greek text and a Forma-styled accessible language switcher.
- Added static language URLs, localized metadata, canonical/alternate language URLs and a build-generated language sitemap when the public origin is set.
- Separated text into stable primary/secondary files while keeping shared brand, destinations, prices and numeric sample data in configuration.
- Added optional language memory, explicit-URL priority and decision version 2; withdrawal attempts cleanup of both theme and language storage.
- Added content/configuration validation and directional layout support, with buyer checks for fonts, translations and right-to-left content.
- Added a dedicated language guide, complete German replacement example and updated customization, SEO, deployment, troubleshooting, upgrade and marketing materials.
- Retained frontend demonstration scope, static hosting, runtime dependencies, commercial licence and support terms.
1.2.0 — 13 October 2026
- Added a Forma-styled first-visit preference banner, detailed dialog and persistent footer entry for changing the appearance-storage decision.
- Added configurable preference copy, cookie name/version/lifetime and an optional privacy-policy link, with no analytics or advertising service installed.
- Made theme persistence conditional on valid optional permission; decline, withdrawal, missing/expired permission and migration stop optional use and attempt to remove the saved theme while current-page appearance controls stay usable.
- Added a dedicated cookies/preferences guide and updated customization, project map, launch, troubleshooting, deployment and upgrade instructions.
- Retained the local font, separate stylesheet, static export, existing runtime dependencies, commercial licence and support terms.
1.1.2 — 13 October 2026
- Added the complete Kitee single-project commercial template licence to the buyer bundle, editable source and supplied static export, with contextual links from the offline guides.
- Production builds now include the canonical template licence and runtime/font notices in
out/; packaging rejects missing or stale legal copies. - Clarified that non-Codester paid purchases include 12 months of template support, with an initial-response aim of two business days and documented scope/exclusions.
- Kept template licensing distinct from support terms and the separately licensed open-source runtime/font materials.
- Application features and source behaviour are unchanged from 1.1.1.
1.1.1 — 13 October 2026
- Made scrollable documentation code examples and tables keyboard-focusable, with visible focus indicators, so narrow-screen readers can scroll them without a pointer.
- Application features and source behaviour are unchanged from 1.1.0.
1.1.0 — 13 October 2026
- Added configurable demo/link actions for header, hero, pricing, final CTA and dialog success, plus optional yearly-specific plan destinations.
- Centralized additional interface copy, accessibility labels, language, appearance labels and workspace sample data.
- Added full offline HTML documentation with guide navigation, contents lists, worked customization examples, SEO instructions, troubleshooting and upgrade guidance.
- Updated the buyer quality guide into a practical launch checklist and retained release verification records separately from buyer instructions.
1.0.3 — 13 October 2026
- Corrected full-README links in the buyer bundle.
- Clarified terminal setup, Node/npm prerequisites, dependency installation and production metadata.
1.0.2 — 12 October 2026
- Added complete distributed runtime/font licence notices to documentation and the compiled export delivery.
1.0.1 — 12 October 2026
- Added buyer support guidance, publisher notices and the single source/docs/static-export buyer bundle.
1.0.0 — 12 October 2026
- Initial single-page landing template with responsive sections, Light/Dark/System, interactive sample workspace, pricing and FAQ.
Regenerate the documentation
Guide Markdown files in docs/ are the source of the corresponding HTML. After editing them, run:
npm run docs
npm run docs:check
The generator uses only Node.js built-in modules and produces self-contained offline pages. It does not require a separate documentation service, remote scripts or web fonts. Packaging generates the root entry and both documentation locations from these same sources to keep their links consistent.