This week, Pure Cascade stopped being a UI mockup and became a working tool.
🔧 What’s new
Built the core analyzer using PostCSS
Added metrics for:
total rules / selectors / declarations
unique selectors
property frequency
Implemented ZIP import — you can now drop a project archive right into the browser and get a real JSON report.
Connected everything: front → analyzer → report.
It’s still raw, but it already parses real CSS and shows meaningful data.
🧩 Why this matters
The hardest part isn’t building UI — it’s making the system actually understand CSS.
Now that the parsing and counting pipeline works, adding more logic (duplicates, conflicts, health score) is straightforward.
🚀 Next
detect duplicate selectors and conflicting declarations
compute a CSS “health score”
display it nicely in the Report page
Once that’s in, Pure Cascade will evolve from “parser” into a true CSS health monitor.
Small step, big unlock — now it’s analyzing real code.
Top comments (0)