Menu

How I Built a Data-Driven Portfolio That Takes 30 Seconds to Update
📰

How I Built a Data-Driven Portfolio That Takes 30 Seconds to Update

Reading 0:00
15s threshold

Adding a new project to my portfolio takes 30 seconds. No component changes. No new routes. No layout adjustments. Just 4 lines of JSON and an image dropped into a folder.

I got tired of the typical portfolio maintenance cycle: build something cool, then spend an hour wiring it into your portfolio site, adjusting layouts, making sure the new card doesn't break the grid. So I designed mine to be completely data-driven from the start.

Here's how it works.

The Single Source of Truth

Every project on my portfolio lives in one file: projects.js . Each project is an object with exactly 4 fields:

{ id: 'crystal-index', title: 'Crystal Index', techStack: 'TypeScript, Next.js, Prisma, SQL, GPT4, React 3 Fiber', info: 'Custom CMS for cataloguing crystals with structured filters for colour, chakra, and properties, and GPT-4-generated descriptions.', }

That's it. Four lines. The entire portfolio renders from an array of these objects.

The ID Does Triple Duty

The id field is where the design gets interesting.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.