Skip to content

Update docs to cover uv managed installations#2072

Merged
davisagli merged 19 commits into6.0from
uv-managed
Mar 28, 2026
Merged

Update docs to cover uv managed installations#2072
davisagli merged 19 commits into6.0from
uv-managed

Conversation

@davisagli
Copy link
Copy Markdown
Member

@davisagli davisagli commented Mar 25, 2026

Fixes plone/cookieplone-templates#354

Summary:

  • Update conceptual guide on packaging to cover more of the tools used in the community
  • Update "Override core Plone packages" how-to to include uv-managed installations, and organize into tabs based on the different package managers.
  • Update "Install Plone add-ons" how-to to include uv-managed installations, and organize into tabs based on the different package managers.

📚 Documentation preview 📚: https://plone6--2072.org.readthedocs.build/

Copy link
Copy Markdown
Contributor

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass on draft. I think we'll need another pass or two. Thanks for your work on this!

@github-project-automation github-project-automation bot moved this from New to In Progress in Plone Documentation Mar 26, 2026
Co-authored-by: Steve Piercy <web@stevepiercy.com>
Copy link
Copy Markdown
Member Author

@davisagli davisagli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stevepiercy Thanks for the quick first-pass review. I applied most of the suggestions and will follow up later on the others.

@davisagli
Copy link
Copy Markdown
Member Author

I've now updated a couple more chapters. I think this is ready for review.

@davisagli davisagli marked this pull request as ready for review March 26, 2026 03:11
@davisagli davisagli changed the title [WIP] Update docs to cover uv managed installations Update docs to cover uv managed installations Mar 26, 2026
@stevepiercy
Copy link
Copy Markdown
Contributor

@davisaglis how about on every commit to main in cookieplone-templates, run CI to automatically tag it with a timestamp, then use that tag when running Cookieplone?

I just now looked, and it appears that @ericof had a similar thought, based on https://github.com/plone/cookieplone-templates/releases/tag/20260320.1. Should I create a new issue in cookieplone-templates to have this discussion?

- Break steps into subheadings, starting with configure the add-on installation
…identical. Combine into the project creation method instead.
…. Its target audience is first-timers.

- Create new subsection for installation of the add-on.
- Sync tabs.
… and installation, and sync tabs as that for PyPI installation
Copy link
Copy Markdown
Contributor

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I created a separate PR for docs/admin-guide/add-ons.md only. I haven't reviewed the other files closely yet. I think that a lot of the work in #2073 could be reused here.

@davisagli
Copy link
Copy Markdown
Member Author

@davisaglis how about on every commit to main in cookieplone-templates, run CI to automatically tag it with a timestamp, then use that tag when running Cookieplone? I just now looked, and it appears that @ericof had a similar thought, based on https://github.com/plone/cookieplone-templates/releases/tag/20260320.1. Should I create a new issue in cookieplone-templates to have this discussion?

@stevepiercy I think it's worth discussing if we can improve our release process for cookieplone-templates. But I want to keep that out of scope for this PR, where my goal is to document the status quo better. So yes, a new issue there sounds good.

(Also it doesn't really help here, because the distinction that matters is whether or not the project is configured as uv-managed, and as I realized yesterday, that varies by other factors than just the cookieplone-templates version.)

- Update override-core.md to follow the improvements in add-ons.md
- Factor out the instructions for restarting the instance into _inc/_build-and-restart.md
- Use a simpler check for whether it's a uv-managed Cookieplone project or not
@davisagli
Copy link
Copy Markdown
Member Author

@stevepiercy I tried to update override-core.md to follow your improvements from add-ons.md. I also moved the repeated instructions for restarting the instance into a snippet in the _inc folder.

@erral
Copy link
Copy Markdown
Member

erral commented Mar 27, 2026

I have created a PR for mxdev adding support for the uv.tool.sources option, hopefully we can use that option too in case someone sticks to mxdev for handling checkouts mxstack/mxdev#81

* More uv managed revisions
- The instructions for installation from PyPI have only two options, Cookieplone and Buildout, not the three options from the include. The attempt to avoid DRY with an include won't work here.

* - DRY for complete the add-on installation

* "mxdev" isn't an inline literal

* "mxdev" isn't an inline literal

* tighten up spacing

* grammar

* Increasing specificity

* Make URL clickable

* Add an introductory paragraph to the empty subheading

* - Link to sections in add-ons documentation
- spelling of mxdev and pip
- Oxford comma

* Fix Vale errors

* Fix Vale errors

* Remove unnecessary section subheading

* Promote uv as the first package manager, and combine its first two sentences.

* MyST markup, grammar, link to the pip interface for uv

* Update docs/conceptual-guides/package-management.md

* Update docs/admin-guide/override-core.md

Co-authored-by: David Glick <david@glicksoftware.com>

---------

Co-authored-by: David Glick <david@glicksoftware.com>
@stevepiercy
Copy link
Copy Markdown
Contributor

stevepiercy commented Mar 27, 2026

@erral would you like to create either a suggestion or a separate PR against this branch to document the option, or should we wait until your PR in mxdev gets merged and create a new issue as a placeholder to update these docs?

I'll do a final review of this PR tonight. I think it's good, but I ought to check against the recent merge of the other PR.

Copy link
Copy Markdown
Contributor

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is ready to merge. @davisagli if you agree, would you please do the honors?

@stevepiercy
Copy link
Copy Markdown
Contributor

@erral I created a new issue as a placeholder for whenever your PR gets merged.

#2076

@davisagli davisagli merged commit 178f754 into 6.0 Mar 28, 2026
3 checks passed
@davisagli davisagli deleted the uv-managed branch March 28, 2026 15:39
@github-project-automation github-project-automation bot moved this from In Progress to Done in Plone Documentation Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Update docs and track advanced feature we want to bring into a uv managed backend

3 participants