Skip to content

feat: offer next steps on the order received page - #4

Open
YvesCesar wants to merge 3 commits into
mainfrom
feat/order-received-next-steps
Open

feat: offer next steps on the order received page#4
YvesCesar wants to merge 3 commits into
mainfrom
feat/order-received-next-steps

Conversation

@YvesCesar

Copy link
Copy Markdown
Contributor

Suggestion by @henmohr

No checkout/order-received colocar um botão para o usuário acessar o painel de configurações (wordpress) ou fazer sua primeira assinatura (encaminha para o nextcloud).

Related issue: Onboarding do cliente


Implementation: a next steps section with two actions

Screenshot From 2026-07-27 08-27-02

Signed-off-by: YvesCesar <yvesamorim73@gmail.com>
@YvesCesar
YvesCesar marked this pull request as draft July 27, 2026 12:52
Signed-off-by: YvesCesar <yvesamorim73@gmail.com>
@YvesCesar
YvesCesar marked this pull request as ready for review July 27, 2026 13:20
@YvesCesar
YvesCesar requested a review from vitormattos July 27, 2026 13:20

@vitormattos vitormattos left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this should be done differently. If we add a new product, or if the next step isn't this one, this will always remain the next step because it is hardcoded.

@henmohr

henmohr commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

I believe this should be done differently. If we add a new product, or if the next step isn't this one, this will always remain the next step because it is hardcoded.

This could be added to the backlog, since we currently only have one product on offer, but it is a future issue that can be easily resolved. I added a commit in an attempt to fix this.

@vitormattos vitormattos Jul 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the best approach is to use the product note. It’s a default field for a product and it can support rich text. When we translate a product, the note also needs to be translated. Hardcoding the next steps would be a risky workaround.

Follow the suggested field to be used:

Image

If we add this PR as-is to the backlog, we can avoid approving a workaround that would generate a lot of code and extra work for a change that can be solved with a simple fix.

A more simple approach is to define a best place to display the product note.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants