plone-docs — Discussion about the Plone documentation

Re: [Plone-docs] Status: the case for WikiWords

[Amr M. <aea...@ya...>]

Wow! great post! I'm going to hold on to these "Initial Phase" type posts and
put them in a folder and try to put them all together later on. I think it
would be great for people to see what thinking processes went into how the
things are going to turn out in the future :)

I would just like to comment on the "comment clutter" scenario that can happen
in backtalk. Maybe something like the "Active Renderer" On Marc Barrot's site
could help? ( http://radio.weblogs.com/0104487/outlines/aR/activeRenderer.html
) Basically the idea is to use JavaScript to hide details of his weblog
entries. Essentially, the reader can click on the outline item to see the
comments, otherwise they're out of the way, but still logically/visually linked
to a given paragraph. The concept is essentially borrowed from RadioUserland's
Instant/outliner concept, and extended to the webpage. 

Please don't treat this as a feature request, I'm just throwing this out as
part of the brainstorming that is going on. This may have been considered
already.

I'll have to digest the rest, but a very thought provoking post indeed!

Thanks,

Amr

--- laura trippi <lat...@sf...> wrote:
> Working to catch up and synthesize all this, I'm reminded of why I love 
> zwikis! =}
> 
> This is long -- apologies. But there was lot to digest.
> 
...
Text Clipped..

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

[Plone-docs] OSX Plone Installer

[Amr M. <aea...@ya...>]

Hi,
   I guess I should be directing this message to DreamCatcher, but I'll just
post it here and hope he's reading it. 

I have run the Plone installer for OSX after installing Jaguar (10.2) and I get
the Plone instance in my applications folder okay.

Problem is that when I try to run the Controller, it fires up the interface,
but after a couple of seconds, it dies on me with a message that "..The
application has quit unexpectedly"

On the original install, it was giving me an "ioctl" error but the app would
stay on. Then I noticed that the user in there was set to "sidnei" so I changed
it to my user id on my iBook which has admin privs on it. After that it won't
start period. I don't have the builtin Apache running.

Also I noticed that in the Plone folder, the zope.conf file had the ZOPE_PORT
set to 8000. Is this a ZEO thing? I changed it to 8080 to conform with the
other conf file, but it still craps out on me unexpectedly.

Has anyone else been able to run the OSX Installer and get a Plone instance
working that way?

TIA,

-Amr


__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

Re: [Plone-docs] Status: the case for WikiWords

[laura t. <lat...@sf...>]

Working to catch up and synthesize all this, I'm reminded of why I love 
zwikis! =}

This is long -- apologies. But there was lot to digest.

Mark McEahern wrote:

 > I'm sure as we work together, a style and process will
 > emerge.

This is important, I think. Good conventions and light weight tools 
will help us manage a process whose complexities we can't foresee.

So far, the discussion has generated a small *goldmine* of ideas about 
things needed to support the live-book, distributed authoring process. 
Has this been done before? No?! Great! (Or if there are examples, it 
might be good to look at them.)

In any case, I found myself resorting to WikiWords in my mind to make 
sense of it all. Why? WikiNames and WikiBadges are incredibly powerful 
tools for designing and capturing conventions on the fly, and could 
answer a number of issues that have come up already.

For example, the CVS question.

Andy McKay wrote:

 > Unfortunately CVS doesnt really fit in with the Zope model.

That's interesting. In what way?

 > The point of this is that
 > everyone can comment on the book and the comments appear in line. Hmm.
 > Thinking about it more it would remove the point of BackTalk.

Maybe we shouldn't jump too quickly over the role that CMFBackTalk plays 
in all this. I mean, without going overboard, can we take a little time 
to consider its functionality?

We have the opportunity of pooling some fine minds toward the design of 
a great online authoring tool for Plone.

Kapil, maybe you want to avert your eyes for a moment. ;)

I'm not familiar with the background on BackTalk or with what's involved 
in adapting STX for various uses. But SAY, JUST FOR A MOMENT, we could 
use WikiNames in CMFBackTalk. And say they created pages, not in 
CMFBackTalk but in a zWiki back end to the book. (I don't mean "back 
matter," this part wouldn't be published.) Page creation could of course 
be restricted to certain categories of contributors.


MANAGING MULTIPLE TYPES OF CONTRIBUTORS

Amr Malik wrote:
 > 1. We need to have people commit for certain sections of the book, and
 > make this commitment transparent ("DocBowl" if you will). Somehow if
 > we can record activity against an general area that would be good. So
 > if someone doesn't have the time any more, someone else can pick it
 > up. In an ideal world, the current owner of a piece would yield the
 > effort based on their other workload, but sometimes it just doesn't
 > happen elsewhere).

and

 > the DEVeloper <==> DOCumenter relationshiop.

Ah, another a wiki head, I see! If BackTalk could recognize WikiNames 
and create pages in a zwiki backend to the book, people would be able 
sign and 'claim' pages with WikiBadges.

SectionEditor | ItemDOCumenter | ItemDEVeloper

For example, signing a page as the SectionEditor:ThisPerson, or as the 
ItemDOCumenter:ThatPerson or ItemDEVeloper:AnotherPerson for a given 
subsection.

That way, no ONE person has to project manage those aspects from the 
ground up. But there's a *clear and explicit convention* for tracking 
who's doing what.

Click on ThisPerson and you get a page with their contact info and a 
list of the sections and items they're working on....  Click on 
ItemDEVeloper and you would get a page with a list of all the developers 
who are contributing, linking to pages with their contact info and a 
list of the sections and items they're working on, and possibly a status 
report.

What else would we could get with CVS? It might be worth spelling that 
out so we can anticipate issues that are likely arise. But I like the 
idea of working with CMFBackTalk.

Andy McKay wrote:
 > I tried to sum this in appendix d:
 > http://plone.org/documentation/book/d but
 > if in anyone wants to start figuring out concrete rules, Im all ears ;)
 > Looking at that statement now I realise I need to relax it a bit.

You mean the section on Documentation Process? I think it's an excellent 
start, not sure what needs relaxing -- me, maybe? =}

But, it addresses "anon" contributors, while there are also these other 
roles, noted by Amr and above. What concerns me is managing the input 
and editing process.

MANAGING INPUT/EDITING ON SECTIONS IN TRANSITION

If WikiNames could create pages in a zwiki backend, that would provide a 
fluid space for drafting more complex sections -- getting them up to the 
point of being ready for commenting -- or the major revisions Mark 
mentioned:

