Archive | News RSS feed for this section

You Know When You’ve Been Oxtoned

5 Jun

I remember when John blogged about how much traffic he’d gone through since he got listed at StyleGala, CSSBeauty/Vault etc.

Well in like fashion, already my bandwidth report this month has prompted a flurry of panicked emails from me to my host – we’re only 5 days into this new month and I’ve already shifted nearly 2GB in traffic. Just to put that in perspective, I normally do around 1.5 – 1.8 GB per month!.

Just for your interest – here’s what that looks like on a graph.

Anyway, my hosts being exceptionally great chaps have promised me nothing nasty will happen to the site or my bank balance and in return I feel I should definitely let you know what a bloody good bunch of geezers Martin and Khalid at SiteHQ are.

This is a great month for me – John choosing June to be my turn ‘in the barrel’ so to speak has meant a lot more people than usual will get to hear about Autistic Pride Day and my hosts being all round good sorts means they’ll be able to carry on being exposed to it. A lot of people who’ve come across from John’s place have mailed me privately to say how much they’ve liked reading the autism related stuff as well as the design related stuff and that to me is brilliant. So, next time you hear about what a shitty world we live in, remember that people are also generous and kind.

On Having An Entry Rejected By A CSS Gallery

2 Jun

OK. I’m going to have to word this post very carefully. I want to get it upfront that this entry is in no way just a great big sulk about not getting listed on StyleGala or CSS Beauty/Vault or Unmatched Style. Seriously, its not. Stop sniggering.

There has to be a line of quality that differentiates what gets listed and what doesn’t. Thats as it should be – not every design can make it in. But lets get the awkward question out the way – do I think this design should be listed? The honest answer is that I’m ambivalent. It would be nice, but I’m not going to lose any sleep over it if I don’t. So whats the point of this post?

I know that at least one of these sites has come calling just by checking my referrer stats. I further can see that I haven’t been listed (thats not to say I won’t be of course, I really don’t know if anyone’s even submitted the design or not, let alone had the other gallery sites come calling to have a look). So OK – as I said above, its nice to be listed but at the end of the day if I’m not then I’m not. I’m not gagging for a listing – my self confidence has grown enough since I stopped doing just Flash work that I’m not too worried what others think. But what would be great would be some kind of indication as to the factors that led me not to be listed.

Imagine how useful that would be? All designers are interested in pushing themselves and growing past their current boundaries right? What better way than to get some kind of feedback from the people who made the call as to their opinions as to why it didn’t make the cut? It wouldn’t necessarily have to be massively in-depth, just a sort of tickbox affair stating what the main issue(s) was/were and an indication of what needed to be worked on. A paragraph of text at most. StyleGala does this for successful designs – wouldn’t that effort be better placed offering constructive critiques to those that didn’t make it in?

Now I know the guys running these galleries are busy people but wouldn’t that be a great thing for them to do? I know I would really appreciate constructive criticism on a design from some of the best in the business.

Who’s Site Is It Anyway?

31 May

There’s been an uptake in 3rd party apps interacting with websites in ways previously unthought of this year. Two of the biggest known are the Google Content Rewriter and now, Greasemonkey.

What both these things do is alter aspects of a website. The onus in each of these caes is slightly different. Google does it mostly, it seems, for Google whilst Greasemonkey does it for users. The end result is the same however – sites are altered.

This for me throws up lots of interesting questions about sites and the various aspects that can be ‘owned’ and who the various people are that ‘own’ these aspects.

At its most basic level a web page is comprised of three things: markup, design elements and content. Greasemonkey and Google can alter all three of these things. The question then is: should they be allowed to do so? Who ‘owns’ the site?

I take the view that all aspects of my site are owned by me but that by explicitly allowing others to access the content and the design then they have at least a part ownership in that aspect of the page(s). Once its downloaded to their browser then they should be able to alter is as they see fit to suit their needs. In this respect I have less of an issue with Greasemonkey than I do with Google. Greasemonkey is to help users. Google’s little tool is to help Google – they can make money from my content.

You’ve probably noted that in the above paragraph that I didn’t include markup in my list of what I personally find acceptable to alter. This is because I don’t find it acceptable for anything other than me to alter the code used on my site. Changing my code can have implications for how the site does/doesn’t work on the most basic of levels. For example, I use semantic code as I think its important. I use various bits of Javascript to do various things (the comments form spell checker for example) and whilst I can appreciate that users might want to have more control I don’t think that altering my code is acceptable.

At some point there has to be an element of trust. I don’t serve ads, I don’t track anyone with cookies or sessions (except in as much as I do for the comment form details). I don’t use hidden frames and I don’t think users have the right to alter the most basic building block of how I choose to serve content.

I serve content in two formats – markup and RSS. Those, to me, are your options as a user. I think a mutually respectful relationship where I trust you not to make unwanted changes to the functionality of my site and you trust me not to flood you with spam or other ads is important.

Dean Edwards recently wrote a script to disale Greasemonkey.

…GreaseMonkey broke my site. I didn’t realise what the problem was at first. I use a JavaScript syntax highlighter to make code on this site look slightly less boring. It uses some regular expressions and a little bit of DOM scripting. After installing GreaseMonkey I noticed that some of my code samples were completely broken in Firefox.

I entirely agree with Dean here. OK, he’s talking about design elements which I don’t have such an issue with but the fact remains that this Greasemonkey script is interfering in coded elements of the page Dean published. That to me is not acceptable. I find it as annoying as I do Google’s attempt to rewite my content – even if it is much more benign in intent.

There are also a few scripts here that apparently totally disable Greasemonkey. I don’t think anyone really wants that but I can sympathise with site owners wanting their sites to be presented as they intended them.

As a point of note, I installed the script to disable Google rewriting my content straight away. I’m still wavering as to whether or not to install a Greasemonkey killer. I’d be very interested in others opinions on this.

One Month, Three Redesigns

28 May

Well, almost.

As I said in the recent past, the last redesign before this one was created during a bad down spiral – I was very tired and in bad physical shape. Above all else this new redesign I hope is a bit more upbeat.

Its a fairly comprehensive overhaul. I took the opportunity to upgrade to WordPress 1.5.1 and had a think about ways to add value to the site and make it easier for people to find what they need. To that end I’ve totally re-jigged the archives to offer breakdown by date and subject. I’ve also added a (controversial!) Flash RSS Parser that I modified a fair bit from Sam Wan’s RSS Factory. I’m an old-skool Actionscripter so this suited me fine. I’ve also used sIFR for the first time. It was a bit of a fiddle getting the sizes right and its still a bit weird in IE but it works.

Also added is a sidebar of links to relevant articles in the manner of John’s side salad feature. I’ve been daringly naughty here and used a transparent PNG as the div background for this area and (gasp!) used ‘the bad code’ to get it to work in IE – but never fear, all the IE specific code is in a separate CSS file called in conditionally.

For commenter’s I’ve added a spell-checker which isn’t quite functional yet but it just needs a minor tweak from my host works really well.

The big change of course is the fixed | fixed | streeeeetch layout which I have to be honest was a bit intimidating at first but its incredibly liberating – the amount of CSS resizing hacks have plummeted just by utilising this style of layout.

As to the design, I wanted something friendly (hence the vector styles and nice curvy typeface – Vag in case you were wondering). However, I didn’t want to shy away from the fact autism == difference, hence the (overly literal?) stickmen family.

I’m happy with it overall. It feels much more complete and unified than either of my past two designs. It also feels much more ‘mine’. I learnt a lot doing it and thats the biggest payback I guess.

Stats:

  • IE5.* support dropped
  • 800px width support dropped

New Design: Update

27 May

I threatened promised a redesign of this blog and thats whats coming. I’m not ready to launch just yet but I’m not far off. In fact I’m not far off the ‘90% finished ennui‘ stage.

