Jack

Sort of. Your parent div with a width of 100% is likely in the center, but you just can't see it because it spans full width. It won't center the child items automatically, the way this is usually done is to wrap them in a smaller container like in my example above. If you want the text to be centered inside of that, you can use text-align. I've updated my example here to show how that works https://codepen.io/anon/pen/JyKoxv.

I've changed your HTML slightly to add a class. I would recommend not styling this class, but treating it as something that binds your JS and HTML.
 
https://jsfiddle.net/g25mehjh/

Linking block elements is valid as of HTML5. That said, linking the text inside your paragraph, setting that to display block, and using padding is possibly more semantic in this case.

Without being able to test anything out it's hard to say, the docs leave a lot to be desired. For example, if {{ blog.id }} is the ID of the blog entry you're on, you should be able to match it to {{ article.id }}
{% assign currentPageId = blog.id %} <ul> {% for article in blog.articles limit:20 %} <li>{{ article.id }} - {{ currentPageId }}</li> {% endfor %} </ul> Otherwise, you could probably grab the current article ID, loop through a list of all articles and find one that matches.
{% assign currentArticleId = article.id %} <ul> {% for article in blog.articles limit:20 %} <li>{{ article.id }} - {{ currentArticleId }}</li> {% endfor %} </ul>

Try
{{ product.vendor | downcase | replace: ' ', '-' }}

You may need to do something like this.
{% if tag contains 'meta-related-collection-' or tag contains 'cf-' or tag contains '_' %} {% endif %} You will need to ask Shopify directly, but basically it would be nicer to pass in an array instead.
{% assign supportedTags = ['meta-related-collection-', '-', 'cf-'] %} {% if tag in supportedTags %} content {% endif %} This code won't work, it's a mixture of a similar language called Twig, and Shopify's Liquid, but it should give you an indication to at least go back to Shopify with.

I don't this this is a CSS issue. You're missing a parameter called viewBox.
 
At the top:
 
<svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" version="1.2" width="402" height="201.55145" id="svg2987"> Should be: <svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" version="1.2" width="402" height="201.55145" viewBox="0 0 402 201.55145" id="svg2987">  

Some folders and files will require stricter permissions, so be careful not to set the whole system as 777.
 
There's a plugin that scans your files and folders to check if they're the right permissions.

Glad it worked

I would suggest removing those floats in favor for display: block; and display: inline-block;.
 
Items in red you remove, items in green you add to your styles.

.post .text {
float: left;
min-height: 80px;
}

.contact-form input[type=email] {
display: block;
}

This file > http://live.bobosh.com/selector/style.css.
body {font:13px/20px Arial,sans-serif;color:#ccc;text-shadow:0 1px 1px rgba(0,0,0,0.4);overflow:hidden;}  

Absolutely, but it can be avoided. There's a good post here about it.

You need to update your path to ../lightbox/images E.G ../lightbox/images/close.png

It could be a number of things:
 
Your file path is incorrect (I tend to store my fonts in a folder called 'fonts' and use the following in my stylesheet ../fonts/ instead of the website URL. Your server does not support the mime types required for @font-face (http://stackoverflow.com/questions/3594823/mime-type-for-woff-fonts as an example). You are not targeting the correct element in your CSS. Try using H1 as a selector instead of #content2 ( h1 { font-family: 'AngelinaRegular';} ). Your issue could be browser specific, have you tested in a few? Alternatively take a look at http://www.fontsquirrel.com/blog/2010/11/troubleshooting-font-face-problems.