nextcloud / nextcloud/cookbook
Complete rework of frontend
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
The userinterface is not really intuitive and very overwhelming.
Describe the solution you'd like
There are some things that could be improved:
-
Move Tags to Sidebar, similar to how the files app deals with shares
-
Use a Three Column Layout, similarly to the contacts-app.
This allows for the following:- Categories do not need to expand, they would filter the "second"-column
- The same applies to tags
- The main-recipe-view will be less "filled", only a simple list will provide access, and the third colum would be empty except a recipe was selected.
- Filtering&search can be handled more easy, removing buttons and selectors that are too tiny for people with accessibility issues
-
Generally increase spacing in the Recipe-View
-
Use a single-row breadcrumb, that shows categories
If you want, i could try to make mock-ups. I dont know if you have an overhaul planned, but i think some of the points could improve the app greatly!
(I think it is especially important to remove the tiny buttons, since they really interfere with accessibility)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by reviewing the current recipe view and the contacts-app and files-app layouts referenced in the request, then establish the frontend scope before changing anything. Done would mean a substantially less overwhelming recipe interface with the proposed three-column navigation, sidebar tags, improved spacing, breadcrumb, and more accessible filtering controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100