Re: Don't rubberstamp Borat blurbs.

Hi Jon & all

> +1, Jean, thanks for raising this.  Indeed, it is a fine line between
> being open/respecting people for whom English is a second (or third or
> fourth!) language and making sure plone.org is professional.

Everyone should get respect, no question about that. I think that includes
helping to get the text up to scratch.

> +1 for copy-editing if you have time energy; also +1 for sending stuff
> back with a polite note.

Agreed.

Fixing https://dev.plone.org/ticket/11652 would facilitate this.

> I don't think your edits are too harsh.

OK, I've applied it to the listing.

> One thought that occurs to me is that most of the second/third paragraphs
> could really be cut from a simple site listing; they would be more
> appropriate for a full-blown case study.

True. In such cases we could invite submitters to create a case study instead.

Hmm, it might work to give the listing content type a body field for the case
study version.

I know the Description field is supposed to be un-parsed Dublin Core metadata,
but it sure would be prettier if linebreaks were preserved.
I created a ticked for this one: https://dev.plone.org/ticket/12384

-- 
jean                                              . .. .... //\\\oo///\\

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam