Kippo - HTML Storefront & Digital-Commerce Template
1 of 1
Loading screenshot

What it is

Kippo is a hand-authored digital-commerce storefront template: fifty-eight HTML screens, one shared chrome, two colour modes, two directions, and no build step. Nothing installs, nothing compiles, nothing is fetched from a CDN — every font, library and picture lives inside the folder. Double-click index.html and the whole product runs.

It is built for selling digital goods: a storefront front page, a product detail flow, a cart and checkout, an order and invoice trail, and the account, payout, tax and community pages that sit around a purchase. Everything a buyer touches is here. Nothing in this package is an admin panel — there is no dashboard, no reporting view and no back office.

The three switches

  • Light and dark — one token swap on <html data-theme>. A single stylesheet re-values the palette; there is no second CSS file anywhere in the package, so a component cannot look right in one mode and wrong in the other.
  • English and Arabic — dir="rtl" mirrors the entire layout, because every rule uses logical properties (margin-inline-start, inset-inline-end) instead of left and right.
  • Motion — honours prefers-reduced-motion, and data-motion="off" on the <html> element switches entrance animations off for still captures.

Fits the screen it is on

Viewport behaviour is hand-authored, not inherited from a framework. assets/css/responsive.css loads last on every page and bends the shared chrome in six documented passes: at 1100px the navigation folds into the dialog trigger and the bento panels pair up, at 900px the hero art drops under the copy, at 720px the layout goes single column and the footer stacks, the two-column commerce and content grids collapse in one addressable place, and at 560px the header keeps only the wordmark, the menu trigger and the colour control. Page-specific tiers stay inside their own sheet beside the rules they bend, and because every rule uses logical properties, the same passes mirror correctly in Arabic.

Screens

group screens
Entry & auth index, home, login, register, forgot-password, reset-password, verify-email, onboarding, account, 404
Storefront & discovery product, category, search, discover, compare, bundles, wishlist, reviews, storefront, library, discounts, creators, affiliate
Purchase & money cart, checkout, order, orders, order-confirmation, invoice, refunds, payouts, taxes, security, status
Shop & community add-product, notifications, community, thread, roadmap, changelog, integrations, api, pricing, customers, team
Content & support blog, article, help, help-article, about, contact, features, case-studies, press, careers
Company & legal legal, cookies, accessibility
Starting point _starter.html — copy it to add a screen; the chrome comes with it

The group rows total 58 screens (10 / 13 / 11 / 11 / 10 / 3).

What ships with the item

  • 59 HTML files — 58 screens plus _starter.html, one file each, no templating engine
  • 11 stylesheets, loaded in one fixed order: base, shell, components, commerce, content, home, app, pages, assistant, theme modes, responsive
  • 19 scripts for the behaviours: chrome, tabs, rails, galleries, checkout flow, theme, charts, motion, assistant
  • Vendored libraries as local files — GSAP 3.15.0 with ScrollTrigger, Chart.js 4.4.7, Swiper 11.2.10, Bootstrap Icons 1.11.3 (MIT / GreenSock standard licence; licence texts are kept beside each file)
  • 24 self-hosted woff2 font subsets under the SIL Open Font License 1.1
  • Original art — brand marks, product covers, avatars, mascot frames, screenshots and a social card, all local files, no hotlinks
  • SEO plumbing — sitemap.xml, robots.txt, og: card, plus vercel.json and .htaccess carrying the same cache and security contract for two hosts
  • A 12-chapter manual — design system, theming, components, behaviour, pages, mascot, accessibility, tooling, AI customization guide, deploy, support
  • 14 paste-ready AI prompts inside that guide, in one copy-block per job: the ground-rules preamble, then brand and colour ×2, type and tokens, components ×2, pages and navigation, behaviour and motion, mascot and frames, screenshots and the directory, RTL and copy, accessibility audit, QA and validation, hosting and release

Making it yours

Change the brand by changing tokens, not rules. The colour families live in assets/css/theme-modes.css; the type scale and faces live in assets/css/main.css. Swap the copy in the HTML, swap the art in assets/images/. The shared chrome — header, side rails, footer — is plain markup repeated in every page, so a chrome edit is one edit applied to all pages. The folder is complete in itself: nothing outside it is needed to change anything inside it.

Requirements

None. No server language, no database, no package manager, no compiler. Any static host works, and the pages also open straight from disk. If you want a working URL bar while editing, serve the folder with any static server.

Browser support

Chrome 111+, Edge 111+, Firefox 121+, Safari 16.2+, Opera 97+. Legacy Edge and Internet Explorer are not supported. Advanced effects (View Transitions on the theme swap) are feature-detected and simply stay unused where absent.

Honest limits

  • It is a front end. No cart logic, payment processing, or accounts exist until you wire them to your own backend or checkout provider.
  • There is no dashboard. No admin panel, no reporting screen, no analytics view ships. Seller-side work is limited to the storefront pages that carry it (product entry, orders, customers), and the store's back office is a separate product.
  • No CSS framework is used, so there is no Bootstrap/Tailwind API to lean on; the grid and utilities are hand-authored.
  • No PSD or Figma source ships with the item — the deliverable is the running HTML, CSS, JS, fonts and images.
  • The chrome is repeated markup by design. It is fast to read and portable, and it means a header change touches every page; the manual's Tooling chapter ships the checks that make that safe.

Documentation & support

The manual covers the design system, theming, every component, the behaviour of each script, accessibility, tooling, deployment and troubleshooting. Support is answered from this profile. Scope: the template as shipped. Out of scope: installation on your server, third-party plugins, and custom development work.