Geobert Quach

Sorry for this huge delay, a video game sucked me out real life x) I've updated the proposal with more paginator object description. All the values in `_cobalt.yml` are available...

Maybe I'm misunderstanding something but this part: > all the values in config can be overriden in frontmatter of each page Means all the values I defined in the `_cobalt.yml`...

I'm trying to understand how Cobalt is working to identify where I will put the pagination code. Correct me if I'm wrong: I'll need to work on `liquid.rs` project as...

Also, I'm studying Liquid, and especially the for loop block. But I can't understand how `collections.posts.pages` is resolve in Liquid, can you give me some insight on this please? :)

Got it! It's in `generate_doc` in `cobalt.rs` when we put "collections" into `globals` :D

After studying the code and [made the refactoring](https://github.com/cobalt-org/cobalt.rs/issues/436) I understand a bit more the implication of pagination. I'm rewriting the proposal

Rewritten proposal posted! :D

> I think this gets down to recording requirements which should be the first role of a proposal which we don't have written down and agreed to yet. I've seen...

I've read what you wrote as requirements and I quite agree with all. I just added `published_date` with no year nor month in order to paginate `collections.posts.pages`.

Updated the proposal with no global config and activation from frontmatter