Browse documentation

Start here

OverviewYour first siteBuild and inspect your siteWrite useful documentationGlossaryTroubleshooting

Shape your site

ConfigurationAuthoring recipesSections and identityCustomize the home pageThemesCustom CSS (advanced)Machine-readable contractsVisual fixturesMathematics

Publish safely

Audit your documentationGitHub PagesPre-publish checklistHistorical documentationQualification evidenceMigration

Pascal and project internals

PasWeave integrationArchitectureArchitecture analysisProject specification (historical)

Project decisions

BoundariesHistory and customisationRelease-tag publicationReader-first documentationLocal syntax highlightingExisting-repository adoptionGitHub Pages setupDocumentation auditSimple configurationv1.0 stable contractDocSprout rebrand

Customising sections and identity

This is step 2 of the customisation order: use configuration to rename sections, choose colours, add project links and use a small project mark in the header. DocSprout keeps the page layout and accessibility behaviour working, so you do not need to copy or maintain its CSS.

Before and after: navigation

Edit the navigation value inside your existing docs/layout.json; leave its schema_version, home and unlisted entries unchanged. Before, a small site has one section:

{"navigation": [{"title": "Getting started", "pages": [{"title": "Overview", "path": "index.md"}]}]}

After, replace that navigation value with deliberate groups in the same written order:

{"navigation": [
  {"title": "Getting started", "pages": [{"title": "Overview", "path": "index.md"}]},
  {"title": "Reference", "pages": [{"title": "API", "path": "reference/api.md"}]}
]}

Before and after: project identity

Before (default configuration)

With no theme or identity object, this configuration uses DocSprout’s default blue colour preset and its built-in document mark:

{
  "schema_version": 1,
  "project": {"name": "Example-FP"}
}

The top header shows the built-in document mark immediately before Example-FP. Its accent and highlight colour use the default blue pair. There is no custom identity footer or link, so generated pages have no identity footer at their bottom.

After (DocSprout’s own configuration)

DocSprout’s documentation site uses this curated non-default preset and local identity asset:

{
  "schema_version": 1,
  "project": {"name": "DocSprout"},
  "theme": {"preset": "purple"},
  "identity": {
    "logo": "docs/assets/docsprout-mark.svg",
    "footer": "Built with DocSprout.",
    "links": [{"label": "Project", "url": "https://github.com/ikelaiah/docsprout"}]
  }
}

You can inspect the complete maintained docs/docsprout.json and its local SVG asset. On generated DocSprout pages, purple is the accent and highlight colour; the DocSprout mark appears immediately before the project name in the top header; Built with DocSprout. appears at the bottom in the footer; and the Project link appears in that same footer.

identity.logo is an optional repository-local path to an SVG or PNG. The DocSprout configuration above is the maintained logo example: it copies docs/assets/docsprout-mark.svg into the built site and shows it immediately before DocSprout in the top header. Use its configuration and asset together as the starting point for your own mark.

Create your image at the configured path before building. Paths must stay inside the repository; absolute paths, parent-directory traversal and other image formats are rejected. The logo is constrained to a small square header area and uses object-fit: contain, so unusually wide or tall marks keep their aspect ratio without pushing the title or controls out of place.

The project name remains the accessible name of the header link. The image is decorative because the adjacent text already names the project. Omit identity.logo to retain DocSprout’s built-in document mark.