Category: WebTeacherTips

Curation in an Age of Information Overload

Information. There’s so much of it. What’s a teacher to do to help filter out the debris and collect the gems?

One solution is Twitter lists. Set up a list of people on Twitter who say things you want your students to notice. Then go to paper.li and create an account. Set it up to create a daily paper from the tweets of the people on your list. You’re done. Your effort from then on is just a daily scan through the paper to see if anything great pops out at you.

See Why I’m Loving Paper.li for more.

Another solution is to set up a list of web sites and blogs that you want to watch at scoop.it. This takes more effort, both to set up and to curate. You get a daily reminder to go curate the search results for the day. This takes maybe 5 minutes. Most of what shows up will be rejected, but the quality articles can be “scooped up” and added to your information. And there is a bookmarklet for any post you find outside of the scoop.it search that makes it easy to add to your site.

See HTML5 News for an example.

There are other services that let you collect and share. Tumblr. Pinterest. Posterous. Storify. Even the bookmarking sites like Delicious – even though they feel a bit old fashioned now.

I like to post and comment on useful links. I want to let you know all the helpful articles I see during my day. That feels a bit old fashioned, too, but it also feels like sharing what I love. It helps me remember, too. If I post a useful link here and say something about it, I’m more likely to remember it than if I click a bookmarklet to add something to Tumblr or Scoop.it.

What works for you?

 

Guest Post: 7 Things Everyone in Your Organization Should Know

This weekend, I attended the Online News Association Conference in Boston. It was a great gathering of multimedia developers and those concerned with all things digital – quite a fantastic event. I had the opportunity to participate on a panel called “If I Were in Charge, I’d…” Proposals for the panel were solicited before the conference, and mine was one of six selected. The presentation is below, but I wanted to provide a few more details, beyond the eight minutes I had to present. And I wanted to see if there was any feedback or critique. Rob Quigley live blogged the entire session, if you’d like to see the other topics and presenters.

ONA: 7 Things Everyone Should Know

View more presentations from clroyal

Are you in charge? Maybe you’re an editor or a general manager of a newsroom, or perhaps you’re a dean or director of a university organization. Maybe you lead a media company that specializes in PR or Advertising. Do you consider yourself in charge of a digital media organization? And, does everyone in your organization know that they work in a digital media organization?

Does everyone in your organization know what an API is and why that’s important? Do they know what SEO means and what value it brings the organization? Are they familiar with the type of CMS your organization uses and how it works? And do they know some basic concepts like HTML or how to embed a video or widget onto another Web page?

If I were in charge, I’d be making sure everyone associated with the organization – every reporter, columnist, copy editor, photographer, videographer, every faculty member, every associate – I’d even go as far as saying that every person who answers the phone – knows these things and more. This is not the template for a two-hour workshop. This is not a quick fix or a tweak. This is a tectonic shift in the ways that people envision what it is they are expected to know and do and the kind of organization for which they work.

I propose 7 Things Everyone in a Digital Media Organization Should Know:

1. Everyone would know the history and background of the Web.

Why? Because it’s fun to study the history of something. And, it provides a foundation for understanding the future. By learning about the role of the ARPAnet (and later Tim Berners-Lee in Switzerland), the people involved and the culture surrounding the development of the Internet, we begin to see what makes this environment different. We can learn about the origins of hacker and open source culture and why this presents an alternative and a complement to commercialization. Oh, and we’d know that Al Gore didn’t invent the Internet, and that he never actually said he did.

2. Everyone would understand the key terms of digital media.

We must speak the same language in order to collaborate and have a shared understanding. You can’t have the tech folks spewing jargon while the rest of the organization stands around the sidelines and rolls their eyes. We’re not talking about buzzwords and marketing posturing, but things that everyone needs to know, like what an Application Programming Interface (API) is and why you might use one, why your organization should have them and who benefits from them. When we talk about the “cloud,” what do we mean and how is that different than where we’ve been hosting things all along? What is Search Engine Optimization and how does that compare to Social Media Optimization? What do we mean when we use the phrase “data visualization” and what are these platforms (frameworks) of Ruby on Rails and Django? People may not actually perform these functions or use these platforms, but they should have a clue about what they are and what they do.

