Figured I’d post about this here as well:
I’m looking for new user testimonials to be used on the landing page of Kitsun. If you have something nice to say about using Kitsun and would not mind being on the landing page (with a small picture and your first name), please let me know through PM on either the Kitsun forums or on discord (Neicudi#8494) 
Your username will not be mentioned so you can stay kinda anonymous if that’s your wish.
First thanks @neicul for Kitsun, I am really enjoying it after the first month of use, the anki import feature especially was fantastic for me. One question, if you dont mind: Is it possible to modify the icon of community decks we are using? Not a big deal but was hoping to customize my deck page a bit.
Hey @superfunc, glad to hear you enjoy using Kitsun!
Community deck icons can not be modified as the author decides on the look and feel of the deck and cards. For your own decks you are in full control of course.
That said, if you really wanted to and have the coding knowledge for it, you (or someone else) could create a userscript that changes it according to your wishes. But it might be more effort than it would be worth it 
its days like this I wish my programming knowledge was in webdev rather than systems programming haha (I mostly work on internal C++ libraries).
Posting another preview of something that might be coming up soon :
Spreadsheet functionality
Adding this will hopefully make it much easier to create, manage and update your cards ^^
This view will be available as an alternative “editing mode” for the current management table, and will only be available for your personal decks.
This sounds like a great way to edit and manage cards. 
If someone exports a link to a WK item to this spreadsheet will it be clickable in the card or spreadsheet?
Thanks, I think so too!
That depends on the layout that they are using. If the layout is set up in a way that it creates a button/link out of the field values, then yeah 
How do we create such a layout? I am thinking of Item Inspector users. What type of link should they export toward Kitsun? A plain URL or an html a tag?
It depends on the layout they select or have created. The plain URL would allow for the most freedom in terms of what to do with it, while the <a> tag would be easier in use for users without knowledge of HTML.
Layouts in Kitsun are made with HTML, CSS and a special templating syntax for built in functionality. It depends on the user which ones they use for their cards
I see. What should I recommend to users that are not geeks? Can we recommend a simple default option to users that can’t find their way in HTML and CSS? I have something for spreadsheet and Anki users in the Item Inspector doc but I have nothing for Kitsun users. I want to fill this gap in my doc.
Understandable! I imagine a <a href='linkhere' target='_blank'></a> would work for them. I do remember our talk about some tags being stripped from the Kitsun import, so I’ll have to doublecheck if that was changed by now. But if you add the option I’ll make sure it works well soon 
On a sidenote, perhaps it would be cool to offer both options so the user can always choose whether they want the HTML in there or not? (I personally would prefer it without it) Could leave the default as the html version as well ^^
Item Inspector already has the option of exporting either a plain URL or an <a> tag. There is also a formula format option for spreadsheet users.
I will recommend non-technically oriented users to use whatever works best for them. At the same time power users have the ability to use the plain URL as they see fit. However the <a> tag does not come with target='_blank'. If you recommend this to be the best for non technical users I will add this option for Kitsun in the next version of Item Inspector. I just need to coordinate with you to make sure what I recommend works in Kitsun.
Some details on how this works:
Item Inspector export feature has been ready for months now. All that is missing is making sure that HTML imports work on the Kitsun side and what is the best recommendation to put in documentation to users that are not HTML experts. Everything else has been tested and is working.
Ah great!
A target='_blank' attribute would ensure that the link is opened in a new tab, rather than replacing the current page (thus ending the review session), so that would definitely be helpful I think
Sorry for the wait on the tag whitelisting. I’ve added it and it will be going live with the new update in a few days. So after that the imports should work correctly.
Thanks for your work!
OK I will add a target='_blank' option for Kitsun users since this is clearly the best option for them.
I’m not fully following this conversation, but if a tags are whitelisted in layouts, you may want to automatically add target='_blank' when rendering the card so the deck creator doesn’t have to know to do this.
If this comment is irrelevant, sorry about that.
I think this is a good idea. However I will adapt Item Inspector to whatever Kitsun is doing.
Has anyone made any decks on kitsun yet that contain the other words that WK does not cover? Or even better, did anyone create a deck that has the other WK words that also use the WK mnemonics to help remember?
Yeah, there are a couple of different decks that contain stuff that WaniKani misses. One is common words that contain kanji we learn, the other is the kanji from N2/N1 that aren’t included here, if I recall.
Oh nice! Do they contain the mnemonic system that WK uses or is it more like anki?
I recently published a deck that contains the missing Joyo and N1 kanji (w/ supplemental vocab) based on wkstats. I wrote the mnemonics based on WK radicals. You can work it like WK or go free style but tagged the cards for a level 61-70 experience.
I kept the mnemonics short given the format (and I think it’s easier to remember rather than a long story). Some mnemonics are based on known kanji (if you gone through WK)…I think this is a far more efficient method than forcing more radicals than necessary. I don’t claim to be a mnemonic master, I did the best I could. I have to work through it to tune it if necessary along with any feedback.
