# Building just specific pages when developing **URL:** \ **Category:** Help\ **Created:** [June 30, 2020, 8:29am UTC](https://talk.jekyllrb.com/t/building-just-specific-pages-when-developing/4659 "2020-06-30T08:29:54Z")\ **Posts on this page:** 1\ **Showing post:** 8
**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:** [July 2, 2020, 5:54pm UTC](https://talk.jekyllrb.com/t/building-just-specific-pages-when-developing/4659/8 "2020-07-02T17:54:59Z")
if you move the asset processing to Gulp or some other task runner you can speed stuff up quite a bit. Gulp can process sass almost instantly, so if you are just working on css then that is much easier - but it also removes that step from jekyll so it makes the rest of what jekyll does faster. Gulp can also move the images which is another thing that takes time for jekyll to do. I have my site so that jekyll mainly handles the page creation/layouts/includes. Gulp handles sass, js and images. Check this post for info on what I did and also info from MM on how he does it. It can be a little complicated if you are not familiar with Gulp, which I was not, but I got the hang of it. > [@Speed up jekyll - use gulp for sass/assets](https://talk.jekyllrb.com/t/speed-up-jekyll-use-gulp-for-sass-assets/1036): > > I wrote a blog post about using gulp to process all sass files as well as JS and images - removing them from the Jekyll work load at the same time as not needing to have Jekyll rebuild the site whenever a sass file or js file or image is edited. Gulp will compile sass files instantly more or less, so using live reload, saving a change to a sass file almost instantly refreshes the browser. By using gulp for all of those assets has cut my build time for Jekyll down to half a second from about 6 … --- _[View the full topic](https://talk.jekyllrb.com/t/building-just-specific-pages-when-developing/4659)._