[bruno-andrade-azion]

What & why

Related issue: MM-16248 · Epic MM-16212
Pages affected: /en/documentation/style-guide/writing/procedures/ and /pt-br/documentacao/guia-de-estilo/escrita/procedimentos/; About Azion Console (en and pt-br); about 150 page pairs with a Console procedure; the migration-guide partials in src/includes/migration-guides/; and the three API version notices in src/includes/snippets/, which render on about 50 pages.

The convention. The style guide now sets one form for Azion Console click paths, in en and pt-br. The path names only what the reader selects: Access [Azion Console](https://console.azion.com/) > **<menu item>**. It leaves out the menu, because the Console gives it no label and there is no "Products menu", and it leaves out the menu sections (Build, Secure, Edge Libraries…), because the section an item sits in changes with the account type and the item label does not. Account pages use … and, in the account menu, select **<entry>**, and a later step uses Go to **<item>**. The menu labels were checked against the Console's public bundle: the menu items are Firewalls, WAF Rules, and Custom Pages; the account menu holds Account Settings, Variables, Personal Token, and Activity History; the sections are headings with no link.

Applying it. The convention is applied in en and pt-br in step. This covers the Products menu chains, the section prefixes, the "three horizontal lines, upper-left corner" sentences, separate sign-in steps merged into the first step, **Firewall** → **Firewalls**, **Account** > **Personal Token** → the account-menu form, chains moved out of <DocStep> titles, and the Console link always set to https://console.azion.com/. The three API version notices now say "the Azion Console menu" instead of Products menu.

About Azion Console matches the current Console menu: the Store section, Connectors, Custom Pages, Firewalls, and the Copilot header button. Variables moved to the account menu. The section is now called "Console menu", the prose name the style guide sets.

Rebased on main. The branch was rebased on af6a3697c. The five migration guides now share their procedures as partials (#2619), so the convention is applied to the partials (waf-console, rate-limit-console, env-vars-console, certificate-console, en and pt-br) instead of the guide pages. The create-certificate pair was deleted on main (#2593) and stays deleted. The pt-br origins.mdx now says conteúdo ou aplicação, as #2621 left that line to this PR.

Left as is on purpose:

• Domains: some accounts show it in place of Workloads, and the v3 pages document it.
• Edge Nodes and Edge Services: they are Console labels quoted in a click path.
• The Real-Time Metrics dashboard tabs (**Build** > **Applications** > **Data Transferred**), because those are tabs inside the page, not menu sections.
• Release notes and changelog, which are append-only.
• The pages that docs(secure): retire the pre-Workloads security journey and guide pages #2586 and docs(platform): retire the v3 build and deploy journey pages #2587 retire. They still carry old paths, which go away with them.
• The legacy template guides, which MM-16246 is migrating.

How it was checked:

• A search for these old forms (Products menu, section prefixes, "three horizontal lines", a Console step linking to a docs page, Go to [Azion Console], Acesse o [Azion Console], **Account** menu, the Console link without its trailing slash) over src/content/docs, src/includes/migration-guides, and src/includes/snippets returns only the style guide's own Incorrect example, the release notes, the Real-Time Metrics tabs, and the pages being retired.
• The build-free link check returns the same 115 broken links as main, so this PR adds none.
• The new style-guide section parses as two lists of two items each, in en and pt-br.
• The docs write-time gate reports no new findings on the files edited during the rebase.
• Not run: pnpm build:local.

Open items, not fixed here:

• The Feedback button that About Azion Console describes is not in the current header. Its location needs confirming.
• pt-br trabalhar-com-variaveis.mdx L162 has 7.Clique with no space, so the line does not render as a list item.

Type of change

• 🆕 New content (feat)
• 🩹 Fix (fix) — typo, broken link, wrong information
• ♻️ Content update (docs) — rewrite, expansion, upkeep
• 🌐 Translation sync (i18n)
• 🏗️ Platform / structure (refactor / chore) — reviewed by UXE, no content mixed in

Author checklist

• PR title follows type(scope): summary (see GOVERNANCE.md §4)
• Frontmatter complete: title, description, meta_tags, namespace, permalink, last_reviewed — no frontmatter field is added or removed; last_reviewed is on no page in the corpus
• No legacy "edge-" product names in the copy — the Edge strings on the lines this PR edits are Console labels (Edge Libraries, Edge Services, Edge Nodes, Edge Pulse) or prose already on the line before it (Edge Node in the Orchestrator first-steps pair), which this PR does not rename
• How-to/tutorial content includes at least one runnable, copy-paste-tested code block — no runnable code block is added or changed; the style guide gains one mdx example fence
• Screenshots (if any) have alt text and follow image standards — no screenshot is added or changed
• Internal links are relative and resolve locally
• If any permalink changed or page moved: redirect added in this PR — no permalink changes
• i18n: pt-br updated in this PR or follow-up i18n issue created: pt-br updated in this PR
• I ran pnpm build:local (build + frontmatter check) without errors — not run; CI runs the build

[marcus-souza-azion]

This PR rewrites the pt-br menu-principal/referencia/build/edge-application/origins.mdx line 56, which still says localizar seu conteúdo ou aplicativo. MM-16253 (#2621) replaces aplicativo with aplicação for the customer's own software, per guia-de-estilo/convencoes/paginas-bilingues.mdx, and leaves this line to your PR so the two don't conflict. Could you change it to localizar seu conteúdo ou aplicação here?