745e147de9
Only community_membership and community_school had application: True;
the other 6 product modules (community_benefits, community_classifieds,
community_interac, community_portal, community_theme_base,
event_qr_ticketing) had application: False despite being fully installed
and functional. Odoo's Apps screen filters to application=True by
default, so they were invisible there even though Technical > Installed
Modules showed them correctly - looked like they weren't installed.
Per the plan's own resellability rule ("each module is independently
installable and independently sellable"), every community_* product
module should be a discoverable Apps-grid entry. tncsc_deployment stays
application: False - it's the hidden client-config layer, not something
anyone browses to install on its own.
Verified on tncsc_site: -u upgrade picked up the flag for all 6, and the
site still serves every page (/, /about, /membership, /tamil-school,
/contact, /event) after the upgrade.
======================== Community OS Theme Base ======================== Configurable brand tokens (colours, logo, fonts) for community and cultural organizations, exposed as settings and injected as CSS variables across the website, member portal, and PDF reports. Installation ============ Install as any Odoo module. Configuration ============= Settings > Website > Community OS Theme. Usage ===== * Set primary/secondary/accent colours, logo, and heading/body fonts once under Settings > Website > Community OS Theme. * Those tokens are injected as CSS variables across the public website, the member portal, and PDF reports (e.g. the membership card), so a new deployment can rebrand entirely with data — no SCSS edits required. * Ships with a neutral default navbar/footer layout and no client colours in code; a fresh install looks generic until a deployment module (or an admin) sets its own brand tokens. Credits ======= Authors ------- * Metatroncube Software Solutions LLP