Implemented in 4.x
Implementation tracked in MGNLBLOG@jira.
Purpose
Implement a collection of page and component templates that enable blogging with Magnolia CMS. Blog functionality is often asked for on RFP's. While we don't see Magnolia CMS as a blogging platform per se, the infrastructure we provide out of the box should make it almost trivial to provide blog functionality that to some extend might even exceed some of the existing options. It could also be useful for our own bloggers, or used as a system to provide blog space for the community once we have a proper forge.
Goals
Map between typical blog functionality and Magnolia CMS features.
Blog functionality | Magnolia CMS feature |
|---|---|
Create a blog entry | Standard page creation |
Edit a blog entry | Standard content editing |
List of recent blog posts | STK teaser list |
Commenting | |
List of latest comments | |
RSS feed | |
Post archive | Paginated list of blog entries |
Social bookmarking | |
Calendar | STK |
Tags | |
Search | |
Security, administration & all the other goodies | Standard Magnolia functionality |
Missing functionality | Status |
|---|---|
Trackback and ping | Out of scope for first version |
Status
Teresa has done a prototype for a recent demo; this is working but not yet what I [BK] want. A wire frame has been attached to this page that describes what it should look like. The wire frame is done exclusively using existing paragraphs or stuff from the STK html prototype. No specific new design would be necessary, however, we should make the templates reside on a top level (multi-site support !) as a blog generally looks better without being embedded in a corporate site (we don't want all the menu entries etc).
Next steps
As soon as someone has time, it would be nice to see this template(s) come together. Please also document your steps, either in daily blog entries or otherwise, as the goal is also to put together a tutorial (Antti) that shows how to create your own blog system using Magnolia.
To Be Decided
- should the blog module be part of standard STK or its own module?
Overview
Content Tools