Build a Marketing Website

A landing page or content site that loads instantly, ranks well, and looks like you spent more on it than you did. Astro for content-heavy, Next.js if you also need auth/payments later.

Repos

Layers

Build time

A weekend

Outcome

See below

You will ship

A multi-page marketing site with blog, SEO meta, OG images, dark mode, and analytics.

How to feed this to your AI agent Browse the full directory

Framework

2 repos

bywithastro

astro

Ship static-first. Ship less JS. Use when there is no auth or dashboards.

Content-first framework with islands architecture. ~47k stars. Ships minimal JS, multi-framework component support (React + Vue + Svelte in …

byvercel

next.js

Use Next when you know auth/payments are coming and want one codebase.

The React framework. ~128k stars. App Router is the bet — server components, server actions, edge runtime. 2026 sentiment is mixed: people l…

UI + Animation

5 repos

byshadcn-ui

Hero, pricing, FAQ, navbar — copy in, customize, ship.

The default for Next.js builders in 2026. Not a dependency — you copy components into your codebase and own them forever. Built on Radix pri…

byorigin-space

origin-ui

shadcn-style components with 300+ pieces. Best for marketing site sections.

byDavidHDev

react-bits

Animated React components — Instagram-worthy hero sections.

Animated React UI components for landing pages. Aceternity-style aesthetics, actively maintained, copy-paste primitives. ~12k stars. The rig…

bysaadeghi

daisyui

Pure Tailwind components — no JS required.

Tailwind component classes — no JS, just CSS. Add `btn btn-primary` and you have a styled button. ~33k stars. Best for teams that want Tailw…

bymarkmead

hyperui

Free Tailwind UI blocks — drop-in marketing sections.

Free Tailwind UI blocks — heroes, pricing tables, cards, navigation. Copy-paste sections for marketing sites. ~11k stars. Best for non-desig…

Server-rendered (alternative to React)

1 repo

bybigskysoftware

htmx

HTML over the wire. No JS bundle, no build step. The anti-SPA movement's flagship.

The anti-SPA. HTMX lets you build interactive UIs by adding HTML attributes — no React, no build step, no JS bundle. Server returns HTML fra…

10 more layers · 20 more repos · members only

CMS2 repos
Forms + Email capture2 repos
Analytics3 repos
Animation + motion5 repos
3D / WebGL (for hero impact)2 repos
Icons + visuals1 repo
SEO essentials1 repo
Markdown / MDX content2 repos
Images1 repo
Search1 repo

20 more curated repos · unlock full access · members only

Unlock with lifetime membership.

Pay once. Full directory unlocked forever. No renewals, no surprise charges.

See pricing

How to build build a marketing website with AI

The 4-step AI workflow

The AI agents are good at code. They're bad at deciding what stack to use. This bundle does the second part. You bring the agent.

1
Ideate with ChatGPT or Claude.ai (web)
Paste your idea: “I'm building build a marketing website. Help me sharpen the product spec — features, edge cases, MVP scope.” Iterate for 10-15 minutes until you have a clear one-page brief.
2
Pick your coding agent
For this kind of bundle, we recommend Claude Code — Sonnet 4.6/4.7 handles full-stack multi-file reasoning best. See the install guide → Cursor and Codex are also great; pick the one you already pay for.

Feed this bundle to the agent

Open Claude Code / Cursor / Codex in an empty folder, then paste:

I'm building build a marketing website. Use this bundle as the source of truth for the stack:
https://stackpicks.dev/build/marketing-website

Brief from my product spec:
[paste your brief from step 1]

Follow the bundle order strictly:
  1. Framework
  2. UI + Animation
  3. Server-rendered (alternative to React)
  4. CMS
  ...

Stop and confirm with me after each layer.

4
Wire one layer at a time, commit between each
Don't let the agent install everything before the first git commit. One layer = one commit. Catches drift early, easy rollback.

Beyond the bundle

1Ship the boring version first. The bundle above is the maximalist list. For an MVP, start with 60% of these and add the rest when real users ask.
2Deploy early. Push to Railway / Vercel after layer 02 (auth) — not after layer 09. Production breaks differently than localhost.
3Read CLAUDE.md / .cursor/rules in this repo for the project conventions your AI agent should follow.
4Iterate on the take. If a repo here doesn't fit your specific use case, tell us — contact — and we'll add a better one within 60 minutes.