The move to MostlyText

0 of 5 merged

MacDown 2 becomes MostlyText. The visible crossover: the app's name and icon, kept settings and documents, the CLI, distribution and the repository move. Still ahead.

One of the five chapters on the way to 1.0: 0 of its 5 work areas are merged into the development code, which is not the same as verified for release. Checked against the development repository on 15 October 2026.

The MostlyText mark, a forward-leaning M and T that share one stem, shown in dark ink on a light ground and in white on a near-black ground.
The MostlyText identity: the Slant mark in one colour, on light and on dark. The website already uses it; the app still runs as MacDown 2 until this chapter renames it.

In short

MostlyText began as MacDown 2, a rewrite of the open-source MacDown editor. This chapter is the visible crossover: the app’s name, icon and identifiers change, your settings and documents carry over, the command-line tool becomes mostlytext, and the code moves to its own repository.

The identity is decided, but the app is still called MacDown2.app. Renaming it safely is the work: fresh installs and upgrades from MacDown 2 must both keep preferences, sessions, recovery files, recent folders, snippets and custom themes. The MacDown lineage, its MIT licence and its copyright stay intact.

It also covers how official builds will reach people. The direction is open-source MIT code with affordable paid official builds, sold directly without DRM and through the Mac App Store, as a one-time purchase with no subscription, account or activation. Timing and channels are still being reconciled; today’s testing alpha is source-only, with nothing to buy.

Why the name and icon don’t match yet

For now you’ll see two names. The website, the alpha’s release page and this roadmap say MostlyText; the app itself still opens as MacDown 2, installs as MacDown2.app and keeps its settings under that name. That’s deliberate.

The identity came first. In September the Slant mark was chosen: an M and a T sharing one stem, leaning forward, in a single colour, ink on light and white on dark. The website uses it already because a website has nothing to migrate.

The app has a lot to migrate. Its name and identifiers decide where macOS keeps its preferences, recovery copies, sessions, snippets and themes, and which app opens your Markdown files. Change them carelessly and an upgrade could seem to lose all of that. So the rename happens once, in this chapter: tested on fresh installs and on upgrades from MacDown 2, and done before the interface and its translations are frozen, so the new name is only translated once.

The icon follows the same path. The development build still has a placeholder icon generated by a script. In September the Slant mark went through Apple’s icon tool once, to prove the production icon works in the real Dock and Finder; that test was then taken out again. The brand rules treat colour and gradients on an icon as styling rather than identity, because the mark has to stand up in one colour first. The final icon, built from this same mark, is fitted and checked in Finder, in the Dock and at small sizes as part of this chapter.

Where it stands

How it will be checked

From the acceptance criteria in the plan. Merged work still has to pass these on a release build.

  • A Mac upgrading from MacDown 2 keeps every setting, session, snippet and theme, and a fresh install starts clean.
  • The icon reads correctly in Finder, in the Dock and at small sizes.
  • The repository is mirrored with its full history at the final cutover, and the release commit is identical in both places.
  • The website offers the real download, requirements, documentation, privacy, licence and support, with screenshots from the release build.

The 5 work areas

MacDown 2 → MostlyText: brand and identity crossover

Still required

  • Apply MostlyText display/product identity, menus, About/Help and onboarding
  • Integrate accepted production icon/wordmark and document-icon assets; verify Finder/Dock/small sizes
  • Use app.mostlytext.MostlyText and consistent Quick Look/theme/document identifiers
  • Migrate preferences, Application Support, sessions, recovery, recent roots, snippets and custom themes without data loss
  • Adopt mostlytext CLI and decide compatibility alias/delivery topology
  • Align mostlytext.app, mostlytext.dev routing, downloads, docs, support, signing and updater identity
  • Mirror full repository history only at final cutover; preserve MIT, copyright and MacDown lineage

The identity is decided; integration and migration are still required. Fresh installs and upgrades from MacDown 2 must both be verified.

Depends on Everyday editor essentials.

Issue 158Plan reference identity

Release-side software before UI freeze

Still required

  • Development/beta identity and recovery/session/snippet/theme-state migration
  • Legacy MacDown preferences import without clobbering configured new values
  • CLI open/stdin/--wait and final delivery topology
  • Sparkle 2 updater/settings and EdDSA update channel
  • About/licence surface and notices in catalogs

Depends on MacDown 2 → MostlyText: brand and identity crossover; Mac integration and personalisation; File, settings and native hardening.

Issue 18Issue 53Issue 148Plan reference E17-software

Final repository cutover

Still required

  • Freeze/tag exact release commit, mirror full history to Joncallim/mostlytext
  • Verify identical release SHA/tag, CI/builds and repository-only proof commit
  • Preserve provenance and archive old development repository

Product-input changes after mirror reopen artifact verification.

Depends on Close all release-required debt.

Issue 158Plan reference cutover

Website, proof and launch readiness

Still required

  • Download-first canonical site with requirements, docs, privacy, licence/lineage and support
  • Real release-build screenshots and concise open/edit/preview/Quick Look/export demo
  • Small external beta and one feedback route before broad amplification
  • Verify install/download/update paths, known issues and concise launch notes

Launch material will use real release-build evidence.

Depends on Final signed candidate and compliance; MacDown 2 → MostlyText: brand and identity crossover.

Product direction, October 2026Plan reference launch-surface

Official distribution and support

Still required

  • Open-source MIT code with affordable paid official binaries
  • Direct DRM-free distribution and a Mac App Store direction
  • One-time purchase direction, without a subscription, account or activation
  • A clear support route for official builds

Distribution timing and channel compatibility still need to be reconciled. The testing alpha is source-only; no purchase or signed app download is available.

Depends on MacDown 2 → MostlyText: brand and identity crossover.

Product direction, October 2026Plan reference commercial-direction

Open in the development repository

Titles as the developers wrote them, on 15 October 2026.

Not part of this

  • Windows and Linux versions.

What the labels mean

Still required
work or verification still needed before 1.0.