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

[Alex Clark]

Hi Rose,

On Wed, Sep 12, 2012 at 10:36 AM, Rose Pruyne <rtp2 at psu.edu> wrote:

> 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.
>


Kudos for the update! I am not editing content nor do I plan to, but I know
that Armin was concerned about this as well:


   - http://chat-logs.dcpython.org/day/plone.com/2012-09-11#16.18.26.acsr


I would strongly suggest that the content team enforce a content deadline
like you suggest, at which point the content can be moved from Netsight
staging to Six Feet Up production. I don't care about GDocs vs. Plone, as
long as the content ends up in Netsight staging at some point, so it can be
easily moved to production.

Also, if we don't hear from the Design time, I'm going to revert to using
the plone.org theme in the meantime, just so we have something to look at.
I think we should continue to aim to stage content on the netsight staging
site, then move to Six Feet Up "production" for staging the theme (where we
can easily pull in theme changes from designers). Actually, maybe I can
deploy the production site with Martin Aspeli's new themed editor as Dylan
suggests. Worst case, we can launch with default bootstrap (kidding!)



Alex







>
> --
> Rose Pruyne
> Project Manager
> WebLion at Penn State
>
>
>
> _______________________________________________
> Starting point: https://plone.org/community/teams/plone.com-development
> Trello collaboration:
> https://trello.com/board/plone-com/50465ecb7f12337f5e230dd6
> Staging site: http://plonecom.netsightdev.co.uk/
> Code: https://github.com/collective/plonecom-buildout
> List archives: http://lists.plone.org/pipermail/plone-com/
> Chat: irc://freenode.net#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
>



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