params.json

{"name":"Ops-baidu.github.io","tagline":"wiki of ops-baidu","body":"# Jekyll-Bootstrap\r\n\r\nThe quickest way to start and publish your Jekyll powered blog. 100% compatible with GitHub pages\r\n\r\n## Usage\r\n\r\nFor all usage and documentation please see: <http://jekyllbootstrap.com>\r\n\r\n## Version\r\n\r\n0.3.0 - stable and versioned using [semantic versioning](http://semver.org/).\r\n\r\n**NOTE:** 0.3.0 introduces a new theme which is not backwards compatible in the sense it won't _look_ like the old version.\r\nHowever, the actual API has not changed at all.\r\nYou might want to run 0.3.0 in a branch to make sure you are ok with the theme design changes.\r\n\r\n## Contributing \r\n\r\nThis repository tracks 2 projects:\r\n\r\n- **Jekyll-Bootstrap Framework.**  \r\n  The framework for which users should clone and build their blog on top of is available in the master branch.\r\n  \r\n  To contribute to the framework please make sure to checkout your branch based on `jb-development`!!\r\n  This is very important as it allows me to accept your pull request without having to publish a public version release.\r\n  \r\n  Small, atomic Features, bugs, etc.   \r\n  Use the `jb-development` branch but note it will likely change fast as pull requests are accepted.   \r\n  Please rebase as often as possible when working.   \r\n  Work on small, atomic features/bugs to avoid upstream commits affecting/breaking your development work.\r\n  \r\n  For Big Features or major API extensions/edits:   \r\n  This is the one case where I'll accept pull-requests based off the master branch.\r\n  This allows you to work in isolation but it means I'll have to manually merge your work into the next public release.\r\n  Translation : it might take a bit longer so please be patient! (but sincerely thank you).\r\n \r\n- **Jekyll-Bootstrap Documentation Website.**    \r\n  The documentation website at <http://jekyllbootstrap.com> is maintained in the gh-pages branch.\r\n  Please fork and contribute documentation additions to this branch only.\r\n\r\nThe master and gh-pages branch do not share the same ancestry. Please treat them as completely separate git repositories!\r\n\r\n\r\n## License\r\n\r\n[MIT](http://opensource.org/licenses/MIT)\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}