docs: prototype new get started journeys - #25986
Draft
dvdksn wants to merge 21 commits into
Draft
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dvdksn
force-pushed
the
codex/get-started-prototype
branch
from
September 2, 2026 14:24
8df8b9d to
83ebf64
Compare
The existing Get started entry point routes beginners into a long fundamentals course and workshop. Replace it with focused application and AI sandbox journeys, and carry the two-path model through navigation and discovery surfaces. Co-Authored-By: Codex <noreply@openai.com>
The prototype opened with commands before establishing the problems each tutorial solves or the results learners should notice. Add concise problem statements, frame the sample as a prepared stage, and include observable checkpoints throughout both paths. Co-Authored-By: Codex <noreply@openai.com>
Give the custom landing page a full-width canvas and balance the two journey cards. Keep the section sidebar and mobile menu on tutorial pages.
The two-card landing page could not represent the broader container, agent, and administrator audiences. Replace it with three staggered persona journeys that expose each route and its available tutorials.
The staggered journey cards introduced noisy pricing-page styling and inconsistent alignment. Replace them with three restrained, vertically aligned tutorial rows with one destination each.
The simplified tutorial index no longer needs a full-width landing-page exception. Restore the standard section sidebar and mobile menu, and keep tutorial rows stacked until enough width remains beside the sidebar.
The prototype tutorials did not cover the complete container workflow, the simplest sandbox path, or a concrete administrator outcome.\n\nRewrite all three tutorials around concise happy paths and update their landing-page titles and descriptions.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
The agent tutorial showed an isolated image but did not make the sandbox experience or its safety boundary meaningful.\n\nShow an ordinary agent workflow that changes the shared workspace while containing packages and containers, then discard and recreate the environment.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
The agent tutorial used harmless package installation and did not demonstrate the practical blast radius of host execution.\n\nUse a realistic clean-build request that removes unrelated Docker state, then show that the collateral loss remains inside the sandbox daemon.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
Replace the synthetic cleanup canary with two real checkouts of Docker's todo application. Demonstrate how a routine Compose database reset can collide on a shared daemon, while a sandbox keeps the agent's stack and Docker state isolated.
The agent tutorial required two checkouts, a host application stack, and a Compose collision preview before reaching the sandbox payoff. Replace it with one real project, one sandboxed debugging task, and a direct demonstration of isolated Docker state and disposable cleanup.
Reframe the agent tutorial around moving an existing full-autonomy workflow into Docker Sandboxes. Add installation entry points above the get-started tutorials.
Introduce images and containers before the first run command, explain the command options, and connect the single-container, Compose, build, and sharing steps for first-time users.
Introduce the first-run network policy before recommending a preset and simplify the workspace isolation, imported skills, and cleanup explanations.
Add next-step links to the container and sandbox tutorials. Remove the superseded Introduction series, preserve its published routes with aliases, and update inbound links to the replacement tutorial.
Present installation paths and tutorials with the same restrained card treatment used on the documentation homepage. Remove the row arrows and keep audience and duration as quiet tutorial metadata.
Carry the workshop aliases added on main to the replacement container tutorial. Update new inbound links and the sharing shortlink target so removing the superseded introduction does not leave broken routes.
dvdksn
force-pushed
the
codex/get-started-prototype
branch
from
September 2, 2026 14:37
83ebf64 to
495f524
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Prototypes a task-first Get started experience organized around three short journeys:
The change replaces the existing Get started landing content with a compact journey selector, adds direct installation paths for Docker and Docker Sandboxes above the tutorials, adds the tutorials as a collapsible sidebar group, and updates homepage and
llms.txtdiscovery paths. The container and sandbox tutorials include focused next steps into relevant concept and manual pages.The superseded Introduction series and its unused images are removed. Its published routes and legacy aliases, including the workshop routes consolidated on
main, redirect to the replacement container tutorial or the Get Docker page. Inbound documentation links point to the new tutorial.The existing Docker concepts content remains available while this direction is evaluated.
@netlify /get-started/
Deploy preview
Generated by Codex