Skip to content
DIH Knowledge Base
    Sign in

    Markdown formatting

    Starlight extends Markdown with admonitions (asides), heading links, and MDX so authors can mix prose with components — a common pattern for SaaS docs (Notion-style clarity, developer-portal depth).

    Use these for onboarding notes, breaking changes, security warnings, and support escalations.

    Markdown directive syntax works too:

    TierSupportSLASSO
    EvaluateCommunity + docsBest effortOptional
    BusinessEmail, 8×599.5%SAML/OIDC
    EnterpriseNamed CSM, 24×799.9%SAML/OIDC + SCIM

    Ordered setup (release notes, upgrade paths):

    1. Provision tenant in DIH admin.
    2. Create connector credentials.
    3. Register webhook endpoints.
    4. Run connectivity test from the console.

    Unordered capabilities (feature marketing in docs):

    • Multi-tenant isolation
    • Audit log export
    • EU data residency options

    Task checklist (implementation guides):

    • Create Keycloak client
    • Configure redirect URIs
    • Assign product access groups in Keycloak (see access matrix)

    Good documentation answers: who is this for, what will they achieve, and what do they need before they start?

    Connector : A governed integration endpoint that exchanges assets and events between your systems and the DIH platform.

    Data space : A contractual and technical boundary for sharing data under agreed policies.

    Inline Authorization: Bearer <token> and paths like /assets/{assetId} stay readable without a full code block.

    Figures can include captions (accessibility and SEO). Hero imagery on the home page uses the official DIH diamond from production docs.

    NeedMarkdownMDX
    Policy / legal text
    Tabbed SDK samples<Tabs>
    Embedded demo or API✅ custom components
    Auto-generated OpenAPI✅ embed or link

    Next: Starlight components for layout primitives.