_content/.well-known: revert register libera.chat project

These files were never served correctly but the libera.chat folks have
verified that the CL was merged (and presumably intended to be
displayed) and the project now has all the required permissions.

This reverts commit 7150aade441d21b06ee1a0634f02b985b0a67a95.

Change-Id: I74f10bd9899abaf8c189cc2fde2ac316ca584cd3
GitHub-Last-Rev: f2dca522865b97f4d74a604579f2c3f8b18aba8f
GitHub-Pull-Request: golang/website#61
Reviewed-on: https://go-review.googlesource.com/c/website/+/327251
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Trust: Heschi Kreinick <heschi@google.com>
Trust: Ian Lance Taylor <iant@golang.org>
1 file changed
tree: 39e77a297dbfc38dc14ab89673f4111588f74c3b
  1. .gitattributes
  2. .prettierrc
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. _content/
  10. blog/
  11. cmd/
  12. codereview.cfg
  13. content.go
  14. go-app-deploy.sh
  15. go.dev/
  16. go.mod
  17. go.sum
  18. internal/
  19. tour/
README.md

Go website

Go Reference

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.

JS/CSS Formatting

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.

Report Issues / Send Patches

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.