|author||Dmitri Shuralyov <email@example.com>||Tue Mar 22 23:09:11 2022 -0400|
|committer||Dmitri Shuralyov <firstname.lastname@example.org>||Wed Mar 23 12:42:45 2022 +0000|
_content/blog/intro-generics: apply minor touch-ups The blog post wasn't listed at go.dev/blog because its metadata was missing a '---' line at the bottom. Add it. (It was showing up at go.dev/blog/intro-generics only, with metadata visible as plain text.) Fix the URL of the embedded YouTube video. Point to the moved location of the constraints package in x/exp. Replace absolute go.dev links with relative ones, so they work for more users (at golang.google.cn/blog, and so on). Shorten the links to proposal slightly, using HEAD to refer to the default branch. Change-Id: Ie78838a50bb50843e6c242781252d5347063e361 Reviewed-on: https://go-review.googlesource.com/c/website/+/394994 Run-TryBot: Dmitri Shuralyov <email@example.com> Trust: Dmitri Shuralyov <firstname.lastname@example.org> TryBot-Result: Gopher Robot <email@example.com> Reviewed-by: Eli Bendersky <firstname.lastname@example.org>
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org 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.
It is encouraged that all JS, TS, and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
<script type="module" src="/ts/filename.ts">
Write unit tests for TypeScript code using the jest testing framework.
./npx jest [TestPathPattern]
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
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.