Skip to main content

Developer Docs

For people who want to build Serpent locally or become contributors: setup, architecture, testing, packaging, and how to participate. These pages ship on main. They are not the slice logs or internal specs in docs/internal/.

Developer documentation is split into two parts.

Part 1: Software development​

For developers working on Serpent itself: architecture, building from source, testing.

  • Setup — dependencies, first build, development environment
  • Build & packaging — package / make / release pipeline / signing
  • Architecture — process model, directory layout, key design
  • Testing — test layers and how to run them
  • Adding media format support — registry, import, preview, filters, protocols, and acceptance
  • Branches and workflow — branching strategy, open source contribution process, and maintainer workflow discipline
  • Contributing guide — open source collaboration, Pull Requests, and code gate requirements
  • Contributors — contributions accepted and merged into the project

Other software docs (internal records live on the repo dev branch and are not published to the site):

Part 2: Extension development​

For developers writing plugins, scripts or MCP adapters. No software-architecture knowledge required — go straight to the extension author manual:

End users: see Using plugins, Browser extension, and Automation.