+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.
+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 :)