Chore: Broken link check

Open
#51 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #52 by @adityawaghamare — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
documentation

Research direction

Start by combing through the documentation site and checking its links, as the issue does not name particular pages or a checking tool. Record any remaining broken links so they can be fixed; done means identifying stragglers, though the issue does not specify how to report them.

Written by the indexing model from the issue text.

Description

good first issue help wanted

Many of the links have been checked and fixed but there are stragglers.

Need people to comb through the site and identify any remaining broken links so they can be fixed.

Dominant language
C#
Stars
4
Forks
7
Avg merge
6h 10m
Merged PRs (30d)
4

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Redot-Engine/Redot-Documentation

All issues in Redot-Engine/Redot-Documentation

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.