{"section":"tracks","requestedLocale":"en","requestedSlug":"legacy-cms-portal","locale":"en","slug":"legacy-cms-portal","path":"docs/en/tracks/vtex-modules-getting-started/cms/legacy-cms-portal.md","branch":"main","content":"The CMS Portal (Legacy) was the first Content Management System (CMS) on VTEX and is no longer available for new accounts. If you're using the CMS Portal (Legacy), you can continue accessing and managing your store content using this guide.\n\nFor new features and modern resources, consider migrating to one of our latest CMS solutions: **[CMS](https://developers.vtex.com/docs/guides/cms-for-faststore-storefronts)**, the recommended CMS solution for stores developed with [FastStore](https://developers.vtex.com/docs/guides/faststore), or **[Site Editor](https://help.vtex.com/docs/tutorials/site-editor-overview)**, the CMS solution for stores developed with [Store Framework](https://developers.vtex.com/docs/guides/store-framework).\n\nIn this guide, you'll learn how to use the CMS Portal (Legacy) to manage your store content, including creating and organizing layouts, configuring pages and folder structures, and getting familiar with VTEX native controls available for templates.\n\n## Layout\n\nThe [Layout](https://help.vtex.com/docs/tutorials/layout-subcategory) section allows you to build your storefront with HTML and CSS.\n\n![CMS - Layout PT](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/pt/tracks/módulos-vtex-primeiros-passos/cms/cms-portal-legado_1.png)\n\nThis section is organized into folders and files with the following functions:\n\n- **HTML Templates:** Build the HTML code and reference JavaScript and CSS files to be used in the website pages.\n\n- **Shelves Templates:** Manage [shelves](/en/docs/tutorials/what-are-shelves) [templates](https://help.vtex.com/docs/tutorials/what-are-templates) — the components that render a group of products on the storefront.\n\n- **Custom Elements:** Create the necessary conditions to implement reusable components, such as footers, in other areas of the store.\n\n- **URL Builder:** Redirect existing URLs to others of interest. This will avoid indexing errors and help maintain SEO rankings.\n\n- **Files Manager:** Upload image files for your store website. Store JavaScript, CSS, and image files of the website. If you want to use any of these files in your store, you must reference them within the **HTML Templates** section.\n\n- **Product Cluster (Collections):** Create product groups. You can use them to build Campaign or Product Collection landing pages that load specific product clusters.\n\n- **Sites and Channels:** Configure [your store's binding](/pt/docs/tutorials/o-que-e-binding) and other License Manager settings. To learn more, see the [CMS folder structure](/https://help.vtex.com/docs/tutorials/cms-folder-structure) article.\n\n## CMS Portal (Legacy) folder structure\n\nOn VTEX, every new account comes with preinstalled folders in the CMS. Some of these folders are **required**.\n\nTo ensure proper navigation and indexing, every store must have the following folders in the CMS:\n\n- Search\n- Category\n- Departament\n- Login\n- Product\n\n![2 1](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/pt/tracks/módulos-vtex-primeiros-passos/cms/cms-portal-legado_3.png)\n\n> ⚠️ **Don't change** the names of the required folders. If these folders aren't named exactly as specified above, you'll encounter navigation and indexing issues. Because these folders refer to dynamic pages, their names don't appear in the customer's navigation or in the final URL paths, so they **don't affect the site's internationalization**. On the other hand, the names of **[layouts](https://help.vtex.com/docs/tutorials/what-are-layouts) within these folders** can be freely edited without affecting store functionality.\n\nThe other folders aren't required. These are only suggestions, as they’re important and useful for most stores. Therefore, we recommend that you don’t delete them. They are as follows:\n\n- `/account`: Customer account\n- `/account/orders`: Customer orders\n- `/system/emptrysearch`: Folder the user is directed to if the search returns no results.\n- `/system/{codigoHTTP}`: Folder that renders error pages according to HTTP status codes, like 404 (page not found), 401 (unauthorized), and 500 (server error).\n- `/brands`: Folder containing brand page layouts, which can be customized with an exclusive layout. If no specific layout is available for brands, these pages will be rendered using the same layout as the search folder. To understand how brand pages work, see the article [How VTEX search works](https://help.vtex.com/docs/tutorials/how-does-vtex-search-legacy-work).\n\nSince these folders aren't required, you can rename them as you see fit. In these cases, what matters is the [control](https://developers.vtex.com/docs/guides/list-of-controls-for-templates) or the [placeholder](https://help.vtex.com/docs/tutorials/managing-placeholders) reading their contents.\n\n## VTEX native controls\n\nIn the CMS Portal (Legacy), [controls](https://help.vtex.com/docs/tutorials/what-are-controls) are markers that you include in **HTML templates** to display dynamic store data. For example, they can display the product name and price, a search box, or a breadcrumb, without requiring you to reimplement this logic on every page.\n\nVTEX provides **native controls**. When you publish the template, the platform recognizes each control and renders the corresponding content or functionality in the storefront.\n\nFor example, by using the `<vtex.cmc:productName/>` control on a product page, the system will display the product name on the page.\n\nTo use a control, include the tag in the desired location within the template's HTML. What the control generates appears exactly in this position in the published layout.\n\n> ℹ️ In the [list of controls for templates](https://developers.vtex.com/docs/guides/list-of-controls-for-templates), you can find all native controls and their respective uses.\n\n## Learn more\n\n- **[Creating and editing a page template](https://help.vtex.com/docs/tutorials/how-to-create-a-page-template):** Learn how to create a page template. A page template is a model created to define an HTML structure for presenting page content.\n\n- **[Associating a template with a layout](https://help.vtex.com/docs/tutorials/associating-a-template-with-a-layout):** Associate a template with a layout using the Sites and Channels folder.\n\n- **[What is the purpose of the Customized Control?](https://help.vtex.com/docs/tutorials/what-is-the-purpose-of-the-customized-control):** Besides VTEX native controls, you can create your own controls.\n\n- **[Storefront Settings - Storefront](https://help.vtex.com/docs/tutorials/store-settings---storefront-subcategory):** Set general definitions for your storefront, like metadata, SEO tags, file types, image dimensions, and regional settings to determine where your products will be available."}