docs: improvements following feedbacks

[MarieS-WiMLDS]

context

First release of the docs, we had a lot of feedback. Let's concatenate all of them here.

TODO

• docs: Real-life use case in getting started #592
• docs: orders of the top menu and left one are different #593
• docs: markdown issue in cross_validate #589
• docs: order in the user guide is odd #590
• docs: remove "without notice" in the top warning #591
• fix(docs): In the skore cross validation example, the plotly graph is not full size in the rendering #594
• docs: A few feedbacks from @tuscland #595

[augustebaum]

Why is this an epic? Now that everything has been converted to issues, can this issue be closed?

[MarieS-WiMLDS]

no we can't close it, the idea is to track the progress at a global level. for instance, I linked only this issue in the notion listing the prerequisites for the announce.
The goal of the subissues is only to simplify the link issue-MR, so you can have short MR and use the auto-close feature.
The epics are not tracked in the board, so they don't pollute your view theoretically.
Should I understand that you think it's a bit overkill is this use-case?

[augustebaum]

Ah, so it was marked as "epic" specifically because we don't want it to pollute; that's fine, thanks for explaining.

I don't think it's overkill, especially because I know that writing one big issue is much easier than many little ones. I'm just wary that issues like these are never-ending, and I generally like closing issues.

[MarieS-WiMLDS]

issues like these are never-ending

It's definitely something that we will have to monitor so we don't end up with a huge list of epics!

[sylvaincom]

#611 fixed most of these issues, the reste is WIP

[sylvaincom]

Should we close this issue in favor of #627? cc @MarieS-WiMLDS

[MarieS-WiMLDS]

Can't we finish the last task before closing this issue? (the plotly graph one) It's not a huge issue, and Auguste is already working on it.

[sylvaincom]

Sure

[MarieS-WiMLDS]

all tasks are done --> we can close.