# Developer tool landing page template (premium, $39)

> Landing page template for a developer tool or SaaS: a tilting product panel, a sorting scene, outputs, a review diff and pricing. One HTML file you own. Made by 8B (https://8b.com/), an AI website builder. Updated November 2026.

Developer tool landing page template for a SaaS or developer product sold to product teams: one HTML file with a product panel, seven spoken problem lines, a sorting scene, the outputs you ship to, a version history, a change review diff, customer quotes, a plan sheet, questions and a contact form. It opens on a tall grain poster plate that widens while a token panel tilts flat onto it, beside a dictionary entry for the word token. It is a single HTML file in pure HTML and CSS, and a GSAP version of the same page comes with it.

- Page: https://8b.com/templates/sikt/
- Price: $39, one-time license for your own and client sites; no resale or redistribution of the template.
- Preview: https://8b.com/templates/sikt/scroll.mp4 (scroll video) and https://8b.com/templates/sikt/desktop.webp. There is no live demo, and the template's code is not public.
- Template name: Sikt

## About

It suits a developer tool, an API or infrastructure product, a design system or tokens tool, or a SaaS for product and engineering teams that wants a calm, technical page instead of a gradient hero. Developer tool landing pages mostly need the same things on one scroll: what the product does in plain words, how it works, where its output goes, how a change is reviewed, what it costs per seat and a way to talk to the team. This page gives each its own section, and it shows the product as drawn HTML, a panel, a diff and a version list, so there are no screenshots to produce before launch.

The demo business is Sikt, an invented design token manager from a small studio in Gothenburg. Every product claim, token name, version, quote, price in euros and customer name is demo copy to replace. The panel, the diff rows and the versions are plain HTML lists, so a team in any field swaps in its own values: endpoints for an API, commands for a CLI, or releases for any tool with a history.

If you would rather not edit HTML at all, [8B, the AI website builder](https://8b.com/) designs a site from one sentence about your product, with more pages when you need them. This template is for people who want this exact design in their own hands: one index.html with its CSS and its motion inside, which you or a coding agent can edit and host anywhere, next to the docs and the app you already run.

## What a developer tool website needs

Developer tool landing pages that convert answer the same questions quickly. Here is how this template covers each of them.

- What it does, in one sentence. The opening heading says every design decision is named once, and a dictionary entry right below defines the product's core word.
- The problem, in the buyer's words. Seven short spoken lines go from 412 shades of blue to every product following a change.
- How it works. A sorting scene shows forty-eight loose values becoming six labelled families, so the product's promise is something you watch.
- Where the output goes. Four plates name the web, iOS, Android and Figma outputs, each with a line on what it contains.
- Trust in how changes are made. A version history of one token and a change request with a visual diff and an approval line show that every change is reviewed.
- Proof and a clear price. Five customer quotes, and one plan sheet with three columns and six shared rows, with the unit of billing stated in the heading.
- A way to talk to a person. The contact section has a walkthrough request form with a team size field, the address, email, phone and hours; connect the form before you go live.

What it does not have is docs, a sign-up or login flow, a live demo or a changelog feed: the panel, the diff and the versions are drawn in HTML, and the buttons lead to your own sign-up, docs and app, which stay on their own addresses.

## Design

- Palette: #0c1519 (deep petrol ink: the page ground, the header and the footer), #ece6e7 (mist white: headings and body text, and the lit spoken line), #ff5a43 (coral: the poster blob, buttons, the top edge of the plan underlay, the strike lines and the colour storm behind the contact eclipse), #45959f (sea teal: the token chips, the version plate and the output plates), #17323b (dark petrol: the ground of the grain plates, the Fjord family on the sorting board and the hover fill of outline buttons), #e6b8b0 (dusty pink: the quote plates, the FAQ plate, the contact card and the edge tags on photo plates), #a3979b (muted mauve: unlit lines, small labels and old values)
- Fonts: Stack Sans Headline (the light display headings, the spoken lines, plan names, version numbers, the old and new review values, the quotes and the footer wordmark), Stack Sans Text (body text, microtype labels, navigation, buttons, token names in the panel, plan prices and rows, and form fields)

A deep petrol ink page where grain plates carry the images, each labelled along its edges in small uppercase microtype like a print proof. The opening is two screens, a heading on the left with a tall poster plate on the right, then a dictionary entry on the left with the token panel. The problem is a column of seven spoken lines, the sorting scene is a sticky stage with a board of six rows and eight steps, the outputs are four offset plates, the versions sit beside a sticky plate, the review is four full-width rows, and the plans are one sheet with three columns and six shared rows. On phones the plate becomes a band in the lower half of the opening, the outputs sit in two columns, the token panel shows four of its six rows and the plan sheet keeps its three columns.

## Sections and motion

- **Navigation** (navigation): header with the wordmark and city, five links, Start free, and a full-screen menu on phones
- **Every design decision, named once.** (opening): two screens: a poster plate with the heading Every design decision, named once, then a dictionary entry for token and a token panel that tilts flat onto the widened plate. Motion: On load the plate stretches open from a shorter height and the heading block rises; the poster blob drifts and breathes in a loop, and a small diamond mark in the plate corner turns. On scroll the plate widens from portrait to landscape, its blob swells and sinks, its edge labels and mark slide out, and the token panel rises from a steep tilt until it lies flat and complete on the plate.
- **Why product teams need one source for design decisions** (problem): seven spoken lines from 412 shades of blue to every product following a change, each with a small turning chip. Motion: Each of the seven lines lights from mauve to mist as it reaches the middle of the screen, sliding in slightly from the right, while its chip turns from edge-on to face-on and its fill slides across.
- **Loose values in. Six families out.** (how-it-works): a sorting scene: forty-eight loose value tiles fly into six colour families on an eight-step scale. Motion: Forty-eight loose value tiles lie scattered and turned across a sticky stage; as you scroll they fly into their family column, one family after another, and settle into the eight-step scale, and the family labels draw in at the end.
- **One source. Four ways out.** (integrations): four offset poster plates for the outputs: CSS custom properties, Swift, Compose and Figma variables. Motion: The heading and the intro rise in one after the other, and each plate opens from its lower edge while its photo settles from slightly larger.
- **One token, four versions. Nobody had to ask.** (changelog): one token through four versions, v1.0 to v4.2, beside a sticky plate that changes colour with each. Motion: As each of the four versions reaches the middle it lights up while the others dim, the sticky plate beside the list changes its colour to that release's colour, and a soft band sweeps down through the plate.
- **Review a token change the way you review code.** (review): a change request with four tokens, each row striking the old value and wiping in the new one, then the approval line. Motion: Each row in turn strikes through its old value, wipes in the new value and covers the old swatch with the new one; the approval line closes the scene.
- **Teams who stopped asking which blue.** (testimonials): a continuously moving row of five customer quote plates. Motion: The label and the heading rise in one after the other, and the five quote plates move in a continuous row that pauses on hover and focus.
- **Made in an old shipyard office across from the Eriksberg crane.** (about): a wide photo plate of the Eriksberg crane that opens out above a heading, a note from the studio, the founders and three facts. Motion: The photo plate widens from a small proof to a wide plate while the photo counter-scales and develops from grey to colour, and the note's paragraphs, the founders line and the facts slide in from the left as they brighten.
- **Pay per editor. Everyone who reads is free.** (pricing): one plan sheet with Solo, Team and Studio in three columns and six shared rows, with a sliding coral-edged underlay and a Most teams label on Team. Motion: A coral grain underlay slides from the Solo column to the Team column as the sheet crosses the screen, and the Most teams label above Team draws in from the left.
- **Questions teams ask before they switch.** (faq): six questions in native accordions beside a small plate with an email line. Motion: The heading rises into place and the small plate beside the questions opens from its lower edge.
- **Bring us your 412 blues.** (contact): an eclipse plate with address, email, phone and hours beside a walkthrough request form. Motion: A black disc crosses the plate from beyond its left edge to its resting place, growing as it comes, while the colour storm behind it slides.
- **Product** (footer): footer with a tagline, product, company and legal links, a huge wordmark and the company line. Motion: The tagline rises into place and the rule under the wordmark draws in from its left end.

## Good for

- developer tool, API product or design system tool with a pricing sheet by seats
- SaaS for product, design or engineering teams that wants a calm, technical look
- product with several outputs or integrations that need one clear place on the page
- startup that wants a product panel and a diff view on its landing page instead of stock screenshots

## Questions

**What do I get for $39?** The developer tool landing page template as a single HTML file, index.html, in pure HTML and CSS, a GSAP build of the same page as index.gsap.html, a DESIGN.md with every colour, font and motion rule, an AGENTS.md for coding agents, the agent prompt and the design prompt from this page, and CREDITS.md for the photos and fonts. Updates to this template are included.

**Can I use this developer tool template for client sites?** Yes. One purchase lets you build as many sites as you like with it, for your own product or for clients, and change anything. What it does not allow is selling or giving away the template itself, as a template, theme or kit, or putting its source in a public repository.

**Can I show my own product instead of the token panel?** Yes. The panel, the diff, the version list and the sorting board are plain HTML, not images, so you change the words and values in place or ask a coding agent to rewrite them for your product, such as endpoints, commands or releases. If you have real screenshots, put them on the plates of the outputs section or beside the panel. The sorting scene is built for forty-eight tiles in six families, so a different count means adjusting that scene.

**How do I change the plans, prices and sign-up links?** The three plans are one HTML table with six shared rows, so you edit the names, prices and rows in place; the demo prices are in euros per editor a month and you write your own currency and unit. The plan buttons and every Start free button point to the contact section until you set them to your sign-up or checkout address. The contact form sends nothing until you connect a form service such as Formspree or Netlify Forms, or your CRM, and the pure HTML and CSS version shows no thank-you line after sending (the GSAP build writes one under the button), so point it at a thank-you page or add one.

**Will it work with Claude Code, Codex or Cursor?** Yes. Put index.html and AGENTS.md in your project and give the agent the prompt that comes with the template. AGENTS.md says which attributes the scroll motion reads, what to keep and what to replace, so the agent swaps the product claims, values, plans and photos without breaking the scenes.

**What do visitors see in Firefox or with reduced motion?** Firefox does not support scroll-driven animations yet, so it shows every section in its finished layout, as does any browser when the visitor asks for reduced motion. If the scroll motion must also play in Firefox, use the GSAP build, index.gsap.html, which loads GSAP, ScrollTrigger and Lenis from a CDN.
