RE: How to extend the Classic Theme for Liferay DXP 7.2?

thumbnail
Ben Kinsey, modified 6 Years ago. New Member Posts: 9 Join Date: 2/17/19 Recent Posts
When I ran `yo liferay-theme` and then `gulp deploy`, the resulting theme looked quite different (and worse) than the default classic theme on my Liferay DXP 7.2 site. I assume this is because it is extending  liferay-theme-styled instead of the full Classic theme. See https://portal.liferay.dev/docs/7-0/tutorials/-/knowledge_base/t/themes-generatorI tried running `gulp kickstart` and searched for `classic` but got  `Warning: found 1 packages (matching criteria) not targeting 7.2 version`. I saw somebody tried to get it working by copying a bunch of files into the src of the generated theme, but that seems like a hard path. Is there any easier idea I'm missing?
Lee Jordan, modified 5 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
I feel the same pain, 7.0 themes were complete when using styled. I think there is a strong basis for a feature request to have the generator produce an "_ultrastyled" theme in the yo process. Code named Com Truise waaaay styled, sunglasses, a limited edition chrome and black Sony Walkman with autoreverse, weatherband radio and extra bass ... the whole shebang.

Ultrastyled imports ...
https://portal.liferay.dev/docs/7-2/frameworks/-/knowledge_base/f/clay-css-and-themes
​​​​​​​https://portal.liferay.dev/docs/7-2/frameworks/-/knowledge_base/f/customizing-atlas-and-clay-base-themes


Discussion ...
https://github.com/liferay/liferay-js-themes-toolkit/issues/395
thumbnail
Andrew Jardine, modified 5 Years ago. Liferay Legend Posts: 2416 Join Date: 12/22/10 Recent Posts
LOL -- best message post I have read all day. +1 to you Lee emoticon


Theme Development has always been a bit of a nightmare, imho, but honestly, it has been a pain in the ass for pretty much every platform I have ever worked with. I haven't found the 7.1 themes all that bad to work with actually and I have done several themes based off of HTML templates I have bought online. I haven't done much with the 7.2 stuff though. To date all I have done is made sure that the theme I have purchased, or the front end devs I have worked with, had adhered to using Bootstrap the way it was meant to be used. That seems to be about 75% of the battle since really, Clay is just overriding bootstrap right?

All that said, I like tools and automation too. I think it would be great to even have a way to feed themes that are done into the tool. So if you have a _ultrasexy theme you want to make available you can load it from the tool and have it listed as one of the options moving forward. By the same token though -- I'm not sure what that means for support or how Liferay could possibly account for all the different ways (sometimes HORRIBLE ways) people create themes.