[prev in list] [next in list] [prev in thread] [next in thread]
List: midgard-dev
Subject: [midgard-dev] cvs: /midgard/doc manual.sgml contentmgmt.sgml
From: bergie <midgard-dev () greywolves ! org>
Date: 1999-12-29 9:38:17
[Download RAW message or body]
bergie Wed Dec 29 11:38:17 1999 EDT
Modified files:
/midgard/doc manual.sgml contentmgmt.sgml
Log:
More Content Management updates from Jamie, who is also added to the
author list of the Manual.
Index: midgard/doc/manual.sgml
diff -u midgard/doc/manual.sgml:1.12 midgard/doc/manual.sgml:1.13
--- midgard/doc/manual.sgml:1.12 Sat Dec 25 22:16:10 1999
+++ midgard/doc/manual.sgml Wed Dec 29 11:38:15 1999
@@ -1,4 +1,4 @@
-<!-- $Id: manual.sgml,v 1.12 1999/12/25 20:16:10 emiliano Exp $ -->
+<!-- $Id: manual.sgml,v 1.13 1999/12/29 09:38:15 bergie Exp $ -->
<!DOCTYPE BOOK PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
<!ENTITY appendix.faq SYSTEM "faq.sgml">
<!ENTITY introduction SYSTEM "introduction.sgml">
@@ -50,6 +50,9 @@
</author>
<author>
<firstname>Jonni</firstname><surname>Lehtiranta</surname>
+ </author>
+ <author>
+ <firstname>Jamie</firstname><surname>Tomlinson</surname>
</author>
<author>
<firstname>Jukka</firstname><surname>Zitting</surname>
Index: midgard/doc/contentmgmt.sgml
diff -u midgard/doc/contentmgmt.sgml:1.10 midgard/doc/contentmgmt.sgml:1.11
--- midgard/doc/contentmgmt.sgml:1.10 Tue Dec 28 13:45:17 1999
+++ midgard/doc/contentmgmt.sgml Wed Dec 29 11:38:16 1999
@@ -1,4 +1,4 @@
-<!-- $Id: contentmgmt.sgml,v 1.10 1999/12/28 11:45:17 bergie Exp $ -->
+<!-- $Id: contentmgmt.sgml,v 1.11 1999/12/29 09:38:16 bergie Exp $ -->
<chapter id="contentmgmt">
<title>Content Management</title>
@@ -62,12 +62,6 @@
security over your server? Again, me too!
</simpara>
- <simpara>
- Midgard and its dynamic content control allows all of this and
- more, but to achieve this, you have to understand a little
- about its dynamic structure, content and control.
- </simpara>
-
<sect3>
<title>What do you want your site to look like?</title>
@@ -84,22 +78,6 @@
</sect3>
<sect3>
- <title>What do your viewers think?</title>
-
- <simpara>
- TODO: write me
- </simpara>
- </sect3>
-
- <sect3>
- <title>What do your clients think?</title>
-
- <simpara>
- TODO: write me
- </simpara>
- </sect3>
-
- <sect3>
<title>How easy is it for your clients to update their sites?</title>
<simpara>
@@ -130,50 +108,42 @@
</sect2>
<sect2>
- <title>Who can do it</title>
+ <title>Free-form Management</title>
<simpara>
- TODO: write me
+ At a more in-depth level, managing the content of your site is
+ made simple through an HTML interface into an administration
+ site. This allows administration of the site at any time from
+ anywhere through any machine, even if its not your primary
+ development machine.
</simpara>
</sect2>
-
- <sect2>
- <title>Where can it be managed from</title>
- <simpara>
- TODO: write me
- </simpara>
- </sect2>
-
- <sect2>
- <title>When can it be managed</title>
-
- <simpara>
- TODO: write me
- </simpara>
- </sect2>
+ <simpara>
+ <!-- moved this here as a transition into the next section -->
+ Midgard and its dynamic content control allows all of this and
+ more, but to achieve this, you have to understand a little about
+ its dynamic structure, content and control.
+ </simpara>
</sect1>
<sect1>
<title>Advantages of dynamic pages</title>
- <simpara>
- TODO: write me
- </simpara>
-
- <sect2>
- <title>Introduction</title>
-
- <simpara>
- TODO: write me
- </simpara>
- </sect2>
+ <!-- Do dynamic pages include the hosts? -->
<sect2>
<title>What are dynamic pages</title>
<simpara>
- TODO: write me
+ <!-- This is basically the introduction -->
+ Looking in the dictionary, you'll find Dynamic defined as
+ "...marked by usually continuous and productive activity or
+ change". Dynamic Pages are just that. The hosts, pages,
+ topics, articles and site structure that are continuously (and
+ hopefully productively) changed. With its free-form
+ structure, Midgard allows you great flexibility in the form
+ and layout of your web structure.
</simpara>
</sect2>
@@ -185,42 +155,119 @@
</simpara>
<sect3>
- <title>Quick modifications</title>
+ <title>Online/offline</title>
<simpara>
TODO: write me
+ <!-- awaiting info on dual hosts -->
</simpara>
</sect3>
<sect3>
- <title>Online/offline</title>
+ <title>Password protection</title>
<simpara>
- TODO: write me
+ Anyone who has ever password protected a site or series of
+ web pages can attest that Apache's mechanism, while
+ effective, is not intuitive. With the ability to protect a
+ site with a single click, and the simple addition of groups
+ and users through an HTML form, you can implement basic
+ password protection for your web site.
</simpara>
- </sect3>
- <sect3>
- <title>Password protection</title>
+ <simpara>
+ By simply going to the Host Administration page in the
+ administration web site, you can place a host under password
+ authentication with four clicks of your mouse. After you
+ are at the host administration page, click on the host that
+ you want to protect, then click modify. Click on
+ "Authentication: required" and click on "submit" and you are
+ done. The site is password protected.
+ </simpara>
<simpara>
- TODO: write me
+ Adding authentication to a topic or page in Midgard 1.2.x is
+ somewhat different. Authentication for topics and pages are
+ not native to this version, but that doesn't prevent you
+ from adding a script to authenticate a user. While not very
+ elegant, you can place the following script in an element
+ that activates the automatic content element:
</simpara>
+
+ <programlisting>
+<?php if ($midgard->user && mgd_is_member($GROUP)); ?>
+<<(content)>
+<?php else; ?>
+<(unauthorized)>
+<?php endif; ?>
+ </programlisting>
+
+ <simpara>
+ Translated, this states that if the person accessing the
+ site is a registered user, and is a member of the group that
+ owns the page then show the content (shown as
+ <(content)> ), else show him that he is not authorized
+ to access this page (shown as (<(unauthorized)>). This
+ is an HTML element that you create with the name
+ <literal>unauthorized</literal>).
+ </simpara>
+
+ <simpara>
+ Extensive access control is planned for version 2.0 of
+ Midgard including being able to set read, write, modify,
+ etc. permissions for specific groups and/or users for all
+ objects in the Midgard database.
+ </simpara>
</sect3>
<sect3>
<title>Low maintenance</title>
<simpara>
- TODO: write me
+ Site maintenance has always been the bane of the Webmaster.
+ Each time a page is added or a directory tree is modified,
+ the Webmaster must go back through the pages and insure that
+ none of his links are broken. Midgard's separation of
+ content and layout simplifies that task immensely.
+ </simpara>
+
+ <simpara>
+ With a small amount of forethought and a bit of code, the
+ site's pages and links become truly dynamic. Midgard
+ references its pages, topics, and articles by a record
+ number in a database. With a rich set of functions to
+ search and display an entire page or topic tree, your pages
+ will become truly dynamic adjusting their displayed content
+ automatically as you add pages, topics and articles. For
+ example, if you have set up a menu to display articles of of
+ a given topic, a bit of code such as:
+ </simpara>
+
+ <!-- insert a menu code snippet here -->
+
+ <simpara>
+ will not only display the articles, but each time you add a
+ new article to the topic, it is added to the menu
+ dynamically without intervention on the Webmaster's part.
+ Midgard doesn't care what the article is called, it simply
+ searches the topic tree and reports those articles that are
+ below the supplied topic.
</simpara>
+
+ <simpara>
+ This separation of content management and layout management
+ allows the Webmaster to concentrate on what he wants to
+ present instead of worrying about how it will effect the
+ rest of the web site.
+ </simpara>
</sect3>
<sect3>
<title>Adjustable to browser and host</title>
<simpara>
- TODO: write me
+ Single content
+ Use styles for presentation
</simpara>
</sect3>
@@ -229,6 +276,8 @@
<simpara>
TODO: write me
+ Uses a database for storage of data
+ Structures of web sites can be changed quickly
</simpara>
</sect3>
@@ -244,7 +293,9 @@
<title>PHP</title>
<simpara>
- TODO: write me
+ "Native" language for Midgard
+ Used to dynamically switch content
+ Can be used for self modifying trees
</simpara>
</sect3>
@@ -257,7 +308,7 @@
</sect3>
<sect3>
- <title>Limited only by your imagination</title>
+ <title>Multiple administrative interfaces</title>
<simpara>
TODO: write me
@@ -265,7 +316,7 @@
</sect3>
<sect3>
- <title>Multiple administrative interfaces</title>
+ <title>Limited only by your imagination</title>
<simpara>
TODO: write me
@@ -277,10 +328,6 @@
<sect1>
<title>Topic trees</title>
- <simpara>
- TODO: write me
- </simpara>
-
<sect2>
<title>Introduction</title>
@@ -299,15 +346,15 @@
<!-- What would be the correct way to
discuss this area? -->
+ <!-- JT: Isn't this basically the topic tree from host down to
+ the articles, including the styles? Perhaps a description of
+ each? -->
+
</sect2>
</sect1>
<sect1>
<title>Mapping dynamic content to pages</title>
-
- <simpara>
- TODO: write me
- </simpara>
<sect2>
<title>Introduction</title>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic