========
Create example API documentation in multiple languages (like [Stripe's API
docs][stripe-api])
[stripe-api]: http://stripe.com/docs/api
Usage
-----
### Directory
You need (roughly) this directory structure.
├── code
│ ├── test.py
│ └── test.rb
├── docs
│ └── index.md
└── layout
│ └── index.html
├── static
├── styles.css
└── some_img.jpg
It will be transformed into (roughly) this directory structure:
├── code
│ ├── test.py.html
│ └── test.rb.html
├── index.html
└── static
├── some_img.jpg
└── styles.css
### Individual Files
For code, just write code as normal. Flockdoc will try to take care of
formatting for you. The output will look a little like [Docco][docco].
For markdown, think [Jekyll][jekyll]: header with layout specified, and then
your code. YAML header with Markdown body. Example:
title: Test
context:
key: value
---
This is a test document with a key: {{ key }}
Documents are passed through Jinja2 rendering before they are output.
[docco]: http://jashkenas.github.io/docco/
[jekyll]: http://jekyllrb.com/
Metadata
Release files for flockdoc 0.0.4
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 |
|---|---|---|---|---|
| flockdoc-0.0.4.tar.gz | 4.9 kB | Without provenance | Details for flockdoc-0.0.4.tar.gz |
Release files / flockdoc-0.0.4.tar.gz
| Download URL | flockdoc-0.0.4.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42b4f0e6dcbe209341aebfb7540b1dd9910b36793b203b542c8a225b5f165807
|
|
BLAKE2b-256 checksum How to use checksums |
cc1d177a84671004aadb25437ce21349eac800d1324fb5f65a8de21d3a94f1c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for flockdoc 0.0.4
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.