I can see there’s a discussion / branch here, but I get the impression that this is more related to remote data.
I think this goes some way to solving my problem, however I’m more interested in creating simple logic that then triggers the creation of a new page. An example of this triggering mechanism might be:
I’d be OK with a scripted approach, it’d be a shame to lose the live-reload during development and additional overhead of running scripts with every change. I guess I could use a task-runner to handle this.
As an aside, I realised why I thought this might be doable - Hugo’s .Paginate system does in fact generate new pages based on internal logic. It generates /page/n depending on the number of pages, and the PageSize.
Thanks for clarifying. I’ve decided for the interim to take this approach:
To assume this feature will eventually happen (thanks @bep)
Store my data in the /data/ directory
Create a shortcode that accepts two data paths (left and right) and outputs my comparison page
Use a script to create section content for all data-combinations, the content will simply use the shortcode.
---
title: "A vs B"
---
{{< comparison left="data/a.json" right="data/b.json" >}}
With this approach I would get livereload when editing the data files, and it should be easy enough to change my theme if / when a “scripted page generator” becomes available.