Thanks for trying it out! The main use case is for more focused discussions / information sharing. It started as a threaded chat app but evolved over time. I u

Thanks for trying it out! The main use case is for more focused discussions / information sharing. It started as a threaded chat app but evolved over time. I used the GitHub Issues analogy because you could use the app to make a customized generic version of a GitHub-issues-like bug tracker. For that analogy, you can think of each board in ThinkBase as a repository of issues, while the cards are like issues. Each board that you create in ThinkBase can have its own "card template" to focus the cards/conversations on that board, just like GitHub Issues has templates. When it comes to tracking the status of your cards, you can create your own tags like status:open, priority:10, asignee:mike, and then perform queries on these custom tags (e.g.: segment engine status:open priority>1) to segment the cards to your liking. The main power (I hope) of the app is that you can focus each board on whatever type of discussion or information sharing use case that you'd like depending on how you craft your templates and tags. Boards don't have to be "issues" focused but they could be. To be honest, at this point in time I'm still refining the different possible use cases. Perhaps there is a better analogy to use. Once I'm able to hone in on one or a couple solid use cases I'd like to build out more features to better support them. You bring up a great point about columns. I've been thinking lately of a feature that would allow you to choose which tags you want to use as your columns if you prefer a column view. So for the GitHub Issues analogy, you would create the tags - status:TODO, status:doing, status:done, and designate those as your "columns". Appreciate the feedback.