Even if you’re an absolute beginner, making changes to an existing CSS style sheet is not complicated. Yes, there are things you need to learn, and computer code is often unforgiving, but as I hope I explained in the previous post the basics are easy to grasp. Fuel your own initiative with a reference site like W3Schools, where you can pick up tips and information as needed, or even try out techniques before implementing them, and the only thing standing between you and success will be the bitter realization that an innocent misstep may lead to hours of hysteria because you don’t know how to protect yourself from your own ignorance. So let’s solve that problem.

Whatever goals you have for learning or even just tinkering with CSS, the first thing you need to do is see those goals in context. Yes, finding the exact right shade of green for your hyperlinks is important, but so is ensuring the stability and functionality of your site. There’s nothing inherently dangerous about making changes or even making mistakes when you’re working with computer code as long as you know how to protect yourself from inevitable errors. That protection begins with making sure you can always get back to the most recent stable build, even after you’ve made (and forgotten about) multiple changes.

1. CTRL-Z IS YOUR FRIEND. CTRL-Y IS YOUR OTHER FRIEND.
If you’ve been using a computer for any length of time you probably know that pressing and holding the Control (Ctrl) key, then simultaneously pressing the Z key will undo the most recent action in many applications. Most word-processing and image-editing software uses this convention, and the same holds true for many of the applications used to edit CSS style sheets.

If you make a change to the CSS in your style sheet, then upload the change and get results you’re not expecting, you can usually press Ctrl-Z to undo your mistake. Since mistakes are quite often unintentional you may not even be sure what you did to cause the problem, so Ctrl-Z can be a real lifesaver. Even better, many applications allow for multiple undos, so you can go back through five, twenty or even fifty edits. (Check the documentation to determine the exact number.) Since some mistakes become apparent only after multiple changes, Ctrl-Z may be the only way to step back through the sequence that triggered the problem.

What many people don’t know is that holding the Control key down and pressing the Y key will often redo an action, meaning between Ctrl-Z and Ctrl-Y it’s possible to go backwards and forwards through your most recent changes. For example, maybe you made a change but forgot what the original value was and suddenly realize it’s important. With Ctrl-Z and Ctrl-Y you can cycle back and read the value, write it down on a piece of paper or copy it to a separate document for reference, then cycle back to where you were. (What you must not do is cycle backwards with Ctrl-Z and make a change unless you’re sure you won’t need to press Ctrl-Y again. Any change you make when you go backwards with Ctrl-Z necessarily starts a new Ctrl-Y sequence in the application’s memory at that point.)  [ Read more ]

This isn’t the first time I’ve tinkered with a website or tweaked a WordPress theme, but as usual it feels like it. While I do remember a few things from previous style-sheet adventures, as with all things tech the horizon is constantly receding, and what once seemed like bedrock knowledge has become obscured by an ever-evolving feature set.

In the face of such inevitable changes the only options are to stay constantly up-to-date or effectively start from scratch each time. Because nobody in their right mind would stay up-to-date on CSS if it wasn’t paying the bills, it’s probably safe to assume that any CSS hacking you intend to do is driven more by your desire to have things just so than it is by a love of code. You want things to look the way you want them to look, but because money is an object you either have to suffer the indignity of off-the-rack blogging or make those changes yourself.

I feel your pain. In order to prevent you from feeling some of the pangs and jolts I’ve experienced, however, I thought I would pass along one tip I’ve never forgotten, which has saved me more time and trouble than the sum of all the CSS knowledge I’ve gleaned from websites, books and kind strangers who took pity on me. For all I know this is a common practice even among CSS professionals, but if that’s the case it’s considered so obvious that nobody mentions it when offering tips to absolute beginners. I stumbled upon it myself by accident and only belatedly recognized it as a means of preventing the kind of frustration and disorientation that can, in more advanced cases, lead to a seventy-two hour psych hold. Sure, you laugh — or at least I hope you do — but don’t laugh too hard because CSS can perplex almost anyone.  [ Read more ]