From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Website revamp?
Date: Thu, 6 Aug 2020 18:25:42 +0700 [thread overview]
Message-ID: <rggpbn$v8l$1@ciao.gmane.io> (raw)
In-Reply-To: <87y2mt2s8v.fsf@gmail.com>
05.08.2020 19:03, TEC wrote:
> Maxim Nikulin <manikulin@gmail.com> writes:
>
>> Sorry, but "An innovative and intuitive plain text markup syntax" means nothing
>> to me. "Created by Carsten Dominik in 2003" is a sign of mature and stable
>> enough software without disgusting "since ..." but contradicts a bit with
>> "innovative".
>
> Good to know. I'd be interested in hearing more thoughts on this, but for now
> here are my own:
> - innovative :: does 'new' and exciting things that similar products don't
This is the most "offensive" word for me. Minor issue is that 2003 means
17 years ago, not new, but really I consider the age as an advantage. I
admit that the word could be must have for startup fund raising but it
is so general that usually I consider it as an alarm that it could be
used just to inflate a phrase when nothing particular could be said
fairly. It could increase rating only if reputation of person who
mentioned it is known. It seems it is not only my perception:
https://www.urbandictionary.com/define.php?term=innovative
> - intuative :: despite doing a lot, it isn't complex to work with, but
> thoughtfully designed to be easy to use
Actually, I do not mind against "intuitive". Frankly speaking, I have
not noticed it at all. "Innovative" caused a kind of temporary
blindness. Do not take the following seriously. Every forum/wiki/bug
tracker engine has its own peculiarities in markup requiring a special
kind of intuition (even before introducing of WYSITYG feature). Old
joke: ... with intuitive interface has been automatically upgraded,
please, download upgrade your intuition from the site ... It is
unrelated to org-mode, I consider its markup syntax as mostly convenient.
>> In a "full" version my suggestion is to minimize amount of text significantly
>> larger than 1em. 4em is excessively huge font for normal monitor. I am in doubt
>> it is feasible to require readable but not oversized font on mobile devices,
>> 1366x768px laptops, and 4k monitors simultaneously.
>
> I take it you mean 1em to be the body text size, and are just referring to the
> size of headings? Or do you mean 1rem?
> The body text is currently ~1.2rem FYI.
There is a mix of em's and rem's, My complains are for desktop version
only. Text size of 1.2em below the banner is OK for me. 4em for
"Org-mode" is excessively huge for me. 3rem=2.7em for "An innovative" is
too large as well. 2rem for a couple of paragraphs in the banner
("Designed to...") is too heavy in comparison to 1.2rem=1em in the
banner bottom line.
>> On the other hand, I hope, donate links work but in new design thy are not
>> contrast and eye catching enough despite their colors.
>
> Interesting that you should say this, personally I find them more eye-catching
> than the current grey box in the corner.
I am comparing with widely used yellow "donate" paypal button. On the
current site the block is more noticeable due to "irregularity" of its
placement. In new variant small text is smoothly put to the banner
bottom line somewhere after other text.
>> I see 3 category of users requiring content different to some extent but should
>> be easily recognizable:
>
> Mmmm. This is a good point. The essential details are communicated by the
> current large banner IMO
I am trying to say that most of the points should be addressed outside
of the banner. My personal opinion is that the banner is overloaded already.
next prev parent reply other threads:[~2020-08-06 11:29 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 13:55 Website revamp? TEC
2020-07-30 13:00 ` TEC
2020-07-30 13:20 ` Russell Adams
2020-07-30 13:36 ` Amin Bandali
2020-07-30 14:19 ` TEC
2020-07-30 14:47 ` Bruce D'Arcus
2020-07-30 15:53 ` Amin Bandali
2020-07-30 17:22 ` Russell Adams
2020-07-30 17:57 ` TEC
2020-07-30 19:03 ` Russell Adams
2020-08-01 8:15 ` TEC
2020-08-02 18:08 ` TEC
2020-08-03 5:10 ` Colin Baxter
2020-08-03 5:11 ` TEC
2020-08-03 7:01 ` Colin Baxter
2020-08-03 7:53 ` TEC
2020-08-03 8:03 ` tomas
2020-08-04 5:54 ` Eric S Fraga
2020-08-05 10:17 ` Bo Grimes
2020-08-05 10:26 ` Eric S Fraga
2020-08-05 10:40 ` Bo Grimes
2020-08-05 10:43 ` TEC
2020-08-03 10:54 ` Gustav Wikström
2020-08-04 15:48 ` Maxim Nikulin
2020-08-04 15:53 ` TEC
2020-08-04 16:18 ` Bruce D'Arcus
2020-08-04 16:23 ` TEC
2020-08-04 16:30 ` Bruce D'Arcus
2020-08-05 11:56 ` Maxim Nikulin
2020-08-05 12:03 ` TEC
2020-08-06 11:25 ` Maxim Nikulin [this message]
2020-08-06 11:52 ` TEC
2020-08-24 7:43 ` TEC
2020-08-25 10:28 ` Maxim Nikulin
2020-08-25 12:02 ` TEC
2020-08-25 15:09 ` TEC
2020-08-27 16:09 ` Maxim Nikulin
2020-09-01 16:39 ` TEC
2020-09-30 16:24 ` Maxim Nikulin
2020-08-11 15:24 ` Maxim Nikulin
2020-08-04 15:53 ` Bruce D'Arcus
2020-08-04 16:09 ` TEC
2020-08-04 21:43 ` Bo Grimes
2020-08-05 15:24 ` Maxim Nikulin
2020-08-05 16:00 ` TEC
2020-08-07 5:19 ` David Rogers
2020-08-04 5:59 ` Eric S Fraga
2020-08-04 6:27 ` TEC
2020-08-04 20:44 ` gyro funch
2020-08-24 15:39 ` Maxim Nikulin
2020-07-30 19:40 ` Scott Randby
2020-09-01 16:44 ` TEC
2020-09-01 18:07 ` Tom Gillespie
2020-09-01 18:11 ` Tom Gillespie
2020-09-02 3:48 ` TEC
2020-09-02 2:59 ` TEC
2020-09-04 9:37 ` Bastien
2020-09-05 9:08 ` Martin Schöön
2020-09-05 10:16 ` Colin Baxter
2020-09-07 17:24 ` TEC
2020-09-07 18:13 ` TEC
2020-09-08 5:41 ` Tom Gillespie
2020-09-08 5:49 ` TEC
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='rggpbn$v8l$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).