For this episode of Radio Liferay, I've talked with Bryce Osterhaus, Frontend Developer at Liferay for ~ 6 years.
With his experience, he's a perfect complement to me: While he feels at home in the browser, client side, I'm comfortable on the backend, away from all of the messy frontend stuff - prepare for some naïve questions coming his way.

We spoke about a design decision that has been made in some internal projects: His team has built a UI that does not utilize Liferay's page/site infrastructure. It's rather  an application that utilizes some of the infrastructure but not what's typically used to compose frontend applications on a portal.

Or, in the rage of the day, you could say: "Headless". ;)

Or, in more detail, here are some talking points

• Systems that Bryce worked on - e.g. Loop (a timeline based Intranet solution used within Liferay), Analytics Cloud UI.
• Reasons to go headless, not utilizing Liferay's pages
• What's still being used from the platform (only touching)
• How maintainable is such an approach? Does it upgrade well?
• quo vadis, react@Liferay?
• Clay, a web implementation of the Lexicon Experience Language https://github.com/liferay/clay, https://clayui.com
• Highlighting dropzones, a long story that finally came to an end
• Where does the frontend team hang out?
• Versions of Liferay and React - running together?
• React and Liferay's SPA framework

Follow @RadioLiferay and @olafk (me) on twitter.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory. If you like this, make sure to write a review for the podcast directory of your choice - or find everything (*) about Radio Liferay on radioliferay.com.

Or just download the MP3 here:

(*) At the time of publishing this episode, you actually won't find everything - the Radio Liferay homepage didn't yet move to the community pages, so it isn't updated with newer episodes. Sorry - we're working on it, but as the podcast is a spare time project, working on the infrastructure is slower than on other projects... But the feed continues to work - just subscribe...