sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling > GSoC 2010 mini-CMS project
Date Wed, 28 Apr 2010 09:06:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1810/1/1/_/styles/combined.css?spaceKey=SLING&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">GSoC
2010 mini-CMS project</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Bertrand
    <div class="notificationGreySide">
         <h1><a name="GSoC2010mini-CMSproject-Overview%28fromSLING1438%29"></a>Overview
(from SLING-1438)</h1>

<p>This is a Google Summer of Code 2010, Federico Paparoni has been accepted as a student
to work on it, mentored by Bertrand Delacretaz (hopefully with the help of the Sling community!)</p>

<p>The goal is to create a mini-CMS with Sling, that demonstrates Sling best practices.

<p>The emphasis is on the quality and readability of the demo code, and we expect to
have to go through several iterations to refine it and the corresponding JCR content model
so that they demonstrate Sling best practices. We will not necessarily create a full-fledged
CMS, the goal is for the result to be educational and help Sling newcomers understand how
to create web applications with it. </p>

<p>Suggested technologies: jQuery for the front-end, ESP and/or JSP for server-side
scripting, and Java code in OSGi bundles for back-end functionality. </p>

<p>We should find a better name than "mini-CMS" for this project.</p>

<p>See <a href="" class="external-link" rel="nofollow"></a>
for the full list of GSoC 2010 projects at the ASF, and <a href=""
class="external-link" rel="nofollow"></a> for general
GSoC information.</p>

<h1><a name="GSoC2010mini-CMSproject-Requirements"></a>Requirements</h1>
	<li>Create an educational application that people can study to find out how to use
	<li>At the same time, the mini-CMS should be usable, not just a toy.</li>
	<li>Ideally, the mini-CMS should allow for editing the Sling website. Detailed requirements
TBD, but storing the content and generated website in subversion is probably required.</li>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message