Dashboards import feature update #794
Conversation
There was a problem hiding this comment.
Does it make sense to add a section here Importing a dashboard that just links to the Import docs?
There was a problem hiding this comment.
Now that Import refers to two formats, NeoDash and Dashboards, I think we should be more explicit about this throughout this page. My suggestion is to sprinkle NeoDash around where possible to avoid confusion.
There was a problem hiding this comment.
ideally we don't want to make people aware of NeoDash too much and point new users in the direction of a tool that will be deprecated. Perhaps we can call out NeoDash somewhere, but call it out as "legacy NeoDash dashboards"?
There was a problem hiding this comment.
so, keep it neutral for the general description?
we do have a subheading "Supported NeoDash reports", which could be changed to "Supported legacy NeoDash reports"
| In the dashboards tile page, use the more menu *[...]* of a dashboard tile and select **Delete**, then confirm. | ||
|
|
||
|
|
||
| == Exporting the dashboard JSON as a file |
There was a problem hiding this comment.
since we have a page for import that is seperate from 'managing dashboards', maybe we should also have an individual page for export? Or merge the import/export pages into one?
There was a problem hiding this comment.
since we have a page for import that is seperate from 'managing dashboards', maybe we should also have an individual page for export? Or merge the import/export pages into one?
it's not a lot of text - i added the actual description to the "Managing dashboards" page, and then referred to those in the "Import" page.
How about changing "Import" to "Import and export", and then make it clearer in terms of subheadings?
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
5 participants
No description provided.