fix: make check:markdown pass on a clean checkout (#315)

- LAUNCH.md: normalize table pipe spacing (MD060)
- MILESTONES.md, MAINTAINERS.md: rewrap paragraphs so wrapped lines no
  longer start with '#', which markdownlint misparsed as ATX headings
  (MD018 false positive)
- blog: write the truncate marker as {/*truncate*/}; the spaced form
  tripped MD037 (spaces inside emphasis markers). The Docusaurus
  truncate regex allows zero whitespace, so truncation still works.
- docs/community/end-user-community.md: drop single trailing space
- add .markdownlintignore for docs/architectures/**: these files are
  deleted and regenerated from upstream content by
  scripts/import-architectures.mjs on every daily import run, so
  hand-applied lint fixes there would be overwritten. Generated pages
  remain covered by scripts/validate-architectures.mjs.

Verified: 'npm run check:markdown' exits 0 (was 123, 164 errors in 11
files) and 'npm run test:unit' passes on main @ 00b44df.

Closes #306

Signed-off-by: kubestellar-hive[bot] <kubestellar-hive[bot]@users.noreply.github.com>
Co-authored-by: kubestellar-hive[bot] <kubestellar-hive[bot]@users.noreply.github.com>

Author: hivecommons-hive[bot]

.markdownlintignore

@@ -0,0 +1,6 @@
+# docs/architectures/*.md is generated content: scripts/import-architectures.mjs
+# deletes and rewrites these files from upstream sources on every daily import
+# run, so hand-applied lint fixes would be overwritten. Linting is enforced on
+# hand-maintained content only; generated pages are covered by
+# scripts/validate-architectures.mjs instead.
+docs/architectures/**

LAUNCH.md

@@ -28,28 +28,28 @@ Salt Lake City. **Today (2026-08-08) is 13 weeks out — launch Monday is
 ## Timeline (weeks are Mondays)
 
 | Week | Date | Milestone |
-|------|------|-----------|
+| ------ | ------ | ----------- |
 | W-13 | 2026-08-11 | Merge LICENSE (#40) and close Phase 0; create the four GitHub milestones (#78) so every launch task is tagged |
 | W-12 | 2026-08-17 | ADR 0001 ownership decision made (#46/#99) — this gates the announcement target and DNS work |
 | W-11 | 2026-08-24 | Metrics refresh workflow landed (#74); events page lists KubeCon NA 2026 co-located end-user events (#75) |
 | W-10 | 2026-08-31 | Awards list verified complete against cncf.io announcements (#77) |
-| W-9  | 2026-09-07 | Architectures freshness indicator on-page (#80); community/TAB staleness signal (#79) |
-| W-8  | 2026-09-14 | Good-first-issue curation done (#98); CONTRIBUTING walk-through by someone who didn't write it |
-| W-7  | 2026-09-21 | Blog cadence resumes: first post-welcome article (#76) — end-user story or architecture deep-dive |
-| W-6  | 2026-09-28 | Success-metrics baseline captured (see below) and dashboard/tracking issue live (#100) |
-| W-5  | 2026-10-05 | Launch blog post drafted; announcement channels confirmed (CNCF blog/Twitter amplification, end-user Slack, TAB mailing list) |
-| W-4  | 2026-10-12 | Full content freeze rehearsal: every generated-data workflow runs green end-to-end |
-| W-3  | 2026-10-19 | Launch blog post reviewed; DNS cutover executed if ownership decision landed on a CNCF org (Phase 3) |
-| W-2  | 2026-10-26 | Dry-run announcement to end-user community Slack; collect last-mile fixes |
-| W-1  | 2026-11-02 | Final content refresh; all Phase 1 issues closed or explicitly deferred |
-| W-0  | 2026-11-09 | **Launch during KubeCon NA week**: publish launch post, amplify on agreed channels, open feedback issue template |
+| W-9 | 2026-09-07 | Architectures freshness indicator on-page (#80); community/TAB staleness signal (#79) |
+| W-8 | 2026-09-14 | Good-first-issue curation done (#98); CONTRIBUTING walk-through by someone who didn't write it |
+| W-7 | 2026-09-21 | Blog cadence resumes: first post-welcome article (#76) — end-user story or architecture deep-dive |
+| W-6 | 2026-09-28 | Success-metrics baseline captured (see below) and dashboard/tracking issue live (#100) |
+| W-5 | 2026-10-05 | Launch blog post drafted; announcement channels confirmed (CNCF blog/Twitter amplification, end-user Slack, TAB mailing list) |
+| W-4 | 2026-10-12 | Full content freeze rehearsal: every generated-data workflow runs green end-to-end |
+| W-3 | 2026-10-19 | Launch blog post reviewed; DNS cutover executed if ownership decision landed on a CNCF org (Phase 3) |
+| W-2 | 2026-10-26 | Dry-run announcement to end-user community Slack; collect last-mile fixes |
+| W-1 | 2026-11-02 | Final content refresh; all Phase 1 issues closed or explicitly deferred |
+| W-0 | 2026-11-09 | **Launch during KubeCon NA week**: publish launch post, amplify on agreed channels, open feedback issue template |
 
 ## Success metrics (baseline + 30-day post-launch targets)
 
 Baselines are as of 2026-08-08; capture the W-6 baseline snapshot in #100.
 
 | Signal | Baseline (2026-08-08) | 30-day post-launch target |
-|--------|----------------------|---------------------------|
+| -------- | ---------------------- | --------------------------- |
 | GitHub stars | 0 | 50 |
 | Watchers / forks | 0 / 1 | 10 / 5 |
 | Unique contributors (humans, non-bot) | 1 | 5 |

MAINTAINERS.md

@@ -3,8 +3,8 @@
 This file lists the people responsible for reviewing and merging changes to
 endusers.cncf.io, and the process for adding more of them. It exists because a
 single point of failure on review/merge limits both continuity and community
-trust for a site that presents itself as a CNCF community property (see issue
-#47).
+trust for a site that presents itself as a CNCF community property
+(see issue #47).
 
 ## Current maintainers
 

MILESTONES.md

@@ -65,8 +65,9 @@ Tag issues/PRs covering:
 North America 2026 (Nov 9–12, Salt Lake City).
 
 See `LAUNCH.md` (PR #108) for the full date-backed plan. This milestone tracks
-launch-specific coordination. The six content-pillar issues (#74, #75, #76, #77,
-#79, and #80) remain in Phase 1 because GitHub supports one milestone per issue;
+launch-specific coordination. The six content-pillar issues
+(#74, #75, #76, #77, #79, and #80) remain in Phase 1 because GitHub supports
+one milestone per issue;
 the launch milestone depends on that phase instead of duplicating those
 assignments.
 

blog/2026-07-22-welcome-to-endusers-cncf-io.md

@@ -14,7 +14,7 @@ us end up adopting. This site is for them.
 Community](https://www.cncf.io/enduser/): the practitioners, architects, and
 organizations adopting cloud native technologies to build things that matter.
 
-{/* truncate */}
+{/*truncate*/}
 
 ## What lives here
 

blog/2026-08-08-month-in-metrics-august-2026.md

@@ -9,7 +9,7 @@ This is the first in a monthly series pulled straight from the numbers behind
 [/metrics](/metrics/) and [/architectures](/architectures/) — no editorializing, just what
 changed and where the data comes from.
 
-{/* truncate */}
+{/*truncate*/}
 
 ## The landscape, by the numbers
 

docs/community/end-user-community.md

@@ -196,6 +196,6 @@ since 2018 and how to nominate an organization.
 
 ## CNCF End User Support Staff
 
-Your membership in the CNCF [funds full time staff](https://www.cncf.io/membership-hub/) to help coordinate community efforts. This includes access to community experts with hundreds of years of collective OSS experience, as well as world class marketing and event support. 
+Your membership in the CNCF [funds full time staff](https://www.cncf.io/membership-hub/) to help coordinate community efforts. This includes access to community experts with hundreds of years of collective OSS experience, as well as world class marketing and event support.
 
 <CommunityPeople section="staff" />