Skip to content

Add introducing conda-workspaces blog post - #358

Draft
jezdez wants to merge 9 commits into
conda:mainfrom
jezdez:blog/introducing-conda-workspaces
Draft

Add introducing conda-workspaces blog post#358
jezdez wants to merge 9 commits into
conda:mainfrom
jezdez:blog/introducing-conda-workspaces

Conversation

@jezdez

@jezdez jezdez commented Apr 27, 2026

Copy link
Copy Markdown
Member

Summary

  • Announces conda-workspaces 0.4.0 and explains the workspace model (TOML manifest, named environments composed from features, multi-platform conda.lock, built-in task runner) layered on conda's existing solver, package cache, and channel auth.
  • Builds on the direction in Building a Better conda CLI: A Vision and credits the pixi, anaconda-project, conda-project, and conda-lock teams whose work it reuses.
  • Enables Prism syntax highlighting site-wide for toml, yaml, bash, diff, and json so the post (and future ones) render code blocks correctly.

Contents

  • Definition + mermaid diagram positioning conda-workspaces vs pixi (same manifest, different stack, isolated .conda/envs/ vs .pixi/envs/).
  • Worked TOML example and the matching conda workspace / conda task / conda workspace quickstart flow.
  • Feature beats: composable features, PyPI deps in the same solve (with explicit "still in active development" note for conda-pypi and conda-rattler-solver), multi-platform conda.lock, CI-split locking with --merge, cross-format export/import, and the task runner.
  • Install tabs (conda / mamba / micromamba / pixi global) and a "what it doesn't do" section against pixi.
  • Inline links into the relevant conda-workspaces docs pages and the four coming-from/* migration tutorials.

Test plan

  • npm run start renders the post (images, mermaid, syntax highlighting, tabs, admonitions).
  • npm run build succeeds with no new warnings.
  • All inline links resolve.
  • Publish date coordinated with the conda-workspaces 0.4.0 conda-forge release.

Notes

  • Date 2026-04-27 is a placeholder; happy to bump if review/release slips.
  • additionalLanguages in docusaurus.config.js is broadly useful and not specific to this post; can be split out if reviewers prefer.

@jezdez
jezdez requested review from a team as code owners April 27, 2026 21:26
@netlify

netlify Bot commented Apr 27, 2026

Copy link
Copy Markdown

Deploy Preview for conda-dot-org ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 6cc5c5e
🔍 Latest deploy log https://app.netlify.com/projects/conda-dot-org/deploys/6a0e6540d68052000853be4c
😎 Deploy Preview https://deploy-preview-358--conda-dot-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 96 (🔴 down 3 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 89 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

jezdez and others added 8 commits May 21, 2026 03:22
Announces conda-workspaces 0.4.0 and explains the workspace model
(TOML manifest, named environments composed from features, multi-platform
conda.lock, and built-in task runner) by reusing pixi's manifest schema on
top of conda's existing solver, package cache, and channel authentication.

Also enables Prism syntax highlighting site-wide for toml, yaml, bash,
diff, and json so the new post (and future ones) render code blocks
correctly without language-specific overrides.
Replace the `context._subdir` mechanic with what it achieves: conda is
pointed at the target platform so the right repodata is fetched and the
matching `__linux` / `__osx` / `__win` virtual packages are reported,
making a cross-platform lock see the same world the target machine
would.
Drops "genuinely good" (an empty intensifier flagged in AI-detection
guides), removes the anthropomorphic "the polite one" framing of the
pyproject-toml exporter in favour of a plain conditional, and replaces
the PM-jargon "long pole" with "bottleneck" in the CI-split section.
No content changes.
Open with the lived experience of a maturing conda project (concrete
tools: environment.yml, Makefile/tox.ini, conda-lock) and name the gap
in one sentence: conda underneath, but conda itself never sees the
project the pieces belong to.

The change paragraph stays concept-first (what a workspace is, what the
manifest declares, conda CLI drives it, conda underneath is unchanged)
and drops the mid-paragraph mechanics about .conda/envs/ and install
writing conda.lock, which are already covered in the dedicated feature
sections later.
Drop dismissive "bolted on" framing of conda-lock and Makefile/tox.
Describe a typical conda project's moving pieces, name the existing
good tools respectfully, and position conda-workspaces as the layer
above them rather than as a fix for something broken.
Replace the unsupported "typical conda project has these tools" claim
with a two-paragraph intro that opens on Dan Yeaw's vision post and
credits pixi as the source of the workspace model. Move the vision
link above the truncate so it shows on the index and RSS. Trim the
"Isn't that what pixi is for?" section opener so it doesn't restate
the credit the intro now gives.
Aligns with the conda CLI vision post's endorsement of
conda-workspaces as the future of environment management.
@jezdez
jezdez force-pushed the blog/introducing-conda-workspaces branch from eab8803 to 988f7f2 Compare May 21, 2026 01:51
@jezdez
jezdez marked this pull request as draft June 1, 2026 09:52
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