> I think it would be useful to have an example of how to make “widgets”, larger components with more complex behaviors that could be reused across many applica

> I think it would be useful to have an example of how to make “widgets”, larger components with more complex behaviors that could be reused across many applications Yeah, that's probably a good idea. Aberdeen doesn't prescribe any 'standard' for how components should be implemented; they're just functions that draw stuff after all. But figuring out some best-practices may not hurt! > I recommend making the HTML boxes scrollable, and allowing the code to scroll x. Reading wrapped code on a small screen is difficult. You'd think that in 2025, I'd remember to test my pages on a mobile phone, right? Doh! :-)