This started as a playground to try elm-ui, but it is here as a proof of concept for a plugin-based reusable UI (for now based on an infamous iframe) and code sample for a question on StackOverflow
What are the pitfalls of embedding using iframe stackoverflow 
The Idea
The idea is to have external components bundled in self-contained html files, fetch those files at startup time based on yaml config files, and run the components in sandboxed iframes -- Dan Amoroso github
> I guess web components are a more elegant way to solve this "problem", but I wanted to take a shot at solving this "the naive way"
.
From Cam Jackson's Micro Frontends article on martinfowler.com, Run-time integration via iframes page
> Just as with the server-side includes option, building a page out of iframes is not a new technique and perhaps does not seem that exciting. But if we revisit the chief benefits of micro frontends listed earlier, iframes mostly fit the bill, as long as we're careful about how we slice up the application and structure our teams. > > We often see a lot of reluctance to choose iframes. While some of that reluctance does seem to be driven by a gut feel that iframes are a bit “yuck”, there are some good reasons that people avoid them. The easy isolation mentioned above does tend to make them less flexible than other options. It can be difficult to build integrations between different parts of the application, so they make routing, history, and deep-linking more complicated, and they present some extra challenges to making your page fully responsive.
Oh and also why Mondrian?
Mondrian is the guy that made those cool geometric paintings, and every time I think of tiles and components and cards (not very often, I am a backend dev as you can see by the overflow of colors and style in the POC) I think Mondrian. -- Dan Amoroso