In which I make a local copy of this site, and them manage modifications to it on OS X.
In which I show a solution to the problem of calling for a stylesheet only if it exists.
In which I discuss problems with php for my new child theme, murkymatic. Murkymatic is based on the thematic framework.
In which I provide php code which causes wordpress to add lots of useful class declarations to the HTML - which will provide opportunities for easy styling with CSS
The observant may have noticed that the look of this site has suddenly got rather gaudy. There is a good reason for this - I've been creating a WordPress theme which I want to be as flexible as possible. I.e. a 'bare' theme, which can then be styled easily with css. I know these themes already exist, but I wanted my own, m'kay?
The reason for the gaudy colours? Testing. I wanted the default colours to be fairly obvious, with each main element being distinct so that I could be sure that I had the no typos in the CSS selectors.
I'll leave the theme running for a little while, I'd be interested to hear about any usability issues (other than the horrible colour scheme).
The theme should be fully widgetised, it should have comment threading, avatars and so on.
The theme should be fluid and resize gracefully, as screen width reduces, the images reduce whilst keeping aspect ratio.
Things I know I want to fix - some of these are purely 'behind the scenes':
- I want, at most, one sticky post on the front page. At the moment, it'll put any number on.
- I want to have a tags page which shows the tag cloud.
- Behind the scenes, the entry formatting uses the same template, called when needed by index.php and archive.php. I need to get the single.php template to use this as well in order to minimise maintenance (requires some 'if' statements).
- Do I *need* single.php and archive.php once I've done that?
- Author pages, ideally automatically pulling in gravatars.
- Decent 404 page
- The comment form gets screwed up on a narrow screen and doesn't resize gracefully. I don't know why.
- I want the theme to be accessible. I.e. Good for screen readers and the like. I have no way to test this however, so if you know anyone with a screen reader, please do point them in this direction and ask them to comment (or, pass on their comments should it *really* be unusable).
- Is the order of elements okay?
- aural stylesheet hasn't been done, for me, that'd be coding without testing - I would want a sheet though!
- The tags/related tags stuff - does there need to be a way to, ideally optionally, skip that for screenreaders.... I wonder how (without introducing new screen cruft)
- I'll then package up this rough theme for release, create a duplicate and change the look and feel to customise it. If I find that I have to customise anything other than a stylesheet, I'll need to amend the 'raw' theme.
Things I'm unsure of:
- I've appended categories to tags (with a different class for styling)
- Do I want to keep the related posts thing? It relies on a plugin, so isn't essential for the theme (plugin may be disabled as a recent update caused a problem behind the scenes... I hope I remember to remove this sentence when fixed, but I've couched it as a conditional just in case)
I was looking at my email, when a message from google appeared on the top of the screen. This proclaimed to the world (well, to me...) that if I went into my settings, I could choose a theme for Gmail. I've gone Ninja (I liked the font mainly!)
For more, see the Gmail Blog on the subject.