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

Source: Dev.to

The Story Behind Pepperminto-Enhanced 🍵

Background

I’ve been learning React and came across Peppermint.sh, a solid open‑source ticket management system. A community fork called Pepperminto had started adding a Knowledge Base (KB) but was essentially a “skeleton” – full of bugs, half‑finished features, and broken workflows. I decided to dive in and fix what was broken.

Work Done

• 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.

Learning Experience

Working on the fork gave me hands‑on experience with:

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

Fixing state‑management bugs proved far more instructive than just reading documentation.

Known Issues

• Guest tickets aren’t triggering webhooks yet.
• The ticket list needs live‑refresh logic.
• SMTP handshakes can be finicky.

I’m committing to weekly updates until this fork becomes the most stable version of Peppermint available.

Roadmap

• Full Markdown support for documents.
• Custom theming & fonts (brand your own Help Center).
• Enhanced Kanban with custom boxes/columns.

Repository

If you’re looking for a lightweight, open‑source alternative to Zendesk or HelpScout that actually has a working Knowledge Base, check out the repo:

👉 Repo: