markdown guide

Not exactly Modular in terms of making project-independent modules, but possibly some thoughts could be helpful in your research:


I don't know about your state management or tech stack but this is the approach we took for a really big react-redux application:

Essentially when evaluating an approach you have to aim at achieving a good level of cohesion and close to no coupling between modules (except your normal commons like your Button abstraction,...).

Logical cohesion is what we strived for in the article I mentioned earlier, at the moment we group everything for example like this:

Our project has objective so we have a folder "project" with a few submodules and one of those is objectives.

This makes it so that we can lazy load modules and their data requirements, this also implies that for example an npm module we only use in module x won't be required initially until we load in module x.


If you're looking for standard (ie zero dependency) Web Components written in vanilla JS, check out.

Classic DEV Post from May 15

What are your five most used terminal commands?

community post to share our most used terminal commands.

Blue Turtle profile image
Web Development Blog

Blue Turtle
Web Development Blog.

Sore eyes? now has dark mode.

Go to the "misc" section of your settings and select night theme ❀️