docs(ep-v2): relabel the new Enterprise Portal from Alpha to Beta - #4401
Draft
Bishibop wants to merge 1 commit into
Draft
docs(ep-v2): relabel the new Enterprise Portal from Alpha to Beta#4401Bishibop wants to merge 1 commit into
Bishibop wants to merge 1 commit into
Conversation
sc-138828 (the EP v2 Beta entitlement flip) lists a merged relabeling PR as an explicit gate condition. This is the docs half; the code half is a separate PR in vandoor. Follows the Security Center relabel, #4231. - All 16 enterprise-portal-v2-* pages open with the same ":::note Alpha Feature" block. Retitled to "Beta Feature" and rewritten two-tier the way #4231 did: the availability claim goes only on the about page, the sub-pages get the shorter subject-to-change line. - "For access, contact your Replicated account representative" is deleted rather than reworded on the twelve pages that carried it. It describes the alpha access gate and is false at Beta, which is how #4231 handled the same sentence. - "Some capabilities might require additional access" is kept on the four pages that carried it instead. It is still true: Terraform modules are premium-plan gated, and Security Center and Ask AI are separate toggles. - Sidebar category label, the Security Center enable-access heading, and the stray "which is in alpha" aside on the Custom Domains page. The Security Center heading gets a pinned {#enterprise-portal-new} anchor so its URL stops tracking the maturity word and does not move again at GA. It had one inbound link, which 1112b89 removed, so nothing in the repo points at the old slug today. Two "alpha" mentions remain on enterprise-portal-v2-invite.mdx. They are release channel names in an example, not maturity labels. Vale: 352 alerts before, 352 after. The one heading warning that moved is the same pre-existing sentence-case warning on the same heading.
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
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
2 participants
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.
Docs half of the EP v2 Alpha -> Beta relabel. Story: https://app.shortcut.com/replicated/story/138827
sc-138828 (the EP v2 Beta entitlement flip) lists a merged relabeling PR as an explicit gate condition. The code half is replicatedhq/vandoor#10401. Follows the Security Center relabel, #4231.
What changed
The 16 page-level admonitions. Every
enterprise-portal-v2-*page opens with the same:::note Alpha Featureblock. Retitled toBeta Featureand rewritten two-tier, mirroring what #4231 did for Security Center — the availability claim goes only on the about page, the sub-pages get the shorter subject-to-change line.aboutconnect-repo,invite,vendor-api-automationTwo sentence-level decisions worth flagging:
"the new Enterprise Portal" rather than "the Enterprise Portal", since the latter is ambiguous while Classic still exists.
The other three.
sidebars.js:211Enterprise Portal (New) (Alpha)->(Beta)security-center-enable-customer-access.mdx:46## Enterprise Portal (New) (Alpha)->## Enterprise Portal (New) (Beta) {#enterprise-portal-new}custom-domains-using.md:76The Security Center heading gets a pinned anchor so its URL stops tracking the maturity word and does not move again at GA. It had exactly one inbound link, from
enterprise-portal-v2-about.mdx, which1112b899fremoved last week — so nothing in the repo points at the old#enterprise-portal-new-alphaslug today. Explicit anchors are already the repo idiom ({#ec},{#add-domain},{#about-saml}).custom-domains-using.mdis the one place a maturity label leaked onto a page that has nothing to do with EP v2 — the direct analogue of the six such hits #4231 found, and the row most likely to be missed.Not in scope
replicated enterprise-portal preview), including theenterprise-portal-v2-accessH1.enterprise-portal-v2-invite.mdx(lines 36 and 40) are release channel names in an example. Renaming them would make the docs wrong.enterprise-portal-configure.mdxis EP v1 and genuinely still Alpha.llms.txtlists only the six Classic pages and omits all 16 EP v2 pages. That is a coverage gap, not a maturity marker; it belongs to sc-139273.Checks
TokenIgnores, as intended.Alpha Feature,Enterprise Portal (New) (Alpha), orenterprise-portal-new-alpha.Ordering
Overlaps #4391 (Portal Features / Ask AI) on
sidebars.jsandsecurity-center-enable-customer-access.mdx, but on non-adjacent lines — 211 vs 217, and 46 vs 62. Either order merges cleanly. Marked draft; the intent is that it goes in with the sc-138828 flip rather than ahead of the Beta announcement.