-
Notifications
You must be signed in to change notification settings - Fork 2
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 for the examples #1
Comments
We currently have the examples in their own separate folders, but to view each example it would require a person to click each folder to then be able to click the JSfiddle link. So should we create a TOC at repo root level which will list all the examples and what they do and have their demo link as well. This way we have a single place where people can see what all there is and quickly see the demos. I suppose a weekly cron to update the TOC should suffice or depending on how low volume it is right now, manually just editing it would work as well. Thoughts? |
Well, that would be possible I assume but I don't quite see the purpose. While jsfiddle (and the like) is nice and all, it is an external resource, so we add another layer of external dependency to it. If jsfiddle happens to be down, the examples can't be viewed right away. Now, if you have everyone just push their examples to the This is a live example. https://github.com/BonsaiDen/JavaScript-Garden |
Ooooohh you're talking about http://pages.github.com/ yeah we can definitely do that. |
Even if JSfiddle is an external resource it's a nice feature to have so one can see a quick demo of what the code actually does. I second the (bi)weekly cronjob. |
@godka of course but external resources should be optional. We can have both things together. |
@godka the Github Pages would allow us to do the same thing as far as I know. So we don't have to use a 3rd party service to show demo. |
I think it would make sense to have a GH page for all the examples.
Maybe having people push their examples right to the
gh-pages
branch would be a good idea.The text was updated successfully, but these errors were encountered: