-
Notifications
You must be signed in to change notification settings - Fork 59
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
Use gh-pages for demos
for metal-* components
#133
Comments
The plan so far was to have Metal.js's site include the demos, but we haven't managed to start working on that yet. Your idea is very good though, and could be done even before the website is ready to include demos. We don't have travis set up for each repo yet either, but we could have a gulp task until that's ready, like we do for metaljs.com. What do you think @eduardolundgren and @zenorocha? |
From @zenorocha on July 19, 2016 20:51 Yeah, we just need to make sure that these demos are going to be up to date. |
@blzaugg, @zenorocha, can you guys go over this as part of the |
@Robert-Frampton, can/should we automated this into Electric? Or is this too specific to Metaljs.com? |
Sounds too specific to metaljs.com's use case. |
From @cirocosta on July 19, 2016 18:20
Hey!
I've noticed that most of the
metal-*
repositories have ademo(s)
directory, but they are just "runnable" ifgit cloning
and then running the build steps. It'd be pretty cool to have them just one click away by usinggh-pages
to provide that. What do you think about setting a script for publishing them? There are various examples about travis integration that pushes togh-pages
when a push to master is done.Thx! 👯
Copied from original issue: mairatma/metal-lerna#15
The text was updated successfully, but these errors were encountered: