Comments (4)
For what it's worth, there used to be a literal "broken links" page on the dev site that would aggregate these. I think it has been disabled at some point.
Anyway, I think these should be addressed basically on a case-by-case basis. I checked a couple of links quickly:
- https://docs.raku.org/type/int - this used to point at the documentation of uppercase Int which I think is wrong; the link should simply be removed or refer to the native type documentation
- https://docs.raku.org/type/Signal - this simply never existed on the old site (no archive.org snapshots); should be removed
- https://docs.raku.org/language/ - this used to redirect to https://docs.raku.org/language which I believe to be the correct behavior, the server rules should be adapted
- https://docs.raku.org/language/Attributes - never existed, should be removed
- https://docs.raku.org/language/independent-routines - this moved URL for some reason, now it's https://docs.raku.org/type/independent-routines; I think it should go back under language/
- I'd assume that
language/language/...
links have always been wrong and simply should be fixed; same forlanguage/type/...
links - https://docs.raku.org/syntax/proto - this used to be generated, now it isn't; probably it should be
from doc.
Oh yeah, related to reporting broken links... Raku/doc-website#72
from doc.
The broken link page was not included on doc-website because my CSS colour choices are too garish!!! :)
The link report is generated on my new-raku deployment site
A number of the errors are due to changes between the way internal links are generated. I shall be working on this over the next few days.
from doc.
Appreciate the report, we'll work off of @finanalyst's page
from doc.
Related Issues (20)
- RAKUDO_LINE_EDITOR doesn't mention Terminal::LineEditor HOT 2
- pass new test xt/rakudoc-types.rakutest HOT 1
- Asking for feedback
- Track references to non core modules
- compilation example cleanup HOT 2
- Tone of 5-6 articles HOT 2
- Standardize links for methods in docs.
- xt/check-signatures.t doesn't understand class $.variables
- xt/check-signatures.t to report on missing docs
- 6.e updates
- Fix all broken links HOT 9
- Weird .head example
- Avoid links of form L<#Thing>
- checklist for 2024.05
- Need a better example of formatting code L<> (Links), particularly for links to another pod document
- Add practical examples of using Allomorphs, e.g., changing a Str Allomorph to an Int.
- Should NYI features be documented? HOT 4
- Stubs as operators
- Recent changes fail xt/ X<> test HOT 3
- Don't use Markdown as our source docs.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from doc.