Mark McEahern wrote:

 > I like to
 > fix broken windows right away (obvious typos, grammatical errors) and
 > leave more substantial changes in content or diction as a point of
 > discussion.

This makes sense to me. And suggests another WikiCategory: 
EditingConventions.

MANAGING MULTIPLE REFERENCES TO ZOPE BOOTSTRAPPING INFO

In addition to different types of contributors, there are also different 
types of users that the book needs to address, as noted:

Steve Rauch wrote:
 > but new users need to know what ZMI means, and need to know what "It's
 > in the properties tab" means. Perhaps some agreement on what
 > components of these other pieces does Plone need to address to make
 > sure the Plone user has a positive experience

Andy McKay wrote:
 > Yes my basic assumption is that Plone documentation should be stand
 > alone. Plone brings many new users into the Zope fold and I think we
 > need to make that assumption. Thats why on chapter 5
 > (http://plone.org/documentation/book/5) I suddenly realised, golly I
 > have to explain the ZMI
[snip]
 > We can give a bit of
 > an overview, enough to get some one working and then point them off in
 > the direction of the Zope Book for the rest.

It's difficult to know at the outset what the best way of organizing 
this will be. If we had a convention like, say, *ZopeBootStrap* or 
*PloneBootStrap* or whatever, it would allow us to tag pages with 
bootstrapping info on Zope and the CMF, and minimize replication.

Material could perhaps be sketched into pages in this mythical zwiki 
back end I've invented, so notes could be made about the precise angle 
on a ZopeBootStrap issue needed from a particular area. That is, "ZPT" 
needs to be explained one way in one place, and another in another. So, 
we could gather these notes while perhaps also sketching in up front 
intro material, then figure out later where it makes sense to hyperlink 
to the intro or appendix, where put it inline, and maybe where something 
needs a special sidebar.

I'm also wondering whether we need to distinquish more clearly in the 
book's organization between different types of users. Is chapter 3 for 
"front end" end users? And chapters 4-8 for ZMI users? If so, I think 
there's a gap: users like me! That is, ZMI users who don't come with 
programming expertise already, um, configured (PythonBootStrap).

A larger discussion, but we might want to look again at the chapter 
outlines and order, to work this in: SiteUsers, ZMIUsers, SiteAdmins

WHERE COMMENTS GO

Amr Malik wrote:
 > way to getting the book into a seamless printable format (with the
 > user comments moved to the end of each chapter, or to a place at the
 > end of the book, so that reader's train of thought is not disturbed
 > while using the book.

Andy McKay wrote:
 > I think the documentation can be gotten in PDF with no comments. My
 > goal is to distribute the documentation in many formats with comments
 > off, for example Windows Help or whatever the Mac equivalent is. If
 > its not an option in backtalk, it soon will be ;)

Well, speaking of complexity, I don't mean to overcomplicate this. And 
CMFBackTalk is already a HUGE improvement in legiblity over the version 
of BackTalk running over at zope.org. But I'm with Amr on this one and 
would even take it further -- I'm concerned about online legibility once 
the comments start coming in. My mind freezes, my eyes glaze over when 
confronted with those pages where teeny slivers of "book text" are 
overwhelmed by multiple comments in BackTalk.

At the same time, having the comments readily accessible is invaluable.

BUT SAY you had the option to show comments in a box to the left of 
paragraphs, instead of inline in the text! As a clickable threaded list 
by subject line, maybe? Wouldn't that be much more legible?

Maybe I'm missing something major in the idfference between CMFBackTalk 
commenting and Plone discussion_items. But I think we want to think 
about users here, don't we? =}

AND FINALLY: PloneStories

Steve Rauch wrote:
 > 3. Case-based documentation.

and Andy McKay wrote:

 > I was thinking of adding a Chapter
 > or Appendix (probably) called "Plone Stories" or something that is a
 > series of small articles that don't fit in anywhere else and may have

Yes! I like "Plone Stories" but acknowledge that case studies is perhaps 
more precise. It would be nice to have an easy way to capture *readers'* 
(users') PloneStories, big and small, as distinct from comments and 
other documentation.

OK, that's all. Kapil, you can open your eyes now. =}

best,



::laura
-- 
::
laura trippi
Faculty, Information Technologies & Interactive Arts
Simon Fraser University at Surrey
http://tonka.research.techbc.ca/laura/protoTools :: 604.586.6037 :: 
lat...@sf...

Re: [Plone-docs] Status

[alan r. <ru...@ru...>]

the WEBDAV source port is also open, port 8088.
http://plone.org:8088/plone.org/documentation/CMFTypesBook/Introduction
the plone CMF Site object is called "plone.org" just FYI.


----- Original Message ----- 
From: "Andy McKay" <an...@ag...>
To: "Mark McEahern" <mar...@mc...>; <plo...@li...>
Sent: Friday, October 18, 2002 5:32 PM
Subject: Re: [Plone-docs] Status


> Runyaga just made a great suggestion, if we use WebDAV as opposed to ftp we
> will be able to lock the documents... Unfortunately when you WebDAV out a
> CMFBackTalk document you get the pages HTML. Doh!
> --
>   Andy McKay
>   www.agmweb.ca
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> Access Your PC Securely with GoToMyPC. Try Free Now
> https://www.gotomypc.com/s/OSND/DD
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
> 

Re: [Plone-docs] Status

[Andy M. <an...@ag...>]

Runyaga just made a great suggestion, if we use WebDAV as opposed to ftp we
will be able to lock the documents... Unfortunately when you WebDAV out a
CMFBackTalk document you get the pages HTML. Doh!
--
  Andy McKay
  www.agmweb.ca

Re: [Plone-docs] Status

[Andy M. <an...@ag...>]

> Just to make sure I understand, you mean something like this:
>
>   1. initial version --> cvs
>   2. anon user's comments --> plone.org
>   3. editor's edits --> cvs
>   4. merge comments --> cvs
>   5. publish book from cvs --> plone.org
>
> Between 4 and 5, is it possible someone will make a comment--and it will
get
> obliterated by the publish?

Yeah exactly, a little painful. Plus you can check the output of things like
images and stx easily on line, although we could patch something together
there. I dont know if this is really a viable way of proceeding.
--
  Andy McKay
  www.agmweb.ca

RE: [Plone-docs] Status

[Mark M. <mar...@mc...>]

[Andy]
> Yeah but how would that deal with comments? The point of this is that
> everyone can comment on the book and the comments appear in line. Hmm.
> Thinking about it more it would remove the point of BackTalk.

Good point--comments would get clobbered if you just slurped the stuff from
CVS naively.  Ouch.

> Perhaps do an initial run using cvs, then put up... and repeat each time
> merging the comments back into the cvs tree every month or so.

Just to make sure I understand, you mean something like this:

  1. initial version --> cvs
  2. anon user's comments --> plone.org
  3. editor's edits --> cvs
  4. merge comments --> cvs
  5. publish book from cvs --> plone.org

Between 4 and 5, is it possible someone will make a comment--and it will get
obliterated by the publish?

> Thats in the plone stylesheet. We could do a local one... I prefer full Im
> more used to it.

Full it is.

Cheers,

// m

-

Re: [Plone-docs] Status

[Andy M. <an...@ag...>]

> Is it feasible to put the book in Plone's CVS?  I guess one obstacle there
> would be how do we go from CVS to plone.org?  Ideally, one of the editors
> could log into plone.org, click a button, and plone.org would suck the
> content from sf.net's CVS and update the documentation.  This may be too
> much hassle to setup right now, though.

Yeah but how would that deal with comments? The point of this is that
everyone can comment on the book and the comments appear in line. Hmm.
Thinking about it more it would remove the point of BackTalk.

Perhaps do an initial run using cvs, then put up... and repeat each time
merging the comments back into the cvs tree every month or so.

> p.s. Unless someone's really attached to the full-justification, can we
> switch that to left?

Thats in the plone stylesheet. We could do a local one... I prefer full Im
more used to it.
--
  Andy McKay
  www.agmweb.ca

----- Original Message -----
From: "Mark McEahern" <mar...@mc...>
To: <plo...@li...>
Sent: Friday, October 18, 2002 11:26 AM
Subject: RE: [Plone-docs] Status


> Andy, thanks for setting the book up.  It's the end of the week for me, so
> it's likely I won't take a big bite until next week.  In the meantime,
here
> are some initial meta-comments (some of these overlap comments made by
> others, so please consider the overlap a form of emphasis).
>
> Is it feasible to put the book in Plone's CVS?  I guess one obstacle there
> would be how do we go from CVS to plone.org?  Ideally, one of the editors
> could log into plone.org, click a button, and plone.org would suck the
> content from sf.net's CVS and update the documentation.  This may be too
> much hassle to setup right now, though.
>
> I'm sure as we work together, a style and process will emerge.  I like to
> fix broken windows right away (obvious typos, grammatical errors) and
leave
> more substantial changes in content or diction as a point of discussion.
> I'd be happy to do the Red Hat installation section.  I have RH 7.3, for
> what it's worth.
>
> The content I've seen so far (browsed most of it) looks good.  I like the
> outline you provided, Andy!
>
> Thanks!
>
> // mark
>
> p.s. Unless someone's really attached to the full-justification, can we
> switch that to left?
>
>
> -
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>

RE: [Plone-docs] Status

[Mark M. <mar...@mc...>]

Andy, thanks for setting the book up.  It's the end of the week for me, so
it's likely I won't take a big bite until next week.  In the meantime, here
are some initial meta-comments (some of these overlap comments made by
others, so please consider the overlap a form of emphasis).

Is it feasible to put the book in Plone's CVS?  I guess one obstacle there
would be how do we go from CVS to plone.org?  Ideally, one of the editors
could log into plone.org, click a button, and plone.org would suck the
content from sf.net's CVS and update the documentation.  This may be too
much hassle to setup right now, though.

I'm sure as we work together, a style and process will emerge.  I like to
fix broken windows right away (obvious typos, grammatical errors) and leave
more substantial changes in content or diction as a point of discussion.
I'd be happy to do the Red Hat installation section.  I have RH 7.3, for
what it's worth.

The content I've seen so far (browsed most of it) looks good.  I like the
outline you provided, Andy!

Thanks!

// mark

p.s. Unless someone's really attached to the full-justification, can we
switch that to left?


-

Re: [Plone-docs] Status [PloneZopeZenSkinDoc Attached]

[Amr M. <aea...@ya...>]

Hi,

> Wow, thank you. Since the Plone book is structured text, I'd rather pull the
> source out of ZopeZen (stx) and run a spell check over that. Unless you can
> give me back that corrected article in stx from the PDF.

   I have it in word format, I can forward you that if you like. I spell
checked it there and printed to pdf995 (pretty lowtech eh?) but it works.

...
> or Appendix (probably) called "Plone Stories" or something that is a series
> of small articles that don't fit in anywhere else and may have relevance.
> Making an XYZ skin, or getting Plone to do some particular task ....
...

I like Steve's "Case Studies" idea as well, This document could probably go
into that type of a section. Nomenclature is secondary for me, though its
important. Main thing for me is to get as much doc's out into newcomer's hands
as possible.

thanks,

Amr
 


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com

Re: [Plone-docs] Documentation Thoughts

[Andy M. <an...@ag...>]

> 1. I did not use CMF before using plone, but I had used Zope. So it was
> not apparent to me that content as added from within Plone as opposed to
> from the ZMI. Much of the current documentation on CMF (basicly the CMF
> list) is developer oriented. Answers that assume years of experience with
> CMF don't work for newcomers. Saying "Google this" or "subclass that"
> might be sufficient for developers, but is pretty dense otherwise.

Yes my basic assumption is that Plone documentation should be stand alone.
Plone brings many new users into the Zope fold and I think we need to make
that assumption. Thats why on chapter 5
(http://plone.org/documentation/book/5) I suddenly realised, golly I have to
explain the ZMI, because chances are a user wont know what it is.

> 2. Do we need to separate Zope | CMF | Plone functionality and
> documentation? I know we don't want to doc all 3 things (a life's work!)
> but new users need to know what ZMI means, and need to know what "It's in
> the properties tab" means. Perhaps some agreement on what components of
> these other pieces does Plone need to address to make sure the Plone user
> has a positive experience, or does not spend too long floundering around
> trying to figure out something that resides outside of Plone.

You're right we cant document all 3 things, but there are areas where we
will have to. We can't just say go read the Zope Book. We can give a bit of
an overview, enough to get some one working and then point them off in the
direction of the Zope Book for the rest.

I tried to sum this in appendix d: http://plone.org/documentation/book/d but
if in anyone wants to start figuring out concrete rules, Im all ears ;)
Looking at that statement now I realise I need to relax it a bit.

> 3. Case-based documentation. There have been some discussions lately on
> Plone-users(?) about customizing news items so that content is added,
> published to a news folder, etc. It would be great to document a real-life
> case like one of these. It gets into permissions, workflows, content
> management -- the real meat of taking Plone and making it work for you.
> Or is this a Tutorials Appendix or something like that?

Yep I think you are right, see earlier email with Amr about the ZopeZen skin
docs, I think this is the way to go. The Plone book works you through all
the key points examples, and then we build up some tutorials / how tos in an
appendix dealing with a special use case.
--
  Andy McKay
  www.agmweb.ca


----- Original Message -----
From: "Steve Rauch" <srauch@u.washington.edu>
To: <plo...@li...>
Sent: Friday, October 18, 2002 9:57 AM
Subject: [Plone-docs] Documentation Thoughts


> I am really pleased to see this effort taking wing! I will try to add what
> I can to assist the effort.
>
> These are just a couple thoughts I had that I wanted to share -- mostly to
> help me get a grip on my own need for Plone documentation.
>
> 1. I did not use CMF before using plone, but I had used Zope. So it was
> not apparent to me that content as added from within Plone as opposed to
> from the ZMI. Much of the current documentation on CMF (basicly the CMF
> list) is developer oriented. Answers that assume years of experience with
> CMF don't work for newcomers. Saying "Google this" or "subclass that"
> might be sufficient for developers, but is pretty dense otherwise.
>
> 2. Do we need to separate Zope | CMF | Plone functionality and
> documentation? I know we don't want to doc all 3 things (a life's work!)
> but new users need to know what ZMI means, and need to know what "It's in
> the properties tab" means. Perhaps some agreement on what components of
> these other pieces does Plone need to address to make sure the Plone user
> has a positive experience, or does not spend too long floundering around
> trying to figure out something that resides outside of Plone.
>
> 3. Case-based documentation. There have been some discussions lately on
> Plone-users(?) about customizing news items so that content is added,
> published to a news folder, etc. It would be great to document a real-life
> case like one of these. It gets into permissions, workflows, content
> management -- the real meat of taking Plone and making it work for you.
> Or is this a Tutorials Appendix or something like that?
>
>
> Thx --
>
> Steve Rauch
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>

