Skip to content

Docs: Add F5 ADS AWS and Google Cloud - #2300

Draft
travisamartin wants to merge 16 commits into
mainfrom
f5ads/migrate-aws-and-google
Draft

travisamartin wants to merge 16 commits into
mainfrom
f5ads/migrate-aws-and-google

Conversation

@travisamartin

@travisamartin travisamartin commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Proposed changes

This PR:

  • Moves F5 ADS for AWS docs from content/nginxaas/aws to content/f5ads/aws (completed in an earlier commit on this branch)
  • Copies NGINXaaS for Google Cloud docs to content/f5ads/google and updates them with the new F5 Application Delivery Service for Google Cloud branding and prose
  • Preserves content/nginxaas/google and content/nginxaas/overview as live pages with <link rel="canonical"> pointing to the F5 ADS equivalents, and adds a {{< renamed-notice >}} callout on every page
  • Adds canonical front matter support: overrides layouts/partials/meta.html to emit the canonical tag, and layouts/_default/list.html to render the notice on section landing pages
  • Updates {{< renamed-notice >}} to read canonical front matter instead of the removed f5-moved-to key

F5 ADS nav updates

image image

Stub page with "This page has moved" shortcode

image

Canonical links

image

JTorreG and others added 8 commits September 11, 2026 01:05
Introduce F5 Application Delivery Service for Google Cloud as the
canonical product name and location, while keeping the existing
NGINXaaS pages live and pointing search engines at the new tree.

- Copy content/nginxaas/google to content/f5ads/google, updating
  internal Hugo ref paths, url: front matter, and f5-product for the
  new name and location
- Add canonical front matter to all 27 files in both google trees:
  f5ads pages self-declare, nginxaas pages defer to their f5ads
  counterpart
- Add f5-product-former and the renamed-notice shortcode to all 27
  files in content/nginxaas/google and all 15 in
  content/nginxaas/overview
- Add self-referencing canonical to all 15 files in
  content/f5ads/overview
- Override layouts/partials/meta.html to emit the canonical front
  matter key as <link rel="canonical">, falling back to .Permalink
- Override layouts/_default/list.html to render .Content on section
  pages carrying f5-product-former, so the notice appears above the
  card grid on _index.md pages
- Update layouts/shortcodes/renamed-notice.html to read canonical
  instead of the removed f5-moved-to key
- Update the homepage card and product selector to reference the new
  name and f5ads/google URL
- Add F5 Application Delivery Service for Google Cloud to the AGENTS.md
  product names list
Apply the new product naming to body prose across content/f5ads/google.
Front matter is untouched.

- First mention per file uses the full name, F5 Application Delivery
  Service for Google Cloud; subsequent mentions use F5 ADS for Google
  Cloud
- Drop the "(NGINXaaS)" abbreviation introduced at first mention, since
  F5 ADS for Google Cloud is now the short form
- Standalone NGINXaaS becomes F5 Application Delivery Service
- NGINXaaS Console and NGINXaaS console become F5 ADS Console and
  F5 ADS console
- Update link text to match the new naming
- Update the Cloud Monitoring dashboard displayName and the helper
  script comment in fenced code blocks
- Fix a pre-existing truncated product name in
  monitoring/enable-nginx-logs.md, which read "F5 NGINXaaS for Google"

Leaves the `F5 NGINXaaS Service Account Unique ID` UI field name as is,
because the product UI has not been renamed yet. Also leaves lowercase
identifiers and asset paths untouched, such as nginxaas_deployment_name,
$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID, and the marketplace URL slug.
Replace the expanded legacy form "NGINX as a Service" with
"F5 Application Delivery Service" in the usage dashboard overview
paragraph, matching the naming applied to the rest of
content/f5ads/google.
@github-actions github-actions Bot added documentation Improvements or additions to documentation tooling Back end, repository, Hugo, and all things not related to content process documentation Documentation related to how the repository or documention itself is managed. labels Sep 18, 2026
@github-actions

Copy link
Copy Markdown

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/2300/

Bring content/f5ads/google/overview.md into alignment with the
already-edited content/f5ads/aws/overview.md, and add the NGINX Plus
license management note to both files.

- Add missing description, f5-keywords, f5-summary, and f5-audience
  front matter to the Google file, matching the AWS pattern
- Tighten the intro, introduce the "(F5 ADS for Google Cloud)"
  abbreviation on first mention, and shorten to F5 ADS afterward
- Add the NGINX Plus license management sentence to both files
- Turn off isFeaturedSection on the card section and add the missing
  "Get help" card
- Fix the duplicated "operational overhead" capability and rewrite the
  garbled consumption-based pricing bullet
- Convert architecture bullets to active voice, add missing terminal
  punctuation, and align parallel structure with the AWS bullets
- Remove passive "allows client access" phrasing in both frontend
  sections; drop the ad hoc "Access control" subheadings in favor of
  inline treatment matching AWS; split an overlong private endpoint
  paragraph
- Replace self-referencing ref shortcodes with in-page anchors
- Remove "we"/"our" language in Current limitations, add contractions,
  and tighten the constraints intro sentence
- Match the architecture diagram alt text to the F5 ADS short form
- content/f5ads/aws/_index.md: set cascade.contentVars.product to the
  full name, F5 Application Delivery Service for AWS
- content/f5ads/google/_index.md: set title to the full name, F5
  Application Delivery Service for Google Cloud, and add linkTitle:
  F5 ADS for Google Cloud to keep the nav label short
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation process documentation Documentation related to how the repository or documention itself is managed. tooling Back end, repository, Hugo, and all things not related to content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants