-
201011 Mar
Posted in Site Updates
The announcement of our redesign last month received an overwhelming number of comments, with the majority expressing negative feedback. The main concerns raised were that the new design was too dark, lifeless / boring and lacking in fun, spirit and character.
As previously stated, the main reason for the redesign was from a functional perspective to allow us to expand the site and take it forward. The reason that the old design was removed, and not simply recoded to make the functional changes required, was in fact due to a number of negative comments I had received about the previous design since taking over the site in July 2009, however following the large number of comments received over the last three weeks in support of the previous design, it is now apparent that these negative comments were not representative of the views of the majority of our readers. With this in mind I have made the decision to temporarily reinstate the old design whilst considering the best way to move forward with the site.
Have Your Say
Taking into account the feedback received from you the readers, I believe there are two options to take the site foward:
1) To recode the current theme, keeping the overall look and feel of the site, but making the necessary functional changes.
2) To hold a design competition, allowing you the readers to submit potential new designs for the site, as suggested by a number of comments.
Please let me know your comments / thoughts on the subject below.
You can skip to the end and leave a response.
-
Comments
-
01.
That’s a good news :)
Thanks
-
02.
Michal says:Comment » March 11th, 2010 at 6:23 pm
I do like this one, but I really disliked the new "dark blue" one. So I vote for "keep and recode the current one."
-
03.
I vote for: “1) To recode the current theme, keeping the overall look and feel of the site, but making the necessary functional changes.”
-
04.
To tell the truth I don’t really care as long as medium sized fonts will be used for content… I doubt it’ll change any time soon though.
-
05.
3. Accept that people will whine and do your own thing.
-
06.
-
07.
CyberSkull says:Comment » March 11th, 2010 at 8:45 pm
I agree with you in trying to move the structure of the design forward, but it was the look & feel that was wrong. I like the look of this version and I am looking forward to seeing what you do to advance it. :D
-
08.
You’re going to have to recode this one. People hate drastic change. If you want to evolve in a direction, you have to do it in small unnoticeable steps.
-
09.
Richard Ayotte says:Comment » March 11th, 2010 at 9:13 pm
– Recode the existing site using CSS3 as much as possible.
– Ignore what it looks like in IE*
– like Jeffrey Gilbert said, small gradual changes. -
10.
i’m for recoding this one. it’s a great look, why mess with it?
glad to see it’s back for the meantime!
-
11.
It’s important to keep in mind that if you hear feedback, it will most likely skew negative. If people are happy, maybe some will give words of appreciation and/or encouragement, but most will be content to just silently use the site to accomplish their goal. If people are unhappy—when something isn’t going their way—they’ll tell you about it in the hopes that you’ll fix it.
Jeffrey has a point in that people hate drastic change. My favorite examples are the numerous complaints from facebook users *every* time the interface is updated. However, I believe that when the change is in the right direction, people will get over their knee-jerk reactions and end up getting used to The New Way. I hope that three weeks was enough time to gauge whether the change was in the right direction or not.
Chris, I think you should get started on option #1. When you make the necessary functional changes, then you can worry about a redesign.
-
12.
Thorsten says:Comment » March 11th, 2010 at 10:12 pm
I’m for 1). This design is much cooler than the newer bland one.
-
13.
If you tweaked the RSS feed so that it provided all the content of a post instead of a brief summary, the site’s design wouldn’t much matter to me at all.
-
14.
4. Get back to publishing articles about CSS3 and fit in #1 when you can. Seriously, I’ve been reading lots of articles and seeing sites relating to CSS3 lately, but none of them have been mentioned here. http://css3please.com/ is a good example.
-
15.
@John Faulds – I already have an article in the works about CSS3Please! and CSS3Generator.com, should be ready tomorrow
-
16.
“I do like this one, but I really disliked the new “dark blue” one. So I vote for “keep and recode the current one.””
same here :) -
17.
This design isn’t fantastic, but I didn’t feel that the dark blue design showed off enough CSS3. So I think option #2 would be a great idea – let designers come up with a real flagship for CSS3-based development.
-
18.
Well done for listening to your audience, Chris.
I’d be suggesting you recode this one but take it forward a bit too. e.g. it needs more whitespace – it’s a bit cluttered and in some parts (such as below header) it struggles to breathe; and you might want to refresh colors and graphics to something more contemporary (it does look a little 2008) but maintain the same overall look and feel.
As a few others said, smaller changes.It’s a good design, it just needs to a bit of buffing every now and again.
If (and when) you were to do another total redesign, you’ve got to have the primary goal as being a leading edge feel. You want a design that people want to copy.
It’s funny we’re all full of advice but none of us have suggested #2. :) We all know how difficult a redesign is.
-
19.
correction, one suggested #2 while I wrote my previous reply. :)
-
20.
I vote for number one: I like this high spirited design. I suppose if someone proposed a different design of the same caliber, I wouldn’t mind the switch.
Let’s see what other have to say.
-
21.
I vote for either.. as long as the site doesn’t end up looking like the previous redesign. I would like to see a lot more CSS3… after all that’s what this site is about. One last thought – please avoid heavy box-shadow.
-
22.
I vote option 1.
Why option 1?
The current white/blue is beautiful and fresh while still leaving a lot of room for the content.
Yes, dont forget the content; You don’t need to have lots of css3 in the site design. Feel free to, but don’t make that a main goal – after all, the demos are a lot more useful for seeing exactly what one specific css feature does.Why not option 2?
Because there is no need to spend hours redesigning something that works well. Instead, spend that time adding more quality content and clear examples, not to mention keep the existing articles up to date with regards to browser versions and support (some are quite dated). That content is what we are here for. -
23.
I have to say I like the older theme. It looks much more creative and free, as opposed to simple and boring. Although you should rewrite it so things like rounded corners and gradients are done with CSS3 (since this _is_ the CSS3 site).
-
24.
-
25.
I vote option 1. This is a pretty cool design. The dark design wasn’t -bad- per se, the main problem was that it’s not memorable. This design is very memorable, and it clearly helps further the brand of this blog… even down to the logos this difference is very apparent.
With all of that said; the vast majority of comments you’re going to get on anything will be negative. Don’t let us, the great unwashed masses, get you down.
-
26.
oh yeah, I’m with Marc: either way you go, please avoid the heavy text shadow. it made reading the titles difficult, and one of the main selling points of css3 is that it can help make things more readable.
-
27.
I just got here. What did the other site look like? please post a link to a screenshot or something so I can compare.
Please Note: I have been in the tech business for a looooooong time. People always complain about change and it is not always because the new thing is worse. Usually it’s because they just aren’t used to the change yet.
-
28.
I vote for number 2! :) More fun, more engagement, and the website needs to be refreshed from time to time anyway :)
-
29.
Raymond Torres says:Comment » March 12th, 2010 at 10:14 am
I vote for #1.
The new design really shocked me. Thx for taking it back :) -
30.
If anything the site should utilize more CSS3 in it’s design. The next version of my site will use JavaScript to determine the correct browser/version for which to apply CSS3 to avoid errors in the console. Since it’s not yet public if you’d like to implement this in to the site feel free to email me. It’s actually not too complex and doesn’t require any frameworks.
-
31.
As John hints, I would expect the site to be a CSS3 playground, use what you write about. As for the design, why not take a stand, alright there may have been some negative feedback, but the beauty of CSS is that the design is separate from the function, so address issues people may have using the topic of the site!
As for “if it ain’t broke, don’t fix it comment”, there’s the old saying that if Henry Ford had given his customers what they wanted, they’d have asked for faster horses.
Be bold. Its the content I’m here for.
PS – I hate this design! But that’s just an opinion!
-
32.
People always complain, just consider how people react when there’s a change on facebook…I’m kind of a nazi, but you shouldn’t ask them what they think, and impose your own view, as anyway, there will always be a minority complaining and a majority not caring…And this minority is basically the one that will come back regularly. So to me, just make sure the ergonomy is ensured, and then, do whatever you want…
-
33.
Thanks for reverting to this design!
I don’t know how messy the code for this theme is but I’d say tidy it up slowly and change it in increments to implement the features you have in mind. This way we can give you feedback along the way instead of saying at the end of your work “No, thanks”.
-
34.
CyberSkull says:Comment » March 12th, 2010 at 2:57 pm
Can you provide us with a zipped sample of what you tried to do with the new design? I think we’d be able to help out if we had the output of where you are trying to go with your code. :D
-
35.
Evolve/recode this design.
The ‘redesign’ you just had used css3 but was a really poor/dull design.
This design has a nice ‘feel’ but it feels weak like it was never really completed. You should keep the direction of this design and move it along.
Use as few ‘hacks’ / images to achieve the build via as much CSS as possible.
You should practice what you preach and one thing that really lets this site down for me is that it doesn’t. It could be easily changed.
-
36.
This layout is sick, so I say keep it and recode it. Having a design contest is a good community idea, but this theme is what I would think of when I think of CSS.
-
37.
Waldir says:Comment » March 13th, 2010 at 1:42 am
I second Gyrobo’s comment above. Please provide the full feed
-
38.
You could do both. :) A competition sounds fun, and I think this audience would come up with a lot of cool options. You could even present the best ones that don’t win as alternate style sheets! But to do that, you need them to have a common markup structure. So I’d say, start with this design, tweak it until you get a markup structure that’s fully functional, request some pre-competition feedback from would-be participants on the structure, and then open it up for design.
-
39.
-
40.
Very pleased when I arrived here today to see the old design back!
So much easier on the eye. =)
-
41.
I am very pleased to see the new design back as well. And I’m sure the coding should go well, as development and design are separate. A theme shouldn’t affect how a site works, functionally. Different themes will load different backgrounds and maybe cause some slowdown when it comes to load time, but it can work out alright. Just make sure it’s very CCS3-ish when complete! :D xD
-
42.
yes, this design is much better, I was shocked and thought I had entered a wrong site when seeing the new bland looking design. Holding a design competition would be great too.
-
43.
I like both & always interested in seeing change.
But small progressive changes maybe more appropiate – ever noticed how much people complain when Facebook make changes to the UI?
-
44.
I vote for one. The design looks really nice. I had the tab for the box-shadow with the old design open for 2weeks now and was really happy to see the site didn’t go into the new design when refreshing.
I double Josh’s comment for the new code to be VERY CSS3-ish :) -
45.
-
46.
Having never seen this layout till today, I am still shocked… at first I thought I stumbled across a daycare’s page… not sure what to think of this design other than, where are the unicorns?
-
47.
I I liked the redesign better my self, it was simple and informative. I don’t usually come to this site to be entertained except by CSS3 itself.
-
48.
Although I did not send an email to let you know I really didn’t like the design. Now the main reason for it was not becaue it was ugly (it wasn’t ugly), or even that it was flat and dull (which I think it was), but simply this: it didn’t feel like CSS3.info!
I would argue that CSS3.info has become a brand of sorts, one with a warm personality. I hope you attempt a redesign again, but keep this in mind this time.
I hope you haven’t been to demotivated by the negative reactions, doing redesigns is no easy thing! I hope you don’t do a competition, but work closeley with some talanted designers (or simply yourself), and make a new site that is fresher and newer, yet still have the warmth and personality that we love in the current design of CSS3.info.
I wish you the best of luck!
-
49.
Some useful comments, too many to say I agree with etc..
But i think going for option #1 of recoding it will work best. Echoing previous comments – small gradual changes are better rather than the full blown re-branding and re-design with the last attempt.
Redesign the site, but dont rebrand it.
I’ll be looking forward to the next one :)
-
50.
lucideer says:Comment » March 16th, 2010 at 5:59 pm
Why not go with both options?
#1 Make any functional changes you need
then
#2 Hold a design competition to allow people to contribute their creative works using the newly coded site
-
01.
