You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if network managers had the ability to change/customize the background image for pages on the root network. Currently, we can only change header images on the network homepage.
Feature Use Case
Currently, network managers are unable to change the background image for pages on the root network without using custom CSS. I can imagine that many super admins for their university PressbooksEDU networks are librarians like myself and without any CSS skills. This would be really helpful to those of us wanting to change the background image. Thanks!
The text was updated successfully, but these errors were encountered:
). When doing this we may wish to change the name of the current 'Header Image' option to say 'Home Page Header Image' and this second option to say 'Child Page Header Image' or something to that effect.
On the edit page menu for individual pages on the site root we should add a small button that allows the user to set a custom header image for that page. It would look/function much like the featured image function for core WordPress.
When a page has a custom header/featured image, that image would display as the page's header background image instead of the theme default.
Feature Description
It would be great if network managers had the ability to change/customize the background image for pages on the root network. Currently, we can only change header images on the network homepage.
Feature Use Case
Currently, network managers are unable to change the background image for pages on the root network without using custom CSS. I can imagine that many super admins for their university PressbooksEDU networks are librarians like myself and without any CSS skills. This would be really helpful to those of us wanting to change the background image. Thanks!
The text was updated successfully, but these errors were encountered: