- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Sat, 18 Apr 2015 09:29:41 -0400
- To: public-webapps <public-webapps@w3.org>
Below is an announcement about a project "to provide a modern design to future technical reports published by the W3C" i.e. updating the stylessheet used for Technical Report <https://github.com/w3c/tr-design/blob/gh-pages/README.md >. If you have any feedback, please use <https://github.com/w3c/tr-design/issues> (and do not reply to this thread). -------- Forwarded Message -------- Subject: Updating our /TR stylesheets Date: Thu, 16 Apr 2015 08:53:21 -0400 From: Philippe Le Hegaret <plh@w3.org> To: spec-prod <spec-prod@w3.org> I'd like to find a path for W3C to update our /TR style sheets and since we weren't able to do it so far, here is a radical change on how to do so. First, since it's too complex to change documents that have been published in the past, we must not try to do it. It has the simplification that we're breaking the consistency of style between all W3C documents but it allows us more forward. Second, we shouldn't assume we need one new style and be done. Instead, I'd like to enable ourselves to have progressive enhancements over the years. It will also avoid having everyone trying to squeeze their own ideas between of a once-in-a-lifetime chance to change the styles. To make it easier on the tooling, we also need something predictable. So, I'd like to propose that we allow ourselves to update the /TR style sheets once per year, on January 1. All documents published in that year would have to use the style, ensuring some consistency. Note that it doesn't imply we have to change the style every year, but it gives us an opportunity if we want to. I added a set of guidelines and an hopefully simple process to do it: https://github.com/w3c/tr-design/blob/gh-pages/README.md Feedback is welcome. Philippe
Received on Saturday, 18 April 2015 13:30:10 UTC