Currently it's quite hard to customise the display of post metadata, outside the limited options available for individual elements (dates, authors). Emmanuel Gravel has proposed a single action hook, th_metadata. My approach would more likely be along the lines of the tarski_navbar hook, where elements are added and removed via filters.

The 'Asides' functionality is all hard-coded, limited to one category, can't be disabled programmatically etc. Improving it would allow plugin authors to extend or remove it, while keeping its default mode of operation the same.

PHP not having many good facilities for abstraction is no reason to anger the object-oriented gods. We can peel a few layers from this particular onion and still retain backwards-compatibility with regards to its API.

Lots of things end up in odd places, so this needs the same care and attention that the theme stylesheet has had.

WP core is now minifying a lot more stuff, and this can help a lot with the load times for people whose hosts don't have gzip enabled (and a little for those that do).

This would be more pressing if Tarski loaded a lot of JavaScript, but its JS dependencies are currently very small; this may change in the future.

Currently this is ruled out by the various IDs in use, plus probably some other issues. I tried to do this once but ran out of patience. A decent theme ought to be able to manage this.

Should include the translations for all versions of Tarski. Binary (.mo) files should be included in the repository only when relevant source files (.po) do not exist. There are some other pieces of work that would need to be done in concert with this:

• Create new gettext generation tool for Tarski, to make it easier to automatically generate the POT file upon release
• Create new translation packaging tool to generate translation binaries from source and zip them up