Skip to content

Usage

FkeMark is built around one idea: your documents stay in local folders, and the editor only makes Markdown writing, reading, organizing, and publishing easier.

FkeMark writing workflow

Daily workflow

StepActionResult
1Open a local folderThe sidebar shows your existing Markdown structure
2Create or open a .md fileThe file stays plain text
3Choose Live / Split / Read / SourceSwitch between drafting, side-by-side checks, proofreading, and source control
4Insert images, tables, links, or code blocksBuild common Markdown structures quickly
5Save, review version history, export, or publishContinue with local files, snapshots, export formats, or the docs site
  1. Structure first: write headings, lists, and paragraphs in Source or Live.
  2. Fill the content: use the toolbar for links, images, tables, and code blocks.
  3. Check side by side: use split view for complex tables, formulas, or code blocks.
  4. Proofread as an article: switch to Read and review hierarchy and rhythm.
  5. Save reliably: keep Markdown as the primary format; export only for sharing, archive, or migration.

Saving and snapshots

  • When saving an existing document, FkeMark keeps a local snapshot before writing the new content.
  • To keep a manual checkpoint, click “Create Current Snapshot” in the Version History toolbar menu.
  • When comparing a snapshot, use “Previous diff / Next diff” to jump between changed lines.
  • If a file changes very frequently, adjust the per-file snapshot limit in “Settings → Behavior”.

Folder organization tips

ScenarioSuggested folders
Project docsdocs/, notes/, changelog/
Study notesinbox/, reading/, summary/
Blog draftsdrafts/, assets/, published/

TIP

Keep images and attachments near the Markdown files that use them. A local assets/ folder is usually enough.

Next steps

  • Markdown features: Syntax.
  • Buttons and actions: Toolbar.
  • Faster operation: Shortcuts.
  • Theme, toolbar, subscription, or debug-entry preferences: Settings.

Released under AGPL-3.0-only.