* include it in the main page
* update the RSS feed
* include it in all the category/tag listings
* if you have prev/next article links, you have to add it to the last article
* included images need to be prepared for web
* if you show a code example, you might want to syntax-highlight it
If you want to change the design, you have to touch all pages (or do search/replace and hope that it doesn't mess anything up)
...
Or you could have a program that you feed text + raw images for your articles and that automatically generates all the necessary files/changes old ones accordingly, based on this input and templates.
The result then can be served by web server that doesn't speak any server-side language.
I do remember a time when the expression "dynamic HTML" was popular to designate HTML+JS. Therefore, "static" may have been used in contrast to "dynamic" to designate plain HTML pages indeed. This is not the case now.
I remember this being a MASSIVE pain. Managing that is a huge benefit. Thanks for the explanation!
They are best when building landing pages, corporate sites, or simple blogs. It's cleaner, lighter and more maintainable than solutions like wordpress, drupal or most cms
Here's my genuine question: it seems like the term 'static site' means something different from my understanding of it in the 00's-a plain HTML page with no server side processing (PHP, ASP, Coldfusion, etc). Is this correct? What exactly are these static sites and why does one need to be "generated" versus crafting your own markup? Time and efficiency or is there more under the hood than I understand?
Thanks!