From bb902de421d6e45bb94ae2e45185834e3a670bd5 Mon Sep 17 00:00:00 2001
From: David Ragnar Nelson <35697532+drnelson6@users.noreply.github.com>
Date: Thu, 18 Apr 2024 15:48:56 -0400
Subject: [PATCH] Adjust sample repo based on wg meeting

---
 content/lessons/repro_research.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/lessons/repro_research.md b/content/lessons/repro_research.md
index 9edd569..d9e5471 100644
--- a/content/lessons/repro_research.md
+++ b/content/lessons/repro_research.md
@@ -36,7 +36,6 @@ Your project organization might look something like this:
 
 ```
 impressive-project/
-├── README.md
 ├── data/
 |  ├── README.md
 |  ├── metadata.csv
@@ -44,16 +43,17 @@ impressive-project/
 |     ├── book_a.txt
 |     ├── book_b.txt
 |     └── ...
-├── data-processing/
-├── plots/
+├── code
 ├── tests/
 ├── doc/
 │   ├── index.rst
 │   └── ...
+├── .gitignore
+├── CITATION.cff
+├── CONTRIBUTING.md
+├── dependencies.md
 ├── LICENSE
-├── requirements.txt
-├── package.json
-└── package-lock.json
+├── README.md
 ```
 
 By using a clear organizational structure like this one, someone unfamiliar with your project will quickly be able to understand what your project is doing and how they might go about reproducing your work or building upon it for their own purposes.