Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEV Misc SEO Update #3002

Merged
merged 8 commits into from
Jan 4, 2025
Merged

DEV Misc SEO Update #3002

merged 8 commits into from
Jan 4, 2025

Conversation

james-hooper-spryker
Copy link
Collaborator

PR Description

changed the meta description for misc articles within the developing standalone modules section in dev docs

Steps before you submit a PR

  • Please add tests for the code you add if it's possible.
  • Please check out our contribution guide: https://docs.spryker.com/docs/dg/dev/code-contribution-guide.html
  • Add a contribution-license-agreement.txt file with the following content:
    I hereby agree to Spryker\'s Contribution License Agreement in https://github.com/spryker/spryker-docs/blob/HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH/CONTRIBUTING.md.

This is a mandatory step to make sure you are aware of the license agreement and agree to it. HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH is a hash of the commit you are basing your branch from the master branch. You can take it from commits list of master branch before you submit a PR.

Checklist

  • I agree with the Code Contribution License Agreement in CONTRIBUTING.md

changed the meta description for misc articles within the developing standalone modules section in dev docs
@james-hooper-spryker james-hooper-spryker added the TW review needed PR needs Technical writer's review label Dec 18, 2024

#### Support requests
* Open a support request to apply the new configuration to the environment. Attach the deploy file and shortly explain expected changes, that is the stores that need to be introduced. If the necessary configuration is in a specific repository branch, reference it in the ticket and make sure the support team has access to your code base.
* Run the destructive deployment, assuring the right store(s) is specified.
Copy link
Collaborator

Choose a reason for hiding this comment

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

@feversocial How's this related to support?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Running the destructive deploy - is not related to support directly. The idea is, as long as support request is satisfied, one (customer/partner) has to run a destructive deployment as a next step.

### Production Setup
#### Configuration Preparation

* Prepare the production environment’s configuration similarly to the staging setup.
Copy link
Collaborator

Choose a reason for hiding this comment

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

By preparing do you mean adding the configuration and running a destructive pipeline?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Adding the configuration - yes (basically doing the "coding" part)

@andriitserkovnyi andriitserkovnyi merged commit 40f2020 into master Jan 4, 2025
3 checks passed
@andriitserkovnyi andriitserkovnyi deleted the DEV-Misc-SEO-Update branch January 4, 2025 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TW review needed PR needs Technical writer's review
Development

Successfully merging this pull request may close these issues.

3 participants