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/documentation-coverage-matrix.md
+1
View File
@@ -11,6 +11,7 @@
| @wrnexus/db | /packages/db | /guides/db | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/dev-server | /packages/dev-server | Architecture/package guide | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/encryption | /packages/encryption | Architecture/package guide | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/helpers | /packages/helpers | Architecture/package guide | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/i18n | /packages/i18n | Architecture/package guide | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/jwt | /packages/jwt | Architecture/package guide | Planned | Generator coverage | Preview | No standalone CI fixture |
| @wrnexus/mobile | /packages/mobile | /guides/mobile | Planned | Generator coverage | Experimental | No standalone CI fixture |
docs/release-access-status.md
+2 -2
View File
@@ -2,6 +2,6 @@
## Decision: Mode B — Private Developer Preview
Active version: 0.2.15, derived from package.json#wrnexus.version. All 25 installed @wrnexus packages resolve to 0.2.15. On 2026-07-12, npm view using a clean empty user config returned E404 for @wrnexus/cli@0.2.15 and @wrnexus/core@0.2.15. The repository remote is a private WorkRoot Git service and no public license file exists.
Active version: 0.2.17, derived from package.json#wrnexus.version. All 26 installed @wrnexus packages resolve to 0.2.17 and npm reports restricted access. The repository remote is a private WorkRoot Git service and no public license file exists.
External users cannot execute an installation without approved private registry credentials. The truthful CTA is Request preview access. After approval, the canonical command is bunx @wrnexus/cli@0.2.15 create my-app. Tokens must never appear in documentation or source.
External users cannot execute an installation without approved private registry credentials. The truthful CTA is Request preview access. After approval, the canonical command is bunx @wrnexus/cli@0.2.17 create my-app. Tokens must never appear in documentation or source.
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/.