14 Commits

Author	SHA1	Message	Date
Hector Ramos	11707d5ce2	Extract docs during static site generation ... Summary: Addresses an issue introduced in 6a8200df95. While that commit successfully avoids extracting the docs while developing locally, it neglected to handle the case when the site was being built for deployment. As a result this broke CI. Options are now optional as they should be, and the site generation script will ensure docs are built during deployment. Closes https://github.com/facebook/react-native/pull/12267 Differential Revision: D4523906 Pulled By: lacker fbshipit-source-id: ee00d5653eb98b16b94734299bb15ba5473a0f61	2017-02-07 14:31:38 -08:00
Héctor Ramos	bdbadd1142	Re-style Blog, Add Newsletter Signup Form ... Summary: The goal of this PR is to place greater emphasis on the blog as a destination. The dark Hero from the landing page is now present in the blog as well, and the content is front and center. The sidebar has been removed. It is not necessary to show a list of recent blog posts in the sidebar when the blog landing page shows the same number of posts along with short excerpts. The prev/next links have swapped positions, and will now display "Older posts" and "Newer posts". The excerpts have been stripped of formatting and they are now consistent across the blog landing page and the OpenGraph metatags. Fixes #10597. A signup form for the new React Native newsletter has been added to the footer. Newsletter signup form in footer:  Blog landing page: ![screencapture-localhost-8079-r Closes https://github.com/facebook/react-native/pull/10660 Differential Revision: D4117034 Pulled By: bestander fbshipit-source-id: 215f966008fdf5c8870ed28d92384034a0d23c39	2016-11-02 05:43:43 -07:00
Héctor Ramos	9cb370dd5b	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:28:37 -07:00
Konstantin Raev	6f1417c849	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:17:42 -08:00
Joshua Sierles	21a8145fe8	instead of ignoring the documention javascript support files, just write them without trying to process them	2015-10-14 20:40:20 +02:00
Joshua Sierles	d9ee81c127	embed an appetize.io simulator for AlertIOS documentation	2015-10-14 19:57:23 +02:00
Brent Vatne	debd5b0942	[Docs] Remove Transforms from sidebar, add to Style	2015-05-07 16:05:30 -07:00
Ben Alpert	d81cb6e162	Die with status 1 when website generation fails ... So Travis won't wipe out the website on error. :\	2015-04-01 18:31:18 -07:00
Ben Alpert	efe446e962	Fail generating website if any page throws an error ... This will prevent us from having pages on the site that just show error stack traces -- instead, Travis will fail with an error and we'll notice sooner. I cleaned up this logic to use promises which was eay easier to track for the error behavior and should be simpler to follow regardless.	2015-04-01 17:42:33 -07:00
Christopher Chedeau	e811181034	Add copyright header on website files	2015-03-23 10:56:09 -07:00
Christopher Chedeau	591d7b321f	Make the publish script faster by not converting all the files on every file	2015-03-15 19:54:14 -07:00
Christopher Chedeau	ad3192c360	Attempt #5	2015-03-15 19:32:59 -07:00
Christopher Chedeau	70f28332b6	Initial version of the automatically generated docs	2015-02-12 14:44:00 -08:00
Christopher Chedeau	9231d4f8f0	Initial version of the website and docs.	2015-02-11 20:26:43 -08:00