gitpushblog

A static blog generator.
A set of npm scripts that make it easy to build a blog using the githubAPI and nunjucks.

gitpushblog is a set of scripts that will generate some static files into another directory(/dist or /dev), and then it will push those files to the appropriate branch of the appropriate reositoty based on the configuration file (_config.yml) It also supports various themes, jekyell themes can be converted to gitpushblog themes easily.

It is sort of like Jekyll, but currently does very limited stuff and is in its early stage and probably broken but works fine.

live demo 1
live demo 2

Get started with the quickstart guide

Requrements: Node4.4 or above and node-sass package installed globally

$ npm run help

Usage: npm run [SCRIPT NAME]

Commands:
  dev                   Start a development server in port 3000, output in /dev
  generate              Generate minified version for the public site, output in /dist
  push                  Pushes contents of `/dist` to the appropriate branch of repository
  draft [FILE NAME]     Create a markdown file with minimal boilerplate text inside /drafts
  upload                Lets you select which drafts to upload to github issues from /drafts
  theme [THEME NAME]    Create a theme directory with minimal boilerplate files inside /themes

Features

Uses npm scripts
Built with webpack and preprocessor support
easily create themes
Github and Disqus Comments
Offline markdown draft support, live editing(needs reload)
Works hasslefree with github repository pages and profile pages.
Easily add,remove and edit themes. ( Need help creating themes )
Edit posts from mobile easily using any github client or browser*
Make a post using Github or using the commandline.

Basic idea

Here's the idea,

Github Element	Blog Element
Issues	BlogPosts
Issue comments	BlogPosts comments
Issue labels	BlogPosts categories

There was not much of a need, but I guess it's fun, also I wanted to use something like Jekyll but not Jekyll.

gitpushblog is suitable for personal blogs for people who use github regularly. The workfolw is simple, points 1 to 4 are one time unless you want to push your drafts/ online or push theme changes to the repository. Otherwise, to interact with the blog you'll only need to run 5 to 7.

You clone/fork this repository and set the correct git remotes to your blog repository
Then configure _config.yml according to your needs
Modify themes
Create offline draft posts using cli or using github issues on the browser
use npm run dev to do theme development and see live changes while editing offline drafts.
git push the whole repository if you want to.
run npm run push to publish your blog, you don't need to git add/commit gitpushblog will do that and figure out the repository to push to based on the configurations in _config.yml

Please see installation and usage for more details.

Note: dev/ is gitignored.

Paraphrasing a HN comment related to the use of github issues for blogposts

person1: I don't really like the idea of "exploiting" GitHub issues for blog comments. This is obviously not a designed feature of GitHub API and it feels like an abuse of GitHub service.

person2: To me this feels like something GitHub would approve of. GitHub Issues intentionally gives users a lot of freedom so they can use it however they want. Unlike competitors who forced you to do something a certain way. This is creative, and if your blog is hosted via GitHub Pages, then using Issues to discuss the content is not far-fetched at all.

so I think this is a valid idea.

The GithubAPI is not directory accessed, instead it uses a github-blog-api ,using that npm package you can make a fully client side blog if you want to, but here we're using it to generate the static content.

Quick Start

1. Create a new github repository, name it whatever you like, I recommend naming it blog. we'll call it <repo_name>

2. Clone gitpushblog repository locally

$ git clone https://github.com/geekodour/gitpushblog.git <repo_name>

3. Point the cloned gitpushblog remotes to <repo_name> and npm install or yarn

$ cd <repo_name>
$ sudo rm -r .git && git init
$ git remote add origin https://github.com/<username>/<repo_name>.git
$ npm install
$ yarn

Notes:

$ sudo rm -r .git && git init will not work in windows, you just have to delete the .git directory and the git init in the same directory after that.
The command for an username geekodour and <repo_name> blog will be as follows,

$ git remote add origin https://github.com/geekodour/blog.git

npm install takes very long, so I recommend using yarn instead because it's very fast. to install dependencies using yarn, just run the following

$ yarn

4. Open _config.yml and update the following:

.
.
    userpage: false
    baseurl: <repo_name>

username: <username>
author: <username>
repo: <repo_name>
.
.

Optionally you set custom theme in meta.blog_theme, it takes the name of the directory inside /themes, currently only 2 themes available.

5. Create few blogposts

Offline draft post

$ npm run draft hello_world_draft.md

This will create a file inside /drafts with appropriate template, update the file if you want to.

Github issue post from web

