First let me try to explain the differences:
Mobile Template = A mobile website is a separate version of your desktop website and it is designed to be used exclusively on smartphone devices.
Responsive Template = A responsive designed website is a website designed for use on desktops, tablets and smartphones.
If you do not have the time to maintain (upgrade) your current template, adding a Mobile Template will mean you will now have 2 templates to maintain.
Go Responsive!
All the templates I offer ARE responsive, I do believe all Anne's templates offered here on Zen-Cart uses my Responsive DIY Template Default CSS framework as well, I haven't had much time to keep up with the Zen-Cart forum so I may be wrong.
What the Responsive DIY Template Default CSS framework was built for....
1.) Creates a Responsive Template as a starting point for those designing their own website templates.
2.) Allows one to easily adapt the HTML necessary to convert an existing website template.
a.) The included CSS framework does the magic! :smile:
3.) Includes google Mobile Detect which allows Mobile users to view Full Website (desktop version) if they choose too.
4.) Includes php and css code to hide sideboxes on mobile devices which would otherwise clutter screen and slow loads.
Johnnycopilot:
Will this change the appearance of my site on a (regular) sized computer screen? I mean, the CSS tweeks and stuff, are those just needed for viewing on the mobile size screens? I just don't want to get in over my head
The CSS is designed to make your template fit the screen size but has included code to restrict the templates width to a fixed px.
So if your desktop monitor is 1024 wide, the template will fill the screen but if your current template was designed with a fixed with of 980px, simply un-commenting 1 line of CSS code and adding your templates width is all that is needed from preventing it from filling the entire screen.
CSS tweeks will most likely be needed, I couldn't account for every template designers added HTML divs, tables and code. Most tweeks will involve removing "fixed widths" or "forced widths (!important)".
Johnnycopilot:
and anytime there's an SQL upload, I get a little out of my league.
The SQL patches include:
1.) Activation - This was included only to keep Zen-Cart stock code (tables) intact, once activated it removes the tables and replaces with divs
2.) Adds a show@minWidth option to the layout box controller in ADMIN so you can hide individual side boxes on mobile devices
3.) Adds configuration to offer different views for different devices
- mobile users can view full non-responsive version
- tablet users can view mobile version or full non-responsive version
- is an optional sql patch but some mobile or tablet visitors prefer to view the full site
The Responsive DIY Template Default CSS framework is also GOOGLE RECOGNIZED as a Mobile Site, **right now Google indexes sites and adds Mobile friendly - before the sites description **, GOOGLE has plans to exclude non Mobile friendly site from search results for mobile users to speed up GOOGLE results on mobile devices in near future.
While Google supports multiple mobile site configurations, creating separate mobile URLs greatly increases the amount of work required to maintain and update your site, and introduces possible sources of technical problems. You can often simplify things significantly by using responsive web design (RWD) and serving desktop and mobile on the same URL! Responsive web design is Google’s recommended configuration. Google Source
Everyone here will give you good advice (but different) advice on how to proceed.
I will advise this, if you plan to DIY:
-Create a sub-directory and upload the latest version of zen-cart to it.
-With a fresh copy of your current template package, merge the The Responsive DIY Template Default code
-Upload your newly coded template
-Install easyPopulate or a comparable plugin and upload your categories and products
-Activate your template and see what CSS tweeks will be needed
This will:
A) familiarize you with the files that need merging
B) give you an idea of what CSS tweeks will be needed
If you do that and get stuck, share a link and I'm positive that someone or myself will chime in and help!
From there you can start uploading your plugins, all of which you listed, I don't see any major appearance issues that will need CSS tweeks, I cannot say they are or will be compatible with the latest version of zen-cart though.
Hope this helps and is not overwhelming!