Remix Website

Setup

cp .env.example .env
pnpm install

Local Development

pnpm run dev

To enable HMR:

pnpm run hmr

Build and Preview

pnpm run preview

Preview builds the app before starting the production server.

Deployment

• Production deploys from main.
• Staging deploys from the stage tag via:

pnpm run push:stage

Contributing

• Create a branch from the latest target branch.
• Push your branch and open a PR.
• Run pnpm run build before shipping a PR.
• See AGENTS.md for repo-specific rules (routes, assets, tests). Remix framework patterns live under .agents/skills/ (start with remix-overview).

Codebase

• app/ — Remix 3 site: routes.ts (URL contract), router.ts (Vite SSR entry, middleware, route wiring), actions/, ui/, data/, etc.
• server.ts (repo root) — Node HTTP server in production; serves the built app from build/server/.
• data/ — Blog posts and author metadata (separate from app/data/, which holds app-layer server modules such as blog queries).

Content

Newsletter Archive

• The /newsletter archive renders issues from the private remix-run/newsletter GitHub repository at runtime via a single tarball fetch.
• Because the repo is currently private, set NEWSLETTER_GITHUB_TOKEN (see .env.example) locally and in production to enable archive rendering. Without it, /newsletter returns a 503 when no cached snapshot exists.
• Issue directories are strict integers (newsletter-<N>); markdown filenames carry the UTC publication date (YYYY-MM-DD-remix-newsletter-N.md).

Authoring Blog Posts

• Add a markdown file at data/posts/{slug}.md.
• Keep post author names aligned with data/authors.yml.
• Put post images under public/blog-images/posts/{slug}/.
• Put featured header images under public/blog-images/headers/.
• Use relative blog links like [Title](post-slug) (not /blog/post-slug).