[turtle4]

Traditionally, dynamic websites run their script to generate a page at the time a request is made so that they output the site in an up to date state. So generally each request looks up data, does some logic, and outputs a templated result. While this ensures that the data shown is the most up to date, it also means your processing time and resource demand goes up a great deal with increasing traffic.

A typical improvement to this is to add a cache layer so that the data is only looked up once in a while. This involves setting up an appropriate time to cache data and/or an appropriate cache expiration scheme.

Jekyll takes a different approach and rather than generating a result when it is requested, it generates the result when the data is saved/published. This is very efficient because the data is ever only looked up once, and it simplifies caching. The trade off is that you aren't looking up the data each request, so it may or may not fit your needs depending on the type of data you are serving and the number of updates that are going to be made.

For a wiki page or a blog, where the number of updates is few compared to the number of requests to read it, Jekyll is a good fit because of its efficiency and ability to scale out simply. That is its appeal, in terms of your original question.

Your description of a few articles from time to time seem to be in line with its use case. That said, if you aren't intending to get alot of traffic, then it is up to you whether the workflow adjustments that it requires makes it a good fit for you or not.