Geobert Quach

Ok, I understand better now, let me rephrase it to be sure: We are going to enable the feature by default in the compilation + activate it by default (on...

For the moment, only pages create a `paginator` object (in `generate_pages`). `generate_posts` does not call `generate_paginators`. But we do have a `collections` object containing a field `context.posts.slug` which contains a...

I've reached a point where `generate_collections_var` is only used by `generate_posts`. So we can, in `generate_collections_var`, generate a `paginator` which is an alias to `collections.posts` so we can still do...

What kind of support? A warning? What if some are using it? :-/ (I don't, I only use next/previous)

Uh? next/previous is in the `page` object, not `collections`.

At the beginning, I've put lowercase strings for these and using serde rename but you weren't sure about it. I'm all for lowercase string for the values, or maybe case...

Just found this https://docs.rs/serde-aux/0.6.1/serde_aux/container_attributes/index.html

What about some overloading mechanism? A global theme, and possibility to override per collection and/or per page?

And we should support Jekyll's theme out of the box, so we'll get the existing huge repository. Gutenberg has so many themes thanks to Hugo's. EDIT: or enhance the Jekyll...

We can mix both ideas, using epage format and the title as the folder name so we can walk collections in parallel. This whole collection concept looks like gutenberg's `Section`...