moved files from F&C9 gitbook to curriculum/general

moved files from general section of F&C9 gitbook to curriculum/general. related #28

curriculum/general/README.md

@@ -0,0 +1,3 @@
+# General
+
+This section is about general information applicable throughout the duration of the course.

curriculum/general/about.md

@@ -0,0 +1,21 @@
+# About FAC
+**Founders & Coders C.I.C.** is a social enterprise.
+
+As well as running the training programme, the company operates as a freelance co-operative.
+
+Everyone here is a member of the co-operative
+
+## HOW DO WE SUPPORT OURSELVES?
+Our main sources of income are:
+* a proportion (10%) of the income of graduates who are freelancing in the space;
+* fees received from employers for hiring our graduates.
+
+We have two main costs: rent and Dan's salary.
+
+## GIVING BACK 
+There are several ways we ask you to give back to the community here.
+* Help with our free coding meetups and workshops
+* Communications and publicity
+* Looking after the space
+* Running the next course
+* Letting us help you find work

curriculum/general/calendar.md

@@ -0,0 +1,5 @@
+# Calendar
+
+Check out the updated calendar [here](https://calendar.google.com/calendar/embed?src=h7329vu9qpi64cli2sdk53l9ec@group.calendar.google.com&ctz=Europe/London).
+
+Weeks 1-10 will be dedicated to learning. There will be a reading fortnight (break) between week 10 and week 12 over the Winter holidays. Weeks 12-17 will be dedicated to projects with charities and social enterprises.

curriculum/general/facilities.md

@@ -0,0 +1,13 @@
+# Space
+The space here is shared between the current cohort, graduates of previous cohorts, Dan and *dwyl*.
+
+*dwyl* is run by Nelson and Ines. Nelson is our lead technical mentor and Ines is director of Founders & Coders. *dwyl* is an agency that employs some of our graduates on a freelance basis. You will hear more about *dwyl* in due course.
+
+## Facilities 
+We have just one loo. Hopefully it will be enough, but this space is now shared by over 30 people, so it will get well used.
+
+The kitchen area is used by all of us. Please clear up after yourself and don't leave stuff in the sink or on the counter.
+
+The fridge tends to get pretty full. Please put anything you wish to keep overnight in a container. Milk is for sharing.
+
+We also have a shower room.

curriculum/general/house-rules.md

@@ -6,6 +6,8 @@
 
 + **Clean desk policy**. We have a clean-desk policy. Please leave your desk clear before you leave each day.
 
-+ **Hot desking**. Please sit anywhere downstairs when you arrive each morning. 
++ **Hot desking**. Please sit anywhere downstairs when you arrive each morning.
 
 + **20-minute rule**. Struggle is good, but not too much of it. As a general rule, if you cannot solve a problem within 20 minutes, then stop and talk to somebody about it (there should be a timer on your desk)
+
++ **No frameworks**. For the first 10 weeks of the course, stick to vanilla JavaScript. That means no frameworks, backend or frontend (i.e. no Bootstrap/jQuery etc...). This is for the benefit of your understanding of JavaScript; trust us (and all the previous FAC cohorts) – it works!

curriculum/general/mentors.md

@@ -0,0 +1,25 @@
+# Mentors
+ We have no paid teaching staff, but everyone in this space is here to assist you in your learning. Here is a list of people active in F&C:
+
+* [Dan Sofer](https://github.com/sofer) (director)
+* [Ines Teles](https://github.com/iteles) (director/dwyl)
+* [Nelson Correia](https://github.com/nelsonic) (lead technical mentor/dwyl)
+* [Besart Hoxhaj](https://github.com/besarthoxhaj) (F&C2)
+* [Izaak Rogan](https://github.com/izaakrogan) (F&C2)
+* Harry Fox (F&C3/dwyl)
+* Simon Labondance (F&C5/dwyl)
+* Anita Czapla (F&C5/dwyl)
+* Jack Rans (F&C5/dwyl)
+* Mina Gyimah (F&C5)
+* Daniel (F&C5/dwyl)
+* [Sohil Pandya](https://github.com/sohilpandya) (F&C6)
+* Tormod Smith (F&C6)
+* [Eoin McCarthy](https://github.com/des-des) (course facilitator/F&C6/dwyl)
+* Naaz Ahmed (F&C6/dwyl)
+* Marie Kasai (F&C6/dwyl)
+* Conor Campbell (F&C6/dwyl)
+* [Bradley Reeder](https://github.com/bradreeder) (course facilitator/F&C8)
+* [Noga Inbar](https://github.com/nogainbar) (F&C8)
+* [Sofia Pohjalainen](https://github.com/sofiapoh) (F&C8)
+
+And most of F&C7 and F&C9!

curriculum/general/responsibilities.md

@@ -0,0 +1,55 @@
+# Responsibilities
+
+##Course facilitators
+* Eoin
+* Bradley
+
+##Pre-course
+* Jen
+* Nick
+* Cleo
+
+## Week1 - Toolkit
+* Jen
+* Nick
+* Cleo
+
+## Week2 - Testing
+* Ewelina
+* John
+* Peter
+
+## Week 3 - API
+* Ewelina
+* Lucy
+* Emily
+
+## Week 4 - Node core
+* Marina
+* Will
+* Steve
+
+## Week 5 - Node core (cont.)
+* Nick
+* Marko
+* John
+
+## Week 6 - PostgreSQL
+* Emily
+* Tom
+* Steve
+
+## Week 7 - Hapi views
+* Marko
+* Will
+* Marina
+
+## Week 8 - Hapi authentication
+* Nori
+* Jen
+* Lucy
+
+## Week 9 - Redis & websockets
+* Nori
+* Tom
+* Peter

curriculum/general/rota.md

@@ -0,0 +1,10 @@
+# Meetup Rotas
+
+As members of the FAC family, we expect you to help run our meetup groups Coding for Everyone (every Monday, 18:30 - 20:00) and Coding for Women (every other Tuesday, 18:30 - 20:00).
+
+We need at least two people of any gender present at every meetup to greet people, watch the space and lock up at the end of the session.
+
+Please add your availability to both:
+
+* [Coding for Everyone Rota](http://doodle.com/poll/g59e4dnbyfzz39uzr44zuzkw/)
+* [Coding for Women Rota](http://doodle.com/poll/76bxp4nxcthrk34d66536f5y/)

curriculum/general/tips-for-mentoring.md

@@ -0,0 +1,20 @@
+# 10 tips for teaching code
+
+1. Always ask questions first. Most of the time the students actually know the answer, but just don’t feel confident in it.
+2. Encourage the students to type and not copy paste.
+3. The student should always be in control of the keyboard and mouse (don’t type for them)
+4. Draw things out! Keep a notepad and pen with you and prepare yourself to draw out the problems/solutions to visually aid your explanations
+5. If you don’t know the answer that is completely okay! The best thing to do is find out the answer with the student. Google it and then you guys can both learn something new. Ideally this also signals to the person you are mentoring that it is okay not to know something
+6. If a student is feeling overwhelmed, breaking down the problem into very small chunks works well. They need to be shown they can figure it out on their own, you are just there to guide them.
+7. Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore.
+8. Don't say no when the students are not doing something right. Be gentle, approach it in a mild way.
+9. Work collaboratively with your students. If you have two or more students, you should work with all of them. Don't focus all your attention on one of them.
+10. Assume that anyone you're teaching has no knowledge but infinite intelligence.
+
+###Before the course we suggest you...
+
+* Run through some of the material with someone who hasn’t coded before - This is deployed to Read the docs for easy viewing
+* Get more practise! We recommend mentoring at [codebar](https://codebar.io/member/new). Many of the attendees there are new to programming so it is good preparation for the course.
+
+
+##### #thanxNathalia for sending us these tips!

curriculum/general/week-schedule.md

@@ -0,0 +1,59 @@
+# General Week Schedule
+
+
+#### Monday
+
+09:45 - 10:15 Show and Tell
+
+10:15 - 11:15 Morning challenge
+
+11:15 - 13:00 Workshops
+
+14:00 - 18:00 Go through tutorials
+
+#### Tuesday
+
+10:00 - 11:00 Morning Challenge
+
+11:00 - 13:00 Go through tutorials
+
+13:00 - 14:00 Lunch
+
+14:00 - 17:30  Readmes/research
+
+17:30 - 18:00 Project planning
+
+#### Wednesday
+
+10:00 - 13:00 Projects
+
+13:00 - 14:00 Lunch
+
+14:00 - 18:00 Projects
+
+#### Thursday
+
+10:00 - 13:00 Projects
+
+13:00 - 14:00 Lunch
+
+14:00 - 17:00 Projects
+
+17:00 - 18:00 Internal project team code review
+
+
+#### Friday
+
+10:00 - 11:00 Code review
+
+11:00 - 13:00 Respond to issues
+
+13:00 - 14:00 Lunch
+
+14:00 - 15:00 Respond to issues
+
+15:00 - 16:00 Project presentations
+
+16:00 - 18:00 Business development, Stop, Go, Continue and Our projects
+
+Put up a Weekend challenge on github

curriculum/general/you.md

@@ -0,0 +1,17 @@
+# Developing your online presence
+
+Regardless of whether you are looking for a job or wanting to work freelance, you will make your life easier if you have a visible online presence.
+
+Here is a checklist:
++ Have a great Github profile, see e.g. [this one](https://github.com/nelsonic)
+  + Expose organisations you're a part of
+  + Make sure you have a profile picture of some sort
+  + Work towards a streak to show you put in consistent effort
+  + Fork group projects you work on so they appear under your repositories
++ Have a great profile on Linkedin;
++ Have a great CV, see e.g. [this one](https://github.com/Neats29/CV)
++ Have a great personal website, see e.g. [this one](http://www.rleonardi.com/interactive-resume/)
++ Follow and endorse each other on Github (star liberally), Linkedin and Twitter
++ Contribute to open source projects on Github
++ Contribute to open source learning materials on Github (like ours!)
++ Contribute to Linkedin forums and groups