manuel introduces Featured Lists, a theme component that allows administrators to create, filter, and showcase custom topic lists on their forum. The component is highly customizable via CSS, supporting various design styles, and includes a settings editor for configuration. It utilizes specific CSS classes (.featured-lists__wrapper, .featured-lists__list-container, etc.) for styling.
Users raised several questions regarding functionality and customization. digitaldominica asked how to hide “About the category” topics and empty rows. manuel confirmed that empty lists are no longer rendered after an update and suggested using CSS to hide pinned topics, as there is no dedicated class for “About” topics. digitaldominica later clarified that they wanted the “Post” button to direct users to the specific category of the list rather than the admin default; manuel explained this functionality is already built-in, pre-filling the composer based on the list’s category or site settings.
Other inquiries included hiding specific lists on certain pages. hoangviet and Maria asked about hiding lists on specific categories or moving them below content. manuel and manuel advised using CSS or placing the component on different plugin outlets. manuel also noted that custom class names can be assigned to lists for targeted styling.
Regarding limitations, manuel stated that displaying categories instead of topics requires a different component, such as Featured Categories Header. dmitcha reported an issue where the display count reverted to 3; manuel clarified that the setting must be saved twice (in the editor and on the main page). Stephane_Roy reported a display bug with Topic Cards, which manuel resolved by updating the component to the new Glimmer topic list component.
Finally, manuel explained that the component uses default topic list styling and cannot be isolated from other theme changes. satonotdead asked about custom URLs, and manuel clarified that only specific routes from the dropdown are supported. After a breakage in Discourse v2026.9.0, manuel merged a PR to fix the error and moved the repository back to GitHub for better alignment with update tools.