Replies: 4 comments 2 replies
-
|
As always, this is awesome stuff @danymat! 🥳 Nested projectsRight now, if I understand things correctly, your folder structure associates different meaning to the first level of folders (calling them areas of focus (which I presume are contexts?)) which in turn include a single file per project. Do you plan to support more deeply nested structures? For example: I think it would be reasonable to assume that (when working on large projects) some sort of sub projects will arise at which point the single-file-per-project will no longer work. May I propose instead a folder-tree-per-project structure? You could then default to e.g. using an Areas of focusThese are what you use to construct the base folders, right? To me, this seems a bit misleading. Unless there is a difference between these areas of focus and contexts, then disregard all of the below. I know that we said before that you want to have single workspace for gtd, but assuming a config like below I think this may also be worth exploring: load = {
["core.norg.dirman"] = {
config = {
workspaces = {
main = "~/neorg",
gtd = "~/gtd",
home = "~/projects",
work = "~/work",
}
}
},
["core.gtd.base"] = {
config = {
workspace = "gtd",
contexts = {
home = "home",
work = "work",
},
},
},
}Maybe you could even do: ["core.norg.dirman"] = {
config = {
workspaces = {
main = "~/neorg",
gtd = "~/gtd",
home = "~/gtd/home",
work = "~/gtd/work",
}
}
},
if you wanted to keep your idea of having everything in one gtd folder. But you see how this way is less restrictive and more powerful. These were just some thoughts on the |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that nested workspaces are indeed a thing :) |
Beta Was this translation helpful? Give feedback.
-
|
Hello @mrossinek, thank you for your propositions, and I will try to respond to everything. Nested ProjectsI already though about the proposition, but somehow I forgot to write it down on the specs. Separate workspaces for AOFIndeed, it is an idea to explore. However, we have to be sure to understand what's an AOF before: In GTD, they recommend to ask yourself the question: what are your responsibilities you want to be accountable of? (Mines are atm: Personal, Work, Studies) But reading through this, and sleeping on the project management workflow made me think of different implementation, which is Tasks SpecsI'm very concerned about the amount of code and feasibility of the initial proposed solution, which involves tasks groupings.
Projects SpecsFollowing above, a project could be a heading in a file, like so: AOF SpecsFollowing above, the new AOF location could be a .norg file, with the related projects inside the file. Example treeThis could be an example for this new spec: What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, I updated the specs, new changes are precised on |
Beta Was this translation helpful? Give feedback.
-
|
New changes in task format: |
Beta Was this translation helpful? Give feedback.
-
|
New changes: please checkout out the |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
I kept discussion #61 for implementation purposes.
I created a spec for GTD, taking into account: my experience with gtd, your remarks on #61, best practices on other applications and the default gtd specification.
Below are the specifications (with norg format, feel free to paste it in a .norg file in order to have syntax highlighting).
Beta Was this translation helpful? Give feedback.
All reactions