commit | 7fe5e1bf67352dcc963c4a663acdb283be7ff1c8 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Wed May 26 20:53:52 2021 -0400 |
committer | Russ Cox <rsc@golang.org> | Wed Jun 16 18:38:38 2021 +0000 |
tree | d0945529953df335ddb66c6556f89914f1c2a203 | |
parent | 96b571dae15d66409582a0791f6fdcabbd561dc9 [diff] |
blog: simplify app, stop being a submodule This app has a lot of history. App Engine used to require different code for local execution and running on App Engine, because the latter supplied func main. No longer. Unify all the code into a simpler single file. Also use the new x/website. (The old go.mod was pinning an older x/website from before we adopted fs.FS. Now that we have a backported io/fs, we can use the new x/website, which is what lets us get rid of the submodule boundary.) This brings blog in line with the other websites in this repo, which will help smooth the eventual merge. Change-Id: Ibe95674ac6765c15bb82a82dc52845a2377cebf7 Reviewed-on: https://go-review.googlesource.com/c/website/+/323894 Trust: Russ Cox <rsc@golang.org> Reviewed-by: Jamal Carvalho <jamal@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.