Build with {{product.name}}

{{product.name}} technical enablement

Everything a technical person needs to implement and run {{product.name}} for, or on behalf of, a client. This portal is the engineering counterpart to the employee learning paths: how the product is built, the components that make it up, how to stand it up, how to deploy it, and how to connect it to a client's own systems.

ⓘ

Template notice. This portal ships as a skeleton. Each page carries example entries and [Replace: …] prompts for facts only your team knows. Replace them before sharing the site.

Latest updates

⚡

[Example] 2026-01-15 — Version 1.0 baseline. [Replace: one or two sentences summarising your most recent release in plain language. Lead with what someone can now do.]

See all release notes →

The journey

The sections group into three phases: understand the system, implement it for a client, then extend and run it. Jump straight to any of them.

UNDERSTAND Architecture Components Feature reference how it's built & what it does IMPLEMENT Operations Implementation flow Deployment models stand it up for a client EXTEND & RUN Integrations connect it to the client estate
The portal's sections, grouped into three phases. Release notes sit at the front of the nav.

Explore the sections

01 · Architecture Architecture overview How {{product.name}} is put together: components, request lifecycle, data stores and the main design decisions. Read the architecture → 02 · Components Components A catalogue of the main building blocks of {{product.name}}: what each does, its interfaces and its owner. Browse components → 03 · Features Feature reference Every capability in one searchable list: what it does, how it works, and how it links to the rest of the product. Browse features → 04 · Operations Operations Running {{product.name}} day to day: environments, monitoring, support, access and cost. Operate the product → 05 · Implementation Implementation flow The step sequence for standing {{product.name}} up for a client, and which steps unlock which capabilities. See the flow → 06 · Deployment Deployment models The ways {{product.name}} can be deployed, with trade-offs and a decision guide. Compare models → 07 · Integrations Integrations How {{product.name}} connects to client and third-party systems, and how to add a new integration. Plan integrations →

Before you start

You don't need all of this on day one, but a full client implementation of {{product.name}} typically touches:

AreaWhat you'll need
Environment[Replace: cloud subscription / account, regions, and the permissions needed to create the resources {{product.name}} runs on.]
Access[Replace: repository access, CI/CD permissions, and any licences or API keys the product depends on.]
Client inputs[Replace: the information a client must supply, e.g. data sources, brand or policy material, user lists.]
Data[Replace: source systems, sample data, and any data-protection constraints. Check with your Data Privacy Officer before using client or personal data.]
Tooling[Replace: languages, runtimes, infrastructure-as-code and CI/CD tooling with minimum versions.]

How to use these docs

  • The left rail moves between sections; the right rail ("on this page") jumps within one.
  • Code blocks have a copy button; the feature reference has a filter + search.
  • Ground claims in your repository: quote file paths and config keys so readers can verify against source.
⚠

Honesty note. Mark anything described here that is not shipped today (roadmap items, recommended approaches) so readers don't mistake it for existing capability. Also, the access code on this portal is a deterrent, not authentication: don't publish confidential client information here.