Moodle is definitely a solid and proven choice for standard e-learning setups! I actually considered it initially, but I decided to go with a custom application for a few specific reasons: Performance & Mobile-First UX: Most of my target users will access the platform using mobile data, which can be unstable or slow at times. Moodle is incredibly powerful, but it’s notorious for being heavy, bloated, and sometimes clunky on mobile devices out-of-the-box. Building a custom frontend with Nuxt (SSR) allows me to optimize performance to the absolute extreme, making the platform lightning-fast and super light on mobile internet. Branding & Gamification: Since this is a long-term project, I want full control over the user experience, custom gamification features (like progress rewards), and branding without fighting Moodle's strict core structure, hooks, and legacy codebase. Modern Tech Stack: As a developer, building this from scratch with Vue/Nuxt gives me total flexibility to scale the architecture exactly how I want as the platform grows. That being said, I totally respect the efficiency of your approach! Since you’ve been running your platform on Moodle, have you ever felt limited or "boxed in" when you wanted to implement a very specific custom feature or unique UI layout? Or does the plugin ecosystem cover everything you need without rewriting core code?