To run the application in fully accessible development mode you need to run an instance of a mock OIDC server. You can spin up a preconfigured instance with the following command.
cd oidc_mock && docker-compose up -d
Then to run the application with correct settings run:
# yarn
yarn install
# npm
npm install
# yarn
yarn dev
# npm
npm run dev
# yarn
yarn build
# npm
npm run build
# yarn
yarn lint
# npm
npm run lint
Location of theme config file:
src/
└── config/
└── theme.js
default
activeThemeFile: "bbmri"
Location of theme scss files:
src/
└── assets/
└── scss/
├── theme-bbmri.js
├── theme-eucaim.js
└── theme-canServ.js
You can change the values of the color variables as you see fit
default
activeLogosFiles: "bbmri"
Location of logos files:
src/
└── assets/
└── images/
├── bbmri/
│ ├── footer-bbmri.svg
│ ├── home-bbmri.png
│ └── nav-bar-bbmri.svg
├── canserv/
│ ├── footer-canserv.png
│ ├── home-canserv.png
│ └── nav-bar-canserv.png
└── eucaim/
├── footer-eucaim.png
├── home-eucaim.png
└── nav-bar-eucaim.png
If you want to change the image, you can replace the existing one with a new one, but with the same name, file type and size
default
isFooterFollowUsVisible: "true"
Additional configuration for the footer to be found in Footer Configuration
Location of matomo config file:
src/
└── config/
└── matomo.js
matomoHost: "MATOMO_HOST_PLACEHOLDER",
matomoId: "MATOMO_SITE_ID_PLACEHOLDER"
Location of featureFlags config file:
src/
└── config/
└── featureFlags.js
You can adjust the visibility of features, components or code that is ready for testing but not intended for realese is hidden behind feature flags.
Location of external links config file:
src/
└── config/
└── externalLinks.js
You can set which URLs external links lead to
Location of matomo config file:
src/
└── config/
└── oidc.js
Library to provide OpenID Connect (OIDC) and OAuth2 protocol support for client-side, browser-based JavaScript client applications. Also included is support for user session and access token management.