Maybe a similar question - It seems like the plugin just goes to broken URLs for records in nested directories instead of the expected. Is there a way to pass the model archetype as part of the url that the preview plugin can inject?
And instead for the second question, we don’t manage the “nested directories” in DatoCMS, it’s something that you should take care of in your Gatsby code, OK?
Thanks @mat_jack1. I’m using the Gatsby Dato CMS starter template that leverages the File System Route API instead of creating pages through gatsby-node.js. It creates pages inside of a post directory already. How would I go about making it work with the plugin via the gatsby code so that the plugin discovers the post directory?
Thanks for the suggestion on making a custom plugin. Unfortunately, I am not familiar with making and hosting custom plugins. Is anybody from your team can help to modify the same gatsby source plugin to work with slug text field as well?
@s.verna I have seen it git that, you have worked on this gatsby source plugin. Will you be able to modify this plug-in to work with the slug text field or Can you guide me on how to customize this plugin and use it?
We are planning to add a partner program soon on DatoCMS so that you could be in touch with selected partners that could help you. But I don’t have an ETA for that, sorry