Commit 54bbcf9b5ade7042142bafcfbb3a4e508bef66a0
Replace links to thetwaddle.co.uk
Grey Nicholson committed on 7/2/2023, 8:50:15 PMParent: 8e0d7e643c647b11a09fa74cf75bd78b828004c6
Files changed
| content/brandnewcms.md | changed |
| content/ensemantic.md | changed |
| content/hiatus.md | changed |
| content/six.md | changed |
| content/tfifirday.md | changed |
| content/weblog035.md | changed |
| content/weblog049.md | changed |
| content/brandnewcms.md | |||
|---|---|---|---|
| @@ -12,9 +12,9 @@ | |||
| 12 | 12 … | title: "The Twaddlebot has been unleashed" | |
| 13 | 13 … | description: "About the Twaddlebot, Mooquackwhatnotbot's older, simpler brother" | |
| 14 | 14 … | rel: related | |
| 15 | 15 … | type: text/html | |
| 16 | - - url: http://purl.org/thetwaddle/ | ||
| 16 … | + - url: https://gkn.me.uk/thetwaddle/ | ||
| 17 | 17 … | title: "El Twad" | |
| 18 | 18 … | description: "The Twaddle, produce of the Twaddlebot" | |
| 19 | 19 … | rel: related | |
| 20 | 20 … | type: aplication/xhtml+xml | |
| @@ -24,9 +24,9 @@ | |||
| 24 | 24 … | <p> | |
| 25 | 25 … | ...if you ask nicely. Mooquackwooftweetmeow is now, like The Twaddle, generated from arbitrary <abbr title="Extensible Markup Language">XML</abbr> using batch <abbr title="Extensible Stylesheet Language Transformations">XSLT</abbr>. If that's completely foreign to you, the rest probably will be (but I'll try my best). | |
| 26 | 26 … | </p> | |
| 27 | 27 … | <p> | |
| 28 | -At <a href="http://www.thetwaddle.co.uk/">El Twad</a>, everything is done in nice, distinct articles - there are no piddly little entries like here. So for The Twaddle, each article can be kept in its own file. These files are then each passed through the same XSLT template/filter, resulting in similarly structured pages, each with different content. The filter uses a little <code>class</code>- and <code>id</code>-based trickery to implement the differences between the front page, the Articles page, the other admin pages and the articles; these amount to a different set of meta-blurb around the outside of the main content. | ||
| 28 … | +At <a href="https://gkn.me.uk/thetwaddle/">El Twad</a>, everything is done in nice, distinct articles - there are no piddly little entries like here. So for The Twaddle, each article can be kept in its own file. These files are then each passed through the same XSLT template/filter, resulting in similarly structured pages, each with different content. The filter uses a little <code>class</code>- and <code>id</code>-based trickery to implement the differences between the front page, the Articles page, the other admin pages and the articles; these amount to a different set of meta-blurb around the outside of the main content. | ||
| 29 | 29 … | </p> | |
| 30 | 30 … | <p> | |
| 31 | 31 … | Here, however, it'd be hopelessly impractical - or rather, inconvenient - to have a separate file for each entry. Especially when an entry may be no more that a couple of lines. So everything must live in one big file - <code>mqwtm.xml</code>, The Big, Bad Source File. If I have one source file and want to create many pages (which would be nice), I need many XSLT filters. | |
| 32 | 32 … | </p> | |
| content/ensemantic.md | ||
|---|---|---|
| @@ -16,9 +16,9 @@ | ||
| 16 | 16 … | |
| 17 | 17 … | --- |
| 18 | 18 … | |
| 19 | 19 … | <p> |
| 20 | -I don't like being wrong. I like it even less when everyone else is wrong and I can't (or shouldn't) tell them, for reasons of etiquette. I suppose I'm just finicky, which is why I spend quite a bit of time reviewing my own websites, <a href="/" title="Mooquackwhatnot">Here</a> and <a href="http://www.thetwaddle.co.uk/" title="El Twad">There</a>, enjoying their majesty. Or something. | |
| 20 … | +I don't like being wrong. I like it even less when everyone else is wrong and I can't (or shouldn't) tell them, for reasons of etiquette. I suppose I'm just finicky, which is why I spend quite a bit of time reviewing my own websites, <a href="/" title="Mooquackwhatnot">Here</a> and <a href="https://gkn.me.uk/thetwaddle/" title="El Twad">There</a>, enjoying their majesty. Or something. | |
| 21 | 21 … | </p> |
| 22 | 22 … | <p> |
| 23 | 23 … | It's OK when I don't know that a rule is being broken, or that something is just wrong. Unfortunately, I'm also just a little bit curious, so I eventually learn the rules, and then notice when things disobey them. |
| 24 | 24 … | </p> |
| content/hiatus.md | ||
|---|---|---|
| @@ -22,14 +22,14 @@ | ||
| 22 | 22 … | title: "Flickr Pictures" |
| 23 | 23 … | description: "Colours and shapes and stuff." |
| 24 | 24 … | rel: related |
| 25 | 25 … | type: text/html |
| 26 | - - url: http://www.thetwaddle.co.uk | |
| 26 … | + - url: https://gkn.me.uk/thetwaddle/ | |
| 27 | 27 … | title: "The Twaddle" |
| 28 | 28 … | description: "Mostly random." |
| 29 | 29 … | rel: related |
| 30 | 30 … | type: text/html |
| 31 | - - url: http://www.thetwaddle.co.uk/bollocks | |
| 31 … | + - url: https://gkn.me.uk/thetwaddle/bollocks | |
| 32 | 32 … | title: "The Bollocks" |
| 33 | 33 … | description: "Spin-off random." |
| 34 | 34 … | rel: related |
| 35 | 35 … | type: text/html |
| @@ -39,9 +39,9 @@ | ||
| 39 | 39 … | <p> |
| 40 | 40 … | I don't think Mooquackwooftweetmeow has ever really hit its stride. There may have been <a href="/weblog021" title="Planet X-2, for example">a few moments</a> back when the Mooquackwooftweetmeow 4 weblog was new, and perhaps <a href="/planetx4" title="Planet X-4 was pretty good">the odd moment of glory fairly recently</a>; but it's never been a constant fountain of genius. |
| 41 | 41 … | </p> |
| 42 | 42 … | <p> |
| 43 | -Now, I'm not saying that Mooquackwooftweetmeow will <em>never</em> gather momentum and flourish into the most spectacularly astounding website ever, just that it won't be doing so any time soon. <em>Especially</em> since Mooquackwooftweetmeow currently lives in my university webspace and I recently left university, which means there's a pretty good chance it and <a href="http://www.thetwaddle.co.uk/">The Twaddle</a> will fall off the edge of the internet at some point in the near future. | |
| 43 … | +Now, I'm not saying that Mooquackwooftweetmeow will <em>never</em> gather momentum and flourish into the most spectacularly astounding website ever, just that it won't be doing so any time soon. <em>Especially</em> since Mooquackwooftweetmeow currently lives in my university webspace and I recently left university, which means there's a pretty good chance it and <a href="https://gkn.me.uk/thetwaddle/">The Twaddle</a> will fall off the edge of the internet at some point in the near future. | |
| 44 | 44 … | </p> |
| 45 | 45 … | <p> |
| 46 | 46 … | I <em>am</em> doing other stuff—it just all lives elsewhere on the web—so in the meantime, <a href="/">the front page</a> has morphed into a summary of that stuff. The Mooquackwhatnotbot is a clunky old thing, and my connection to the university's servers is a bit dodgy at the best of times; so having The Man host my content is considerably more convenient than doing everything myself. |
| 47 | 47 … | </p> |
| content/six.md | ||
|---|---|---|
| @@ -38,9 +38,9 @@ | ||
| 38 | 38 … | <p> |
| 39 | 39 … | A lot of <abbr class="caps">TV</abbr> programmes (particularly recent American dramas) have their title sequences at the <em>end</em> of the first part; I thought this might be a good idea to apply to the site. So I got rid of the <em>site</em>'s title from the top of the page, and put the <em>entry</em>'s title front-and-centre instead. This was the starting point for Spica. I've kept the links to other parts of the page at the top—they <em>are</em> actually useful: maybe you're trying to go a few entries forwards, so you just want the link to the next entry, and don't actually want to read <em>this</em> entry. The skip-links save lots of scrolling, and are pretty essential for keeping the site easy to use for everyone (especially keyboard-users). |
| 40 | 40 … | </p> |
| 41 | 41 … | <p> |
| 42 | -At the bottom of every entry is essentially a replica of the front page—I'm <a href="http://powazek.com/2005/09/000540.html" title="...in which Derek Powazek rewards readers that actually read all the way to the bottom of the page">embracing my bottom</a>; been doing it since Canopus, <em>and</em> over at <a href="http://www.thetwaddle.co.uk/" title="...in which I embrace The Twaddle's bottom">The Twaddle</a>. Or rather: the front page is just an entry page minus the entry—a generic reception page. This was easy to do now that every page shares a single template. I did consider putting all the bottom-stuff on the <em>archive</em> pages as well, but it didn't seem right: no-one's expected to read to the bottom of an archive page, a list of <em>other</em> things to read. | |
| 42 … | +At the bottom of every entry is essentially a replica of the front page—I'm <a href="http://powazek.com/2005/09/000540.html" title="...in which Derek Powazek rewards readers that actually read all the way to the bottom of the page">embracing my bottom</a>; been doing it since Canopus, <em>and</em> over at <a href="https://gkn.me.uk/thetwaddle/" title="...in which I embrace The Twaddle's bottom">The Twaddle</a>. Or rather: the front page is just an entry page minus the entry—a generic reception page. This was easy to do now that every page shares a single template. I did consider putting all the bottom-stuff on the <em>archive</em> pages as well, but it didn't seem right: no-one's expected to read to the bottom of an archive page, a list of <em>other</em> things to read. | |
| 43 | 43 … | </p> |
| 44 | 44 … | <h2 id="text">What does the text look like?</h2> |
| 45 | 45 … | <p> |
| 46 | 46 … | One thing that <em>wasn't</em> broken in Canopus was the selection of fonts. Vega had used Georgia for titles and links, and a generic sans-serif font for the main text; Canopus changed that to <a href="http://www.sil.org/~gaultney/gentium/">Gentium</a> for titles and links, and Franklin Gothic Book for the main text. Spica uses Gentium, URW Palladio L or Palatino Linotype (the first one that's available) for titles, and Franklin Gothic Book or <a href="http://dejavu.sourceforge.net/">DejaVu Sans Condensed</a> for everything else. |
| content/tfifirday.md | ||
|---|---|---|
| @@ -23,9 +23,9 @@ | ||
| 23 | 23 … | <p> |
| 24 | 24 … | I also came up with the perfect slogan for Last.fm - “Stay tuned”. It works on multiple levels, as do all the best slogans, providing you define being “tuned” as the state of having tunes... which you should. |
| 25 | 25 … | </p> |
| 26 | 26 … | <p> |
| 27 | -Originally, I was planning to make a weekly post to <a href="http://www.thetwaddle.co.uk/forums">The Twaddle Forums</a>, primarily as a way to liven the place up a bit, but then decided to turn it into a full-blown blog. I briefly considered using <a href="http://blogger.com">Blogger</a> until I realised that Last.fm's music journal is designed for exactly this. | |
| 27 … | +Originally, I was planning to make a weekly post to <a href="https://gkn.me.uk/thetwaddle/forums">The Twaddle Forums</a>, primarily as a way to liven the place up a bit, but then decided to turn it into a full-blown blog. I briefly considered using <a href="http://blogger.com">Blogger</a> until I realised that Last.fm's music journal is designed for exactly this. | |
| 28 | 28 … | </p> |
| 29 | 29 … | <p> |
| 30 | 30 … | So, every Friday evening from now on, I'll be writing stuff on my Last.fm journal. |
| 31 | 31 … | </p> |
| content/weblog035.md | ||
|---|---|---|
| @@ -6,9 +6,9 @@ | ||
| 6 | 6 … | |
| 7 | 7 … | --- |
| 8 | 8 … | |
| 9 | 9 … | <p> |
| 10 | -Last night version 1.0 of <a href="http://www.thetwaddle.co.uk/">The Twaddle</a> went live. It uses arbitrary <abbr title="Extensible Markup Language">XML</abbr> and <abbr title="Extensible Stylesheet Language Transformations">XSLT</abbr> to generate valid <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> pages... offline. | |
| 10 … | +Last night version 1.0 of <a href="https://gkn.me.uk/thetwaddle/">The Twaddle</a> went live. It uses arbitrary <abbr title="Extensible Markup Language">XML</abbr> and <abbr title="Extensible Stylesheet Language Transformations">XSLT</abbr> to generate valid <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> pages... offline. | |
| 11 | 11 … | </p> |
| 12 | 12 … | <p> |
| 13 | 13 … | The idea of uploading bare-bones articles and an XSLT template, allowing the browser to generate pages as they're required, was <a href="/weblog028">a no-go</a>. But I managed to rig up the transformation offline, to be run as a batch. |
| 14 | 14 … | </p> |
| @@ -121,9 +121,9 @@ | ||
| 121 | 121 … | <p> |
| 122 | 122 … | The text output is just to make the command console more interesting while the batch program is running. It also helps pinpoint any errors, such as typos, which show up as blobs of text in the command console. |
| 123 | 123 … | </p> |
| 124 | 124 … | <p> |
| 125 | -The result of all this fiddling is that I can change pages' contents more easily; I've been able to, fairly easily, implement a few minor changes that would have taken effort before. The final product lives <a href="http://www.thetwaddle.co.uk/">here</a>. | |
| 125 … | +The result of all this fiddling is that I can change pages' contents more easily; I've been able to, fairly easily, implement a few minor changes that would have taken effort before. The final product lives <a href="https://gkn.me.uk/thetwaddle/">here</a>. | |
| 126 | 126 … | </p> |
| 127 | 127 … | <p> |
| 128 | 128 … | In semi-related news, it turns out that PURLs such as <a href="http://purl.org/mooquackwooftweetmeow">purl.org/mooquackwooftweetmeow</a>, without the trailing slash, are possible - it's just partial redirects that have to end with slashes. The Twaddle's now on PURLs, too - <a href="http://purl.org/thetwaddle/">purl.org/thetwaddle</a> - with or without the slash. |
| 129 | 129 … | </p> |
| content/weblog049.md | ||
|---|---|---|
| @@ -15,7 +15,7 @@ | ||
| 15 | 15 … | <p> |
| 16 | 16 … | It's not quite <a href="http://www.bootstrap.org/#9B">Purple Numbers</a> but it does the job more than effectively (and it's not half as <span title="Invented word of the day">overkilly</span>). I reckon it's fair to assume that if someone wants to link to a part of your page in another page, they'll have the ability to view your page's source and find the ids. And if they can't, purple numbers would probably befuddle them anyway. |
| 17 | 17 … | </p> |
| 18 | 18 … | <p> |
| 19 | -<a href="http://thetwaddle.co.uk">I do it</a> automatically - it really takes little effort. Another point is to use proper titles, not <code>#title4</code>, so that if you add a chunk, nothing will break (and referring urls look much friendlier). | |
| 19 … | +<a href="https://gkn.me.uk/thetwaddle/">I do it</a> automatically - it really takes little effort. Another point is to use proper titles, not <code>#title4</code>, so that if you add a chunk, nothing will break (and referring urls look much friendlier). | |
| 20 | 20 … | </p> |
| 21 | 21 … | |
Built with git-ssb-web