Is there any point in using Jekyll and not WordPress?

Question

CMS

I have always used WordPress for website development and I still like it. But lately I've been hearing a lot about the Jekyll static site generator, with which you can create light and simple sites.
Now I am planning to start working on a portfolio site and, in principle, I can do without an admin panel. I started to study Jekyll and it is more or less clear to me how to use it, but on the other hand, I got the feeling that, in fact, it does not differ from the usual layout. After all, you can also assemble the usual layout using Gulp, Sass and the Nunjucks template engine.
Can someone explain what the cardinal difference is, I just don't fully understand it yet? Or maybe stay on WordPress altogether?
For me it is important:

1. so that the URL does not have .html endings or something like that
   
2. so that if I create a folder "portfolio" in the root of the site, and in it a folder with the name of the project "project-name", as a result it turns out like this "site.ru/portfolio/project-name"
   

Answer 1

For me, it is important: 1. that the URL does not have .html endings or something like that; 2. so that if I create a folder "portfolio" in the root of the site, and in it a folder with the name of the project "project-name", as a result it turns out like this "site.ru/portfolio/project-name"

There will be no problems with this.
Yes, but... Scattering posts by tags and categories, rss and sitemap, page navigation, search, something else... it's lazy to do all this yourself. Jekyll acts as a ready-made configuration that you can take and use for such tasks without worrying about what is there and how it works. This is his purpose. It is clear that jekyll will not replace gulp or webpack in tasks like building a modern frontend (you know, this is when there are 100500 modules, babel or even typescript, preprocessors, postprocessors, etc.), but the issues are precisely the file structure of the site and everything that it can be connected with it, he solves it well and without any questions.
If you just want a static portfolio - then why is there some kind of cms? It will only slow down and do nothing. You can also host statics on github - for free and quite reliably.