- SP361 - Pyramids and Dropouts
- SP416 - Chess Engines Don't Always Get It
- SP034 - How Top Players Treat the Same Chess960 Position
- SP448 - Chess960 Twins
- SP534 - Chess960 Opening Theory
- SP059 - Undefended Pawns in Chess960 Start Positions
- SP024 - A Followup, an Error, and an Insight
- SP534 - A Database of Chess960 Start Positions
- SP002 - An Exercise in Chess960 Positional Thinking
- SP900 - Lesson in Chess960 Opening Patterns
- SP787 - Chess960? I'm Hooked!
Using a blog as a database to manage content isn't obvious, but I hit on the idea of assigning specific historical dates to specific SPs. For example, 1 January in the year 1 AD (or any day in that year) could be SP001, a day in the year 2 AD could be SP002, and so on through 1 January 960 for SP960. (In fact, chess960 SPs are numbered 0 to 959, but that's a detail that doesn't change the concept.)
A key question to use this scheme is how far back I can pre-date blog posts. I tested the possibilities in Find Earliest Possible Post, and discovered that Blogger.com -- the software service domain for blogs published at Blogspot.com -- allows only the dates 1 January 2000 or later. This is a limitation for blogs that treat historical subjects. I can easily imagine that it would be useful for a WWII blog to pin posts against specific dates in the 1930s and 1940s, or for an American Civil War blog to tie posts to dates in the 1860s. Since Blogspot doesn't work that way, I had to find another method.
Another idea would be to use the category concept to tie posts together. For example, a category called 'SP518' would pull together all posts referencing the traditional start position (RNBQKBNR), while category 'SP534' would do the same for its twin (RNBKQBNR). This might in fact be the best method to keep track of SPs. One drawback is that with 960 categories, the length of the category sidebar would become a nuisance to scroll.
Next I hit on the idea of assigning SPs to specific dates starting 1 January 2000. That date would be used for SP000, 2 January would be SP001, and so on. It's a little clumsy to keep track of which date corresponds to which SP, but it's easy to invent navigational tools that locate SPs quickly. The category system isn't excluded for important positions like SP518.
The start of each month maps to specific SPs according to the following table. Using this scheme the post 'SP787 - Chess960? I'm Hooked!' would be referenced under 27 February 2002.
2000-01-01 (31 days) : SP000 BBQNNRKR
2000-02-01 (29 days) : SP031 NQNRKRBB
2000-03-01 (31 days) : SP059 NNRQBKRB
2000-04-01 (30 days) : SP090 NNRKBBRQ
2000-05-01 (31 days) : SP120 NBQRBNKR
2000-06-01 (30 days) : SP151 NRBNQKRB
2000-07-01 (31 days) : SP181 NRBBNKRQ
2000-08-01 (31 days) : SP212 NBBQRKNR
2000-09-01 (30 days) : SP243 BNRKQNRB
2000-10-01 (31 days) : SP273 BNRBKNRQ
2000-11-01 (30 days) : SP304 BBNQRKRN
2000-12-01 (31 days) : SP334 NRQKRBBN
2001-01-01 (31 days) : SP365 NRKBRQBN
2001-02-01 (28 days) : SP396 QBRNNKBR
2001-03-01 (31 days) : SP424 RBNQBNKR
2001-04-01 (30 days) : SP455 RNBNKQRB
2001-05-01 (31 days) : SP485 QRBBNKNR
2001-06-01 (30 days) : SP516 RBBNQKNR
2001-07-01 (31 days) : SP546 BRNKNBQR
2001-08-01 (31 days) : SP577 BQRBNKRN
2001-09-01 (30 days) : SP608 BBRNQKRN
2001-10-01 (31 days) : SP638 RNKQRBBN
2001-11-01 (30 days) : SP669 RNKBRNBQ
2001-12-01 (31 days) : SP699 RQKNBNRB
2002-01-01 (31 days) : SP730 RKNQBBNR
2002-02-01 (28 days) : SP761 RKNBBNRQ
2002-03-01 (31 days) : SP789 RQBBKNRN
2002-04-01 (30 days) : SP820 RBBKNQRN
2002-05-01 (31 days) : SP850 BRKNRBNQ
2002-06-01 (30 days) : SP881 BRQBKRNN
2002-07-01 (31 days) : SP911 RKQRNNBB
2002-08-01 (31 days) : SP942 RKRNQBBN
Note that I've excluded 29 February 2000 from the table. This keeps the numbering consistent across Februaries in different years. I'll introduce this scheme over the next few days to see how it works in practice.