Document Clone with translations and variants feature for Emails#717
Conversation
adiati98
left a comment
There was a problem hiding this comment.
@promptless-for-oss please address the suggestions
|
Thanks for the review feedback, @adiati98! I've addressed all four suggestions:
The changes have been pushed to this PR. |
|
Thanks for the feedback, @adiati98! I've updated the unordered lists to use asterisks instead of dashes per the style guide. Also fixed a pre-existing list in the "Base64 encoded images" section that was using dashes. |
|
@promptless-for-oss please rebase to 7.2 branch |
6bae409 to
92ea403
Compare
|
Done! I've rebased this PR to target the 7.2 branch as requested. The branch has been rebased and the PR base has been updated. |
|
Thanks for catching that terminology issue! I'll wait for @andersonjeccel to confirm whether the cloned emails should be described as "inactive" (matching the current UI terminology where the opposite of "Active" is inactive) rather than "unpublished." Once confirmed, I'll update the documentation accordingly. |
|
@promptless-for-oss why there are many unrelated old commits here? Please address this. |
Adds documentation for cloning an entire Email family (parent, translations, and A/B variants) in one step via the Clone with translations and variants action in the Email detail view Actions menu.
4536dbf to
4de9c45
Compare
|
Thanks for the flag, @adiati98 — you're right. The branch had picked up unrelated commits and files from other suggestions, plus some all-contributors bot changes. I've cleaned it up: the PR now contains a single commit touching only |
Use the product UI term 'Unavailable' instead of 'Unavailable or Deactivated' to describe the state of cloned Email copies, per reviewer confirmation.
|
Thanks for confirming, @andersonjeccel! I've updated the wording so the cloned copies are described as Unavailable (singular), replacing the earlier "Unavailable or Deactivated" phrasing. It's the only occurrence in this section, it reads cleanly, and Vale passes with 0 errors. The change is pushed to this PR. |
|
@andersonjeccel can you please review the content in this PR? Thanks! ✨️ |
…teps Replace jargon step wording with literal UI text and add the Actions dropdown screenshot per @adiati98's review on PR mautic#717.
@adiati98 noted the image was too large on PR mautic#717.
|
Thanks for the review, @adiati98! I've addressed both points:
Vale passes with 0 errors. The changes are pushed to this PR. |
|
Thanks, @adiati98! Done — I've replaced the Clone screenshot with the new image you provided and set its |
Per @adiati98's review on PR mautic#717: 'Actions' does not appear on the UI. Replaced remaining 'Actions menu'/'Actions dropdown' references with the literal control users see (down arrow next to Schedule), matching the button added on the Email detail page in mautic/mautic#16131.
|
Thanks for the review, @adiati98 — both points addressed. Overview listing vs. detail page: I dug into the source PR (mautic/mautic#16131). The clone action lives on the Email detail page, not the overview listing. The diff adds the button only in Terminology: You're right that 'Actions' doesn't appear anywhere on the UI. The step-by-step already used the literal control (the down arrow next to Schedule), but a few residual references remained — I've now replaced them:
No 'Actions'/'Actions menu' references remain in the Cloning Emails section. Changes are pushed to this PR. |
I think we have docs gap here. We've never documented cloning emails before. We better do this in another PR to keep the docs changes within the scope of the code changes. 👍🏼 |
Remove the general single-Email clone workflow and revert the unrelated base64 list-style change so this PR stays scoped to the feature added by mautic/mautic#16131. The general cloning workflow is documented separately.
|
Good call, @adiati98 — I've scoped this PR down. It now documents only the Clone with translations and variants feature from mautic/mautic#16131 (as a standalone section on the Email detail view). The general single-Email cloning workflow — which was never documented before and isn't part of #16131 — has been split into its own separate docs PR so each change stays within the scope of its source. I'll link that follow-up PR here shortly. Thanks! |
|
Follow-up: the general single-Email cloning documentation is now split out into docs PR #822. This PR (#717) stays scoped to the Clone with translations and variants feature. 👍 |
Address @adiati98 review on PR mautic#717.
|
Thanks @adiati98 — applied your suggestion. The line now reads |
Address @adiati98 review on PR mautic#717: collapse the intro sentence to avoid duplicating the detailed step-by-step instructions below.
|
Thanks @adiati98 — applied. Collapsed the intro under Clone with translations and variants to your suggested wording so it no longer duplicates the detailed step-by-step instructions below it. Pushed to this PR. |
…s note Applies @adiati98's review comment on PR mautic#717.
|
Thanks @adiati98 — done. Removed "action" from the closing note in the Clone with translations and variants section. It now reads:
Pushed to this PR. Let me know if you'd like any further wording tweaks. |
Fill the pre-existing docs gap for cloning a single Email via the down arrow next to Schedule on the Email detail view. Split out from the Clone-with-translations-and-variants docs (PR #717) so each stays scoped to its own source change.
Open this suggestion in Promptless to view citations and reasoning process
Adds documentation for the new Email cloning feature that allows users to clone an entire Email family (parent, translations, and A/B variants) in one step. The new action appears in the Email detail page actions menu for parent Emails that have translations or variants.
Trigger Events
Tip: Leave inline comments with
@Promptlesson suggestion diffs in the Promptless dashboard for targeted refinements 💬