add class content

Author: tektechnologies

.gitignore

@@ -0,0 +1,155 @@
+
+# Created by https://www.gitignore.io/api/node,linux,macos,windows,visualstudiocode
+
+### Linux ###
+*~
+
+# temporary files which can be created if a process still has a handle open of a deleted file
+.fuse_hidden*
+
+# KDE directory preferences
+.directory
+
+# Linux trash folder which might appear on any partition or disk
+.Trash-*
+
+# .nfs files are created when an open file is removed but is still being accessed
+.nfs*
+
+### macOS ###
+# General
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+### Node ###
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# next.js build output
+.next
+
+# nuxt.js build output
+.nuxt
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless
+
+### VisualStudioCode ###
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+
+### Windows ###
+# Windows thumbnail cache files
+Thumbs.db
+ehthumbs.db
+ehthumbs_vista.db
+
+# Dump file
+*.stackdump
+
+# Folder config file
+[Dd]esktop.ini
+
+# Recycle Bin used on file shares
+$RECYCLE.BIN/
+
+# Windows Installer files
+*.cab
+*.msi
+*.msix
+*.msm
+*.msp
+
+# Windows shortcuts
+*.lnk
+
+
+# End of https://www.gitignore.io/api/node,linux,macos,windows,visualstudiocode

README.md

@@ -1,2 +1,81 @@
-# cedarrapids-code-102w26
-Introduction to Software Development.
+# Code 102: Intro to Software Development
+
+## Course Information
+
+- Course Level: 102
+
+## Course Prerequisites
+
+- Computer updated with the latest version of OS, all security patches installed.
+- Familiarity with basic algebra concepts.
+- Code 101 or equivalent exposure to basic HTML and CSS.
+
+Recommended: Be able to type at least 30 words per minute.
+
+> Students with previous relevant or equivalent experience can test out of this requirement in their application.
+
+## Course Description
+
+In this course you will build a strong software development foundation and learn how to use HTML, CSS, and JavaScript to build for the modern web. You will learn the methods and tools of professional software developers through studying computer science concepts and utilizing contemporary development technologies, including VSCode, Chrome (and its developer tools), Git, GitHub, and Terminal.
+
+## Program Learning Outcomes
+
+Builds a strong software development foundation and learn how to use HTML, CSS, JavaScript, and various libraries to create fully-functional web apps.
+
+This course guides students toward developing a well-rounded foundation of skills necessary for modern web development. These skills include HTML, CSS, and JavaScript coding; utilizing Git workflow processes, project organization, designing with wireframing and employing introductory Agile development methods.
+
+## Student Learning Outcomes
+
+Upon satisfactory completion of this course, a student should be able to:
+
+### Describe and Define
+
+#### Web Development
+
+- Website structure (files, resources)
+- The benefits of version control with Git and GitHub
+- Markdown
+- Proper use of Semantic HTML
+- The role of CSS in website development and design
+
+#### JavasScript Programming
+
+- Variables & storing data
+- Conditionals
+- Flow control with "for" and "while" loops
+
+### Execute
+
+- Tie together HTML, CSS, and JavaScript in an interactive web page.
+- Use the same tools utilized by professionals across the tech industry.
+- Apply CSS to style content with color, typography, and images.
+- Utilize Javascript to make web projects interactive.
+- Utilize industry-standard version control tools and workflows, including Git and GitHub.
+- Configure your computer and see the workflow for serious software development, with free and open-source tools.
+- Learn to write documentation using Markdown.
+
+## Course Schedule
+
+| Class # | Topic |
+|-----------------|-----------|
+|1| [Learning. Markdown.](class-01/)
+|2| [The Coder's Computer](class-02/)
+|3| [Revisions and the Cloud](class-03/)
+|4| [Structure web pages with HTML](class-04/)
+|5| [Design web pages with CSS](class-05/)
+|6| [Activate web pages with JavaScript](class-06/)
+|7| [Programming with JavaScript](class-07/)
+|8| [Just enough math, logic, and computer architecture](class-08/)
+|9| [Career Coaching](class-09/)
+|10| [201 Entrance Exam](class-10/)
+
+### Tips for Success
+
+Get ready to tackle some seriously ambitious material! You'll have the most success if you:
+
+- Take notes during class.
+- Keep up with the daily assignments (code and reading).
+- Research topics that are new or confusing.
+- Speak up when you're stuck for more than 15 minutes.
+- Be thorough and deliberate when reading error messages and console/terminal responses. Take your time and do not go too fast. Always know what you are doing.
+- And, above all else, pay attention to details.

class-01/DISCUSSION.md

@@ -0,0 +1,31 @@
+# Reflection and Discussion
+
+Below is a collection of resources of varying types and lengths which describe the topics from lecture.  
+
+Go through these resources, and **create a page in your reading-notes repo** that summarizes the topics you learned as though you were presenting the material to a non-technical friend interested in learning about it.
+
+Note entry ideas:
+
+* Blog Article (2-3 paragraphs with code sample)
+* Dictionary / Flash Cards
+* Notes in outline form
+* Fill-in-the-blank worksheet of key concepts
+
+## Read
+
+* [Markdown Basic Syntax](https://www.markdownguide.org/basic-syntax/){:target="_blank"}
+* [Mastering Markdown on GitHub](https://guides.github.com/features/mastering-markdown/){:target="_blank"}
+
+## Watch
+
+* [GitHub Pages](https://pages.github.com/){:target="_blank"}
+
+## Bookmark
+
+* [GitHub Markdown Syntax](https://help.github.com/en/articles/basic-writing-and-formatting-syntax){:target="_blank"}
+
+## Submission
+
+Share what you've learned by copying and pasting the full text of your new rendered web page into the 'Reply' below. Include the live URL of the new page below your pasted text.
+
+You are invited to check out your classmates' replies and give positive feedback and words of encouragement.  

class-01/README.md

@@ -0,0 +1,36 @@
+# Learning. Markdown.
+
+Welcome to Code 102! We will dive right in to learning new things.
+
+## Learning Objectives
+
+- Students will understand the impact of mindsets on the learning process and know how to adjust their mindset for effective skill acquisition.
+- Students will use essential Markdown syntax to create documents and publish a web site of interconnected pages using a Jekyll theme through GitHub Pages.
+- Students will publish a reading-notes, to highlight skills gained during the course.
+
+## Agenda
+
+1. Campus Orientation & Intros
+1. Learning to Learn
+    - Growth mindset
+    - Demo & Lab
+1. Web Publishing
+    - Markdown
+    - GitHub Pages
+
+See class slides and assignments for details.
+
+## New Vocabulary
+
+- Professional Competencies
+- Proficiencies
+- Canvas
+- GitHub
+- Slack
+- Growth mindset
+- Fixed mindset
+- Repository
+- Markdown
+- Web publishing
+- Path learning
+- Sandbox learning

class-01/lab/README.md

@@ -0,0 +1,31 @@
+# Create a reading-notes Repo
+
+Give yourself a learning challenge: Figure out how to publish a GitHub Pages web site, to use as a reading-notes.
+
+## Setup and Documentation
+
+Use these resources to get going:
+
+- [Growth Mindset](https://www.atlassian.com/blog/inside-atlassian/growth-mindset){:target="_blank"}
+- [Markdown on GitHub](https://help.github.com/en/articles/basic-writing-and-formatting-syntax){:target="_blank"}
+- [Getting Started with GitHub Pages](https://guides.github.com/features/pages/){:target="_blank"}
+
+## Requirements
+
+1. Your site should exist at `https://USERNAME.github.io/reading-notes/`
+1. The "source" for your site should be a README.md file, written with Markdown
+1. On the main page:
+    - Explain "growth mindset" in your own words
+    - Include 3 reminders to yourself of how to keep yourself in a growth mindset
+1. Utilize at least 5 different features of Markdown to structure your page
+1. Be sure to introduce yourself, and include a link to your GitHub portfolio page
+
+### Stretch Goals
+
+Beef up your profile page! Add an image, a bio, contact info... as much as you feel comfortable including. Remember, this page will act as a showcase of your developer skills, so make it look great!
+
+### Submission Instructions
+
+Share a link to your live site with your classmates, in the discussion below.
+
+Then, review the sites of your classmates, comment with what you learned from them. Click through to profile pages to "follow" each of your classmates.

class-02/Choosing-A-Text-Editor--The-Older-Coder.pdf

@@ -0,0 +1,34 @@
+# Reflection and Discussion
+
+Below is a collection of resources of varying types and lengths which describe the topics for the upcoming lecture.  
+
+Go through these resources, and **create a page in your reading-notes repo** that summarizes what you learned as though you were presenting the material to a non-technical friend interested in learning about it.
+
+Reading-notes entry ideas:
+
+* Blog Article (2-3 paragraphs with code sample)
+* Dictionary / Flash Cards
+* Notes in outline form
+* Comparison of "basic" text editor vs coding-specific text editor vs IDE.
+
+## Read
+
+* [Choosing a Text Editor](https://codefellows.github.io/code-102-guide/curriculum/class-02/Choosing-A-Text-Editor--The-Older-Coder.pdf){:target="_blank"}
+
+Document in your reading-notes the different classifications of text editors, and why it's important for software developers to be thoughtful about their selection of what they use to write code.
+
+## Read Carefully
+
+The following pages will give you a step by step introduction to using a terminal. While it refers to Linux, the same commands are available in macOS and Windows (with WSL). Read through these pages carefully. Don't worry about trying this out on your own system yet, that will come very soon. For now, take notes on how commands are used, and which look similar to how you are used to using the GUI File Explorer/Finder.
+
+* [The Command Line](https://ryanstutorials.net/linuxtutorial/commandline.php){:target="_blank"}
+* [Basic Navigation](https://ryanstutorials.net/linuxtutorial/navigation.php){:target="_blank"}
+* [About Files](https://ryanstutorials.net/linuxtutorial/aboutfiles.php){:target="_blank"}
+
+Record in your reading-notes a "cheat sheet" or other resource for basic terminal usage.
+
+## Submission Instructions
+
+Share what you've learned by copying and pasting the full text of your new rendered web page into the 'Reply' below. Include the live URL of the new page below your pasted text.
+
+You are invited to check out your classmates' replies and give positive feedback and words of encouragement.