Thanks for writing this. I have added and removed about 4 million lines of code: https://github.com/wekan/wekan/graphs/contributors You are not dumb. It is normal to feel frustrated, when figuring out, step by step, how something works, and what to do. It is like labyrinth. Having enough breaks, taking a walk when needed, having enough coping skills or adding more of them, having patience to keep notes of what is... - Source: Hacker News / 7 months ago

Hi Wekan, looks cool but IHMO suffers from confusing documentation and onramp. It took me multiple attempts, days apart, after initially stumbling upon this comment to get a better sense of it. The project homepage (https://wekan.github.io/) stresses the different installers but at that point I didn't know if I want to install it or not. Clicking on the Features link (https://wekan.github.io/#features) just takes... - Source: Hacker News / 10 months ago

When I was evaluating open source Kanban recently I found WeKan had the closest REST API compatibility with Trello: https://wekan.github.io. - Source: Hacker News / about 1 year ago

Try to look at wekan. Https://wekan.github.io/. Source: about 1 year ago

Deck is very minimal and not really suited for anything beyond simple, personal stuff, in my opinion. As far as self-hosted, my favorite is still Kanboard, which has a lot of plugins and themes to choose from. Leantime is good too and a bit different. I also like Vikunja and Wekan. Source: about 1 year ago

When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises. For documents, we had to do... - Source: Hacker News / 3 months ago

There is no one-size-fits-all approach to writing descriptions, so you need to figure out what works best for you and your team. However, seeing real-world examples might inspire you to find new ways to write them. Here are some examples from descriptions we have written for Kitemaker. - Source: dev.to / over 1 year ago

Kitemaker.co - Collaborate through all phases of the product development process and keep track of work across Slack, Discord, Figma, and Github. Unlimited users, unlimited spaces. Free plan up to 250 work items. - Source: dev.to / over 1 year ago

At Kitemaker, we recently made the leap to Recoil.js for our React state management needs. Before using Recoil, Kitemaker used a simple state management solution built upon useReducer(). We built Kitemaker to be super fast, responding to every user interaction instantly. However, in organizations with lots of data, we sometimes had a difficult time achieving this due to unnecessary re-renders. Kitemaker has a sync... - Source: dev.to / over 1 year ago

Definitely feel your pain. We did a full OT implementation for our startup [0] and it was a beast. We based it on Slate.js which has a nice concept of operations that maps nicely to OT, but it was still a lot of work to get it working well (and there are still rough edges we try to improve all of the time). We did base it on Postgres in the backend so really looking forward to what the Supabase team comes up with... - Source: Hacker News / almost 2 years ago