Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/pinax/pinax-blog
a blog app for Django
https://github.com/pinax/pinax-blog
Last synced: 3 months ago
JSON representation
a blog app for Django
- Host: GitHub
- URL: https://github.com/pinax/pinax-blog
- Owner: pinax
- License: mit
- Created: 2009-12-22T02:18:07.000Z (almost 15 years ago)
- Default Branch: master
- Last Pushed: 2021-12-13T10:39:36.000Z (almost 3 years ago)
- Last Synced: 2024-04-23T11:15:06.658Z (6 months ago)
- Language: Python
- Homepage:
- Size: 457 KB
- Stars: 462
- Watchers: 21
- Forks: 155
- Open Issues: 20
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Pinax Blog
[](https://pypi.python.org/pypi/pinax-blog/)
[](https://circleci.com/gh/pinax/pinax-blog)
[](https://codecov.io/gh/pinax/pinax-blog)
[](https://github.com/pinax/pinax-blog/graphs/contributors)
[](https://github.com/pinax/pinax-blog/pulls)
[](https://github.com/pinax/pinax-blog/pulls?q=is%3Apr+is%3Aclosed)
[](http://slack.pinaxproject.com/)
[](https://opensource.org/licenses/MIT)
## Table of Contents
* [About Pinax](#about-pinax)
* [Important Links](#important-links)
* [Overview](#overview)
* [Features](#features)
* [Dependencies](#dependencies)
* [Supported Django and Python Versions](#supported-django-and-python-versions)
* [Documentation](#documentation)
* [Installation](#installation)
* [Usage](#usage)
* [Settings](#settings)
* [Scoping](#scoping)
* [Customizing Admin](#customizing-admin)
* [Templates](#templates)
* [Blog Feed Templates](#blog-feed-templates)
* [Change Log](#change-log)
* [History](#history)
* [Contribute](#contribute)
* [Code of Conduct](#code-of-conduct)
* [Connect with Pinax](#connect-with-pinax)
* [License](#license)
## About Pinax
Pinax is an open-source platform built on the Django Web Framework. It is an ecosystem of reusable
Django apps, themes, and starter project templates. This collection can be found at http://pinaxproject.com.
## Important Links
Where you can find what you need:
* Releases: published to [PyPI](https://pypi.org/search/?q=pinax) or tagged in app repos in the [Pinax GitHub organization](https://github.com/pinax/)
* Global documentation: [Pinax documentation website](https://pinaxproject.com/pinax/)
* App specific documentation: app repos in the [Pinax GitHub organization](https://github.com/pinax/)
* Support information: [SUPPORT.md](https://github.com/pinax/.github/blob/master/SUPPORT.md) file in the [Pinax default community health file repo](https://github.com/pinax/.github/)
* Contributing information: [CONTRIBUTING.md](https://github.com/pinax/.github/blob/master/CONTRIBUTING.md) file in the [Pinax default community health file repo](https://github.com/pinax/.github/)
* Current and historical release docs: [Pinax Wiki](https://github.com/pinax/pinax/wiki/)
## pinax-blog
### Overview
`pinax-blog` is a blog app for Django.
#### Features
Current features include:
* support for multiple channels (e.g. technical vs business)
* use of Creole (optional) and Markdown as markup format
* Atom and RSS feeds
* previewing of blog posts before publishing
* optional ability to announce new posts on twitter
* Traditional date based urls or simpler slug-only urls, via configuration
* Control over opengraph and twitter card meta data per post
* Review comments per post for multi-author workflows
* public but secret urls for unpublished blog posts for easier review
#### Dependencies
* django-appconf
* pytz
* pillow
* markdown
* pygments
* pinax-images
See `setup.py` for specific required versions of these packages.
#### Supported Django and Python Versions
Django / Python | 3.6 | 3.7 | 3.8
--------------- | --- | --- | ---
2.2 | * | * | *
3.0 | * | * | *
## Documentation
### Installation
To install pinax-blog:
```shell
$ pip install pinax-blog
```
Add `pinax.blog` and dependency `pinax.images` to your `INSTALLED_APPS` setting:
```python
INSTALLED_APPS = [
# other apps
"pinax.blog",
"pinax.images",
]
```
Add `pinax.blog.urls` to your project urlpatterns:
```python
urlpatterns = [
# other urls
url(r"^blog/", include("pinax.blog.urls", namespace="pinax_blog")),
]
```
### Optional Requirements
`pinax-blog` ships with a few management view templates. These templates reference pinax-images
URLs for adding and viewing images. They also use "bootstrap" formatting.
In order to use these built-in templates, add `django-bootstrap-form` to your project requirements
and `"bootstrapform",` to your INSTALLED_APPS:
```python
INSTALLED_APPS = [
# other apps
"pinax.blog",
"pinax.images",
"bootstrapform",
]
```
Then add `pinax.images.urls` to your project urlpatterns:
```python
urlpatterns = [
# other urls
url(r"^blog/", include("pinax.blog.urls", namespace="pinax_blog")),
url(r"^ajax/images/", include("pinax.images.urls", namespace="pinax_images")),
]
```
If you want `creole` support for mark-up:
```shell
$ pip install creole
```
NOTE: the `creole` package does not support Python 3.
### Usage
As an author, you work with this app via the Django Admin.
You can [customize](customize-admin.md) the editor for the admin at the site
level or just use the stock text areas.
The `description` field in the admin represents the text that will be used in
different HTML META header tags that are useful for controlling the display
on social networks like Twitter and Facebook.
This is the same idea behind the `primary_image` field in the admin.
#### Images
There are custom `markdown` and `creole` extensions for embedding images that
have been uploaded via the inline on the post create or edit form in the admin.
You first upload the image or images you want to use in the post by selecting
them in the file selector in the images section, and then hitting "Save and
Continue Editing". Once the form reloads, you'll see indicators above each
uploaded image with a number between two brackets, e.g. `{{ 25 }}`.
This is the syntax if you are using `creole` for adding that image to your
post. You can just copy and paste that.
If you are using `markdown` however, you will need to use the following
markup in your post:
```markdown
```
or without alt text:
```markdown
```
Adjusting for the number of the image, of course.
### Settings
#### PINAX_BLOG_SCOPING_MODEL
String in the format `"app.Model"` that will set a ForeignKey on the `blog.Post` model
#### PINAX_BLOG_SCOPING_URL_VAR
URL variable name used in your url prefix that will allow you to look up your scoping object
#### PINAX_BLOG_HOOKSET
A hookset pattern common to other Pinax apps. Just a single method: `get_blog(self, **kwargs)` is defined.
Override this in your project to the `Blog` object that will scope your posts.
By default there is only one `Blog` instance and that is returned.
### Scoping
The idea of scoping allows you to setup your project to have multiple blogs
partitioned by whatever domain object you would like.
Add `pinax.blog.context_processors.scoped` to your context processors to put `scoper_lookup` in templates for url reversing.
#### Example
To demonstrate how to set all this up let's walk through an example where we
will scope by `auth.User` so that each user has their own blog at `/users/:username/`.
First we will modify the `settings.py`:
```python
# ... abbreviated for clarity
TEMPLATES = [
{
# ...
"OPTIONS": {
# ...
"context_processors": [
# ...
"pinax.blog.context_processors.scoped"
],
},
},
]
PINAX_BLOG_SCOPING_URL_VAR = "username"
PINAX_BLOG_SCOPING_MODEL = "auth.User"
PINAX_BLOG_HOOKSET = "multiblog.hooks.HookSet" # where `multiblog` is the package name of our project
```
Now, we'll add the url in `urls.py`:
```python
url(r"^users/(?P[-\w]+)/", include("pinax.blog.urls", namespace="pinax_blog"))
```
And finally we'll implement our hookset by adding a `hooks.py`:
```python
from django.contrib.auth.models import User
class HookSet(object):
def get_blog(self, **kwargs):
username = kwargs.get("username", None)
return User.objects.get(username=username).blog
```
This is designed to work out of the box with templates in `pinax-theme-bootstrap`
so you can either use them directly or use them as a reference. If you need to
reverse a URL for any of the `pinax-blog` urls you can simply do:
```django
{% url "pinax_blog:blog" scoper_lookup %}
```
### Customizing Admin
Customizing the admin functionality can be as complex as overriding the `ModelAdmin`
and `ModelForm` that ships with `pinax-blog` or as simple as just overriding
the `admin/blog/post/change_form.html` template.
Here is an example of an actual customization to use the [ACE Editor](http://ace.c9.io/) for
teaser and body content:
```django
{% extends "admin/change_form.html" %}
{% load i18n admin_urls %}
{% block extrahead %}
{{ block.super }}
$(function () {
var contentDiv = $("<div>").attr("id", "content-editor"),
teaserDiv = $("<div>").attr("id", "teaser-editor"),
setupEditor = function (editor, textarea) {
editor.setTheme("ace/theme/twilight");
editor.getSession().setMode("ace/mode/markdown");
editor.getSession().setValue(textarea.val());
editor.getSession().setUseWrapMode(true);
editor.getSession().on('change', function(){
textarea.val(editor.getSession().getValue());
});
editor.getSession().setTabSize(4);
editor.getSession().setUseSoftTabs(true);
};
$(".field-content div").append(contentDiv);
$(".field-teaser div").append(teaserDiv);
var editor1 = ace.edit("content-editor");
var editor2 = ace.edit("teaser-editor");
var textarea1 = $('textarea[name="content"]').hide();
var textarea2 = $('textarea[name="teaser"]').hide();
setupEditor(editor1, textarea1);
setupEditor(editor2, textarea2);
});
#content-editor {
min-height: 300px;
width: 80%;
min-width: 800px;
}
#teaser-editor {
min-height: 100px;
width: 80%;
min-width: 800px;
}
{% endblock %}
```
### Templates
Default templates are provided by the `pinax-templates` app in the
[blog](https://github.com/pinax/pinax-templates/tree/master/pinax/templates/templates/pinax/blog)
section of that project.
Reference pinax-templates
[installation instructions](https://github.com/pinax/pinax-templates/blob/master/README.md#installation)
to include these templates in your project.
View live `pinax-templates` examples and source at [Pinax Templates](https://templates.pinaxproject.com/pinax-blog/list/)!
#### Customizing Templates
Override the default `pinax-templates` templates by copying them into your project
subdirectory `pinax/blog/` on the template path and modifying as needed.
For example if your project doesn't use Bootstrap, copy the desired templates
then remove Bootstrap and Font Awesome class names from your copies.
Remove class references like `class="btn btn-success"` and `class="icon icon-pencil"` as well as
`bootstrap` from the `{% load i18n bootstrap %}` statement.
Since `bootstrap` template tags and filters are no longer loaded, you'll also need to update
`{{ form|bootstrap }}` to `{{ form }}` since the "bootstrap" filter is no longer available.
#### `blog_base.html`
#### `blog_list.html`
`BlogIndexView` and `SectionIndexView` both render the template
`pinax/blog/blog_list.html` with `post_list`, `search_query`, `current_section`
context variables, where `current_section` is either a `Section` object or the
string `"all"`.
The `post_list` variable is a queryset of current blog posts. If the `GET` parameter,
`q` is found, it filters the queryset create a simple search mechanism, then
assigns the value to `search_query`.
#### `blog_post.html`
The four blog detail views (`DateBasedPostDetailView`, `SecretKeyPostDetailView`,
`SlugUniquePostDetailView`, and `StaffPostDetailView`) all render the template
`pinax/blog/blog_post.html` with the `post` and `current_section` context
variables.
The `post` is the requested post. It may or may not be public depending on the
url requested.
#### `dateline.html`
#### `dateline_stale.html`
### Blog Feed Templates
#### `atom_feed.xml` and `rss_feed.xml`
The url `blog_feed` will either render `pinax/blog/atom_feed.xml` or
`pinax/blog/rss_feed.xml` depending on the parameters in the URL. It will pass
both templates the context variables of `feed_id`, `feed_title`, `blog_url`,
`feed_url`, `feed_updated`, `entries`, and `current_site`.
Both templates ship already configured to work out of the box.
## Change Log
### 8.0.1
* Change `from django.utils.functional import curry` to `from functools import partial as curry`
### 8.0.0
* Drop Django 1.11, 2.0, and 2.1, and Python 2,7, 3.4, and 3.5 support
* Add Django 2.2 and 3.0, and Python 3.6, 3.7, and 3.8 support
* Update packaging configs
* Direct users to community resources
### 7.0.5
* Enable installation of both .html and .xml template files via egg
### 7.0.4-image-reenabled
* Reenable imagesets to be inline in the post creation
* Fix Markdown 3 installation exception by changing to 2.6.11 which is the latest working version
### 7.0.3
* Fix migration missing on_delete=
### 7.0.2
* Restore and improve documentation guidance for pinax-images usage
### 7.0.1
* Replace pinax-theme-bootstrap test dependency with pinax-templates
### 7.0.0
* Add Django 2.0 compatibility testing
* Drop Django 1.8, 1.9, 1.10 and Python 3.3 support
* Move documentation into README, and standardize layout
* Convert CI and coverage to CircleCi and CodeCov
* Add PyPi-compatible long description
* Bump minimum required version of pinax-images to v3.0.0 for Django 2.0 compatibility
### 6.3.1
* Bump minimum required version of pinax-images
### 6.3.0
* Add image support in admin
### 6.2.0
* Make the js inclusions a setting
### 6.1.1
* remove inadvertently included IDE file
### 6.1.0
* Add Django 2.0 compatibility testing
* Drop Django 1.9 and Python 3.3 support
* Move documentation into README
* Convert CI and coverage to CircleCi and CodeCov
* Add PyPi-compatible long description
### 6.0.3
* `scoped` context processor handles case when `request.resolver_match` is None
### 6.0.2
* increased max_length of Post.slug field from 50 to 90 chars, matching Post.title field length.
### 6.0.1
* fix templatetag scoping
### 6.0.0
* added support for frontend editing
* removed twitter integrations
* swapped out internal image management for pinax-images
* added a `Blog` scoping model and enabled site defined one to one relationship
custom site-defined scoping.
### 5.0.2
* updated pytz version ([PR #92](https://github.com/pinax/pinax-blog/pull/92))
* updated docs ([PR #87](https://github.com/pinax/pinax-blog/pull/87), [PR #89](https://github.com/pinax/pinax-blog/pull/89))
### 5.0.1
* Fixed feed_url creation in blog_feed view ([PR #82](https://github.com/pinax/pinax-blog/pull/82))
* Updated docs to use url namespace ([PR #87](https://github.com/pinax/pinax-blog/pull/87))
### 5.0.0
* Initial version for core distribution
## History
This app was named `biblion` when originally developed by Eldarion, Inc.
After donation to Pinax, the app was renamed to `pinax-blog`, making it easier
to find and know what it is.
## Contribute
[Contributing](https://github.com/pinax/.github/blob/master/CONTRIBUTING.md) information can be found in the [Pinax community health file repo](https://github.com/pinax/.github).
## Code of Conduct
In order to foster a kind, inclusive, and harassment-free community, the Pinax Project has a [Code of Conduct](https://github.com/pinax/.github/blob/master/CODE_OF_CONDUCT.md). We ask you to treat everyone as a smart human programmer that shares an interest in Python, Django, and Pinax with you.
## Connect with Pinax
For updates and news regarding the Pinax Project, please follow us on Twitter [@pinaxproject](https://twitter.com/pinaxproject) and check out our [Pinax Project blog](http://blog.pinaxproject.com).
## License
Copyright (c) 2012-present James Tauber and contributors under the [MIT license](https://opensource.org/licenses/MIT).