DEV Community

Discussion on: Static Site Generators rundown - How I set up my own blog with Jekyll

Collapse
 
fyodorio profile image
Fyodor

Please, give your thoughts after that πŸ˜‰ I like the resulting setup of this integration, and interested if other developers find this useful and what pros/cons do they see

Thread Thread
 
deepu105 profile image
Deepu K Sasidharan

Given it was too easy to try, I just tried here is what I think.

  • It's stupid easy to do this, so if you just want to host dev blogs on your own blog as well, then this is good
  • It has some issues like the Dev specific liquid tags are broken if you use Hugo or something as the framework
  • I don't think you will still have as much control as the manual process(Which I tend to automate further using the Dev API)

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:

  • Use Dev API to automatically publish/update posts I publish to my blog to Dev account as well
  • Automatically update links in the post to refer to the link in Dev.to or my blog depending on where its published
Thread Thread
 
fyodorio profile image
Fyodor

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.

Thread Thread
 
deepu105 profile image
Deepu K Sasidharan

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

Thread Thread
 
fyodorio profile image
Fyodor

Looks very cool, thanks for sharing πŸ‘