# Developer Options for Export

Both in transcription view and in paper-edit view, there is the option for developers users to export a `json`. Either of the transcription or of the paper-edit.

This is because autoEdit could be used as a starting point to build interactives that have some component that is "transcription powered".

## Example

For example, I once went to a POV hackaton, and finished 2 hours before the deadline thanks to this.

* [github repo](https://github.com/pietrop/BattleSounds)
* [presentation](https://docs.google.com/presentation/d/19TB4CpkCDqMJQvhmZF3I9AN7IQ0VsIA8nsfpdHkfDss/)
* [interactive](http://pietropassarelli.com/BattleSounds/)
* [Notes on tech used](https://github.com/pietrop/BattleSounds/blob/master/notes.md)

The idea is that you can get the transcription (or paper-edit) `json` from autoEdit, as well as the converted webm video. [Combined with some client side tempting and a js logic](https://github.com/pietrop/BattleSounds/blob/master/docs/index.html#L171) can quickly make an "hyper-transcript" like the one in [Battle Sound](http://pietropassarelli.com/BattleSounds/) .


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://autoedit.gitbook.io/user-manual/master/developer-options-for-export.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.