Document split for routers and template renders

[geerteltink]

I just found this in the Expressive v3 project:

Document v3 changes

We need to document version 3. We can begin by creating a new v3 section of the docs based on latest v2, and modifying it to conform to what will actually release with v3.

We may want to consider splitting documentation into discrete repositories as well: pushing router and template renderer docs to the appropriate repositories, etc.

Especially the last part. I'm all in favor of this. I've seen too many notes in those projects that docs need to be updated in zend-expressive.

I'm opening the issue here so we can discuss it and I can close the expressive v3 project.

[weierophinney]

Go ahead and close the v3 project; we've definitely completed the documentation milestone.

I do want to figure out a way to move documentation closer to the packages the documents describe. One issue, however, is that the current structure makes it trivial to link back and forth between documentation; that becomes much harder once we move docs to each package. As such, we need to start with an idea of how we want to manage that linking, and fit it into a bigger narrative of features and reference material.

I'd be happy for somebody to get the ball rolling on that aspect, and I can then provide help around implementation and delivery.

[weierophinney]

This repository has been closed and moved to mezzio/mezzio; a new issue has been opened at https://github.com/mezzio/mezzio/issues/10.