Suggestion: is there anything from commerce, workflow, UI builder or marketing suite that could be useful generic UI components that goes into UUI library.

I suspect the preference from the front-end team is to keep uui lean and mean, and include only components that are required by the backoffice. That's not to say the calendar example couldn't be bundled up as a standalone component with a dependency on uui. That example is all CSS, and very much a PoC for some future workflow features, but I can see how it could be useful outside of workflow, or made to be extensible for adding additional data

Would be cool if there can be an extension package maybe with these components so we can have a consistent way of doing things...

Aim of the UI Library is to contain components that serves a general purpose. With extension of backoffice as its main target. But there is always the downside of maintenance, if a component does not serve an immediate need, its hard to argue for that effort. As components of the UI Library should be in a definite state, tested and documented. A calendar could certainly be of general use, but that is a very complex component. In other words getting it into such state would mean a lot of work. But once we have polished components that serves a general purpose, then we are happy to get them into the UI Library. Available for others to build UI for their projects or extensions.

Yeh thats a good idea Richard - perhaps like common package UI components that commerical products/DXP team could contribute to along with the community so we have a good base of

Lego bricks

to mix and match so we all have a common UI styling and approach