What is Mill ?

[xeodou]

Mill is a micro blog system, which focus on lightweight, fast and open source. Easily deploy on your github account in 10 seconds and costs nothing.

How it works

Mill builds on the top of github, use github static page to host all the static files and github issues as a blog editor. Each github issue is one blog post, so you get markdown support naturally and you even have a comment system. You readers can read your blog posts on the beautiful web pages we built make comments. Here are few steps for how to build your own awesome blog website:

• Fork the repo to your github account
  Fork our repo to your account
• Customize your blog site
  Clone your repo to your local and editor the config.js under master branch, the file format is like

{   
    // Blog title
    title: 'mill',
    // Blog description
    description: 'the lightest blog engine base on github issues.'
    github: {
       // The owner of this repo.                  
       owner: 'graffie',
       // Which repository's issue you want use as posts.
       repo: 'mill.blog',
    }
}

• Push back your changes
  Commit your changes with git commit -am 'Update config.' and push back to your github us git push.
• Build your gh-pages
  Run command npm run deploy to deploy your website, this step will create a gh-pages branch on your github repo, and then you can open https://your_github_name.github.io/mill check your blog site.

Conclusion

With very few steps above your will get a very cool and githubify blog site. And it's a completely blog system with tags, comments, permission manage, blog editor. All source files are under MIT license, that means you can build your own system with our code.
_Contributions are welcome!!_

__ Mill Team

[rajington]

What about comments?

[xeodou]

It's in roadmap, but we need thinking how to organize the comments ,even
support comment direct from the blog website. :)

Best

Xeodou
On Apr 20, 2016 05:02, "Rajarshi Nigam" notifications@github.com wrote:

What about comments?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)