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

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...MobiNuke Module for Mobile Sites or Separate site?MobiNuke Module for Mobile Sites or Separate site?
Previous
 
Next
New Post
12/4/2012 11:27 AM
 

I currently have DotNetNuke 6.2.3 installed.

We are looking to create a mobile version of an existing site.  I've read all the hype about the new functionality that the release of DotNetNuke 6.1 had with mobile redirection, etc.  I've watched YouTube videos on how to create a mobile site which essentially meant creating a seperate site such as m.domain.com.  And then using the mobile redirection feature to redirect users to that mobile site.  Here are my questions:

1. Why didn't DotNetNuke include some sort of responsive web design functionality so a separate website was NOT needed?  Seems like a lot of redundant work to create and maintain a separate site.  Am I missing something here?

2. I am running a trial version of the MobiNuke module.  Seems like this might do the trick so when a user accesses my site from a mobile device, they will only see the modules I've specified to include on a mobile device.  I can also apply my own stylesheet to the site when viewing on a mobile device.  Why do people think that the updates in DotNetNuke 6.1 replace the functionality that the MobiNuke module seems to provide?  I will say that the documentation on MobiNuke is scarce and probably non-existent but it's also pretty self explanatory when installed.

3. What method did you use to create a mobile site?  My site is quite complex with registration procedures and a shopping cart so I want to make sure I am implementing the best up-to-date method out there.

Thanks!

 
New Post
12/4/2012 12:21 PM
 
Tanya,
Here is how I do it, I keep it simple and I do not create a domain alias.

A: Create mobile pages based on relevant content needed for the mobile user (do not display on menu).

m-home (as parent page)
>m-news (as child pages)
>m-journal
>m-contact
>m-logon

etc...

On each page, I add a module already in use - per page (so your content is always there)
m-news get's a copy of the news module from the news page, no need to re create content, so on. If the developer has updated the theme it would be responsive to the mobile user as well. For certain pages that are content driven by the user such as the journal you can just drop that module on the m-page and the mobile side will pick it up with all the content already there.

Next under Admin -> Site Redirection Management I just told the system if a mobile device hits the home page to direct to m-home, and I did this per m-page added, took just a few min to add them all to the redirection management..

I went further and disabled the default mobile navigation trigger in the mobile page code.

And I replaced it with my own CSS button code, so on the mobile pages I can control where I want the mobile user to go via just text links.

Example:
p style="text-align: left;"><a class="button" href="/m-home/m-profile/m-myClassifieds">Manage Classifieds</a></p>
<p style="text-align: left;"><a class="button" href="/m-home/m-news">News</a></p>


B: DNN 7.0 Default skins Aphelia is responsive and there are a ton of Responsive and Adaptive skins and themes, the community of module builders are rolling out responsive themes in their products as well, just takes time.
Thanks
DWilson


 
New Post
12/4/2012 3:28 PM
 

Thank you for your response.  I think we have decided to create additional pages just as you have done.  While mobinuke could have saved us some time, we are concerned with the lack of documentation and the fact this is the only module that company sells.  I am worried about future support of that module and what it could mean with rework.

Therefore, it looks like we will be creating about 15-20 mobile pages and utilize the existing modules in our original site.

Thanks again,

Tanya

 
New Post
12/4/2012 3:29 PM
 

deleted

 
New Post
12/4/2012 3:29 PM
 

deleted

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...MobiNuke Module for Mobile Sites or Separate site?MobiNuke Module for Mobile Sites or Separate site?


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