History

Hector Ramos 5b79ee6808 Move tabbing logic back to individual docs Summary: In preparation for an upcoming website update, we need to host the tabbing logic used by Getting Started, Integration with Existing Apps, and Running on Device, in the individual documents themselves. The website update will allow us to use actual React components to implement this behavior. When the website update is live, we can work on the React alternative. Ran website, verified tabbing worked as expected in all three documents. Closes https://github.com/facebook/react-native/pull/15758 Differential Revision: D5758202 Pulled By: hramos fbshipit-source-id: bd00c6c2ac9377b4427022b30ca7ed7787eb3a86		2017-09-01 18:06:24 -07:00
..
core	Add "- React Native" to all pages title in doc section	2017-08-30 15:31:30 -07:00
jsdocs	remove disableAutomock from jest tests (new default) @bypass-lint	2017-06-13 15:04:09 -07:00
layout	creatClass codemod	2017-07-25 10:28:42 -07:00
server	Add Android React Native Checkbox	2017-08-25 10:30:54 -07:00
src/react-native	Move tabbing logic back to individual docs	2017-09-01 18:06:24 -07:00
.gitignore	Generate Atom feed for the React Native blog.	2016-10-28 13:28:37 -07:00
README.md	Update guidelines.	2017-06-14 15:16:59 -07:00
package.json	Remove unused npm dependencies and add missing ones	2017-07-08 01:45:01 -07:00
publish-gh-pages.js	shelljs/global -> shelljs	2017-07-12 16:08:22 -07:00
setup.sh	…
showcase.json	Add Skype to showcase	2017-08-18 18:45:29 -07:00

README.md

Install prerequisites

Before running the website, make sure you've run the following:

git clone https://github.com/facebook/react-native.git
cd react-native
npm install

Run the website server

The first time, get all the website dependencies loaded via

cd website
npm install

Then, run the server via

npm start
open http://localhost:8079/react-native/index.html

Anytime you change the contents, just refresh the page and it's going to be updated.

Publish the website

The website at https://facebook.github.io/react-native is automatically deployed by our continuous integration infrastructure, specifically CircleCI. This is configured in circle.yml in the root of the repository.