Tree: bb00e4d72e

lukechilds-patch-1

main

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'bb00e4d72e'

${ noResults }

Commit Graph

5 Commits (bb00e4d72ecb31b26c9711c439dab33e639b11e3)

Author	SHA1	Message	Date
Brian Vaughn	52b694eaae	Add new docs website (#10896) 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	7 years ago
Paul O’Shannessy	9b06b8838f	[docs] Give authors links.	10 years ago
Julen Ruiz Aizpuru	3ebec4b55b	Docs: do not render components to `document.body` Rendering to `document.body` in the examples is conveniently short, but it can be misleading at the same time, especially for newcomers. While it's possible to render React components to `document.body`, any 3rd party scripts can also mess up with it, and it can have unintended consequences and be source of difficult-to-trace bugs.	10 years ago
Paul O’Shannessy	efc42e8bf1	Default to layout: post for posts Just a little less boilerplate. This also removes a bit of trailing whitespace because it shouldn't have been there.	11 years ago
Paul O’Shannessy	7e824c875a	react-rails blog post	12 years ago