Why you shouldn't use FrontPage

To quote myself...

"Just whatever you do..

Don't. Use. Frontpage."

Why? Let's take a look at some sample code (credit my friend Brian for sample code).

quote:

---

<p align="left">
<applet code="fphover.class" codebase="./" width="156" height="24">
<param name="textcolor" value="#FFFFFF">
<param name="color" value="#808000">
<param name="hovercolor" value="#800000">
<param name="effect" value="fill">
<param name="font" value="Dialog">
<param name="fontstyle" value="bold">
<param name="fontsize" value="15">
<param name="text" value="Home">
<param name="url" valuetype="ref" value="index.htm">
</applet>
</p>

---

What is this? A link. Something simple turned into A LOT of unnecessary code. Frontpage has a knack for doing this with everything - so does Microsoft word. Do the entire web community a favor by not using either of those programs to write your HTML.

Slime has given us a good list of reasons:

quote:

---

1. FrontPage creates unclean code which is hard to edit.
2. FrontPage creates code that does not reliably work in non-IE browsers.
3. FrontPage creates web pages that do not adhere to web standards.
4. FrontPage creates web pages which are inaccessable to people with disabilities.
5. FrontPage creates web pages which do not rank well in search engines, due to its non-standard code.
6. FrontPage creates web pages which are not made to be presentable in any device other than a computer screen (such as a PDA, cell phone, etc)
7. FrontPage, like any other WYSIWYG, starts with assumptions about the web page that you want to create. This stifles creativity and taints the design with the WYSIWYG look.

---

------------------------
Relevant threads:

please don't let FrontPage get me....

__________________

(Added by: Raptor on Sun 09-Mar-2003)

(Edited by: Emperor on Fri 06-Jun-2003)

(Edited by: kuckus on Fri 06-Jun-2003)