Skip to content

docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages - #2558

Merged
bruno-andrade-azion merged 31 commits into
mainfrom
docs/fundamentals-review-notes
Nov 12, 2026
Merged

bruno-andrade-azion merged 31 commits into
mainfrom
docs/fundamentals-review-notes

Conversation

@marcus-souza-azion

@marcus-souza-azion marcus-souza-azion commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

What & why

Related issue: MM-16289. The source is a reader review of the Fundamentals pages, one highlight per sentence, read on the Portuguese pages.
Pages affected: 21 pages, each in en and pt-br, plus src/nav/trees/fundamentals.json. The en permalinks, all under /en/documentation/fundamentals/:

  • Overview and getting started: / (the Fundamentals overview), how-it-works/, first-deploy/
  • Management and billing: accounts-teams-and-users/, your-settings/, account-settings/, activity-history/, accounts/, teams-permissions/, users-management/, billing-and-subscriptions/
  • Security: multi-factor-authentication/, single-sign-on/, social-login/, personal-tokens/, account-lockout-policy/, user-session-timeout/, pci-dss-certification/, soc/, shared-responsibility/
  • Reference: http-status-codes/

The Fundamentals pages are the first pages a new reader opens. A review read them as a reader would and marked 42 sentences: some were hard to follow, some named Console controls that no longer exist, some carried facts that are no longer true, and one diagram could not be read. This PR applies that review in both languages, then applies the same kind of check to the HTTP status codes page and to every page of the Security group, and brings those pages, and every page of the Management group, to the structure the style guide sets.

Where the facts come from

  • Console labels come from the Console's public JavaScript, read on November 3, 2026: the Account Settings sections and fields, the Users Management form, the GitHub import form, the connector's Transport Protocol Policy options (Preserve, Force HTTPS, Force HTTP), and the account menu entries by account type. No Console screen sets the Account Lockout Policy or the User Session Timeout.
  • Permissions come from GET /v4/iam/permissions. The public OpenAPI file has no IAM paths, so nothing states what each new permission grants beyond its name. The "also requires the permission View …" notes on the new rows follow the pattern of the existing Edit/View pairs; the API does not confirm them.
  • Plans come from the pricing page, read on November 3, 2026.
  • Response headers and the error page come from live requests: X-Azion-Edge-Location is always present, X-Azion-Edge-Pop comes only with Pragma: azion-debug-cache, and the default error page for a 400 shows the fields the page lists.
  • Console labels re-read on November 12, 2026, from the same public JavaScript: the GitHub integration rows show Connected and a Disconnect button; the client and group forms label Active and Email Identifier; Your settings labels Phone Number.
  • Labels taken from guides, not observed in the Console: "Creation failed" and "Deploy Log" come from the GitHub import guide, and "Astro Boilerplate" comes from the template guide.

How this was checked

  • docs_gate.py --check on every changed page reports only false positives: etc. inside the Console label Apartment, floor, etc., & inside Billing & Subscriptions, and "a few clicks".
  • linkcheck.py reports 0 broken links, 0 cross-language links, and 0 unpaired namespaces. pnpm lint:navcheck, pnpm lint:slugcheck, and pnpm build:local ran on the branch after the merge of main.
  • Not verified: what each new permission grants, whether creating a Group needs the same permissions as adding a client, Enterprise overage pricing, and the use of the account ID in support tickets. The SOC page says "biannual" in its introduction and "annually" under Report frequency; that text predates this PR and waits on the compliance team.

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 — every page has title, description, meta_tags, namespace, and permalink; none carries last_reviewed
  • No legacy "edge-" product names in the copy
  • How-to/tutorial content includes at least one runnable, copy-paste-tested code block — the First deploy commands were not run in this PR
  • 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 changed
  • i18n: pt-br updated in this PR or follow-up i18n issue created:
  • I ran pnpm build:local (build + frontmatter check) without errors

