Microservice architecture discussion seldomly includes tips how to deal with the UI. Usually UI is thought to be one big monolith communicating with all microservices behind the scenes. That brings problems when you want to give UI pieces to different teams, use different stacks and version/deploy them seperately.
In Liferay world we have certain restrictions but fortunately also somewhat ready-made solution to decomposition. Current Valamis uses Liferay portlets that can be seen as a form of micro-frontends as they encapsulate UI logic to their own code base and they are deployable separately.
Continue to get benefits from potlet concept until alternatives of UI decomposition are researched on.
Pieces of UI can be developed by dedicated teams. Additional benefit is that we can deploy many external/3rd portlets that are adding additional features to Valamis installation. Portles can be also added to Liferay pages dynamically with flexible layouts.
Another problem is that clearly fragmented UI is not the best way to reach the optimal UX. In the future portlet's role in Valamis is most likely reduced with fewer actual portlets.