Unify the way we serve the website

[abdonrd]

Right now, we have two kinds of deploys:

Production

• Created with the npm run generate
• Static deployment (pre-rendered) on an IBM static server

PR previews

• Created with the npm run build
• Server deployment with npm start on Heroku

We have already had cases where one deploy worked and the other did not: #2088 (comment)

I want to propose to unify them: or both with static or both with server deployment.

Personally, since all of our content is static, I would lean towards the static deployment.

[korgan00]

This is not decoration. It is not related to aesthetics.

[Tansito]

Same opinion. Another issue related with this discussion was happening here #2399 , taking into account that static content offers really good performance compared to a server I agree going with the static option.

[vabarbosa]

updated preview build to use static deployment (similar to production), which also resolved the preview build errors:

• update Dockerfile to resolve preview build errors #2401