zotcite VS markdown-blog

I use VimWiki in Markdown format. It is portable and lightweight, but at the same time very versatile. If I need to print some of my notes, I use Pandoc to convert it into a PDF (or other format). I also use it in conjunction with zotcite in order to use my bibliographical database from Zotero inside (Neo)Vim.

According to the author, it is possible to use it with LaTeX, but it is not a feature that is supported. Someone else would have to properly implement and take responsibility for maintaining the code.

There are some plugins for Vim that can use Zotero to do citations. Like this or this. I don't really know much else because I only use Neovim to take notes. I write my papers in LibreOffice which has Zotero integration.

I still have a Blogger site just because I am not sure how to export all the data without days of work to copy the content, images and reformat everything to go to something like WordPress or markdown [0].

[0]: https://github.com/Cristy94/markdown-blog

I did something similar, but for adding a blog system to a server running PHP: https://github.com/Cristy94/markdown-blog

The idea is that having it server-side allows for the page to be cached by a CDN (e.g. CloudFlare), so you end up serving static HTML, with better performance and SEO than JS-compiled markdown.

I store them on my server, some of them that I think can help others I put on my webserver with https://github.com/Cristy94/markdown-blog

If you host anywhere a LAMP stack: I built a very basic markdown-based in PHP: https://github.com/Cristy94/markdown-blog

The idea is that Apache/PHP handle the loading/displaying of markdown files form a directory, so to add a new post you just create a new markdown file. It's very basic, but it's easy to customize with a bit of HTML/CSS/PHP.

If you want something really basic, I created a tiny PHP blog that simply renders your Markdown files: https://github.com/Cristy94/markdown-blog

Working on building userTrack[0] I always encountered the need of various auxiliary tools. I had to implement a custom deploy system to build different variants of the product, to create a licensing server (to create and verify license codes and to allow downloads for valid license owners), a blogging platform[1], some JS snippets [2], etc.

Most of the times, the libraries/tools that you build yourself are either to connect and interact with a specific external service OR to have a simpler (only the features you need) or cheaper version of an existing product/platform.

[0]: https://www.usertrack.net/

[1]: https://github.com/Cristy94/markdown-blog

[2]: https://github.com/Cristy94/dynamic-listener

What a coincidence, I just added RSS support for my open-source "blog" scaffold: https://github.com/Cristy94/markdown-blog#changelog