If you’ve got a spare moment it would be great for you to drop by the forums and post a new topic about your cms.

Thanks

My question is how do you edite the site content… I don’t see any admin pages to point my browser to?

thanks

Jack

Now onto Skeleton..

The benefit over using a normal file configuration really depends on what you find “normal”. At it’s very basic, it can be used to create a site with a common header and footer that has nice rewritten urls while being able to use dynamic content. I’ll think of a basic site I can use it for and make one this week/weekend and post the example along with the source code for you and anyone else wondering.

I don’t really have any specific questions. What I was wondering was why would you use skeleton over a normal file configuration, in other words, I simply don’t understand the purpose. By reading through the documentation already in it, I feel like it’s a really powerful tool though and thus want to understand how it works, which will be a lot easier with some usage examples.

Anyway, I really like your blog, and will be checking here frequently!

I’d love to put up some documentation for it soon, but I’m pretty busy this month and focusing on a few other projects. I could answer some specific questions though, if you wanted to know exactly how to do something specific with it.

I must say this looks really promising. I’ve downloaded it and attempted to use it, but I am yet to completely understand the way it works, and right now I think it’s above my league. I think one way to make it easier to understand would be to pose some practical uses.

I really like the way CushyCMS works (I’ve checked it out after your blog post), but it lacks some things to me… First being able to install it on my own server as back-end site administration tool, that’d be really useful (this is where their business is though, with webdesigners having custom styling and paying for it). Second it misses the option for repeating patterns of blocks of code, which would be useful in for example a news page (bringing along obvious problems though).

So skeleton as a CMS system sounds great, but I don’t understand how it works so far.

That tells me enough to fix your problem, but I’d like to understand more about the way WOSportable works without downloading it so that file will help me out a great deal.

Perhaps this will tell you something about my install:
I browse to (I removed the http prefix): localhost/skeleton/

All the internal links come up like this:
(I removed the http-colon so your site doesn’t autocode this line)

localhostF:\wosportableSE\www\skeleton/theme/reset.css

Thanks.

Do me a favor and download this file. Put it in the same directory as you are running Skeleton from and open it in your browser. Save that page as html and then email it to me at greg(at)greg-j[dot]com. I’ll have a look and post a fix for you when you get that output to me.

I have a stupid coding question. I have a WOS Portable server on a USB stick for testing, and have used it to try out many CMS systems. I put Skeleton on it, and have a root/base/url problem that I don’t understand. When I pull up the Skeleton page, all the internal urls (css, links, etc.) are wrong, in form like this:

Templating 101

My USB stick is F. Obviously, I need to change the root directory code somehow. I’m guessing I need to modify this code at the top of /skeleton/index.php:

// THIS is the root directory
define(‘ROOT’, getcwd());

// make some URL’s
$url = new stdClass();
$url->root = ROOT;
$url->base = ‘http://’ . $_SERVER['HTTP_HOST'] . str_replace($_SERVER['DOCUMENT_ROOT'], ”, ROOT);
$url->theme = $url->base . ‘/theme’;

But I don’t know how to do it. Any suggestions?