Since version 4.4, WordPress has a native responsive image support by including srcset and sizes attributes to the image markups. It’s a good function, no doubts.
However, it can cause problems which you are probably have, if you are reading this.
In my case, I convert my blog from a local WordPress installation using HTTrack. As for today, HTTrack can’t recognize those attributes, then, some images weren’t being showing for my readers.
Since the update 11.58, I noticed that cPanel NAT solution wasn’t working with Apache on Amazon Web Services and Google Cloud Engine.
Apache was using the public IP on the VirtualHost. Bad bad boy.
As far as I’m concerned, you don’t want to change the public IP to the internal IP every time some httpd.conf edition is made.
Static websites are faster than WordPress installations. However, I am tech enthusiast and I love a challenge. I’m well aware of Jekyll’s existence, but I love WordPress.
Since my blog doesn’t have any dynamic content besides the comments, I decided to go for it.
There are plenty reasons why you shouldn’t do that, here’s a few:
1. Very difficult to scale;
2. Difficult to edit;
3. Just for static content.