Commit 1ea15432 authored by nwindis's avatar nwindis
Browse files

UPDATE readme

parent 85d6d740
Pipeline #154322 failed with stages
in 1 minute and 54 seconds
......@@ -211,6 +211,7 @@ There are two files in regards to configuration. Both deal with the Viewer's sta
- show or hide individual bars (info, navigation, toggles)
- rename labels
- tell the Viewer how it will be used (standalone / embedded)
- change the color scheme
- b) configure the panels (**src/config/panels.js**)
- set the order of the panels
......@@ -237,7 +238,12 @@ As a rule of thumb, every key with a boolean value (e.g. *true* or *false*) defa
"item": "Sheet",
"manifest": "Manuscript"
"standalone": true
"standalone": true,
"colors": {
"primary": "false",
"secondary": "false",
"accent": "false"
......@@ -294,6 +300,16 @@ It's a *JSON* object. So if you are going to make any changes and you have to qu
Defaults to `true`.
- **colors**
Set the colors used in the frontend.
`primary` and `accent` should be a darker tone, so that white text is visible if used as background. It's the other ways around with `secondary`.
Hex values (like `#a1a1a1`) or color names (like `hotpink`) can be used.
If values are left `false`, a default color schee will be used.
## Configure the panels
b) In order to configure the panels, locate the `panels.js` file inside the `src/config` folder of your project dir and find the *panels* constant at the top of the file:
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment