UI infrastructure

I've been designing some ad-hoc UI infrastructure: debusine.web.views.ui_shortcuts, debusine.web.views.files, template tags to render a sidebar in various views.

For UI shortcuts I made widgets rendered from Python (like django forms would do); for the sidebar since I started designing it from templates I ended up implementing some rather complicated support template tags.

If the ideas of UI shortcuts and sidebar information make sense, I would be tempted to streamline things a bit:

• build the sidebar like we're building UI shortcuts, getting rid of the complicated template tag
• create a base view that combines UIShortcutView with functions to generate the sidebar, designed to be the view counterpart of debusine/web/templates/web/_base_rightbar.html
• possibly add functions to support showing the current workspace in the top navigation bar

The idea is to have matching templates and views to support the UI visual language we're using in debusine.

This makes lots of sense to me, and it naturally makes it so that new views naturally tend to speak the same visual language as the other ones.

However, the current visual language was improvised by me, and was not a team choice.

Question: is it good enough, and shall we call it official for this generation of Debusine? Is there something you'd change?

You can use https://playground-986.debusine.dev/work-request/1/ as a reference, which has the redesigned work request view with information in the sidebar and artifacts in the center, like the artifact detail view has information in the sidebar and files in the center