> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/content-management-cms/contentful-101/editing-a-product-in-contentful.md).

# Editing a Product in Contentful

### Introduction

Editing a product requires a good understanding of contentful models and best practices. The step-by-step will help you edit a product in your workspace.

###

Workspace

Log in to Contentful and select your **Space.**

The space selector allows you to switch between your different projects' spaces. The main elements are:

* **Organization name:** the organization name to which these spaces belong is located at the top.
* **Space list:** a list of all spaces you’re a member of. Select a space to see its contents. You can also switch between environments. More than likely, you will have a Staging and a Production environment.

The Content page lists all your content entries in that space. This is where you can publish, duplicate, edit, delete, or archive your entries in bulk.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-589058307e5d816ff1bc60569a8f22da66d3b85a%2Fediting-a-product-in-contentful-1.jpg?alt=media)

* **Add entry button:** Adds an entry of a specific content type.
* **Search and filter field:** quickly search for entries by name or filter to specific content types to narrow in on what you see in the list.
* **Save as view button:** Save a view that displays a list of entries you searched for. By saving the current view, you can reuse it later.
* **Content list:** all content is listed here depending on what you filter or search for.
* **Bulk actions** allow you to perform an action to multiple entries simultaneously. The actions displayed depend on the status of the selected entries.
* **Select visible columns button:** customize the columns in the content list to show only what you need.
* **Scheduled content link**: View a list of content that is scheduled to be published.
* **Saved views list:** Allows you to jump to a content list you previously saved quickly. For example, you can view all entries by type of content, status, and any of the pages you usually work with.

In this example, let’s assume we want to update some entries for Product 1.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-69f2e884388454f869a74738082bab3c51574bb8%2Fediting-a-product-in-contentful-2.jpg?alt=media)

Select Content Type = Product and search for Product 1

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-eb1c1830677dad3215163c483fff755400d5847b%2Fediting-a-product-in-contentful-3.gif?alt=media)

Take a look at the main elements of the Content Editor page:

* **Title bar:** displays the current entry's title and its content type (above the title). In our case, Product/**Product 1**
* **Main content area:** edit the contents of that product
* **Actions button:** Where you perform an action for an entry (Publish, Scheduled, Archive, and such...)
* **Status:** see the status of an entry. Currently, in our case, the Status is Published.
* **Tasks:** assign tasks for someone to complete.
* **Preview:** preview an entry on a live or preview site.
* **Links**: See a list of other entries where this entry is used.
* **Translation:** enable languages for an entry, and then add content for that language - useful if you have international Stores
* **Versions:** select a version, compare it with the current version, and revert any necessary changes.

**Change #1**

Let’s make a change to the Product Description

Scroll down to **Long Description**, update that field, and click\*\* Publish.\*\*

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-214c4196b1f2088ee83f1a481cd0efb78cf61046%2Fediting-a-product-in-contentful-4.gif?alt=media)

**Change #2**

Let’s make a change to the price.

To change the price of a given product, you’d have to navigate to the **variant** card - If you want to change all of your Variants, you’d need to repeat the change for them all.

{% hint style="warning" %}
Remember to republish your products when you make a change to a Variant.
{% endhint %}

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-b7f77b31719cfac38c06d4ce98755ff557d30696%2Fediting-a-product-in-contentful-5.gif?alt=media)

Your changes will appear on your site within minutes!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/chord-oms/content-management-cms/contentful-101/editing-a-product-in-contentful.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.