-
Notifications
You must be signed in to change notification settings - Fork 89
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
EDU-14376: Standard Content Types in FastStore projects #1735
Open
mariana-caetano
wants to merge
1
commit into
main
Choose a base branch
from
EDU-14376
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
26 changes: 26 additions & 0 deletions
26
docs/localization/standard-content-types-in-faststore-projects.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: "Standard Content Types in FastStore projects" | ||
createdAt: "2025-02-18T19:02:14.003z" | ||
--- | ||
|
||
Headless CMS [Content Types](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-2-adding-content-types-to-the-headless-cms) are the building blocks for creating a scalable and maintainable storefront in FastStore. After onboarding via the [FastStore WebOps](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview) app, these Content Types are pre-implemented in your starter store, enabling you to quickly build pages like the Home, Product Listing, and Custom Landing. | ||
|
||
Content Types are organized by [Scopes](https://developers.vtex.com/docs/guides/faststore/headless-cms-managing-content-with-scopes-and-requiredscopes#scopes), which define the context in which each Content Type can be used. They categorize Content Types based on their functionality. For example, a Content Type with a `pdp` scope can only be used on PDPs. | ||
|
||
The following table provides an overview of the standard Content Types, their IDs, scopes, and their respective purposes. | ||
|
||
> ℹ These standard Content Types are natively implemented. You can view their structure in the [content-types.json](https://github.com/vtex/faststore/blob/main/packages/core/cms/faststore/content-types.json) file. | ||
|
||
| **Content Type** | **ID** | **Scopes** | **Purpose** | | ||
| ------------------------------- | -------- | --------------- | --------------- | | ||
| Global Sections | `globalSections` | `global` | Defines reusable sections that appear across pages. | | ||
| Global Header Sections | `globalHeaderSections` | `global` | Defines the content for the global header, displayed at the top of every page. | | ||
| Global Footer Sections | `globalFooterSections` | `global` | Defines the content for the global footer, displayed at the bottom of every page. | | ||
| Landing Page | `landingPage` | `landing` and `custom` | Creates custom landing pages with SEO optimization. | | ||
| Home | `home` | `home` | Defines the structure and SEO metadata for the home page. | | ||
| Product Page | `pdp` | `pdp` | Defines the structure and template for Product Detail Pages (PDP). | | ||
| Product List Page | `plp` | `plp` | Defines the structure and settings for Product Listing Pages (PLP). | | ||
| Search Page | `search` | `plp` and `search` | Defines the structure and settings for search results pages. | | ||
| Login | `login` | - | Defines the structure for the login page. | | ||
| Error 500 | `500` | - | Defines the structure for the 500 Internal Server Error page. | | ||
| Error 400 | `400` | - | Defines the structure for the 400 pages, including the 404 Not Found Error page. | |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[style-check] reported by reviewdog 🐶
❌ Found "home page"
Use Style Guide.
💡 Suggestion - Replace with "homepage".