With all due respect, I think this is a pretty trash solution and just because it exist, doesn't mean you should use it. I'd rather use a headless CMS for something like this. Github issues aren't there to give your blog a comment functionality.
If you are going to use Gatsby.js and go against its static nature, not to forget compiling it every time you add something, you know you have a hammer for a problem that is not a nail.
For a blog, I'd rather use WordPress. I can add Barba.js for prefetching and smooth page transitions which will make it feel like any other SPA with the added benefit of superior SEO and dynamic content. Along with WebPack, code-splitting, lazy loading, I don't think there is any other better option available today.
If you are going to use a JAM stack website and end up going against its essential static nature, I think it is better to use Next.js if not WordPress. Because God forbid if one goes against the hype-train and use old technologies that are for cavemen (referring to PHP and WordPress).
Please, reread my comment because you misunderstood me. I'm a MERN and LAMP stack developer. I don't choose one technology over another because I hold biases or misconceptions against them. I'm the type of person who understand that there are options and must choose a suitable option in order to solve the given problem. I've created the last few websites using WordPress and even my blog website is in WordPress.
I just think English is not your first language. I never said that PHP and WordPress is for cavemen, I said that usually new developers that jump at the MERN hype-train thinks that PHP and WordPress are for cavemen.
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.
With all due respect, I think this is a pretty trash solution and just because it exist, doesn't mean you should use it. I'd rather use a headless CMS for something like this. Github issues aren't there to give your blog a comment functionality.
If you are going to use Gatsby.js and go against its static nature, not to forget compiling it every time you add something, you know you have a hammer for a problem that is not a nail.
For a blog, I'd rather use WordPress. I can add Barba.js for prefetching and smooth page transitions which will make it feel like any other SPA with the added benefit of superior SEO and dynamic content. Along with WebPack, code-splitting, lazy loading, I don't think there is any other better option available today.
If you are going to use a JAM stack website and end up going against its essential static nature, I think it is better to use Next.js if not WordPress. Because God forbid if one goes against the hype-train and use old technologies that are for cavemen (referring to PHP and WordPress).
Please, reread my comment because you misunderstood me. I'm a MERN and LAMP stack developer. I don't choose one technology over another because I hold biases or misconceptions against them. I'm the type of person who understand that there are options and must choose a suitable option in order to solve the given problem. I've created the last few websites using WordPress and even my blog website is in WordPress.
I just think English is not your first language. I never said that PHP and WordPress is for cavemen, I said that usually new developers that jump at the MERN hype-train thinks that PHP and WordPress are for cavemen.