MareArts Gadget
MareArts Markdown Studio
A reader for Markdown files. Double-click a .md and the rendered document opens, the way a PDF reader opens a PDF.
1. Opening and moving around a document
The sidebar is built from the document's own headings, so a long file becomes a contents list you can jump around in. The other three sidebar panels are the folder you are reading from, the files you opened recently, and your favourites.
You do not have to go looking for a file: Ctrl+K finds one by typing part of its name. If the file changes on disk while it is open, the page re-renders and keeps your place rather than jumping back to the top.
2. What gets rendered
GitHub-flavoured Markdown, in full: tables, task lists and footnotes, code with syntax highlighting, LaTeX maths through KaTeX, and Mermaid diagrams drawn from their source.
Images the document references are read from the folder beside it, and only from there — a document cannot reach files outside its own folder.
3. Source beside the rendered page
Split view puts the Markdown source next to the rendered result, scrolled together, which is the view you want when you are checking why something rendered the way it did.
Ctrl+F searches the open document, with Enter and Shift+Enter stepping between matches.
4. Themes, zoom and printing
Light and dark themes, and zoom for when the text is too small on a large screen.
Printing goes through your operating system's own print dialog, and PDF export writes the file directly. Both use the same rendering you are looking at, so the printed page matches the screen.
5. Keyboard
| Ctrl+K | Quick open — find a document by name |
| Ctrl+O | Open a file |
| Ctrl+F | Find in document |
| Ctrl+P | |
| Ctrl+D | Add or remove from favourites |
| Ctrl+1–4 | Contents, Folders, Recent, Favourites |
| Ctrl+\ | Show or hide the sidebar |
| Ctrl+±, Ctrl+0 | Zoom |
Quick open is on Ctrl+K rather than the Ctrl+P editors use for it, because here Ctrl+P prints.
Linux (Ubuntu 22.04 & 24.04) · macOS (Apple Silicon & Intel) · Windows 10 & 11
MareArts Backup System
Your folders copied to another disk on a schedule — and everything you changed or deleted, kept.
1. Is everything copied?
The first screen answers the only question a backup has to answer: how many of your folders are up to date, when the next check runs, and how much room is left on the backup disk.
A run started here shows a progress bar and the live rsync log, so a long copy is something you can watch rather than wait blindly through.
2. Choosing folders and a destination
Add as many source folders as you like; they all copy to one destination disk. Each row shows the folder and exactly where on the backup disk it lands, along with both sizes, so a source that has quietly grown is visible before it fills the disk.
On macOS the app needs Full Disk Access before it can read Documents, Desktop and Downloads. It shows a banner with a button that opens the right settings pane — a backup that silently skips those folders would be worse than none.
3. Scheduled runs and their history
Runs happen daily, weekly or monthly, driven by your own operating system's scheduler — a systemd user timer on Linux, launchd on macOS, Task Scheduler on Windows. They continue with the window closed, and they keep running even if the subscription lapses: a lapse closes the console, not the backups.
Past runs are plotted on a real time axis, so a week when nothing was copied looks like a week-wide gap instead of one row among many. Only one backup runs at a time, whether it was started by the timer, by the button, or by hand.
4. Going back to an earlier day
Pick a date and browse the backup as it stood then — including files you have since changed or deleted — and restore a single file or a whole folder from it.
5. How the backup disk is laid out
Copies are made with rsync into plain folders. There is no archive format, no database and no encryption layer, so the files can be read with the file manager on any machine — nothing needs this app to get them back.
target/
├── current/ the latest copy, mirroring your sources
└── .versions/ one folder per run, holding what changed
├── 2026-04-22/
└── 2026-08-08/
A new file goes into current/. A modified one is updated in current/ and its previous copy moves into that run's version folder. A deleted one leaves current/ and is preserved in the version folder. Only changed files are stored, but each is stored whole, not as a diff.
Linux (Ubuntu 22.04 & 24.04) · macOS (Apple Silicon & Intel) · Windows 10 & 11