imventura
commented
6 years ago Evaluation HW-01 for maisybyerly
| Topic | Excellent | Satisfactory | Needs Work |
|---|---|---|---|
| Coding style | * | ||
| Coding strategy | * | ||
| Presentation | * | ||
| Achievement, creativity | * | ||
| Ease of access | * |
Remarks:
-
Elaborate on above, especially for "needs work." Presentation was creative and streamlined.
-
Some specific praise? Code was easy to read and understand.
-
Something I learned? How to do a hyperlink that is a different text than the link.
-
Specific constructive criticism? Though I don't know how to do this either, it would be great if you could make the photo smaller so it doesn't overpower your text.
-
Something I know and that you, my peer, might like to know because it is relevant to something you struggled with. Another way to embed an image is the following: Clode:
Then, have the png image in your repository and upload it with the .md file.
cernhofer
My process: I forked the class repository using the clone/download button. I copied the url of my forked repository. I clicked new project -> version control -> git, and entered the url. Once there, I opened README.md. I typed into the file directly, rather than the console. I pushed my changes to github after every single small edit. That was useful for internalizing the push/pull process. I kept github open to make sure that my changes had updated every time.
The most difficult edits were adding a link and adding a photo. I used a photo of myself from the web, because I thought that would be easier then using a local file. I am still interested in trying to use a local file. My photo and link didn't work initially because I had a space between the [ ] and the ( ).
I found this guide to authoring on github helpful. It's similar to the github one, but its section on links is clearer because it included the text "linked phrase." After reading that guide, I updated my inputs with great success.