[Plone-docs] Documentation Thoughts

[Steve R. <srauch@u.washington.edu>]

I am really pleased to see this effort taking wing! I will try to add what
I can to assist the effort.

These are just a couple thoughts I had that I wanted to share -- mostly to
help me get a grip on my own need for Plone documentation.

1. I did not use CMF before using plone, but I had used Zope. So it was
not apparent to me that content as added from within Plone as opposed to
from the ZMI. Much of the current documentation on CMF (basicly the CMF
list) is developer oriented. Answers that assume years of experience with
CMF don't work for newcomers. Saying "Google this" or "subclass that"
might be sufficient for developers, but is pretty dense otherwise.

2. Do we need to separate Zope | CMF | Plone functionality and
documentation? I know we don't want to doc all 3 things (a life's work!)
but new users need to know what ZMI means, and need to know what "It's in
the properties tab" means. Perhaps some agreement on what components of
these other pieces does Plone need to address to make sure the Plone user
has a positive experience, or does not spend too long floundering around
trying to figure out something that resides outside of Plone.

3. Case-based documentation. There have been some discussions lately on
Plone-users(?) about customizing news items so that content is added,
published to a news folder, etc. It would be great to document a real-life
case like one of these. It gets into permissions, workflows, content
management -- the real meat of taking Plone and making it work for you.
Or is this a Tutorials Appendix or something like that?


