Skip to main content

Product

SiteKit,
from every angle.

SiteKit is the runtime behind editorial public sites like Arpeta Codex: chapters, artifacts, forms, and theme DNA stay editable without forking a new codebase per brand.

Product definition

Composable Public Site Runtime

“Separates brand chrome and chapter storytelling from one-off hardcoded microsites.”

Lets organisations publish branded public sites — chapters, products, forms — from a governed CMS runtime.

Key capabilities

Themeable public surfacesSection variants per brandLocale-aware chapter sites

Product modules

Which modules make up SiteKit?

Each module focuses on a specific need and can be used together or independently.

Themes & chrome

Header, footer, background, and token presets that define a site’s visual DNA.

Page & section CMS

Composes chapters from typed sections and variants instead of one-off pages.

Product catalog pages

Publishes artifact/PDP surfaces from product entries and extra JSON packs.

Forms & vault

Collects inquiries into governed form definitions with chapter handoff.

Locale packs

Keeps TR and EN chapter content and navigation in sync without duplicate codebases.

Publish controls

Controls what is live per site domain and locale.

Technology architecture

A secure, scalable foundation.

The product runs on complementary layers from experience to data.

Composable
Chapters assemble from reusable section variants — not hardwired one-offs.
Brand DNA
Theme + chrome presets keep visual language consistent across pages.
Locale pairs
TR and EN chapter slugs stay mapped so language switching does not 404.
Product depth
Artifact detail can carry bilingual packs without duplicating the PDP shell.

Architecture layers

Site domain bindingLayer 01
Page/section JSON modelsLayer 02
Theme token presetsLayer 03
Next.js public runtimeLayer 04

AI capabilities

Where does AI add measurable value?

AI is used only where benefit is measurable, traceable, and under user control.

Content structure

Keeps storytelling in CMS sections so design systems can evolve without rewriting routes.

Locale discipline

Supports TR/EN chapter pairs and locale-aware product packs.

Brand presets

Maps theme tokens and chrome components to a named visual DNA (e.g. arpetaCodex).

Key figures

Essentials about SiteKit.

Indicators that summarise scope and operational value.

CMS

Section-driven pages

TR|EN

Locale-aware sites

DNA

Theme + chrome presets

Fit

Who is it for?

We evaluate strong-fit scenarios and cases where another approach may be better.

A strong fit when

You need a governed public site with chapters, products, and brand themes — not a disposable landing page.

Consider another path when

A single static page with no CMS lifecycle is enough.

Let’s review your project

How can SiteKit adapt to your business?

Let’s assess your needs, current systems, and operational goals together.

Product ecosystem

Explore other Arpeta products.

Each product can run independently; together they share data, integration, and workflow layers when needed.