Closed cmeessen closed 1 year ago
I can see how people used to GitHub use Organizations to wrap repositories. I agree with your statement. Should we plan a design session to come up with a layout alternative?
Maybe we can just split the current page in two? That would be relatively quick and easy to implement and should achieve the goal? The same approach should be implemented on the edit project page for consistency (and shared components sake). I'll give it a try this week.
We notice that, when editing their software entries, many users in the Helmholtz RSD create an Organisation for something that would more appropriately be considered as a project.
My guess is that the reason for this is that the user might not be aware that there can be related projects, because it is not immediately apparent on the edit page: the relations are hidden behind the "Related topics" entry. From my perspective, the user might be more aware of these relations if "Related Projects" and "Related Software" would be separate entries in the menu.