On 10 Jan, Derek Beattie wrote:
> Hi all,
Greetings!
> 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.
Yes, at the moment that is the option for US citizens, or you
can use the normal RPMs and install Apache separately. It
would be nice if someone there could start making versions
of the monster package that would be legal to use in the US
(replace mod_ssl with something that doesn't have export
restrictions).
> 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.
We're working on them, but the problem is that most people
in the project are programmers not writers.
At the moment best source for documentation is this mailing
list. The PHP manual is also useful but doesn't cover
Midgard-specific functionalities.
> 1. What elements are required for every site?
ROOT. Everything else is optional. You can see the
default elements that are called for every page in
the midgard-root.php3 file:
<[code-compat]>
<[code-global]>
<[code-init]>
<[ROOT]>
As usually with the Midgard style system, you can
leave any of these elements out and there will be
no errors. It is just something of a convention to
use ROOT element for containing the actual layout
and content for that page and the code- elements
for code snippets that need to be processed before
going to the actual page.
As to any other elements, you can use them or
leave them unused. It is possible to only have
the ROOT element in your style if you wish so.
Other 'required' elements are content and title.
Those two come from the fields of the Midgard
page.
> 2. Is it common to have a different Layout for each site?
People usually do that. But it is entirely up
to the site administrator to decide. For example,
on the Greywolves.org server we have many different
Styles that are all child styles of one style and
so can share some elements from it but differ
in others.
> 3. Is it common to store all sites in one DB?
This depends on whether you want to share some
data between your sites or no. There is a slight
performance hit if you use multiple databases
so it might be a good idea to avoid that if
you don't have much memory on your server.
> 3. On the example site under Style admin I see the following:
<snip>
> 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 or what determines how
> the subtopics Content,Events,News Releases,Products are layed out?
The content element calls for content of that particular
page (which you can find from the Host administration), and
the page then contains a Midgard/PHP script that fetches
needed content from a topic tree (in the content administration).
Midgard uses this method for flexibly separating layout,
structure and content from each other.
> Derek
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
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]
