Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

1.1 Software requirements for custom styling

To change the theme colors (i.e. the styling) of your Digizuite™ Media Manager (MM), some requirements need to be met.

The requirements are as follows:

Once these have been installed, you should be able to start building your new custom CSS files.

1.2 Enabling live editing (i.e. live reload) (optional)

Some prefer to see their changes to the color variables appear in an MM when editing the colors.

Please be advised. that this is not strictly necessary, and that you can entirely skip this step, if you want to do it manually instead. Doing ti manually, will take 1 minute longer every time you have to build → Find the CSS → Upload the MM.

By following the following steps, you enable a local MM on your computer, to automatically receive the colors you choose for your MM.

  1. First off, you need to have a MM with the "include source" postfix in an unzipped state.
  2. Have a DC installed and running on your local computer
  3. Host the "include source" from your computer, and hook it up to your DC.
  4. Edit the MM's web.config


Change

<add key="UseDist" value="true" />

to be

<add key="UseDist" value="false" />


Now all your changes to the files "style_overwrites" and the "variables.less" found in the "MP2" folder, will instantly show up in your MM upon saving the files. (Meaning that you'll not have to build the entire thing manually)

Side note

The original variables file is located in ..\[your site's name]\MP2\src\app\mp2\layout\less.

Configuring in this will overwrite the default colors supplied to you by Digizuite. It is not recommended to edit this original file!

Side note

When you're done live editing, you may choose to "flip back the switch" on the UseDist value you changed to be "false" when you started editing.

It is, however, not recommended to use the "include source" of a MM, as it can be considered to be more "bulky". Therefore, just copy the main.css file you've generated into a non-"include source" build of the MM.

  • No labels