Goodly — Course Commerce Platform

$ cat ./problem

The problem

Goodly sells Excel & Power BI courses to thousands of students — but every page of the product site was hand-coded React. A price change, a new course, an SEO tweak: each one meant calling a developer and shipping a deploy. The brief was blunt: “we should only need the developer for structural changes.”

$ git log --built

What we built

• Self-serve admin for the whole catalogue: courses, curriculum (modules → topics → videos), pricing tables, FAQs, hero sections, testimonials
• Draft → publish → archive workflow — archiving a course hides its page and its homepage card instantly, no deploy
• Per-page SEO manager: titles, descriptions, OG images and crawler-rendered share pages for Google, WhatsApp and LinkedIn
• Paddle checkout with INR/USD pricing, purchase-success flow and GA4 purchase events for a complete revenue funnel
• Production hardening: Dockerised infra, a local-build deploy pipeline (the 1-vCPU server never builds), automated database backups

$ cat ./architecture

How it's put together

Postgres holds the catalogue; the public site reads only published content; nginx rewrites crawler user-agents to server-rendered share pages so a React SPA still gets real SEO. Deploys are built locally, shipped as images, and swapped with zero downtime.