The official open source landing page for King Context, a retrieval layer for AI agents.
Live at: https://deandevz.github.io/king-context-landing-page/
King Context is an open source project, and so is this landing page. Both are free to use, study, fork, and modify. Everything ships under AGPL-3.0, which means any derivative work has to stay open source too.
If you want to learn what King Context actually does, head to the main repo: king-context.
Astro, TypeScript, static CSS, and optimized image assets. Pure static output, no backend, no database, no runtime dependencies on the host.
git clone https://github.com/deandevz/king-context-landing-page.git
cd king-context-landing-page
pnpm install
pnpm run devOpen http://localhost:4321.
pnpm run buildOutput goes to dist/. The site is fully static, so any host that serves files works (GitHub Pages, Vercel, Netlify, Cloudflare Pages, S3, plain nginx).
A GitHub Actions workflow at .github/workflows/deploy.yml builds and deploys to GitHub Pages on every push to main. To use it on your own fork:
- Fork the repo
- In Settings, Pages, set Source to "GitHub Actions"
- Push to main
The workflow sets the Astro BASE_PATH automatically:
https://user.github.io/repo-name/uses/repo-namehttps://user.github.io/uses/
For a custom domain, see GitHub's docs on configuring a CNAME for Pages.
The page lives in src/pages/index.astro, global styles live in src/styles/global.css, and images live in src/assets/. Colors, copy, layout, and visuals are yours to change. The only constraints come from the license: keep your fork open source under AGPL-3.0, and credit upstream where it makes sense.
If you ship something interesting on top of this, open an issue or PR upstream so others can find it.
AGPL-3.0-or-later. You can:
- Use it, including commercially
- Modify and fork it
- Distribute and host modifications
You have to:
- Keep the same license on derivatives
- Provide source for any modified version you distribute or run as a service
That last part is the difference from MIT or plain GPL. If you host a modified version as a web service, the modified source must be available to the people using it. The goal is to keep this layer of the stack honest, shared, and impossible to fork into a closed product.