New blog post: Building a #router with #HTMLFragments.

https://blog.dwac.dev/posts/html-fragments-routing/

This explorers how we can use HTML fragments to define routes, load them dynamically, and then apply them to the main page content. It talks about more complexities with streaming #HTML (because I didn't learn my lesson last time) and even has a bonus section on shipping an application server _inside_ a #ServiceWorker.

Lots of interesting stuff, I hope you check it out!

HTML Fragments Routing - Devel without a Cause

Let's build a router by fetching each route as an HTML fragment!

@develwithoutacause Very interesting post! To be honest, I still love my good old `<frameset>`. I’ve tried to modernize such an architecture based on `<iframe>`: https://web.dev/mini-app-example-project/. You get a lot of things for free like that.
Applying the mini app programming principles to an example project

This chapter shows an example project that follows the "programming the mini app way" approach.

web.dev

@tomayac 😁 I hadn't heard of "mini apps", I'll have to read more in that series, but the use of iframes sounds very similar. It reminds me a bit of the `embed` element I proposed here: https://blog.dwac.dev/posts/html-fragments/#ecosystem

I imagine sandboxing would make those iframes tricky to work with in a lot of respects. With #HTMLFragments, at least everything is in the same frame and has the same JS execution context.

A Simpler HTML-over-the-Wire - Devel without a Cause

Is it possible to build an HTML-over-the-wire application with only native web technologies? See how far can we go with zero custom tooling, and how the web specification can change to support it.