<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lyx |</title><link>http://kalz.cc/tags/lyx/</link><atom:link href="http://kalz.cc/tags/lyx/index.xml" rel="self" type="application/rss+xml"/><description>Lyx</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Sat, 25 Mar 2023 09:36:59 +0000</lastBuildDate><image><url>http://kalz.cc/media/icon_hu_1c0e9cb08cfb822a.png</url><title>Lyx</title><link>http://kalz.cc/tags/lyx/</link></image><item><title>Redefining my writing workflow</title><link>http://kalz.cc/post/redefining-my-writing-workflow/</link><pubDate>Sat, 25 Mar 2023 09:36:59 +0000</pubDate><guid>http://kalz.cc/post/redefining-my-writing-workflow/</guid><description>&lt;p&gt;One of the things I have started recently is a book-project. For this purpose I have been working on a new writing workflow which combines reference management, reading, highlighting and note-taking, writing and publishing. In this short post I will try to describe the setup and workflow.&lt;/p&gt;
&lt;h1 id="my-book-writing-workflow-in-detail"&gt;My book-writing workflow in detail&lt;/h1&gt;
&lt;ol&gt;
&lt;li&gt;&lt;em&gt;Sources&lt;/em&gt;: Of course, the basis of all writing is reading :-). To identify prior work and to get an overview about the domain I have collected approximately 80 sources which I have started to read. These sources are mainly journal articles, some are books and book-chapters. I mostly start with GoogleScholar and combine it with some meta-databases like EBSCOHost, but I also appreciate article newsletters from journals (and can recommend the
for our domain). The list of potential sources to identify related work is of course endless and I want to try in the future AI services like
or
(which I both got to know through conversations with Yanay Zaguri: Thanks!).&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Reference management&lt;/em&gt;: I have switched some years ago from Mendely to
and besides a little outdated interface I really appreciate the reliability and extendability of Zotero. I can recommend for example the extension
. The extension takes for example care for renaming PDF and sorting them into a specific folder. In general, Zotero works great in importing references from the web and it can for example also generate references to books based on ISBN-numbers. You can easily collect a nice list of well-formated references.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Reading and structured notetaking&lt;/em&gt;:
has really changed the way I read papers and take notes about them. As described in an
the PDF-reader and annotation environment is perfect for taking structured notes. The nice thing is, that I can directly access papers from Zotero. I can start a paper from my database and open it on the left side of the screen while I have a chapter structure for my book-projekt as an outline on the right side. Whenever I think something fits into this structure I can either mark and shift pieces of text from left to rigth, or I can note down ideas for chapters.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Writing&lt;/em&gt;: My main target format for the book is a well-formatted PDF. Due to this requirement I am using
as a visual editor which can produce nicely formatted documents via LaTeX. Again, the interface looks a little outdated, but the functionaliy is really great. LyX can access directly my reference libary from Zotero and has sufficient styling options to produce a nice looking text.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Publishing&lt;/em&gt;: As already mentioned, one important output format is a PDF file. This is the standard format of the editor I am using for writing. At the same time, I would like to produce a web-version of the text. For this purpose I have configured LyX to produce MarkDown files from the same text which I can easily integrate into
which is running on the basis of
. Via this route I can easily give people access who can provide feedback to the chapters during the writing process.&lt;/li&gt;
&lt;/ol&gt;</description></item></channel></rss>