Updated information on the open source accelerator overview doc

Author: charlottebrf

_Open_source_accelerator/overview.md

@@ -3,122 +3,35 @@ title: Hack Brexit open source accelerator overview
 ---
 # Introduction - Overview
 
-###  What will we learn
+###  What is the accelerator all about?
 
-* How websites are made
+* A three month programme that takes 2 of the 10 projects created during Hack Brexit weekend
 
-* How to put up your own webpage
+* Run monthly meetings for the teams to present and discuss their projects progress, hosted by ThoughtWorks London
 
-* Basic skills and tools that will be useful for any coding you do
+* Help source additional volunteers to work with the teams on the projects
 
-We hope you will become curious about how the Internet works and will look at websites in a different way.
+* The organising committee will be on hand to provide planning and process assistance over the whole 3 months, and tap into expertise from ThoughtWorks and Code First: Girls community
 
-### How courses will be run
+* The organising committee will manage external communications for the open source accelerator to help spread the word
 
-The hardest thing about learning to program is knowing **where** to start and **what** to learn.
+* At the end of 3 months we will run a final external presentation event with external attendees, we will analyse the progress and development of the project along with its future potential for continuing to grow
 
-The course **aims** to provide a basic overview of the technologies used, along with the tools and resources to discover more.
+* Connect the team members to the wider Hack Brexit meetup community
 
-The **focus** of this course is learning the basics of how and why things work and to provide the basis to build upon in future courses. We will **not** be able to cover everything in great depth or comprehensive detail.
+### Why are we doing this?
 
-Sessions will be as **hands-on and practical** as possible. Each week there will be a number of tasks to do in between the sessions to reinforce what you have learnt.
+We want to continue from the success of the Hack Brexit hackathon on the 23-4 July to bring together technical and non-technical people to create tech solutions to drive dialog, unity and positive action beyond Brexit. We want to sustainably support and scale up projects that have a clear positive impact on society and respond to one of the three key themes we chose for the weekend: 1. Truth, fiction, & accountability; 2. Tolerance & prejudice; 3. Effective organising & campaigning.
 
