Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mgr/dashboard: Add guideline how to brand the UI and update the color scheme #25988

Merged
merged 6 commits into from Jan 23, 2019
Merged

mgr/dashboard: Add guideline how to brand the UI and update the color scheme #25988

merged 6 commits into from Jan 23, 2019

Conversation

Exotelis
Copy link
Contributor

Add guidelines for the vendors how to brand the frontend of the ceph dashboard.

I also updated the color scheme of the UI to match the branding of ceph.com

ceph-dashboard-ui-branded-01

As you can see in the screenshot I changed the layout of the buttons as well as the hyperlink text color. The idea was to use as less different colors as possible to keep the color scheme consistent and clean. That's why I added the scss variables $color-primary, $color-secondary and $color-accent which are assigned to the most important and eye-catching elements.

  • References tracker ticket
  • Updates documentation if necessary
  • Includes tests for new functionality or reproducer for bug

$ npm run build -- --prod

Unfortunately it's currently not possible to use multiple configurations when
serving or buildung the ui at the same time. That means a configuration just
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/buildung/building/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upsi, thanks :)

$ npm run build -- --prod

Unfortunately it's currently not possible to use multiple configurations when
serving or buildung the ui at the same time. That means a configuration just
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UI instead of ui?


Unfortunately it's currently not possible to use multiple configurations when
serving or building the UI at the same time. That means a configuration just
for the branding ``fileReplacements`` it not an option, because you want to use
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
for the branding ``fileReplacements`` it not an option, because you want to use
for the branding ``fileReplacements`` is not an option, because you want to use

(https://github.com/angular/angular-cli/issues/10612).
Furthermore it's also not possible to use glob expressions for
``fileReplacements``. As long as the feature hasn't been implemented, the
vendor has to add the file replacements manually to the angular.json
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
vendor has to add the file replacements manually to the angular.json
vendor has to add the file replacements manually to the angular.json file

vendor has to add the file replacements manually to the angular.json
(https://github.com/angular/angular-cli/issues/12354).

Nethertheless you should stick to the suggested naming scheme because it makes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Nethertheless you should stick to the suggested naming scheme because it makes
Nevertheless you should stick to the suggested naming scheme because it makes

To change the variable defaults you can overwrite them in the file
``./frontend/src/vendor.variables.scss``. Just reassign the variable you want
to change, for example ``$color-primary: teal;``
To overwrite or extend the default css, you can add you own styles in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To overwrite or extend the default css, you can add you own styles in
To overwrite or extend the default css, you can add your own styles in

~~~~~~~~~~~~~~~~~

Every vendor can customize the 'Ceph dashboard' to his needs. No matter if
Logo, HTML-Template or Typescript, every file inside the frontend folder can be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Logo, HTML-Template or Typescript, every file inside the frontend folder can be
logo, HTML-Template or TypeScript, every file inside the frontend folder can be

To change the variable defaults you can overwrite them in the file
``./frontend/src/vendor.variables.scss``. Just reassign the variable you want
to change, for example ``$color-primary: teal;``
To overwrite or extend the default css, you can add you own styles in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To overwrite or extend the default css, you can add you own styles in
To overwrite or extend the default CSS, you can add you own styles in

Copy link
Member

@s0nea s0nea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it correct that the 'Back'-Button is not as round as the 'Create'-Button?

buttons

Copy link
Member

@s0nea s0nea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please do a little clean-up of your git history?

@LenzGr
Copy link
Contributor

LenzGr commented Jan 17, 2019

Could you please do a little clean-up of your git history?

Agreed, can you please squash your commits, @Exotelis ?

the production configuration anyway
(https://github.com/angular/angular-cli/issues/10612).
Furthermore it's also not possible to use glob expressions for
``fileReplacements``. As long as the feature hasn't been implemented, the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to replace "the vendor" with "you".

Sebastian Krah added 6 commits January 18, 2019 14:44
Explains how to brand the ui without running in merge conflicts once a source
file gets updated

Signed-off-by: Sebastian Krah <skrah@suse.com>
Adds a new scss variable called color-primary that the primary color only has
to be changed at one point

Signed-off-by: Sebastian Krah <skrah@suse.com>
Changes the primary, secondary and accent color and adds a radius to all
buttons to match the branding of ceph.com

Signed-off-by: Sebastian Krah <skrah@suse.com>
Adds the files vendor.overrides.scss and vendor.variables.scss.
In those files the css and variable defaults can be overwritten.

Signed-off-by: Sebastian Krah <skrah@suse.com>
Mark all variables as default, that they can get overwritten.
Also import the file vendor.variables

Signed-off-by: Sebastian Krah <skrah@suse.com>
Fixes linting error in two files

Signed-off-by: Sebastian Krah <skrah@suse.com>
@Exotelis
Copy link
Contributor Author

jenkins test make check arm64

@LenzGr LenzGr merged commit 2b36b7f into ceph:master Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants