14
246
Fork
You've already forked pyfedi
75

[Enhancement] Improve "all communities" page #703

Closed
opened 2025年06月05日 11:48:41 +02:00 by QuiteSimple · 2 comments

Just some minor nitpicks on the "all communities" page

image

  1. Having a dropdown button to reveal filters & search doesn't make too much sense, 99% of people opening the page are probably looking for a specific community. On Lemmy, these are visible by default. I think this page would look nicer if we just ditch the dropdown altogether and show these options by default.
  2. The "create local community/add remote community" buttons should be in the same container as everything else so it doesn't take so much vertical space
Just some minor nitpicks on the "all communities" page ![image](/attachments/061d9d7f-0d11-4ac3-b164-dfbca7c7aee0) 1. Having a dropdown button to reveal filters & search doesn't make too much sense, 99% of people opening the page are probably looking for a specific community. On Lemmy, these are visible by default. I think this page would look nicer if we just ditch the dropdown altogether and show these options by default. 2. The "create local community/add remote community" buttons should be in the same container as everything else so it doesn't take so much vertical space
Collaborator
Copy link

Alright, I have updated the template, inspired by this issue and have attached the updated /communities page (on a test instance). Does this look like what you have in mind? If so, I can make the PR, as I agree that the expandable filters box is unnecessary.

  • I decided to break apart the Create Local and Add Remote buttons into separate buttons. The two of them being in a button set doesn't make much logical sense to me. So, hopefully this makes it visually clearer that these are separate actions.
  • I also did some tweaking of the css classes for the dropdowns and search bar that make them a bit more responsive (especially if an instance doesn't have feeds or topics).
  • I was torn on whether to add a title heading to the page above the buttons/filters, but decided to keep the page without a title heading to prevent taking up more vertical space.

I would also appreciate any input that @rimu might have on the updated visual. One technical benefit that this updated template has is that it no longer requires running the coolfieldset js script.

Alright, I have updated the template, inspired by this issue and have attached the updated `/communities` page (on a test instance). Does this look like what you have in mind? If so, I can make the PR, as I agree that the expandable filters box is unnecessary. - I decided to break apart the Create Local and Add Remote buttons into separate buttons. The two of them being in a button set doesn't make much logical sense to me. So, hopefully this makes it visually clearer that these are separate actions. - I also did some tweaking of the css classes for the dropdowns and search bar that make them a bit more responsive (especially if an instance doesn't have feeds or topics). - I was torn on whether to add a title heading to the page above the buttons/filters, but decided to keep the page without a title heading to prevent taking up more vertical space. I would also appreciate any input that @rimu might have on the updated visual. One technical benefit that this updated template has is that it no longer requires running the `coolfieldset` js script.

Looks good to me, nice work.

Looks good to me, nice work.
Sign in to join this conversation.
No Branch/Tag specified
main
v1.7.x
v1.6.x
v1.5.x
v1.4.x
v1.2.x
v1.3.x
async-microservice
gevent
schema
v1.1.x
swagger-api
v1.0.x
v0.99
infinite-scroll
refactor-post-new
v1.7.5
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.6.27
v1.6.26
v1.6.25
v1.6.24
v1.6.23
v1.6.22
v1.6.21
v1.6.20
v1.6.19
v1.6.18
v1.6.17
v1.6.16
v1.6.15b
v1.6.15
1.6.14
v1.6.13
v1.6.12
v1.6.11
v1.6.10
v1.6.9
v1.6.8
v1.6.7
v1.6.6
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.0
v1.5.4
v1.5.3
1.5.2
v1.5.1
v1.5.0
v1.4.6
v1.2.7
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.3.10
v1.4.1
v1.4.0
v1.3.9
v1.3.8
v1.3.7
v1.3.6
v.1.3.5
v.1.3.4
v1.3.3
v1.3.2
v1.3.1
v1.3.0
v1.2.6
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.0
v1.0.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rimu/pyfedi#703
Reference in a new issue
rimu/pyfedi
No description provided.
Delete branch "%!s()"

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?