Web 2.0 user interface features
Within portal, the Web 2.0 features are implemented as follows:
- Client side portlet programming model: Use the client side programming model for the portlets. We can do everything with the client side programming model we can do with the server side portlet programming model. Additionally, the client side programming model has the following advantages:
- Improved user experience by faster responses and performance, as many interactions are processed on the client side rather than on the server.
- User customization of user profile, preferences, and changes to the portlet state are done locally, and therefore with a faster response time. A fragment containing the customization is later sent to the server and saved.
- The user experience is consistent between both client side aggregation and server side aggregation.
- Live text: Use live text. Live text provides elements embedded in portal pages that become active in the browser and are enhanced with additional functionality by JavaScript libraries. For example, if you include portal user IDs in the portlet output and mark them as live text, users can click these IDs in the browser and see a person info card or a menu that allows them to send a mail to the person. Live text has the following advantages:
- Live text allows easier click to action.
- We can adopt new portal content within the company more easily, as it is now easier to handle portal tags. For example, we can write tags and make them available centrally, and UI developers can reuse these tags for in their portlets for various purposes.
- Content editors can add meaningful live text elements to portlets without requiring portlet development knowledge.
- We can embed content from other sources, for example, from a HTTP or .NET server.
- REST services:
- Portal offers many REST services, such as Layout model, Portlet model, Content model, Navigation model, Wire model, and User profile.
- By the use of REST services we can write our own advanced Web application and build it with REST (Representational State Transfer) services that provide the XML request information.
- REST services allow us to access portal models remotely for both read and write access. The Navigation model allows read access only; it is updated by changes made to the content model.
- Controller SPI: The Controller SPI is a public portal interface. It is not directly related to the Web 2.0 type of user experience, but it allows us to perform certain administrative tasks more easily.
See
Parent Develop portlets