Hi I have downloaded the binary, and even checked out from SVN - both working fine. My question now, as a newbie to portal development (but not architecture), is what is the best way to implement what I need in a portal. Here is what I'm after:
1) I need the ability to have public as well as private widgets (I have designed similar approach for Liferay before with public and private communities). There will be anonymous access to a few key capabilities, but external users will need to signup/login to extract full value from the site. Internal users will log into the sight to access a different set of widgets etc. I presume that I will need to create my own version of the home page, but I don't know if it's best to edit directly in the downloaded code or if its best to treat Rave as a black box and create a separate project with a dependancy upon Rave (and if so, hints on how would be appreciated). My preference is to keep an ability to upgrade Rave as a separate component without introducing too many changes that require complicated merging. 2) I need to create my own private/public widgets (with some social integration as an enhanced capability). I'm not familiar with Shindig or Wookie, so I can't tell which approach would be best, or whether its something I create "within" the Rave development or outside and deploy to a runtime? 3) Not at the moment, but I believe an aspect of content management will be useful in the near term - I note the presentations on Spring HMVC extension, and was wondering what is the state of the content-services sandbox? Thanks Derek
