# What asset pipeline for Jekyll?

**URL:** <https://talk.jekyllrb.com/t/what-asset-pipeline-for-jekyll/9559>\
**Category:** Help\
**Created:** [November 27, 2024, 6:39am UTC](https://talk.jekyllrb.com/t/what-asset-pipeline-for-jekyll/9559 "2024-11-27T06:39:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VillyVretthorn](https://avatars.discourse-cdn.com/v4/letter/v/a587f6/32.png) [@VillyVretthorn](https://talk.jekyllrb.com/u/VillyVretthorn)\
**Post date:** [November 27, 2024, 6:39am UTC](https://talk.jekyllrb.com/t/what-asset-pipeline-for-jekyll/9559/1 "2024-11-27T06:39:11Z")

</div>

What asset pipeline do people use with Jekyll?

I have seen there is Jekyll-asset-pipeline ([GitHub - matthodan/jekyll-asset-pipeline: Powerful asset pipeline for Jekyll that collects, converts and compresses JavaScript and CSS assets](https://github.com/matthodan/jekyll-asset-pipeline)) but this project seems abandoned.  
The project lists this post as its “website”: [https://matthodan.com/2012/11/22/jekyll-asset-pipeline.html](https://matthodan.com/2012/11/22/jekyll-asset-pipeline.html) and this points to a blog that seems to be deleted.

---

<div class="post-metadata">

**Author:** ![rdyar](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.jekyllrb.com/rdyar/32/710_2.png) [@rdyar](https://talk.jekyllrb.com/u/rdyar)\
**Post date:** [November 27, 2024, 4:43pm UTC](https://talk.jekyllrb.com/t/what-asset-pipeline-for-jekyll/9559/2 "2024-11-27T16:43:37Z")

</div>

I’m not aware of any that are recently mentioned - this used to be popular but I never hear anything about it now:

> **[GitHub - envygeeks/jekyll-assets: :art: Asset pipelines for Jekyll.](https://github.com/envygeeks/jekyll-assets)**
>
> :art: Asset pipelines for Jekyll.

At one point I separated out the css,js and img handling from jekyll and handled it on my own via Gulp. You can also do something similar with NPM. It actually worked really well.

Here is some info on what I did though it is fairly old:  
[https://rdyar.github.io/2017/10/01/speed-up-jekyll-by-using-gulp-for-sass-and-other-assets/](https://rdyar.github.io/2017/10/01/speed-up-jekyll-by-using-gulp-for-sass-and-other-assets/)

---

<div class="post-metadata">

**Author:** ![VillyVretthorn](https://avatars.discourse-cdn.com/v4/letter/v/a587f6/32.png) [@VillyVretthorn](https://talk.jekyllrb.com/u/VillyVretthorn)\
**Post date:** [November 28, 2024, 12:20pm UTC](https://talk.jekyllrb.com/t/what-asset-pipeline-for-jekyll/9559/3 "2024-11-28T12:20:25Z")

</div>

> [@rdyar](#):
>
> At one point I separated out the css,js and img handling from jekyll and handled it on my own via Gulp. You can also do something similar with NPM. It actually worked really well.
> 
> Here is some info on what I did though it is fairly old:  
> [Speed Up Jekyll By Using Gulp For Sass And Other Assets](https://rdyar.github.io/2017/10/01/speed-up-jekyll-by-using-gulp-for-sass-and-other-assets/)

I am too afraid of node/NPM. I want all my jekyll sites to be low maintenance and it seems node is a whole new world I need to understand, so would like to avoid a dependency on it. Although I see that it is so widely used in all kinds of projects that I probably have to figure it out at some point…

Thanks for the link, I will check out what you did there.