Add a 'docs-doc2dash' Tox target.

[tseaver]

Generates a Dash-style docset from the Sphinx-rendered HTML using doc2dash.

I've copied the docset manually into my Zeal library, and it looks pretty good.

Follow-up to my comment on #1690.

[dhermes]

Do we actually need this?

[jgeewax]

Yea - confused. What's the goal ?

[tseaver]

The goal is to generate Dash-compatible docsets, to allow developers to import the docs into their offline API docs (searchable/readable via Dash, Zeal, etc.): I was trying to address one of the problems with just expecting people to read the online docs.

[daspecster]

I know a decent number of people that use Dash. If this works as is and is low maintenance, I vote to use it.

[dhermes]

@tseaver Shall we close this PR?

[tseaver]

I've rebased it to resolve the conflict in .gitignore.

If we automated building the Dash docsets and pushing them to Dash as part of our tag-release deployment, that seems like a low-cost win to me: users who like using offline docs will be able to consume them with their preferred tool.

[dhermes]

@tseaver Feel free to merge when my request is addressed.

Are you going to automate the process of creating and publishing this target?

[tseaver]

Are you going to automate the process of creating and publishing this target?

I'm thinking about it. There seem to be two options:

• Host the docs ourselves, e.g. in the gh-pages branch.
• Create a pull request to the Dash-User-Contrib repository, creating or updating a docset there.

Automating the first seems quite feasible; the second seems infeasible.