- From: Mark Sadecki <mark@w3.org>
- Date: Mon, 14 Jul 2014 16:35:55 -0400
- To: Marcos Caceres <w3c@marcosc.com>, Shane McCarron <shane@aptest.com>
- CC: Steve Faulkner <faulkner.steve@gmail.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>, Frederick Hirsch <w3c@fjhirsch.com>
On 7/14/14, 4:25 PM, Marcos Caceres wrote: > > > On July 14, 2014 at 4:18:55 PM, Mark Sadecki (mark@w3.org) wrote: >>> There are many use cases for wanting stable, static snapshots >> of our >> specifications. One came up today, which is why Shane posed the >> question to the >> group in the first place (a user who needed to review one of our >> respec >> documents was wondering why so much of the boilerplate was missing >> and why there >> was no TOC to navigate the document with.) There are some pretty >> smart people on >> this list. I think we are just trying to see if anyone has put any >> thought into >> building an automated workflow that took master and published >> a static snapshot >> of it to gh-pages upon each commit. It's really not such a bad idea >> and it >> would have multiple benefits. > > I think a few people have tried with Phantom JS, but it hasn't worked out well. Thanks Marcos. This info is helpful. I'm wondering if this can be done with a bash script in .git/hooks/post-commit? It would most likely have to be customized for each editors particular environment, but it might be a start. I'm not sure how to automate the publishing of a snapshot from respec. Anyone? Is Phantom JS the only method? Mark > > > > -- Mark Sadecki Web Accessibility Engineer World Wide Web Consortium, Web Accessibility Initiative Telephone: +1.617.715.4017 Email: mark@w3.org Web: http://w3.org/People/mark
Received on Monday, 14 July 2014 20:35:57 UTC