Jorge Ferrer 5 Years Ago Great article! Please sign in to reply. Reply as... Cancel Louis-Guillaume Durand Jorge Ferrer 5 Years Ago Thank you very much Jorge! Please sign in to reply. Reply as... Cancel
Louis-Guillaume Durand Jorge Ferrer 5 Years Ago Thank you very much Jorge! Please sign in to reply. Reply as... Cancel
Dimitris Menounos 5 Years Ago "Even if — for some reason — you still want to use Bootstrap components, you need to customize Clay components because Liferay is using them and consequently your users will experience them." That sounds horrible only to me? Frankly I am still using 6 but, given my experience, I would want to build my themes on top of pure Bootstrap and have nothing Liferay in it. Now I would't mind if Liferay code existed but affected only Liferay components. That is one of the reasons I don't like the 7 redesign where the control panel integrates with the sites. Actually I hate pretty much all client side Liferay tech :) I think that for 7 I will have to learn how to use it in headless style because it is still an great CMS. Please sign in to reply. Reply as... Cancel Louis-Guillaume Durand Dimitris Menounos 5 Years Ago Thank you for your feedback :) I totally understand your concerns. If you want to build themes on top of pure Bootstrap, you could, but you will experience some inconsistency in your site. For example, default alerts from Liferay are Clay components and not Bootstrap components. So if you only customize on top of Bootstrap, you will have slightly different styles with alerts. So Clay customization is highly recommended in this perspective, but not mandatory. You can checkout this examples : https://github.com/lgdd/liferay-startbootstrap. It’s simply an integration of Bootstrap themes without customizing Clay components. I’d be glad to have your thoughts about this. And if you want to use Liferay in an headless way, you might be interested in this Liferay project : https://github.com/liferay/com-liferay-apio-architect. Please sign in to reply. Reply as... Cancel Dimitris Menounos Louis-Guillaume Durand 5 Years Ago Thank you for the links! Please sign in to reply. Reply as... Cancel
Louis-Guillaume Durand Dimitris Menounos 5 Years Ago Thank you for your feedback :) I totally understand your concerns. If you want to build themes on top of pure Bootstrap, you could, but you will experience some inconsistency in your site. For example, default alerts from Liferay are Clay components and not Bootstrap components. So if you only customize on top of Bootstrap, you will have slightly different styles with alerts. So Clay customization is highly recommended in this perspective, but not mandatory. You can checkout this examples : https://github.com/lgdd/liferay-startbootstrap. It’s simply an integration of Bootstrap themes without customizing Clay components. I’d be glad to have your thoughts about this. And if you want to use Liferay in an headless way, you might be interested in this Liferay project : https://github.com/liferay/com-liferay-apio-architect. Please sign in to reply. Reply as... Cancel Dimitris Menounos Louis-Guillaume Durand 5 Years Ago Thank you for the links! Please sign in to reply. Reply as... Cancel
Dimitris Menounos Louis-Guillaume Durand 5 Years Ago Thank you for the links! Please sign in to reply. Reply as... Cancel
Fernando Fernandez 5 Years Ago I was really enjoying the article but I had to pause reading when I reached the error message example... :-( Bootstrap: error message = 3 lines / 88 chars Clay: error message = 8 lines / 326 chars The Clay example adds no functionality. It's still an error message. Nothing more. Why should the developer have to write so much more code? We need simplification, not complexification. I'll continue reading now. Please sign in to reply. Reply as... Cancel Louis-Guillaume Durand Fernando Fernandez 5 Years Ago - Edited Those HTML snippets represent the result in the DOM, but in practice, the developer won't have to write this lines in pure HTML. Here's examples of what it looks like for a developer depending on the front technology he chose : JSP: https://dev.liferay.com/fr/develop/tutorials/-/knowledge_base/7-1/clay-alerts Soy & Web components: https://clayui.com/docs/components/alerts.html I hope this make it clearer on the apparent complexity Clay is adding. Thanks for your feedback! Please sign in to reply. Reply as... Cancel Fernando Fernandez Louis-Guillaume Durand 5 Years Ago Thank you for the clarification, Louis! Please sign in to reply. Reply as... Cancel
Louis-Guillaume Durand Fernando Fernandez 5 Years Ago - Edited Those HTML snippets represent the result in the DOM, but in practice, the developer won't have to write this lines in pure HTML. Here's examples of what it looks like for a developer depending on the front technology he chose : JSP: https://dev.liferay.com/fr/develop/tutorials/-/knowledge_base/7-1/clay-alerts Soy & Web components: https://clayui.com/docs/components/alerts.html I hope this make it clearer on the apparent complexity Clay is adding. Thanks for your feedback! Please sign in to reply. Reply as... Cancel Fernando Fernandez Louis-Guillaume Durand 5 Years Ago Thank you for the clarification, Louis! Please sign in to reply. Reply as... Cancel
Fernando Fernandez Louis-Guillaume Durand 5 Years Ago Thank you for the clarification, Louis! Please sign in to reply. Reply as... Cancel
Marcos Castro 5 Years Ago Really awesome article! thanks Louis Please sign in to reply. Reply as... Cancel Louis-Guillaume Durand Marcos Castro 5 Years Ago Thank you very much Marcos :) Please sign in to reply. Reply as... Cancel
Louis-Guillaume Durand Marcos Castro 5 Years Ago Thank you very much Marcos :) Please sign in to reply. Reply as... Cancel