GoogleChromeLabs / tooling.report

tooling.report a quick way to determine the best build tool for your next web project, or if tooling migration is worth it, or how to adopt a tool's best practice into your existing configuration and code base.
https://tooling.report
Apache License 2.0
848 stars 49 forks source link

Tool pages #163

Open argyleink opened 4 years ago

argyleink commented 4 years ago

Our current IA:

We've got the data, we've got components (cards and datagrids), so this may be low effort with great results. Means we'd absorb all links to like webpack and rollup to this page, and then on this page link out to the respective tool. Thoughts?

This is a good one to be designed in the browser.

surma commented 4 years ago

I keep thinking that a per-tool view would be great and it should be very easy to make that a static build. Let’s try and an get this for launch