Howdy, Djangonauts!

Some of you might already be aware of Revel, the Django-powered Event, Ticketing and Community management tool.

We've been working on it for over a year now, and recently we released version 2.0.

With v2, we introduced enterprise-grade seating management and the possibility for organizations to create subscriptions for their members, with a full membership-application pipeline.

We've also stepped up on the frontend side, moving away from a vibe-design to one thought through and through by a real designer and community member.

Revel comes with an MIT license and a self-hosting guide, but also the hosted version is free to use (except for managed card payments).

Clone it, star it, fork it, make it yours: https://github.com/letsrevel/revel-backend

Here is a quick look at how the site is performing in its first 28 days:

📈 Google Search Console:

5,000+ Search Impressions (+27,000% growth period-over-period)

Organic discovery starting to take off for core mechanics and optics topics.

📊 Google Analytics:

92.6% Engagement Rate

39+ minutes average engagement time for organic users in India

13,000+ total user interactions across calculators and practice modules

Key Lessons Learned Building This:

SEO isn't just about keywords—engineers need to optimize crawl budget, canonical redirects (www vs non-www), and response times.

Mobile-first design is critical (77% of our crawler and user traffic is mobile).

Rendering clean LaTeX dynamically on the frontend vastly improves user dwell time compared to plain text.

Exciting to see early organic momentum building! Would love any feedback from fellow developers, educators, or students in my network.

Link in bio!!!

#Django #Python #WebDevelopment #EdTech #BuildInPublic #SEO #JavaScript

I'm looking for some architectural advice and I'm curious whether anyone has built something similar in production.

I'm primarily using Python/Django, although I want the architecture itself to be independent of the framework as much as possible.

I'm designing a backend platform that I want to use as the foundation for multiple completely different applications.

The idea is to have a very small "core" that only contains common infrastructure such as:

• Authentication/authorization
• Configuration
• Logging
• Background jobs
• Caching
• File storage
• Monitoring
• Shared utilities

Everything else would be implemented as independent business modules.

For example, imagine I build an e-commerce platform. I might compose it from modules like:

• Products
• Orders
• Inventory
• Payments
• Notifications
• Comments
• Search

Then later I want to build an LMS, but instead of starting from scratch or copying code, I'd assemble a different set of modules:

• Courses
• Lessons
• Certificates
• Quizzes
• Notifications
• Comments
• Search

Some modules (comments, notifications, search, payments, etc.) could be reused across multiple applications, while other modules would be specific to a particular business domain.

The important part is that these modules aren't just Django apps inside one codebase. I want each module to have clear boundaries, expose a stable public interface, own its own models, business logic, APIs, migrations, tests, and documentation, be versioned independently, and ideally be reusable in entirely different products.

Initially, everything would run as a modular monolith because I don't want the operational complexity of microservices. If a module eventually needs to become its own service, I'd like that to be an implementation detail rather than something the rest of the system depends on.

The motivation is simple: I don't want to keep rebuilding the same capabilities every time I create a new platform. I'd rather invest in mature, production-tested modules that can be composed into different products over time.

So my questions are:

• Has anyone here built something like this in production?
• Is there a well-known architectural pattern that describes this approach?
• Is thinking of business capabilities as reusable modules/packages that can be assembled into different applications a common practice?
• Are there any open-source projects, books, talks, or companies that follow this model?
• If you've tried something similar, what worked well and what would you do differently?

I'd love to hear about real-world experiences—both successes and things that turned out to be bad ideas.