Introduction to Complianz documentation

Try a request See the innovation hub See a sample repo

At a glance

Summary: This wiki centralises product documentation, integration guides and answers to recurring questions. It is designed to be browsed by slice (profile, topic, task) or in linear reading.
Objective: Give you a clear view of the system and actionable entry points without multiplying back-and-forth with support.
Who this page is for: Developers, project managers, integration partners and technical clients.
Prerequisites: No prerequisites for this page; “API” pages assume basic HTTP/JSON knowledge.

This wiki is not a simple stack of PDFs: it follows an information architecture where each page has a role, an audience and clear exit links.

Info

Long pages expose a sticky table of contents on the right (desktop) to keep your place without random scrolling.

We separate journeys (who are you?) and reference (how does it work?). Hub cards place you in an intent first, then lead to atomic pages.

Visible landmarks, checked contrasts, keyboard navigation on menus and TOC, explicit button labels.

Systematic breadcrumb, hierarchical headings without level skips, explicit main / nav / aside zones.

Hub search filters cards and the full page list (client-side). Tags serve as semantic shortcuts.

Warning

Do not duplicate the same procedure on three pages: prefer a single link and one “source of truth” page.

Sample configuration block (fictional):

config.json

{
  "environment": "staging",
  "wiki": {
    "baseUrl": "https://example.com/en/wiki",
    "search": true
  }
}

Where to ask a business question?: Contact page or your usual contact — the wiki remains the stable reference.
Does the wiki replace the blog?: No: the blog keeps news; the wiki carries structured documentation.