Dreamweaver is dying

[Author's profile]

Tom arsh, senior designer, set up his own online design company after graduating from Edinburgh University in 1987 and embarked on the path of designer.

 

 

 

 

 

 

 

 

 

 

I have received a lot of well-intentioned emails about my latest digital design column, but I have to admit that some of these emails make me feel a little uncomfortable.

 

These emails were sent by designers to thank me. When they moved from print design to web design, I pointed them to the Dreamweaver path. They have been grateful for Dreamweaver for many years. It provides the best platform for their webpage design career. Gratitude is their intention.

 

 

But the problem is: dreamwveaver is moving towards a dead end ......

 

To be fair, this is not the fault of Dreamweaver, nor is it the problem of Adobe and Its Development Team-the latest Dreamweaver cs4
It is the most impressive release version in recent years. In addition, although Microsoft Expression web looks better than frongpage
With a more substantial threat, Dreamweaver is still the best html/CSS-based editor.

 

The real problem between Dreamweaver and its users is that the nature of the network is that changes are too fast. Various dynamically generated network applications, from giant Amazon to ordinary blogs, all of which provide many features-embedded comments, voting, RSS feeds, and so on-compared to the best website built based on static html.

 

This is not a problem with additional functions, but a fundamental change. Basically, the content of a website is king-publish the content and make it available-for these two core tasks, dreamweaver and other static HTML editors have proved to have fundamental defects.

Root
This is because the old mode is not scalable or dynamic. The core administrator needs to manually create each page of each website. Worse, you also need to manually add the necessary navigation to help the user find the content. Future only
One feasible way is that content contributors can publish content, whether it is a webmaster or a visitor, and the best navigation should be built around the dynamic content that users continuously contribute.

 

In other words, Web2.0 is not an empty slogan. It is fundamentally different from the past, while Dreamweaver is on the wrong side. So, is this the last day for Dreamweaver and traditional web designers who make a living with Dreamweaver?

 

Eventually, yes. In the near future, each website will become a dynamically generated network application. Today, all sites created Based on Multiple Static webpages will be squeezed out and replaced.

 

The good news is that for web designers who accept this fact, there is a huge opportunity in this process-think about the gold rush.

 

This
Yes. Just like Dreamweaver's easy migration of graphic designers into the tag-based HTML New World, content management systems such as joomla and Drupal
Simplified static Web
1.0 designers switched to the new web world migration process based on PHP scripts. Pay more attention to them, and you will be amazed at what you can do, and you will not encounter a line of code throughout the process.

 

I don't know how to recommend this. If you are a Dreamweaver user, don't worry about making contributions to Dreamweaver by upgrading to the latest version or exploring the end users of Adobe, instead, we should save money and invest time in the real future of web design: a server-based content management system.

 

Dreamweaver is dying. Long live Drupal.