Thx --

Steve Rauch

Re: [Plone-docs] Status [PloneZopeZenSkinDoc Attached]

[Andy M. <an...@ag...>]

> BTW, I went ahead and integrated your excellent articles on the ZopeZen
skin
> into one document, did a wee bit of reformatting and ran the spell check
and
> converted it to PDF. Not sure where this should go. As a first step I'm
posting
> it here to solicit comments and then I can submit it to the holding pen
for the
> documentation in waiting.

Wow, thank you. Since the Plone book is structured text, I'd rather pull the
source out of ZopeZen (stx) and run a spell check over that. Unless you can
give me back that corrected article in stx from the PDF.

Anyway yes I was thinking about this too and it doesn't really make sense to
put this anywhere in the book, since its one small self contained tutorial.
BUT I believe there is value in including it, I really dont want a section
of links that points to a bunch of tutorials, which then become broken and
lost over time, so we lose information. I was thinking of adding a Chapter
or Appendix (probably) called "Plone Stories" or something that is a series
of small articles that don't fit in anywhere else and may have relevance.
Making an XYZ skin, or getting Plone to do some particular task or "How I
won over a bunch of knuckle heads and persuaded them Plone is the best thing
since the digital watch" stories. Mostly I want to preserve this data so its
not lost.

> - CVS sounds intriguing, I haven't used it, but I think it would be good
and
> instructive (at least for me) to learn, especially since I'm trying to get
in
> touch with OSX's inner child :)

Unfortunately CVS doesnt really fit in with the Zope model.

> the maintainer (I think its dreamcatcher) but not sure

Thats him.

> the apple "help engine" type thingy for an equivalent bundle in Apple Help
> format.

That would be great.
--
  Andy McKay
  www.agmweb.ca

Re: [Plone-docs] Status

[Andy M. <an...@ag...>]

> This is great news! Andy, as we have discussed earlier, I believe I can
> contribute to the Mac OSX installer doc part. And other portions, whic I
can
> submit for review.

Great.

I started putting your Word FAQ document into the Appendix B,
http://www.plone.org/documentation/book/b and trimming it quite a bit, since
some questions dont apply to 1.0 etc. Thanks a lot for that!

> 1. We need to have people commit for certain sections of the book, and
make
> this commitment transparent ("DocBowl" if you will). Somehow if we can
record
> activity against an general area that would be good. So if someone doesn't
have
> the time any more, someone else can pick it up. In an ideal world, the
current
> owner of a piece would yield the effort based on their other workload, but
> sometimes it just doesn't happen (not necessarily in Zope++ but I've seen
it
> elsewhere).

Yeah actually looking at this more I really want cvs for this ;) I can't
think of an easy way of doing this except one or two people keeping on top
of this as much we can.

