You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repositions the devsy.sh landing hero, home page metadata, and the what-is-devsy docs intro so devcontainer terminology and the
backend-agnostic value prop are explicit and indexable, instead of a
generic "cut onboarding cost" claim shared by every competing
dev-environment tool.
Hero sub/lede now name devcontainer.json explicitly and tie together
the two audiences the page already serves structurally (engineers and
their AI agents), via the backend-agnostic mechanic: same devcontainer.json runs as a Docker container, Kubernetes pod, or
hardware-isolated microVM, switchable with one command.
Home page <title>, <meta description>, OpenGraph, and Twitter tags
updated to match.
content/docs/what-is-devsy.mdx gets a keyword-rich title, a new description frontmatter field (schema already supported it, unused
until now), and its opening paragraph now names Kubernetes pods and
microVMs alongside plain containers.
No em dashes, no adverbs, per stakeholder style preference.
Scope
Three files only: app/(home)/page.tsx, app/(home)/layout.tsx, content/docs/what-is-devsy.mdx. Nav copy, other landing sections
(FEATURES/AGENTS/DEPLOY ANYWHERE), other docs pages, dl-devsy-sh, and images-devsy-sh are untouched.
Verification
npm run build in sites/docs-devsy-sh succeeds. Static export HTML
confirmed the new <title>, <meta description>, og:title, og:description, twitter:title, twitter:description, hero copy, and
docs page title/description all render correctly.
… backend-agnosticism
Lead the landing hero, home page metadata (title/description/OG/Twitter),
and the what-is-devsy.mdx intro with devcontainer-based developer
workspaces that run as Docker containers, Kubernetes pods, or
hardware-isolated microVMs, for both engineers and their AI agents.
Previous copy never mentioned devcontainer in indexable title/meta/hero
text and led with a generic onboarding-cost claim shared by every
competing dev-environment tool. Repositions around the two differentiated
capabilities already built: full backend-agnosticism across every
devcontainer-capable runtime, and first-class AI-agent sandboxing.
Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: c6855e91-fa42-4a17-ad82-3470e923c5b7
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
🔍 Trigger review
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
skevetter
changed the title
docs(site): reposition devsy.sh hero and metadata around devcontainer backend-agnosticism
docs(site): update landing page
Aug 18, 2026
AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
skevetter
changed the title
Summary
Repositions the devsy.sh landing hero, home page metadata, and the
what-is-devsydocs intro so devcontainer terminology and thebackend-agnostic value prop are explicit and indexable, instead of a
generic "cut onboarding cost" claim shared by every competing
dev-environment tool.
devcontainer.jsonexplicitly and tie togetherthe two audiences the page already serves structurally (engineers and
their AI agents), via the backend-agnostic mechanic: same
devcontainer.jsonruns as a Docker container, Kubernetes pod, orhardware-isolated microVM, switchable with one command.
<title>,<meta description>, OpenGraph, and Twitter tagsupdated to match.
content/docs/what-is-devsy.mdxgets a keyword-rich title, a newdescriptionfrontmatter field (schema already supported it, unuseduntil now), and its opening paragraph now names Kubernetes pods and
microVMs alongside plain containers.
No em dashes, no adverbs, per stakeholder style preference.
Scope
Three files only:
app/(home)/page.tsx,app/(home)/layout.tsx,content/docs/what-is-devsy.mdx. Nav copy, other landing sections(FEATURES/AGENTS/DEPLOY ANYWHERE), other docs pages,
dl-devsy-sh, andimages-devsy-share untouched.Verification
npm run buildinsites/docs-devsy-shsucceeds. Static export HTMLconfirmed the new
<title>,<meta description>,og:title,og:description,twitter:title,twitter:description, hero copy, anddocs page title/description all render correctly.