Files
AgentCompany/landing/README.md
T
ZacharyZhang-NY d833ff4776 Move release manifest into lib/ to fix dependency direction
Architecture review (hai-architecture / APoSD) of the shipped redesign found one
structural smell: the shared lib/ layer imported the release manifest from
components/ — data in the presentation layer, dependency pointing the wrong way.
- move components/release-links.generated.ts -> lib/; update the four importers
  and the README. lib/ no longer imports from components/.
- downloads.ts: reuse PlatformDownload["id"] instead of re-declaring the union.

No behavior change (download counter + tracked hrefs identical); build + e2e 12/12.
2026-07-08 01:11:23 -04:00

15 lines
560 B
Markdown

# AgentCompany Landing
Next.js landing page for the AgentCompany desktop release lane.
## Copy Sources
| Surface | Source |
|---|---|
| Download cards | `landing/lib/release-links.generated.ts` |
| Platform FAQ | `landing/lib/platform-support.ts` |
| Hero, How It Works, software JSON-LD features | `landing/lib/product-narrative.ts` |
| Runtime download URLs | generated from `scripts/generate-landing-release-links.mjs` |
The public story mirrors the first-run desktop flow: Welcome, Requirements, Providers, Company, Team Models, Mode, Mission, Launch.