This is a really good idea with great potential. Image a standarized API for different blogs. You can automatize publishing and editing, multiple collaborators. And use a git provider as unique source of content.
And you can also make your git repo as some sort of blog. I'll use it for my next posts for sure.
Software engineer, I've been working with Angular for 6 years now and strive to work more full stack. I publish on dev.to about topics I love around open source, frontend, data privacy, automations.
Thanks! I do intend to push it further and someone else plans to help me out :)!
Image a standarized API for different blogs
That was the original purpose. But I realized it wouldn't fit into a hackday so I decided to get the project up and running with support for only one "publisher" (dev.to). My original though was that I'd build something completely abstract and we could choose for one article to publish on multiple "publisher" at the same time (dev.to, medium, etc).
And you can also make your git repo as some sort of blog
This is a really good idea with great potential. Image a standarized API for different blogs. You can automatize publishing and editing, multiple collaborators. And use a git provider as unique source of content.
And you can also make your git repo as some sort of blog. I'll use it for my next posts for sure.
Thanks!
Hi Brian,
Thanks! I do intend to push it further and someone else plans to help me out :)!
That was the original purpose. But I realized it wouldn't fit into a hackday so I decided to get the project up and running with support for only one "publisher" (dev.to). My original though was that I'd build something completely abstract and we could choose for one article to publish on multiple "publisher" at the same time (dev.to, medium, etc).
Definitely!
Awesome, glad to hear that! =)
Check out my git jekyll blog takes less than a few minutes to setup.
Jekyll