Grey Golus logoGREYGOLUSStart here

06 // Resource guide

Updated June 2026

GitHub + Vercel

GitHub stores the project and its revision history. Vercel builds and publishes it. Together they create a simple path from local work to a live URL.

All resources

Bottom line

GitHub is the source of truth; Vercel is the delivery system. Keep secrets out of the repository, preview changes, then publish intentionally.

01 // The pipeline

From idea to public URL

  1. 01

    Project folder

    The files on your computer where the website or application is built and tested.

  2. 02

    GitHub repository

    The online copy with revision history, a README, visibility settings, and collaboration tools.

  3. 03

    Vercel project

    A deployment configuration connected to the repository.

  4. 04

    Preview deployment

    A temporary live version used to inspect changes before they reach the main site.

  5. 05

    Production deployment

    The approved version connected to the public domain.

02 // Minimum vocabulary

Six words that remove most confusion

Repository

01

A project and its revision history stored on GitHub.

Commit

02

A named snapshot of a set of changes.

Branch

03

A parallel line of work that does not have to change production yet.

Push

04

Send local commits to the remote repository.

Deployment

05

A built, hosted version of the project with its own URL.

Domain

06

The human-friendly address that points to the production deployment.

03 // Beginner path

A safe first deployment

  1. 01

    Create the repository

    Choose public or private deliberately, add a short README, and keep the project name clear.

  2. 02

    Check before pushing

    Remove passwords, API keys, personal files, and anything that should not become part of repository history.

  3. 03

    Import the repository into Vercel

    Choose the repository, confirm the project settings, and deploy.

  4. 04

    Open the generated URL

    Test the page, links, forms, mobile layout, and browser console before adding a custom domain.

  5. 05

    Connect the domain last

    Point the domain only after the deployment works at its Vercel URL.

04 // Public means public

Pre-publish checklist

  • Confirm repository visibility before the first push.
  • Never commit `.env` files, API keys, passwords, tokens, or private source material.
  • Read the generated site as a stranger: names, emails, notes, metadata, downloads, and source files all count.
  • Use preview deployments for review and keep `main` as the production branch unless you have a reason to change it.
  • Write a README that explains what the project is and how to run it.

Official sources

GitHub - About repositories GitHub - Repository quickstart GitHub - Repository best practices Vercel - Deploying Git repositories