From: TEC <tecosaur@gmail.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: New website - back to the old unicorn!
Date: Mon, 26 Oct 2020 22:26:09 +0800 [thread overview]
Message-ID: <871rhl6otn.fsf@gmail.com> (raw)
In-Reply-To: <4cccb119-3855-9e9c-e123-019900c9b30e@grinta.net>
Daniele Nicolodi <daniele@grinta.net> writes:
> I like the new design. Thank you for your work!
Thanks for the kind words!
> Two things:
*cough, Three 😆
> - in Firefox on a macOS machine, the colophon renders as "Made
> with XX
> by TEC" with the XX being an Unicode replacement character. What
> is it
> supposed to be?
Currently a brown heart, though I've actually had a better, less
tacky
idea. You'll see it in a day or two ;)
> - (minor) I would add a background to the example in the home
> page to
> make it stand out more as an example org-mode syntax buffer
Hmm, I've got mixed feelings about that. I kinda like how smoothly
it
fits in at the moment, and I wouldn't want to jeopardise that. If
we can
have it fit in smoothly, and more clearly be a example that would
be
great though :)
> - (very minor) why does the example on the home page need to be
> an SVG
> file? It would be very cool if it could be copy and pasted, but
> right
> now it is not possible (with Firefox, at least)
That sounds like a good idea! I'll see if I can do that
(medium-term).
PRs welcome as usual of course 😛
Thanks for the feedback,
Timothy.
next prev parent reply other threads:[~2020-10-26 14:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 9:41 New website - back to the old unicorn! Bastien
2020-10-26 9:44 ` TEC
2020-10-26 10:27 ` TEC
2020-10-26 10:51 ` Leo Vivier
2020-10-26 10:53 ` TEC
2020-10-26 13:32 ` gyro funch
2020-10-26 14:03 ` TEC
2020-10-26 13:54 ` Daniele Nicolodi
2020-10-26 14:26 ` TEC [this message]
2020-10-26 14:38 ` Daniele Nicolodi
2020-10-26 14:32 ` Daniele Nicolodi
2020-10-26 14:33 ` TEC
2020-10-26 14:51 ` Eric S Fraga
2020-10-26 17:14 ` TEC
2020-10-26 17:39 ` Tom Gillespie
2020-10-27 8:20 ` Eric S Fraga
2020-10-28 12:25 ` TEC
2020-10-28 15:40 ` Daniele Nicolodi
2020-10-28 15:58 ` Ken Mankoff
2020-10-28 16:59 ` TEC
2020-10-28 17:11 ` Daniele Nicolodi
2020-10-28 18:18 ` Stefan Nobis
2020-10-28 19:15 ` TEC
2020-10-29 8:00 ` Stefan Nobis
2020-10-28 16:58 ` Dante Catalfamo
2020-10-26 10:34 ` stardiviner
2020-10-27 11:01 ` JRSS
2020-10-27 11:05 ` TEC
2020-10-27 14:14 ` Leslie Watter
2020-10-26 13:04 ` Detlef Steuer
2020-10-26 10:11 ` Carsten Dominik
2020-10-26 10:19 ` Carsten Dominik
2020-10-26 11:05 ` Jude DaShiell
2020-10-26 10:22 ` Bastien
2020-10-26 10:19 ` John Herrlin
2020-10-26 10:39 ` Bastien
2020-10-26 14:16 ` Nick Dokos
2020-10-26 14:19 ` TEC
2020-10-26 15:02 ` Nick Dokos
2020-10-26 15:59 ` Jude DaShiell
2020-10-26 14:11 ` Jack Kamm
2020-10-26 16:28 ` Diego Zamboni
2020-10-26 16:54 ` Dante Catalfamo
2020-10-26 17:08 ` Greg Newman
2020-10-26 17:24 ` Neil Cherry
2020-10-26 18:22 ` Scott Randby
2020-10-27 7:15 ` Carsten Dominik
2020-10-27 8:23 ` Eric S Fraga
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=871rhl6otn.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=daniele@grinta.net \
--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).