-
-
Notifications
You must be signed in to change notification settings - Fork 18
RFC: switch "featured content" and "donate" features to be generic WordPress block areas #105
Copy link
Copy link
Open
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature🏁 status: ready for workReady for workReady for work💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🕹 aspect: interfaceConcerns end-users' experience with the softwareConcerns end-users' experience with the software🟨 priority: mediumNot blocking but should be fixed soonNot blocking but should be fixed soon🤖 aspect: dxConcerns developers' experience with the codebaseConcerns developers' experience with the codebase
Description
Metadata
Metadata
Assignees
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature🏁 status: ready for workReady for workReady for work💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🕹 aspect: interfaceConcerns end-users' experience with the softwareConcerns end-users' experience with the software🟨 priority: mediumNot blocking but should be fixed soonNot blocking but should be fixed soon🤖 aspect: dxConcerns developers' experience with the codebaseConcerns developers' experience with the codebase
Type
Projects
Status
Backlog
Problem
The
creativecommons-basetheme currently defines theme configuration forms and templates for two specific components:However, the hard-coded nature of these templates may be inflexible while introducing a maintenance burden to the project.
Description
Consider creating two generic theme block areas, such as
below_headerandabove_footerwherein we can place Gutenberg blocks. For example, there can be a separate project for CC-specific Gutenberg blocks such as a Donation Appeal Block and a Featured Content Card block.Additional context
WordPress 5.8 allows developers to define template regions that can contain Gutenberg blocks.