3. Everyone would know how Google makes money.

Why? Because Google makes a lot of money. And I bet most of your organization has never paid anything to Google to use their multitude of services. Google has a $170B market cap, one of the most successful companies in history. They made the majority of their $29B in revenue in 2010 with advertising – those little ads you see on the sides and the sponsored links on the top of your Google search. But it’s the power of their search algorithm and their ability to provide products to us that are useful and that integrate with our lives, that allows them to continue to learn more and more about us. Knowledge is power, right?

4. Everyone would be able to explain why social media is important.

No, Twitter’s not about what you ate for breakfast. And Facebook’s not just a place to upload photos of your kid’s birthday party. A modern media organization understands that interaction is the key. The technologies known as Web 2.0 drive interaction with the audience that was unheard of in prior eras. They make media a conversation, and those conversations have value. People are gaining an expectation of participation because of their participation on social networks, and they will begin to find media irrelevant that don’t give them something to do, don’t provide a user experience. Get ready for new social platforms to be introduced over time. Google, who is the king of search, is now trying to develop social competencies with Google+. Location-based platforms, reviewer sites, online games… new things are coming out every minute. But you can’t expect people to understand them if they don’t use them. People should be encouraged to try new things. And they should be comfortable with the idea of using social media to develop their own brand or to support that of the organizations with which they work.

5. Everyone would understand how data can tell a story.

That doesn’t mean that everyone will know how to program a data visualization. But everyone should understand that a data visualization is an important element of storytelling, just like text, photos, video, other graphics. The benefit is the interaction, the ways that you develop to integrate the user into the story. There are a million ways to do this, and we are just starting to see brilliant examples of this type of work by organizations like the New York Times, the Guardian, the LA Times, the Texas Tribune, the Associated Press, the Chicago Tribune, ProPublica and more. The example I used in my presentation is the Rent vs. Buy interactive that the New York Times did several years ago, but is still updated on their site. You can read a story about whether or not you should rent or buy a house, but how does that really help someone make their own decision, with their own variables? Everyone needs to understand the power of this type of information and comprehend their role in creating it. How would they propose such a project? Who will they work with? What tools can they use and what resources are out there? This doesn’t mean someone needs to tell them or train them. They need to be focused enough on the importance of it that they are seeking out this information on their own and figuring out ways to integrate it into their own workflow. That’s how the people who are doing this kind of work learned it… by figuring it out themselves.

6. Everyone would know a little HTML (and some CSS for that matter).

Why? Because it’s the language of the Web. If you don’t know the language, you can’t understand the platform. You need to know HTML to maximize your ability to customize the things you do in blog or content management systems. And it is the foundation for more advanced coding, like CSS, Javascript, JQuery and on and on. For the most part, code snippets are available in libraries, so what most people are doing when they work in code is tweaking and customizing, rather than cranking it out from scratch. It’s not that everyone should become a programmer, but it wouldn’t hurt to know a bit about how it all works. Knowing a little html can go a long way in being able to read and tweak code (like reading a foreign language versus writing or speaking it). And, it’s not hard. It’s a markup language, using tags to give meaning to text. It fits in perfectly with a communicator’s skill set. And it’s fun to learn.

7. Everyone would understand the elements of a digital-, and increasingly mobile-, first strategy.

Until this happens, your organization will still be mired in legacy culture. People need to understand how it changes the processes of the newsroom, how their roles change, and most importantly, how it affects the experience of the user. Breaking a story on Twitter is the new “scoop.” The analysis and conversations that happen after is what a news organization does now. Sure, you still produce a paper or newscast, but that’s only a part of what you do. It’s what you share all day long and what others share of the work that you are doing that establishes your brand and your value. You have to re-prioritize that to your organization.

So, as I said above, this isn’t about developing a 2-hour workshop and then going back to the way things have always been. We’re not a weekend behind and then we’re all caught up. Digital media has been developing for the better part of two decades, and it’s time everyone who works in media realizes they work for a digital media organization. We can’t solve the pressing problems of the field with just a few who are in-the-know. We need everyone to be working toward the same goals, gaining knowledge and contributing to the solutions. This will require constant, ongoing and consistent messaging in the following areas:

  • Leadership must evangelize from the top – it’s not enough to have the tech people at the grass roots take responsibility for training the whole organization. Leadership must communicate that it is everyone’s responsibility to keep up-to-date and learn. It must be a consistent part of all messaging, all meetings, the mission and goals of the organization.
  • Foster a meetup culture – how can they learn? Well, for one, they can start attending any of the multitude of professional meetups that are probably already happening in their area. These resources exist. There are regular presentations on relevant topics, and you don’t even have to organize them. Just make sure your organization knows that it is an expectation that people participate. And, people should gain a level of comfort in going to groups where they don’t feel like they have a command of the material. Don’t be afraid to be the stupidest person in the room. In fact, that’s preferable. That’s when you learn. And, like a lot of this stuff, it’s fun. You meet people, who may be able to help you professionally, or guess what..? You just might end up with a few new friends. Personally, I view my professional network for its power in assisting my students, but I really enjoy meeting people and learning about these topics, and have made some wonderful contacts in the process. Don’t attend a meetup that you dread or hate. Find one that interests you. They’re out there.
  • Encourage innovation through exploration – It should be expected that people try new things when they are released. Get on Google+, try Foursquare and Gowalla, sign up for Storify… Guess what? They’re free. Yes, they take time. But if that’s what your job is, then you are using that time wisely. Having a little knowledge about a new platform and some perspective can be quite beneficial when trying to weigh options and quickly make decisions about the usage and relevance of platforms. And you don’t want to ignore new technologies to the point that you suddenly have “unexpected” time on your hands, do you?
  • Read tech/media publications – This should be a given. We expect people to keep up with news, be on top of things, know their beats, keep up with trends. Well, this is our business now, so shouldn’t we expect people to keep up with it? Know about the key players, tech mergers, new media projects, startups. There are numerous publications, but Wired, Fast Company and a multitude of blogs, like Mashable, 10,000 Words and TechCrunch, are a good start.

I have had success in sharing these concepts with students. My feeling is that they gain an enthusiasm for the future of media by having it presented in this manner. These are opportunities, not annoyances. There are challenges, but everyone needs to be on board so they can be overcome. If I were in charge, I’d find a way to make everyone excited about the future of media.

Are you in charge? What do you think about these points? Does everyone in your organization know these things? Maybe you’re not “in charge.” I’m not either. This was just a hypothetical exercise. But what do you think your organization should do to integrate these concepts, if you think they are valid at all? Let me know if you have any additional items or if you just think I’m full of it. I’ll be interested in any discussion generated.

Some resources I have used:

The Internet: Behind the Web – it’s an old video, and is probably only available on VHS (I have since dubbed it DVD), but it’s a great way to learn about the history of the ARPANet, Internet and Web. It has some abridged content from the longer series Nerds 2.0.1

Download: The True Story of the Internet – this is a great series that covers Browsers, Search, E-Commerce and Social Networking. It brings everything up to date after the above video.

Hacks/Hackers Glossary – a great set of terms and definitions developed by the main Hacks/Hackers organization. Their a meetup group, probably a chapter in your area, that brings journalists and programmers together.

Lynda.com – this is a software and programming training library. It costs money, but on a month-by-month basis, it’s cheaper than purchasing a book to learn a particular language or platform.

South By Southwest – You should attend conferences. ONA is fantastic. Another one that I love is the South By Southwest Interactive Festival. It’s huge and broad, but nothing has influenced my approach to teaching media than my regular attendance, year after year, at this event. And, like a lot of these recommendations, it’s fun. Trust me on this one. Plan to attend SXSW in March.

