public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: iains.gcc@gmail.com, gnutools-advocacy@gcc.gnu.org
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <CAE2sS1gj2MkbN16g5XCGPMtzvfnq04yw1u-SPU_tsfXBVTYhMA@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnynBRm06NsPLnu101i6V8dDYZqh_bVe5W7NXzf0sjcEXgg@mail.gmail.com>

On Fri, Oct 5, 2018 at 10:16 AM David Edelsohn <dje.gcc@gmail.com> wrote:
>
> I propose that we want to target two different audiences and, as a
> stretch goal, want two distinct web sites.
>
> 1) A focal point for users and developers to access information.
>
> 2) A marketing landing page with testimonials, like a startup
> e-commerce landing page.
>
> They can be combined, but each has a different style and feel.

A high level marketing landing page with slick graphics feels like it
should be the first thing you see.

Followed by a  "developer" button for developers to jump into a sub-page.

However... some companies split this in two.

See for example:

https://www.wix.com/

vs.

https://dev.wix.com/

There is almost no overlap between the two sites. You have to scroll
to the very bottom of the first page and click "Developers" under
"Product" get to dev.wix.com, *but* Google searches can take you
directly to dev.wix.com.

We have registered gnu.tools, so we could also use dev.gnu.tools to
take you to a developer facing page vs. www.gnu.tools which takes you
to a marketing landing page?

Cheers,
Carlos.

  reply	other threads:[~2018-10-05 17:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  0:00 Iain Sandoe
2018-01-01  0:00 ` Carlos O'Donell
2018-01-01  0:00   ` Alexandre Oliva
2018-01-01  0:00     ` Carlos O'Donell
2018-01-01  0:00       ` Alexandre Oliva
2018-01-01  0:00       ` Richard Stallman
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Alexandre Oliva
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` Richard Stallman
2018-01-01  0:00               ` Alexandre Oliva
2018-01-01  0:00                 ` Richard Biener
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                     ` David Edelsohn
2018-01-01  0:00                       ` Alexandre Oliva
2018-01-01  0:00                         ` David Edelsohn
2018-01-01  0:00                           ` Alexandre Oliva
2018-01-01  0:00           ` Richard Stallman
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` David Edelsohn
2018-01-01  0:00       ` Carlos O'Donell [this message]
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` David Edelsohn
2018-01-01  0:00             ` David Edelsohn
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` Joseph Myers

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE2sS1gj2MkbN16g5XCGPMtzvfnq04yw1u-SPU_tsfXBVTYhMA@mail.gmail.com \
    --to=carlos@systemhalted.org \
    --cc=dje.gcc@gmail.com \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    /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.
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).