Video summary

Лучшие плагины для Obsidian и правильная структура базы за 2 года работы

Main summary

Key takeaways

Educational

Main ideas / lessons conveyed

  • The speaker argues that moving from paid tools (e.g., Notion/Code) to free Obsidian can be smooth and productive if you:
    • use a small set of useful plugins,
    • understand workflow/structure (not just how to “create notes”),
    • apply a few “advanced” features to reduce daily friction.
  • The focus is on building an “algorithm” for working with notes:
    • make daily planning work inside Obsidian (calendar/daily notes),
    • keep note creation organized (folders, limited bookmarks),
    • design a structure so notes connect into a graph (landing pages).
  • The speaker emphasizes that you don’t need a huge plugin ecosystem.
    • Criticism like “you can’t work in Obsidian without X/Y plugins” is rejected.
    • Instead, choose plugins that solve your concrete problems.

Methodology / workflow described

1) Set up an Obsidian calendar using Daily Notes + a third-party calendar plugin

  • Install/enable a calendar-related third-party plugin (exact name unclear in subtitles).
  • In Obsidian:
    • Enable Daily Notes (built-in feature; may be disabled by default).
    • In settings, enable Daily Note opens on Obsidian startup.
    • Specify a folder where daily notes will be saved.
  • Example “algorithm” behavior:
    • Create a note for “the day after tomorrow.”
    • When you restart Obsidian, it shows what’s scheduled “for today.”
    • If today has no note yet, you see the next relevant daily page (e.g., when “the day after tomorrow” arrives, it becomes the daily page shown).

2) Use a small number of bookmarks to force structure

  • Create bookmarks only for what you truly need.
  • Limit bookmarks (example given: “around ten”).
  • Keep:
    • a couple of global bookmarks, plus
    • a few bookmarks inside a couple of folders
    • (example constraint: “three or four bookmarks maximum” per folder)
  • Expected effect:
    • the limitation encourages intentional structure, eventually leading to landing pages.

3) Keep an “emergency notebook” for quick capture

  • Maintain a separate notebook to jot down information immediately.
  • Why:
    • otherwise you may write things down somewhere, forget where, and lose the information after a couple of days.
  • Later workflow:
    • sort what you captured,
    • keep what matters,
    • file it into Obsidian.
  • Example content mentioned:
    • notes about selecting “prompts for Stable Diffusion”.

4) Organize notes via folders and “landing pages” connected by links

  • Prefer organizing notes into folders (example shown: “Personal” and “Work”).
  • When notes don’t fit an existing category:
    • create a new note in the correct folder.
  • Core structural principle:
    • don’t scatter notes without connections.
    • the “database” should form a graph where ideally “everything is connected.”
  • Landing pages:
    • reached/maintained via hyperlinks between notes (compared to a “matryoshka doll” / nested structure).

5) Keep the system minimal: two databases + navigation support

  • After structuring, the speaker’s content fits into two main databases:
    • Personal
    • Work
  • They also mention using built-in search to locate missing info, but structure is what saves time long-term.

Plugin instructions & described capabilities

Installing plugins in Obsidian (general method)

  • Go to the third-party plugins overview
  • Find Install
  • Then connect/enable the plugin

Plugin: Telegram → Obsidian feed via Bot (main “advanced” one)

Purpose: forward messages from Telegram into Obsidian notes.

Setup steps described

  • Install/enable the Telegram-forwarding Obsidian plugin.
  • In plugin settings:
    • specify a Telegram bot and an identifier (nickname/ID).
  • To create/configure the bot (in Telegram):
    • create a bot via the bot management flow (subtitles mention “blue checkmark” and bot account name).
    • provide:
      • bot name
      • bot username (the “@…” style identifier)
  • Then in plugin settings:
    • enter the nickname or User ID if nickname doesn’t work
    • Telegram should confirm/notify about the user identifier.
  • The plugin may require retries (speaker mentions deleting/restarting and attempting again).

Forwarding rules / output behavior

  • Create a Telegram folder inside Obsidian for incoming notes.
  • Configure the bot so each message becomes a note:
    • note name includes the first ~30 characters of the message
    • plus date/time (creation time implied)
  • Optional mode:
    • route message content into a single “Feed” note rather than creating many notes:
      • create a note (e.g., “Telegram Feed”)
      • set the plugin to append messages there.

Templates to format note content

  • Issue observed:
    • feed items arrived without a date
  • Fix described:
    • create/use a template (referenced as coming from the developers’ site commands list)
    • include date formatting like year / month / day
    • optionally remove “content preview” if undesired (the template included “content preview in 300 pixels”).
  • Paths referenced:
    • “template path” and a folder named tele templates.

Reduce clutter in Telegram

  • In plugin advanced settings:
    • enable a checkbox to delete the Telegram message after sending it to Obsidian.

Implied daily-use plugin list

  • “Notepad” (quick capture; possibly a workflow plugin)
  • a landing pages system (2–3 max)
  • a calendar setup
  • Telegram syn/feed as automation

Plugin: Tables (ADV)

  • Used for working with tables in Obsidian.
  • Speaker notes:
    • Obsidian “complex tables” can be awkward.
    • Excel-style plugins exist, but the speaker prefers Google Sheets for complex spreadsheet work.
  • Plugin name: ADV (as stated in subtitles).
  • Mentions settings/convenience, but details are limited.

Plugin: Backlinks at the bottom of the page

  • Capability:
    • show backlinks (pages linking to the current page) near the bottom.
  • Motivation:
    • built-in backlinks exist, but the tab is often closed; this avoids extra navigation.

Plugin: Insert link title from an external URL

  • Capability:
    • paste a URL and automatically fetch:
      • the article title
      • the resource name
  • Plugin name appears as: A Link title

Plugin: Toolbar customization (“Conder”)

  • Capability:
    • customize the toolbar layout.
  • Example:
    • move a page-separation button to a preferred position.
  • Speaker says they didn’t over-tune it, but it can help.

Plugin: Design elements / widgets (visual enhancement)

  • Speaker values this plugin for:
    • breaking monotony of plain text
    • adding widgets/design elements (improves visual usability)
  • Exact plugin name isn’t clearly stated in subtitles; it’s referenced as a design-related plugin.

Main takeaways / conclusion points

  • Advanced productivity in Obsidian comes from:
    • a consistent capture + structuring workflow
    • a small, intentional plugin set
  • The speaker’s “must-have” concept isn’t “X/Y plugin is mandatory” but:
    • use tools that solve your specific problems
  • Synchronization across devices is mentioned as an important separate topic, using cloud folder sync.

Sources / speakers featured (as stated or implied)

Speaker / channel

  • “The Aunts channel” (speaker presenting the video content)

Named examples inside the content

  • Vova Lomov (example folder/person name)
  • Jeff the demon (example Telegram message)

Original video