Cursorless HTML cheatsheet follow-up work

[pokey]

• Add developer docs for cheatsheet #843
• Figure out how to dump to file and then open in browser from VSCode
• Fav icon
• 'until' is missing from cheatsheet and docs #648
• The row scope does not appear in the cheatsheet #636
• Tara cheatsheet feedback #478
• Fit cheat sheet on one page #459
• Update docs to clarify that all actions require a target #456
• Improve colors and shapes display in cheatsheet #460
• Improve styling of cheatsheet #465
• Update cursorless reference, help terms and docs #599
• New simple modifiers from Support fully compositional modifiers #672
• Add sponsor button
• Set title using helmet
• Output ngrok command?
• Indicate which spoken forms are not default
• Dark mode
• Highlight section using colored border when its anchor is in the url
• Hide empty sections
• Add local search box that filters results https://github.com/krisk/Fuse
• Add settings box
  • Beginner mode Have basic version of cheat sheet #458
  • Non-coder mode Different use cases cheatsheets - specifically non-programming cheatsheet #663
  • Sorting options, eg alphabetical vs functional
  • Dark mode
• Add pencil next to each section heading that opens the given csv in VSCode. Do so by registering Cursorless URI handler. Then either try using a VSCode API open function of some sort, if it will focus the correct window. If not, spawn a subshell and call code <file>. For security purposes, probably don't want to just trust the file from the API; instead probably have set of files that are given from Talon and kept in global VSCode storage?
  • Probably simpler to just have a voice command that they can use, and show how to use it in the info box, or maybe pencil could just pop up a little hint saying the voice command to change that csv. Voice command could even be active all the time. Voice command would just run code <file> in a shell.
  • Question: will they always have code cli?
• Make each <T>, <P>, etc link to the item in the legend. Would do this by using a regex to split each description, ensuring that the regex handles <T>, <T1>, T, and T1
  • Also ensure that the legend item is highlighted when you follow a link to it (ie its id is in the url)
• Add hover-activated label above <T>, <P>, etc using info from legend
• Add voice commands for everything in the cheatsheet, including closing the tab
  • Add a box with info about these voice commands
• Add cursorless hats to all links in cheatsheet
• Switch colours and shapes to use the actual colour and shape
• Auto-hide all but a few from each section and add ...more button at the bottom of each
  • And add something to settings box to disable auto-hide
• Add link icon next to each section heading so can be linked to
• Switch to curly quotes
• Remove <> from placeholders
• Make placeholders more obviously placeholders, eg inline box with rounded corners and background or bold coloured text or something
• Use full words for placeholders, eg <modifier> instead of <M>
• Add "target T" instead of just "T" in Meaning
• Add little question mark next to section headings linking to section in docs
• Have separate "Actions" and "Complex actions" section, the former containing the actions that have single target and no formatters / pairs / whatever; hte latter containing everything else
  • Remove T from everything in simple actions section
  • subheading on Actions saying that it requires target?
• Figure out tree-shaking / bundle size using eg https://bundle-buddy.com/
• Make sub-section of modifiers for scope-based modifiers (eg "<scope>", "next <scope>")

[auscompgeek]

Dark mode

IMO this shouldn't be a setting and should just respect prefers-color-scheme

[pokey]

IMO this shouldn't be a setting and should just respect prefers-color-scheme

That's how it works today. Was thinking of adding a setting that can be used to override the system setting, but if you think that's overkill I'm happy to punt on that until someone specifically requests it