Skip to content

seo(about-us): align copy with Kestra 2.0 - #5538

Open
vfanucci wants to merge 1 commit into
mainfrom
seo/about-us-2-0-copy
Open

seo(about-us): align copy with Kestra 2.0#5538
vfanucci wants to merge 1 commit into
mainfrom
seo/about-us-2-0-copy

Conversation

@vfanucci

@vfanucci vfanucci commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Why

/about-us had not had a copy rewrite since January (#3725). The only change since was #5326, which removed the news block. Result: zero mention of 2.0, agents or "workers anywhere" on the page, while the homepage now leads with "One orchestrator. Every workflow. Agentic AI under the same controls." Visitors arriving from the launch content — a lot of them come through blog and footer nav — land on the pre-2.0 story.

The page also had no link at all to /two-zero.

What changed

Copy only. No layout, no component structure, no new assets.

Where Change
about-us.astro Title → "About Us: Our Team, Values and Investors"; meta description rewritten
Orchestrate.astro — hero Existing paragraph kept, one sentence appended on 2.0 (workers anywhere, flows as agent tools) carrying the page's only link to /two-zero
Orchestrate.astro — trust block Rewritten around what enterprises actually run on Kestra
Mission.astro Paragraph rewritten around 2.0 and Apache 2.0; <h1><h2>
Mission.astro — values Three grammar fixes, same length
Investors.astro Second sentence now lists AI agents; amounts untouched

Two bugs fixed along the way

Duplicate H1 — the page shipped two: the hero and "Staying True to our Mission". The mission one is now an <h2>.

Missing spaces in the trust block — Astro strips the newline placed before a <strong>, so production was serving:

We believe that<strong>Kestra's potential is limitless</strong>
are eager to explore new<strong>opportunities</strong>

Visible as "thatKestra's" and "newopportunities" on the live page. The rewrite drops that <strong>/<br /> soup, and the replacement markup keeps the space outside the tag. It also fixes "how Kestra transform the way".

Deliberately not in this PR

  • Team list — handled by About Us: Update #5436 (8 new faces, Elliot → Fernando). No overlap, no conflict: that PR touches the teamMembers array, this one touches the surrounding copy.
  • 2.0 UI screenshotMission.astro still shows executions.png, a 1.x dashboard. Candidates already exist in src/components/twozero/assets/; holding until we pick one.
  • Team photo and the Acxiom "Wizard of Oz" quote — both dated. The offsite photos will be the moment for a deeper pass.

Review

Please check the hero and mission wording against how we want to talk about 2.0, and the link anchor. Cloudflare preview once CI is green.

…ng spaces

The page copy had not been rewritten since January and made no mention of
2.0, agents or workers anywhere, so visitors arriving from the launch
content landed on the pre-2.0 story.

- title/meta rewritten around the team, values and investors
- hero paragraph now ends on 2.0 (workers anywhere, flows as agent tools)
  and carries the page's only link to /two-zero
- "Trusted by Enterprises Worldwide" rewritten: the previous markup made
  Astro strip the newline before <strong>, shipping "that<strong>Kestra's"
  and "new<strong>opportunities" to production
- mission paragraph updated, its <h1> demoted to <h2> (the page had two)
- three grammar fixes in the values ("a strong relationships",
  "users feedbacks", "committed to deliver")
- investors paragraph now lists AI agents alongside data and infrastructure

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

☁️ Cloudflare Worker Preview Deployed!

🔗 https://ks-seo-about-us-2-0-copy-docs.kestra-io.workers.dev
🔗 https://c717c51c-docs.kestra-io.workers.dev

🔦 Lighthouse Benchmark

Tested: http://localhost:8787 on 2026-09-08 14:53 UTC
Compared against main baseline from 2026-09-08

Scores (0–100, higher is better)

Page Performance Accessibility Best Practices SEO
Home 77 🔻 -17 84 73 92
Get Started 60 83 73 100
Pricing 97 92 73 100
Enterprise 94 83 73 100
Cloud 89 80 73 100
About Us 83 91 73 100
Docs Landing 95 88 73 92
Contribute to Kestra (simple docs) 98 88 73 92
Flow (full featured docs) 97 90 73 92
Blog Index 75 91 73 100
Blog Post (sample) 89 88 73 100
VS Page (sample) 98 88 73 100
Plugins Landing 91 81 73 92
Plugin Page (sample) 91 88 73 100
Plugin Debug Page (sample) 93 88 73 100
Plugin Debug Return Page (sample) 93 88 77 100
Blueprints Landing 76 91 73 100
Blueprint Audit Logs CSV Export 86 92 73 100

Core Web Vitals (lower is better)

Page LCP FCP TBT CLS Speed Index
Home 1.25 s 0.67 s 387 ms 🔻 0.000 1.69 s
Get Started 2.30 s 0.69 s 885 ms 🔻 0.000 🟢 1.19 s 🔻
Pricing 1.10 s 0.63 s 81 ms 🔻 0.005 0.89 s
Enterprise 1.49 s 0.67 s 64 ms 🔻 0.003 0.84 s
Cloud 2.11 s 0.64 s 59 ms 0.001 0.94 s
About Us 3.05 s 0.66 s 48 ms 🔻 0.000 0.86 s
Docs Landing 1.00 s 0.59 s 146 ms 0.000 1.06 s
Contribute to Kestra (simple docs) 1.06 s 0.54 s 66 ms 0.000 🟢 0.79 s
Flow (full featured docs) 1.10 s 0.61 s 83 ms 🟢 0.002 1.14 s
Blog Index 8.31 s 🟢 0.53 s 62 ms 🔻 0.001 0.87 s
Blog Post (sample) 2.17 s 🔻 0.59 s 38 ms 0.000 🟢 0.75 s
VS Page (sample) 0.99 s 0.60 s 52 ms 0.064 0.73 s
Plugins Landing 0.96 s 0.60 s 33 ms 0.000 3.15 s
Plugin Page (sample) 0.94 s 0.59 s 131 ms 🔻 0.000 2.44 s
Plugin Debug Page (sample) 0.93 s 0.54 s 68 ms 0.000 2.34 s
Plugin Debug Return Page (sample) 1.04 s 0.66 s 48 ms 0.000 2.51 s
Blueprints Landing 2.46 s 1.01 s 46 ms 0.005 4.23 s
Blueprint Audit Logs CSV Export 1.12 s 0.65 s 141 ms 🟢 0.000 4.69 s
Legend

🟢 improved  ·  🔻 regressed  ·  (blank) no significant change
Score threshold: ±10 pts  ·  Metric threshold: ±30% of baseline

View full Lighthouse HTML report for a page

Full per-page Lighthouse Results (LHR) are attached as the lhr-reports artifact on this run. Download and unzip it, then open https://googlechrome.github.io/lighthouse/viewer/ and drop the <page>-lhr.json file into the page to see every audit, opportunity, and diagnostic.

@vfanucci

vfanucci commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

@MartinRst Question about the UI image, do we need to change it with the new version or this one is fine ?

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

Labels

None yet

Projects

Status: To review

Development

Successfully merging this pull request may close these issues.

1 participant