Official landing page repository for the EEP ecosystem under the eep-dev organization.
- EEP protocol repository: https://github.com/eep-dev/EEP
- EEP landing page repository: https://github.com/eep-dev/eep-site
This site is the public-facing documentation and landing experience for EEP. It must stay aligned with:
- Protocol repo: https://github.com/eep-dev/EEP
- Landing repo: https://github.com/eep-dev/eep-site
- Package scopes: npm
@eep-dev/*, Pythoneep-*
Run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun devOpen http://localhost:3000 to preview the site.
Edit app/page.tsx and related components; the page auto-updates during development.
Before release, confirm these are reflected in site content:
- Strict fail-closed semantic verification defaults
- Zero-trust audit readiness and report links
- Compliance scoring and
--report-json/--report-mdexamples - Canonical adoption links (agent onboarding + enterprise playbook)
- Repository URLs under
eep-dev
The site serves the EEP technical whitepaper as a paginated PDF at /whitepaper (production: https://eep.dev/whitepaper).
Before npm run build, generate the PDF in the protocol repo and let prebuild copy it into public/docs/:
cd ../EEP/docs && pdflatex WHITEPAPER.tex && pdflatex WHITEPAPER.tex
cd ../../eep-site && npm install && npm run buildpostinstall / prebuild also copy pdf.worker.min.mjs from pdfjs-dist for the in-browser viewer.
Deploy using your preferred platform (Vercel, Netlify, container-based deployment, etc.).
Keep production environment variables and domain configuration in sync with the eep-dev organization setup.
For production, ensure WHITEPAPER.pdf exists at build time (run pdflatex in CI or commit public/docs/WHITEPAPER.pdf after each whitepaper release).
Docker (docker compose build): the image copies scripts/ before npm ci (postinstall needs them). The build context is only eep-site/, so commit public/docs/WHITEPAPER.pdf or generate it locally before docker compose up --build — the container cannot reach ../EEP/docs.