5b79ee6808
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 |
||
---|---|---|
.. | ||
core | ||
jsdocs | ||
layout | ||
server | ||
src/react-native | ||
.gitignore | ||
README.md | ||
package.json | ||
publish-gh-pages.js | ||
setup.sh | ||
showcase.json |
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.