Use org-mode for editing

Celorga documents are ordinary .org files, so they open in Org Mode without extra configuration.

That gives you mature Org editing, outline navigation, folding, timestamps, TODO keywords, and tables while Celorga continues to own the standalone parser, CLI, publishing, and compiler semantics.

Use the CLI beside Emacs

Run Celorga commands from a shell, compile, async-shell-command, or your own Emacs wrapper:

celorga agenda --dir ~/notes --recursive
celorga fmt --dir ~/notes --recursive --check
celorga lint --dir ~/notes --recursive
celorga publish docs-site --config org2.json

Mutating commands preview by default and require --apply to write files, which makes them reasonable to wire into custom Emacs commands once you are comfortable with the output.

Coexistence notes

• Existing .org files can remain in place; Celorga scans them directly.

• Celorga is not a bug-for-bug Org Mode clone. It keeps common Org-shaped constructs but chooses clearer behavior where portability needs it.

• The Celorga app and its writers canonicalize accepted source-block sugar before saving .org. Compiler/provenance properties remain readable even when Emacs does not assign them Celorga semantics.

• If you rely on advanced Org Mode packages, keep using them; Celorga can act as a parallel compiler/runtime over the same text where the semantics overlap.

Current status

Dedicated Emacs integration is still open work. Useful future pieces would include CLI command wrappers, LSP setup, agenda buffers backed by celorga agenda --format json, and helpers for roam IDs/backlinks.