From 3f55cb09a67ad478278667ff2b5275c755e0f0bd Mon Sep 17 00:00:00 2001
From: Steven Pestana <650301+spestana@users.noreply.github.com>
Date: Tue, 30 Apr 2024 09:45:27 -0700
Subject: [PATCH] Add sentence about intended audience for project design
 details

---
 book/projects/index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/book/projects/index.md b/book/projects/index.md
index a52c992..d160246 100644
--- a/book/projects/index.md
+++ b/book/projects/index.md
@@ -8,6 +8,10 @@ Each hackweek’s community of research scientists and domain practitioners gene
 * **Deepening tutorial learning with hands-on experience with data sets/tools**
 * **Developing a new community tool or library**
 
+# How projects are designed
+
+On the following pages you will find more details on how projects are designed. This information is provided to help guide project leaders, but can be for all hackweek participants to be familiar with. 
+
 We encourage all project leaders to be creative with their ideas and when planning out the project’s group work and learning opportunities. *The organizers will help each lead think through how to best scope the project* to match the desired outcomes for the group work. In the meantime, leads can consider the range of scoping options described in the table below to get a sense of where their idea may fall.
 
 On the left, the project is less structured so that it can be adapted to where team members would like to take the project based on what they can contribute and want to learn. On the right, the project work is much more structured allowing participants to make quick progress on project goals and/or focused learning experiences. Then some projects are in between, a blend of focused, structured, and adaptable.