Fix up recent changes in docs and update links to TiddlyTools

[YakovL]

Hi @markkerrigan , I've updated classic.tiddlywiki.com yesterday after committing fixes with this PR. What I'd like to note are 2 things:

• change in Translations.tid: the title of a tiddler in the built TW is defined by the title "slice", not by the name of file (you could even had left it as "translations.tid", but to have it become "Translation" tiddler in TW you need to change the "slice" like I did here, without which we just got a broken link)
• change in split.recipe: unfortunately, to add, rename or remove tiddler, we have to change not only the .tid file, but also the list of tiddlers in split.recipe which is read by the building tools

This is something to be mentioned in documentation contribution guidelines, I guess

[markkerrigan]

Hi Yakov

Thanks for the info, I didn't think about that, but I put that down in my notes for the documentation process.

One thing I wanted to point out and I suppose it is relevant to our previous discussions about what heading level to use is the size differences between h1 and the title of the tiddler are seemingly too similar. Only a difference of .25 em, which doesn't quite look right.

I think this is more of a problem with how the tiddler title and heading are styled being too similar in both size and color, and less about the choice to use h1 over h3. I don't have a problem using h1, but I find it's an interesting problem. Notably if you look in TiddlyWiki Browser Compatibility, you can also see Jeremy also used h3 within a tiddler.

I also realized I put in extra line breaks before the headings. Usually I don't put in those extra line breaks, but due to the fact I'm editing these .tid files in Sublime Text, I don't immediately see the output of how it would look on TiddlyWiki. So I'll change those in my next pull request.

[YakovL]

Hi Mark, exactly same thoughts about headers (noticed when reviewing [[Documentation]], too).

I'm also going to move the cross svg icon used currently in the message area into some accessible part of code so that it can be reused and then we can update SimpleSearchPlugin so that its search results uses it instead of the ugly "close" button. I'll mention that in the google group thread, just haven't found time to read and reply there thoroughly yet. The good thing about the site is we can change styles there more boldly unlike the TWC core which requires caring about backward compability.