Craft Content Nashville 2017

I’m presenting a session at Craft Content Nashville 2017 called Let’s Talk Multimedia this Saturday (April 8) at 3:15 in Design Room 2. The session will  provide an over-view of what designing for multimedia means and what goes into digital content creation. The Twitter hashtag is #CCN17Multimedia. Craft Content Nashville is located at Nossi College of Art.

Whether you are a podcaster, blogger, iBook creator, citizen journalist, or small business owner needing media for your FaceBook or LinkedIN account, the goal is to accomplish a goal. The goal may be to sell, inform, educate, entertain, or get our visitor to sign up for our email list. The best way to engage our audience is to tell a story. How can we work a story into our multimedia? It requires that we have a plan. Come to the session and let’s discuss it.

The Presentation

Here is the presentation I used for the session. It’s a Prezi presentation so it won’t work on mobile. Here is the pdf for download.

Did you like my session. Let’s connect. What are you working on?

Talking to the browser

When we code in HTML, CSS, JS, etc. we are communicating to the browser. That’s what we do as web designers. We are telling the browser how to display content. The browser understands many different languages. It understands, HTML, CSS, JavaSript, XML, SVG and others. Each of those languages have their own syntax. For the browser to interpret the languages correctly we have to tell the browser which language we are using.

For example, when we link an external stylesheet, the browser is expecting to see only CSS characters in the .css file. We link it as <link rel="stylesheet" type="text/css" href="someFileName.css">. We are telling the browser that we are linking a file that has a relationship to the HTML file as a stylesheet and is using text characters that should be interpreted as CSS code. The browser is expecting something very specific. If you give it something other than what it is expecting, you will get errors.

The > character does exist in CSS, but it doesn’t mean the same thing as it does in HTML.

wwwroot

In the unit A project the author has you create a folder named wwwroot. Why?

When you get a web host account, you’ll find that there a number of folders that you have to work with. One folder will be the designated folder where all of your publicly accessible web files will be located. Different hosts call that folder different things. I’ve seen:

  1. public_html
  2. public
  3. wwwroot

I’m sure there are other folder names in use by other web hosts.

Vodnik asks you to create a folder called wwwroot to put your web files into. So does that mean that ALL your files go there. Not necessarily. You will find that a lot of files go into creating a project. The wwwroot folder in this case will be the upper-most folder for web files for this project. Unless the project plan, wireframes, and storyboard(s) are documents that you want the public to see, you keep them out of the web site folder. This is mostly a good file management practice. If the file is not needed for the web site, then it really doesn’t need to be under the web site’s root folder.

Will having a non web site file under the root folder break the site? No.