Sling site at [2].
So now, our site is dynamically generated from the wiki content and will
- with some delay involved due to exporting and syncing - actual with
respect to the wiki.
Thanks go to Marcel Offermans and Luminis for the nice CSS and export
template work.
Please report if you find any
mplate of the Confluence and the CSS to make the export
> look like a real web site. Finally the exported Wiki content is synced
> into the Sling site at [2].
>
> So now, our site is dynamically generated from the wiki content and will
> - with some delay involved due to exporting and
Hi all,
We have a long standing issue around our documentation which is sort-of
messy and to a big extent outdated and mostly incomplete. I have been
thinking about this an propose a rigorous reorganization of our site
along these general lines:
* Home Page - general introduction to Sling and i
Added my free-form notes here:
http://cwiki.apache.org/confluence/display/SLING/Introductions
Sorry for the lack of formatting, I don't have time for that at the
moment. Please feel free to correct me and/or improve it!
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
I would add a whole bunch of short intros from various perspectives
that answer these questions for the beginner:
- Sling in a few words (like the 15 min by Bertrand but just for
reading without coding)
- Why should I care with yet another webapp framework? (getting ready
for flame-wars ;-)
Hi Felix,
maybe you have mentally included these topics somewhere, but what comes to
my mind:
- setting up a dev environment
- debugging Sling applications
Michael
On 2/13/08, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> We have a long standing issue around our documentation whic
Hi Michael,
Am Donnerstag, den 14.02.2008, 11:29 +0100 schrieb Michael Marth:
> Hi Felix,
>
> maybe you have mentally included these topics somewhere, but what comes to
> my mind:
> - setting up a dev environment
> - debugging Sling applications
Yes I had this in mind, but for convenience I crea
make a note to the mailing list after
changing something on the Sling site?
2) Is it a good idea to publish documentation which is probably not complete
or maybe incorrect in the public wiki for reviewing and transfer it to the
Sling site later?
3) Does someone has drafts of documentation which
. Or do you handle it
> like code (commit then review) and I just make a note to the mailing list
> after
> changing something on the Sling site?
We don't have any written workflow. We pretty much just update as we see
fit. The only concern I try to cope with is that we keep the UR
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 Documen
Hi,
first of all, good to see progress on the documentation front!
On Fri, May 22, 2009 at 4:08 AM, Mike Müller wrote:
> Manipulating Content/SlingPostServlet
is a rather important topic for most everyday Sling development, so it
should get a more prominent location (could also be done through
Hi Alex
> first of all, good to see progress on the documentation front!
>
> > Manipulating Content/SlingPostServlet
>
> is a rather important topic for most everyday Sling development, so it
> should get a more prominent location (could also be done through a
> link from an overviewpage, though).
I like the idea of an overview page (the new "documentation" parent page)
with a "hot topics" or better "Getting Started" box with a roadmap of links
the user can follow to get a good overview of Sling. This would allow to
have a technically correct hierarchy, but supporting newcommers who have no
Hio Dominik
> I like the idea of an overview page (the new "documentation"
> parent page)
> with a "hot topics" or better "Getting Started" box with a
> roadmap of links
> the user can follow to get a good overview of Sling. This
> would allow to
> have a technically correct hierarchy, but support
Hey Mike,
glad you like my idea, here a first draft of a list which imho would be
didactical sense:
- What is Sling
- Getting and building Sling
- Architecture
- Resources
- Setting up an Sling-Project with Eclipse [NEW - [1]]
- Sling-Taglib (JSP) [NEW - especially sling:include needs good
docume
2009/5/22 Dominik Süß :
> I like the idea of an overview page (the new "documentation" parent page)
> with a "hot topics" or better "Getting Started" box with a roadmap of links
> the user can follow to get a good overview of Sling. This would allow to
> have a technically correct hierarchy, but su
Hi Mike,
On Fri, May 22, 2009 at 11:08 AM, Mike Müller wrote:
> ...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
Cool, thanks!
See below for a few comments on the new structure.
> NEW:
On Sun, May 24, 2009 at 11:56 PM, Alexander Klimetschek
wrote:
> 2009/5/22 Dominik Süß :
>> I like the idea of an overview page (the new "documentation" parent page)
>> with a "hot topics" or better "Getting Started" box with a roadmap of links
>> the user can follow to get a good overview of Slin
Hi Betrand
> I like this as well, but I also think our docs need tags to provide
> several ways of navigating them.
>
> I don't think the Confluence export plugin that currently generates
> our website handles tags, but we could still add them to our pages
> already, something like:
>
> TAGS #se
On Mon, May 25, 2009 at 9:21 AM, Bertrand Delacretaz wrote:
> I like this as well, but I also think our docs need tags to provide
> several ways of navigating them.
>
> I don't think the Confluence export plugin that currently generates
> our website handles tags, but we could still add them to o
2009/5/25 Dominik Süß :
> On Mon, May 25, 2009 at 9:21 AM, Bertrand Delacretaz > wrote:
>> ... TAGS #servlets #scripts #javascript
>>
>> In the content of the page.
>>
>> For now this can be used by web search engines, and later we might
>> create a Sling navigation app and run it on an ASF zone. T
Hi Bertrand
Hi Betrand
> >- How Sling uses and integrates with JCR [NEW]
>
> I would prefer "Sling and JCR" as a title for the last item.
agreed.
> > - Engine, the heart of Sling
> >- Architecture
> >- Resources [UPDATE]
> >- Request Parameters [OK]
> >- Filters [OK]
> >
Hi Mike,
Mike Müller schrieb:
> 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,
able way, which cannot be out of sync (link using
slingdoc tags described below).
[2] http://incubator.apache.org/sling/site/servlet-resolution.html
A technique that I've found useful to avoid duplicating info is to tag
code sections as belonging to the explanation of some aspect of our
sof
s it has to be maintained in
> parallel with the code. I'd rather link to a javadoc page which lists
> those parameters, or better, directly to the code where the parameters
> are defined in a readable way, which cannot be out of sync (link using
> slingdoc tags described below).
>
er of course), the table of
> reference properties at [2] is risky, as it has to be maintained in
> parallel with the code. I'd rather link to a javadoc page which lists
> those parameters, or better, directly to the code where the parameters
> are defined in a readable way, which cannot
26 matches
Mail list logo
