_content/doc: module naming best practices

This adds new content with best practices for the module path. It also
revises existing content to use the best practice.

This change includes:

* A new "Naming a module" section in "Managing dependencies" describing
  naming best practices and reserved terms for module paths.
* Changing module path prefix from "example.com/*" to "example/*"
  where the content seems aimed specifically at new users. This is
  designed to reduce confusion for those who wonder if a domain name
  is required in the local, simple context.
* Links to the "Naming a module" section so that new users can follow up
  from the simple case to learn about best practices.

Change-Id: I07eac1f805ce506a486d3c0e7b54539554e3c30b
Reviewed-on: https://go-review.googlesource.com/c/website/+/344469
Trust: Steve Traut <straut@google.com>
Trust: Bryan C. Mills <bcmills@google.com>
Reviewed-by: Bryan C. Mills <bcmills@google.com>
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Go Bot <gobot@golang.org>

1 files changed, 6 insertions, 0 deletions

diff --git a/_content/doc/tutorial/create-module.html b/_content/doc/tutorial/create-module.html
index e9df3367..d187f4f9 100644
--- a/_content/doc/tutorial/create-module.html
+++ b/_content/doc/tutorial/create-module.html
@@ -152,6 +152,12 @@ cd greetings
       Go tools. That would be your code's repository.
     </p>
 
+    <p>
+        For more on naming your module with a module path, see
+        <a href="/doc/modules/managing-dependencies#naming_module">Managing
+        dependencies</a>.
+    </p>
+
     <pre>
 $ go mod init example.com/greetings
 go: creating new go.mod: module example.com/greetings