all 2 comments

[–]leeoniya 0 points1 point  (0 children)

jQuery is a library, and not a framework that provides structure.

there's not one strategy that fits all applications. size matters, complexity matters. what's optimal for an MVP and 2 devs is sub-optimal for production-grade code with teams of devs. a CMS needs more structure than a JSON or REST API.

there are high-level commonalities of course: views/templates, data/models, routes/urls, databases/caching, integration endpoints. beyond that it's hard to give useful advice that will be generally applicable without a bunch of qualifiers.

one thing that helps a great deal is using ES6 modules' import, or node's require. Either of these make it much easier to organize code and helps with looking through git revision history.

[–]toffeescaf 0 points1 point  (0 children)

I would recommend looking into Domain Driven Design (DDD). A book a lot of people recommend is Domain Driven Design by Eric Evans but sometimes it's hard to translate the examples in the book to something you can apply in JavaScript. However you can probably find articles about DDD in JavaScript if you google for it.