I am a product engineer and have helped build software from small startups, to manipulating hundreds of millions of data points. I write API's and make tools that make developers lives easier.
As long as you have an RSS feed Dev can already pull in your posts, auto populate the canonical_url and leave it unpublished in your drafts. No need to make an api. Just make sure your RSS feed is being generated
Ah, that's really cool! I didn't realize that was a thing.
Do you know if it updates your posts on dev if the RSS feed gets updated? Are there limits to the types/lengths of content that can be imported via RSS?
I am a product engineer and have helped build software from small startups, to manipulating hundreds of millions of data points. I write API's and make tools that make developers lives easier.
I’m a full stack developer who has experience with several front-end tools like Reactjs, Vuejs, and jQuery as well as some back-end tools like PHP, Laravel, Node, and Express.
Location
IL
Education
AAS in Information Technology/Web Development
Work
Senior Software Development Engineer at Wizards of the Coast
+1. My first instinct was to suggest this. I played around with this a little bit (I have some drafts lying around, haven't actually posted publicly so far) and it works like a charm. There can be some content editing required from time to time, so I strongly agree that it's important that posts start off as drafts and have a manual intervention for public posts.
I like this approach since its not too tightly coupled between gatsby<-->dev.to and works using a industry standard API (RSS) that's proven and can work as a generic solution across the board between various sources and sinks... Not to mention it's readily available without too much effort for gatsby!
There may be some specific use-case enhancements we envision that this may lack but I guess this is at least a great 80-20 scenario that works well :)
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.
As long as you have an RSS feed Dev can already pull in your posts, auto populate the
canonical_urland leave it unpublished in your drafts. No need to make an api. Just make sure your RSS feed is being generatedAh, that's really cool! I didn't realize that was a thing.
Do you know if it updates your posts on dev if the RSS feed gets updated? Are there limits to the types/lengths of content that can be imported via RSS?
The dev.to/settings/publishing-from-rss says so - at least for unpublished posts is what I'm guessing (it did for me).
I don't believe it will update posts that were already published. But I have not tried that
In addition, there’s a gatsby plugin which automatically creates an RSS feed for your site. gatsbyjs.org/packages/gatsby-plugi...
+1. My first instinct was to suggest this. I played around with this a little bit (I have some drafts lying around, haven't actually posted publicly so far) and it works like a charm. There can be some content editing required from time to time, so I strongly agree that it's important that posts start off as drafts and have a manual intervention for public posts.
I like this approach since its not too tightly coupled between gatsby<-->dev.to and works using a industry standard API (RSS) that's proven and can work as a generic solution across the board between various sources and sinks... Not to mention it's readily available without too much effort for gatsby!
There may be some specific use-case enhancements we envision that this may lack but I guess this is at least a great 80-20 scenario that works well :)