- Add Table : Add tables to anki cards
- Advanced Browser : Add column sorting
- AwesomeTTS : Add audio to anki cards
- Browser TableEditor : Display Table and editor side by side
- Colorful Hierarchical Tags : Add hirearchical tags
- CrowdAnki : Import and export deck as JSON
- Custom Background : Rice Anki UI
- Duplicate and Reorder : Create cards by duplicating existing
- Enhance main window : Rice Anki UI
- Highlight Search Results : Highlight search results
- Mini Format pack : More formatting options
- Minimal Flat Big Buttons : Rice Anki UI
- More Deck stats and time left : Display time stats on home screen
- Remaining time for anki 21 : Display time stats on review screen
- Review Heatmap : Display heatmap for reviews
- Search Bar : Add search bar to reviewer and editor
- Vim answer shortcuts : Vim shortcuts to answer
I tried open sourcing and public collab using github + anki. I don't really like the current status of remote collaboration. In my experience, if you want a large group of people to collaborate you have to reduce the barriers as much as possible. It has to be as simple as - here is a link , edit/comment on the column you feel like needs to be changed. I want the work flow to look something like this :
-
Editing remotely is done to a shared file (e.g. google sheets)
-
Editing locally is done in Anki
-
In both cases you read from github directly making the github file the main "source of truth".
-
To publish changes use GithubSheets (or something similar for whatever service you are using) with an authentication token
-
To publish changes from Anki , clicking sync would export deck as Json/CSV/XML/... this would create a pull request to github.
-
If you are a recognized editior (i.e. have an authentication token) the pull request gets auto accepted = auto sync.
-
Both sheets and anki reflect changes automagically since they are reading and editing the same file.
-
It's not live and editior permissions can be mananged by choosing to share sheets link/permission or the github authentication token.
This doesn't seem achievable unless anki itself integrates with github or some other versioning service. The closest thing to this seems like Anki Remote Decks.
Current things that irk me :
- CrowdAnki : Each deck has to be in a seperate repo which I don't like
- CrowdAnki : The repo name has to be the same as the local deck name which I don't like
- CrowdAnki : Editing suggested be done in to JSON file , not user friendly at all.
- BrainBrew : No idea on what exactly the yaml recipies are ... ?
- Anki Remote Decks : Creates a new seperate class of deck 'remote decks' and all remote decks are subdecks. Cannot rename/move the deck.