The request path diagram drew six unconnected nodes inside a data center
subgraph, so it rendered tiny and showed neither the workload nor the
way back. It now follows the use-case convention: top to bottom, the
workload first, dotted return arrows, numbered labels that match the
steps under it.

Also rewords the opening sentence, the Our Network link (the page does
not list data centers), the standalone resources table row, and the
What you can build intro, in English and Portuguese.

Also moves the custom page set from the Application row to the Workload
row, because the workload deployment names it, and phrases the
Standalone resources row like the other rows.
… topology list

Replaces the two opening paragraphs with a short definition of Azion,
states plainly that each product lives inside the resource it acts on,
drops the card instruction the diagram does not need, and rewrites the
application and functions items without diagram jargon. Adds a sign-up
button next to the account paragraph, in English and Portuguese.

Also says that a Reseller account, not a Group account, holds client
accounts, as the Console account menu shows.
…arn about frameworks

The GitHub path named controls the import form no longer has (build and
deploy commands, Protect with Azion Firewall, Create and deploy). Its
last steps now follow the Import from GitHub form: Application Name,
Preset, Root Directory, Install Command, Deploy, and the Creation failed
state with the Deploy Log panel.

Also points the template path at Astro Boilerplate while keeping the
choice open, makes the supported-framework requirement a warning with
the Preset list and a compatibility link, renames the Test it headings,
replaces the AI prompt, links the sign-up page, drops the unsourced
credit-card claim, and points the custom-domain card at the guide that
does it, in English and Portuguese.

The step that set Root Directory and Install Command becomes one step
per field, the link to the GitHub import guide uses its current title,
and the Portuguese related resources no longer say edge.
Splits the email-change sentences into their own paragraph, moves the
30-day Activity History retention into a note, names Account Owners and
the Company ID as the Console does, and sets the Group account type in
italics, in English and Portuguese.

Also follows the Console where the page disagreed with it: Reseller
accounts create client accounts and Company accounts create Group
accounts, the Apartment, floor, etc. address field is optional, and the
account owner changes the login settings. Most permissions, not all,
come in View and Edit pairs, because the Orchestrator permissions have
Edit without View.
The Console splits the old Account Profile into General and Company
Information, calls the legal identifier Company ID, adds an optional
Apartment, floor, etc. address field, and has a GitHub Integration
section before account deletion. The page now follows that, and drops
Company Size and Job function, which the Console no longer shows, in
English and Portuguese.

Also names the Login Settings and Danger Zone sections as the Console
does, rewrites the opening that listed the sections, and moves the
headings to sentence case.
…to Profile

The Console names the section Profile. English and Portuguese.
…s management

Uses Azion Web Platform where the page meant the platform, and renames the User profile section to Profile, as the Console does. English and Portuguese.

Also names the Phone Number field and documents the Status section with
its Active switch, as the Console user form shows them.
…and clients

Adds a Group accounts section: Company accounts create Group accounts in
Groups Management, with the same sections as a client account. The page
is renamed Groups and clients, so the sidebar no longer reads Accounts >
Accounts, and the links to it follow the new title.

Reorders the Accounts group of the Fundamentals sidebar: Your settings,
Account settings, Activity history, then Groups and clients, which only
some account types use. English and Portuguese.

Also aligns the page with the Console account types: Company accounts
create Group accounts in Groups Management, and Reseller accounts create
Client accounts in Clients Management. The page said that Clients belong
to Group accounts; its description, note, and client fields now follow
the Console, including the Apartment, floor, etc. address field.
…ent plans

The page still described a sign-up credit and a 365-day trial period.
It now describes the Hobby, Pro, and Enterprise plans as the pricing
page states them: included usage and limits, what happens above them on
each plan, the Pro billing cycle, and when plan changes take effect.
English and Portuguese.

Also names Savings Plans as the pricing page does.
…ough the API only

Azion Console has no screen for the policy; every guide sets it through /v4/auth/policies/lockout. English and Portuguese.
…gh the API only

Azion Console has no screen for the policy; the guide sets it through /v4/auth/policies/session. English and Portuguese.
…e permissions API

