Hi all, a little late to the game since we've been at it for a few years. We specialize in experience-based gifts to consumers and corporate clients. Happy to answer questions, thanks.
https://enjoywishlist.com
enjoywishlist.com - experience gifting
- 212
- 1458
- 7/18/2010
- Russia
cshen wrote:
Hi.
..all of the pages of the categories on the site looks like a landing page .. very nice. How did you do this ... plugin/template or just ..? Could provide some details? I want the same, could you give piece of advice? .. anyway good, exciting job.
Best regards.
... Happy to answer questions, thanks.
https://enjoywishlist.com
https://enjoywishlist.com
Hi.
..all of the pages of the categories on the site looks like a landing page .. very nice. How did you do this ... plugin/template or just ..? Could provide some details? I want the same, could you give piece of advice? .. anyway good, exciting job.
Best regards.
- 3
- 35
- 12/11/2012
- United States
Hi there,
We have a completely separate frontend project built on top of the nopCommerce backend. We basically created a new Web Application Project (Web API) and referenced Nop.Web.Framework, Nop.Services, Nop.Data, etc. The Nop.Web project is effectively unused, and even though it's a nice frontend, we needed a separate frontend project to give us ultimate flexibility. The frontend architecture is comprised of AngularJS (1.x) with WebAPI controllers serving as the interface to the backend.
In the very beginning I investigated an architecture where nopCommerce was extended with our needs through the plugin architecture. However, there was a combination of it being too limiting and/or having to make overly complicated solutions to have things work properly under the plugin model. I found it far easier to work directly with the source code and keeping things as separate as possible through partial class extensions and class inheritance. Hope this helps, thanks!
We have a completely separate frontend project built on top of the nopCommerce backend. We basically created a new Web Application Project (Web API) and referenced Nop.Web.Framework, Nop.Services, Nop.Data, etc. The Nop.Web project is effectively unused, and even though it's a nice frontend, we needed a separate frontend project to give us ultimate flexibility. The frontend architecture is comprised of AngularJS (1.x) with WebAPI controllers serving as the interface to the backend.
In the very beginning I investigated an architecture where nopCommerce was extended with our needs through the plugin architecture. However, there was a combination of it being too limiting and/or having to make overly complicated solutions to have things work properly under the plugin model. I found it far easier to work directly with the source code and keeping things as separate as possible through partial class extensions and class inheritance. Hope this helps, thanks!