Skip to content

docs: add plugins concept page - #49

Draft
djsauble wants to merge 2 commits into
mainfrom
docs/plugins-concept-page
Draft

docs: add plugins concept page#49
djsauble wants to merge 2 commits into
mainfrom
docs/plugins-concept-page

Conversation

@djsauble

@djsauble djsauble commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds concepts/plugins.mdx for the [plugins] manifest section (schema v1.14.0, experimental, flox/flox#4535).
  • Covers both experiences: installing/configuring a plugin as a consumer, and writing one (a profile.d script + flox_plugin_data) as a producer.
  • Anchored on the secrets-retrieval use case that motivated the feature — packaging the on-activate pattern from concepts/secrets-management.mdx into an installable component — with an explicit "Beyond secrets" section noting [plugins] is general-purpose, not secrets-specific.
  • Adds a short cross-link from concepts/secrets-management.mdx to the new page, and a nav entry in docs.json.

Not included

  • man/manifest.toml.mdx — this is synced automatically from flox/flox's latest branch by the scheduled sync-man-pages workflow, which only tracks released stable, not main. [plugins] docs will appear there once 1.14.0 ships as latest, same as the auto-activation man pages deferred in docs(auto-activation): drop feature-flag framing for Flox 1.14.0 #48. No manual edit needed or wanted here.

Test plan

  • vale concepts/plugins.mdx concepts/secrets-management.mdx — 0 errors
  • mint broken-links — no broken links
  • Spot-check rendering with mint dev
  • Content review — draft, opened ahead of spec review for early feedback

🤖 Generated with Claude Code

The `[plugins]` manifest section shipped in flox/flox schema v1.14.0
(experimental) with only man-page documentation. This adds the concepts
page covering both experiences: installing/configuring a plugin, and
writing one via a profile.d script and flox_plugin_data. Anchored on
the secrets-retrieval use case from concepts/secrets-management.mdx,
with a note that plugins are a general-purpose mechanism.

The man page itself (man/manifest.toml.mdx) isn't touched here — it's
synced automatically from flox/flox's `latest` branch once 1.14.0 ships,
per the existing sync-man-pages workflow.
@mintlify

mintlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
flox 🟢 Ready View Preview Jul 28, 2026, 5:48 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Comment thread concepts/plugins.mdx Outdated
Comment thread concepts/plugins.mdx Outdated
…hored

Address review: whether a missing [plugins.<name>] table aborts
activation is determined by how the plugin's own script calls
flox_plugin_data, not something Flox guarantees. Reworked both the
consumer-facing note and the writing-a-plugin example to show this
as an explicit choice (fail hard vs. fail soft).

Also switch the example script from a bare `jq` call to `${_jq:-jq}`,
matching how Flox's own activation helpers resolve jq for profile.d
scripts to use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant