If you are planning an internet presence, you can start quickly with a wiki (like this one) or your own cloud. However, since most such sites require a web server as a basis, we should install the de facto standard - Apache 2. The installation is done in a few minutes, but if you value encrypted transmission, there are a few things to consider.
Required to reach the website from the Internet

• a DynDNS address
• a port release pointing to port 80 (unencrypted) and/or port 443 (encrypted)

sudo apt-get install apache2

Done, that's it. Under http://<your-IP-address/ you can see the result

This topic is quite extensive and I will describe it in detail later.

Encrypted communication requires, at least that's how the experts see it (I disagree), that you know who you're communicating with. Signed certificates are responsible for this on the Internet, from which one can see who is sitting on the other side. The certificate can be compared to an identity card. Since the current browsers check very carefully whether a certificate is valid, it must be signed (quasi signed) by a trustworthy party. Free certificates are provided by the Let's Encrypt Initiative.

The Certbot software is recommended to automate the installation, the integration into our web server (Apache 2) and the update (the certificates are only valid for 3 months). The How-To's on the Internet looks varied, extensive, often in English and sometimes outdated. I would like to refer to two who helped me to create my certificates and to automate the administration (a little expertise is also imparted).

• Create certificates
• renew certificates

As I said, I'm continuing to work on this article to create a detailed guide (as befits a how-to).