NOF is what it is -- it's a WYSIWYG environment with a database back-end. It produces HTML that works (for now --see note* below), but that is essentially meaningless. (Note that in the source, there is no distinction between body text and headings, apart from the font markup and bold and underline tags.) Unlike some other, similarly-aimed environments (like the Domino web server component of Lotus Notes), there is no good way to manually alter the HTML created and continue to work on the project in Fusion.
The problem with the HTML that NOF creates isn't that it doesn't "look professional" (a good designer can make absolutely gorgeous pages in the editor), but that it is virtually inaccessible. That is, there are no cues to tell a user (or his/her assistive technology) what the various items on the web page mean. I can see this as a particular problem with a genealogical site, since it is usually the oldest and youngest members of the family that have the greatest interest in the history (the young are curious, the old are the curators of the family memory). Those family members who've found that their arms have gotten too short for comfortable reading (or who may be suffering from more severe forms of visual degeneration) can often benefit from a more structured web page. (That particularly applies to members who may rely on screen readers or Braille output.) It also applies to people who may have difficulty accurately using a mouse, and those folks live at both extremes of the age spectrum.
I'd be glad to help you restructure your pages if you'd like (no cost or obligation).
---------- Post added 09-03-2010 at 01:11 AM ---------- Previous post was 09-02-2010 at 08:05 PM ----------
Oops -- forgot the note I promised above. Many of the tags that NOF has generated are deprecated, and support for them will be dropped at some point in the future in browsers. It won't make the page unreadable, but it will render in the default font face and font size with no bold or underlining.