Skip to main content

Developer documentation

The developer documentation explains how Picteus is structured, built, tested, and delivered. Use it when working on the Picteus source code, its build system, or its continuous integration workflows.

Documentation in this section​

  • Architecture — understand the main application components, their boundaries, and how they work together;
  • Build — build Picteus and its workspaces locally and understand the required development commands;
  • CI/CD — review the continuous integration and delivery workflows used to validate and publish changes.

Guidance​

Start with Architecture when you need to locate a change or understand a cross-component dependency. Read Build before modifying tooling or validating a local change. Use CI/CD to check how a change is validated in automation and how releases are produced.