-It’s up to you whether you do the tasks or not, but the more you put in the more you will get out! If you’re ever in doubt, [Google it](http://lmgtfy.com/?q=how+do+i+use+google%3F), check [StackOverflow](http://lmgtfy.com/?q=how+do+i+use+stackoverflow), ask the person beside you, or ask one of us!
+### T&Cs for accelerator
 
-**Now, let’s check that you’ve installed all the right software and signed up for GitHub and the Student Developer Pack!**
+* An open source project publicly available & accessible to all
+* Projects are created in a repository under the Hack Brexit public repository with an MIT License
+* Projects have an IP that is open to all & can be used by anyone
+* Projects speak to one of the three key themes identified at the Hack (Truth, Fiction & Accountability; Tolerance & prejudice; Effective organising & campaigning) or a future theme as agreed by the community
+* Commitment to work with a group of volunteers on the project for a duration of 3 months
+* Work alongside your project team volunteers & the Hack Brexit organisers to plan the outcomes for at least 3 months
+* Be a project that has scope to continue to be worked on by others in the future
 
-**Note:**
 
-**DEMOS will be in blue with a salmon background -**** Like this.**** - Please show them to do this as you talk through it.**
-
-**STUDENT TASKS will be in red with a pale-blue highlighted background -**** ****Like this.**
-
-# Introduction - Session by Session Course Overview
-
-### Pre-course Preparation: Welcome
-
-* Welcome to web dev & Code First: Girls community
-* Basic intro to web languages with mention of  HTML, CSS, JS (jQuery) & how they are related (i.e. web pages & web servers)
-* Not expected to understand the syntax, but we will demonstrate what each language does to a web page
-* Introduction to the tech community, resources & how to study, developer news
-* Open-source, collaboration (GitHub), stack overflow, w3 schools for online references
-* How can i quickly get help? how can i meet other developers?
-* what can these skills prepare me for? where do I go after this course?
-* To Do 1: Create a github account, sign up for GitHub Student Developer pack
-* To Do 2: installing software: Chrome, GitHub Desktop Client (https://desktop.github.com/), Atom / Sublime Text
-* To Do 3: GA Dash 1
-
-### Session 1: Getting going + HTML
-* software installation troubleshooting (10 minutes)
-* Intro to webpages & web servers (10-15 mins)
-* Creating a HTML page (15 mins)
-* HTML  syntax - use a demo to talk through it (10-15 mins)
-* Homework:  Internet video, GA Dash 2, create your own website locally, read something on CSS
-
-### Session 2: CSS
-* Mention using CSS in <head> tags, but get them to use CSS in a separate file.
-* CSS, Selectors and Attributes, Stylesheets
-* Competition: Explain competition criteria, ask everyone to form teams by week 3 and brainstorm ideas - collaborate on Fb/Slack.
-* Homework: GA Dash 3, Why do software developers collaborate, and what tools are available for them to do so easily?
-
-
-### Session 3: GitHub & the Command Line
-* How to use GitHub - what is version control? & Q&A (basic concepts, commits, pulls, forks, etc) (10 mins)
-* GitHub Pages (https://pages.github.com/), hosting your website (+ talking about competition) (10 mins)
-* Mention other things available on GitHub (https://education.github.com/pack for students), GitHub Gist
-* Introduction to the Command Line - live demo / exercises with students
-* Competition: Spend 10 mins at the end of the session ask the participants to get into their teams. Find teams for those who do not yet have a team. Write down names of teams and ideas. Explain competition criteria again to students (outlined below)
-
-
-
-### Session 4:  Recap & basic development concepts + Course competition
-* Recap HTML & CSS, webservers & URL (10-15 mins)
-* Introduction to frameworks & libraries (in CSS & JS later)
-* What is an API? How is it different from a Framework?
-* Course competition: Start working on your websites! Create the project repository & add HTML & CSS files. Encourage groups to meet up outside class to work on the project
-
-
-### Session 5:  Bootstrap
-* Using Twitter Bootstrap to improve presentation of webpages
-* Homework: make your website responsive
-
-
-### Session 6:  JavaScript & jQuery
-* Basic JS + resources for JS
-* jQuery: what? - talk about how it’s different from JavaScript
-manipulating CSS with jQuery + AJAX(?)
-
-### Session 7:  Plugins, website metrics, hosting & Working on projects
-* Metrics: Google Analytics, Google Forms
-* CloudFlare, domain names & CNAME
-* (Optional): External APIs - Twitter, Facebook - ?
-* Work on group projects for the CF:G Competition
-
-### Session 8:  Course Competition: Presenting final projects
-* Spend the first 30 minutes finalising project websites.
-* Spend at least 1 hour on group presentations (5-10 mins/group).
-* Instructors to choose a winner and announce it at the end of the session.  	
-
-
-### Competition Guidelines
-
-The CF:G competition is a chance for students to put into practice the skills learnt on the course. Students can work individually or in groups of 2-3 to create a landing page for a website. Aim to form teams by Week 3.
-
-The criteria for the competition are here:
-* A visually appealing design - good use of CSS and HTML elements, Twitter Bootstrap
-* Good formatting
-* Code split into the appropriate files
-* Files indented properly
-* A live website (Github page, Heroku or own domain)
-* Extras e.g:
-* A contact form (for example name and email)
-* Social buttons
-* Widgets
-* As many different HTML elements you can manage
-* Interactive elements (like forms) on the website don’t need to be functional, but should be present if they need to be for the visual aspect of the design.
-* (optional) Good organisation
-* Version control using GitHub
-* Sensible commit messages
-
-Some of the winning entries from last term's competition can be found here.
-There'll be prizes of Amazon vouchers for the winning team and a chance to be pitched alongside the winning entries from courses around the U.K. for a grand prize.
+We'll be updating this page with further information as the projects develop, so do watch this space!