Hey, I'm Skyversal. In this guide, I won't make you memorize commands. We'll build a small but rock-solid project from scratch together, explore the modern App Router, and finally push your code to the world. Ready when you are!
What's waiting for you at the end?
You're looking at an empty screen right now, but in a few minutes, you'll have a slick, live web app like this:
Welcome to Skyversal 🚀
Deploy in Seconds. Running on Next.js
1. So, What's the Deal with Next.js?
Look, React alone is amazing for painting the UI, but when it comes to routing or SEO, it basically says, "Hey man, I just draw components." That's where Next.js steps in. It wraps React with SSR (Server Side Rendering), APIs, and massive performance boosts, turning it into a full-blown beast.
- Routing: The system that allows users to navigate between different pages on a website (e.g., going to /about).
- SSR (Server Side Rendering): Generating the web page on the server before sending it to the browser. It makes your site incredibly fast and easy for Google to index (SEO).
- API: The invisible bridge that allows your frontend to communicate with your database or other services.
At Skyversal, we love this framework, and our systems recognize it instantly. This means you don't have to waste time telling Skyversal how to build or start your server. We just go "Aha, Next.js!" and wire everything up for you in the background.
2. Let's Build This Thing
Open up that black terminal window (don't worry, it doesn't bite) and paste this:
npx create-next-app@latest hello-skyversal
Next.js will ask you a few setup questions. Trust my 20 years of experience and answer them like this:
- Would you like TypeScript? Yes — Trust me, it prevents a lot of tears later.
- Would you like Tailwind? Yes — The best way to build modern interfaces rapidly.
- Would you like App Router? Yes — It's the future of Next.js. Get used to it now.
3. A Quick House Tour (Folder Structure)
When you hop into the project folder (cd hello-skyversal), you'll see a bunch of files. Don't panic, you only really care about these 4:
The living room. All your pages, layouts, and routes hang out here.
The pantry. Logos, fonts, and static images gather dust here.
Your project's ID and grocery list. Shows what libraries are installed.
The fuse box. Contains crucial build and runtime settings.
4. Coding Our First Masterpiece
Open up app/page.tsx, wipe out all that default boilerplate code, and paste in this sleek snippet I wrote for you:
export default function Home() {
return (
<main className="min-h-screen flex items-center justify-center bg-black">
<section className="border border-white/10 p-10 rounded-2xl bg-white/5 text-center">
<h1 className="text-4xl font-bold text-white mb-4">
Welcome to Skyversal 🚀
</h1>
<p className="text-gray-400 mb-8">Deploy in Seconds. Running on Next.js</p>
<div className="flex gap-4 justify-center">
<span className="bg-emerald-500/20 text-emerald-400 px-3 py-1 rounded">
GitHub Connected
</span>
<span className="bg-blue-500/20 text-blue-400 px-3 py-1 rounded">
Tailwind Ready
</span>
</div>
</section>
</main>
);
}
Let me save you from the most famous rookie trap: If you added a button to this page with an onClick event, it would blow up immediately. That's because the App Router renders everything as a Server Component by default. If you need client-side interactivity (like a button click), don't forget to proudly slap "use client"; at the very top of the file!
5. Let's See It on Localhost
We built it, now let's admire it. Fire this up in the terminal:
npm run dev
Jump over to http://localhost:3000 in your browser. Looks crisp, right? And here's the magic: change something in the code, hit save, and watch it update without even pressing F5. The kids call this HMR (Hot Module Replacement).
- HMR (Hot Module Replacement): When developing (on localhost), hitting save updates only the button or text you changed instantly without refreshing the whole browser page. It saves developers from losing their minds.
6. Boxing Up the Code (What is Git?)
Everything precious needs a backup. Git is that lifesaver system that takes snapshots of your code over time. Let's seal our project with these 3 commands:
git init
git add .
git commit -m "My first masterpiece: Hello Skyversal"
7. Pushing to GitHub
Go make an empty repository on GitHub, grab the URL they give you, and whisper these two magic lines to your terminal:
git remote add origin https://github.com/your-username/hello-skyversal.git
git push -u origin main
8. Showtime: Launching on Skyversal
The code is safe on GitHub. Now, let's turn it into a real, live website that your friends (and the whole internet) can actually visit.
Hop into the Skyversal dashboard and smack that "Create Project" button.
Authorize your account and pick the `hello-skyversal` repo.
We auto-detect everything anyway. Just click Deploy and lean back.
9. What's Happening in the Kitchen? (Deploy Log)
The second you hit Deploy, a Matrix-style terminal starts flowing. Don't worry, here's what we're sweating over in the background:
Great Job!
Believe me, a lot of folks give up when they see a black terminal. But you? You just took an empty folder and turned it into a real, working product served on Skyversal's Edge CDN. On behalf of the engineering team, congrats!
Alright, What's Next?
You're in the club now. To level up your project, I'd suggest poking around these: