## Start your blog
1. Fork [unn-skeleton](https://github.com/runningskull/unn-skeleton)
2. Clone your new repository to your computer (optionally, run `mkvirtualenv myblog`)
3. Run `pip install -r requirements.txt`
4. Edit config.py to set up your deployment settings (default is S3)
5. Think of something good to write (this step is harder than the others)
## Use it day-to-day
`unn idea my-idea` to start a new draft. Use markdown for formatting.
`unn publish my-idea` to converta draft to a post.
`unn build` to build your site's pages.
`unn local` to serve it locally.
`unn deploy` to push it live. (this will build first, as a convenience)
## Customize it
Check the `_template` folder for the basic file structure. `unn` uses Jinja2 for templating.
The `index.html` template gets the following context:
```
{
"posts": [{
"Slug": "the-file-name-without-.md"
... all headers included in this post ...
}, ...]
}
```
The `single.html` template gets the following context:
```
{
"post_html": "<p>The rendered HTML of the post</p>",
... all headers included in this post ...
}
```
`base.html` defines the box that `index.html` and `single.html` live inside (ie. header/footer).
`error.html` is a generic error display page.
Metadata
Release files for unn 0.0.14
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 |
|---|---|---|---|---|
| unn-0.0.14.tar.gz | 4.6 kB | Without provenance | Details for unn-0.0.14.tar.gz |
Release files / unn-0.0.14.tar.gz
| Download URL | unn-0.0.14.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2be639dbe4e6d07367559c94579e28da500aefdab09c43d9101f50940f3bf102
|
|
BLAKE2b-256 checksum How to use checksums |
e71cfd8601e012dc629a9f5f24c264d6794dc1c4c6bdaea7e52a178577008ce8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for unn 0.0.14
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.