eraluma (core)#
Main application entry point — global URL routing, homepage, live-data APIs, legal/static pages, and site-wide configuration.
Models#
None. This app is the glue layer connecting all other apps.
URL Routes#
API Endpoints#
Path |
View |
Description |
|---|---|---|
|
|
JSON: live Cape Town data (loadshedding, dams, traffic, crime) |
|
|
JSON: current traffic data |
|
(include) |
Loadshedding app API |
Content Pages#
Path |
View |
Description |
|---|---|---|
|
|
Homepage with categories, popular posts, live data widgets |
|
|
Full-text search |
|
|
Coming soon placeholder |
Legal Pages#
Path |
View |
Description |
|---|---|---|
|
|
Privacy policy |
|
|
Terms of service |
|
|
Cookie policy |
|
|
Membership information |
|
|
EU withdrawal/refund rights |
Infrastructure#
Path |
Description |
|---|---|
|
Robots.txt (served by view) |
|
Django sitemap framework |
|
Redirect to static file |
Management Commands#
Command |
Description |
|---|---|
|
Report on translation coverage across apps |
URL Routing Architecture#
Key Design Decisions#
Webhooks outside i18n: Stripe and reports webhook URLs are mounted outside
i18n_patternsat fixed paths so external services always reach them.Live data aggregation:
cape_town_nowaggregates loadshedding, dam levels, traffic, and crime data into a single JSON response for the homepage widgets.Multi-language: All user-facing URLs use
i18n_patternsfor German/English language prefix routing.