Currently LE certs are automatically renewed 7 days prior to expiration, we should document this.

devops - The super user. Can do everything.
dev - The developer user. Can use Kontena Platform to deploy stacks, access logs, use Kontena Vault and more.

what does "and more" mean - what's missing between dev and devops

When clicking on the Official deb package link under tools/cli.md page the package returned to download is a osx pkg file titled: kontena-cli-osx-v1.3.5-amd64.pkg.
the link on the page before the redirect looks correct so I am not sure where the issue is.
I am downloading through Ubuntu/Chrome

(or any default values if there are any?)

https://kontena.io/docs/using-kontena/loadbalancer#using-kontena-load-balancer-for-ssl-termination

The "Preparing LetsEncrypt Certificates" section links to the updated Using LetsEncrypt Certificates section that uses the new kontena certificate request commands, but then the following LB docs section on Using SSL Certificates from Kontena Vault still uses secrets, so it won't work with the new LE certificates...

The secrets stuff is unfortunately still also relevant for "Preparing Traditional SSL Certificates" before kontena certificate import gets merged...

or you can just remove an replica set instance and re-deploy it to another one (mongodb should re-sync data)

The Quick Start docs only link to the omnibus release packages for OSX, but these are now also available as Debian/Ubuntu deb packages for the 1.4 release. The docs for Linux should be updated to prefer the omnibus deb package over a manual gem install.

Problems with the manual gem install:

• Ubuntu: gem install kontena-cli doesn't actually work: you need to either sudo gem install, or gem install --user-install and get ~/.gem/ruby/2.3.0/bin onto your $PATH: kontena/kontena#2604
• The 1.4 release now includes native extensions in the kontena-cli dependencies, so gem install will fail if you do not have a compiler + ruby-dev installed. Is that available by default on normal Ubuntu/Windows ruby installs?: kontena/kontena-websocket-client#11

It's still unclear what we should do about Windows, because we don't have a omnibus packages for that platform (kontena/kontena#2307). Should we recommend Windows Subsystem for Linux + the deb package for Windows 10, or do the windows ruby distributions include the necessary compiler + ruby-dev stuff to install native extensions?

See kontena/kontena#2918

build - Specify the configuration options that are applied at docker image build time. 
Learn more. 
NOTE! The network and label options mentioned in docker compose documentation do
not work with Kontena Stack Files.

There's no mention about network and labels in dockerfile documentation in build section.

When installing from ruby gems, cloud plugin is not bundled. Would be nice to add some text about cloud plugin if user wants to operate with cloud commands

See kontena/kontena#3000

The docs for grid --default-affinity imply a single affinity rule, and there's no mention of how multiple --default-affinity options behave, particularly in regards to kontena grid update: https://www.kontena.io/docs/using-kontena/platform.html#create-a-new-kontena-platform

default-affinity - Specify the default affinity rule for the entire Kontena Platform using the affinity filter syntax. The default affinity rule is applied to all Kontena Stacks on this Kontena Platform by default. The most common use case is to prevent Kontena Stack deployments to specific Kontena Nodes unless specified in Kontena Stacks.

Since the "fork" there has been quite a few PRs on https://github.com/kontena/kontena that have changed docs. This issue is to collect them into one list. We shall create a PR for each of those to re-port the docs into new repo.

* CLI: Removed the app subcommand, it is now available as a plugin (kontena/kontena#2675) removed already in docs re-work

• Agent: Allow overriding KONTENA_NODE_NAME (kontena/kontena#2693), see #2
• Node scheduling availability (kontena/kontena#2306), see #3
• Add v4auth to create registry with s3 driver (kontena/kontena#2242), see #4
• Add support for soft affinities (kontena/kontena#2540), see #5
• Configurable agent node ID, labels (kontena/kontena#2590), see #6
• Ubuntu kontena-agent: Use /usr/bin/dockerd for compatibility with Docker 1.12 - 17.06 (kontena/kontena#2589), see #7
• Rewrite agent websocket client (kontena/kontena#2560), see #8
• Add new user_admin role (kontena/kontena#2577), see #9
• Create HostNode with per-node token for websocket auth (kontena/kontena#2504)

https://kontena.io/docs/using-kontena/stacks.html needs some kind of stack lifecycle flowchart, such as:

       [Kontena Stack YAML] -<<<------+
                |                     |
 +-yes- < Needs to be built? > -no-+  |
 |                                 |  |
 +- [ Build ]    +-----------------+  |
         |       |                    |
      [ Push ]   |                    |
         |       |                    |
         +-----+ |                    |
               | |                    |
            [ Install ]               |
                 |                    |
             [ Deploy ]               |
                 |                    |
            [ Upgrade ] ->>>----------+

but prettier.

(also I think the repetition of the word Kontena Stack in the chapter list does not look pleasant and most of the chapters are oneliners + command example.)