> 2. We need to have relatively open lines of communications between the
> Developer of a certain module/pkg/produc/customization etc., and the
person
> responsible for its documentation. What may be the best way of doing this?
I'm
> not sure. Maybe #plone, maybe the list. Two things IMO in this regard
would be
> the DEVeloper <==> DOCumenter relationshiop. #plone has seemed more than a
tad
> quiet, for the very few times that I've had the chance to login to that
> channel.

Plone, list, emails, if they live nearby coffee/beer? I would just send an
email to the developer (and cc plone-docs) telling him you are working on
his bit, what can he give you etc. Where are you located, could be time
zones or that everyone is busy working.

> 3. This is just a wish at this point, but it might be worthwhile looking
into a
> way to getting the book into a seamless printable format (with the user
> comments moved to the end of each chapter, or to a place at the end of the
> book, so that reader's train of thought is not disturbed while using the
book.
> Personally, I would benefit quite a bit from this (or its just that I need
to
> get my Attention Deficit problem under control :) heheh )

I think the documentation can be gotten in PDF with no comments. My goal is
to distribute the documentation in many formats with comments off, for
example Windows Help or whatever the Mac equivalent is. If its not an option
in backtalk, it soon will be ;)

Thanks for FAQ Amr, and looking forward to more.
--
  Andy McKay
  www.agmweb.ca

----- Original Message -----
From: "Amr Malik" <aea...@ya...>
To: "Andy McKay" <an...@ag...>; <plo...@li...>
Cc: "laura trippi" <lat...@te...>
Sent: Friday, October 18, 2002 7:06 AM
Subject: Re: [Plone-docs] Status


> This is great news! Andy, as we have discussed earlier, I believe I can
> contribute to the Mac OSX installer doc part. And other portions, whic I
can
> submit for review.
>
> Just a few suggestions:
>
> 1. We need to have people commit for certain sections of the book, and
make
> this commitment transparent ("DocBowl" if you will). Somehow if we can
record
> activity against an general area that would be good. So if someone doesn't
have
> the time any more, someone else can pick it up. In an ideal world, the
current
> owner of a piece would yield the effort based on their other workload, but
> sometimes it just doesn't happen (not necessarily in Zope++ but I've seen
it
> elsewhere).
>
> 2. We need to have relatively open lines of communications between the
> Developer of a certain module/pkg/produc/customization etc., and the
person
> responsible for its documentation. What may be the best way of doing this?
I'm
> not sure. Maybe #plone, maybe the list. Two things IMO in this regard
would be
> the DEVeloper <==> DOCumenter relationshiop. #plone has seemed more than a
tad
> quiet, for the very few times that I've had the chance to login to that
> channel.
>
> 3. This is just a wish at this point, but it might be worthwhile looking
into a
> way to getting the book into a seamless printable format (with the user
> comments moved to the end of each chapter, or to a place at the end of the
> book, so that reader's train of thought is not disturbed while using the
book.
> Personally, I would benefit quite a bit from this (or its just that I need
to
> get my Attention Deficit problem under control :) heheh )
>
> Once again, thanks for investing the time in setting this up, i think this
is
> awesome!
>
> -Amr (LninYo@[plone,zopezen].org)
>
> P.S. I'm not sure what is meant by "serious commitment", you might want to
> elaborate on that. We might be talking a certain level of productivity
here and
> IMO that's not such a bad thing even in OpenSource world.
>
> --- Andy McKay <an...@ag...> wrote:
> > So CMFBackTalk is up and sort of running. Please send Kapil some good
vibes
> > for working on it and continuing to do so, there are some bugs to do.
Thanks
> > Kapil!
> >
> > I'm pleased to announce Mark McEahern and Laura Trippi (along with
myself)
> > have agreed to be editors for the book process. This stills means anyone
can
> > write docs, do it anywhere in any format, just send an email here and we
> > will get around to putting it in the book.
> >
> > This process I laid out here: http://plone.org/documentation/book/d
> >
> > Once we have a few bugs fixed and some more actual documentation we will
> > publish this, at the moment the docs are just in visible status.
> >
> > If you want to be an editor and are willing to devote some serious time
to
> > sitting down and writing docs, then please let me know.
> >
> > Some of the areas needing documentation now:
> > - MacOSX Installation (Chapter 2)
> > - Linux Installation (debian, redhat) (Chapter 2)
> > - Using Plone (yes a very big topic, not sure even the headings)
> > - or any bit you want...
> >
> > Cheers.
> > --
> >   Andy McKay
> >   www.agmweb.ca
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: viaVerio will pay you up to
> > $1,000 for every account that you consolidate with us.
> > http://ad.doubleclick.net/clk;4749864;7604308;v?
> > http://www.viaverio.com/consolidator/osdn.cfm
> > _______________________________________________
> > Plone-docs mailing list
> > Plo...@li...
> > https://lists.sourceforge.net/lists/listinfo/plone-docs
>
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
>

Re: [Plone-docs] Status

[Amr M. <aea...@ya...>]

This is great news! Andy, as we have discussed earlier, I believe I can
contribute to the Mac OSX installer doc part. And other portions, whic I can
submit for review.

Just a few suggestions:

1. We need to have people commit for certain sections of the book, and make
this commitment transparent ("DocBowl" if you will). Somehow if we can record
activity against an general area that would be good. So if someone doesn't have
the time any more, someone else can pick it up. In an ideal world, the current
owner of a piece would yield the effort based on their other workload, but
sometimes it just doesn't happen (not necessarily in Zope++ but I've seen it
elsewhere). 

2. We need to have relatively open lines of communications between the
Developer of a certain module/pkg/produc/customization etc., and the person
responsible for its documentation. What may be the best way of doing this? I'm
not sure. Maybe #plone, maybe the list. Two things IMO in this regard would be
the DEVeloper <==> DOCumenter relationshiop. #plone has seemed more than a tad
quiet, for the very few times that I've had the chance to login to that
channel. 

3. This is just a wish at this point, but it might be worthwhile looking into a
way to getting the book into a seamless printable format (with the user
comments moved to the end of each chapter, or to a place at the end of the
book, so that reader's train of thought is not disturbed while using the book.
Personally, I would benefit quite a bit from this (or its just that I need to
get my Attention Deficit problem under control :) heheh )

Once again, thanks for investing the time in setting this up, i think this is
awesome!

-Amr (LninYo@[plone,zopezen].org)

P.S. I'm not sure what is meant by "serious commitment", you might want to
elaborate on that. We might be talking a certain level of productivity here and
IMO that's not such a bad thing even in OpenSource world. 

