|author||Jonathan Amsterdam <firstname.lastname@example.org>||Mon Nov 13 11:33:24 2023 -0500|
|committer||Jonathan Amsterdam <email@example.com>||Wed Nov 15 11:30:05 2023 +0000|
_content/doc: change relnote definition lists to headings Since 1.7, the "Minor changes to the library" second has used a definition list to describe the changes to each package. Use level 4 headings instead. This removes one feature that is not CommonMark-compliant. It paves the way for using a CommonMark-compliant Markdown parser and renderer for both display and generation of release notes. For golang/go#64169. Change-Id: I2327499971a2db4eee06ef35e3e41cd0d2f953b3 Reviewed-on: https://go-review.googlesource.com/c/website/+/541976 Reviewed-by: Dmitri Shuralyov <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <email@example.com> Run-TryBot: Jonathan Amsterdam <firstname.lastname@example.org> TryBot-Result: Gopher Robot <email@example.com>
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.