modular-monolith-with-ddd VS html5-boilerplate

Link to PR here: https://github.com/kgrzybek/modular-monolith-with-ddd/pull/286

- https://github.com/kgrzybek/modular-monolith-with-ddd (a really well documented example)

You can see there is a module called building_blocks. Inside it, I keep all the utilities needed in the project, like a logger, serializers, and so on. I did not make up this name, I borrowed it from this repo.

9. Modular Monolith with TDD

This covers far more than just DDD, however, I find the links and README super helpful for a wide range of subjects: https://github.com/kgrzybek/modular-monolith-with-ddd

Modular monolith. Here is one of the best production-ready examples https://github.com/kgrzybek/modular-monolith-with-ddd

Am wondering what react community thinks of DDD.

I've been reading "blue" DDD book (by Eric Evans) and "red" book (by Vaugh Vernon) and that was a completely "my whole life was a lie" type of experience and relief at the same time. It's just so great to have the principles of who to structure the code. It, by definition makes, your codebase structure meaningful. Because it's structured according to some common knowledge, not your random thoughts at the time you were writing code.

I was surprised to find so little DDD react sample codebases. Let's say for backend there is huge amount of samples, i.e. https://github.com/kgrzybek/modular-monolith-with-ddd . For react/frontend I have bookmarked only https://github.com/talyssonoc/react-redux-ddd/tree/master/sr... and few more, but those others does not meet the optional criteria i like really much - at the highest (or at app) level all codebase need to have folders app, domain, infra and ui. Simple rule, but simplifies life a lot.

So my question is - is DDD for some reasons not very applicable for app frontend development. Or it just never became popular. Or maybe DDD is popular amongst react developers, just I am not aware of this.

Many thanks for any ideas and comments!

Download the HTML5 Boilerplate template from the official website (https://html5boilerplate.com/). You can choose to download the standard or the enhanced version, depending on your needs.

The ol' HTML5 boilerplate project does favicons in three lines:

Also https://html5boilerplate.com might be good starting point.

Learn to a medium degree of proficiency HTML and CSS. Dig through something like the source code for https://html5boilerplate.com/ and try to understand why they're doing the things that they're doing. Learn Git and use it in practice. Even if you're just working on your own code.

Do you guys still use HTML5 Boilerplate when starting new projects? https://html5boilerplate.com/

2. Html Boilerplate

Wasn't this moved into Modernizr? There's a library I haven't thought of in a long time.

Oh, yep. There it is at the bottom:

> April 2011: IEPP v2 comes out. Modernizr and the html5shiv inherit the latest code. Meanwhile developers everywhere continue to use HTML5 elements in a cross-browser fashion without worry.

Paul Irish also started (or helped start) the html5 boilerplate project[1], which I am surprised to see is still actively being developed. I relied on that boilerplate for so many of my years of my early career (started full-time front-end in 2011). If you want another blast of nostalgia, check out the earlier releases[2,3] of it. I'm so happy I don't have to use conditional IE statements in my html anymore

1. https://html5boilerplate.com/

2. https://github.com/h5bp/html5-boilerplate/tree/v0.9

3. https://github.com/h5bp/html5-boilerplate/tree/v0.9.5

To get started with templates. https://html5boilerplate.com/