If you're actually looking at this page on the web, rather than viewing it in Google Reader as my stats say is more likely, you'll have had a bit of a surprise yesterday.  This is why I've been so quiet recently: I estimate that I've spent something like four man days on this skin and I've got to admit I'm quite exhausted.  Although Origami is a good professional skin, half of the .NET internet is using it and my customizations probably weren't noticeable to most of the users of the site. Let me set out what I wanted to...

The good news is, skins have hardly changed in Subtext 2.0.  The skins were very powerful in 1.9, so there wasn't a big reason to change them.  The bad news is, they're not quite the same.  If you've got your own skin, here's all you need to do: Copy across any non-standard skin you were using from your version 1 folder. Copy across the skin settings from the old Admin/Skin.config to the new one. If the skin is locked, put a space in the web.config first, which will unlock the skin.  Note that if you're using a modified...

I know a fair bit of CSS.  I know about the three pixel bug, I've even contributed IE5 fixes to three column layout solutions.  However, I've just been reminded extremely forcefully of my limitations. As is pretty obvious, I'm using SubText as my blogging engine.  It's a good, fully featured system that supports more use cases than you might imagine if you're still thinking "How hard can it be to write a blog engine?".  It comes with a number of default skins and a "Naked" skin for developing your own skins. The skinning system is really powerful and very easy to understand. ...