-------Getting Started and Customizing--------
To get started, copy the staycms package to a place
that you can access from a web server, which can parse PHP.
The latest package is always available at http://mirrors.katmore.com/staycms.
It should work out to the box using the the default configuration,
combined with the prepackaged content example and barebones theme.
The starting point for your configuration is with the file
The default config file from the package is fully annotated.
The most important place to customize is the Content namespace.
Content namespace is divded into "contentid's"
StayCMS divides content into "pages".
A new "Page" of content is added by creating new files in the content namespace.
The name of the file determines the unique "contentid" of the "Page".
Creating a file called "mycontent.inc.php" would add a "page" called "mycontent" to your site.
It would be accessed like this: http://example.com/sf.php?p=mycontent
There are reserved characters, reserved strings, and reserved areas of the filename that
can have an affect on wheather you will create a new contentid when creating a file.
For the most part, any combination of letters and numbers, followed by ".inc.php" in the
content folder should work.
The contents of this file, determine the value of the page. Straightforward enough.
The content of the file can be evaluated/parsed as PHP at runtime, for maximum flexibility.
The same rules apply of course, as any PHP script (<?php and ?> brackets).
Themes have the ability to refer to attributes of the contentid which can be articulated by creating new files in the Content folder with "special" names. Examples of such special names are
"titletext-mycontent.inc.php". Creating a file with that name, will not add a new contentid to the Content namespace. The contents of that file will be used by staycms to create an attribute OF the content id referenced in the filename (in our example it's "mycontent"). In this case, "titletext" is the name of the attribute. Most importantly, this attribute can be referred to in the Theme, to create text for headings, title tags, etc. As was just alluded, there are other attributes that can be created this way for contentids. Other examples are "headingtext", "sitetext", "copyright". Not only can these attributes be referred to in the theme, but also in the Content itself, but that would be strange practice.
-------Look/Feel of the Site-------
Theme: the look and feel. The theme files include mandatory files which could be
explicitly called by the CMS classes at runtime (ie: "page.inc.php") and "helper"
files that are arbitrary and specific to a particular theme (ie: "bottom.inc.php").
Documentation © 2011-2012 Doug Bird. All Rights Reserved.
Staycms is © 2011 P.D.Bird.II. and is released under the terms of the FreeBSD License.
Generated Sun, 24 Sep 2017 13:56:24 -0700 by bldoc: © 2011 P.D.Bird.II. All Rights Reserved.