Skip to content

Update Google Next 2026 landing page to use event-page template#17655

Open
cnunciato wants to merge 3 commits intomasterfrom
cnunciato/google-next-landing
Open

Update Google Next 2026 landing page to use event-page template#17655
cnunciato wants to merge 3 commits intomasterfrom
cnunciato/google-next-landing

Conversation

@cnunciato
Copy link
Copy Markdown
Contributor

@cnunciato cnunciato commented Feb 24, 2026

  • Replaces the custom google-next layout with the shared event-page template (same as kubecon)
  • Updates content for Google Cloud Next 2026 with new hero, features, promo banner, testimonial, and location sections
  • Deletes the now-unused layouts/page/google-next.html template file

Notes

  • Uses Kubecon images as placeholders for now, pending Google Next assets
  • Workshop registration link is a placeholder (#) until the actual link is available

Fixes MA-5.

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Feb 24, 2026

Documentation Review

Files reviewed: content/google-next/_index.md, layouts/page/google-next.html

Overall this is a clean migration to the shared event-page template. The content is well-structured, clearly written, and the alias for the old 2025 URL is correctly set. A few items need tracking before the page goes live.


Issues

Placeholder images throughout (acknowledged in PR notes)

Five images are KubeCon placeholders that will display incorrect branding on the Google Next page:

  • Line 4meta_image: /images/kubecon/kubecon-2026-meta.png
  • Line 20hero.image: /images/kubecon/kubecon-hero-2026.png
  • Line 45features.image: /images/kubecon/code-kubecon-2026.svg
  • Line 88promo_banner.bg_image: /images/kubecon/aws-credits-background.png
  • Line 122testimonial.bg_image: /images/kubecon/bmw-background.png

The image at line 88 is named aws-credits-background.png, which suggests AWS branding — worth double-checking that this background is visually neutral before going live with it. Recommend tracking all five replacements as follow-up work items so they don't get missed when designer assets arrive.

Placeholder workshop link (line 81)

    cta_link: "#"

This renders a non-functional link on the live page. If the workshop isn't confirmed yet, consider either omitting the CTA button until the link is available, or using a disabled/coming-soon state if the template supports it.


Minor notes

Line 56 – "day-2 operations" is a recognized technical term often written as "Day 2 operations" with a capital D. Either form is acceptable but the capitalized form is more common in technical writing.

Line 119 – The testimonial author title reads former Head of Engineering, Cloud Platform. This is grammatically fine, but verify this is the preferred attribution style Pulumi uses for past employees in testimonials.


What looks good

  • Alias /google-next-2025 is correctly set — old URLs will redirect properly.
  • All images have alt text.
  • Booth number, dates, and venue are consistent throughout (April 22–24, 2026, Mandalay Bay, Booth 3624).
  • Hero, features, testimonial, and location copy is clear and well-written.
  • The deletion of the custom layouts/page/google-next.html template is appropriate given the shared template migration.
  • Footer CTA links (/signup, /contact) and internal product links are valid paths.

Mention @claude if you'd like additional review after placeholder assets or links are updated.

@pulumi-bot
Copy link
Copy Markdown
Collaborator

title: former Head of Engineering, Cloud Platform
company: Snowflake
logo: /logos/customers/snowflake-logo.svg
bg_image: /images/kubecon/bmw-background.png
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need a background for snowflake

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

title: Operate GCP at AI-speed without losing control
subtitle: |
As GCP environments scale and AI accelerates change, visibility drops, security drifts, and waste increases without a consistent operational model. Give us a few minutes, and we'll show you how Pulumi can help.
image: /images/kubecon/code-kubecon-2026.svg
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

product image needs to be adapted to google cloud example?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vctrfrnndz Do you have this in SVG? I'd much prefer that if you do (and in general would always prefer SVG for illustrations like this — the PNGs always seem to be either lossy or massive. 😅

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cnunciato Yes, this one is an svg if you open in a separate window!

@vctrfrnndz
Copy link
Copy Markdown

@cnunciato Flagged assets that need to be created, will follow up in the comments 🙏

Copy link
Copy Markdown
Contributor Author

Amazing, thank you @v-victor! I'll get these dropped in today.

cnunciato and others added 2 commits March 3, 2026 17:41
Replaces the custom google-next layout with the shared event-page
template used by kubecon. Adds updated content for Google Cloud
Next 2026 including new hero, features, promo banner, testimonial,
and location sections.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds hero image, meta image, product code image, and Snowflake
testimonial background from design review. Updates markdown to
reference new images in /images/google-next/ instead of kubecon.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cnunciato cnunciato force-pushed the cnunciato/google-next-landing branch from 3578cae to 2aac79c Compare March 4, 2026 01:42
@pulumi-bot
Copy link
Copy Markdown
Collaborator

@pulumi-bot
Copy link
Copy Markdown
Collaborator

@scottmparker scottmparker marked this pull request as ready for review March 4, 2026 23:29
Copy link
Copy Markdown
Contributor

@scottmparker scottmparker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a bunch of comments that infuse more of a community tone and tighten up the language

Tighten copy with a more community-friendly tone across hero,
features, and demo sections per Scott's feedback.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pulumi-bot
Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Contributor

@CamSoper CamSoper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cnunciato -- This still WIP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants