use wordpress as a backend for your spike static project
npm i -S spike-wordpress
check out this video demonstrating how you can easily set up a wordpress-powered static site that recompiles whenever you publish a new post or push to github using roots-wordpress, which this project is based on :eyes:
add the plugin to your app.js
file...
// app.js
const Wordpress = require('spike-wordpress')
const standard = require('reshape-standard')
const locals = {}
module.exports = {
plugins: [
new Wordpress({
site: 'my_wordpress_site.com',
addDataTo: locals
})
],
reshape: standard({ locals }),
// ...other config...
}
...and then access your posts as local variables in your view files:
// some_template.sgr
extends(src='layout.sgr')
block(name='content')
h1 My awesome static blog
h2 Recent posts
.recent
each(loop='post, i in wordpress.posts')
if(condition='i < 10')
h1 {{ post.title }}
h2 {{ post.excerpt }}
h3 by {{ post.author.name }} on {{ post.date }}
postTransform
hookPRs welcome for new features!
by default the plugin dumps all your posts into a single wordpress.posts
array in the view locals, but you can configure multiple queries in the posts
config key. pass in an array of config objects with a name
(required, so that you can access it in your locals at wordpress[name]
) and any parameter supported by the wordpress v1 api:
const locals = {}
new Wordpress({
name: 'my_wordpress_site',
addDataTo: locals,
posts: [
{
name: 'posts'
number: '10' // default limit is 20, max is 100
},
{
name: 'interviews',
category: 'interview',
order: 'ASC',
search: 'some text'
}
]
})
you can also include an arbitrary transform
function to apply to posts on the fly during the build process (see postTransform hook if you want to manipulate your locals after they've already been processed):
new Wordpress({
name: 'my_wordpress_site',
addDataTo: locals,
posts: [{
name: 'funtimes',
transform: (post) => {
post.foo = 'bar'
return post
}
}]
})
posts are run through a generic transform function by default; you can pass transform: false
to bypass it and return the raw result
you can add an optional template
param that will render each item in posts[param]
to a specific view template with a configurable output path:
const locals = {}
new Wordpress({
name: 'my_wordpress_site',
addDataTo: locals,
posts: [{
name: 'portfolio',
template: {
path: 'views/portfolio-item.sgr',
output: (item) => `posts/${item.slug}.html`
}
}]
})
Any post that gets rendered to a template gets a convenient _url
key tacked on as well (the result of the output
function you must pass):
// portfolio-item.sgr
a(href={{ item._url }})
h1 {{ item.title }}
img(src={{ item.featured_image }})
p {{ item.content }}
pass a file name to the json
param to write the locals.wordpress
output to:
const locals = {}
new Wordpress({
name: 'my_wordpress_site',
addDataTo: locals,
json: 'data.json'
})
add a postTransform
hook to modify posts and locals before
your templates get compiled, but after each post
's (optional) transform
function runs:
const fs = require('fs')
const locals = {}
new Wordpress({
name: 'my_wordpress_site',
addDataTo: locals,
posts: [{
name: 'posts',
transform: (post) => { // this runs first...
return post.title
}
}],
hooks: {
postTransform: (posts, locals) => {
posts.map(p => p.toUpperCase())
return [posts, locals] // posts = ['TITLE1', 'TITLE 2', etc]
}
}
})
The tests depend on a jetpack-enabled test wordpress instance. If you are developing a new feature and want to run the test suite either submit a PR (they'll be auto run by travis), or file an issue and I'll get you access to the test server :)
# install module dependencies
npm i
# create a config file from the boilerplate
mv .env.sample .env
# run the tests
npm test