Revindex is not for the faint of heart and is designed for programmers wanting an e-commerce storefront. It’s the most complex module on the market when it comes to customization, but that comes at a cost of time and learning curve. If you want something fast and simple stay away from this module. If you want your storefront to look *exactly* the way you want it and are willing to learn some XSL – this is your best option.
Revindex has a pre-requisite module that must be installed first (the AkaxControlToolkit), otherwise it’s a one module install. Once you get it installed you create one page (the storefront admin) and drop the revindex module on it... that’s when it gets a bit confusing and you better hit the docs.
This module is *NOT* for the average DNN Admin... heck – I’m not an average admin and I’m not sure I have the knowledge to work this thing. The basics are covered through your normal suite of checkboxes and configuration tools… but if you *really* want to do anything with this module you will need to learn some XSL. All the advanced features of this module are only configurable via XSL Transforms which will relegate usage of this module to programmers primarily.
The documentation is found on their site in the form of a downloadable PDF but once you get past the initial setup it’s more of a broad overview on each section than a detailed explanation of the fields. There is also a video guide on setting up the site. Inline help is available within the module to explain a few fields.
So technically, with the XSL transform you can apparently do anything (maybe even fire an event that will shoot your e-commerce store around the globe in a time traveling rocketship), but “I ain’t got that knowledge”.
Customization to me is defined as the ability to change the look of the product as well as the general flow via portal based templates. Customizations should be preserved though every product upgrade and do not require editing anything outside of the portal root.
Scalability to me is the ability for the product to scale in two distinct areas. These are not reflections of performance or hardware required but simply the ability for the product to exist and operate in these two scenarios.
- Does it support multiple instance/store/portals?
- How will the user interface work with 10,000 products?