Myth – Websphere portal is not compatible with latest front end frameworks like bootstrap, foundation, jQuery Mobile, etc.
Fact – Websphere portal is completely compatible with all the latest front end frameworks and there should be no reason why one should be concerned about including the front end framework in the portal. Basically, the front end frameworks include a css file, which is responsive, follows a grid system, provides styling for UI elements and takes care of accessibility and cross browser compatibility to an extent. The html in the portal will only be referencing the class names that are defined in the framework’s css file, enhancing the user experience and this css file is included in the portal theme.
Myth – Websphere portal is not compatible with jQuery and associated plugins.
Myth – To make a change in the css file, this should be done in the portal theme, deployed to QA, tested and then served to production.
Best Practices a Front End Developer needs to follow while working with portal theme.
2. Move the css to a web server or IHS and reference this css in the theme from the web server so that, any change to the css does not really require a theme deployment. All it needs is front end developer access to the web server. Same goes with library javscripts (jQuery, plugins, etc) and images. To swap a logo, it can be done in the images folder on a web server, tested in QA, pushed to staging, verified and finally served in the production.
4. If you are parsing large json data and integrating that with the html in the jsp of the portlet, then just throw up the json on the portlet. Make use of handlebar or mustache templates to parse the json and inject that json data directly in the html. This helps in separating the html from the data and also any changes to the html can be done without altering backend logic.