Re: [Communications] bastille day followup | plone.org/plone.com

although this discussion was/is harsh, I actually think this is a Good
Thing (TM). People care. That's good.

and I do think we can find our way out of this.

I get the SEO thing, and I also fully get the other side of the
argument. As purely personal opinion, I think the two sites should be
separate *on a technical level*. So, fully separate instances, but under
a same TLD.

Neither one of the 'decision maker' and 'community' sites will move
permanently faster than the other, rather they will move at different
speeds at different times. Sometimes the 'decision maker' site will need
radical re-design or re-wording, sometimes the 'community' site will be
shaken up by some energetic people and have quick progression.

But there is no reason we cannot combine the two towards the outside world.

The current plone.org is dedicated towards the community, with some
awkward marketing thrown in, but mostly directed to those who already
work with Plone.
We know, and can reach, those people. A change to move that whole site
towards http://plone.org/community or http://community.plone.org (or
whatever, creative suggestions welcome) as a replacement for what is
currently the landing page of plone.org will not harm that community,
those are savvy people that can actually work tha interwebz, and will
quickly know where to find all they find now.

A "marketing" landing site for people not yet into the Plone fold at
plone.org (what we used to think of as plone.com) can be independently
developed. (and should be, with all speed possible!!!)

I'm with Florian on this one, we can do this in a way that will do
justice to the two different audiences, and allow for independent speeds
of developements.

Again, speaking purely personal, I think plone.gov and plone.edu were
mostly 'problem children', and would definitely benefit from being taken
up in the new plone.org, to benefit from better design and visibility,
and thus can cater to those specific markets without the burden of
separate maintenance.
But the community site should be separate in a technical sense, being
able to be developed by Victor e.a., although united under the same TLD.

Paul

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk