Skip to content

Glossary

Every term the documentation relies on, one line each, linking to the concept page that explains it.

Seventy-seven terms, one line each, grouped by the story that explains them and linked to the exact section. A line here disambiguates — it doesn't repeat the explanation on the other end of the link.

Structure

base type
The underlying shape a content type is built on top of.
category
A hierarchical taxonomy term attached to content, distinct from a flat tag.
collection
A named, filterable set of content consumed through a feed.
content node
One row in the site tree, addressable by its own path.
content type
The schema a piece of content is authored against.
feed
A configured, filtered list of content a module or collection pulls for display.
field
One named, typed value on a content type's schema — the fields half of a page.
field type
What a field becomes in storage and in its admin editing control.
layout document
The layout half of a page: regions, sections, columns and modules.
locale
One configured language or region a site can render content in.
media item
One uploaded file tracked in the media library.
media variant
A generated resize or format of a media item.
menu / menu item
A named, ordered list of links, and one entry in it.
module
One placeable block inside a layout document, configured through its own props.
module category
The palette grouping a module is listed under.
module prop
One configurable value on a module instance.
region
The top-level slot in a layout document that holds sections.
saved component (linked)
A reusable module or group, edited once and updated everywhere it's placed.
saved layout (blueprint)
A reusable starting layout copied onto a page, not kept in sync afterward.
section / row / column
The nesting inside a region: a section holds rows, a row holds columns, a column holds modules.
section template
Kywi's term for a saved layout used as a page's starting point — see saved layout.
site
One configured entry in a deployment, matched by host, in the layered render model.
site membership
The optional, per-user list of sites a role applies to.
site tree
The addressing structure of a site — a page's URL is its position in it.
slug and path
A node's own segment, and its full, position-derived URL.
tag
A flat, unordered label attached to content, distinct from a category.
translation
One locale's version of a piece of content, linked to its source.

Lifecycle

audit entry
A record of who did what to a document; most direct content writes leave none today.
changeset
A batch of content items published or rolled back together, atomically.
content status ladder
The five stages a document moves through: draft, pending, approved, published, archived.
soft delete / trash
A reversible delete for pages and media only; everything else deletes immediately.
version / version snapshot
A stored copy of a document's fields, layout and status at one point in time.

Targeting

A/B experiment
A named record with its own arms and traffic split; wrapping a section in A/B mode alone doesn't create one.
arm
One alternative inside a variant container; exactly one is served to any given visitor.
audience
A named segment defined by condition groups and, optionally, a score threshold.
audience pin
A stored id that forces one specific audience ahead of ordinary rule resolution.
audience priority
The list position that decides which of several matched audiences is actually served.
condition group
One AND-ed set of conditions; an audience matches when any one group matches in full.
consent record / consent category
A visitor's tracking decision, and the category each signal is classified under.
conversion goal
The event an experiment measures against exposures to compute a conversion rate.
default arm
The arm served when nothing else claims the visitor — the real page, not a placeholder.
deterministic bucketing
Arm assignment computed as a hash of experiment and visitor id, with nothing stored.
exposure
One visitor bucketed into, and counted for, an experiment arm.
instant match vs. score contribution
A pass/fail condition versus one that only adds points toward a threshold.
locked winner
An arm forced onto a container ahead of its own split, set on the container itself.
page variant
A whole page, rather than one section, carrying audience-targeted variants.
personalization opt-out
A visitor's signal to suppress audience matching; doesn't exempt them from a live A/B split.
preview token
A signed, revocable link that forces one audience for whoever opens it, briefly.
public audience
An audience deliberately marked so its name is exposed through a public listing route.
score threshold
The points total an audience's scoring conditions must clear to match.
self-ID field
One configured question on a self-identification widget; its answer becomes a rule signal.
self-identification
A visitor answering directly instead of being inferred from behavior.
statistical significance
A 95%-confidence test between an arm and control, gated by a minimum exposure floor.
traffic split
The whole-number percentages, summing to 100, that decide an experiment's authoritative division of visitors.
transparency panel
The persistent, visitor-facing control showing whether a page was personalized, with a switcher and opt-out.
variant container
A section or module wrapped to hold more than one arm, resolved per visitor.
visitor id
The persistent cookie id that ties a visitor's repeat requests together.
visitor signal
Any value a rule condition can test about a visitor.

Access

API key scope
A ceiling on the role a key's requests run as — never a grant.
content permission (per-node ACL)
An additive, per-document grant; restricts nothing until the first grant exists.
group
A bucket of users targeted by a content-permission grant or an approval-chain step, nothing else.
role and the role ladder
Five grantable roles in a strict order; every capability reduces to a minimum floor on it.

Platform

adapter (pull / push)
Code that feeds visitor signals into the audience builder from an external system.
Agent Experience (AX)
The machine-readable surfaces (.md, llms-full.txt) a project publishes about its own content.
cache key namespace
The prefix scoping one deployment's cached values from another's inside a shared provider.
deployment mode
Coupled, headless, or decoupled — a scaffold-time choice, not a runtime switch.
design token
A themed value emitted per request as a `--kywi-*` custom property.
extension subtype / attribute set
The database-side way to add fields to a config type without a migration.
hook
Code that runs on a content-type lifecycle event or the platform's event bus.
host app vs core engine
The seam between core, which never imports next, and the project that mounts it.
layer
One of the per-site sources a layered render composes together — not a CSS layer.
migration journal
The record of which database migrations have run against a given environment.
override by placement
The rule that a file's location, not its content, decides what it overrides.
plugin
A packaged unit a project installs to extend core at defined extension points.
scope
An SDK route family a request can be limited to.
theme
A project's design and behavior configuration, one per site.
webhook event
A named occurrence a project can subscribe an external URL to.