01 / 15 · Start here

Start here

Welcome to Forma, a single-page SaaS landing-page template published by Kitee. This guide takes you from the downloaded ZIP to your first local preview. Read the HTML guides directly in a browser; they work offline and do not need a documentation server.

What you receive

Folder or filePurpose
START-HERE.htmlOpen this first in your browser. Its navigation leads to all guides.
source/Editable Next.js project. Run every project command inside this folder.
static-export/Generic prebuilt demonstration. Customize and rebuild the source before publishing your brand.
docs/Complete browser-readable HTML guides, Markdown originals and third-party notices.
NOTICE.txtPublisher and ownership notice.
LICENSE.txtComplete commercial template licence; read it before using Forma for a project.

When reading a guide from source/docs/, file paths such as src/config/site.ts are relative to source/. When working from a standalone source download or repository, use the folder containing package.json instead.

Understand the template scope

Forma includes a responsive hero, customizable image/video product preview, general feature cards, image workflow gallery, sample testimonials with navigation and optional autoplay, monthly/yearly pricing, FAQ, conversion links, optional email signup, footer, Light/Dark/System appearance, two configurable languages and a preference-storage manager. English and Greek examples use /en/ and /el/; buyers can replace the pair and provide their translations. Its source is Next.js with TypeScript and separate CSS files.

The supplied media and testimonials are sample content. The header's Get started popup demonstrates a local name/email access flow: valid input reveals an explicitly labelled demo confirmation and a configurable link to the product preview. Nothing is sent or saved, and closing resets the scenario. It does not create an account, subscription or protected demo; the product preview remains directly accessible. See Customization.

You can configure the source yourself or ask a coding agent to do it for your licensed project. Give the agent your product brief and Agent customization manual; the manual is written as instructions for the agent to read, implement and verify, with the correct files and integration limits.

Email signup separately defaults to a non-collecting page-section preview. A valid email and checked sample consent box show a labelled demo confirmation and reset the form; no subscription is created or entered details saved/transmitted. Controls stay disabled without JavaScript. Buyers can connect Forma-styled fields to Kit (kit-native), embed a Kit-designed Form (kit), or post to their own compatible receiver (endpoint). Newsletter signup can use a section or a dedicated signup popup. Independently, demoAccess.mode: 'kit' can add optional mailing-list permission to the name/email demo-access popup: unchecked continues without submitting to Kit. The continuation is still a public link, not authentication. See Email signup and Kit for complete setup and copy-and-paste examples.

A first-party cookie remembers the optional-storage decision; theme and language are remembered only with valid permission. Declining still allows switching, and the language in an explicit URL takes priority. No analytics, advertising or automatic translation service is installed. There is no authentication, payment processing, subscriber database, email delivery backend or CMS. Conversion links can point to your own real service.

Sample prices, people, testimonials, product claims and artwork are placeholders. Replace them with accurate information before launch.

The default product preview is a short original silent video with a themed control bar and no autoplay. An image gallery is also available: change siteSettings.preview.mode to 'images' and rebuild. Both modes use local assets and the same configuration entry point. The sample clip describes a fictional product, not a working application. See Product screenshots and video for replacing media, captions and the translated controls.

The included commercial licence covers one website project for your own use or one client's use, with commercial use and customization permitted within its terms. A different licence expressly supplied with your purchase governs where it conflicts; this release does not automatically rewrite an earlier buyer's licence. Third-party software/fonts retain their own licences. Read Licensing for the material covered and Support for the separate included support service.

Before you start

You need:

  • A code editor that can edit plain-text TypeScript and CSS files. Basic familiarity with files, a terminal and simple code edits is helpful; this is a code template rather than a drag-and-drop builder.
  • Node.js 22.13 or later within version 22, or Node.js 24 or later, with npm 10 or newer. Node.js 24 is the recommended starting point. The exact requirements are in package.json.
  • Internet access for the first dependency installation from the npm registry. The documentation and bundled font do not require external services.
  • A browser for reviewing the page.

Install a compatible Node.js version with npm from the official Node.js download page if needed. A global Next.js installation is unnecessary.

1. Extract the ZIP and open the correct folder

