Skip to content

Commit

Permalink
Merge branch 'main' into DEVDOCS-5373
Browse files Browse the repository at this point in the history
  • Loading branch information
Sarah Riehl authored Dec 28, 2023
2 parents 016df23 + e38de6d commit 80f169b
Show file tree
Hide file tree
Showing 185 changed files with 2,043 additions and 1,926 deletions.
46 changes: 46 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <[email protected]>. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
39 changes: 3 additions & 36 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,40 +1,7 @@
# BigCommerce Developer Documentation

This repository contains the markdown files and static assets powering [developer.bigcommerce.com](https://developer.bigcommerce.com/), which includes [API Docs](https://developer.bigcommerce.com/docs), [Theme Docs](https://developer.bigcommerce.com/stencil-docs), and [BigCommerce for WordPress](https://developer.bigcommerce.com/bigcommerce-for-wordpress/overview).
**As of December 27, 2023, you can find all the public BigCommerce DevDocs at [https://github.com/bigcommerce/docs](https://github.com/bigcommerce/docs)!**

This repository is archived and read only. The final commit has been tagged.

Other repositories that contain content that appears on [developer.bigcommerce.com](https://developer.bigcommerce.com/) include [theme-context-object-schemas](https://github.com/bigcommerce/theme-context-object-schemas/) for [Theme Objects](https://developer.bigcommerce.com/theme-objects) and [api-specs](https://github.com/bigcommerce/api-specs) for [API Reference](https://developer.bigcommerce.com/docs/api).

## Contributing

If you're interested in contributing to BigCommerce Developer Documentation, see [CONTRIBUTING.md](CONTRIBUTING.md).

## Directory Structure

```shell
.
├── .github/ # github config
└── workflows/ # workflows to lint pull requests, etc.
├── .notes/ # directory ignored by git - use for yourself
├── assets/
├── csv/ # static files used in docs
├── images/ # images and screenshots
├── json/ # theme translation files
└── PO/
├── docs # narrative documentation
├── api-docs/
├── bigcommerce-for-wordpress/
├── legacy/ # Blueprint and V2 API docs
├── msf/ # MSF docs
├── partner-apps/ # docs for some partner integrations
└── stencil-docs/ # theme docs
├── .eslintrc.json # config for MDX linter
├── .gitignore # gitignore
├── .nojekyll
├── .spelling
├── CONTRIBUTING # guidelines for contribution
├── package-lock.json
├── package.json
├── pull_request_template.md # template for most pull requests
└── README.
```
This consolidation lets the BigCommerce DX team offer a more streamlined developer experience. We look forward to seeing your [issues](https://github.com/bigcommerce/docs/issues), [discussions](https://github.com/bigcommerce/docs/discussions), and [pull requests](https://github.com/bigcommerce/docs/pulls) at [bigcommerce/docs](https://github.com/bigcommerce/docs)!
10 changes: 5 additions & 5 deletions docs/api-docs/analytics/bodl-for-storefronts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ This guide illustrates the basics of using BODL data in your integration. This a

For scripts to successfully use BODL to access storefront data, the following must be true:

- Enable BODL on the subject storefront using the control panel or the [GraphQL Admin API's Enable data layer mutation](/api-docs/store-management/graphql/data-layer#enable-data-layer)
- Enable BODL on the subject storefront using the control panel or the [GraphQL Admin API's Enable data layer mutation](/docs/store-operations/settings/data#enable-data-layer)
- The storefront must use a stencil theme
- If a merchant enables cookie tracking consent on the subject storefront, the shopper must consent to the [appropriate category](#category-of-consent)

Expand Down Expand Up @@ -65,8 +65,8 @@ When the shopper clicks a button to view the category page for a product, the fo

| Event field | Type | Description | BigCommerce data map |
|:---|:---|:---|:---|
| `category_id` | integer | ID of the category. | [Get all categories](/docs/rest-management/catalog/category#get-all-categories) <br /> `data.id` |
| `category_name` | string | Name of the category. | [Get all categories](/docs/rest-management/catalog/category#get-all-categories) <br /> `data.name` |
| `category_id` | integer | ID of the category. | [Get all categories](/docs/rest-catalog/categories#get-all-categories) <br /> `data.id` |
| `category_name` | string | Name of the category. | [Get all categories](/docs/rest-catalog/categories#get-all-categories) <br /> `data.name` |
| `channel_id` | integer | The BigCommerce channel ID. Channel ID of the channel where checkout is taking place. | [Get all channels](/docs/rest-management/channels#get-all-channels) <br /> `data.id` |
| `event_id` | string | Unique ID for each event instance. | Unique event ID generated by BigCommerce. |
| `line_items[]` | array of `line_item` objects | Items in the category. | See [line_item](#line_item-object-schema) object for event fields |
Expand Down Expand Up @@ -385,7 +385,7 @@ If a merchant enables cookie tracking consent, the shopper must provide consent

### Scripts API example

The following is an example request that uses the Scripts API to associate the example script with pages on a storefront. Send a request to the [Create a script](/docs/rest-management/scripts#create-a-script) endpoint. For more, see the [Scripts API article](/api-docs/store-management/scripts).
The following is an example request that uses the Scripts API to associate the example script with pages on a storefront. Send a request to the [Create a script](/docs/rest-management/scripts#create-a-script) endpoint. For more, see the [Scripts API article](/docs/integrations/scripts).

```http filename="Example request: Create a Script" showLineNumbers copy
POST https://api.bigcommerce.com/stores/{{STORE_HASH}}/v3/content/scripts
Expand All @@ -409,6 +409,6 @@ Accept: application/json

## Resources

- [Scripts API article](/api-docs/store-management/scripts)
- [Scripts API article](/docs/integrations/scripts)
- [Scripts API reference](/docs/rest-management/scripts#create-a-script)
- [Scripts Manager support article](https://support.bigcommerce.com/s/article/Using-Script-Manager)
12 changes: 6 additions & 6 deletions docs/api-docs/analytics/data-layer-api.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,19 @@ keywords: GA4, ga4, data, graphql, admin, google analytics 4,

# Data Layer Settings in the GraphQL Admin API

The GraphQL Admin API's data layer setting allows BigCommerce to send data from BigCommerce-hosted storefronts to third-party analytics providers through [Big Open Data Layer](/api-docs/partner/analytics-solutions/bodl). Bigcommerce can build native integrations to analytics providers, such as Google Analytics 4, using the data layer. Partners may also build their own integrations using the data layer. In each case, you must first enable the data layer using the GraphQL Admin API. The data layer is enabled at the global level.
The GraphQL Admin API's data layer setting allows BigCommerce to send data from BigCommerce-hosted storefronts to third-party analytics providers through [Big Open Data Layer](/docs/integrations/hosted-analytics). Bigcommerce can build native integrations to analytics providers, such as Google Analytics 4, using the data layer. Partners may also build their own integrations using the data layer. In each case, you must first enable the data layer using the GraphQL Admin API. The data layer is enabled at the global level.

This guide shows you how to use the GraphQL Admin API's data layer queries and mutations. For full schema, see the [GraphQL Admin API reference](/graphql-admin-reference).
This guide shows you how to use the GraphQL Admin API's data layer queries and mutations. For full schema, see the [GraphQL Admin API reference](/graphql-admin/reference).

## Prerequisites

You need a [store-level API account](/api-docs/getting-started/api-accounts#store-level-api-accounts) that contains the following [OAuth scopes](/api-docs/getting-started/api-accounts#oauth-scopes):
You need a [store-level API account](/docs/start/authentication/api-accounts#store-level-api-accounts) that contains the following [OAuth scopes](/docs/start/authentication/api-accounts#oauth-scopes):

| UI Name | Permission | Parameter | Description |
|:--------|:-----------|:----------|:------------|
| Information & Settings | modify | `store_v2_information` | View and modify store information and settings |

For more about API accounts that generate `access_token`s, see [API Accounts and OAuth Scopes](/api-docs/getting-started/authentication/rest-api-authentication).
For more about API accounts that generate `access_token`s, see [API Accounts and OAuth Scopes](/docs/start/authentication).

## Get data layer

Expand Down Expand Up @@ -157,5 +157,5 @@ Send the following mutation to disable the data layer in the store:
</Tabs>

## Resources
- [GraphQL Admin API reference](/graphql-admin-reference)
- [Big Open Data Layer](/api-docs/partner/analytics-solutions/bodl)
- [GraphQL Admin API reference](/graphql-admin/reference)
- [Big Open Data Layer](/docs/integrations/hosted-analytics)
8 changes: 4 additions & 4 deletions docs/api-docs/apps/apps-id.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@



Select partners [building channel apps](/api-docs/channels/guide/building-channel-apps) need to know their app's ID in order to create and modify the channel's configuration. This tutorial demonstrates how to find an app's ID in the [Developer Portal](#find-in-developer-portal) and the [control panel](#find-in-control-panel).
Select partners [building channel apps](/docs/integrations/channels/guide) need to know their app's ID in order to create and modify the channel's configuration. This tutorial demonstrates how to find an app's ID in the [Developer Portal](#find-in-developer-portal) and the [control panel](#find-in-control-panel).



Expand Down Expand Up @@ -63,6 +63,6 @@ Accept: application/json
```

## Resources
* [Building Apps Guide](/api-docs/getting-started/building-apps-bigcommerce/building-apps)
* [Building Channel Apps](/api-docs/channels/guide/building-channel-apps)
* [Extending Existing Apps with Channels Toolkit](/api-docs/channels/extending-existing-apps)
* [Building Apps Guide](/docs/integrations/apps)
* [Building Channel Apps](/docs/integrations/channels/guide)
* [Extending Existing Apps with Channels Toolkit](/docs/integrations/channels/guide/extending-existing-apps)
20 changes: 10 additions & 10 deletions docs/api-docs/apps/apps-quick-start.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@ keywords: apps, app extensions, configuration, environment variables, env vars,

# BigCommerce Apps Quick Start

In this quick start tutorial, you will create a [single-click app](/api-docs/getting-started/building-apps-bigcommerce/types-of-apps) using [Node.js](https://nodejs.org/en/), [React](https://www.reactjs.org/), [Next.js](https://nextjs.org/), and [BigDesign](https://developer.bigcommerce.com/big-design).
In this quick start tutorial, you will create a [single-click app](/docs/integrations/apps/guide/types) using [Node.js](https://nodejs.org/en/), [React](https://www.reactjs.org/), [Next.js](https://nextjs.org/), and [BigDesign](https://developer.bigcommerce.com/big-design).

## Prerequisites

To successfully complete this tutorial, you will need the following:

* [BigCommerce sandbox store](/api-docs/partner/getting-started/create-a-sandbox-store) (required to develop and test apps)
* [BigCommerce sandbox store](/docs/start/about/sandboxes) (required to develop and test apps)
* [Developer Portal Account](https://devtools.bigcommerce.com/) (required to register apps)
* Experience using [npm](https://www.npmjs.com/)
* The most recent LTS version of Node.js and its highest corresponding npm version
Expand Down Expand Up @@ -53,7 +53,7 @@ Next, create a draft app profile in the [Developer Portal](https://devtools.bigc
6. Enter the **Load Callback URL** as `https://{ngrok_url}/api/load{:http}`.
7. Enter the **Uninstall Callback URL** as `https://{ngrok_url}/api/uninstall{:http}`.
8. If your app supports multiple users, locate the **App Features** section. Select **Multiple Users**, then enter the **Remove User Callback URL** as `https://{ngrok_url}/api/remove_user{:http}`.
9. Because you will be using the API to modify the store's products, set the Products OAuth scope to `modify`. To learn more about the available OAuth scopes, see [OAuth scopes](/api-docs/getting-started/api-accounts#oauth-scopes).
9. Because you will be using the API to modify the store's products, set the Products OAuth scope to `modify`. To learn more about the available OAuth scopes, see [OAuth scopes](/docs/start/authentication/api-accounts#oauth-scopes).
10. Click **Update & Close**.
11. Click **View Client ID** to view this app's client ID and client secret, or _app-level API account_.

Expand Down Expand Up @@ -156,18 +156,18 @@ Congrats! You've created and installed a BigCommerce draft app.

<Callout type="info">
#### Becoming a partner
Interested in sharing or selling your app? Learn more about [becoming a BigCommerce partner](https://www.bigcommerce.com/partners/become-a-partner) and [getting your app approved](/api-docs/partner/app-store-approval-requirements).
Interested in sharing or selling your app? Learn more about [becoming a BigCommerce partner](https://www.bigcommerce.com/partners/become-a-partner) and [getting your app approved](/docs/integrations/apps/guide/requirements).
</Callout>


## Next steps
* [Learn more about building apps](/api-docs/getting-started/building-apps-bigcommerce/building-apps)
* [Learn more about building apps](/docs/integrations/apps)
* [Apply to become a BigCommerce partner](https://www.bigcommerce.com/partners/become-a-partner)
* [Check out the BC App Marketplace approval requirements](/api-docs/partner/app-store-approval-requirements)
* [Check out the BC App Marketplace approval requirements](/docs/integrations/apps/guide/requirements)

## Resources
* [BC App Marketplace](https://www.bigcommerce.com/apps/)
* [Guide to API Accounts](/api-docs/getting-started/api-accounts)
* [Testing locally with ngrok](/api-docs/apps/guide/development#testing-locally-with-ngrok)
* [Types of apps](/api-docs/getting-started/building-apps-bigcommerce/types-of-apps)
* [Becoming a partner](/api-docs/partner/becoming-a-partner)
* [Guide to API Accounts](/docs/start/authentication/api-accounts)
* [Testing locally with ngrok](/docs/integrations/apps/guide#testing-locally-with-ngrok)
* [Types of apps](/docs/integrations/apps/guide/types)
* [Becoming a partner](/docs/start/partner)
Loading

0 comments on commit 80f169b

Please sign in to comment.