Link "getting help" to community forums and update logo and README co…

…ntent

Co-authored-by: Jenny <[email protected]>

neo4j/content.md

@@ -1,4 +1,4 @@
-# What is neo4j?
+# What is Neo4j?
 
 Neo4j is the world's leading graph database, with native graph storage and processing. You can learn more [here](http://neo4j.com/developer).
 
@@ -23,37 +23,4 @@ By default, this requires you to login with `neo4j/neo4j` and change the passwor
 
 # Documentation
 
-For more examples and complete documentation please go to our manual [here](https://neo4j.com/docs/operations-manual/current/docker/introduction/).
-
-# Releases after 3.4.14 and 3.5.6
-
-As of 11th June 2019 all new Neo4j Docker images will be released with a base image of debian-slim instead of alpine linux. This was prompted by [security concerns](https://github.com/docker-library/openjdk/issues/320), which caused the docker maintainers to pull the alpine images from the official `openjdk` images.
-
-Older Neo4j images have already been released with `openjdk:8-jre-alpine` as the base image. This means our old images can no longer be listed as "supported" on docker hub, although **they are still available for download**.
-
-In addition to the supported tags, we also have these legacy images of Neo4j available through docker hub:
-
--	`3.5.5`, `3.5.5-enterprise` and earlier patches
--	`3.4.13`, `3.4.13-enterprise` and earlier patches
--	`3.3`, `3.3-enterprise`, `3.3.9`, `3.3.9-enterprise` and earlier patches
--	`3.2`, `3.2-enterprise`, `3.2.14`, `3.2.14-enterprise` and earlier patches
-
-A complete list of all available Neo4j images can be found here: https://github.com/neo4j/docker-neo4j-publish/tree/master
-
-## Migrating from Alpine Linux to Debian Slim
-
-If you have created a custom Dockerfile based off a `neo4j` image, the main change to be aware of is that debian uses the `aptitude` package manager instead of `apk`. In most cases you can just replace uses of `apk` with `apt`, but be aware that not all packages in `apk` may be available or have the same name.
-
-Alpine Linux provide a more complete comparison on their documentation page:
-
-https://wiki.alpinelinux.org/wiki/Comparison_with_other_distros
-
-## Changes to file permission requirements
-
-Some users have [raised concerns](https://github.com/neo4j/docker-neo4j/issues/130) that the Neo4j image changes file permissions on the host machine.
-
-By default, Neo4j runs as the user `neo4j` who only exists in the container, not on the host. That means that it's hard to set up mount folders on the host which this new user has write permissions for. We have updated the error messaging with advice about how to fix file permission errors. We also introduced writability checks and reduced the amount of file permission changes the image will perform. This has been found to interfere with some Kubernetes setups, so is currently an opt-in feature.
-
-To enforce stricter file permissions checking you can pass this environment variable to the container:
-
-`--env SECURE_FILE_PERMISSIONS=yes`
+For more examples and complete documentation please go to our manual [here](http://neo4j.com/docs/operations-manual/current/deployment/single-instance/docker/).