#3: Option to add development blogs to projects
- Contents
Active projects may wish to have a place to blog about what's going on. Having a "Development Blog" for each PSC project could make this easier.
- Proposed by
- optilude
- Seconded by
- limi
- Proposal type
- Architecture
- State
- being-discussed
Motivation
Active projects often want to build a relationship with their users, for example by giving regular updates about the progress of development. A development blog is a good vehicle for such updates.
Proposal
Add a "Development blog" type to the PSC that projects can optionally create.
Implementation
There are two choices:
- Use an existing blog product (there are several
- Use simple smart folders with an ATDocument-derived type for blog entries that has comments enabled.
There are concerns that the existing blog products are too complex for this simple use case. This should be evaluated carefully.
Risks
- Re-inventing the wheel! We must either find a suitable existing blog product, or make something that takes 90% of its implementation from standard Plone features (smart folders with RSS, simple content types, workflow, comments).
- Making it too "lose". The smart folder option runs the risk that people will tinker with the smart folder settings and modify the criteria to break the blog functionality.
