Skip to content
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

Add new docs website #10896

Merged
merged 232 commits into from Sep 28, 2017
Merged

Add new docs website #10896

merged 232 commits into from Sep 28, 2017

Conversation

bvaughn
Copy link
Contributor

@bvaughn bvaughn commented Sep 27, 2017

Adds a new docs website, built with Gatsby JS, to replace the old Jekyll site. Source code for the new site lives in /www (although markdown and YML data still comes from the legacy /docs folder).

Changes to either markdown or website source code can be previewed on Netlify. The react-js bot should automatically add comments to each PR with preview links. (This preview is generated by running the newly-added yarn build:docs command in the root package.json.)

The majority of the changes in this PR are contained within the new /www directory. However some minor modifications have been made to existing content in the /docs directory:

  • Modified frontmatter author block to always be an array
  • Small markdown formatting tweaks

I do have one open question about this PR though. In order to simplify the build script, I added a .nvmrc file to require Node v8.4.0. Is this acceptable? If it is frowned on for any reason, I can update the build script to remove the newer async/await syntax.

Once this PR has been merged, I'll update Netlify and set master as the main branch for the website. Then to make it live (more live) we can merge something like #10856 and push out one final update to gh-pages.

Brian Vaughn and others added 30 commits June 30, 2017 09:49
…avior on wider pages (like Typechecking with PropTypes)
…ehavior out of component in favor of using 'react-sticky' lib
@flarnie
Copy link
Contributor

flarnie commented Sep 27, 2017

Looks like we lost - id: react-dom-node-stream... title: ReactDOMNodeStream from docs/_data/nav_docs.yml. Not sure that was intentional.

@gaearon
Copy link
Collaborator

gaearon commented Sep 27, 2017

It shouldn't be there. (We should make sure it doesn't get added back.)

@flarnie
Copy link
Contributor

flarnie commented Sep 27, 2017

Great - docs/docs/reference-react-dom-node-stream.md was removed as expected then.

@flarnie
Copy link
Contributor

flarnie commented Sep 27, 2017

Read through all the changes to /docs and lgtm :)

lgtm_silly_cat

@flarnie flarnie self-requested a review September 27, 2017 22:21
Copy link
Contributor

@flarnie flarnie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd love as many eyes on this as possible, but since all the commits that went into this were already reviewed, and I reviewed the changes to /docs, I think this is good to go whenever.

Of course we should merge at a well chosen time. 😁

@flarnie
Copy link
Contributor

flarnie commented Sep 27, 2017

I'm going to work on some of the easy a11y fixes that we need, but I'll wait to open a PR untilo after this is merged, so that you don't need to re-do this PR to get the changes in.

{
resolve: `gatsby-remark-images`,
options: {
maxWidth: 800,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maxWidth of the main content div is 840px

{
resolve: `gatsby-plugin-google-analytics`,
options: {
//trackingId: `ADD YOUR TRACKING ID HERE`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs copied over from the existing site (I'm assuming you're using Google Analytics — if not remove this)

@KyleAMathews
Copy link
Contributor

KyleAMathews commented Sep 27, 2017

Two quick plugins you might want to add.

@KyleAMathews
Copy link
Contributor

We use both of those on gatsbyjs.org

import ExternalLinkSvg from 'templates/components/ExternalLinkSvg';

const FooterLink = ({children, target, to}) => (
<a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should use gatsby-link for internal links — probably the cause of #10898

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I suspected that was the case but hadn't had time to dig in yet. Thanks.

@bvaughn
Copy link
Contributor Author

bvaughn commented Sep 28, 2017

Two quick plugins you might want to add.

Cool, thanks. There are follow-up issues (some on a wiki, gradually converting them to GitHub issues) where gatsby-plugin-nprogress is already added. I'll list gatsby-plugin-twitter too. 😄

@bvaughn
Copy link
Contributor Author

bvaughn commented Sep 28, 2017

I'm going to work on some of the easy a11y fixes that we need, but I'll wait to open a PR untilo after this is merged, so that you don't need to re-do this PR to get the changes in.

Thanks @flarnie !

This fixes the scrollTop offset issue reported in #10898
@bvaughn
Copy link
Contributor Author

bvaughn commented Sep 28, 2017

I just read through all of the PR feedback. (Thanks! ❤️ ) I think I've made all suggested changes.

Unless I hear differently, I will merge this PR sometime this morning. Please let me know if you'd like additional time to review.

gaearon and others added 3 commits September 28, 2017 17:46
* Added gatsby-plugin-nprogress for slow-loading pages (eg Blog)

* Set progress bar color to match React site theme

* Updated Gatsby for Blog redirect delay fix
@bvaughn bvaughn merged commit 96fde8a into master Sep 28, 2017
@bvaughn
Copy link
Contributor Author

bvaughn commented Sep 28, 2017

Thank you everyone for your helpful review commits and tweaks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants