Write in a folder of plain Markdown files. One document on screen, search across the folder, and Hebrew and English correct in every paragraph. macOS, iPhone and iPad.
ProductivityGitHub @yybdOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
GitHub star growth between the latest completed 8-hour observations
DeepSeek Harness Remote can securely connect a phone or another computer to the computer where you run DeepSeek Harness, so you can continue your work anytime and anywhere, check progress anytime, and continue working.
AI translation
Ayakaleaf Pro is a free, open-source, self-hosted Overleaf alternative: Overleaf Community Edition with almost all Server Pro features — track changes, project history, admin panel, SSO, Git-bridge, Z
Open-source, local-first task manager that works offline, syncs every device, runs on a Raspberry Pi, and requires no subscription.
AI translation
Open Source Office suite for users used to MS Office - multi-platform, tuned for performance
Export a note or a folder as a book-ready Word or EPUB file, Hebrew and English alike — PureWrite's export engine in Obsidian.
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Book-ready Word, PDF and EPUB from a note or a whole folder — real footnotes, tables, lists, images and chapter breaks, with Hebrew and English set correctly side by side. Works on desktop and on phones and tablets (PDF on desktop). Free.
What sets it apart
The file is written into the vault, beside what it was made from, and the dialog offers to open it. Nothing leaves the device. A PDF is laid out with PureWrite's own print layout (paged.js) and printed by Obsidian's Chromium, so it is made on the desktop only; a phone offers Word and EPUB. The dialog speaks Hebrew when Obsidian does.
Chapter order is by name (number your notes 01, 02, …), unless the folder holds an
order saved by PureWrite (below). Obsidian syntax is read as Reading view shows
it: image embeds become images, wikilinks their text, callouts quotes with a bold
title; front matter, %%comments%% and block ids are left out.
From Obsidian: Settings → Community plugins → Browse, search for PureWrite Export.
By hand: copy main.js, manifest.json and styles.css from the latest
release into <vault>/.obsidian/plugins/purewrite-export/.
Disclosure: after an export, the result screen shows a small card about PureWrite, the author's own app, with a link to its page. It appears only there, after an export you started — never as a pop-up or a notice — and nothing is loaded from the internet to show it.
The export is built by the export engine of PureWrite, a focused Markdown writer for Mac, iPhone and iPad, sold separately on the App Store. This plugin is free and needs no PureWrite.
If you do use both, they are one tool over one folder: a folder exported here and in
PureWrite is the same document, and the folder remembers its settings in
.purewrite-book.json — the title, the switches, and the chapter order you drag into
place in PureWrite's sidebar. Each export starts where the last one left off,
whichever app made it.
vendor/purewrite/ is PureWrite's engine, copied file for file — never edit it here.
pnpm install
pnpm build # builds main.js from the committed vendor/, linted with Obsidian's rules
pnpm test
Updating the engine needs the PureWrite repository, which is not public:
PUREWRITE=<path to PureWrite> pnpm sync-engine # copy the engine again
PUREWRITE=<path to PureWrite> pnpm build # fails if vendor/ is stale
Bump version in manifest.json and package.json, add it to versions.json,
commit, then push an annotated tag with that version and the release notes as its
message (git tag -a 0.2.3 -m "…"). The Release workflow builds, attests the files
and publishes them.
MIT — see LICENSE. That covers this repository, the engine in
vendor/purewrite/ included; it does not cover the PureWrite app.