8dd97dec9b
- Replace the Phase-0 "content to be completed" placeholder Usage section in every community_* README.rst with the actual features built across Phases 1-6 (routes, crons, portal pages). - Add CHANGELOG.rst (19.0.1.0.0) to every community_* module. - Note independent-vs-bundled module relationships in the root README. - Fix HANDOFF.md: Phase 8 was already committed (9a24691) and a git remote is configured, contrary to what it still said; record 9-A progress and the open gaps (missing banner.png assets, live --test-enable suite not re-run this session, no v1.0.0 tag yet).
34 lines
1003 B
ReStructuredText
34 lines
1003 B
ReStructuredText
========================
|
|
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
|