Dendron Weekly: 0.79 release, faster publishing builds, announcing our Dendrologists, and more!
It’s time for a weekly roundup! The email newsletter is a curated collection of weekly updates about Dendron and the Dendron community!
Dendron 0.79 has sprouted 🌱
Publishing got a lot faster for existing deployments. Builds are now 10x faster when publishing with cached dependencies.
We also made multi-vault easier to work with by default. When creating new notes, in multi-vault workspaces, confirmVaultOnCreate now defaults to true.
Breaking change: A fix in this release will disable date variable substitution, so current users will not be able to use it for the time being. We’re aiming to re-introduce next week - apologies for the churn!
Highlights
- enhance(publish): logo can reference a full URL path to external image (docs)
- enhance(lookup): add configuration for vault selection behavior with new
vaultSelectionModeOnCreateconfig option, and changeconfirmVaultOnCreatedefault totrue(docs) - enhance(publish): attempt to update Next.js template in-place
- enhance(publish): add lockfile to Next.js
Everything Else
- fix(server): highlighting breaks when there’s too much text
- fix(workspace): stop link candidate logic when disabled
- fix(commands): renamed command from
Goto NotetoGo to Note - fix(markdown): Exclude parenthesis from tags
- fix(publish): logo doesn’t respect
assetsPrefix - fix(workspace): cursor moves to top when opening file through the search
- fix(schema): Use string replace instead of lodash for date variable substitution (breaking change)
- fix(publish): some published pages will show error
Community
Announcing our Dendrologists
We’d love to introduce the Dendron community to our new Dendrologists! They’ll be focusing on growing and fostering the Dendron community by covering key focus areas such as contributor experience, coordinating community events, improving the docs, and maintaining community gardens.
Starboard and TIL Highlights
These are highlights from the Dendron Discord
#starboardand#today-i-learnedchannels.
- ⭐
viddo#9229shared a link to a Tweet about new VS Code insider features: The latest VS Code insiders adds completions for Markdown links, including: path/file links, header links, and reference links - ⭐
hrmck#7968learned how you can Add Dendron to application launchers on Linux desktops - ⭐
lukecarrier#2081showed how he used Gource to create a video of his Dendron Second Brain growing over time: “I figured it’d be interesting running Gource over my Dendron workspace to show its growth since I went all in with it around a year ago” - 💡
krisfremen#6757wondered if Dendron was hiring: the answer is yes! - 💡
moksha#0720learned about schemas and templates, and now uses them for interstitial journaling within Dendron - 💡
Jack of some quantity of trades#3247said: “TIL about the existence of cooklang, a markup language + cli tool + webserver setup for recipe/grocery management” - 💡
Jack of some quantity of trades#3247said: “TIL about the Final Version Perfected algorithm for exhaustively and efficiently prioritizing tasks on any itemized to-do list under most conditions”
Dendron Reading Series
This week’s entry in the Dendron Reading Series.
SQLite is one of the most widely used and versatile databases of all time. Perhaps its greatest strength is how easy it is to embed it in any sort of programming environment.
Over 100 separate source files are concatenated into a single large file of C-code named “sqlite3.c” and referred to as “the amalgamation”. The amalgamation contains everything an application needs to embed SQLite.
Takeaway: having everything in one blob is useful in many situations.
Developers sometimes experience trouble debugging the quarter-million line amalgamation source file… To circumvent this limitation, the amalgamation is also available in a split form, consisting of files “sqlite3-1.c”, “sqlite3-2.c”, and so forth, where each file is less than 32,768 lines in length
Takeaway: sometimes having everything in a multitude of blobs is more useful in other situations
This reminds me of two parallel concepts in Dendron
- the Amoeba: splitting information into smaller and smaller notes as needed
- the Katamari (credit to
@Jack of some quantity of trades#3247for helping seed the concept): combining information back into a single blob
There isn’t a best way of organizing, depending on the context, you might prefer information in one structure or another. The best way to structure information is context-dependent which is why it is so important for a PKM to give you the flexibility to restructure knowledge for your given context.
Office Hours and New User Tuesdays
- Office Hours: Visit the Office Hours page for notes from previous sessions.
- New User Tuesdays: Visit the New User Tuesdays page for notes from previous sessions.
Thank You’s
A big thanks to the following gardeners that brought up issues, contributions, and fixes to this release. Visit Discord Roles for more information.
- Vik
@constantpresent#2695 - Luke Carrier
@lukecarrier#2081 - Nicklas Gummesson
@viddo#9229 - Tsvetomir Bonev
- Adam Gluck
@glucinater21#0869 - Callum Mcdonald
@chmac#2931 - David Gomes
- Binly42
As Always: Community Resources
- Join the Dendron Discord
- Register for Dendron Events on Luma
- Follow Dendron on Twitter
- Checkout Dendron on GitHub
- Read the Dendron Blog