Menu
▾
▴
plone-docs — Discussion about the Plone documentation
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(83) |
Nov
(55) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(29) |
Feb
(31) |
Mar
(37) |
Apr
(6) |
May
(25) |
Jun
(36) |
Jul
(19) |
Aug
(7) |
Sep
(17) |
Oct
(40) |
Nov
(33) |
Dec
(44) |
| 2004 |
Jan
(20) |
Feb
(15) |
Mar
(22) |
Apr
(17) |
May
(24) |
Jun
(19) |
Jul
(15) |
Aug
(25) |
Sep
(79) |
Oct
(35) |
Nov
(112) |
Dec
(31) |
| 2005 |
Jan
(110) |
Feb
(40) |
Mar
(35) |
Apr
(37) |
May
(24) |
Jun
(10) |
Jul
(8) |
Aug
(54) |
Sep
(23) |
Oct
(17) |
Nov
(35) |
Dec
(41) |
| 2006 |
Jan
(72) |
Feb
(184) |
Mar
(57) |
Apr
(83) |
May
(38) |
Jun
(44) |
Jul
(11) |
Aug
(60) |
Sep
(33) |
Oct
(75) |
Nov
(227) |
Dec
(89) |
| 2007 |
Jan
(46) |
Feb
(27) |
Mar
(28) |
Apr
(33) |
May
(94) |
Jun
(33) |
Jul
(48) |
Aug
(24) |
Sep
(57) |
Oct
(32) |
Nov
(32) |
Dec
(23) |
| 2008 |
Jan
(65) |
Feb
(51) |
Mar
(30) |
Apr
(111) |
May
(19) |
Jun
(31) |
Jul
(114) |
Aug
(57) |
Sep
(26) |
Oct
(72) |
Nov
(252) |
Dec
(98) |
| 2009 |
Jan
(100) |
Feb
(37) |
Mar
(89) |
Apr
(57) |
May
(81) |
Jun
(27) |
Jul
(27) |
Aug
(42) |
Sep
(25) |
Oct
(45) |
Nov
(21) |
Dec
(72) |
| 2010 |
Jan
(74) |
Feb
(23) |
Mar
(6) |
Apr
(47) |
May
(64) |
Jun
(7) |
Jul
(19) |
Aug
(3) |
Sep
(26) |
Oct
(6) |
Nov
(15) |
Dec
(28) |
| 2011 |
Jan
|
Feb
(9) |
Mar
(7) |
Apr
(8) |
May
(13) |
Jun
(1) |
Jul
(35) |
Aug
(21) |
Sep
(9) |
Oct
(16) |
Nov
(6) |
Dec
(3) |
| 2012 |
Jan
(10) |
Feb
(6) |
Mar
(7) |
Apr
(26) |
May
(2) |
Jun
(7) |
Jul
(2) |
Aug
(6) |
Sep
(6) |
Oct
(15) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
(2) |
Sep
(3) |
Oct
(6) |
Nov
(1) |
Dec
(3) |
| 2014 |
Jan
|
Feb
|
Mar
(2) |
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(4) |
|
From: Mikko O. <mik...@re...> - 2012-04-13 21:46:54
|
On Fri, Apr 13, 2012 at 23:42, John Schinnerer <jo...@ec...> wrote: > I am totally new to github...the apparently relevant button says "Fork and > Edit this file" - not sure if that is the correct thing to do? Please > advise how to make the edit without making a mess... > Should go like this 1. Go to Writing and updating the documentation <https://github.com/collective/collective.developermanual/edit/master/source/introduction/writing.rst>on GitHub. 2. Press *Fork and edit this file* button 3. Edit file contents using GitHub's text editor in your web browser 4. Press *Propose file change* at the bottom of the page > > thanks, > John S. > > > On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: > >> Hi John, >> >> Mention early on, with link, to see the Hosting Guide for information >> about production installations/deployments. >> >> >> Good spot. Can you go ahead and fix it directly here? >> >> https://github.com/collective/**collective.developermanual/** >> blob/master/source/tutorials/**installation.rst<https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst> >> >> -Mikko >> >> For example where it now says: >> >> ------------------------------**---------- >> ... >> Installing Plone using Unified UNIX Installer >> >> Note >> This is the recommended installation method >> >> This recipe is good for >> Lightweight production sites >> Plone development and testing on Ubuntu / Debian >> ... >> ------------------------------**------------ >> >> ...add some following text like: >> >> "For information on using this installation with production >> environments/deployments, see the [hosting guide]." >> >> There is a line that hints at that at the very end of the unified >> installer section, and I think it could be clearer and sooner. >> >> thanks, >> John S. >> >> On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: >> > Hi, >> > >> > I try to modernize / centralize existing Plone installation >> instructions. >> > >> > Please take a look on: >> > >> > >> http://collective-docs.**readthedocs.org/en/latest/** >> tutorials/installation.html<http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html> >> > >> > ...and then take a stab on the document or me. >> > >> > Cheers, >> > Mikko >> > >> > ----- >> > >> > Follow me in Twitter >> > >> > >> > >> > Read my blog >> > >> > >> > >> > >> > >> > -- >> > View this message in context: >> http://plone.293351.n2.nabble.**com/New-installation-**instructions-** >> tp7453156p7453156.html<http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html> >> > Sent from the Documentation Team mailing list archive at Nabble.com. >> > >> > >> ------------------------------**------------------------------** >> ------------------ >> > Better than sec? Nothing is better than sec when it comes to >> > monitoring Big Data applications. Try Boundary one-second >> > resolution app monitoring today. Free. >> > http://p.sf.net/sfu/Boundary-**dev2dev<http://p.sf.net/sfu/Boundary-dev2dev> >> > ______________________________**_________________ >> > Plone-docs mailing list >> > Plo...@li...urceforge.**net<Plo...@li...> >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> > >> >> > https://lists.sourceforge.net/**lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >> >> -- >> John Schinnerer - M.A., Whole Systems Design >> ------------------------------**-------------- >> - Eco-Living - >> Whole Systems Design Services >> People - Place - Learning - Integration >> jo...@ec... <mailto:jo...@ec...> >> >> http://eco-living.net >> >> ------------------------------**------------------------------** >> ------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-**d2dvs2<http://p.sf.net/sfu/Boundary-d2dvs2> >> ______________________________**_________________ >> Plone-docs mailing list >> Plo...@li...urceforge.**net <Plo...@li...> >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> > >> >> https://lists.sourceforge.net/**lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >> >> -- >> Mikko Ohtamaa >> http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> >> >> > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------**-------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... > http://eco-living.net > > -- > Mikko Ohtamaa > <http://eco-living.net>http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: John S. <jo...@ec...> - 2012-04-13 20:42:35
|
I am totally new to github...the apparently relevant button says "Fork and Edit this file" - not sure if that is the correct thing to do? Please advise how to make the edit without making a mess... thanks, John S. On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: > Hi John, > > Mention early on, with link, to see the Hosting Guide for information > about production installations/deployments. > > > Good spot. Can you go ahead and fix it directly here? > > https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst > > -Mikko > > For example where it now says: > > ---------------------------------------- > ... > Installing Plone using Unified UNIX Installer > > Note > This is the recommended installation method > > This recipe is good for > Lightweight production sites > Plone development and testing on Ubuntu / Debian > ... > ------------------------------------------ > > ...add some following text like: > > "For information on using this installation with production > environments/deployments, see the [hosting guide]." > > There is a line that hints at that at the very end of the unified > installer section, and I think it could be clearer and sooner. > > thanks, > John S. > > On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: > > Hi, > > > > I try to modernize / centralize existing Plone installation > instructions. > > > > Please take a look on: > > > > > http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html > > > > ...and then take a stab on the document or me. > > > > Cheers, > > Mikko > > > > ----- > > > > Follow me in Twitter > > > > > > > > Read my blog > > > > > > > > > > > > -- > > View this message in context: > http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html > > Sent from the Documentation Team mailing list archive at Nabble.com. > > > > > ------------------------------------------------------------------------------ > > Better than sec? Nothing is better than sec when it comes to > > monitoring Big Data applications. Try Boundary one-second > > resolution app monitoring today. Free. > > http://p.sf.net/sfu/Boundary-dev2dev > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > <mailto:Plo...@li...> > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > John Schinnerer - M.A., Whole Systems Design > -------------------------------------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > http://eco-living.net > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > <mailto:Plo...@li...> > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > -- John Schinnerer - M.A., Whole Systems Design -------------------------------------------- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration jo...@ec... http://eco-living.net |
|
From: Mikko O. <mik...@re...> - 2012-04-13 06:56:44
|
Hi John, Mention early on, with link, to see the Hosting Guide for information > about production installations/deployments. > Good spot. Can you go ahead and fix it directly here? https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst -Mikko > For example where it now says: > > ---------------------------------------- > ... > Installing Plone using Unified UNIX Installer > > Note > This is the recommended installation method > > This recipe is good for > Lightweight production sites > Plone development and testing on Ubuntu / Debian > ... > ------------------------------------------ > > ...add some following text like: > > "For information on using this installation with production > environments/deployments, see the [hosting guide]." > > There is a line that hints at that at the very end of the unified > installer section, and I think it could be clearer and sooner. > > thanks, > John S. > > On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: > > Hi, > > > > I try to modernize / centralize existing Plone installation instructions. > > > > Please take a look on: > > > > > http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html > > > > ...and then take a stab on the document or me. > > > > Cheers, > > Mikko > > > > ----- > > > > Follow me in Twitter > > > > > > > > Read my blog > > > > > > > > > > > > -- > > View this message in context: > http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html > > Sent from the Documentation Team mailing list archive at Nabble.com. > > > > > ------------------------------------------------------------------------------ > > Better than sec? Nothing is better than sec when it comes to > > monitoring Big Data applications. Try Boundary one-second > > resolution app monitoring today. Free. > > http://p.sf.net/sfu/Boundary-dev2dev > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > John Schinnerer - M.A., Whole Systems Design > -------------------------------------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... > http://eco-living.net > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: John S. <jo...@ec...> - 2012-04-13 04:26:06
|
Aloha,
This is nice and clear and simple.
One suggestion to get people to the right places beyond this page more
clearly or quickly:
Mention early on, with link, to see the Hosting Guide for information
about production installations/deployments.
For example where it now says:
----------------------------------------
...
Installing Plone using Unified UNIX Installer
Note
This is the recommended installation method
This recipe is good for
Lightweight production sites
Plone development and testing on Ubuntu / Debian
...
------------------------------------------
...add some following text like:
"For information on using this installation with production
environments/deployments, see the [hosting guide]."
There is a line that hints at that at the very end of the unified
installer section, and I think it could be clearer and sooner.
thanks,
John S.
On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote:
> Hi,
>
> I try to modernize / centralize existing Plone installation instructions.
>
> Please take a look on:
>
> http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html
>
> ...and then take a stab on the document or me.
>
> Cheers,
> Mikko
>
> -----
>
> Follow me in Twitter
>
>
>
> Read my blog
>
>
>
>
>
> --
> View this message in context: http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html
> Sent from the Documentation Team mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
--
John Schinnerer - M.A., Whole Systems Design
--------------------------------------------
- Eco-Living -
Whole Systems Design Services
People - Place - Learning - Integration
jo...@ec...
http://eco-living.net
|
|
From: Dylan J. <dy...@dy...> - 2012-04-11 22:30:52
|
On 11/04/2012, at 6:10 PM, Jean Jordaan <jea...@gm...> wrote: > On Tue, Apr 10, 2012 at 10:03 PM, Mikko Ohtamaa > <mik...@re...> wrote: >>> short, ragged lines, and not reflowing paragraphs, for ease of editing & >>> versioning. >> >> Personally I don't care > > Good :-) > > While going through the dexterity manual, I formatted the last part > in that way. See the pull request: > https://github.com/giacomos/collective.dexteritymanual/pull/1 > >> * Modern editors can wrap lines (take that, pico!) > > Yeah, but I think that wrapping paragraphs is often counterproductive for text > source files. > >> * Also some people tend to justify text with somewhat sane line width >> (60-160) > > When the text source is meant to be read by many (e.g. README files), that make > sense. When it is mainly the source format for publication in other formats, > then not so much. These manuals will eventually distributed with the plone source and read from source. > > -- > jean . .. .... //\\\oo///\\ > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Jean J. <jea...@gm...> - 2012-04-11 08:10:24
|
On Tue, Apr 10, 2012 at 10:03 PM, Mikko Ohtamaa <mik...@re...> wrote: >> short, ragged lines, and not reflowing paragraphs, for ease of editing & >> versioning. > > Personally I don't care Good :-) While going through the dexterity manual, I formatted the last part in that way. See the pull request: https://github.com/giacomos/collective.dexteritymanual/pull/1 > * Modern editors can wrap lines (take that, pico!) Yeah, but I think that wrapping paragraphs is often counterproductive for text source files. > * Also some people tend to justify text with somewhat sane line width > (60-160) When the text source is meant to be read by many (e.g. README files), that make sense. When it is mainly the source format for publication in other formats, then not so much. -- jean . .. .... //\\\oo///\\ |
|
From: Mikko O. <mik...@re...> - 2012-04-10 17:04:45
|
Dylan Jay-4 wrote > > Begin forwarded message: > >> I've just returned from yet another memorable Plone event, the 2nd >> annualCioppino Sprint. For the past 4 days, twelve of us gathered at >> a house in lovely Bodega Bay, CA for a weekend of fun, relaxation, >> and giving back to the Plone community. >> >> The theme of the sprint was improving Plone's documentation and >> community infrastructure. On the first evening we gathered to >> brainstorm tasks, > I can do some "should-have-done-long-time-ago" spring cleaning on on c.dm if someone tells me which branch should land in :) BTW thanks for renaming all the .rst - that was so simple, but brilliant, idea. Cheers, Mikko ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Fwd-Report-from-Cioppino-Sprint-2012-tp7411833p7453607.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-04-10 15:23:20
|
Jean Jordaan wrote > > So I'd like to ask what your feelings would be about writing (or just > reading) > short, ragged lines, and not reflowing paragraphs, for ease of editing & > versioning. > Personally I don't care * Modern editors can wrap lines (take that, pico!) * Also some people tend to justify text with somewhat sane line width (60-160) I am happy as long as hard tabs are avoided (which I often found myself guilty). BTW created / creating this tool to validate various files in git pre-commit hook, including .rst - I hope to enforce policy where one cannot submit bad entries using Git and also Travis CI checks the files for bad Sphinx output: https://github.com/miohtama/vvv Cheers, -Mikko ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/One-sentence-per-line-tp7447819p7453152.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-04-10 15:23:10
|
Hi, I try to modernize / centralize existing Plone installation instructions. Please take a look on: http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html ...and then take a stab on the document or me. Cheers, Mikko ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Jean J. <jea...@gm...> - 2012-04-08 15:09:36
|
Hi there
Putting this out there for your thoughts:
By starting a new line at the end of each sentence, and splitting sentences
themselves at natural breaks between clauses, a text file becomes far
easier to edit and version control. Text editors are very good at
manipulating lines — so when each sentence is a contiguous block of lines,
your editor suddenly becomes a very powerful mechanism for quickly
rearranging clauses and ideas.
And your version-control system will love semantic linefeeds. Have you ever
changed a few words at the beginning of a paragraph, only to discover that
version control now thinks the whole text has changed?
from: http://rhodesmill.org/brandon/2012/one-sentence-per-line/
Documentation tends to be a rather personal thing, with different people used
to their own styles and the preferences of the editors that they use.
However it's also something we maintain in common, and that we version using
line-oriented tools.
As such, it would be good if we shared some understanding of how we want
things to work.
When I'm editing, I tend to re-flow very long lines to fit in 80 columns,
and I re-flow paragraphs when I've rewritten enough that most lines would
change anyway.
So I'd like to ask what your feelings would be about writing (or just reading)
short, ragged lines, and not reflowing paragraphs, for ease of editing &
versioning.
--
jean . .. .... //\\\oo///\\
|
|
From: Dylan J. <dy...@dy...> - 2012-03-27 23:57:44
|
Begin forwarded message: > Date: 27 March 2012 5:52:28 PM > Subject: Report from Cioppino Sprint 2012 > Source: Planet Plone > Author: David Glick > > I've just returned from yet another memorable Plone event, the 2nd > annualCioppino Sprint. For the past 4 days, twelve of us gathered at > a house in lovely Bodega Bay, CA for a weekend of fun, relaxation, > and giving back to the Plone community. > > The theme of the sprint was improving Plone's documentation and > community infrastructure. On the first evening we gathered to > brainstorm tasks, > ... <cool stuff that was done snipped> ... Really exciting to see so much effort put into documentation. > > One thing that did not happen at the sprint was a clear designation > of a revitalized documentation team to make sure that our > documentation is well-managed on an ongoing basis. Personally I feel > that this is a role that is lacking in the community—Mikko and > others are doing a fantastic job of getting people to add and update > documentation in the collective developer manual, but I there is a > need for a more focused manual and introductory documentation for > people who are trying to learn Plone development for the first time > rather than looking up particular tasks or topics—communally edited > documentation is inevitably of varying quality and relevance, and > newbies have no way to judge that. There is also a need to make sure > that old documents are updated or marked as obsolete as appropriate. > It's not entirely surprising that we've lacked this editing, as it > is a thankless task (everyone can get excited about new > documentation; someone always hates you when you delete something). > I don't have answers but I hope we can brainstorm as a community > about how to solve this problem (or maybe you can convince me I've > diagnosed the wrong problem.) > I've got a couple of ideas :) One of the things you said David on #sprint really hit home. Both the knowledgebase and the c.dm can suffer from the following problem. That people feel they have the authority to add and correct, but often not to delete, reorganise and merge content. The consequence is c.dm will make less and less sense read end to end over time, which is a shame as the real advantage c.dm has over the KB is its "browsability". What I mean by "browsability" is that I can find what I'm looking for by scrolling up and down and also navigating within the same section, rather than relying purely on google. I think solving the authority problem is what will prevent c.dm becoming a dumping ground like the KB is. Here's an idea to kick off discussion: Have a team of 2-3 who have the authority to consolidate c.dm. This doesn't mean they are the only ones that do that work, just that it gives you someone to ask your proposed restructure is a good idea or not. Think of it as a kind of FWT for c.dm. As an example I've thought for a long time we should rename the "tutorials" section to "Introduction to Plone's Architecture" and then move anything in there that doesn't fit to where it does fit, such as AGX into the content section. I feel I need to ask permission to make such a change but it's currently unclear who to ask and hence I've left it. Exactly the behaviour David described. If instead we had a small team with a joint vision of where the manual is going, I'd just put my proposed changes to them via this list and they can make that decision. Would this work? or is it overkill? Also, I think another thing that would help is some kind of mechanism of redirecting from the old location of moved content. Does RTD support this? |
|
From: Mikko O. <mik...@re...> - 2012-03-18 14:50:08
|
Done! Can you further delegate to access website team members (not sure what's the process here) On Sun, Mar 18, 2012 at 08:03, Jon Stahl <jon...@gm...> wrote: > On Sat, Mar 17, 2012 at 9:15 PM, Mikko Ohtamaa > <mik...@re...> wrote: > > Hi, > > > > On Fri, Mar 16, 2012 at 18:50, Tom Kapanka <sp...@ka...> wrote: > >> > >> To me, this is another argument for keeping our documentation "local"; > we > >> have access to analytics. Not sure if we can get stats from other areas > >> like RTD. I can be corrected though. > > > > > > We have Plone specific Google Analytics tracker on RTD docs. > > Cool, I don't see it under the Plone Foundation google analytics > accounts I have access to, could you permission jon...@gm... to > see it? > > :jon > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: Jon S. <jon...@gm...> - 2012-03-18 06:04:05
|
On Sat, Mar 17, 2012 at 9:15 PM, Mikko Ohtamaa <mik...@re...> wrote: > Hi, > > On Fri, Mar 16, 2012 at 18:50, Tom Kapanka <sp...@ka...> wrote: >> >> To me, this is another argument for keeping our documentation "local"; we >> have access to analytics. Not sure if we can get stats from other areas >> like RTD. I can be corrected though. > > > We have Plone specific Google Analytics tracker on RTD docs. Cool, I don't see it under the Plone Foundation google analytics accounts I have access to, could you permission jon...@gm... to see it? :jon |
|
From: Mikko O. <mik...@re...> - 2012-03-18 04:42:16
|
Hi, On Fri, Mar 16, 2012 at 18:50, Tom Kapanka <sp...@ka...> wrote: > To me, this is another argument for keeping our documentation "local"; we > have access to analytics. Not sure if we can get stats from other areas > like RTD. I can be corrected though. > We have Plone specific Google Analytics tracker on RTD docs. -Mikko > > -- > > ~Spanky > > On Mar 15, 2012, at 3:55 PM, Jon Stahl wrote: > > > Since we have a bit a conversation starting about Plone documentation, > > I though it would be helpful and interesting to share some stats from > > Plone.org's Google Analytics account about what people are looking for > > and finding w/r/t Plone.org documentation. (If anyone has interesting > > stats on our various externally-hosted docs, e.g. RTD, I'd love to get > > them or get access to them.) > > > > First, some toplines: > > > > Our docs section got about 500k visits in the past year originating > > with a search (the vast majority of searches from Google, no surprise > > there.) We also had about 85k searches on plone.org, excluding > > searches originating in the Products section. So, while it is true > > that most of people "search plone.org via Google" we are still seeing > > a substantial fraction of search usage happening internally. So I > > think it is important that we continue to invest in making plone.org > > searching as good as it can be. > > > > I also think it is interesting to look at the most commonly used > > search terms and landing pages. I looked at three things: > > > > 1) Top 100 Documentation pages reached via external (Google) searches > > 2) Top 100 Google Search terms landing on plone.org > > 3) Top 100 searches performed on plone.org (excluding searches > > starting in /products) > > > > Data dump below, but here's some interpretation: > > > > - Wow, looks like we've SEO-optimized for "xxx," let's slap some ads > > up there. ;-) > > - lots of interest in ldap, windows, webdav, active directory. > > - Also seeing strong interest in diazo, dexterity other core components > > - Common features like blogs, forums, handling PDFS, calendars, > facebook, rss > > - Lots of KB articles in our Top 100, this could be because we've > > moved lots of our official manual content off-site. > > > > Anyway, I hope this provides some useful food for thought for > > documentation authors, editors and developers. > > > > cheers, > > jon > > > > > > 1) Top 100 Documentation pages reached via external (Google) searches > > > > Landing Page Visits > > /documentation/glossary/xxx 20,224 > > /documentation 10,320 > > /documentation/kb/webdav 7,364 > > /documentation/kb/plone-apache/virtualhost 6,885 > > /documentation/kb/ldap-in-windows 6,517 > > /documentation/kb/using-pdb 6,278 > > > /documentation/manual/plone-community-developer-documentation/serving/http-request-and-response > 3,786 > > > /documentation/phc_topic_area?topic=Users,+Authentication,+and+Permissions > 3,602 > > /documentation/kb/single-sign-on-with-active-directory 3,322 > > /documentation/kb/internet-explorer-invisible-text 3,290 > > /documentation/kb/installing-a-plone-buildout-on-ubuntu 3,235 > > > /documentation/manual/developer-manual/indexing-and-searching/querying-the-catalog > 3,227 > > /documentation/kb/changing-the-admin-password 3,131 > > > /documentation/faq/on-windows-xp-i-get-no-python-installation-found-in-the-registry-when-installing-certain-products-1 > 3,083 > > /documentation/kb/plone-apache/preface 3,035 > > /documentation/kb/add-ons/installing 3,011 > > /documentation/kb/backup-plone 2,995 > > /documentation/kb/how-to-embed-content-flickr-youtube-or-myspace > 2,947 > > /documentation/kb/csv-files-display-browser-window-inline-excel > 2,907 > > /documentation/kb/using-z3c.form-forms-in-plone/tutorial-all-pages > 2,859 > > > /documentation/manual/developer-manual/managing-projects-with-buildout/understanding-buildout.cfg > 2,795 > > /documentation/kb/customizing-main-template-viewlets/tutorial-all-pages > 2,635 > > /documentation/kb/using-jquery-to-write-dependent-comboboxes 2,580 > > > /documentation/kb/developing-plone-with-eclipse/setting-up-pythonpath-in-eclipse > 2,572 > > > /documentation/manual/developer-manual/archetypes/fields/widgets-reference > 2,548 > > > /documentation/manual/developer-manual/archetypes/fields/fields-reference > 2,500 > > /documentation/movies/ 2,484 > > /documentation/manual/plone-4-user-manual/referencemanual-all-pages > 2,308 > > > /documentation/manual/plone-4-user-manual/introduction/plone-user-accounts > 2,212 > > /documentation/manual/developer-manual/managing-projects-with-buildout > 2,204 > > /documentation/kb/plone-with-apache 2,188 > > > /products/dexterity/documentation/manual/developer-manual/referencemanual-all-pages > 2,148 > > /documentation/error/attribute-flock 2,132 > > /documentation/manual/plone-4-user-manual 2,132 > > /documentation/error/importerror-no-module-named-implpython 2,092 > > /documentation/kb/singlesignonwindowsdomains 2,068 > > /documentation/manual/upgrade-guide 1,933 > > /documentation/error/ie500error 1,893 > > /documentation/kb/plone-behind-varnish-using-pound-for-ssl 1,845 > > /products/dexterity/documentation/manual/developer-manual 1,845 > > /documentation/topic/Configuration+and+Set-Up 1,837 > > > /documentation/manual/developer-manual/managing-projects-with-buildout/creating-a-buildout-for-your-project > 1,813 > > /documentation/faq/where-can-i-host-my-plone-site 1,797 > > /documentation/kb/addiconsortextwithlinks 1,749 > > /documentation/kb/i18n-for-developers 1,749 > > > /products/tinymce/documentation/manual/tinymce-user-manual/referencemanual-all-pages > 1,733 > > /documentation/kb/use-paster 1,725 > > /documentation/faq/what-is-a-cms 1,661 > > /documentation/kb/setup-from-source 1,661 > > /documentation/kb/backup-and-recover-data-fs-in-linux 1,653 > > /documentation/kb/plone-on-debian-etch 1,605 > > /documentation/kb/redirect-to-a-url-or-default-view 1,605 > > /documentation/kb/archgenxml-getting-started/relationships 1,597 > > /documentation/manual/theme-reference 1,597 > > /documentation/error/ioerror-decoder-jpeg-not-available 1,565 > > /documentation/kb/secure-login-without-plain-text-passwords 1,565 > > > /documentation/manual/plone-community-developer-documentation/searching-and-indexing/query > 1,549 > > /documentation/kb 1,541 > > /documentation/kb/change-the-logo-in-plone-3 1,517 > > /documentation/kb/using-buildout-on-windows 1,517 > > /documentation/kb/ask-for-help 1,501 > > > /documentation/kb/enable-full-text-indexing-of-word-documents-and-pdfs-in-plone-3-0-gnu-linux > 1,453 > > > /documentation/kb/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one > 1,373 > > > /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-global-definitions-in-templates > 1,365 > > /documentation/kb/plone-apache 1,357 > > /documentation/manual/developer-manual 1,341 > > /documentation/books 1,325 > > > /documentation/kb/customizing-main-template-viewlets/overriding-a-viewlet > 1,325 > > /documentation/kb/developing-plone-with-eclipse/creating-eclipse-project > 1,317 > > /documentation/error 1,301 > > /documentation/kb/working-with-resourceregistries/tutorial-all-pages > 1,301 > > > /documentation/manual/plone-community-developer-documentation/serving/traversing > 1,301 > > /documentation/manual/theme-reference/page/using-jquery-and-jquery-tools > 1,286 > > /documentation/error/nonetype-keys 1,278 > > /documentation/kb/authenticating-with-active-directory 1,278 > > /documentation/manual/theme-reference/quick-start/change-the-logo > 1,278 > > > /documentation/manual/developer-manual/archetypes/referencemanual-all-pages > 1,270 > > /documentation/manual/installing-plone/referencemanual-all-pages > 1,262 > > > /documentation/manual/theme-reference/buildingblocks/skin/templates/advanced-usage > 1,262 > > /documentation/kb/flickering-background-images-internet-explorer > 1,254 > > /documentation/kb/creating-a-content-type-for-plone-3-for-developers > 1,246 > > /documentation/kb/svn-import-to-plone-collective-unix 1,238 > > > /documentation/kb/handle-accented-characters-using-utf8-encoding-in-mysql > 1,222 > > /documentation/faq/how-do-i-restart-zope 1,214 > > > /documentation/kb/developing-plone-with-eclipse/creating-a-new-project-and-managing-your-project-with-subclipse > 1,206 > > /documentation/manual 1,198 > > /documentation/kb/simple-soap-client-using-suds 1,190 > > /documentation/manual/installing-plone/installation-quick-guide > 1,166 > > > /documentation/manual/theme-reference/buildingblocks/skin/style-sheets/css/css-quick-start > 1,166 > > /documentation/kb/replacing-tabs-with-images 1,118 > > /documentation/manual/developer-manual/archetypes 1,118 > > /documentation/kb/changing-tabs 1,110 > > > /documentation/kb/collaboration-using-the-sharing-tab/creating-a-simple-intranet > 1,086 > > /documentation/kb/active-directory-authentication 1,078 > > > /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/referencemanual-all-pages > 1,078 > > > /documentation/manual/installing-plone/installing-on-linux-unix-bsd/debian-libraries > 1,070 > > /documentation/kb/apache-ssl 1,062 > > > /documentation/kb/enable-indexing-of-pdf-and-word-docs-with-windows-in-five-steps-occurs-three-minutes-without-problems > 1,054 > > /documentation/kb/using-macros-and-metal-in-plone-page-templates > 1,046 > > /documentation/kb/simple-etc-rc-d-init-d-script-for-zeocluster > 1,030 > > > > 2) Top 100 Google Search terms landing on plone.org > > > > Search Term Total Unique Searches > > ldap 1,034 > > diazo 984 > > forum 946 > > blog 896 > > pdf 822 > > dexterity 780 > > facebook 763 > > calendar 722 > > ploneboard 687 > > wiki 665 > > video 659 > > demo 617 > > gallery 536 > > theme 524 > > collage 521 > > rss 517 > > buildout 512 > > ploneformgen 508 > > carousel 506 > > twitter 504 > > upgrade 492 > > captcha 477 > > mobile 449 > > workflow 447 > > portlet 444 > > upload 430 > > widget 402 > > form 389 > > google 371 > > social 369 > > menu 367 > > newsletter 362 > > editor 354 > > chat 350 > > redirect 350 > > tinymce 346 > > plone 341 > > plomino 331 > > themes 316 > > active directory 313 > > jquery 309 > > navigation 307 > > search 295 > > flowplayer 281 > > linguaplone 279 > > zope 279 > > survey 274 > > image 271 > > plone.app.theming 271 > > apache 269 > > PloneFormGen 268 > > poi 268 > > mail 267 > > dropdown 265 > > mysql 259 > > kupu 255 > > paster 255 > > collective 254 > > slideshow 253 > > fckeditor 247 > > ckeditor 246 > > formgen 243 > > zettwerk 242 > > intranet 233 > > portlets 230 > > backup 229 > > board 228 > > hotfix 227 > > cache 226 > > webdav 226 > > database 224 > > migration 224 > > xdv 223 > > maps 222 > > booking 221 > > install 213 > > logo 210 > > news 208 > > LDAP 207 > > flash 200 > > sql 197 > > css 196 > > plumi 195 > > email 194 > > photo 194 > > shop 194 > > python 193 > > archetypes 192 > > collections plone 3 188 > > portlets in the content column 187 > > language 185 > > forms 183 > > faq 180 > > getpaid 176 > > banner 175 > > discussion 170 > > Ploneboard 167 > > security 165 > > tag 164 > > raptus 163 > > > > > > 3) Top 100 searches performed on plone.org (excluding searches > > starting in /products) > > > > Search Term Start Page Total Unique Searches > > demo / 224 > > dexterity / 174 > > redirect /documentation/kb/redirect-to-a-url-or-default-view 158 > > portlets in the content column /documentation/kb/changing-tabs 128 > > upgrade /documentation 123 > > widget > /documentation/manual/developer-manual/archetypes/fields/widgets-reference > 116 > > .pid (entrance) 108 > > diazo / 108 > > default.cfg (entrance) 97 > > ldap / 92 > > diazo (entrance) 90 > > themes / 89 > > dexterity /documentation 88 > > buildout /documentation 87 > > facebook / 79 > > logo / 79 > > hotfix / 78 > > mobile / 72 > > calendar / 71 > > ploneformgen / 70 > > theme / 69 > > demo /documentation 67 > > forum (entrance) 67 > > upgrade / 64 > > wiki / 64 > > captcha (entrance) 63 > > workflow /documentation 63 > > carousel / 60 > > fckeditor / 58 > > portlets in the content column (entrance) 58 > > widget (entrance) 57 > > blog / 56 > > collections plone > > 3 > /documentation/kb/enable-collection-indices-fields-for-searching-for-custom-types > 56 > > security / 55 > > video / 55 > > buildout / 54 > > redirect (entrance) 54 > > zope / 54 > > ldap /documentation 53 > > blog (entrance) 52 > > ldap (entrance) 52 > > tinymce / 52 > > migration /documentation 51 > > plomino / 51 > > ploneboard / 50 > > deco / 49 > > collage / 48 > > plone.app.theming / 48 > > rss / 46 > > workflow / 46 > > install /documentation 45 > > paster > /documentation/manual/plone-community-developer-documentation/views/browserviews > 45 > > pdf (entrance) 44 > > pdf / 44 > > apache / 43 > > forum / 42 > > products / 42 > > using frames in plone (entrance) 42 > > intranet / 41 > > xdv / 41 > > jquery / 40 > > python / 40 > > backup /documentation 39 > > collage (entrance) 39 > > migration / 39 > > plone / 39 > > workflow (entrance) 39 > > apache (entrance) 38 > > gallery / 38 > > generate pdf file (entrance) 38 > > portlet / 38 > > dexterity (entrance) 37 > > getpaid (entrance) 37 > > mysql / 37 > > calendar (entrance) 36 > > navigation (entrance) 36 > > apache /documentation 35 > > newsletter / 35 > > PloneFormGen / 35 > > twitter / 34 > > test / 33 > > webdav / 33 > > collections plone > > 3 > /documentation/manual/theme-reference/buildingblocks/components/viewletsandportlets > 32 > > ploneboard (entrance) 32 > > theme (entrance) 32 > > buildout (entrance) 31 > > flowplayer / 31 > > linguaplone / 31 > > anchors (entrance) 30 > > captcha > /documentation/faq/how-can-i-test-which-version-of-plone-i-have-running 30 > > conference / 30 > > diazo /documentation 30 > > google / 30 > > nginx / 30 > > raptus / 30 > > wiki (entrance) 30 > > backup / 29 > > twitter (entrance) 29 > > paster /documentation 28 > > portlets / 28 > > --- > > Jon Stahl > > MPA Candidate, Evans School of Public Affairs > > University of Washington > > http://jstahl.org > > 206.226.0818 > > > > > ------------------------------------------------------------------------------ > > This SF email is sponsosred by: > > Try Windows Azure free for 90 days Click Here > > http://p.sf.net/sfu/sfd2d-msazure > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: Tom K. <sp...@ka...> - 2012-03-16 16:51:11
|
To me, this is another argument for keeping our documentation "local"; we have access to analytics. Not sure if we can get stats from other areas like RTD. I can be corrected though. -- ~Spanky On Mar 15, 2012, at 3:55 PM, Jon Stahl wrote: > Since we have a bit a conversation starting about Plone documentation, > I though it would be helpful and interesting to share some stats from > Plone.org's Google Analytics account about what people are looking for > and finding w/r/t Plone.org documentation. (If anyone has interesting > stats on our various externally-hosted docs, e.g. RTD, I'd love to get > them or get access to them.) > > First, some toplines: > > Our docs section got about 500k visits in the past year originating > with a search (the vast majority of searches from Google, no surprise > there.) We also had about 85k searches on plone.org, excluding > searches originating in the Products section. So, while it is true > that most of people "search plone.org via Google" we are still seeing > a substantial fraction of search usage happening internally. So I > think it is important that we continue to invest in making plone.org > searching as good as it can be. > > I also think it is interesting to look at the most commonly used > search terms and landing pages. I looked at three things: > > 1) Top 100 Documentation pages reached via external (Google) searches > 2) Top 100 Google Search terms landing on plone.org > 3) Top 100 searches performed on plone.org (excluding searches > starting in /products) > > Data dump below, but here's some interpretation: > > - Wow, looks like we've SEO-optimized for "xxx," let's slap some ads > up there. ;-) > - lots of interest in ldap, windows, webdav, active directory. > - Also seeing strong interest in diazo, dexterity other core components > - Common features like blogs, forums, handling PDFS, calendars, facebook, rss > - Lots of KB articles in our Top 100, this could be because we've > moved lots of our official manual content off-site. > > Anyway, I hope this provides some useful food for thought for > documentation authors, editors and developers. > > cheers, > jon > > > 1) Top 100 Documentation pages reached via external (Google) searches > > Landing Page Visits > /documentation/glossary/xxx 20,224 > /documentation 10,320 > /documentation/kb/webdav 7,364 > /documentation/kb/plone-apache/virtualhost 6,885 > /documentation/kb/ldap-in-windows 6,517 > /documentation/kb/using-pdb 6,278 > /documentation/manual/plone-community-developer-documentation/serving/http-request-and-response 3,786 > /documentation/phc_topic_area?topic=Users,+Authentication,+and+Permissions 3,602 > /documentation/kb/single-sign-on-with-active-directory 3,322 > /documentation/kb/internet-explorer-invisible-text 3,290 > /documentation/kb/installing-a-plone-buildout-on-ubuntu 3,235 > /documentation/manual/developer-manual/indexing-and-searching/querying-the-catalog 3,227 > /documentation/kb/changing-the-admin-password 3,131 > /documentation/faq/on-windows-xp-i-get-no-python-installation-found-in-the-registry-when-installing-certain-products-1 3,083 > /documentation/kb/plone-apache/preface 3,035 > /documentation/kb/add-ons/installing 3,011 > /documentation/kb/backup-plone 2,995 > /documentation/kb/how-to-embed-content-flickr-youtube-or-myspace 2,947 > /documentation/kb/csv-files-display-browser-window-inline-excel 2,907 > /documentation/kb/using-z3c.form-forms-in-plone/tutorial-all-pages 2,859 > /documentation/manual/developer-manual/managing-projects-with-buildout/understanding-buildout.cfg 2,795 > /documentation/kb/customizing-main-template-viewlets/tutorial-all-pages 2,635 > /documentation/kb/using-jquery-to-write-dependent-comboboxes 2,580 > /documentation/kb/developing-plone-with-eclipse/setting-up-pythonpath-in-eclipse 2,572 > /documentation/manual/developer-manual/archetypes/fields/widgets-reference 2,548 > /documentation/manual/developer-manual/archetypes/fields/fields-reference 2,500 > /documentation/movies/ 2,484 > /documentation/manual/plone-4-user-manual/referencemanual-all-pages 2,308 > /documentation/manual/plone-4-user-manual/introduction/plone-user-accounts 2,212 > /documentation/manual/developer-manual/managing-projects-with-buildout 2,204 > /documentation/kb/plone-with-apache 2,188 > /products/dexterity/documentation/manual/developer-manual/referencemanual-all-pages 2,148 > /documentation/error/attribute-flock 2,132 > /documentation/manual/plone-4-user-manual 2,132 > /documentation/error/importerror-no-module-named-implpython 2,092 > /documentation/kb/singlesignonwindowsdomains 2,068 > /documentation/manual/upgrade-guide 1,933 > /documentation/error/ie500error 1,893 > /documentation/kb/plone-behind-varnish-using-pound-for-ssl 1,845 > /products/dexterity/documentation/manual/developer-manual 1,845 > /documentation/topic/Configuration+and+Set-Up 1,837 > /documentation/manual/developer-manual/managing-projects-with-buildout/creating-a-buildout-for-your-project 1,813 > /documentation/faq/where-can-i-host-my-plone-site 1,797 > /documentation/kb/addiconsortextwithlinks 1,749 > /documentation/kb/i18n-for-developers 1,749 > /products/tinymce/documentation/manual/tinymce-user-manual/referencemanual-all-pages 1,733 > /documentation/kb/use-paster 1,725 > /documentation/faq/what-is-a-cms 1,661 > /documentation/kb/setup-from-source 1,661 > /documentation/kb/backup-and-recover-data-fs-in-linux 1,653 > /documentation/kb/plone-on-debian-etch 1,605 > /documentation/kb/redirect-to-a-url-or-default-view 1,605 > /documentation/kb/archgenxml-getting-started/relationships 1,597 > /documentation/manual/theme-reference 1,597 > /documentation/error/ioerror-decoder-jpeg-not-available 1,565 > /documentation/kb/secure-login-without-plain-text-passwords 1,565 > /documentation/manual/plone-community-developer-documentation/searching-and-indexing/query 1,549 > /documentation/kb 1,541 > /documentation/kb/change-the-logo-in-plone-3 1,517 > /documentation/kb/using-buildout-on-windows 1,517 > /documentation/kb/ask-for-help 1,501 > /documentation/kb/enable-full-text-indexing-of-word-documents-and-pdfs-in-plone-3-0-gnu-linux 1,453 > /documentation/kb/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one 1,373 > /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-global-definitions-in-templates 1,365 > /documentation/kb/plone-apache 1,357 > /documentation/manual/developer-manual 1,341 > /documentation/books 1,325 > /documentation/kb/customizing-main-template-viewlets/overriding-a-viewlet 1,325 > /documentation/kb/developing-plone-with-eclipse/creating-eclipse-project 1,317 > /documentation/error 1,301 > /documentation/kb/working-with-resourceregistries/tutorial-all-pages 1,301 > /documentation/manual/plone-community-developer-documentation/serving/traversing 1,301 > /documentation/manual/theme-reference/page/using-jquery-and-jquery-tools 1,286 > /documentation/error/nonetype-keys 1,278 > /documentation/kb/authenticating-with-active-directory 1,278 > /documentation/manual/theme-reference/quick-start/change-the-logo 1,278 > /documentation/manual/developer-manual/archetypes/referencemanual-all-pages 1,270 > /documentation/manual/installing-plone/referencemanual-all-pages 1,262 > /documentation/manual/theme-reference/buildingblocks/skin/templates/advanced-usage 1,262 > /documentation/kb/flickering-background-images-internet-explorer 1,254 > /documentation/kb/creating-a-content-type-for-plone-3-for-developers 1,246 > /documentation/kb/svn-import-to-plone-collective-unix 1,238 > /documentation/kb/handle-accented-characters-using-utf8-encoding-in-mysql 1,222 > /documentation/faq/how-do-i-restart-zope 1,214 > /documentation/kb/developing-plone-with-eclipse/creating-a-new-project-and-managing-your-project-with-subclipse 1,206 > /documentation/manual 1,198 > /documentation/kb/simple-soap-client-using-suds 1,190 > /documentation/manual/installing-plone/installation-quick-guide 1,166 > /documentation/manual/theme-reference/buildingblocks/skin/style-sheets/css/css-quick-start 1,166 > /documentation/kb/replacing-tabs-with-images 1,118 > /documentation/manual/developer-manual/archetypes 1,118 > /documentation/kb/changing-tabs 1,110 > /documentation/kb/collaboration-using-the-sharing-tab/creating-a-simple-intranet 1,086 > /documentation/kb/active-directory-authentication 1,078 > /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/referencemanual-all-pages 1,078 > /documentation/manual/installing-plone/installing-on-linux-unix-bsd/debian-libraries 1,070 > /documentation/kb/apache-ssl 1,062 > /documentation/kb/enable-indexing-of-pdf-and-word-docs-with-windows-in-five-steps-occurs-three-minutes-without-problems 1,054 > /documentation/kb/using-macros-and-metal-in-plone-page-templates 1,046 > /documentation/kb/simple-etc-rc-d-init-d-script-for-zeocluster 1,030 > > 2) Top 100 Google Search terms landing on plone.org > > Search Term Total Unique Searches > ldap 1,034 > diazo 984 > forum 946 > blog 896 > pdf 822 > dexterity 780 > facebook 763 > calendar 722 > ploneboard 687 > wiki 665 > video 659 > demo 617 > gallery 536 > theme 524 > collage 521 > rss 517 > buildout 512 > ploneformgen 508 > carousel 506 > twitter 504 > upgrade 492 > captcha 477 > mobile 449 > workflow 447 > portlet 444 > upload 430 > widget 402 > form 389 > google 371 > social 369 > menu 367 > newsletter 362 > editor 354 > chat 350 > redirect 350 > tinymce 346 > plone 341 > plomino 331 > themes 316 > active directory 313 > jquery 309 > navigation 307 > search 295 > flowplayer 281 > linguaplone 279 > zope 279 > survey 274 > image 271 > plone.app.theming 271 > apache 269 > PloneFormGen 268 > poi 268 > mail 267 > dropdown 265 > mysql 259 > kupu 255 > paster 255 > collective 254 > slideshow 253 > fckeditor 247 > ckeditor 246 > formgen 243 > zettwerk 242 > intranet 233 > portlets 230 > backup 229 > board 228 > hotfix 227 > cache 226 > webdav 226 > database 224 > migration 224 > xdv 223 > maps 222 > booking 221 > install 213 > logo 210 > news 208 > LDAP 207 > flash 200 > sql 197 > css 196 > plumi 195 > email 194 > photo 194 > shop 194 > python 193 > archetypes 192 > collections plone 3 188 > portlets in the content column 187 > language 185 > forms 183 > faq 180 > getpaid 176 > banner 175 > discussion 170 > Ploneboard 167 > security 165 > tag 164 > raptus 163 > > > 3) Top 100 searches performed on plone.org (excluding searches > starting in /products) > > Search Term Start Page Total Unique Searches > demo / 224 > dexterity / 174 > redirect /documentation/kb/redirect-to-a-url-or-default-view 158 > portlets in the content column /documentation/kb/changing-tabs 128 > upgrade /documentation 123 > widget /documentation/manual/developer-manual/archetypes/fields/widgets-reference 116 > .pid (entrance) 108 > diazo / 108 > default.cfg (entrance) 97 > ldap / 92 > diazo (entrance) 90 > themes / 89 > dexterity /documentation 88 > buildout /documentation 87 > facebook / 79 > logo / 79 > hotfix / 78 > mobile / 72 > calendar / 71 > ploneformgen / 70 > theme / 69 > demo /documentation 67 > forum (entrance) 67 > upgrade / 64 > wiki / 64 > captcha (entrance) 63 > workflow /documentation 63 > carousel / 60 > fckeditor / 58 > portlets in the content column (entrance) 58 > widget (entrance) 57 > blog / 56 > collections plone > 3 /documentation/kb/enable-collection-indices-fields-for-searching-for-custom-types 56 > security / 55 > video / 55 > buildout / 54 > redirect (entrance) 54 > zope / 54 > ldap /documentation 53 > blog (entrance) 52 > ldap (entrance) 52 > tinymce / 52 > migration /documentation 51 > plomino / 51 > ploneboard / 50 > deco / 49 > collage / 48 > plone.app.theming / 48 > rss / 46 > workflow / 46 > install /documentation 45 > paster /documentation/manual/plone-community-developer-documentation/views/browserviews 45 > pdf (entrance) 44 > pdf / 44 > apache / 43 > forum / 42 > products / 42 > using frames in plone (entrance) 42 > intranet / 41 > xdv / 41 > jquery / 40 > python / 40 > backup /documentation 39 > collage (entrance) 39 > migration / 39 > plone / 39 > workflow (entrance) 39 > apache (entrance) 38 > gallery / 38 > generate pdf file (entrance) 38 > portlet / 38 > dexterity (entrance) 37 > getpaid (entrance) 37 > mysql / 37 > calendar (entrance) 36 > navigation (entrance) 36 > apache /documentation 35 > newsletter / 35 > PloneFormGen / 35 > twitter / 34 > test / 33 > webdav / 33 > collections plone > 3 /documentation/manual/theme-reference/buildingblocks/components/viewletsandportlets 32 > ploneboard (entrance) 32 > theme (entrance) 32 > buildout (entrance) 31 > flowplayer / 31 > linguaplone / 31 > anchors (entrance) 30 > captcha /documentation/faq/how-can-i-test-which-version-of-plone-i-have-running 30 > conference / 30 > diazo /documentation 30 > google / 30 > nginx / 30 > raptus / 30 > wiki (entrance) 30 > backup / 29 > twitter (entrance) 29 > paster /documentation 28 > portlets / 28 > --- > Jon Stahl > MPA Candidate, Evans School of Public Affairs > University of Washington > http://jstahl.org > 206.226.0818 > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Jon S. <jon...@gm...> - 2012-03-15 22:55:58
|
Since we have a bit a conversation starting about Plone documentation, I though it would be helpful and interesting to share some stats from Plone.org's Google Analytics account about what people are looking for and finding w/r/t Plone.org documentation. (If anyone has interesting stats on our various externally-hosted docs, e.g. RTD, I'd love to get them or get access to them.) First, some toplines: Our docs section got about 500k visits in the past year originating with a search (the vast majority of searches from Google, no surprise there.) We also had about 85k searches on plone.org, excluding searches originating in the Products section. So, while it is true that most of people "search plone.org via Google" we are still seeing a substantial fraction of search usage happening internally. So I think it is important that we continue to invest in making plone.org searching as good as it can be. I also think it is interesting to look at the most commonly used search terms and landing pages. I looked at three things: 1) Top 100 Documentation pages reached via external (Google) searches 2) Top 100 Google Search terms landing on plone.org 3) Top 100 searches performed on plone.org (excluding searches starting in /products) Data dump below, but here's some interpretation: - Wow, looks like we've SEO-optimized for "xxx," let's slap some ads up there. ;-) - lots of interest in ldap, windows, webdav, active directory. - Also seeing strong interest in diazo, dexterity other core components - Common features like blogs, forums, handling PDFS, calendars, facebook, rss - Lots of KB articles in our Top 100, this could be because we've moved lots of our official manual content off-site. Anyway, I hope this provides some useful food for thought for documentation authors, editors and developers. cheers, jon 1) Top 100 Documentation pages reached via external (Google) searches Landing Page Visits /documentation/glossary/xxx 20,224 /documentation 10,320 /documentation/kb/webdav 7,364 /documentation/kb/plone-apache/virtualhost 6,885 /documentation/kb/ldap-in-windows 6,517 /documentation/kb/using-pdb 6,278 /documentation/manual/plone-community-developer-documentation/serving/http-request-and-response 3,786 /documentation/phc_topic_area?topic=Users,+Authentication,+and+Permissions 3,602 /documentation/kb/single-sign-on-with-active-directory 3,322 /documentation/kb/internet-explorer-invisible-text 3,290 /documentation/kb/installing-a-plone-buildout-on-ubuntu 3,235 /documentation/manual/developer-manual/indexing-and-searching/querying-the-catalog 3,227 /documentation/kb/changing-the-admin-password 3,131 /documentation/faq/on-windows-xp-i-get-no-python-installation-found-in-the-registry-when-installing-certain-products-1 3,083 /documentation/kb/plone-apache/preface 3,035 /documentation/kb/add-ons/installing 3,011 /documentation/kb/backup-plone 2,995 /documentation/kb/how-to-embed-content-flickr-youtube-or-myspace 2,947 /documentation/kb/csv-files-display-browser-window-inline-excel 2,907 /documentation/kb/using-z3c.form-forms-in-plone/tutorial-all-pages 2,859 /documentation/manual/developer-manual/managing-projects-with-buildout/understanding-buildout.cfg 2,795 /documentation/kb/customizing-main-template-viewlets/tutorial-all-pages 2,635 /documentation/kb/using-jquery-to-write-dependent-comboboxes 2,580 /documentation/kb/developing-plone-with-eclipse/setting-up-pythonpath-in-eclipse 2,572 /documentation/manual/developer-manual/archetypes/fields/widgets-reference 2,548 /documentation/manual/developer-manual/archetypes/fields/fields-reference 2,500 /documentation/movies/ 2,484 /documentation/manual/plone-4-user-manual/referencemanual-all-pages 2,308 /documentation/manual/plone-4-user-manual/introduction/plone-user-accounts 2,212 /documentation/manual/developer-manual/managing-projects-with-buildout 2,204 /documentation/kb/plone-with-apache 2,188 /products/dexterity/documentation/manual/developer-manual/referencemanual-all-pages 2,148 /documentation/error/attribute-flock 2,132 /documentation/manual/plone-4-user-manual 2,132 /documentation/error/importerror-no-module-named-implpython 2,092 /documentation/kb/singlesignonwindowsdomains 2,068 /documentation/manual/upgrade-guide 1,933 /documentation/error/ie500error 1,893 /documentation/kb/plone-behind-varnish-using-pound-for-ssl 1,845 /products/dexterity/documentation/manual/developer-manual 1,845 /documentation/topic/Configuration+and+Set-Up 1,837 /documentation/manual/developer-manual/managing-projects-with-buildout/creating-a-buildout-for-your-project 1,813 /documentation/faq/where-can-i-host-my-plone-site 1,797 /documentation/kb/addiconsortextwithlinks 1,749 /documentation/kb/i18n-for-developers 1,749 /products/tinymce/documentation/manual/tinymce-user-manual/referencemanual-all-pages 1,733 /documentation/kb/use-paster 1,725 /documentation/faq/what-is-a-cms 1,661 /documentation/kb/setup-from-source 1,661 /documentation/kb/backup-and-recover-data-fs-in-linux 1,653 /documentation/kb/plone-on-debian-etch 1,605 /documentation/kb/redirect-to-a-url-or-default-view 1,605 /documentation/kb/archgenxml-getting-started/relationships 1,597 /documentation/manual/theme-reference 1,597 /documentation/error/ioerror-decoder-jpeg-not-available 1,565 /documentation/kb/secure-login-without-plain-text-passwords 1,565 /documentation/manual/plone-community-developer-documentation/searching-and-indexing/query 1,549 /documentation/kb 1,541 /documentation/kb/change-the-logo-in-plone-3 1,517 /documentation/kb/using-buildout-on-windows 1,517 /documentation/kb/ask-for-help 1,501 /documentation/kb/enable-full-text-indexing-of-word-documents-and-pdfs-in-plone-3-0-gnu-linux 1,453 /documentation/kb/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one 1,373 /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-global-definitions-in-templates 1,365 /documentation/kb/plone-apache 1,357 /documentation/manual/developer-manual 1,341 /documentation/books 1,325 /documentation/kb/customizing-main-template-viewlets/overriding-a-viewlet 1,325 /documentation/kb/developing-plone-with-eclipse/creating-eclipse-project 1,317 /documentation/error 1,301 /documentation/kb/working-with-resourceregistries/tutorial-all-pages 1,301 /documentation/manual/plone-community-developer-documentation/serving/traversing 1,301 /documentation/manual/theme-reference/page/using-jquery-and-jquery-tools 1,286 /documentation/error/nonetype-keys 1,278 /documentation/kb/authenticating-with-active-directory 1,278 /documentation/manual/theme-reference/quick-start/change-the-logo 1,278 /documentation/manual/developer-manual/archetypes/referencemanual-all-pages 1,270 /documentation/manual/installing-plone/referencemanual-all-pages 1,262 /documentation/manual/theme-reference/buildingblocks/skin/templates/advanced-usage 1,262 /documentation/kb/flickering-background-images-internet-explorer 1,254 /documentation/kb/creating-a-content-type-for-plone-3-for-developers 1,246 /documentation/kb/svn-import-to-plone-collective-unix 1,238 /documentation/kb/handle-accented-characters-using-utf8-encoding-in-mysql 1,222 /documentation/faq/how-do-i-restart-zope 1,214 /documentation/kb/developing-plone-with-eclipse/creating-a-new-project-and-managing-your-project-with-subclipse 1,206 /documentation/manual 1,198 /documentation/kb/simple-soap-client-using-suds 1,190 /documentation/manual/installing-plone/installation-quick-guide 1,166 /documentation/manual/theme-reference/buildingblocks/skin/style-sheets/css/css-quick-start 1,166 /documentation/kb/replacing-tabs-with-images 1,118 /documentation/manual/developer-manual/archetypes 1,118 /documentation/kb/changing-tabs 1,110 /documentation/kb/collaboration-using-the-sharing-tab/creating-a-simple-intranet 1,086 /documentation/kb/active-directory-authentication 1,078 /documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/referencemanual-all-pages 1,078 /documentation/manual/installing-plone/installing-on-linux-unix-bsd/debian-libraries 1,070 /documentation/kb/apache-ssl 1,062 /documentation/kb/enable-indexing-of-pdf-and-word-docs-with-windows-in-five-steps-occurs-three-minutes-without-problems 1,054 /documentation/kb/using-macros-and-metal-in-plone-page-templates 1,046 /documentation/kb/simple-etc-rc-d-init-d-script-for-zeocluster 1,030 2) Top 100 Google Search terms landing on plone.org Search Term Total Unique Searches ldap 1,034 diazo 984 forum 946 blog 896 pdf 822 dexterity 780 facebook 763 calendar 722 ploneboard 687 wiki 665 video 659 demo 617 gallery 536 theme 524 collage 521 rss 517 buildout 512 ploneformgen 508 carousel 506 twitter 504 upgrade 492 captcha 477 mobile 449 workflow 447 portlet 444 upload 430 widget 402 form 389 google 371 social 369 menu 367 newsletter 362 editor 354 chat 350 redirect 350 tinymce 346 plone 341 plomino 331 themes 316 active directory 313 jquery 309 navigation 307 search 295 flowplayer 281 linguaplone 279 zope 279 survey 274 image 271 plone.app.theming 271 apache 269 PloneFormGen 268 poi 268 mail 267 dropdown 265 mysql 259 kupu 255 paster 255 collective 254 slideshow 253 fckeditor 247 ckeditor 246 formgen 243 zettwerk 242 intranet 233 portlets 230 backup 229 board 228 hotfix 227 cache 226 webdav 226 database 224 migration 224 xdv 223 maps 222 booking 221 install 213 logo 210 news 208 LDAP 207 flash 200 sql 197 css 196 plumi 195 email 194 photo 194 shop 194 python 193 archetypes 192 collections plone 3 188 portlets in the content column 187 language 185 forms 183 faq 180 getpaid 176 banner 175 discussion 170 Ploneboard 167 security 165 tag 164 raptus 163 3) Top 100 searches performed on plone.org (excluding searches starting in /products) Search Term Start Page Total Unique Searches demo / 224 dexterity / 174 redirect /documentation/kb/redirect-to-a-url-or-default-view 158 portlets in the content column /documentation/kb/changing-tabs 128 upgrade /documentation 123 widget /documentation/manual/developer-manual/archetypes/fields/widgets-reference 116 .pid (entrance) 108 diazo / 108 default.cfg (entrance) 97 ldap / 92 diazo (entrance) 90 themes / 89 dexterity /documentation 88 buildout /documentation 87 facebook / 79 logo / 79 hotfix / 78 mobile / 72 calendar / 71 ploneformgen / 70 theme / 69 demo /documentation 67 forum (entrance) 67 upgrade / 64 wiki / 64 captcha (entrance) 63 workflow /documentation 63 carousel / 60 fckeditor / 58 portlets in the content column (entrance) 58 widget (entrance) 57 blog / 56 collections plone 3 /documentation/kb/enable-collection-indices-fields-for-searching-for-custom-types 56 security / 55 video / 55 buildout / 54 redirect (entrance) 54 zope / 54 ldap /documentation 53 blog (entrance) 52 ldap (entrance) 52 tinymce / 52 migration /documentation 51 plomino / 51 ploneboard / 50 deco / 49 collage / 48 plone.app.theming / 48 rss / 46 workflow / 46 install /documentation 45 paster /documentation/manual/plone-community-developer-documentation/views/browserviews 45 pdf (entrance) 44 pdf / 44 apache / 43 forum / 42 products / 42 using frames in plone (entrance) 42 intranet / 41 xdv / 41 jquery / 40 python / 40 backup /documentation 39 collage (entrance) 39 migration / 39 plone / 39 workflow (entrance) 39 apache (entrance) 38 gallery / 38 generate pdf file (entrance) 38 portlet / 38 dexterity (entrance) 37 getpaid (entrance) 37 mysql / 37 calendar (entrance) 36 navigation (entrance) 36 apache /documentation 35 newsletter / 35 PloneFormGen / 35 twitter / 34 test / 33 webdav / 33 collections plone 3 /documentation/manual/theme-reference/buildingblocks/components/viewletsandportlets 32 ploneboard (entrance) 32 theme (entrance) 32 buildout (entrance) 31 flowplayer / 31 linguaplone / 31 anchors (entrance) 30 captcha /documentation/faq/how-can-i-test-which-version-of-plone-i-have-running 30 conference / 30 diazo /documentation 30 google / 30 nginx / 30 raptus / 30 wiki (entrance) 30 backup / 29 twitter (entrance) 29 paster /documentation 28 portlets / 28 --- Jon Stahl MPA Candidate, Evans School of Public Affairs University of Washington http://jstahl.org 206.226.0818 |
|
From: Gert <ge...@ps...> - 2012-03-04 22:20:28
|
Hi! Don't know, if this is the proper way, but this list is listed on the page. When working through the guide I found some broken Links: Page: http://plone.org/documentation/manual/theme-reference/buildingblocks/skin/templates/overview Link.text: ZPT Reference on Zope.org Link.destination: http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/AppendixC.stx Link.newDestination?: http://docs.zope.org/zope2/zope2book/AppendixC.html Link.text: There's a useful introduction to this in the Plone User Link.destination: http://plone.org/documentation/plone-2.5-user-manual/managing-content/folder-view/ Link.newDestination?: http://plone.org/documentation/manual/plone-2.5-user-manual/managing-content/folder-view Link.newDestination?: http://plone.org/documentation/manual/plone-4-user-manual/managing-content/folder-view A letter too much? <: to format the a time field according to the default >: to format the time field according to the default hth, Gert |
|
From: Jon S. <jon...@gm...> - 2012-02-14 23:48:52
|
Hi all- I've just thrown together a very short document on our generic upgrade procedure for buildout-based installations. Changes/corrections/improvements welcome, I'm hardly an expert at this! https://plone.org/documentation/manual/upgrade-guide/version/minor-version-upgrades :jon --- Jon Stahl MPA Candidate, Evans School of Public Affairs University of Washington http://jstahl.org 206.226.0818 |
|
From: Jon S. <jon...@gm...> - 2012-02-14 02:48:11
|
Alan- It is now online at https://plone.org/documentation/kb/plone-4-windows-installer. I do not have the knowledge to edit this very well, but since it is a Knowledge Base article, this means that anyone with Collective privs can edit/improve it. :jon On Mon, Feb 13, 2012 at 8:25 AM, Alan Runyan <ru...@gm...> wrote: > https://docs.google.com/document/d/19-o6yYJWuvw7eyUiLs_b8br4C-Kb8RcyHcQSIf_4Pb4/edit > > Please put this document somewhere visible. It probably needs editing. > > On Mon, Feb 13, 2012 at 1:43 AM, Mikko Ohtamaa > <mik...@re...> wrote: >> Bump. >> >> Someone must know where and how Windows installer is being created? >> >> >> Mikko Ohtamaa wrote >>> >>> Hi, >>> >>> Are there instructions to update Windows installer somewhere? >>> >>> Current Plone 4.1 installer has some serious issues regarding >>> functionality and user friendliness >>> >>> https://dev.plone.org/ticket/12494 >>> >>> https://dev.plone.org/ticket/12495 >>> |
|
From: Dylan J. <dy...@dy...> - 2012-02-09 21:54:56
|
On 10/02/2012, at 8:26 AM, Mikko Ohtamaa <mik...@re...> wrote: > > JonStahl wrote >> >> On Thu, Jan 26, 2012 at 3:13 PM, Dylan Jay <dylan@> wrote: >>> On 27/01/2012, at 7:17 AM, Mikko Ohtamaa wrote: >>> >>>> Hi all, >>>> >>>> After successful take down of api.plone.org I hope to continue my >>>> kill it >>>> with fire spree. >>>> >>>> http://plone.org/documentation/manual/developer-manual has not seen >>>> recent >>>> updates. >>>> >>>> It contains vast amount of deprecated information. >>>> >>>> Does anyone actively maintain it? Last update is ~300 days ago. >>>> >>>> My suggestion is that we move everything to Sphinx doc and take down >>>> the >>>> section on plone.org. Some parts have been moved already. >>> >>> >> >> Is there anything in there that is not outdated and is not replicated >> in the collective developer manual? >> >> > > I am not sure about the replication status as I have been moving just tiny > bits myself. > > Someone should read through both manuals and copy all bits still left on the > official manual only. Same thing for some of the knowledgebase content. Anything duplicated in kb needs to be depricated and a link to the manual version > > -Mikko > > > > ----- > > Follow me in Twitter > > > > Read my blog > > > > > > -- > View this message in context: http://plone.293351.n2.nabble.com/Taking-down-documentation-manual-developer-manual-tp7228122p7270787.html > Sent from the Documentation Team mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Mikko O. <mik...@re...> - 2012-02-09 21:26:40
|
JonStahl wrote > > On Thu, Jan 26, 2012 at 3:13 PM, Dylan Jay <dylan@> wrote: >> On 27/01/2012, at 7:17 AM, Mikko Ohtamaa wrote: >> >>> Hi all, >>> >>> After successful take down of api.plone.org I hope to continue my >>> kill it >>> with fire spree. >>> >>> http://plone.org/documentation/manual/developer-manual has not seen >>> recent >>> updates. >>> >>> It contains vast amount of deprecated information. >>> >>> Does anyone actively maintain it? Last update is ~300 days ago. >>> >>> My suggestion is that we move everything to Sphinx doc and take down >>> the >>> section on plone.org. Some parts have been moved already. >> >> > > Is there anything in there that is not outdated and is not replicated > in the collective developer manual? > > I am not sure about the replication status as I have been moving just tiny bits myself. Someone should read through both manuals and copy all bits still left on the official manual only. -Mikko ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Taking-down-documentation-manual-developer-manual-tp7228122p7270787.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Jon S. <jon...@gm...> - 2012-02-09 04:05:34
|
Hi all! In preparation for the upcoming Cioppino Sprint, which will likely focus largely on improving plone.org, I took a bit of time to think about what a roadmap for improving the infrastructure of our docs + products sections could look like. My thinking is grounded in two key assumptions: 1) The experiments we've been doing with Github version-controlled, Sphinx-rendered documentation has been highly successful (thanks, Mikko & Dylan for showing us the way!) and we should base our future around this appraoch. 2) For products, we need to transition towards a "scrape data from Pypi" type approach, again the actions of our developers are speaking loudly here. I've taken a stab at writing up some more detailed thoughts that are still half-baked, but I'd like to offer them up for comments/feedback/constructive edits. https://docs.google.com/document/d/1OMSwK7XlWSnfw4MsQ2vc8LOvMefm6WTbBOVtn7d2t7k/edit?hl=en_US You'll be able to add ideas/comment/etc there. It is my hope that in a week or two, we'll have a reasonable working consensus around a path forward. I'll then try to turn these into a bit of a "roadmap" document that will inform the Cioppino sprinters' agenda (no promises). cheers, jon --- Jon Stahl MPA Candidate, Evans School of Public Affairs University of Washington http://jstahl.org 206.226.0818 |
|
From: Jon S. <jon...@gm...> - 2012-02-08 03:47:40
|
On Thu, Jan 26, 2012 at 3:13 PM, Dylan Jay <dy...@dy...> wrote: > On 27/01/2012, at 7:17 AM, Mikko Ohtamaa wrote: > >> Hi all, >> >> After successful take down of api.plone.org I hope to continue my >> kill it >> with fire spree. >> >> http://plone.org/documentation/manual/developer-manual has not seen >> recent >> updates. >> >> It contains vast amount of deprecated information. >> >> Does anyone actively maintain it? Last update is ~300 days ago. >> >> My suggestion is that we move everything to Sphinx doc and take down >> the >> section on plone.org. Some parts have been moved already. > > +1 > > Btw, I'm working on getting the sphinx docs back up plone.org such > that it will be updated once a day. > >> >> Of course this would involve some politics as I believe official >> developer >> manual is copyrighted by the foundation, but collective docs are by >> individual contributors. Is there anything in there that is not outdated and is not replicated in the collective developer manual? :jon |
|
From: Dylan J. <dy...@dy...> - 2012-01-26 23:44:21
|
On 27/01/2012, at 7:17 AM, Mikko Ohtamaa wrote: > Hi all, > > After successful take down of api.plone.org I hope to continue my > kill it > with fire spree. > > http://plone.org/documentation/manual/developer-manual has not seen > recent > updates. > > It contains vast amount of deprecated information. > > Does anyone actively maintain it? Last update is ~300 days ago. > > My suggestion is that we move everything to Sphinx doc and take down > the > section on plone.org. Some parts have been moved already. +1 Btw, I'm working on getting the sphinx docs back up plone.org such that it will be updated once a day. > > Of course this would involve some politics as I believe official > developer > manual is copyrighted by the foundation, but collective docs are by > individual contributors. > > > ----- > > Follow me in Twitter > > > > Read my blog > > > > > > -- > View this message in context: http://plone.293351.n2.nabble.com/Taking-down-documentation-manual-developer-manual-tp7228122p7228122.html > Sent from the Documentation Team mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft > developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, > MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Mikko O. <mik...@re...> - 2012-01-26 20:17:44
|
Hi all, After successful take down of api.plone.org I hope to continue my kill it with fire spree. http://plone.org/documentation/manual/developer-manual has not seen recent updates. It contains vast amount of deprecated information. Does anyone actively maintain it? Last update is ~300 days ago. My suggestion is that we move everything to Sphinx doc and take down the section on plone.org. Some parts have been moved already. Of course this would involve some politics as I believe official developer manual is copyrighted by the foundation, but collective docs are by individual contributors. ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Taking-down-documentation-manual-developer-manual-tp7228122p7228122.html Sent from the Documentation Team mailing list archive at Nabble.com. |
173 messages has been excluded from this view by a project administrator.
