It occurs to me that moving swift-evolution to use *only* a gh-pages branch, like swift-internals does, would allow this to work without JS.
On Thu, Jul 14, 2016 at 1:30 AM, Jacob Bandes-Storch <[email protected]> wrote: > I got sidetracked today and mocked up a proposal "status page": > > http://jtbandes.github.io/swift-evolution/ > > This moves the proposal status info (currently in README.md) into a > separate "source of truth": > > https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml > > The status page is then generated from the source of truth using XSLT. > Unfortunately, in order to get this working on GitHub Pages, I had to load > the files using JavaScript (otherwise the browser blocks the cross-origin > requests): > https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html. > > > If we wanted to adopt this for the official swift-evolution repo, the > steps would be: > > 1. push the XML and XSL files to master > > 2. push a gh-pages branch with the status page > > 3. update README.md on master to point to the status page, rather than > duplicating all the information. > > > Thoughts? Tweaks? Insults? > > Jacob >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
