# data[].attributes.body
1. Please login or put your name/initials in your posts.
2. To add a post, click the + sign at the bottom of each column.
3. Add one idea per post (so you may have multiple posts per category)
4. Include the name of the site (Brooke or Match) in each post.
5. Feel free to read other posts, but you will have time to do this on our call as well.

# data[].attributes.body
I like how Brooke uses very clear filter options on the left side.

# data[].attributes.body
On the Brooke website, you can view all of the materials without logging in. I think we should have a login for each user so that we can track who is accessing the materials.

# data[].attributes.body
I saw a video on the Match site, which made me think it would be cool if we had short videos of kids explaining the importance of each type of resource :-)

# data[].attributes.body
Like how clearly organized and linear match system is. Want to be able to clearly share / organize materials.

# data[].attributes.body
I find the Brook search features and display of results jumbled and confusing. Prefer match layout

# data[].attributes.body
Neither site does a lot to build context, they mostly get you "into" looking at the curriculum. Because I think match and brooke are more traditional, there is less context needed. How do we build and share context for our program.

# data[].attributes.body
Both Brooke and match seem to have stand-alone courses- Reading is separate from writing. Since we have integrated programs (reading, writing SDL/ science investigations,SDL) how do we convey the connections

# data[].attributes.body
The unit level and the lesson level are bifurcated on Match. It almost encourages a "lesson by lesson" sampling rather than a coherrent program. That's helpful form a "let me find a resource" perspective but not from a we recommend adoption of a  program rather than a lesson by lesson approach.

What is our philosphy on sharing- do we want to encourage one type of sharing over another and/or should the set up of the site encourage one type of sharing over another.

# data[].attributes.body
I didn't read closely, so possible I missed this, but we have tried (though not perfect) to dial up our focus on DEI in the program. I would want that to come through on our site.

# data[].attributes.body
How do we get feedback, welcome feedback and acknowledge that this is a work in progress not a perfect pretty thing

# data[].attributes.body
JL - I don't love that there are two ways to navigate 1) boxes at the bottom and 2) menus at the top.  I feel like it is confusing - until you click in you can't tell that they are duplicative.

# data[].attributes.body
JL - I like the organization of categories - the separation of other tools from the actual curriculum.

# data[].attributes.body
JL - Other than the concept of filters, I do not like this home page. I feel like it doesn't allow for the user to understand what is being shared and how it relates to their overarching approach.

# data[].attributes.headline
Creating a user (or multi-user) experience

# data[].attributes.subject
Creating a user (or multi-user) experience

# data[].attributes.body
JL - How to set the site up to take the user on a journey rather than leave it up to them what they look at first?
Could we apply the concept of filters from the Brooke's site to set up a guided journey based on user type (teacher, leader, central office, etc.)

# data[].attributes.headline
Set-up to minimize the creation of new resources

# data[].attributes.subject
Set-up to minimize the creation of new resources

# data[].attributes.body
JL - how to we set this up to minimize the need to create externally facing versions of resources? For example - the match site has "how to guides" I like the concept and see how something for GF could be very useful. However, I would want any "how to" strategy to work for both internal and external stakeholders

# data[].attributes.body
AKP - how are resources managed on the backend? Are they hard to manage by someone who isn't super tech saavy? Would we need to setup a new login generation mechanism and manage that on the backend?

# data[].attributes.body
AKP - this is flagging for me that not all of our assessments that accompany our curriculum live in "neat" documents. Some completely live in Illuminate, and only have super basic "paper" versions as our contingency plans. How do we solve this with minimal lift?

# data[].attributes.body
AKP - love the match videos. Convinces me even more that we need to do this!

# data[].attributes.body
AKP - I love how they created the Curriculum Team section; it really helps put faces to products and makes the curriculum seem more relate-able in a sense. It also really seems to show how much these teammates are values for all of the curriculum they produce (like everlasting shout-out!) and also serves as recruitment mechanism which is SO smart!

# data[].attributes.body
(AKP) I think the organization of the Match Content Area main page is great - obviously would need to be adapted for GF-specific components; however, I think that (1) most things you need to execute a unit is available (standards map, unit overviews, lessons, "how to use this course" video, summary of course)

# data[].attributes.body
AKP - I disklike how they don't share any teacher/leader tools to help track data or help with IPP/LASW, etc... I would want us to share a few of these tools on THESE pages (or references them in "Other Resources" section) because I assume most will go straight to curriculum pages and start downloading

# data[].attributes.headline
"Too Much" Integration of Curriculum in Website - Match

# data[].attributes.subject
"Too Much" Integration of Curriculum in Website - Match

# data[].attributes.body
AKP - On the Match Curriculum Pages, the lessons are each deconstructed from whatever source they came from and built out directly on the webpage - I'm assuming it's for ease of use; however, this is too much ongoing work and we need to find a more creative way to make our materials easy to use yet as little lift as possible for us to maintain/update.

# data[].attributes.body
AKP - the organization of the Brooke Open Source home page is extremely confusing, especially all of the tiles that load at the bottom. I also dislike how little descriptive text there is any where on the site and how everything is mainly in video format.

# data[].attributes.body
AKP - i really like how Brooke's "how we teach" section is included alongside their curriculum; I think similarly to them, we have redefine teacher roles and expectations, and in order to help paint a clear picture of how teaching load is shared, properly planned for and executed, we should codify some thing similar.

# data[].attributes.headline
Brooke - Switching between Regular Website and Curriculum Site

# data[].attributes.subject
Brooke - Switching between Regular Website and Curriculum Site

# data[].attributes.body
AKP - I dislike that as you toggle in a couple of layers to the curriculum site, you may get taken to a page on the regular brooke website, and then i couldn't figure out how to get back to curriculum site. If possible, I think any shared information should be mirrored to external sharing site for us, as it makes it confusing when it jumps around website to website.

# data[].attributes.body
AKP - while I am kicking myself as I am typing this right now, I really like how Match's external sharing site was it's own distinct website (vs. Brooke's, which sometime lead you away from resource site and back to main website, making it harder to toggle through)