From f390467b752debba4ddb41170238f7498e46454c Mon Sep 17 00:00:00 2001 From: George Lima Date: Thu, 9 Jan 2025 11:10:32 -0300 Subject: [PATCH] Remove file uploaded to wrong folder --- docs/en/grammar/product-and-feature-naming.md | 212 ------------------ ...duct-and-feature-naming.md:Zone.Identifier | 4 - 2 files changed, 216 deletions(-) delete mode 100644 docs/en/grammar/product-and-feature-naming.md delete mode 100644 docs/en/grammar/product-and-feature-naming.md:Zone.Identifier diff --git a/docs/en/grammar/product-and-feature-naming.md b/docs/en/grammar/product-and-feature-naming.md deleted file mode 100644 index 4c83b2cb3..000000000 --- a/docs/en/grammar/product-and-feature-naming.md +++ /dev/null @@ -1,212 +0,0 @@ ---- -title: 'Product and feature naming' -id: guides0001 -status: PUBLISHED -createdAt: 2025-01-09T19:24:22.388Z -updatedAt: 2025-01-09T19:24:22.388Z -publishedAt: 2025-01-09T19:24:22.388Z -firstPublishedAt: 2025-01-09T19:24:22.388Z -contentType: trackArticle -productTeam: Localization -slugEN: product-and-feature-naming -locale: en -trackId: 5PxyAgZrtiYlaYZBTlhJ2A -trackSlugEN: product-and-feature-naming ---- - -## Objective - -Establish a clear, consistent, and meaningful naming strategy for VTEX products, features, and projects to enhance brand identity, customer understanding, and market positioning. This strategy aims to ensure that names are descriptive, practical, and aligned with industry standards, making them easy to spell, pronounce, and remember. - -By implementing these guidelines, VTEX will create a cohesive naming convention that facilitates communication, supports marketing efforts, and strengthens the overall VTEX brand in the global marketplace. - -Why have a naming process? - -**Consistency:** Ensures all names align with the [brand's identity and values](https://brand.vtex.com/), creating a unified image. - -**Clarity:** Helps customers easily understand what each product, feature, or module does, reducing confusion. - -**Professionalism:** Demonstrates a well-organized and thoughtful approach, enhancing the company's reputation. - -**Market Positioning:** Differentiates VTEX products from competitors and clearly communicates their unique value. - -**Global Relevance:** Ensures names are appropriate and understandable across different languages and cultures. - -**Efficiency:** Streamlines the naming process, saving time and resources by providing clear guidelines and reducing the need for ad-hoc decisions. - -**Marketing and SEO:** Improves searchability and marketing effectiveness by using names that are easy to find and understand online. - -When does this process apply? - -* Launching new products; -* Developing features and modules; -* Updating existing names; -* Adapting names for different regions and languages. - -When to run the naming process? - -**The sooner, the better.** Ideally, run this process at least 2 months before rolling out to closed beta. - -### General guidelines - -Names must be: - -**Meaningful:** Conveys relevant meaning and fits within the industry; use terms that are commonly used and easily recognizable by merchants. - -**Unique:** Differentiates from competitors and is not too generic. - -**Memorable:** Easy to remember and recognize. - -**Easy to Spell:** Should be spelled as it is pronounced. - -**Easy to Pronounce:** Should be pronounced as it is spelled. - -**Brief:** Limited to one or two words, max of three, or a compound word. - -**Weighty:** Conveys strength and importance. - -**Global Relevance:** Ensure names are easy to understand in different languages and cultures. - -**SEO Friendly:** Names should be searchable and rankable. - -**Word Choice:** Opt for words with positive connotations and impact to ensure memorable and engaging names. - -Specific guidelines - -**Versioning and Updates:** Use [semantic versioning](https://www.notion.so/vtexhandbook/POC-MVP-Alpha-Beta-what-and-when-do-we-communicate-things-6eee838febdd48feb0d60d00b9173ffa) for updates to existing features rather than renaming them. Add “(Beta)” for test pages and “(Legacy)” for outdated systems. - -**Translations:** We use different translation strategies for products, modules, and features to ensure brand consistency and recognition across all markets. - -**Products:** Keep in English. - -* Examples: Sales App, Live Shopping, FastStore. - **VTEX Admin Modules:** Translated. -* Examples: Overview / Visão geral, Shipping / Envio, Orders / Pedidos - **Permission Roles:** Not translated. -* Examples: Owner (Admin Super), VTEX IO Admin. - **Features:** Translated. -* Example: Operational capacity / Capacidade operacional. - **Apps:** Some are translated, some are not. -* Examples: Wishlist / Lista de desejos, Customer Credit. - -**Capitalization:** Capitalization rules differ by language. Use title case for titles in English, and sentence case in Portuguese and Spanish. For more details, see our [style guides](https://language.vtex.com/content/style_guides.html) or contact the Localization team. - -**Character Limit:** - -* Modules \- 18 characters -* Sections \- 16 characters -* Subsections \- 21 characters - - -What to avoid - -* Don’t use verbs. For example, use “Available Sellers” instead of “Find Sellers.” -* Don’t use punctuation. -* Don’t use personal pronouns. -* Avoid redundancy or repeat unnecessary terms. Example: avoid repeating the section title, such as when using the words *Management* or *List*. - -* Avoid using abbreviations unless they are widely recognized and understood, such as “B2B” or “SKU.” - -Naming examples - -**VTEX Product Names** (examples)**:** - -* VTEX Commerce Platform -* VTEX IO Development Platform -* VTEX Live Shopping -* VTEX Tracking -* VTEX Shipping Network - -**VTEX Module Names** (examples)**:** - -* VTEX Marketplace -* VTEX OMS (order management system) -* VTEX Intelligent Search -* VTEX CMS (content management system) -* VTEX IO Store Framework -* VTEX IO FastStore -* VTEX IO WebOps -* VTEX IO App Platform - -**VTEX Feature Names** (examples)**:** - -* VTEX Promotions -* VTEX Catalog -* VTEX Master Data -* VTEX Sales Dashboard - - -### Streamlined process for simpler features - -1. Fill a workflow - * Fill out the product-naming workflow in the \#terminology Slack group to ensure all relevant teams are informed, aligned, and participating in the naming process. - 1. Key drivers/contributors: PMs, Designers. -2. Necessity check: - * Determine if a new name is truly necessary. Evaluate if an existing name can be adapted or if the new feature/module/product can fit under an existing naming convention. - 1. Key drivers/contributors: PMs or Designers (when creating the request), Localization (when analyzing the task to proceed to step 3). -3. Generate name ideas: - * Analyze how competitors name similar products and features; - * Create a short list of possible names; - * Check for alignment with VTEX’s strategy and brand guidelines - 1. Key drivers/contributors: PMs or Designers (when creating the request), Localization (when doing the brainstorm for naming suggestions). -4. Team discussion: - * Validate names with the requester, and the Localization and Product Marketing teams to ensure they are suitable across different languages and markets; - * Collect internal feedback and refine the list based on input. This can be done publicly in the thread opened on the terminology channel so everyone interested can contribute. - 1. Key drivers/contributors: Localization, PMs, PMMs, Designers, and anyone else who contributed to the discussion in the thread. -5. Implementation: - * Review the feedback and decide the name that best fits the criteria; - * Once there’s a final decision, make it clear on the request thread; - * Socialize it with relevant stakeholders; - * Ensure all marketing materials, product documentation, and internal communications use the new name consistently. - 1. Key drivers/contributors: Localization, Education, PMs and PMMs. - - Comprehensive process for big product launches - -1. Fill a workflow - * Fill out the product-naming workflow in the \#terminology Slack group to ensure all relevant teams are informed, aligned, and participating in the naming process. - 1. Key drivers/contributors: PMs, Designers -2. Necessity check: - * Determine if a new name is truly necessary. Evaluate if an existing name can be adapted or if the new feature/module/product can fit under an existing naming convention. - 1. Key drivers/contributors: PMs, working collaboratively to determine the necessity of a new name and evaluate existing naming conventions. -3. Research and validation: - * Begin [documenting](https://docs.google.com/document/d/1cBrYkQuUQAg-FFxCL6-HQIS90rw6PUhEZbXolp4CWB8/edit?usp=sharing) the step-by-step process for defining the name; - * Analyze how competitors name similar products and features; - * Check if customer interviews have been conducted for insights on how they refer to the feature or product. If not, consider conducting one. - 1. Key drivers/contributors: PMMs, PMs and Product Designers - 1. PMM: Begin documenting, lead competitor analysis and provide market insights relevant to naming; - 2. PM and PD: Ensure customer interviews are conducted and identify gaps for additional insights -4. Generate name ideas: - * Create an exhaustive list of potential names; - * Evaluate each name against the guidelines (meaningful, unique, memorable, etc.); - * Conduct a comprehensive trademark search to ensure the proposed name isn’t already in use or registered by another entity; - * Ensure the names align with VTEX’s overall company strategy, product portfolio, and brand architecture. - 1. Key drivers/contributors: PMs, PMMs, Education and Localization - 1. PM & PMM: Generate an exhaustive list of potential names. - 2. PMM: Conduct a comprehensive trademark search. - 3. Education and Localization: Provide feedback on name clarity and cultural appropriateness. -5. Team discussion: - * Validate names with localization and product marketing teams to ensure they are suitable across different languages and markets; - * Collect feedback and refine the list based on input. - 1. Key drivers/contributors: Localization, PMMs and PM - 1. Localization: Validate names for suitability across different languages and markets. - 2. PMM & PM: Refine the name list based on feedback. -6. Testing: - * Consider testing a shortlist of names with sponsor clients, friendly customers, related internal teams, and business partners; - * Document responses, likes, and dislikes to gather insights. - 1. Key drivers/contributors: PMMs and Product Designers - 1. PMMs & PD: Test a shortlist of names with sponsor clients, friendly customers, related internal teams, and business partners and gather insights. -7. Final decision: - * Review the feedback and finalize the name that best fits the criteria; - * Validate the chosen name with [Alexandre Gusmão](mailto:alexandre.gusmao@vtex.com) and [Natalia Costa](mailto:natalia.costa@vtex.com). - 1. Key drivers/contributors: PMs and PMMs collaborate in finalizing the name that best fits the criteria, and validate it with Leadership. -8. Implementation: - * Complete the step-by-step process [document](https://docs.google.com/document/d/1cBrYkQuUQAg-FFxCL6-HQIS90rw6PUhEZbXolp4CWB8/edit?usp=sharing) and communicate the chosen name; - * Socialize it with stakeholders in product, marketing, sales, solution engineering, and customer success; - * Ensure all marketing materials, product documentation, and internal communications use the new name consistently. - 1. Key drivers/contributors: PMMs, PMs, Education, and Localization - 1. PMMs: Complete the step-by-step process document, communicate the chosen name; - 2. PMMs, PMs, Education, and Localization: Collaborate on socializing the name as well as ensure the consistency usage of it. - -### Seek assistance if needed - -If doubts persist after following the process, consult with the Product Marketing team for additional guidance and final decision-making support. diff --git a/docs/en/grammar/product-and-feature-naming.md:Zone.Identifier b/docs/en/grammar/product-and-feature-naming.md:Zone.Identifier deleted file mode 100644 index 8c3e15a69..000000000 --- a/docs/en/grammar/product-and-feature-naming.md:Zone.Identifier +++ /dev/null @@ -1,4 +0,0 @@ -[ZoneTransfer] -ZoneId=3 -ReferrerUrl=https://docs.google.com/ -HostUrl=https://doc-0k-1g-docstext.googleusercontent.com/export/07lh14jjvfegduiuiroq22i3fg/jq590nplbm8g5aedltfeifjpho/1736421200000/105250506097979753968/106188387448324179856/11N3DbuAqClDznAS2aW97DOZCubV0muGcTMRXFVx-WuA?format=md&id=11N3DbuAqClDznAS2aW97DOZCubV0muGcTMRXFVx-WuA&token=AC4w5Vgp0rR8hDRhPE4ftwxkCq8TtvV5Tg:1736421140665&includes_info_params=true&cros_files=false&tab=t.0&inspectorResult=%7B%22pc%22:7,%22lplc%22:58%7D&dat=AOBvIb1zCVR758zIISPamWaMZiD93yubP3onkjq0hvan805RUsgVyopVH8dy4UoyWsGoqhXkyYCoUPOkSRZky_Yu1VEndP4HiXIeqKWaFlCX3gzeuBNRmNsUzjCENMH-xAHuDtCtJ14bgDroATYhJ_bpc0dcyAIVmJGKDHuTcTSmhqyHvYB_34qXqQ_b2P6XnO-W_U3t1eX59Zsu1mYbpl7Clc5N2ceAJQaKRuPAmHdz1UmB_En4Ohh7fAq_Nm3suZWohDwv1moPp_kAEHxCfPWZ6Kds2pYaDTRvZKEeprnJOYBvEMwRVB_Y1pUKyHFNdWdIDe5Mo5y7CNEsWvB9e5VRuDQyVzSPi6EtyjZDtgk0KCK5bj6CAevrSpU-753nbb9tq9z7AHJUMZ1k5wlkbGL2nPvlZcR61ar5B3q0zY7huNlhhkOsa0VsgmIFssydfnPrY01hvg6-J4dIq9C0Q0BnaxjXSYuNGrpAP3ssbZq0TJv38hi98l6MaouEK1R0rPvHPdHDb4llZyV6cj_DQ1oWSTW7F82mQXaO3JSMwVckCA_lGmO_9BBs8lGS8UOyY1n8JDpDogP6dLiSpqUqecujJA-Sqa6ix31GsP2unm8Mmnx3-c_0Kav-t9s8-5UTD0aNNm6_qdif7PjrHeg_kXR4nbFgnkRNANal_OjS6nMf31PfrMnW_Gi_27A1by8GSKEXh25H7-Vn8ZCIc3NqWuRooM53tnKmmRP4O-LTJSDPkGR1OxMQEjuuaLGm1Gko-Dk4HtDTfej7lXFLIWgfMzCkQEcifWXEXJ-dcqV5eRv6HtoMgOt8fwIfnPslOG3R5WULfhffu9WetAkEPwSPKM6AShOBx58AdtrYFeKEldMp0cBgpV0UjzrWJ-5ayCRF6lcAFbe3s1F6eYaF6Nfjgh1W-bleUp-_G7xf3VY4dHTBiXFCdfHcC2VjqRf5hWAaz2NH8h3-wAjNRhHFzbD_xKGB0DZQIa7iDg