[Plone-com] Plone.com Content - A Request

[Alex Clark]

On Wed, Sep 12, 2012 at 12:00 PM, Armin Stroß-Radschinski <developer at acsr.de
> wrote:

> I am sorry , I can only answer in short due to I am, out of business now
> until tomorrow. Cannot dive in now. We should not produce too much double
> stuff between the staging server and google docs.
>
> We cannot comment on phrases in Plone, so in spite of Matts enforcing
> statements, content is not good yust because it is on the staging server.
> We should stay in Goggle docs for now. As I wrote yesterday.
>
> This will slow us down finally if not well planned.
>


I think we are all agreed on Google Docs for content creation and editing,
and Plone for hosting. So any content in staging right now should be
considered disposable. If you want to make a change, change the Google doc.





>
> Armin
>
> Am 12.09.2012 um 16:36 schrieb Rose Pruyne:
>
>  To everyone who has commented and recommended changes on Plone.com
>> content drafts that I've been working on --  Your feedback is very much
>> appreciated! Your comments are great, and point to a big improvement of the
>> content.
>>
>> My failure is that I am lacking the time each day to sift through the
>> feedback coming in by e-mail and GDoc comments and adjust the text
>> accordingly. I apologize for being a blocker and a bottleneck.
>>
>> So I'm making a request that I hope will move drafts along more
>> efficiently and gain the benefit all of our content specialists'
>> perspectives: Instead of commenting, do go ahead and incorporate your
>> material into the draft. (If you are already doing that, bless you.)
>>
>> Then, let's agree on a pre-launch *deadline* for concluding the drafting
>> of this content. At that point, those with editorial skills can tidy up the
>> content for style considerations, flow, grammar/spelling/punctuation/**etc.,
>> and move this fresh content to the Plone site so it's in place for the
>> unveiling at the Conference. I'm talking about a pre-launch content freeze.
>> Content can be continually improved after the Conference is over.
>>
>> I'm mainly referring to the drafts that I've been working on -- 'what is
>> plone?' and 'why should i choose plone?' -- but we might want to use this
>> 3-step process for all the content: 1. full collaboration (author, don't
>> comment), 2. content freeze and final edit, 3. move content to the site.
>>
>> Or if everyone would prefer to collaborate on the content directly in
>> Plone rather than GDocs, that's a-ok by me.
>>
>> --
>> Rose Pruyne
>> Project Manager
>> WebLion at Penn State
>>
>>
>> ______________________________**_________________
>> Starting point: https://plone.org/community/**teams/plone.com-development<https://plone.org/community/teams/plone.com-development>
>> Trello collaboration: https://trello.com/board/**plone-com/**
>> 50465ecb7f12337f5e230dd6<https://trello.com/board/plone-com/50465ecb7f12337f5e230dd6>
>> Staging site: http://plonecom.netsightdev.**co.uk/<http://plonecom.netsightdev.co.uk/>
>> Code: https://github.com/collective/**plonecom-buildout<https://github.com/collective/plonecom-buildout>
>> List archives: http://lists.plone.org/**pipermail/plone-com/<http://lists.plone.org/pipermail/plone-com/>
>> Chat: irc://freenode.net#plone.com | http://chat-logs.dcpython.org/**
>> channel/plone.com <http://chat-logs.dcpython.org/channel/plone.com>
>> ______________________________**_________________
>> This is the Plone-com mailing list
>> Plone-com at lists.plone.org
>> http://lists.plone.org/**mailman/listinfo/plone-com<http://lists.plone.org/mailman/listinfo/plone-com>
>>
>
> ______________________________**_________________
> Starting point: https://plone.org/community/**teams/plone.com-development<https://plone.org/community/teams/plone.com-development>
> Trello collaboration: https://trello.com/board/**plone-com/**
> 50465ecb7f12337f5e230dd6<https://trello.com/board/plone-com/50465ecb7f12337f5e230dd6>
> Staging site: http://plonecom.netsightdev.**co.uk/<http://plonecom.netsightdev.co.uk/>
> Code: https://github.com/collective/**plonecom-buildout<https://github.com/collective/plonecom-buildout>
> List archives: http://lists.plone.org/**pipermail/plone-com/<http://lists.plone.org/pipermail/plone-com/>
> Chat: irc://freenode.net#plone.com | http://chat-logs.dcpython.org/**
> channel/plone.com <http://chat-logs.dcpython.org/channel/plone.com>
> ______________________________**_________________
> This is the Plone-com mailing list
> Plone-com at lists.plone.org
> http://lists.plone.org/**mailman/listinfo/plone-com<http://lists.plone.org/mailman/listinfo/plone-com>
>



-- 
Alex Clark · http://pythonpackages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-com/attachments/20120912/9d2603fd/attachment.html>