Brief: Choosing the publishing workflow with Seamonkey Composer

Seamonkey Composer, the WYSIWYG website editor, has two possible workflows.

First is to have a local repository directory that you open files in and deploy the whole site from.

The other is to Ctrl+E your own website as you're browsing it. Then on save it will ask you the title of the page if it didn't have one and where to save it, albeit more of a default mode will be to publish it to FTP/SFTP

The former, however, means opening an html file as resident to local filesystem. And whenever you move around links, it translates them back and forth into absolute hyperreferences - and thus even a simple drag&drop will result in your links turning absolute with the locators ending up being "file:///home/..."

I have now turned to editing even my git-managed websites in the web-Ctrl+E way. Costs me having to pick the file location and sometimes getting unexpectedly asked for the title (maybe just in case of my.. pages.. that.. may have not have had a title yet ..the url was pretty enough)