Selecting the specific CSS from inside any other CSS will speed things up a lot as I have to keep pressing back to search through the list.
Ability to search for a specific line of code would be very helpful to see where I am changing it.
AI-generated summary
Users are discussing the need for a more efficient way to search through CSS within components. hipp0 suggests adding a search feature that scans the full contents of components — including CSS code — not just names or descriptions, to avoid manually scrolling through lists. They provide screenshots illustrating the current workflow limitations and the desired functionality. ToddZ seeks clarification, confirming whether the request is to extend the component list filter to include CSS content, noting that the current filter doesn’t even search descriptions — possibly a bug. hipp0 confirms the goal: full-text search across all components and CSS. ToddZ questions the approach, sharing that they manage all CSS in a single, well-commented component, and asks if hipp0 is creating many separate components — which might explain the need for better search. hipp0 explains they organize CSS by website area (e.g., Sidebar, Header) across different components to avoid scrolling. Moin suggests consolidating CSS into one theme component with separate SCSS files (e.g., /stylesheets/my-styles.scss) imported via common.scss, as recommended in the documentation, to maintain organization without fragmenting components. The discussion highlights a tension between component organization preferences and the need for powerful, full-text CSS search capabilities.
This seems a little confusing, so just for clarity: are you saying that you’d like the components list filter:
…to not just look at component name & description, but also the full contents of any components with custom CSS?
(Side note: as near as I can tell, the filter currently acts only on component names, and doesn’t return anything based on words in descriptions. So that bit might warrant a bug report.)
1 Like
Yes, to search all your components/css for specific search terms.
Hm. Sounds tricky. Components come in many forms, and lots have nothing to do with CSS.
Are you creating a lot of separate components for your CSS customizations? Just curious, as I’ve never had issues navigating mine. I keep them all in a single custom CSS component, heavily commented with timestamps…
1 Like
Maybe the component section and CSS section need to be separated so they aren’t confused.
I have my CSS organized f or the areas of the website, so I don’t need to scroll through a bunch of stuff.
Like any changes to Sidebar is in the sidebar component, etc.
If you have that many CSS changes, it may make sense to create one theme component where you use separate files to organize your changes by area.
2 Likes