MarkdownExportDsl

Optional four presentation groups around existing interface-point analyses, including empty groups.

Fail when any model relation has no exported destination instead of accepting plain text.

Ends each exported Analysis page with a table linking the analyses of the elements it contains, for example the component analyses on a cluster page. An analysis is listed under the analysis of its nearest ancestor element that also has an exported, enabled analysis. An authored <!-- STIG: child analyses --> insertion point instead renders a module-folder hierarchy with classification and recorded assessment arguments, including QM elements.

Disable when the destination site computes reverse links while rendering. Forward links are always exported.

Model table-of-contents labels; names include derived interface-point analysis names.

Merges exact exported page paths into the selected module-root navigation branches.

Existing MkDocs YAML configuration; its docs_dir (default docs) supplies the Markdown destination.

Selects project paths relative to the root (e.g. "components/pecu/cdds/PthAdc"), matching the consumer's directory layout. Supports Ant-style globs: a single * matches within one path segment; a doubled star matches across segments, so a pattern ending in a doubled-star segment below components/pecu selects every project nested under it.

Overrides the title of a selected module root, for example navBranch("components", "SW components").

Exact navigation titles leading to the parent of the generated branches; empty means top-level nav.

Destination root directory; one file per selected element/viewpoint is written beneath it.

Publication paths passed to the destination MkDocs site's publisher with the exported model.

Select the CREATE viewpoints to export.