Mastering Plone 6#

Proposed changes to this treainning for Plone 6
About Mastering Plone::

1. Upcoming Trainings
2. Previous Trainings
3. Trainers
4. Using the documentation for a training
5. Building the documentation locally
6. Build new
7. Train the trainer
8. Contributing
9. License

Introduction::

1. Who are you?
2. What will we do?
3. What will we not do?
4. What to expect
5. Classroom Protocol
6. Documentation
7. Further Reading

What is Plone?::

1. Core concepts
    ++ Add Info on RESTAPI and VOLTO

Installation & Setup::

1. Installing Plone
    ++ Add info on building the Frontend
2. Hosting Plone
    ++ Add Info on deploying the Frontend
3. Production Deployment

Installing Plone for the Training::

1. Installing Plone without vagrant
2. Installing Plone with Vagrant
    ++ Update to build VOLTO

The Case Study::

1. Background
2. Requirements
    ++ Discuss where which feature will need to be develop

The Features of Plone::

1. Starting and Stopping Plone
2. Walkthrough of the UI
3. Users
4. Configure a Mailserver
5. Content-Types
6. Folders
7. Collections
8. Content Rules
9. History
10. Manage members and groups
11. Workflows
12. Working copy
13. Placeful workflows
    ++ Update to use new fronte

The Anatomy of Plone::

    ++ Start with Backend / RESTAPI / Fronte
1. Database
2. Zope
3. Content Management Framework
4. Zope Toolkit / Zope3
5. Zope Component Architecture (ZCA)
6. Pyramid
7. Exercise

What’s New in Plone 5, 5.1 and Plone 5.2::

    ++ Rewrite for Plone 6 and Volto
1. Default Theme
2. New UI and widgets
3. Folder Contents
4. Content Types
5. Resource Registry
6. Chameleon template engine
7. Control panel
8. Date formatting on the client side
9. plone.app.multilingual
10. New portlet manager
11. Remove portal_skins
12. Plone 5.1
13. Plone 5.2

Configuring and Customizing Plone::

    ++ Rewrite for Controlpanels in VOLTO
1. The Control Panel
2. Portlets
3. Viewlets
4. ZMI (Zope Management Interface)
5. Summary

Theming::

    ??

Extending Plone::

    ++ Rewrite for React and RESTAPI
1. Extension technologies

Extend Plone With Add-On Packages::

    ++ Rewrite to discuss frontend and backend-addons
1. Some notable add-ons
2. How to find add-ons
3. Installing Add-ons
4. collective.easyform
5. Add page layout management with plone.app.mosaic
6. Internationalization
7. Summary

Buildout I::

    ++ Move after "Add your own addons"
    ++ Add a chapter that discusses the Volto-Addon structure
1. Minimal Example
2. Syntax
3. Recipes
4. References
5. A real life example
6. Mr. Developer
7. Extensible
8. Be McGuyver

Write Your Own Add-Ons to Customize Plone::

    ++ use plonecli
Creating the package
Eggs
Inspecting the package
Including the package in Plone
Exercises
Summary

Dexterity I: Content types::

    ++ Rewrite (Start with Python Schema in the Filesystem)
What is a content type?
The makings of a Plone content type
Modifying existing types
    #. Default Behaviors
Creating content types TTW
Exercises


Dexterity II: Talk::

    #. The fti
    #. The type registration
    #. The schema
    #. The instance class
    #. Enabling our code (install/reinstall)
    #. Field type reference
    #. Schema directives: widgets, permissions
    #. point to later chapter for complete list of features


XX. Add your own Volto addon

    #. Add a Volto Addon (create-volto-app)

XX. Add a custom view component for talks

    #. Register new view src/components/Views/Talk.jsx
    #. Finish View incrementally


Views I::

    ++ Maybe move to a later state
1. A simple browser view

Page Templates::

    ++ Remove / Replace with a chaptere on custom Components with JSX
1. TAL and TALES
2. Chameleon
3. Exercise 1
4. METAL and macros
5. Accessing Plone from the template
6. Exercise 2
7. Accessing other views
8. What we missed

Customizing Existing Templates::

    ++ Replace with chapter on overwriting existing React components
1. The view for News Items
2. The Summary View
3. Finding the right template
4. skin templates
5. Summary

Views II: A Default View for “Talk”::

    ++ Replace with custom component
