I was going to reply earlier but had to figure out a problem (headache) with git first. I had been using two machines to push and pull and I made a few mistakes along the way.
The theme I 'm using is twentyfourteen, but I also had a problem while loading hyde-x, and others. But hyde for example runs without a problem.
I normally run it, with the hugo server --theme=<themename> --buildDrafts, or I specify the theme in the config.yml file or the config.toml
Michael’s suggestion seems to make sense, but my knowledge is limited to implement it correctly. Is it case {{.Site.BaseURL}} ?
If you’re getting two slashes, it’s likely that your config file has a slash at the end of the baseurl and that your layout is also putting a slash at the beginning. In that case, just remove the slash at the end of baseurl.
Just wondering if you’ve found solution for your problem with the double slashes? I’m also using the twentyfourteen theme without any modification (so far)
I’ve just started with Hugo - running the hugo server locally works fine as I guess the hugo server is a bit forgiving with the double slash in the url’s for the stylesheets etc. S3 is not so forgiving as the local server (travel.jamesprenderga.st).
hugo config shows baseurl without the trailing slash and the theme templates don’t have an extra slash in them either ie:
yeah, I’m doing that for the time being. I see it’s fixed in the latest commit, but I’m using wercker to build and deploy and that’s currently using the 0.13 build. Will revert once the 0.14 build is released.
When Hugo 0.14 is out in the open, I would say that these should be the recommended way to link in static resources like CSS, JS etc. It’s much easier to handle missing or too many trailing slashes etc. in a Go func, compared to a template.