Hassan Munj: A personal brand site the team runs without a developer

01 / Overview

About Hassan Munj

02 / The challenge

What Hassan Munj needed to solve

A personal brand site is mostly editorial work, and it goes stale if every change needs a developer.

1. 01

   The site had to read well on any screen and bring his ventures, podcast and blog together in one place he owns.

2. 02

   Writing posts, sending the newsletter, answering messages and keeping recommendations fresh had to happen without a developer.

3. 03

   Readers needed a proper way to leave the mailing list, and an editor who writes posts should not be able to mail the whole list.

4. 04

   Recommended tools needed clicks that can be measured, so the owner can see which picks readers act on.

03 / What we built

How we built Hassan Munj

We built a React and TypeScript site with Vite and Tailwind, an Express and MongoDB API, and a private dashboard where three staff roles are enforced in both the dashboard and the API.

• 01

  Public website

  The site presents his ventures, podcast, blog, recommended tools and AI upskilling offer, and reads well on phone and desktop. A Join the Community card points visitors to the LEAP AI networking app on iOS and Android.

• 02

  Tiptap post editor

  Staff write posts in a Tiptap rich text editor with a cover image, slug, category, tags, excerpt and reading time. Posts stay as drafts until they are ready to publish.

• 03

  Shared media library

  Images live in Cloudinary and show up in one library that staff can search by file name or alt text. Each image shows how many posts use it, and a cover can be picked straight from the library.

• 04

  Newsletter campaigns

  Staff compose campaigns and see subscribed and unsubscribed counts at a glance. Issues go out through Nodemailer in batches of 25 with a two-second pause, every email carries a signed unsubscribe link, and sent issues land in a public archive.

• 05

  Tracked recommendations

  The resources page holds affiliate links, books and recommended tools, grouped into sections such as AI tools and essential foundations. Every link passes through a click counter, so the dashboard shows which picks readers actually click.

• 06

  Messages and video links

  Contact form submissions land in a messages screen with new, read and archived statuses, where the team can search and reply. Video links are managed from their own YouTube screen.

• 07

  Dashboard overview and roles

  The overview shows published and draft posts, subscribers and new messages, with Recharts charts for blog views and weekly subscriber growth. Three staff roles are checked in the dashboard and again in the API.

04 / The results

What changed for Hassan Munj

The owner now runs the whole site from one dashboard, with three levels of staff access.

• Posts go from draft to published without a developer.
• The mailing list runs with proper unsubscribe links, and sent issues stay readable in a public archive.
• The owner can see which recommended tools readers actually click.
• Resources, video links and contact messages are managed from the same dashboard as the blog.
• The public site brings his ventures, podcast and AI upskilling offer together alongside the blog.