1. View Classes
2. Browser Views
3. Reusing Browser Views
4. The default view
5. Using helper methods from DefaultView
6. The complete template for talks
7. Behind the scenes

Views III: A Talk List::

    ++ Replace with a custom component that uses the @search endpoint to get talks
    ++ Keep information on catalog, indexes and metadata. Discuss search endpoint
1. Using portal_catalog
2. brains and objects
3. Querying the catalog
4. Exercises
5. The template for the listing
6. Setting a custom view as default view on an object
7. Summary

Testing in Plone::

    ++ ???
1. Types of tests
2. Writing tests
3. Plone tests
4. Robot tests
5. More information

Behaviors::

    ++ Keep as it is
1. Dexterity Approach
2. Names and Theory
3. Practical example
4. Adding it to our talk

Writing Viewlets::

    ++ Replace with a component
1. A viewlet for the featured behavior
2. Featured viewlet
3. Exercise 1
4. Exercise 2

Programming Plone::

    ++ Add chapter (before or after) on restapi and various endpoints
    ++ Discuss best-practices and tools for JS/React-Development
1. plone.api
2. portal-tools
3. Debugging
4. Exercise

IDEs and Editors::

    ++ Same as above: Discuss helpful features in editors for JS Development


Dexterity Types II: Growing Up::

    ++ remove part on marker interfaces (since we already have a python
1. Add a marker interface to the talk type Interface)
2. Upgrade steps
3. Add a browserlayer
4. Add catalog indexes
5. Query for custom indexes
6. Exercise 1
7. Add collection criteria
8. Enable versioning
9. Summary

Custom Search::

    ++ maybe remove or mention volto-based addons here
1. eea.facetednavigation
2. collective.collectionfilter

Turning Talks into Events::

    ++ Keep behavior. Replace view-change with reusing a (hopefully) existing react component
1. Exercise 1
2. Exercise 2

User Generated Content::

    ++ Keep this
1. Self-registration
2. Constrain types
3. Grant local roles
4. A custom workflow for talks
5. Move the changes to the file system

Resources::

    ++ Remove or add info on theming with Volto

Using Third-Party Behaviors::

    ++ remove or replace.
    ++ Maybe the addon collective.behavior.banner could be useful in Volto as well with a custom endpoint
1. Add Teaser With collective.behavior.banner

Dexterity Types III: Python::

    ++ Keep content-type as before
    ++ change Viewlet to custom component
    ++ the scaling-thing might be a problem
1. The Python schema
2. Directives
3. Validation and default values
4. The Factory Type Information, or FTI
5. The view
6. The viewlet
7. The template for the viewlet

Relations::

    ++ Keep but add a use-case for the conferennce-Website (e.g. linking Users to Talks if self-registration and membrane would work in Plone 6)
1. Creating relations in a schema
2. Accessing and displaying related items
3. Creating RelationFields through the web
4. The stack
5. RelationValues
6. Accessing relations and backrelations from code

Manage Settings with Registry, Control Panels and Vocabularies::

    ++ Keep control panel in backend? Add example for control panel in Fronend?
1. The Registry
2. A setting
3. Accessing and modifying values in the registry
4. Add a custom control panel
5. Vocabularies

Creating a Dynamic Front Page::

    ++ Remove with a simple blocks-bases site
1. The Front Page
2. The template
3. Twitter
4. Activating the view

Creating Reusable Packages::


More Complex Behaviors::

    ++ Add custom restapi-endpoint for voting
    ++ Change to use BTrees instead of PersitentDict
1. Using Annotations
2. Using Schema
3. Writing Code

A Viewlet for the Votable Behavior::

    ++ Replace with new frontend component for the new Voting endpoint
1. Voting Viewlet
2. Writing the Viewlet code
3. The template
4. JavaScript code
5. Writing 2 simple view helpers

Making Our Package Reusable::

    ++ Keep this since it ties the different addons together
1. Adding permissions
2. Using our permissions
3. Provide defaults

Using starzel.votable_behavior in ploneconf.site::

    ++ keep

Releasing Your Code::

    ++ ???

Buildout II: Getting Ready for Deployment::

1. The Starzel buildout
2. A deployment setup
3. Other tools we use

Plone REST API::

    ++ Add new custom react component for lightining talks
    ++ Move up since it is easier than voting
1. Installing plone.restapi
2. Explore the API
3. Implementing the talklist
4. Submit lightning talks
5. Exercise

The Future of Plone::

    ++ Update


Optional::

    ?