Bark is a single file static site generator. I set out to make it primarily because I got tired of dealing with Jekyll and didn’t want to put a bunch of effort into tweaking Pelican to look alright.
I hope to continually improve it so perhaps others might find it useful.
Features
Single file
Jinja2 templating language
Posts support markdown formatting thanks to Hoedown with SmartyPants.
Installation
You can install using the source by simply using:
python setup.py install --user
or:
sudo python setup.py install
for system wide installation.
Usage
Usage: bark [options] (new NAME|make [SETTINGS])
- -h, --help
Show this message.
- --version
Show version.
Contributing
If something is wrong or could be improved, let me know or submit a pull request.
1 maintainer
Metadata
1 maintainer
Release files for bark-ssg 1.3.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 | |
|---|---|---|---|---|
| bark-ssg-1.3.4.tar.gz | 4.3 kB | Without provenance | Details |
Release files / bark-ssg-1.3.4.tar.gz
| Download URL | bark-ssg-1.3.4.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47298489f181d17b58e73da5c6dda5d8da366f6e739202f27d02d8feaf206fdf
|
|
BLAKE2b-256 checksum How to use checksums |
3adfd15c465a46428046f89322bf6b16b6efcb28a17228341c6221a48bcc7f07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bark-ssg 1.3.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.
