V4 of Drafts was simply a way station where my text was entered, but always went to a destination outside of Drafts.
V5 changes this. This is due to Workspaces, tags and the macOS app.
Using Drafts as my text destination and repository has caused some challenges and I’m looking for others who are doing this and want to learn from their workflow and actions and strategy.
I’ve had some email interchanges with Agile Tortoise about this and thought it would be good for the forum.
What is the best way to store your drafts. Getting stuff in is unparalleled. No app is as fast and it’s what I love about drafts. But if Drafts is the final destination how is the information best saved? For example, I take meeting notes in drafts, do I create a tag for each area and create a workspace? All my tasks are in Drafts. Currently in one Draft, however, having a separate Draft per task would allow me to make notes and subtasks. With 150 tasks, does this become to unwieldy? Is the secret in setting up detailed workspaces to help you find your information?
Should I create long notes or short snippets that become linked by tags? How easy is linking drafts, would that be better than tags? Can I take my draft meeting note and easily email it as an rtf pdf to all attendees?
If Drafts becomes my text database, how much text can it handle? There would be no point if in a years time it takes too long to open or do anything?
Is mass export possible? After a year I may want to permanently archive text outside of the app because the text is now redundant?
These are just some questions I’m asking and am looking forward to how you use Drafts as your notes database.