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

Instead, I would vote to strip out everything that is not core functionality from the main solution and move it to plugins. Implementations that need them could still use them, but the main solution would be more lightweight for those that don't need them.

Instead, I would vote to strip out everything that is not core functionality from the main solution and move it to plugins. Implementations that need them could still use them, but the main solution would be more lightweight for those that don't need them.

Couldn't agree more, I don't use forums, news, want to disable wishlist globally. They all seem like things that should be plugins. I'm seeing a trend towards being everything to everyone, and a lot of wheel reinventing. For example, newsletters: no host will ever let you blast out newsletters for long, this should totally be left up to plugin integration to existing systems like mailchimp/constant contact/sendgrid.

Instead, I would vote to strip out everything that is not core functionality from the main solution and move it to plugins. Implementations that need them could still use them, but the main solution would be more lightweight for those that don't need them.

Couldn't agree more, I don't use forums, news, want to disable wishlist globally. They all seem like things that should be plugins. I'm seeing a trend towards being everything to everyone, and a lot of wheel reinventing. For example, newsletters: no host will ever let you blast out newsletters for long, this should totally be left up to plugin integration to existing systems like mailchimp/constant contact/sendgrid.
There is a work item for that. You can vote

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?

Can anyone comment on the ability to assign SKU’s to simple product attributes. Right now, we are limited with how we can customize product attributes.

I would be looking for a field where you could enter a SKU number.

For less maintenance, my suggestion is to separate the css file to three
main css file
LTR css file
RTL css file

the last two will include all the RTL LTR properties
the first one will have all the common properties