commit | 4689eb36e1207eb01b795c0504ad694c67766708 | [log] [tgz] |
---|---|---|
author | Ian Lance Taylor <iant@golang.org> | Thu Jun 20 17:18:18 2024 -0700 |
committer | Gopher Robot <gobot@golang.org> | Mon Jun 24 16:47:42 2024 +0000 |
tree | bca7f1c38d19b80eed3a3c2ff118aa0c168092d6 | |
parent | df09bd3dcd46e2aeb53de03cc30edcab9d938976 [diff] |
_content/doc: convert faq from HTML to Markdown Change-Id: Ie62e9132520d6fc08e90f99160f4696b60db9670 Reviewed-on: https://go-review.googlesource.com/c/website/+/593875 Reviewed-by: Joedian Reid <joedian@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Ian Lance Taylor <iant@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.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.
This repository uses eslint to format JS and TS files, and stylelint to format CSS files.
See also:
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.
./npm install
./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
TypeScript files served from _content are transformed into JavaScript. Reference .ts files in html templates as module code.
<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.