I’m quite pleased with how its turning out so far and, most importantly its allowed me to learn and implement some new skills and revisit some old ones in a new way. A few things the new design will carry:

  • An actual colour scheme instead of brown sludge
  • At least one stretchy column (an idea I nearly ditched after I found out Andy Clarke had launched with it. Then I thought ‘what the hell – its a good system, who cares if its been done?’)
  • A vastly improved Archive system
  • Some Flash – not necessarily sIFR – that I think is functionally very good
  • No support for IE5.* as it only makes up 0.7% of my audience

I’ve toyed with Dean’s IE7 but must admit I’m having a few issues with it – its not running very well in combination with WordPress I think and I’m still mulling over sIFR which I’ve had limited success with in the past but these are side issues. Essentially things are progressing nicely.

This Is What Exhaustion Does

11 May

Call me flighty, call me unsettled but as of next week I’ll be redesigning this blog. Again. Again again. For the third time in a month.

Why? Lots of reasons.

Firstly, I realised that the last 2 incarnations of this blog suffered from something that the previous pink one – which got me nods from CSSVault and CSS Beauty – did not, they were designed by a very tired and approaching burnt out designer.

Truth be told, I never realised until I signed up for the CSSReboot just how much of a physical activity design was. Thats when I realised that being permanantely tired thanks to a daughter that thrives on lack of sleep and being overweight and being in the middle of a major design and content overhaul at my workplace had had an effect on both my ability to be creative and my ability to execute good design.

I don’t hate this design but boy is it drab. Its tired and reflects how I felt designing it. However in the last 4 weeks Megans sleep pattern is more stable, the work website is just about done and I’ve lost nearly a stone and a half in weight and switched to a high fruit/protein diet and feel much better for it.

I’m also totally knocked out by the sheer quality of recent redesigns from various others and want to bring this site up to scratch with a more vibrant design.

So – redesign number 3 will be underway in a little over a week!

Spam: On The Wane?

3 May

Is it just me or has the unremitting flood of spam, um, remitted?

I’m aware that as the proud user of one the worlds leading CMS’ I have a plethora of excellent spam fighting hacks, plug-ins and built in tools at my disposal – from centrally managed blacklists through to advanced comment moderation and server configuration tools but even so, it does seem slightly quiet on the western front.

I’m used to the odd one or two slipping through the net – where a particularly dedicated spammer has visited me in person to negotiate Gatekeeper or they’ve added my Gatekeeper keys to some evil spam database cracking system but its been zip, nada, zlich, zero, bupkis, fuck-all.

Anyone else getting this or am I extremely lucky and yet have obviously just jinxed myself?

Cutting Edge – Why?

25 Apr

Like most of us in this line of work/hobby I stop by the four main CSS galleries every few days to see whats new and make the odd comment if I particularly like a design.

I’ve noticed a trend over the last few months on all these sites in a few of the commenters remarking that a showcased site isn’t using ‘cutting edge’ CSS techniques or that there’s nothing new to see aesthetically and without fail it always puzzles me who is making these comments and why – some of these commenters even say a design isn’t ‘worthy’ of the gallery its been submitted to.

What is the big deal about using cutting edge techniques? Lets not forget that all the designs showcased at these sites are in live production, often serving a commercial purpose. It strikes me as incredibly dangerous to use cutting edge techniques (CSS or otherwise) on clients live sites. The reason these techniques are cutting edge is that they are new, unproven and possibly unstable. The only place I personally would consider utilising cutting edge techniques is on a designated experimentation area. I can’t imagne paying customers being overjoyed to find designs failing due to unstable techniques coming apart in unforseen ways due to lack of testing. Its really very unfair to base judgement on a showcased design on its lack of cutting edge technique – by not using cutting edge technique the designer has proven themselves not only a good designer but also responsible.

