tripu
tripu
eg: * header * left-hand menu * main content * footer
…for automatic publication with Echidna + Travis CI. It would be an additional “template file” [here](https://labs.w3.org/hatchery/repo-manager/repo/import).
https://github.com/w3c/ash-nazg/blob/fc1944334280834fac5ddacd75ad66ad6a461130/package.json#L6-L12 We're (optionally) using both [`nodemon`](https://www.npmjs.com/package/nodemon) and [`watchify`](https://www.npmjs.com/package/watchify) during local development to monitor JS and CSS sources for changes, and rebuild automatically. Can we simplify dependencies a bit by using...
The “Web Content Accessibility Guidelines WG” changed its name to [“Accessibility Guidelines WG”](https://w3c.github.io/Unitas/?g=35422) some time ago, but its name remained unchanged in the lits of groups in [`/repo/import`](https://labs.w3.org/hatchery/repo-manager/repo/import) (strangely enough,...
I've seen that users who detect issues don't know where to direct feedback. Imitate the “standard” footer that we have been using in other projects (w3c/wbs-design#40). If the footer is...
**Disclaimer:** think of this idea purely as progressive enhancement (read: don't complain about the need to run JS and load things dynamically). If the network is slow and dynamic data...
Advantage: you can see all tags at a glance, and you save clicking on the drop-down (and possibly scrolling on it), which may be tedious. /cc @bert-github.
ie, assign different colours to different statuses (REC, WD, PER…) and do *not* colourise tags (security, WoT, data…). /cc @bert-github.