Let CMS Admin Edit Header

[wesleyboar]

Is your feature request related to a problem? Please describe.
The design of the header of the CMS is controlled solely via code. CMS admin can not update any UI, not even logo.

Describe the solution you'd like
Allow a CMS admin to change some aspects of header:

1. Logo
   • Yes, because this is the primary goal.
2. Choose Breakpoint for Nav Collapse
   • Yes, because this changes as site grows.
3. Custom Branding
   • Helpful, because custom branding elements can arise after setup.
4. Enable/Disable Portal Nav
   • Helpful, because custom branding elements can arise after setup.
5. Enable/Disable Search Bar
   • Maybe, because some clients may want to try it but not keep it.
6. Branding Choice and Order
   • Meh, because does not change once set

Describe alternatives you've considered

Alternate Steps	Limitation
change CMS settings in Core-Portal-Deployments	CMS admin's coding skills unreliable
add logo in Core-CMS-Custom	CMS admin's GitHub skills unreliable

Additional context

Important

Make it backwards compatible! I.e. if no content, then use existing code.

Note

Consider options, effect, and enhancements e.g.

• Add admin interface (unfamiliar).
• Add content placeholder (familiar).
  • Limit content allowed in placeholder (easy, see Texascale-CMS/pull#43).
  • Where to put placeholder in structure?
    • Top make sense (but admin complained about top once, for a placeholder proposed for editing News page).
    • Texascale adds placeholder (easy) and re-orders it (hacky).

[wesleyboar]

Logo Implementation Plan

This implementation plan was drafted by AI in discussion with me and is posted here for the record.

Backwards Compatible: If no content in the header logo placeholder, use existing code. Only superuser can edit static placeholders (footer and header logo).

---

Part 1: Editable Header Logo (static placeholder + Picture)

Goal: Allow CMS admin to change the header logo in the CMS UI. When the placeholder is empty, keep current settings-driven logo.

Approach:

1. Header template
   In taccsite_cms/templates/header.html, replace the current "Portal Logo" include with a static placeholder and fallback (same pattern as footer):

   {% load cms_tags %}
   {% static_placeholder "header-logo" or %}
     {% include "header_logo.html" %}
   {% endstatic_placeholder %}

2. Restrict placeholder to one Picture
   In settings, set CMS_PLACEHOLDER_CONF for slot header-logo: allow only the Picture plugin, max_children: 1.

3. "Header logo" Picture template

   • In taccsite_cms/_settings/djangocms_plugins.py, add a template choice to DJANGOCMS_PICTURE_TEMPLATES, e.g. ('header_logo', _('Header logo')).
   • Add template taccsite_cms/templates/djangocms_picture/header_logo/picture.html that outputs the same structure as the current header logo: <a id="header-logo" class="navbar-brand" href="..." target="..."><img class="portal-logo" ... /></a> using the Picture plugin context (e.g. instance, picture_link, image src, alt).

   Admin adds a Picture in the header-logo placeholder and, in Advanced settings, sets Template to "Header logo".

Result: Empty placeholder → existing logo from settings. One Picture with template "Header logo" → custom logo. No new plugin; uses existing Picture + template dropdown.

---

Part 2: Static Placeholders Editable Only by Superuser

Goal: Only superuser (e.g. CMS admin) may edit static placeholders (footer and header-logo). Editor groups must not have "Can change static placeholder."

Approach (single file: taccsite_cms/management/commands/util.py):

1. Stop granting the permission: remove the add_perm(group, 'cms', 'static placeholder', 'Can change static placeholder') call from let_view_page_and_structure() (and the TACC/WTCS comment above it if only for that permission).

2. Strip permission on every run so existing groups are updated on deploy: in let_view_page_and_structure(group), after the remaining add_perm calls, remove the static-placeholder permission from the group when present:

   # Only superuser may edit static placeholders (footer, header-logo). Ensure editor groups do not retain it.
   content_type = ContentType.objects.get(app_label='cms', model='staticplaceholder')
   perm = Permission.objects.get(name='Can change static placeholder', content_type=content_type)
   group.permissions.remove(perm)

   post_migrate → create_groups → each set_group_perms → let_view_page_and_structure(group) runs on deploy, so all editor groups are updated without a one-off script or manual admin.

Result: Only superusers (or users in a group that is explicitly given this permission elsewhere) can edit footer and header-logo. Every deploy keeps permissions in sync.

---

Summary

Part	What	Where
1	Static placeholder "header-logo" with fallback to header_logo.html	taccsite_cms/templates/header.html
1	Restrict slot to Picture, max 1	CMS_PLACEHOLDER_CONF in settings
1	Picture template choice "Header logo" + template file	djangocms_plugins.py, taccsite_cms/templates/djangocms_picture/header_logo/picture.html
2	Do not add and remove "Can change static placeholder" from groups	taccsite_cms/management/commands/util.py

No changes to apps.py or to any group_perms/*.py; Part 2 is entirely in util.py.

[wesleyboar]

Added more feature/solutions —

1. Logo
   • Yes, because this is the primary goal.
2. Choose Breakpoint for Nav Collapse
   • Yes, because this changes as site grows.
3. Custom Branding
   • Helpful, because custom branding elements can arise after setup.
4. Enable/Disable Portal Nav
   • Helpful, because custom branding elements can arise after setup.
5. Enable/Disable Search Bar
   • Maybe, because some clients may want to try it but not keep it.
6. Branding Choice and Order
   • Meh, because does not change once set

— but focus on logo, for now. Others, later.