[EW] Browse Mode Should Differentiate Digital Content from Functional Content
Open
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 71
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 29
Description
The browse mode treats all content the same. Folders like `/docs/blocks` appear as equal to folders that actually contain content which is confusing for authors. Taxonomy that serves backend processes should be able to be removed from the UI for some users. This is for KP.
Contributor guide
Research direction
Start by locating the browse mode entry point and how it classifies folders. Review how paths such as /docs/blocks are presented and how visibility could vary by user. Done means digital-content folders are differentiated from functional taxonomy and backend taxonomy can be hidden for the intended users; no specific files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100