Mega Boilerplate

@kevinyun Thanks! Please let me know if you have any suggestions for the README. It is still very much work in progress.

@dja1o https://github.com/RailsApps/rai...

@noahtovares This project consists of hundreds of micro modules (files) that are composed on the fly. I start with a base file, e.g. server.js, which contains a bunch of comment strings that are removed or replaced based on user's choices. The idea is really simple, it's just very time consuming, hence it took so long to build this project.

@gopietz Thanks for your kind words. I have enjoyed working on this project and will continue to do so, as it allows me to play around with different tools and technologies. For example, I don't know anything about Angular 2, TypeScript, Meteor, Electron yet (currently on the roadmap), so in a way Mega Boilerplate is an opportunity to learn these new tools! :) The name, despite sounding very boring and generic, is actually well thought-out. Besides the availability of megaboilerplate.com domain, there weren't any relevant Google search results for this name, but now the entire first page is all about this particular project: https://www.google.com/#q=mega+b...

@evnowandforever good thinking. im especially waiting for the electron boilerplate and how you might allow me to tweak it. photonkit.com might come in very handy for that one :)

@gopietz I am excited for Electron boilerplate as well. It will be based on the existing boilerplate (https://github.com/chentsulin/el...) but slightly simplified, with custom UI, and several checkbox options, and perhaps a simple email-based authentication. I was blown away when I saw that I could build desktop apps with Hot Reload - a single change to CSS or React components and you can immediately see the results! In fact, my next two side-project apps will be built using Electron. 👍

@evnowandforever i just noticed that the static site boilerplate doesnt come with an option to add a css framework like you offer for node.js. you might want to add that.

@gopietz I was planning to add CSS framework and a few other choices from Node.js, but decided to keep it real simple to gauge the interest for those static site generators, to see if it was a good time investment. As of 6/9/2016, the ratio between node.js and static site generator downloads is Node.js 7,279 (44.21%) vs Static Site 4,973 (30.21%). Between Jekyll and Middleman it it's Jekyll 2,386 vs Middleman 1,945.

@_samuelbeard Hmm, that's a good point. That will also solve the React template engine issue that I have talked about with @peteallport above. Instead of swapping, I might just add Template Engine choices right after JS Framework. So it would be: Platform > Framework > CSS Framework > CSS Preprocessor > JS Framework > Template Engine > Unit Testing > Database > Auth > Deployment.

@ironxcross That was my main concern with Hackathon Starter, but with Mega Boilerplate project not so much. If someone proposes a new "feature X" to the React generator, it could simply be optional, similar to how you check Socket.IO and PM2 checkboxes under Express radio button. Generator code will certainly increase in code and complexity over time, but the output should not, and I will actively try to streamline it to make generated code simple and clean.