Hans-Jørgen Vedvik

Currently, there is no easy way to do that, unfortunately. But we can consider implementing `nextNode` and `previousNode` fields on each node type. And also have an argument to decide...

Would this be a good solution? Default sorting is by descending `date`, so `next` will be older posts. But the field can have custom sorting with `sortBy` and `order` arguments...

Sort by directory structure order might not work for source nodes from external APIs. Unless the filesystem source plugin inserted and resolved this field itself. But what about implementing a...

I think we'll add the `edges.next/previous` example above as a simple solution. But the `@gridsome/source-filesystem` plugin will get an overhaul sometime soon to support the number prefixes in filenames and...

I have been testing various options and after some consideration, I think we will wait with this. We are going to allow more configuration for how pages are created from...

Not sure why it behaves differently on Netlify. Can you try querying by `id` instead? ```graphql query MeetingPage ($id: String!) { meetingPage (id: $id) { ... ```

Hi, @hognevevle. I understand your concern about the development of this project. 2020 didn't exactly turn out as we planned... :) We have spent much time building a visual editor...

Hi, which plugins are you using in your project?

Okay. It might be related to the `capture-website` package. Do you have `_keepAlive` set to `true`?

Hi, you can try to use the [`outputDir`](https://gridsome.org/docs/config/#outputdir) option to build the files to another directory instead. GitHub Pages uses subdomains, so a `pathPrefix` shouldn't be necessary.