From abe5e88f172e77c6e9a72e9dd0aac987db78f7eb Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Wed, 4 Sep 2019 16:42:45 -0400 Subject: [PATCH 1/8] Answered 3 Reasons --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3b21c11..05d64ac 100644 --- a/README.md +++ b/README.md @@ -20,9 +20,9 @@ A repo to play with the common git operations in and learn how to get working wi ## Working definition of Git and what it's done for ## What do you think the top 3 reasons to use GitHub / GitLab are? -1. -2. -3. +1. It's the most popular version control system out there. +2. The community is alive. +3. Github is very user-friendly. ## What is a Pull Request? From eda6247d0b3ca18b3449d68557ba93c1ebce1965 Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Wed, 4 Sep 2019 16:54:07 -0400 Subject: [PATCH 2/8] Answered Questions --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 05d64ac..e45d79b 100644 --- a/README.md +++ b/README.md @@ -18,20 +18,21 @@ A repo to play with the common git operations in and learn how to get working wi # FILL THINGS OUT BELOW THIS LINE AND DO IT IN MARKDOWN ## Working definition of Git and what it's done for - +Git is a version control platform that uses the command line to manipulate branches. ## What do you think the top 3 reasons to use GitHub / GitLab are? 1. It's the most popular version control system out there. -2. The community is alive. -3. Github is very user-friendly. +2. **The community is alive.** +3. *Github is very user-friendly.* ## What is a Pull Request? - +A pull request is informing other users of a project about the changes you are pushing to a branch. Pull requests can become conversations discussing the changes once opened. ## Links to relevent Github / git tutorials - [Github](https://github.com/) -- Add a resource link here -- Add another resource link here +- [Help - Github](https://help.github.com/en) +- [YouTube](https://www.youtube.com/) ### Change this image to be something else with different alt data You can also do images like the one just below here using the ! ![Oh Spongebob](https://media.giphy.com/media/3oEjI4sFlp73fvEYgw/giphy.gif). +![Forever Alone](https://giphy.com/gifs/forever-alone-CSORTyXB78REI) From acfb1437b977865a1722dbdb9df99af2b6dd8c9a Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Wed, 4 Sep 2019 16:55:26 -0400 Subject: [PATCH 3/8] Fixed Gif --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e45d79b..eb70542 100644 --- a/README.md +++ b/README.md @@ -35,4 +35,4 @@ A pull request is informing other users of a project about the changes you are p ### Change this image to be something else with different alt data You can also do images like the one just below here using the ! ![Oh Spongebob](https://media.giphy.com/media/3oEjI4sFlp73fvEYgw/giphy.gif). -![Forever Alone](https://giphy.com/gifs/forever-alone-CSORTyXB78REI) +![Forever Alone](https://media.giphy.com/media/gtoONZQegPnPy/giphy.gif) From ca9e396ccb4809f89d4879f03f15b31b906e23ef Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Sun, 8 Sep 2019 16:52:53 -0400 Subject: [PATCH 4/8] Updated Reflection with relevant information --- Reflection.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/Reflection.md b/Reflection.md index 01e5b18..9729e8d 100644 --- a/Reflection.md +++ b/Reflection.md @@ -1,9 +1,12 @@ -# My Reflection / Blog -Use this file to submit your blog post to your github account / repo. In it, include some markdown to practice, especially a link to your video. -*Screencast submission* - [YouTube video by HAXcms core contributor Michael Potter](https://www.youtube.com/watch?v=5aPae031TxM&list=PLJQupiji7J5cGYiOflGYFwXSEoHMoowkP&index=17&t=0s) -Here's a reminder of how you do the link above as code. -```markdown -*Screencast submission* - [YouTube video by HAXcms core contributor Michael Potter](https://www.youtube.com/watch?v=5aPae031TxM&list=PLJQupiji7J5cGYiOflGYFwXSEoHMoowkP&index=17&t=0s) -``` +# My Reflection / Blog - Michael Wisser +**Class Section:** IST 402.002 +**Date:** September 8, 2019 -Good luck! +## MWiz - Markdown Explanation + Video + This is MWiz today and I will be discussing the popular text-to-HTML conversion tool used in Github, Markdown. Markdown is a text-to-HTML tool meaning that it takes text information and transforms it into HTML for better readability on documentation. Markdown is very popular with software developers, especially on version control software like Git. A popular alternative to Markdown is reStructuredText which both seem very similar on the surface but differ in semantics and extensibility (“reStructuredText vs Markdown for documentation”). + +*M Wiz explains it: Markdown* - [video](https://youtu.be/Li9GBICGSq4) + +## My Thoughts: + Markdown is an excellent lightweight markup language and text-to-HTML conversion tool, but I did not fully understand it when I had started using it. For one, the goal behind Markdown is the idea of **readability**. Readability is being able to make any piece of information as easy to understand as possible if that information is only read. This is accomplished by appealing to the mind’s perceptive nature by making certain things bolder, italicized, underlined, bigger, or smaller, to emphasize the purpose of the information. Markdown is not just limited to doing just that, it can also separate things via boxes, use lists to number information (or to better represent attributes of the key piece of information), and much more. As someone without too much experience about what formatting should be used to emphasize what, I may not be making my documentation as readable as it should be. I may be abusing the **bold** formatting too much when I should be *italicizing* more and I would not know. Feedback is extremely important by people whom have experience in Markdown and using Markdown for documentation, as I can better understand which formatting I should use to appeal to the reader and make my documentation more understandable. + My favorite aspect of Markdown is how simple most of the formatting is accomplished. It limits a lot of the potential spelling errors that could be made writing normal HTML. Making a word bold in HTML uses the tags and to close the bold tag but in Markdown it is reduced to just two asterisks between a word or series of words: *This sentence is definitely foo, but not bar*. It’s not a difficult markup language to pick up at all and it is very effective when applied to documentation. From b75c066d96593ec3baa44249dea756c6ea31c70d Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Sun, 8 Sep 2019 16:54:33 -0400 Subject: [PATCH 5/8] Fixed link --- Reflection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reflection.md b/Reflection.md index 9729e8d..c6417f2 100644 --- a/Reflection.md +++ b/Reflection.md @@ -5,7 +5,7 @@ ## MWiz - Markdown Explanation + Video This is MWiz today and I will be discussing the popular text-to-HTML conversion tool used in Github, Markdown. Markdown is a text-to-HTML tool meaning that it takes text information and transforms it into HTML for better readability on documentation. Markdown is very popular with software developers, especially on version control software like Git. A popular alternative to Markdown is reStructuredText which both seem very similar on the surface but differ in semantics and extensibility (“reStructuredText vs Markdown for documentation”). -*M Wiz explains it: Markdown* - [video](https://youtu.be/Li9GBICGSq4) +*M Wiz explains it: Markdown* - [video](https://youtu.be/oL6i30vi4LQ) ## My Thoughts: Markdown is an excellent lightweight markup language and text-to-HTML conversion tool, but I did not fully understand it when I had started using it. For one, the goal behind Markdown is the idea of **readability**. Readability is being able to make any piece of information as easy to understand as possible if that information is only read. This is accomplished by appealing to the mind’s perceptive nature by making certain things bolder, italicized, underlined, bigger, or smaller, to emphasize the purpose of the information. Markdown is not just limited to doing just that, it can also separate things via boxes, use lists to number information (or to better represent attributes of the key piece of information), and much more. As someone without too much experience about what formatting should be used to emphasize what, I may not be making my documentation as readable as it should be. I may be abusing the **bold** formatting too much when I should be *italicizing* more and I would not know. Feedback is extremely important by people whom have experience in Markdown and using Markdown for documentation, as I can better understand which formatting I should use to appeal to the reader and make my documentation more understandable. From 28776f0fe2c97fe31c58e128d406df6b0b8bcc07 Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Sun, 8 Sep 2019 16:59:44 -0400 Subject: [PATCH 6/8] added links --- Reflection.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Reflection.md b/Reflection.md index c6417f2..4c291da 100644 --- a/Reflection.md +++ b/Reflection.md @@ -3,10 +3,15 @@ **Date:** September 8, 2019 ## MWiz - Markdown Explanation + Video - This is MWiz today and I will be discussing the popular text-to-HTML conversion tool used in Github, Markdown. Markdown is a text-to-HTML tool meaning that it takes text information and transforms it into HTML for better readability on documentation. Markdown is very popular with software developers, especially on version control software like Git. A popular alternative to Markdown is reStructuredText which both seem very similar on the surface but differ in semantics and extensibility (“reStructuredText vs Markdown for documentation”). + This is MWiz today and I will be discussing the popular text-to-HTML conversion tool used in Github, Markdown. Markdown is a text-to-HTML tool meaning that it takes text information and transforms it into HTML for better readability on documentation. Markdown is very popular with software developers, especially on version control software like Git. A popular alternative to Markdown is reStructuredText which both seem very similar on the surface but differ in semantics and extensibility (“reStructuredText vs Markdown for documentation”). There exists plenty of helpful guides on the web for learning an using Markdown: + -Markdown Guide Website: [Site](https://www.markdownguide.org/getting-started) + -Github’s Guide to Markdown: [Site](https://guides.github.com/features/mastering-markdown/) + -Markdown Cheat-sheet: [Site](https://www.markdownguide.org/cheat-sheet/) + *M Wiz explains it: Markdown* - [video](https://youtu.be/oL6i30vi4LQ) ## My Thoughts: Markdown is an excellent lightweight markup language and text-to-HTML conversion tool, but I did not fully understand it when I had started using it. For one, the goal behind Markdown is the idea of **readability**. Readability is being able to make any piece of information as easy to understand as possible if that information is only read. This is accomplished by appealing to the mind’s perceptive nature by making certain things bolder, italicized, underlined, bigger, or smaller, to emphasize the purpose of the information. Markdown is not just limited to doing just that, it can also separate things via boxes, use lists to number information (or to better represent attributes of the key piece of information), and much more. As someone without too much experience about what formatting should be used to emphasize what, I may not be making my documentation as readable as it should be. I may be abusing the **bold** formatting too much when I should be *italicizing* more and I would not know. Feedback is extremely important by people whom have experience in Markdown and using Markdown for documentation, as I can better understand which formatting I should use to appeal to the reader and make my documentation more understandable. + My favorite aspect of Markdown is how simple most of the formatting is accomplished. It limits a lot of the potential spelling errors that could be made writing normal HTML. Making a word bold in HTML uses the tags and to close the bold tag but in Markdown it is reduced to just two asterisks between a word or series of words: *This sentence is definitely foo, but not bar*. It’s not a difficult markup language to pick up at all and it is very effective when applied to documentation. From 3eac1f475600e253587ccfa06ddb23994e54c9a7 Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Sun, 8 Sep 2019 17:02:20 -0400 Subject: [PATCH 7/8] updated --- Reflection.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/Reflection.md b/Reflection.md index 4c291da..8ebccd1 100644 --- a/Reflection.md +++ b/Reflection.md @@ -4,14 +4,17 @@ ## MWiz - Markdown Explanation + Video This is MWiz today and I will be discussing the popular text-to-HTML conversion tool used in Github, Markdown. Markdown is a text-to-HTML tool meaning that it takes text information and transforms it into HTML for better readability on documentation. Markdown is very popular with software developers, especially on version control software like Git. A popular alternative to Markdown is reStructuredText which both seem very similar on the surface but differ in semantics and extensibility (“reStructuredText vs Markdown for documentation”). There exists plenty of helpful guides on the web for learning an using Markdown: - -Markdown Guide Website: [Site](https://www.markdownguide.org/getting-started) - -Github’s Guide to Markdown: [Site](https://guides.github.com/features/mastering-markdown/) - -Markdown Cheat-sheet: [Site](https://www.markdownguide.org/cheat-sheet/) + - Markdown Guide Website: [Site](https://www.markdownguide.org/getting-started) + - Github’s Guide to Markdown: [Site](https://guides.github.com/features/mastering-markdown/) + - Markdown Cheat-sheet: [Site](https://www.markdownguide.org/cheat-sheet/) *M Wiz explains it: Markdown* - [video](https://youtu.be/oL6i30vi4LQ) ## My Thoughts: + +### Struggles Markdown is an excellent lightweight markup language and text-to-HTML conversion tool, but I did not fully understand it when I had started using it. For one, the goal behind Markdown is the idea of **readability**. Readability is being able to make any piece of information as easy to understand as possible if that information is only read. This is accomplished by appealing to the mind’s perceptive nature by making certain things bolder, italicized, underlined, bigger, or smaller, to emphasize the purpose of the information. Markdown is not just limited to doing just that, it can also separate things via boxes, use lists to number information (or to better represent attributes of the key piece of information), and much more. As someone without too much experience about what formatting should be used to emphasize what, I may not be making my documentation as readable as it should be. I may be abusing the **bold** formatting too much when I should be *italicizing* more and I would not know. Feedback is extremely important by people whom have experience in Markdown and using Markdown for documentation, as I can better understand which formatting I should use to appeal to the reader and make my documentation more understandable. - - My favorite aspect of Markdown is how simple most of the formatting is accomplished. It limits a lot of the potential spelling errors that could be made writing normal HTML. Making a word bold in HTML uses the tags and to close the bold tag but in Markdown it is reduced to just two asterisks between a word or series of words: *This sentence is definitely foo, but not bar*. It’s not a difficult markup language to pick up at all and it is very effective when applied to documentation. + +### What I liked +My favorite aspect of Markdown is how simple most of the formatting is accomplished. It limits a lot of the potential spelling errors that could be made writing normal HTML. Making a word bold in HTML uses the tags and to close the bold tag but in Markdown it is reduced to just two asterisks between a word or series of words: *This sentence is definitely foo, but not bar*. It’s not a difficult markup language to pick up at all and it is very effective when applied to documentation. From 6fcb63c4e941c8177c1aaee59e05ee230523535b Mon Sep 17 00:00:00 2001 From: realMWiz <54648087+realMWiz@users.noreply.github.com> Date: Fri, 13 Sep 2019 23:04:00 -0400 Subject: [PATCH 8/8] Update Reflection.md --- Reflection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reflection.md b/Reflection.md index 8ebccd1..ef4adcb 100644 --- a/Reflection.md +++ b/Reflection.md @@ -1,4 +1,4 @@ -# My Reflection / Blog - Michael Wisser +# My Reflection / Blog - Mhykol W **Class Section:** IST 402.002 **Date:** September 8, 2019