readthedocs / readthedocs/ext-theme
Listing: use same buttons pattern for builds and versions listing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 12
- Forks
- 6
- Avg merge
- 13h 25m
- Merged PRs (30d)
- 1
Description
I think we have been happy with the pattern we have in the version listing with those buttons at the right:
Today I found that those buttons are different in the build listing page but it seems we should be able to use the same pattern:
Why we don't we move the content from the chip into the list item? The "Book" icon could be a button, similar to the version listing page, and the other two links could be inside the "..." (dots) dropdown. That way we remove the extensive usage of chips that require hovering --which is usually harder than just a simple click.
Contributor guide
No contributing guide indexed for this repository
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 locating the build and version listing templates, then compare how each renders its right-side actions. Move the build actions into the list item using the version listing’s button pattern, with the Book action as a button and the other links in the dots menu; done means the build listing no longer relies on hover-only chips and matches the version listing pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100