The idea seems to be very similar by keeping actual content separate from the final output rendering so that changing the template or styling is trivial.
通过将实际内容与最终输出呈现分开来看，这个想法似乎非常相似，因此更改模板或样式是微不足道的。
1 个解决方案
#1
4
2 things that spring to mind:
想到的两件事：
- You don't have to write the transform engine yourself
- 您不必自己编写转换引擎
- You don't have to write your pages in XML; in Hyde, for instance, you can write your pages in Markdown and use filters to convert it to HTML
- 您不必用XML编写页面;例如，在Hyde中，您可以在Markdown中编写页面并使用过滤器将其转换为HTML
UPDATE: Regarding the idea behind it, I think the main goal is to get (most of) the benefits of a dynamic blog or cms engine, but all the performance (especially w.r.t. memory footprint) wins of static files. As a secondary benefit, this enables you to write your content in your favorite text editor and version it using your favorite version control tool.
更新：关于它背后的想法，我认为主要目标是获得（大部分）动态博客或cms引擎的好处，但所有性能（特别是w.r.t.内存占用）赢得静态文件。作为次要优势，您可以使用自己喜欢的版本控制工具在自己喜欢的文本编辑器中编写内容并对其进行版本化。
#1
4
2 things that spring to mind:
想到的两件事：
- You don't have to write the transform engine yourself
- 您不必自己编写转换引擎
- You don't have to write your pages in XML; in Hyde, for instance, you can write your pages in Markdown and use filters to convert it to HTML
- 您不必用XML编写页面;例如，在Hyde中，您可以在Markdown中编写页面并使用过滤器将其转换为HTML
UPDATE: Regarding the idea behind it, I think the main goal is to get (most of) the benefits of a dynamic blog or cms engine, but all the performance (especially w.r.t. memory footprint) wins of static files. As a secondary benefit, this enables you to write your content in your favorite text editor and version it using your favorite version control tool.
更新：关于它背后的想法，我认为主要目标是获得（大部分）动态博客或cms引擎的好处，但所有性能（特别是w.r.t.内存占用）赢得静态文件。作为次要优势，您可以使用自己喜欢的版本控制工具在自己喜欢的文本编辑器中编写内容并对其进行版本化。