Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken link in docs #324

Open
Strooom opened this issue Jan 17, 2022 · 1 comment
Open

Broken link in docs #324

Strooom opened this issue Jan 17, 2022 · 1 comment
Assignees
Labels
topic: documentation Related to documentation for the project type: imperfection Perceived defect in any part of project

Comments

@Strooom
Copy link

Strooom commented Jan 17, 2022

When navigation to the rules documentation (https://github.com/arduino/arduino-lint/blob/main/docs/rules.md), clicking on libraries, it leads to https://github.com/arduino/arduino-lint/blob/main/docs/rules/library.md but this gave an Error 404 on github

@per1234 per1234 added topic: documentation Related to documentation for the project type: imperfection Perceived defect in any part of project labels Jan 17, 2022
@per1234 per1234 self-assigned this Jan 17, 2022
@per1234
Copy link
Contributor

per1234 commented Jan 17, 2022

Hi @Strooom. Thanks for your interest in the Arduino Lint rule documentation.

The reason this link is broken is because this library.md file is programmatically generated from the Arduino Lint code.

This content is intended to be read on the documentation website here:
https://arduino.github.io/arduino-lint/dev/rules/

I considered the idea of storing the generated documentation in the repository alongside the code when I started working with the system in the Arduino CLI repository, but I was unsure if it would be worth the effort because the documentation will need to be updated on every code change that affects it. Since that time, we added a documentation versioning system and never had any reports until now of people hitting those broken links, even though Arduino CLI is a very popular project. That made me feel like it was not so much needed.

But perhaps there is a way to more effectively communicate that the files under docs are only the source code of the website content. MkDocs expects that all the Markdown files under docs are meant to be part of the website, so adding a README.md to the folder to contain the explanation would cause the website validation to fail. But a README.txt could be used instead to avoid that problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

2 participants