i haven't looked at it, but i think an attribute as="url" in the link macro should do the job because a link to the root site is available as <% root.link ... %>.

yeah, i think that was my part... sorry for the delay. at least i started with going through some of the macros.

i don't think the macros-in-macros feature should be part of the guidelines.

i think these rather should contain a generic structure and how certain functionalities are implemented if needed.

e.g. the way a macro returns a url (which robert does with the "as" parameter most of the time).

currently, the goal should be to reduce the amount of macros instead of add even more.

my proposal at the time for a generic macro:

<% handler.macro prefix="str" suffix="str" encoding="html|xml|form|url" [id="str" html="str" as="str"] %>

str stands for an arbitrary string.

prefix, suffix and encoding are already processed automatically by helma.

as defines the return type, e.g. "url", "link", "editor" (still has to be evaluated how this can be done consistently).

the other parameters only make sense for macros that create html tags:

id i would prefer over class because it can be used with javascript as well.

html could be a parameter that contains arbitrary html attributes (e.g. onmouseover handler or whatever). it simply would appended at the end of the tag, before the ">").

i also thought about how default parameters could be handed over in a macro, sometimes this could be useful e.g. when having select forms or the like.

and linkto is also a good parameter i'd like to keep.

but as i said: still truckin'...