Ask questions across your Markdown notes using a fully local Graph RAG engine. Built for Obsidian vaults, works with any folder of Markdown files. Extracts entity-relation triples from wikilinks & YAML frontmatter, retrieves answers via hybrid search (vector + BM25 + temporal). Multilingual. No cloud. Runs on Ollama.

https://github.com/benmaster82/Kwipu

Nor have I managed to create a custom superset that extends markdown enough that you can make a video game with it. You can also not edit markdown with it (imagine that!).

It’s just a reader, and I did manage to make it pretty easy to read markdown in a browser, you can drop a file, paste raw markdown or paste a URL to parse the contents into markdown, among other ways to pass content into the app.

You can annotate if needed (select anything and start typing), download an annotated or clean copy, or export just the notes. The annotated copy is still a plain .md file, the notes live inside it as comments, drop it back in and everything comes back.

You can even share it with others, either as a view only or annotator link, no account, only people holding the link can open it, and you can delete it at any time.

I don’t want your money, your email, or your personal data, I just want you to be able to quickly read markdown in the least intrusive way possible.

The reader is very opinionated, give it a whirl at reader3000.com

If you like it, great, if you don’t, fair enough :D. I invested a lot into making it resilient, but if a normal markdown file breaks it (not one purposefully constructed to break things), lemme know.

If you’ve ever spent three hours configuring Webpack, fixing broken npm dependencies, or tweaking a docusaurus.config.js or mkdocs.yml file just to spin up a basic documentation site, you know the fatigue is real.

I recently stumbled upon an emerging open-source tool called docmd (strictly lowercase), and it feels like exactly where documentation engines should be heading. It strips away all the framework bloat and focuses entirely on speed, security, and AI compatibility.

Here is a quick, honest breakdown of what it is and why it's a massive upgrade from traditional tools:

What actually is it?

docmd is a zero-configuration, local-first documentation engine. You point it at a folder of raw Markdown files, run a single command, and it compiles a blazing-fast, Single Page Application (SPA) instantly.

Why it beats traditional tools at scale:

• Zero Configuration: There are no bulky boilerplate setups. You run npx docmd build and it automatically maps your folder structures, handles asset routing, and builds your site out of the box.
• Insane Performance (~18 KB Payload): Tools like Docusaurus load heavy React component hydration trees for every route, causing massive bloat on large sites. docmd compiles down to pure vanilla DOM manipulation with a client payload of under 20kb. Pages load instantly with a literal 100/100 Lighthouse score.
• 100% Local Semantic Search: Most documentation generators force you to pay for or configure third-party cloud services like Algolia just to get a functional search bar. docmd runs full-text and fuzzy search entirely on the client side using browser-side tokenizers. Zero data ever leaves your machine.
• Built for AI Agents (The Secret Weapon): This isn't just for human eyes. docmd natively handles the shifting developer landscape. It auto-generates structured llms.txt context buffers at build time and features a native Model Context Protocol (MCP) server (docmd mcp). If you use AI assistants like Claude Code or Cursor, they can plug directly into your local docs via stdio to eliminate code hallucinations completely.

Evolution: From 0.1 to Now

The project didn't just stop at basic Markdown parsing. The developers have been aggressively shipping high-discipline engineering updates:

1. Multi-threaded Worker Pools: It handles thousands of enterprise documents concurrently without hitting single-thread Node bottlenecks.
2. Strict Security Hardening: They systematically stripped raw innerHTML execution across the monorepo to eliminate XSS vulnerabilities, making it safe for secure, air-gapped corporate setups.
3. Modular Custom Plugins: Instead of bloating the core engine with heavy third-party npm packages, they custom-engineered micro-libraries like lite-matter (frontmatter parsing) and lite-hl (syntax highlighting) to keep execution lightning fast.

Quick Test Drive

You don’t even need to install it to see how it looks. Drop some markdown files in a folder and run:

npx @docmd/core build

If you are using Claude Code or Cursor and want to feed it the native developer rules, you can install the standalone skill set directly to your agent directory:

npx docmd-skills ~/.claude/skills

It’s completely free, MIT-licensed, and 100% offline. If you're tired of framework bloat or want to give your AI tools better codebase context, it is well worth checking out.

GitHub Project: github.com

AGY Builders,

We are all trying to build useful and scalable workflows for our AGY CLI and ecosystem, but the speed at which we need to learn, build, and deploy new things is incredibly overwhelming. If you are feeling that pressure, you are in the right place here at r/GoogleAntigravityCLI.

Over the past few weeks, I have been testing an "AGY WIKI OKF" setup that I put together myself (after inviting some members of this community to collaborate; mod is not proud). I know some folks might hesitate to trust a tutorial from a random Redditor, but I wanted to share this with the community anyway because it actually works.

