Using windows 8, I installed a fresh copy of wintersmith (npm i -g wintersmith).
Then in my repos dir I ran wintersmith new mysite. That created site perferctly.
Then ran wintersmith preview - server ran and site looked great.
Then ran wintersmith build - which generated the site successfully but when opening the site in Chrome I see that main.css wasn't found. This quickly boils down to the initial reference path of /css/main.css. Notice the leading slash which apparently on windows looks up the path in the root dir of the drive.
Recommended behavior - change this into a relative path such as :
css/main.css. Changing this locally fixed the problem for me, I reckon a lot of beginners would be quick to dispose of a tool that initially doesn't work as planned.
Using windows 8, I installed a fresh copy of wintersmith (
npm i -g wintersmith
).Then in my
repos
dir I ranwintersmith new mysite
. That created site perferctly.Then ran
wintersmith preview
- server ran and site looked great.Then ran
wintersmith build
- which generated the site successfully but when opening the site in Chrome I see thatmain.css
wasn't found. This quickly boils down to the initial reference path of/css/main.css
. Notice the leading slash which apparently on windows looks up the path in the root dir of the drive.Recommended behavior - change this into a relative path such as :
css/main.css
. Changing this locally fixed the problem for me, I reckon a lot of beginners would be quick to dispose of a tool that initially doesn't work as planned.Otherwise - all works great!