To get started, we got Github Accounts, and pulled open Github in Chrome. We downloaded github desktop and visual studio code. I ran into some problems with passwords and codes.
As we got ourselves started, we talked about how important building basic web pages and full stack development can be. The end goal here is to be able to show this to your students. asa job interview, if you cannot talk about version control, you’ll be booted from the interview. Github is a standard of version control methodology. Github version control can keep things clean and easy.
First its a file management tool. Next its a synchronization location between computers. Last it can be used for version control. Most websites require 5 pages, folder for scripts, folder for images, folder for styles. Git is the language or protocol for working with files.
We talked about protocols. We talked about the inventor of LINUX. We talked about how GIT hub was used to host files in the cloud for easy storage and retrieval. why would a small business want to have a server in their office? Github was bought for 7Billion by microsoft. there are over 100,000 abandoned software packages up there. There are also millions or billions of files there in active use.
We talked about dry code (well done work coded once) and wet code (repeated materials on multiple pages). Not everyone can do this in early classes, but as time moves on, it become essential. Everythin in Github is public. so cheating could occur. There is also an option for private to 3 individuals for free. So, some items can be private to the teacher and then hidden from classmates.
Repo is a repository. The extensions in here are MD. This represents Markdown language. The README.MD file will post its information by default at the bottom.
We had a chance to look at the repositories for this event.
- Github based on Git
- Linus Torvaldis created git after frustrations with existing (or non-existing) version control: https://en.wikipedia.org/wiki/GitHub
- Took two weeks and applied his unique mindset… so some stuff is a bit… odd
- Many use via CLI (Command Line Interface)
- Github (not to be confused with git) was a company built around providing repositories (“repos”) using the git protocol.
- Microsoft paid $7 BILLION for github in 2018
- git and github have quickly moved to a dominant position in the version control space, with git now supported in a variety of environments and with many supporting tools, in addition to the original CLI
- if your students graduate without version control experience you are doing them a disservice
- it makes all kinds of things a lot easier, including: — maintaining copies of projects in multiple locations — collaborating with students and between students — tracking and merging changes — creating public repos, including webpage support (and wikis and tasks and much more)
Then we moved over into the tasks section.
- Remember IGNORE and EXPLORE (IE)
- Create github account on http://github.com
- Login (and stay logged in to) your email
- Create a repo – — I suggest either NCCIA2020-LastnameFirstMI – i.e. NCCIA2020 von Briesen DI or — Course name in format YEAR-COURSEID-LastName or just COURSEID (i.e. CSC143-general or WEB110 von Briesen) — Github will put dashed wherever you have spaces in the repo name – you can change the name on the fly, but note what github changes your name to. — Choose options for creating a readme.md file and enabling web content
- Edit your readme file — check out MD (MarkDown) tutorials/cheatsheets: https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf – you can also use html — write something about your repo.
- open up Github Desktop for Windows — login to your account — clone your repo — open your repo in visual studio and/or file explorer — create an index.html file with something simple like
Yo! It’s my repo webpage!!
— save this file. — make a change to the readme.md file (i.e. “I edited this document on my computer, not on the web!!”). Save this file. — note how the changes show up in github desktop. Commit changes (saves to repo) and push origin (pushes up to server). You cannot commit more than one file without updating the note (single files don’t require a note/summary). — view your repo on it’s website: http:/yourid.github.io/yourreponame
Commits are ways of saving to your repository
CHoose to initialize with readme. You can use this for an attendance task. First, you open your project folder and look at the files. Then you check them in your EDITOR. Then push them to the internet and check them on the web.
We opened up the repo, and adjusted the Readme. After saving, we can see the adjustments- with color changes.
If we’re making 2+ file changes, they must be committed individually. If no problem, add text and you’ll be allowed to commit to the repository.
We then moved to the online material and changed … then we saw the differences between fetch and pull. Fetch gets the original, pull open the issue. When conflicts take place, both sides are shown and you can work this out.
I see this is an easy way to keep materials together.
Visual Communication Using Adobe Photoshop CC 2015 ACA Certification Achieved!
In the middle of the NCCIA conference, I had the opportunity to take a scheduled examination. The Adobe Certified Associate (ACA) certification allows you to demonstrate proficiency in Adobe digital communications tools. Become a Certified Associate and you will stand apart from your peers, boost your confidence, and expand your career opportunities.
The Visual Communication Using Adobe Photoshop exam validates skills in communication corresponding to Photoshop software. Adobe conducted research to identify the foundational skills needed to effectively communicate using digital media tools. Based on feedback from educators, design professionals, businesses, and educational institutions around the world, the objectives cover skill expectations for professional visual communication.
The following skills were assessed on the Visual Communication Using Adobe Photoshop exam:
- Domain 1.0 Setting Project Requirements
- 1.1 Identify the purpose, audience, and audience needs for preparing images.
- 1.2 Demonstrate knowledge of standard copyright rules for images and image use.
- 1.3 Demonstrate knowledge of project management tasks and responsibilities.
- 1.4 Communicate with others (such as peers and clients) about design plans.
- Domain 2.0 Identifying Design Elements When Preparing Images
- 2.1 Demonstrate knowledge of image resolution, image size, and image file formats for web, video, and print.
- 2.2 Demonstrate knowledge of design principles, elements, and image composition.
- 2.3 Demonstrate knowledge of typography.
- 2.4 Demonstrate knowledge of color correction using Photoshop.
- 2.5 Demonstrate knowledge of image-generating devices, their resulting image types, and how to access resulting images in Photoshop.
- 2.6 Understand key terminology when working with digital images.
- Domain 3.0 Understanding Adobe Photoshop
- 3.1 Identify elements of the Photoshop user interface and demonstrate knowledge of their functions.
- 3.2 Demonstrate knowledge of layers and masks.
- 3.3 Demonstrate knowledge of importing, exporting, organizing, and saving.
- 3.4 Demonstrate knowledge of producing and reusing images.
- 3.5 Demonstrate an understanding of and select the appropriate features and options required to implement a color management workflow.
- Domain 4.0 Manipulating Images by Using Adobe Photoshop
- 4.1 Demonstrate knowledge of working with selections.
- 4.2 Use Photoshop guides and rulers.
- 4.3 Transform images.
- 4.4 Adjust or correct the tonal range, color, or distortions of an image.
- 4.5 Demonstrate knowledge of retouching and blending images.
- 4.6 Demonstrate knowledge of drawing and painting.
- 4.7 Demonstrate knowledge of type.
- 4.8 Demonstrate knowledge of filters.
- Domain 5.0 Publishing Digital Images by Using Adobe Photoshop
- 5.1 Demonstrate knowledge of preparing images for web, print, and video.