Designing the recipe catalogue #112
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#112
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have the wonderful https://dev.apps.coopcloud.tech
We also have the stale https://docs.coopcloud.tech/apps
It would be good to think about this, how to categorise these apps, how do we filter them? How do we cater to the multiple publics and concerns in this one view?
In YunoHost days, I remember seeing a lllottt of discussion of how to improve on https://yunohost.org/en/apps and I don't think they were ever really happy with it.
Good to work on a solid design up-front here, I think.
How do we make the app catalogue grokkable by all?to How do we make the app catalogue useful to all?afaik @hazelnot and ana luisa are working on this 🚀
How do we make the app catalogue useful to all?to Designing the recipe catalogue