Non-Bric Data in Web Root?

Folks,

File this one under "stupid questions" if you
must, but there's  
something I can't seem to sort out on my own. Is there any
danger or  
potential pitfalls associated with keeping non-Bricolage
data within  
the site's public webroot? If example.com is run entirely
via  
Bricolage, and then I install WordPress at
example.com/blog/, might  
that be problematic for Bricolage? Or does Bricolage have no
reason to  
worry about any files or directories that it has no
knowledge of, and  
therefore ignore it?

Best,
Waldo

---
Virginia Quarterly Review
One West Range, Box 400223
University of Virginia
Charlottesville, VA 22904-4223

On Mar 20, 2008, at 07:25, Waldo Jaquith wrote:

> File this one under "stupid questions" if you
must, but there's  
> something I can't seem to sort out on my own. Is there
any danger or  
> potential pitfalls associated with keeping
non-Bricolage data within  
> the site's public webroot? If example.com is run
entirely via  
> Bricolage, and then I install WordPress at
example.com/blog/, might  
> that be problematic for Bricolage? Or does Bricolage
have no reason  
> to worry about any files or directories that it has no
knowledge of,  
> and therefore ignore it?

That's correct. You can build knowledge into your templates,
though.  
For example, you can have authors create blog entries in
Bricolage,  
and then when they publish, the templates can format them as
 
appropriate for Wordpress. Or it can push them to WordPress
directly  
and return `undef` (so that no files will be distributed by
the  
distribution system).

Best,

David