--- Andy McKay <an...@ag...> wrote:
> So CMFBackTalk is up and sort of running. Please send Kapil some good vibes
> for working on it and continuing to do so, there are some bugs to do. Thanks
> Kapil!
> 
> I'm pleased to announce Mark McEahern and Laura Trippi (along with myself)
> have agreed to be editors for the book process. This stills means anyone can
> write docs, do it anywhere in any format, just send an email here and we
> will get around to putting it in the book.
> 
> This process I laid out here: http://plone.org/documentation/book/d
> 
> Once we have a few bugs fixed and some more actual documentation we will
> publish this, at the moment the docs are just in visible status.
> 
> If you want to be an editor and are willing to devote some serious time to
> sitting down and writing docs, then please let me know.
> 
> Some of the areas needing documentation now:
> - MacOSX Installation (Chapter 2)
> - Linux Installation (debian, redhat) (Chapter 2)
> - Using Plone (yes a very big topic, not sure even the headings)
> - or any bit you want...
> 
> Cheers.
> --
>   Andy McKay
>   www.agmweb.ca
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: viaVerio will pay you up to
> $1,000 for every account that you consolidate with us.
> http://ad.doubleclick.net/clk;4749864;7604308;v?
> http://www.viaverio.com/consolidator/osdn.cfm
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com

Re: [Plone-docs] Status: PageEditors & page menus?

[Andy M. <an...@ag...>]

> (Well, mostly. I guess you know the bug with the leading space at the
> start of the line. Also, I inadvertently inserted a comment button and
> can't seem to delete it. Oops.)

How did you do that? A comment button appears at the end of a paragraph.
Although it seems to be a little haphazard. I hate the image though. Limi
will fix this before we publish.

> Maybe a convention for people to 'claim' pages, like putting
> "PageEditor: name" at the bottom of a page you're working on?

Sure or just say im going to work on this for a while go away. The problem
is if we both work on the same page, we can happily each others changes
away, especially since Im doing it by ftp. I'd love it if you started
Chapter 3. Its the toughie ;)

But I thought you could make a start by putting some of the prototools user
guides in.

> Also, it might be useful to have a page-based ToC or menu (i.e. for the
> page's main headings) in, say, a box on the upper right, opposite the
> navigation box. Or would that be too difficult?

Good idea! Navigation is broken until we can refactor Backtalk, so just dont
forget about this one and remind me again.

> Thanks, Andy, this is exciting.

Me too, thank you for helping out. Its great to have an accomplished writer
on board.
--
  Andy McKay
  www.agmweb.ca

Re: [Plone-docs] Status: PageEditors & page menus?

[laura t. <lat...@sf...>]

It's beautiful! Nice work, Andy, organizing it all and on the outline.

And, Kapil, kudos!!! I was almost afraid to look! =}

I like the pencil! It also works!

(Well, mostly. I guess you know the bug with the leading space at the 
start of the line. Also, I inadvertently inserted a comment button and 
can't seem to delete it. Oops.)

Andy, I reorganized the content on the "about" page and did a bit of 
editing.

I'm wondering whether it would be helpful to have main editors for 
specific sectons so we don't step on each other's toes?

Maybe a convention for people to 'claim' pages, like putting 
"PageEditor: name" at the bottom of a page you're working on?

Also, it might be useful to have a page-based ToC or menu (i.e. for the 
page's main headings) in, say, a box on the upper right, opposite the 
navigation box. Or would that be too difficult?

Thanks, Andy, this is exciting. It's nice to think my mania for 
documentation will be contributing to something useful! =}


::laura

Andy McKay wrote:
> So CMFBackTalk is up and sort of running. Please send Kapil some good vibes
> for working on it and continuing to do so, there are some bugs to do. Thanks
> Kapil!
> 
> I'm pleased to announce Mark McEahern and Laura Trippi (along with myself)
> have agreed to be editors for the book process. This stills means anyone can
> write docs, do it anywhere in any format, just send an email here and we
> will get around to putting it in the book.
> 
> This process I laid out here: http://plone.org/documentation/book/d
> 
> Once we have a few bugs fixed and some more actual documentation we will
> publish this, at the moment the docs are just in visible status.
> 
> If you want to be an editor and are willing to devote some serious time to
> sitting down and writing docs, then please let me know.
> 
> Some of the areas needing documentation now:
> - MacOSX Installation (Chapter 2)
> - Linux Installation (debian, redhat) (Chapter 2)
> - Using Plone (yes a very big topic, not sure even the headings)
> - or any bit you want...
> 
> Cheers.
> --
>   Andy McKay
>   www.agmweb.ca
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: viaVerio will pay you up to
> $1,000 for every account that you consolidate with us.
> http://ad.doubleclick.net/clk;4749864;7604308;v?
> http://www.viaverio.com/consolidator/osdn.cfm
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
> 
> 


-- 
::
laura trippi
Faculty, Information Technologies & Interactive Arts
Simon Fraser University at Surrey
http://tonka.research.techbc.ca/laura/protoTools :: 604.586.6037 :: 
lat...@sf...

[Plone-docs] Status

[Andy M. <an...@ag...>]

So CMFBackTalk is up and sort of running. Please send Kapil some good vibes
for working on it and continuing to do so, there are some bugs to do. Thanks
Kapil!

I'm pleased to announce Mark McEahern and Laura Trippi (along with myself)
have agreed to be editors for the book process. This stills means anyone can
write docs, do it anywhere in any format, just send an email here and we
will get around to putting it in the book.

This process I laid out here: http://plone.org/documentation/book/d

Once we have a few bugs fixed and some more actual documentation we will
publish this, at the moment the docs are just in visible status.

If you want to be an editor and are willing to devote some serious time to
sitting down and writing docs, then please let me know.

Some of the areas needing documentation now:
- MacOSX Installation (Chapter 2)
- Linux Installation (debian, redhat) (Chapter 2)
- Using Plone (yes a very big topic, not sure even the headings)
- or any bit you want...

Cheers.
--
  Andy McKay
  www.agmweb.ca

Fw: [Plone-docs] understanding workflow and folders

[Alexander L. <li...@pl...>]

Hi Mark, found an old mail that had been flagged, which usually means that
it's relevant for the docs-list. I will give short hints below, if you need
more detail, tell me. But you probably have most of these figured out.

> I'm using Plone 1.0 beta 1.  I'm trying to understand workflow and
folders.
> Here are the questions I have:
>
> Q:  If I want to organize my content in folders and have a portal tab for
> each top-level folder, do I have an option besides going into
portal_actions
> and adding a portal_action for each folder?  I see that not all
portal_tabs
> are folders, some are scripts (e.g., search, news).  So maybe this is
> inherently complicated and seemingly redundant because of the desired
> flexibility.  I say redundant because if all I want for portal tabs is
> content folders, to me, merely creating those top-level folders and maybe
> clicking a property on for each one ought to be sufficient for creating my
> top-level menu.

A: This is for added flexibility, yes. Once you learn how they work, you
will appreciate their strengths. That being said, in 1.1 I am working
towards exposing more of this kind of functionality through the Plone UI
itself.

> Q:  For content folders, there seems to be a difference between folders I
> add in the ZMI and folders I add through the portal (login as admin,
> navigate up one level until I'm at the portal root, then add a folder).
The
> icon for the later type of folders is blue, the icon for the former
(normal)
> folders is yellow.  Also, the blue folders show up in the navigationBox,
the
> yellow ones don't.  Why can't I add a blue folder from the ZMI?

You can (add Plone Content -> Plone Folder), but in general it is
recommended to stay on the Plone side of things, as you can easily disrupt
things via the ZMI.

> Q:  Suppose I settle on using blue content folders for my portal tabs.
> Within the organization, there are people who will, for example, add a
News
> Item.  But it seems odd that, at the end of the day, when someone reviews
> this News Item and publishes it, the external URL points to the original
> author's Member folder.  An additional unexpected consequence is that the
> person who added the News Item can subsequently delete it.  Yikes!

This is a workflow thing, you can decide that once a News item has been
published, only you can revoke it. For example. But most of the time you
trust your users, right? ;)

It's the same with editing a document after it is published. The Plone
default workflow is not very strict, as that would hamper productivity. But
you can set up any rules you want.

> I would
> think when it's published, it should get moved/copied somewhere (e.g., a
> NewsItem content folder).  Am I thinking of things backwards?  If not, I'm
> guessing I need to mess with the workflow.  Yikes.  Any pointers?

