The local version of the Jekyll site makes a good job of minifying assets and exporting them to the /_site/ directory.
This works all right since when you are developing locally, the generated files all live at /_site/.
The issue comes when building for deploying on the server, the minifying step is generating the ouput in /_site/ means that instead of just replacing the ones at the root / it creates a duplicate at /_site/. You can see this by visiting https://godotengine.org/_site/ which is actually a minified clone version of the website.
The solution would be to make the necessary adjustments in the CI so that when building the site for release, we don't output the minified files in /_site/.
The local version of the Jekyll site makes a good job of minifying assets and exporting them to the
/_site/directory. This works all right since when you are developing locally, the generated files all live at/_site/.The issue comes when building for deploying on the server, the minifying step is generating the ouput in
/_site/means that instead of just replacing the ones at the root/it creates a duplicate at/_site/. You can see this by visiting https://godotengine.org/_site/ which is actually a minified clone version of the website.The solution would be to make the necessary adjustments in the CI so that when building the site for release, we don't output the minified files in
/_site/.