-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stub Articles and new names #7200
Conversation
@calcsam I think we'll need to use some redirects for these new names, correct? If so, I'm happy to learn from someone how to do that or assign it to someone. Tell me which one you think makes sense!
Deploy preview for gatsbyjs failed. Built with commit 90bed13 https://app.netlify.com/sites/gatsbyjs/deploys/5b6df33db13fb113484cc4bd |
Deploy preview for using-postcss-sass failed. Built with commit 90bed13 https://app.netlify.com/sites/using-postcss-sass/deploys/5b6df33eb13fb113484cc4c8 |
Deploy preview for using-drupal ready! Built with commit 90bed13 |
Deploy preview for gatsbygram ready! Built with commit 90bed13 |
#6810 Wondering where to put this doc in the left hand sidebar.
Deploy preview for using-contentful failed. Built with commit c5f32f9 https://app.netlify.com/sites/using-contentful/deploys/5b6cc14a73f2cf648dd3de0a |
Deploy preview for using-glamor failed. Built with commit c5f32f9 https://app.netlify.com/sites/using-glamor/deploys/5b6cc14973f2cf648dd3de06 |
- GraphQL learning curve is one of the top 3 pain points of Gatsby users | ||
- GraphQL learning curve drives many people away from Gatsby | ||
- Many people think GraphQL is a requirement for using Gatsby, which isn't true | ||
- Probably 5% need GraphQL but we're making 100% of them go through GraphQL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
who is "we" here? sentence structure
@shannonbux for redirects take a look at https://github.com/gatsbyjs/gatsby/blob/master/examples/using-redirects/gatsby-node.js#L21-L26 you'll want to put this in |
ok @calcsam hope I did this correctly!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @shannonbux!
I guess these stubs will also need to be added to the sidebar? We can do that in a follow up PR though.
* master: (597 commits) Add a site(https://mojaave.com) to showcase list (gatsbyjs#7275) feat: create a doc for open source pair programming sessions (gatsbyjs#7266) [docs] Add video lesson to the StaticQuery docs (gatsbyjs#7249) [v2] docs - update page query docs (gatsbyjs#7285) [v2] docs "Styling" overview (gatsbyjs#7288) Remove delay (gatsbyjs#7273) add site (gatsbyjs#7291) Adding new site to the showcase. (gatsbyjs#7281) chore(release): Publish initial webpack externals support (gatsbyjs#7245) add missing package dependencies (gatsbyjs#7259) add: custom configuration overview (gatsbyjs#7231): tutorial part four updates (gatsbyjs#7240) [www] Fix showcase search, checkbox styles (gatsbyjs#7014) (gatsbyjs#6584): Restructure plugin overview and plugin authoring pages (gatsbyjs#7229) Use Hubspot form for email subscription (gatsbyjs#7233) Adding bootstrap CV starter (gatsbyjs#7207) Stub Articles and new names (gatsbyjs#7200) Improve readability of verbose logging code in wordpress source plugin (gatsbyjs#7146) Update hash link to scroll to right section of page (gatsbyjs#7161) ...
* Stub Articles and new names @calcsam I think we'll need to use some redirects for these new names, correct? If so, I'm happy to learn from someone how to do that or assign it to someone. Tell me which one you think makes sense! * Where to put this in the sidebar? gatsbyjs#6810 Wondering where to put this doc in the left hand sidebar. * redirect for `/netlify-cms/` ok @calcsam hope I did this correctly!
@calcsam I think we'll need to use some redirects for these new names, correct?
If so, I'm happy to learn from someone how to do that or assign it to someone. Tell me which one you think makes sense!
This finishes up work from #7121