Issues porting existing website with Gatsby

Summary

Basically I have a set up where I have my own index.html page and I use Gatsby to create blog. Since the index.html page is really complicated, rather than try to migrate it’s code to react, I would prefer to have a set up where the ‘/’ routes by default to my index.html page while the Gatsby page/index.js is mapped to ‘/blog’. How can I accomplish this? Is it possible to have Gatby’s index.js map to some other html page like blog.html or something like that?

File contents (if changed)

gatsby-config.js: N/A package.json: N/A gatsby-node.js: N/A gatsby-browser.js: N/A gatsby-ssr.js: N/A

[und3fined-v01d]

Ohhhh I see there has been a feature request on it but was held back on the pretext that the maintenance for something this trivial would not be worth it! Thank you so much @herecydev, I think your suggestion is the best way out 😁. I’ll close this issue now!

[herecydev]

I see what you’re trying to do, when you use the pathPrefix gatsby will build all the content into the public folder without the blog prefix but will make the links work correctly, e.g. <Link to="/my-first-blog" /> => <Link to="/blog/my-first-blog" />

I think an easy way forward is to:

1. Build the gatsby blog stuff first
2. Move all the files to /blog
3. Add your static index.html to the root
4. Deploy all that to netlify

Hope that makes sense