Relocate instructions that are specifically geared towards test authors
to the "docs" directory. Persist API documentation in its current
location and configure Sphinx to include relevant aspects in the
generated website.
This is an rough cut of a new structure for the wptserve documentation. I'll
admit that the organization of content about "pipes" is a little too focused on
implementation details. gh-3 identifies this same problem in some of the
existing documentation; if we can agree on this solution at a high-level, then
I'd be happy to address that issue with more fine-grained restructuring in a
follow-up patch.
Relocate instructions that are specifically geared towards test authors to the "docs" directory. Persist API documentation in its current location and configure Sphinx to include relevant aspects in the generated website.
This is an rough cut of a new structure for the wptserve documentation. I'll admit that the organization of content about "pipes" is a little too focused on implementation details. gh-3 identifies this same problem in some of the existing documentation; if we can agree on this solution at a high-level, then I'd be happy to address that issue with more fine-grained restructuring in a follow-up patch.
Depends on gh-7.