Appearance
Comprehensive Strategic Analysis of the Developer Knowledge Base Ecosystem: 2026 Technical Report
1. Application Overview
The landscape of personal and team knowledge management for developers has crystallized into a diverse ecosystem of tools that prioritize data sovereignty, interconnectedness, and technical extensibility. This analysis evaluates seven critical platforms: Obsidian, Logseq, SiYuan, Joplin, Trilium, mdBook, and Outline.
Obsidian
Obsidian is a private, local-first knowledge base that operates on a vault-based architecture, utilizing a directory of plain text Markdown files as its foundational data layer.1 The application is built on the principle that the human brain is non-linear, facilitating the creation of a "second brain" through a web of linked ideas.3
How it works: Obsidian functions as an integrated development environment for thought. It does not ingest files into a proprietary database; instead, it provides a high-performance interface on top of existing local folders.1 This architecture allows users to use standard file management tools, version control (such as Git), and external text editors alongside the application without causing data corruption. Formatting is achieved through standard Markdown, with the application offering a "Live Preview" mode that renders Markdown in real-time while maintaining editability.1
Business model: Obsidian employs a "Free for Personal Use" model, which allows individual users to access the full application without limits.2 Revenue is generated through three primary channels: first, premium add-on services such as Obsidian Sync, which provides end-to-end encrypted file synchronization with one year of version history, and Obsidian Publish, a web hosting service for digital gardens.1 Second, a Catalyst license provides early access to beta versions for a one-time fee.4 Third, a commercial license is required for organizations with two or more employees using Obsidian for work-related purposes.1
Logseq
Logseq is an open-source, privacy-first outliner that manages networked thoughts using a block-based architecture.3 Originally designed to work on top of local Markdown and Org-mode files, the platform is currently undergoing a significant architectural transition toward a database-backed system.6
How it works: Logseq interprets text files as a series of atomic blocks. Each bullet point or paragraph is treated as a unique entity with its own ID, allowing for granular referencing and transclusion.5 The "Logseq OG" version relies on the DataScript in-memory database, which is rebuilt from Markdown files every time the application starts.7 The newer "Logseq DB" version utilizes an SQLite backend to provide superior performance, more reliable synchronization, and advanced data views like Gallery and Kanban.6
Business model: As a community-driven open-source project, the core application is free. Monetization strategies are focused on future cloud-based synchronization and collaboration services, while maintaining the "local-first" ethos.7
SiYuan
SiYuan is a local-first, block-based personal knowledge management system that blends the flexibility of Notion with the privacy of self-hosted software.10
How it works: The application uses a completely decentralized mesh structure for its knowledge base, referred to as a "Graph".5 SiYuan treats every element (paragraph, image, math formula) as a block.11 It provides a full Markdown experience but backs the data with a local database to enable high-speed queries and complex metadata management.11 It is cross-platform, supporting desktop, mobile, and browser-based access through self-hosting via Docker.11
Business model: SiYuan utilizes a tiered payment structure. The basic functions are free for lifetime use.13 A "PRO Features" tier ($64 lifetime) enables third-party S3 or WebDAV synchronization and backups.13 An "Annual Subscription" ($148 lifetime) includes official cloud assets hosting with 8GB of space and official data synchronization.13
Joplin
Joplin is an open-source, notebook-based note-taking and to-do application designed for secure cross-device accessibility.3
How it works: Joplin follows a traditional notebook and sub-notebook hierarchy.3 Notes are stored as Markdown files but are managed through a centralized internal database. One of Joplin's primary selling points is its robust End-To-End Encryption (E2EE), which uses a Master Key generated by the user to ensure that data remains unreadable by third parties, including service providers.15
Business model: The core software is free. Revenue is generated through "Joplin Cloud," which offers three tiers: Basic (€2.40/month), Pro (€4.79/month), and Teams (€6.69/user/month).15 These tiers provide varying levels of storage (2GB to 50GB), note publishing capabilities, and collaboration features.15
Trilium (and TriliumNext)
Trilium is a hierarchical note-taking application designed for building large-scale personal knowledge bases, characterized by its extreme scriptability and database-driven performance.16
How it works: All notes are stored in a local SQLite database, allowing the application to scale beyond 100,000 notes with high efficiency.16 Unlike file-based tools, Trilium allows a single note to be "cloned" into multiple locations within its tree hierarchy without duplicating data.16 It provides a rich WYSIWYG editor and supports specialized note types like "Code notes," "Relation maps," and "Canvas".16 Following the original creator's move to maintenance mode in 2024, the community fork "TriliumNext" has become the primary driver of development, introducing features like Preact/JSX support for custom widgets and improved internationalization.19
Business model: Trilium is entirely free and open-source, supported by community contributions and forks.16
mdBook
mdBook is a specialized command-line tool designed for technical authors to create professional, navigable documentation from Markdown files.21
How it works: Written in Rust, mdBook functions as a static site generator. It processes a directory of Markdown files and generates a web-based book with integrated search, syntax highlighting, and customizable themes.21 It features a modular architecture with "Preprocessors" that can modify content before rendering and "Backends" that can output to HTML, PDF, or other formats.21
Business model: The software is free and open-source under the Mozilla Public License v2.0.21
Outline
Outline is a collaborative team wiki and knowledge base designed to consolidate fragmented team information into a high-speed, centralized platform.23
How it works: Outline is a modern SaaS platform (with a self-hostable open-source option) that emphasizes real-time collaboration and deep integration with the Slack ecosystem.23 It uses an RPC-style API and supports instant search and AI-generated answers based on the team's documentation.23
Business model: Outline uses a tiered pricing model based on team size for its cloud-hosted service: $10/month for 1–10 members, $79/month for up to 100 members, and $249/month for up to 200 members.23 Non-profits and educational institutions receive a 30% discount.23
2. Target Market & Users
The target market for these knowledge base systems is primarily composed of high-information professionals who require reliable external memory systems to manage technical complexity.
Primary Audience: The Technical Solo Practitioner
This segment includes software engineers, data scientists, researchers, and technical writers. These users are often motivated by the "Second Brain" or "Zettelkasten" methodologies, seeking a tool that can grow with them over decades.
- User Context: A developer using Obsidian might use it to document code snippets, debug logs, and architectural decisions, utilizing the Graph View to find connections between different project modules.1 A researcher using Logseq might rely on its PDF annotation feature to link source material directly into a daily research journal.8
- Motivators: Data longevity, privacy, and the ability to customize the workspace through community-developed plugins.1
Secondary Audience: Engineering Teams and Project Managers
Teams require tools that facilitate collaborative documentation and shared situational awareness.
- User Context: An engineering team at a startup might use Outline as their central wiki, integrating it with Slack so that documentation is searchable from their primary communication channel.23 A project maintainer for an open-source Rust library would use mdBook to generate the library's official API documentation, ensuring it is searchable and visually consistent with the Rust ecosystem.21
- Motivators: Real-time collaboration, ease of deployment, and high-speed retrieval of team knowledge to reduce redundant questions in chat.23
| Application | Primary User Persona | Key Context of Use |
|---|---|---|
| Obsidian | The "Digital Gardener" | Long-term knowledge synthesis; personal project management. |
| Logseq | The "Fluid Thinker" | Rapid capture of atomic thoughts; daily journaling; research. |
| SiYuan | The "Privacy-Conscious Notion User" | Structured data management with local-first security. |
| Joplin | The "Pragmatic Mobile Professional" | Cross-platform note access with high-security requirements. |
| Trilium | The "Knowledge Engineer" | Managing massive datasets (>50k notes) with custom automation. |
| mdBook | The "Technical Documentation Lead" | Publishing high-quality, searchable manuals for codebases. |
| Outline | The "Agile Engineering Team" | Centralized wiki for fast-moving collaborative environments. |
3. Problem & Value Proposition
The Problem: The "Mess of Docs" and Data Decay
Developers in 2026 face unprecedented information density. The primary pain points include:
- Information Fragmentation: Critical project insights are often buried in Slack threads, email chains, and disjointed Markdown files.25
- Vendor Lock-in and Data Fragility: Many cloud-based tools use proprietary formats, making it difficult to exit the ecosystem if the service shuts down or changes its pricing.2
- Cognitive Overload: Traditional hierarchical structures (folders) fail to represent the networked nature of software engineering, where one concept (e.g., a specific database optimization) applies to multiple projects.3
Value Propositions
- Longevity through Plain Text (Obsidian, Logseq OG): By storing notes in standard Markdown files on the user's local disk, these tools promise that the user's data will remain readable for decades, independent of the software's survival.1
- Networked Thought and Emergent Structure (Logseq, Obsidian): These platforms allow users to build a personal "Wikipedia" where structure emerges from internal links and graph visualizations rather than pre-defined folders.1
- Scriptability and Automation (Trilium, Obsidian): For developers, the ability to write custom JavaScript to automate note organization or query data via plugins like Dataview transforms a note app into a programmable environment.18
- Security and Privacy (Joplin, SiYuan): End-to-end encryption and local-first storage provide peace of mind for professionals handling sensitive client data or proprietary code documentation.12
- High-Speed Collaborative Truth (Outline): For teams, the value lies in a tool that is faster than Notion and more integrated than a basic wiki, serving as a real-time source of truth that reduces cognitive friction.18
4. Feature Inventory
The following inventory details the critical features of these applications, their mechanics, and the specific problems they solve.
Obsidian: Extensibility and Visualization
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Graph View | Relationship visualization. | Generates a dynamic node-and-edge map from ]. Nodes are files, edges are links.1 | Hidden patterns; non-linear discovery.1 |
| Canvas | Spatial brainstorming. | Infinite 2D grid where notes, images, and web pages are cards connected by arrows.1 | Linear writing limits; visual planning needs.2 |
| Dataview (Plugin) | Dynamic querying. | Uses a SQL-like language to generate tables/lists from note metadata (YAML frontmatter).2 | Data fragmentation; manual index maintenance.2 |
| Web Clipper | Content capture. | Browser extension that saves web pages directly to the vault as Markdown.2 | Information hoarding; source tracking.2 |
| Obsidian Sync | Encrypted synchronization. | E2EE sync between devices with one-year version history.1 | Cross-platform access; data loss anxiety.2 |
Strengths: Unrivaled plugin ecosystem (1,000+); extremely stable.24 Weaknesses: High configuration overhead; non-open source.27 Improvements: Native block-based editing features would reduce reliance on complex plugins.
Logseq: The Atomic Outliner
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Block Referencing | Atomic content reuse. | Each bullet is an object; can be embedded or referenced in other pages via ((UUID)).5 | Redundant typing; information duplication.5 |
| PDF Annotation | Integrated research. | Highlights in PDFs create blocks linked back to the source document.8 | Disconnected notes and sources.24 |
| Daily Journal | Low-friction capture. | Default landing page is today's date, encouraging chronological logging.24 | Blank page syndrome; time-tracking.24 |
| Advanced Query | Structural retrieval. | Datalog-based queries to find blocks with specific properties or tags.8 | Manual search; complex metadata retrieval.32 |
| Flashcards (SRS) | Long-term retention. | Uses #card tag and a built-in algorithm for spaced repetition.8 | Forgetting technical concepts.24 |
Strengths: Natural "thinking" flow; powerful block granularity.5 Weaknesses: Historically unstable sync; steep learning curve for advanced queries.31 Improvements: Transitioning to SQLite DB version is expected to solve indexing and sync reliability.7
SiYuan: Block-Level Data Integrity
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Database Views | Structured data display. | Kanban, Gallery, and Table views of block-level data.6 | Flat list limitations.6 |
| Self-Hosting (Docker) | Absolute data control. | Can be deployed as a web-accessible container on private infrastructure.11 | Dependency on third-party clouds.11 |
| S3/WebDAV Sync | Flexible backup. | Integrates with third-party storage like Amazon S3 or Azure.13 | High cost of proprietary cloud storage.13 |
Strengths: Rich feature set out-of-the-box (like Notion but local); high-speed editing.11 Weaknesses: Complex pricing model; fewer community plugins compared to Obsidian.13
Joplin: Secure Synchronization
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| E2EE (End-to-End) | Privacy assurance. | Data is encrypted on-device before being sent to the sync target.15 | Surveillance and data tampering.15 |
| Email to Note | External capture. | Forwards emails to a custom address to create notes in Joplin Cloud.15 | Disparate information channels.15 |
| Multi-Resource Support | Multimedia handling. | Native support for PDF, images, video, and audio within notes.15 | Text-only limitations.15 |
Strengths: Reliable cross-platform sync; strong encryption.15 Weaknesses: Clunky UI; obfuscated file naming in local storage.30
Trilium / TriliumNext: The Programmable Note Tree
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Note Cloning | Relational flexibility. | A single note (atom) can have multiple parents in the tree.16 | Hierarchical rigidity.18 |
| Promoted Attributes | Custom metadata UI. | Surfaces specific labels as fields in a dedicated sidebar.16 | Unstructured metadata.29 |
| Scripting API | Endless customization. | Full Node.js/JavaScript API to interact with the note database.17 | "Out-of-the-box" limitations.18 |
| Relation Maps | Visualizing relations. | Auto-generated diagrams of note connections and link maps.16 | Cognitive load in complex systems.16 |
Strengths: Scales to 100k+ notes; high-performance local SQLite.16 Weaknesses: Steep learning curve; no official mobile app (relies on web frontend/unofficial forks).16
mdBook: Technical Presentation
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Integrated Search | Navigation support. | Built-in full-text search for generated documentation.21 | Information retrieval in long manuals.21 |
| Rust Playpen | Interactive code. | Code blocks can be made editable and runnable in the browser.21 | Static, non-verifiable code samples.21 |
| Preprocessors | Content modification. | Custom scripts modify Markdown (via JSON) before rendering.21 | Standard Markdown formatting limits.21 |
Strengths: Extremely fast; professional output; specialized for Rust.21 Weaknesses: Minimalistic; not intended for general-purpose note-taking.38
Outline: Collaborative Velocity
| Feature Name | Function | Mechanics | Problem Solved |
|---|---|---|---|
| Slack Integration | Contextual search. | Search and share documentation directly within Slack chat.23 | "App-switching" friction.23 |
| Real-time Editing | Multiplayer collab. | Simultaneous document editing with comments and @mentions.23 | Version conflicts in teams.23 |
| Custom Domains | Branding control. | Host the wiki at docs.yourcompany.com with white-labeling.23 | Fragmented internal brand.23 |
Strengths: High-speed UI; deep team integration.18 Weaknesses: Less suitable for deep personal knowledge synthesis.18
5. Feature Relationship Map
The developer knowledge base ecosystem is characterized by complex interdependencies between the storage layer, the interface, and the extensibility model.
Storage and Retrieval Dependencies
There is a fundamental trade-off between Markdown file parity and Database performance.
- Obsidian and Logseq OG prioritize the Markdown file. The relationship is a "File -> Index" model. If the file is modified externally, the index updates. This enhances portability but can lead to sync conflicts if the indexer misses a change.1
- Logseq DB, SiYuan, and Trilium prioritize the Database. The relationship is "Database -> UI." Markdown is treated as a "view" or an "export format".7 This enhances performance and enables block-level properties but complicates external tool integration.7
Core User Loops
- The Obsidian Loop: Capture -> Internal Link -> Graph View Discovery -> Knowledge Synthesis. This loop is enhanced by the Plugin Ecosystem, where a user might use Templater to standardize capture and Dataview to automate synthesis.1
- The Logseq Loop: Daily Journal -> Block Tagging -> Query Aggregation -> Project Development. The core loop here is time-centric, where information is "resurfaced" based on tags rather than manually sorted into folders.24
- The Trilium Loop: Note Creation -> Attribute Assignment -> Scripted Automation -> Relational Visualization. This loop treats notes as data objects in a relational system.18
Feature Gaps and Enhancements
- Sync vs. Privacy: Joplin solves the gap of secure sync through E2EE, but at the cost of UI elegance.15
- Personal vs. Public: mdBook bridges the gap between private notes and public documentation, but requires a command-line workflow that is too high-friction for daily notes.21
- Solo vs. Team: Outline fills the gap left by personal tools like Obsidian and Logseq, which lack robust multi-user permission management.18
6. User Sentiment Analysis
What Users Love
- Obsidian: The "Local-First" philosophy is the primary driver of loyalty. Users feel a sense of security knowing their data is in .md files.2 The "Live Preview" editor is highly rated for its balance of Markdown utility and visual polish.30
- Logseq: Users who prefer outliners find it superior to Obsidian for "frictionless" thought capture.31 The "click to zoom" functionality on nodes is a specifically beloved feature.42
- Trilium: Power users love the "cloning" concept and the fact that they can write their own widgets using JavaScript.18
- mdBook: Developers appreciate its speed and how it "just works" for API documentation, especially within the Rust ecosystem.21
Common Gripes and Churn Reasons
- Logseq Data Integrity: Concerns about data loss and sync errors are the most cited reasons for leaving Logseq for Obsidian.30
- Joplin UI: The "clunky" and "dated" interface often leads users to explore Obsidian or SiYuan once they become comfortable with Markdown.30
- Obsidian Mobile/Sync Cost: While the desktop app is free, some users find the $4–$10 monthly cost of official sync to be a deterrent, though many work around this with Syncthing or iCloud.24
- Trilium Mobile Absence: The lack of a native mobile app is a significant barrier for users who need to capture notes on-the-go.16
Requests and Future Expectations
- AI Integration: There is a high demand for AI-powered "chat with your notes" features, but users want this implemented in a privacy-preserving way.26
- Improved Sync: Across all local-first tools, users are looking for "magic" sync that just works without manual re-indexing or conflict resolution.9
7. Competitive Landscape
Market Positioning Matrix
| Application | Philosophy | Collaboration | Technicality | Key Advantage |
|---|---|---|---|---|
| Obsidian | Local-First | Low | Medium-High | Massive Plugin Ecosystem.1 |
| Logseq | Block-Outliner | Low | High | Fluid atomic thinking.3 |
| SiYuan | Notion-Alternative | Medium | Medium-High | Local structured data.10 |
| Joplin | Traditional Notebook | Medium | Medium | Industry-standard E2EE.3 |
| Trilium | Programmable DB | Medium | Very High | Limitless scriptability.16 |
| mdBook | Public Doc Tool | Low | High | Speed and navigation.21 |
| Outline | Team Wiki | Very High | Low-Medium | Collaborative velocity.23 |
Feature Comparison across Platforms
| Feature | Obsidian | Logseq | SiYuan | Joplin | Trilium | mdBook | Outline |
|---|---|---|---|---|---|---|---|
| Markdown Native | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Block-Based | No* | Yes | Yes | No | No | No | No |
| Graph View | Yes | Yes | Yes | No* | Yes | No | No |
| Mobile App | Yes | Yes | Yes | Yes | No | No | No |
| Self-Hostable | No | No | Yes | Yes | Yes | N/A | Yes |
| Open Source | No | Yes | Yes | Yes | Yes | Yes | Yes |
| E2EE | Yes | No | Yes | Yes | No | N/A | No |
*Obsidian has block-ID support but is not "block-first." Joplin has a community plugin for a knowledge graph.
Competitive Advantages and Gaps
- Obsidian's Moat: The sheer volume of community plugins makes it difficult for any new competitor to achieve feature parity for power users.28
- Logseq's Advantage: For users who think in hierarchies and bullets, Logseq provides a level of friction-free entry that Obsidian cannot match without heavy customization.31
- Outline's Market Gap: While personal tools are evolving, there is still a massive gap for a tool that offers Obsidian-level personal features with Confluence-level team administration.18
8. Ideal User Experience & Feature Roadmap
The current landscape suggests that the "ideal" developer knowledge base is one that combines the permanence of plain text with the power of a relational database.
The "Unified Knowledge Base" Vision
An ideal platform would provide a Hybrid Storage Layer—using a high-performance database (like SQLite) for the application's active state while maintaining a real-time, bidirectional mirror in a human-readable folder of Markdown files.7
Priority Recommendations for Future Development
- Privacy-First AI RAG (Retrieval-Augmented Generation):
- User Want: "Ask my notes questions" without sending data to a central server.26
- Solution: Integrate local LLM support (e.g., via Ollama) to index the vault/graph locally and provide natural language search and summarization.27
- Elevation: Move from generative AI (writing for you) to assistive AI (finding for you).25
- CRDT-Based Synchronization:
- User Want: Real-time collaboration in local-first apps without sync conflicts.9
- Solution: Implement Conflict-free Replicated Data Types (CRDTs) to allow decentralized peer-to-peer sync between devices.9
- Elevation: This would enable "Obsidian for Teams" without needing a central cloud server.9
- Semantic Search and Unified Metadata:
- User Want: Finding content across different types (code, images, text) through a single search.25
- Solution: Use vector embeddings for all notes to enable "Semantic Search," where a query for "Database Performance" returns notes about "SQL Optimization" and "Indexing" even if the exact keywords are missing.25
- Universal Web Clipper with "Self-Correction":
- User Want: Capturing web content that doesn't break over time as websites change.2
- Solution: An AI-augmented clipper that doesn't just "scrape" but "interprets" the page structure to save clean, meaningful Markdown with all metadata automatically extracted.2
Feature Roadmap: Priority Recommendations
| Priority | Feature | Problem Solved | Data Source Reference |
|---|---|---|---|
| High | SQLite Engine Transition | Indexing speed and sync reliability in large graphs. | 7 |
| High | Local AI / RAG | Information retrieval fatigue in large knowledge bases. | 26 |
| Medium | Native Canvas/Whiteboard | Visual thinking beyond linear text constraints. | 1 |
| Medium | Multi-User CRDT Sync | Friction in team collaboration for local-first apps. | 9 |
| Low | Mobile Responsive Themes | UX friction on non-desktop platforms. | 41 |
The developer knowledge base space in 2026 is moving toward "Programmable Knowledge." The tools that succeed will be those that allow developers to not just store text, but to treat their accumulated knowledge as a living, queryable database that enhances their primary workflows.18 The transition of major players like Logseq to database-backed architectures confirms this trend.6 As information continues to sprawl, the value of a high-performance "Second Brain" becomes the defining competitive advantage for the modern engineer.
Works cited
- Obsidian (software) - Wikipedia, accessed February 9, 2026, https://en.wikipedia.org/wiki/Obsidian_(software)
- Obsidian - Sharpen your thinking, accessed February 9, 2026, https://obsidian.md/
- Joplin vs. Logseq vs. Obsidian Comparison - SourceForge, accessed February 9, 2026, https://sourceforge.net/software/compare/Joplin-vs-Logseq-vs-Obsidian/
- Obsidian Help: Home, accessed February 9, 2026, https://help.obsidian.md/Home
- Understanding Core Concepts of Logseq: The Structure of Knowledge Base, Pages, and Blocks - Oreate AI Blog, accessed February 9, 2026, https://www.oreateai.com/blog/understanding-core-concepts-of-logseq-the-structure-of-knowledge-base-pages-and-blocks/54d224272028b08e10e38a6e0262bc9f
- Logseq OG (markdown) vs Logseq (DB:sqlite) - FAQ - Logseq, accessed February 9, 2026, https://discuss.logseq.com/t/logseq-og-markdown-vs-logseq-db-sqlite/34608
- Logseq OG (markdown) vs Logseq (DB:sqlite) - Reddit, accessed February 9, 2026, https://www.reddit.com/r/logseq/comments/1pz6mdf/logseq_og_markdown_vs_logseq_dbsqlite/
- db-version-changes.md - logseq/docs - GitHub, accessed February 9, 2026, https://github.com/logseq/docs/blob/master/db-version-changes.md
- Seflhosted Logseq DB synching - Questions & Help, accessed February 9, 2026, https://discuss.logseq.com/t/seflhosted-logseq-db-synching/34537
- What do you think of Logseq or SiYuan? Logseq[1] is also markdown based but also... | Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=44950494
- Deploy Siyuan (Open-Source Notetaking & Knowledgebase Platform) - Railway, accessed February 9, 2026, https://railway.com/deploy/siyuan
- Why Choose SiYuan Note: A Local-First Knowledge Management Solution - Oreate AI Blog, accessed February 9, 2026, https://www.oreateai.com/blog/why-choose-siyuan-note-a-localfirst-knowledge-management-solution/d255a34b3f8472b2328a6d95618b469e
- Pricing - SiYuan - Privacy-first personal knowledge management system that supports Markdown, block-level ref, and bidirectional links, accessed February 9, 2026, https://b3log.org/siyuan/en/pricing.html
- This minimal note-taking app was the missing piece I didn't know my setup needed, accessed February 9, 2026, https://www.makeuseof.com/siyuan-notes-app-on-pc/
- Joplin, accessed February 9, 2026, https://joplinapp.org/
- Trilium Notes, accessed February 9, 2026, https://triliumnotes.org/
- Build your personal knowledge base with Trilium Notes - GitHub, accessed February 9, 2026, https://github.com/TriliumNext/Trilium
- I finally replaced Notion with a self-hosted knowledge base built on Trilium Next - XDA Developers, accessed February 9, 2026, https://www.xda-developers.com/trilium-next-notion-alternative/
- How TriliumNext Revitalized an Abandoned Open Source Project with Dosu's Help, accessed February 9, 2026, https://dosu.dev/blog/how-triliumnext-revitalized-an-abandoned-open-source-project-with-dosus-help?ref=selfh.st
- Releases · TriliumNext/Trilium - GitHub, accessed February 9, 2026, https://github.com/TriliumNext/Trilium/releases
- Introduction - mdBook Documentation, accessed February 9, 2026, https://rust-lang.github.io/mdBook/
- For developers - mdBook Documentation, accessed February 9, 2026, https://rust-lang.github.io/mdBook/for_developers/index.html
- Outline – Team knowledge base & wiki, accessed February 9, 2026, https://www.getoutline.com/
- Choosing between Logseq and Obsidian | by Mark McElroy - Medium, accessed February 9, 2026, https://medium.com/@markmcelroydotcom/choosing-between-logseq-and-obsidian-1fe22c61f742
- 5+ Knowledge Base Challenges You Should Look Out for in 2026 [With Solutions], accessed February 9, 2026, https://betterdocs.co/knowledge-base-challenges-you-should-look-out/
- AI knowledge base: A complete guide for 2026 - Zendesk, accessed February 9, 2026, https://www.zendesk.com/service/help-center/ai-knowledge-base/
- Obsidian, Trilium or Freeplane as the ultimate note-taking and organization of knowledge app (with LaTeX integration) ? : r/linux - Reddit, accessed February 9, 2026, https://www.reddit.com/r/linux/comments/199xsfx/obsidian_trilium_or_freeplane_as_the_ultimate/
- What is Obsidian's best competitor and why? : r/ObsidianMD - Reddit, accessed February 9, 2026, https://www.reddit.com/r/ObsidianMD/comments/1msflr7/what_is_obsidians_best_competitor_and_why/
- Debating moving from Obsidian - Trilium - Reddit, accessed February 9, 2026, https://www.reddit.com/r/Trilium/comments/1o26guk/debating_moving_from_obsidian/
- How did you choose between Joplin, Foam, Trilium, Obsidian, Logseq, Roam?, accessed February 9, 2026, https://news.ycombinator.com/item?id=33069621
- I loved Obsidian to death, but felt a bit of friction. As nice as it was, I wasn... | Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=33195631
- Unlocking the Power of Structure in Logseq's Markdown Version (with a Focus on Export), accessed February 9, 2026, https://discuss.logseq.com/t/unlocking-the-power-of-structure-in-logseqs-markdown-version-with-a-focus-on-export/31603
- What do you prefer Obsidian over Logseq for? - Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=33190786
- SiYuan - App Store - Apple, accessed February 9, 2026, https://apps.apple.com/us/app/siyuan/id1583226508
- Obsidian vs. Joplin: Which note-taking app fuels your productivity? : r/joplinapp - Reddit, accessed February 9, 2026, https://www.reddit.com/r/joplinapp/comments/1fi2j31/obsidian_vs_joplin_which_notetaking_app_fuels/
- Pre-Pre-RFC: Moving Rust By Example to mdBook, into rust-lang.org - documentation, accessed February 9, 2026, https://internals.rust-lang.org/t/pre-pre-rfc-moving-rust-by-example-to-mdbook-into-rust-lang-org/5319
- Plugins case study: mdBook preprocessors - Eli Bendersky's website, accessed February 9, 2026, https://eli.thegreenplace.net/2025/plugins-case-study-mdbook-preprocessors/
- Plugins case study: mdBook preprocessors - Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=46311993
- MdBook – A command line tool to create books with Markdown | Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=36528984
- How does the 'current' DB version of Logseq compare to MD version? When it comes to plugins etc - Reddit, accessed February 9, 2026, https://www.reddit.com/r/logseq/comments/1oakhpt/how_does_the_current_db_version_of_logseq_compare/
- I went deep into to the PKMS rabbit hole a year and a half ago, benchmarked Obsi... | Hacker News, accessed February 9, 2026, https://news.ycombinator.com/item?id=44023808
- This chart shows what makes Logseq unique - General, accessed February 9, 2026, https://discuss.logseq.com/t/this-chart-shows-what-makes-logseq-unique/30547
- 7 Tech Stack Pitfalls to Avoid in 2026 - Information Week, accessed February 9, 2026, https://www.informationweek.com/software-services/7-tech-stack-pitfalls-to-avoid-in-2026
- The Vendor View 2026 - A breakthrough AI year, and one of reckoning - Legal IT Insider, accessed February 9, 2026, https://legaltechnology.com/2026/01/15/the-vendor-view-2026-a-breakthrough-ai-year-and-one-of-reckoning/
- Empowering Developers with Markdown-based Documentation for Better Software Maintenance for NEDB 2026 - IBM Research, accessed February 9, 2026, https://research.ibm.com/publications/empowering-developers-with-markdown-based-documentation-for-better-software-maintenance