Search Bar Position
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- documentation, frontend
Research direction
Start at the documentation website linked in the issue and trace the template or entry point that renders the page title and search bar. Move the search bar below the title, then verify on the generated documentation pages that the order and appearance match the requested layout.
Written by the indexing model from the issue text.
Description
Describe the feature
Currently, on the documentation website at docs.vlang.io, the search bar appears above the title. I wonder if it would look nicer and improve the user's experience if it was displayed underneath the title.
Acknowledgements
- I may be able to implement this feature request
- Dominant language
- HTML
- Stars
- 33
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 vlang/docs
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Search windowOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mozilla/bedrock#17413 · 1 reaction ·
Maintainers usually reply within 2 days
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
drizzle-team/drizzle-orm#6418 ·
Maintainers usually reply within 4 days
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lirantal/discoprint#31 ·
Maintainers usually reply within 1 day