-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add section about the task element #233 #296
base: main
Are you sure you want to change the base?
Conversation
Hi @tomschr , could you please have a look? I get strange output in the example, although I tried to copy the structure that you used in your example. |
Yes, that's to be expected. 🙂 The Maybe my memory is wrong, but we haven't discussed it in the SLE Writer's call, have we? As such, before we describe it, we should first define when and how we use it. Additionally,
Therefore, it might be useful for a smaller task or if you split a huge task into small sub-tasks. However, that could impose some structural changes that is not always wanted. On the other side, it could be beneficial is you want to Therefore, I'd suggest to discuss this in a broader audience if we want to live with the restrictions and use it, or if the existing structures are enough for us. |
I have worked a lot with tasks elements before and never felt limited. I am in favor of having it |
I'm fine with our without it. It might be an additional crutch for writers to come up with a decent structure. Those who feel limited, can still opt to go without ;) |
+1 for having it. I think it could be applied to 99% of our topics and will further unify them (if used consistently). And if the structure doesn't fit, well, you can still go without it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dariavladykina I have added a minor question.
<tasksummary> | ||
<para>This is the summary of this task.</para> | ||
</tasksummary> | ||
<taskprerequisites> | ||
<para>This contains the requirements.</para> | ||
</taskprerequisites> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we require a <title>
for <tasksummary>
and <taskprerequisites>
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in my experience <tasksummary>
is only a repetition of the title itself in most cases, having it as an optional element is sufficient
<taskprerequisites>
should have a default title like 'Prerequisites'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. "Requirements" are rendered as a headline by the style sheets, and the summary does not really need another title.
Co-authored-by: Tom Schraitle <tomschr@users.noreply.github.com>
This PR aims to add a subsection about the task element to the Structure and Markup chapter #233