Compared the table with GET /v4/iam/permissions. Renames the four rows
the API now names differently (View Analytics, View and Edit Workloads,
View Events, View and Edit DNS) and adds the 32 permissions the table
did not list: Connectors, Custom Pages, Storage Credentials, Policies,
VCS Integrations, VCS Continuous Deployment, Orchestrator Nodes and
Services, Marketplace Publisher, and SCIM Integration.

The API returns names only, so each new row states what its name says,
plus the matching View requirement on Edit rows. English and Portuguese.

Also states the Edit Multi-Factor Authentication row by its name only,
says that the Clients feature belongs to Reseller accounts, and names
Certificate Manager in the Portuguese table.
…irect-loop steps

The 500 fix named API v3 Console controls (an Origins tab, Protocol
Policy, Enforce HTTP). The connector now carries the setting as
Transport Protocol Policy, with Force HTTP, so both procedures follow
the current Console and use DocSteps.

Each status code is now its own section with its fixes under it, the
error page fields are a table, the request examples are text fences,
and the page closes with related resources. The Portuguese page gains
the redirect-loop fix it was missing.

Each procedure ends with the state it leaves, and the opening no longer
says Below.
…g and related resources

Renames the Error treatment section to Common MFA problems and closes the page with the MFA guide and the three settings pages that turn MFA on. English and Portuguese.

For a lost phone, the page now says that an Account Owner resets the
MFA, or Azion Support when you are the only owner, and links the sign-in
troubleshooting page.
Replaces the closing 'visit the creating an account page' sentence with a related-resources list (create an account, the Social Login switch in Account settings, Single Sign-On) and uses dash bullets. English and Portuguese.
The creation fields become a table with a Required column, the visibility rules get their own section, and the page closes with related resources. The English title moves to sentence case, and the Portuguese page now names the last modified date, as the English page does.

The page now opens with what a personal token is, the English
description says what the Portuguese one says, and the Personal Token
menu option is named as the Console names it.
…uides

The five one-paragraph sections that defined IdP, service provider, SAML, OIDC, and SCIM become one terms table, and the Implementation table of guides becomes the related-resources list. The X.509 section keeps its own heading, in sentence case. English and Portuguese.

The page now links the Azion Console setup guide for SSO.
The three settings become one table with their API fields, types, and defaults from the configuration guide. The Implementation table and the three mid-page guide buttons become inline links and a related-resources list. English and Portuguese.

The Unlocking users heading becomes Manual unlock.
The two settings become one table with their API fields, ranges, and defaults from the configuration guide; their sections keep the definitions and the update behavior. The Implementation table and the guide button become an inline link and a related-resources list, and the Session time heading now names Maximum session time. English and Portuguese.

The maximum idle time range now states its 1440-minute ceiling, as the
configuration guide does.
Each FAQ question becomes a subject heading under Attestation details, with its answer unchanged, and the page closes with related resources. The English title moves to sentence case, and the Portuguese page now names PCI DSS 4.0.1, as the English page does.

Both descriptions now say 4.0.1, the coverage sentence names each
Platform Resource without calling any of them an add-on, and the
Portuguese related resource says SOC 2 Tipo 2.
Each FAQ question becomes a subject heading under Report details, with its answer unchanged, and the page closes with related resources. The English title moves to sentence case, and a Portuguese heading typo is fixed (availação).

The coverage sentences name each Platform Resource without calling any
of them an add-on, the SOC 2 Type 2 heading matches the body, and the
Portuguese page says Azion Web Platform instead of plataforma de edge.
The diagram was an image of a two-column table that still named the
Azion Edge Platform. It is now a table with the same rows, readable in
both languages and by agents reading the markdown twin, and the page
text names Azion Platform throughout.

Also moves the title and headings to sentence case, turns the bold
Azion Control Assurance line into a heading, fixes the description and
the opening that started with "This document", and closes the page
with related resources. English and Portuguese.

The description now starts with a verb, and the page says Azion Platform
where it said Azion's Platform.
…rces to four

