While fantastic already, sometime an API-only project comes along. Having the option to go:
Node
Express/Meteor
without:
CSS Framework
CSS Preprocessor
Javascript Framework
Template Engine
But that right before the CSS Framework allows me to pick between:
Frontend
REST/JSON API only
Why include this option?
While it's nice to have an all-in-one package, when you're creating an API that will be visible from web, a mobile app and electron, having a decentralized api at api.mydomain.tld makes more sense.
That being said, when the Electron option for Megaboilerplate becomes available this might be a greater requirement. That being said, making the distinction between 'Static Site' and 'Single Page Webapp' might be another great addition but that is outside of the scope of this request.
While fantastic already, sometime an API-only project comes along. Having the option to go:
without:
But that right before the CSS Framework allows me to pick between:
Why include this option?
While it's nice to have an all-in-one package, when you're creating an API that will be visible from web, a mobile app and electron, having a decentralized api at api.mydomain.tld makes more sense.
That being said, when the Electron option for Megaboilerplate becomes available this might be a greater requirement. That being said, making the distinction between 'Static Site' and 'Single Page Webapp' might be another great addition but that is outside of the scope of this request.