How cleancookie/coggo works
Project type and purpose
• This is a small Node.js-based MVC web framework or web application skeleton named “Bones.”
• It provides:
• A custom HTTP server bootstrap (core/BoneServer.js)
• A routing layer (core/BoneRouter.js)
• A controllers directory for business logic (controllers/)
• EJS-based view rendering (views/)
• A configuration entry (server.config.js) and an application entrypoint (index.js)
File structure
• Top level:
• index.js → Application bootstrap
• server.config.js → Server settings (port, middleware toggles)
• package.json → Dependency declarations
• Directory “core/”:
• BoneServer.js → Creates an HTTP server, applies middleware, attaches router
• BoneRouter.js → Parses routes, matches URLs to controller actions
• Directory “controllers/”:
• HomeController.js → Example controller implementing request handlers
• Directory “views/”:
• index.ejs → Template for HomeController’s view
• layouts/main.ejs → Shared layout wrapper
• Configuration files: .eslintrc, .gitignore, .nvmrc
README for additional insights
• Minimal README—project is under construction
Detailed callout suggestions
• Index.js loading server.config.js and then initializing BoneServer.
• Inside BoneServer, illustrate where BoneRouter is registered.
• Within BoneRouter, map URL patterns (e.g., “/”) to HomeController methods.
• Render pipeline: Controller returns a view name and data object → EJS compiles and returns HTML.
• Response is sent back via the HTTP server to the client.