Store store language preference for docs in cookie / clientside
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Would make a lot of sense to store the language preference (javascript / python / ..) in a cookie imo.
Now each time I look for examples I have to manually shift from python to javascript.
Keeping the latest language clicked in a cookie and default to that (and absent that default to python) on each page, improves UX quite a bit.
Thoughts?
Contributor 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.
Research direction
Start by locating the documentation page or template that renders the language examples and the client-side code behind the language selector. Verify how the current selection changes examples; done means the latest choice is stored in a cookie, reused on subsequent pages, and falls back to Python when no choice exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100