emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy E Chapman <tecosaur@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: The Website Revamp: The final stretch
Date: Thu, 24 Sep 2020 00:00:51 +0800	[thread overview]
Message-ID: <CAHNg_jME8bdSBr-8PuCeCf9X1CU53kH=L-oYtPvkvnm0Tn_xFA@mail.gmail.com> (raw)
In-Reply-To: <875z85dlip.fsf@gnu.org>

Hi Bastien,

Just remembered I haven't addressed everything you mentioned here.

Bastien <bzg@gnu.org> wrote:

> Also, let's remove the mini-unicorn in the top bar, it is redundant
> and reminds me of the opening of IT Crowd.

Ah yes, I see the resemblance :P I'm not sure this is a good idea though, as
while this can be seen as redundant on the homepage, the navbar is used on
every page. Considering that this is a site to help people learn about Org,
I think that the visual consistency of having it on every page, and
how that helps reinforce the association between Org and that logo is worth it.
Having it regularly appear should help it stick.

> - I believe there are too many pages: I'd love the website to be just
>   one HTML page.  Rich contents should go to Worg and yes, we need to
>   upgrade Worg's design too. Let's try moving such contents to Worg as
>   soon as we can -- but this is not a blocker for the switch.

I think a single page might be a bit further than ideal, as I see it a
'core' of static pages
for orgmode.org would be
 - index/homepage
 - features
 - quickstart
 - install

How does that sound to you? Of course, all of this migration to Worg
can happen after an iniIal switch.

> - For the manual, I'd prefer to use the same design that the one used
>   on the gnu.org website:

This is quite easy (and not actually part of this branch), I think we
just need to pass
--css-ref "https://www.gnu.org/software/emacs/manual.css"
to the makeinfo/texi2any/texi2html command in
https://code.orgmode.org/bzg/org-mode/src/master/doc/Makefile

All the best,

Timothy.


  reply	other threads:[~2020-09-23 16:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 14:11 The Website Revamp: The final stretch TEC
2020-09-22 14:58 ` Palak Mathur
2020-09-22 15:10   ` TEC
2020-09-23 12:14     ` Eric S Fraga
2020-09-22 15:17 ` Stefan Nobis
2020-09-22 16:40   ` Devin Prater
2020-09-23  7:02     ` Bastien
2020-09-24 11:02     ` TEC
2020-09-24 13:01       ` Devin Prater
2020-09-24 16:34       ` Nick Dokos
2020-09-22 16:03 ` Nicolas Goaziou
2020-09-22 16:10   ` TEC
2020-09-22 20:38     ` Nicolas Goaziou
2020-09-22 17:22 ` Dominik Schrempf
2020-09-23  7:01 ` Bastien
2020-09-23 16:00   ` Timothy E Chapman [this message]
2020-09-24  9:52     ` David Arroyo Menendez
2020-09-24  9:55     ` David Arroyo Menendez
2021-04-27 20:30       ` Bastien
2021-04-27 20:35         ` Timothy
2021-04-27 21:24           ` Bastien
2020-09-23  7:08 ` Lars Chr. Duus Hausmann
2020-09-23 14:29 ` Takaaki Ishikawa
2020-09-24 11:25 ` Greg Newman
2020-09-24 13:20 ` TEC
2020-09-24 13:54   ` Palak Mathur
2020-09-24 16:39   ` Nick Dokos
2020-09-24 17:22     ` Carsten Dominik
2020-09-24 16:47   ` Tom Gillespie
2020-09-25  1:48   ` Ihor Radchenko
2020-09-25  2:06     ` Samuel Wales
2020-09-28 21:54       ` Leslie Watter

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='CAHNg_jME8bdSBr-8PuCeCf9X1CU53kH=L-oYtPvkvnm0Tn_xFA@mail.gmail.com' \
    --to=tecosaur@gmail.com \
    --cc=bzg@gnu.org \
    --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).