go to https://github.com/<username>/<repo_name>, It will be an empty respository or with some basic README and LISENSE. Create a new issue by going in the issue tab. Remember, issues are our blogposts. Give it a title of "I am a title from github issues" Give it a comment body of of

## heading
I am some text inside heading

then submit the issue. Now we've created two very basic blogposts, one in the offline /drafts directory another directly in Github. let's see gitpushblog in action now.

6. After installation is complete, run npm run dev

7. Visit localhost:3000 in your browser You'll now see a development build of the blog, if you make changes in your draft or theme and reload, the changes will reflect immediately.

8. Now it's time to push our blog to Github

$ npm run push

git will ask for credentials before the push if using HTTPS, give it. This will push the /dist directory, it will do the git add and git commit for you. the push will be done to the gh-pages branch of the repository, it will create one if does not already exist.

Additionally, You can also push the working repository to Github using git add,commit and push origin master if you want to. (use git push --force origin master if git push origin master fails)

9. Make gh-pages branch the publishing branch

Head over to the settings page of your <repo_name> repository in Github, in the Github Pages section, choose gh-pages branch as the source and save.

10. Visit https://<username>.github.io/<repo_name>/ , it might take a few seconds to show up the first time.

You'll notice that the posts inside /drafts are not there, whereas they were showing locally. You'll need to npm run upload to upload drafts to github, which is discussed later in usage.

That's all for the QuickStart.

Installation

I highly recommend you do the QuickStart if you haven't already

There are two ways you can get started with:

fork
clone

I recommended cloning, because you won't have that forked from thing under the repository name. If you don't mind having that, then please follow the fork installation instructions 😄

Github offers userpages and repopages.

userpages are basically profile pages, eg. geekodour.github.io.

repopages are repository pages, eg. geekodour.github.io/gitpushblog.

When using userpages, Github only allows the master branch to be the publishing branch so, see configuration for using gitpushblog with userpages. The installation instructions also have important information on setting up userpage/profilepage

Options for setting up the blog

Use userpage as the blog, eg. geekodour.github.io.
Use repopage as the blog, eg. geekodour.github.io/gitpushblog.

Installing gitpushblog (by cloning)

Create a Github repository named <repo_name>, I recommend naming it 'blog', in our case <repo_name> will be 'blog'.

NOTE for userpages:

You can skip rest of this step if you already have a username.github.io repository.

Now, If you are planning to make this blog your userpage/profilepage then head over to GitHub and create a new repository named username.github.io, where username is your GitHub username. If the first part of the repository doesn’t exactly match your username, it won’t work, so make sure to get it right.

So, you'll have two new repositories now, one <repo_name> and another username.github.io.

Clone gitpushblog repository locally

$ git clone https://github.com/geekodour/gitpushblog.git <repo_name>

Point the cloned gitpushblog to <repo_name>

$ cd <repo_name>
$ sudo rm -r .git && git init
$ git remote add origin https://github.com/<username>/<repo_name>.git

Notes:

$ sudo rm -r .git && git init will not work in windows, you just have to delete the .git directory and then git init in the same directory after that.
The command for an username geekodour and <repo_name> blog will be as follows,

$ git remote add origin https://github.com/geekodour/blog.git

Open _config.yml and change according to your needs, read configuration to know how to modify _config.yml
Inside <repo_name>, run npm install or yarn (yarn is recommended)

That's all for the install.

See usage for usage instructions.

Installing gitpushblog (by forking)

Fork this repository
In the forked version, go to settings and enable issues,you may also change the repository name to something like 'blog'.
Now clone the forked repository, and cd inside it and run npm install or yarn (yarn is recommended)
open _config.yml and change according to your needs, read configuration to know how to modify _config.yml

That's all for the install.

See usage for usage instructions.

Usage

gitpushblog uses npm scripts.

Basic Usage

After the installation,

Please note that if you make changes to blogposts eg. update the github issue or upload a draft, you'll have to rebuild the blog. gitpushblog uses github api to generate static content, but does not use github api on the frontend(exceptions).

Rebuilding the blog refers to running any of npm run dev,generate,push

Running in development

npm run dev is a very handy command that runs a development version of the blog in watch mode on port 3000. It can be useful when writing an offline draft or editing the theme.

Writing a new post
- Create a github issue in <repo_name> repository.
- npm run draft <filename.md> inside <repo_name> directory, a new file will be created inside the /drafts directory with appropriate template.
Editing a post

