Huge congratulations on the launch!

Thanks Matt :)

3.2 million users - 1 dev - 1 marketer - 1 designer

Here’s a similar project I made when I was a teenager:

Marx, The classless CSS reset (perfect for Communists).

https://github.com/mblode/marx

I like it, it's very minimalist and purist!

Thank you dang for updating the title and URL!

The funny thing is that the thread so far has still mostly been generic, yet I swear the comments are higher-quality than they would have been without the change. (Impossible to say for sure, of course)

I contributed the RSS icon[1] to Feather a few years ago. The circle shape in the RSS icon is visually denser and deviates from all other shapes in the icon set. I apologize for breaking the constraints but in my defense, it looks much nicer this way

[1] https://feathericons.com/?query=rss

This is my similar project from 2015: Marx - The classless CSS reset (perfect for Communists) https://mblode.github.io/marx/

PurgeCSS is a tool to remove unused CSS styles https://purgecss.com/

I found this to be an extremely valuable tutorial! The step-by-step format using code diffs made everything very clear and easy to follow along. If you're a beginner or intermediate Rust developer, Phillipp's series of tutorials can also be useful as a guide to structure a moderately feature-full codebase in a way that is easy to grok. Great work and I'd love to see a similar series like this on other topics like building a Markdown parser or basic key-value database for example.

Thank you! I enjoyed writing this a lot, but I have to admit that having kilo as the predecessor allowed me to focus exclusively on Rust without having to worry about other things. I hope to find the time to write a different tutorial soon.

I recently built my personal site and this is the first time I'm sharing it with the world! https://matthewblode.com/

For my university essays, I keep my research citations in Zotero and write in Markdown using Ulysses. Then when it is ready to submit, I'll use Raphael Kabo's technique [1] to export into Microsoft Word. It is a truly simple workflow to get perfect formating with little effort.

[1] http://raphaelkabo.com/blog/posts/markdown-to-word

Genuine question: what do you do with Word docs sent back to you as email attachments with track changes and embedded comments?

I'm slowly realising that my colleagues for whom this "works" are never going to change. Our shared folders are littered with "Copy of FINAL final + comments 2.7.18-my-copy.docx.docx". It doesn't matter how slick my git + markdown + pandoc workflow is when conversations go like this:

"Just use track changes."

"But..."

"JUST USE TRACK CHANGES."

Is your markdown to Word reversible? If so, accept all changes, convert back to Markdown and run git diff. I guess you're losing comments though.

Definitely worth a go.

Comments might be extractable, I'm not familiar with docx format but it's zipped X(?)ML type data so there will be parsers. Or a conversion to an intermediate format that's more amenable to computer processing, perhaps.

The problem remains in reverse, though: it's expected that I will produce Word docs full of track changes edits.

I second this workflow - thanks to Zotero and Ulysses I felt I was able to keep track of research for my thesis and easily restructure as I went along. My editor on the other hand was not so happy when I thought it was a good idea to use MS Word's built-in citation tool.. he made me pull them all out and add them back in manually. A good lesson to chat with your editor first before trying to be efficient.

Zotero's cross-platform plugins meant I could use any device for reading and not worry that if I followed important links I'd never find them again.