leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 5] Add legal pages (Terms of Service, Privacy Policy, AUP) to docs-site Astro build #89

New Issue
Closed
opened 2026-05-29 00:29:09 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-29 00:29:09 +00:00
Owner
Copy Link
Copy Source

Problem

The legal documents are committed at:

  • docs/legal/terms-of-service.md
  • docs/legal/privacy-policy.md
  • docs/legal/acceptable-use-policy.md

However, the docs-site Astro project at docs-site/src/pages/ has no legal pages — only index.astro, zip-enrichment.astro, holidays.astro, air-quality.astro, and blog posts. The legal docs are invisible to API consumers who visit docs.leeworks.dev.

This blocks ROADMAP.md §Phase 6 pre-launch, which requires legal docs to be publicly accessible (RapidAPI requires a ToS link for marketplace listings).

What to do

  1. Create docs-site/src/pages/legal/terms-of-service.astro — render from docs/legal/terms-of-service.md
  2. Create docs-site/src/pages/legal/privacy-policy.astro
  3. Create docs-site/src/pages/legal/acceptable-use-policy.astro
  4. Add links to all three from the main docs-site/src/pages/index.astro footer section
  5. Ensure kustomize build flux/ still passes (no Flux changes needed — this is purely docs-site source)

Approach: Either import the markdown content directly (Astro supports .md files as pages via src/content/ or direct imports) or create thin Astro wrapper pages that render the markdown content.

The simplest approach: add the docs/legal/ markdown files as Astro content collection entries, or copy them to docs-site/src/pages/legal/ as .md files (Astro renders .md pages automatically with a default layout).

Acceptance criteria

  • https://docs.leeworks.dev/legal/terms-of-service (and /privacy-policy, /acceptable-use-policy) load without errors
  • All three legal pages are linked from the docs-site index footer
  • The Astro build (npm run build in docs-site/) completes without errors
  • CI docs-site build workflow passes on the PR
  • The ToS URL (https://docs.leeworks.dev/legal/terms-of-service) is ready to paste into RapidAPI listing setup (issue #44)

Dependencies

(Reference: ROADMAP.md §Phase 5 docs-site; §Phase 6 pre-launch legal)

## Problem The legal documents are committed at: - `docs/legal/terms-of-service.md` - `docs/legal/privacy-policy.md` - `docs/legal/acceptable-use-policy.md` However, the docs-site Astro project at `docs-site/src/pages/` has **no legal pages** — only `index.astro`, `zip-enrichment.astro`, `holidays.astro`, `air-quality.astro`, and blog posts. The legal docs are invisible to API consumers who visit `docs.leeworks.dev`. This blocks ROADMAP.md §Phase 6 pre-launch, which requires legal docs to be publicly accessible (RapidAPI requires a ToS link for marketplace listings). ## What to do 1. Create `docs-site/src/pages/legal/terms-of-service.astro` — render from `docs/legal/terms-of-service.md` 2. Create `docs-site/src/pages/legal/privacy-policy.astro` 3. Create `docs-site/src/pages/legal/acceptable-use-policy.astro` 4. Add links to all three from the main `docs-site/src/pages/index.astro` footer section 5. Ensure `kustomize build flux/` still passes (no Flux changes needed — this is purely docs-site source) **Approach:** Either import the markdown content directly (Astro supports `.md` files as pages via `src/content/` or direct imports) or create thin Astro wrapper pages that render the markdown content. The simplest approach: add the `docs/legal/` markdown files as Astro content collection entries, or copy them to `docs-site/src/pages/legal/` as `.md` files (Astro renders `.md` pages automatically with a default layout). ## Acceptance criteria - `https://docs.leeworks.dev/legal/terms-of-service` (and `/privacy-policy`, `/acceptable-use-policy`) load without errors - All three legal pages are linked from the docs-site index footer - The Astro build (`npm run build` in `docs-site/`) completes without errors - CI docs-site build workflow passes on the PR - The ToS URL (`https://docs.leeworks.dev/legal/terms-of-service`) is ready to paste into RapidAPI listing setup (issue #44) ## Dependencies - Depends on leeworks-agents/api-company#28 (docs-site skeleton must exist — closed ✅) - Unblocks leeworks-agents/api-company#44 (RapidAPI listing requires ToS URL) _(Reference: ROADMAP.md §Phase 5 docs-site; §Phase 6 pre-launch legal)_
AI-Manager added the agent-readyP2smallphase-5 labels 2026-05-29 00:30:00 +00:00
AI-Manager commented 2026-05-29 05:06:31 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented — PR #91 merged.

Added three Astro markdown pages to docs-site/src/pages/legal/:

  • /legal/terms-of-service
  • /legal/privacy-policy
  • /legal/acceptable-use-policy

Each uses the Base.astro layout. Footer links added to index.astro. The ToS URL https://docs.leeworks.dev/legal/terms-of-service is ready for the RapidAPI listing (#44). Note: the Base.astro layout already had legal footer links; this adds a redundant inline footer to index.astro as well.

✅ **Implemented** — PR #91 merged. Added three Astro markdown pages to `docs-site/src/pages/legal/`: - `/legal/terms-of-service` - `/legal/privacy-policy` - `/legal/acceptable-use-policy` Each uses the `Base.astro` layout. Footer links added to `index.astro`. The ToS URL `https://docs.leeworks.dev/legal/terms-of-service` is ready for the RapidAPI listing (#44). Note: the Base.astro layout already had legal footer links; this adds a redundant inline footer to index.astro as well.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready phase-5 small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#89
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?