nextcloud / nextcloud/external
External links as a dropdown menu
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 132
- Forks
- 43
- Avg merge
- 15m
- Merged PRs (30d)
- 2
Description
First of all, I want to express my gratitude for your product, it is impeccable and I admire and use it.
Today I installed a new app, namely external links.
I have a couple of suggestions that, in my opinion, will make it more usable and will expand the possibility of nesting a lot of external links:
If technically possible, you need to make something like a drop-down menu to select the appropriate link there.
If links are 1, 2 ... 10, the current placement of the lines (Header, Setting Menu) will be more convenient. What happens if there are 100 or more links?
I think it would be more convenient to place links in this way, the menu will display the same logo with the inscription extarnal links and all resources will be collected in one me, or you can even arrange them by groups, if the link grouping function is added.
Taking the opportunity, I wanted to ask, the positions of the user quota and public footer, when specifying them, where the links will be placed. I still don't understand how to find the user quota and public footer to see the links =)
Thank you in advance for the allotted time, and forgive my English, if I put it incorrectly
Yours faithfully,
Jamshid Tursunov
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
Start by reviewing the current external-links UI and how links are placed in the Header and Settings Menu. Define the desired dropdown or grouping behavior, including how user quota and public footer placements should work; done means the proposed navigation supports many links and clearly exposes their locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100