docs(onprem): make the self-hosting page a real landing page - #15464
Merged
Conversation
The page was two sentences and a sales address, which no longer works now that it sits above a section covering sizing, installation, migration, upgrades, backups, and storage. It now does the job a landing page should. It explains the two deployment models and what actually separates them, that a single Compose host has to be sized for peak because nothing scales out while Kubernetes lets you provision for steady state and add replicas, and it gives a recommendation rather than leaving the reader to infer one. Adds what you need before starting, including the point that sizing depends on both finding count and concurrent users because those drive different parts of the deployment, and how to obtain a license and tooling. Keeps both contact paths. Existing customers are pointed at their account representative or support, and evaluators at the sales address the page previously used on its own. Frontmatter is deliberately untouched so this does not collide with the weight change in the hardware sizing PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blakeaowens
approved these changes
Aug 1, 2026
Maffooch
approved these changes
Aug 1, 2026
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.
installation_options.mdwas two sentences and a sales address. That was fine when it was one of three pages in the section; it isn't now that it sits above pages covering sizing, installation, migration, upgrades, backups, upload limits, and storage.It now does what a landing page should:
Notes for review
Frontmatter is deliberately untouched. The diff hunks start at line 8, so this does not collide with the
weight: 4toweight: 5change in #15459. The two PRs can merge in either order.No cross-links yet. Most of the pages this one describes are still in open PRs, so linking them would fail the offline link check on this base. The section navigation covers discovery in the meantime, and the links belong in a single pass once #15452, #15455, #15456, #15458, #15459, and #15461 have landed.
Testing
hugo --minify --gc --config config/production/hugo.tomlbuilds clean with no new warnings.noscriptfallbacks, verified in the built output.🤖 Generated with Claude Code