Metadata-Version: 2.0
Name: Publ
Version: 0.1.17
Summary: A content-management system for flexible web-based publishing
Home-page: https://github.com/fluffy-critter/Publ
Author: fluffy
Author-email: fluffy@beesbuzz.biz
License: UNKNOWN
Project-URL: Main Site, http://publ.beesbuzz.biz
Project-URL: Bug Reports, https://github.com/fluffy-critter/Publ/issues
Project-URL: Funding, https://patreon.com/fluffy
Project-URL: Source, https://github.com/fluffy-critter/Publ/
Project-URL: Discord, https://discord.gg/xADP3ja
Keywords: website cms publishing blog photogallery sharing
Platform: UNKNOWN
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Framework :: Flask
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content :: Content Management System
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content :: News/Diary
Description-Content-Type: text/markdown
Provides-Extra: dev
Requires-Dist: Flask
Requires-Dist: flask-caching
Requires-Dist: arrow
Requires-Dist: peewee
Requires-Dist: misaka
Requires-Dist: Pillow
Requires-Dist: pygments
Requires-Dist: watchdog
Requires-Dist: awesome-slugify
Provides-Extra: dev
Requires-Dist: pylint; extra == 'dev'
Requires-Dist: twine; extra == 'dev'

# Publ

A personal publishing platform. Like a static publishing system, only dynamic.

## Motivation

I make a lot of different things — comics, music, art, code, games — and none of
the existing content management systems I found quite satisfy my use cases.
Either they don't allow enough flexibility in the sorts of content that they can
provide, or the complexity in managing the content makes it more complicated than
simply hand-authoring a site.

I want to bring the best of the classic static web to a more dynamic publishing
system; scheduled posts, category-based templates, and built-in support for
image renditions (including thumbnails, high-DPI support, and image galleries).
And I want to do it all using simple Markdown files organized in a sensible
file hierarchy.

## Basic tenets

* Containerized web app that's deployable with little friction (hopefully)
* Do one thing (present heterogeneous content), do it well (hopefully)
* Use external tools for site content editing
* Be CDN-friendly
* High-DPI images and image sets as first-class citizens

## See it in action

The main demonstration site is at http://publ.beesbuzz.biz/ — it is of course a
work in progress!

## Operating requirements

I am designing this to work in any WSGI-capable environment with Python 3. This
means that it will, for example, be deployable on any shared hosting which
has Passenger support (such as Dreamhost), as well as on Heroku, Google AppEngine,
S3, or any other simple containerized deployment target.

The file system is the ground truth for all site data, and while it does use a
database as a content index, the actual choice of database shouldn't matter all
that much. I am targeting SQLite for development, but mysql and Postgres should
be supported as well.


