Yes, your summary sounds fair, at least my impression of that was kind of similar. Some guys here use CI for GitHub repos where their *.md posts are to automate posting to several targets (using DEVβs API also), probably that could work too. I would take a look at GitHub actions for that.
I made some updates to my workflow and I think its perfect now. I can now author posts in my Git repo codebase on VsCode and publish to my site which automatically create/update posts in Dev.to
The links are also smarter now and point to appropriate sites.
Given it was too easy to try, I just tried here is what I think.
So I think I'm still gonna stick with my setup and improve it further to do more.
I have these in mind to remove manual steps:
Yes, your summary sounds fair, at least my impression of that was kind of similar. Some guys here use CI for GitHub repos where their
*.md
posts are to automate posting to several targets (using DEVβs API also), probably that could work too. I would take a look at GitHub actions for that.I made some updates to my workflow and I think its perfect now. I can now author posts in my Git repo codebase on VsCode and publish to my site which automatically create/update posts in Dev.to
The links are also smarter now and point to appropriate sites.
I did these using a Jekyll pre-render hook and a nodeJs script triggered from my publish script
Looks very cool, thanks for sharing π