Let's discuss the upcoming integration of nopCommerce and Umbraco
- 112
- 1518
- 1/20/2016
- Russia
Dear colleagues!
It seems that we don't have many suggestions on minimum functions and integration variants. Then we will share our vision of this integration. Maybe it will be a good base for your further suggestions on functionality. Here it is:
We can divide the scheme into three individual parts:
1. nopCommerce. We are unlikely to change anything crucial in nopCommerce, the changes would be minimal and mainly related to API interaction. Maybe, absolutely nothing will be changed on nopCommerce core
2. https://github.com/SevenSpikes/nopCommerce/tree/Web-Api-3.70 Web API plugin. It'll be developed by our solution partners nop-templates. It'll be finished and release soon
3. Umbraco plugin. This is what we will develop.
Now let’s examine how these parts will work together.
nopCommerce and Umbraco will be installed as separate applications. We presume that the Umbraco plugin should contain new DataType(s) allowing a store owner to choose what elements an administrator might want to display on Umbraco pages. The primary DataTypes will be the following ones: product box(es), product page, category navigation block, shopping cart, checkout pages. On further development, this selection will be widened by adding new DataTypes. We will also add extension methods for getting the presentation module and rendering both with the embedded or customized templates situated in the structure of Umbraco. The Umbraco plugin will also contain a mapping table between "Umbraco members" and "nopCommerce customers". We'll keep them in synchronization.
What do you think?
It seems that we don't have many suggestions on minimum functions and integration variants. Then we will share our vision of this integration. Maybe it will be a good base for your further suggestions on functionality. Here it is:
We can divide the scheme into three individual parts:
1. nopCommerce. We are unlikely to change anything crucial in nopCommerce, the changes would be minimal and mainly related to API interaction. Maybe, absolutely nothing will be changed on nopCommerce core
2. https://github.com/SevenSpikes/nopCommerce/tree/Web-Api-3.70 Web API plugin. It'll be developed by our solution partners nop-templates. It'll be finished and release soon
3. Umbraco plugin. This is what we will develop.
Now let’s examine how these parts will work together.
nopCommerce and Umbraco will be installed as separate applications. We presume that the Umbraco plugin should contain new DataType(s) allowing a store owner to choose what elements an administrator might want to display on Umbraco pages. The primary DataTypes will be the following ones: product box(es), product page, category navigation block, shopping cart, checkout pages. On further development, this selection will be widened by adding new DataTypes. We will also add extension methods for getting the presentation module and rendering both with the embedded or customized templates situated in the structure of Umbraco. The Umbraco plugin will also contain a mapping table between "Umbraco members" and "nopCommerce customers". We'll keep them in synchronization.
What do you think?
- 25
- 293
- 4/11/2016
- United Kingdom
CMS integration is an area I am very keen to see improve, so I thought I would try and give some of my thoughts.
An area that is potentially missing from your overview diagram is the customer area. e.g. Customer's viewing their order history, modifying their saved addresses etc.
Essentially, from my point of view, for an integration with a CMS (be that Umbraco or Orchard) to be complete, all customer focused 'commerce' pages must be able to be built in the CMS. Another way of saying that could be that all pages except the home page and Topic pages really need to be considered, I think.
Also, as a store owner, I would not expect to have to create a page in the CMS system for each product/category etc. I would expect to create one page for each type e.g. one page for products (or maybe two, one for simple and one for grouped), one page for categories. The ability to create different layouts for different categories/products would be a nice to have, but should not a be necessity.
Hopefully that all makes sense, and please forgive me it they are obvious requirements that have already been thought of.
Phil
An area that is potentially missing from your overview diagram is the customer area. e.g. Customer's viewing their order history, modifying their saved addresses etc.
Essentially, from my point of view, for an integration with a CMS (be that Umbraco or Orchard) to be complete, all customer focused 'commerce' pages must be able to be built in the CMS. Another way of saying that could be that all pages except the home page and Topic pages really need to be considered, I think.
Also, as a store owner, I would not expect to have to create a page in the CMS system for each product/category etc. I would expect to create one page for each type e.g. one page for products (or maybe two, one for simple and one for grouped), one page for categories. The ability to create different layouts for different categories/products would be a nice to have, but should not a be necessity.
Hopefully that all makes sense, and please forgive me it they are obvious requirements that have already been thought of.
Phil
- 112
- 1518
- 1/20/2016
- Russia
phil.kendall.dynamics.consultants wrote:
Phil, thanks for feedback and suggestion
CMS integration is an area I am very keen to see improve, so I thought I would try and give some of my thoughts.
An area that is potentially missing from your overview diagram is the customer area. e.g. Customer's viewing their order history, modifying their saved addresses etc.
Essentially, from my point of view, for an integration with a CMS (be that Umbraco or Orchard) to be complete, all customer focused 'commerce' pages must be able to be built in the CMS. Another way of saying that could be that all pages except the home page and Topic pages really need to be considered, I think.
Also, as a store owner, I would not expect to have to create a page in the CMS system for each product/category etc. I would expect to create one page for each type e.g. one page for products (or maybe two, one for simple and one for grouped), one page for categories. The ability to create different layouts for different categories/products would be a nice to have, but should not a be necessity.
Hopefully that all makes sense, and please forgive me it they are obvious requirements that have already been thought of.
Phil
An area that is potentially missing from your overview diagram is the customer area. e.g. Customer's viewing their order history, modifying their saved addresses etc.
Essentially, from my point of view, for an integration with a CMS (be that Umbraco or Orchard) to be complete, all customer focused 'commerce' pages must be able to be built in the CMS. Another way of saying that could be that all pages except the home page and Topic pages really need to be considered, I think.
Also, as a store owner, I would not expect to have to create a page in the CMS system for each product/category etc. I would expect to create one page for each type e.g. one page for products (or maybe two, one for simple and one for grouped), one page for categories. The ability to create different layouts for different categories/products would be a nice to have, but should not a be necessity.
Hopefully that all makes sense, and please forgive me it they are obvious requirements that have already been thought of.
Phil
Phil, thanks for feedback and suggestion
- 6
- 30
- 2/27/2011
- United States
How do you envision this plugin working from a marketing person's standpoint?
1) Will the business user login to NopCommerce or Umbraco (or both) for editing content?
2) Will they still edit products and categories within NOP, or will they create category pages manually from within Umbraco and map the page to a category in NOP?
I think that the plugin should continue to enforce the rules that are specified in NOP
1) Product Pricing, Tiers, attributes, specs, etc
2) Multi Store rules - the plugin should make sure a product doesn't end up on the wrong site
3) Customer roles and security
4) Product / Category Mappings
1) Will the business user login to NopCommerce or Umbraco (or both) for editing content?
2) Will they still edit products and categories within NOP, or will they create category pages manually from within Umbraco and map the page to a category in NOP?
I think that the plugin should continue to enforce the rules that are specified in NOP
1) Product Pricing, Tiers, attributes, specs, etc
2) Multi Store rules - the plugin should make sure a product doesn't end up on the wrong site
3) Customer roles and security
4) Product / Category Mappings
Bronze Solution Partner
Certified Developer
- 153
- 1309
- 1/15/2013
- Poland
Hello guys,
1) It will be good if we have login and flayout shopping cart views in your Umbraco module http://clip2net.com/s/3wZXngG.
2) Also it will be good if we have possibility to connect umbraco page with nop products. I suppose it will be done by using DataTypes: product box(es) or/and product pages.
1) It will be good if we have login and flayout shopping cart views in your Umbraco module http://clip2net.com/s/3wZXngG.
2) Also it will be good if we have possibility to connect umbraco page with nop products. I suppose it will be done by using DataTypes: product box(es) or/and product pages.
Bronze Solution Partner
Certified Developer
- 153
- 1309
- 1/15/2013
- Poland
By the way I suppose we don't need to map all nop customers with Umbraco members. Actually this step is nice to have but I suppose it's not required. Usually we need Umbraco just for 3-5 content editors and nop for 1000 customers. So we can use nop pages to login/checkout and umbraco for the content.
I don't remember exactly but I suppose we can implement the following step "1) It will be good if we have login and flayout shopping cart views in your Umbraco module http://clip2net.com/s/3wZXngG." without mapping users by using authorization cookies.
I don't remember exactly but I suppose we can implement the following step "1) It will be good if we have login and flayout shopping cart views in your Umbraco module http://clip2net.com/s/3wZXngG." without mapping users by using authorization cookies.