Kassetra Stevenson wrote: > Ok, here are the steps (in order) that I understand to do to convert my > existing web site to midgard (at least most of it -- please comment on > any and all steps if I have misunderstood something -- sorry for being > such a newbie!):
We've all been there. Nothing to apologize for; how else would one learn? On to the answers, although some have been addresses a few days ago: > 1. Create a Page for each directory I have on the current site (like > help, signup, services, etc... i.e. www.mycompany.org/Page/ ) with the > root Page as my "home" page. That's one possible solution. Most sites use pages to implement logic (the web apps), and put content in topcs & articles, and have the pages fetch them from there and show it. In this setup. pages are more driven by their functionality (one page serves all or most of all the URLs that have the same behaviour). But it is possible to implement it all in the style, and have the pages hold the actual content. > 2. Create a Style for each "look" I want to have (like I can have a > holiday, spring, etc. "themes" to use, and the root Style is my default > or standard style.) Right. > 3. Create style elements that contain the actual html code for any html > template I reuse, with a special <[content]> tag in them, where I want > content and a special <[css]> tag that calls a style element for my css. The css tag is not special, but yes, correct. > 4. Then I create page elements for each "directory" that contains the > Page specific content... like the forms for the signup, or the php code > that pulls articles by topic (and makes the first letter a jpeg). Yes, since those ar all different behaviour (see above). > 5. Then I can make groups that are allowed access to only those Pages > (which used to be directories) I want them to access ... Midgard currently doesn't have read access controls (which is going to be addressed as sooen as the scripting backend stabilizes), but group-based read controls are easily implemented by active checking (in the code-init element for example, bouncing people back to the homepage or somesuch is they don't have the required privilege). > If this is one correct procedure for converting to midgard... then I'm > starting to understand it. > > Except -- where do I put my image files -- and how do I reference them? > Right now I have them stored in a single directory that all pages > access. So in my templates I have something like: <img > href="../directory/image.jpg"> -- would I make a style element that > calls the graphic from *somewhere?* for each of the template graphics I > use and then just put <[logo]> (and other names) in my styles, like I > did for my css code? You can still use file-based images if you want to (my site does, but it's addmittedly a very simple site). The Midgard-native way of doing images is through attachments. Page-bound attachments are served automatically, for others (images bound to articles, for example) you'll need to implement a little script to serve them out. NAdmin includes such a script. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
