Rebuilding my portfolio with Next.js 16
Why I chose a plain, text-first design over animations and gradients — and how Cache Components keep the whole site static.
Anish Kumar1 min readWeb#nextjs#tailwind#portfolio
My portfolio is usually the first thing a recruiter or client sees. The first version had gradients, animated cards, and a 3D-looking hero. It looked busy, and it was harder to read. So I rebuilt it around one rule: someone should understand who I am and what I've built in 30 seconds.
Why Next.js
Next.js is the framework I ship with every day. Using it here means the repository itself is a working sample of my stack:
- Static by default. With Cache Components, every page is prerendered at build time.
- SEO built in. Metadata, Open Graph images, a sitemap, and JSON-LD all come from the framework.
- MDX for writing. Blogs and notes are just files in the repo, so there's no CMS to maintain.
Caching content
Blogs and notes are read from the filesystem inside a cached function, so the result is reused across every page that needs it:
export async function getEntries(collection: Collection): Promise<Entry[]> {
"use cache";
const files = await fs.readdir(path.join(CONTENT_DIR, collection));
// parse frontmatter, sort by date…
}Design
Plain text, one column, real sentences. Experience, products, and projects are simple lists with dates — the way a resume reads. No animations, no gradients.
If you'd like to talk about a role or a project, email me.