-
Notifications
You must be signed in to change notification settings - Fork 0
/
docpad.coffee
173 lines (135 loc) · 6.64 KB
/
docpad.coffee
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
# The DocPad Configuration File
# It is simply a CoffeeScript Object which is parsed by CSON
docpadConfig =
# =================================
# Template Data
# These are variables that will be accessible via our templates
# To access one of these within our templates, refer to the FAQ: https://github.com/bevry/docpad/wiki/FAQ
templateData:
# Specify some site properties
site:
# The production url of our website
# If not set, will default to the calculated site URL (e.g. http://localhost:9778)
#url: "http://website.com"
# Here are some old site urls that you would like to redirect from
oldUrls: [
'www.website.com',
'website.herokuapp.com'
]
# The default title of our website
title: "Your Website"
# The website description (for SEO)
description: """
When your website appears in search results in say Google, the text here will be shown underneath your website's title.
"""
# The website keywords (for SEO) separated by commas
keywords: """
place, your, website, keywoards, here, keep, them, related, to, the, content, of, your, website
"""
# The website's styles
styles: [
'/css/layers.min.css'
'/css/font-awesome.min.css'
'/css/style.css'
'http://fonts.googleapis.com/css?family=Montserrat:400,700|Open+Sans:400italic,700italic,400,700'
]
# The website's scripts
scripts: [
'https://code.jquery.com/jquery.js'
'/js/plugins.js'
'/js/beetle.js'
]
# -----------------------------
# Helper Functions
# Get the prepared site/document title
# Often we would like to specify particular formatting to our page's title
# we can apply that formatting here
getPreparedTitle: ->
# if we have a document title, then we should use that and suffix the site's title onto it
if @document.title
"#{@document.title} | #{@site.title}"
# if our document does not have it's own title, then we should just use the site's title
else
@site.title
# Get the prepared site/document description
getPreparedDescription: ->
# if we have a document description, then we should use that, otherwise use the site's description
@document.description or @site.description
# Get the prepared site/document keywords
getPreparedKeywords: ->
# Merge the document keywords with the site keywords
@site.keywords.concat(@document.keywords or []).join(', ')
# Get the current year
thisYear: (new Date()).getFullYear()
getComments: (slug) ->
dt = new Date("October 13, 2014 11:13:00")
comments = [
{author:'Bob Builder',mtime: dt,content:'It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout.'},
{author: 'John Smith',mtime: dt,content:'It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout.'}
]
return comments
getRecentPosts: (num) ->
num = num || 20
posts = @getCollection('posts').query({limit:num}).toJSON()
return posts
# =================================
# Collections
# Here we define our custom collections
# What we do is we use findAllLive to find a subset of documents from the parent collection
# creating a live collection out of it
# A live collection is a collection that constantly stays up to date
# You can learn more about live collections and querying via
# http://bevry.me/queryengine/guide
collections:
# Create a collection called posts
# That contains all the documents that will be going to the out path posts
posts: ->
@getCollection('documents').findAllLive({relativeOutDirPath: 'posts'},[{date:-1}])
# =================================
# Environments
# DocPad's default environment is the production environment
# The development environment, actually extends from the production environment
# The following overrides our production url in our development environment with false
# This allows DocPad's to use it's own calculated site URL instead, due to the falsey value
# This allows <%- @site.url %> in our template data to work correctly, regardless what environment we are in
environments:
development:
templateData:
site:
url: false
static:
templateData:
site:
url: 'http://stevemcarthur.github.io/docpad-skeleton-beetle'
# =================================
# DocPad Events
# Here we can define handlers for events that DocPad fires
# You can find a full listing of events on the DocPad Wiki
events:
renderDocument: (opts) ->
if 'static' in @docpad.getEnvironments()
siteUrl = @docpad.getConfig().templateData.site.url.replace(/\/+$/, '')
if opts.extension is 'html'
opts.content = opts.content.replace(/href="\//g,'href="'+siteUrl+"/")
opts.content = opts.content.replace(/src="\//g, 'src="'+siteUrl+"/")
opts.content = opts.content.replace(/url\(\//g, 'url('+siteUrl+"/")
# Server Extend
# Used to add our own custom routes to the server before the docpad routes are added
serverExtend: (opts) ->
# Extract the server from the options
{server} = opts
docpad = @docpad
# As we are now running in an event,
# ensure we are using the latest copy of the docpad configuraiton
# and fetch our urls from it
latestConfig = docpad.getConfig()
oldUrls = latestConfig.templateData.site.oldUrls or []
newUrl = latestConfig.templateData.site.url
# Redirect any requests accessing one of our sites oldUrls to the new site url
server.use (req,res,next) ->
if req.headers.host in oldUrls
res.redirect(newUrl+req.url, 301)
else
next()
# Export our DocPad Configuration
module.exports = docpadConfig