Re: How to organize tasks about Worg within Worg documents

[Adam Porter <adam@alphapapa.net>]

On 3/30/24 05:47, Ihor Radchenko wrote:
> Adam Porter <adam@alphapapa.net> writes:
> 
>> Using a normal heading for a task would "commandeer" the structure of
>> the document, which I think is a real problem.
> 
> Not really. If some section is incomplete, marking it "TODO" means that
> it should be completed. And the details might be listed in the logbook
> notes, for example. The section name itself does not necessarily have to
> details what needs to be done.
> 
> We have multiple instances of such "TODO" items in WORG, some also
> include comments on what should be done.
> 
> On the other hand, inlinetasks are more concrete and immediately mark
> both where exactly and what needs to be done.

You make a good point: for some cases, an entire section/heading may 
need "to be done," so giving the whole heading a TODO makes sense.  For 
other tasks, an inline one would be more appropriate.

> I am not 100% sure if we need to constrain "TODO" items to one or
> another style. Global todo list, marking existing sections as TODO, and
> inlinetasks all may have their place depending on the situation.
> 
> The policy we may want to set is whether "TODO" keywords and notes
> should be displayed to all the users. WORG has this set all over the
> place - some TODO headings are marked to be not exported, some TODO
> keywords are hidden via #+options: todo:nil, some notes are placed into
> # comments.
> 
> May we have some kind of css-based toggle that will enable "developer
> mode", revealing all the todo keywords, inlinetasks, and notes? Then, we
> hide the "unfinished" parts from users by default, but let them see what
> can be contributed?

I like the idea of a visual toggle very much, so I'm certainly in favor 
of that.

I'm not sure that we must have a constraint on the way TODOs are 
written, but having some limitations on or conventions about it might 
make such a visual toggle easier to implement (as well as other tools 
one might use to collect and visualize tasks across the project).