I was able to build this because I am all-in on Google and the Antigravity Ecosystem. I’m a truly AGY—I am not some ultra-smart, 10x developer, but I know how to work hard, I dig for the right information, and I iterate.

AGY WIKI OKF | The Idea

To build a frictionless, token-efficient knowledge WIKI engine that transforms static documentation or notes (information) into an active, intelligent collaborator—orchestrated entirely by Antigravity CLI.

The core philosophy is simple: treat knowledge management as a clean pipeline and tokens as a premium, finite resource.

By anchoring this architecture to Google’s Antigravity CLI, the AGY WIKI OKF bypasses heavy middleware and complex UI layers, delivering a hyper-focused AI partner built entirely for execution speed, context hygiene, and minimal footprint.

Why adopting AGY WIKI OKF matters:

• Stay organized (AGY OCD): Structured Markdown and YAML keep the chaos in check.
• Save tokens: Doing more with less context window bloat.
• Scale shareable knowledge: Making it easy to pass context and logic between different LLMs.
• Humans and Agents working together: One standardized, readable format that works perfectly for both of us.
• BYOD (Bring Your Own Data): Own your context. Port it to the newest model, platform, or OS instantly.

The Tools

• Antigravity CLI
• Obsidian : The IDE for the Knowledge bank
• Obsidian Web Clipper:
  • Official Site
  • Chrome Web Store
  • Firefox Add-on

The WIKI

In the agent-first era, a WIKI is no longer just a static graveyard for human notes; it is the operational hard drive for your agents. By maintaining a highly structured WIKI, you ensure that every piece of context is stored in a clean, machine-readable format. This means that whether you are testing a new modular skill or spinning up a specialized agent, your AGY CLI knows exactly where to find the precise context it needs to generate autonomous action, moving you far beyond simple, reactive conversational text.

Reference: Gist on Knowledge Representation

Google Open Knowledge Format (OKF)

Google’s Open Knowledge Format (OKF) feels like the exact missing piece we've needed for orchestrating multiple AI agents effectively. It provides a vendor-neutral, interoperable standard for storing and sharing organizational knowledge.

Why this is huge for orchestration:

1. The "Lingua Franca" for Agents: Any agent can read it out of the box without platform-specific integrations.
2. Seamless Context Passing: Specialized agents can access, update, and pass the exact same foundational context back and forth.
3. Human-in-the-Loop Oversight: Because OKF is just Markdown and YAML, it’s inherently readable and auditable.
4. Scalable Knowledge: It acts as a shared, living library that grows alongside your agents.

AGY WIKI OKF Integration

Structuring an AGY Wiki using OKF revolutionizes how complex knowledge is shared. By standardizing documentation with concise Markdown and YAML frontmatter, OKF provides a unified taxonomy for cataloging AGY CLI slash commands or skills It is highly token-efficient, stripping away bloated formatting and maximizing context window limits.

The Prompt for Building an AGY WIKI OKF

AGY CLI WIKI OKF PROMT EXAMPLE

/grillme I want to initialize a brand-new, empty Obsidian vault from scratch that adheres strictly to the Open Knowledge Format (OKF) standard, with the specific intent of potentially open-sourcing or sharing this architecture later. I want a purely blank, skeletal framework with no pre-populated data. Please grill me to define the optimal architectural blueprint for this vault. I need you to interrogate me on: Do not generate the directory structure or files until you are satisfied that you have captured all my requirements for a production-ready, shareable knowledge base. 
Core Directory Hierarchy: How should we structure the root (e.g., /concepts, /resources, /indices, /log) to be intuitive for external users? Template Strategy: What base boilerplate templates do we need to ensure every new file is automatically OKF-compliant and structured for consistent metadata? Workflow Logic: Since this is a fresh start, what processes should we bake in for capturing information vs. refining knowledge that could be easily documented for others? CLI Integration: What specific file locations or configurations do we need to ensure this vault plays nicely with the Antigravity CLI from day one? Open-Source & Contributor Documentation: What files should we create to make this a "deployable" standard? Please include requirements for: A README.md with installation and usage instructions. A CONTRIBUTING.md that defines how to add new concepts or schemas. A "System Architecture" document that explains the logic behind the folder structure and metadata fields, ensuring anyone who clones this vault understands how to extend it.

The Final File Structure

