bigoh1
commented
3 weeks ago First of all, let me express my sincere thanks to all AppFlowy maintainers!
I can second this issue. Let me give some additional motivation.
In PARA method, one aims to have a central place to store all of your
- Projects
- Notes
- Resources
- Tasks
- ...
and then create relations between them.
Let me illustrate it with an example. Imagine you have two projects:
- a) Open a restaurant
- b) Open a coffee shop
And in both cases you'd like to store somewhere in your (personal) knowledge management system, the greatest coffee recipe on the planet. You will use it in both projects, so how to apply the programmer's DRY here?
- You could probably just create a dedicated page with the recipe in one project, and add a link to it in the other.
- Or, you could create one database for your Projects and one for Notes, and in every project display the associated Notes to that project
Why is 2 much better than 1? You can now use the full power of the databases:
- Create a field called 'Archived' in your notes DB, and display only notes with that field unchecked
- Or create 'progress' field for a note
- Or 'starred'
- And whatever you want!
This approach can also be applied to tasks. Create a main DB for all of your tasks and have a relation in them pointing to the projects they are assigned to
This way, you can see all of your current tasks in the main view (say on your home page) and also see tasks per project.
And all of those involve creating many many views. Specifically, each project (you might have 20+ of those) will have a dedicated view for Notes DB, Tasks DB, Resource DB etc
Description
One thing that’s a bit frustrating is when I have a main grid called 'Tasks' where I manage all my tasks. Every time I link this grid inside, for example, a document, a new view is automatically added to my main grid. This becomes a problem because if I link the Task grid to, say, 50 different documents, I end up with 50 new views in my main grid, making it unusable. If I try to remove these views from the main grid, it also removes the linked grid from the documents. Is there any way to prevent this from happening?
Impact
Database users
Additional Context
No response