The roadmap has been updated to give a more accurate and complete picture of what’s going to be in 1.2, but I thought I’d write up a brief summary of where things stand and where we go from here.
Firstly, I’ve rewritten a fair amount of the CSS, to make it more flexible and extensible. Content areas (such as entries, comments and so on) are now denoted by the content class, while the two columns are referred to by primary and secondary classes. This replaces a large and disparate set of classes and ids, making the code cleaner and easier to extend and modify. Additional stylesheets, for example, should now be much easier to write.
Secondly, Chris has been working on the Tarski Options page, cleaning it up and improving it substantially. We hope that the new version will be easier and more intuitive to use.
There are also the usual raft of tweaks and improvements, including the much-requested pagination and next/previous links, better trackback and language support, and a new and improved loop.php file which should make modifications based on the Tarski code much easier to implement.
1.2 beta test
Because there are such substantial alterations to the code, we want to run a small test before releasing it publicly. Sign up for the 1.2 beta on this forum thread.
Beta applications are now closed.
Tags: 1.2, beta test, customisability, features, forum, modifications, roadmap, theme hooks, themes, tweaks
-
I see some wonderful changes on the way.
A clean Options page will be nice to have.Thank you for sharing this exciting news with me !
-
Since you are still working on the next version there might be some time, space, beer and pizza for yet another stylish feature: I’m using Darius Dunker’s Intypo plugin to change stadard typography to the correct German version. Unfortunately, this plugin doesn’t reach into footer, sidebar and archives. Wouldn’t it be a neat idea to incorporate the plugin into the theme? That would give the whole thing the first international spin.
-
I’ll see what we can do, once Chris gets back from his honeymoon.
-
Wonderful
-
Just stumbled over another issue, this time concerning search engine behaviour: The recent articles in the footer seem to produce confusing leads with Google. Just this morning some searching life form was looking for something a bishop said and was lead to my gallery page (“Bilder”). The searched words must have appeared in the footer when the Googlebot came by. Unfortunately, the gallery isn’t as often updated as the recent articles section and – violà – the user found nothing but confusion. Perhaps a
rel="noindex"might help, even though I have no idea if that tag exist in the first place. -
Funny you should mention this, we had another user wanting us to change ‘Recent Articles’ to ‘Previous Articles’ and have it list the five articles prior to the displayed one (on the single post view), as some kind of SEO thing. Anyway, I’ll look into it.
-
Changing “ecent” to “previous” might be a fine service for readers, but nobody gets READERS by misleading search engine entries. All that results from that are just HITS. I even doubt that frustrated users are willing to click on Adsense links or anything else. They just go away after a second or two and thereby ruin the visit length stats, which is just as undesireable in SEO terms.
Comments are now closed.
7 comments