# Broken Links in Developer documentation

**URL:** https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399
**Category:** Development
**Created:** [April 10, 2022, 4:59pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399 "2022-04-10T16:59:45Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Fabian](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/f6c823/32.png) [@Fabian](https://discourse.paraview.org/u/Fabian)
#### Post date: [April 10, 2022, 4:59pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/1 "2022-04-10T16:59:45Z")

</div>

In `Documentation/dev/git/develop.md` in the section  
_1. (Optional but highly recommended.) [Register](https://open.cdash.org/register.php) with the ParaView project on Kitware’s CDash instance to better know how your code performs in regression tests. After registering and signing in, click on “All Dashboards” link in the upper left corner, scroll down and click “Subscribe to this project” on the right of ParaView._  
The link [https://open.cdash.org/register.php](https://open.cdash.org/register.php) is broken.

Following in  
_ParaView development uses a [branchy workflow](http://public.kitware.com/Wiki/Git/Workflow/Topic) based on topic branches._  
The link for branchy [http://public.kitware.com/Wiki/Git/Workflow/Topic](http://public.kitware.com/Wiki/Git/Workflow/Topic) is also broken

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 19, 2022, 10:40am UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/2 "2022-05-19T10:40:19Z")

</div>

Thanks. I’ve fixed the CDash link, but the wiki page still seems to be fine here at least.

[https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/5723](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5723)

---

<div class="post-metadata">

### Author: ![bagginstyrone](https://discourse.paraview.org/user_avatar/discourse.paraview.org/bagginstyrone/32/6405_2.png) [@bagginstyrone](https://discourse.paraview.org/u/bagginstyrone)
#### Post date: [May 21, 2022, 8:55am UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/3 "2022-05-21T08:55:39Z")

</div>

The link is still broken. Upon clicking on the link, I am getting “page not found”. Please do something about it.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 21, 2022, 7:17pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/4 "2022-05-21T19:17:54Z")

</div>

Which link? The ones pointed out in the OP are fine AFAICT.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 23, 2022, 3:43pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/5 "2022-05-23T15:43:44Z")

</div>

@ben.boeckel When I click on [https://open.cdash.org/register.php](https://open.cdash.org/register.php) using Firefox through the Sandia firewall, all I get in return is the words “Not Found”.

---

<div class="post-metadata">

### Author: ![Fabian](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/f6c823/32.png) [@Fabian](https://discourse.paraview.org/u/Fabian)
#### Post date: [May 23, 2022, 4:55pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/6 "2022-05-23T16:55:16Z")

</div>

The .php harms, without it works for me: [https://open.cdash.org/register](https://open.cdash.org/register)

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 23, 2022, 5:24pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/7 "2022-05-23T17:24:05Z")

</div>

Where are you all finding the link ending in “.php”? It has been removed in the `master` branch: [https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/git/develop.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/git/develop.md)

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 23, 2022, 5:36pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/8 "2022-05-23T17:36:42Z")

</div>

I don’t know where it originally came from, but in the first paragraph of this bug is the following:

![Screen Shot 2022-05-23 at 11.35.35 AM](https://discourse.paraview.org/uploads/default/original/2X/9/9ddea4fdd64058f0c6cf4a0a0ef93133eb855869.png)

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 23, 2022, 6:41pm UTC](https://discourse.paraview.org/t/broken-links-in-developer-documentation/9399/9 "2022-05-23T18:41:20Z")

</div>

Yep; I’m not concerned with the link in this thread (hopefully it doesn’t become the launching point for new ParaView developers 😉 ), but if there are other instances around, it’d be great to hear about them.

While we’re at it, maybe there’s some tool that can poke links in documentation and call out dead ones?
