Appearance and assets
Forma keeps its base layout/theme styling in src/app/globals.css, reusable media/card styling in src/styles/marketing.css, signup/demo-form details in src/styles/newsletter.css, and logo variants/social links in src/styles/branding.css. Shared accent colors, logo/media paths and dimensions are in src/config/site.ts. Components use a small number of calculated values for configured colors and media aspect ratios. Ordinary rebranding does not require editing components.
On this page
Edit the brand colors
For an ordinary rebrand, edit siteSettings.brand.colors.light and .dark in src/config/site.ts. Each theme has five required accent fields:
light: {
accent: '#6554d8',
accentHover: '#5543c2',
accentSoft: '#eeebfc',
accentText: '#5643bd',
ring: '#6554d8',
},
Edit the matching dark fields separately, choosing colors readable on the dark surfaces. These shared settings feed the accent CSS tokens; changing components is unnecessary. The same file also contains the visible product name, logo, favicon and social image references.
Expected result: action colors, accent surfaces/text and focus rings use the configured theme palette. Inspect normal, hover and focused controls in both appearances. Keep contrast and visible focus; a syntactically valid color is not necessarily readable.
Deeper stylesheet changes
At the top of globals.css, :root defines the light palette and :root[data-theme='dark'] defines the dark palette. Common tokens include:
| Token | Controls |
|---|---|
--bg | Main page background |
--surface, --surface-soft, --surface-raised | Cards and raised interface surfaces |
--text, --muted, --faint | Main, secondary and quieter text |
--border | Dividers and outlines |
--accent, --accent-hover | Main action colours |
--accent-soft, --accent-text | Soft accent backgrounds and accent text |
--ring | Keyboard focus indicator |
Use the stylesheet for page backgrounds, surfaces, body text, borders and deeper layout changes. Edit the existing tokens rather than adding competing blocks. The five configured accent tokens come from siteSettings.brand.colors; change them there for a consistent rebrand. Review both palettes after any change.
Production builds use Next.js's experimental inlineCss: true setting in next.config.mjs. Source styles remain in their separate CSS files; the build places the required styles in each page's HTML, including the exported missing-page document, so their application does not require JavaScript. This trades larger HTML for fewer separate stylesheet requests; those inlined styles cannot be cached as a separate stylesheet across page visits. If repeat-visit stylesheet caching is a higher priority for your site, set only inlineCss to false, preserve the other configuration, rebuild and compare production results. After changing this setting, check both languages/themes, native video without JavaScript, the missing page and print preview.
Light, Dark and System
The header provides a quick appearance toggle and a menu with Light, Dark and System. System is the default when there is no permitted saved preference and follows the browser's prefers-color-scheme setting.
Choosing Light or Dark applies that explicit preference. Choosing System restores automatic behaviour. The quick toggle switches the resolved appearance; it does not disable the System option. These controls work even when the visitor declines appearance storage.
The preference uses the browser's forma.theme local-storage key only with valid allow permission from the cookie-preference manager. Without permission, the current page keeps the choice in memory and a new load starts from System. The footer reopens the preference dialog; withdrawal stops optional reads/writes and attempts to remove stored appearance immediately. If the browser blocks saving a new decision, the dialog explains the current-visit fallback; a later load may see an earlier saved choice. Storage restrictions can also prevent physical cleanup. The preference does not sync between devices or accounts. No subscriber details or consent records are persisted there.
Relevant files are src/lib/theme.ts and src/components/theme-controls.tsx, with translated appearance/cookies text in both content files, consent helpers in src/lib/cookies.ts and shared settings in src/config/cookies.ts. Keep the before-paint initialization in document-frame.tsx when restructuring; removing it can flash the wrong palette or bypass checks. Changing language loads another page, so an unpermitted in-memory theme returns to System; a valid saved preference restores.
After changes, test saved Light and Dark after granting permission, decline and withdrawal, System when the browser's colour scheme changes, and operation when storage is unavailable. See Cookies and preferences for the storage inventory and configuration, and the Launch checklist for browser checks.
Replace the logo and icons
The visible logo reads siteSettings.brand.logo. To replace it, add your own licensed file to public/ and edit the configuration:
logo: {
src: '/brand/logo.svg',
darkSrc: '/brand/logo-dark.svg',
width: 30,
height: 30,
showName: true,
},
Those URLs refer to public/brand/logo.svg and logo-dark.svg. darkSrc is optional. Set width/height to your logo's intended ratio and inspect its size in the compact header/footer. showName: false hides the adjacent product-name text when your artwork already contains it. The shared logo component is src/components/brand-logo.tsx; no SVG path editing is needed for this normal setup.
The favicon is separately configured by brand.favicon, initially /icon.svg. Configure brand.socialImage too; SEO explains its dimensions and metadata. The visible mark, browser icon and sharing artwork can be different files.
Interface icons remain code-native SVGs. Feature cards use one of the supported check, arrow, spark, shield, link or plus names in their shared settings. There is no icon-pack dependency or image-upload service.
Add images and public files
Place public assets in public/. A file at public/product.webp is referenced in code as /product.webp, without public in the URL.
Use an asset you own or are licensed to publish. Configured product, workflow and feature images require meaningful, nonempty alternative text in both content dictionaries; validation rejects empty text. Thumbnail and testimonial-avatar decorative alternatives are handled by the existing components. Use empty alternative text only for purely decorative images you add through custom markup. Reserve each image's size or aspect ratio to avoid layout shifts.
The supplied product SVGs, their displayed WebP copies and the silent sample video use a 1280 × 720 (16:9) canvas. Keep the actual dimensions of your replacement files in shared configuration; the sample ratio is a useful consistent starting point, not a reason to stretch or crop unrelated artwork. The social-sharing image has its separate 1200 × 630 dimensions.
The supplied product/gallery samples display optimized local WebP images of the original illustrations, with a short original silent clip used by the default video preview. Their editable SVG originals remain in public/product/ as overview.svg, detail.svg and report.svg. Replace the configured media with assets you own, using siteSettings.preview and the image settings in siteSettings.sections. No remote screenshot or upload service is required.
For screenshots, prefer an appropriately sized, compressed WebP file. SVG is still supported and suits compact vector artwork such as logos; a complicated screen illustration can cost more to render than its compressed raster copy. Static export disables the built-in server image optimizer in next.config.mjs, so resize and compress raster files before adding them. Export near the largest size you need and compare file size with readable detail. Avoid shipping a huge source image merely to display a small card.
Provide width/height matching each configured image's actual ratio. Optional darkSrc selects another local asset for the resolved dark theme; omit it when one image serves both themes. The preview stage reserves the first image's ratio and fits the other images inside it. The displayed product screenshot loads eagerly with high priority; below-the-fold feature/workflow images and gallery thumbnails load lazily. Check mobile layouts and asset URLs in the built production export, not only development.
Landing pages preload the configured video poster, or the first product image when it has no darkSrc. This follows siteSettings.preview, so replacing its local path needs no separate preload edit. Separate dark-image variants remain supported. The exported missing-page document does not preload product media. Keep the first image/poster small enough for a mobile connection; priority does not make a large file inexpensive.
For a video, use an optimized local file, poster and optional WebVTT captions. Forma does not autoplay it and uses preload="none". Keep audio/video alternatives accessible and verify browser support for your chosen media format. Customization gives image/video recipes, translated control labels and playback checks.
Video frame styles
Change siteSettings.preview.video.frameStyle in src/config/site.ts to choose the video's presentation. 'window' keeps the decorative browser header and bottom descriptive caption bar. 'minimal' removes the header's three dots, product name/top label and the bottom descriptive text bar, including that bar's space, padding and dividing border. Both styles keep the same rounded outer frame, outline, ring and shadow, including the existing smaller frame treatment on phones. The descriptive caption remains available to screen readers without being visible in minimal mode. The sample-media disclaimer below the preview remains visible. Omitting the setting has the same effect as 'window'. Rebuild after changing it; no component edit or new asset is needed.
The video retains its own media dimensions, themed controls, loaded video-track captions, focus styles and native/error fallback in either presentation. A playback-error status still appears visibly when needed. This setting applies only to video mode and does not crop any frame baked into the video or poster. For deeper adjustments, compare the window and minimal presentation rules in src/styles/marketing.css without removing the player's control or focus rules. Check both themes, narrow screens and long translated text, including failure messages.
Video player colors and motion
Forma's centered Play affordance, brief Play/Pause feedback, floating-bar Play/Pause button and slider progress use the configured siteSettings.brand.colors.light/.dark accent palette. The supplied accents are violet. The bar's background, borders and supporting controls use the existing surface, border and accent-text tokens. Rebrand the shared settings rather than editing the player component; deeper styling is in src/styles/marketing.css under .forma-video-player and its control rules. Review both themes against your actual poster, including readable icons and visible keyboard focus.
Clicking or tapping the video surface toggles playback. An icon briefly confirms a successful Play or Pause, for about 0.6 seconds, without intercepting further clicks. It disappears after feedback finishes. The paused centered Play affordance returns; at phone widths it hides while the bar is visible and returns when the paused bar hides. With reduced motion requested, the same brief feedback is static. The video surface remains keyboard-focusable during playback, with Enter or Space as alternatives to a pointer. No additional media setting is required.
The bar floats inside the lower edge of the video and appears with pointer activity or keyboard-visible focus. In the page, mouse/pen hovering keeps it visible when paused or ended; leaving hides it even when stopped. During in-page playback, about three seconds of pointer inactivity hides it too. A touch tap gives about three seconds of in-page visibility whether playing or paused, without immediate hiding when the finger lifts. In fullscreen on supported desktop or mobile browsers, entering reveals the bar, then about two seconds of inactivity hides it whether playing, paused or ended. Mouse/pen movement, a tap or releasing a held control restarts that timer. Holding or dragging a control keeps it visible until release/cancellation; a window losing focus clears a held pointer interaction. Keyboard navigation/focus keeps controls available in either view, while a mouse/touch click alone does not pin the bar. Exiting fullscreen restores the in-page behavior. Preserve the shared visibility state and keyboard-focus handling when customizing; native fallback controls retain browser-controlled behavior.
While video is playing, a small CSS halo pulses around the bottom Play/Pause button. It stops when paused and is disabled for prefers-reduced-motion. The effect uses opacity and transform on a small decorative element, without a JavaScript animation library. To remove it for everyone, change the existing playing-state .forma-video-toggle::after animation to none, preserving the focus and control styles.
At phone widths of 600 px or less, the control bar uses a compact two-row layout: seeking and elapsed/total time share the 24 px-high first row; the available Play/Pause, mute, captions and fullscreen buttons stay grouped at the start of the second row with 8 px gaps and 44 px targets. Optional buttons leave no reserved empty slots when absent. The desktop volume slider is hidden. The .forma-video-progress wrapper keeps the first row together; it uses display: contents above phone widths to preserve the desktop bar. Keep these layout rules together when customizing; test the smallest width with captions and fullscreen both available, rather than shrinking the button targets. The brief 40 px playback-feedback icon sits above the bar. The paused centered Play icon is hidden only while the phone bar is visible, avoiding overlap. Visitors can still mute/unmute; device controls may govern the sound level. Captions require a successfully loaded configured track, and fullscreen is shown only with standard browser support.
Automatically positioned bottom captions move above the visible overlay bar where the browser supports this adjustment, then return when it hides. Authored WebVTT cue positions are preserved rather than overridden. Check your own captions and poster at phone widths, fullscreen and 200% zoom, with controls visible and hidden. Native browser caption settings and support can affect their placement.
Native browser controls are retained before the JavaScript enhancement, without JavaScript and after a playback failure. On failure the custom retry bar sits below the video so it does not cover native controls. Their appearance is browser-controlled; Forma's themed bar does not recolor that fallback toolbar. No external player library or playback service is included.
Font and language coverage
Manrope is bundled locally at src/assets/manrope-latin-wght-normal.woff2 and loaded with next/font/local in src/components/document-frame.tsx. It uses --font-manrope. Visitors do not need a remote font service for the supplied font.
After building, scripts/site-files.mjs calls scripts/font-preload.mjs to add a missing early font preload to the known root, language and missing-page HTML files. The helper derives the actual generated URL when the export contains exactly one safe WOFF2 font; it preserves an existing matching preload and makes no guess when there are no fonts or several choices. The supplied font needs no additional setting or hardcoded generated filename. If you change the font setup, inspect the production page source and network panel: the intended local font should start early, with no duplicate transfer for the same font caused by mismatched preload URLs. This does not change the font licence, glyph coverage or fallback behavior.
The supplied font subset is Latin. Its localFont declarations include a unicode-range matching that file's character coverage, so other scripts use their fallback rather than waiting for an inapplicable font. Greek example content uses system font fallbacks; appearance varies by device. For another writing system or more consistent typography, use an appropriately licensed local font with the required glyphs, update the localFont source in document-frame.tsx, and update or remove the existing unicode-range when the replacement has different coverage. Keeping the old range can prevent the replacement from being used for its additional characters. Check both languages after building; fallbacks are not a guarantee of complete coverage or consistent typography for every language. See Languages for direction and replacement-language checks.
Retain MANROPE-LICENSE.txt when distributing the bundled font. Review the licence, weights, glyph coverage and file size of any replacement.
Layout and responsive rules
The .container class controls the main content width. Component rules and media queries in globals.css control the base section spacing and mobile layout; marketing.css styles the reusable product preview, feature cards and workflow gallery. Start by editing existing values rather than adding duplicate rules with conflicting selectors.
Review at roughly 320 px, 390 px, tablet and desktop widths, plus 200% zoom. Long headlines, navigation labels, plan names and translated copy can require spacing changes. Preserve reduced-motion support and comfortable targets for touch and keyboard users.
Rendering sections as they approach the viewport
At the beginning of src/styles/marketing.css, seven later sections use content-visibility: auto: features, workflow, testimonials, pricing, FAQ, newsletter and the final CTA. Supporting browsers can defer offscreen rendering while their content remains in the document. The hero, product preview and footer are excluded. Browsers that do not support the property render normally; no JavaScript scroll observer is used.
contain-intrinsic-block-size: auto var(--section-estimate, 350px) reserves an estimated section height before its content is rendered. The auto value lets a supporting browser remember the rendered height. Existing section selectors and the 800 px media query set larger estimates for the supplied content. If you add many cards, gallery rows or substantially longer translations, compare the actual section heights at desktop and phone widths and adjust the relevant --section-estimate values in those existing rules. An estimate is a layout placeholder, not a fixed limit on the content.
After a layout change, test scrolling both ways, direct section URLs, navigation anchors, keyboard traversal, browser Find and 200% zoom in your target browsers. Print rules explicitly restore visible rendering and remove the estimated size; inspect print preview too. See the Launch checklist for production checks.
The optional video caption track uses a compact, high-contrast video::cue treatment in src/styles/marketing.css. Browser caption preferences and supported cue styling can vary; check readability with your own track at phone widths and 200% zoom.
Workflow gallery panels
The gallery's colored outer panels stay level; their screenshots alternate between a static −2° and +2° tilt. At phone widths of 600 px or less, the tilt becomes −1.5° and +1.5°. There is no rotation animation. Images fit within the centered panel space while preserving their ratio rather than being cropped.
These rules are in src/styles/marketing.css, under .forma-workflow-image. Panel padding is 20 px on larger screens and 18 px at widths of 800 px or less. Reducing this padding gives the screenshot more room inside the same colored panel. The reserved panel ratio stays consistent across a row; an image with a different ratio can leave more empty space along one axis. Use clear, optimized screenshots and review their readability at phone sizes.
To keep screenshots level, change the existing transform declaration for .forma-workflow-image img to none. Keep the fitting and padding rules so the image remains centered and contained. Media paths, dimensions and optional dark versions remain in siteSettings.sections.workflow.steps; the Customization guide explains adding more panels without editing components.
Hero typography
The hero uses font-relative letter spacing, so tracking scales with the heading size. The supplied Greek heading uses normal tracking through :root:lang(el) .hero h1 because it falls back to a system font. If you replace that font or configure another language, review the actual glyph spacing in both languages before adjusting the existing heading rules. Font size alone does not determine suitable tracking; avoid applying tightly spaced Latin styling to every writing system.
Header and footer controls
The theme group, language trigger, mobile menu button and header action share a 44 px outer or minimum height. The theme group's two compact controls sit inside its border; this does not mean each control is a 44 × 44 px square. Preserve their alignment and visible focus when changing sizing.
Footer links and Cookie preferences have vertically centered labels and a 44 px minimum height. When space is tight, complete navigation items can move onto another row. Desktop/tablet rows align toward the outer edge opposite the brand; phone rows start alongside the brand. This wrapping is intentional. Keep translated labels concise and review both language pages rather than forcing manual line breaks for one screen width. See Customization for the text fields.
For a right-to-left language, set its direction in src/config/languages.ts. Forma applies document direction and directional stylesheet rules; review translated cards, media captions, testimonial controls, mixed-script numbers and navigation after customization. Do not force all translated content left-to-right to hide a layout problem.
If you change the background palette, update the two viewport.themeColor values in src/app/[[...lang]]/layout.tsx so browser interface colours match both appearances. These values do not change page CSS automatically.