DocumentIt renders [markdown]() syntax to HTML and uploads it to the
[Mozilla Developer Network](https://developer.mozilla.org/)
It is run by:
document-it [options] manifest [manifest] [...]
See `document-it --help` for options. It will render to a local
temporary directory by default but you can specify its output with
`--dest` (although you will need to pass `--user` and `--password` to
POST data).
## Manifests
A manifest is in the form:
relative_file_path page_name
...
The file path is relative to the manifest.
(*TODO: more columns of options may be added in subsequent release to
e.g. specify input format and expand macros)
An example manifest is at
http://k0s.org/mozilla/hg/DocumentIt/file/tip/example.manifest
## TODO
Currently, to POST, DocumentIt assumes `curl` is available on the
path. This is an obvious deficiency and it should be replaced with a
request from (e.g.) `urllib2`.
In addition to http://developer.mozilla.org it would be nice to POST
to `http://wiki.mozilla.org` as well. This would allow staging
documents at `wiki.mozilla.org` and then moving to MDN.
There are other features that would be nice to have:
- inclusion of other files
- inclusion of `--help` documentation
In general the approach taken shouldn't compromise the general
approach that the documentation should be the documentation, not
pre-documentation. This may be achieved by the use of (e.g. regex)
macros. For instance:
append(--help.*$,shell(mozmill --help))
Metadata
Release files for document_it 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| document_it-0.1.1.tar.gz | 4.6 kB | Without provenance | Details for document_it-0.1.1.tar.gz |
Release files / document_it-0.1.1.tar.gz
| Download URL | document_it-0.1.1.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8ade28736bbd6e622d34bbc544d6e22cc495efe5f6ae8b9031f64ba598f02da
|
|
BLAKE2b-256 checksum How to use checksums |
cdd1a5f4fcff2994723b52ab314a4f8e803cad947312b8ba933dc89afda2bc7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for document_it 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.