tripu

Okay, I don't mind having @plehegar's simpler solution only (although, for the record, I like the quick live navigation between all versions of the spec that the JS pop-up would...

Note to self: timeline on the right-hand side of [an IE3 standard](http://ieeexplore.ieee.org/document/4610935/versions).

I read that there are advantages to each approach (autofocus on main input of main form on the page, or not), but can't find a definitive answer. I understand that...

Also: * Test automatically new CR workflow with GH issues (Extend the test suite; cf https://github.com/w3c/echidn/pull/575 )

I think that's the idea, @plehegar: not having to publish using `gh-pages`, using different branches, tags or commits… much like when we define [Git npm dependencies](https://docs.npmjs.com/files/package.json#git-urls-as-dependencies).

The package [I started looking at, `nodegit`](https://github.com/w3c/echidna/compare/tripu/support-git-scheme), does not support Node.js `10` (nodegit/nodegit#1490), so [some builds error](https://travis-ci.org/w3c/echidna/builds/427118070), and it may be a blocker going forward. Possible alternatives may be [`git`](https://www.npmjs.com/package/git)...

This old idea may become more important, now that [RawGit is shutting down](https://rawgit.com/)…

Three strategies about this (not necessarily exclusive): * https://labs.w3.org/echidna/ui * https://github.com/features/actions * https://travis-ci.com/

In the long term, I prefer to have documentation [on the Specberus/Echidna web pages themselves](https://github.com/w3c/specberus/tree/master/views) (and discard the GH wiki). It will allow us to structure things better, embed other...

Once w3c/specberus#261 is merged, we'll be extracting the shortname as metadata sooner in the process, but still that's Specberus. So +1 to try to infer it earlier in Echidna.