Back

@zachleat The “h-i” slide cracks me up.

@khalidabuhakmeh we do what we must

@zachleat Great post. I’d like to see the aspirational idea you have come to fruition.

The biggest issue with web component approaches, even the good ones like WebC, is that they still require a build step. This limits them to folks who are comfortable with JS build chains.

I want to spread the love to Django, ASP.NET, Laravel, Rails, and all future web frameworks.

@khalidabuhakmeh @zachleat the aspirational ideal is literally how Enhance works. You define your template in a function and then it is expanded into light DOM custom elements by the SSR piece.

We’d love to bring Enhance SSR to other languages so if you are interested in submitting PR’s we’d be happy to work on that with you.

@macdonst @khalidabuhakmeh @zachleat kinda weirdly absent again. :/

@brianleroux @macdonst @zachleat

@khalidabuhakmeh @brianleroux @zachleat he missed the Enhance mentions on his read-through. I already mentioned it to him.

@macdonst @khalidabuhakmeh @zachleat yea sorry, missed the single bullet footnote mention there

@brianleroux @macdonst @khalidabuhakmeh everything okay?

I do try to mention Enhance whenever I talk about WebC e.g. https://github.com/11ty/webc#similar-works

I don’t see any mentions of WebC on enhance.dev though (which is fine!)—but I’m sensing a little passive aggressiveness here which in the larger picture seems a little unfair (same team!)

@zachleat @macdonst @khalidabuhakmeh not super great tbh. thx! sorry for making you feel that way. (we do mention 11ty a lot on our blog and even had support for it in Enhance pre-webc)

@zachleat @macdonst @khalidabuhakmeh we figured it was less confusing but if you don't think so I'm into it. we should have some ssg option to point folks at.