Re: [Communications] bastille day followup | plone.org/plone.com
Christian Ledermann <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CABCjzWoa=+vi0FNFsKaWJiuyrKxfaP-_XMKkiXBE8Cn-Vh6smg@mail.gmail.com> |
I just read: http://lwn.net/Articles/558172/ ''' Finally, the PSF itself is adapting to better serve the needs of the Python community. It is working on a new web site (a preview of which can be found at preview.python.org). The design goal of the new site is to make it easy for the community to get involved. It is also putting a lot of thought into representing the community, and there will be efforts to address various needs, such as learning Python or teaching Python. Lindberg also lamented that the PSF is not broad and inclusive enough. Membership in the PSF currently requires a nomination from an existing member, but Lindberg believes that every member of the Python community should be a member of the PSF. In April, the PSF voted to completely redo its membership program and to open up membership to anyone. Answering a question from the audience, Lindberg clarified that basic membership will be available to anyone who signs up. Further rights, such as voting privileges, will be given to those members who have demonstrated a commitment to the Python community, such as by contributing code, documentation, or test cases — or by organizing events. ''' it would be nice to have http://preview.plone.org/ On Fri, Jul 19, 2013 at 10:23 PM, Jim Bartek <[email protected]> wrote: > Someone asked about Traffic flow earlier. Hopefully you all can receive the attached flowchart through the mail lists. > > >From the chart you can see since 2005: > > - 4.38 million came in through the homepage > - 2.26 million came in through /products OR a page within /products > - 1.22 million came in through /documentation/kb or a page within > - 4 million came directly into other product, support, or documentation pages > > So ~2/3rds of the traffic is direct linking to some content in products or documentation. The other 1/3rd is coming through the "front door". But then most of the people coming in the front still end up in /products or /documentation. > > So we absolutely need to respect /products and /documentation, but we also need to make the front door much more focused on helping newcomers get engaged. > > *2 cents from the "new guy"* > > > Best, > > > Jim Bartek > Director of Marketing > > -- > Six Feet Up, Inc. | Where sophisticated web projects thrive > Direct Line: +1 (317) 861-5948 x609 > Mobile: +1 (317) 292-6301 > Email: [email protected] > Try Plone 4 Today at: http://plone4demo.com > > > ----- Original Message ----- > From: "Paul Roeland" <[email protected]> > To: [email protected] > Cc: "plone-developers@lists. sourceforge. net developers" <[email protected]> > Sent: Friday, July 19, 2013 2:48:57 PM > Subject: Re: [Communications] [Plone-developers] 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 > _______________________________________________ > Communications mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-communications > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > Plone-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/plone-developers > -- Best Regards, Christian Ledermann Nairobi - Kenya Mobile : +254 702978914 <*)))>{ If you save the living environment, the biodiversity that we have left, you will also automatically save the physical environment, too. But If you only save the physical environment, you will ultimately lose both. 1) Don’t drive species to extinction 2) Don’t destroy a habitat that species rely on. 3) Don’t change the climate in ways that will result in the above. }<(((*> ------------------------------------------------------------------------------ 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 _______________________________________________ Plone-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-developers