From 3fe5f57ea08233e1ee67c8aa2453a631d7e9698a Mon Sep 17 00:00:00 2001 From: Steve Piercy Date: Tue, 14 Jan 2025 11:19:22 -0800 Subject: [PATCH] Update docs/developer-guide/standardize-python-project-configuration.md Co-authored-by: Maurits van Rees --- .../developer-guide/standardize-python-project-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-guide/standardize-python-project-configuration.md b/docs/developer-guide/standardize-python-project-configuration.md index 8c08903ed..77930b074 100644 --- a/docs/developer-guide/standardize-python-project-configuration.md +++ b/docs/developer-guide/standardize-python-project-configuration.md @@ -15,7 +15,7 @@ It does not cover the following. - Volto or any other JavaScript-based project, which has its own ecosystem. - Monorepo projects with backend and frontend code bases, such as those created by [Cookieplone](https://github.com/plone/cookieplone). Repositories must have a single Python package at the top level. -- Project that support multiple versions of Plone in the same branch. +- Projects that support multiple versions of Plone in the same branch. Plone consists of hundreds of projects. To lessen the effort of configuring a new project in the Plone GitHub organization, and to keep these projects current with latest configuration practices, the Plone community agreed upon a trusted set of configuration items.