Add comparison between Buildout and pip installation tools for Classi… #1766
+43
−0
Conversation
This file contains 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
stevepiercy
requested review from
davisagli,
petschki,
yurj,
MrTango and
1letter
yurj
approved these changes
Nov 8, 2024
|
CI failure is a temporary link failure. Merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…c UI
This PR fills a gap with a conceptual guide to inform users whether to choose Buildout or pip when installing Plone with Classic UI.
This is by no means a comprehensive comparison, but only what I was able to collect from various comments and notes. Feedback greatly appreciated.
📚 Documentation preview 📚: https://plone6--1766.org.readthedocs.build/