📍 META: Redesign springwolf-ui: Feedback, Discussion & Participation

[timonback]

springwolf-ui is getting a new design, share your feedback and participate.

Check the latest demo at https://demo.springwolf.dev (by clicking the feature toggle in the toolbar header)

How to code

1. Clone this repository and go to the springwolf-ui folder
2. Install dependencies: npm ci
3. Start the ui: npm start
4. The ui is ready at http://localhost:4200 - including live refresh
5. Start changing code, i.e. the new sidebar is at springwolf-ui/src/app/components/new/sidenav

[hirth-abi]

I think the new UI is very nice for quick navigation. What's mainly lacking is IMHO the very "clean/tidy" look of the old one. We are using it also to communicate with non-developer stakeholders, where this is not unimportant 😉

For example the current sidebar

in comparison to something like (spacing, auto-width, no line breaks, icon alignment)

[timonback]

Thank you @hirth-abi for the feedback.
I see the improvements in the second screenshot. In case these were code changes, do you mind putting them on an branch and opening a PR? i.e. the styling for the sidenav is located at springwolf-ui/src/app/components/new/sidenav

Regarding your users and stakeholders: you do you mainly think about spacing, etc. (clean/tidy) as in the sidebar or also a different way to present the information?

[hirth-abi]

I've just hacked the changes in https://github.com/hirth-abi/springwolf-core/tree/css-playground but those are probably not clean and the auto-width does not really work, since I have too little CSS experience currently.

What would be also nice - for our way we use it - is a possibility to hide unused/empty sections. In the old UI the operation bindings were not visible by default (tab) which we don't use, and some information is basically clutter:

• message binding is not used
• content-type is always application/json, so redundant at each message
• server is always the same, so redundant at each message

[hirth-abi]

Is it possible to configure the default configuration of the UI? The possibility to hide bindings and headers is nice (and switching the UIs) 👍, but that's lost on reload and is not very well understood by stakeholders who just want to click a link and see the messages without clutter.

[timonback]

Sure @hirth-abi, can you open an enhancement issue for this feature request?

You are also very welcome to contribute this feature. Initial thought regarding implementation is a new endpoint that returns (validated) configuration (application.properties is mapped by Spring into SpringwolfConfigProperties.java). The ui queries the new endpoint - similar like the publishing functionality and shows/hides the parts in the ui.

[timonback]

@hirth-abi I opened an enhanchement issue in #1001 for your request.

---

As the ui is available for some time and the default now, I close this issue.

For any feature requests/issues/contributions/etc, please open a new issue