You need to edit the post/issue in github directly and then rebuild the blog to see changes.

Deleting a post

You have to close the post/issue to delete the post.

Generating minified files to /dist

You don't usually have to run this because npm run push already runs this command. It basically does excatly what npm run dev does, but with disabled watchmode+minified+correct baseurl+in the /dist directory.

Pushing blog changes

npm run push is the command. It pushes the contents of the /dist directory to the appropriate repository:branch It also runs the npm run generate command which creates the /dist directory in the first place.

Pushing happens differently for userpages and repository pages.(gitpushblog manages all these, you don't have to worry)

In repopages the public githubpages branch is in the gh-pages branch of the <repo_name> repository.

In userpages the public githubpages branch is in the master branch of the username.github.io repository.

So you have a <repo_name> repository, where all your have themes/, scripts/, dist/ etc. But when you push the changes with npm run push the content of /dist gets pushed into another repository or branch depending upon what you configure in _config.yml.

Uploading an offline draft

You'll need to have your github personal access token set to the GITHUB_AUTH_TOKEN env. variable for npm run upload to work. Read: Setting GITHUB_AUTH_TOKEN

npm run upload lets you choose which files from /drafts to upload to github issues, if upload was successful the uploaded file will be deleted from /drafts. Use it when you're done writing a draft offline and ready to publish it online.

If you want to push the draft changes to <repo_name> (not the publishing branch/repo) you can do that. You just have to do git add -A then git commit -m 'message' and git push orign master.

Pushing repository changes

Repository changes include, changes to anything other than the contents of /dev and /drafts. for example, changes in theme,scripts etc. npm run dev, npm run generate, npm run push these commands will always use the local configuration and files, so if you made a change in the local you'll see the changes reflected in the blog when using these commands.

npm run push will only push the contents of /dist so you'll have the changes in the blog too as /dist will be generated using local configurations only.

But the repository on github which git remote origin points to. In our case, <repo_name> does not know about these repository changes. If you want to push these changes to <repo_name> push changes to the origin.

$ git add -A
$ git commit -m 'commit message'
$ git push --force origin master

Advanced Usage

npm run generate : Generates the production build to say, minifies static assets etc. The files are in /dist
npm run push : It runs npm run generate first and then pushes the /dist directory to the gh-pages branch.
npm run push:only : Only pushes the /dist directory to gh-pages branch if using userpages then to the master branch of username.github.io repository.
npm run theme <theme_name> : Will create a directory named theme_name inside /themes with some basic boilerplate.

Configuration

All blog configurations are done in /_confg.yml and is accessible to all templates as the context object bc
All theme configurations are done in /themes/<theme_name>/_confg.yml and is accessible to all templates as the context object tc (optional)

Userpages and repo pages

npm run push will push contents of /dist to master branch of username.github.io repository if meta.username is true. The baseurl should be a empty string when using userpages.

Otherwise it will push contents of /dist to the gh-pages branch of the repository the origin is pointing to, which we set during installation, when using repopages there is the problem of baseurl so you need to set it to /<repo_name>

So, if you're planning to use userpages for the blog, then set meta.userpage to true and meta.baseurl to "", please also see the 2nd point in installing by cloning if you are planning to use it for userpage

Themes

Themes are located in /themes, currently all the available themes are included in there. meta.blog_theme is the name of directory which includes the theme files inside /themes

If you want to build your own theme or convert html template/jekyell theme to a gitpushblog theme, then read the building theme docs and themes can be managed by git subtree command if you wish to create a separate repositoty for the theme. It takes ~15mins to turn a Jekyell theme into a theme that gitpushblog supports.

Comments

There is comment field in _config.yml, the theme uses these values in comments to insert,remove comments, include github comments or disqus comments. The settings are pretty self explanatory.

`_config.yml` explanations

meta.blog_name : Name of the blog, can be used in places like navbar by the theme
meta.blog_theme : Name of the directory inside /themes to use as the theme
meta.engine : This should be nunjucks as that's the only templating engine that's supported as of now.
meta.userpage : should be set to true if blog is a userpage
meta.baseurl : <repo_name>, it is required for repopages, for userpages set it to "", read more about baseurl
username : github username
author : github username explanation: github-blog-api filters issues based on author, so if someone else creates an issue, only the ones you created will show up.
repo : <repo_name>, name of the repository, where you want gitpushblog to be.
posts_per_page : number of posts to fetch at once (max 100), used by static generator and javascript in the theme
comments_per_page : number of comments to fetch at once (max 100), used by static generator and javascript in the theme
comment.disabled : if true no comments will show up, no one can comment.
comment.isGithub : if true github comments will be shown. isGithubAuth is super experimental, please check the issue regarding this if you'd like to help, I recommend you set it to false for now
comment.isGithubAuth : if true a will show a comment box, where you can comment by authenticating with your github account.
comment.isDisqus : if true will let the theme declare divs and containers for the disqus commenting system, disqus is already integrated in default theme, so just set this to true and isGithub to false if you want disqus comments.
comment.disqus_id : your disqus id

firebaseConfig is experimental, please check the issue regarding this if you'd like to help, I recommend you don't set anything in there for now

firebaseConfig.* : these firebase configuration options that you get from firebase, again this is highly experimental, recomment not using it for now. If you want to experiment, then read setting up githubAuth and commenting with firebase

Setting up GithubAuth and commenting with firebase

Follow this guide from firebase to get the credentials and put the ones needed in _config.yml

Setting up GITHUB_AUTH_TOKEN Env

To get the personal access token go to https://github.com/settings/tokens give it the whole repo scope permission and give a name to your token and you'll have a newly generated token.
Copy that token
Create a file named .env inside the blog repository, put the token inside the .env file like this:

GITHUB_AUTH_TOKEN=YOUR_TOKEN_HERE_NO_SPACES

you're done, .env file is gitignored, so it will remain local to your system always.

TroubleShooting

If you get a node-sass error about bindings not found, run this command npm rebuild node-sass

Templates and Theme details

Use npm run theme <theme_name> to generate new themes with some basic boilerplate in /themes.

The templates are created using nunjucks. The directory structure of a theme looks something like this:

.
├── index.html
├── post_page.html
├── feed.xml
├── _config.yml
├── category_page.html
│
├── pages
│   ├── about.html
│   ├── ...
│   └── projects.html
│
├── snippets
│   ├── aboutbox.html
│   ├── base.html
│   ├── footer.html
│   ├── ...
│   ├── ...
│   └── navbar.html
│
└── static
    ├── css
    │   ├── main.sass
    │   └── prism.css
    └── js
        ├── main.js
        ├── services.js
        ├── prism.js
        └── utils.js

On running npm run dev or npm run generate, the output of these templates in /dev and /dist look something like this:

.
├── index.html
├── 2.html
├── 3.html
│
├── assets
│   ├── main.css
│   └── main.js
│
├── category
│   ├── hacking.html
│   └── tech.html
│
├── posts
│   ├── Code-reading:-LuaJIT.html
│   └── Why-Snabb.html
│
├── about.html
└── projects.html

If you put a index.html file inside /pages then it will be used as the homepage and all the blog related html files(i.e /index.html,/post_page.html) will be moved to a directory named /blog, see themes for examples. For more theme based information, please see theme docs

Todo

will add soon

Contribute

PRs and everything else is welcome
It will be awesome if anyone can help in creating some themes, you can create themes using nunjucks for now.
There are a lot of issues, check them out. It will be really great if you can help 😄

Limitations

Probably does not work on Windows as of now.
Uses only nunjucks for now, let me know if to add support of any other templating engine.
Currently only works with github pages (want to keep it that way)
See issues for others.

Contributors

@CodeDotJS
@MaxySpark
@geekodour

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

gitpushblog

Features

Table of contents

Basic idea

Quick Start

Installation

Installing gitpushblog (by cloning)

Installing gitpushblog (by forking)

Usage

Basic Usage

Advanced Usage

Configuration

Userpages and repo pages

Themes

Comments

`_config.yml` explanations

Setting up GithubAuth and commenting with firebase

Setting up GITHUB_AUTH_TOKEN Env

TroubleShooting

Templates and Theme details

Todo

Contribute

Limitations

Contributors

Files

README.md

Latest commit

History

README.md

File metadata and controls

gitpushblog

Features

Table of contents

Basic idea

Quick Start

Installation

Installing gitpushblog (by cloning)

Installing gitpushblog (by forking)

Usage

Basic Usage

Advanced Usage

Configuration

Userpages and repo pages

Themes

Comments

_config.yml explanations

Setting up GithubAuth and commenting with firebase

Setting up GITHUB_AUTH_TOKEN Env

TroubleShooting

Templates and Theme details

Todo

Contribute

Limitations

Contributors

`_config.yml` explanations