Tobias Fors wrote: > I haven't really used WebDAV-tools, so can't say much about it myself, > but it sounds interesting, especially if support is wide. File system > based editing from both Windows/Mac/Linux would be sweet. > > Do you have any ideas on how best to handle things like the "slug", > publish status, chosen filter, behavior etc?
Hi Tobias,
looking at other CMSs they typically try to wrap as much of the
metadata into the metadata fields provided by the document, e.g. HTML
metatags. This may not work well with Radiant because of its special
document structure consisting of parts. However, one could always use
YAML or a similar text-based format as a page's file representation.
For example:
# behavior:Page
# status:draft
# title:Test Page
# part:body
# filter:textile
h1. Part with Textile content
# part:extended
# filter:
<p>Part with raw HTML</p>
The slug could just be represented by the filename.
This model, however, does not directly support pages that have
children, i.e. act like directories. To support this each page may be
represented as a directory containing a file "index" or "content" that
reflects the content and metadata of the page.
Alternatively, a page's content and properties can represented as a
set of files within the directory. Example:
homepage/
+- @status
+- @behavior
+- @title
+- @part.body
+- @part.extended
+- child1
| +- @status
| +- @behavior
| ...
+- child2
+- @status
...
Eventually some of the properties may be combined into a single file
called @metadata or similar.
Those are just some preliminary thoughts which hopefully will generate
more ideas. I personally favor the first approach as it allows easier
support of other document types such as images or PDF files.
Let me know what you think.
Oliver
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