Guest Post by Cindy Royal. This post was originally published at Cindy’s Take on Tech.

The Secret of Building a Table with Dreamweaver

It’s easy peasy to create a table in Dreamweaver. It’s not so easy to create a table in Dreamweaver that sticks to the ideal of separation of content from presentation and uses CSS rather than HTML to determine presentation.

If you want to build a table for your web page that does use best practice rules and will be responsive to every potential situation, there are a lot of things in Dreamweaver that you should not do. I’m going to show you what not to do, explain why, and give you a best practice alternative.

The insert table dialog box

Do not put anything in the table width, border thickness, cell padding, or cell spacing boxes. Do select the appropriate heading type for your table, and do enter a caption and summary if needed.

table dialog box

I added an X to the boxes that you should leave empty. Table width, border thickness, cell padding, and cell spacing options are all used to add HTML presentation to the table. You want to keep the width, border, and padding presentation rules in the CSS. It’s best to use percentage widths for the various table rules rather than pixels. (See Adding borders to data tables with CSS for information about adding border with CSS.)

The Document Window

When you create a table the way I just described, you see something like this in your Dreamweaver document.

empty table in DW Document window

Insert the cursor in the first table cell so you can enter text and Tab your way into the next table cell. As you enter text, the table expands to fit the text you’ve entered. Padding for the td cells and other width and spacing rules to make the table more attractive go in the CSS.

table with text

It’s possible to drag the borders of the table around in the document window. This is another thing you should not do. As you can see in the image below, when you drag the table borders to resize it, absolute pixel values appear and are written into the HTML. In your stylesheet, use the width property for selectors like table, th, and td to set widths in percentages or ems for your table.

table border being dragged

The Properties panel

While you’re entering data in the table, you see table properties in the Properties panel. This is another set of options that you should not touch.

Properties panel

Do not enter pixel values in the width or height boxes. Do not select a background color for the table or for individual table cells. I’ve put an X in the forbidden fields in the image above. All of these options add HTML presentation to the table. You want to set these presentation values in the CSS. The image above shows the Properties panel with the HTML toggle selected. When the CSS toggle is selected, entering values into the width and height boxes also results in values coded into the HTML, not added to the style sheet as you might expect when the CSS toggle is active.

That’s it. Most of what Dreamweaver offers as table controls need to be left alone, and the majority of your work needs to happen in the stylesheet, not in the Document window. You can create a table that will work for all your users on just about any device if you learn what not to touch.

Modifying an hReview microformat to include HTML from schema.org

Google, Yahoo and Bing announced schema.org yesterday.

Many sites are generated from structured data, which is often stored in databases. When this data is formatted into HTML, it becomes very difficult to recover the original structured data. Many applications, especially search engines, can benefit greatly from direct access to this structured data. On-page markup enables search engines to understand the information on web pages and provide richer search results in order to make it easier for users to find relevant information on the web. Markup can also enable new tools and applications that make use of the structure.

A shared markup vocabulary makes easier for webmasters to decide on a markup schema and get the maximum benefit for their efforts. So, in the spirit of sitemaps.org, Bing, Google and Yahoo! have come together to provide a shared collection of schemas that webmasters can use.

I immediately began to think about how this would apply to my frequently used hReview microformat. I looked at the schema for books, and tried to see how I could incorporate that into a book review if I continue to use the hReview microformat to do book reviews.

Here’s what I came up with. I’d love comments. The additions to the hReview from the book schema are in red.

<div class="hreview"
itemscope itemtype="http://schema.org/Book">
<span style="display:none">product</span>
<p><img class="photo" src="image.jpg" alt="alt here"></p>
<div class="description" itemprop="reviews">
<p><a class="fn url" itemprop="name url" href="link here"
title="affiliate link to Amazon"><cite>book title
here</cite></a>
by <span itemprop="author">author's name</span> is from
 <span itemprop="publisher">publisher's
