Wednesday, November 28, 2012 | 1:30 PM
Labels: Drive SDK
Would you like to programmatically publish some web content? Or let your users do so in the context of your Drive app?
Publishing from Drive is a simple, two-step dance: create a public folder and use a link to the root folder — the
webViewLink — to publish its contents. You can refer to the Drive SDK documentation for full detail on how to work with public folders and content links, but basically the requirements are:
- The folder containing site assets must be public. Assets added to public folders must also be public on the web.
- Link to the files contained in the folder using the
webViewLink(included in the folder’s JSON representation).
It’s important to emphasize the added simplicity provided by a
webViewLink: using this link as a starting point, you can extend the path to any web asset in any subfolder without worrying about retrieving the exact file ID. What used to look like
0B2Gk2F2ImIBiaUkwY3JNX1JMaTg is now a recognizably cute path such as
images/kittens.jpg. For the root path to the folder, we’ll display a list of files in the folder, or, if you have an
index.html file in your folder we’ll load that as expected.
To see Google Drive site publishing in action, check out this example site served from Google Drive at https://googledrive.com/host/0B716ywBKT84AcHZfMWgtNk5aeXM.
The ability to publish files this way opens lots of possibilities for Drive app developers. Writing a blogging tool, creating a process to publish updates to shared docs, outputting images in a folder in a gallery page — any Drive use case that involves presenting a file in a browser can benefit from site publishing. We look forward to seeing what you create, and we’re happy to answer your questions on Stack Overflow.
Eric is a technical writer working with the Developer Relations group. Previously dedicated to Google Apps APIs, he is now busy writing about all aspects of the Google Drive SDK.