> The Nav menu above could be refactored into a Ruby class to allow developers to add items to the menu without needing to understand the underlying HTML.
Either you do SSR and you have to understand HTML or you don't and you can just build a Typescript front-end that calls a ruby server that doesn't generate HTML.
Lets say you do SSR and don't want to understand the HTML, then you can separate the project in two parts and give one part to someone else, but I still don't see how mixing classes and HTML helps.
Functions or templates are enough for SSR, lets be honest this is just about doing OOP everywhere and it creates coupling which IMO is no good.
Either you do SSR and you have to understand HTML or you don't and you can just build a Typescript front-end that calls a ruby server that doesn't generate HTML.
Lets say you do SSR and don't want to understand the HTML, then you can separate the project in two parts and give one part to someone else, but I still don't see how mixing classes and HTML helps.
Functions or templates are enough for SSR, lets be honest this is just about doing OOP everywhere and it creates coupling which IMO is no good.