Conversation
FloxHub labels the default package group **Default**, while CLI messages and the lockfile call it `toplevel`, and a manifest only names it when `pkg-group = "toplevel"` is set explicitly. Make the docs say "Default package group (`toplevel`)" at the first mention so readers learning Flox see that the two names are the same group: - concepts/package-groups: retitle the section to "Default Group (`toplevel`)", label the diagram's subgraph "Default (toplevel)", and explain that FloxHub, the CLI, and the lockfile name the same group differently. - concepts/manifest-builds, concepts/nix-expression-builds, languages/rust: use "Default package group (`toplevel`)" at the first mention. Keep literal `toplevel` where it refers to CLI output, lockfile keys, or `flox upgrade toplevel`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… comparison table The Appendix A comparison table still said "`toplevel` default group", which didn't match the naming used everywhere else on the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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.
FloxHub labels the default package group Default, while CLI messages and the lockfile call it
toplevel. The docs only usedtoplevel, so someone reading them has no way to tell that the two names refer to the same group.This PR calls it the "Default package group (
toplevel)" at the first mention on each page, and explains the two names in the package groups concept page.Changes
concepts/package-groups.mdxtoplevel)".concepts/manifest-builds.mdx,concepts/nix-expression-builds.mdxandlanguages/rust.mdxuse "Default package group (toplevel)" at the first mention.toplevelstays wherever it refers to CLI output, lockfile keys, orflox upgrade toplevel.Not included
man/is generated from flox/flox (cli/flox/doc). A few man pages mention the default group too, includingflox-upgrade,manifest.toml,flox-buildandflox-publish. They can get the same wording upstream.package-groups.mdxuses title-case headings throughout, so the new heading matches the rest of that page rather than the sentence-case rule in AGENTS.md.Checks
mint broken-linksreports only the 3 existing/changelog/rss.xmllinks, which this PR doesn't touch.🤖 Generated with Claude Code