DocPad: Absolute URL Helper

README.md

DocPad: Absolute URL Helper

Uses a docpad configuration file to specify template data that we can use in our document to generate absolute urls.

docpad.coffee

module.exports = 

	# =================================
	# Template Data
	# These are variables that will be accessible via our templates

	templateData:

		# Site Information
		site:

			# Site Production URL
			url: 'http://your-website.com'



		# -----------------------------
		# Helpers

		# Get the Absolute URL of a document
		getUrl: (document) ->
			return @site.url + (document.url or document.get?('url'))

document.html.eco

Via helper: <a href="<%= @getUrl(@document) %>">visit me</a>

Without helper: <a href="<%= @site.url+@document.url %>">visit me</a>

Perfect, that's exactly what I needed =]

What's the difference between docpad generate and docpad generate --env static?
Couldn't find this info on that Deploy guide.

Using --env static runs your app under the production and static environments.

That static environment will turn off things like cleanurls and livereload that are dependent on the node.js server.

The production environment will try and compress and compilations that happen (when supported) versus giving you readable output. E.g. minified stylesheets, html, etc.

👍

When it comes to scripts, styles, etc. called via @getBlock().toHtml() wouldn't it be possible and appropriate to translate absolute urls to relative, at least in static env?

Like that:

@getBlock('scripts').add(['/vendor/jquery.js']).toHTML()

returns

<script defer="defer"  src="../../vendor/jquery.js"></script>

when rendered document is, say out/blog/2013-04-27/man-i-love-docpad.html.

This would require detecting out path and generating relative path from absolute given. Seems easy. What do you think?

I'm surprised there is not a push to solve this issue. One of the first things I do while building and testing a new site is deploy it to github pages,... but ghpages are stored in a sub-directory so all navigation links, scripts, and styles generated by the docpad skeletons are broken. In any event here is my solution.

I add a helper that fixes absolute urls (urls starting with a forward slash). The helper function takes strings, documents, and arrays so it is multi-use. I thought about making this a plugin but I'm not sure if this is the best (or even good) solution.

Here is my code:

        # Get the Absolute URL of a document
        getUrl: (_, site) ->
            site = site || @site.url

            if (typeof _ == "string")
                if (_[0] == "/" && _[1] != "/")
                    return site+_
                return _

            if (typeof _ == "object")
                if (_.url)
                    return @getUrl(_.url,site)
                if (_.map)
                    _getUrl = arguments.callee
                    return _.map((d) ->
                        return _getUrl(d,site)
                    )

            return _

Used like this

@getUrl(document)

or for scripts and styles

@getBlock('styles').add(@getUrl(@site.styles)).toHTML()

WIP: https://github.com/Hypercubed/docpad-plugin-geturl/

Comments welcome.

Is there any way to get the actual relative URL, see http://stackoverflow.com/questions/19252513/how-to-get-the-relative-url-for-the-rendered-document ?

I need to output for several different websites which share some content but also have unique content. Basically the sites are focused on specific countries, but some content references multiple countries (and so is on all sites (and this is fine with Google).

E.g.,
nepal.com/projects // unique content to this site
nepal.com/summer-volunteering-in-south-asia // shared content
india.com/projects // unique content to this site
nepal.com/summer-volunteering-in-south-asia // shared content (identical to above)

How should I organize using docpad? Should this be two different docpad installations where I manually copy the shared content? Or can this be one docpad but use folders/subfolders such as:

/india-projects
/summer-volunteering-in-south-asia
/nepal-projects

And then produce multiple static sites (or a single site with inbound redirection/rewrite of base URL based on site request)?