figglewatts / daybookr

SSG for journals. Quick and dirty, extremely barebones. Great for scatterbrained people in a rush.

daybookr

Simple static site generator. Quick and dirty, extremely barebones. Great for scatterbrained people in a rush.

Installation

$ go get -u github.com/figglewatts/daybookr/cmd/daybookr

Usage

NAME:
   daybookr - generate a static site based on some content, config and templates

USAGE:
   daybookr [global options] COMMAND [options]

VERSION:
   2.0.4

AUTHOR:
   Figglewatts

COMMANDS:
   generate  generate the site
   new       create a new site
   open      open a daybookr site in a browser
   help, h   Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --help, -h     show help (default: false)
   --version, -v  print the version (default: false)

COPYRIGHT:
   (c) 2020 Figglewatts

Advanced usage

Using custom config fields in layouts

If you have custom fields in your daybook.yml file, i.e.:

custom_field: this is a string

These can be accessed in a layout by doing something like this:

<h1>{{(.Site.Conf.Get "custom_field").String}}</h1>

Resulting in:

<h1>this is a string</h1>

The config file is parsed with the simpleyaml package. For more information on how to get all kinds of YAML values from the config file (i.e. not just a string as above), please see their documentation.

daybookr's Issues

Error checking for everything is needed

Sometimes markdown isn't formatted correctly

Support for non blog style sites

When running daybookr without a 'posts' directory, this error occurs:

ERROR: could not create site: could not load posts: open site/posts: no such file or directory

Would be good to support any kind of site.
Could be made more generic by just taking markdown documents and turning them into collections of site areas. Doesn't matter if they're posts, pages, or whatever.