Login to the Cookbook
About the Cookbook
The Daylife Cookbook is a collection of recipes to help you bootstrap applications that use the Daylife platform (DayPI).
These recipes come from Daylifers and the cookbook community, with entries ranging from sample code to tutorials, half baked ideas, and spotlights of the latest deployments of the DayPI.
Feel free to share, steal, criticize, applaud, and feed back!
Resources
Testimonials
Daylife is a perfect fit for our strategy of presenting the best and most tightly focused content, whether it is produced by us at USA TODAY or anywhere else on the Web. It helps us provide our readers with a full 360-degree view of a given topic, and adds depth and richness to niche areas important to our readers and advertisers.- Jeff Webber, SVP, USAToday.com
You guys have what seems like an amazingly powerful and easy to use API, we're pretty excited about playing with it and possibly integrating it with Hubdub. - Tom Griffith, Hubdub.com
It's amazing how simple this is to integrate into django. When a view is creating a page, it just calls a thin wrapper function that I put around the daypi module. - Bracket Boy
I found the Daylife API for PHP really easy to use, and coded something up quickly for my site, Brooklyn and Beyond - Brooklyn & Beyond
This tool makes it really easy to get a quick look or dive in deep thanks to our partner Daylife, who built a comprehensive service that yields up-to-the-minute results - The Washington Post
I was trying to make it work by using Google News RSS feeds but turned out impossible since they don't organize their data in the feeds. I now know its possible with the Daylife API - Akash Xavier
Redistributing the content i get from Daylife
The FAQ suggests that a Free DayPI application may not redistribute the content obtained from Daylife directly, but can only serve it on their site. My confusion lies, what if an application is not a website ?
My application acts as a small server, and then sends the data directly to the users instead of later visiting the site.
Does this void the DayPI User agreement ? And if it does, is there any solution to it ?
Portals, Widgets, AJAX apps, mobile apps - all good!
Amitabh,
Our concern in terms of redistributing content from Daylife is primarily for a scenario where you write an API on top of the Daylife APIs and offer that to others as "your API".
You are most welcome to write applications that are web sites, widgets, AJAX apps, desktop clients, web clients, mobile apps etc...
Exciting!
- Vineet