CMS functionality

[snvandoorn]

1. As a prerequisite for CMS/Blog functionality, different user rights are needed.
2. I would like to see the possibility to add and manage i18n content in NDB tables.
3. As a next step I would like to see full text search functionality.

Is something already working on adding these. If not, i´ll be. But I would need support from someone on adding suitable unit tests, as I am not very familiar with writing these for such framework projects.

[snvandoorn]

I suggest to add the CMS-i18n functionality to the core boilerplate module (and not as a separate module), because I guess most people would need something like it.
A rough outline of what is planned:

MenuItems can link to any in- or extra site functionality
Articles are html editable content

Foreseen forms:
EditMenu (also used for creating)
TranslateMenu (top has original, bottom has translation language(s))
EditArticle (also used for creating)
TranslateArticle (top has original language, bottom has translation language(s))
ListMenus(lists all menus, with for each supported locale the translation status - as a link to it)
ListArticles(lists all articles, with for each supported locale the translation status - as a link to it)
ViewArticle (with youtube content possible)
ViewArticleTeaser
UploadFile (for referenced images etc.)
ChangeNewsletterSubscription

View rights:
They are configured on a per menu and article item basis, and may only be set by editor and above.
The view levels foreseen are: guest, subscriber1-4, translator, editor, superuser, admin
The edit levels foreseen are: translator, author, editor, superuser, admin

Edit rights:
Only an Administrator and higher may edit menu structure.
An Author and higher may create an article or menu item
A Translator may translate an article into one of his configured languages
An editor may release an article, and change menu and article structure

[coto]

interesting... would you like to begin on it?

[snvandoorn]

Yes, now that I am not aware of any remaining major issues of your excellent boiler plate.
Would you also be contributing? Especially how to add sensible unit tests for such web functionality is not quite clear to me. If yes, should we use your, or my repository as the main repository, while development is going on?
I'll start with the CMSUserRights, CMSMenuItem and CMSArticle classes and the EditMenu and EditArticle forms.

[coto]

just let me know