you preview your site in as many browsers as you can on as many devices as you can,.you have a watcher running in the background, linting, testing, compiling your code and your assets (Grunt, Brunch, Gulp, others…),.you edit your code in a text editor (Vim, Emacs, Sublime Text, Atom, Brackets, TextMate, VisualStudioCode, others…),.you have some package manager to deal with your project's dependencies (npm, bower, others…),.you have your project under some version control system (Subversion, Git, Mercurial, others…),.To the risk of being too caricatural, 'modern' professional front-end dev is currently done like this:

In the mean time, front-end development has become a bit more involved than it used to be: preprocessors, watchers, hundreds of frameworks and libraries from tiny to huge, dependency managers, package managers… but the trend is somewhat funnily command-line-centered. It uses Firefox 2's rendering engine so you shouldn't wonder why your website doesn't look right! It made me a lot faster and a lot better.Īnd, well… the latest Kompozer release is from five years ago. I started with Dreamweaver 2 back in 1999 but dropped it very quickly for a more bare bones workflow where I control everything. The text editing is not as good as in an actual text editor (and Vim is kind of the gold standard when talking about editors), the rendering is not as good as in an actual browser, the generated code is often too verbose… Kompozer - like its predecessor Nvu or Dreamweaver, the commercial software they are supposed to be an alternative to - makes a lot of compromises to give you a supposedly easy to use interface. No, writing your code in an editor and previewing the result in a browser is not 'archaic' it is actually the only sane way to create a website.

Website kompozer