MuhammadAli2003 wrote a reply+100 XP
6h ago
yeah that hits hard tbh 😅
I think that’s exactly what happened here — I kept doing “quick fixes” thinking I’ll clean it later, and now I’m basically paying for it
extracting component styles into a single place makes sense though, I guess right now everything is kind of scattered so even identifying what belongs to a “component” is part of the problem
like a button might have base styles in one place, hover somewhere else, and spacing overrides inside a section
I’m starting to realize I probably need to define a clean version of each component first and then slowly replace the old ones instead of trying to fix everything in place
did you ever go as far as doing a partial reset (like stripping a section back to almost raw styles) just to rebuild it clean, or do you usually refactor on top of what’s already there?
MuhammadAli2003 wrote a reply+100 XP
1d ago
yeah that makes sense, I think what’s messing me up right now is that I don’t really have a clear “source of truth” anymore
like I’ll try to fix one section (say buttons), but then I realize there are like 4 slightly different versions of the same thing across the page
so even if I standardize one, I’m not sure if I’m actually fixing the system or just creating another variation again
right now I’m leaning toward slowly extracting patterns instead of touching everything at once
like:
- rebuild one clean button component
- then replace old ones gradually
- same for cards / sections
but it still feels a bit risky because everything is kind of interconnected
did you ever try isolating styles first (like resetting or removing overrides) before rebuilding components, or do you usually just start fresh inside the existing mess?
MuhammadAli2003 wrote a reply+100 XP
2d ago
yeah that actually sounds like what I should’ve done from the start instead of redefining things everywhere
I think part of the problem now is I don’t even know what my “base” styles are anymore because everything got slightly modified over time
like even buttons or cards look similar but aren’t actually using the same structure underneath
did you ever run into a point where it just becomes easier to rebuild instead of trying to standardize something that’s already all over the place?
MuhammadAli2003 wrote a reply+100 XP
2d ago
yeah that actually makes sense, I think one of my main issues is I didn’t structure anything from the start
everything was built section by section so even when I used classes, they ended up getting redefined in different places instead of reused properly
the separate css per component idea sounds way cleaner compared to what I’ve done
curious though — when you’re dealing with something that’s already messy like this, do you usually try to reorganize it gradually or just rebuild with a proper structure?
because right now it feels like fixing one part just creates problems somewhere else
MuhammadAli2003 started a new conversation+100 XP
2d ago
Hey,
I’m working on a small project built on WordPress, but instead of using a proper theme structure I ended up building most of the UI using custom HTML + CSS blocks.
It worked fine early on, but now I’m starting to hit a wall.
Main issues I’m running into:
styles are duplicated across multiple sections I’ve relied too much on !important to override things no real global system for spacing / typography layout is inconsistent (mix of flex/grid depending on what worked at the time) small changes tend to break something else
At this point it feels like I’m constantly patching instead of improving anything.
So I’m trying to figure out the right move here from a dev perspective:
Do you usually refactor incrementally (cleaning styles section by section)? Or is this one of those cases where it’s better to scrap and rebuild properly with a structured system?
Curious how others approach this when a project reaches this stage.