This website requires JavaScript.
Explore
Help
Sign In
status-im
/
react-native
Watch
2
Star
0
Fork
0
You've already forked react-native
mirror of
https://github.com/status-im/react-native.git
synced
2025-01-10 09:35:48 +00:00
Code
Issues
Projects
Releases
Wiki
Activity
react-native
/
website
/
.gitignore
7 lines
96 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Initial version of the automatically generated docs
2015-02-12 14:43:41 -08:00
src/react-native/docs/**
Introduce blog Summary:Ported the infrastructure from jest.  Closes https://github.com/facebook/react-native/pull/6629 Differential Revision: D3094423 Pulled By: vjeux fb-gh-sync-id: a01aec6a55d28484c45bb241d037ca6717bc5e81 shipit-source-id: a01aec6a55d28484c45bb241d037ca6717bc5e81
2016-03-24 14:10:15 -07:00
src/react-native/blog/**
core/metadata*
Generate Atom feed for the React Native blog. Summary: An Atom feed is now generated as part of the build script. This is done statically and not as a React view because React is not the right tool for generating XML documents. Some additional metadata is stored in `metadata-blog.js` and duplicated to `metadata-blog.json` in the `server/` directory to aid in the generation of the feed. Let me know if there's a better way to import this data using the existing Haste module that wouldn't require writing an additional JSON file. The feed will be available at https://facebook.github.io/react-native/blog.xml A sample output of the Atom feed is included at the bottom. It is a [valid Atom 1.0 feed](https://validator.w3.org/feed/check.cgi), with some additional recommendations that can be ignored for now. > Congratulations! > > [Valid Atom 1.0] This is a valid Atom 1.0 feed. > Recommendations > > This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations. > line 2, col Closes https://github.com/facebook/react-native/pull/10611 Differential Revision: D4097381 Pulled By: mkonicek fbshipit-source-id: 8d2e18923358d1903b2715b00c48680b0c4dff68
2016-10-28 13:27:33 -07:00
server/metadata*
Add *.log to website directory
2015-05-04 02:32:20 +03:00
*.log
CI now builds docs website and deploys it to /%version% path Summary: Copy of #5760 reverted merge. We need to preserve history of docs changes on the webserver. The goal is to allow users to browse outdated versions of docs. To make things simple all websites will be released to https://facebook.github.io/react-native/releases/version/XX folder when there is a branch cut. I switched from Travis CI to Cirle CI because it works faster and I am more familiar with it. How it works: 1. If code is pushed to `master` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/next folder. Github will serve this website from https://facebook.github.io/react-native/releases/version/next URL. All relative URLs will work within that website 2. If code is pushed to `0.20-stable` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/0.20 folder. Github will serve this website from https://facebook.github.io/react-native/releases/v Closes https://github.com/facebook/react-native/pull/5873 Reviewed By: svcscm Differential Revision: D2926901 Pulled By: androidtrunkagent fb-gh-sync-id: 16aea430bac815933d9c603f03921cc6353906f1 shipit-source-id: 16aea430bac815933d9c603f03921cc6353906f1
2016-02-11 06:16:34 -08:00
/build/
Reference in New Issue
Copy Permalink
