chrome/common/extensions/docs/server2/README - Issue 10916019: Move MediaGalleries.getMediaFileSystems out of experimental.

Side by Side Diff: chrome/common/extensions/docs/server2/README

Issue 10916019: Move MediaGalleries.getMediaFileSystems out of experimental. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Update docs Created 8 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « chrome/common/extensions/api/media_galleries.idl ('k') | chrome/common/extensions/docs/server2/templates/intros/experimental_mediaGalleries.html » ('j') | chrome/test/data/extensions/api_test/media_galleries/no_access/manifest.json » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 Overview	1 Overview

2	2

3 This is a Google App Engine server which serves the documentation for Chrome	3 This is a Google App Engine server which serves the documentation for Chrome

4 apps and extensions. At time of this writing, the primary URL is:	4 apps and extensions. At time of this writing, the primary URL is:

5 http://developer.chrome.com/.	5 http://developer.chrome.com/.

6	6

7 Documentation for Chrome apps and extensions is partly generated from API	7 Documentation for Chrome apps and extensions is partly generated from API

8 definitions (for the reference material), and partly hand-written.	8 definitions (for the reference material), and partly hand-written.

9	9

10 All documentation sources are checked into source control, just like any other	10 All documentation sources are checked into source control, just like any other

(...skipping 23 matching lines...) Expand all Loading...
34 Editing Docs	34 Editing Docs

35	35

36 1. Edit files.	36 1. Edit files.

37	37

38 - If you are not updating the static HTML for a docs page, you will most	38 - If you are not updating the static HTML for a docs page, you will most

39 likely not have to do anything. The docs server will automatically pick	39 likely not have to do anything. The docs server will automatically pick

40 up changes to the JSON or IDL schemas.	40 up changes to the JSON or IDL schemas.

41	41

42 - Otherwise, they will be in	42 - Otherwise, they will be in

43 chrome/common/extensions/docs/server2/templates/. See the	43 chrome/common/extensions/docs/server2/templates/. See the

44 "Overview of ./tempaltes Directory" section for more information.	44 "Overview of ./templates Directory" section for more information.

45	45

46 - Files in templates directory use the Handlebar template language. It is	46 - Files in templates directory use the Handlebar template language. It is

47 extremely simple, essentially: write HTML.	47 extremely simple, essentially: write HTML.

48 See third_party/handlebar/README.md.	48 See third_party/handlebar/README.md.

49	49

50 2. Run './preview.py'	50 2. Run './preview.py'

51	51

52 3. Check your work at http://localhost:8000/(apps\|extensions)/<doc_name>	52 3. Check your work at http://localhost:8000/(apps\|extensions)/<doc_name>

53	53

54 4. Send a CL and commit files as with any other Chrome change. The live	54 4. Send a CL and commit files as with any other Chrome change. The live

(...skipping 47 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
102	102

103 4. When prompted for your credentials, enter the information for the account	103 4. When prompted for your credentials, enter the information for the account

104 that has access to the production app.	104 that has access to the production app.

105	105

106 5. Go to http://www.appspot.com, select the docs project, click "versions" in	106 5. Go to http://www.appspot.com, select the docs project, click "versions" in

107 the sidebar, and make the version you just deployed the "default" version.	107 the sidebar, and make the version you just deployed the "default" version.

108	108

109 If you get an error about too many versions when deploying, go into this	109 If you get an error about too many versions when deploying, go into this

110 view and delete the version which was deployed the longest time ago. Then	110 view and delete the version which was deployed the longest time ago. Then

111 try to deploy again.	111 try to deploy again.

OLD	NEW