Re: [psa-devel]SiteMap

[Justin K. <ju...@ko...>]

Albert Lash wrote:
>>>Have you thought any more about the idea of replacing the site structure
>>>with an xml document?
>>
>>Hmm.. I forgot about that... Run it by me again to refresh my memory.
> 
> Rather than having the db define
> the site structure, you can have an xml document that specifies the site
> structure. Often called a sitemap. This concept is tried and true - used in
> Cocoon (a Java CMS), Popoon (a php CMS framework used in BitFlux), and
> Nexista (a php application platform). PSA would then read the sitemap file
> rather that the page urls from the db. The best part of this is that
> developers could then use the sitemap file to also specify class includes
> based on uri, and much much more.

It does sound like a good idea. I don't know how you'd go about using 
wildcards in a site map though - especially if your site uses the XML 
file to generate it as a navigation point for users.

I can see how this would be good for initializing and updating the site 
structure. However, we'd have to add functionality to automatically 
determine how to create wildcard entries where they want them in a way 
that it wouldn't effect the site map XML file if it is being used for 
the site itself.

I will take a look into this some more and post a few ideas of how it 
can work. Once the plan is laid out, we could proceed from there.

> I would have to suggest checking out Nexista. http://www.nexista.com/ The
> code is very clean and well thought out though a little nebulous and tries
> to be everything to everyone. It at least is a very good example of how a
> sitemap is used. 

I will try to check this out.

>>That reminds me... do have experience with the SourceForge CVS?
>>Specifically setting up write access for developers to certain directories?
> 
> I don't! And I'm getting a bit frustrated at Sourceforge in general. There
> is also Tigris which seems very nice. http://www.tigris.org/ This is where
> Nexista will be hosted once the developer releases the most up to date
> version to the public. 

I will check this out as well.