UI / UX Improvement Requests (Mainly CSS-related)
Hello,
Thank you for your continued work on FluentCommunity.
After extensive real-world usage, we would like to share several UI/UX improvement requests. Most of these are small visual or structural inconsistencies, but they have a noticeable impact on polish, accessibility, and design consistencyβespecially for communities that care deeply about visual quality.
Below are the detailed points.
1. Clickable area of lesson links
- Currently, only the thumbnail image or the title is clickable.
- We would strongly prefer that the entire lesson block be wrapped in an
<a>tag. - This improves usability, accessibility, and alignment with common UX expectations.
2. Verse block in Dark Mode
- In Dark Mode, the text color of Verse blocks changes to white as expected.
- However, the background color of the Verse block does not adapt to Dark Mode.
- This results in very low contrast and poor readability because the text and background become nearly the same tone.
3. Blockquote citation visibility in Dark Mode
- In Dark Mode, the
<cite>element insideblockquotedoes not change color. - This reduces readability and visual hierarchy in dark environments.
4. Border-radius inconsistencies with embedded media
Feed
- When a video is embedded in a feed post, the top-left and top-right corners are rounded correctly.
- However, when an image is embedded, the image itself does not have a border-radius, causing the surrounding border to look visually βcutβ or broken.
Courses
- When a video is embedded inside a course lesson, the embedded media follows the same styling as the Feed: the top-left and top-right corners are rounded, while the bottom corners remain flat.
- It would be preferable to unify the styling in course lessonsβeither make all four corners rounded, or make the embed fully flatβso the visual rules are consistent and intentional.
Feed popup
- When opening a feed post in a popup, the footer section (
feed_comment) does not have bottom border-radius applied. - As a result, it visually overflows outside the rounded popup container.
5. Duplicate borders in course lesson lists
- In the lesson list view, the
border-bottomsurrounding sections appears duplicated. - A straight border and a rounded border-radius overlap, creating a double-line effect.
- This looks unintended and slightly degrades the visual clarity.
6. Incomplete color customization coverage
-
Some UI elements do not reflect color customization settings, including:
- Hover states for lesson pagination
- Hover states for forum topics
-
Additionally, the link color for the βLoad more / See moreβ text cannot be customized.
-
Expanding color controls to fully cover these elements would be very helpful for branding consistency.
7. Feed menu settings consistency
- When the Feed menu is edited in the menu settings (icon or label),
the same configuration is not reflected in the sidebar feed. - It would be ideal if sidebar feed items inherited the same menu settings automatically.
8. Rendering of first name and last name
- Currently, full names are rendered as a single string.
- We would like the first name and last name to be rendered separately, each with its own class selector.
- This would allow more flexible styling and better localization support (e.g., surname-first cultures).
We hope these suggestions are helpful and align with FluentCommunityβs long-term UX goals.
Thank you again for building such a promising community platform.
Thank you for your feedback. Some of the issues that you have mentioned are already improved/fixed in dev. For instance, you can check here on this site.
- Border-radius inconsistencies
For feed, in modern view, single image top borders will now appear rounded just like video embeded.
And feed modal bottom borders are now rounded too.
And the other things that you mentioned, we will review these.
Tawsif Ahmed RiyadΒ Thank you for the update.
Iβm looking forward to the upcoming updates.
I also appreciate you reviewing the other points and look forward to those as well.
Tawsif Ahmed RiyadΒ Hi, after updating the plugin, the text in verse blocks has become difficult to read due to low contrast between the text color and background color. This occurs in both light mode and dark mode. All verse blocks within my community content are affected. We request your prompt attention to this issue.
Yuhei KuwahataΒ can you specify exactly where this is happening? please share the sequences so that I can recreate the issue and then fix it.
Tawsif Ahmed RiyadΒ Please check the lesson pages for my online course here. https://tokyobigaku.com/academy/course/shizenbi-reading-poetry-program/lessons
Yuhei Kuwahata, will give it a check, thank you.
Tawsif Ahmed RiyadΒ What's the current situation? I'd like to know what immediate steps I can take.
Yuhei Kuwahata, hello, the above link you provided is broken. Itβs not leading anything + getting error toast. Would be helpful if you can provide the steps on how to recreate the issue, or you can provide a screen recording, that will be very helpful and easy to fix the issue, thank you.
Tawsif Ahmed RiyadΒ Hi, the link above seems to be working, but could you please check other urls as well.
Also, please take a look at the screen recording.
Tawsif Ahmed RiyadΒ Have you been able to confirm the details of the issue?
Yuhei Kuwahata, I have identified the issue and have fixed it in my local dev setup environment. I have also created the pull request for the fix.
To help you right away, please use the below CSS properties below in Settings > Customization > Custom CSS, then save it.
.fcom_lesson_content .wp-block-verse {
color: var(--theme-palette-color-6);
}
At least, you can see the content correctly in view lesson mode. So use the CSS for the time being.
Tawsif Ahmed RiyadΒ Thanks! The verse block text is actually legible now!
Yuhei Kuwahata v2.3.0 has been released. I would suggest you to remove the custom CSS from the Settings, as this temporary fix is no longer needed, I have provided the fix in the new version. Another reason I am telling you to remove the custom CSS is, it might conflict with the new version, so you can just remove the temporary solution.
Tawsif Ahmed RiyadΒ Great news! I've updated to v2.3.0 and the fix works perfectly. Iβve also deleted the temporary custom CSS as requested. Thanks again for the fix!