Consider adding a redirect system for language feature specifications similar to Flutter design docs #5079
Labels
a.language
Relates to the Dart language tour
co.proposal
Community ask to change an approach or process for docs.Dart.dev
e2-days
Can complete in < 5 days of normal, not dedicated, work
fix.link
Adds, changes, or removes a link to a page
from.team
Reported by Dash docs team member
infra.structure
Relates to the tools that create dart.dev
p3-low
Valid but not urgent concern. Resolve when possible. Encourage upvote to surface.
Currently it's a bit awkward to link to feature specifications on the language repository. When they are being worked on, then accepted, then released, their link changes every time. Beyond that, the links are long and definitely not memorable.
Developers often love to see what's coming, learn from the specifications, track them, share them, etc. We also use these links occasionally on dart.dev.
We should consider tracking redirects that we handle updating, so we can have a persistent link to link to from anywhere, sort of similar to Flutter design docs that live at
flutter.dev/go/
.This could be done on this repository, but it would probably be better on the language repository's
spec.dart.dev
Firebase instance, which would allow atomic updates of the redirects as the documents move. Then we could add a single redirect fromdart.dev
tospec.dart.dev
for those design docs.If we managed this in
dart-lang/language
, the workflow would look like:dart-lang/language
'sfirebase.json
under a name/feature-spec/class-modifiers
or something similar.\cc @MaryaBelanger
The text was updated successfully, but these errors were encountered: