1. Our Questions
- How long for non-technical people to be ready to enter content?
- How "fast" does the site respond with thousands, millions of items?
- Is it easy for an administrator to manage users, permissions, workflows, and notifications?
2. Default Editor
Plone's default editor is TinyMCE 4 which is very common and used by many projects such as Wordpress. It has custom panels for image upload and linking to internal content to make these experiences much smoother.
Plone provides automatic image scales as you upload new pictures and you can customize the sizes the system creates via the Site Setup.
You can also customize the TinyMCE editor experience via Site Setup, but the UI to do so is only aimed at more experienced administrators.
Content can be set to have an effective date and expiration date that will control its visibility in various areas of the navigation.
Both sites support making revisions of the content as edits are made allowing the author to make a comment on the changes.
The structure of the site is determined by how you place content in containers. Pages can be created in the context of the folder where you want them to show in the site. Plone will have the navigation mimic the structure of your content in the navigation by default. Collections can be used to create synthetic browse paths based on queries to generate lists of content.
Collections are similar to Drupal Views, but have an nice easy interface for creating the query of content. The Collection itself is a firstclass piece of content in the system and has a Title and Body text that is searchable via the standard search mechanism. Collection support many different displays out of the box to customize how the collection is rendered to the visitor.
Drupal Blocks line up to Plone’s Viewlets
In Plone, images uploaded via the WYSIWYG are first class content citizens.
CKEditor is the default editor.
The experience of adding content has always been dramatically improved in Drupal 8.
Customization of the CKEditor is very nice with a drag and drop toolbar editor.
Image handling within Ckeditor is upload only
Revision tracking available by default BUT requires a check to enable it optionally per edit
Menu allows for adding the page you’re creating to a menu. Which menu any given content type can be added to is configurable per content type.
To create hierarchy, simply place a new or existing node into a menu and select the parent menu item which already exists.
Ex: Services page exists and you’re adding “home repair” node. Add it under Main-menu->Services and it is a child of Services
Note: zero zilch nada ux for leveraging this hierarchy. Drupal makes zero assumptions on how you will leverage this.
Popular contribution modules for this are simple_menu, menu_block, megamenu, maximenu
Views is the mega awesome list building module with a rich UI for building complex queries for rendering on the page as html. The initial page for creating a view is simple and fits most use cases. Save-And-Edit brings you more functionality if needed.
Out of the box, Views can create a Page, a Block, a Feed,
Optional (set by default) separate theme for front-end/backend
Images uploaded via the WYSIWYG are not first class content citizens.
There are no formal workflows in core.