Users view via users.yml blueprint

We could offer creating a users.yml next to site.yml that controls the user view.

Default falls back to a tab per role (+ all) with a users section per tab.

In that sense, a users section would be a pre-requirement (https://feedback.getkirby.com/28).

Would also solve then: https://feedback.getkirby.com/681

I was just about to open the same suggestion. In my current case the strongest need simply is displaying the name of the organization the editor belongs to in the users list section after the username.

But I could also think of:
– customize the userlist section
– display different information
– display all roles in one tab, but different lists like with drafts and published pages
– add info fields with additional information
– add custom fields and sections in general