name</span>, <span itemprop="datePublished">date
here</span>.
Text of the review here.</p>
<p>Text of the review here.</p>
<p>Text of the review here.</p>
<p class="summary">Summary: text of the summary</p>
<p><span class="reviewer vcard">A review by
<a href="http://www.webteacher.ws/" rel="me">Virginia
DeBolt</a></span> of <cite itemprop="name">
book title here</cite>
<span class="rating" itemprop="rating">
(rating: n stars)</span></span></p>
</div>
</div>

What I’m wondering.

  1. Is the hReview microformat even needed since there is so much overlap between the book schema and the hReview microformat. It’s redundant. Should reviewers switch to the schema and abandon the microformat?
  2. I’m wondering about putting an itemprop in the cite element, since most of the schema HTML is added with span tags. It seems more semantic to me.

What do you think? Are schemas going to replace microformats completely?

Want to get in on Google +1? Here’s how.

Google +1 is now live. If you want to make it part of your process, here are some tips for getting started.

Add it to Your Web Page

Using +1

Hypermile your CSS

Have you heard these rules for best practices in web design?

  1. Keep your HTML as lean as possible – stick with plain old semantic HTML (POSH)
  2. Put all your presentation rules in the CSS

Well, it’s possible to do #2 while failing at #1. That’s because of a condition known as classitis. Classitis is a condition in which your HTML is cluttered up with multiple classes when just one would do the trick. Classitis happens when the class attribute gets attached to the wrong element in your HTML.

An example of classitis

Look at this code. The purpose is to style the contents of a blockquote to look a particular way.

<blockquote>
<p class="pullout">Yakkity yak, don't look now but this is classitis.</p>
<p class="pullout">Yakkity yak, don't look now but this is classitis.</p>
<p class="pullout">Yakkity yak, don't look now but this is classitis.</p>
</blockquote>

Notice the class applied to each paragraph in the blockquote? That’s a bit of overkill that adds a class rule into your HTML in three places, when only one would be enough.

Hypermile that class

You can make the same thing happen more efficiently and with leaner HTML. Here’s how.

<blockquote class="pullout">
<p>Yakkity yak, this blockquote is lean and mean.</p>
<p>Yakkity yak, this blockquote is lean and mean.</p>
<p>Yakkity yak, this blockquote is lean and mean.</p>
</blockquote>

Apply the class to the parent or container element – in this case the <blockquote>. The results will be the same as if you had applied the class to every individual element within that container.

The same kind of thinking would apply if you were styling a list. Apply the class to the <ul> or <ol> element, not to each individual <li>. If you were styling text in a <div>, <article> or <section>, apply the class to the parent element rather than to child elements like paragraphs within a div or article.

Multiple Background Images with CSS3

There are two background images on the demo page. The page is a standard Dreamweaver HTML template page, with the styles in the document head. To add a second background image URL, the Dreamweaver style element must be edited manually.

Here’s the relevant rule:

background: url(img/Adelie_Penguin-sm.jpg) right bottom no-repeat,
#FFF url(img/bg.jpg) repeat;

You can view the results in this demo page, if your browser supports it.

If your browser does not yet support multiple background images, here is a screen shot of the Opera browser rendering of this rule.

background images demo screen shot

The various background images are in a comma separated list. The order of the images listed by url in the background rule is important. You can think of the list like layers in Photoshop or like z-index stacking. The first image in the list is at the top of the stacking order. As you add more and more background images to the list, they move to the back in the stacking order.

If the penguin image were second, it would be obscured by the repeating background. However, if the second background image were not repeating, but instead had a no-repeat placement and the top left, then both images would be visible and the listing order of the urls in the background rule would seem to be less significant. Nevertheless, it’s a good habit to keep stacking order in mind when listing the urls for multiple background images — background images in specific positions might overlap each other if the page is resized.