On Sunday, March 1, 2015 at 3:18:11 PM UTC-6, Amber Adams wrote: > > > On Sunday, March 1, 2015, andrew mcelroy <[email protected] <javascript:>> > wrote: > >> >> I wouldn't be opposed to this option either. >> I already proposed a different option. We should talk about this at >> the next NLUG meeting. >> >> > No, you haven't. NashJS uses the exact Github solution >
They've got a github org, and their old website looks like it used gh-pages, but looking at nashjs.org, it's definitely running node and sydjs. Slow your roll. My only real issue with Andrew's suggestion is hosted infra managed by a single person is probably not the greatest idea (in terms of webapp availability and human availability). If you wanted to push the code to a free heroku dyno (belonging to an nlug org), I think that'd probably be a happy medium. I'm obviously still in favor of gh-pages, but that's only because I think we'd see more contributions from nlug members (Jekyll being a much lower learning curve, in my biased opinion). GitHub Pages or not, though, there's nothing preventing us from creating an nlug org for member projects. -Igneous -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
