A while ago I sat down with Ryan Schuhler. He's Associate Program Manager at Liferay, which is a fancy name for Webteam Lead, and we talked about "dogfooding" Liferay DXP to build liferay.com - which features are used, how the site evolved and what is fed back into the product.

Or, in more detail, here are some talking points

• the versions in use and how Liferay DXP is used to build the different liferay.com sites.
• How use of the features changed over time - e.g. today, marketing authors are writing their own content, utilizing Content Pages
• How similar pages are maintained - using events as examples
• Integration of external tools into the site - e.g. for analytics, marketing, business development, and who's working with that data
• What goes back into the product? Feedback? Tools? Integrations?
• Maintainable Plugins (my presentation in german language) (via LDSF-On-Demand 2020 https://www.liferay.com/de/web/l/events-ldsf-dach-recap) and the Maintainable Plugins Challenge (english) https://liferay.dev/blogs/-/blogs/maintainable-plugins-challenge
• To what extent does Liferay DXP get extended for use on liferay.com vs using stock features?
• The infrastructure required to run liferay.com
• geographically distributed clusters vs recent developments in accellerating the speed of light ;)
• Ryan's Devcon presentation "Migrating liferay.com to 7.2 and DXP Cloud" https://youtu.be/FrJRhIFzc0M
• And , of course, "eat your own dogfood" vs "drink your own champagne" as illustrated in this image, CC by-sa 2.0, by anne beaumont