CSS/JS Manager

About the Extension

Small storefront changes without touching your theme

A different button colour, a promo bar, a hidden element on the checkout page or a tracking snippet – small adjustments like these usually mean editing theme files or asking a developer to build a plugin. CSS/JS Manager gives you one place in the Administration where you write these adjustments yourself and ship them straight into your storefront.

Your code is kept in the shop's database instead of in theme files. Theme updates therefore never overwrite your adjustments, and you always see in one list which customisations are live in your shop.

Organised in containers

Every adjustment lives in its own named container with an optional internal note, so your team knows what it does and why it exists. A container holds SCSS, JavaScript or both – for example the styles and the script of a promo banner side by side. Each code field comes with syntax highlighting and can show practical examples on demand.

Containers can be switched on and off at any time, limited to selected sales channels and put in a fixed order. Search finds containers by name and by the code they contain, and an existing container can be duplicated as a starting point for the next one.

Styles that follow your theme

Your styles are compiled together with your storefront theme. That means your theme's colours, breakpoints, mixins and functions are available in your own SCSS, and plain CSS works just as well. If your brand colour changes in the theme settings, your custom styles follow automatically after the next compile.

Your CSS ends up in the theme's regular stylesheet and your JavaScript is delivered with the page itself. Visitors do not load a single additional file, so your adjustments do not slow down your shop.

Safe publishing

Changes reach the storefront only when you compile the theme – either for all sales channels from the list or with Save & compile directly from the container you are editing. Until then you can edit freely without customers seeing half-finished work.

If your SCSS contains a mistake, the plugin tells you which container and which line caused it, and your previously compiled theme simply stays online. In the storefront, every script runs separately and catches its own errors, so one faulty snippet cannot stop the others.