Putting decision contents into the sphinx elements bloats the needs model

[NEOatNHNG]

The decision record element is supposed to contain attributes for the context, decision, and consequences:

process_description/process/process_areas/change_management/guidance/change_management_decision_record_template.rst

Lines 37 to 39 in 0ac7c3b

	:context: <Your text>
	:decision: <Your text>
	:consequences: <Your text>

But that has a few problems:

1. There is a regex for the attribute restricting it to one line. That is impractical for any serious decision.
2. It bloats the needs model with all the contents which are not necessary to be used from anywhere else in a structured manner.

Therefore my proposal would be:

1. Instead of having an attribute for the decision, just make say that the content of the element contains the decision
2. Context, Considered Alternatives, etc. should be contained in the context surrounding the needs element.

That way the decision and where it applies to, status, etc. is still available as structured information but when you want to know how it came to the decision you can just click on the ID so that you jump to the page containing the decision and can read all the background there.

[masc2023]

Thank you for your input, as it sound as an improvement proposal, Improvement Template would be the right selection for that, I will add the correct issues topics for that. You can just provide a PR including your proposal directly, linked to this issues, if applicable for you.

[masc2023]

@NEOatNHNG , please have a look here: #206