CrisisCleanup / crisiscleanup-1

[OLD] Legacy Crisis Cleanup on GAE/Python
https://sandy-disaster-recovery.appspot.com
Other
8 stars 4 forks source link

Micro CMS and blog #209

Closed aarontitus closed 11 years ago

aarontitus commented 11 years ago

Original author: cpw...@gmail.com (March 01, 2013 15:32:06)

  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.

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

Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=209

aarontitus commented 11 years ago

From cpw...@gmail.com on March 01, 2013 15:33:05 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.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 05, 2013 18:54:07 Candidate library: http://www.gae-cms.com/ (python, not Django, still under active development)

aarontitus commented 11 years ago

From v...@aarontitus.net on March 05, 2013 19:03:28 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.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 05, 2013 19:25:55 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:

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

aarontitus commented 11 years ago

From cpw...@gmail.com on March 08, 2013 15:21:22 Based on discussion today,

Stage 1 is:

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

aarontitus commented 11 years ago

From cpw...@gmail.com on March 08, 2013 15:22:04 I will take this.

aarontitus commented 11 years ago

From v...@aarontitus.net on March 12, 2013 13:22:59 Also add admin textareas for /home

aarontitus commented 11 years ago

From v...@aarontitus.net on March 12, 2013 13:24:43 Andy is using a responsive CSS Junction template. For now, just apply that same template to each of these pages.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 12, 2013 23:58:23 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.

aarontitus commented 11 years ago

From v...@aarontitus.net on March 19, 2013 22:52:55 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, “

Your HTML here

” Am I missing something?

aarontitus commented 11 years ago

From cpw...@gmail.com on March 20, 2013 10:40:19 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.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 20, 2013 15:36:23 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).

aarontitus commented 11 years ago

From cpw...@gmail.com on March 20, 2013 15:36:55 Also, should we need to backup the edited HTML / PageBlocks somehow?

aarontitus commented 11 years ago

From v...@aarontitus.net on March 20, 2013 16:06:32 When we build a backup feature (#106), the html blocks should be backed up too.

So, if I were to delete all of the fields that currently say

Your HTML here

, instead of going blank, the website would revert to the HTML/Jinja defaults. Is that correct?

aarontitus commented 11 years ago

From cpw...@gmail.com on March 20, 2013 23:05:35 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.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 24, 2013 21:48:54 This is now done and deployed to production.

aarontitus commented 11 years ago

From cpw...@gmail.com on March 26, 2013 12:53:29 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.

aarontitus commented 11 years ago

From v...@aarontitus.net on March 26, 2013 14:27:23

17: Understood.

I'm going to mark this done.