Repository navigation
docs: polish the factory infrastructure and self-hosting pages (audit 5/5) - #857
Draft
hongyi-chen wants to merge 9 commits into
Draft
hongyi-chen wants to merge 9 commits into
hongyi-chen wants to merge 9 commits into
Conversation
Reshape the factories overview from a launch-post structure into a technical overview: a concrete definition up front, one short section per part of a factory, sizing guidance, and related pages. Removes the "Who benefits", "What you get", product-table, and "Key terms" sections and the undefined "delivery policy" coinage. The #sizing-a-factory anchor that three pages link to is preserved. Aligns the opening definition on how-factories-work and the docs homepage with the overview, trims the diagram legend, cuts the salesy self-improvement framing, and adds the missing Related pages section. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Oz <oz-agent@warp.dev>
…w-copy # Conflicts: # src/content/docs/factories/how-factories-work.mdx # src/content/docs/factories/index.mdx # src/content/docs/index.mdx
Tighten the opening (drop "tools your team already uses"), make the component headings parallel, say "repeated failures" consistently, and note that benchmarks now compare harnesses as well as models and runners per #841. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Oz <oz-agent@warp.dev>
Add Microsoft Teams and Azure DevOps to the how-factories-work work sources legend so it matches the overview, and drop the restated consequence clause from the overview's Execution section in favor of naming what the infrastructure page covers. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Oz <oz-agent@warp.dev>
Same treatment as the factories overview: a concrete opener, three short lists of what Enterprise adds (administration, security and compliance, shared team configuration), role-based entry points, and related pages. Removes the "Who Warp Enterprise is for", "What this section covers", "Why enterprises choose Warp", and "Support and resources" sections and the marketing adjectives. Every retained claim was checked against the enterprise page it links to. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Oz <oz-agent@warp.dev>
This reverts commit ff03ffb.
Shorten the lead to two sentences, keep the CTA cards directly under it, and open a "What a factory does" section for the foreman, example, and human-checkpoint detail so the body is not an unbroken block of prose before the first H2. Rewrite the description so it stops repeating the lead paragraph it renders next to. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Oz <oz-agent@warp.dev>
Part 5 of 5 of the Warp Factories docs audit, split out of #852. Co-Authored-By: Warp <agent@warp.dev>
hongyi-chen
added
the
warpy-factory
Warp Agent Staging
Collaborator
Author
|
This PR was generated with Warp. Comment   |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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
Part 5 of 5 of the Warp Factories docs audit (split out of #852). The infrastructure cluster plus the leftovers that didn't belong to another part: the quickstart, troubleshooting, the definition page's label, and the sidebar. The self-hosting changes are almost entirely mechanical.
Changes
infrastructure-and-security.mdxwarp-hosting.mdxrunners.mdx(aarch64 and macOS runners exist); the sentence now matches the runners page and links to it.---is gone. The IP list is untouched.deployment-patterns.mdxandrunners.mdxrunners.mdx: en dashes in lists become the hyphen the rest of the section uses; "file-managed" becomes "GitHub-backed"; one unspaced em dash fixed.self-hosting/*(10 pages)---separators removed (54 of them), em and en dashes in list items normalized to-(170 lines), bold-wrapped list links made plain. Four sentences reworded in the quickstart, Docker, and Direct intros ("the default and fastest path", a rhetorical question in a callout, "something like X / Y"). No technical content changed.Leftovers
quickstart.mdx: "the Implement agent" lowercased; "Available team usage" becomes "Team credits"; Next steps follow the quickstart shape (recap line, plain links).troubleshooting.mdx: the framing line "Each entry below names the symptom you'd see" is cut; plain link style.factory-as-code.mdx: frontmatter label matches thesidebar.tslabel that actually renders ("Definitions as code"); Related pages use plain links and the renamed GitHub page title. The reference body is untouched.sidebar.ts: "How Factories work" becomes "How factories work" (mid-phrase "Factories" alone isn't the product name per the terminology rule).Content design plan
Audience and JTBD: Platform and security engineers deciding where factory work runs, and anyone following the quickstart.
Problem: One contradiction between hosting pages, an architecture-first opening, and inconsistent formatting across the self-hosting cluster.
Goals: Hosting claims agree across pages; the cluster uses the same list and separator conventions as the rest of the section.
Content type: Existing conceptual, feature, reference, and quickstart pages; no new pages.
Unverified claims
None.
Documentation risk
Risk: engineering-review-required
Rationale: One platform-support sentence on warp-hosting.mdx now matches runners.mdx (aarch64 Linux images and macOS runners); the rest is wording, formatting, and labels.
Engineering review status: pending
Docs override: none
Validation
npm run build,check_links.py --internal-only(0 broken), andstyle_lint.pywere run on the combined audit branch that these files were split from.Plans:
Co-Authored-By: Warp agent@warp.dev