Deploy y2k-web to GitHub Pages, Netlify, or Vercel

y2k-web is a pure static site — there are no API backends, no environment variables, and no server-side logic required. Because the router uses hash-based navigation (#/route), the browser handles all route resolution entirely on the client side. This means every static hosting provider works out of the box, with no special redirect rules or server configuration needed.

GitHub Pages
Netlify
Vercel

GitHub Pages serves static files directly from your repository — it’s free for public repos and requires no external tooling.The y2k-web repo already includes a .nojekyll file in the root, which tells GitHub Pages to skip Jekyll processing and serve all files as plain static assets. Because the compiled assets (assets/main.js, assets/main.css, components/Primitives.js, components/Guestbook.js) are committed directly to the repository, you can deploy straight from the repo root without running a build step.

Push your repo to GitHub

Make sure your latest code is pushed to the main branch on GitHub.

Open repository Settings

Navigate to your repository on GitHub and click the Settings tab.

Configure Pages source

In the left sidebar, click Pages. Under Source, select Deploy from a branch.

Select branch and folder

Choose the main branch and the / (root) folder, then click Save.

Visit your live site

After a short build delay, your site will be live at:

https://<username>.github.io/<repo-name>/

GitHub Actions workflow (automated builds)If you have made source changes and want GitHub Actions to rebuild the assets and publish the compiled output automatically on every push, create .github/workflows/deploy.yml in your repository:

name: Deploy to GitHub Pages
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm install && npm run build
      - uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./dist

This workflow installs dependencies, runs the Vite build, and publishes the dist/ directory to the gh-pages branch on every push to main.

Netlify offers two deployment paths — a quick drag-and-drop option and a Git-connected option for automatic deploys.Option A — Drag and drop

Run the production build locally:
```
npm run build
```
Open app.netlify.com and drag the dist/ folder into the deploy dropzone. Netlify will upload and publish it instantly.

Option B — Git deploy (recommended)

Connect your GitHub repository in the Netlify dashboard.
Set the Build command to:
```
npm run build
```
Set the Publish directory to:
```
dist
```
Click Deploy site. Netlify will build and publish automatically on every push.

No redirect rules are needed — hash-based routing is resolved entirely in the browser, so Netlify never needs to rewrite or redirect any URL.

Netlify’s free tier includes a custom subdomain of the form your-name.netlify.app at no cost. You can rename it from the Site settings → Domain management panel.

Vercel automatically detects Vite projects and requires zero configuration.Option A — Vercel CLIRun the following in the project root and follow the interactive prompts:

npx vercel

Vercel will detect the Vite framework, set the build command to npm run build, and set the output directory to dist automatically.Option B — Vercel dashboard

Go to vercel.com and click Add New → Project.
Import your GitHub repository.
Vercel auto-fills the framework preset as Vite. Confirm the settings:
- Build command: npm run build
- Output directory: dist
Click Deploy.

Vercel generates a unique preview URL for every push to any branch — not just main. This makes it easy to share work-in-progress builds with collaborators before merging.

Custom domain

All three platforms — GitHub Pages, Netlify, and Vercel — support custom domains at no additional cost. To connect your own domain, point the domain’s DNS either to the platform’s IP address via an A record or to the platform’s hostname via a CNAME record (consult each platform’s DNS documentation for the exact values). Then add and verify the domain inside the platform’s dashboard. TLS certificates are provisioned automatically.

Because y2k-web uses hash-based routing, all internal links use the #/path format (e.g., /#/about, /#/projects). If a visitor navigates directly to a path like /about — without the hash — the hosting provider will return a 404, because that path doesn’t correspond to a real file. The hash form /#/about will always work on any static host without any additional server configuration.

Customization

Deployment

Deploy y2k-web to GitHub Pages, Netlify, or Vercel

Custom domain

Build docs developers (and LLMs) love

Customization

Deployment

Documentation Index

​Custom domain

Build docs developers (and LLMs) love

Custom domain