Workflow is the way to go here, yes. In addtion, we will have the concept of
workspaces, see my post to plone-users.

-- Alexander Limi

[Plone-docs] Fw: [Plone-users] Some simple Plone questions

[Alexander L. <li...@pl...>]

----- Original Message -----
From: "Luca Manini" <ma...@fl...>
To: <plo...@li...>
Sent: Thursday, October 17, 2002 4:54 PM
Subject: [Plone-users] Some simple Plone questions


> Hi,
>
> here go some considerations on "understanding Plone (and/or CMF)",
> whit some call for help...
>
> Plone Interface
>
>   or: where do those pieces come from? A newbie try to understand
>   Plone " default" interface structure. With questions for gurus.
>
>   The "paths" in portal_skins->properties.
>
>     Plone add another objects' search mechanism "on top" of those
>     provided by Zope (inheritance, acquisition). For each skin, there
>     is a list of folders where objects are looked for.
>
>     This is very nice for configuration but makes "discovery" a little
>     more complex. It would be nice to have a skin with a very short
>     "path": may be one can delete some plone_xxx folders when there is
>     an "equivalent" zpt_xxx one (guru-question).
>
>     In the meantime beware of skins' path when using Zope's find
>     utility.
>
>     Note: if you "empty" the path for the current skin, Plone still
>     works! Why?  Usual Zope magic?
>
>   The index_html
>
>     When visiting a Plone site (say
>     http://localhost:9673/MyPloneSite), I expect Zope to render
>     http://localhost:9673/MyPloneSite/index_html. So have a look at
>     it! It is really a Document (not a DTML one) with very little
>     content (if you chance or rename it you will see your changes, so
>     it plays some role) and **no** reference to standard footers or
>     headers, so where does all the rest of the page come from? May be
>     actions (guru-question).
>
>     OK, so try to find another index_html. One is in plone_templates,
>     it uses main_template/macros/master filling the macro "main" with
>     the site title and description (you can change them from the
>     "plone setup" link).
>
>   main_template
>
>     One main_template is "available" in portal_skins/plone_templates,
>     and contains some revealling lines like:
>
>     <head metal:use-macro="here/header/macros/html_header">
>     <div metal:use-macro="here/header/macros/portal_header">
>     <div class="footer"
metal:use-macro="here/footer/macros/portal_footer">
>
>     From here on, things seems simpler (or at least clearer).
>
>   So my questions are:
>
>   - is this analysis right?
>
>   - is this (I mean: a first exploration journey into Plone interface)
>     explained somewhere?
>
>   - is there a way to strip the base plone site (for simplifying this
>     kind of research) may be deleting some skinks and reducing the
>     "length" of the search paths?
>
>   - is there a tool for browsing macros and slots (I'm thinking about
>     something that reads ZPT -- may be from the file system -- and
>     produces Emacs' etags or browsable html)?
>
>
>      TIA for any help,
>      bye Luca
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: viaVerio will pay you up to
> $1,000 for every account that you consolidate with us.
> http://ad.doubleclick.net/clk;4749864;7604308;v?
> http://www.viaverio.com/consolidator/osdn.cfm
> _______________________________________________
> Plone-users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

[Plone-docs] Fw: [Plone-users] Plone Navigation summary (was: second level nav)

[Alexander L. <ale...@zo...>]

This will be useful for the documentation.


----- Original Message -----
From: "Philipp Auersperg" <ph...@bl...>
To: <ma...@mc...>; <plo...@li...>;
<ale...@zo...>
Sent: Friday, October 11, 2002 2:30 AM
Subject: Re: [Plone-users] Plone Navigation summary (was: second level nav)


> answer is late, but:
>
> I've put up a new version of  the tree navigation to Plone_beta1:
>
> when creating a new Plone instance, navtree_properties is created in
> portal_properties
> with all possible navigation options as follows:
>
>
> topLevel(int):                                     from which level to
> start the tree (Portal ==0)
> includeTop(bool):                                 should the Portal
> itself be displayed as root
> showMyUserFolderOnly(bool):          if set I see below Members only my
> own Folder and that one I am currently browsing
> showFolderishSiblingsOnly(bool):     in the hierarchy above the current
> object just Folders are listed
> showFolderishChildrenOnly(bool):    show only folderish objects below
> the current object
> showNonFolderishObject(bool):         if the previous option is set and
> I am browsing a non-folderish object, it is displayed anyhow
> batchSize(int):                                   how many rows at once
> in the tree?
> showTopicResults(bool):                      show results of topics in
> the navigation
>
> it does NOT break existing plone sites, but you can optionally create
> portal_properties.navtree_properties for getting
> the flexibility.
>
> this should cover some of the points below, but not all (reflecting
> publishing state should be next on my list).
>
> phil
>
> >- Section (first-level) navigation is performed using the top tabs, like
> >your Corporate first-level navigation. This should normally point to a
> >folder in the root, like /corporate. (This is not absolutely necessary,
> >but I usually recommend keeping the URL scheme and the logical
> >organization of the site in sync.)
> >
> >- Subsection (second-level) navigation is performed with the navigation
> >box on the left hand side. The main idea is to show Folders that have the
> >state Published, and to hide the other folders. Manager users can of
> >course see all folders, and I'm working on a mechanism / color scheme so
> >it will be easy to see which folders are public, and which are not.
> >
> >Please note that you don't have to use the left navigation box metaphor,
> >with little customization this could easily be moved to the top area like
> >you initially suggested. However, keeping the second-level navigation as
a
> >tree on the left solves another problem: third-to-n level navigation.
> >
> >
>
> >The Navigation tree will, when properly done, behave as follows:
> >
> >- Will be visible to anonymous users if there are published folders
> >(hidden if not)
> >
> >- Will always show a link to the root folder.
> >
> >- Will always show a certain pre-defined amount of folders (2 or 3
> >probably) leading up to the current folder you are located in.
> >
> >- Will always show the sieblings of the current folder. If there are too
> >many sieblings (more than 20, for example), there will be batching.
> >
> >So, in summary, you get:
> >
> >- Easy expansion from two-level navigation to n-level navigation
> >
> >- An easy way of creating navigation (make folders, publish them)
> >
> >- A powerful navigation mechanism that is a more visual representation
> >than the breadcrumbs alone.
> >
> >This is the theory. At the moment, it doesn't work like that. That's why
i
> >CC'ed the developer list, plus Phil who is responsible for the current
> >navigation tree.
> >
> >I would like to hear comments and ideas on this, as it is crucial to have
> >this navigational mechanism in place before we ship 1.0. Currently
> >navigation is one of Plone's biggest weaknesses, and we should really get
> >on with implementing the last missing bits into it.
> >
> >We are almost there, just the last bit about the publishing status
> >controlling how the tree will look for anonymous/manager users plus some
> >visual tweaks are missing. If I remember correctly, that is. :)
> >
> >Thanks for inspiring me to do this little write-up, Mark - it was really
> >needed, as most of this has just been inside my head until now, and I
> >always assume that people can read my mind. (Alan nearly does by now, but
> >that's another story ;)
> >
> >Any questions, suggestions or comments? Developers?
> >
> >
> >
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Plone-users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

[Plone-docs] understanding workflow and folders

[Mark M. <ma...@mc...>]

I'm using Plone 1.0 beta 1.  I'm trying to understand workflow and folders.
Here are the questions I have:

Q:  If I want to organize my content in folders and have a portal tab for
each top-level folder, do I have an option besides going into portal_actions
and adding a portal_action for each folder?  I see that not all portal_tabs
are folders, some are scripts (e.g., search, news).  So maybe this is
inherently complicated and seemingly redundant because of the desired
flexibility.  I say redundant because if all I want for portal tabs is
content folders, to me, merely creating those top-level folders and maybe
clicking a property on for each one ought to be sufficient for creating my
top-level menu.

Q:  For content folders, there seems to be a difference between folders I
add in the ZMI and folders I add through the portal (login as admin,
navigate up one level until I'm at the portal root, then add a folder).  The
icon for the later type of folders is blue, the icon for the former (normal)
folders is yellow.  Also, the blue folders show up in the navigationBox, the
yellow ones don't.  Why can't I add a blue folder from the ZMI?

Q:  Suppose I settle on using blue content folders for my portal tabs.
Within the organization, there are people who will, for example, add a News
Item.  But it seems odd that, at the end of the day, when someone reviews
this News Item and publishes it, the external URL points to the original
author's Member folder.  An additional unexpected consequence is that the
person who added the News Item can subsequently delete it.  Yikes!  I would
think when it's published, it should get moved/copied somewhere (e.g., a
NewsItem content folder).  Am I thinking of things backwards?  If not, I'm
guessing I need to mess with the workflow.  Yikes.  Any pointers?

Thanks,

// mark

-

[Plone-docs] diff between Plone folder and CMF folder

[alan r. <ru...@ru...>]

documentors. L-arry just asked this but left

nothing.  in fact we could probably get rid of this difference 
if we made CMF folders smarter.  basically a CMF Folder
is not skinned (it will acquire a default view, index_html).
Also you can not publish a CMF Folder (I believe).  another
huge reason is that we want to show folder_listing.pt when
there is no default view.  this is similiar to apache's Directory
listing -- but only if the user has 'List folder contents' permission.

~runyaga

[Plone-docs] (no subject)

[m. <ca...@ma...>]

[Plone-docs] httpd.conf for plone.org

[alan r. <ru...@ru...>]

<VirtualHost *>
ServerName plone.org
ServerAlias www.plone.org
ServerAdmin web...@pl...
ProxyPass /
http://localhost:8080/VirtualHostBase/http/plone.org:80/plone.org/
ProxyPassReverse /
http://localhost:8080/VirtualHostBase/http/plone.org:80/plone.org/

#
# gzip handler
#
mod_gzip_item_include handler proxy-server
mod_gzip_on Yes

CacheRoot "/tmp/proxy/plone.org"
CacheSize 500
CacheGcInterval 2
CacheMaxExpire 24
CacheLastModifiedFactor 0.1
CacheDefaultExpire 1
CacheDirLength 2
#
# Expire - by request
#
 ExpiresActive On
 ExpiresByType image/gif A86400
 ExpiresByType image/png A86400
 ExpiresByType image/jpeg A86400
 ExpiresByType text/css A86400
 ExpiresByType text/javascript A86400
 ExpiresByType application/x-javascript A86400


CustomLog /usr/local/apache/logs/plone-access_log combined
CustomLog /usr/local/apache/logs/plone-access-gzip_log
common_with_mod_gzip_info2
ErrorLog /usr/local/apache/logs/plone-error_log
</VirtualHost>