nopCommerce 3.30 roadmap and estimated release date. Let's discuss.

create 3 css files style, style.rtl and skin

in skin put only properties that can be changed with out changing the layout
basically colors, background colors, images and fonts

Hi folks,

By the way, have a look at this work item ("Make the default theme responsive"). What do you think about it? Should it be done out of the box? If yes, should we maintain both mobile versions (a new responsive and the current jQuery mobile)? Or drop should we drop the current jQuery mobile support in order to keep the solution more simple (no code duplicates) and have only responsive one?

Hi folks,

By the way, have a look at this work item ("Make the default theme responsive"). What do you think about it? Should it be done out of the box? If yes, should we maintain both mobile versions (a new responsive and the current jQuery mobile)? Or drop should we drop the current jQuery mobile support in order to keep the solution more simple (no code duplicates) and have only responsive one?

jQuery Mobile or Responsive theme is not a replacement of each other. Both of them has got their place. I would prefer to make default theme responsive, but at the same time maintain jQuery mobile version due to following reason:

- It generates optimized code, which is better and lesser for mobile sites, enables quick loading on slower mobile connection
- Optimized for touch using UI similar to native app
- Gives more freedom to someone looking to create special mobile site, especially sites specifically targeted to mobile / tabs
- Someone building mobile app for his nopCommerce site can use jQuery UI to build the app quickly

However, I would like other opinions of other community members on this as well. And more importantly the one who are using jQuery mobile themes extensively!

One of the task I see in work item is about Migrate from Telerik ASP.NET MVC Extensions to any other UI framework.

I am following a task very closely here https://nopcommerce.codeplex.com/workitem/10860 but not sure which framework nop team is planning to use?

Can we have some idea?

I also agree fully with the need to make the one page checkout a REAL one page checkout. This is so much more important than any other detailed campaign feature or what have you. It's the ESSENCE of any ecommerce site.

I also agree fully with the need to make the one page checkout a REAL one page checkout. This is so much more important than any other detailed campaign feature or what have you. It's the ESSENCE of any ecommerce site.

Agree X 3. I have a lot of clients complain about current checkout page, and those people have some idea what they are talking about. Its time to make the checkout page more simple.