Hi Federico, On Wed, May 26, 2010 at 12:35 PM, Federico Paparoni <[email protected]> wrote: > ...There is a blog where I will write every step done with project > (http://davidgsoc.wordpress.com/). When GSoC will end, these posts will be > reorganized to became a useful guide...
Cool - I would even suggest reviewing that blog near the end of the project, and contributing meaningful content to the Sling website. But keeping a log of your "adventures" is great. > ...I also opened an account on Google code > (http://code.google.com/p/davidgsoc2010/) where I'll syncronize my project.... Ok. > The first milestone of this project will be a simple mini cms, with basic > features: > - Autentication for different user with different level I would keep this for a second iteration... > - Administration panel to create/edit/delete content (there are a lot of JS > WYSIWYG editor). The content can also have file attachments ...and concentrate on this for a first iteration, even without a wysiwig editor if that makes things easier. > - Standard view of CMS (anonymous), with the possibility to populate > different panel with different content (like a portlet container)... probably too much for a first iteration. > The first milestone should be available for the midterm evaluation of GSoC > (16 July).... I would much prefer having a minimal first iteration as soon as possible, say within 10 days. We can then give you feedback on it to steer the project - waiting until mid-july for that feedback is too long IMO, what do you think? > The second milestone will be more focused on the development of different > features like: > > Notification when some documents are modified (JCR observation) > ATOM and RSS feed of entries > Search in the entries and in the attached files (Lucene integration works ad > default with Sling?)... yes, search is provided out of the box by the JCR repository, no need to worry about Lucene yourself. > A stupid tag cloud for the entries submitted > Also a synchronization of entries with svn as you told me (using a library > like SVNKit http://svnkit.com/)... Ok, or maybe just a static HTML export of the cms content - the svn sync can be done manually in a first step. > ...I haven't a clear idea about the feature I will develop in the second > milestone, so every comments/ideas/criticisms.... I see good ideas above, and agree to rediscuss them as we go. I'd rather have 5 iterations with refocusing after each one. Thanks for these ideas, looking forward to the corresponding code! -Bertrand
