CSS preprocessors like LESS and Sass are hugely popular – and for good reason! Once you’ve picked up their syntax, they can shorten the time taken to write CSS, give you all sorts of useful functions, enable CSS compression, and give you a warm fuzzy feeling inside. Well, perhaps not that last one but you get the idea.
I’ve been using Sass for a few recent projects and I quite like it although it does give me a slight sense of disconnect from my normal working environment. In case you might be wondering why, I use (shock horror) Dreamweaver as my main coding and development environment. I find it works really well, OK?!
So, I expect to use Sass more and more but I’m not making it my first priority. Instead, I want to spend a lot more time making my final CSS smarter by reading more about OOCSS, SMACCS and similar – and putting these into practice. For me and my ‘typical’ projects, I can put a style sheet together quickly enough so the time saving factor of LESS or Sass is not the main thing. It just seems to make more sense for me (at the moment) to focus on making the end product smarter.
Of course, time saving and writing smarter CSS are not mutually exclusive but I think that concentrating on one of these will be better for me. You may have a different process or be at a different development stage – in which case, all power to your elbow! (or something like that). For me though, the OOCSS route looks better at the minute.
This year, I’ve started a local co-working group in Horsham. It’s always a good idea to regularly review an initiative like this. How is it going? The pros and cons. How do I develop it further? I’ve been thinking about these recently so this post is a good opportunity to summarise and assess progress.
Firstly, a little back story…
With the release of Textpattern 4.5.0 I’m taking the opportunity to update and modernise this site, both on the admin side and the design/build of the site itself. I may well ‘start again’ with Phil Wareham’s new default theme.
While I expect this to go reasonably smoothly, there may be a few glitches over coming days. Bear with me, but if you see anything that isn’t working, let me know in the comments. Thanks!
Update: I’ve decided to improve the site step-by-step rather than with a ‘big bang’ approach. Hopefully, less disruption that way ;-)
I like to run a few personal websites and really enjoy writing articles for these. The articles are not about web-related technical stuff but describe things I get up to in my spare time. I guess this is a bit of a ‘diversion’ for me and one way to get away from my 9-to-5 job as a freelance web developer/designer.
One of these websites is Clive Goes Cycling …
I’ve bought quite a few domain names in the last ten years and also created websites on many of them. Some of these have been personal projects where I had an idea for making millions on the Internet (like we all have) but, no surprise, they failed in that respect. I’ve made some pocket money with Google Adsense on a few of them so that’s been good but I won’t be retiring from my day job as a web designer/developer any time soon.
- Adobe Air
- Quick Tips
- Search engines
- Web design
- Web development
- Web standards
- Website review
Shopify makes it easy to open an online store by providing all the tools and help you need. Click here to try it for free!
- Clive Walker on Decisions, decisions...
- Sven Latham on Decisions, decisions...
- Caron Lesley on Why I'm using Brackets as code editor
- Clive Walker on Why I haven't joined Adobe Creative Cloud
- Caron Lesley on Why I haven't joined Adobe Creative Cloud
- Konrad on Displaying blog category descriptions with Perch