On Mon, Dec 1, 2008 at 11:11 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: >> In this case I agree that it might make sense to use script resolution >> based on node types, but in the general case I find the >> sling:resourceType way of resolving scripts closer to our "data first, >> structure later" recommendation. >> >> My best practice recommendation would then be to use >> sling:resourceType if possible, and nodetype-based script resolution >> only if one has to. >> > Hmm, ok, although I personally don't like to add rendering hints into > the content, but anyways, what about documenting this? :)
Regarding script resolution we "only" have something in the wiki (which is too detailed for the beginner) [1]. There is also Lars' sling cheat sheet, which is very good for a beginner (but a PDF and not hosted on/pointed to from the sling site) [2]. The "official" documentation for this is outdated [3]. [1] http://cwiki.apache.org/SLING/url-to-script-resolution.html [2] http://dev.day.com/microsling/content/blogs/main/cheatsheet.html [3] http://incubator.apache.org/sling/site/servlet-resolution.html Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
