Build from top-level project

[jputrino]

Description

@bmarshall13 has a makefile that lets him build from the top-level project (this one) when writing docs for a subproject (lightweight-proxy).
We need to leverage this to identify and correct issues that would not occur when building docs locally from a subproject (e.g., not finding the _static directory or knowing where to find included files).

• investigate variablizing paths to make it easier to specify where files can be found

[bmarshall13]

I'm not sure if this is an issue or not.

I am building this repo with make html while in f5-ci-docs/docs

The paths are these:

1. f5-ci-docs/docs/f5-fpp/README.rst
2. f5-ci-docs/docs/f5-fpp/_includes/topic_kubernetes-notes.rst
3. f5-ci-docs/docs/f5-fpp/_static/example-service-flowpoint.yaml

1 contains .. include:: _includes/topic_kubernetes-notes.rst referencing 2
2 contains .. literalinclude:: _static/example-service-flowpoint.yaml referencing 3

1 correctly renders the content in 3, which is suprising. It shows that the relative root of the literalinclude is that of 1, and not 2 where the statement exists.

The problem here is that I can only include that content from a specific directory. To prove this to myself, I also include 2 from f5-ci-docs/docs/index.rst. That doesn't render correctly.

However,

[bmarshall13]

The docs say that the path should be relative to the file doing the importing, but this doesn't appear to be the case.

http://www.sphinx-doc.org/en/stable/markup/code.html#includes

[jputrino]

added to lightweight-proxy; see project Makefile.

[jputrino]

rST epilog needs to be controlled from f5-ci-docs to ensure consistency and easy updating across all docs.