Discovered today that thumbshots.com died on November 10th. Obituary at www.thumbshots.com/Support/...3/EntryID/47/Default.aspxa Odd spammy text at the bottom of the page makes it look like they've either gone insane or been hacked too. Some of you have been using thumbshots.com thumbshots in WSN. It used to be the default, but for the past few years pagepeeker has been the default with thumbshots.com available via the thumbshotskey tweak. With today's WSN releases, I've retired the thumbshotskey tweak and switched all sites to pagepeeker.
Structured data markup is basically another way of helping search engines understand your site. It describes pages in terms of objects or concepts and how they relate to each other. For a news article for example, it tells what the headline is, the description, the images, and the author details. A couple years ago, I spent a lot of time marking up the WSN templates with schema.org structured data markup. It made a bit of a mess out of the HTML and was easy to end up with an incomplete version of, but it conveyed the basic info.
A few months ago, Google Maps drastically lowered their free use allowance. The vast majority of us are, alas, still in no danger of having any websites popular enough to hit the limit. For a customer who was hitting the limit, I added a 'click to load map' option in WSN to reduce their number of maps impressions. That, of course, is a far from ideal solution. What we really need is an alterative mapping service. I thought about Bing, but they have limits of their own and may put a tighter squeeze on people at any time.
In WSN 10.2, I spent a lot of time on WordPress integration. Perfected the theme integration, and made a WordPress plugin for each WSN script that installs and integrates and manages it and provides access to the WSN admin from WordPress. While starting work on 10.3, I realized WSN was actually integrating more fully with WordPress than with other WSNs. Time to fix that. The first step was to take the previously hacky template integration and turn it into something standard and reliable.
Thought I'd revive this blog to go into more detail about developments in the WSN 10.3 series so far. Let's start with an entry about the bootstrap-related developments, which have been numerous. To free things up a bit from the non-bootstrap legacy, WSN now has two different base styles. When using a legacy (non-bootstrap) theme, the schemas/base.css gets called in as before -- but for bootstrap themes, WSN now calls schemas/bootstrapbase.css instead. I've been trimming some legacy cruft out of bootstrapbase.css and trying to let as much of bootstrap's own rules take precedence as possible.