Software architecture is usually seen as this big, complex thing that no one really understands; that grows organically; and that needs to be refactored when it is “complete”. But does it really always have to be like this? With all the effort put into architecture – and all the pain this approach usually gives us in the end – is it really worth the effort to even think about it? Wouldn’t we be better off without explicitly focusing on the architecture?
Join this session to learn a system to create a loosely coupled, maintainable, and clean architecture. We need to understand the modular approach to its core combined with both object-oriented and domain-driven design principles. Lastly, we'll see how the concept can be used to design a clean architecture on a larger scale. In doing so, we'll take a look at the pros/cons of implementing microservices architecture, and how the clean architecture approach helps to design good microservices.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.