There are a few CSS files already in Classy. They have .theme. in their file names, because those were the names when the files were moved. We original were going to work with a two step process of copying everything to Classy and then rename/reorganize everything. We are too close to release to use a two step process. Other CSS that is being copied will have the correct names and folders. This issue is to clean up the ones that are already there.
See attached screenshot.
1) Remove the .theme. from the file names.
2) Move them from the folders they are in now, which were named similar to the template folders, and put them into an appropriate folder named for the category they are in. It looks like the three there now belong in css/theme since they are added in the theme category.
Optionally:
1) See if these should be moved to component.
2) Evaluate the library names. The comment library doesn't need to be called 'drupal.comment.threaded' but that is what it was probably called when it was in the comment module. We could use a simpler name. But, if changing the library names is disruptive, leave it as-is.
Beta phase evaluation
Issue category | Task because nothing is broken |
---|---|
Issue priority | Not critical because nothing is broken |
Prioritized changes | The main goal of this issue is put Classy's files into a more shippable state. |
Disruption | For most existing 8 sites there should be no disruption. Any disruption for fringe cases would be easily fixed. |
Comment | File | Size | Author |
---|---|---|---|
#2 | clean_up_existing_css-2565719-2.patch | 2.92 KB | LewisNyman |
folderstructureandcss.png | 107.58 KB | davidhernandez |
Comments
Comment #2
LewisNymanI think you will like this patch:
Comment #3
davidhernandezComment #4
davidhernandezOh, good call.
Comment #5
LewisNymanPostponed on: #2566597: [Mega patch] Move system *.theme.css files to Classy
Comment #6
davidhernandezThis was completed in the other issue.