Message Boards

How to be "future-proof" when building themes?

Marius Heinzmann, modified 4 Years ago.

How to be "future-proof" when building themes?

New Member Post: 1 Join Date: 12/18/19 Recent Posts
Dear fellow Liferay devs,we are currently in the process of migrating our old dynamic-theme from 6.2 -> 7.1 and in this process we developed a couple of questions:
1. What is the recommended way to create a theme build on top of liferay's classic theme in 7.1 so that we can easily migrate the theme to newer versions, i.e. 7.2, 7.3 and the upcoming dynamic css that was presented on the DevCon?
2. We have tried Liferay's Theme Generator and it's npm/gulp-based build and the maven/gradle-based theme builds from the sample projects and created via blade-cli. Unfortunately none of the toolchains seems to be able to generate a complete and consistent set of SCSS files that can be compiled with any SCSS-compiler.  For our dynamic-css we need to be able to export such a tree and compile it for each portal-instance/group-scope/page as needed. 
Do any of you know if there is a way to generate a complete and consistent SCSS-tree?

3. We are looking forward to the upcoming dynamic-css implementation from Liferay themselves and if any Liferay Devs are reading this, can you guys tell us about your general approach to implement this? Maybe we can adjust ours to be closer to yours so that when we migrate to Liferay 7.3 or 7.4 we can switch to the provided one without too much hassle.
We are looking forward to getting other devs' feedback and opinion about the theming topic. emoticon
Kind regards
​​​​​​​ Marius H.