Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sphinx generated documentation #521

Merged
merged 10 commits into from
Nov 28, 2019
Merged

Sphinx generated documentation #521

merged 10 commits into from
Nov 28, 2019

Conversation

Borda
Copy link
Member

@Borda Borda commented Nov 17, 2019

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos, doc improvements)
  • Did you read the contributor guideline?
  • Did you make sure to update the docs?
  • Did you write any new necessary tests?

What does this PR do?

Fixes #465.

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

The main changes:

  • create Sphinx documentation
  • move docs from MD to docstring in particular package/modules
  • CI: add building documentation
  • rename root_module.root_module -> base_module.lightning

Watch

cd docs
pip install -r requirements.txt
make clean
make html
make latexpdf

then open pytorch-lightning/docs/build/html/index.html

@Borda
Copy link
Member Author

Borda commented Nov 19, 2019

@Ir1d do you have practical experience with customization of pytorch_sphinx_theme?
I was able to add it and build but I have not found an option how to overwrite short links and navigation elements...

@Ir1d
Copy link
Contributor

Ir1d commented Nov 20, 2019

@Borda I didn't modify the theme.. perhaps we need to maintain a fork by modifying pytorch_sphinx_theme itself

@Borda Borda changed the title Sphinx generated documentation [WIP] Sphinx generated documentation Nov 22, 2019
@Borda
Copy link
Member Author

Borda commented Nov 22, 2019

@williamFalcon @Ir1d @neggert @jeffling could you pls have look and new docs...
you can build it locally or I can issue a public version on ReadTheDocs (but it will be public) :]

@Borda
Copy link
Member Author

Borda commented Nov 22, 2019

also @williamFalcon I would like to know what paths shall we use for doc/tutorial/blog/etc.

@neggert
Copy link
Contributor

neggert commented Nov 22, 2019

Got everything checked out and building. Lots of warnings, but everything seems to have worked okay.

First off, thanks for tackling this. This is a huge undertaking and it's going to be a great improvement to the package.

A couple notes:

  • Template needs to be tweaked a little bit to remove or fix dead links in the header.
  • Need to replace they PyTorch logo with something else (do we have an official logo for Lightning?)
  • Because a lot of the trainer is split up into mixins, the auto-generated doc tree is a little bit confusing. It might be more effective to do what PyTorch does: Create the high-level structure of the docs manually, but pull in autodoc for individual classes/functions/methods. That way we can organize things in a way that makes more sense for the user.

I don't want the perfect to be the enemy of the good, though. A lot of work has gone into getting this all set up, so maybe we just merge this with the understanding that it needs a bit more tweaking before we set RTD to public.

@williamFalcon
Copy link
Contributor

williamFalcon commented Nov 22, 2019

@Borda this looks amazing! i agree with @neggert, let’s merge and fix to get it to a spot to publicly launch.

I do also need to build it over the next day or so.

@Borda
Copy link
Member Author

Borda commented Nov 22, 2019

Got everything checked out and building. Lots of warnings, but everything seems to have worked okay.

I saw them too, but I wanted to get a feedback if this is the right way to go before I will invest more time to it...

  • Template needs to be tweaked a little bit to remove or fix dead links in the header.

Sure, depending on how large changes will we need we may need to fork the theme, but first I would need to know what links to keep and what to drop... @williamFalcon

  • Need to replace they PyTorch logo with something else (do we have an official logo for Lightning?)

yes, there is but it is the sam eas icon of an epic task in JIRA :)

  • Because a lot of the trainer is split up into mixins, the auto-generated doc tree is a little bit confusing. It might be more effective to do what PyTorch does: Create the high-level structure of the docs manually, but pull in autodoc for individual classes/functions/methods. That way we can organize things in a way that makes more sense for the user.

I will have a look

I don't want the perfect to be the enemy of the good, though. A lot of work has gone into getting this all set up, so maybe we just merge this with the understanding that it needs a bit more tweaking before we set RTD to the public.

I agree that we (me) shall get to stage that it is publishable, but then we shall merge it or move it to created docs branch so also others can help because this just reveals lost of issues which were simply hidden behind the static pages...

@williamFalcon
Copy link
Contributor

the lightning logo is on the readme :)

@Borda
Copy link
Member Author

Borda commented Nov 22, 2019

@Borda Borda mentioned this pull request Nov 23, 2019
@awaelchli
Copy link
Contributor

@Borda I see no problem. Lightning IS epic. ;)

@Borda
Copy link
Member Author

Borda commented Nov 24, 2019

@neggert I have forked the PyTorch theme and did some adjustment but somehow the logo is not visible, it is probably something in CSS which I do not understand... Could you have look?

@Ir1d
Copy link
Contributor

