diff --git a/pegasus/sites.v3/code.org/public/educate/professional-learning/facilitator-2019.md b/pegasus/sites.v3/code.org/public/educate/professional-learning/facilitator-2019.md index e65dcf0d46e89..5d225b52c50e5 100644 --- a/pegasus/sites.v3/code.org/public/educate/professional-learning/facilitator-2019.md +++ b/pegasus/sites.v3/code.org/public/educate/professional-learning/facilitator-2019.md @@ -1,10 +1,9 @@ --- title: Facilitator Development Program theme: responsive +noindex: true --- - - # Facilitating with Code.org [col-50] @@ -17,7 +16,7 @@ theme: responsive ## Change the face of computer science education - become a Code.org facilitator. -Code.org counts on engaging, committed, and knowledgeable facilitators to develop and support the next generation of computer science educators. +Code.org counts on engaging, committed, and knowledgeable facilitators to develop and support the next generation of computer science educators. Ready to take your leadership to the next level? @@ -33,7 +32,7 @@ Our online applications take 25-30 minutes to complete, and are not optimized fo
+
-1. Each Regional Partner organization is provided with one partner account. - * If multiple people in your organization need to access the data, we encourage you to set up your account with a password that can be shared within your organization. -2. Email your Regional Manager if you have not been set up with an account. - * Once your account has been set up, you will receive an email from Tableau with instructions on how to access your Tableau account, including setting up your password. +1. Each Regional Partner organization is provided with one partner account. + * If multiple people in your organization need to access the data, we encourage you to set up your account with a password that can be shared within your organization. +2. Email your Regional Manager if you have not been set up with an account. + * Once your account has been set up, you will receive an email from Tableau with instructions on how to access your Tableau account, including setting up your password. * The email will say “You’ve been invited to Tableau Online” - * There will be an orange button prompting you to sign up for the first time and set up your password. + * There will be an orange button prompting you to sign up for the first time and set up your password.
- +
+ * This might occur if a teacher is teaching with a Code.org account that is different from the one they used to register for your workshop or TeacherCon. If you are able to give us the email address of the account the teacher is using to teach, we can fix their data in Tableau.
- +
+
* There may be some people that are included in the attendance for your workshop according to the dashboard, but shouldn't be listed as part of your cohort (e.g., novice and apprentice facilitators). Please identify these people so we can remove them.
* It is possible that the same teacher might appear multiple times on your list. Please identify these people so we can remove one of the two entries.
* You should not remove teachers that are no longer teaching the course or participating in PD for any reason. This information is important to retain for implementation rates.
@@ -70,16 +70,16 @@ Note that there is a filter for each course, CS Discoveries and CS Principles, s
+
-* If for any reason a teacher is missing from your roster, please provide their email address. The address you provide should be associated with the Code.org account they use to teach.
+* If for any reason a teacher is missing from your roster, please provide their email address. The address you provide should be associated with the Code.org account they use to teach.
-
+
+
* Include a call in your newsletters for students, teachers, parents, and districts to fill out the survey at http://code.org/yourschool. You can find sample language to use in your newsletter [here](https://docs.google.com/document/d/1O9julhujYWIkg-JAm92B-6havhPLSTI0avnXFXlthsk/edit?usp=sharing)
* Connect to local organizations in your region who can spread the word on your behalf.
* Connect us to organizations that may already have this information in your region (accessreport@code.org).
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/directory.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/directory.md
index 9cc3ec911bfee..a897e2cce8b0d 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/directory.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/directory.md
@@ -1,8 +1,8 @@
---
title: Regional Partner Directory
nav: regional_partner_playbook_nav
+noindex: true
---
-
# Regional Partner Network
@@ -28,9 +28,9 @@ As the Regional Partner program continues to mature and expand, Code.org will lo
**Purpose**
-The advisory committee is a valuable resource for Code.org to understand our partners’ needs and to tailor our models accordingly. Regional Partners are carrying on the teacher recruitment, professional learning, and district management work that Code.org began, and as such, they are now the power users of Code.org tools and processes and are best suited to offer valuable feedback and input. While there are numerous avenues for all partners to provide feedback, make suggestions, and share ideas such as regional managers, ongoing feedback surveys, and at Partner Summits, the advisory committee provides a formal structure for ongoing communication with a representative group of Regional Partners. Code.org benefits from hearing feedback, advice and receiving guidance on the direction of the program.
+The advisory committee is a valuable resource for Code.org to understand our partners’ needs and to tailor our models accordingly. Regional Partners are carrying on the teacher recruitment, professional learning, and district management work that Code.org began, and as such, they are now the power users of Code.org tools and processes and are best suited to offer valuable feedback and input. While there are numerous avenues for all partners to provide feedback, make suggestions, and share ideas such as regional managers, ongoing feedback surveys, and at Partner Summits, the advisory committee provides a formal structure for ongoing communication with a representative group of Regional Partners. Code.org benefits from hearing feedback, advice and receiving guidance on the direction of the program.
-The advisory committee is also a forum to connect peers across the Regional Partner network to share resources and successes, discuss ideas, and connect and learn from each other. Committee members serve a 2- or 3-year term and represent a broad range of partners from all Groups, institutional types, and geographic locations. New committee members are nominated by Code.org staff in collaboration with the current advisory committee. If you are interested in serving on the committee in the future, have questions, or would like to learn more, please email the Chair(s) to express your interest.
+The advisory committee is also a forum to connect peers across the Regional Partner network to share resources and successes, discuss ideas, and connect and learn from each other. Committee members serve a 2- or 3-year term and represent a broad range of partners from all Groups, institutional types, and geographic locations. New committee members are nominated by Code.org staff in collaboration with the current advisory committee. If you are interested in serving on the committee in the future, have questions, or would like to learn more, please email the Chair(s) to express your interest.
@@ -39,7 +39,7 @@ The advisory committee is also a forum to connect peers across the Regional Part
<%= view :about_headshots, people:DB[:cdo_team].where(kind_s:'rpadvisory') %>
-## Shared Resources
+## Shared Resources
Access the Regional Partner Network Google Drive [here](https://drive.google.com/drive/folders/1yKAijpPre8wFRStRhIpl_1BuKcxQa9HW?usp=sharing).
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/facilitator-support.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/facilitator-support.md
index 91c8b48bb8d98..75559a2e4f3fe 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/facilitator-support.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/facilitator-support.md
@@ -1,8 +1,8 @@
---
title: Facilitators
nav: regional_partner_playbook_nav
+noindex: true
---
-
@@ -30,11 +30,11 @@ ________________
________________
-### Interviewing Facilitators
+### Interviewing Facilitators
Keep these three important things on your radar as you prepare for upcoming facilitator interviews. Watch this [very quick recording](https://code.zoom.us/recording/play/_kbC3EU3s8sHFBPeessecWvewQcZLofgK0dFZXzOFL2BU8SYM-gorH_WBj6vuXQ-?startTime=1548267193000) for more details, and read below for the highlights.
-1. **Interview Scheduling:**
+1. **Interview Scheduling:**
All Group 1 - 3 Regional Partners are responsible for scheduling interviews with their candidates during the interview period of Feb. 11 - March 1. Interviews should be booked for 30 minutes, and should include a video chat (e.g., Google hangout, Zoom, etc.) if they’re not hosted in-person. However, we recommend you block an hour on your calendar for prepare and review. Remember that many candidates are teachers who have limited availability during the school day, so please be prepared to host interviews in the late-afternoon or early evening.
2. **Interview Support:** All Group 1 - 3 Regional Partners are responsible for hosting interviews on their own, without the support of a Code.org-contracted co-interviewer. This means that Regional Partners will need to plan ahead to make sure they are able to conduct the interview while taking notes in the application dashboard.
3. **Interview Questions and Process:** We will cover the interview process and required interview questions in detail during the February Regional Partner Summit.
@@ -60,10 +60,10 @@ ________________
### Example contract
[This is an example](/files/example-facilitation-agreement.pdf) of an agreement that facilitators sign when facilitating for Code.org. You should develop your own agreement for use with facilitators that meets your organization's particular needs, and which ensures that the terms of the Regional Partner agreement you have signed with Code.org, particularly Section 3 (Indemnification), Section 6.1 (Description of Duties) and Section 7 (Confidential Information), are met.
-We have created these example Scope of Work documents that you can use as a planning resource when establishing a relationship with a K-5 or 6-12 facilitators. These document lives in our shared Google Drive folder.
+We have created these example Scope of Work documents that you can use as a planning resource when establishing a relationship with a K-5 or 6-12 facilitators. These document lives in our shared Google Drive folder.
- K-5 example Scope of Work
-- 6-12 example Scope of Work
+- 6-12 example Scope of Work
*DISCLAIMER: By providing these resources and example documents, Code.org is not offering you legal advice. You should consult a lawyer if you need advice about contracts, the language therein, or any other legal matter. These resources are meant to serve as general guides for you to customize and make adjustments that are right for your organization, while still staying within the bounds of the program guidelines Code.org has outlined.*
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/funding.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/funding.md
index a3089d814f716..19da82c898c54 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/funding.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/funding.md
@@ -1,8 +1,8 @@
---
title: Fundraising Resources
nav: regional_partner_playbook_nav
+noindex: true
---
-
# Topics
@@ -35,9 +35,9 @@ It's important to start thinking about how you will sustain these programs witho
### What can you do if you're just getting started?
-- Create your prospect list of potential funders (who is likely to fund your Program Manager, etc.)
-- Project how much you need and how much you can raise from this list in 3-4 months
-- Start outreach to potential funders to pitch them through emails, calls or in person meetings
+- Create your prospect list of potential funders (who is likely to fund your Program Manager, etc.)
+- Project how much you need and how much you can raise from this list in 3-4 months
+- Start outreach to potential funders to pitch them through emails, calls or in person meetings
- Use a special event as your “closer” event
[**Back to the top**](#top)
@@ -46,16 +46,16 @@ ________________
-December 2017
+December 2017
- Dec 12 TEALS & the CS Principles Classroom ([Video](https://code.zoom.us/recording/play/7YH4DmJAL5OutCqgRsE5-YORNg0RUP5Uu-c_KtcX0P-LS-ohu9wUfXJS-K_URZz6))
@@ -108,7 +108,7 @@ March 2017:
- Guest Speaker Series: NCWIT [Video](http://videos.code.org/plp/NCWIT_March17.mp4), [Slides](https://docs.google.com/presentation/d/1nxC--kbLdFF41laOZqKFmKjMZmfsFUMAwf2VZkF59q4/edit)
- CS Principles Webinar for Teachers [Video](http://videos.code.org/plp/3-28-2017_CSPrinciples_Webinar.mp4)
-January 2017:
+January 2017:
- How to Review Teacher Applications [Video](https://videos.code.org/teacher/Teacher+Application+Review+Process.mp4), [Slides](https://docs.google.com/presentation/d/11bDnl_ekOspmJ4cVhShvoRQ3k0GVq0DeSWpRPx56CJg/edit?usp=sharing)
- CSP Teacher Application Process for Local Workshops [Video](http://videos.code.org/cs-principles/CSP-teacher-application-process-for-local-workshops.mp4), [Slides](https://docs.google.com/presentation/d/1SHF7pfrJmFt53Cp6GRpvw6VIo93x4euT-InYWYfe8Q4/edit?usp=sharing)
diff --git a/pegasus/sites.v3/code.org/views/theme_common_head_before.haml b/pegasus/sites.v3/code.org/views/theme_common_head_before.haml
index 0de9395b50194..f0806d19d90da 100644
--- a/pegasus/sites.v3/code.org/views/theme_common_head_before.haml
+++ b/pegasus/sites.v3/code.org/views/theme_common_head_before.haml
@@ -1,6 +1,8 @@
- @header['social'].each_pair do |property, content|
%meta{property:property, content:content}
+- if header['noindex']
+ %meta{name: "robots", content: "noindex"}
%title= page_title_with_tagline
Teachers to add
- How can you help?
-
-# Fundraising Playbook
+# Fundraising Playbook
When looking for donor support, it is important for your organization to understand the different types of donors. Each donor type may have different partnership expectations and giving trends that can either help or detract from your organization’s mission.
**Types of Support:**
-
-- **Individuals:** “major donors” - high net worth/family foundations, “small” donors (typically online)
-- **Corporate:** grant from corporation’s foundation or sponsorship (donation in exchange for benefits such as logos and other marketing / visibility)
-- **Large National Foundations:** ex. Gates Foundation, Rockefeller, etc.
-- **In-Kind:** donated products and services (ex. office space, software, catering, advertising)
+
+- **Individuals:** “major donors” - high net worth/family foundations, “small” donors (typically online)
+- **Corporate:** grant from corporation’s foundation or sponsorship (donation in exchange for benefits such as logos and other marketing / visibility)
+- **Large National Foundations:** ex. Gates Foundation, Rockefeller, etc.
+- **In-Kind:** donated products and services (ex. office space, software, catering, advertising)
Note: This list of revenue streams is not exhaustive, but outlines the types of revenue streams Code.org pursues. You could also explore: crowdfunding, employee matching/giving, planned giving, events/galas, etc). Your organization should decide what fundraising methods work best to achieve your mission.
@@ -82,11 +82,11 @@ ________________
### Fundraising Strategy Best Practices:
-- **Diversify your revenue streams:** ex. Code.org if funded by approximately 40% corporations, 40% foundations/high net worth individuals, 20% online donations
- * Having a mix of types of support creates more stable funding and reduces risk year over year
-- **Program/mission focus:** Code.org best practice is lead with the ask with potential funders who have mutual goals, believe in your mission, and do not ask for you to stray away from your mission. Code.org does not pursue customized programs with funders, where the funder donates to create a specific program with the nonprofit. This enables us to stay focused on achieving our mission at scale, maintain lean fundraising operations/staff, and ultimately create more impact.
-- **General operating support vs. restricted funding:** Code.org best practice is to try to maintain as much general operating support to allow your organization to stay flexible to meet the needs of your program goals, and maintain low overhead and staff to manage grants and donors
-- **Multi-Year Grants:** if possible, try to secure multi year grants to advance your mission. This will help you raise funds more efficiently and be able to better project your future income and cash flow.
+- **Diversify your revenue streams:** ex. Code.org if funded by approximately 40% corporations, 40% foundations/high net worth individuals, 20% online donations
+ * Having a mix of types of support creates more stable funding and reduces risk year over year
+- **Program/mission focus:** Code.org best practice is lead with the ask with potential funders who have mutual goals, believe in your mission, and do not ask for you to stray away from your mission. Code.org does not pursue customized programs with funders, where the funder donates to create a specific program with the nonprofit. This enables us to stay focused on achieving our mission at scale, maintain lean fundraising operations/staff, and ultimately create more impact.
+- **General operating support vs. restricted funding:** Code.org best practice is to try to maintain as much general operating support to allow your organization to stay flexible to meet the needs of your program goals, and maintain low overhead and staff to manage grants and donors
+- **Multi-Year Grants:** if possible, try to secure multi year grants to advance your mission. This will help you raise funds more efficiently and be able to better project your future income and cash flow.
|Best Practices| |
@@ -102,7 +102,7 @@ ________________
# Research
-The relationship between an organization and their donors should be based on clear communication and a partnership based in a common goal and mission. Throughout the research process to identify prospective donors, your organization will look at many different aspects of the prospective donor to assess if the donor is a good match for your organization.
+The relationship between an organization and their donors should be based on clear communication and a partnership based in a common goal and mission. Throughout the research process to identify prospective donors, your organization will look at many different aspects of the prospective donor to assess if the donor is a good match for your organization.
## Prospective Research sheet:
@@ -126,30 +126,30 @@ Overall, match level is based on the research areas aligning with your own organ
## Other Research Resources:
- Here is a list of potential funders.
-- General Fundraising Websites:
+- General Fundraising Websites:
* [Foundation Center](http://foundationcenter.org/findfunders/fundingsources/fdo.html)
* [The Chronicle of Philanthropy](https://philanthropy.com/)
* [GrantSpace](http://grantspace.org)
* [Charity Navigator](http://www.charitynavigator.org/)
-
+
[**Back to the top**](#top)
________________
-# Outreach
+# Outreach
Outreach is the securing of initial calls and meetings with potential funders. Once you have your research completed and you have determined your “pipeline” i.e. target list of potential donors to reach out to, its time to make the ask.
## Basic Solicitation Cycle:
-- Begin with thoughtful research to determine if potential donor is a good fit for your mission (see research template)
+- Begin with thoughtful research to determine if potential donor is a good fit for your mission (see research template)
- Outreach to potential donor via email (an introduction from a mutual contact or Board Member is always helpful)
- Meet or schedule a call to determine interest and inclination of potential donor
- * Involve donor prospect substantively to determine partnership value and fit - ask questions on what goals they have, what are their pain points?
- * Demonstrate your organization’s accomplishments and share your community of supporters who help provide credibility
- * Show you address their goals and why your partnership is a good fit
- * Ask if you can follow up with another call, meeting, or proposal
-- Develop a proposal (include $ ask)
-- Follow-up, answer any questions, negotiate and secure the donation
+ * Involve donor prospect substantively to determine partnership value and fit - ask questions on what goals they have, what are their pain points?
+ * Demonstrate your organization’s accomplishments and share your community of supporters who help provide credibility
+ * Show you address their goals and why your partnership is a good fit
+ * Ask if you can follow up with another call, meeting, or proposal
+- Develop a proposal (include $ ask)
+- Follow-up, answer any questions, negotiate and secure the donation
- Thank and steward the donor throughout the year. Include an opportunity to engage directly with your programs or employee engagement. Email communications on your accomplishments and program updates and engaging key executives to learn more about your mission.
- Create Impact Reports/communications to demonstrate the value of the donor’s support
- Reach out and set up a call or meeting 6-9 months into your grant cycle to start having renewal discussions
@@ -216,16 +216,16 @@ ________________
## Do's:
-- Have a clear vision, strategy and outcomes
+- Have a clear vision, strategy and outcomes
- Focus on building authentic, mutually beneficial relationships
-- Find funders who truly believe in your organization’s mission, vision and program
+- Find funders who truly believe in your organization’s mission, vision and program
- Leverage your position as a leader and expertise for your cause
-- Understand the pain points and goals of your potential funder and position yourself as a solution to help them achieve those goals
+- Understand the pain points and goals of your potential funder and position yourself as a solution to help them achieve those goals
- Share a list of your other donors and funders to demonstrate credibility
-- Be transparent with your finances and how you spend your money / where the money goes
-- Recognize, thank and communicate with your donors often
-- Be proactive with your follow up and stewardship
-- Demonstrate the impact of your work through data, evaluation, case studies, impact stories
+- Be transparent with your finances and how you spend your money / where the money goes
+- Recognize, thank and communicate with your donors often
+- Be proactive with your follow up and stewardship
+- Demonstrate the impact of your work through data, evaluation, case studies, impact stories
## Don'ts:
@@ -244,9 +244,9 @@ ________________
# Supports for Pursuing Federal and State Grants
-This resource has been created to provide regional partners who may be interested in pursuing federal or state grant funding with some basic guidance and suggestions on doing so. In many cases the language can also be applied to the pursuit of corporate, foundation, or individual funding.
+This resource has been created to provide regional partners who may be interested in pursuing federal or state grant funding with some basic guidance and suggestions on doing so. In many cases the language can also be applied to the pursuit of corporate, foundation, or individual funding.
-The document has been organized to reflect the major sections typically associated with federal grant applications and will include a basic explanation of what the particular section is about, indicators of effectiveness, a few tips to keep in mind, and generic templates from which to build your specific proposal off of. Templates are meant to be examples and not prescriptive. In the end your proposal should uniquely reflect the strengths and resources of your organization and the efforts you will engage in both as a Regional Partner of Code.org and as a leader of computer science education in your region. It is up to you to determine how much you want to highlight your collaboration with Code.org or take a more general approach focusing on your organization’s efforts.
+The document has been organized to reflect the major sections typically associated with federal grant applications and will include a basic explanation of what the particular section is about, indicators of effectiveness, a few tips to keep in mind, and generic templates from which to build your specific proposal off of. Templates are meant to be examples and not prescriptive. In the end your proposal should uniquely reflect the strengths and resources of your organization and the efforts you will engage in both as a Regional Partner of Code.org and as a leader of computer science education in your region. It is up to you to determine how much you want to highlight your collaboration with Code.org or take a more general approach focusing on your organization’s efforts.
Click [here](https://docs.google.com/document/d/1-F21aQTOmWuYt4l1wm8Ae2SrsGydBDoXiM7ifzCqsi0/edit#) to access the resource.
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/legacy.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/legacy.md
index 96f607cc6da9b..1b63e7dec0c63 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/legacy.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/legacy.md
@@ -1,15 +1,14 @@
-
-
---
title: Legacy Programs
nav: regional_partner_playbook_nav
+noindex: true
---
# Legacy Programs
-See below for documents and more information about Code.org's legacy programs. Code.org has discontinued professional learning for these programs, but are leaving the information available for those partners who have decided to continue them.
+See below for documents and more information about Code.org's legacy programs. Code.org has discontinued professional learning for these programs, but are leaving the information available for those partners who have decided to continue them.
## Quick Links
@@ -24,7 +23,7 @@ Click on the program name below to find out more about our **legacy programs**.
________________
-## **Computer Science in Algebra**
+## **Computer Science in Algebra**
[CS In Algebra homepage](https://code.org/curriculum/algebra)
[CS in Algebra Course A Curriculum (PDF)](https://curriculum.code.org/algebra/courseA.pdf)
@@ -105,7 +104,7 @@ Always accommodate vegetarian needs, roughly ⅓ of the order. In communications
________________
-## **Computer Science in Science**
+## **Computer Science in Science**
[CS in Science homepage](https://code.org/curriculum/science)
@@ -180,7 +179,7 @@ Always accommodate vegetarian needs, roughly ⅓ of the order. In communications
________________
-## **Exploring Computer Science**
+## **Exploring Computer Science**
[ECS Curriculum homepage](http://www.exploringcs.org/for-teachers-districts/curriculum)
- Central location: Is the location central to the spread of teachers attending?
- Catering: Are there several options to order from within 20 miles? Is there an internal or preferred caterer for the venue?
- Parking: Does parking cost anything? Will teachers need parking passes? Is the lot close to an entrance? *Tip: teachers are more likely to show up to the workshop when parking is free.*
- Access: Will there be someone from the venue there to open the building, help with getting supplies to your room(s), and be available to help with technology as needed during the workshop?|
-|**Rooms and
Set Up**|Reservation time:
Rooms need to be reserved from 7:30 am to 4:30 pm (M-Th) and 7:30 am to 2:30 pm (F).
General itinerary:
7:30 am - 8:30 am - facilitators arrive and set up room
8:30 am - 9:00 am - teachers arrive, register & eat breakfast 9:00 am - 12:00 pm - workshop time
12:00 pm - 1:00 pm - break for lunch
1:00 pm - 3:30 pm - workshop time
3:30 pm - 4:30 pm - facilitators clean up for the night
Note: ECS workshops end at 1:30 pm on Fridays.
Rooms Needed:
- One room for entire group
- Breakout room to set up catering and for eating. Hallway space also works. We want to avoid interrupting the session by setting up food in the room.
- Wall space for hanging poster sized paper with Blue painter's tape
Seating
- Pods of 4 people for the size of the group. We recommend 8 pods.|
+|**Rooms and
Set Up**|Reservation time:
Rooms need to be reserved from 7:30 am to 4:30 pm (M-Th) and 7:30 am to 2:30 pm (F).
General itinerary:
7:30 am - 8:30 am - facilitators arrive and set up room
8:30 am - 9:00 am - teachers arrive, register & eat breakfast 9:00 am - 12:00 pm - workshop time
12:00 pm - 1:00 pm - break for lunch
1:00 pm - 3:30 pm - workshop time
3:30 pm - 4:30 pm - facilitators clean up for the night
Note: ECS workshops end at 1:30 pm on Fridays.
Rooms Needed:
- One room for entire group
- Breakout room to set up catering and for eating. Hallway space also works. We want to avoid interrupting the session by setting up food in the room.
- Wall space for hanging poster sized paper with Blue painter's tape
Seating
- Pods of 4 people for the size of the group. We recommend 8 pods.|
|**Technology
Requirements**| - Projector and screen
- Power outlets and extension cords
- Wifi that can support access by all participants (4 MB/s minimum, 8 MB/s is ideal.)
|
|**Logistical and Facilitator One Pager Information**|- Physical Address of Workshop
- Address to ship supplies (If needed)
- Map of the Campus and/or building to help teachers find the room. Driving instructions should be provded to teachers. This can be done via Google Maps or Bing Maps.
- Wifi strength, name and password. All participants will need to be on the network at the same time with no lag.
- Arrangments for Access: You should make arrangements with your venue contact to give you access to the building and help you locate supplies.
-Need an example of an official invoice? Visit [this site](http://www.wikihow.com/Sample/Services-Rendered-Invoice).
+Need an example of an official invoice? Visit [this site](http://www.wikihow.com/Sample/Services-Rendered-Invoice).
See more info in the [Community Building tile](http://code.org/educate/regional-partner/playbook/community).
[**Back to the top**](#top)
@@ -185,7 +185,7 @@ ________________
## Teacher Recruitment Fund
-To receive reimbursement for expenses incurred towards your Recruitment Fund, complete the form and attach recripts for [allowable expenses](https://staging.code.org/educate/regional-partner/playbook/teacher-recruitment#recruitment) at [bit.ly/codeinvoices](http://bit.ly/codeinvoices).
+To receive reimbursement for expenses incurred towards your Recruitment Fund, complete the form and attach recripts for [allowable expenses](https://staging.code.org/educate/regional-partner/playbook/teacher-recruitment#recruitment) at [bit.ly/codeinvoices](http://bit.ly/codeinvoices).
Required information for reimbursement will include date, amount, invoice, receipts, a brief explanation of how the expenses supported recruitment in your region, and your best estimate of the number of teachers reached.
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/reporting-and-evaluations.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/reporting-and-evaluations.md
index 951bc2be6d11e..47c1b9e7db968 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/reporting-and-evaluations.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/reporting-and-evaluations.md
@@ -1,8 +1,8 @@
---
title: Reporting and Evaluation
nav: regional_partner_playbook_nav
+noindex: true
---
-
# Reporting and Evaluations
@@ -30,7 +30,7 @@ ________________
## **Regional Partner Annual Planning**
-The annual plan is one of the tools you will use to self-evaluate and improve in the main categories for success as a Regional Partner.
+The annual plan is one of the tools you will use to self-evaluate and improve in the main categories for success as a Regional Partner.
Find the annual plan template for your group:
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/summit.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/summit.md
index cd64c4fbd2b1e..f0217f330674f 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/summit.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/summit.md
@@ -2,10 +2,8 @@
title: Summit
theme: responsive
style_min: true
-
+noindex: true
---
-
-
# Who's Who at the Regional Partner Summit
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/teacher-recruitment.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/teacher-recruitment.md
index ef10a9871dbe6..d44766fd3b85f 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/teacher-recruitment.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/teacher-recruitment.md
@@ -1,8 +1,8 @@
---
title: Teacher and District Recruitment
nav: regional_partner_playbook_nav
+noindex: true
---
-
# Teacher and District Recruitment
@@ -33,25 +33,25 @@ ________________
Review the 2019-20 Teacher Application Process Document for everything you need to know about the Code.org teacher application process including finalizing your Local Summer Workshop dates, the list of teacher application questions and how they map to the rubrics, using the Code.org teacher applications system, and FAQs.
### What are the important dates I need to know about?
-- **Two weeks** before your application open date your set-up forms are due. Save this table for a quick way to reference these important dates.
+- **Two weeks** before your application open date your set-up forms are due. Save this table for a quick way to reference these important dates.
- **Two months** prior to your Local Summer Workshops is the deadline for accepting a minimum cohort of teachers. This is to allow adequate time to go through the process of cancelling a workshop, if absolutely necessary, and reaccommodating teachers into another workshop outside your region.
-- **Four weeks** prior to your Local Summer Workshop is the deadline for accepting teachers as this is also the deadline for ordering workshop supplies.
+- **Four weeks** prior to your Local Summer Workshop is the deadline for accepting teachers as this is also the deadline for ordering workshop supplies.
### Application Links
- Landing page for school ZIP code lookup
- 2019-20 Professional Learning Program Teacher Application
### Where can I find some resources to help with recruitment?
-- Visit the [Curriculum Tile](https://code.org/educate/regional-partner/playbook/curriculum) for one-pagers on each program as well as a overview of the professional learning program that you can share with administrators and potential applications.
+- Visit the [Curriculum Tile](https://code.org/educate/regional-partner/playbook/curriculum) for one-pagers on each program as well as a overview of the professional learning program that you can share with administrators and potential applications.
- Teachers and administrators can visit https://code.org/educate/professional-learning/middle-high to start learning about CS Discoveries, CS Principles and the program requirements.
- Encourage teachers to check out our course and Professional Learning Program options to determine the best fit for their teaching situation.
### Teacher Recruitment Fund
-In order to support teacher recruitment efforts and increase the number of submitted teacher applications, Code.org will reimburse each Regional Partner a maximum of $1,000 towards the costs of teacher recruitment that you incur between March 8 and 8-weeks prior to your Local Summer Workshop.
+In order to support teacher recruitment efforts and increase the number of submitted teacher applications, Code.org will reimburse each Regional Partner a maximum of $1,000 towards the costs of teacher recruitment that you incur between March 8 and 8-weeks prior to your Local Summer Workshop.
-This additional funding may be used for:
+This additional funding may be used for:
- Registration fees for a booth at education leadership/educator conferences
- Travel for on-the-ground recruitment, including mileage, hotels, flights, and meals
@@ -106,7 +106,7 @@ The K–12 Computer Science Framework is a high-level guide for states, district
Microsoft Digital Skills Toolkit
A toolkit for middle and high schools to increase
-diversity in computer science education.
+diversity in computer science education.
### Agreeing to Terms
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/timeline.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/timeline.md
index 46b20432b0546..afcbc74383ec8 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/timeline.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/timeline.md
@@ -1,8 +1,8 @@
---
title: Timeline
nav: regional_partner_playbook_nav
+noindex: true
---
-
diff --git a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/training-materials.md b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/training-materials.md
index 1289fce9ea12c..532c86cc03956 100644
--- a/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/training-materials.md
+++ b/pegasus/sites.v3/code.org/public/educate/regional-partner/playbook/training-materials.md
@@ -1,8 +1,8 @@
---
title: training materials
nav: regional_partner_playbook_nav
+noindex: true
---
-
# Training Materials
@@ -74,7 +74,7 @@ January 2018
**2017 Virtual Trainings**