The static generated site onto public does not render correctly, whereas the same content with hugo server works perfectly fine. repo-url.
Iβm using nginx to render the generated site, but the same problem is with httpd too.
The theme - hugo-cactus-theme is a submodule. So after clone, one needs to do git submodule init git submodule update
Iβve checked baseurls and all appear fine. I might be missing something very trivial.
Below is the garbled rendering -
Iβm using Hugo command to build the site. The contents of public are generated fine including css/ js/ fonts.
keshava@KEHP-M-X03J:keshavabharadwaj.com (master=)$ hugo
0 draft content
0 future content
18 pages created
29 paginator pages created
22 tags created
0 categories created
in 286 ms
keshava@KEHP-M-X03J:keshavabharadwaj.com (master=)$ hugo version
Hugo Static Site Generator v0.15 BuildDate: 2015-11-26T11:59:00+05:30
Yes indeed. I was pointing my base url to the one obtained on namecheap.
Hence all resolutions were pointing there. Now changed it to github.io page. it works now.
@rickcogley Thanks for your pointer which triggered the light bulb.
Could anyone elaborate the concept behind the solution in greater detail (relative path with .Site.BaseURL)? I had the same problem after switching to a new theme. The site looked perfect when using Hugo sever, but when I built and deployed, the theme was not rendering.
I tried my username.github.io but that didnβt work. So I went back to my custom domain lukemperez.com. I rebuilt the site it and it worked. Iβm stoked about that but I would like to know what I did that actually fixed it.
I did try previous answers such as changing my baseurl to βhttp://bgalvao.github.io/β so that it can find the files from there, hosted in the github repoβ¦ (e.g. my profile picture). I changed back and forth to my custom domain bgalvao.pt
Hint: You havenβt configured www for your domain and all of your siteβs assets are 404 because you are using that version of your domain to serve them.
For example: <link rel="stylesheet" href="http://www.bgalvao.pt/css/style.min.css">
Also if you plan to publish your site under https you really need to serve all your assets under the same protocol.