HomoeoInsights

A small homeopathy clinic needs one place online for everything a patient touches: reading about the services, booking a consultation, following a blog and asking about medicines. The people running it also need to update that content and see bookings without calling a developer each time.

In 2024 I built HomoeoInsights as a portfolio prototype for that kind of clinic. It has a public website, an appointment booking flow, a blog with an admin editor, pages for ordering medicines, and an admin dashboard for managing content, users and appointments. It is a prototype: it was never launched and it never ran with real patient data. The names, phone numbers and team profiles in it are placeholders.

How it works

The repo has three parts. The web app is React 18 with Material UI, built with Create React App. It covers the home page, seven service pages, the blog, booking, contact, testimonials, login and registration, and an admin area with screens for blogs, comments, media, products, users, appointments, newsletters and services. The blog editor is Jodit, and the booking form uses Google reCAPTCHA.

The web app talks to an Express 4 API on Node.js through Axios. The API stores everything in MongoDB through Mongoose models for appointments, blogs, comments, contact messages, medicines, newsletter subscribers, products, services and users. People sign up with email and password (bcrypt and JWT) or with Google through Passport, then pick a role: doctor, patient or customer. When someone books an appointment, the API saves it and sends confirmation emails with Nodemailer, and uploaded images go through multer. The React Native app is only a two-screen stub. In October 2024 I started a Next.js 14 rewrite with Tailwind CSS on a separate branch, and I did not finish it.

Stack: React, Material UI, Node.js, Express, MongoDB with Mongoose, Passport, JWT, Nodemailer.

Status and links

This is a prototype, not a live service, and there is no public demo. I am not linking the repo because its name and content identify the clinic. Before anything like this could go live, it would need three things it does not have today: authentication on the admin and appointment routes (as written, those API routes are open), real content in place of the placeholders, and tests. If you need a booking site and a small CMS for a practice, this is the shape I would start from, with those gaps closed first.