DEV Community

Cover image for Jekyll to Jigsaw

Jekyll to Jigsaw

Jason McCreary on January 08, 2019

All these year in review and New Year's resolutions got me motivated. I decided use it to complete one of my own goals for the year - redesign blog...
Collapse
 
sharu725 profile image
sharath Kumar

Nice post Jason. I would like to know why did you make the switch from Jekyll. Were there any flaws that made you switch?
I have been using Jekyll for a long time and even for a jekyll themes directory called Jekyll Themes and I love it.

Collapse
 
pojntfx profile image
Felicitas Pojtinger

IMHO the "solution" to switching SSGs is to use Gatsby. Why? React Components are universal, so it doesn't really matter if you switch your SSG to say Next, just recreate the pages with the same components - done! Also makes it possible to use the same design system for your app (Parcel), documentation (MDX), slides (MDX), ...

Collapse
 
gonedark profile image
Jason McCreary

Indeed, there are dozens of solutions available and as such the choice for one is quite subjective. For me, Jigsaw was a natural migration given the PHP base, with Blade + Markdown templates.

Collapse
 
pojntfx profile image
Felicitas Pojtinger

Sure; it's a good SSG indeed. What I mean though is that you're using the SSG as a framework, an whenever you change the framework, you'll have to more or lesd rewrite your app. Using Gatsby you're writing your site/app/whatever using standard (JSX) using a library (React) - makes migration much easier later on. Not saying you're approach is wrong, I just think that it's time to stop writing web sites and rather start writing web apps (which may be implemented by a SSG, and can be just as static) ;)