Pros and Cons of Jekyll over WordPress

Jekyll is a static site and blog generator. This means, instead of installing server-side software that’s built with a language like PHP, you use the command line on your local computer to generate static files (HTML, CSS, etc).

Written in Ruby by Tom Preston-Werner, GitHub's co-founder, it is distributed under an open source license.

Pros:

• first and most important
  Instead of using databases, Jekyll takes the content, renders Markdown or Textile and Liquid templates, and produces a complete, static website ready to be served by Apache HTTP Server, Nginx or another web server.

• Jekyll is the engine behind GitHub Pages, a GitHub feature that allows users to host websites based on their GitHub repositories for no additional cost.

• Jekyll is flexible and can be used in combination with front-end frameworks such as Bootstrap, Semantic UI and many others.

• The amount of load is almost impercetible. You’d have to try hard (or have a really lousy web host) to make your blog crash.

• Wordpress Hosting is costly Jekyll hosting is not a too much costly.

• SEO is baked in.

Cons:

• No server-side scripting (e.g. contact forms) you need a api for this.

• No image manipulation tool for interactively cropping and resizing images.

• Spinning up a local installation may intimidate non-programmers.

• Like wordpress u can't update your site or blog on live. You need to be done in local and then make it live for updates.

• Typical for non-technical person to update website or make changes.

Conclusion:
I think a simpler platform like Jekyll is worthy of being considered first.