Patrice Chalin
Patrice Chalin
@ngrayluna - can you give this PR's preview a try? It is an initial partial solution: - #2343 It seems better. **Edit**: I added some JS, similar to what @KivalovIlya...
Actually, I'd say that this issue is fixed by: - #2343 I'll consider further improvements outside the scope of this issue. All: if you have any further feedback, share here...
Is https://jaeger.readthedocs.io still supported? ```console $ curl -sI https://jaeger.readthedocs.io | grep HTTP HTTP/2 302 $ curl -sI https://jaeger.readthedocs.io/en/latest/ | grep HTTP HTTP/2 404 ```
How do you propose editing the parts of the docs that refer to `jaeger.readthedocs.io`? Just remove the prose that refers to it? That link is also used in many config...
Examples: - https://opentelemetry.io/search/?q=histogram - Google Search + Kapa's Ask AI - https://kubernetes.io/search/?q=pod - https://grpc.io/search/?q=tcp
> ... Is it possible to restrict it to only work on the latest versions? Yes we can address that via: - #910
@yurishkuro - would it make sense to redirect `/docs/2.*/operator` and `/docs/operator` to `/docs/latest/kubernetes`?
How to you want to handle the `client-libraries` 404s? Should we: 1. Redirect to some other target, such as either of: a. https://www.jaegertracing.io/docs/1.63/client-libraries/, the last version for which the page...
> > Redirect to ... the last version for which the page existed > > sounds good, Ok, I'll do that. > but only from the other 1.x pages. From...
Also, note the following bug. I'm not sure if it was introduced by this PR or not: - #5588