Refactor story page to summary page

[manuelmeister]

This PR introduces the ability to filter ContentNodes and display them in an summary.

Solves #5067

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

[BacLuc]

please fix the lint warnings in the new code, then i will approve.

[BacLuc]

You still have lint warnings in new code, e.g. here:

please fix these

[manuelmeister]

@BacLuc strange, it somehow didn't complain when I linted locally in the container.

[pmattmann]

Even if I understand the idea and can see the technical 'beauty' in it, I still wonder whether all our users understand the function.
Wouldn't it be easier to create separate function blocks for the individual summaries?

A few detailed questions:

• Should users be able to print the notes (without context) individually?
  Or does that rather tempt to use them in a strange way?
• Should it be possible to print block destinations and block contents individually?
  Wouldn't a combination be practical here?

[manuelmeister]

Wouldn't it be easier to create separate function blocks for the individual summaries?

We could still do this afterwards, if we see the need for it.

• Should users be able to print the notes (without context) individually?

What context du you mean?

Or does that rather tempt to use them in a strange way?

What bad could it do?

• Should it be possible to print block destinations and block contents individually?

  Wouldn't a combination be practical here?

I don't understand what you mean. Can you give an example?

[pmattmann]

Wouldn't it be easier to create separate function blocks for the individual summaries?

We could still do this afterwards, if we see the need for it.

Note sure. Migration from generic to concrete is not necessarily trivial.

• Should users be able to print the notes (without context) individually?

What context du you mean?

In what case are 'all' notes meaningful without the other block information?
I guess that the notes are named specifically so that only some of them can be printed.
This is so specific that we can hardly take it into account when migrating from generic to concrete concept.
And it will probably be difficult to remove it completely.

Or does that rather tempt to use them in a strange way?

What bad could it do?

If we can't get rid of this print-block, we will have to be maintain forever.

• Should it be possible to print block destinations and block contents individually?
  Wouldn't a combination be practical here?

I don't understand what you mean. Can you give an example?

Sorry, typo.
Should be LearningObjectives and LearningTopics.
Wouldn't be more practical to have printed both of them?

[manuelmeister]

Core Meeting Decision

• Only do this for 'Storycontext' & 'SafetyConsiderations'
• Create two separate configs for the GUI
• Remove instanceNameFilter. This way it will certainly be abused. We would rather implement a more sophisticated way of defining "categories"/"tag"

[pmattmann]

There is one more problem - but it already existed before this PR.

If you have a content with the period selector in the print configurator, the periods are printed in the order in which the periods were clicked.