Node status publication.

There is a need for publish to static.

I am looking at node_node_operations, node_filters, node_admin_nodes, node_form, etc.

Since drupal allows for the pulication of content, uses url rewriting, etc. there can certainly be a module that takes the output of a node rendering and place it in an HTML file. As I see it, the node revisions would not be removed. But, certain URL's may, at some final stage be written to a static page, and these pages do not have to be accessed via the PHP subsystem.
The page may be demoted from static publication to merely published or not published, etc. The URL rewriting may always refer to the page by the same URL whether or not the node is static or generated. Ideally, the option should only be available if there is an active module that enables static publication. Furthermore, a module that allows static publication should provide or should be limited to working only if there is a urlrewriting service that provides for switching between static directories and php generation.

It is unlikely that for many static pages that all dynamically updating information would be displayed. E.G. a sidebar might not be required to show updating stock information of a static page of node type 'product'. People interested in product pages, or technical spec sheets, may just want to get their information really fast.

By the way, I found the work done on the forms really impressive. And, I do mean that. On the other hand, I am trying to understand if there is a reason that form expansions need to return to the server. I suppose that DHTML is not available to everyone. However, it seems that it should be preferred. So, I was thinking the forms should be handled with DHTML and trips to the server should be reduced as a default case. I understand that in the hours of programming one does not always have time to add in specific changes.