One post tagged with "docs"

eslint-plugin-vite now has a clearer baseline for the things maintainers and users touch first: branding assets, docs navigation, ADRs, charts, and repository-wide validation.

That baseline work matters because the project is no longer a generic plugin template. The site, manifest, and docs structure need to communicate that this package is about Vite config safety, client-runtime correctness, and Vitest workspace discipline.