Restructure documentationdocumentation_restructure

The big plan in motion, see https://gitlab.com/gitlab-org/gitlab-ce/issues/3349

1 files changed, 35 insertions, 0 deletions

diff --git a/doc/user/workflow/project_features.md b/doc/user/workflow/project_features.md
new file mode 100644
index 00000000000..a523b3facbe
--- /dev/null
+++ b/doc/user/workflow/project_features.md
@@ -0,0 +1,35 @@
+# Project features
+
+When in a Project -> Settings, you will find Features on the bottom of the page that you can toggle.
+
+Below you will find a more elaborate explanation of each of these.
+
+## Issues
+
+Issues is a really powerful, but lightweight issue tracking system.
+
+You can make tickets, assign them to people, file them under milestones, order them with labels and have discussion in them.
+
+They integrate deeply into GitLab and are easily referenced from anywhere by using `#` and the issue number.
+
+## Merge Requests
+
+Using a merge request, you can review and discuss code before it is merged in the branch of your code.
+
+As with issues, it can be assigned; people, issues, etc. can be referenced; milestones attached.
+
+We see it as an integral part of working together on code and couldn't work without it.
+
+## Wiki
+
+This is a separate system for documentation, built right into GitLab.
+
+It is source controlled and is very convenient if you don't want to keep you documentation in your source code, but you do want to keep it in your GitLab project.
+
+## Snippets
+
+Snippets are little bits of code or text.
+
+This is a nice place to put code or text that is used semi-regularly within the project, but does not belong in source control.
+
+For example, a specific config file that is used by > the team that is only valid for the people that work on the code.