Why using Kubrick on 1.3 is a mistake
I am going to get flamed here and that is fine but I am going to voice my opinion on this one. The default template in WP sucks, this is something most heavy users and early adapters know. But replacing it with a version of Michael Hellerman’s Kubrick is a bigger mistake.
I will admit that it is nice on the eyes but when I tried to load it on a brand new test install (Mingus) it had htaccess problems. Then to edit it to make it have a banner graphic etc I have to edit it with photoshop??? How many people can afford photoshop. Let’s say Matt converts it out to css, is he also going to take out the plugins or expect all brand new users to learn enough on their first day to learn how to turn it on. I think it is going to be so hard to edit that most people won’t meaning very bland pages that all look alike (are we trying to become MT), I know I don’t want it so how many files will I have to delete to get rid of it but I know it was a pain to get off my test install.
I think there are a lot of people who have worked hard to have an easily editable templates for WP. One of the things I loved about WP over MT is that I did not have to be a rocket scientist to make my blog pretty. I love WP and generally like the development cycle we have been on, but I am not sure that going from a very bad template to a really complex one is the way to go.
- The topic ‘Why using Kubrick on 1.3 is a mistake’ is closed to new replies.