nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Mobile CMS Content

stya

Hi All,

we are planning to make a mobile version of our existing website.

In existing website the content is from cms.

The following sequence is used for our existing website.

Teamsite dcr->generated to html-->deployed to webserver.

Now will there be any change if I want to resuse the same content to

mobile version.

Could any one help me .

If any one has steps to convert a web application to mobile application pls
let me know (help guides/urls)

thanks in advance.
stya

Find more posts tagged with

Comments

Bjorn

Hi All,

we are planning to make a mobile version of our existing website.

In existing website the content is from cms.

The following sequence is used for our existing website.

Teamsite dcr->generated to html-->deployed to webserver.

Now will there be any change if I want to resuse the same content to

mobile version.

Could any one help me .

If any one has steps to convert a web application to mobile application pls
let me know (help guides/urls)

thanks in advance.
stya

Will there be any change? Yes. Actually - YES. Your "workflow" or process will look somewhat the same, but it will (or should) have an added step of now generating both the mobile and standard content.

The good news is that if you're using TeamSite it's really easy to generate something like WML or XHTML Mobile that WAP devices can use by taking your existing content (in the DCR) and generating new output. But you need to know about these standards/protocols to do so. So if your question is in regards to designing a site for mobile use, that really has nothing to do with TeamSite and is well beyond the scope of these forums. You might try starting here: http://articles.sitepoint.com/article/designing-for-mobile-web, but that's about site design and development, not content management or TeamSite specifics.

(Also, even if your mobile site is intended for so-called "smart phones" that have web browsers, you'll still almost certainly going to want alternate, slimmed-down content to handle such situations.)

In closing, it's easy to use the same content to generate many different kinds of output; that's one of the benefits of TeamSite. But the development and design of that content requires its own knowledge and skill sets.

sample_data.JPG