Previously, I’ve written about why static blogging tools can be better than WordPress, and about a range of tools worth considering for this purpose. But for most people, I recommend one of two tools:
之前，我曾写过关于为什么静态博客工具可以比WordPress更好的文章 ，以及有关为此目的值得考虑的一系列工具 。 但是，对于大多数人来说，我推荐以下两种工具之一：
I’ve used both generators extensively and have a lot of love for both of them, so I don’t want to pit them against each other as if there’s some sort of objective winner. But I will compare them because they share many similarities and, to a newcomer, it might not necessarily be easy to choose between them.
我已经广泛使用了两个生成器，并且对它们都非常喜欢，所以我不想让它们相互竞争，就好像有某种客观的赢家一样。 但我将它们进行比较，因为它们具有许多相似之处，而且对于新手来说，在它们之间进行选择可能不一定容易。
Here’s what you need to know:
这是您需要了解的内容：
简单 (Simplicity)
In the past, I’ve described Jekyll as “the WordPress of static blog generators”, and I think that label still applies. It’s the first tool that comes to mind when people think of static blogging and, popularity-wise, it has a huge lead over the nearest competitor (and even then, “the nearest competitor” is a fork of Jekyll).
过去，我将Jekyll描述为“静态博客生成器的WordPress”，但我认为该标签仍然适用。 当人们想到静态博客时，它是想到的第一个工具，并且在流行度方面，它比最近的竞争对手具有巨大的领先优势 (即使那时，“最近的竞争对手”也是Jekyll的分支)。
There’s probably a number of reasons why Jekyll became so popular — it was one of the earliest generators, for instance — but I’d argue the reason it’s remained so popular is because of its simplicity.
Jekyll如此受欢迎的原因可能有很多，例如它是最早的发电机之一，但我认为它仍然如此受欢迎的原因是它的简单性。
This is what the Jekyll blogging process looks like:
这是Jekyll博客过程的样子：
- Install Jekyll. 安装Jekyll。
- Create a blog via the command line. 通过命令行创建博客。
- Create text files inside a “_posts” folder. 在“ _posts”文件夹中创建文本文件。
Of course, this process can generally be applied to all static blogging tools, but the difference is that Jekyll doesn’t require any notable tweaking or configuration to get going. The default template is fine, the default settings are sensible, and the only real changes you need to make are in defining the name and URL of the blog.
当然，此过程通常可以应用于所有静态博客工具，但是区别在于Jekyll不需要任何显着的调整或配置即可开始。 默认模板很好，默认设置很合理，您唯一需要做的真正更改就是定义博客的名称和URL。
Middleman, on the other hand, requires extra setup to get going. You’ll need to dig into the documentation, install the “blog” extension, and spend an afternoon figuring out what you’re doing before you end up making anything that looks like something. Once that setup is done, Middleman is essentially the same as Jekyll in regards to simplicity, but since Jekyll has fewer features, it has a built-in “idiot proof” factor. You’ll have a harder time breaking everything as a result of a silly mistake.
另一方面，Middleman需要额外的设置才能开始。 您需要深入研究文档，安装“ blog”扩展，并花一个下午弄清楚自己在做什么，然后才能完成任何看起来很像的事情。 一旦完成设置，就简单性而言，Middleman本质上与Jekyll相同，但是由于Jekyll具有较少的功能，因此具有内置的“白痴证明”因素。 由于愚蠢的错误，您将很难再破坏所有内容。
Jekyll, then, has an advantage when building a personal blog, or when building a blog that won’t need to expand far beyond the blogging mold.
那么，Jekyll在建立个人博客或建立不需要扩展到超出博客范本的博客时具有优势。
灵活性 (Flexibility)
To say that Middleman is a static blog generator is a little misleading. In actual fact, it’s a static site generator. The blogging component must be installed as a plugin (as is the case with a number of other features).
要说Middleman是静态博客生成器，这有点误导。 实际上，这是一个静态站点生成器。 博客组件必须作为插件安装( 许多其他功能就是这种情况)。
This, however, can be considered an advantage.
但是，这可以认为是一个优势。
Middleman doesn’t lock you into a particular way of working. Most people will use the blogging plugin, but you can also build a complicated site — even choosing to create multiple blogs, if you want. Because of this flexibility, some simplicity is lost, but for anyone with a little development experience, it’s hardly a big sacrifice.
Middleman不会将您锁定在特定的工作方式上。 大多数人将使用Blogging插件，但您也可以构建一个复杂的网站-甚至可以选择创建多个Blog。 由于具有这种灵活性，因此失去了一些简单性，但是对于只有少量开发经验的人来说，这并不是什么大的牺牲。
With my own blog, for instance, I didn’t want it to be just a blog. I wanted to publish books online in a manner distinct from the blog, and with Middleman, I’ve been able to do that. Is that same thing possible with Jekyll? Basically, yes. But Jekyll works best when used to build a standard blog, which aids in simplicity, but isn’t always the best option.
例如，对于我自己的博客，我不希望它只是一个博客。 我想以不同于博客的方式在线出版书籍，而与Middleman一起，我已经做到了。 Jekyll有可能发生同样的事情吗？ 基本上是。 但是，Jekyll在用于构建标准博客时效果最佳，这有助于简化操作，但并非总是最佳选择。
Middleman has some blog-centric features that I prefer over Jekyll — you don’t have to include a date in the file names of your blog posts, for instance — but the major distinction comes down to how much you want to do with your tool of choice. If you “just” want a blog, Jekyll will serve you well. If you need more complex structures for your content, Middleman has a strong lead.
与Jekyll相比，Middleman具有一些以博客为中心的功能，例如，您不必在博客文章的文件名中包含日期，但是主要区别在于您想对工具进行多少操作选择。 如果您“只是”想要一个博客，Jekyll将为您服务。 如果您的内容需要更复杂的结构，Middleman可以发挥主导作用。
速度 (Speed)
One of the biggest benefits of static blog generators is that, because the generated results are completely static files, they’re able to load extremely fast on any web host. I even managed to get my blog to load in well-under a second. In this regard, Jekyll and Middleman are identical.
静态博客生成器的最大好处之一是，由于生成的结果完全是静态文件，因此它们能够在任何Web主机上快速加载。 我什至设法使我的博客加载时间不到一秒钟 。 在这方面，杰基尔和米德尔曼是相同的。
Middleman does, however, have a slight edge due to the variety of performance-focused extensions available:
但是，由于可用的各种以性能为中心的扩展，Middleman确实有一点优势：
Using these extensions will help eke out further performance benefits.
使用这些扩展将有助于获得更多的性能优势。
Jekyll has some equivalents though, and most of these things are easy enough to handle manually. So while this is an edge for Middleman, it’s not exactly a definitive point in either platform’s favor.
Jekyll有一些等效项，而其中大多数都很容易手动处理。 因此，尽管这对Middleman来说是一个优势，但这并不是任何一个平台都支持的明确观点。
发展历程 (Development)
We’re experiencing a rennaissance for static blog generation but there’s still a lot of room for improvement. As such, it’s important to consider which blog generator is under the heaviest development.
我们正在经历静态博客生成的复兴，但仍有很大的改进空间。 因此，重要的是要考虑哪个博客生成器处于最繁忙的发展之中。
Luckily, Middleman and Jekyll are both receiving a lot of love in this regard.
幸运的是，Middleman和Jekyll在这方面都收到了很多爱。
Middleman, for instance, is closing in on the release of Version 4. You can click here to see their new website, and also read about the various changes made to the tool. This particular upgrade focuses on:
例如，Middleman正在关闭版本4的发布。您可以单击此处查看其新网站，还可以了解对该工具所做的各种更改 。 此特定升级专注于：
…removing a lot of lesser used features in the core and replacing them with either better-supporting approaches which already existed or moving that functionality into an extension.
…在核心中删除了许多较少使用的功能，并用已经存在的支持更好的方法替换了这些功能，或者将该功能迁移到扩展中。
There’s no particular “wow factor” to point out, but the tool is maturing a significant amount with this release.
没有特别的“惊喜因素”要指出，但是该工具在此版本中日趋成熟。
Jekyll, on the other hand, is closing in on the release of Version 3, and there are a number of features on the horizon. The addition of incremental generation, for instance, means that generating a blog with Jekyll will be much faster. This feature can already be found in Middleman but it’s nevertheless a great addition to Jekyll.
另一方面，Jekyll将关闭版本3的发布 ，并且即将推出 许多功能 。 加入增量的产生，例如，意味着产生具有杰基尔一个博客会快很多 。 该功能已经在Middleman中找到，但它仍然是Jekyll的重要补充。
If I had to pick a winner, I’d say Jekyll comes out ahead since it has a larger team of core developers, a bigger community, and more regular blog updates, but it’s also an imperfect comparison. Middleman is a bigger piece of software with a number of features that Jekyll has yet to add, so it makes sense that its growth doesn’t appear as rapid.
如果我必须选择一个赢家，我想说Jekyll会领先一步，因为它拥有更多的核心开发人员团队，更大的社区和更定期的博客更新，但这并不是一个完美的比较。 Middleman是更大的软件，具有Jekyll尚未添加的许多功能，因此可以理解其增长速度并没有那么快。
Either way, neither tool is on its way to the deadpool and we can expect a lot more from both of them over the coming months.
无论哪种方式，这两种工具都不会陷入僵局，我们可以期望在接下来的几个月中这两种工具会有更多的发展。
最后的想法？ (Final Thoughts?)
Like I’ve said, there’s no real winner in a comparison between Jekyll and Middleman. Both are great tools that serve different purposes within the same space. Middleman is what I use for my business blog, while Jekyll is what I’d use for a personal blog. That doesn’t mean one can’t be used for either purpose but therein lies a useful question:
就像我说过的那样，杰基尔和米德尔曼之间没有真正的赢家。 两者都是出色的工具，可在同一空间内实现不同的目的。 我在商业博客中使用中间人，而在个人博客中使用Jekyll。 这并不意味着一个人不能用于任何一个目的，但其中存在一个有用的问题：
What are you actually trying to create?
您实际上想创建什么？
If you can answer that question clearly, then I hope the points I’ve covered in this article help make the decision a little clearer.
如果您可以清楚地回答该问题，那么我希望本文中介绍的要点可以使您的决定更加清晰。
Which static blogging tool do you prefer? Do you have any tips for getting the most out of your favorite?
您更喜欢哪种静态博客工具？ 您有什么技巧可以充分利用自己喜欢的东西？
翻译自: https://www.sitepoint.com/static-blogging-g-face-middleman-vs-jekyll/
3091
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
