HOME

Teaching Online Journalism

Get started with Web coding. Part 4: Software and CMSs

See all posts in this series.

This post deals with two common assumptions:

  1. You need to learn particular software programs (e.g. Dreamweaver) so you can make things for the Web.
  2. Journalists work inside corporate content management systems (CMSs), so there’s no need for them to know Web coding.

Both of those are incorrect. Let’s proceed.

Software for Web work

Dreamweaver is a nice program. I’ve used it for many years. But you don’t need it, and what’s more, too many people unknowingly make a lot of very bad code because they are using Dreamweaver. This last is the basis for my strongest objection to Dreamweaver: It does not help you learn how to use code correctly.

Another reason to ignore Dreamweaver: You’re not likely to find Dreamweaver in most professional newsrooms.

The software a Web coder needs:

In teaching journalism students, I think it’s worthwhile to spend some time teaching an image editing program, because serious ethical issues are involved in photo editing.

The text editing programs require no instruction. Every student can download and use those programs without help.

FireZilla FTP program

A demonstration of FTP might be helpful. Students can be surprisingly clueless about how the Web works. What happens when you type a URL into your Web browser? Where are those files that the browser downloads for you? They are on a Web server. How does the Web server interact with the Web browser on your computer? If you don’t understand how to manage files and folders on your own computer, and on your server, you’re going to run into problems.

No time should be spent teaching Dreamweaver.

‘Infect the CMS’

That was the title of a session at the 2013 NICAR conference, presented by Heather Billings, Jacob Harris and Al Shaw. The gist of the idea: Coders cannot build news apps, or data apps, inside the CMS — the content management system.

The CMS is built for handling articles, text, and photos. Maybe it handles video well, or maybe not. The CMS is not flexible. It expects articles, and pages that are like a big table of contents, with links to articles. The CMS does not expect an interactive animated feature with multiple options. The CMS does not expect a map that allows interactions.

Screen from "Infect the CMS" presentation

So innovative features, interactive features, must be built (by coders) outside the CMS. And then (as explained in “Infect the CMS”) the coders must build new hooks into the system that allow those features to be discoverable — to be found by the CMS search engine, to be visible in the CMS archives, to show up in the “related items” sidebars of related stories in the CMS.

So when you hear someone say, “Journalism students don’t need to learn code, because they will always work inside a CMS,” you need to remember that every CMS has limitations. The limitations prevent innovation inside the CMS — so all the innovation must take place outside.

Those who cannot work outside the CMS are trapped in the CMS.

WordPress and hosted Web templates

A writer who wants only to write does not need to learn any code at all to have a website. Anyone can start a free blog at WordPress.com and write to her heart’s content.

A student or professional who wants to create an online portfolio of photos, videos, articles, etc., can do so at various sites, including Wix, Weebly and Squarespace. No coding required.

Wix home page

So the person who says, “I want to learn to code,” really needs to think, first, what he or she wants to do online. What does he want to build? If all he wants is to display old media works — photos, illustrations, text, videos — then code is not required.

If you want to design the future, these readymade templated sites will not help you do that.

If you want to design the future, learn to code.

This Series


Categories: code, teaching, training


6 Comments

  1. @bobstep says:

    .@macloo Agree, and I first heard both in 1999. “Two common assumptions are wrong – about #journalists and code…” http://t.co/fiZui4lEqe

  2. I’ll disagree a bit with FTP. It’s pretty darn rare I ever touch FTP, and it’s basically unusable for teams. I firmly believe Git should be the requirement instead of FTP.

  3. @Dave Stanton – At some point you have to put it on a server. Or you’re doing that with Git only?

  4. Mu Lin says:

    Mindy, would you agree that “data tools are for everyday work of every digital journalist, and coding is for special features by data specialists”? Data visualization tools such as infogr.am and Tableau Public provide a “what you see is what you get” interface for data coding, in a way similar to what Dreamweaver does with html coding. If we can do web design without learning html coding, then we can also expect to do data visualization without learning data coding.

  5. @Mindy McAdams – Yep, Git only or even better if deployment script (though clearly that’s unnecessarily gnarly for getting started). But Git works everywhere. That’s how I move stuff even to shared hosting like Bluehost or Dreamhost. Way less chance of failure than FTP.

  6. Re: Using Git, not FTP. Certainly for production teams, this is true. But for journalism students working solo, they would need a lot of hand-holding to get comfortable with Git, and much less for straight-up FTP. That said, I’m thinking hard about how to make Git a viable addition to my classes.

    I do agree that not every digital journalist needs to be a hard-core code jockey, but data visualization is one thing; becoming familiar with code, how it works, and how to manage your files and their interaction — that’s another thing. I don’t think most journalism students are well-served by assignments that throw them into using a specific tool (which might vanish in a year or two). Students make way more egregious errors in Dreamweaver than they do when they code HTML and CSS by hand in a text editor.

    I strongly disagree with the statement “we can do web design without learning html coding.” Well, yes — we CAN do it. That’s true. But the code produced by people who don’t know how to code outside Dreamweaver is very bad code. My students are not well served by using Dreamweaver to produce crap code.

Leave a Reply