Transforms your application shortcuts into beautiful and comprehensive interactive graphics.

• Do you develop an application but tend to lose sight over the shortcuts you already built into your app?
• Do you use applications which feature a litany of different shortcuts and wished these could be displayed in a comprehensive cheatsheet?
• Or do you simply want to create a custom cheatsheet for your favourite game?

If you answered any of the above questions with "yes," then this package is for you!

It takes your shortcuts and creates a single-file cheatsheet which you can then either use locally, serve on your website, or even print out!

• Support for building multiple shortcuts profiles (only in the GitHub Actions workflow)
• GitHub Actions workflow to build cheatsheets without installing dependencies locally

• Support for custom keyboard layouts (ZMK, KLE)
• Printer friendly markup
• Language layout order customization. OS language detection

Need some inspiration? Then head over to the ./examples-directory and have a look at some settings that will out of the box generate beautiful cheatsheets.

If you have a GitHub account, you can use the GitHub Actions to build your cheetsheets. Create a new repository using this template repo.

1. Create a new repository using the template
2. Create a new shortcut configuration file someapp.config.yaml
3. Edit the cheatsheet-build.yaml file to include the new configuration file. Use build-schema.json as a reference to validate the build configuration file.
4. Commit and push the changes to the repository
5. Go to the Actions tab in the repository and click on the cheatsheet-build workflow. Download the artifacts from the workflow run.

You can use the devcontainer to build the cheatsheets locally. The devcontainer is a pre-configured development environment that runs in a Docker container. It contains all the tools and dependencies you need to build the cheatsheets.

Setup the environment by following the official guide.

1. Clone the repository and open it in a devcontainer
2. Create a new shortcut configuration file config.yml in the root of the repository
3. Runt the npm install command to install the dependencies
4. Run the npm run build command to generate the cheatsheets

Resulting cheatsheet will be available in the dist directory.

NB: you can, of course, build the cheatsheets without using the devcontainer, but you will need to install the dependencies manually. Use the .devcontainer as a reference to install the required dependencies. Only GitHub Actions and devcontainer are officially supported.

This is a citation from the original author of the project: Hendrik Erz

While thinking of new shortcuts to add for desperately needed commands for my app, I realised that I actually have no idea of the ergonomics of the app's shortcuts. Plus, I didn't know which keys were already occupied. So I began the usual process of finding a solution in the form of a visual shortcut designer: Google, Stackoverflow, Reddit. After I didn't even find any useful SVG-images of keyboards to built upon, I decided to act and spent a weekend coding two keyboards and this small tool. What it does is neither new nor revolutionary, it is inspired by the attempts of some other developers to visualise the shortcuts for their apps. Specifically, I thought of KotOR II, which came with a decent, high-quality printed cheatsheet back in the day.

However, this means:

• This tool is not designed to be used as an on-screen keyboard. You can certainly use it that way, but then the tool around the SVG-files won’t be necessary.
• I only included two keyboards, because you don't need more, and these were already hard to code (I wrote the SVG files by hand and decided against a dedicated app to maintain readability and DRY).
• "Why a Surface keyboard?" There's a litany of different keyboards out there, and when I have to decide, I use the one from the same company which makes the software for these keyboards in the first place. It should also work for Linux, because, you know, there's no such thing as dedicated linux keyboards (at least not well-known).
• Keys that are secondary on certain keyboard layouts (that is, you need to press the Shift-key to reach it) are not supported. Use Shift+<the default key> instead. Layer 2 and Layer 3 support is now available.

Adding shortcuts works by adding them as key:value-pairs to the config. Delimit them using plus-signs (+). You have the following special characters available:

• Esc or Escape
• Option-Left, Option-Right, shorthand: Option (falls back to option left)
• Alt-Left, Alt-Right, shorthand: Libertarian nonsense Alt (falls back to alt left)
• CmdOrCtrl, resolves to either Cmd (when selecting macOS from the platform dropdown) or Ctrl (for both Windows and Linux)
• Comma
• Plus
• Minus
• F1 through F12
• Arrow-Left, Arrow-Up, Arrow-Down, and Arrow-Right, shorthands without "Arrow-"
• Control, shorthand Ctrl
• Command, shorthand Cmd
• Shift-Left and Shift-Right, shorthand: Shift (falls back to shift left)
• Fn (function key)
• Windows
• Menu (the menu key available, e.g., on the surface)
• Tab
• Backspace
• Delete (will fall back to Backspace on macOS!)
• Space
• Special (the special key in the top-right corner of macOS keyboards, mostly Eject or On/Off)

The two SVG keyboards are licensed via CC BY-NC-SA 4.0, which means: You are allowed to modify and redistribute them, as long as you maintain a compatible license and make sure to attribute the author (that is: me). For more info, please have a look into the files, where all terms are conveyed. Additionally, see the full and legally binding license text here. Make sure you don't forget the license block in your derivatives.

The accompanying code is licensed via GNU GPL v3. Please see the LICENSE file for more information.