Lessons 18 through 21 cover using Gulp to manage an asset pipeline for fonts, SASS, and images. As of now there are many improved methods of processing these assets within Eleventy's build process, reducing dependence on Gulp.

Possible Implementation

Luckily, these lessons are isolated from the rest of the course and changing these should not require changes in later lessons. A few thoughts:

Lesson 18: Setting up Gulp —> Delete lesson?

Lesson 19: Setting up SASS —> Replace Gulp tasks with custom Eleventy template formats? See "Process CSS or Sass With LightningCSS | 11ty Rocks!".

Lesson 20: Setting up fonts —> I don't see a way to smoothly integrate this with an Eleventy build process. Is it even necessary to process fonts more than once? Can we just passthrough copy fonts? Should we register them as custom template languages?

Lesson 21: Setting up images —> Switch to 11ty's own eleventy-img processing should work perfectly and will probably be simpler than the current lesson (see also #9?).