In the orange banner, to do that modify the sentence in the mkdocs.yml file

The following options are now available:

• dataPath
• logPath
• logFile

• Rename --validators-key-file to --validators-unencrypted-key-file
• In a future release the --eth1-enabled option will be removed. ETH1 will be enabled when --eth1-endpoint is provided and otherwise disabled.
• Add --rest-api-host-whitelist

Update Teku readme to link to docs and remove outdated information

Add a description for the response object for a call made by beacon/block

I just did a search on Teku docs site for "whitelist" and no results show even though the content is there - does this mean something needs to be updated? (Other search terms eg "withdrawal" work) https://docs.teku.pegasys.tech/en/latest/Reference/CLI/CLI-Syntax/#rest-api-host-whitelist

This content was created before we had any testnets available. And users coming to these instructions may get confused.

Suggest we remove this since it's covered in the "Connect to a testnet" instructions. Also, much work will
go into fixing this area, see https://docs.google.com/document/d/14fl5LGA6abpSETxdRQLzVjWl0_5cpk5Us5tz3O6KVhQ/edit#

https://docs.teku.pegasys.tech/en/latest/HowTo/Get-Started/Register-Validators/

The Teku configuration file is now YAML formatted.

Update the the Config option in the CLI options topic and add conceptual or how-to information.

Similar to https://besu.hyperledger.org/en/latest/

Document the CLI options used to configure Eth2Signer <> Teku.

PR: Consensys/teku#2098

See Consensys/teku#1672

For reference see https://consensys.slack.com/archives/C014L7NGS2G/p1590797667028900

From @ajsutton:

Production deployments shouldn’t be using ‘both’ logging. For a production deployment either ‘console’ and then have something like systemd handle the output or at minimum ‘file’ logging is strongly recommended.
Actually @pliny-team would be really handy to add something to the docs on this to make clear that by default status updates go to the console but most of the information goes to the log file.

See https://bintray.com/consensys/pegasys-repo/teku

PR: Consensys/teku#2122

Altona is now the default named network.

Additionally, remove the notes about using the 0.12.1-integration branch.

The subcommand has two additional subcommands generate and register

See https://app.zenhub.com/workspaces/team-ziz-5e45dedb5ca1523669f3c3a0/issues/pegasyseng/teku/2113

Teku currently has CLI options to enable metrics. This requires some conceptual information.

Similar to the Besu one - https://besu.hyperledger.org/en/stable/HowTo/Monitor/Logging/

Create a diagram. For example, see https://besu.hyperledger.org/en/latest/Concepts/ArchitectureOverview/

Document that we need to set the --network option when sending the deposit transaction.

See Consensys/teku#1754

Use the enableSwagger [beaconrestapi] setting to disable/enable the endpoint.

Defaults to true

See https://app.zenhub.com/workspaces/team-ziz-5e45dedb5ca1523669f3c3a0/issues/pegasyseng/teku/2088

Describe how to use the teku validator generate and teku validator register subcommands to generate/register validators and make deposits to an Eth1 deposit contract.

We do not need to explicitly set boolean options to true.

For example --log-color-enabled[=]

Teku can now connect to an Infura Eth 1.0 endpoint. E.g
--eth1-endpoint=https://goerli.infura.io/v3/<your-api-key>)

Additionally, make it more clear to the user that they do not need to install Besu to run a Teku validator.

See https://docs.google.com/spreadsheets/d/1E6Gkl9osc0Q5vx08boG-XvARYmCuGX_lbgq4vALhCnA/edit#gid=0

We’re in a slightly tricky period transitioning between beacon chain spec versions for Teku. It may be worth adding a note to our docs to indicate that:

• master branch and v0.11.x builds are compatible with the 0.11.3 specification, including the witti multiclient testnet.
• 0.12.1-integration branch and v0.12.x builds are compatible with the 0.12.1 specification, including Prysm’s new Onyx testnet. These are even more early access than usual as we haven’t completed testing of our v0.12 changes yet.

[Per Adrian]
My recommendation is that people use the master branch/0.11.x releases with the witti testnet.
A new multiclient testnet using spec version 0.12.1 will be launched in the next couple of weeks which is when we recommend people switch to our 0.12 builds (and we’ll likely merge the 0.12.1-integration branch into master at that point since witti will be shut down)

See https://bintray.com/consensys/pegasys-repo/teku#files

Add 2 issue templates:

• Doc tool bug report
• Doc content issue report

Add 2 PR templates:

• Content pull request
• DocOps pull request

See also PegaSysEng/Misc#67

Refer to the Besu content.

https://besu.hyperledger.org/en/stable/HowTo/Monitor/Logging/

Add instructions about using Grafana to visualize Prometheus data.

Link to the Teku Grafana dashboard when it's ready.

The --rest-api-enabled and --rest-api-docs-enabled requires a Command Line tab, and the current Configuration File syntax is incorrect.

See Consensys/teku#2024

Document running Teku docker containers with multiple users

@joshuafernandes is the one for questions/review