QUESTION

Portal technology, according to specs like JSR 168 and 286, is difficult and needs a lot of overhead to develop web applications. The arguments to chose the technology often include the words integration, SOA, personalization, federation and scalability. But are these reasons strong enough to overcome the development hurdles? Or should we just accept that serious portal frameworks from IBM / BEA / Oracle are just meant for the big Enterprises who have a strategy that will allow them to invest millions each year in portal development?

ANSWER

Yet the MOST important question when it comes to CMSs is: “What IF the system we utilize is stomped in?” This is the most tricky question out there because migration and data mining efforts to move 1000s of pages of content can quickly go into the 100ks and lead to a system the company will stick to for several years, improvising the living hell out of the thing, making it vulnerable and totally exposed. Same applies for intranet and knowledge management solutions.

But to go back to your question… Yes, it most definitly is. Not only is the rights management of the publishers worth it. But also considder the fact that creating a new page means a bigger hassle in standard programming. Furthermore, you face issues like SEO, accessibility, etc. etc. that you have to review on every single page while a CMS takes care of that for you through the framework.If you need more help please feel free to call me. I have pointed out my international phone numbers in the bottom. 

Related posts:

1. Poor search functionality in Enterprise Content Management make the systems obsolete
2. Knowledge management – increasing the value of your business
3. BOOK MONDAY: Learning marketing from the porn industry