| commit | f4bac3ba7f4cb1ec053594821cb04e250913eb95 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Tue Jun 27 20:57:06 2023 -0400 |
| committer | Gopher Robot <gobot@golang.org> | Wed Jun 28 14:34:57 2023 +0000 |
| tree | 83af22c0474d4699382a9b671bde6c6fa09634d3 | |
| parent | aa6fa315fa2fd36c33ae7c46a7cbbbaf6ca58617 [diff] |
_content: add brand guidelines page: https://go.dev/brand In 2018 Google filed for a trademark on the new Go Logo (https://go.dev/blog/go-brand) and the word Go in the context of programming languages (more specifically "Computer programs and downloadable computer programs, namely compilers and reference libraries, that implement a statically typed, compiled computer programming language for use in developing, building and managing other software.") Since then we have not provided clear guidance about the permitted uses of the logo and the word mark Go. This commit adds that guidance, written by Google's trademark counsel and based on the Open Usage Trademark Guidelines 0.1.0 [1], adapted for the Go project. We also adapted some high-level text from the Python Software Foundation's excellent Trademark Usage Policy [2]. The guidance in this commit will be served at https://go.dev/brand and linked at the bottom of the menu under "Brand Guidance" where there is currently a link to the blog post. As it says in the new web page, in general, we want the word mark “Go” and the Go Logo to be used freely to refer to the Go programming language. It is explicitly not a goal to restrict the many excellent uses of the word Go in projects today. Instead the goal is to authorize those excellent uses properly, to avoid any confusion or doubt about whether they are proper. As it also says in the new web page, anyone with questions can email them to trademark@golang.org, which forwards to me and a few other people at Google, and we will do our best to answer them. [1] https://openusage.org/trademark-guidelines/ [2] https://www.python.org/psf/trademarks/ Fixes golang/go#58412. Change-Id: I82aca152a4f33140b6f05eacd256de0d0ee686e9 Reviewed-on: https://go-review.googlesource.com/c/website/+/506756 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@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.