[pavpanchekha]

I think the key thing about Org-mode is to not read the documentation. All you need to start is stars and the tab key. The docs have a way of dumping keybindings onto you. Org mode has a lot of features --- don't try to read the manual through. Just start using it and every time you think of a feature you would like, look it up in the manual.

[officemonkey]

It is worth looking through the documentation to learn what it _can_ do. I've met people who say "I wish it could do x" and I reply "It can do x!"

[ottbot]

This is probably good advice, and I think I'll give org-mode another try without trying to build it around someone else's setup.

I've been using emacs for years, but could never quite make an habit out of org mode. I think deft handling simple org files might be a good way to get started.

[pavpanchekha]

I kept trying to start with a todo list in Org-mode, and it was never worth it. Instead, I ended up getting into Org-mode through using it as a markup (it supports inline LaTeX!) and only later learned some of the shortcuts. I've just started using C-RET and similar to add outline nodes, for example; similarly C-. and C-d and such. Now I use Org-mode heavily for literate programming as well.

One of the reasons I love Emacs and Org-mode so much is that it never forces you to use its features. For the right approach and for the power user, this is beautiful.

[josephkern]

Yeah, don't follow other people's guides to get started. Just realize that org-mode has so many features (including Literate Programming) it's easy to get lost.

Just start by using it as an outliner, when your files get too big or you need to start keeping TODO lists, look into agenda views, then capture, then ... well you know.

Start as simple as possible, and when things break, or don't do what you need, spend 15 minutes and make them work.