Welcome to Logseq and the community @prince! Sorry to hear your initial Logseq experience wasn’t good. I fully understand the frustration of data loss.
Logseq is still very much in beta, and some features are still in alpha. That’s no excuse, but Logseq isn’t labeled stable on purpose. Issues like data loss (common when using file-sync services like iCloud or Dropbox) are a big reason why Logseq’s architecture is being rewritten as we speak (see the announcement). Hopefully early next year Logseq will be a better choice for you.
And my two cents as a fellow PKM nerd: please don’t spend a week customizing a tool you’ve only just started using.
Having wasted hundreds of hours on tinkering with tools I never ended up using, I always recommend people first use a tool as-is for 1 to 3 months. Only once you know whether you’re going to stick with a tool is it worth spending hours tinkering and customizing it.
Just my opinion of course, but I’ve been in your situation too many times and had the same issue when I just started out with Logseq. But the funny thing after three years of using this tool fulltime is that I barely use any plugins and have zero CSS tweaks in my graphs. Most of the customizations ended up being distractions anyway, not helping me be any more productive than just using vanilla Logseq.
In any case, thank you for your feedback and I’ll make sure the dev team sees it as well.