You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

49 lines
2.2 KiB

Ai/docs alignment (#91) * chore: initialize the memory bank Add the canonical .memory-bank base with evidence-based project context: purpose and scope, workflows, stack and validation commands, architecture map, decisions, and the open work found while documenting the cmdlets. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com> * docs: align documentation with the cmdlet source - Fill all 36 platyPS cmdlet pages from the C# source: synopsis, description, parameters, defaults, examples, inputs, outputs, and notes, including documented limitations of the current code - Check every example against live parameter metadata and run them in a sandbox; fix examples that did not work (CSV restore, account filter, recursive inheritance, -AccessRights typos) - Rewrite the home, concepts, examples, README, and contributor pages; add a grouped cmdlet overview, module settings, privileges, long paths, and the platyPS workflow - Document Remove-Item2 -PassThru as renamed after 4.2.6 (#64) - Fix mkdocs.yml navigation, edit_uri, and copyright markup; add build.os and a pinned MkDocs version for Read the Docs - Point online help links to the pages on GitHub; add CHANGELOG.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com> * ci: build the module and check the docs against the build The documentation check ran Update-MarkdownHelp against the NTFSSecurity release from the PowerShell Gallery (4.2.6), so it failed for every unreleased parameter change. PR #91 failed because 4.2.6 still has Remove-Item2 -PassThur while the source and the docs have -PassThru. - Build NTFSSecurity.csproj in Release on the Visual Studio 2022 image, using the .NET Framework 4.5.2 reference assemblies package instead of an installed targeting pack - Check Docs/Cmdlets against the module built from source - Pin platyPS 0.14.2 and MarkdownLinkCheck 0.2.0, and enable TLS 1.2 so the NuGet provider bootstrap works Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com> * chore: record the green PR 91 build in the memory bank Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>
1 month ago
# Markdown and platyPS specifics
This page lists the Markdown rules for the NTFSSecurity documentation and
the additional rules for the cmdlet reference pages, which platyPS processes.
## Markdown
- Use ATX headings (`#`), one level 1 heading per page, and don't skip
heading levels.
- Use `-` for bulleted lists and `1.` for numbered lists.
- Surround headings, lists, tables, and code blocks with blank lines.
- Give every fenced code block a language, for example `powershell`.
- Don't use hard tabs or trailing spaces.
- Link to other pages with relative links to the `.md` file, for example
`[Concepts](Concepts.md)` or `[Get-NTFSAccess](Cmdlets/Get-NTFSAccess.md)`.
MkDocs converts them to links to the generated pages.
- End every file with a single newline.
## Cmdlet reference pages
platyPS converts the pages in `Docs/Cmdlets` to help files and updates them
from the module. Keep the structure that platyPS expects:
- Keep the front matter. `external help file`, `Module Name`, and `schema`
must stay as they are. `online version` is the address of the page on
GitHub, which `Get-Help -Online` opens.
- Keep the level 2 headings in capital letters and in this order: SYNOPSIS,
SYNTAX, DESCRIPTION, EXAMPLES, PARAMETERS, INPUTS, OUTPUTS, NOTES,
RELATED LINKS. Don't add other level 2 headings.
- Don't edit the SYNTAX blocks or the YAML block of a parameter by hand.
platyPS regenerates them from the module. The only exception is
`Default value`, which platyPS keeps.
- Write each paragraph on a single line. platyPS carries line breaks into the
text that `Get-Help` shows.
- Start each example with a level 3 heading such as
`### Example 1: Get the permissions of a folder`, followed by a code block
with the language `PowerShell` whose first line starts with `PS C:\>`.
- Under INPUTS and OUTPUTS, keep the level 3 headings with the type names and
add a sentence below each one.
- In RELATED LINKS, write each link on its own line and separate the links
with blank lines.
## MkDocs
- The site uses the built-in `readthedocs` theme.
- Every page must be listed in the `nav` section of `mkdocs.yml`.
- Files in `Docs` that aren't Markdown are copied to the website. Exclude
files that don't belong there with `exclude_docs` in `mkdocs.yml`.