Analysis: Exporting a Liferay instance to Facebook and OpenSocial(repost)

I need an analysis document that describes how to: Use a combination of Liferay hooks, plugins, ..., to share **a whole portal instance** as a single **Facebook or OpenSocial (MySpace, ...)** application. The analysis must describe how to export to both APIs. ## Deliverables Dear Sir/Madame, I'm a software engineer, but I don't get to do anything with web-programming at work. I've decided to make my own website, and I need someone to jump-start my project. ? My goal: Create Facebook and OpenSocial (MySpace, ...) web-applications using the LifeRay portal. ? How do I want to do it: Using a combination of Liferay hooks, plugins, ..., make it possible to share **a whole portal instance** as a single Facebook or OpenSocial application. Liferay supports sharing an individual portlet instance right out of the box, but this just isn't good enough. I want to use the Tomcat bundle that comes with Liferay as my Java web server. Once a portal instance is shared, it should be possible to **use any portlet without modification** (for example, the chat-portlet) in that instance, just like in a normal instance, except that all users are actually mapped to users of the social portal (FB, ...) that registered/added my application (except guest). And the portal instance is going to be completely private to the Internet itself, except (IMHO) the front-page, giving the registration instructions. ? My problem: I just don't have the time and energy to learn the APIs of Facebook, OpenSocial, and Liferay, before I can put my first simple application on FB / MySpace. ? Required Deliverables: An analysis document defining the following things: * Facebook and OpenSocial APIs that are needed to export a whole Liferay Portal Instance as a FB/OS application. This should be about *3 to 6 pages* (for both). It should be geared toward my goal. If there are several APIs available, I want to know which one I should use, and why. * A list of general functionality that most applications running on Facebook or OpenSocial should implement (can be platform-specific). This should include for example, accessing the user's picture, information and friend-list, posting "news" to the user, dealing with deleted and/or de-installed users, and users blocking the app. Letting users register, letting users send invitations to friends, ... All those things that are common to most apps. This should be about *2 to 4 pages.* * List of interesting optional API functionalities that could make an application stand out, like being accessible over a mobile phone, ... This should be about *1 to 2 pages.* * List of changes required to Liferay, so that it supports the above mentioned features (if at all possible, without using Ext or changing directly Liferay's sources). This should be about *2 to 4 pages.* * List of known/expected pitfalls involved in implementing those features. This should be from about *1 to 2 pages.* * A detailed / explained estimation of the effort / cost involved, to produce a piece of software the can turn a Liferay instance into a full-fledged Facebook/OpenSocial app. This should be about *1 page.* * A few graphics to better show the APIs. This could be about *1 to 2 pages.* This makes together a document of about 15 pages (explicitly, it should be at least 13 pages, more then 15 pages is of course acceptable). Supplementary requirements on the analysis document: * The text has to be in clearly expressed and understandable English. * The text has to be comprehensible for a developer who has never done this kind of thing before. In other words, API-specific concepts have to be explained. * Acronyms should be explained when first used. * It should not contain any copy-righted material, that would make it's redistribution illegal. * The text should be based on the most current information available on the Internet about Facebook API, OpenSocial API, and Liferay (version 6.*). * Whenever appropriate, links to public documents used as source for the analysis. * Document should be in PDF format ("printable" and "editable"), and? text font size should be 10 or 12, except for headings/titles. Once I accepted your bid, I expect you to provide the document within one week (seven days). Using this document, I will then be able to create a requirement document to get a someone to do the programming. Please define your experience with the different APIs involved in your bid offer. Links public examples of your work would be appreciated. If the document is satisfactory, it might give you an edge when I post the request for the software. ## Platform Liferay 6.0