Read & Respond week 16 – Best of US!

April 20, 2017

Here it is: Your final read & respond! This one will be easy. You’ll be assessing your own work, based on the material you provided me. Based on the following examples, you’ll be voting (via this Google Forms ballot) on the following categories:

NOTE: If your name doesn’t have links, you need to provide them to me!

Group Blog Honors

Note: You can’t vote for your own group unless otherwise indicated!

The Groups (group-selected posts are linked):

The Categories

1. Best Post on a Group Blog (can’t vote for your own post, but can vote for a post by your group)

2. Most Improved Group Blog

3. Best Group Blog Overall

Personal Blog Awards

Note: You can’t vote for yourself!

The Personal Blogs (best posts provided by you)

Mateo Alexander Post 1 Post 2
Lindsey Baatz Post 1 Post 2
Rachel Brosky Post 1 Post 2
Ashley Conley Post 1 Post 2
Cara Devenney Post 1 Post 2
Steven Devine Post 1 Post 2
Denali Hedrick Post 1 Post 2
Madalyn Lamastro Post 1 Post 2
Carly Magnotta Post 1 Post 2
Haley Moore Post 1 Post 2
Zaakira Muhammad Post 1 Post 2
Cayla Nolder Post 1 Post 2
Aishina Shaffer Post 1 Post 2
Shannon Stanley Post 1 Post 2
Mia Swanegan Post 1 Post 2
Jackie Thompson Post 1 Post 2
Rebecca Toro Post 1 Post 2
Laura Vázquez-López Post 1 Post 2

The Categories

1. Best Post on an Individual Blog

2. Most Improved Personal Blog

3. Best Personal Blog Overall

Superlatives

Nominate another blogger for a “Most/Best ____” category (e.g., Best use of GIFs, Most Likely to Proofread Everyone’s Work)

Nominate yourself for something at which you think you excel (e.g., Best Interviewer of Homeless Persons) or perhaps are notorious for (e.g., Most Likely to Get Caught Texting)

The usual deadline applies, but you don’t have to respond as a comment. Instead, complete the ballot on Google Forms by 11:59 p.m. Monday, April 24 (note the extended deadline).


Class coding: HTML #2

April 19, 2017

This week, we start with the foundation from earlier this week and add lists and styles (learned this in this week’s Codecademy module: Web Fundamentals: HTML Basics II):

Remember these basics for coding and previewing your work:

To preview in TextWrangler:

  1. Open Chrome and TextWrangler
  2. In Chrome, go to File > Open File… and open “index.html”
  3. Command-Tab to select TextWrangler and write code
  4. Command-Tab to select Chrome
  5. Command-R to refresh your webpage

You’ll do the following:

  1. Use/create WWW folder; create “index.html”; add structural tags
  2. Create a comment inside that says “In-class assignment #2: HTML2”
  3. Create a first-level heading and an intro paragraph
  4. Create a second-level heading and an ordered list of your top three books, movies, or bands
  5. Create a fourth-level heading and an unordered list of skills you possess
  6. Add a fourth item to the ordered list (step 4) and add an image to it

Too easy? Try these:

  1. Change background color of page
  2. Change style of top headline to Verdana font family, a different color, and centered alignment
  3. Change style of your intro paragraph to 30px, a different color, and centered alignment

Class Coding: HTML 1

April 17, 2017

After completing your first Codecademy assignment in Web Fundamentals (HTML I) and showing me your completion badges, do the following:

  1. Preparation:
    • Create a desktop folder called WWW
    • Open TextWrangler (or another text editor), create a new file called “index.html” and save to WWW
    • Save two images (ideally with short names) to your WWW folder
  2. Place your structural tags
  3. Create a title
  4. Add a first-level headline and one paragraph
  5. Bold a few words. Italicize a few other words.
  6. Insert an image
  7. Add a second-level headline and another paragraph
  8. Create a hyperlink to the SOJ homepage within this paragraph
  9. Add a third-level hed and another image
  10. Make this second image into a hyperlink

To preview in TextWrangler

  • In Chrome, go to File > Open File… and open “index.html
  • Command-Tab to select TextWrangler and write code
  • Command-Tab to select Chrome and Command-R to refresh your webpage

To view a webpage’s source code

  • Chrome: View > Developer > View Source
  • Firefox: Command-U OR Tools > Web Developer > Page Source
  • Safari (why are you using Safari???): Develop > View Page Source

Read & Respond week 13 – Video

April 6, 2017

This week’s readings are mostly viewings. To start, though, let’s have a moment of silence for Vine. The six-second-video-sharing app is owned by Twitter, which in October announced plans to shut it down. In a nutshell, Vine could be used to create and share a six-second clip of anything … just how useful can that be?

There are several possible reasons. For one, Twitter has been scaling back in the hopes of turning a profit. For another, livestreaming apps have horned in on its territory. Periscope (also owned by Twitter) is popular and defeated competition like Meerkat, and Facebook Live is perhaps even more popular; one mark in Facebook Live’s favor is the use of the social networking giant’s ability to note popularity of specific points in a stream through viewer likes and reactions. This is our current social media world: Ideas live, they die, they live again (but under new management).

So how do you livestream? The Providence Journal has some suggestions, as does HuffPost. Is livestreaming something you’d try? How can we apply this to the practice of journalism, and what are its problems?

Before Wednesday’s class (we’ll be editing podcasts on Monday), give livestreaming a try. Take a few minutes on Facebook Live to broadcast something you’d like to share – it’s a good idea to tell your followers in advance so interested parties can check it out – and see what you think. We’ll discuss!

Post your responses in a comment to this post by 11:59 p.m., Sunday, April 9.