And what about all those ‘seen it all before’ comments? What exactly are people unhappy with when they make these comments? If one site is a carbon copy of another then fair enough but if a site merely happens to use a similar information design then I don’t see the issue. One example of this is the amount of complaints that come in when a blog is posted: ‘it just looks like a blog’ is the recurring comment – well no shit, Sherlock – guess what? thats because it is a blog! Blogs are structured the way they are because over time thats how the user goals have shaped the design. At bottom all e-commece sites look pretty much the same too – not aesthetically, but in terms of flow. Why? Because this is how the design of an e-commerce has evolved with the needs of the site user to the fore as oppose to the needs of the site designer to showcase their skillset.

So, does this mean I think all designs should be the same – no way. We need cutting edge technique, we need innovation and we need people to push the boundries but we also need to realise that there is a time and a place to do these things. We also need to realise that a good design is much more than a cutting edge style sheet and lots of graphics.

What sort of site am I talking about? What sort of site is great looking but doesn’t use anything which might impact negatively on user experience – well, John’s recent redesign of Joshuaink is a perfect example. It looks fantastic but at heart, its a very simple, solid blog design. Its beauty is not only skin deep, it goes beyond into the semantics, usability and flow of information. Another is Garrett Dimon’s recent design. In terms of aesthetics its nowhere near the same as Joshuaink but look at the semantics and look at the information flow and its plain to see that what we have here is ‘just another blog’ but just like John’s redesign it has a beauty and style that can be appreciated for what it is – a great design, executed perfectly.

Lets not get caught up in a need to be cutting edge merely for the sake of being cutting edge. Instead lets appreciate good design for what it is. If it doesn’t float your boat then fine but don’t fault a good design merely because its not using cutting edge technique.

Redesign Redux

23 Apr

Whereas the previous design was brash, over-heavy and looked bad in certain situations, hopefully this design is the antithesis of that.

What I hoped to do with this design is bring my content to the fore and improve usability but at the same time create an aesthetic that promoted a feeling of calmness and willingness to continue as well as evoking trust.

The previous design was basically trying too hard. I forgot that the primary role of a blog was not to use every CSS trick in the book and ‘force’ a design on people but rather to make it easy for users to read the content.

To that end the body text is the darkest colour on the screen, I’ve set the ‘skip’ link to be viewable at all times rather than hidden via CSS. Links are unobtrusive rather than disrupting the flow of the content and external links are all shown and grouped better rather than hiding some away.

The ‘suggest’ feature whilst a nifty trick was hardly used so I’ve dropped that – it made me uncomfortable that it invalidated the markup anyway – and behind the scenes I’ve started introducing more categories in order to make finding things easier. Lastly, I’ve also tidied up the comments and reduced them to something less hard on the eyes – I think (hope!) I’ve made better use of Gravatars this time too.

So, thats it. I still couldn’t hang on for the CSS Reboot but I’m happier with this design than I was before. For now anyway ;o)

Change Is Coming

22 Apr

I’ve done a very difficult thing this week – I’ve admitted to myself that this design is poor.

When I set out tor edesign from the pink design I had last time I had two goals: first, to improve the readability and second to have something nice to look at. Its fair to say that I’ve compromised both of those goals.

This design is overdone, swamps the middle of the page and is way, way too heavy on the eyes. It doesn’t scan well on shorter entries and the lack of a footer makes the whole page unbalanced. I concentrated so much on grandstanding that I forgot a few of the fundemental rules of design. I designed solely for me.

In a way I’m glad I made this live before the CSS Reboot because it certainly wouldn’t grace that competition. I’m not fishing for compliments at all here but clarity after the fact is all too easy and clarity when designing for onesself is never easy to come by.

I have to view this as a learning process and so I’ll be redesigning this blog as much as I can over the next few days. In a way, it’ll tie in nicely to the fact that I’ve just upgraded WordPress to 1.5. Expect something radically different to this design that concentrates on the needs of the user when reading the page, rather than showing all the nifty CSS tricks I’ve learnt.

By the way, if anyone’s having trouble commenting please mail me kevleitchATgmailDOTcom. As I say, I’ve just upgraded and I know at least one person has had trouble adding comments.