Org essentials

Headings are the structure

Start a heading with one or more asterisks followed by a space. More asterisks mean a deeper level. Text below belongs to that section until the next heading.

#+TITLE: My notebook

* A project
Notes about the project.

** A smaller piece
Details that belong inside it.

In OrbitalNote, headings can be folded, searched, linked to, and focused independently.

Tasks, dates, and tags

A heading becomes a task with a state such as TODO. Mark it DONE when complete. Dates use Org timestamps, and tags sit at the end of the heading.

* TODO Send the proposal :work:
SCHEDULED: <2026-10-26 Mon>
DEADLINE: <2026-10-28 Wed>

* DONE Book the room :work:

You can set these values through the task form instead of typing them. See Tasks & repeating work for the meaning of schedules and deadlines.

Lists and emphasis

- A bullet point
- Another point
  - A nested point

- [ ] Something to do
- [X] Something finished

*bold* /italic/ _underlined_ =verbatim= ~code~

Heading asterisks need a space after them; inline bold wraps the words. Checkbox lists are useful within tasks, but they do not each become agenda tasks.

Links and tables

[[https://orgmode.org][The Org website]]
[[file:Projects.org][My projects]]

| Topic    | Next step |
|----------+-----------|
| Notebook | Write     |
| Calendar | Plan      |

Links can point to websites, local files, and headings. Keep local attachments in your workspace folder so their relative paths stay useful when you move the folder.

Code, diagrams, and compatibility

#+begin_src python
print("Hello, notebook")
#+end_src

Source blocks preserve code as text. Reading view supports rich content such as Mermaid diagrams and math, but OrbitalNote does not execute Babel blocks.

Org is broader than any one app. OrbitalNote supports core writing and planning workflows rather than the full Emacs environment. Unsupported constructs can remain in your source even when they have no special presentation.