#528·unopim

[Feature]: Theme: custom CSS editor for admin UI overrides

Author: chrisBradley-devCreated Jun 27, 2026Updated Jun 29, 2026
LabelsFeature request

[Feature] Settings > Theme: custom CSS editor for admin UI overrides

Pre-submission checklist

  • I have searched the existing issues and this feature has not already been requested.

Is your feature request related to a problem? Please describe.

Several UI dimensions and layout values in the UnoPim admin are hard-coded inline styles or fixed Tailwind classes in core blade templates — for example, the right sidebar width on the product edit page (style="width:380px;"). Adjusting any of these requires editing core template files directly, which are overwritten on every upgrade. There is currently no supported mechanism for administrators to make UI customisations that survive updates.

Describe the solution you'd like

A Custom CSS field under Settings → Theme (or a dedicated Appearance section) where administrators can enter arbitrary CSS that is injected into every admin page inside a <style> tag.

This would allow targeted overrides without touching core files — for example:

css
/* Widen the product edit sidebar */
.right-column {
    width: 420px !important;
}

/* Increase category tree font size */
.category-tree-item {
    font-size: 13px;
}

Ideally, core templates would also be updated to use CSS custom properties (e.g. --product-edit-sidebar-width: 380px) so that overrides can be made cleanly via :root variable declarations without needing !important.

The implementation would involve:

  • A textarea field in Settings stored as a plain-text config value
  • Output rendered in the admin layout's <head> as <style>{!! $customCss !!}</style>
  • Basic sanitisation to strip <script> tags or other non-CSS content

Describe alternatives you've considered

  • Editing core blade templates directly — works but breaks on upgrade and is not a supported customisation path.
  • A custom plugin/package that injects a stylesheet — possible but requires PHP/composer knowledge and is significant overhead for what is essentially a UI preference.
  • Tailwind config overrides — not viable for runtime changes by non-developers.

Additional Context

This is a common pattern in other PHP admin platforms (e.g. WordPress has Additional CSS in the Customiser, Bagisto has a similar theme settings area). A CSS editor in Settings would make UnoPim meaningfully more customisable for non-developer administrators and reduce the volume of minor template-patch issues raised against core.