We would like all of the designs/styling used in Drupal core to use reusable components. Unfortunately, its not always obvious what these components should be named.
Do a survey of various style guides to see what others have named these components.
We are building a list of possible components in a Google drive spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AvR7gnIrX0ckdDgzNDI0blZVSnF...
Here's the list of style guides/resources that should be used for each component:
As components are identified and a survey is made of its naming, create an issue for each component and then try to come to consensus based on the survey data. Add that new issue to the issue summary of #1995272: [Meta] Refactor module CSS files inline with our CSS standards
Comments
Comment #1
ry5n commentedBesides the Seven Style Guide and Anna Debenham’s Mother of All Styleguide Lists (see issue summary), there is also the ARIA roles spec, which may help with naming.
http://www.w3.org/WAI/PF/aria/roles#abstract_roles
http://www.w3.org/WAI/PF/aria/roles#widget_roles
Comment #1.0
ry5n commentedAdded links to the Seven Style Guide and to Anna Debenham’s Mother of All Style Guide Lists
Comment #2
johnalbinHere's the survey doc I'm fleshing out. https://docs.google.com/spreadsheet/ccc?key=0AvR7gnIrX0ckdDgzNDI0blZVSnF...
Comment #2.0
johnalbinFixed Anna Debenham link and added Cloud Four's spreadsheet.
Comment #3
johnalbinI've updated the issue summary with more concrete steps.
Comment #4
rainbowarrayI went through the six style guides besides Seven that were listed under menu_tree and filled out all the information that I could. There are more on the master spreadsheet, but this is maybe a good starting place?
Some of the style guides are of higher quality than others. Foundation and Bootstrap had the most number of components.
A lot of these are very class heavy. Some of that is inevitable. It just seems a bit wordy in some cases. AUI in particular prefixes near every class with aui- which seems unnecessary.
Anyhow, here's the updated spreadsheet.
https://docs.google.com/spreadsheet/ccc?key=0AvR7gnIrX0ckdDgzNDI0blZVSnF...
Comment #4.0
rainbowarrayAdd more formalized plan
Comment #5
lewisnymanMoving into core
Comment #6
lewisnymanThis survey spreadsheet is really useful, I think it would help to have an overview of all the components we've address in the spreadsheet in this issue summary, because it's hard to tell what we are missing.
Comment #7
lewisnymanI've added the issues to each identified component that has already been fixed
Comment #8
lewisnymanComment #9
idebr commentedComment #23
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #24
smustgrave commentedSince there's been no follow up going to close this one out. If still a valid task feel free to re-open.