add deprecation chapter #1850
add deprecation chapter #1850
Conversation
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
Co-authored-by: Alessandro Pisa <[email protected]>
stevepiercy
left a comment
stevepiercy
left a comment
There was a problem hiding this comment.
Please follow the amended original plan #1464 (comment)
|
|
||
| : They may got renamed for consistency or are superfluos after an update. | ||
| Code does not need to break to support this. | ||
|
|
There was a problem hiding this comment.
Everything up to this point is a Conceptual Guide, and needs to be split into a separate file placed in the conceptual-guides directory.
Everything after this point is a How-to Guide and should be moved under Developer guide. This section is a recent addition, and more suitable for this content.
jensens
left a comment
jensens
left a comment
There was a problem hiding this comment.
Overall fine, found two minor improvements.
Co-authored-by: Alessandro Pisa <[email protected]> Co-authored-by: Jens W. Klein <[email protected]>
docs/backend/index.md
Outdated
| configuration-registry | ||
| content-types/index | ||
| control-panels | ||
| deprecation |
There was a problem hiding this comment.
Do you all think that this insertion point in the TOC is the most appropiate place for this subject?
|
@MrTango I'm awaiting changes per #1850 (review) before merging. Please let me know. Thank you! |
|
@MrTango should I close this PR as abandoned and won't fix? It needs help before it can be merged. |
It would be a pity because it is a very nice write up :/ |
Indeed. However, my review has not been addressed. I don't know why. No response from @MrTango implies this PR is not needed. If you care to push it forward, please be my guest. |
I will take a look. I wrote this initially back in the days... so I would like to see it survive. |
jensens
force-pushed
the
chapter-deprecation
branch
from
2ccbcf2 to
46b14eb
Compare
|
Ok, this should work. @stevepiercy what do you think? |
Co-authored-by: Alessandro Pisa <[email protected]>
There was a problem hiding this comment.
Thank you very much to all of you :)
@stevepiercy do you mind having another look?
First-time contributors
You must read and follow our First-time contributors.
Submit a pull request
Thank you for your contribution to the Plone Documentation.
Before submitting this pull request, please make sure you follow our guides:
Issue number
Description
Write a description of the fixes or improvements.
Add screenshots or links to a preview of the changes
📚 Documentation preview 📚: https://plone6--1850.org.readthedocs.build/backend/deprecation.html