github-starred/awesome-neovim
2
0
Fork 0
mirror of https://github.com/rockerBOO/awesome-neovim.git synced 2026-11-09 10:40:24 -06:00
Code Issues 217 Packages Projects Releases Wiki Activity

[Collaborators] Could the "UI" section be restructured? #188

New Issue
Open
opened 2025-11-06 06:37:00 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-06 06:37:00 -06:00
Owner
Copy Link
Copy Source

Originally created by @DrKJeff16 on GitHub (Nov 3, 2025).

Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.

Description

My idea is to move from this:

- [Colorscheme](#colorscheme)
  - [Tree-sitter Supported Colorscheme](#tree-sitter-supported-colorscheme)
  - [Lua Colorscheme](#lua-colorscheme)
  - [Colorscheme Creation](#colorscheme-creation)
  - [Colorscheme Switchers](#colorscheme-switchers)
- [Bars and Lines](#bars-and-lines)
  - [Statusline](#statusline)
  - [Tabline](#tabline)
  - [Cursorline](#cursorline)
...
- [Animation](#animation)
...
- [Split and Window](#split-and-window)
  - [Tmux](#tmux)
...
- [UI](#ui)

to this structure:

- [UI](#ui)
  - [Colorscheme](#colorscheme)
    - [Tree-sitter Supported Colorscheme](#tree-sitter-supported-colorscheme)
    - [Lua Colorscheme](#lua-colorscheme)
    - [Colorscheme Creation](#colorscheme-creation)
    - [Colorscheme Switchers](#colorscheme-switchers)
  - [Bars and Lines](#bars-and-lines)
    - [Statusline](#statusline)
    - [Tabline](#tabline)
    - [Cursorline](#cursorline)
  - [Animation](#animation)
  - [Split and Window](#split-and-window)
    - [Tmux](#tmux)

Also, some UI-related plugins not in any of these sections could be moved to the "UI" section (or
related) alone. If you wish I could compile a list with examples to discuss further.

Thoughts on this?

Originally created by @DrKJeff16 on GitHub (Nov 3, 2025). Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub. ## Description My idea is to move from this: ```markdown - [Colorscheme](#colorscheme) - [Tree-sitter Supported Colorscheme](#tree-sitter-supported-colorscheme) - [Lua Colorscheme](#lua-colorscheme) - [Colorscheme Creation](#colorscheme-creation) - [Colorscheme Switchers](#colorscheme-switchers) - [Bars and Lines](#bars-and-lines) - [Statusline](#statusline) - [Tabline](#tabline) - [Cursorline](#cursorline) ... - [Animation](#animation) ... - [Split and Window](#split-and-window) - [Tmux](#tmux) ... - [UI](#ui) ``` to this structure: ```markdown - [UI](#ui) - [Colorscheme](#colorscheme) - [Tree-sitter Supported Colorscheme](#tree-sitter-supported-colorscheme) - [Lua Colorscheme](#lua-colorscheme) - [Colorscheme Creation](#colorscheme-creation) - [Colorscheme Switchers](#colorscheme-switchers) - [Bars and Lines](#bars-and-lines) - [Statusline](#statusline) - [Tabline](#tabline) - [Cursorline](#cursorline) - [Animation](#animation) - [Split and Window](#split-and-window) - [Tmux](#tmux) ``` Also, some UI-related plugins not in any of these sections could be moved to the "UI" section (or related) alone. If you wish I could compile a list with examples to discuss further. Thoughts on this?
GiteaMirror added the questiondiscussionenhancementmaintenance labels 2025-11-06 06:37:00 -06:00
GiteaMirror commented 2025-11-06 06:37:01 -06:00
Author
Owner
Copy Link
Copy Source

@Penaz91 commented on GitHub (Nov 3, 2025):

I fear adding nesting levels may make the repository harder to read, but I would definitely at the very least move the UI-related plugins closer together, since now they're all scattered around the repository.

If we wanted to add more nesting, it has to be clear both in the Table of Contents and while reading the list.

Also this change would touch upon #1755 's territory too, so I'm wondering if it would be better to either tackle them together or at least specify an order that reduces the total amount of work to do.

Also, some UI-related plugins not in any of these sections could be moved to the "UI" section (or
related) alone.

I disagree, if we make "UI" a super-section (containing other subsections), placing plugins there would increase confusion (since the sections would appear nested in the TOC but almost "detached from each other" in the content).

I would rather have a "Misc" section at the end where all the miscellaneous plugins can fit. As long as it doesn't become another "Utility section", it should be fine.

@Penaz91 commented on GitHub (Nov 3, 2025): I fear adding nesting levels may make the repository harder to read, but I would definitely at the very least move the UI-related plugins closer together, since now they're all scattered around the repository. If we wanted to add more nesting, it has to be clear both in the Table of Contents and while reading the list. Also this change would touch upon #1755 's territory too, so I'm wondering if it would be better to either tackle them together or at least specify an order that reduces the total amount of work to do. > Also, some UI-related plugins not in any of these sections could be moved to the "UI" section (or related) alone. I disagree, if we make "UI" a super-section (containing other subsections), placing plugins there would increase confusion (since the sections would appear nested in the TOC but almost "detached from each other" in the content). I would rather have a "Misc" section at the end where all the miscellaneous plugins can fit. As long as it doesn't become another "Utility section", it should be fine.
GiteaMirror commented 2025-11-06 06:37:01 -06:00
Author
Owner
Copy Link
Copy Source

@DrKJeff16 commented on GitHub (Nov 3, 2025):

I think #1755 is more important. Also, you're right about nesting. Was thinking about it when I wrote the Issue but forgot to mention it.

I disagree, if we make "UI" a super-section (containing other subsections), placing plugins there would increase confusion (since the sections would appear nested in the TOC but almost "detached from each other" in the content).

I would rather have a "Misc" section at the end where all the miscellaneous plugins can fit. As long as it doesn't become another "Utility section", it should be fine.

I see your point.

@DrKJeff16 commented on GitHub (Nov 3, 2025): I think #1755 is more important. Also, you're right about nesting. Was thinking about it when I wrote the Issue but forgot to mention it. --- > I disagree, if we make "UI" a super-section (containing other subsections), placing plugins there would increase confusion (since the sections would appear nested in the TOC but almost "detached from each other" in the content). > > I would rather have a "Misc" section at the end where all the miscellaneous plugins can fit. As long as it doesn't become another "Utility section", it should be fine. I see your point.
GiteaMirror commented 2025-11-06 06:37:02 -06:00
Author
Owner
Copy Link
Copy Source

@rockerBOO commented on GitHub (Nov 3, 2025):

Only thing for the nesting is different projects pull from this repo so adding more nesting in the actual README means they would have to alter their parsing stuff. So would rather not add that complexity if not needed but we can reorganize them to be together more generally without the nesting.

@rockerBOO commented on GitHub (Nov 3, 2025): Only thing for the nesting is different projects pull from this repo so adding more nesting in the actual README means they would have to alter their parsing stuff. So would rather not add that complexity if not needed but we can reorganize them to be together more generally without the nesting.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
automated issue
automated-report
bug
discussion
enhancement
help wanted
maintenance
pull-request
Mirrored from GitHub Pull Request
 question
report
urgent
No labels discussion enhancement maintenance question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-neovim#188