Related resources had seven items, above the cap of four. The five Fundamentals pages the body already links leave the list, and the teams and users how-to guides join MFA and Single Sign-On. English and Portuguese.
The Profile, Contact information, and Security settings bullets become field tables, with a Required column where the page states it, and the page closes with related resources. The title and the Contact information heading move to sentence case. English and Portuguese.

Portuguese also fixes the platforma typo, names Social Login as the product, and writes e-mail.
The General, Company information, and Address information bullets become field tables, the Social Login and MFA links move to related resources, and the title moves to sentence case. English and Portuguese.

Portuguese also drops Atualmente, fixes usuário to usuários, and removes the empty separator at the end of the file.
The page gains related resources and a sentence-case title. English and Portuguese.

The Portuguese description said the history goes back to account creation, which contradicted the 30-day limit in the body; it now matches the English one. The empty separator at the end of the Portuguese file is removed.
The Main settings, Address information, and Account Owner bullets become field tables, the subsection headings move to sentence case, and the page closes with related resources. The required fields stay as the page states them: marked with an asterisk in the form. English and Portuguese.
… related resources

The table headers become Permission and Description, the Account Owner restriction becomes a note, Error treatment becomes Errors, and the page closes with related resources. The title moves to sentence case. English and Portuguese.

Row fixes: View Functions named no object in English and said domains in Portuguese; Wildcard Purge spelled Real Time-Purge, with a broken bold in Portuguese. Portuguese also fixes Ele concede, platforma, Listas de Rede, and times.
The Profile, Contact information, Security settings, and Status bullets become field tables; the Account owner and Teams rows absorb the paragraphs that followed them, and the page closes with related resources. The title moves to sentence case. English and Portuguese.

English fixes privilegies and teams already existent; Portuguese drops eficientemente and facilmente and uses equipes for teams.
@marcus-souza-azion

Copy link
Copy Markdown
Contributor Author

