leostera/cactus

🌵A composable static site generator

cactus's Issues

Consider renaming `site` to `cactus`

1. Much more unlikely to accidentally match an existing file with that name (given the domain of the tool)
2. Makes it more obvious that something is related to the build tool

Support more General Templating

If site files supported rules like:

(page
   index.md
   (with-generator Index.re))

Then perhaps we can define Index.re to be:

open Cactus;

include Cactus.Generator.Make({

  let render = (ctx, project, site, page) => {
     /* and here we can transform the Index.md page using Omd */ 
  };

});

This would allow to treat pages as inputs to modules, which can then do really just any amount of side-effects to transform them (including any I/O).

xrefs: #8

Testing Cactus

Hey @Ostera, nice work. Thanks you for sharing this.

I tried this and seems to do what it says its supposed to do. A few questions.
Here is the demo: https://github.com/idkjs/cactus-example.

Running now from the _public dir seems to work. Deployed here: https://public-hfxpuofntn.now.sh. Is there a way to generate an index page?

Also, running gh-pages -d _public doesn't seem to do anything though it creates the repo branch. Is there a particular set up to get something to render?

Tell you what, you were serious when you said it ridiculously simple. Thanks again.

Surface OMD Errors with line number

While compiling, getting a nice error telling me what line number is the broken one seems ideal to fix it quickly.

Support watch mode on build.

The watch mode should keep no cache, and should not keep any state in memory.

It should listen to file system changes (adding, removing, modifying) and retrigger a full build.