Eonix Stream Manual

Welcome. This manual describes the DXP (the browser admin at /dxp): how to sign in, pick a Space, author content, and use Engage and Observe surfaces. Use the sidebar for modules, or jump in below.

Who this is for

Operators — staff who manage sites, billing, and day-to-day publishing.
Creators — people who edit pages, posts, products, and library assets.
Reviewers — anyone who needs to understand what the desk can do in the current release.

It is not a deployment runbook; engineers should use repository docs (readme.md, docs/engine-edge-streaming.md, service units under dist/) for topology and operations.

What Eonix Stream is

Eonix Stream is a digital experience platform with:

A workspace (organisation) tied to your account, with Spaces (sites / destinations) you publish to.
A block-based canvas for pages: structured content (headings, paragraphs, lists, sections, and mapped data blocks), not raw HTML as the source of truth in the database.
Create — Spaces, library, drafts, page/post editor, products, block builder.
Engage — people, companies, journeys, exchange (relationships and funnels).
Observe — signals, outcomes, webhooks (visibility into behaviour and integrations).

Public visitors typically hit the edge (cached HTML). Staff use the platform desk over HTTPS; your host or reverse proxy should route /dxp, /api/v1, /spaces, and related paths to the platform process as described in your operator configuration.

Quick start (first day)

Sign in — Open your organisation’s desk URL and complete sign-in (password and, where enabled, passkeys). See Signing in.
Pick a Space — Use the workspace switcher and Spaces list (/dxp/spaces/all) so the desk knows which site you are editing. See Workspace and Spaces.
Create — Open Create from the shell, choose Spaces, Library, or Drafts, or jump straight into the page editor for the active Space.
Commerce (optional) — For UK shops, set Spaces → Settings → Regional to United Kingdom (GMT/BST) before entering scheduled sale prices on Products. When checkout holds are enabled, read Checkout inventory holds for reserved vs on-hand stock.
Publish — Saving in the canvas is not always the same as publish; use the publish action when you are ready for live traffic to see the version (subject to edge cache behaviour in your environment).

Modules (overview)

Module	You use it to…
Start	Sign in, understand workspace vs Space, navigate the desk, fix common access issues.
Create	Author pages and posts, manage products, library assets, drafts, and new Spaces.
Engage	Work with contacts, companies, journeys, and exchange workflows.
Observe	Read signals and outcomes, configure webhooks and integration visibility.
Reference	Glossary and a compact URL map for the DXP Core.

Introduction

Enterprise stacks often split commerce, content, CRM, and analytics across many tools. Eonix Stream targets an integrated model: one engine-backed workspace, one desk for operators, and a gRPC-first pipeline so writes and publishing flow through the engine while the edge serves fast, cacheable public views.

The DXP focuses on core completeness for the areas above, not on every future module.

Design principles (why it feels different)

Blocks, not blobs — Rich text is stored as structured spans and lists; HTML is produced at render time.
Engine as source of truth — Critical writes go through the engine; the desk talks to APIs that mirror that boundary.
Spaces as boundaries — Routing, themes, and much of the data you edit are Space-scoped; always confirm the active Space before publishing.

Typographic note

Where paths appear as /dxp/..., they are pathnames on your desk host (your operator may serve them behind https://your-company.example/dxp/... or a dedicated admin hostname).