Laravel and Atomic Design Methodology

[misog]

Hi. Laravel originally used view - section - include - template way of composing the view/presentation layer. View files are files where interesting content is defined.

Mentally, it was "middle-up-down" approach, because developers let the view extend a layout (middle-up) and then developers included children into the view (middle-down). And also, it was unpractical to create deep element/component hierarchy from the view file (where interesting content is defined). It should not be unpractical to create deep element/component hierarchy - HTML and DOM is so popular because elements can be nested nicely.

Layouts may also be created via "template inheritance". This was the primary way of building applications prior to the introduction of components.
https://laravel.com/docs/9.x/blade#layouts-using-template-inheritance

Deep nesting (like in HTML) gives a context - a high level overview of what is deeper in view - and what is view.

As it turns out, deep nesting was invented way before HTML :)

Atoms, Molecules, Organisms (+ Templates and Pages/Screens) https://atomicdesign.bradfrost.com/chapter-2/

React perspective on Atomic Design Methodology https://paulonteri.com/thoughts/atomic-design-react

I think Atomic Design Methodology could be mentioned or explained directly in Laravel docs.