From: Ihor Radchenko <yantar92@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal
Date: Sun, 05 Dec 2021 20:08:09 +0800 [thread overview]
Message-ID: <87lf0zb6fq.fsf@localhost> (raw)
In-Reply-To: <87y24zs40r.fsf@posteo.net>
Juan Manuel Macías <maciaschain@posteo.net> writes:
> Yes, sorry for not explaining myself well: I was also referring to
> search results, not the title in the web site...
>
> But the question is: what need is there to remove the reference to Emacs
> in the search result? I think the emphasis is necessary. As we say in
> spanish, it's like putting the bandage on before the wound. If there are
> people who think that Org Mode can 'live' in some way outside of Emacs
> (a respectable opinion, but that I do not share, at least 100%), I think
> the burden of the work falls on them and not on us, the users of
> Emacs-Org-Mode. Anyway it is my simple and subjetive opinion, and it is
> not my intention to initiate a controversy with it.
Ok. Let me explain my thought process.
First of all, there is no burden on users of Org mode in making edits to
orgmode.org. It is a burden on Org contributors.
One of the aims of my proposal is reducing this burden by involving
non-emacs users to provide contributions to Org (e.g. by making more
tests for Org-element parser). To do it, we need to make the
contribution process for non-emacs developers easier. Ideally, without
too much effort on our side.
The idea of involving non-emacs users does have a potential because we
do know that third-party tools are already using Org. The problem is the
disconnect between those tools and Org mode proper.
The sources of the disconnect are (1) lack of technical "blueprints" for
Org that do not require knowing Elisp; (2) lack of discovereability of
Org mode as something that can live outside narrow field of Emacs. In
this branch of our discussion, I am going to talk about the second
point.
People simply do not expect to see a markup language when they encounter
a link with "Org mode for Emacs" title. Someone looking for Org mode
markup to be used in, say, websites will think that "Org mode for Emacs"
is limited to Emacs. Someone just interested in plain text markup will
find no relevance at all.
Title is important. If we care at all about orgmode.org website
appearing in search results, we want the title and the summary to have 2
main properties: (1) Provide search keywords to make it searchable by
potentially interested people; (2) Provide a title that immediately
signal that our website contains the information people are looking for.
Now, we need to understand what kind of people may be looking to
orgmode.org website.
1. Existing emacs users
If a Emacs user is faced with "Org mode for Emacs", the word "Emacs"
is indeed recognisable. On the other hand, the word "Org mode" does
not provide much further info, except that it is a major (or maybe
minor?) mode for "Org"??
Now, consider "Org mode: your life in plain text".
For emacs users, "Org mode" is not just a strange phrase, but a very
clear indication that we are talking about Emacs.
The "your life in plain text" provides extra information about what
"Org mode" refers to. Clearly, text documents and "your life in plain
text" should resonate with every Emacs user's soul.
We can change the second variant of the title to contain "Emacs", but
will it add much value? I am not convinced. On the other hand, making
title too long or too complex _is_ bad. Long titles tend to be
skipped (there was even formal research on this!)
2. Non-emacs users interested in plain text markup
These users know nothing about Emacs and "Org mode" has no meaning
for them as is. So, we do need something more descriptive.
Adding "Emacs" may be fine, but it will serve no purpose for people
not familiar with emacs. Just another unknown term making the title
longer.
3. Non-emacs users interested in GTD/project management, etc
"Org mode: your life in plain text" is somewhat relevant when people
are looking to manage "life" (typically true for GTD enthusiasts).
Though we can probably do better for this category.
Maybe "Org mode: manage your life and notes in plain text"?
Though it makes the title less relevant to group #2.
4. Researchers looking for ipython-like environment
Not covered, except by reading my proposed site summary. I am not
sure how we can improve title for this audience.
5. ??? (Suggestions are welcome)
Of course, better suggestions for the title are welcome. I just wanted
to make it clear the reasoning I do not like the current title and how
the proposed alternative is better (though not ideal).
Finally, I want to emphasise that our aim for search engines is not
advertising Emacs (we already do it by trapping users inside Org and
making them switch to Emacs by force :evil_laughter:). The aim is
encouraging people to use and contribute to Org mode in useful ways
(even unrelated to writing Elisp or, really, any code at all).
Search result is just an entrance for users to be curious about the new
beast of "Org mode". The website front page is the means to make users
try. And the Org mode itself is the way to make users fall in love with
Org in one way or another (even unrelated to Emacs [at least
initially]).
Best,
Ihor
next prev parent reply other threads:[~2021-12-05 12:07 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 7:35 Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal Ihor Radchenko
2021-12-05 9:16 ` Juan Manuel Macías
2021-12-05 10:24 ` Ihor Radchenko
2021-12-05 11:08 ` Juan Manuel Macías
2021-12-05 11:54 ` Heinz Tuechler
2021-12-05 12:08 ` Ihor Radchenko [this message]
2021-12-05 13:32 ` Tim Cross
2021-12-05 13:52 ` Bruce D'Arcus
2021-12-05 22:20 ` Tim Cross
2021-12-05 14:30 ` Ihor Radchenko
2021-12-05 22:39 ` Tim Cross
2021-12-08 13:47 ` Ihor Radchenko
2021-12-08 14:39 ` Tim Cross
2021-12-08 16:16 ` Dr. Arne Babenhauserheide
2021-12-08 17:07 ` Russell Adams
2021-12-08 19:22 ` Dr. Arne Babenhauserheide
2021-12-08 20:14 ` Russell Adams
2021-12-08 21:50 ` Tim Cross
2021-12-09 8:12 ` Dr. Arne Babenhauserheide
2021-12-08 21:25 ` Tim Cross
2021-12-09 8:07 ` Dr. Arne Babenhauserheide
2021-12-09 8:36 ` Timothy
2021-12-09 9:18 ` Ihor Radchenko
2021-12-09 10:46 ` Eric S Fraga
2021-12-09 15:21 ` Russell Adams
2021-12-09 16:25 ` Eric S Fraga
2021-12-09 21:15 ` Samuel Wales
2021-12-09 23:27 ` Dr. Arne Babenhauserheide
2021-12-10 2:42 ` Tim Cross
2021-12-10 6:08 ` Dr. Arne Babenhauserheide
2021-12-11 10:03 ` Ihor Radchenko
2021-12-11 21:19 ` Tim Cross
2021-12-06 19:41 ` Karl Voit
2021-12-05 18:59 ` Juan Manuel Macías
2021-12-05 23:24 ` Russell Adams
2021-12-06 5:57 ` Juan Manuel Macías
2021-12-06 6:02 ` Timothy
2021-12-06 7:24 ` Juan Manuel Macías
2021-12-06 10:04 ` Greg Minshall
2021-12-06 14:59 ` Juan Manuel Macías
2021-12-06 17:59 ` Tom Gillespie
2021-12-06 18:25 ` M. ‘quintus’ Gülker
2021-12-06 18:42 ` Russell Adams
2021-12-06 18:47 ` Timothy
2021-12-06 19:28 ` Russell Adams
2021-12-06 19:34 ` Timothy
2021-12-06 18:30 ` Russell Adams
2021-12-06 19:10 ` Gerry Agbobada
2021-12-08 12:56 ` Ihor Radchenko
2021-12-06 10:08 ` Greg Minshall
2021-12-06 19:45 ` Karl Voit
2021-12-07 11:08 ` Vincent Breton
2021-12-08 13:13 ` Ihor Radchenko
2021-12-08 13:30 ` Ihor Radchenko
2021-12-05 13:06 ` Tim Cross
2021-12-05 14:55 ` Ihor Radchenko
2021-12-05 18:54 ` Timothy
2021-12-06 11:08 ` Max Nikulin
2021-12-06 18:43 ` Russell Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lf0zb6fq.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).