<?xml version="1.0" encoding="utf-8"?>
<feed version="0.3" xmlns="http://purl.org/atom/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en">
  <title>Solutions for Adobe Products</title>
  <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/" />
  <modified>2006-07-25T18:19:26Z</modified>
  <tagline></tagline>
  <id>tag:blog.pixelmill.com,2006:/dreamweaver/7</id>
  <generator url="http://www.movabletype.org/" version="3.2">Movable Type</generator>
  <copyright>Copyright (c) 2006, corrie</copyright>
  <entry>
    <title>Doctype made easy</title>
    <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/2006/07/doctype_made_easy.html" />
    <modified>2006-07-25T18:19:26Z</modified>
    <issued>2006-07-20T09:55:17-08:00</issued>
    <id>tag:blog.pixelmill.com,2006:/dreamweaver/7.46</id>
    <created>2006-07-20T17:55:17Z</created>
    <summary type="text/plain"><![CDATA[When you create a new page in Dreamweaver, the first line of code usually looks something like this: &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt; Ever wondered what that means? Understanding the docctype statement, as that line is called,...]]></summary>
    <author>
      <name>corrie</name>
      <url>www.pixelmill.com</url>
      <email>chaffly@pixelmill.com</email>
    </author>
    
    <content type="text/html" mode="escaped" xml:lang="en" xml:base="http://blog.pixelmill.com/dreamweaver/">
      <![CDATA[<p>When you create a new page in Dreamweaver, the first line of code usually looks something like this:</p>

<p>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;</p>

<p>Ever wondered what that means? Understanding the docctype statement, as that line is called, requires a very, very brief history lesson. Don't worry, I'll make it brief.</p>

<p>HTML started with a very basic list of tags (and rules on how to use them) back in 1989. Over the years, more tags were added (and some removed), so HTML came out with version 2, version 3, version 3.2, version 4, and finally 4.1. XHTML was then developed. (To make it even more confusing, we have different versions of HTML 4.1 and XHTML  -- a "strict" version that has very strict rules, a "transitional" version that is a little more loose, and a "frames" version for sites that use frames.)</p>

<p>(Wasn't that brief?) </p>

<p>These different versions of HTML and XHTML have slightly different rules for how -- and which -- HTML tags can be used in a document and how to format them. Just to give you a quick example, XHTML has stricter rules than HTML -- the tags have to be lowercase and certain tags (&lt;u&gt; for underlining) can't be used at all. In HTML, tags like &lt;br&gt; and &lt;link&gt; now require a "closing slash" in XHTML, so they <em>must</em> be written like &lt;br /&gt; and &lt;link /&gt;.</p>

<p>So for optimized viewing of the site, the browser should be able to tell what version of HTML/XHTML you're using. That's when the doctype statement comes in. Compare these different doctype statements below:</p>

<p>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;</p>

<p>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;</p>

<p>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"&gt;</p>

<p>The doctype tag contains the information about which DTD, or document type definition, is being used, and contains a web address that links to the full explanation of that language.</p>

<p>Now, what's great about Dreamweaver (which was the point of this blog) is that you don't have to worry about keeping track of which tags you can or can't use and how your code should be formatted. As soon as you set the doctype of your web site, Dreamweaver handles the code for you automatically. Even if you are used to hand-coding an &lt;img&gt; or a &lt;br&gt; tag in the old-school HTML way, if your doctype is set to XHTML, Dreamweaver automatically adds the closing slash for you.</p>

<p>You can change the docctype by typing Ctrl-J (Command-J for Macs) to access the page properties, then going to TItle/Encoding and changing the Document Type. (You can also right-click on the page itself and choose Page Properties.) Once you do that, Dreamweaver formats your code accordingly!</p>]]>
      
    </content>
  </entry>
  <entry>
    <title>What do you want to learn?</title>
    <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/2006/04/what_do_you_want_to_learn.html" />
    <modified>2006-04-24T17:38:27Z</modified>
    <issued>2006-04-24T09:35:22-08:00</issued>
    <id>tag:blog.pixelmill.com,2006:/dreamweaver/7.34</id>
    <created>2006-04-24T17:35:22Z</created>
    <summary type="text/plain">Our Dreamweaver Support knowledgebase area is pretty bare-bones right now. We&apos;re always looking to add on more tutorials and knowledgebase articles to PixelMill&apos;s support knowledgebase. So... what do you want to know? Feel free to post a comment....</summary>
    <author>
      <name>corrie</name>
      <url>www.pixelmill.com</url>
      <email>chaffly@pixelmill.com</email>
    </author>
    
    <content type="text/html" mode="escaped" xml:lang="en" xml:base="http://blog.pixelmill.com/dreamweaver/">
      <![CDATA[<p>Our <a href="http://www.pixelmill.com/support/al1012.htm">Dreamweaver Support</a> knowledgebase area is pretty bare-bones right now. We're always looking to add on more tutorials and knowledgebase articles to PixelMill's support knowledgebase. So... what do you want to know? Feel free to post a comment.</p>]]>
      
    </content>
  </entry>
  <entry>
    <title>Why Use Libraries and Templates?</title>
    <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/2006/01/why_use_libraries_and_template.html" />
    <modified>2006-01-19T19:02:02Z</modified>
    <issued>2006-01-19T11:01:03-08:00</issued>
    <id>tag:blog.pixelmill.com,2006:/dreamweaver/7.22</id>
    <created>2006-01-19T19:01:03Z</created>
    <summary type="text/plain">Libraries are a feature of Dreamweaver that allow you to use the same content on multiple pages. What this means is that you can have repeated content on multiple pages, but only have to edit the content in one place....</summary>
    <author>
      <name>corrie</name>
      <url>www.pixelmill.com</url>
      <email>chaffly@pixelmill.com</email>
    </author>
    
    <content type="text/html" mode="escaped" xml:lang="en" xml:base="http://blog.pixelmill.com/dreamweaver/">
      <![CDATA[<p>Libraries are a feature of Dreamweaver that allow you to use the same content on multiple pages. What this means is that you can have repeated content on multiple pages, but only have to edit the content in one place.</p>

<p>Let's say that you have a news box that appears on every page. Without libraries, you would have to open each and every page and edit the news box anytime you wanted it updated. WIth libraries, the news box can be a library item, included on each page, but only requiring that you edit and save the library item. One change, one save, and every page with the library item gets updated. Dreamweaver libraries make this kind of editing a breeze!</p>

<p>Templates, or .dwt files, are similar but different -- you have a main template page with a specific layout, and the content areas in the layout can be defined to change for each page. The similarity with include pages is that if you update the template, all pages "attached" to the template will update. The difference is that templates control an entire page layout, while libraries control a component of a page. You can have multiple templates used in the same web site - for example, you could have a 2-column .dwt and a 3-column .dwt. Our designers can help make it seamless when switching from one template to another by keeping the same "editable areas;" when you switch templates, essentially all that changes is where on the page those content areas end up.</p>

<p>Now, let's say that six months down the road you decide that it's time for a new look for your site. Without DWTs, you'd have to create or download the new design template, open every page of your site, copy and paste all the content from each page into the page template, save-as, modify the meta tags and title for each page ... you can see it would be quite a job. But <em>with</em> DWTs, you would create or download a new DWT and then apply the design to your pages with two or three clicks! </p>

<p>PixelMill Dreamweaver templates are all required to use DWTs, and most of them use libraries for items like the header or footer as well. (The real power of Libraries comes in the components that you create for yourself -- such as my news box example from before!) Also, most of our DWTs are DWTIG-compliant, which is another blog topic in itself, but for now it will suffiice to say that DWTIG-compliant templates make applying a new design truly seamless.</p>]]>
      
    </content>
  </entry>
  <entry>
    <title>Making accessibility easy</title>
    <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/2006/01/making_accessibility_easy.html" />
    <modified>2006-01-17T00:19:36Z</modified>
    <issued>2006-01-16T16:19:48-08:00</issued>
    <id>tag:blog.pixelmill.com,2006:/dreamweaver/7.20</id>
    <created>2006-01-17T00:19:48Z</created>
    <summary type="text/plain">Dreamweaver makes accessibility a few steps easier! First, let&apos;s look at the accessibility report tool, which was also available in some previous versions of Dreamweaver. If you go to Site &gt; Reports, you can check the Accessibility report option and...</summary>
    <author>
      <name>corrie</name>
      <url>www.pixelmill.com</url>
      <email>chaffly@pixelmill.com</email>
    </author>
    
    <content type="text/html" mode="escaped" xml:lang="en" xml:base="http://blog.pixelmill.com/dreamweaver/">
      <![CDATA[<p>Dreamweaver makes accessibility a few steps easier!</p>

<p>First, let's look at the accessibility report tool, which was also available in some previous versions of Dreamweaver. If you go to Site > Reports, you can check the Accessibility report option and then click Run.</p>

<p><img alt="dw-accessibilityreport.png" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/dw-accessibilityreport.png" width="450" height="365" /></p>

<p>In the Reports panel, look first for the red X's, which signify where your page actually failed.</p>

<p><img alt="dw-accessibilityreport2.png" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/dw-accessibilityreport2.png" width="567" height="285" /></p>

<p>You can then fix the problem or click the "information" icon in the left of the panel to learn more about why it's a problem.</p>

<p>The other question marked items are things that need to be manually checked. Glance through the list and look for possible problem areas.</p>

<p>One of my favorite features about the new Dreamweaver is that when you insert a picture, a dialog box automatically comes up for you to add ALT informatin or a Long Description link:</p>

<p><img alt="dw-accessibility.png" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/dw-accessibility.png" width="477" height="202" /></p>

<p>No longer do I have to remember to add the ALT description - Dreamweaver 8 makes it easy!<br />
</p>]]>
      
    </content>
  </entry>
  <entry>
    <title>Dreamweaver 8: Better CSS Rendering</title>
    <link rel="alternate" type="text/html" href="http://blog.pixelmill.com/dreamweaver/2005/11/testing.html" />
    <modified>2005-11-08T22:19:39Z</modified>
    <issued>2005-11-08T14:04:03-08:00</issued>
    <id>tag:blog.pixelmill.com,2005:/dreamweaver/7.13</id>
    <created>2005-11-08T22:04:03Z</created>
    <summary type="text/plain">I recently installed Dreamweaver 8. I haven&apos;t even begun to fully delve into the changes and improvements, but right away I knew that I was going to love it when I noticed how much better the &quot;Design View&quot; rendering of...</summary>
    <author>
      <name>corrie</name>
      <url>www.pixelmill.com</url>
      <email>chaffly@pixelmill.com</email>
    </author>
    
    <content type="text/html" mode="escaped" xml:lang="en" xml:base="http://blog.pixelmill.com/dreamweaver/">
      <![CDATA[<p>I recently installed Dreamweaver 8. I haven't even begun to fully delve into the changes and improvements, but right away I knew that I was going to love it when I noticed how much better the "Design View" rendering of CSS-based layouts was. No more floating elements were forced to the bottom of the page; the page looked just as it would in any popular browser. With the ability to outline divs in dotted lines or to even color them with different background colors, working with CSS-based layouts has been made easier than ever.</p>

<p>Take a look! Here's a CSS-based layout page (no tables used) in Dreamweaver's Design View:</p>

<p><img alt="cssrendering1.jpg" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/cssrendering1.jpg" width="450" height="261" /></p>

<p>The visual aids button helps you to quickly toggle on or off the dotted borders, called CSS Layout Outlines:</p>

<p><img alt="cssrendering2.jpg" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/cssrendering2.jpg" width="450" height="261" /></p>

<p>You can also display the CSS Layout Backgrounds, which hides any backgrounds you've defined and gives each div its own background color. It's very useful for figuring out what's going on with your CSS layout.</p>

<p><img alt="cssrendering3.jpg" src="http://blog.pixelmill.com/dreamweaver/dreamweaver/images/cssrendering3.jpg" width="450" height="261" /></p>

<p>I'll be posting more Dreamweaver 8 tips and tricks as I discover or use them!<br />
</p>]]>
      
    </content>
  </entry>

</feed>