This PR rewrites the pt-br menu-principal/compliance/soc.mdx paragraph that still says isso levaria a diferenças de desempenho. MM-16253 (#2621) replaces desempenho with performance across pt-br pages, 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 isso levaria a diferenças de performance here?

* origin/main: (53 commits)
  docs(style-guide): standardize Azion Console click paths (#2596)
  docs(store): name the SQL and Storage libraries by their scoped packages (#2575)
  fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621)
  docs(observe): fix dataset name, Data Stream filter, and Grafana Data path (#2573)
  fix(fundamentals): rewrite the Load Balancer steps in minimize-downtime from the reference (#2578)
  i18n(pt-br): label unlabelled asides and fix label casing (#2622)
  fix(links): point pt-br links to their existing pt-br pages (#2620)
  i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs (#2624)
  i18n(pt-br): pair three pages with their English versions by namespace (#2625)
  docs(style-guide): adopt the jsonl tag for JSON Lines samples (#2642)
  chore(lint): check the changelog entries a PR adds (#2634)
  [NO-ISSUE] ci: replace technote-space/assign-author (SO-5131) (#2591)
  fix(structure): tag bare code fences, fix heading skips, add pt-br meta_tags (#2629)
  docs(style-guide): drop the nonexistent GlossaryFilter from the glossary template (#2577)
  docs(release-notes): fix the October 14 anchor and merge the duplicate February 24 entry (#2572)
  fix(orchestrator): fix broken bind and create-service API samples (#2574)
  docs(readability): split the long sentences in the Runtime, CLI, Reference, and KV Store pages (#2635)
  chore(nav): count only visible rows toward the navcheck soft max (#2640)
  docs(nav): triage the pages outside the navigation (#2593)
  fix(guides): match the QStash variable and the Functions usage response to the code (#2571)
  ...

# Conflicts:
#	apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx
#	apps/docs/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx
#	apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx
…ew findings

- Use the Console labels: Connected and Disconnect for GitHub accounts,
  Active and Email Identifier on the client and group forms, Phone Number
  in Your settings.
- Draw the origin fetch from the application to its connector, as the
  steps and the Workloads page describe it.
- Say that GitHub templates need a GitHub account; stop calling the plans
  usage-based in Billing.
- pt-br: performance instead of desempenho on SOC, Account Owner instead of
  proprietário, SOC 2 Tipo 2.
- Restore the first-mention links to Social Login and MFA, spell out AOC,
  and drop time-sensitive, page-narrating, and promotional sentences.
@bruno-andrade-azion
bruno-andrade-azion merged commit c9b16ab into main Nov 12, 2026
9 of 10 checks passed
@bruno-andrade-azion
bruno-andrade-azion deleted the docs/fundamentals-review-notes branch November 12, 2026 17:49
bruno-andrade-azion pushed a commit that referenced this pull request Nov 12, 2026
* origin/main: (48 commits)
  docs(templates): list the Astro templates that only the showcase covered (#2595)
  docs(orchestrator): consolidate duplicate guides and write How it works (#2588)
  docs(secure): retire the pre-Workloads security journey and guide pages (#2586)
  docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites (#2580)
  docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages (#2558)
  fix(observe): name the query editor list instead of its position in the Grafana guides (#2643)
  docs(templates): migrate the legacy template guides to the current guide pattern (#2597)
  docs(style-guide): standardize Azion Console click paths (#2596)
  docs(store): name the SQL and Storage libraries by their scoped packages (#2575)
  fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621)
  docs(observe): fix dataset name, Data Stream filter, and Grafana Data path (#2573)
  fix(fundamentals): rewrite the Load Balancer steps in minimize-downtime from the reference (#2578)
  i18n(pt-br): label unlabelled asides and fix label casing (#2622)
  fix(links): point pt-br links to their existing pt-br pages (#2620)
  i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs (#2624)
  i18n(pt-br): pair three pages with their English versions by namespace (#2625)
  docs(style-guide): adopt the jsonl tag for JSON Lines samples (#2642)
  chore(lint): check the changelog entries a PR adds (#2634)
  [NO-ISSUE] ci: replace technote-space/assign-author (SO-5131) (#2591)
  fix(structure): tag bare code fences, fix heading skips, add pt-br meta_tags (#2629)
  ...

# Conflicts:
#	apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx
#	apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx
#	apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/faturamento.mdx
#	apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx
bruno-andrade-azion pushed a commit that referenced this pull request Nov 13, 2026
* origin/main: (58 commits)
  docs(workloads): review the Workloads section with the style guide and correct it from live tests (#2570)
  fix(ai-inference): review the AI Inference section and correct it from live tests (#2641)
  docs(templates): apply the review of the migrated template guides (#2645)
  docs(templates): point Deploy links to the current Marketplace catalog (MM-16236) (#2582)
  docs(orchestrator): split how-tos into API v4 and API v3 pages (#2584)
  fix(accounts): hyphenate Real-Time Purge and name the Bills tab in the permissions table (#2581)
  chore(lint): accept the English-only Marketplace Agreement and lower the linkcheck baseline (#2647)
  fix(links): point the v3 Applications reference and the guides at the current pages (#2646)
  docs(runtime): migrate Node.js API samples to the ES Modules handler (MM-16245) (#2592)
  docs(observe): use the current GraphQL dataset names across Observe and guides (#2579)
  docs(templates): list the Astro templates that only the showcase covered (#2595)
  docs(orchestrator): consolidate duplicate guides and write How it works (#2588)
  docs(secure): retire the pre-Workloads security journey and guide pages (#2586)
  docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites (#2580)
  docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages (#2558)
  fix(observe): name the query editor list instead of its position in the Grafana guides (#2643)
  docs(templates): migrate the legacy template guides to the current guide pattern (#2597)
  docs(style-guide): standardize Azion Console click paths (#2596)
  docs(store): name the SQL and Storage libraries by their scoped packages (#2575)
  fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621)
  ...
bruno-andrade-azion pushed a commit that referenced this pull request Nov 13, 2026
…nce-soc-pci

* origin/main: (59 commits)
  docs(console): apply the review of the Console path convention (#2644)
  docs(workloads): review the Workloads section with the style guide and correct it from live tests (#2570)
  fix(ai-inference): review the AI Inference section and correct it from live tests (#2641)
  docs(templates): apply the review of the migrated template guides (#2645)
  docs(templates): point Deploy links to the current Marketplace catalog (MM-16236) (#2582)
  docs(orchestrator): split how-tos into API v4 and API v3 pages (#2584)
  fix(accounts): hyphenate Real-Time Purge and name the Bills tab in the permissions table (#2581)
  chore(lint): accept the English-only Marketplace Agreement and lower the linkcheck baseline (#2647)
  fix(links): point the v3 Applications reference and the guides at the current pages (#2646)
  docs(runtime): migrate Node.js API samples to the ES Modules handler (MM-16245) (#2592)
  docs(observe): use the current GraphQL dataset names across Observe and guides (#2579)
  docs(templates): list the Astro templates that only the showcase covered (#2595)
  docs(orchestrator): consolidate duplicate guides and write How it works (#2588)
  docs(secure): retire the pre-Workloads security journey and guide pages (#2586)
  docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites (#2580)
  docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages (#2558)
  fix(observe): name the query editor list instead of its position in the Grafana guides (#2643)
  docs(templates): migrate the legacy template guides to the current guide pattern (#2597)
  docs(style-guide): standardize Azion Console click paths (#2596)
  docs(store): name the SQL and Storage libraries by their scoped packages (#2575)
  ...

# Conflicts:
#	apps/docs/src/content/docs/en/pages/main-menu/compliance/pci-dss.mdx
#	apps/docs/src/content/docs/en/pages/main-menu/compliance/soc-2.mdx
#	apps/docs/src/content/docs/pt-br/pages/menu-principal/compliance/pci-dss.mdx
#	apps/docs/src/content/docs/pt-br/pages/menu-principal/compliance/soc.mdx
bruno-andrade-azion pushed a commit that referenced this pull request Nov 13, 2026
* origin/main: (59 commits)
  docs(console): apply the review of the Console path convention (#2644)
  docs(workloads): review the Workloads section with the style guide and correct it from live tests (#2570)
  fix(ai-inference): review the AI Inference section and correct it from live tests (#2641)
  docs(templates): apply the review of the migrated template guides (#2645)
  docs(templates): point Deploy links to the current Marketplace catalog (MM-16236) (#2582)
  docs(orchestrator): split how-tos into API v4 and API v3 pages (#2584)
  fix(accounts): hyphenate Real-Time Purge and name the Bills tab in the permissions table (#2581)
  chore(lint): accept the English-only Marketplace Agreement and lower the linkcheck baseline (#2647)
  fix(links): point the v3 Applications reference and the guides at the current pages (#2646)
  docs(runtime): migrate Node.js API samples to the ES Modules handler (MM-16245) (#2592)
  docs(observe): use the current GraphQL dataset names across Observe and guides (#2579)
  docs(templates): list the Astro templates that only the showcase covered (#2595)
  docs(orchestrator): consolidate duplicate guides and write How it works (#2588)
  docs(secure): retire the pre-Workloads security journey and guide pages (#2586)
  docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites (#2580)
  docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages (#2558)
  fix(observe): name the query editor list instead of its position in the Grafana guides (#2643)
  docs(templates): migrate the legacy template guides to the current guide pattern (#2597)
  docs(style-guide): standardize Azion Console click paths (#2596)
  docs(store): name the SQL and Storage libraries by their scoped packages (#2575)
  ...

# Conflicts:
#	apps/docs/redirects/en/01.json
#	apps/docs/redirects/pt-br/01.json
#	apps/docs/src/content/docs/en/homes/architctures/by-use-case/application-and-network-security.mdx
#	apps/docs/src/content/docs/pt-br/homes/arquiteturas/por-solucao/seguranca-de-aplicacoes-e-redes.mdx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants