3 min read

Newsletter #13: We've Been Busy Building This Summer!

Newsletter #13: We've Been Busy Building This Summer!

Dear Logseqers,

We're back from our newsletter break! As the community was enjoying the summer and not sharing as many resources, we used the time to keep building. In this newsletter, we'll share some of the things we've been working on and what you can expect next from us.

This summer, we also ran two learning sprints to help you master Logseq queries. Go to the queries forum or scroll down towards the end of this newsletter to catch up with the curriculum.

Last but not least, we finish the newsletter with a roundup of new community plugins.

What workflows will you create with these new building blocks?

Get early access to Logseq Sync

Probably the most frustrating part of Logseq is syncing between different devices.

As avid mobile users ourselves, we often ran into sync conflicts when using services like iCloud and Dropbox. We heard the same from you, not to mention the privacy concerns of using such services. That's why we've been working on our own sync service, offering end to end encryption so don't have to trust anyone with the keys to your data (including us).

We've been testing Logseq Sync with a small group of testers and our Sponsors (those who donate more than $15 per month). Now that we've solved some important challenges, we're almost ready to make Sync available to our Backers as well (those who donate $5 per month). If you're a Backer (or become one now), expect an email with more information later this week.

We don't know yet when Sync will be generally available. But if you want to get early access and provide us with your invaluable feedback, please become a Backer or a Sponsor.

What has changed since 0.7.9.

When we sent the last newsletter, we were on version 0.7.9. of Logseq Beta. Over the past weeks, we've iterated quickly and are now up to 0.8.7. These are the most important changes in the past weeks:

  • Massive performance improvements for large graphs.
  • Improved linked references, including a search field for values.
  • (Page) properties are now clickable and create pages (thus offering more ways to search).
  • Added support for a global config file, which applies your configuration to all of your graphs.
  • Added support for Ctrl-f (Cmd-f on macOS) to find in a page. This feature works on every page in Logseq, including built-in keyboard shortcuts page.
  • Thanks to the community, Logseq is now available in the following languages: English, French, German, Dutch, Afrikaans, Norwegian, Polish, Italian, Spanish, Portuguese (Brazilian and European), Turkish, Russian, Chinese (Simplified and Traditional), Japanese, and Korean.

Take a deep dive into Logseq queries

The summer query sprints are a wrap! In July and August, over 250 of you decided to take the time and energy to better grok Logseq.

The August sprint was structured as a self-paced course, with a daily challenge to make the knowledge your own. In case you missed the lessons here's a full overview:

Once you have the theory down, challenge yourself some more by doing these build challenges:

New community plugins

Several new plugins landed in the Marketplace in the past weeks. Search for them in  ...  >  Plugins  >  Marketplace  within Logseq.

🔄 Logseq Random Block
Give yourself a jolt of inspiration with this random block plugin. Using tags and links, you can finely tune from what pool of blocks to pull.

📈 Logseq Echarts
If you use Apache Echarts (a JavaScript visualization library), you'll like this plugin. It allows you to write Echarts JSON directly in Logseq and have it render the charts.

📗 Logseq Dictionary
With this multi-language dictionary, learning languages with Logseq is a breeze.

🪧 Admonition Panels
Building your personal wiki just became much easier thanks to this admonitions plugin. It enables you to call attention to blocks using beautiful styling:

📄 Merge Nested Blocks
Do you use Logseq for long form writing? This plugin will come in handy, as it allows you to turn an entire branch of blocks into one single page-like block: