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

DM-11004: Update based on build-stack-docs tool implementation #3

Merged
merged 2 commits into from
Jul 20, 2017

Conversation

jonathansick
Copy link
Contributor

@jonathansick jonathansick commented Jul 8, 2017

This updates the documentation design based on implementation developments with the build tool (see also lsst-sqre/documenteer#14).

  • There is now a doc/manifest.yaml file that declares what documentation directories are included in a package and helps to create links.
  • Introduces a new package topic type so that the packages/git repositories can be documented clearly. Previously package documentation was being conflated with module (python API) documentation topics, but this isn't a great fit — especially for data only packages, or packages with multiple modules.

See https://dmtn-030.lsst.io/v/DM-11004

manifest.yaml and the idea of separating module and package
documentation types came up during development of the build-stack-docs
tool in documenteer.

Declaring documentation layout in manifest.yaml makes it easier to build
the integration documentation.
Making package documentation (documentation at the level of a Git
repository) separate from documentation about the Python module is a
good thing. This commit reflects the introduction of the package topic
type.
@jonathansick jonathansick merged commit 9831b60 into master Jul 20, 2017
Copy link

@SimonKrughoff SimonKrughoff left a comment

Choose a reason for hiding this comment

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

I know this is merged, but I failed to give it a read before.

..

Module documentation directories are symlinked into pipelines_lsst_io_\ ’s ``modules/`` directory.
Likewise, package documentation directories are symlinked into pipelines_lsst_io_\ ’s ``packages/`` directory. With all documentation content directories linked into the pipelines_lsst_io_ directory, Sphinx is able to build the LSST Science Pipelines documentation if it were a unified project.

Choose a reason for hiding this comment

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

Extra space between linked and into.

documentation if --> documentation as if

- EUPS dependencies (computed both downstream and upstream).

Most documentation provided by a package is included in :ref:`module topics <module-type>`.
The package topic type, though, provides a documentation platform the package itself.

Choose a reason for hiding this comment

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

platform the --> platform for the

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.

2 participants