what is liferay and why do we need it
play

What is Liferay and why do we need it? Vy Bui Todays agenda - PowerPoint PPT Presentation

Apr 07, 2024 •205 likes •668 views

What is Liferay and why do we need it? Vy Bui Todays agenda Introduction What is Liferay? Why should developers care about Liferay? What is Liferay as a CMS? How to use some cool features to achieve the fullest results? Q&A

  1. What is Liferay and why do we need it? Vy Bui

  2. Today’s agenda Introduction What is Liferay? Why should developers care about Liferay? What is Liferay as a CMS? How to use some cool features to achieve the fullest results? Q&A

  4. Background Liferay developer Code Engine Studio Engineering intern December 2015 - Now Code Engine Studio Training: 6.2 and DXP November 2014 - May 2015 Graduated and became a software engineer Code Engine Studio June 2015

  5. What is Liferay Portal?

  6. Leveraging a Suite of Frameworks and Libraries

  7. Leveraging a Suite of Frameworks and Libraries

  8. Creating your own applications and extending existing ones Common ways of expanding or customizing Liferay Portal’s features: ● Developing a new fully-developed web application (eg: Portlets). ● Customizing an existing web application or feature. ● Creating a new web service (external system, an IoT device ...) ● Developing a mobile app (Liferay as back-end or Liferay Screens ). ● Creating a custom theme to adapt to visual needs of your project

  9. Why developers should care about Liferay DXP?

  10. What are fundamentals about Liferay that developers should know about? It’s Open Source and puts a strong emphasis on following standards . ● Ticketing system -> JIRA - LPS . ● GitHub -> liferay-portal. ● Forums.

  11. Open Source but based on Standards In addition to being Open Source, Liferay is also heavily based on standards . ● Portlets 1.0 (JSR-168) and Portlets 2.0 (JSR-286) and upcoming Portlets 3.0 ● Java Content Repository (JSR-170) ● JSF (JSR-127, JSR-314, JSR-344) ● WebDAV

  12. Technologies that Liferay is using ● For demanding and critical enterprise environments. ● Widely adopted and have a mature community. ● Easy as possible to contribute back. ● Should be possible to use only the piece of the project.

  13. Front-end technologies CSS: ● Bootstrap ● SaSS Javascript libraries: ● jQuery ● Angular 1 & 2 ● React ● Metal.js (Liferay developed)

  14. Native apps ● Liferay as back-end

  15. Back-end technologies With Java EE and OSGi at the bottom of the stack. The goals are: ● Up to date ● Easy-to-use ● Stable platform

  16. Modular Architecture

  17. Modules ● A module is the single unit of distribution and deployment in a modular architecture. ● OSGi defines how modules can depend on each other and communicate An OSGi module is just a typical JAR ● file.

  18. Real Life Benefits of Modular Development ● Distinct functionality. ● Dependencies. ● Encapsulation. ● Reusability.

  19. Modular Development Example

  20. Modular’s Benefits ● The app depends on modules, that are easy to develop , test , and maintain . ● The modules can be reused in different applications.

  21. Liferay versioning

  22. DXP vs Liferay 7

  23. DXP Exclusive Features ● Clustering ● Audience Targeting 2.0 (with detailed later) ● Support for Enterprise Databases ● Elasticsearch

  24. What makes Liferay EE different? ● It's not meant for small businesses. ● It’s not cheap. BUT ● It is rich in functionality. ● The community is very helpful and it is flexible and customizable, being useful for a wide range of necessities. Plus, its code is well written.

  25. Enterprise Edition Benefits Enterprise-Ready Professional Management Software Tools Support Our subscription includes Liferay Connected Services Software updates, security access to every current version helps you diagnose slow patches and a 24-hour of Liferay page load times support team that will respond quickly to your call.

  26. Magic Quadrant for DXP Liferay Named a Leader in 2018 Gartner Magic Quadrant for Digital Experience Platforms

  27. Awesome features of Liferay DXP

  28. Liferay as a CMS

  29. CMS (Content management System) ● ECM (Enterprise Content Management) ● WCM (Web Content Management)

  30. Popular CMS

  31. Audience Targeting

  32. Personalized Assets using Audience Targeting User segment Campaigns 1 Campaigns 2

  33. Audience Targeting materials ● User segments: are different groups of users that are served different content ● A campaign: represents an effort to expose a certain user segment to a certain set of assets within a specific period of time ● Rules: enable Audience Targeting administrators to define how users are classified into the user segments they create.

  34. Real Life Example A company name “Code Engine Studio” is hiring Java and PHP developers to join their awesome team. Each Java/PHP developer will get a position as well as their salary related to their experience. Intermediate - 3+ years experience - 15 million - 20 million Senior - 5+ years experience - 20 million - 30 million Tech Lead - 8+ years experience - 25 million - 35 million

  35. User segments and Rules User Segments: Java Developers. ● PHP Developers. ● Rules: User with more than 3 year experience is called Intermediate ● User with more than 5 year experience is called Senior ● User with more than 8 year experience is called Tech Lead ●

  36. Campaigns strategy ● Intermediate users will get 15 million - 20 million in their salary. ● Senior users will get 20 million - 30 million in their salary. ● Tech Lead users will get 25 million - 35 million in their salary.

  37. Let’s take a tour

  38. Interested?

  39. WE ARE HIRING

  40. PHP Developer Java Developer Intermediate - 3+ years experience - 15mill - 20mill Senior - 5+ years experience - 20mill - 30 mill Tech Lead - 8+ years experience - 25mill - 35mill

  41. Developer Intern Quality Control Intern Digital Marketing Intern

  42. SEND YOUR ENGLISH CV TO: career@codeenginestudio.com

  43. Conclusion

  44. Questions & Answers

  45. Thank you!!!

More recommend