Sphinx Theme Adjustments
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- design, documentation
Research direction
Locate the Sphinx theme entry point and compare its mobile and desktop layout with the Docsy arrangement described here. Check how the header, sidebars, search bar, logo, library link, and version selector are currently assembled. Done means the specified ordering and responsive placement are implemented and verified on both mobile and desktop.
Written by the indexing model from the issue text.
Description
The items outlined below are a summary of a recent call with Allan and I.
The Sphinx theme should include the following elements:
- On mobile:
- Show library name & version dropdown selector in header
- All other links will be displayed in left sidebar menu
- Move right sidebar menu and search bar below header to match Docsy
- Show library name & version dropdown selector in header
- On desktop:
- Header should contain the following elements in the following left-to-right order:
- RAPIDS logo w/ chevron & dropdown menu showing main
rapids.ailinks - library name, which is a link to library's documentation homepage
- version dropdown selector
- library specific links
- RAPIDS logo w/ chevron & dropdown menu showing main
- Header should contain the following elements in the following left-to-right order:
- Dominant language
- HTML
- Stars
- 53
- Forks
- 74
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 7
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from rapidsai/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
rapidsai/docs#818 · 1 comment ·
Maintainers usually reply within 5 days
-
? - Needs Triage doc
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rapidsai/docs#673 · 1 comment ·
Maintainers usually reply within 5 days
-
[DOC] Publish named versions to docs.nvidia.com via the deploy workflowMay be free again @josephine-wolf-oberholtzer claimed this 61 days ago, and no pull request is open. Open
rapidsai/docs#819 · 1 assignee ·
Maintainers usually reply within 5 days
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rapidsai/docs#751 · 1 reaction ·
Maintainers usually reply within 5 days
Similar issues
-
右下角的图标问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
esengine/DeepSeek-Reasonix#12044 · 2 comments ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
lingdojo/kana-dojo#31665 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
elementary/dock#620 ·
-
Request: <Freeagent>Opennew icon permissions in review
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simple-icons/simple-icons#15053 ·
Maintainers usually reply within 1 day