Olaf iLink ha scritto:
Hello,
are there some best practices you can suggest concerning the management
of news items and similar data?
No, nothing written! It is up to you and to your implementation :-)
F.e. in the new STK there is a news-area, where the content-editor can
edit the news-items inline, but there doesn't seem to be a way to add
*new* news-items from the front-end inline interface.
In the "out-of-the-box" news area, you can't create a new news from the
front end. You must create a new page under news section page:
- news
- news-01
- news-02
- your-new-news
It seems this has
to be done from the website tree in the authoring interface? Is there a
particular reason for this? And can end-users understand this, because
they can add all kinds of paragraphs in the front-end, but one of the
most used areas, news, they cannot add from the front-end?
This is a common problem: why "turn back" to admin interface in order to
create a news? But even to activate a page..
We manange this adding XHR functionalities to our templates (Activate
pages, create content, deactivate pages, clone content..).
E.g.: you can add a new button which launch a javascript call (Ajax) to
the server. The call can simple add a new page for you.
I can think of globally 3 ways of managing news: - from the website
tree,
of course, the standard way...
from the data module with a news type,
in this way you can loose agility on editing, because CMS taglibs that
came out with Magnolia don't works well with data (or other) workspaces.
or in the front-end inline.
yes, sure, but avoid to reproduce dialogs. I suggest to implement only
methods which operates at "page" level, not at paragraph level.
In the last case, how do you cope with publishing dates? Do you have to
program your templates so that an editor sees *all* the available
news-items, or does the editor only see the "live" news-items (ie
published/active/etc.) that the website visitor also can see?
This is another common problem. On author instance you often manage
content not already activated or already deactivated. So, you can
consider to query only "activated" content, the ones with the green
light *on preview* (not on normal admin mode).
Maybe you can consider to use visual icons saying that this news is not
activated, like a "v" sign or "x" sign (or what you like).
On our content we have a common status bar which indicates the status
and the author.
A lot of thoughts and directions, and thus the question if there are
some best practices on this topic :)
HTH!
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
