public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gnutools-advocacy@gcc.gnu.org,
	"Carlos O'Donell" <carlos@systemhalted.org>,
	 iains.gcc@gmail.com
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <CAGWvnykfxnOAG0hAiK_uhQF2pU6YbCjWj4dVNXgBi8iwjBHq0Q@mail.gmail.com> (raw)
In-Reply-To: <E58BF8CD-1BA0-4B22-8A87-2FC524E2E339@gmail.com>

I have updated the mock-up with a new, simple landing page with a link
for "Users" and a link for "Developers", and the previous information
page moved to dev.html.

https://edelsohn.github.io/gnutools/

We can expand the new landing page to a sleeker landing page similar
to e-commerce sites.

- David
On Fri, Oct 5, 2018 at 2:03 PM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> On October 5, 2018 7:36:48 PM GMT+02:00, Carlos O'Donell <carlos@systemhalted.org> wrote:
> >I'd rather see a consistent use and clear developer naming.
> >
> >e.g.
> >dev.gnutools.org / dev.gnu.tools / dev.gnutoolchain.org = Developer
> >landing page.
> >www.gnutools.org / www.gnu.tools / www.gnutoolchain.org = Marketing
> >landing page.
> >
> >Thoughts?
>
> Just make sure to make it easily possible to go from one to the other as people are going to land on the wrong one whatever scheme you end up with.
>
> So I'd do a single 'neutral' landing page with content targeting both.
>
> Richard.
>
> >
> >On Fri, Oct 5, 2018 at 1:33 PM David Edelsohn <dje.gcc@gmail.com>
> >wrote:
> >>
> >> We also have registered gnutools.org and gnutoolchain.org.
> >>
> >> Maybe gnutools.org for dev and gnutoolchain.org for marketing.
> >>
> >> - David
> >>
> >> On Fri, Oct 5, 2018 at 1:27 PM Carlos O'Donell
> ><carlos@systemhalted.org> wrote:
> >> >
> >> > 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 19:33 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               ` Alexandre Oliva
2018-01-01  0:00                 ` Richard Biener
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                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00               ` Richard Stallman
2018-01-01  0:00           ` Richard Stallman
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` Joseph Myers
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` David Edelsohn
2018-01-01  0:00       ` Carlos O'Donell
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00             ` David Edelsohn
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` David Edelsohn [this message]

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=CAGWvnykfxnOAG0hAiK_uhQF2pU6YbCjWj4dVNXgBi8iwjBHq0Q@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    --cc=richard.guenther@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).