sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1076286 - in /sling/site/trunk: content/index.mdtext templates/sidenav.mdtext templates/skeleton.html
Date Wed, 02 Mar 2011 16:45:58 GMT
Author: bdelacretaz
Date: Wed Mar  2 16:45:58 2011
New Revision: 1076286

SLING-2002 - rough conversion of index page


Modified: sling/site/trunk/content/index.mdtext
--- sling/site/trunk/content/index.mdtext (original)
+++ sling/site/trunk/content/index.mdtext Wed Mar  2 16:45:58 2011
@@ -1,5 +1,186 @@
-Title: Welcome to Apache Sling
+Title: Apache Sling - Bringing Back the Fun!
-This is a placeholder index page, will be replaced by content exported from Confluence.
+{tm}Apache Sling{tm} is an innovative web framework that is intended to
+bring back the fun to web development.
-Making a change to trigger staging.
\ No newline at end of file
+Discussions about Sling happen on our mailing lists, see the [Project Information](project-information.html)
+ page for more info.
+<a name="ApacheSling-bringingbackthefun!-ApacheSlinginfivebulletspoints"></a>
+# Apache Sling in five bullets points
+* REST based web framework
+* Content-driven, using a JCR content repository
+* Powered by OSGi
+* Scripting inside, multiple languages (JSP, server-side javascript, Scala,
+* Apache Open Source project
+<a name="ApacheSling-bringingbackthefun!-ApacheSlinginahundredwords"></a>
+# Apache Sling in a hundred words
+Apache Sling is a web framework that uses a [Java Content Repository](
+, such as [Apache Jackrabbit|]
+, to store and manage content.
+Sling applications use either scripts or Java servlets, selected based on
+simple name conventions, to process HTTP requests in a RESTful way.
+The embedded [Apache Felix](
+ OSGi framework and console provide a dynamic runtime environment, where
+code and content bundles can be loaded, unloaded and reconfigured at
+As the first web framework dedicated to [JSR-170](
+ Java Content Repositories, Sling makes it very simple to implement simple
+applications, while providing an enterprise-level framework for more
+complex applications. 
+<a name="ApacheSling-bringingbackthefun!-News"></a>
+## News
+* [all news...](news.html)
+<a name="ApacheSling-bringingbackthefun!-History"></a>
+## History
+Sling started as an internal project at [Day Software](
+, and entered the Apache Incubator in September 2007. As of June, 17th,
+2009 Apache Sling is a top level project of the Apache Software Foundation.
+The name "Sling" has been proposed by Roy Fielding who explained it like
+\[The name is\](the-name-is\.html)
+ Biblical in nature.  The story of David: the weapon he uses to slay the
+giant Goliath is a sling.  Hence, our David's \[David Nuescheler, CTO of
+Day Software\] favorite weapon.
+It is also the simplest device for delivering content very fast.
+<a name="ApacheSling-bringingbackthefun!-WhousesSling?"></a>
+## Who uses Sling?
+See [Who is using Sling](
+ on our public wiki.
+<a name="ApacheSling-bringingbackthefun!-Gettingstarted"></a>
+## Getting started
+If you prefer doing rather than reading, please proceed to [Discover Sling in 15 minutes](discover-sling-in-15-minutes.html)
+ or read through the recommended links in the [Getting Started]
+ section, where you can quickly get started on your own instance of Sling.
+{note:title=Excuse our mess while we redesign}
+Sling has undergone an important redesign in the last few months, and we're
+not done updating this website yet.
+The status of each page is indicated by a note like this at the top of each
+Pages which do not have such a note should be considered *not reviewed*:
+the information that they contain might be out of sync with the current
+Sling codebase.
+<a name="ApacheSling-bringingbackthefun!-Contents"></a>
+## Contents
+* [Documentation](documentation.html)
+ \- Here you will find the documentation on Sling
+* [Development](development.html)
+ -- Documentation on how to develop web applications with Sling and what
+tools you have at your disposal
+* [Links](links.html)
+* [Wiki](
+* [FAQ](
+* [Project Information](project-information.html)
+<a name="ApacheSling-bringingbackthefun!-UseCasesforSling"></a>
+## Use Cases for Sling
+<a name="ApacheSling-bringingbackthefun!-Wiki"></a>
+#### Wiki
+Day built a Wiki system on Sling. Each Wiki page is a node (with optional
+child nodes) in the repository. As a page is requested, the respective node
+is accessed and through the applying Component is rendered.
+Thanks to the JCR Mapping and the resolution of the Component from the
+mapped Content, the system does not care for what actual node is addressed
+as long as there is a Content mapping and a Component capable of handling
+the Content.
+Thus in the tradition of REST, the attachement of a Wiki page, which
+happens to be in a node nested below the wiki page node is easily accessed
+using the URL of the wiki page attaching the relative path of the
+attachement  ode. The system resolves the URL to the attachement Content
+and just calls the attachement's Component to spool the attachement.
+<a name="ApacheSling-bringingbackthefun!-DigitalAssetManagement"></a>
+#### Digital Asset Management
+Day has implemented a Digital Asset Management (DAM) Application based on
+Sling. Thanks to the flexibility of the Content/Component combo as well as
+the service registration/access functionality offered by OSGi, extending
+DAM for new content type is merely a matter of implementing one or two
+interfaces and registering the respective service(s).
+Again, the managed assets may be easily spooled by directly accessing them.
+<a name="ApacheSling-bringingbackthefun!-WebContentManagement"></a>
+#### Web Content Management
+Last but not least, Sling offers itself very well to implementing a Web
+Content Management system. Thanks to the flexibility of rendering the
+output - remember: the system does not care what to render, as long as the
+URL resolves to a Content object for which a Component exists, which is
+called to render the Content - providing support for Web Content authors
+(not PHP programmers but users out in the field) to build pages to their
+likings can easily be done.
+<a name="ApacheSling-bringingbackthefun!-References"></a>
+## References
+<a name="ApacheSling-bringingbackthefun!-ApacheJackrabbit"></a>
+#### Apache Jackrabbit
+The main purpose of Sling is to develop a content-centric Web Application
+framework for Java Content Repository (JCR) based data stores. Sling is
+implemented - with the notable exception of JCR Node Type management -
+purely in terms of the JCR API and as such may use any JCR compliant
+repository. The default implementation for [Apache Jackrabbit](
+ is provided out of the box.
+<a name="ApacheSling-bringingbackthefun!-OSGi"></a>
+#### OSGi
+Sling is implemented as a series of [OSGi](
+ Bundles and makes extensive use of the OSGi functionality, such as
+lifecycle management and the service layer. In addition, Sling requires
+several OSGi compendium services to be available, such as the Log Service,
+Http Service, Configuration Admin Service, Metatype Service, and
+Declarative Services.
+<a name="ApacheSling-bringingbackthefun!-ApacheFelix"></a>
+#### Apache Felix
+While Sling does not require a specific OSGi framework implementation to
+run in, Sling is being developed using [Apache Felix](
+ as the OSGi framework implementation. It has not been tested yet, but it
+is expected that Sling also operates perfectly inside other OSGi frameworks
+such as [Equinox|]
+ and [Knopflerfish|]

Modified: sling/site/trunk/templates/sidenav.mdtext
--- sling/site/trunk/templates/sidenav.mdtext (original)
+++ sling/site/trunk/templates/sidenav.mdtext Wed Mar  2 16:45:58 2011
@@ -1,10 +1,34 @@
-# Sling links
-  - [Home](index.html)
-# ASF links
-  - [Apache Software Foundation](
-  - [License](
-  - [Thanks](
-  - [Become a Sponsor](
-  - [Security](
+# Documentation
+* [Getting Started](getting-started.html)
+* [The Sling Engine](the-sling-engine.html)
+* [Development](development.html)
+* [Bundles](bundles.html)
+* [Tutorials & How-Tos](tutorials-&-how-tos.html)
+* [Configuration](configuration.html)
+* [API docs](
+* [Wiki](
+* [FAQ](
+# Project info
+* [Downloads](
+* [License](
+* [Contributing](contributing.html)
+* [News](news.html)
+* [Links](links.html)
+* [Project Information](project-information.html)
+* [Issue Tracker](
+* [Browse Source Repository](
+* [Security](
+# Sponsorship
+* [Thanks](
+* [Become a Sponsor](
+* [Buy Stuff](
+	src=""
+	style="border-width:0; float: left" frameborder="0" 
+	scrolling="no"
+	width="135" 
+	height="135">

Modified: sling/site/trunk/templates/skeleton.html
--- sling/site/trunk/templates/skeleton.html (original)
+++ sling/site/trunk/templates/skeleton.html Wed Mar  2 16:45:58 2011
@@ -1,6 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
     Licensed to the Apache Software Foundation (ASF) under one or more
@@ -18,34 +17,42 @@
     See the License for the specific language governing permissions and
     limitations under the License.
-  <link href="/sling/css/sling.css" rel="stylesheet" type="text/css">
-  <title>Apache Sling - {% block title %}{{ headers.title }}{% endblock %}</title>
-  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-  <link rel="icon" type="image/png" href="/sling/images/sling-logo/sling-favicon.png"/>
-  <div id="navigation"> 
-  <img title="Sling logo" width="274" height="125" src="/sling/images/sling-logo/sling-2010-270-transparent.png"/>
-  {% filter markdown %}{% include "sidenav.mdtext" %}{% endfilter %}
-  </div>
-  <div id="content">
-    <h1 class="title">{% block title %}{{ headers.title }}{% endblock %}</h1>
-    {% block content %}{{ content|markdown }}{% endblock %}
-  </div>
-  <div id="footer">
-    <div class="copyright">
-      <p>
-        Copyright &copy; 2010 The Apache Software Foundation, Licensed under 
-        the <a href="">Apache License, Version
-        <br />
-        "Apache Sling" and the Apache feather and Sling logos are trademarks of The Apache
Software Foundation.
-      </p>
+  <head>
+    <title>Apache Sling - {% block title %}{{ headers.title }}{% endblock %}</title>
+    <link rel="stylesheet" href="" type="text/css"
+    <link rel="icon" href="">
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+  </head>
+  <body>
+    <div class="title">
+      <div class="logo">
+        <a href="">
+          <img border="0" alt="Apache Sling" src="">
+        </a>
+      </div>
+      <div class="header">
+        <a href="">
+          <img border="0" alt="Apache" src="">
+        </a>
+      </div>
+    </div>
+    <div class="menu"> 
+      {% filter markdown %}{% include "sidenav.mdtext" %}{% endfilter %}
+    </div>
+    <div class="main">
+      <div class="breadcrump" style="font-size: 80%;">
+		(TODO: breadcrumb here)
+      </div>
+      <h1 class="title">{% block title %}{{ headers.title }}{% endblock %}</h1>
+      <div>
+	    {% block content %}{{ content|markdown }}{% endblock %}
+      </div>
-  </div>
+    <div class="trademarkFooter"> 
+		Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo
are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks
or registered trademarks of their respective owners.
+	</div>
+  </body>

View raw message