The new Roblox communities layout introduces multiple user experience and display issues that significantly impact readability and engagement. Below are the specific problems encountered:
1. Group Descriptions Do Not Respect Newlines (Visual Clumping Issue)
As shown in the screenshot below, the group description entered on the configuration page includes proper newline formatting:
However, when viewed on the community page, all newlines are ignored and the entire description is displayed as one clumped paragraph:
This makes it extremely difficult to read, especially when listing social links, event info, or multiple lines of text.
Newlines only appear correctly if the user clicks the “more” button to expand the description, which should not be necessary for basic formatting like line breaks. This is a serious downgrade in readability and overall UX.
2. “more” Button Is Poorly Styled
The “more” button is lowercase and visually outdated. It appears unstyled, like a generic hyperlink, and is not consistent with modern UI practices. This makes it easy to miss and contributes to users not expanding the description to view intended formatting. It should be capitalized (“More”) or replaced with a more contemporary button style.
3. Social Links Now Hidden Behind “More” Button
Previously, social links were visible directly on the group’s main page, increasing exposure and engagement with external communities like Discord and Twitter. Now, social links are only shown after clicking “more,” which drastically reduces their visibility and will likely result in fewer people joining linked servers or platforms.
There should be a setting in the group configuration to toggle whether social links are shown immediately or hidden behind the “more” button. This change feels like a regression and negatively impacts community outreach.
Unfortunately I don’t have before & after screenshots for any of these three issues, because the updated UI seems to be at 100% rollout right now. But if anyone has them on hand and wants to contribute to this report, feel free to do so!
A private message is associated with this bug report