About this article
Written by: | Imar Spaanjaars |
Posted: | 6/14/2010 9:19 AM |
Last updated: | 6/17/2010 8:22 AM |
Page views: | 9818 |
Rate this article
About the author
Imar Spaanjaars is the owner of De Vier Koeden, a company specializing in consultancy and development on the Microsoft .NET platform and Dynamicweb.
Interested in custom development or consultancy on Dynamicweb or .NET? Then contact De Vier Koeden through the Contact page.
If you want to find out more about Imar Spaanjaars, check out his About page on this web site or check out his personal website.
Follow Imar on Twitter if you want to be notified of new articles in this Dynamicweb series.
Introducing an Article Series on Dynamicweb
Some of you may know me from role as Technical Director of Dynamicweb Netherlands, the Dutch branch of the popular Danish Content Management and eCommerce platform Dynamicweb. If that's the case for you, you're probably also familiar with the Dynamicweb CMS and Dynamicweb eCommerce products. (If you're not familiar with Dynamicweb, go check it out at the International Dynamicweb web site now. Dynamicweb is an excellent, very user friendly and highly customizable and extensible CMS and eCommerce platform, with many great features to rapidly build complex web sites and eCommerce stores). If you are familiar with Dynamicweb, it means you're probably also aware that it's not always easy to find the right help files, API documentation and walkthroughs to guide you through building a Dynamicweb site, with or without extensibility.
With the recent release of Dynamicweb 7.1, a lot of time and effort has been invested in better documentation. Samples include the documentation on Designs and Layouts and the standard release notes and the technical release notes on Dynamicweb 7.1. Additionally, the documentation team is working hard to document both the CMS as the eCommerce API.
Clearly, these documentation efforts should lead to easier and quicker implementations, better time to market and final results, and happier developers and customers in general.
To help the documentation team spread the word about Dynamicweb, the new 7.1 release and the many cool features in the extensibility API, I've decided to start a blog series about Dynamicweb, showing you many of its existing and new capabilities.
Over the next couple of weeks or even months, I'll be posting articles on a a variety of subjects. I'll be focusing mostly on development related topics rather than day to day content management tasks, although I will touch on those areas once in a while as well when discussing the new features of Dynamicweb 7.1.
Topics that I currently have listed:
- Programmatically hooking into page rendering with an extender to change the appearance of a page
- Hooking into paragraph rendering using the new paragraph notifications to change the appearance of a page
- Hooking into many of the new Cart notifications to change the way order steps and the cart behaves
- Hooking into the various extender that are available to change the appearance of products, product lists, orders, order lines and more
- Expanding the navigation of your site by dynamically extending the Menu using a MenuProvider
- A series of articles on building custom modules
- Building your own SalesDiscountProvider to support discount types not supported out of the box
- Building your own Admin interfaces using the new Ribbon layout controls
- Editing custom extranet fields, for example by a logged in Extranet user
- Easier configuration for the Search module
- Configuring custom 404s specific to a language layer
- Extending the News module using new extensibility options
- Serving customized scaled images using the auto image scaler
- More.....
As always, I am open for suggestions and ideas. If you have a topic you want me to add to this list: be sure to let me know.
I'll be posting the first article in a few days. Hopefully, I'll be able to post at least a new article each week after that. Stay tuned. Or better yet, follow me on Twitter where I'll be announcing new articles in this series.