Extract the entire ZIP into a folder you can edit. Do not run commands inside the compressed archive. Keep an untouched copy of the download for comparison and updates.

Open the extracted source/ folder in your editor. You should see package.json, package-lock.json, src/, public/ and scripts/ at its top level.

On Windows, open source/ in File Explorer, click the address bar, type powershell and press Enter. The terminal opens in that folder. On macOS or Linux, open Terminal and change into your actual source folder:

cd "/full/path/to/your/extracted-bundle/source"

Replace the example path with your own. If your editor has an integrated terminal, open it after opening source/ and confirm its current folder contains package.json.

Expected result: your terminal is in the editable project folder, not the buyer bundle's outer folder or static-export/.

2. Check Node.js and npm

node --version
npm --version

Both commands should print a version compatible with the requirements above. If a command is unavailable, install Node.js with npm and reopen the terminal before checking again.

On Windows, if PowerShell says npm.ps1 cannot run because scripts are disabled, use npm.cmd in place of npm for every command in these guides:

npm.cmd --version
npm.cmd ci
npm.cmd run dev

No PowerShell execution-policy change is required.

3. Install the locked dependencies

npm ci

Wait until the command finishes successfully and the terminal prompt returns. This downloads the dependencies recorded in package-lock.json and creates node_modules/. Installation time varies with your network and computer. Keep the supplied lockfile; do not replace npm ci with a dependency upgrade as part of first setup.

Expected result: installation completes without an error. If it reports a network or compatibility failure, use Troubleshooting before continuing.

4. Start the development preview

npm run dev

Open http://127.0.0.1:3100 in your browser. This address is local to your computer; it is not your public website. Keep the terminal running while editing. Press Ctrl+C in that terminal when you want to stop the server.

Expected result: the default Forma landing page appears with its hero, product preview and sections below it. Use the language switcher to visit both /en/ and /el/. On a fresh visit, review the cookie banner and try Necessary only or Allow preferences. Try Light/Dark/System, testimonial navigation/pause, monthly/yearly pricing and FAQ. The footer reopens Cookie preferences. The header's Get started button opens the local name/email demo-access popup; pricing and final signup buttons lead to the separate, clearly labelled newsletter preview. Neither demo sends email or saves the entered details.

5. Make your first edit

Open src/config/site.ts. Change the product name:

name: 'Your Product',

Save the file and return to the development preview. The shared product name should update. This changes the text name, not every translated claim or image. The logo, brand colors, media, social links and CTA settings live in this same file; the complete branding checklist is in Customization.

Change one thing at a time and inspect the result at a desktop and phone width. Preserve the commas, quotation marks and property names in the configuration. TypeScript checks help catch accidental mistakes.

6. Check the production version

Stop the development server with Ctrl+C before starting the production preview; both use port 3100 by default.

npm run format
npm run check
npm run start

format applies Prettier across the editable project under its ignore rules; review its changes. check validates both language settings/content files, generated docs, formatting, lint, TypeScript, tests and a production build. Wait for success. The build creates out/; start serves that optimized output at http://127.0.0.1:3100. Source edits do not refresh production output: rebuild after changes.

If you edit guide Markdown, run npm run docs to regenerate its HTML before check. Ordinary landing-page content edits do not require regenerating documentation.

Expected result: the commands pass and the optimized page loads. For launch, customize all content, set the real public site URL and follow Build and deploy. The local preview is not a production hosting service.

Choose your next task

I want to…Guide
Find the right file or commandProject map and commands
Have a coding agent configure the template from my briefInstructions for your coding agent
Edit branding, copy, pricing, FAQ or signup linksContent and conversion links
Choose two languages or replace their translationsLanguages and translations
Change colours, themes, font or imagesAppearance and assets
Connect email signup to my own Kit account or endpointEmail signup and Kit
Configure theme/language storage and visitor choicesCookies and preferences
Set browser titles, social previews and the real site URLSEO and site settings
Build and upload my siteBuild and deploy
Check everything before launchLaunch checklist
Resolve an errorTroubleshooting
Apply a later Forma releaseUpdates and changelog
Request help or review purchase rightsSupport and Licensing