Can we generate Mobile app version of already created web-site on Interwoven products

Hi There,

We are using Temasite 7.1, Livesite 7.1 and OpenDeploy 7.1.

We have created a site which is component based using above mentioned versions of Teamsite.
Now we have create Mobile version of the same site i.e. it should be available for Mobile apps. It there any way we can directly used already developed web-site. How we can accomplish it for Mobile apps..

Please suggest.

Thanks,
Kapil Jain

Find more posts tagged with

Comments

Bowker

*** Disclaimer - this may not be the best way to do this, but this is what our current plans are ***

We are doing the same thing and I'm sure other are.

The difficulty factor will be based upon a couple of things:
0) Are the pages 100% the same content just laid out differently?
1) Did you use DCRs for all your content or is the content entered in the content area of each page?
2) Are the words being used on the desktop site the same words you want on the mobile site? [or separate fields in the DCRs for desktop vs. mobile]
3) Do you want the same IA (Information Architecture) on both sites [not a show stopper, but has ramifications if the answer is no]

If the answer to 0) above is yes, then you need to create new CSS and you're done. That is assuming the pages were built in such a way that CSS does all the layout work.

However you will, most likely, need to build a new page layout, new components, new CSS, new .page files for the mobile site. Then use segmentation to segment people to the different pages in the site map.

Item 0) does not apply to us, our pages are very different.

Rick Poulin

If the answer to 0) above is yes, then you need to create new CSS and you're done. That is assuming the pages were built in such a way that CSS does all the layout work.

If the answer is no, then you've got a bigger issue. Building a mobile site as an afterthought is kindof like making a meat-oriented meal and simply removing the meat for your vegetarian friends (if you don't have vegetarian/vegan friends, just know that they find this extremely rude/insulting/inconsiderate).

My personal rule of thumb is DON'T make the mobile site a separate entity. Not only are you creating a maintenance nightmare, you're also treating your mobile users as second rate. People accessing sites from today's smart phones want the full experience. Independent mobile sites only make sense for now-ghetto cell phones, and then you're usually only serving up the most relevant portion (~20 pages) of your site, say "latest news" and such. Instead, I'd say rethink and rework your primary site to be able to have two (or more) renditions of it. In the best case, that's simply playing with the CSS. In more complex cases, make your components mobile-aware and serve up variations on the content (maybe excluding images or something like that).

</high_horse>

Kapil_sape

HI All,

Thanks for your replies.
Answer to (0) is YES. Also most of the data is coming from DCRs.

So, in this case I want the new CSS from UI dev team and then I need to create my new .page files for mobile site to incorporate CSS changes. No need to modify any of the .component file. Am I correct?

Secondly you told something about segmentation to segment people to the different pages in the site map .i.e. segmenting mobile users to mobile page and site users to site pages. Can you please tell me from where I can get details for this and how to implement it?

Thanks,
Kapil Jain

thatfish

Sounds like you are in a good place.

I suggest using server-side or client-side logic to apply the appropriate CSS depending upon mobile device or not (server-side is best - there are some open source good mobile detection libraries). Start with a simple proof-of-concept.

CMS Preview may need some extra thought and you are entering a whole new world of browser compatibilty issues on the mobile platforms

Antharix

Any further updates on this? I am looking for some more details for a similar requirement.

interDev

*** Disclaimer - this may not be the best way to do this, but this is what our current plans are ***

We are doing the same thing and I'm sure other are.

The difficulty factor will be based upon a couple of things:
0) Are the pages 100% the same content just laid out differently?
1) Did you use DCRs for all your content or is the content entered in the content area of each page?
2) Are the words being used on the desktop site the same words you want on the mobile site? [or separate fields in the DCRs for desktop vs. mobile]
3) Do you want the same IA (Information Architecture) on both sites [not a show stopper, but has ramifications if the answer is no]

If the answer to 0) above is yes, then you need to create new CSS and you're done. That is assuming the pages were built in such a way that CSS does all the layout work.

However you will, most likely, need to build a new page layout, new components, new CSS, new .page files for the mobile site. Then use segmentation to segment people to the different pages in the site map.

Item 0) does not apply to us, our pages are very different.

Dan, Are you using Custom-Fixed layouts or freestyle layouts?If fixed layouts, how did you overcome the problem of having defined width of each section. These widths are specified for Desktop browsers and not specified according to mobile browsers. So how did you overcome this problem and defined new widths for mobile browsers?

Rick Poulin

Dan, Are you using Custom-Fixed layouts or freestyle layouts?If fixed layouts, how did you overcome the problem of having defined width of each section. These widths are specified for Desktop browsers and not specified according to mobile browsers. So how did you overcome this problem and defined new widths for mobile browsers?

First thought that pops into mind is override those widths in your mobile stylesheet and mark the overrides as !important. This requires that you use inline-css="false" in your layout, because I don't believe you can override inline styles with !important.