\
**Category:** Dash Python\
**Created:** [February 1, 2019, 5:12am UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869 "2019-02-01T05:12:04Z")\
**Posts on this page:** 6\
**Page:** 1
**Author:**  [@halloleo](https://community.plotly.com/u/halloleo)\
**Post date:** [February 1, 2019, 5:12am UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/1 "2019-02-01T05:12:05Z")
The Dash reference documentation is pretty slow to navigate. Standalone files would be sooo much easier!
**Is there a way to download the reference documentation as HTML/Markdown files?**
ps: I have just [requested to add the Dash/Plotly reference](https://github.com/Kapeli/Dash-User-Contributions/issues/2199) to the [Dash](https://kapeli.com/dash) DocSets (The 2nd Dash stands here for the [Document viewer](https://kapeli.com/dash)!!!), but of course this only will happen, if the documentation is available in static HTML or markdown format…
---
**Author:**  [@tracek](https://community.plotly.com/u/tracek)\
**Post date:** [March 16, 2019, 8:08am UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/2 "2019-03-16T08:08:15Z")
Any news on this one?
Would be great to have the documentation offline such that people without good internet access (or travelling) could easily use Dash docs. I tried making a mirror of Dash docs, but to no avail due to JS content. Any recommendations?
---
**Author:**  [@chriddyp](https://community.plotly.com/u/chriddyp)\
**Post date:** [March 16, 2019, 3:07pm UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/3 "2019-03-16T15:07:16Z")
We have a PDF version of the docs here: [https://github.com/plotly/dash-docs/blob/master/pdf-docs/Dash\_User\_Guide\_and\_Documentation.pdf](https://github.com/plotly/dash-docs/blob/master/pdf-docs/Dash_User_Guide_and_Documentation.pdf)
---
**Author:**  [@mbkupfer](https://community.plotly.com/u/mbkupfer)\
**Post date:** [March 16, 2019, 3:31pm UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/4 "2019-03-16T15:31:02Z")
> [@tracek](#):
>
> Would be great to have the documentation offline
The team does a pretty phenomenal job with docstrings. If you use ipython or jupytere notebook, you can just add a question mark (?) at the end of term to get its docstring. Without those two, you can still do this with `help(python_object)`. This is much faster then the reference pages and works offline.
Just a few helpful examples of how I use this:
**Getting layout properties**
```python
In [1]: import plotly.graph_objs as go
In [2]: go.Layout.legend?
```
**Getting trace specific (i.e data) properties**
```python
In [3]: go.Bar.textposition?
```
**Getting available properties for dash core components**
```python
In [4]: import dash_core_components as dcc
In [5]: dcc.Graph?
In [6]: dcc.Tab?
```
---
**Author:**  [@halloleo](https://community.plotly.com/u/halloleo)\
**Post date:** [March 17, 2019, 12:34am UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/5 "2019-03-17T00:34:04Z")
That’s fantastic! For everyday look-ups of the API a standalone (HTML/Markdown or a least PDF) version of the [plotly API](https://plot.ly/python/reference/) would be great too.
But I can see this is _here_ in the Dash forum a bit off-topic…
---
**Author:**  [@tracek](https://community.plotly.com/u/tracek)\
**Post date:** [March 17, 2019, 9:34am UTC](https://community.plotly.com/t/refrence-documentation-as-plain-html-markdown-files/18869/6 "2019-03-17T09:34:50Z")
> [@mbkupfer](#):
>
> The team does a pretty phenomenal job with docstrings
And I certainly appreciate that! However, what I am looking for is a reference manual that presents a full overview of the available functionality rather than docs for a particular object. I’d like to use `dash` (`plotly` docs download just fine!) on an airplane or in remote places where internet access is very limited at best. In these places `lynx` could be your favourite internet browser :).
@chriddyp Thanks for sharing the docs! Any chance for you guys to regenerate the docs with latest-greatest API changes? I know it’s hardly high prio item, but if you could just consider it in future…