Ir1d commented Nov 24, 2019

Have you tried replacing this file directly? https://github.com/Borda/lightning_sphinx_theme/blob/master/images/logo.svg

@Borda
Copy link
Member Author

Borda commented Nov 24, 2019

Have you tried replacing this file directly? https://github.com/Borda/lightning_sphinx_theme/blob/master/images/logo.svg

these images are irrelevant, you need to look at these inside the package...
Well, it seems to be fixed now... 8-)

@Borda
Copy link
Member Author

Borda commented Nov 24, 2019

@williamFalcon @Ir1d @neggert @jeffling I would go for a merge, so pls could you do a review...

@Borda
Copy link
Member Author

Borda commented Nov 25, 2019

Todo: ensure back compatibility...

@Borda Borda changed the title Sphinx generated documentation Sphinx generated documentation [wip] Nov 25, 2019
@Borda Borda changed the title Sphinx generated documentation [wip] Sphinx generated documentation Nov 25, 2019
@Borda Borda mentioned this pull request Nov 25, 2019
4 tasks
Copy link
Contributor

@jeffling jeffling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff, only a few nitpicks. I did not read every single word on the actual docs, but we should do a quick review once this is deployed just for readability

.readthedocs.yml Show resolved Hide resolved
.readthedocs.yml Show resolved Hide resolved
docs/source/intro.md Show resolved Hide resolved
pytorch_lightning/callbacks/pt_callbacks.py Show resolved Hide resolved
tests/test_y_logging.py Outdated Show resolved Hide resolved
This was referenced Nov 26, 2019
@williamFalcon
Copy link
Contributor

@Borda rebase?

@Borda Borda changed the title Sphinx generated documentation Sphinx generated documentation [wip] Nov 27, 2019
@Borda
Copy link
Member Author

Borda commented Nov 27, 2019

yes, working on it right now, there are couple collisions... 😺
Well, it turns out that I have to do a cherry-picking

@Borda Borda changed the title Sphinx generated documentation [wip] Sphinx generated documentation Nov 27, 2019
@williamFalcon
Copy link
Contributor

williamFalcon commented Nov 28, 2019

I'm following your instructions @Borda:

