# Build /docs/ into the server

**URL:** <https://discourse.nodered.org/t/build-docs-into-the-server/49083>\
**Category:** Feature Requests\
**Created:** [29 July 2021 14:52 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083 "2021-07-29T14:52:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nagy](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@nagy](https://discourse.nodered.org/u/nagy)\
**Post date:** [29 July 2021 14:52 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083/1 "2021-07-29T14:52:56Z")

</div>

Currently when going to the servers local `/docs/` route path (e.g. [http://127.0.0.1:1880/docs/](http://127.0.0.1:1880/docs/))  
I get:

```auto
Cannot GET /docs/

```

Could we make a copy of the contents of `https://nodered.org/docs/` also available  
under the local `/docs/` route? I see several advantages:

- The docs will be available even when you are offline, for example in a  
basement when there is almost no WiFi connection or in poorer countries where  
a data plan is more expensive.

- The version of the delivered `/docs/` is always matched with the version  
installed. This will allow users to run a Node-RED version for a long time  
without having to worry that the upstream homepage may decide to remove some  
docs because the corresponding version is too old.

One downside is that the delivered server is a bit larger in size.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [29 July 2021 17:07 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083/2 "2021-07-29T17:07:35Z")

</div>

If you want the docs offline, why not clone the repository?

---

<div class="post-metadata">

**Author:** ![nagy](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@nagy](https://discourse.nodered.org/u/nagy)\
**Post date:** [29 July 2021 17:18 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083/3 "2021-07-29T17:18:00Z")

</div>

Oh, I didn't know about [GitHub - node-red/node-red.github.io: Node-RED Site](https://github.com/node-red/node-red.github.io) , good to know , thank you.

I guess its not that accessible to non-technical people since you need to know  
how to build it with Jekyll but it is certainly better than I thought.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [29 July 2021 17:56 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083/4 "2021-07-29T17:56:00Z")

</div>

Yes, well personally I dislike Jekyll intensely and there is a long list of issues regarding Jekyll on my blog. But it was the first tool to be usable with GitHub pages I think. I've tried it and it failed in so many ways I completely redid my blog in Hugo.

The technical docs for uibuilder are done using Docksify and so available both as GitHub pages and as a local web within Node-RED 😀 Not sure how well that would scale though - I may find out since I've done the same with our IT Standards site at work.

Of course, there is little enough resource to develop Node-RED so I'm certainly not going to suggest time is spent on reworking the docs site. Though maybe Nick and Dave wouldn't mind if someone committed to doing the changes. Who knows.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [27 September 2021 17:56 UTC](https://discourse.nodered.org/t/build-docs-into-the-server/49083/5 "2021-09-27T17:56:24Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.