<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
"One last thing, if we ever get a more robust folder contents or
"structure" menu where we can globally manage content for plone in a
better way, this might be less of a problem"<br>
<br>
I'd love to see an additional or improved folder contents view - a
tree, where you can see all the site's content, edit, delete, move
items around.. Other option would be something like
<a class="moz-txt-link-freetext" href="https://pypi.python.org/pypi/bda.plone.finder">https://pypi.python.org/pypi/bda.plone.finder</a> or github-like browser
(ajax loading + you have a clear overview of the current path, which
is something you might not have in your Plone theme, if there is no
path bar).<br>
<br>
But that's a topic for another discussion.<br>
<br>
On placeless adding I have nothing really helpful to say, except
that I'm +1 on this. I'm not sure how to realize this. Maybe if
users (or admin) had the option to bookmark certain sections of the
site (e.g. 'Banners', 'Events', 'Media releases', ...), which would
be easy accessible from the menu ('Go to -> ...' ), it might be
somewhat helpful.<br>
<br>
cheers,<br>
ibi<br>
<br>
<br>
<div class="moz-cite-prefix">On 02/21/2013 02:56 AM, Nathan Van
Gheem wrote:<br>
</div>
<blockquote
cite="mid:CAL8hw9GA0DW0g=qyCPsXozJsLjLKSN6DS2H+ocTTq2S_uCnXAg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">First off, let me just say, I feel your pain.
We've had users have a difficult time knowing where to add.
Those same users will most likely have a difficult time
managing content with large sites on any system though.
Plone's folder structure is a pretty nature way to organize
content; however, we do need to think of ways to make it
better.</div>
<div><br>
</div>
With that, I'll say a few thoughts here as I'm on both the UI
and Framework team:
<div><br>
</div>
<div style="">- The implementation described makes the UI more
complicated and actually requires the user to think more.</div>
<div style="">- There are already other ways to solve this
problem. One being what Jon just described, another by
creation your own custom factory urls</div>
<div style="">- The global add concept still seems awkward. How
do you set which types have that ability and are there default
locations they add to? Can there be multiple add locations?</div>
<div style="">- Because of some of these points, it seems like
this is more, at least at this point, an integrator level
problem--there are ways to solve it and they can be addressed
by integrators.</div>
<div style="">- <a moz-do-not-send="true"
href="https://github.com/plone/plone.app.contentmenu/issues/2">https://github.com/plone/plone.app.contentmenu/issues/2</a>
provides another way to add additional "add new" menu items.</div>
<div style="">- This is definitely a plip where it's better to
first implement it as an addon so we can see it working
somehow first before we accept the implementation.</div>
<div style=""><br>
</div>
<div style="">- One last thing, if we ever get a more robust
folder contents or "structure" menu where we can globally
manage content for plone in a better way, this might be less
of a problem<br>
</div>
<div style=""><br>
</div>
<div style="">So, with all that being said, let's not end the
discussion here. Perhaps, we just need to work through a
difficult solution.</div>
<div style=""><br>
</div>
<div style=""><br>
</div>
<div style="">
-Nathan</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Feb 20, 2013 at 7:35 PM, Jon
Stahl <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jonstahl@gmail.com" target="_blank">jonstahl@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Dylan-<br>
<br>
You know, I've had this use case and very successfully
solved it with<br>
just a simple content rule to "move all items of type X to
WHERE THEY<br>
BELONG." Users can create those content types anywhere, but
then<br>
poof, they magically go to the place they're supposed to be
as soon as<br>
they hit save.<br>
<br>
:Jon<br>
<div>
<div class="h5"><br>
<br>
On Wed, Feb 20, 2013 at 5:12 PM, Dylan Jay <<a
moz-do-not-send="true" href="mailto:djay@pretaweb.com">djay@pretaweb.com</a>>
wrote:<br>
> Hi,<br>
><br>
> You might remember awhile back I talked about
"Placeless Adding". Since then<br>
> I have submitted it as PLIP and it was rejected on
the grounds that the<br>
> implementation wasn't accepted. Despite this, I
believe that this issue is<br>
> still something that needs to be addressed in Plone
and I thought that it<br>
> would be good to go back to the beginning and with
the collective UX wisdom<br>
> on this list, come up with a more acceptable
solution to this problem.<br>
><br>
> Plone's UI for adding content for types that live
in a specific location<br>
> have some complexities which can be a frustration
for users. Namely, users<br>
> need to have special knowledge of where that
content should be placed and in<br>
> creating that content it requires many clicks to
navigate to that section of<br>
> the site and add the content. Wordpress sites prove
to be far easier in this<br>
> regard because the "blog post" type is immediately
available on the front<br>
> page though an "add post" button and represents 99%
of the content adding<br>
> content use cases.<br>
><br>
> In some larger sites the problem becomes far worse.
Particularly where you<br>
> have a front page composed of multiple content
sources and types drawn from<br>
> different parts of the site managed by different
people. This was the case<br>
> for one of our clients who operated one of the
largest Plone sites in the<br>
> world - we were not the implementers of this site
but just giving support,<br>
> however, they have recently decided to switch to
another CMS for a variety<br>
> of reasons. One of those reasons we can identify is
that for content editors<br>
> it had become complex to train and operate place
sensitive content buried 3<br>
> or 4 levels deep. This situation needs lots of
navigation clicks to jump<br>
> between those sections of the site making the
experience rather frustrating.<br>
> Most users only had edit access to these specific
sections.<br>
><br>
> As someone pointed out earlier, even in the initial
Plone install we have an<br>
> events folder and a news folder. You need to learn
to go there to add those<br>
> kinds of content. This seems natural to us but the
concept of where you add<br>
> something matters a lot, we have to teach every
time to new users. Instead<br>
> this could be simplified so that News only goes to
the news folder and<br>
> events only go the events folder and we had a way
to make it easy to add<br>
> either of those from anywhere. This should, I
believe, make for a simpler<br>
> experience and a more gentle introduction when
coming from a different CMS.<br>
><br>
> Do you agree?<br>
><br>
> If so, whats the best UX to implement this?<br>
><br>
><br>
><br>
> Adam Terrey<br>
> Software Engineer<br>
> PretaWeb<br>
><br>
> Visit our website<br>
> Email me at <a moz-do-not-send="true"
href="mailto:adam.terrey@pretaweb.com">adam.terrey@pretaweb.com</a><br>
> Call me on <a moz-do-not-send="true"
href="tel:%2B61%202%208203%204021"
value="+61282034021">+61 2 8203 4021</a><br>
><br>
> Multi-site solutions for high availability and
scalability.<br>
> Find out about Plone<br>
><br>
><br>
</div>
</div>
> _______________________________________________<br>
> UI mailing list<br>
> <a moz-do-not-send="true"
href="mailto:UI@lists.plone.org">UI@lists.plone.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.plone.org/mailman/listinfo/plone-ui"
target="_blank">https://lists.plone.org/mailman/listinfo/plone-ui</a><br>
><br>
_______________________________________________<br>
UI mailing list<br>
<a moz-do-not-send="true" href="mailto:UI@lists.plone.org">UI@lists.plone.org</a><br>
<a moz-do-not-send="true"
href="https://lists.plone.org/mailman/listinfo/plone-ui"
target="_blank">https://lists.plone.org/mailman/listinfo/plone-ui</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
UI mailing list
<a class="moz-txt-link-abbreviated" href="mailto:UI@lists.plone.org">UI@lists.plone.org</a>
<a class="moz-txt-link-freetext" href="https://lists.plone.org/mailman/listinfo/plone-ui">https://lists.plone.org/mailman/listinfo/plone-ui</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Jure Cerjak
Termitnjak d.o.o.
Web: <a class="moz-txt-link-freetext" href="http://www.termitnjak.com">http://www.termitnjak.com</a>
Tel: +386 (0)40 162-740
Email: <a class="moz-txt-link-abbreviated" href="mailto:jcerjak@termitnjak.si">jcerjak@termitnjak.si</a>
Skype: jurecerjak</pre>
</body>
</html>