Skip to content

Commit

Permalink
its
Browse files Browse the repository at this point in the history
  • Loading branch information
@andriitserkovnyi
andriitserkovnyi committed Jan 2, 2025
1 parent 0e4290b commit 6ea5da7
Show file tree
Hide file tree
Showing 905 changed files with 1,575 additions and 1,563 deletions.
2 changes: 1 addition & 1 deletion _archive/release-notes/release-notes-202212.0/release-notes-202212.0.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Adapting your offerings to your customers' needs and locales is crucial for prov

#### Number formatting in the Storefront

For an effortless shopping experience, the localized number formatting is available throughout the Storefront for any user locale. Whether it is a catalog, product details page, cart, checkout, or customer account, your customers and guests can now enjoy their known number format. This helps to avoid any confusion about pricing or quantities.
For an effortless shopping experience, the localized number formatting is available throughout the Storefront for any user locale. Whether it's a catalog, product details page, cart, checkout, or customer account, your customers and guests can now enjoy their known number format. This helps to avoid any confusion about pricing or quantities.

##### Documentation

Expand Down
2 changes: 2 additions & 0 deletions _data/sidebars/dg_dev_sidebar.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -909,6 +909,8 @@ entries:

- title: Internationalization and multi-store
nested:
- title: Adding stores in a multi-database setup
url: /docs/dg/dev/internationalization-and-multi-store/adding-stores-in-a-multi-database-setup.html
- title: Handling internationalization
url: /docs/dg/dev/internationalization-and-multi-store/handling-internationalization.html
- title: Managing glossary keys
Expand Down
2 changes: 1 addition & 1 deletion _drafts/acp-apps-development/develop-an-app/app-manifest.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ For the manifest, make sure to follow these conditions:
|description | Full description of the app. New line symbols and HTML tags are not allowed. | "description": "BS PAYONE GmbH is headquartered in Frankfurt am Main and is one of the leading omnichannel-payment providers in Europe. In addition to providing customer support to numerous Savings Banks (Sparkasse) the full-service payment service provider also provides cashless payment transaction services to more than 255,000 customers from stationary trade to the automated and holistic processing of e-commerce and mobile payments." |
|developedBy | Optional. Provides information about who developed the App. | "developedBy": "Spryker Systems GmbH" |
|url | URL to a homepage of the application provider (not visible in the AppCatalog). | "url": "https://www.payone.com/DE-en" |
|isAvailable | Shows if the application is currently available. Possible values:<br><ul><li>false — the application is not available, it isn't possible to connect and configure it.</li><li>true — the application is available, it’s possible to connect, configure, and use it.</li></ul> | "isAvailable": true |
|isAvailable | Shows if the application is currently available. Possible values:<br><ul><li>false — the application is not available, it'sn't possible to connect and configure it.</li><li>true — the application is available, it’s possible to connect, configure, and use it.</li></ul> | "isAvailable": true |
|businessModels | An array of suite types that are compatible with the application. Possible values:<ul><li>B2C</li><li>B2B</li><li>B2C_MARKETPLACE</li><li>B2B_MARKETPLACE</li></ul> | See *businessModels example* under this table. |
|categories | An array of categories that the application belongs to. Possible values:<ul><li>BUSINESS_INTELLIGENCE</li><li>CONSENT_MANAGEMENT</li><li>LOYALTY_MANAGEMENT</li><li>PAYMENT</li><li>PRODUCT_INFORMATION_MANAGEMENT</li><li>SEARCH</li><li>TAX</li><li>USER_GENERATED_CONTENT</li></ul> | See *categories example* under this table. |
|pages | Adds additional content to the application detail page. This part contains an object with a page type and its blocks.<br>Possible page types (object keys):<ul><li>Overview</li><li>Legal</li></ul>Each page can contain no or multiple blocks. Each block should be specified by an object with the following keys:<ul><li>title — header of the block;</li><li>type — the way the data is displayed. Possible values:<ul><li>list<li>text</li></ul><li>data — information that is displayed inside the block. Can be a string, if *type=text*, or an array of strings if *type=list*.</li></ul> | See *pages example* under this table. |
Expand Down
2 changes: 1 addition & 1 deletion _drafts/acp-apps-development/develop-an-app/sync-api.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ redirect_from:
- /docs/acp/user/sync-api.html
---

