On 3/23/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
Now that I've looked at this a bit I have a couple more things that I
would like to suggest ...

1. If the template is required (or tied to a specific action in the
upcoming code) then we don't show the Name, Link, and Description
elements as form fields.  Instead we just provide targeted help text to
explain exactly how the specific template relates to the weblog design.

I think name, link and description are helpful bits of information and
I don't see any reason to stop displaying them. They don't have to be
greyed out form fields, they could just be text.


2. I am starting to think that we don't really need the 'description'
property of a template.  How many people actually want to put in a
description for their template?  I think that the template name serves
as enough of a description and the less form fields users have to deal
with the better.

-1. I use it and find it quite helpful.

If you've got a large number of templates, then having a description
field is quite helpful.


3. I don't think the content type controls need to be available for
templates that are required.  It wouldn't make much sense to change the
content type for the Weblog template, for example.

-1 on this too. Some bloggers want XHTML.

Bloggers and theme designers should be able to pick the content type
of their blog. Some folks are going to want HTLML 4 (text/html), some
are going to require XHTML (application/xhtml+xml) and some might want
XML + XSLT -- we should force everybody to use text/html.

- Dave

Reply via email to