AGY WIKI OKF
    ├── .agyrc
    ├── ARCHITECTURE.md
    ├── CONTRIBUTING.md
    ├── README.md
    ├── .agy
    │   └── .keep
    ├── .obsidian
    │   ├── app.json
    │   ├── appearance.json
    │   ├── core-plugins.json
    │   └── workspace.json
    ├── 00-Inbox
    │   └── .keep
    ├── 10-Projects
    │   └── .keep
    ├── 20-Areas
    │   └── .keep
    ├── 30-Resources
    │   ├── .keep
    │   └── Google Antigravity Documentation.md
    ├── 40-Archive
    │   └── .keep
    ├── 99-Meta
    │   └── Templates
    │       ├── Base_Template.md
    │       ├── Project_Template.md
    │       └── Resource_Template.md
    └── Clippings

TL;DR

• AGY WIKI OKF: Organizes your information (context) , AGY CLI commands, skills  behaviors, and A2A workflows into a token-efficient, shareable format that reduces inference costs for any LLM.
• Open Knowledge Format (OKF): Provides a standardized, vendor-neutral way to share context (Markdown + YAML), preventing platform lock-in and eliminating data fragmentation.

AGY Builders, I genuinely want your input on this. Please comment, grill me, roast me, ask questions, or give me your raw feedback on this AGY WIKI OKF setup. We are building the foundation to organize and share our data in the BYOD era. Let's build the future together.

Hey everybody,

I just wanted to introduce everyone to Fluster and Conundrum, if you're looking for a markdown application with some additional features. It uses a completely independent Rust powered compiler that takes 90% of commonmark markdown, and a list of additional components that extend the functionality considerably.

It's still in it's early stages, with the iPad app maybe 2-3 weeks away still, but the potential is really limitless for this extended syntax.

Links
Flusterapp.com

Let me begin with my experience with Note-Taking Apps. I have tried to increase my productivity with a lot of note-taking apps like Obsidian, Notion, Google Notes etc. But each one had its own limitations.

Obsidian - Yeah! It is preferred by many people, it has a rich plugin library, but it is not free and open source. It also requires you to sign-up with an Account. I tried Logseq as its alternative, and even though it is quite good for an open-source app is still currently in its beta stages and the overall experience is not quite polished yet.

Google Notes - It is very simple to use and it does actually work for me, but here also there are disadvantages. First is it is owned by Google. It also does not have many features like tables, math formulae etc., even though its basic syntax works for many people. But here the problem comes for Digital Privacy.

Notion - Again it is a corporate product, and I wasted more time organizing notes instead of reading them which killed my productivity.

As I was looking for more tools like these, I came through some YouTube videos in which I knew about Apple Notes like these -

[How I Organized My Entire Life Using Just Apple Notes](https://youtu.be/IMJSkU3rVNg?si=gGf192xN1zIq_LnV)

And even though I am a Windows user, I liked the simplicity of Apple Notes and especially its premium-looking User Interface. So, I started looking for its Windows-Alternatives. I found -

Joplin - FOSS, Simple UI, rich-plugin library, rich-markdown features. But the catch here was, it didn't give that premium Apple-Notes like feeling. I searched for many such apps like Trillium, QOwnNotes etc. but they did not quite match the aesthetics I was looking for.

Finally, I found this Note-Taking App - HelixNotes.

It is an AGPL3-Licensed FOSS, fast and lightweight Note-Taking app with simple and premium looking UI (which I personally prefer). Ofcourse, it does not have the famous Apple "Ecosystem" features but it can do most of the things in a simple and fluid way. Here are some features -

1. No account sign-up required.
2. All files are stored locally (no database) inside a folder you make as .md files.
3. KaTeX math and Mermaid diagrams, rendered natively, also images, documents etc.
4. Full-text search inside notes.
5. Optional AI, local with Ollama or your own key.
6. And more features that you probably wouldn't even need :)

Here are some useful features I found from the previous Note-Taking apps I used like-

1. Graph/Node view of Obsidian.
2. Backlinks and Daily Journal of Logseq.
3. with many features for customization like 29 in-built color palates (you can even create your own theme) so that you can make it match your aesthetics.

This note-taking app is for Linux, Windows, MacOS and Android. You can sync your notes across devices using your own WebDAV server (No need of OneDrive or Google Drive). You can sync manually and even automatically through settings.

Source Code - [Helix Notes](https://codeberg.org/ArkHost/HelixNotes)

Setup for Windows is only 8.24MB! Very Lightweight, but I don't know how it will perform when I start writing more and more notes in it (Hope it does not start lagging.)

Overall, it has a very similar interface, It has the same folder system of Apple Notes with simple commands, customizable shortcuts and many more. It does not have all features of Apple Notes but I feel this is the closest to experience it in Linux, Windows and Android. If you have tried Helix Notes, you may also check another such AGPL3-Licensed FOSS, Note-Taking app which is similar to Apple Notes-

[Tolaria](https://tolaria.md/)

Obsidian Users! You can import your Notes Vault to Helix Notes in the settings!

When I use the {{column-count: 3}} I also tried naming the group and using the css accessor to target it, but it seems like declaring a section is moving it down slightly in the first column, any help would be appreciated thanks.

Hi! I have been working on this App with a file manager, an Editor called Workbench and Digital Gardens sharing app. All the apps are well integrated within a unified OS like environment. It is not an OS, but the UI is as such.

I created primarily due to my nostalgia/love for older file formats like Markdown. And the early web digital gardens and webrings.

If you would like to know more like the technical details or just want to have a conversation around it then feel free to shoot me a DM!:)

Markdown is basically the language my whole setup speaks. Notes, docs, project files, all of it lives in Markdown and just works. The problem was everything that doesn’t start as Markdown, and that turned out to be a lot. PDFs, Word docs, slide decks, spreadsheets, EPUBs, web pages, even audio I wanted transcribed. Getting all of that into clean Markdown so I could actually reuse it was the missing piece.

So I built MDFlux. It’s based on microsofts library “markitdown” which is hard to setup and has a few problems, main reason i made this app, It’s a local desktop app, Windows for now. You drop a file or a whole folder and get clean Markdown back. What I wanted from it:

One tool for everything. PDF, DOCX, PPTX, XLSX, EPUB, HTML, CSV, JSON, XML, and audio, not a different converter per format.

It reads scanned PDFs and images. Naive extractors return basically nothing on an image-only page, so it runs OCR locally to pull the text back out.

It runs entirely on my machine. No upload, no account, no API key. Private stuff stays private.

Batch, because I usually had folders to get through, not one file at a time.

It’s free and MIT licensed, still very much a work in progress. Tables and formula-heavy pages are where every converter struggles, so I’d love to hear what breaks for you there.
Happy marktitdowning or whatever haha, hope it helps, i do this in my free time so let me know if it helps :)

Repo: https://github.com/ibrahimqureshae/mdflux

cwMarkdown is a focused, read-only Markdown viewer for macOS. It deliberately has no editor: the entire surface area is given to presentation, so a document looks as good as the writing in it. The goal is the reading experience of Typora — clean measure, comfortable line height, a native system font — in a small, fast, native app.

Under the hood it’s a SwiftUI app that renders Markdown in a WKWebView, which gives pixel-level control over typography while keeping the window chrome, toolbar, and outline fully native. Parsing is done with marked, code is highlighted with highlight.js, and math is typeset with KaTeX — everything bundled, so the viewer works with no network access at all.

https://code.intellios.ai/cwmarkdown/

I have a monetized youtube channel where I mostly upload Short videos and gained over 100M views last year. So from my experience and some research I build a website to estimate average monthly/ yearly earnings.

Take a look and tell me if you find useful and feel free to share feedback.

Youtube Shorts channel revenue calculator

Features:

• You can filter by country like US, India, Brazil, Indonesia, Mexico, Japan, Germany, Vietnam,....
• you can say it contains tagged products in video for accurate calculation.
• If you know their average monthly views and RPM, there is one more dedicated calculator
• Shorts Ad-Revenue RPM table ranked by Territory
• If you need a Youtube Long video calculator try: Youtube Long video revenue calculator

I hope this helps you to choose a better Niche and audiance.
Give it a try.

Posted this here a while back and got some great feedback — mainly that the export looked rough and didn't support callouts, and that a local CLI beats a browser tool for most real workflows. Both fair. Here's what changed:

visit here: Markdown to PDF converter

New:

• Callout/alert rendering — > [!note], [!warning], [!tip], etc. now render as actual styled boxes instead of plain blockquotes. Supports GitHub's 5 alert types plus Obsidian's full callout set (13 types total), including foldable callouts ([!tip]+/[!tip]-)
• Mermaid diagrams and LaTeX math still render natively (flowcharts, sequence diagrams, KaTeX equations) — this was the original reason I built it
• Page-break control — code blocks, tables, and diagrams won't get sliced across a page edge; table headers repeat on continued pages
• 4 print themes (Default, Report, Resume, Academic)
• Two export options: one-click download, or "Export to PDF" through your browser's print dialog for sharper text and guaranteed clean breaks on longer/technical docs

On the local-processing point, since that's what most of you actually cared about:

Everything — markdown parsing, Mermaid rendering, math typesetting, PDF generation — runs in your browser tab. Nothing you paste or upload touches a server. I didn't just slap a "100% private" badge on it and call it done; the site has a section showing you how to verify that yourself instead of taking my word for it: turn off your wifi and try it anyway, or watch the Network tab while you convert. Both work regardless of whether the code is open source.