Coming back to items 3-5:
- This is a tough one. Ideally there is no input lag and the lightbulb system as it is now works amazing. I get why you opted for that. I’m far from a web-tech expert, but I’d imagine that would be expensive in hardware / ISP costs to improve that.
The others options do indeed come with their own downsides usability wise. I think all of these options are about equal to me. If I had to choose I’d just not hide the row after marking as known. That one has downside if you are just there for marking, but also upside in the sense you can see which one you DO know. Maybe a filter on the page in combination with that could work wonders?
4a+b. I think simplest would be to add a page to the ‘Articles’ section with this information. And maybe rename that section to ‘help’ or ‘FAQ’ or something similar.
4c. Sounds great. I have no real suggestions here since I know nothing about building a website. But that sounds like it might do the trick. Just don’t bankrupt yourself on hosting costs, that’s not worth it 
- These are smaller issues for sure. It would just be a shame if people go to your site and bounce of it confused because they didn’t find the menu’s. (like me the first time I used the site) Sounds like you have a good handle on that.
1 Like
Done, thanks! Still new here, so didn’t know that was an option. 
2 Likes
- I definitely think having a multi-select would probably work best. Web-dev wise, its the smart thing to do, as you don’t bombard the server with hundreds of requests each with a single state change.
Sometime in the future, maybe also add support for WK API keys and importing your current guru’d list of vocab? I definitely find it pretty tedious going through and clicking every single word manually, especially when theres thousands.
1 Like
To be honest, maybe its better to rethink the account and database approach and take a more Anki-like approach? Something like storing all words and data locally, on the browser, and then adding some sort of sync mechanic.
1 Like
Although not currently on my to-do list, it is very doable. It’s something I’ll keep in mind as a potential future item.
Do you have examples of where something like this might be used for a site like Manga Kotoba?
One area I could see is when marking words as known, initially store all markings in the browser’s local storage, then after x words marked or y amount of time passes, or a link is clicked, push the word changes to the server all in one go.
1 Like
I think the main idea with this is that you completely remove the server-side rendering aspect which would remove a lot of the problems with sticky bars, marking stuff taking a while to process, etc. It would basically be like how the site was initially (stuff was stored locally it seemed), but just with an additional sync button to let you sync progress across computers.