Instantly convert Google Documents into reStructuredText
For documents inside organizations (e.g. G Suite), make sure
Link Sharing settings are set to
Anyone with the link
Once the document is converted, you can revert any sharing permissions. Curious how this looks before trying? Take a look below
- Handles in-line bold, italic and link markup
- Bulleted lists, including nesting at multiple levels
- Captures imagery and serves them as part of the converted bundle
- Writes rST friendly tables!
Don't have a Google Doc handy? Copy and paste this link and try it out ☝️
It's not difficult to convert content in Google Docs to reStructuredText, but it sure is boring. Automating that process to get 90% of the work done by a machine is preferred.
There's a few other reasons. Google Docs is a great place to collaborate and write things out. But in most organizations, much of those useful words don't make it out of Google Docs! They grow stale rather than making it to developer-facing documentation that can be maintained and used by a larger audience.
If you have no documentation in an open standard like reStructuredText, perhaps this service was the final nudge you needed to get started. Otherwise if you have existing documentation in rST, hopefully this provides you some convenience!
What happens with my documents when I send them to your service?
First, the reason we ask for a single, shareable Google URL is so we don't scrape your documents. We intentionally chose this method so this application has no capabilities to search through the documents on your Google Drive.
Once the file is shared, it is fetched via the Google API, stored temporarily for parsing, and returned to you under a salted hash.
Finally, when the
rst file (or bundle with images) is
downloaded, we immediately ask if you'd like to remove it from our
servers. If you request so, we remove all associated files from our
servers and related database entries. Yes, this is hard delete. We're
happy if you leave the data on our servers if it's not sensitive as it
provides more samples to run the parser against, improving the service.
reStructuredText is the most ideal choice for creating rich, searchable, and portable documentation. It is widely used within the Python community, specifically via the Sphinx project.
What's the stack?
This project was built by Bartek Ciszkowski. He cares about documentation and misses the open idealism of the early web. This is a small attempt to bring some of that back.