WordPress 3.0 Implementation

This site is undergoing maintenance to the “look-and-feel” of a new WordPress theme, but is available for general use. During this period, you may see the site with a different appearance from normal as new software is tested.

Style mavens who wish to complain about the current layout should find some other useful way to occupy their time. This is a work in progress.

Things I have already fixed/changed:

  • The original default typesize was a tad too small.  I have bumped it slightly, and also changed the option of how available sizes are displayed for selection.
  • The ability to get an RSS feed for an individual article still exists in WordPress 3.0, but was not included in the new default template.  I have updated the comment section so that this feed now appears just above the comment box.
  • Block quotes now have a shaded background so that the italicized text is not confused for comments of my own.
  • Modify CSS so that underscored text does not intercept character descenders (accessibility).
  • Various links did not need to be underscored (next/previous post, for example).  They no longer have it to save on cluttering up the layout.
  • Bullets in lists have been changed from square to disc.
  • Modify CSS so that some fields now displayed in black are shown in dark green, the standard colour of this site.
  • Make the swan avatar appear without the tedious repetition of an ad-hoc bio line on every post.
  • Implement green/brown colour scheme for links.
  • Fix menu area so separators are all green regardless of “visited/unvisited” status.

Works in progress/planned:

  • Mobile support using standard plugins (see separate post on this topic).
  • Block mobile displays from starting with the complete text of the menu bar and all of its options.

6 thoughts on “WordPress 3.0 Implementation

  1. Hmmn… I think you should change the CSS for blockquote to have a different background (and maybe not be in italics) to avoid it looking like your replies, Steve.

    Steve: Thanks for this. I have noticed that the new “standard” theme has tweaked a lot of the styles, and I have to build my own mini-theme to override what I want to change.


  2. Where did the link to the RSS for the comments for separate entries go (on the non-mobile site)?! That was something that was super-useful!

    Steve: Hmmm … yet another unexpected change.

    I have added the WordPress article-based comment feed just ahead of the comment form.


  3. Well, I’ve got to admit that this is a bit of a shock but, what the hey, I’ll get used to it in due time.


  4. Steve … these new menus are showing your LRT bias again — over 50% (14) of the drop-down menu items deal with LRT or streetcars. Don’t make it so obvious man! Maybe a little more coverage of the Spadina subway would even things out. For instance, the TTC just released reports showing the designs for Hwy 407 and Sheppard W. stations.

    Steve: Shhhhh! I thought nobody had noticed. As for all those stations, maybe I should write up how the TTC consistently underestimated their cost. There is a scandal lurking there, but nobody cares. It’s a subway after all, and we all love subways.


  5. I can see why their cost estimates are way off. They’re going all out on the finishes for these stations — even granite is being used in some places. Did you see the designs for 407 and Sheppard W.? — pretty impressive. I doubt that the underground stations on the Eglinton LRT will be anywhere near as nice.

    The icing on the cake is that this is bound to cause a lot of jealousy and controversy over at UrbanToronto.ca with the territorial subway fanatics who want a DRL built Spadina-style now and oppose any non-416 subway construction — so, if you want to have some fun, we’ll both head over there and tease them about it … and even the score. They weren’t exactly too kind to you the last time you were there.


  6. Please consider adding a Preview function to the Reply panel.

    I try to format my comments properly, but the last two I have submitted have contained formatting errors. Without a Preview function it is quite difficult to catch these.

    I find this function invaluable on other boards I post to, and WordPress seems to offer a large number of plugins for just this purpose.

    Steve: I, your helpful editor, fix a lot, except for writers who appear to be full of hot air. No format checker will pick up on the myriad spelling and grammatical errors that show up in comment. I will have a look at the available plugins, but they must be compatible with the spam filter also in place on comments.


Comments are closed.