<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Adobe Muse enables great Web layout, no coding required</title>
	<atom:link href="http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 17:32:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Darryl Manco</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-51089</link>
		<dc:creator>Darryl Manco</dc:creator>
		<pubDate>Tue, 30 Oct 2012 21:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-51089</guid>
		<description><![CDATA[Muse, a flexible tool for the traditional graphic designer who has clients that want a designer exterior website.  No offense intended, but the web is not print or vise versa.  Alas, the web isn’t that simplistic.  Today’s competing website owner needs to be concerned with the behind because web noise is deafening.  Then there is the front; it complements its back.  The two become the tool for marketing on the web.]]></description>
		<content:encoded><![CDATA[<p>Muse, a flexible tool for the traditional graphic designer who has clients that want a designer exterior website.  No offense intended, but the web is not print or vise versa.  Alas, the web isn’t that simplistic.  Today’s competing website owner needs to be concerned with the behind because web noise is deafening.  Then there is the front; it complements its back.  The two become the tool for marketing on the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trenton Bria</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-49787</link>
		<dc:creator>Trenton Bria</dc:creator>
		<pubDate>Tue, 25 Sep 2012 18:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-49787</guid>
		<description><![CDATA[Will there ever be anywhere else We can get facts about this? I&#039;m thinking I might possibly write my term paper on it.]]></description>
		<content:encoded><![CDATA[<p>Will there ever be anywhere else We can get facts about this? I&#8217;m thinking I might possibly write my term paper on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat Korten</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-48153</link>
		<dc:creator>Pat Korten</dc:creator>
		<pubDate>Fri, 03 Aug 2012 20:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-48153</guid>
		<description><![CDATA[I would very much like to be able to import an existing website into Muse so that I can work with it there rather than in Dreamweaver.  Is there ANY way it can be done?]]></description>
		<content:encoded><![CDATA[<p>I would very much like to be able to import an existing website into Muse so that I can work with it there rather than in Dreamweaver.  Is there ANY way it can be done?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yve Legler</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-44440</link>
		<dc:creator>Yve Legler</dc:creator>
		<pubDate>Fri, 25 May 2012 18:14:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-44440</guid>
		<description><![CDATA[Rob, go to www.Lynda.com. They have excellent video Tutorials, including MUSE
Yve]]></description>
		<content:encoded><![CDATA[<p>Rob, go to <a href="http://www.Lynda.com" rel="nofollow">http://www.Lynda.com</a>. They have excellent video Tutorials, including MUSE<br />
Yve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yve Legler</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-44439</link>
		<dc:creator>Yve Legler</dc:creator>
		<pubDate>Fri, 25 May 2012 18:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-44439</guid>
		<description><![CDATA[I can&#039;t agree with you more, but it is outdated, is having problems and has no more support. As a designer I have been pushing Dreamweaver away as to complicated. Muse seems just what I need as a designer. What about the GoLive built Website? Can it be imported into Muse? Any suggestions?
Thanks
Yve]]></description>
		<content:encoded><![CDATA[<p>I can&#8217;t agree with you more, but it is outdated, is having problems and has no more support. As a designer I have been pushing Dreamweaver away as to complicated. Muse seems just what I need as a designer. What about the GoLive built Website? Can it be imported into Muse? Any suggestions?<br />
Thanks<br />
Yve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SSS</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-38144</link>
		<dc:creator>SSS</dc:creator>
		<pubDate>Thu, 27 Oct 2011 18:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-38144</guid>
		<description><![CDATA[Adobe needs to pay attention to the comments on this page.  I am extremely interested in Muse, but will NEVER pay a monthly fee for software.  If Adobe comes to its senses and offers it for purchase, I will then consider Muse.]]></description>
		<content:encoded><![CDATA[<p>Adobe needs to pay attention to the comments on this page.  I am extremely interested in Muse, but will NEVER pay a monthly fee for software.  If Adobe comes to its senses and offers it for purchase, I will then consider Muse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan-Gunnar Kiris</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-37197</link>
		<dc:creator>Jan-Gunnar Kiris</dc:creator>
		<pubDate>Sat, 10 Sep 2011 13:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-37197</guid>
		<description><![CDATA[Hi,
How are searchengines like Google and Yahoo going to find my website made with Muse but published at another server than Adobe`s? (The site is exported via &quot;Export HTML... in the filesmenu&quot; then pput on the webhotels server using Dreamweaver FTP.
When I looked at the code in the &quot;Head section&quot; there were no &quot;metaname tag&quot;???????????and more.
Am I wrong?
I like Muse EXCEPT for one thing: The rental model.
I miss, and this are two serious things:
1; I can not import an HTML- site build in for ex. Dreamweaver.
2: There is no FTP-engine.
Best regards
Jan-Gunnar]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
How are searchengines like Google and Yahoo going to find my website made with Muse but published at another server than Adobe`s? (The site is exported via &#8220;Export HTML&#8230; in the filesmenu&#8221; then pput on the webhotels server using Dreamweaver FTP.<br />
When I looked at the code in the &#8220;Head section&#8221; there were no &#8220;metaname tag&#8221;???????????and more.<br />
Am I wrong?<br />
I like Muse EXCEPT for one thing: The rental model.<br />
I miss, and this are two serious things:<br />
1; I can not import an HTML- site build in for ex. Dreamweaver.<br />
2: There is no FTP-engine.<br />
Best regards<br />
Jan-Gunnar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Atkinson</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36869</link>
		<dc:creator>Nick Atkinson</dc:creator>
		<pubDate>Fri, 26 Aug 2011 21:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36869</guid>
		<description><![CDATA[Personally I always thought GoLive CS2 was really good!  I am still using GoLive 9 on OS X Snow Leopard for some projects.

I don&#039;t really understand why GoLive was terminated after the Macromedia acquisition (other than politics, maybe??!!).

Two problems with Adobe Muse:

First, it is an AIR application.  Not a native application experience.  Personally I am not prepared to pay money for an application written in Air or indeed Java.  I expect a native experience.  

Second, the rental model.  I agree with other commenters above that this is going to put some people off.

There is a native Mac visual HTML design tool already (if you want a code generator) and that is Softpress Freeway.  Which does not have a rental model.

It would be interesting to see a detailed feature comparison between Adobe Muse and Softpress Freeway Pro.  That is something I am going to look in to.]]></description>
		<content:encoded><![CDATA[<p>Personally I always thought GoLive CS2 was really good!  I am still using GoLive 9 on OS X Snow Leopard for some projects.</p>
<p>I don&#8217;t really understand why GoLive was terminated after the Macromedia acquisition (other than politics, maybe??!!).</p>
<p>Two problems with Adobe Muse:</p>
<p>First, it is an AIR application.  Not a native application experience.  Personally I am not prepared to pay money for an application written in Air or indeed Java.  I expect a native experience.  </p>
<p>Second, the rental model.  I agree with other commenters above that this is going to put some people off.</p>
<p>There is a native Mac visual HTML design tool already (if you want a code generator) and that is Softpress Freeway.  Which does not have a rental model.</p>
<p>It would be interesting to see a detailed feature comparison between Adobe Muse and Softpress Freeway Pro.  That is something I am going to look in to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Seager</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36866</link>
		<dc:creator>Jeff Seager</dc:creator>
		<pubDate>Fri, 26 Aug 2011 16:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36866</guid>
		<description><![CDATA[I&#039;m with Hans. It&#039;s bad enough that Adobe Air apps are inherently unfriendly to such simple accessibility issues as increasing the size of type in menu items (not all developers are 20-year-olds with perfect vision, after all). Muse and Edge seem to take inaccessibility to a new level.

I don&#039;t understand why Adobe would turn loose a bunch of VISUAL designers (excellent though they may be) in a medium conceived and designed not for print, but for scalability, portability and universal access on an array of devices we haven&#039;t even imagined yet.

I know that the good people at Adobe have heard of graceful degradation and progressive enhancement. So why ignore the fundamentals in the creation of new products? And why now, when more browsers are finally coming into line with standards? Have you learned nothing from the decade-long effort to retrofit accessibility in Acrobat Reader (a product created for print media)? It simply doesn&#039;t work if you don&#039;t begin with an accessible foundation.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m with Hans. It&#8217;s bad enough that Adobe Air apps are inherently unfriendly to such simple accessibility issues as increasing the size of type in menu items (not all developers are 20-year-olds with perfect vision, after all). Muse and Edge seem to take inaccessibility to a new level.</p>
<p>I don&#8217;t understand why Adobe would turn loose a bunch of VISUAL designers (excellent though they may be) in a medium conceived and designed not for print, but for scalability, portability and universal access on an array of devices we haven&#8217;t even imagined yet.</p>
<p>I know that the good people at Adobe have heard of graceful degradation and progressive enhancement. So why ignore the fundamentals in the creation of new products? And why now, when more browsers are finally coming into line with standards? Have you learned nothing from the decade-long effort to retrofit accessibility in Acrobat Reader (a product created for print media)? It simply doesn&#8217;t work if you don&#8217;t begin with an accessible foundation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hans verhaegen</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36782</link>
		<dc:creator>hans verhaegen</dc:creator>
		<pubDate>Mon, 22 Aug 2011 21:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36782</guid>
		<description><![CDATA[You cannot compare postscript with code for web design. The way postscript is written is totally irrelevant for the output of a print process: something with fixed dimensions printed on a certain defined surface. 
A web site must be accessible on very different platforms and the way code (HTML) is written is of absolute essence. The HTML of a website must be ordered in a way that is meaningful (also for humans, remember accessibility!) to understand. 
Postscript is just there for machines to process to get a certain fixed, printed outcome. We do not care how a title of an article is defined in Postscript. It has no effect on the printed outcome. 
But in HTML it really needs to be a heading and not some paragraph with some styling just simulating a heading. Web design is so much more than just creating good looking screens. 
And why keep up that artificial divide between designers and developers! A lot of web designers are simple fantastic coders. And they know damn sure why. 
Please, do not throw away semantics and accessibility because you presume wrongly that coding is a bad thing for designers. Coding is in fact the most efficient and fast way to do proper web design, to really cope with all the complexity involved. If you care to learn, it is a really magical thing, you will love it. 
Adobe Muse seems in its beta form nothing more than a prototyping tool. To do quick sketches. Even for that there are other programs that do better (Axure, etc...) and at the same time have the same limitations (no liquid design). 
Illustrator, Indesign, Photoshop and even FireWorks are all the wrong programs to do web design. (Please, Adobe, remove all these silly export-as-html features.) 
Possibly we might need a new program dedicated more towards web design. But Adobe Muse (beta) is just not good enough because it ignores some fundamental aspects of web design. 
Also I think a lot of future users will regret after a while that they didn&#039;t even learn the HTML/CSS basics by using only  Muse (no coding view). Another reason why this program is a bit disappointing. 
But, hey, it is beta, maybe, we never know, lets see how things go...]]></description>
		<content:encoded><![CDATA[<p>You cannot compare postscript with code for web design. The way postscript is written is totally irrelevant for the output of a print process: something with fixed dimensions printed on a certain defined surface.<br />
A web site must be accessible on very different platforms and the way code (HTML) is written is of absolute essence. The HTML of a website must be ordered in a way that is meaningful (also for humans, remember accessibility!) to understand.<br />
Postscript is just there for machines to process to get a certain fixed, printed outcome. We do not care how a title of an article is defined in Postscript. It has no effect on the printed outcome.<br />
But in HTML it really needs to be a heading and not some paragraph with some styling just simulating a heading. Web design is so much more than just creating good looking screens.<br />
And why keep up that artificial divide between designers and developers! A lot of web designers are simple fantastic coders. And they know damn sure why.<br />
Please, do not throw away semantics and accessibility because you presume wrongly that coding is a bad thing for designers. Coding is in fact the most efficient and fast way to do proper web design, to really cope with all the complexity involved. If you care to learn, it is a really magical thing, you will love it.<br />
Adobe Muse seems in its beta form nothing more than a prototyping tool. To do quick sketches. Even for that there are other programs that do better (Axure, etc&#8230;) and at the same time have the same limitations (no liquid design).<br />
Illustrator, Indesign, Photoshop and even FireWorks are all the wrong programs to do web design. (Please, Adobe, remove all these silly export-as-html features.)<br />
Possibly we might need a new program dedicated more towards web design. But Adobe Muse (beta) is just not good enough because it ignores some fundamental aspects of web design.<br />
Also I think a lot of future users will regret after a while that they didn&#8217;t even learn the HTML/CSS basics by using only  Muse (no coding view). Another reason why this program is a bit disappointing.<br />
But, hey, it is beta, maybe, we never know, lets see how things go&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene Hernandez</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36771</link>
		<dc:creator>Rene Hernandez</dc:creator>
		<pubDate>Mon, 22 Aug 2011 17:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36771</guid>
		<description><![CDATA[Amen! The sad part is, will Adobe ever realize the lost sales due to these details. I for one will never switch to a CS suite should they ever base those apps on AIR. AIR apps never feel right.]]></description>
		<content:encoded><![CDATA[<p>Amen! The sad part is, will Adobe ever realize the lost sales due to these details. I for one will never switch to a CS suite should they ever base those apps on AIR. AIR apps never feel right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene Hernandez</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36770</link>
		<dc:creator>Rene Hernandez</dc:creator>
		<pubDate>Mon, 22 Aug 2011 17:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36770</guid>
		<description><![CDATA[I like that Adobe is thinking about new programs, but I hate to say - AIR based, Adobe GUI&#039;s suck. I had a nightmare the other day that the CS design apps had been converted mainly to being AIR based. I can appreciate Adobe&#039;s desire to &quot;write once&quot; but I use a Mac for its GUI and the touches that Apple brings. And I can appreciate MS&#039; GUI for windows. Why Adobe insists on developing a 3rd convention on top of these standard GUIs is beyond me. What it does remind me of is when I have looked at UNIX apps that have been ported with all the bad UI elements, or Office 6 on the Mac. Bottom line, AIR based apps never feel right and being a designer and long time Adobe and Mac user, that sucks.]]></description>
		<content:encoded><![CDATA[<p>I like that Adobe is thinking about new programs, but I hate to say &#8211; AIR based, Adobe GUI&#8217;s suck. I had a nightmare the other day that the CS design apps had been converted mainly to being AIR based. I can appreciate Adobe&#8217;s desire to &#8220;write once&#8221; but I use a Mac for its GUI and the touches that Apple brings. And I can appreciate MS&#8217; GUI for windows. Why Adobe insists on developing a 3rd convention on top of these standard GUIs is beyond me. What it does remind me of is when I have looked at UNIX apps that have been ported with all the bad UI elements, or Office 6 on the Mac. Bottom line, AIR based apps never feel right and being a designer and long time Adobe and Mac user, that sucks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregory Wostrel</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36729</link>
		<dc:creator>Gregory Wostrel</dc:creator>
		<pubDate>Fri, 19 Aug 2011 19:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36729</guid>
		<description><![CDATA[If one is a very picky, detailed, code-monkey (and in some ways that is a compliment) then tools like Muse will not satisfy. One look at the source code will make you say &quot;meh, terrible code output&quot;. But if the code still meets accessibility needs, renders properly on multiple browsers, and works on mobile devices then its is useful. Let&#039;s see if Adobe can accomplish that.
For the rest, Designers who really are not interested in the complexity of the code level, this is a promising tool. At the risk of sounding like one of those cranky gray-hairs who always point out that someone thought of an idea or product along time ago &quot;back in the day&quot; etc etc I will point out that this concept is a whole lot like Softpress&#039;s Freeway. I first used that back in 1999 or maybe 2000. They started by making an app that looked a lot like and worked like Quark XPress (including keyboard shortcuts). They have steadily developed it and it is a pretty decent app. Doesn&#039;t do everything, the code-monkeys will not like it, but it is work a look too in order to see what a much smaller company has managed to do in the last 10 years.
http://www.softpress.com/]]></description>
		<content:encoded><![CDATA[<p>If one is a very picky, detailed, code-monkey (and in some ways that is a compliment) then tools like Muse will not satisfy. One look at the source code will make you say &#8220;meh, terrible code output&#8221;. But if the code still meets accessibility needs, renders properly on multiple browsers, and works on mobile devices then its is useful. Let&#8217;s see if Adobe can accomplish that.<br />
For the rest, Designers who really are not interested in the complexity of the code level, this is a promising tool. At the risk of sounding like one of those cranky gray-hairs who always point out that someone thought of an idea or product along time ago &#8220;back in the day&#8221; etc etc I will point out that this concept is a whole lot like Softpress&#8217;s Freeway. I first used that back in 1999 or maybe 2000. They started by making an app that looked a lot like and worked like Quark XPress (including keyboard shortcuts). They have steadily developed it and it is a pretty decent app. Doesn&#8217;t do everything, the code-monkeys will not like it, but it is work a look too in order to see what a much smaller company has managed to do in the last 10 years.<br />
<a href="http://www.softpress.com/" rel="nofollow">http://www.softpress.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Abbruzzi</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36709</link>
		<dc:creator>Christopher Abbruzzi</dc:creator>
		<pubDate>Fri, 19 Aug 2011 02:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36709</guid>
		<description><![CDATA[I think it is Adobe&#039;s goal to make everything eventually become by subscription. Only time will tell. Get ready for more credit card debt.]]></description>
		<content:encoded><![CDATA[<p>I think it is Adobe&#8217;s goal to make everything eventually become by subscription. Only time will tell. Get ready for more credit card debt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Gilbertson</title>
		<link>http://blogs.adobe.com/jnack/2011/08/adobe-muse-enables-great-web-layout-no-coding-required.html#comment-36704</link>
		<dc:creator>Alan Gilbertson</dc:creator>
		<pubDate>Fri, 19 Aug 2011 00:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=4772#comment-36704</guid>
		<description><![CDATA[@KC: As one who&#039;s been extremely happy with the 5.5 release, let me say that a) for heavy InDesign users, especially the huge number of us who are willy-nilly getting into ePub, because clients need us to, 5.5 is huge; b) the InDesign --&gt; HTML output improvements are huge; c) the Premiere Pro and After Effects and Dreamweaver improvements are huge.

I understand that you&#039;re not part of the ePub/mobile revolution. Like many other independent designers I know, I don&#039;t have that luxury: I have to satisfy my clients&#039; needs or I don&#039;t eat. eBooks outsold physical books on Amazon last year, so Adobe&#039;s efforts to keep up with the times are crucial. And if you think &quot;few talk about&quot; or use ePub, I can tell you from immediate personal experience that you&#039;re seriously limiting your own income.

Having moved from GoLive (and seen two businesses&#039; websites wrecked by careless use of it) to Dreamweaver, I would submit that there are strong reasons why Adobe needed to concentrate resources on the better platform. GoLive&#039;s strength, and its biggest liability, was that a sloppy (read: &quot;unwilling to learn what goes on under the hood&quot;) user could create dreadfully broken sites with it far too easily. I saw it happen, and it was not nice. I would never to back to GoLive, frankly, any more than I&#039;d switch to Quark Xpress.

If 5.5 doesn&#039;t affect your workflow, you don&#039;t need it. For the rest of us, it was a very important and timely step forward. As for Muse, the subscription price I&#039;ve seen mentioned is far less than my Lynda.com subscription. It&#039;s the least of my considerations about the product.]]></description>
		<content:encoded><![CDATA[<p>@KC: As one who&#8217;s been extremely happy with the 5.5 release, let me say that a) for heavy InDesign users, especially the huge number of us who are willy-nilly getting into ePub, because clients need us to, 5.5 is huge; b) the InDesign &#8211;&gt; HTML output improvements are huge; c) the Premiere Pro and After Effects and Dreamweaver improvements are huge.</p>
<p>I understand that you&#8217;re not part of the ePub/mobile revolution. Like many other independent designers I know, I don&#8217;t have that luxury: I have to satisfy my clients&#8217; needs or I don&#8217;t eat. eBooks outsold physical books on Amazon last year, so Adobe&#8217;s efforts to keep up with the times are crucial. And if you think &#8220;few talk about&#8221; or use ePub, I can tell you from immediate personal experience that you&#8217;re seriously limiting your own income.</p>
<p>Having moved from GoLive (and seen two businesses&#8217; websites wrecked by careless use of it) to Dreamweaver, I would submit that there are strong reasons why Adobe needed to concentrate resources on the better platform. GoLive&#8217;s strength, and its biggest liability, was that a sloppy (read: &#8220;unwilling to learn what goes on under the hood&#8221;) user could create dreadfully broken sites with it far too easily. I saw it happen, and it was not nice. I would never to back to GoLive, frankly, any more than I&#8217;d switch to Quark Xpress.</p>
<p>If 5.5 doesn&#8217;t affect your workflow, you don&#8217;t need it. For the rest of us, it was a very important and timely step forward. As for Muse, the subscription price I&#8217;ve seen mentioned is far less than my Lynda.com subscription. It&#8217;s the least of my considerations about the product.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
