-
-
Notifications
You must be signed in to change notification settings - Fork 544
[python docs] Plotly Fundamentals reorg #1360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I also think the current docs in Add custom controls (Custom buttons, Sliders and Dropdown menus from) can go to the chart studio section as well since ipywidgets and FigureWidgets is the better/easier option offline. And everything currently in fundamentals aside from the 2 orca docs, the config doc and the jupyter notebook doc (although this one does have a few chart studio related sections) could be moved to chart studio. |
When I was looking at other docs that would work best in fundamentals (from the current layout and style sections) this is the list i cam up with: Axes, subplots, multiple axes, graph sizing, setting the titles, legends, text and annotations, text and font styling, hover text, Images, shapes, colorway, and one of the three colorscales docs. I also figured that since the above would break apart the layout section we could consolidate the 3D specific docs that are currently in the layout section into the 3D section. |
I'm good with making this change now. @cldougl thoughts? |
Related: any files impacted by the changes in https://github.com/plotly/plotly.py-docs/issues/16 should go into the "chart studio" bucket :) |
I'm good with this change! |
Great! @michaelbabyn this spreadsheet has certain pages tagged "chart studio" or "framework" that might be good candidates for getting shunted into Chart Studio or Fundamentals or an eventual "Advanced" category for the non-fundamental-yet-still-framework ones :) |
Given that the plan for the v4 docs is to use the current framework for final deployment, it makes sense to start the structural reorg in this repo now!
There are two related things I'd like to tackle first:
@michaelbabyn and I have been chatting about this and I'd love to workshop a list of the changes we could make here... If you could share what you've thought about so far Michael that would be helpful :)
The text was updated successfully, but these errors were encountered: