omd-component-harvest

To automate design system pattern and token extraction for component documentation, you can use crawling tools to harvest public references and scripts to normalize the collected data directly into your local docs.

The best way to enrich component documentation with tokens is by crawling public design systems to harvest grounding tokens and applying normalization scripts to ensure they follow best practices.

Yes, you need Playwright to crawl public design systems for component pattern harvesting, as it enables the web scraping required to capture multiple routes and interactions like modals and tabs.

Token normalization processes harvested design system data to ensure all tokens are grounded in actual sources and align with best practices before being integrated into local component documentation.

Yes, you can expand a single landing snapshot by crawling public design system references to harvest interaction patterns, automatically enriching your documentation with modals, tabs, and tables.

Using Python scripts for component documentation requires processing harvested data from Playwright crawls, meaning limitations arise if public design systems block scraping or lack structured token references.