unified VS Umami

From TFA:

> My idea was that surely it's possible to write a bunch of markdown, and then have that get wrapped in a bunch of JSX tags that come pre-styled, using the styles of your existing repo? For example, what I expected was to be able to write *test* (Markdown for bold) and then get a component that looked liketest where is a library-defined React component

It surely is possible, so perhaps I can share some links if others are wondering the same thing.

If you like to roll your own solution for that, you can use the unified ecosystem: https://unifiedjs.com/

However, if you want JSX just do what everyone does and reach for MDX:

Styling the blog, figure out the eco-system within UnifiedJs, remark-rehype, oh boy, I could write another blog with that.

To build the Markdown editor (and the preview, mostly), I decided to use unified, an ecosystem of tools allowing the developer to parse a format into an abstract tree and back into another format (for example, markdown to html) and modify said tree (for example, to add specific classes to certain html elements before they are converted to an actual html string. The basics of how to do so can be found in this article, but they mostly consist of:

It’ll take you a few hours to become proficient in the “unified” syntax tree libraries. So worth it. Easy fully customized conversion to/from html, react, plain text, markdown, you name it. https://unifiedjs.com/

Why universal? Because a lot of languages are simillar in a bunch of ways and it might be good to reuse existing parts of the compiler to speed up the process of writing new DSLs for example. Also a pretty big use-case is not for compilers itself but just for transformers like Markdown to HTML, there are already a lot of libraries (like https://github.com/unifiedjs/unified for ASTs and https://tree-sitter.github.io/tree-sitter/ for parsing) that try achieve similar goals but they are not working together.

Unified is a framework to process Markdown. It's a plugin-based tool that allows you to inspect and modify the way Markdown is converted to other formats like HTML.

under the hood, the markdown is parsed by the unified remark and rehype processors, which in turn under the hood manipulate the markdown + HTML as an AST, which gives a lot of flexibility on parsing and rendering markdown. The editor uses them as plugins, which allows me to pick the features and inject them into the editor, one such injectable feature is the custom-made "copy from anywhere & paste as markdown" feature.

Having the flexibility to create custom React Components for markdown is essential and with react-markdown, we can achieve this in just a few lines of code. Boosting performance, increasing link security, and having overall increased capabilities for our markdown data are what we achieve here. Aside from the improvements within our application, this component is super easy to use and taps us into the unifiedjs (giving us superpowers!).

The Markdown processor used unified assets.

Are you tired of relying solely on Google Analytics to track your website's performance? Look no further! Introducing Umami , a powerful and privacy-focused alternative that puts you in control of your analytics data. Umami was founded by three brothers, Mike, Brian and Francis Cao as they were frustarted with using Google Analytics, which dominated and still does the industry of analytics despite of privacy concerns. As it is open-source, Umami quickly started being popular open-source project while still respecting privacy of users. My personal opinion, is that Umami is really easy to setup and use, for smaller projects as my personal website it is of great use. It does not many tracking as GA but it really does its job.

Link | Demo | Github | License

For a while now, I've been creating mini web tools to test out ideas or as tiny helpers for myself. I usually publish them on individual subdomains, which might not be the best idea, but I like the concept of a short, easy-to-remember URL. Recently, I discovered that some of these tools actually have a few users, which made me consider adding analytics to them. After a bit of research, I settled on umami. It's a great little privacy-conscious tool with exactly what I need and nothing more.

If you already use Posthog, Web Analytics has been in Public Beta for quite some time.[1]

If I remember correctly, CloudFlare Analytics does not need you to register your domain with them. I personally feel keeping domain registration coupled with your DNS provider is not a good idea.

Plausible[2] has an Open Source self-hostable version but is not so updated in sync with their SaaS version.

Umami[3] is another simple, clean one. And, of course, as many have suggested, Matomo is the other well-established one. If you want to avoid maintaining a hosting routine, a lot do the hosting out of the box these days. PikaPods[4] was good when I tried and played around for a while.

1. https://posthog.com/docs/web-analytics

2. https://github.com/plausible/analytics

3. https://umami.is

4. https://www.pikapods.com

not enough, can confirm, I moved to Umami for ChadNext

Think of metrics that will gather good insights for creating more things for the product later and track them using analytics services like umami or others.

Analytics is something that can easily become a privacy headache. To get around the issues as much as possible, the strategy I've implemented is to self-host the analytics tool Umami (again, via the One click app functionality in CapRover!).

This question is targeted to those who have experience with Umami. I’m wondering if it make sense with a specific configuration.

I've self-hosted Umami and works just fine. Check it out here: https://umami.is/