Timeline for Plugin development - Adding Foundation 5 CSS changes Craft CMS control panel
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2016 at 18:19 | comment | added | Prashanth | I understand that. Its just that I am lazy to edit Foundation.css. I just want to import it and work on it out of the box. Guess that's what bootstraps are for. What I don't get is why CP reacts to foundation. Ofcourse there would be conflicting classes in CP's HTML. Thanks anyway, will work it out. | |
| Sep 20, 2016 at 14:46 | comment | added | John Morton |
Ideally, I try to "contain" any custom styling rules. Like if you could contain your rules in a parent id like "mypluginname" (<div id='mypluginname>your code here</div>). Make the rules for your plugin the more specific rules... know what I mean?
|
|
| Sep 18, 2016 at 18:25 | comment | added | Lindsey D | @Prashanth: No, because then it would be impossible to customize the CP. | |
| Sep 18, 2016 at 17:11 | comment | added | Prashanth | So is this a bug in craft then? shouldn't craft's CP css have the highest priority in its styling? | |
| Sep 18, 2016 at 17:11 | comment | added | Prashanth | Thanks for the comment. I would try and reduce Foundation.css, but I wouldn't be able to remove the .button styling rules as they are being used in the plugin. | |
| Sep 18, 2016 at 17:04 | history | answered | John Morton | CC BY-SA 3.0 |