I made a fork of a fork of Peppermint by Peppermint-labs

#webdev #javascript #productivity #beginners

The Story Behind Pepperminto-Enhanced 🍵

They say the best way to learn a new framework is to build something. I decided to take it a step further: I decided to fix something broken.

I’ve been learning React, and I came across Peppermint.sh, a solid open-source ticket management system. I found a community fork called Pepperminto that had started adding a Knowledge Base (KB), but it was essentially a "skeleton"—full of bugs, half-finished features, and broken workflows.

I decided to dive into the deep end.

🛠️ The 3.5-Day Sprint

I spent the last 80+ hours deep-diving into the codebase. My goal wasn't just to add features, but to repair the foundation.

What I’ve tackled so far:

KB Restoration: Repaired the broken CRUD workflows for the Knowledge Base.

Architecture Cleanup: Removed redundant applications (docs and landing-page) to make the monorepo leaner and faster.
Client Portal Refactor: Redesigned the client experience with a new sidebar and intuitive settings pages.

SEO & Stability: Implemented slug migrations for KB articles and overhauled the CI/CD workflows.

🧠 The "Trial by Fire" Learning Experience

Learning React by reading documentation is one thing; learning it by fixing someone else's state management bugs is another.

Repairing the Pepperminto fork gave me hands-on experience with:

Next.js & Fastify integration.
Monorepo management using Turborepo and pnpm.
Shadcn/ui for modern, accessible components.

🐞 The "Honest" Status Report

It wasn't all sunshine and successful builds. I currently have a massive headache, and I’m still not 100% satisfied. There are known bugs I'm still hunting: