Shipping for Frontend Developers
Shipping is getting frontend code from a commit to users reliably. CI/CD pipelines such as GitHub Actions run linting, tests and builds on each push, then deploy to hosts like Vercel, Netlify or a CDN. Observability tools collect errors and performance data so problems in production are visible.
Stage: Production and Modern Platform · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in Shipping
- Write a GitHub Actions workflow that lints, tests and builds
- Deploy a preview environment for every pull request
- Set environment variables without exposing secrets to the client
- Configure cache headers for hashed assets and HTML
- Track runtime errors with a tool such as Sentry
Shipping interview questions
Why do build tools add hashes to asset filenames?
A content hash changes whenever the file changes, so the file can be cached for a very long time with immutable headers. A new release produces new filenames, which forces browsers to fetch fresh files, while unchanged files stay cached.
What is the difference between CI and CD?
Continuous integration automatically builds and tests every change merged into a shared branch to catch breakage early. Continuous delivery or deployment extends that by automatically preparing or releasing the tested build to staging or production.
Where Shipping fits in the Frontend Developer roadmap
Shipping belongs to the Production and Modern Platform stage (intermediate level), which takes about 5 hours. APIs, auth, deployment and the newer browser capabilities.
Other units in this stage
Back to the full Frontend Developer roadmap