Nvu free WYSWYG HTML editor tutorial

Nvu beginner tips.

1. Maintain an exact desktop version of your site. To maintain a good view while using Nvu, place your image files and external .CSS style sheet on your desktop in the same subfolder relationship as it will appear on the internet.
2. Also get a cheap or free FTP program. Nvu is not very practical for uploading multiple pages, CSS style sheets or image files. Use a separate FTP such as BatchFTP.
3. Use a free source code editor for CSS, doctypes, SSI, and Javascript. Use a separate source code editor such as HTML Kit  for external CSS style sheets, or any important internal source code that you do not want Nvu to change. Also be sure to check the Nvu option to "retain original source code." Even with that option checked, however, Nvu often will change the source, especially anything that you enter while using Nvu. (For SSI and Javascript, it may be possible to enter the code with Nvu, if you then save and close the document before publishing. To publish with Nvu, simply re-open the document.)
4. Keep the <title> tag on one line. Otherwise, Nvu will chop off the rest of the title when you "publish."
5. When in doubt, close it out. Whenever Nvu is not uploading files, not showing changes, or acting up in any way--try closing the entire program. Re-open Nvu and often the problem is gone.

Nvu Quirks.

1. Typical Wyswygs:
 Enter = <p> always
Shift+Enter = <br>.

With Nvu: 
Enter = <br> if current text is not <p>.
Enter = <p> if current text is <p>

Also, I use "display:inline" with <h4>. This does not show up in Nvu unless I add <br>. Nvu then automatically eliminates the line break.

2.  No automatic link formatting? Well not a big deal. Just as well to click the "link" button.

3.  "Save" and "Publish" can suddenly become "save as" and "publish as"....thus requiring extra clicks. If I save...save...save...no problem. If I publish...publish....publish...no problem. But if I save...publish...save... then the file forgets its own name, evidently...?

4.  Can not remain in "source" mode? Soon as I "save" I'm shoved back to "normal" Wyswyg mode. So do I have to use a separate program for serious source editing?

5. If you have any problems with Nvu reading or uploading your external CSS:

-- Erase all CSS links from your head section and delete all entries from the CSS Editor. Then click "Link elt" and go through the process of allowing CSS Manager to write the link. (section B above)
-- Keep your desktop CSS file in the same relationship as it appears on your website. I.e., if on the website it is two levels up, then one level down in an "images" or "includes" folder--it must have the same relationship on your desktop. Otherwise, you may repeatedly edit and re-upload your CSS file--but it does not get uploaded. The website page may be reading an old CSS file and your Wyswyg window may lose the CSS codes after each upload.
-- Presumably, image files and CSS files all must in the same folder. Or you must select "do not include related files" for uploading Nvu pages, and use an FTP for uploading all else.

6. To avoid most of these quirks and complications, simply never use Nvu for uploading.

7. A slight nuisance when using SSI: Nvu intermittently saves pages as html when they should be shtml.

8. Multiple images of the same file can appear in Site Manager after re-uploading. Not to worry they seem to be ghosts that will disappear when refreshed.

My suggestions for Nvu developers.

Priorities:
1. Stability.
2. Stability.
3. Frills.

I believe that the first thing people want from an HTML editor, both beginners and advanced web designers, is reliability. Something that does not regularly freeze up or do something unexpected.

Don't try to do every bit of thinking for the user. It is much easier to learn how to code a link reference than to learn how to use Nvu! So give your users due credit. Don't make Nvu change the CSS link references. Just inform the user that the CSS & image files must be installed in the same relationship on the desktop as on the website! And so allow the CSS Editor always to reference it the same way.

This then will work fine for people who are totally ignorant. And also will allow people who are not ignorant to code the reference manually if they wish. Instead of confusing both of them, and making extra work for your programmers.

Also:

How about allowing Nvu to view a CSS file as if it were an HTM file--and upload it separately? 

That's how TSW webcoder does it. The TSW Wyswyg is bug-ridden, and that's why I'm here. However, the TSW color-coded full-page CSS editing and uploading is flawless. It is quite superior to your tiny, confusing, and click-heavy CSS editor. (And I refuse to accept the solution of keeping my CSS file in my images folder.)