yasithdev opened a new pull request, #112: URL: https://github.com/apache/airavata-portals/pull/112
First step of extracting Wagtail out of the portal: decouple the portal **app shell** from Wagtail so it can later move to a standalone CMS. `base.html` (the app shell) previously queried Wagtail snippet models (`GatewayIcon`, `GatewayTitle`, `NavExtra`) for the favicon, header logo, title, and user-menu dropdown links, so every portal page hard-depended on Wagtail being installed and populated. This introduces a Wagtail-free **`portal_chrome`** template-tag library (`django_airavata/apps/api/templatetags/portal_chrome.py`) that sources those from a small `PORTAL_CHROME` settings dict (empty-safe defaults, overridable in `settings_local.py`), plus three plain-Django include templates that preserve the original HTML/CSS classes. Only `base.html` is repointed. Scope is deliberately limited to the app shell — the Wagtail `navigation_tags` library and the **CMS-page shell** (the `head`/`header`/`footer`/`nav-extra` includes, used only by the Wagtail page templates and rendering the page-tree menu) are left untouched and keep working until the CMS itself is extracted in a later step. Validated on a local dev baseline (Python 3.10): `manage.py check` is green and `base.html` renders without Wagtail. +93/-5 across 7 files. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
