📖 [Docs]: Style guides cover image accessibility, PowerShell matching, and requirement IDs#16

Open

Marius Storhaug (MariusStorhaug) wants to merge 24 commits into

mainfrom

docs/15-style-guide-authoring-gaps

Commits on Jul 5, 2026

Add reference-style link, backtick, and image alt-text guidance to the Markdown standard
Marius Storhaug (MariusStorhaug)
committed
Add matching-operator and read-only-constant idioms to the PowerShell standard
Marius Storhaug (MariusStorhaug)
committed
Name the F#/N# bold requirement-identifier convention in Spec-Driven Development
Marius Storhaug (MariusStorhaug)
committed
Render requirement identifiers in bold in Spec-Driven Development
Marius Storhaug (MariusStorhaug)
committed
Clarify read-only versus constant in the PowerShell constants idiom
Marius Storhaug (MariusStorhaug)
committed
Align spec template requirement identifiers with the no-period bold convention
Marius Storhaug (MariusStorhaug)
committed
Adopt FR/NFR identifiers with stable {#id} anchors, BCP 14 language, and append-only IDs in the spec guide
Marius Storhaug (MariusStorhaug)
committed
Recognize explicit attr_list heading ids in the documentation link checker
Marius Storhaug (MariusStorhaug)
committed
Clarify the BCP 14 keyword set is not exhaustive in the spec guide
Marius Storhaug (MariusStorhaug)
committed
Validate reference-style link definitions in the documentation link checker
Marius Storhaug (MariusStorhaug)
committed
Add the 'prefer .NET for the actual work' principle to the PowerShell standard
Marius Storhaug (MariusStorhaug)
committed
Use native .NET for path resolution and existence checks in the link checker
Marius Storhaug (MariusStorhaug)
committed
Fully qualify [System.IO.Path]::GetFullPath in the PowerShell standard
Marius Storhaug (MariusStorhaug)
committed
Report the normalized link target in link-checker error messages
Marius Storhaug (MariusStorhaug)
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

📖 [Docs]: Style guides cover image accessibility, PowerShell matching, and requirement IDs#16

📖 [Docs]: Style guides cover image accessibility, PowerShell matching, and requirement IDs#16
Marius Storhaug (MariusStorhaug) wants to merge 24 commits into
mainfrom
docs/15-style-guide-authoring-gaps

Commits on Jul 5, 2026

Add reference-style link, backtick, and image alt-text guidance to the Markdown standard

Add matching-operator and read-only-constant idioms to the PowerShell standard

Name the F#/N# bold requirement-identifier convention in Spec-Driven Development

Render requirement identifiers in bold in Spec-Driven Development

Clarify read-only versus constant in the PowerShell constants idiom

Align spec template requirement identifiers with the no-period bold convention

Adopt FR/NFR identifiers with stable {#id} anchors, BCP 14 language, and append-only IDs in the spec guide

Recognize explicit attr_list heading ids in the documentation link checker

Clarify the BCP 14 keyword set is not exhaustive in the spec guide

Validate reference-style link definitions in the documentation link checker

Add the 'prefer .NET for the actual work' principle to the PowerShell standard

Use native .NET for path resolution and existence checks in the link checker

Fully qualify [System.IO.Path]::GetFullPath in the PowerShell standard

Report the normalized link target in link-checker error messages

Commits on Jul 6, 2026

Merge branch 'main' into docs/15-style-guide-authoring-gaps

Conform the documentation link checker to the PowerShell coding standard

Validate anchor fragments case-sensitively in the link checker

Support angle-bracketed reference-style destinations in the link checker

Merge main and align the PowerShell .NET guidance with #18

Require a [Parameter()] attribute and a blank line per parameter, and comment-based help on every function

Add comment-based help and full parameter blocks to the link checker's functions

Scope comment-based help to public functions and match the Markdown extension case-insensitively

Strip single-quoted and parenthesised link titles, not just double-quoted

Describe what [Parameter()] does without the inaccurate advanced-function claim