1. A portal system comprising: a portal connected to at least one social backend, wherein said at least one social backend supports a social media service for a user of the portal, and wherein the social media service allows members of a social community to share their profiles, activities, and web logs (blogs) with each other; a portal object generator for creating a page in the portal, wherein the portal object generator calls model controller application programming interfaces (APIs) for a page model in the portal and a portlet model in the portal that are used to create the page in the portal, wherein the page model describes the page in the portal, wherein the portlet model describes a portlet that is used by the page in the portal, and wherein creating the page in the portal changes a portal model of the portal; and a backend processing component for keeping the portal synchronized with said at least one social backend in response to changes in the portal, wherein the changes in the portal comprise at least one of a group consisting of: creation of a new page, deletion of an existing page, modification of an existing page, creation of a new portlet, and deletion of an existing portlet wherein said portal comprises an integration component communicating with said at least one social backend, the portal system further performing a method comprising: integrating, by one or more processors, functionality of said at least one social backend into said portal environment by creating at least one portal object that is associated with at least one social object, wherein a representative social object is created in response to a web content item with social content being created, wherein content is retrieved from a web content manager in response to said web content item with social content being enriched with associated information, and wherein said associated information comprises social data, “like” tags, a number of “likes”, and access statistics; implementing, by one or more processors, said associated information as meta data entries containing information about said at least one social backend and a social object of said at least one social backend; receiving, by one or more processors, a notification about creation of new portal objects by said integration component; creating, by one or more processors, a new instance of a social object within said social backend by said integration component; receiving, by one or more processors, a new identification from a newly created social object by said integration component; inserting, by one or more processors, new social object identification into meta data of said newly created social object; and representing, by one or more processors, said social object as a portal object to a portal user, wherein said representing reflects deletion and updates of portal objects in said at least one social backend.