Building a Personal Portfolio Website with Next.js and Supabase
A portfolio is more useful when you can update it without touching code. In this post I walk through a stack that makes that possible: **Next.js**, **TypeScript**, **Tailwind CSS**, and **Supabase**. ## Why this stack? - **Next.js** renders pages on the server, which is good for speed and SEO. - **TypeScript** catches mistakes before they reach the browser. - **Tailwind CSS** keeps styling fast and consistent. - **Supabase** gives you a Postgres database, authentication, and file storage without running your own backend. ## The big idea: content lives in the database Instead of hardcoding your projects, skills, and bio into components, store them in tables such as `projects`, `skills`, and `hero_about`. The site reads from those tables, and your admin dashboard writes to them.
const { data: projects } = await supabase
.from("projects")
.select("*")
.order("order_index");If a table is empty, the section simply renders nothing. Everything visitors see is controlled from the admin panel. ## Securing the admin area Supabase uses **Row Level Security (RLS)**. A good pattern is: 1. Anyone can **read** public content. 2. Only users listed in an `admins` table can **insert, update, or delete**. That rule lives in the database, so even if someone finds your public API key, they cannot change your data. ## Keeping the site fresh When you save something in the dashboard, call `revalidatePath("/")` in your server action. Next.js then rebuilds the cached page, and visitors see the update right away. ## Takeaways - Keep content in the database, structure in code. - Enforce permissions with RLS, not just hidden buttons. - Use environment variables for secrets and your site URL. Once this foundation is in place, adding a new section is just a new table, a form, and a component.