docs: Fix documentation according to user feedback

[Paula-Kli]

In the jupyter section was a video that I was not able to open locally neither did it play in the docs - is that just me or a general problem?

Also please read the update of the capella model carefully - not sure whether everything is correct in there

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (94cbd98) 72.83% compared to head (ebc17d8) 72.83%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1206   +/-   ##
=======================================
  Coverage   72.83%   72.83%           
=======================================
  Files         162      162           
  Lines        5345     5345           
  Branches      601      601           
=======================================
  Hits         3893     3893           
  Misses       1321     1321           
  Partials      131      131           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[MoritzWeber0]

@amolenaar Can you review the changes from the "user" perspective? Are the workflows still correct?

[dominik003]

Thanks for updating the docs. I have just a few comments and after they are resolved we can merge this one.

[amolenaar]

It looks more clear this way.

One small improvement suggestion.

[github-actions]

The pull request does not conform to the conventional commit specification. Please ensure that your commit messages follow the spec: https://www.conventionalcommits.org/.
We also strongly recommend that you set up your development environment with pre-commit, as described in our Developer documentation. This will run all the important checks right before you commit your changes, and avoids lengthy CI wait time and round trips.

This is the commit validation log:

⧗   input: docs: Update documentation about T4C token and merge flow and import t4c model documentation
✖   subject must not be longer than 72 characters [subject-max-length]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Here are some examples of valid commit messages:

build: Bump frontend versions
docs(user): Add model creation workflow
feat: Add a monitoring dashboard

[MoritzWeber0]

Thanks for the improvement, looks good in general :)

There is a new Github action to check for mkdocs warnings, please rebase on main to get it in this PR.

In addition, I have two small comments. Once they are resolved, the PR can be merged.

Conversations are resolved & @dominik003 is out of office.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud