npm create astro@latest -- --template minimal

🧑‍🚀 Seasoned astronaut? Delete this file. Have fun!

Inside of your Astro project, you'll see the following folders and files:

/
├── public/
├── src/
│   └── pages/
│       └── index.astro
└── package.json

Astro looks for .astro or .md files in the src/pages/ directory. Each page is exposed as a route based on its file name.

There's nothing special about src/components/, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.

Any static assets, like images, can be placed in the public/ directory.

All commands are run from the root of the project, from a terminal:

Feel free to check our documentation or jump into our Discord server.

• GitHub Pages builds use the PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY, and PUBLIC_PLAUSIBLE_DOMAIN secrets in .github/workflows/deploy.yml.
• The Search AI Edge Function reads OPENROUTER_API_KEY and SERVICE_ROLE_KEY from Supabase secrets.
• Apply supabase/supabase-schema.sql before deploying if you have not already created the search_ai_queries table.
• The news votes block at the end of that file adds news_votes and RPCs toggle_news_vote / news_vote_snapshot. Run the new section in the Supabase SQL editor after pulling changes so upvotes work in production.
• The blog post comments section adds post_comments and extends topic_audit with post_id / post_comment_id. Deploy the post-comment-submit Edge Function (same Supabase secrets as comment-submit) after applying that SQL.
• News auto-ingest: see DEPLOY_CHECKLIST.md for SQL blocks, Edge Function secrets, news-sync deploy, curl test, and GitHub cron secrets.
• Schema block in supabase/supabase-schema.sql (news.ingest_source, news_feed_sources, news_ingest_log). Edge Function secrets: SERVICE_ROLE_KEY, NEWS_SYNC_SECRET.
• Scheduled sync: .github/workflows/news-sync.yml (every 6h) needs repo secrets NEWS_SYNC_URL and NEWS_SYNC_SECRET.