Target IDs and CSS styling for TCWs with step numbers

[ebeshero]

When we work through the steps of a release (like TCW 22 especially), it is sometimes difficult to differentiate step numbers from other numbers in the script (it's easy to lose one's place). Let's do some CSS work to make these easier for human eyes 👁️ to follow, and to add targets so the individual steps are linkable.

[martindholmes]

Just flagging up that it's also difficult to edit these files because there's no way of seeing them without CETEIcean, so perhaps we could supply a CSS file linked from the XML that would just let us view them in a browser directly? The structure is simple and the element set we use is very small, so it should be easy.

[hcayless]

Fully agree the display needs some work, and there are things that we could do better. I really want to add better syntax highlighting for code blocks, for example, and click to copy code snippets. To the extent that this will involve website JavaScript, you may need my help—which I'm happy to offer, of course. Adding targets is simply a matter of setting @xml:ids on whatever elements you want to be linkable in the documentation. Unless you want it to happen automatically, which is possible, but would probably mean defining a new list type or @rend maybe so there's a hook to automatically add ids to list items.

@martindholmes If you're willing to use one of the methods to run the site locally that are documented in the readme, then you can have instantaneous previews. I just added a Docker setup (making it 2 ways). It does rely on your having previously configured npm, so possibly it could be a little better, but the config on the Docker side will be a bit more involved, so it will take me some time to sort that out (it will meant selectively mounting stuff in the root directory and probably a custom Dockerfile).

[martindholmes]

I don't use npm or docker, and I think it would make sense to have a simple css option too.

[lb42]

You people cant read raw tei? O tempora o mores....

[martindholmes]

@lb42 When you're trying to edit the instructions while following them (which is the time when you know exactly what needs changing) it's not ideal to be proofing your changes in the XML. You want the XML to get out of the way and let you read nicely-formatted and spaced text.

[ebeshero]

Council F2F Krakow: We should go back to the Documentation repo and check the TEI for our TCWs and make sure the list elements (especially) have the proper attributes for rendering numbering etc.

Also we really want a very simple CSS adjustment for the display on the tei-c website.