A docinsight.json manifest defines a DocInsight project by connecting project metadata, sources, content, assets, site settings, and output targets. The directory containing it is the project root.
The file uses UTF-8 JSONC (JSON with Comments). In addition to standard JSON syntax, it accepts // line comments, /* ... */ block comments, and trailing commas.
The top-level sections have separate responsibilities:
projectidentifies the documentation project and defines shared metadata.variablesdefines reusable manifest values.sourcesdefines source-analysis contexts, such as a Delphi project and compiler settings.contentdefines publishable Markdown and API documentation.assetsdefines named project-level file sets that output targets can publish.i18ndefines the project-wide default locale.siteandsitesdefine default and named rendering and deployment metadata.outputdefines named output targets and the content and project asset sets each target publishes.
Every manifest identifies the documentation project with a project object:
{
"project": {
"name": "mylibrary",
"title": "MyLibrary",
"description": "A documentation sample project for Delphi",
"copyright": "Copyright © DevJet Software. All Rights Reserved.",
"homepage": "https://docinsight.github.io",
"repository": "https://github.com/docinsight/mylibrary"
}
}
name is the required, case-insensitive project identifier; use a short ASCII value such as mylibrary or my-library. It is also the default Xref namespace for Delphi sources. title is the user-facing project name. Other fields provide shared descriptions, links, and notices.
After editing docinsight.json, run a documentation check from the project root or one of its subdirectories:
docinsight check
DocInsight validates the manifest and checks Markdown files and Delphi XML documentation comments for problems such as invalid configuration, broken links, and unresolved cross-references. It does not generate output.