Since when in the IT industry do you edit a live system???

Since the Dutch immediately started working without a manual

As a Dutch person I will not be liked, but I think the average Dutch person has a very bad habit of immediately using something. Only when things go wrong do we look up and read the supplied manual to understand how we could have worked better.

We can learn how to build a beautiful house with a hammer, but there are people who use the same hammer to smash into someone else's brain.

Just as it is too simplistic to see a hammer as a murder weapon only, it is also too simplistic to say that SitePad does not distinguish between a production and a development environment.

Firstly, you can make an adjustment in a web page of the live environment without saving it. You can then test the modified version next to the existing production environment. If the adjustment is not satisfactory, you simply throw away the changed page without affecting the production environment.

If you are happy with the adaptation, but you don't want to put it into production yet, you can mark it as personal or declare it as a draft version.

And if you save the modified version, just save the definitions in a database without the modification(s) being implemented in the production environment.

Then of course you also have the option to save the definitions of a web page stored in the database with a backup / restore action or to restore them to an earlier version.

Yes, then as a last step you can update the published web page by making the changes in the live environment.

Of course, without having read the manual and without having used the smart options, as a Dutch person, I can implement the changes directly in the live environment. Not preferred, but if you get it right right away without making mistakes, it's a quick method.

So the answer to your question: "Since when in the IT industry do you edit a live system???" is therefore: (sorry fellow countrymen).

First of all, as a Dutchman I didn't want to offend anyone, I and like most Dutch people really start without reading the manual first.

And yes, I also had to learn a lot because as a frugal Dutchman I naturally also started with a license for only one website. Really stupid, of course, because if I had chosen for the multiple licenses option, I could have started setting up a test environment before going live.

I have learned a lot through trial and error how to do it better. And yes, about that documentation, I agree 200% that it's very difficult to figure out exactly what impact an option will have.

My explanation for the quality of software documentation is best described as: There is a terribly good programmer (sometimes called a nerd) who writes a terribly clever program. Unfortunately for him, an hour before the weekend starts, the boss asks if he can still write some documentation. The nerd has good intentions, it's all true, but ..... indeed usually incomprehensible and impossible to follow for the beginner.

And yes I understand your frustration, I understand why it went wrong, but it is fair to say that by pressing the publish button you make the site live. This has nothing to do with an insult, but the justified frustration at the lack of documentation.

FYI, Why do you keep bringing up Dutch... What's that got to do with anything?

4) Once I click on Install, it overwrites my current site without asking me first.
5) It also does so if I select "Enable Dev Mode", except now it has a page that says "Under construction".