Liferay Portal CE 7.0 uses Bootstrap 3’s CSS rule syntax.The new syntax lets developers leverage Bootstrap 3 features and improvements.
Even if you’ve already executed the Upgrade task, it’s best to learn all the steps and make sure they’re applied to your theme. If you’re developing your theme in an environment other than the Plugins SDK, skip this section.
A theme’s Liferay version must be updated to The theme upgrade process involves conforming to these changes.
Since Velocity templates have been deprecated, you should convert your Velocity theme templates to Free Marker.
If you’re using the Liferay JS Theme Toolkit, the For all the theme’s templates, it suggests replacement code for deprecated code.
The first one to update is the The navigation template is updated.
That covers most, if not all, of the required theme template changes.
Next, you’ll learn how to update various theme templates to Liferay Portal CE 7.0.
If you didn’t modify any theme templates, you can skip these sections.
The easiest option is to use the Liferay JS Theme Toolkit’s Gulp upgrade steps, in case you want to run them manually.
A Liferay Portal 6.2 theme can be upgraded to Liferay Portal CE 7.0, regardless of its project environment (Liferay JS Theme Toolkit, Plugins SDK, Maven, etc.).
In this section, you’ll update your theme’s CSS to leverage the styling improvements. Although Sass was available in Liferay Portal 6.2, only Sass partial files followed the Sass naming convention (using file suffix Refer to the Theme Reference Guide for a complete list of expected theme CSS files.