summaryrefslogtreecommitdiff
path: root/src/env
AgeCommit message (Collapse)AuthorFilesLines
2020-08-11Update .env documentaionYoshie Muranaka1-12/+11
Remove theme-colors map example from documentation since this is a pattern we want to avoid. Updates to change "openpower" reference to "ibm" Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: I1715508c91853c35a4169d3fd27ee2f9021eb444
2020-08-10Update IBM .env stylesYoshie Muranaka1-17/+9
Removed Sass theme-color map. With Bootstrap's use of the !default and env import order, these variable assignments are all that is needed to leverage built-in color/theme maps. Also removed IBM gray palette since gray overrides were causing unwanted color changes in the form controls. Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: Iea0af2fe7cbc8ac365c2ec440bca63c60b10e527
2020-07-31Change openpower env files to ibmYoshie Muranaka3-0/+0
- Adds VUE_APP_COMPANY_NAME value that is used for logo alt text - Update VUE_APP_ENV_NAME to ibm since this will need to match the env filenames Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: Ie5b9fc3bedacb493939900a1de77a3a8a1f181c5
2020-07-31Remove envConstants.js fileYoshie Muranaka1-58/+0
Removing because current implementations are not using this file but directly referencing process.env.VUE_APP_* value instead. Also removing reference to this file in the env documentation along with the conditional template rendering section. The conditional template pattern is something that should be avoided and currently researching ways to dynamically generate navigation items so we can avoid this pattern. Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: Icbb92c423dac2b9b353c3701c330c3b9bfb00d7a
2020-07-28Add documentation for env themingYoshie Muranaka1-8/+29
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: I55d3ad755cb897918bb57059334e952ce7829c53
2020-07-27Add ability to customize theme stylesYoshie Muranaka8-0/+57
Showcases how different themes/styles can be supported using .env variables. If an environemnt name is specified during the build process, an overrides file will be pulled in to allow modifications to color and font definitions. This commit includes possible style modifications with the openpower env name as an example. To see the openpower changes, add the variable definition VUE_APP_NAME="openpower" to your .env.development.local file or build using 'npm run build -- --mode openpower' - Moves helper imports into vue config to allow for specific import order - Removed helper imports in SFCs Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: Iaf7a59c24fda06a7b74e23f2f042fb3300cb2056
2020-07-22Intel environmentMateusz Gapski2-0/+13
add environment for Intel add logo as a placeholder Signed-off-by: Mateusz Gapski <mateuszx.gapski@intel.com> Change-Id: Iad1ef66ef73e7f9e0857122cc29729543cbf6682
2020-04-25Add webpack config for env specific buildsYoshie Muranaka3-0/+176
Add documentation and example files to make environment specific build modifications. - Store any env specific router and store modules in separate env directory Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com> Change-Id: I06ff3cb0928707354266dd25b399710847e7fa18