When You Need Both a Public Website and a Portal
Many organizations run a public website and portal on one legacy DXP. When to separate them, three ways to do it, and what stays shared.
Many organizations run a public website and portal on one legacy DXP. When to separate them, three ways to do it, and what stays shared.
We implement both Contentful and Liferay. Here is the rule we use to decide which one fits, the three conditions that override it, and the cases where we recommend neither.
Liferay Data Platform unifies customer and account data inside Liferay DXP. Here’s a first look at what it does, what’s live today, and what’s coming next.
Liferay released Liferay AI Hub- a low-code layer for building AI agents directly inside Liferay DXP. This post walks through what it actually does today, how it compares to the hype, and where it’s still maturing.
Sometimes you want to add JavaScript that doesn’t really make sense as a React App, but you want the guardrails and performance that a modern TypeScript and Webpack build process offers. We’re going to go through the process of creating a blank TypeScript global client extension from beginning to end.
Liferay DXP empowers enterprises to embrace composable architecture with modern tooling, decoupled frontends, low-code data models, and seamless system integration. Whether you’re modernizing legacy apps or building new digital experiences, Liferay provides the flexibility, scalability, and developer-friendly stack to get there faster as a composable digital experience platform.
Now that there are ARMv8 native versions of MySQL and JAVA, there have been no issues running Liferay locally. But since many developers are running Liferay in a docker container, is the ARM ecosystem up to the challenge, while making sure our container stays compatible with traditional x64 machines? Let’s find out!