summaryrefslogtreecommitdiff
path: root/doc/development/documentation
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-03-01 19:07:47 +0000
committerMarcia Ramos <marcia@gitlab.com>2019-03-01 19:07:47 +0000
commit2ee23bb3124588f3de5c25dbc6b5539ab66881f9 (patch)
treee9ebeb6599bb243877b6cfd483167a4f708a0ef5 /doc/development/documentation
parentadf71cfa75fb07c54cb2f55126d1f8596e3ab5c3 (diff)
downloadgitlab-ce-2ee23bb3124588f3de5c25dbc6b5539ab66881f9.tar.gz
Add confidential issue linking guidance
Diffstat (limited to 'doc/development/documentation')
-rw-r--r--doc/development/documentation/styleguide.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/development/documentation/styleguide.md b/doc/development/documentation/styleguide.md
index 7a3a8f25c2d..cd38721e3ab 100644
--- a/doc/development/documentation/styleguide.md
+++ b/doc/development/documentation/styleguide.md
@@ -236,6 +236,24 @@ For other punctuation rules, please refer to the
E.g., instead of writing something like `Read more about GitLab Issue Boards [here](LINK)`,
write `Read more about [GitLab Issue Boards](LINK)`.
+### Links to confidential issues
+
+Don't link directly to [confidential issues](../../user/project/issues/confidential_issues.md). These will fail for:
+
+- Those without sufficient permissions.
+- Automated link checkers.
+
+Instead:
+
+- Mention in the text that the information is contained in a confidential issue. This will reduce confusion.
+- Provide a link in back ticks (`` ` ``) so that those with access to the issue can easily navigate to it.
+
+Example:
+
+```md
+For more information, see the [confidential issue](https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html) `https://gitlab.com/gitlab-org/gitlab-ce/issues/<issue_number>`.
+```
+
### Unlinking emails
By default, all email addresses will render in an email tag on docs.gitlab.com.