From d1932982ad29795da30679923964df81f429dbab Mon Sep 17 00:00:00 2001
From: lmodolo <laurent.modolo@ens-lyon.fr>
Date: Tue, 5 Jun 2018 12:05:24 +0000
Subject: [PATCH] add TP_experimental_biologists.md file

---
 doc/TP_experimental_biologists.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 doc/TP_experimental_biologists.md

diff --git a/doc/TP_experimental_biologists.md b/doc/TP_experimental_biologists.md
new file mode 100644
index 0000000..218b623
--- /dev/null
+++ b/doc/TP_experimental_biologists.md
@@ -0,0 +1,12 @@
+# TP for experimental biologists
+
+The Goal of this practical is to learn how to build your own pipeline with nextflow and using the tools already *wrapped* in Docker and SGE.
+
+## Initialize your own project
+
+You are going to build a pipeline for you or your team. So the first step is to create your own project.
+
+Instead of reinventing the weel, you can use the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow) as a template.
+To easily do so, go to the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow) repository and click on the [**fork**](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/forks/new) button.
+
+In git, the action of forking means that you are going to make your own private copy of a repository.
\ No newline at end of file
-- 
GitLab