Rick Viscomi
Rick Viscomi
Made progress in #45 using ESM to break up the capo logic into reusable scripts for both the snippet and extension. TODO for this issue: - [ ] generate WPT...
Rules are now in their own module: https://github.com/rviscomi/capo.js/blob/main/src/lib/rules.js
https://www.npmjs.com/package/@rviscomi/capo.js @danielroe how does that look? Hope that works for you.
Just realized I'll also need to write a whole new class of documentation 😅
I like the idea of providing more detailed histograms. There are a few challenges: - they're inherently harder to grok than a single data point (ie % good) so we'd...
@Onderhond do you have any supporting documentation that not having 1 H1 is bad? For example this video by John Mueller suggests that it doesn't really matter either way: https://www.youtube.com/watch?v=WsgrSxCmMbM
Chatted with someone from the Search team about this. They suggested a generalized version of this feature request that validates that there is at least one heading element on the...
🛎 @Onderhond ping. Let us know if having at least one H1-H6 would address your concern.
Since we're aiming for feature parity, and there is no existing category dropdown to align with, sorting A-Z SGTM. However, I don't think we should change the sort order of...
We only run tests in Chrome, so I don't think this would be feasible. @pmeenan WDYT?