The repo-based-blog package

[Tags:bsd3, library, program, test]

This package contains a module that can be used in web applications. It's use cases are only limited by the use of blaze for the markup of pages. If anynoe cares to abstract that away, I would not stand in the way.

This package also contains an executable that uses the dyre library to allow a configuration of a web application in the way xmonad or yi does. An examle can be fount in the RBB module.

The blog contents are managed via a version control system. The filestore library has been used as a backend for this and hence the supported repository types mainly depend on the filestore version used. Thes currently suppored repository types are git, mercurial and darcs. The entries are rendered using the pandoc library.

For more information see the haddock documentation of the exported modules or the README.md included in this package.


[Skip to Readme]

Properties

Versions 0.0.1
Change log changelog.md
Dependencies base (>=4.6 && <5), blaze-html (>=0.7.0.2), containers, data-default, directory, dyre, filepath, filestore (>=0.6.0.3), ixset, lens, mtl, old-locale, pandoc (>=1.12.3.3), parsec (>=3), repo-based-blog, stm, text, time, transformers, transformers-base, transformers-compat [details]
License BSD3
Copyright Copyright (C) 2014 Sebastian Witte
Author Sebastian Witte
Maintainer woozletoff@gmail.com
Category Web
Home page https://github.com/saep/repo-based-blog
Bug tracker https://github.com/saep/repo-based-blog/issues
Uploaded Fri Nov 14 12:42:20 UTC 2014 by saep
Distributions NixOS:0.0.1
Downloads 224 total (1 in the last 30 days)
Votes
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Readme for repo-based-blog

Readme for repo-based-blog-0.0.1

buid-status

repo-based-blog

A blogging module that uses a repository as its content backend.

Usage

The Haddock documentation of the module Web.RBB should contain enough information to get started.

Contributing

As long as there are no web application specific changes required, I would usually just review and accept every pull request.

Guidelines

  • Please write documentation!
  • Please try to write tests!
  • If an issue exists, reference it!
  • Similar to neovim's development, use [WIP], [RFC] and [RDY] as tags in pull requests. Especially the [WIP] annotation has the potential to avoid unnecessary duplicate work if the pull request is created immediately after starting to work at the issue.