Templates for onRender about livingmarkup

[aswinvk28]

hxtree won't require a template onRender because there is no replication of content throughout. This requires administration and the complexity improves as you include more flexibility in the production of templates. If content types are added, they must conform with administration of content.

Please check here:
https://refactoring.guru/design-patterns/chain-of-responsibility

Why don't you try code generation based on UI / Graphical Interface?

[hxtree]

Hi Awsin,

The question I don't know the answer to is whether an onRender call could consist of enough markup to justify it being broken up into another a View (*.phtml) type file for separation of concerns? For example, what would a bloated Module/Navbar onRender() look like? I'd rather keep it simple, of course, but it certainly something to consider.

I'm both familiar with the Refactoring Guru and the Chain of Responsibility design pattern. However, reading through it again, got me to think about applying a chain of responsibility to DOM elements, which could be pretty neat for forms.

e.g. button onSubmit could be picked up by a module with xpath \form using the design pattern. This inline with the way the DOM ancestor variable access currently works.

<form>
<button/>
<form>

I certainly see the benefits of a WYSIWYG implementation. But, first I think it's important to flesh out the core modules.

[hxtree]

Also, I see the page templates you're referring to being essentially just a boilerplate page that gets copied over during page creation that consist of LHTML5.

[hxtree]

Page templates should feature semantic elements:
https://www.w3schools.com/html/html5_semantic_elements.asp