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 ?
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 ?
Ron Wheeler wrote:
Mansour Al Akeel wrote:
Thank you again, David. But I didn't get the part of "encapsulating
any recurring contents" and that's exactey what I am looking for. My
idea was to create all the html pages, then put them in war file
(portelt) and create a portlet page for each of. Creating the portelt
pages will be a time consuming task as I am considering doing it
manually (I don't know if there a better way). By saying manually, I
mean extending the WebpagePortelt and add the regular "view", "edit"
.... etc. methods. I don't know if that's what you meant. I don't
think this is the best way, that's why I am asking if someone got a
better idea. Going back again to what I want, all I need is like a
site navigation structure ("about", contact us, ......etc) to be
browseable by anonymous users.
I really appreciate any input.
What David is suggesting is to have your menu as a portlet that
appears on many pages. Same for any advertising, partner logo, news, etc.
Have a separate portlet for "about us"; another one for "contact us",
etc. These only carry their own content - no menus, no news events.
Then construct your PSML files to include the portlets that you want
on each page.
So your "about us" page will include the static portlets for menus,
partners, advertising, etc. as well as the "about us" portlet.
This way, when the "about us " text changes you only change the "about
us" portlet and your page is updated.
When you change your menu, you only change your "menu" portlet and all
of your existing pages will automatically pick up the new menu structure.
If you have a news item that you want to add to your news page, you
just modify the "news" portlet and any page that includes that portlet
will have your new news item.
As your site gets more dynamic and you start to add features that
require login, you can continue to use your static portlets mixed in
with dynamic portlets that are based on the user profile or whatever.
Ron
David Dyer wrote:
Hi Mansour,
See comments inline below. Sorry if this is reiterating things you
already know, it can be hard to tell just how much someone already
knows on the list sometimes.
Mansour Al Akeel wrote:
And I don't even know if it's possible ot include the HTMLPortlets
derectely in the psml file.
Yes, you can add portlets directly to the psml.
My understanding is that I need to create a portlet entry for each
page, then add them to the PSML file.
Like I said in another branch of this thread, you can do it that
way, creating a single portlet for an entire html page, but I'd
recommend encapsulating any recurring content (for ex. a side bar
perhaps that displays a list of sponsor or partner logos that might
get displayed on several pages). That way any modifications/updates
to recurring content can be handled more easily by editing a single
file instead of having to hit each html page that uses the content.
The problem here, even if I wanted to use this method, there's no
example about adding the portlet entry to the registry for JS2.
The portlet registry is seperate from the psml file and is in the
portlet.xml of your portlet application. Check out the j2-admin
project from the repo and have a look at it.
As far as I can remember, I did this while ago, but it was through
j2-admin tool, where you can choose the portlet to add it to the
page, then you can go and customize the url. I can not find this
portlet. I would prefer to add the pages to psml directly.
Any ideas?
Mansour Al Akeel wrote:
Ron, thank you. This was my suggestion in the first place. What do
I do with the existing html pages ?
Do I add each individual page separately as a Html portlets and
put it into psml file ? What about the menus ?
Ron Wheeler wrote:
You might want to think about this from a different approach.
You might find that you just need to add the existing HTML as
html portlets to you new portal.
Make these available to anyone prior to logging in.
If you go to www.napaexcellence.ca, you can see all of the public
content which is for the most part static content.
We built this portal in stages. The first stage was a "marketing"
site that only had static HTML pages delivered by Jetspeed and
then we added some dynamic portlets (catalog search) and finally
a full portal.
Ron
Mansour wrote:
Hello everyone,
I am looking to add jetspeed to an existing website. The site
already contains few static html pages. We need to give the
users the ability to login and use applications provided by
jetspeed. A problem would be is how to introduce JS2 to the
system. A possible way is to add login fields (username and
password) to the existing pages, and forward the credential to
jetspeed. So the users, will be visiting the same old pages
(HTML), and they can login with their credentials. A problem
with this approach is, it limits our ability to add portlets
that can be viewed by the public. So, if we decided that
portlet1 is to be available to all users, we have to find a
solution for this and it will be a pain to do it. Another way is
to use HTML portlets or IFrame, but these will be pain as well,
as we have to create a portlet for each existing page and update
the links back and forth, plus we have to consider the
navigation menus.
The existing site consists of html pages, and menu items
(contact us, about us, products(a page for each ), services(a
page for each ), home , documentation,......etc) with javascripts.
I though about using the concept of subsites, but AFAIK, it's
for hosting another jetspeed instance, and can not be used for
HTML.
If someone have done something similar to this please provide me
with an advice.
Thank you in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
