![]() ![]() Some competitors provide browser plugins or "bookmarklets" to grab information and add it to the repository. Going form waking up in the middle of the night with an idea, or finding inspiration on a random web page or academic paper, to a useful representation in your knowledge management tool should be as smooth and direct as possible. This kind of application has several key attributes. Zettlr also adds the ability to link to external URLs and to academic literature outside the workspace, with the help of a separate reference manager such as ()Ĭompetitors in this area range from the simple, such as () to the complex (), (), () etc. Zettlr fulfils this role in that markdown files within a Zettlr workspace can be used to hold textual "nuggets" and the Zettr variant of Markdown includes a syntax for linking between files. Some such tools support the addition of almost any type of data object (images, videos, captured web pages, rich and plain text documents, etc.), whereas some are more specific The specific variants usually limit themselves to textual information and include some way to connect the "nuggets", either using special text sequences within the information, or by associating external metadata. This is a broad category of applications with a range of approaches, but the common features seem to be the ability to capture and interlink "nuggets" of information, knowledge, or opinion so that they may be found and used later. As a simple Markdown Editor, Zettlr takes a long time to load and manage workspaces of files, even if you only wish to edit a single file.Īnother major aspect of Zettlr is as a () tool. * more solid handling of markdown rendering and eliminating quirks such as lines which start with `#` appearing as headings even in "back-tick" code blocks. Priorities for improving this aspect of Zettlr could include: If a Zettlr user views Zettlr though the lens of a Markdown Editor, the lack of such a preview seems a strange omission. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |