Turning a 4,000-node DOM into 40 components: the hard part of website-to-React (opens in new tab)

In my last post I broke down why "convert this website to React" is so much harder than scraping HTML, and I ended on the one problem I called the hardest: turning a rendered page into actual components. This post is about that problem specifically, because it's the difference between output a developer keeps and output they delete. Here's a 2-minute demo of the tool doing the full conversion first, so you have context: The gap nobody warns you about A rendered marketing page is routinely a f...