Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Mobile Strategy / Content SyncingMobile Strategy / Content Syncing
Previous
 
Next
New Post
4/24/2012 4:58 PM
 

Hello,

We're in the planning stages of a migration to DNN.  We're researching and trying to determine what the best strategy is for our mobile site.  I know there are basically 2 different approaches: separate mobile site and responsive site using media queries.

We're leaning towards the separate mobile site due to the fact that media queries only works in >= IE8 and a lot of our members are older and most likely using older versions of IE.  Another issue is the layout restrictions with the responsive method.  What I hear is that it can cause issues when you use tables and have specific size attributes on your images.

Most likely we'll have a separate mobile site but I wanted to check in with the community and see what everyone else is doing and what experiences you may have come across with both methods and hopefully get some recommendations.

We've considered the mobiNuke approach. Anybody have any experience with that module?

One last question, has anyone ever heard of a module that will sync data between your desktop and mobile sites?  If something like this was available then we'd be able to use a separate mobile site and sync up the pages of the site as we see fit.  We're looking at a site with 10k plus pages and don't really want to have to duplicate all that information.  So if something like this doesn't exist, we'll most likely just pick the most critical pages and duplicate those in the mobile site.

Thanks in advance for anyone's thoughts on this issue.

 
New Post
4/25/2012 3:12 AM
 
I'm interested in whatever you come up with.

I've not got as far as serious planning, but I was wondering if it might be possible to just use a separate skin for a mobile site.

That way the same actual modules get served up to both full size and mobile browsers. The skin could turn off 'frills' areas for the mobile users.

DNN does not have a configuration based way of serviing different skins to different users, but I'm wondering about using the basis of Will Strohl's blog post (http://www.willstrohl.com/Blog/PostId/668/Dynamically-Change-DotNetNuke-Skins-by-Security-R) to issue a skin cookie to mobile users.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
4/25/2012 8:59 AM
 
Richard,

What you mentioned with the separate skin for mobile is my understanding of how the mobiNuke module works. If your on a mobile device it detects that and you can adjust the settings on a per module basis to show the module on mobile, desktop, or both. I haven't used this module yet, but that is how I believe it works from what I've read on it.
 
New Post
4/25/2012 1:51 PM
 

Mobinuke replaces the skin depending on the client being served. Another option is the core mobile soluition -this was previously a PE/EE only feature but we backported it and it's now available to everyone with the 6.1.5 release (see http://www.dotnetnuke.com/Resources/B... for more details) - you can use this to redirect requests to different pages, each of which can obviously have their own look & feel and content.

As for the content, if it is the same you can make a copy of a page easily http://hive.dotnetnuke.com/Default.as... and have the content set as a refence so editing it in one location updates it in all the references - you can do the same with individual modules http://hive.dotnetnuke.com/Default.as... - in many cases this will probably fit your needs, but one thing to be aware of is that sometimes content is not always approriate for all devices e.g. a 20 item list is fine for desktop but a mobile client should show less entries. In some cases the module settings will allow for you to make these changes and in a few cases modules that support templating will allow this, but in others this is not possible e.g. the html module will show all content for all instances. I think that now the mobile capabilities are in all versions it's probable we can make some changes to better support these cases e.g. a simple enhancement to the html module might just show 200 characters of text followed by a "read more..." link for a mobile client. I don't believe any enhancements have been created for this yet, so if you've any good ideas I recommend logging them at support.dotnetnuke.com

Thanks.

 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
4/25/2012 2:20 PM
 
Thanks for your reply Cathal

The redirecting and content copying I assume only works within the same portal, is this correct? We were planning on having a completely separate portal for our mobile site (m.example.com). Is that the best approach for SEO and analytics purposes? I don't spend a lot of time in GA so I'm not sure how the mobile tracking works. I know if we had a separate mobile portal we could track it that way.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Mobile Strategy / Content SyncingMobile Strategy / Content Syncing


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out