cd docs
pip install -r requirements.txt (this was wrong and was missing -r. i just fixed it in your instructions
make clean

I'm getting these errors:

(pytorch-lightning) ➜  pytorch-lightning git:(master) make clean
make: *** No rule to make target `clean'.  Stop.
(pytorch-lightning) ➜  pytorch-lightning git:(master) cd docs
(pytorch-lightning) ➜  docs git:(master) make clean
make: *** No rule to make target `clean'.  Stop.
(pytorch-lightning) ➜  docs git:(master) make html

make: *** No rule to make target `html'.  Stop.
(pytorch-lightning) ➜  docs git:(master)

@Ir1d
Copy link
Contributor

Ir1d commented Nov 28, 2019

are you in the folder of correct Makefile (this PR)?

seems you are in master branch

@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

pip install -r requirements.txt --user
sudo pip install -r docs/requirements.txt
cd docs
make clean
make html

CI builds without any problem https://circleci.com/gh/Borda/pytorch-lightning/298
I have it also tested on RTD, see https://torch-lightning.readthedocs.io/en/docs

formatting

move docs from MD to docstring in particular package/modules

formatting

add Sphinx ext.

rename root_module to core

drop implicit name "_logger"

drop duplicate name "overwrite"

fix imports

use pytorch theme

add sample link mapping

try fix RTD build

use forked template

fix some docs warnings

fix paths

add deprecation warnings

fix flake8

fix paths

revert refactor

revert MLFlowLogger
@williamFalcon
Copy link
Contributor

williamFalcon commented Nov 28, 2019

Yup... still nothing.

(pytorch-lightning) ➜  ~ cd ~/Developer/opensource/pytorch-lightning
(pytorch-lightning) ➜  pytorch-lightning git:(master) pip install -r requirements.txt --user

Requirement already satisfied: scikit-learn>=0.20.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 1)) (0.20.2)
Requirement already satisfied: tqdm>=4.35.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 2)) (4.35.0)
Requirement already satisfied: numpy>=1.16.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 3)) (1.16.4)
Requirement already satisfied: torch>=1.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 4)) (1.3.0)
Requirement already satisfied: torchvision>=0.3.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 5)) (0.4.1a0+d94043a)
Requirement already satisfied: pandas>=0.24 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 6)) (0.24.2)
Requirement already satisfied: test-tube>=0.6.9 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r requirements.txt (line 7)) (0.7.3)
Requirement already satisfied: scipy>=0.13.3 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from scikit-learn>=0.20.2->-r requirements.txt (line 1)) (1.3.1)
Requirement already satisfied: six in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from torchvision>=0.3.0->-r requirements.txt (line 5)) (1.12.0)
Requirement already satisfied: pillow>=4.1.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from torchvision>=0.3.0->-r requirements.txt (line 5)) (6.0.0)
Requirement already satisfied: pytz>=2011k in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from pandas>=0.24->-r requirements.txt (line 6)) (2019.1)
Requirement already satisfied: python-dateutil>=2.5.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from pandas>=0.24->-r requirements.txt (line 6)) (2.8.0)
Requirement already satisfied: imageio>=2.3.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from test-tube>=0.6.9->-r requirements.txt (line 7)) (2.5.0)
Requirement already satisfied: tb-nightly==1.15.0a20190708 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from test-tube>=0.6.9->-r requirements.txt (line 7)) (1.15.0a20190708)
Requirement already satisfied: future in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from test-tube>=0.6.9->-r requirements.txt (line 7)) (0.18.1)
Requirement already satisfied: protobuf>=3.6.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (3.8.0)
Requirement already satisfied: absl-py>=0.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (0.7.1)
Requirement already satisfied: markdown>=2.6.8 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (3.1.1)
Requirement already satisfied: grpcio>=1.6.3 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (1.21.1)
Requirement already satisfied: wheel>=0.26; python_version >= "3" in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (0.33.4)
Requirement already satisfied: werkzeug>=0.11.15 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (0.15.4)
Requirement already satisfied: setuptools>=41.0.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from tb-nightly==1.15.0a20190708->test-tube>=0.6.9->-r requirements.txt (line 7)) (41.0.1)
(pytorch-lightning) ➜  pytorch-lightning git:(master) pip install -r docs/requirements.txt
Requirement already satisfied: mkdocs-material==4.4.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r docs/requirements.txt (line 1)) (4.4.0)
Requirement already satisfied: mkdocs==1.0.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r docs/requirements.txt (line 2)) (1.0.4)
Requirement already satisfied: Pygments>=2.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (2.4.1)
Requirement already satisfied: pymdown-extensions>=4.11 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (6.1)
Requirement already satisfied: mkdocs-minify-plugin>=0.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (0.2.1)
Requirement already satisfied: Jinja2>=2.7.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (2.10.3)
Requirement already satisfied: PyYAML>=3.10 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (5.1.2)
Requirement already satisfied: Markdown>=2.3.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (3.1.1)
Requirement already satisfied: tornado>=5.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (6.0.3)
Requirement already satisfied: click>=3.3 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (7.0)
Requirement already satisfied: livereload>=2.5.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (2.6.1)
Requirement already satisfied: pep562 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from pymdown-extensions>=4.11->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (1.0)
Requirement already satisfied: htmlmin>=0.1.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-minify-plugin>=0.2->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (0.1.12)
Requirement already satisfied: jsmin>=2.2.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-minify-plugin>=0.2->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (2.2.2)
Requirement already satisfied: MarkupSafe>=0.23 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from Jinja2>=2.7.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (1.1.1)
Requirement already satisfied: setuptools>=36 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from Markdown>=2.3.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (41.0.1)
Requirement already satisfied: six in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from livereload>=2.5.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (1.12.0)
(pytorch-lightning) ➜  pytorch-lightning git:(master) cd docs

(pytorch-lightning) ➜  docs git:(master) make clean
make: *** No rule to make target `clean'.  Stop.
(pytorch-lightning) ➜  docs git:(master) cd ..
(pytorch-lightning) ➜  pytorch-lightning git:(master) ls
LICENSE                    appveyor.yml               mkdocs.yml                 pytest.log                 setup.cfg                  tox.ini
MANIFEST.in                dist                       pip-wheel-metadata         pytorch_lightning          setup.py                   update.sh
README.md                  docs                       pl_examples                pytorch_lightning.egg-info site
Untitled Folder            lightning_logs             pyproject.toml             requirements.txt           tests
(pytorch-lightning) ➜  pytorch-lightning git:(master) sudo pip install -r docs/requirements.txt
WARNING: The directory '/Users/user/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
WARNING: The directory '/Users/user/Library/Caches/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Requirement already satisfied: mkdocs-material==4.4.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r docs/requirements.txt (line 1)) (4.4.0)
Requirement already satisfied: mkdocs==1.0.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from -r docs/requirements.txt (line 2)) (1.0.4)
Requirement already satisfied: mkdocs-minify-plugin>=0.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (0.2.1)
Requirement already satisfied: pymdown-extensions>=4.11 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (6.1)
Requirement already satisfied: Pygments>=2.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (2.4.1)
Requirement already satisfied: click>=3.3 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (7.0)
Requirement already satisfied: Jinja2>=2.7.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (2.10.3)
Requirement already satisfied: tornado>=5.0 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (6.0.3)
Requirement already satisfied: PyYAML>=3.10 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (5.1.2)
Requirement already satisfied: livereload>=2.5.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (2.6.1)
Requirement already satisfied: Markdown>=2.3.1 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (3.1.1)
Requirement already satisfied: htmlmin>=0.1.4 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-minify-plugin>=0.2->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (0.1.12)
Requirement already satisfied: jsmin>=2.2.2 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from mkdocs-minify-plugin>=0.2->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (2.2.2)
Requirement already satisfied: pep562 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from pymdown-extensions>=4.11->mkdocs-material==4.4.0->-r docs/requirements.txt (line 1)) (1.0)
Requirement already satisfied: MarkupSafe>=0.23 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from Jinja2>=2.7.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (1.1.1)
Requirement already satisfied: six in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from livereload>=2.5.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (1.12.0)
Requirement already satisfied: setuptools>=36 in /Users/user/miniconda3/envs/pytorch-lightning/lib/python3.7/site-packages (from Markdown>=2.3.1->mkdocs==1.0.4->-r docs/requirements.txt (line 2)) (41.0.1)
(pytorch-lightning) ➜  pytorch-lightning git:(master) cd docs
(pytorch-lightning) ➜  docs git:(master) make clean
make: *** No rule to make target `clean'.  Stop.
(pytorch-lightning) ➜  docs git:(master)

@Ir1d
Copy link
Contributor

Ir1d commented Nov 28, 2019

hi @williamFalcon are you in master branch or this pr?

@williamFalcon
Copy link
Contributor

this pr

@williamFalcon
Copy link
Contributor

oh wait, i think it went back to master for some reason. hold on

@williamFalcon
Copy link
Contributor

@Borda ok, got it to work.

It looks like a good starting point but we need to work on the navigation since it is not intuitive at all right now nor obvious where to find things.

Can we deploy this behind a dev endpoint to see what it looks like right now?

Things that need to be fixed:

  • simple, intuitive menu on the left
  • logo

This is a good start, so I'm just going to highlight a few places we should focus on to get it to a good release point.

I assume the people who look in places like this are people contributing to lightning, but we need to show it in a more user friendly way.
image

This menu should have a Trainer and LightningModule root folder, then a kind of similar structure to the docs we have right now.

Again, this is an amazing v1, so great job! Let's now move to make this more user friendly before we fully switch over to these docs.
image

@williamFalcon
Copy link
Contributor

@Borda I approve to merge this right now (again phenomenal job!).

@neggert @jeffling @Ir1d you guys good to merge as well? this is a big PR so want to get multiple eyes/approvals.

@Ir1d
Copy link
Contributor

Ir1d commented Nov 28, 2019

Talking about dev endpoint.. I'm suggesting netlify again.
Meanwhile it seems @Borda has built this PR on readthedocs

This menu should have a Trainer and LightningModule root folder, then a kind of similar structure to the docs we have right now.

I remember it involves some advanced usage of sphinx? Similar to what pytorch did..? Maintaining a root structure on our own instead of generating automatically? Not so familiar..

@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

Can we deploy this behind a dev endpoint to see what it looks like right now?

Not sure about his, it is a bit bond my experience so far...

Things that need to be fixed:

  • simple, intuitive menu on the left
  • logo

What do you mean by logo, size?

This is a good start, so I'm just going to highlight a few places we should focus on to get it to a good release point.

for sure, I just wanted to keep the PR straight forward and draw the backbone so since this PR the work can be simpler divided (parallelize) into smaller PRs
btw, also each rebases after the master change and solving collision is a bit painful...

@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

@Ir1d I believe that the actual docs is also powered by RTD according to the config in root

@Ir1d
Copy link
Contributor

Ir1d commented Nov 28, 2019

Oh I didn't notice this config before. @Borda Thx
Netlify is really good at deploy previews for docs, saves a lot of time for cloning and builing. https://www.netlify.com/tags/deploy-previews/

@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

@Ir1d RTD allows you to have a separate version for each branch even for each tag/release

@williamFalcon
Copy link
Contributor

@Borda for the record we use pl not pt

import pytorch_lightning as pl

@williamFalcon williamFalcon merged commit d71556e into Lightning-AI:master Nov 28, 2019
@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

for the record we use pl not pt

typo 👼 and what about tl as torch lightning 😉

@Borda Borda deleted the docs branch November 28, 2019 17:49
@Borda
Copy link
Member Author

Borda commented Nov 28, 2019

FYI, this is the fork we are right now using for docs - https://github.com/Borda/lightning_sphinx_theme

@jeffling
Copy link
Contributor

Nice job bringing this in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automatic docs
6 participants