{"id":282,"date":"2009-08-31T10:34:04","date_gmt":"2009-08-31T14:34:04","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/?p=282"},"modified":"2009-09-06T11:55:59","modified_gmt":"2009-09-06T15:55:59","slug":"screenshots-dotnetnuke-and-magento-integration-experiment","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/2009\/08\/31\/screenshots-dotnetnuke-and-magento-integration-experiment\/","title":{"rendered":"Screenshots: DotNetNuke and Magento Integration Experiment"},"content":{"rendered":"

Over the last few months, I have been doing some initial architectural research regarding the integration of DotNetNuke with arbitrary external e-commerce systems. \u00a0Note that this research is highly embryonic, largely experimental, and highly likely to not reach any sort of production-ready fruition. \u00a0Its purpose is to inspire discussion, not demonstrate code. \u00a0Caveat lector<\/em>!<\/p>\n

As one of my goals is reasonable provider-independence (via adaptation<\/a>), this is not about realizing any particular vendor (despite the fact that I address one specific such vendor herein). \u00a0That said, I have been asked by several parties to share a bit more about where this stands;\u00a0it is with this in mind that I present an initial update.<\/p>\n

<\/p>\n

In selecting a set of third-party providers, it was of some importance to deal with an e-commerce system that was reasonably foreign to the .NET universe (within which DotNetNuke lives). \u00a0With this in mind, I selected the Magento framework<\/a> as an initial target for review. \u00a0In addition to being PHP-based, it boasts a reasonably sophisticated API, a beautiful interface, and solid overall architecture.<\/p>\n

Integration in conformance with my internal architectural specifications was largely straightforward. \u00a0However, Magento currently lacks any meaningful cart-API. \u00a0This means that, inter alia<\/em>, there is no API method by which an external consumer may retrieve a customer’s current basket (without resorting to screen-scrapes and other such horrors). \u00a0As such, it remains incomplete as an option for fully satisfactory externalization — though it is tantalizingly close. \u00a0It is my hope that this omission might be corrected in some subsequent Magento release, though I have no inside information about plans for future API development.<\/p>\n

I present the screenshots below — designed to closely emulate the Magento model store<\/a> — as a point of discussion about the potential future of DotNetNuke and e-commerce. \u00a0All components displayed therein are actual, working modules. \u00a0In my opinion, this is what e-commerce on the DotNetNuke framework should look like.<\/p>\n

Note that, in the area of e-commerce, I am largely constrained by contractual IPR constraints, and this significantly affects my ability to release the constituent modules. \u00a0However, as my architectural research continues, it is my hope that these data might be partitioned and released in an open-source manner (as is all of my other DotNetNuke-related work).<\/p>\n

As always, comments are appreciated.<\/p>\n

DotNetNuke and Magento Integration Screenshots<\/h4>\n\n\t\t