content/doc: add an explanatory preamble to Effective Go
Explain that Effective Go is not a living document.
No changes other than one new paragraph in the
introduction.
Fixes golang/go#49937
Update golang/go#28782
Change-Id: I615e48df56313e3d91e8b88b139159f64900db7e
Reviewed-on: https://go-review.googlesource.com/c/website/+/380634
Reviewed-by: DO NOT USE <iant@google.com>
Trust: Michael Knyszek <mknyszek@google.com>
diff --git a/_content/doc/effective_go.html b/_content/doc/effective_go.html
index 9b4eea2..6104d3a 100644
--- a/_content/doc/effective_go.html
+++ b/_content/doc/effective_go.html
@@ -34,6 +34,24 @@
should read first.
</p>
+<p>
+Note added January, 2022:
+This document was written for Go's
+release in 2009, and has not been updated significantly since.
+Although it is a good guide to understand how to use the language
+itself, thanks to the stability of the language, it says little
+about the libraries and nothing about significant changes to the
+Go ecosystem since it was written, such as the build system, testing,
+modules, and polymorphism.
+There are no plans to update it, as so much has happened and a large
+and growing set of documents, blogs, and books do a fine job of
+describing modern Go usage.
+Effective Go continues to be useful, but the reader should
+understand it is far from a complete guide.
+See <a href="https://github.com/golang/go/issues/28782">issue
+28782</a> for context.
+</p>
+
<h3 id="examples">Examples</h3>
<p>
