# Child web pages in flows.nodered.org listings

**URL:** <https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217>\
**Category:** General\
**Created:** [11 August 2019 14:18 UTC](https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217 "2019-08-11T14:18:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kolban](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kolban/32/10366_2.png) [@kolban](https://discourse.nodered.org/u/kolban)\
**Post date:** [11 August 2019 14:18 UTC](https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217/1 "2019-08-11T14:18:17Z")

</div>

If one creates a README.md in ones Github project that is then published to npm, it shows up in the listing of available nodes. For example:

> **[node-red-contrib-google-cloud](https://flows.nodered.org/node/node-red-contrib-google-cloud)**
>
> Node-RED nodes for Google Cloud Platform

However, if one includes sub-page links in the README.md, these show as broken links when clicked in the Node-RED catalog. See above link (at bottom of page) for an example. Is there a recipe one should use to prevent or avoid these broken links? I was thinking of putting in absolute URLs to the Github files but that feels a little less than optimal.

---

<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:** [12 August 2019 12:39 UTC](https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217/2 "2019-08-12T12:39:28Z")

</div>

I think that you've used relative links for those which means that, when you access the page from flows, the links also point to flows and that isn't valid. The same will happen if you view the page on the npm site.

The only way around that is to use absolute URL's with the GitHub prefix. A common issue and not much else anyone can do about it.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 August 2019 13:10 UTC](https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217/3 "2019-08-12T13:10:27Z")

</div>

> [@TotallyInformation](#):
>
> A common issue and not much else anyone can do about it.

Not 100% true - we do _try_ to spot relative urls when they are used to link to images and we automatically rewrite them to the github hosted url. It isn't 100% perfect, but seems to catch the most common cases.

I guess this would be a case of needing to do the same for links.

Here's where we do it for images - [flow-library/routes/nodes.js at 4dc020e100a8e03efe766e7bb9e234908a6c8c8d · node-red/flow-library · GitHub](https://github.com/node-red/flow-library/blob/4dc020e100a8e03efe766e7bb9e234908a6c8c8d/routes/nodes.js#L94-L103) .

If anyone felt up to the task to adding the necessary code for `<a>` tags, then PRs are welcome.

---

<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:** [12 August 2019 14:14 UTC](https://discourse.nodered.org/t/child-web-pages-in-flows-nodered-org-listings/14217/4 "2019-08-12T14:14:13Z")

</div>

I did wonder whether you'd want to do that and now you've mentioned it, I vaguely remember you saying something about that in the past.

Anyway, good work as always.