ezmode geek blogging, like wearing sandals
It's a node.js library that can both serve a markdown file based blog, and also generate a static site from those files as well. GG.
flipflop provides a cli interface so needs a global install
> npm install -g flipflop
##Create a new blog
> flipflop create
This starts a cli app that will prompt for a few bits of info about your blog, and create a directory for it in the
##Start 'er up
Make sure you're inside your blog's directory.
> flipflop start <port>
check your browser @
##Static sites are hawt
Also, from inside your blog's directory.
> flipflop generate
This will create a static version of your site in a
public folder within your blog's directory
Generating a blog with
flipflop create produces a
blog.json file in your blog's root directory. Customize it as you want.
"title": "flipflip blog""description": "ezmode geek blogging, like wearing sandals""keywords":"authors":"bradharris":"name": "Brad Harris""gravatar": "firstname.lastname@example.org""github": "bmharris""articles": "articles""domain": """routes":"archive": "/archive""article": "/:year/:month/:day/:slug""error": "/404.html""homepage": "/""feed": "/feed/rss.xml""tag": "/tag/:tag"
###Options Many of these properties are used within the blog's template files.
titlethe title of your blog
descriptionthe description of your blog
keywordsarray of keywords describing your blog, used for the
authorskey/value object containing article authors' information. This is used to display information about an article's author on the associated article page.
articleslocation of directory containing articles. This defaults to a location relative to your blog's directory but can be absolute as well.
domainused for creating absolute paths for your blog's feed
routesallow a user to configure the urls
You can configure urls for yuor blog via the
routes property in the
blog.json config file. For example, if you wanted to prefix your blog with /blog/, you can do the following:
"routes":"archive": "/blog/archive""article": "/blog/:year/:month/:day/:slug""error": "/blog/404.html""homepage": "/blog""feed": "/blog/feed/rss.xml""tag": "/blog/tag/:tag"
If .html extensions are what you live for, you could change your article route to look like:
There are a few special things to note with routes:
:slugparam. Available params are:
:tagparam. Available params are:
##Write some articles
There will soon be a cli command to generate a new article for you, but you can always create them manually. Simply create a folder inside your blog's
articles folder. Whatever you name the folder will be used as the slug for the url (in combination with the article's date), so keep the folder url friendly. Populate it with an
article.json file and an
- some-post- article.json- article.md
authorshould be a key that maps to the blog config
titletitle of the post, doesn't need to be url friendly
datedate the article was published - a string Date.parse can handle correctly
publishtrue/false - if false the article won't be accessible/generated
tagsarray containing tags describing the article.
I'm happy to accomodate pull requests and bug reports, so fork it and improve it or let me know if you find any issues.
(The MIT License)
Copyright (c) 2013 Brad Harris
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.