commit | d8909ee5a6512dac2fb8cba0a99bc69ab65d9ad1 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Thu Feb 25 09:47:14 2021 -0500 |
committer | Russ Cox <rsc@golang.org> | Wed May 26 13:31:17 2021 +0000 |
tree | 484096472dc15243d460f785d3c981fc48a44587 | |
parent | 538edd84ebc005ae335fe1f26a8202e4d023eaff [diff] |
all: remove Path metadata-based redirects Back when the entire site had to live in $GOROOT/doc, we needed some way to specify content that was served from URLs outside of golang.org/doc, so we added the ability for a doc to declare its own URL (the Path metadata). That meant the file system layout did not match the URL layout. That meant the content for any particular URL could be anywhere in the file system. That meant the entire file system had to be scanned to serve a URL. That meant an index of the file system had to be built and updated. Now that we have a file tree (_content) for the whole of golang.org, we can move files to make the file system layout match the URL space. Then each URL can be served by just reading the right file. Then the index and its updater can be deleted. And now if you want to edit /doc/gdb it's obvious which file to open. Change-Id: I3357f275e61a31c8de3091af580cac80753e71a4 Reviewed-on: https://go-review.googlesource.com/c/website/+/296383 Trust: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
This repo holds content and serving programs for the golang.org web site.
Content is in _content/. Server code is in cmd/ and internal/.
To run the 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/ directory.)
Each command directory has its own README.md explaining deployment.
This repository uses prettier to format JS and CSS files.
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
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.