Frontend Deployment: Why You Should Know cPanel Too
Vercel and Netlify are probably the easiest ways to deploy a frontend project.
As a frontend developer, you should absolutely know how to use them.
But I also think it’s worth knowing how to deploy a website the traditional way — especially with cPanel.
Not because cPanel is better.Because sometimes you’ll get a project where the hosting is already there, the domain is already connected, and the only instruction is:
“Upload the website to the server.”
Understanding that process is useful.
The basic process
Suppose you have a React project.First, create the production build:
npm run buildThis usually gives you a dist folder.
Now open your cPanel:
Get Ariful Islam’s stories in your inbox
Join Medium for free to get updates from this writer.
File Manager → public_html
Upload the contents of dist:
public_html/
├── index.html
├── assets/
└── ...Then make sure your domain points to the hosting server through DNS.Enable SSL, and your frontend is live.
That’s it for a basic static website.
There is one common issue with React applications: refreshing a route like /about can return a 404 because Apache doesn't know that React Router should handle that URL.
That’s where an .htaccess rewrite comes in.
Why learn this?
Using Vercel or Netlify teaches you how to deploy.
Understanding cPanel also gives you a better idea of what deployment actually involves — build files, document roots, DNS, SSL, and server routing.
You don’t need to become a DevOps engineer.
But as a frontend developer, knowing Vercel + Netlify + basic traditional hosting gives you more flexibility when a real project doesn’t fit your usual workflow.
Sometimes the best deployment tool is simply the one the project already has.
Before you go
- Please take a moment to like the post and follow the writer!
- Did you know that over 400,000 developers share what they’re building, learning, and discovering across our platforms every month? Learn how you can contribute here
