I know this is at least somewhat orthogonal to the points you’ve made, but 
perhaps it would be best to standardize how “warning” messages are rendered in 
documentation. For example, the “unstable: may change without warning” messages 
are quite useful, but I have no idea how I’d render those in my own 
documentation.

> On Oct 12, 2015, at 5:01 PM, Neil Van Dyke <[email protected]> wrote:
> 
> There's still a problem of people stumbling upon deprecated stuff in the 
> Racket manuals, and going to a lot of trouble to use it without realizing 
> that it's deprecated.
> 
> For a very quick fix, how about appending "[DEPRECATED]" to certain manual 
> titles, as an easy way of marking each page of the manual?
> 
> For example, the title: "PLaneT: Automatic Package Distribution"
> is changed to: "PLaneT: Automatic Package Distribution [DEPRECATED]"
> 
> This could also be done to individual "compatibility" chapters/section 
> headers of otherwise non-deprecated manuals.
> 
> Also, move things like the PLaneT manual to the "Legacy Languages and 
> Libraries" category.  Maybe append "[DEPRECATED]" to the titles of the other 
> manuals in that category, as well.
> 
> Neil V.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/racket-dev/561C49EF.3010805%40neilvandyke.org.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/842B8014-65AB-4D62-8380-46F60E7756A1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to