Broken link report #45
Replies: 6 comments 1 reply
-
Yes. a must have |
Beta Was this translation helpful? Give feedback.
-
Yes please. |
Beta Was this translation helpful? Give feedback.
-
This would be a huge time saver for us. We have over 1,000 pages of documentation and testing links individually is an impossible task. |
Beta Was this translation helpful? Give feedback.
-
As an option: it's possible to use |
Beta Was this translation helpful? Give feedback.
-
One thing we've done that helps a bit with this is set up a GitHub action that fails the build if it detects broken links in the docs. It's definitely not as clean as having a pretty UI to do this -- but as a temporary measure it might help some people. |
Beta Was this translation helpful? Give feedback.
-
👋 Hi everyone! ✨ We've just introduced a broken link detection feature, now available for users on our Pro plan. For more info on using this feature, please visit our docs. |
Beta Was this translation helpful? Give feedback.
-
What's your feature/idea?
I would like a dashboard or report that lists all broken links found within the GitBook documentation. It's nice that you can hover over a link to find out whether it's broken, but that's a tedious job if you have to manually check every link in on every page in your space.
The report should identify all broken links and provide a link to the page where the broken link resides. Ideally, you could enter the correct link from the dashboard and GitBook automatically fixes the broken link. This would be ideal when there are multiple instances of a broken link to a specific location.
What's your desired outcome?
What would you like to be able to do, if your idea came to life?
What's the impact of this for you?
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions