learnhouse/docs/scripts · le/learnhouse

Sswvefeat(docs): reference v2 — auth rights, search/SEO/llms, playground upgrades, docs-aligned layout

文件	最后提交记录	最后更新时间
generate-llms-full.mjs	feat(docs): reference v2 — auth rights, search/SEO/llms, playground upgrades, docs-aligned layout - Per-endpoint access annotations verified against the API's router wiring and RBAC layer: token-vs-session chips and the required rights bucket:action (e.g. courses:create) on every operation; session-only endpoints now show a JWT placeholder instead of a misleading lh_ token - Layout aligned with the rest of the docs site (1400px container, 250px sidebar, matching link styles and heading typography) - Endpoints are now searchable: pagefind ignores only the nav and code panes, anchors moved onto operation headings for precise deep links; APIReference JSON-LD on group pages; reference URLs confirmed in sitemap - llms-full.txt now appends a compact machine-readable API reference (base URL, auth, every endpoint with params/body/required rights) - Playground: multipart file uploads (streamed passthrough via the proxy with the same path validation), parameter values remembered by name across endpoints, and a recent-requests panel in the nav	1 个月前
update-openapi-snapshot.mjs	feat(docs): add full API reference generated from the live OpenAPI spec Adds a Stripe-style API reference to the docs site at /reference: - Pulls https://api.learnhouse.io/openapi.json (env-configurable via LEARNHOUSE_API_URL) with ISR caching (1h revalidate); a committed snapshot keeps builds green and dev offline-capable if the API is unreachable - Documents the token-usable surface (317 operations across 18 groups) via an explicit allow-list; internal tags never appear - Per-operation articles: params, request/response schemas, curl / JavaScript / Python examples (JSON, multipart and form-encoded bodies) highlighted server-side with shiki - Paste-once lh_ token: stored in localStorage, substituted into every example and copy action, synced across tabs - Live playground per endpoint, proxied through /api/reference-proxy (same-origin; forwards only the Authorization header, strict /api/v1 path validation, no cookies) since API CORS is pinned to tenant domains - New top-level "API Reference" navbar section; existing developer API guide pages now point to the reference	1 个月前