Hi Janith, On Mon, Mar 29, 2010 at 7:17 PM, Janith Bandara <[email protected]> wrote: > ...First of all, I want to know, what is my scope and what are the features > that is expecting in this project....
As described in SLING-1438, the goal is to create an application that demonstrates and teaches Sling best practices, so it should make good use of the Sling features that facilitate development of content-based applications. Having J2EE experience is useful, but at the application level Sling is very decoupled from J2EE - you'll really need to learn about Sling and might have to forget about some of your existing J2EE knowledge. > ...It is better, If you can provide a architectural diagram for these[1] > features and how to bundle those together.... As a newcomer to Sling we cannot expect you to come up with best practices right away, so the best way is to work in an interactive fashion: define some basic CMS use cases, implement them in a way that makes good use of Sling features, analyze the results with the mentor and volunteer Sling community members, rinse and repeat. I think several iterations will be needed to reach a state that has good educational value, so you must be ready to question your design and throw away things along the way, as needed. The best description of this project might be "implement seven mini-CMSes with Sling and keep the best one" ;-) -Bertrand
