There are many good (and not so good) web editing programs available. Some are free, some cost hundreds of dollars. Here are some criteria for picking what software you will get, and the tools I used to develop my web sites.
When I started making web sites, I picked FrontPage. I wanted "themes" that made a consistent look throughout my site. I wanted an easy way to make the navigation system (the menu buttons to move from page to page) easy to maintain. I wanted software I would be able to use in any company I went to. Besides, the company I worked at installed it on my computer...
I liked the ability to have themes that I could customize. Once I had a theme I liked, all fonts, paragraph styles, navigation buttons, and all the other visual elements of the site would be very easy to edit.
Unfortunately, the themes that come with FrontPage are not made with professional web sites in mind. There are "artistic" buttons and banners that detract from a professional image. The font colors do not even match the colors on the buttons and banners!
CSS Style sheets completely replace FrontPage's Themes, with more flexibility and control.
I also wanted to not have to worry about maintaining the navigation system for the site. FrontPage lets you simply drag your web pages around an organization chart, and it automatically maintains the navigation buttons for you. It even makes buttons with text on them for the navigation. But those buttons are graphics, so they don't resize (making them unreadable on high-resolution monitors). Worse, with all the support files needed by Frontpage, each button takes more than twice as much space on your server as the graphic file itself. Change the navigation of your site, and the buttons for each page need to be redone, and all those image files uploaded. CSS style sheets can achieve better-looking navigation systems without the bloat.
Server side includes let you make one file for your menu, to display on every page you want it—and you can have each page listed in the menu exactly where it makes sense to you, instead of having to fit your site design into a strict organization chart. The menu is one small file. The style sheet is one file that servers and browsers will cache for speedy access.
The HTML code FrontPage produces is complex. The default way of assigning fonts, text sizes, colors makes HTML code that is very hard to edit by hand; CSS style sheets are much easier, more flexible, and simpler.
The comments FrontPage uses for objects (such as navigation bars) get shown in search engine listings, rather than the descriptions I include myself.
I have Dreamweaver 8, well worth the money for the ease of use. I adjust properties of a tag simply by positioning the cursor in a tag and the Property Editor shows the options. I change the CSS layout in the CSS Editor, that even shows where the current style was defined (if you have multiple style sheets, plus styles in the header of the file, plus in the body of file, determining where to place your change can be a challenge without this information).
The most important feature of Dreamweaver compared to the free software I've found is the way it keeps track of the structure of your web site, and uploads files into the correct folder. I have the files on my computer, plus the files on a testing server, plus the production files. Not having to use an external FTP program, and carefully upload all files into the correct place, is a huge time saver.
This free collection of applications includes Apache Server, MySQL, PHP, and Perl, in a simple to install package. Test your web site on your own computer, saving the time required to FTP the site to your web host. Keep the production site running as you develop and test new features without worrying about messing up the main site. See my blog for configuring Xampp to have multiple virtual domains on your computer (for testing multiple separate websites).
Firefox
is a better browser than Internet Explorer. For developers, it has add-on
tools including a
View Source
tool and HTML Validator
combined (the source that the browser sees, after
your CGI scripts, server includes, and other changes have occurred)— so
you see the exact coding errors in context. Gives intelligent explanations
of the errors, so you can improve your code. Most HTML Validators refer to
a line number, but due to your scripts and includes the line number never
matches your source. This one works beautifully so you get the results you
want with any browser. Other extensions include easily seeing the form field
parameters, the sizes of screen elements, the CSS styles of elements, editing
the CSS and seeing the results.