[Sync API](https://github.com/spryker-sdk/sync-api/) is the synchronous API that Spryker supports. In the Spryker terminology, it is also known as [Glue API](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/glue-rest-api.html) with its [REST API B2C Demo Shop](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/rest-api-marketplace-b2c-demo-shop-reference.html) and [REST API B2B Demo Shop](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/rest-api-b2b-demo-shop-reference.html) endpoints. The schema files we use follow the [OpenAPI specification](https://swagger.io/specification/).
[Sync API](https://github.com/spryker-sdk/sync-api/) is the synchronous API that Spryker supports. In the Spryker terminology, it's also known as [Glue API](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/glue-rest-api.html) with its [REST API B2C Demo Shop](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/rest-api-marketplace-b2c-demo-shop-reference.html) and [REST API B2B Demo Shop](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/rest-api-b2b-demo-shop-reference.html) endpoints. The schema files we use follow the [OpenAPI specification](https://swagger.io/specification/).
Spryker uses schema files to generate code for your project, including predefined test cases. The purpose of doing so is to let you focus on building your business logic without caring about the boilerplate code.

## Code generation
Expand Down
2 changes: 1 addition & 1 deletion ...irtual-machine/configuring-debugging-in-devvm/configuring-debugging-in-devvm.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ Define servers in PhpStorm:
1. In PhpStorm, go to **Preferences** > **Languages & Frameworks** > **PHP** > **Servers**.
2. Add a new server:
1. Select **+**.
2. Enter a **Name**. For example, `zed.mysprykershop.com` (it is used in CLI below).
2. Enter a **Name**. For example, `zed.mysprykershop.com` (it's used in CLI below).
3. For **Host**, enter `~^zed\.de\..+\.local$`.
4. Select **Use path mappings**.
5. For **Absolute path on server**, select `/data/shop/development/current`.
Expand Down
2 changes: 1 addition & 1 deletion ...nfiguring-spryker-with-devvm/configuring-spryker-after-installing-with-devvm.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ We will soon deprecate the DevVM and stop supporting it. Therefore, we highly re

## Configuring Git

If you want to commit from within the VM, it is recommended to set the right Git preferences:
If you want to commit from within the VM, it's recommended to set the right Git preferences:

```bash
git config --global user.email "[email protected]"
Expand Down
12 changes: 6 additions & 6 deletions _drafts/drafts-dev/database-schema-guide/201811.0/catalog-schema.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ Any product can have any Attributes. The data is stored as pairs of keys / value
**Structure:**

* Attributes are identified by the key (e.g. "material").
* The table `spy_product_attribute_key` can contain attribute keys so that it is possible to add metadata
* The table `spy_product_attribute_key` can contain attribute keys so that it's possible to add metadata
* Super-Attributes must be declared here with `is_super=true`.
* **Data for PIM**: On the left side of `spy_product_attribute_key` you see the general attribute meta data that can be attached to the keys. (warning) This meta data is only used for the integrated PIM and does not work for imported data.

Expand Down Expand Up @@ -193,7 +193,7 @@ Structure:
### Measurement Units

{% info_block infoBox %}
Products can be sold in different **Measurement Units**. For instance, apples can be sold in "Item" and "Kilogram" amounts. Each product variant can be sold in one or multiple different units but only one unit is the base one that we use for all internal calculations.
Products can be sold in different **Measurement Units**. For instance, apples can be sold in "Item" and "Kilogram" amounts. Each product variant can be sold in one or multiple different units but only one unit's the base one that we use for all internal calculations.
{% endinfo_block %}
![Measurement units](https://spryker.s3.eu-central-1.amazonaws.com/docs/Developer+Guide/Database+Schema+Guide/Catalog+Schema/measurement-units.png)

Expand All @@ -212,7 +212,7 @@ Products can be sold in different **Measurement Units**. For instance, apples ca
* **Base Unit**

- An Abstract Product can have a Base Unit (otherwise we assume that the product is sold as "Item")
- The Base Unit is used for all internal calculations of prices and stocks (e.g Cables are usually calculated in kilogram).
- The Base Unit's used for all internal calculations of prices and stocks (e.g Cables are usually calculated in kilogram).

* **Sales Unit**

Expand Down Expand Up @@ -253,7 +253,7 @@ Even when the product is marked as splittable, Spryker may still save them into
### Packaging Units

{% info_block infoBox %}
A shop can sell the same product in different Packaging Units, for example, to sell apples, options could be to sell apples as "Item", a "Bag" of apples or a "Pallet" of apples. Each Packaging Unit is represented by one product variant:
A shop can sell the same product in different Packaging Units, for example, to sell apples, options could be to sell apples as "Item", a "Bag" of apples or a "Pallet" of apples. Each Packaging Unit's represented by one product variant:
{% endinfo_block %}
![Packaging units](https://spryker.s3.eu-central-1.amazonaws.com/docs/Developer+Guide/Database+Schema+Guide/Catalog+Schema/packaging-units.png)

Expand All @@ -269,7 +269,7 @@ A packaging unit contains multiple items of a product. For instance, a "Bag of a

**Structure:**

* A Packaging Unit is represented by a Concrete Product
* A Packaging Unit's represented by a Concrete Product
* The Packaging Unit has a type (like "Bag", "Pallet" or "Item) and a fixed or variable amount.

- `spy_product_packaging_unit_amount::default_amount` - E.g. a bag contains 10 apples
Expand Down Expand Up @@ -373,7 +373,7 @@ Spryker ships with several price related features. Here is an overview:
| Merchant Price | The same product is sold by different merchants. Each merchant provides its own price (like at Amazon Marketplace).In B2C Shops the Merchant Prices are usually used for all customers while in B2B scenarios there can be individual Merchant Prices that are only valid for a relationship between a Merchant and some Company Business Units. |
| Custom Amount Price(for Packaging Units) | With packaging units we will introduce a possibility to change the amount. There is always a default amount that is related to the price of the product variant. In case the customer changes another amount then the price is adapted.Example: A bag of 10 apples costs 5.-. The customer changes the amount to 12 apples then he pays 5 * 12/10 = 6.- |
| Price Types | Some products have multiple Price Types. For instance a mobile phone contract has a one-time price, a monthly fee and a working-price per minute. |
| Promotion price(~ former "Strike Price") | A temporal lower price that is shown as a strike price in shop.This can be configured in two ways per company/business-unit: <ul><li> If the promotion price is lower than the price-per-business unit then it will be used (and vice-versa)</li><li>But it is also possible that a price-per-business is fixed and the promotion price is ignored.</li></ul> |
| Promotion price(~ former "Strike Price") | A temporal lower price that is shown as a strike price in shop.This can be configured in two ways per company/business-unit: <ul><li> If the promotion price is lower than the price-per-business unit then it will be used (and vice-versa)</li><li>But it's also possible that a price-per-business is fixed and the promotion price is ignored.</li></ul> |
{% info_block errorBox %}
The Promotional price feature is currently under development.
{% endinfo_block %}
Expand Down
2 changes: 1 addition & 1 deletion _drafts/drafts-dev/database-schema-guide/201811.0/sales-schema.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ It is currently not possible to realize splits with Sales Order Items that have

### Customer Data

The Sales Order contains a copy of the Customer data so that it is not affected if the Customer makes changes.
The Sales Order contains a copy of the Customer data so that it's not affected if the Customer makes changes.
![Customer data](https://spryker.s3.eu-central-1.amazonaws.com/docs/Developer+Guide/Database+Schema+Guide/Sales+Schema/customer-data.png)

**Structure**:
Expand Down
Loading

0 comments on commit 6ea5da7

Please sign in to comment.