lightning/docs
Dan Nissenbaum 7ada52e33c
Typo in major heading seen by newcomers (#14501)
* Typo in major heading seen by newcomers

Correct typo in one of the first major headings newcomers to Lightning see when they are considering migrating their code to use Lightning.

I know this is a trivial change in terms of the text change itself, but I really think it's valuable for one of the most important landing pages that users first investigating Lightning see - to have rock-solid, professional text without obvious typos. Here was a typo in the main heading itself. I suggest fixing it straightaway via this PR.

Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
2022-09-07 09:06:30 +00:00
..
source-app Introduce lightning connect (#14452) 2022-08-31 15:59:03 -04:00
source-lit Integrate `lightning_utilities.core.imports` (#14475) 2022-09-06 12:56:20 +00:00
source-pytorch Typo in major heading seen by newcomers (#14501) 2022-09-07 09:06:30 +00:00
README.md Update docs README on how to build docs (#13465) 2022-07-17 18:48:10 +00:00
create-symlinks.py prepare space for fused docs (#14160) 2022-08-30 09:25:05 -04:00

README.md

PyTorch-Lightning Docs

We are using Sphinx with Napoleon extension. Moreover, we set Google style to follow with type convention.

See following short example of a sample function taking one position string and optional

from typing import Optional


def my_func(param_a: int, param_b: Optional[float] = None) -> str:
    """Sample function.

    Args:
        param_a: first parameter
        param_b: second parameter

    Return:
        sum of both numbers

    Example::

        >>> my_func(1, 2)
        3

    Note:
        If you want to add something.
    """
    p = param_b if param_b else 0
    return str(param_a + p)

Building Docs

When updating the docs, make sure to build them first locally and visually inspect the html files in your browser for formatting errors. In certain cases, a missing blank line or a wrong indent can lead to a broken layout. Run these commands

git submodule update --init --recursive
make docs

and open docs/build/html/index.html in your browser.

When you send a PR the continuous integration will run tests and build the docs. You can access a preview of the html pages in the Artifacts tab in CircleCI when you click on the task named build-Docs of ci-tests at the bottom of the PR page.

Notes:

  • You need to have LaTeX installed for rendering math equations. You can for example install TeXLive with the necessary extras by doing one of the following:
    • on Ubuntu (Linux) run sudo apt-get update && sudo apt-get install -y texlive-latex-extra dvipng texlive-pictures
    • use the RTD docker image
  • You need to have pandoc installed for rendering Jupyter Notebooks. On Ubuntu (Linux), you can run: sudo apt-get install pandoc

Developing docs

When developing the docs, building docs can be VERY slow locally because of the notebook tutorials. To speed this up, enable this flag in before building docs:

# builds notebooks which is slow
export PL_FAST_DOCS_DEV=0

# fast notebook build which is fast
export PL_FAST_DOCS_DEV=1

docs CSS/theme

To change the CSS theme of the docs, go here. Apologies in advance... this is a bit complex to build and requires basic understanding of javascript/npm.