prestodb / prestodb/prestodb.github.io
CAPTCHA on docs
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6
- Forks
- 70
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
I had to complete a CAPTCHA to read the public docs. Do they really need this protection?
If the rest of the site needs protection against bots, could the documentation move to a subdomain?
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
The issue names no files, tests, or entry points. Start by reviewing how the public documentation is hosted and where CAPTCHA protection is applied; determine whether the documentation can be served separately without that challenge. Done means the public docs remain accessible without CAPTCHA while any required bot protection elsewhere is preserved.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100