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.
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.
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.
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\.
Only talking about the page and its content, since I didn't review the
code and how it works: I love it! I think it would be great to have this
in the official repo.
···
On Thu, Jul 14, 2016, at 11:46, Jacob Bandes-Storch via swift-evolution wrote:
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 > <jtbandes@gmail.com> wrote:
I got sidetracked today and mocked up a proposal "status page":
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.
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.
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.
I'm not sure whether it's possible to have both an "organization page" and
a "project page" (used for both swift-evolution and swift-internals).
Someone could certainly try it out.
Jacob
···
On Mon, Jul 18, 2016 at 4:57 PM, Mark Lacey <mark.lacey@apple.com> wrote:
On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch via swift-evolution < > swift-evolution@swift.org> wrote:
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.
It'd be great to see swift.org as just another repo on github.com/apple via
GitHub Pages ;-)
Jacob
···
On Tue, Sep 6, 2016 at 8:45 PM, Jordan Rose <jordan_rose@apple.com> wrote:
> On Sep 6, 2016, at 05:47, Ben Rimmington via swift-evolution < > swift-evolution@swift.org> wrote:
>
>
>
>> On 6 Sep 2016, at 07:11, Jacob Bandes-Storch <jtbandes@gmail.com> > wrote:
>>
>> Is it possible to have a repo named apple.github.io, and still allow
individual repos having their own pages (like apple.github.io/swift-
evolution)?
>
> The `username.github.io` and `username.github.io/projectname`
combination works for me.
>
> The `orgname.github.io` and `orgname.github.io/projectname` combination
should also work (but I haven't tried it).
>
> <https://help.github.com/articles/user-organization-and-project-pages/>
>
> — Ben
Thanks for the suggestion, Ben. After a bit of discussion we’ve put in a
redirect to github.com/apple/, which is definitely better than just
404ing.