|
5 | 5 | "metadata": {}, |
6 | 6 | "source": [ |
7 | 7 | "# Project structure\n", |
| 8 | + "<h1>Project structure</h1>\n", |
| 9 | + "Good project layout ensures: \n", |
8 | 10 | "<ul>\n", |
9 | | - "<li>There <strong>is no single</strong> way to organise a filesystem</li>\n", |
10 | | - "<li>🔑 The key is to make sure that the structure is consistsent and\n", |
11 | | - "informative</li>\n", |
12 | | - "<li>Use a <strong>single root directory</strong> per project </li>\n", |
13 | | - "<li>Find a structure that works for you and stick to it</li>\n", |
14 | | - "</ul>\n", |
15 | | - "<div class='info'> Start from the top level and add\n", |
16 | | - "folders as your project evolves </div>\n", |
17 | | - "</div>\n", |
18 | | - " \n", |
| 11 | + " <li>Integrity of the data</li>\t<li>Portability of the project</li>\t<li>Easier to pick the project back up after a brak</li></ul> <br><br>There is no single way to organise a project.... butwe need to take advantage of the power of convention.<div class=\"info\">\t\"A place for everything, everything in its place\"<p class='caption_p'>- Benjamin Frankin</p></div></div> \n", |
19 | 12 | " \n", |
20 | 13 | "The image below gives a suggested structure for a project\n", |
21 | 14 | "\n", |
22 | 15 | "\n", |
23 | 16 | "\n", |
24 | 17 | "\n", |
25 | 18 | "We are going to create the project structure in your computer. \n", |
26 | | - "You can do this manually, from the shell or use whatever\n", |
27 | | - "method you prefer.\n", |
| 19 | + "You can do this manually, from the shell or use whatever method you prefer. But we want an opinionated approach for this.\n", |
28 | 20 | "\n", |
29 | 21 | "<a href=\"https://github.com/mkrapp/cookiecutter-reproducible-science\">\n", |
30 | 22 | "Cookie cutter</a> to create our base filesystem and some support\n", |
|
0 commit comments