Skip to content

Conversation

@mr-shellychauhan
Copy link
Contributor

Information on how to amend the checkout to your own specification where required.

Description

Added information on how to change the checkout steps to cater for your own requirements

Type of suggestion

  • Typo/grammar fix
  • Updated outdated content
  • [X ] New content
  • Updates related to a new version
  • Other

Product & version (if relevant)

Umbraco/Commerce 13

Deadline (if relevant)

When should the content be published?
ASAP

Information on how to amend the checkout to your own specification where required.
@eshanrnh
Copy link
Contributor

Thanks @MrEssCee for the PR 💪 We will review it as soon as possible.

@sofietoft
Copy link
Contributor

Thanks again for the PR @MrEssCee !

I've taken the liberty to make some necessary changes to your PR.

Here are some things to keep in mind for your next contributions:

  • All articles added to the docs need to added a .md files.
  • All articles needs a title (H1 heading, #).
  • There must only be one H1 heading in an article.
  • Our documentation is written in US English, hence the changes from customise to customize.

For reference, I'd recommend you checkout our styleguide.

I'll run this by our developers for a review by them as well 💪

@sofietoft sofietoft added the review/developer Use this label if an internal developer review is required label Feb 19, 2025
@sofietoft
Copy link
Contributor

Hi again @MrEssCee ! 👋

We have green lights from our Commerce developers, so with my latest changes we are just waiting for the checks to complete.

Thanks again for the PR 💪 Always great to have more guides added to our documentation! MUCH appreciated 😄

@sofietoft sofietoft merged commit 0e7ea19 into umbraco:main Feb 19, 2025
11 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category/umbraco-commerce review/developer Use this label if an internal developer review is required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants