Mochitto

It would be nice to add an editor of choice in the config and cards open up in it when they have errors, so that users can edit them and...

UI/UX: Add styling for fill-in-the-blanks text

1

As of now, since there is no style defined by the themes, the colors used by the addon are green, orange and red. These work when clozes' colors have good...

Creating a read the docs for the project using pages

1

Right now the Readme is very packed with information and can seem very menacing. It would be much nicer if the project had a doc page with all of the...

Interactive configuration

1

As of now, the setup of the app is pretty complex. Adding an interactive setup (asking the user on first setup) could make for an easier UX. **Notice**: interactive setup...

Cards injected using markdown2anki should have a md2anki tag for future use

1

In the future, there might be the need to fetch all cards created using markdown2anki (editing them, statistics etc.). An easy way to provide an "handle" to do this, is...

Use Anki's API to send cards to Anki

2

Using CSV/manual import is a bit annoying; it would be nice if you could use the Anki API (it would require you to add the path to the collection file...

UI/UX: Add newlines to code blocks

1

As of now, code blocks use `display: block` on the spans that represent a line. This means that when you are copying from the code-block, the text will not have...

Markdown input as folder or file

3

When using markdown to anki, it's likely to create different templates for different decks. As #11 turns markdown files in "templates" or "note types", it's likely that users will have...

Adding metadata to markdown input files

1

When using markdown2Anki, users are likely to create different notes for different decks or note types. This would, in practice, make it possible to define "note types" inside of markdown...

As of now, the only way to "fix" cards is to open up anki's html editor and change the code from there. This is ok but not optimal and if...