commit | 32a21a08d063d0672b02f3d384c206f05b552dac | [log] [tgz] |
---|---|---|
author | Eli Bendersky <eliben@golang.org> | Wed Jul 05 05:33:34 2023 -0700 |
committer | Gopher Robot <gobot@golang.org> | Thu Jul 06 17:51:27 2023 +0000 |
tree | a8902bdf6fee00c55058848e9f0818c7805625da | |
parent | ea9861c44c08bb451262c252f8a18862fa25e6bc [diff] |
doc/faq: update out-of-date mention of gollvm gollvm is mentioned elsewhere in the FAQ too, but this specific mention seems out-of-date now given the state of the project. Change-Id: I5be12faeaf9ea445fc4c28eecb7583fda0adb457 Reviewed-on: https://go-review.googlesource.com/c/website/+/507959 Reviewed-by: Than McIntosh <thanm@google.com> Auto-Submit: Eli Bendersky <eliben@google.com> Run-TryBot: Eli Bendersky <eliben@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Eli Bendersky <eliben@google.com> Reviewed-by: Cherry Mui <cherryyz@google.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.
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.