Hi Imran,
GAE-CMS runs fine for me locally (Windows7).
It was somewhat difficult to get started (e.g. I would not have thought
that Section has anything to do with Menus).
I think the documentation has to start with presenting the structure of a
website according to GAE-CMS (what are the elements of a website and how do
they relate to one another).
Next there should be a number of how tos:
1. how to structure of the site:
1. how to add or manage menu items
2. how to add pages/sections to pages
3. how to change the header (site title, slogan, logo, etc.)
4. how to change the footer
2. How to add/edit content
1. what types of content are supported and how to add/edit the content
3. How to change the appearance
1. How to do theming, etc.
2. How to work with CSS
4. How to add functionality
1. already available functionality/modules
2. adding jQuery functionality and plug-ins
3. develop custom modules
I think all of the above should describe what one can currently do. If you
could provide me a brief list of what you can currently do with the site, I
will try to structure and expand it
In addition, I would strongly recommend:
1. providing a few sample sites as a showcase to give people an idea of
the kinds of things they can do (at least some screen shots)
2. providing some more variation of themes (blog, club or church
community, small business, etc.).
Unfortunately many people have little imagination and unless you show them
an example that is close to what they want to they cannot see how they
would create what they want to have.
I also recommend quickly creating a place for designer/developer support to
encourage designer/developers to create solutions for their customers
around GAE-CMS. (Having a showcase of example sites - even if just front
pages, would greatly help recruiting developers and designers to the CMS).
Regarding permissions; I spent a number of years architecting an
application framework and ERP system built upon it. This including
designing user, session and security management. My number one thing was
high performance. Our solution was built on a relational database, but I
have been giving thought as to how to accomplish the same in the noSQL
world. In general, I have found the permissions functionality in CMS
systems to be lacking the needed flexibility. I say this because most
people are not really looking for a CMS system but rather an application
framework with CMS capabilities. This gets one into situations with
complicated workflows where different users need to be able to see
different views of the same content types or the same user might be able to
see different content depending on the content of particular fields.
Please let me know what you were thinking of as a permission concept and I
will be able to respond with some ideas you might want to consider.
Bill
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/I9WslKykPVwJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
