📣 Updated Documentation - Looking for feedback

Hello everyone – :wave:

After a couple years of the same look & feel, I’m excited to share that the Dash Documentation is getting a makeover! Check it out at: https://dash.plot.ly

The first changes landed tonight:

  1. The visual style has been updated to match our new look (Read more: Plotly has a new look!)

  1. We added a nice new sidebar that shows the hierarchy of pages

  2. The sidebar is filterable and we’ve put some care into it:

    1. It’s focused by default when you open up the page. So, if you want to just quickly look up the properties for e.g. dcc.Dropdown, then you can 1) open https://dash.plot.ly, 2) Starting typing immediately (no need to use your mouse or cursor), 3) Press enter to view the top result. No mouse required! It’s very fast.
    2. We’ve indexed the sidebar so that you can search all of the component properties. For example, if you are trying to find an example of the property selected_row_ids, you’ll get this result:
  3. There is a persistent page menu bar on the right hand side that shows the main sections of each documentation page.

  4. In many areas, the visual style is more readable: darker fonts with higher contrast and bolded text. In particular, you’ll notice it on the reference pages that show all of the properties for a given component:

We still have lots of work to do here and we’ll update the forum with our progress. In the coming weeks, we’ll be adding:

Is there anything else that you would like to see? Please let us know by commenting below. In the meantime, I hope that you enjoy the new look & the latest features.

I hope everyone is staying safe & healthy out there :heart:



I’m not a huge fan of PHP, but I love their community examples section. Everytime I have needed to do something, there is an example written by a member of the community that is close enough to what I am trying to do that I can figure it out with minimal effort and usually just a few modifications.

I find Python, Pandas, and Dash to be lacking in these areas. They will often have examples, but it will only cover 10% of the use cases, and so you need to guess about the correct syntax of what you’re trying to do and hope that it’s correct. This leads you through a trial and error process that takes time, and searching stack overflow for answers which is less than ideal. The community forum here is great and very responsive, but I shouldn’t need to search it for examples of what I’m trying to do; these should exist as part of the documentation itself.

I’d really like to see a community examples section, moderated by the Dash team, at least for their API reference section. I think it would help the Dash team as well, because you would better understand how you users are using your product, which will sometimes be in ways that you wouldn’t have thought of. You can review the top-rated workaround examples and put streamlining those as features on the roadmap for future Dash versions.


:partying_face: Wahoo!

Love the general overhaul.

Only comment is that some of styling is a little cramped. e.g.the code sometimes bleeds in to the text around it. Perhaps a little more spacing and use of background colours to clearly separate different types of information?

1 Like

Thanks for the feedback everyone! It is very much noted.

On content updates, we just published some new chapters on callbacks (notably clientside callbacks) - Feedback welcome here: Dash Callbacks documentation improvements (including clientside examples!)

Great content! Thanks for this!

I second with the previous user’s comment that the page looks cramped. The help docs for Plotly however looks a tad cleaner. I personally am not a fan of the font family used - it seems to work fine for the Plotly homepage with little text, but not a text-dominant page- but that’s probably just me.

Plus also this line is odd:

The plotly docs doesn’t have this.

Selecting a dropdown from the sidebar creates this blue box:

Personally would prefer to entirely hide it or highlight it like how you do with the sub-headings.

Love the flexibility of the sidebar.

Love Dash overall- its fast evolving into an even greater package!

I’ve been using the new documentation a lot more, and I’ve found it much easier to find stuff! The search is really helpful, and it’s laid out well. Thanks!

1 Like

I found an issue in the new documentation. Additionally, another issue arose while trying to report the issue:

Steps to Reproduce #1

  1. Find an issue in documentation, e.g., https://dash.plotly.com/urls
  2. Look for a link or button that says edit or report errors or submit pull request

Actual Results
No such button

Expected results
A link to github where the documentation is hosted, in order to submit a pull request to fix the documentation.

Here’s the actual issue I found:

Steps to Reproduce #2

  1. Go to https://dash.plotly.com/urls
  2. Try to implement a Multi-Page app based on the “flat project layout” code examples

Actual Results
ImportError: cannot import name 'layout1' from layouts …

Expected Results
No error.


In index.py:

from layouts import layout1, layout2
    if pathname == '/apps/app1':
         return layout1

This worked in the non-flat example, where layout1 and layout2 are files (modules). It fails in the flat example because layouts is a single file, defining layout1 and layout2 as variables.