David, I appreciate your help. Please read the comments
David Dyer wrote:
Hi Mansour,
In general I wouldn't put the whole page in as a single portlet, but
certainly it could be done that way.
I thought that's the only way to do it.
What I'd suggest is breaking up your static content into discreet
portlet structures and setting seperate psml pages for each complete
html page.
What do you mean by this ? I was reading a bit in the jetspeed-1
tutorial, in the section "site map" but since very incomplete and I am
not sure how to apply it to JS2. Can you please give me more details in
this direction?
For example, most of our public pages consist of a three column layout
between the header and footer. The left and right column tend to have
a seperate portlet for each "block", allowing the reuse of content
with minimal trouble when it needs to be updated, while the center
column tends to be one big block.
Menuing can largely be handled by using the folder.metadata and,
depending on your page deisgn, maybe modifying the header.vm in your
decorator.
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]
