When creating a new text file for a deck using the Windows Explorer (context menu -> new -> text file) or using e.g. the new file command of VisualStudio Code, Decker fails with an encoding-related error (will provide exact error). I guess this is because Decker expects some encoding, but Windows defaults to another when creating a text file. Copying the `example-deck.md` from `decker example` and replacing its contents works. I know that this is - in a way - a user error, yet it is not easy to create files with the correct encoding on Windows. To support the user, I suggest e.g. a `decker create deck-name` command that adds a `deck-name-deck.md` at the current path, with some sample metadata in the correct encoding?