From: TEC <tecosaur@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Website revamp?
Date: Tue, 04 Aug 2020 14:27:51 +0800 [thread overview]
Message-ID: <877due52hd.fsf@gmail.com> (raw)
In-Reply-To: <87wo2f7xyh.fsf@ucl.ac.uk>
Good to hear from you!
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I do like the animated images in the features page!
Glad you like them! I recently converted the static images to SVGs
with the help of someone using Emacs27 w/ Cairo, would be nice go
do something like an animated SVG in the future, but that's for
(much) later :P
>I do wonder about
> the order of the topics within that page, e.g. working with
> source code, although powerful, is probably not the lead item
> for new users. However, that's a minor point at this stage.
Thanks for this feedback. I prioritised the source code blocks
because:
a) my impression is that to Comp/Data Sci people, they are one of
/the/ most
compelling features of Org-mode
b) they're similar to elements people are familiar with (Jupyter
notebooks, R markdown), so the Comp/Data Sci segment of our
audience is already roughy familiar with part of their
capabilities
I shifted the agenda/capture/clocking/etc. features down because
a) they semantically seem like they should go together b) having
them near the top pushes down too many other features too much,
IMO
Absolutely worth considering the order, please share any further
thoughts you may have :)
> More generally, can the column width for the text be a function
> of the window width and have images scaled so that they are not
> wider than the text column? It should be possible to have
> mobile friendly without making the columns too narrow for full
> desktop use. The fact that the images are much wider than the
> text makes the page look ugly, in my opinion.
The column width already is. I just find long lines undesirable.
50-80 characters is the standard in publishing for a reason.
To quote from /The Elements of Typographic Style/,
> Anything from 45 to 75 characters is widely regarded as a
> satisfactory line length of line for a single-column page set in
> a serifed text face in a text size. The 66-character line
> (counting both letters and spaces) is widely regarded as ideal.
> For multiple-column work, a better average is 40 to 50
> characters. If the type is well set and printed, lines of 85 or
> 90 characters will pose no problem in discontinuous texts, such
> as bibliographies, or, with generous leading, in footnotes. But
> even with generous leading, a line that averages more than 75 or
> So characters is likely to be too long for continuous reading.
There's more to be said about line spacing and the reasons for
this - if I recall correctly /A practical guide to typography/
(available online) goes over this.
I look forward to hearing any further comments you may have!
Timothy.
next prev parent reply other threads:[~2020-08-04 6:50 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
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 [this message]
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=877due52hd.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).