<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Big Red Tin &#187; web design</title>
	<atom:link href="http://bigredtin.com/tag/web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://bigredtin.com</link>
	<description>Thoughts about the web and business from the large pantry</description>
	<lastBuildDate>Wed, 08 Feb 2012 06:55:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>!important is Important</title>
		<link>http://bigredtin.com/2011/css-important-is-important/</link>
		<comments>http://bigredtin.com/2011/css-important-is-important/#comments</comments>
		<pubDate>Thu, 02 Jun 2011 00:52:54 +0000</pubDate>
		<dc:creator>Peter Wilson</dc:creator>
				<category><![CDATA[Behind the Websites]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Responsive Web]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://bigredtin.com/?p=1110</guid>
		<description><![CDATA[The <code>!important</code> declaration has really bad reputation, and deservedly so. As is often the way, this reputation results from abuse rather an inherent problem with the property itself.]]></description>
			<content:encoded><![CDATA[<p>The <code>!important</code> declaration has really bad reputation, and deservedly so. As is often the way, this reputation results from abuse rather an inherent problem with the property itself. An example of its abuse might be:</p>
<pre><code>#nav {
  float: none !important;
  /* where did I float this? */
}
/* ...jumble of code... */
ul#nav {
    float: left;
}</code></pre>
<p>There are, however, instances where the <code>!important</code> declaration is the best tool for the job.</p>
<p><span id="more-1110"></span></p>
<h3>Responsive Web</h3>
<p>The increase of users accessing web sites via mobile devices has redefined the way many design for the web. Rather than considering the desktop first, they now consider the mobile user. Andy Clarke&#8217;s <a href="http://stuffandnonsense.co.uk/projects/320andup/">320 and Up</a> is one reaction to this.</p>
<p>A requirement of the responsive web is that images expand and contract according to the width of the browser. To achieve this, the advice to define the width and height in the <abbr>HTML</abbr> has been reversed, an image should now be added without these attributes.</p>
<pre><code>&lt;img src="img.png" <del>width="30" height="30"</del> /&gt;</code></pre>
<p>This leads to problems when redesigning a site, images in previous blog posts and older content could have the width and height defined. If the site uses a <abbr>CMS</abbr> with a visual editor, it may add the dimension to an image by default and content editors may unwittingly break the layout by leaving them in place.</p>
<p>To allow for this, I usually add the following to the <abbr>CSS</abbr></p>
<pre><code>img {
  height: auto !important;
  max-width: 100% !important;
}</code></pre>
<h3>Print Styles</h3>
<p>There are certain elements that are almost always hidden from print styles: skip links, navigation, and oversized footers, for example. Backgrounds are also removed as they&#8217;re not printed by default. Changes to the screen layout won&#8217;t alter these needs. To avoid future problems, it is legitimate to include the following in your style sheet:</p>
<pre><code>@media print {
  #nav, #footer, .sidebar {
    display: none !important;
  }
  .has-a-background {
    background: #fff !important;
  }
}</code></pre>
<p><a href="http://bigredtin.com/2011/css-important-is-important/#comments">Leave a comment</a> with your thoughts if you frequently use <code>!important</code> for other purposes, agree or disagree.</p>
<p><strong>Update 16 Nov, 2011:</strong> changed <code>img</code> code block. </p>
]]></content:encoded>
			<wfw:commentRss>http://bigredtin.com/2011/css-important-is-important/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The &#8220;D&#8221; Word</title>
		<link>http://bigredtin.com/2009/the-d-word/</link>
		<comments>http://bigredtin.com/2009/the-d-word/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 00:23:44 +0000</pubDate>
		<dc:creator>Josh Kinal</dc:creator>
				<category><![CDATA[Behind the Websites]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[graphic design]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web production]]></category>

		<guid isPermaLink="false">http://soupgiant.com/?p=285</guid>
		<description><![CDATA[To call oneself a 'Web Designer' is about as accurate and explanatory as saying 'I work with computers'.]]></description>
			<content:encoded><![CDATA[<p>Wikipedia has a <a href="http://en.wikipedia.org/wiki/Web_designer">long and annoyingly complicated article about web design</a>, which begins:</p>
<blockquote><p>Web design is the skill of creating presentations of content (usually hypertext or hypermedia) that is delivered to an end-user through the World Wide Web, by way of a Web browser or other Web-enabled software like Internet television clients, microblogging clients and RSS readers.</p></blockquote>
<p>So, &#8216;creating presentations&#8217; you say. To call oneself a &#8216;Web Designer&#8217; is about as accurate as saying &#8216;I work with computers&#8217;.</p>
<blockquote><p>Saving files in HTML format is now a common feature in Office 2000 programs. In other words, you can save Word documents in HTML format and you can publish Excel workbooks as Web pages. <br /><em>&#8211; taken from <a href="http://office.microsoft.com/en-us/help/HA010548931033.aspx?pid=CH010485191033" title="Mircosoft Office 2000 Help">Opening and saving files in Office</a></em></p></blockquote>
<p>For years now we&#8217;ve been able to export Microsoft Word documents as HTML files. By Wikipedia&#8217;s definition, everybody everywhere who has ever created a word document could be called a &#8216;Web Designer&#8217;.</p>
<p>This topic came up recently because we had the phrase &#8216;web designer&#8217;, or something like it, on our <a href="http://bigredtin.com/about/">About</a> page. Meanwhile, on our portfolio page we had some, admittedly ambiguous, text about a specific piece of work we had done before Soupgiant was created.</p>
<p>This caused confusion. We received a demanding email from the graphic designers responsible for that work that we explain ourselves. Apparently their client saw our site and said &#8220;somebody&#8217;s taking credit for your design work&#8221;.</p>
<p>It took a little while before we worked out where the confusion. At no point did we intend to take credit for the design. As a matter of course we outsource all our graphic design because that is not our skill-set.</p>
<p>The common term is &#8216;Web Design&#8217;, but we don&#8217;t do design. Can we be &#8216;Web Engineers&#8217; without having an engineering degree? What about &#8216;Web Architects&#8217;?</p>
<p>We&#8217;ve decided to go with the term &#8216;Web Production&#8217; because what we do is more akin to a Producer&#8217;s role than anything else. We coordinate the production of websites and content. We can create, or organise the creation of, audio and video for podcasts. We can code but we also work with information architecture, testing, usability, and accessibility.</p>
<p>We bring together all the things that go into making a website. We stay up-to-date on technologies to ensure our clients get the best product possible for their budget. We coordinate, we define, we build, we code, we acquire, we provide, but we do not design. At least, we don&#8217;t do it well. We hire graphic designers to do that because that&#8217;s <em>their</em> area of expertise.</p>
<p><em>Our</em> area of expertise is creating excellent, accessible and functional websites using every resource we have at our disposal.</p>
]]></content:encoded>
			<wfw:commentRss>http://bigredtin.com/2009/the-d-word/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

