Reasons To WordPress – The MyCSS Syndrome
When I started setting up WordPress1, I came across the need to adjust the CSS. I felt immediately that messing with the theme’s style.css
would be wrong.2 Instead, I felt there should be an extra CSS file for customization separately included via a plug-in.3
I’m a skilled programmer, so I was about to quickly write the plug-in myself (I figured it wouldn’t be too hard to do it). The names that came to my mind were MyCSS
for the plug-in, and my.css
for the style sheet. But before I set out to coding, I attempted a search for it on wordpress.org.
I was more then surprised: Not so much because I’ve found a plug-in that supports CSS customization, not even because I’ve found one that does exactly what I wanted, but because it was even named exactly as I would have named it.
From time to time, there are those lucky moments when you stumble upon a piece of software and think “Gee! These developers must have been inside my head.”
Indeed, a community capable of giving me such wow effects is priceless.
- and didn’t have an overview of what plug-ins exist yet [↩]
- Changing the theme’s
style.css
complicates theme upgrades. [↩] - I explicitly did not want CSS customization through the WP admin interface exclusively, but a file I could edit with any editor, and upload with any FTP client. [↩]
did you say … inside my “head”
“Gee! These developers must have been inside my had.”
Ooops 😮 Thanks, Patrick!