All solutions looks quite good and there is not one better than the other. As you mentionned it really depends of the process you want to put in place for the end-user and especially the validation workflow process (as, even if you can modify an absolute field from another web page, you need to validate the source page so that the content can go live). So this last point may influence your choice according to how you set the permissions on your site. (BTW: Jahia 4.5 will allow distinct separated workflows on containers or on lists, so this may then help validate a news without having to validate the whole page).
Else you may also put a parameter in the url to create "fake" pages (but why won't appear of course in the sitemap) and store all the information in one container. Example in the news on Jahia.org which are declared on the home page, reused and filtered on http://www.jahia.org/jahia/page270.html with a separated "large view" on:
http://www.jahia.org/jahia/Jahia/cache/bypass/pid/270?ctnid=2007
You may also check the document listing and document detail template which reuse some information from the parent container on the detail page (or the template people which display a larger more complete view of the container in a pop-up).
AFAIC I would keep all data of your "member of the week" type in one container definition. From a semantic manner it looks like more correct. And then find some tricks to display more or less information according to your display needs on such or such boxes or pages.
Cheers
St�phane
At 11:25 23/03/2005, you wrote:
Yes, this is not the problem, we do already have custom box-types with our own JSPs.
My problem is the "suggested" workflow:
Now the administrator creates a small "member of the week"-box on the homepage. In the addcontainer-engine he enters the user-Id of the member and the comment why he has been selected as member of the week. The picture and some short details are selected from our user database. The adminsitrator can also select to propagate this box to other pages underneath the main page. So the small box will also be displayed there.
We have not created a page yet, where the details of the "member of the week" are displayed in the main area box.
Now I can think of different solutions and the question is which is better:
1.) We create a standard "member details" page in a "general site pages" container. This page will have the "member details" box in the main area. The page will be called getting the user-id as parameter and display the wanted user. This page could also be used, from other places, where a member is referenced to display his vCard, not only from the "member of the week" box.
2.) The administrator creates a "member of the week-details"-page in the menu and then creates a "member of the week" box to be displayed on the other pages, whereas he would have to make a link connection to the "member of the week-details"-page. The content in the box could be taken from the original page.
3.) We add a page field to the container of the "member of the week" box and so the page will be created either manually or maybe even automatically. The problem is that this new page needs to get the "member details" box into the main area. It is not the most simple workflow for the administrator, if he has to do that all manually.
4.) Implement something like the "maximize" mode in JSR-168, where the portlet box can be maximized to display more details.
5.) Something similar as "SiteMap" and "Search", which in reality stays in the context of the current page-ID, but displays its own stuff in the main area.
6.) Display the member details in a popup.
We are now "short-term" implementing solution 6, but otherwise I tend to implement solution 1. Are we missing something, what would be even better?
Greetings,
Benjamin
St�phane Croisier <[EMAIL PROTECTED]> wrote on 22.03.2005 15:43:13:
>
> Similar to the current jahia "boxes", just make an JSP include file
> (which will call your external remote user management system) so
> that you can select this jsp when choosing the content from your "box". No?
>
> St�phane
>
> At 16:56 21/03/2005, you wrote:
> I hava a box displaying the "member of the week". The members are
> not held in Jahia containers, but in an external user management
> store. Now, when clicking on the "member of the week", his details
> should be displayed in the main area of the page. I can make a JSP
> to display this details, but I do not want to display only this JSP
> in a popup. It should be embedded in the Jahia page, that means all
> other boxes shold stay around.
>
> The "member of the week" box can be on any page based on any
> template, which allows adding boxes.
> So it is similar as the sitemap and searchresult, which can be
> called from any page, but I do not want to create an own engine to
> display the details of the "member of the week".
>
> Is there a standard or recommended way to do this?
>
> Benjamin Papez
