Patch 7

[SylwiaOliwia2]

Bolded phrases and additional explanations in the "method" section. The previous version can be misleading to non-heavy users.

• I've seen the doc/README.md file
• This change runs in the current version of Plotly on PyPI and targets the doc-prod branch OR it targets the master branch
• If this PR modifies the first example in a page or adds a new one, it is a px example if at all possible
• Every new/modified example has a descriptive title and motivating sentence or paragraph
• Every new/modified example is independently runnable
• Every new/modified example is optimized for short line count and focuses on the Plotly/visualization-related aspects of the example rather than the computation required to produce the data being visualized
• Meaningful/relatable datasets are used for all new examples instead of randomly-generated data where possible
• The random seed is set if using randomly-generated data in new/modified examples
• New/modified remote datasets are loaded from https://plotly.github.io/datasets and added to https://github.com/plotly/datasets
• Large computations are avoided in the new/modified examples in favour of loading remote datasets that represent the output of such computations
• Imports are plotly.graph_objects as go / plotly.express as px / plotly.io as pio
• Data frames are always called df
• fig = <something> call is high up in each new/modified example (either px.<something> or make_subplots or go.Figure)
• Liberal use is made of fig.add_* and fig.update_* rather than go.Figure(data=..., layout=...) in every new/modified example
• Specific adders and updaters like fig.add_shape and fig.update_xaxes are used instead of big fig.update_layout calls in every new/modified example
• fig.show() is at the end of each new/modified example
• plotly.plot() and plotly.iplot() are not used in any new/modified example
• Hex codes for colors are not used in any new/modified example in favour of these nice ones

[nicolaskruchten]

Thank you so much for all these PRs to our documentation! The CI failures you're seeing here can either be ignored for this PR or removed by rebasing onto doc-prod now :)

[SylwiaOliwia2]

@nicolaskruchten thank you. I think I managed to rebase it (my first rebase). If not - feel free to correct me :)
Should I create another pull request?

[nicolaskruchten]

OK so it looks like your rebase worked but not on top of the latest changes. You can try something like:

git checkout doc-prod
git pull
git checkout patch-7
git rebase doc-prod
git push -f

I suspect your local copy of doc-prod does not include the commit which fixes the CI, so the first two lines will be needed to fix that first and then the rebase should proceed normally.

Let me know if you run into any trouble!

[SylwiaOliwia2]

Did it, but please double-check :) I've been using Edit this page on Github, which created branch from my not updated fork.

[emmanuelle]

thank you very much @SylwiaOliwia2 , merging ! 💃