# Wrap-up

Review what you built in the Hygraph e-commerce tutorial, explore best practices, and find structured paths to go deeper on schema design, the API, and deployment.

You built a complete, deployed e-commerce website backed by Hygraph. The schema, content, API, storefront, preview configuration, and deployment automation you configured in this tutorial are the same patterns used in production Hygraph projects.

## What you can now do

**Design a content architecture from business goals.**
You started with four store requirements: product listings, categories, landing pages, and reviews, and translated them into a schema of models, components, enumerations, and remote sources. You can apply this planning process to any content-driven project.

**Build a schema in layers.**
You built the schema across four sections: models, references, components, and remote sources, because models are interconnected and some connections can only be made after their dependencies exist. This layered approach applies to any Hygraph project regardless of complexity.

**Use Content Federation to query external data.**
You connected an external REST API to the Hygraph schema using a remote source, added a remote field scoped to individual product entries, and added a top-level remote field that returns external data independently of any content entry. A single API call now returns Hygraph content and external review data together.

**Query and mutate content programmatically.**
You wrote queries for models, references, modular components, and remote fields using the Hygraph API Playground. You created, updated, published, unpublished, and deleted a content entry using mutations. These are the same operations your frontend uses.

**Connect a Next.js frontend to Hygraph.**
You configured Content API permissions, created a PAT for draft content access, connected a Next.js project using environment variables, and confirmed published content renders in the browser.

**Automate deployments on publish.**
You configured a webhook that sends a POST request to your deployment platform whenever a `Product` entry is published, triggering an automatic rebuild without manual intervention.

## Best practices

**Start with business goals, not schema fields.**
The models in this tutorial came from four store requirements, not from a list of fields someone wanted to store. Knowing what the store must do is what determined the schema structure.

**Name models and fields for collaborators, not for yourself.**
API IDs like `productSlug`, `categoryName`, and `businessDescription` are readable by any developer or editor who joins the project later. Ambiguous names like `field1` or `titleText` create friction that compounds over time.

**Build schemas in layers.**
Models are interconnected. Build base models first, then references, then components, then remote fields. Trying to configure everything at once leads to circular dependencies and incomplete field definitions.

**Localize at the schema level, not as an afterthought.**
Deciding which fields need localization at schema design time is cheaper than restructuring later.

## What to build next

Before going deeper on any specific Hygraph feature, consider adding an SEO component to your project. It is something every production project needs.

| Field | Type | Notes |
|---|---|---|
| SEO title | Single line text | Overrides the page title in search results |
| SEO description | Single line text | Appears under the page title in search results |
| SEO image | Asset picker | Cover image for social sharing. Use a named, compressed image with clear alt text. |
| Canonical URL | Slug | Leave blank to default to the page URL. Prevents duplicate content penalties. |

Attach the SEO component to the `Product`, `Landing page`, and `Blog post` models using a basic component field. 

## Continue your learning

### Schema and content modeling

| Resource | What it covers |
|---|---|
| [Content modeling](https://hygraph.com/docs/core-concepts/content-modeling/content-modeling-in-hygraph) | The full theory behind content modeling in Hygraph: models, fields, scalars, and system artifacts |
| [Components](https://hygraph.com/docs/developer-guides/schema/components) | Component types, nested components, copy/paste, the 50-instance UI limit, and querying |
| [Components or references?](https://hygraph.com/docs/developer-guides/schema/components-or-references) | How to decide between a component field and a reference field |
| [References](https://hygraph.com/docs/developer-guides/schema/references) | All reference types, directions, and cardinality options |
| [Enumerations](https://hygraph.com/docs/developer-guides/schema/using-enumerations) | Enumeration configuration and API behavior |
| [Taxonomies](https://hygraph.com/docs/developer-guides/schema/taxonomies) | Hierarchical classification structures and the `descendants_of` filter |
| [Field types](https://hygraph.com/docs/api-reference/schema/field-types) | API reference for all field types, input types, and filter options |
| [Field configuration](https://hygraph.com/docs/developer-guides/schema/field-configuration) | Settings, validations, and advanced options for every field |

### API and content operations

| Resource | What it covers |
|---|---|
| [Queries](https://hygraph.com/docs/api-reference/content-api/queries) | Full query reference: filters, pagination, ordering, and localization |
| [Mutations](https://hygraph.com/docs/api-reference/content-api/mutations) | Full mutation reference: create, update, publish, unpublish, delete |
| [Content stages](https://hygraph.com/docs/api-reference/content-api/content-stages) | Default and custom content stages, and how to use them in workflows |
| [Content localization](https://hygraph.com/docs/api-reference/content-api/localization) | Full localization reference beyond what the tutorial covers |
| [Assets](https://hygraph.com/docs/api-reference/assets/assets-overview) | Asset upload, management, and transformations |
| [Remote Sources](https://hygraph.com/docs/developer-guides/remote-data/overview) | Full reference for remote sources, remote fields, and top-level remote fields |

### Deployment and automation

| Resource | What it covers |
|---|---|
| [Webhooks](https://hygraph.com/docs/developer-guides/webhooks/webhooks-overview) | Webhook configuration, triggers, logs, and retry behavior |
| [Deploy to Vercel with webhooks](https://hygraph.com/docs/developer-guides/webhooks/trigger-builds-with-webhooks) | Step-by-step Vercel deployment automation |
| [Hygraph-Netlify integration](https://hygraph.com/docs/integrations/connect-netlify) | Manual redeploy button and deployment status indicator in the content editor |
| [Workflows](https://hygraph.com/docs/developer-guides/project/content-workflows) | Custom review and approval workflows between DRAFT and PUBLISHED |