Hi all

Okay, I scanned the whole docs now (took some time...) and would
like to restructure things a little bit to make it more easy to
find the right doc.

Here's the old structure, all topics with a [DELETE] should be
deleted, the others would be transfered to the new structure:

OLD:

x Documentation
  x Discover Sling in 15 minutes
  x Architecture
  x Getting and building Sling
  x JCR - How Sling uses and integrates with JCR (no content)
  x Resources
  x Request Parameters
  x Filters
  x Eventing and Jobs
  - Thread Handling (no content) [DELETE]

x Advanced Topics
  x Logging [OK] [UPDATE]
  x Authentication
  x MIME Type Support
  x Configuration Support
  x Content Loading
  x Manipulating Content/SlingPostServlet
  x Internationalization Support
  x Installing and Upgrading Bundles
  - Assembly (can someone check, seems to be outdated) [DELETE]
  x Implementing a ResourceProvider (no content)
  - Using ScriptEngines from scripting.dev.java.net (no content) [DELETE]
  x Apache Sling Rewriter (Code under whiteboard)
  - Sling API (outdated) [DELETE]
  x Provisioning and Startup (outdated)
  - Object Content Mapping (no content)  [DELETE]
  x Dispatching Requests (outdated)
  x Default Mapping and Rendering (outdated)

x Development
  x Dependency Management
  x Getting and Building Sling
  x Documenting Sling
  x Repository Based Development
  x Bundles - How to create bundles and provide services and
    scripts (no content)
  - Integrating Scripting Languages (not much content) [DELETE]
    - Groovy Support [DELETE]
    x XSLT Processing Pipeline
  x Maven Tips & Tricks
  x Maven Sling Plugin
  x Maven JspC Plugin

x Sling 5 API [OK]


In the new navigation everything is arranged in a hierachical structure
under "Documentation". My proposed new structure looks like this:

NEW:

- Documentation (Overview -> was Documenting Sling [UPDATE])
  - Getting started
    - What is Sling [NEW, extracts from existing home]
    - Discover Sling in 15 minutes [OK]
    - How Sling uses and integrates with JCR [NEW]

  - Engine, the heart of Sling
    - Architecture
    - Resources [UPDATE]
    - Request Parameters [OK]
    - Filters [OK]
    - Dispatching Requests [REWRITE]
    - Default Mapping and Rendering [REWRITE]
    - Eventing and Jobs [CHECK] --> Carsten can you have a look at it
    - Authentication [OK]

  - Development
    - Getting and building Sling [UPDATE]
    - Maven Tips & Tricks [UPDATE]
    - Setup with Eclipse 3.4 [NEW, from Wiki]
    - Maven Sling Plugin [UPDATE, got content from Felix]
    - Maven JspC Plugin [CHECK]
    - How to create a new bundles and services for Sling [NEW]
    - Logging [OK] [UPDATE]
    - RequestProgressTracker [NEW, from SLING-3]
    - Dependency Management [OK]
    - Repository Based Development [OK] (lack of Eclipse Plugin)

  - Bundles
    - MIME Type Support (commons/mime) [OK]
    - Internationalization Support (extensions/i18n) [UPDATE]
    - Manipulating Content/SlingPostServlet (servlets/post) [OK]
    - Content Loading (lack of JSON/XML) (jcr/contentloader) [UPDATE]
    ... a doc page for each bundle should be the future ambition

  - Tutorials & How-Tos
    - Launch Sling (was Provisioning and Startup) [REWRITE]
    - Installing and Upgrading Bundles [OK] --> link to [1]
    - ACL/ACE [NEW]
    - Default Sling JCR layout and nodetypes [NEW]
    - Implementing a ResourceProvider [NEW]
    - Apache Sling Rewriter [OK] (Code under whiteboard)
    - XSLT Processing Pipeline [OK]

  - Wiki

  - configuration (was Configuration Support) [OK]

  - Sling in production
    - Sling standalone [NEW]
    - Sling in a Servlet container [NEW]
    - Sling with Apache httpd [NEW]
    - Access Logging [NEW]

  - Sling API (JavaDoc) [OK]


FAQ [DELETE] -> should rather be integrated into the doc on the
related themes.

Next steps:
* give me your input about the new structure and also
  missing topics
* I begin to update the structure and content (and definitifely
  ask for help from the list for several topics)


[1] http://felix.apache.org/site/apache-felix-web-console.html


best regards
mike

Reply via email to