-
Notifications
You must be signed in to change notification settings - Fork 10
PLAT-102: set-up basic custom button styles for both HTML formats #119
Conversation
@@ -1,3 +1,4 @@ | |||
uuid: ffc7711c-ddd7-475e-b809-9ff7e0e99dbe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AndyEPhipps I think this is exported not via phing config:export
but manually, and thus contains uuid and all that crap :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pvhee so should we be removing this UUID info when exporting manually, or should we only be using phing to export config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AndyEPhipps best way is to use drush cde MODULE_NAME
(see also docs in https://github.com/comicrelief/campaign/blob/develop/docs/development.md#managing-configuration) or if you want all modules together use phing config:export
If you really want to do it via the UI, you'll need to remove the UUID manually :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, UUID is added because this is to support the migration of config from the same site but different environments. We are building platform to power many different sites, hence we can't have the UUID in there
Let's review the standards when we copy and paste code from old sites and keep in mind BEM and SMACSS for naming convention and file structure. For instance can we change .btn-red to .btn--red / .btn-ghost--white to .btn--ghost-white if ghost white is a modifier. Let's not use a variable file for every component. I think the btn mixin is a bit over engineered e.i. .btn-#{nth($button, 1)}. What do you think? We can discuss it and I show you what I mean. Let's not remove outline e.i. _outline: none; _ Not good for accessibility Let's not include input buttons for now. I think this is a good opportunity for us to review, simplify and clean up our code! :) |
Agree with @gusliedke's last comment. Also, I think in most cases, one Also, variables in general were way overused in previous campaigns. IMO, if a value is used twice or more, it gets a variable. If not, it doesn't. |
@AndyEPhipps care to review this here so we can merge in this PR? |
Need to pick this up again to go over Gustavo's suggested improvements, balancing a few plates at the mo |
…ive button production (lol)
…o feature/PLAT-102_CKEditor_custom_styles
…o feature/PLAT-102_CKEditor_custom_styles
…o feature/PLAT-102_CKEditor_custom_styles
Simplified use of mixin, updated class names to user BEM approach properly, exported HTML formats, removed previous campaign-specific styles to keep it general for now. |
https://jira.comicrelief.com/browse/PLAT-102
Deployment instructions