📖 [Docs]: Process documentation publishes from Process-PSModule

[Marius Storhaug (MariusStorhaug)]

The Process-PSModule documentation will publish as a self-contained site from this repository at https://psmodule.io/docs/.

[process-docs-migration]

Changed:

• Added all 53 authored Markdown pages, page assets, includes, navigation, Zensical configuration, consent/social settings, and Tablesort behavior under docs/.
• Added the standalone Docs workflow to build the target site, upload a Pages artifact, and deploy only from main; it keeps source-equivalent manual, schedule, push, pull-request, concurrency, and PR Super-Linter behavior.
• Added the GitHub App-authenticated dynamic module catalog action and all four catalog templates so it writes docs/content/Modules/Catalog/index.md.
• Added the Process-PSModule workflow overview, specification, design, configuration, usage, pipeline, test-exception, and practices reference alongside the framework source.
• Updated repository ownership, edit links, and the README documentation link for PSModule/Process-PSModule.
• Disabled Giscus by omitting the source comment partial from the published site.

Technical Details

• PSModule/docs remains unchanged; this pull request adds the target site without external repository changes.
• The Process-PSModule specification, design, and runtime reference now live under docs/content/Modules/Process-PSModule/, including the workflow media. References to MSXOrg-wide standards remain canonical external links.
• The generic repository Linter retains its existing public-class exclusion and excludes only the self-contained Docs scope: docs/**, .github/actions/update-index/**, and .github/workflows/Docs.yml. Biome's workspace configuration mirrors the docs and catalog-action exclusions; generic lint coverage is unchanged everywhere else.
• The dedicated Docs workflow remains responsible for complete PR lint coverage of the site and its automation with source-equivalent rules, preventing unrelated artifact-pipeline rules from altering the authored corpus. Its pull-request paths explicitly include catalog-action changes so action-only PRs receive that coverage. Its Markdown profile permits the imported corpus's intentional compact and aligned table styles.
• Removed the configuration references to missing extra.css, abbreviation-preview JavaScript, and includes/links.md so the target builds without dangling runtime references.
• The catalog action retains the source ClientID and PrivateKey inputs and SCRIBBLER_BOT_CLIENT_ID / SCRIBBLER_BOT_PRIVATE_KEY secret names. Catalog regeneration runs only for trusted non-PR events on refs/heads/main; PR and branch-dispatched builds use authored documentation without passing secrets to checked-out action code. Non-PR publication requires only the successful Build job.
• GitHub Pages is enabled for GitHub Actions. The https://psmodule.io/docs/ custom-domain/DNS cutover and live-site validation remain outstanding.

Related Issues

• Parent: Consolidate PSModule documentation into Process-PSModule and retire PSModule/docs #423
• Documentation site: Migrate Process-PSModule documentation source of truth into Process-PSModule #426
• Live-site validation: Deprecate and retire PSModule/docs after consolidation cutover #428

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
HTML	Pass ✅
JAVASCRIPT_ES	Pass ✅
JAVASCRIPT_PRETTIER	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter