Gatsby: [www][v1] Link to next.gatsbyjs.org
I had the honor to participate in a UX interview conducted by @shannonbux today 🎉and the interviewee mentioned that he used Google search to find the documentation for Gatsby v2.
My guess is that adding a banner similar to the one on https://next.gatsbyjs.org/ would resolve that issue. Do we want to push v2 and its docs this way (and at this point)?
/cc @KyleAMathews @m-allanson @pieh @calcsam
fk
All 23 comments
Yes, he also mentioned trying to navigate to next.gatsbyjs.org by
navigating to gatsbyjs.org and then adding "next." into the URL, which
doesn't work. https://www.next.gatsbyjs.org/ returns an error.
Is that worth making an issue about? We could somehow redirect people if
they try to do that?
On Tue, Jul 3, 2018 at 10:06 AM, Florian Kissling notifications@github.com
wrote:
I had the honor to participate in a UX interview conducted by @shannonbux
https://github.com/shannonbux today 🎉and the interviewee mentioned
that he used Google search to find the documentation for Gatsby v2.My guess is that adding a banner similar to the one on
https://next.gatsbyjs.org/ would resolve that issue. Do we want to push
v2 and its docs this way (and at this point)?/cc @KyleAMathews https://github.com/KyleAMathews @m-allanson
https://github.com/m-allanson @pieh https://github.com/pieh @calcsam
https://github.com/calcsam—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276, or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2sn3lS10KvTfuHYJ0KWiAmidkQVWks5uC5ZpgaJpZM4VBO5M
.
shannonbux
on 3 Jul 2018
Makes sense! We're getting closer to v2 so good to start pushing people that way. Also seen a number of questions from people wondering how to try out v2 so it's definitely not obvious right now.
KyleAMathews
on 3 Jul 2018
If anyone would like to take this on, you'd need to check out the v1 branch of this repo. Then check these two PRs to see how the banner is implemented on next.gatsbyjs.org:
https://github.com/gatsbyjs/gatsby/pull/6161
https://github.com/gatsbyjs/gatsby/pull/5915
A "stretch goal" would be to create a configurable standalone banner component (or local plugin?) and then port that back to the v1 branch.
m-allanson
on 4 Jul 2018
@martynhoyer this is what we talked about in our chat today!
shannonbux
on 6 Jul 2018
I'm up for this, and would try the "stretch goal".
I'm happy to give the local plugin a shot, too, but wondering what the benefits of this over a component would be?
Also I've been thinking about the copy that we'd need for the v1 site—I'm thinking it'd need to be a little longer than what we currently have for v2 at https://next.gatsbyjs.org/:
Even for that very concise message, we're currently hiding parts to make things fit on a 320px-wide screen to avoid all those position:fixed problems with the header:
For v1, I'm thinking the message could be s/th along the lines of "We're working hard on Gatsby v2—head over to next.gatsbyjs.org for the v2 docs and read the v2 beta blog post!". What do people think about this?
To make things fit on mobile/320px-wide screens, we could break that down to just "v2 beta docs / blog post", but maybe we should think about how to handle either any amount of "one-line content" or _really any amount of content_ here.
fk
on 9 Jul 2018
I'm happy to give the local plugin a shot, too, but wondering what the benefits of this over a component would be?
I guess my thinking behind this was - to be able to switch the banner on and off without needing to go through and edit CSS in the files that need to know the header height. But I'm not sure that that's a good idea, as it doesn't particularly make things clearer.
m-allanson
on 10 Jul 2018
Oops,... I was late by 7 hours
munwr
on 10 Jul 2018
👋Hey @munwr, thanks for looking into this! 🤗
6363 is just moving the banner to a component for www on master, so no reason to abandon your PR (#6370)! I won't get back to this for at least the next 24hrs. Would be 💪 if you could port the component from #6363, but that's nothing to hold off #6370 either (IMO)!
fk
on 10 Jul 2018
Hi,
We are saying in banner "view docs", But linking it to respective version's home page. Would it be better if we can directly land them in their respective docs?
@fk @shannonbux
munwr
on 12 Jul 2018
ah, good point. I'd say let's link to the docs, since the homepage is
exactly the same on each version of the site. This shows how language is
confusing because "the docs" could either refer to the whole gatsbyjs.org
site OR just gatsbyjs.org/docs/.
@fk, what do you think?
On Thu, Jul 12, 2018 at 8:22 AM, Munawar Ahmed notifications@github.com
wrote:
Hi,
We are saying in banner "view docs", But linking it to respective
version's home page. Would it be better if we can directly land them in
their respective docs?@fk https://github.com/fk @shannonbux https://github.com/shannonbux
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404529502,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2k8F-ULdGRj2s4vmhGpBbx8EMXguks5uF1uWgaJpZM4VBO5M
.
shannonbux
on 12 Jul 2018
jlengstorf
on 12 Jul 2018
I think I would expect that link to go straight to the migration guide. If we did that, we'd want to edit the migration guide to say something at the top like "Note: this entire site is on next.gatsbyjs.org, the v2 docs site. See v1 docs here". This would help people who don't see the banner.
How much longer will we have next.gatsbyj.org? It will be nice when we don't have 2 sites...
shannonbux
on 12 Jul 2018
Oh, good call @shannonbux!
I agree that we should link to https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/
How about this text?
Gatsby v2 is now in beta! Upgrade to v2 today.
jlengstorf
on 12 Jul 2018
This would be really useful, I actually asked @jlengstorf for this link. So, I can upgrade to v2. When I visited V2 docs did not know where to look. maybe we can have a link near/in the quick start menu
munwr
on 12 Jul 2018
Sounds good!
On Thu, Jul 12, 2018 at 11:16 AM, Jason Lengstorf notifications@github.com
wrote:
Oh, good call @shannonbux https://github.com/shannonbux!
I agree that we should link to https://next.gatsbyjs.org/
docs/migrating-from-v1-to-v2/How about this text?
Gatsby v2 is now in beta! Upgrade to v2 today.
https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404585032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2mrTl9n_gdUuX_412PR-K6XZVBhvks5uF4RogaJpZM4VBO5M
.
shannonbux
on 12 Jul 2018
PS we just merged a PR so there will be a category called "Migrations &
Versions" as soon as that builds on next.gatsbyjs.org so it ought to be way
easier to find :)
On Thu, Jul 12, 2018 at 11:26 AM, Munawar Ahmed notifications@github.com
wrote:
This would be really useful, I actually asked @jlengstorf
https://github.com/jlengstorf for this link. So, I can upgrade to v2.
When I visited V2 docs did not know where to look. maybe we can have a link
near/in the quick start menu—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404588073,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2otpMhOx1lHtQlEiYvAynRk81JdRks5uF4bbgaJpZM4VBO5M
.
shannonbux
on 12 Jul 2018
Hm, just thinking what if we link to both the docs and migration guide like
so:
Gatsby v2 is now in beta! Upgrade to v2 today
https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/ and visit the v2
docs site https://next.gatsbyjs.org/.
On Thu, Jul 12, 2018 at 12:32 PM, Shannon Soper shannon@gatsbyjs.com
wrote:
PS we just merged a PR so there will be a category called "Migrations &
Versions" as soon as that builds on next.gatsbyjs.org so it ought to be
way easier to find :)On Thu, Jul 12, 2018 at 11:26 AM, Munawar Ahmed notifications@github.com
wrote:This would be really useful, I actually asked @jlengstorf
https://github.com/jlengstorf for this link. So, I can upgrade to v2.
When I visited V2 docs did not know where to look. maybe we can have a link
near/in the quick start menu—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404588073,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2otpMhOx1lHtQlEiYvAynRk81JdRks5uF4bbgaJpZM4VBO5M
.
shannonbux
on 13 Jul 2018
Hmm both don't seem necessary because the migration guide is in the middle of the docs.
KyleAMathews
on 13 Jul 2018
Well, people might not notice the beginning of the URL changed so the link
isn't so much for them to click, but just to clue them in on the fact that
they're going to a new site...that looks essentially identical ;).
So maybe "Gatsby v2 is now in beta! Upgrade to v2 today
https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/ (link will take
you to v2 docs site)" or something like that
On Thu, Jul 12, 2018 at 8:01 PM, Kyle Mathews notifications@github.com
wrote:
Hmm both don't seem necessary because the migration guide is in the middle
of the docs.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404703056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2rXuX9QGXbUIHxIe1d3e-fad7vmSks5uF_-UgaJpZM4VBO5M
.
shannonbux
on 13 Jul 2018
Point to migration guide directly would be very helpful. Someone is already using v1. this could be the right place for them to start. if they are looking to migrate to v2.
So maybe "Gatsby v2 is now in beta! Upgrade to v2 today
https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/ (link will take
you to v2 docs site)" or something like that
munwr
on 13 Jul 2018
I think @munwr makes a good point: many people who see that banner will be migrating sites, and anyone who isn't will be looking at the v2 docs after clicking through.
Maybe we could add a call out at the top of the migration guide, like, "Starting from scratch? Follow the tutorial to get started with Gatsby V2!"
That could help give a thread to follow for new users while emphasizing the upgrade path.
What do you think?
jlengstorf
on 13 Jul 2018
Yeah, that sounds great @jlengstorf! Just did it in this commit
https://github.com/gatsbyjs/gatsby/commit/0933d6035cb5182c9818c4f41bed114eeceb2df7
though maybe it could be more obvious.
On Fri, Jul 13, 2018 at 8:48 AM, Jason Lengstorf notifications@github.com
wrote:
I think @munwr https://github.com/munwr makes a good point: many people
who see that banner will be migrating sites, and anyone who isn't will be
looking at the v2 docs after clicking through.Maybe we could add a call out at the top of the migration guide, like,
"Starting from scratch? Follow the tutorial to get started with Gatsby V2!"That could help give a thread to follow for new users while emphasizing
the upgrade path.What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/6276#issuecomment-404855658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9o2l9A-Goh1IkT3OWtBjo3VlcaivQdks5uGLNAgaJpZM4VBO5M
.
shannonbux
on 13 Jul 2018
Done!
KyleAMathews
on 8 Sep 2018
Related issues
magicly
·
3Comments
jimfilippou
·
3Comments
rossPatton
·
3Comments
benstr
·
3Comments
hobochild
·
3Comments