docs: Add opencode-docker to ecosystem documentations - #41440
Open
pkhamre wants to merge 1 commit into
Open
Conversation
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.
Issue for this PR
Closes #41439
Type of change
What does this PR do?
Adds opencode-docker to the Projects table on the Ecosystem docs page, plus the same row to all 17 translated copies so the description reads naturally in each language. The project is a security-hardened Docker container for running the OpenCode CLI in isolation.
I added the row in English first, then repeated it across the locale directories, translating the one-line description to match the style of neighboring entries. No other rows were touched.
The change is purely additive documentation, so there's nothing behavioral to reason about. The only real risk is a mistranslated description or a broken markdown table, both checked against the existing formatting.
How did you verify your code works?
I built the docs, ran the Astro server locally with
bun installandbun run dev, and verified that the docs looked intact while the new content row was added to the Ecosystem pages.Screenshots / recordings
Not relevant for this PR.
Checklist