go.dev/_content/js: delete h2 manipulation in misc.js

It's unclear what “correct scroll” means here, but it's definitely
incorrect to blow away any HTML (such as links) in every h2
and replace it with the text-only representation of the original h2.
Delete that code. If we figure out what this means, we can look
for a better way to solve this problem (probably scroll-margin-top?).

Also, make it clearer that the stickyNav setup is a no-op without a sticky nav.

Preparation for the golang.org -> go.dev move.

Change-Id: Ib8930a4e3aba688d645f689d3c2ee90b3e09229f
Reviewed-on: https://go-review.googlesource.com/c/website/+/362499
Trust: Russ Cox <rsc@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
1 file changed
tree: 4cb9fc9db742f9f89076923ec2c2d5f00bbd5d3e
  1. _content/
  2. cmd/
  3. go.dev/
  4. internal/
  5. tour/
  6. .gitattributes
  7. .prettierrc
  8. AUTHORS
  9. codereview.cfg
  10. content.go
  11. CONTRIBUTING.md
  12. CONTRIBUTORS
  13. go-app-deploy.sh
  14. go.mod
  15. go.sum
  16. LICENSE
  17. PATENTS
  18. README.md
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org and go.dev web sites.

Content is in _content/ (golang.org), go.dev/_content/ (go.dev), and tour/ (tour.golang.org). Server code is in cmd/ and internal/.

To run the combined golang.org+go.dev 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.

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.