After weeks of "it is just around the corner" compromises, i finally managed to create time for myself to reread the book from the start.. last time i had to stop myself half way.. coz of various reasons which i conveniently choose not to remind myself again.. now on to the book, an excellent introduction by the authors..

Why do we need such a piece of software --> every orgnaization creates 100s if not thousands of sites for themselves for marketing, internal employee and policy mgmt and what not.. going through the same grind of creating html/script based pages, accessing db through or by passing a middle tier.. designing the db etc., are definitively non productive. As the grind is a well laid out sequence of steps and not any magic, there is bound to be an automatic page creator and content manager sw and you can imagine Sharepoint to be one such.

Now a non technical person in your organization (read it as your HR Director/manager or CFO or accounts manager or your office security) can create pages and content that anyway you will not use or by all means will not be useful!!

So is it death knell for the web site developer? Not quite.. just like BPM is and turned out to be (u can create processes linking pieces of services but these services will have to be developed and made by linkable by us) here u can create pages and basic contents but you will neverthe less need our skills to customize the pages - which most often would be required.