Lynn Winebarger wrote:
>
> Hi again. A question and desire to confirm some observations about
> using midgard:
> Q: Is it possible to get the Midgard manual (unfinished though it is)
> in a printable form (tex/pdf/postscript/whatever)?
http://www.midgard-project.org/~emiliano/, html, text & rtf, updated
every night.
> As for observations, I'd gotten a bit confused, I think, between
> "content administration" (topics and articles) and page administration
> (which doesn't have its own section in the admin site).
The way I usually look at it, the articles & topics define the content
of the site, while the pages define the structure of the site. My
pages will have PHP code to generate active parts of the site or to
pull content from the topic tree. The topic & article content will
usually be 'static' text for me.
> So apparently,
> when I create a page, it has at least one default page element, content,
> which can be included by the style as <(content)>.
Right, content & title are available as elements.
> I take it any other
> page-elements I create can be referenced by the style in the same
> way?
Yes.
> Or, vice versa, if a style mentions a <(pe-name)>, any page with
> that style should have a page element named "pe-name"? What happens if it
> doesn't (error, or interpolates as empty)?
Missing elements are not an error. They're simply assumed to be empty.
I use it all the time.
> Meanwhile, I have to
> explicitly deal with articles, through a hard-coded topic number (or is
> their access through topic name?).
1.4 has functions to fetch topics & articles by name, but they way
I've been using it people 'browse' towards the content they want. I
fetch the IDs of topipcs/articles as people select their parent, so
nothing but the topic root is hardcoded.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
