Skip to content
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

Open
mainerror opened this issue May 2, 2013 · 6 comments
Open

GitHub Pages for the examples #1

mainerror opened this issue May 2, 2013 · 6 comments

Comments

@mainerror
Copy link
Member

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.

@ghost
Copy link

ghost commented May 5, 2013

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?

@mainerror
Copy link
Member Author

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 gh-pages repository, we'd have all examples as source code, organized however we want, in separate directories and one could view them right away.

This is a live example. https://github.com/BonsaiDen/JavaScript-Garden

@ghost
Copy link

ghost commented May 5, 2013

Ooooohh you're talking about http://pages.github.com/ yeah we can definitely do that.

@CS1000
Copy link
Member

CS1000 commented May 5, 2013

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.

@mainerror
Copy link
Member Author

@godka of course but external resources should be optional. We can have both things together.

@ghost
Copy link

ghost commented May 6, 2013

@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.

@ghost ghost self-assigned this May 6, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants