In addition to setting up boilerplate best-practices, central design principle of NodeBootstrap is to compose applications with re-usable, fully encapsulated set of modules.
In a more “spaghetti” Node project you may see HTTP route handlers in the main script or application area, tangled together. What TJ argues for and NodeBootstrap implements is: letting each module declare their own handlers, so if you are installing a “user management” or “blog” module, all you need to do is NPM install that module and indicate from the main app where in the URL path the routes get attached.
Feel free to check-out more details about module design per NodeBootstrap in the source code of the sample module.
For a more advanced example, see: https://github.com/inadarei/nodebootstrap-microservice/tree/master/lib/users