Most competitors support some form of "real time" rendering of the rich-text equivalent of the markdown "source code", whereas Zettlr attempts a simpler in-line rendering. Zettlr also supports the addition of "yaml frontmatter" as a means of adding non-printable metadata to markdown documents.Ĭompetitors in this area include markdown-specific local editors such as () and online services such as () as well as general-purpose editing environments which have plugins or extensions to support markdown, such as () The most obvious addition to the Markdown Editor role is the ability to manage one or more "workspaces", each of which contain many markdown documents. While Zettlr certainly fulfils this role, as it is able to edit markdown documents, it also offers more. Markdown is a plain text format for describing rich text documents, and a Markdown Editor is a text editor which has understanding of the Markdown syntax. Right there at the top of the front page it is described as "A MARKDOWN EDITOR FOR THE 21ST CENTURY". If you first find Zettlr via the website, then it is natural to assume that this is the main purpose of the application. In each of the following subsections, I attempt to explain what I mean by each aspect, and evaluate the strengths, weaknesses, and possibilities for Zettlr in this role.
This would not be a problem if the design were static or "finished", but the Zettlr project is ongoing, and the different views of the purpose of the application are causing tension when considering improvements, implementing new features and prioritising bug fixes.įor the purposes of discussion I have identified a few different aspects of the nature of Zettlr. It is a powerful tool with many features but, like (), it appears differently to different people.
0 kommentar(er)
