ada-developers-academy / daily-curriculum Goto Github PK

https://openhatch.org - would be perfect in the week one of intern_weeks.

(see 093c797)

When I navigate to the Week 4 Overview and view Friday, the link to the Sinatra practice is broken.

Add a write-up of what the live coding demonstrations where, key points, goals, etc for week 6 and 8, as needed.

Make the week match elise's spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

Make the week match spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

All links that refer to a file in weeks 1-9 are broken due to changing the directory naming system in week 10. Directories were formerly listed as /1/, /2/, etc. but are now /01/, /02/, etc.

Example: in week 4, a link directs to https://github.com/Ada-Developers-Academy/daily-curriculum/blob/master/week4/friday/sinatra-practice.md , which breaks. Linking to https://github.com/Ada-Developers-Academy/daily-curriculum/blob/master/week04/friday/sinatra-practice.md resolves this problem.

Make the week match spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

According to ADA's website, this curriculum, and other ADA resources should be open source. However, I don't see a license anywhere. Am I missing something?

If it is truly open source, please add an appropriate license.

Can goals be modified to reflect RailsBridge, etc?

Group topics into units for folders accordingly. Make sure all the links don't break moving files into the folders. Also create an "archive" folder for all files that we don't think are being used anymore.

Student Orientation
Setup
Ruby Fundamentals
Web Fundamentals
Sinatra
Databases
Rails
Testing
APIs
JavaScript Fundamentals
JavaScript Frameworks
Capstone
Internship Spike

When I navigate to the Week 4 Overview, the blog project is listed, but not linked.

Some files/folders use dash (-) and some use underscore (_) between words. Can we standardize this so that they all use dash (-).

Make the week match elise's spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

Make the week match elise's spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

Make the week match spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

When I view the Week 4 Overview, the blog project is listed, but there is no linked project description.

See 6951be8

Make the week match elise's spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.

Make the week match spec:

In the GitHub Repository, there should be 24 weekly folders. Each weekly folder should contain:

• A weekly overview, written in markdown
• A folder for each day of class in the week, labeled "monday", "tuesday", etc. (exception is if that day is 100% project time, but should be clearly stated in the weekly overview document)
• The weekly folder can contain a "resources" directory in which multi-day projects and materials are stored

The Weekly Overview Document should contain:

• A paragraph description of the week's topics (purpose of the week and expected outcomes)
• Bulleted list of goals for the week (for each topic, granular purpose and expected outcomes)
• Day-by-day classroom schedule linking to lectures, in-class projects and assignments, and quizzes and Canvas turn-in page (where applicable)
• Bulleted daily homework list (including reading, projects, and assignments) after each day's schedule, linking to description (if needed) and Canvas turn-in page

The Daily Folders should contain:

• Lectures/lecture notes, written in markdown (1-to-1 with weekly overview)
• In-class assignment descriptions (1-to-1 with weekly overview)
• Project description for projects introduced/assigned on that day (1-to-1 with weekly overview), with the exception of multi-day projects, which live in the weekly resources folder
• No class-specific information (i.e. due dates or group assignments - this should be in the weekly overview)
• No daily overview or homework (weekly overview is canonical, this is duplicative)
• Any additional reference files should be in a separate folder entitled "resources"

In the event of impromptu lectures/assignments, instructor should modify the weekly overview to reflect the new content. If the lecture is primarily live coding, the lecture description should include an overview of the material covered and links to applicable resources.