go.dev/_content/blog: update build constraints in fuzz-beta post

CL 351569 updated this blog post to use gotip without arguments,
since the dev.fuzz branch has been merged to the main branch and
is slated to be included in Go 1.18.

Update the build constraint in the shown example accordingly,
since the gofuzzbeta constraint is no longer set as of CL 351118.
Suggest the use of a go1.18 build constraint instead.

While here, also update to the newer go install @latest
syntax for downloading the gotip command, for reasons
similar to what's described in CL 346091.

For golang/go#47037.
Updates golang/go#48080.

Change-Id: Icbf3d3ad5ef5532063ca3e093eed330f7ea0c0d9
Reviewed-on: https://go-review.googlesource.com/c/website/+/353430
Website-Publish: DO NOT USE <dmitshur@google.com>
Trust: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Jay Conrod <jayconrod@google.com>
Reviewed-by: Katie Hockman <katie@golang.org>
1 file changed
tree: f389bf216b3664bbd4881ae22f5c9fe07590647e
  1. .gitattributes
  2. .prettierrc
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. _content/
  10. cmd/
  11. codereview.cfg
  12. content.go
  13. go-app-deploy.sh
  14. go.dev/
  15. go.mod
  16. go.sum
  17. internal/
  18. tour/
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org and go.dev web sites.

Content is in _content/ (golang.org), go.dev/_content/ (go.dev), and tour/ (tour.golang.org). Server code is in cmd/ and internal/.

To run the combined golang.org+go.dev server to preview local content changes, use:

go run ./cmd/golangorg

The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)

Each command directory has its own README.md explaining deployment.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

The version of prettier used is 1.18.2.

It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.