-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Pages Hosting of new BrowserView #64
Comments
@BigBlueHat I do not understand. https://w3c.github.io/scribejs/BrowserView/ simply works, because I had set the repository accordingly: Ie, I do not understand what is the problem... |
Yeah. I guess I was thinking https://w3c.github.io/scribejs/ was nicer. 😄 I can just add a big "Demo" button or something to the readme hosted at https://w3c.github.io/scribejs/ and that would do the trick. Also, could you set https://w3c.github.io/scribejs/ or https://w3c.github.io/scribejs/BrowserView/ as the "homepage" for this repo? |
I am not sure. Having a more prominent note on the page about the existence of the browser view is a good idea, though. |
Cool. Then if you link to https://w3c.github.io/scribejs/ folks will get the README in HTML, and then I'll add a more prominent demo link to the README, and we'll be all set. 😃 Great list of things to add to the BrowserView too, btw! Issues forthcoming. 😉 |
So. Action here would be to set https://w3c.github.io/scribejs/ as the homepage on this repo. |
Added a link to the readme in 82a2f8b, so closing as fixed. 😃 |
The BrowserView directory has a staticly hostable UX for building minutes output from IRC logs, but we can't host out of that directory via GitHub Pages. Consequently, we have three options:
master
)BrowserView
contents only branch (which is a pain to maintain)BrowserView
todocs
--which we can configure to host out ofMy preference would be option 3, as its the simplest to setup.
@iherman let me know your thoughts, and I can send an appropriate PR, and then you can click the things in Settings. 😄
Cheers!
🎩
The text was updated successfully, but these errors were encountered: