Web Engineer. Working mostly with PHP, Symfony and Golang.
Entusiast about Engineering Best Practices, Continuous Delivery and DevOps.
Sports and FC Porto fan!
I did the opposite with my personal website, from Gridsome to Nuxt. ;)
I think where Gridsome really shines is when you need to fetch data from multiple data sources and have an uniform layer over that data.
For my site, I only needed Markdown and some static YAML files and the release of Nuxt Content Module made me switch. I found the data layer of Gridsome a bit overkill for my use case. and like you said, I feel that Gridsome development has slowed down and I am bit unsure about it´s future. Nuxt is a lot more mature and with a bigger community.
I hope it can regain some traction as I think it´s a cool project and there is space for both.
Just an observation about your example of fetching posts from dev.to API in async data. I am still a novice with Nuxt, but since you were rendering a static site, I guess it would be possible to, fetch the posts at build time in a module/plugin and then transforming the results into a format supported by Nuxt Content, for example. Of course if you plan to have other sources in the future, like you said, then yes I think it fits perfectly with Gridsome.
I guess it would be possible to, fetch the posts at build time in a module/plugin and then transforming the results into a format supported by Nuxt Content
I... didn't know this was possible! Will need to research into this a bit more.
A small part of me wants the two projects to be merged together. Imagine having a GraphQL data layer in Nuxt! 🤯
Web Engineer. Working mostly with PHP, Symfony and Golang.
Entusiast about Engineering Best Practices, Continuous Delivery and DevOps.
Sports and FC Porto fan!
I... didn't know this was possible! Will need to research into this a bit more.
Never tried anything similar myself, but Nuxt has Hooks that allows to run code at specific points of Nuxt Lifecycle including build. This is how for example nuxt sitemap plugin works to generate a sitemap at build time. So in theory, it should be possible.
A small part of me wants the two projects to be merged together. Imagine having a GraphQL data layer in Nuxt
Yes. I think it would be a cool add-on on top of Next. It could work similarly to Nuxt Content but with a GraphQL API.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I did the opposite with my personal website, from Gridsome to Nuxt. ;)
I think where Gridsome really shines is when you need to fetch data from multiple data sources and have an uniform layer over that data.
For my site, I only needed Markdown and some static YAML files and the release of Nuxt Content Module made me switch. I found the data layer of Gridsome a bit overkill for my use case. and like you said, I feel that Gridsome development has slowed down and I am bit unsure about it´s future. Nuxt is a lot more mature and with a bigger community.
I hope it can regain some traction as I think it´s a cool project and there is space for both.
Just an observation about your example of fetching posts from dev.to API in async data. I am still a novice with Nuxt, but since you were rendering a static site, I guess it would be possible to, fetch the posts at build time in a module/plugin and then transforming the results into a format supported by Nuxt Content, for example. Of course if you plan to have other sources in the future, like you said, then yes I think it fits perfectly with Gridsome.
I... didn't know this was possible! Will need to research into this a bit more.
A small part of me wants the two projects to be merged together. Imagine having a GraphQL data layer in Nuxt! 🤯
Never tried anything similar myself, but Nuxt has Hooks that allows to run code at specific points of Nuxt Lifecycle including build. This is how for example nuxt sitemap plugin works to generate a sitemap at build time. So in theory, it should be possible.
Yes. I think it would be a cool add-on on top of Next. It could work similarly to Nuxt Content but with a GraphQL API.