Move online documentation to Github Pages

The old PyPI doesn’t allow to upload new documentation to pythonhosted.org, so we need to remove the docs hosted there and move them to readthedocs.

CAM-Gerlach Edit:

• Move docs from both repo branches
• Create/add other key files
  • README
  • CONTRIBUTING
  • LICENSE
  • AUTHORS
  • .gitignore
  • .gitattributes
• Minor fixes to existing docs
  • Harmonize line endings to LF
  • Remove extra spaces
  • Fix build warnings
• Add sphinx building and enable Travis
  • Add/Setup sphinx makefiles
  • Create/setup .travis.yml
  • Enable Travis and test builds
• Setup repo settings
  • Permissions
  • Tags
  • Description
  • Protected branches
  • Other settings as needed
• Setup and enable doctr deployment
  • Create gh-pages and .nojekyll
  • Configure doctr settings and keys
  • Add doctr deployment to Travis
  • Test functionality and deploy
• Other work items
  • Update conf.py with modernization and fixes
  • Minor doc updates
• Before initial public release
  • Update out of date screenshots
  • Baseline editing pass to update and copyedit
    • Initial cross-file changes
    • Per-file updates, copyediting, line breaks and minimal expansion
    • Apply remaining cross-file style guide formatting and fix links
  • Decide on modern theme
  • Add Profiler doc: PR REVIEW
• Final steps to release
  • Decide on what to do about multiple branches and implement
  • Redirect to docs.spyder-ide.org subdomain
  • Add banner and fonts, etc. from our main website
  • Final layout and link fixes
  • Font size harmonization
  • Add common footer (?)
  • Update other links throughout Spyder to point to new docs instead of PyHosted: PR REVIEW
  • Make layout adaptive/non-broken on narrower screens/windows
• Following release
  • Inform/submit PRs to other sources to add/update Spyder website and doc links
  • Redirect or eventually remove PyHosted docs (in a few months)

[ccordoba12]

Let’s try with Github pages first.

[CAM-Gerlach]

It should be ready by the end of next week, but I’d like to have a new theme in place for our docs before doing the transition.

That’s quite a while, but I suppose it makes sense if it takes us that long to decide on a theme. Hopefully I’ll have the baseline editing pass and the screenshots done sooner, as well.

That would be a great start!

I can’t promise how much in-depth content work I can prioritize for 3.2.9 considering my many other tasks for that and other near-term milestones (website, funding, etc), but hopefully @jitseniesen can pitch in there at some point.