Micro CMS and blog

[GoogleCodeExporter]

1. Lightweight content management (CMS) facilities should be available to the 
Administrator for editing a small but configurable set of pages, e.g. "/about", 
"/privacy"...

Should include the ability to upload images.

2. Host a blog separately, then link to it from the CMS.

Original issue reported on code.google.com by cpw...@gmail.com on 1 Mar 2013 at 3:32

[GoogleCodeExporter]

CMS pages could be handled as route catch-alls:

i.e. if page is not a app-defined page (e.g. /map etc.), then try CMS pages, 
else 404.

Original comment by cpw...@gmail.com on 1 Mar 2013 at 3:33

[GoogleCodeExporter]

Candidate library: http://www.gae-cms.com/ (python, not Django, still under 
active development)

Original comment by cpw...@gmail.com on 5 Mar 2013 at 6:54

[GoogleCodeExporter]

Is there a demo somewhere?  If it's even one step above "Type HTML in this 
white box and click save," then I'll probably go for it.

Original comment by v...@aarontitus.net on 5 Mar 2013 at 7:03

[GoogleCodeExporter]

http://www.gae-cms.com/ is itself a demo. Oddly, the author has chosen to use a 
GAE-like theme to cause confusion.

The major issues I see are:
* will it integrate easily with our existing auth (big CMS won't be simple)? 
(open q)
* does it do images? (change log implies yes)

I haven't looked at it in any detail yet - I was going through a list of 10-20 
at a high level.

Original comment by cpw...@gmail.com on 5 Mar 2013 at 7:25

[GoogleCodeExporter]

Based on discussion today,

Stage 1 is:
* add admin textareas to receives HTML for /[root], /about, /terms, /privacy
* add navigation to support these
* add blog url to navigation
* NO image uploads (host offsite)

Stage 2 is: replace stage 1 by integrating a GAE-compatible (simple/micro) CMS.

Original comment by cpw...@gmail.com on 8 Mar 2013 at 3:21

• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

I will take this.

Original comment by cpw...@gmail.com on 8 Mar 2013 at 3:22

• Changed state: Started

[GoogleCodeExporter]

Also add admin textareas for /home

Original comment by v...@aarontitus.net on 12 Mar 2013 at 1:22

[GoogleCodeExporter]

Andy is using a responsive CSS Junction template.  For now, just apply that 
same template to each of these pages.

Original comment by v...@aarontitus.net on 12 Mar 2013 at 1:24

[GoogleCodeExporter]

CMS-a-like block-based editing is now available for the global admin (r232, 
r233, v141) on the testbed, using the new HTML+CSS design. Existing pages only.

Original comment by cpw...@gmail.com on 12 Mar 2013 at 11:58

[GoogleCodeExporter]

Quick question- I see that the Edit Pages are live on crisiscleanup.org: 
https://www.crisiscleanup.org/admin-edit-pages
But they don’t seem like they’re implemented yet, because each block says, 
“<p>Your HTML here</p>”
Am I missing something?

Original comment by v...@aarontitus.net on 19 Mar 2013 at 10:52

[GoogleCodeExporter]

The pickups got reverted/disabled in a revision leading up to r248, likely to 
allow a quick push to the live site.

I will add a default set of values based on the current HTML pages, rather than 
"Your HTML here" - this will allow pushing without having to use Edit Pages 
immediately afterwards.

Original comment by cpw...@gmail.com on 20 Mar 2013 at 10:40

[GoogleCodeExporter]

To be clear, what I am proposing here is:
1. Move out all the HTML again, block by block.
2. Put the blocks in a HTML/Jinja file of defaults.
3. Have that file of defaults populate the PageBlocks instead of using "Your 
HTML here"

This will mean the site works with a blank database (or lacking PageBlocks).

Original comment by cpw...@gmail.com on 20 Mar 2013 at 3:36

[GoogleCodeExporter]

Also, should we need to backup the edited HTML / PageBlocks somehow?

Original comment by cpw...@gmail.com on 20 Mar 2013 at 3:36

[GoogleCodeExporter]

When we build a backup feature (Issue 106), the html blocks should be backed up 
too.

So, if I were to delete all of the fields that currently say <p>Your HTML 
here</p>, instead of going blank, the website would revert to the HTML/Jinja 
defaults. Is that correct?

Original comment by v...@aarontitus.net on 20 Mar 2013 at 4:06

[GoogleCodeExporter]

Yes, exactly.

We could also have a script to update the HTML/Jinja defaults file from the 
PageBlocks, to allow us to update the repository.

Original comment by cpw...@gmail.com on 20 Mar 2013 at 11:05

[GoogleCodeExporter]

This is now done and deployed to production.

Original comment by cpw...@gmail.com on 24 Mar 2013 at 9:48

[GoogleCodeExporter]

Re #14 & #15: I was unclear here. The website will only revert back to the 
defaults if the blocks are deleted from the database - not if they are set to 
empty strings by the Admin. Therefore, it's not possible to revert back via the 
Admin interface at present - you would need to use the Appengine dashboard.

Original comment by cpw...@gmail.com on 26 Mar 2013 at 12:53

[GoogleCodeExporter]

#17: Understood.
I'm going to mark this done.

Original comment by v...@aarontitus.net on 26 Mar 2013 at 2:27

• Changed state: Done