#1663 - Lifecycle of CSS
| Identifier | #1663 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Lifecycle of CSS |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | 1) Starts off as themes/default/css/foobar.css
2) You create a theme 3) If you used the Theme Wizard, you may or may not have themes/yourtheme/css_custom/foobar.css auto-created, depending on if it includes custom colours. We'll assume you did not use the Theme Wizard. In which case, foobar.css is being read from the default theme. 4) The first time you edit foobar.css into your theme, it copies themes/default/css/foobar.css to themes/yourtheme/css_custom/foobar.css and saves your change in there too. You now have an override in your theme. It has all the original code (so you don't need to create anything, it's all there) plus your changes. 5) It also copies themes/default/css/foobar.css to themes/yourtheme/css_custom/foobar.css.editfrom directly, making no changes from the original. 6) Each subsequent change you make, will save into themes/default/css/foobar.css, and also save a copy of themes/default/css/foobar.css.(current-unix-timestamp) as a backup. The .editfrom file lets you see changes between Composr versions, and when you originally created the theme, by comparing themes/default/css/foobar.css to your themes/yourtheme/css_custom/foobar.css.editfrom. The .(current-unix-timestamp) files let you see each revision of your CSS. You can do all this stuff manually by copying files between folders and editing files directly, should you wish to. Make sure you don't edit anything under templates_cached, as that is volatile. All these inherit from default. There is no complex chains. It's extremely unlikely you'll want to make a theme that overrides every single theme file. Maybe in the tutorial we can do a screencast showing how it happens automatically, and doing the same manually, and using diff tools. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
There have been no comments yet