Dreamweaver is heading for a dead end.

The author of this article is Tom Arah, a famous designer.

I've received a lot of nice emails about my latest digital design column, but I have to admit that some of them make me feel slightly uncomfortable.

These emails were sent by the designers to thank me, and when they moved from the print design to the web design, I pointed the way to Dreamweaver. They have been grateful to Dreamweaver for years, providing the best platform for their web design careers, and gratitude is their intention.

But the problem is:Dreamweaver is heading for a dead end ...

To be fair, this is not Dreamweaver's fault, nor is it a problem for Adobe and its development team-the latest Dreamweaver CS4 is the most impressive release in recent years. In addition, while the Microsoft Expression Web appears to pose a more physical threat than Frongpage, Dreamweaver is still the best Easy-to-use editor based on HTML/CSS Web pages.

The real problem with Dreamweaver and its users is that the nature of the web is that it changes too quickly. A variety of dynamically generated Web applications, from giant Amazon to regular blogs, offer much more functionality-inline comments, voting, Rss feeds, and more-than the best Web sites based on static HTML can offer.

This is not an issue of additional functionality, but a completely fundamental change. Fundamentally, a Web site is content-Dreamweaver-publishing and letting it be found-for these two core tasks, the other static HTML editors have proven to be fundamental flaws.

The root cause is that the old schema is not scalable or dynamic, and the site's core administrator needs to hand-make every page of each site, and, worse, manually add the necessary navigation to help users find content. The only possible future is that content contributors can publish content, whether he is a webmaster or a visitor, and the best navigation should be built around the dynamic content that the user is constantly contributing to.

In other words, web2.0 is not an empty slogan, it is fundamentally separate from the past, and Dreamweaver on the wrong side. So is this the end of Dreamweaver and the traditional web designer who dreamweaver for a living?

Eventually it will be. In the near future each site will become a dynamically generated network application, and today all sites based on multiple static web pages will be squeezed out and replaced.

The good news is that there is a huge opportunity in this process for web designers to embrace the fact-think of the gold rush of the krona.

This can be done. Just like Dreamweaver. Graphic designers move into a new world of HTML based on markup languages, and content management systems like Joomla and Drupal ease the migration process of static Web 1.0 designers to the web2.0 New World based on PHP scripting. Pay more attention to them and you'll be amazed at what you can do, and you won't run into one line of code throughout the process.

I don't know how to strongly recommend this. If you're a Dreamweaver user, don't worry about upgrading to the latest version and exploring unhelpful attempts to Dreamweaver by Adobe Transplant end users, Instead, we should save money and devote time to the real future of web design: A server-based content management system.

Dreamweaver is dying, long live Drupal.