Part of the process for making the READynamic environment custom for your organization involves replacing the graphics that appear on the Portal and Reader screens. For example, you can replace the READynamic logo in the upper left corner of the Portal Screen with your own product logo.
For more details about this process, see Branding the READynamic Browser Yourself.
Note it is possible to provide your own names for the graphics files you use to custom brand READynamic, and for the name of the folder (/assets_overrides) where these graphics files are stored.
Your Marketing Department might have established a standard set of colors for use with corporate communications, and a set of standard PNG files featuring the company logos and other images related to the company’s public presence. These files appear everywhere on the company’s web pages, InDesign files used for generating letterhead and marketing materials, email messages, blog and Facebook pages, and the like. You want to be consistent in using the same files, and with the same names, wherever they appear, including with READynamic. We make that possible too.
If you would prefer to change the names of these files so that they reflect your naming convention, you can edit the file names in the docker-compose.yml file. Return to the series of statements where the file names are defined in this configuration file:
- './assets_overrides/reading_view_logo.png:/home/app/public/assets/themes/datalogics/atb_client_shared/images/icons/toolbar/reading_view_logo.png' - './email@example.com:/firstname.lastname@example.org' - './assets_overrides/favicon.ico:/home/app/public/favicon.ico' - './assets_overrides/favicon.png:/home/app/public/assets/atb_portal/icons/favicon.png' - './assets_overrides/DTL-logo.png:/home/app/public/assets/atb_portal/icons/DTL-logo.png'
For the Corporate logo:
The first part of the statement defines the file stored in the assets_overrides directory:
/assets_overrides/DTL-logo.png:/home/app/public/assets/atb_portal/icons/DTL-logo.png The second part maps this file to how the software defines the graphic file.
You can provide your own file name here (after /assets_overrides) and then map it to the file name defined in the software. Keep in mind that you should only change the file name in this YML configuration file statement the first time it appears. Do not change the reference to the file “DTL-logo.png” at the end of the line:
Edit the docker-compose.yml file as needed to change the names of the other custom graphics files you provide to create a custom READynamic brand.
Suppose you have a corporate logo for your organization, and a set of approved PNG files for this logo, available for your staff to use. Your logo file is called “Standard-logo.png,” and you would rather use that file name for READynamic to be consistent with all of the other places in your environment where that logo graphic appears. Using the file called Standard-logo.png in place of the original “DTL-logo.png” (DTL here refers to Datalogics), and copy this file to your new /assets_override directory. But you would need to edit the docker-compose.yml file if READynamic is going to find it . Edit the logo file name in this YML file statement from this:
/assets_overrides/DTL-logo.png:/home/app/public/assets/atb_portal/icons/DTL-logo.png To this:
/assets_overrides/Standard-logo.png:/home/app/public/assets/atb_portal/icons/DTL-logo.png This maps the file called Standard-logo.png to the file DTL-logo.png.
Note that you can also use a different folder name for storing your PNG files, other than /assets_overrides. In that case you must edit the folder name where it is found in the compose docker-compose.yml file, described above. This might be useful if you decide to add multiple sets of PNG and ICO graphics files to READynamic, so that you can quickly and easily rebrand your application.
Maybe you want to have a different set of graphics to reflect the changing seasons of the year. And it is faster and easier to store the files in the READynamic installation package so they are already there when you need them. As a result you might have four sets of graphics files in these four folders:
Each folder would have its own custom set of PNG and ICO files. You would also need to create four sets of references to these files in the docker-compose.yml file. The graphics_fall file references might look like this:
#- './graphics_fall/fall_top_bar_logo.png:/home/app/public/assets/themes/datalogics/atb_client_shared/images/icons/toolbar/reading_view_logo.png' #- './graphics_fall/fall-logo.png:/email@example.com' #- './graphics_fall/fallfavicon.ico:/home/app/public/favicon.ico' #- './graphics_fall/fallfavicon.png:/home/app/public/assets/atb_portal/icons/favicon.png' #- './graphics_fall/fall-logo.png:/home/app/public/assets/atb_portal/icons/DTL-logo.png'
Note that these lines are commented out. You would only use one set of file references at a time. When you would apply your winter graphics to READynamic, the lines in the docker-compose.yml file that refer to the summer, spring, and fall graphics would need to be commented out.