I really mean to write this for myself. But if I write it here then
maybe it will be of use to someone else as well.
I’ve been working on moving the additions I made to Corex into
extensions for Mental. I’ve added a lot of functionality (and plan to
add more). To the page edit screen.
I have an idea from an interface perspective.
Imagine a set of tabs aligned vertically along one of the side of this
page edit screen. The main tab contains the existing Page edit screen.
Extensions could add tabs to this page edit screen.
For instance, there might be a tab for using a particular WYSIWYG editor
For instance, there might be a tab to manage comments on the Page being
edited. (as in the case of a blog post) This tab might only appear for
certain page types.
I my case:
There will be a tab to manage all of the Page Attributes of a page:
A Page can have a number of named attributes. There are different types
of attributes such as UploadedFileAttribute, and different tags for
referring to them (i.e. <r:image attribute=“logo”/> would output an
image tag referencing the file that was uploaded as the “logo”
There will be a tab for managing which parts of a page are layout
oriented. (contain multiple radius tags) And which parts of a page are
content oriented. (These parts are the parts that a client of an already
setup CMS would be interested in) Also in this tab, you can manage an
attribute called “Inherits from Page”, in which you can select any page
as the parent page. (Not parent as in site hierarchy, but parent as in
template) If a particular tag does not resolve on a particular page.
(i.e. there is an <r:content part=“header”/> but there is no “header”
page part) Then the processor should look for and use a page part from
the “parent” page if it is available. Inherits from page supports 2 new
page types (Selectable from the normal page edit interface).
TemplatePage and ContentFromTemplatePage. A shortcut will be made for
creating new ContentFromTemplatePages based on an existing TemplatePage.
The new page will have only the page parts that were marked as “content
oriented” on the TemplatePage it inherits from.
There will be a tab simply for editing those page parts that have been
marked as content oriented. This tab would be displayed in place of
regular editor tab for TemplagePage typed pages.
This means I intend to submit a ticket with the changes to core to
support an ability for extensions to add these page-editor tabs… if I
ever get around to it…
If anybody else is interested in helping me develop (the code or the
interface) for these half-coded ideas, let me know and I’ll send you my
hacked up version of Corex.