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,
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]
> >
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
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
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 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 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:
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
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
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
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
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).
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
13 matches
Mail list logo
