Ron Wheeler wrote:
Mansour Al Akeel wrote:
Ron, I see now. Let's put it this way:
1- obtain the static contents, and create a portlet for each section, including navigation menus. Define these portlets in the registry and wrap it in a war file. 2- In jetspeed create PSML pages to hold each portlet you want including the menus. If you change any page, then just recreate the war and deploy it. This will affect only the changed contents.

Cool up to this point, but then there's two questions here. If I have an existing website that consists of many pages, creating a portlet for each section is a time consuming task. Let's say I have a site of 50 pages only, with navigation and news. Then I will have to create 52 portlet, and then create the corresponding PSML. Isn't this time consuming ?

Assuming that it takes 10 minutes to do each one, you are up to a
couple of days.
There are probably way to make this even faster.
What are these easier ways?  That's what I am after, LOOOL.

The second question: The existing pages already has links between them that links from html to html. In this case I need to know in advance the href for the PSML file. For example, if I have a page called news.html and it has a link to another page called news-1234.html, then I have to update the links to pages/news/recent/news-1234.psml (assuming that the contents of news-1234.html is going to be in pages/news/recent/news-1234.psml). Again, isn't this a time consuming task, and don't I have to know in advance the name of every psml page and what html page it's going to hold.

see now my problems ?

How did you make the links in the first place without knowing the names
of the referenced pages?
I think you got this wrong. I know the names of the pages I am linking to, but I mean I have to change the links from linking to html page to a link to psml. So basically I still have to do a lot of editing in the html part.
Make a small list of the existing pages before you start. Design a
naming convention that maps the new pages to the existing structure.

Ron




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to