Case study · Personal
Blogmors
A blog I designed and built, with searchable posts, topic filters and author pages, rebuilt in 2024 with reusable components.

- My role
- Design and frontend
- Team
- Solo
- Timeline
- Apr 2023 – Jun 2024
- Context
- Personal project
- Platform
- Responsive React app

01 Overview
Blogmors is a blog I designed and built: a home page of the latest posts, a posts page with search and topic filters, post pages with the author's card and reading time and a page per author.
- 5 Pages
- 2 Versions: 2023 and 2024
02 Problem
I wanted one project that carries my design from the logo to the last component, and code I could keep improving.
03 My role
I did all of it: the logo, the UI and the code.
- DesignDesigned the logo and the UI in Figma and Photoshop
- FrontendBuilt five pages with React Router and Tailwind CSS
- ComponentsRebuilt them in 2024 with variants (class-variance-authority and tailwind-merge)
- TestingUnit-tested the reading-time helper with Vitest
- Frontend
React
Vite
Tailwind CSS
React Router
JavaScript
CSS
HTML
- Testing and quality
Vitest
ESLint
Prettier
- Design
Figma
Photoshop
Canva
- Tooling and hosting
Git
GitHub
Netlify
04 Key decisions
The choices that shaped the product. Open one to see why it was made and what it cost.
Posts as data in the app
What we chose
Posts and authors stored as JavaScript data, with no backend
Why
A blog of a few posts needs no server, and it deploys as static files.
Trade-off
A new post means a code change and a deploy.
Search in the browser
What we chose
Posts filtered by keyword and topic on the client
Why
Results appear as you type, with no API.
Trade-off
Fine for dozens of posts, not thousands.
05 Result
Live on Netlify since 2023, and rebuilt in June 2024 with reusable components and a unit test.

What I learned
Rebuilding my own project a year later showed me how much clearer variants make a component library. Next time I'd keep posts in Markdown files from the start.
Next project: X Clone
A Twitter (X) clone in React: sign up, post and like, with accounts and posts stored on a mock API.

Questions