commit | 7485a4ea009f3afbdd325a3da3ab6c88328353b1 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Thu Apr 14 16:29:55 2022 -0400 |
committer | Gopher Robot <gobot@golang.org> | Fri Apr 15 21:34:11 2022 +0000 |
tree | 85e1825c0bd8b837938b5865e932e3f8ec9fa38a | |
parent | 71c2d285b86a517fbac3e662cbf461d326846b4d [diff] |
all: update <meta> tags for social media Use the same og:description and description; Signal at least uses description. Use running gophers for the Twitter image for blog posts. Adjust the gophers5logo to move the Go where it won't get cut off on Google chat. Change-Id: I291ad7bf9ea58c0b6af3087213015196434d3163 Reviewed-on: https://go-review.googlesource.com/c/website/+/400434 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Ian Lance Taylor <iant@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.