Derek Beattie wrote:
>
> Hi all, I've been playing with midgard now for a couple of weeks. Its very
> interesting. I'm in the US and can't use the RPM's with SSL, I guess, so I've
> been learning how to compile apache/ssl/midgard myself.
I'm not entirely sure on this crypto issue so I stuck in the warning to
be on the safe side. I suppose you don't need it anymore, but for others
that want to do this, the RPM spec would be a good start.
> Anyway my question is,
> where is the best source of documentation for Midgard? I've looked on the site
> and the docs seem to be incomplete.
They are. Fortunately work on them has picked up momentum lately.
> I've studied the example site (Virtual
> Midgard Using Company 0.1) and I'm confused about some things.
>
> 1. What elements are required for every site?
Absolute minimum would be a host definition, a root page and a style.
The
root page does not need to have any content, either, but it's what
triggers
the style to use. The style must at least contain a element named ROOT
as
that is where page processing starts.
> 2. Is it common to have a different Layout for each site?
It is one way to do things. The Midgard layout mechanism is very
flexible
and I've yet to find a common way it is used. You can map many different
layouts (with/without frames, flash, images, sounds, etc) to one
content tree or site, or have one style map to various content
trees(/sites).
You can inherit styles and alter them selectively for new hosts or parts
of a site, or use a totally unrelated layout for various part of one
site.
And I could go on.
> 3. Is it common to store all sites in one DB?
You can store as many or as little in one DB as you like. If you want
content
sharing amongst sites you 'll have to have them in the same DB. If you
want
sites separated with no way for them to get at each others' content
you'll
want separate databases (possibly hosted by one DBMS of course).
> 3. On the example site under Style admin I see the following:
> body
> body-content
> body-format
> footer
> head
> head-author
> head-generator
> head-made
> head-style
> head-title
> navilinks
> ROOT
> table
>
> in the table element I see <(content)> tag and I see the actual content in the
> content administration. I don't understand how the actual content in the
> content admin gets layed out in the final product/site
<(content)> and <(title)> are 'magical' in that Midgard will replace
them
with the content/title of the page (URL) that was visited.
> or what determines how
> the subtopics Content,Events,News Releases,Products are layed out?
The layout is fully determined by the style mechanism, which may use
scripts
or statical HTML to generate the navigation environment. While the
content
management uses a hierarchical tree to organize content the layout is
not required by any means to make any use of that hierarchy.
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]
