Closed mattstein closed 1 year ago
Do you want me to do a PR to remove?
@rfay Only if you want to!
It’ll need to remove the Markdown obviously, but should also remove unused images and in-text links to deleted posts, and add redirects to .platform/routes.yaml
. Possibly remove authors that stop having posts, if that becomes relevant.
I did the checkboxes; you made that so easy. If you have any concerns about my choices, feel free to check another box.
Thanks for doing that! I’ll trust your editorial decisions and take care of the project pruning.
I did the checkboxes; you made that so easy.
@rfay If you’re immediately aware of anything you moved to the docs, calling out any redirects will probably save me some time. Otherwise I’ll root around and find what I can.
Added redirects that seemed relevant for four of the articles we removed. This effort’s finished!
Congrats!
Related to the effort in #31, we’ll need to decide what to do with old blog posts. That means reviewing the list of remaining posts, and deciding which should be removed. If there’s an appropriate redirect for a deleted post, we should identify that here as well.
Posts to Keep
The following exhaustive list catalogs the blog posts we have left, in reverse-chronological order, with a link to each one’s detail page on the preview build.
Check off any posts that should stay. If the post should be deleted, specify redirects in the Redirects Needed section below.
stop
commands, plus a hosting team hackathonconfig.*.yaml
, static bind ports, longer project namesRedirects Needed
List any deleted URL paths and the URLs they should redirect to so we can help readers and preserve SEO value.
Example:
/blog/customizing-ddev-local-images-with-a-custom-dockerfile
→https://ddev.readthedocs.io/en/latest/users/extend/customizing-images/