Daniel Woste

Tested it with Sphinx ``4.0.2`` and ``3.5.4`` (Added also to issue description)

There is already a PR to fix this problem a little bit #1218 Sphinx-Needs already has the needed, rtd specific code. All we need is this PR, so that the...

I haven't tested it a while, as the sphinx-needs related fix is already part of the releases since ~6 months. So it should work, if you fix the related line....

@nienn : I hope this PR is fine and solves #117 as expected. I have also added some documentation and a changelog entry. As this is my first PR on...

@agjohnson Thanks for your feedback and for the overall work on RTD. The change itself is really small, one line. And it does not have any side-effects to the theme...

@agjohnson or @Blendify or @nienn: Any thoughts on this concept? Would we lucky to support here with an PR.

It could be doable with ``needuml``. But where shall these needs get represented in the documentation? Or shall they be just "internal" and have no own representation?

@twodrops: Any updates for this one?

Idea: ``` ' @rst ' ' .. req:: REQ 1 ' :id: REQ_1 ' ' Need content ' @endrst node "compoent X" as comp_x ``` Directive `uml_extract` load everything between...

Maybe this can be better done by a generic extension, called e.g. `rst-extractor`. This extension could handle every text-based file and is not specific to uml and co. Example ```...