The coming post over the next two months will be included in a new series. The idea is to help the reader to understand how to enable a versatile and manageable portal. Each post will go through a specific use case or lifecycle group of events that a Content Driven Portal requires the development team to consider. The current planning is to deliver following subjects, each topic will be enclosed in a separate blog post.

1. Introduction – Introduction to the series of posts and what to expect at the end of the series
2. Components, part 1 – UCM, Site Studio and high level introduction to content templates
3. Components, part 2 – Page Templates and  Navigation model
4. Components, part 3 – Applied Customization Framework for Content Presenter Taskflows
5. Scenario 1 – Enable a Portal for runtime administration
6. Scenario 2 – Enable a Portal for Internationalization
7. Scenario 3 – Enable a Portal for Content Workflows

Background

This post series has been issued to help customers, partners and consultants to understand the concept of a WebCenter Portal project where the main focus or a majority of the portal has content interaction. Today the most portal installations Oracle WebCenter Portal is involved in have a vast majority of content based pages. Many of the Portal projects have or will run into challenges, to mitigate these challenges the portal and content lifecycle has to be well designed. The coming posts will address the main components that should be involved when creating such scenarios; it will also go into details on the process by describing three solution scenarios.
The aim with the scenarios is to give the reader a more hands on understanding of the concept of building and architecting a Content Driven Portal. The selected scenarios are selected based on the most common use cases that we have identified until today.