RL067 Bryce Osterhaus's guest appearances

RL067 Bryce Osterhaus

Radio Liferay

Michael Young

Juan Gonzalez

Brian Chan

Dennis Ju

Jorge Ferrer

Kristoffer Onias

Victor Ware

James Falkner

RL054 Scott Nicklous

Neil Griffin

Raymond Augé

Jens Bruhn

Thomas Schweiger

Bryan Ho

Stian Sigvartsen

OwlTail

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 

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 <ul> <li>Systems that Bryce worked on - e.g. Loop (a timeline based Intranet solution used within Liferay), Analytics Cloud UI.</li> <li>Reasons to go headless, not utilizing Liferay's pages</li> <li>What's still being used from the platform (only touching)</li> <li>How maintainable is such an approach? Does it upgrade well?</li> <li>quo vadis react@Liferay?</li> <li>Clay, a web implementation of the Lexicon Experience Language <a href="https://github.com/liferay/clay" rel="nofollow" target="_blank">https://github.com/liferay/clay</a>, <a href="https://clayui.com" rel="nofollow" target="_blank">https://clayui.com</a></li> <li>Highlighting dropzones, a long story that <a href="https://liferay.dev/blogs/-/blogs/drag-drop-indication-on-liferay-ce-7-3-1-ga2" rel="nofollow" target="_blank">finally came to an end</a></li> <li>Where does the frontend team hang out?</li> <li>Versions of Liferay and React - running together?</li> <li>React and Liferay's SPA framework</li> </ul>

RL067 Bryce Osterhaus on Frontend Development