Docs: fix duplicate titles

1983e159 · Marcia Ramos 🚫 (OOO - back on May 21) · Achilleas Pipinellis · 88c02d9e · 1983e159 · 1983e159
Commit 1983e159 authored May 09, 2018 by Marcia Ramos 🚫 (OOO - back on May 21) Committed by Achilleas Pipinellis May 09, 2018
20 changed files
--- a/doc/administration/external_database.md
+++ b/doc/administration/external_database.md
+# Configure GitLab using an external PostgreSQL service
+If you're hosting GitLab on a cloud provider, you can optionally use a
+managed service for PostgreSQL. For example, AWS offers a managed Relational
+Database Service (RDS) that runs PostgreSQL.
+Alternatively, you may opt to manage your own PostgreSQL instance or cluster
+separate from the GitLab Omnibus package.
+If you use a cloud-managed service, or provide your own PostgreSQL instance:
+1. Setup PostgreSQL according to the
+   [database requirements document](../install/requirements.md#database).
+1. Set up a `gitlab` username with a password of your choice. The `gitlab` user
+   needs privileges to create the `gitlabhq_production` database.
+1. Configure the GitLab application servers with the appropriate details.
+   This step is covered in [Configuring GitLab for HA](high_availability/gitlab.md).
--- a/doc/administration/raketasks/project_import_export.md
+++ b/doc/administration/raketasks/project_import_export.md
-# Project import/export
+# Project import/export administration **[CORE ONLY]**
 >**Note:**
 >

--- a/doc/articles/openshift_and_gitlab/index.md
+++ b/doc/articles/openshift_and_gitlab/index.md
-This document was moved to [another location](../../install/openshift_and_gitlab/index.html).
+---
+redirect_to: '../../install/openshift_and_gitlab/index.html'
+---
--- a/doc/ci/services/docker-services.md
+++ b/doc/ci/services/docker-services.md
 ---
-comments: false
+redirect_to: 'README.md'
 ---
-# GitLab CI Services
- [Using MySQL](mysql.md)
- [Using PostgreSQL](postgres.md)
- [Using Redis](redis.md)
--- a/doc/container_registry/README.md
+++ b/doc/container_registry/README.md
-This document was moved in [user/project/container_registry](../user/project/container_registry.md).
+This document was moved to [another location](../user/project/container_registry.md).
--- a/doc/customization/issue_closing.md
+++ b/doc/customization/issue_closing.md
 ---
-comments: false
+redirect_to: '../user/project/issues/automatic_issue_closing.md'
 ---
-This document was split into:
- [administration/issue_closing_pattern.md](../administration/issue_closing_pattern.md).
- [user/project/issues/automatic_issue_closing](../user/project/issues/automatic_issue_closing.md).
--- a/doc/install/docker.md
+++ b/doc/install/docker.md
-# GitLab Docker images
+# Install GitLab with Docker
 [Docker](https://www.docker.com) and container technology have been revolutionizing the software world for the past few years. They combine the performance and efficiency of native execution with the abstraction, security, and immutability of virtualization.

--- a/doc/install/openshift_and_gitlab/index.md
+++ b/doc/install/openshift_and_gitlab/index.md
@@ -6,7 +6,7 @@ article_type: tutorial
 date: 2016-06-28
 ---
-# Getting started with OpenShift Origin 3 and GitLab
+# How to install GitLab on OpenShift Origin 3
 ## Introduction

--- a/doc/legal/README.md
+++ b/doc/legal/README.md
@@ -4,5 +4,4 @@ comments: false
 # Legal
- [Corporate contributor license agreement](corporate_contributor_license_agreement.md)
+Please read through the [GitLab License Agreement](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md).
- [Individual contributor license agreement](individual_contributor_license_agreement.md)
--- a/doc/legal/corporate_contributor_license_agreement.md
+++ b/doc/legal/corporate_contributor_license_agreement.md
-This document has been replaced by a Developer Certificate of Origin and License, 
+---
-as described in [Contributing.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md).
+redirect_to: 'README.md'
\ No newline at end of file
+---
--- a/doc/legal/individual_contributor_license_agreement.md
+++ b/doc/legal/individual_contributor_license_agreement.md
-This document has been replaced by a Developer Certificate of Origin and License, 
+---
-as described in [Contributing.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md).
+redirect_to: 'README.md'
\ No newline at end of file
+---
--- a/doc/raketasks/features.md
+++ b/doc/raketasks/features.md
-# Features
+# Namespaces
 ## Enable usernames and namespaces for user projects

--- a/doc/raketasks/web_hooks.md
+++ b/doc/raketasks/web_hooks.md
-# Webhooks
+# Webhooks administration **[CORE ONLY]**
 ## Add a webhook for **ALL** projects:

--- a/doc/university/training/gitlab_flow.md
+++ b/doc/university/training/gitlab_flow.md
@@ -2,39 +2,31 @@
 comments: false
 ---
-# GitLab Flow
+# What is the GitLab Flow
 - A simplified branching strategy
 - All features and fixes first go to master
 - Allows for 'production' or 'stable' branches
 - Bug fixes/hot fix patches are cherry-picked from master
---
+## Feature branches
-# Feature branches
 - Create a feature/bugfix branch to do all work
 - Use merge requests to merge to master
 ![inline](gitlab_flow/feature_branches.png)
---
+## Production branch
-# Production branch
 - One, long-running production release branch
  as opposed to individual stable branches
 - Consider creating a tag for each version that gets deployed
---
+## Production branch
-# Production branch
 ![inline](gitlab_flow/production_branch.png)
---
+## Release branch
-# Release branch
 - Useful if you release software to customers
 - When preparing a new release, create stable branch
@@ -43,15 +35,11 @@ comments: false
 - Cherry-pick critical bug fixes to stable branch for patch release
 - Never commit bug fixes directly to stable branch
---
+## Release branch
-# Release branch
 ![inline](gitlab_flow/release_branches.png)
---
+## More details
-# More details
-Blog post on 'GitLab Flow' at
+For more information read through the [GitLab Flow](../../workflow/gitlab_flow.md)
-[http://doc.gitlab.com/ee/workflow/gitlab_flow.html](http://doc.gitlab.com/ee/workflow/gitlab_flow.html)
+documentation.
--- a/doc/university/training/topics/gitlab_flow.md
+++ b/doc/university/training/topics/gitlab_flow.md
 ---
-comments: false
+redirect_to: '../gitlab_flow.md'
 ---
-# GitLab Flow
----------
- A simplified branching strategy
- All features and fixes first go to master
- Allows for 'production' or 'stable' branches
- Bug fixes/hot fix patches are cherry-picked from master
----------
-### Feature branches
- Create a feature/bugfix branch to do all work
- Use merge requests to merge to master
-![inline](http://gitlab.com/gitlab-org/University/raw/5baea0fe222a915d0500e40747d35eb18681cdc3/training/gitlab_flow/feature_branches.png)
----------
-## Production branch
- One, long-running production release branch
-  as opposed to individual stable branches
- Consider creating a tag for each version that gets deployed
----------
-## Production branch
-![inline](http://gitlab.com/gitlab-org/University/raw/5baea0fe222a915d0500e40747d35eb18681cdc3/training/gitlab_flow/production_branch.png)
----------
-## Release branch
- Useful if you release software to customers
- When preparing a new release, create stable branch
-  from master
- Consider creating a tag for each version
- Cherry-pick critical bug fixes to stable branch for patch release
- Never commit bug fixes directly to stable branch
----------
-![inline](http://gitlab.com/gitlab-org/University/raw/5baea0fe222a915d0500e40747d35eb18681cdc3/training/gitlab_flow/release_branches.png)
----------
-## More details
-Blog post on 'GitLab Flow' at
-[http://doc.gitlab.com/ee/workflow/gitlab_flow.html](http://doc.gitlab.com/ee/workflow/gitlab_flow.html)
--- a/doc/university/training/topics/merge_requests.md
+++ b/doc/university/training/topics/merge_requests.md
@@ -2,7 +2,7 @@
 comments: false
 ---
-# Merge requests
+# Code review and collaboration with Merge Requests
 ----------

--- a/doc/user/admin_area/labels.md
+++ b/doc/user/admin_area/labels.md
-# Labels
+# Labels administration **[CORE ONLY]**
 ## Default Labels

--- a/doc/user/project/pages/introduction.md
+++ b/doc/user/project/pages/introduction.md
-# GitLab Pages
+# Exploring GitLab Pages
 > **Notes:**
 > - This feature was [introduced][ee-80] in GitLab EE 8.3.
@@ -14,9 +14,7 @@ deploy static pages for your individual projects, your user or your group.
 Read [GitLab Pages on GitLab.com](#gitlab-pages-on-gitlab-com) for specific
 information, if you are using GitLab.com to host your website.
-Read through [All you Need to Know About GitLab Pages][pages-index-guide] for a list of all learning materials we have prepared for GitLab Pages (webpages, articles, guides, blog posts, video tutorials).
+## Getting started with GitLab Pages domains
-## Getting started with GitLab Pages
 > **Note:**
 > In the rest of this document we will assume that the general domain name that

--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -5,6 +5,7 @@
 >  - [Introduced][ce-3050] in GitLab 8.9.
 >  - Importing will not be possible if the import instance version differs from
 >    that of the exporter.
+>  - For GitLab admins, please read through [Project import/export administration](../../../administration/raketasks/project_import_export.md).
 >  - For existing installations, the project import option has to be enabled in
 >    application settings (`/admin/application_settings`) under 'Import sources'.
 >    Ask your administrator if you don't see the **GitLab export** button when

--- a/doc/workflow/protected_branches.md
+++ b/doc/workflow/protected_branches.md
-This document is moved to [user/project/protected_branches.md](../user/project/protected_branches.md)
+This document was moved to [another location](../user/project/protected_branches.md).