Building a portfolio
Portfolio websites are (usually) way too gimmicky. I wanted something simple, fast, and content-focused in my work. I generally do coding in a native-first environment. My focus isn't on creating rich web experiences (even if I care a lot about them). I needed something that felt like I could quickly go from code --> blog.
That's why I chose the following stack:
Technology
- Next.js (because deploying this is painless and server-side rendering is a top priority)
- React (because it's ubiquitous, but I might change this to Vue)
- Contentlayer (for blog writing / slurping of Markdown files)
- Tailwind (because I like my styling to be declarative and local)
- Framer Motion (have you seen that cool home page animation?)
What does it mean to be content-first?
Over the past year, I've really begun to understand the value of accurate information. I really have begun to appreciate blogs that dig into the rich history of technical, scientific, historical, or political topics with a rich set of citations. And that's what I want to do here: come with receipts.
You might be familiar with the notorious motherfuckingwebsite.com (and its slightly less atrocious cousin) But it makes one thing clear -- the less irrelevant overhead we add, the better. I know, real rich from someone using a React framework.
Citations
[1] Citation #1
[2] Citation #2