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

Build a viable pipeline for writing documentation. #22

Closed
pbugnion opened this issue Dec 2, 2014 · 2 comments
Closed

Build a viable pipeline for writing documentation. #22

pbugnion opened this issue Dec 2, 2014 · 2 comments

Comments

@pbugnion
Copy link
Owner

pbugnion commented Dec 2, 2014

This package desperately needs documentation. Unfortunately, the obvious solution of writing IPython notebooks and exporting them to HTML doesn't work. Javascript widgets are not included in the exported HTML, so you can't actually see the maps (see this, for instance).

I think that the solution will be to write a custom 'nbexport' script, but that sounds like a real pain.

@pbugnion pbugnion added this to the v0.2 milestone Dec 2, 2014
@pbugnion pbugnion mentioned this issue Dec 2, 2014
@pbugnion
Copy link
Owner Author

I think the way to do this is as follows:

  • write all the documentation in IPython notebooks.
  • find ways of exporting the Python models to Backbone JS models. This should be as simple as defining a Jinja2 template.
  • for cells corresponding to map views, export the Python model to a JS file. Add a line in the cell metadata corresponding to this JS file..
  • Overload the relevant bits of nbconvert so that the JS models are embedded by default in the output of the relevant cells.
  • Write contributors documentation on "how to write documentation". (How meta is that?)

This sounds like a somewhat difficult pipeline, but I think it's quite elegant. And the ability to export Python models to Backbone is an added bonus.

@pbugnion
Copy link
Owner Author

This is old and outdated. Closing as not really relevant.

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

No branches or pull requests

1 participant