Deploy to relative path about wintersmith

[jnordberg]

Yes, you can pass a base url to all content plugins. content.getUrl(base)

I would suggest doing something like setting basePath: '/mypath' in the config locals and then use that when resolving content urls. e.g. somepage.getUrl(locals.basePath)

That way you can set the basePath to '/' when developing since the preview server runs from the webservers root

This way would definetly works but adds a level of complexity : one should not forget to add locals.basePath in front of every links for his site to work everywhere.

I suggest that basePath can be used by default for every local links. So calling mypage.url or /css/main.css would return in fact /mypath/css/main.

Maybe it's better that I write a plugin for it ?

[jnordberg]

I see your point, but doing it that way would introduce a level of complexity in the plugin structure instead. I'll keep it in mind for future releases

You could write a plugin, have a look at src/contents.coffee and src/plugins/page.coffee.

[00dani]

The lack of relative path support seems to me a rather big issue with this generator. It doesn't reflect well on the system's ability if the result of a simple wintersmith build doesn't work without being uploaded to a server.

In addition, the features page suggests:

Or why not publish directly to your dropbox.

This would be a great feature, but there is a reason not to do it: It won't work at all, due to the lack of relative-path output.

[ericanderson]

No action on this?

[ericanderson]

FYI, you can get this as a helper plugin now:

https://github.com/ericanderson/wintersmith-makerelative