Disable .jekyll since we just serve from site
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 12
- Forks
- 11
- Avg merge
- 34m
- Merged PRs (30d)
- 3
Description
We just serve the already built documentation from the website so we should not need the Jekyll config here.
It should just work with an empty .nojekyll file.
WARNING: This can be potentially disruptive and can cause the pytorch.org/docs site to go down.
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
Inspect the repository's Jekyll configuration and the way the already-built documentation is served from the website. Verify the effect of replacing that configuration with an empty .nojekyll file, and confirm that pytorch.org/docs remains available before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jekyll
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100