Skip to content

[MWPW-195995] - Rich content authorable gradient#6239

Open
DKos95 wants to merge 5 commits into
stagefrom
rich-content-authorable-gradient
Open

[MWPW-195995] - Rich content authorable gradient#6239
DKos95 wants to merge 5 commits into
stagefrom
rich-content-authorable-gradient

Conversation

@DKos95 DKos95 requested a review from a team July 1, 2026 13:04
@aem-code-sync

aem-code-sync Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

@zagi25

zagi25 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

From the authoring perspective, does it make sense to move gradient value to section-metadata or to the column next to the text ? Background image is already added via section-metadata, and I don't expect rich-content block to have an image on the side, so I guess we can also use right column for the gradient.
Screenshot 2026-07-01 at 15 30 54

Comment thread libs/utils/decorate.js Outdated
@DKos95

DKos95 commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

From the authoring perspective, does it make sense to move gradient value to section-metadata or to the column next to the text ? Background image is already added via section-metadata, and I don't expect rich-content block to have an image on the side, so I guess we can also use right column for the gradient.>

I don't know if it makes sense moving it to section-metadata since it's specific to only rich-content.
On moving it to the column next to text I thought about that, but what if they want to have a background color and gradient, would it maybe be confusing, this way they are kind of separate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants