WorkRoot/WRNexusJSDoc
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update portal for WRNexusJS 0.2.17

Browse Source
This commit is contained in:
Clintchiz
2026-07-13 14:07:37 +05:30
parent ce8c43da9d
commit 9fc364ea41
81 changed files with 4388 additions and 594 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/site-audit.md
+8 -8
View File
@@ -1,19 +1,19 @@
# WRNexusJS site audit
Date: 2026-07-12. Baseline: Bun 1.3.14, framework 0.2.15.
Date: 2026-07-13. Baseline: Bun 1.3.14, framework 0.2.17.
## Baseline results
- bun install: pass (169 installs / 209 packages, unchanged).
- docs generation: pass (25 package pages and 5 prior site pages).
- tests: 6 pass. Check: pass. Production build: pass, 30 routes.
- Access test with an empty npm config: @wrnexus/cli and @wrnexus/core returned npm E404.
- Repository: private WorkRoot Git remote; no public LICENSE, SECURITY, or CHANGELOG file found.
- authenticated private-registry installation: pass.
- docs generation: pass (26 package pages plus portal and guide pages).
- tests, lint, formatting, and production build are required by the release check.
- package access remains restricted/private.
- repository: private WorkRoot Git remote; no public license file exists.
## Findings
The prior generator duplicated package H1s, descriptions, install blocks, and dumped full declarations. It also rewrote hand-authored core pages, used four desktop-only nav links, hid navigation on mobile, branded inconsistently, and presented an unusable public create command. Metadata lacked explicit canonicals and route coverage. No sitemap, robots file, docs index, release/access route, security/support/license policy, showcase evidence notes, benchmarks methodology page, or 404 source existed.
Package documentation, discovery assets, and AI-readable references are generated from the installed release. The 0.2.17 portal includes the helpers package, workspace app addition, and safe forward-auth login redirect guidance.
## Audit limitations
Browser tooling, Lighthouse, axe, screenshots, and an authenticated clean scaffold were unavailable. Scores are therefore not fabricated; post-deploy measurements remain required under docs/audits/.
Browser tooling, Lighthouse, axe, screenshots, and authenticated production deployment checks are separate post-deploy work. Scores are not fabricated; reports belong under docs/audits/.