Re: Making Midgard a CMS (packaging and communications)
Henri Bergius <[email protected]> Tue, 28 Oct 2003 07:52:35 +0200
| Newsgroups | gmane.comp.web.midgard.devel,gmane.comp.cms.aegir.devel |
|---|---|
| Organization | The Midgard Project |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tony Lee wrote: | What's the difference between the 'site building framework' and the | other admins? MidCOM is what you can use for actually running your site. Think NemeinNavBar and Aegir Sample Site, but something more customizable and powerful. The base idea of MidCOM is that the site structure comes from topics and articles (just like in NNB), and that there are these things called components handling each topic. The components can simply be a bit different-looking site subsections (static content vs. news), or they can be full applications (say, web store). True, MidCOM also provides one component called midcom.admin.content that could be seen as admin interface. But I would rather consider it an _authoring_ interface. The idea is to use Aegir (or Spider) for building and admininistrating the site, and MidCOM for running it. You can also use MidCOM's authoring interface to enable wiki-like "Edit this page" features for your users. I was originally sceptical of "Edit this page" but recently have noticed it to be great for casual users who make changes to site content only seldomly, or who don't already have Aegir open when they would like to make modifications. | The MidCOM site template is a subtopic of MidCOM right? This wasn't site structure, just list of things and what goes where. But yes, they are obviously connected, a bit like NNB and aegir-sample-site. | I'd sure like to give MidCOM a try and having it prepacked would help | enormously. Since it would already be installed when I get the time to | look at it. That way when I (the newbie) have the urge it doesn't get | lost sorting out installation issues. Luckily MidCOM has become a lot easier to approach. What we're doing now is sorting some issues there and bundling smarter defaults so users don't have to immediately start creating new datamanager schemas or modifying output templates, but can just build the site just like they would with NemeinNavBar. | Please! Please, please. No offense but the site admin is way behind | current developments. We now have a dedicated server courtesy of Envida, so we can run the latest Midgard stuff there. I had already started to build the site last summer but Torben and Armand asked me to stop for chroot installation. I haven't had time to check back after that, but I'm looking forward to actually building the site now. By my recent experiences, building a site with MidCOM takes about 2 hours with making the "Edit this page" nicer included. | There needs to be an access rights rule set. Since there's none right | now new people either get complete devel, 'go ahead and break the | site)', access or nothing at all. Well, there is this little thing called Midgard there which can provide the access rights framework. We can quite easily restrict modification access to site areas using groups. | Ideally the devel server and the site server should be running from | separate locations. The site server should only be for publishing, no? Staging/live? I don't want to go to the old Nadmin-style replication mess and would rather wait for MidRepository to solidify before doing this. | Seems like Tarjei wants to do this ;-) Remember, this is a MidCOM-powered site :-) | Moving day! That's going to be a lot of fun. If Midgard is really going | to do this it's going to take a concentrated effort for a while. Agreed. That is why I wanted to start by seeing if everybody agrees with the ideas. | Tony /Bergie - -- Henri Bergius Henri.Bergius=ZpG/[email protected] Consultant Partner Tel: +358-20-198 6032 Nemein Oy http://www.nemein.com/ Nemein.Net -- Project tracking solution for consulting companies http://www.nemein.com/en/nemeinnet/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/ngQiNkT8k497k9IRAg94AKCCuPI5EbQogsMXaL7l4gImZsIRiwCeMpOp /6kMkYrnd9VWoI3XfSt44UY= =ROOI -----END PGP SIGNATURE-----