I see that this has come up a few times.

I have played with a few options:

1. Hard-coding static pages like the built-in FAQ and About pages.
This works, but it's not very slick.

2. Using Comatose or some other CMS.  This works pretty well, but it
is not easy to make your static pages have the same look and feel as
the rest of the CE site.  Maybe I'm missing something, but it is not
clear how to have Comatose pages use the CE layouts and helpers.

3. Build a simple CMS into CE.

Is anybody interested in option #3?

Off the top of my head, I could see something like this:

- A simple list of pages -- no hierarchy.
- Use essentially the same interface used for managing blog posts
(except perhaps skipping tags)
- Add some checkboxes to determine where to include links to the posts
(bottom of page and in 'Explore...' list are the two that come to
mind).
- Update layout and site_index template to include links to to CMS
pages (of course anybody would be free to over-ride these any way they
want)
- Use /pages as the url prefix for CMS pages

The installer could include a migration that adds the FAQ and About
pages as sample pages in the CMS.

I don't think it makes sense to have a full-blown CMS, but it seems
plausible that many sites will have no content at all outside CE.  I
think it would be pretty typical for such a site admin to want an easy
way to post a 'Terms of Service' page, 'Privacy Policy' page, etc.

For example, I just needed to add a 'How to Donate' page to a CE site
I am hosting for a local non-profit.  One page was not a good enough
reason to try to integrate a 3rd party CMS, but hard-coding it was a
bit of a pain too.

Bruno -- would you be interested in having something like this in
core?
Everybody -- do you have feedback about must-have features, etc?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/communityengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to