[Plone-UI] Folderish Page Proposal

[Dylan Jay]

On 08/10/2013, at 4:32 PM, Nathan Van Gheem <nathan at vangheem.us> wrote:

> So starting this discussion back up, I don't like the idea of adding a display tab to the page type and getting rid of the collection type--I thinking solving a problem by creating another less bad problem. 
> 
> However, I really do like the idea of getting rid of default pages and having everything folderish.
> 
> I'm inclined to say we push plone 5 with the current set of features we've already agreed on and then in plone 6, we move everything folders, get rid of collections and have a deco layout editor.
> 
> If we just let the deco layout engine be applied to any type, it would also solve the default page issue.

It seems a shame that since we are going to break things with plone5 and we seem to mostly agree everything folderish (done right) solves lots of problems, that we don't explore more a stepping stone approach.

I'd like to look more at tinymcetiles since it is more flexible than the page-folder-collection merger but means we don't have to deal with grids in both backend and frontend when we're still not sure how that will work with a world where the frontend could include anything including another grid system. 
Collections get converted to a tile on a page but we don't need to ship with many other tiles. We don't need to change how we do images for example.
We also don't need to change portlets yet or include the deco idea of saved layouts.
When you think about it, its almost the same as the proposal to merge collections and display into the page type, except that you can pick where in the page that listing goes, instead of it being at the bottom.

Although thinking about it more you still don't get rid of the display menu completely as what happens to plugins like solgema.calendar? They rely on being views on collections. I guess they would have to turn into a tile instead and include the query in their own configuration?


http://svn.plone.org/svn/collective/collective.tinymcetiles/trunk/README.txt



> 
> 
> -Nathan
> 
> 
> On Sun, Oct 6, 2013 at 2:48 PM, Nathan Van Gheem <nathan at vangheem.us> wrote:
> 
> 
> 
> On Sun, Oct 6, 2013 at 2:43 PM, Johannes Raggam <raggam-nl at adm.at> wrote:
> I like the idea to have everything folderish and to get rid of the
> "Default View" mechanism.
> 
> For my projects I always use folderish types because I see a lot of
> advantages in it. For Archetypes based sites I use
> collective.folderishtypes.
> 
> In my experience, this has these usability downsides:
> 
> - The folderish types don't show their contents in their view (I solved
> that with a viewlet or portlet on folderish types).
> Make the new folder contents much more useful and encouraging people to use it more should should help this.
>  
> 
> - After adding a folderish type, one lands in it's detail view and
> immediately adding another item adds it into the content created before.
> That's not what you'd expect if you're in a hurry and doing lot's of
> editing. (Can be solved by redirection after creation to the parent
> folder)
> Everyone should take a look at the new folder contents in the mockup project. There is an add menu there that creates the content while keeping you in the folder contents view for these types of situations where you want to add a lot of content at once to build your site quickly.
>  
> 
> Like Martin, I dislike mixing the Collection functionality into a
> Über-Page. To clients I always explain the Collection type as something
> as a Search-Folder and I - from a user-perspective - wouldn't expect
> that functionality in a "Display" fieldset. A collection can still be
> folderish too.
> 
> I'm unsure on getting rid of the "Display" menu. While moving it into
> the editing fieldsets could be a chance to allow users to also add an
> optional content listing of their folderish content, the current menu
> placement makes a lot of sense to me.
> 
>  
> 
> Johannes
> 
> 
> 
> 
> --
> programmatic  web development
> di(fh) johannes raggam / thet
> python plone zope development
> mail: office at programmatic.pro
> web:  http://programmatic.pro
>       http://bluedynamics.com
> 
> _______________________________________________
> UI mailing list
> UI at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-ui
> 
> 
> 
> 
> -- 
> Nathan Van Gheem
> Solutions Architect
> Wildcard Corp
> 
> 
> 
> -- 
> Nathan Van Gheem
> Solutions Architect
> Wildcard Corp
> _______________________________________________
> UI mailing list
> UI at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-ui