- Issue created by @quietone
- Status changed to Needs review
12 months ago 1:45am 23 April 2024 - 🇳🇴Norway hansfn
Deleted "Using Drupal 7 with Rackspace CloudFiles CDN" and "Optimizing Drupal on Rackspace Cloud Sites".
I think we might need a meta issue to discuss how to treat D7 specific documentation. That there is a doc page for D8+ doesn't mean that we should delete the D7 version - if we want to support D7.
- 🇳🇴Norway hansfn
Deleted "Complete Open Source Dev Stack".
Rant: I really dislike these "mega" guides that covers everything. We recently got a new one for Windows / WSL: Installing Drupal with DDEV in WSL2 on Windows →
- 🇳🇿New Zealand quietone
Yes, it would help to know if there is a plan or expectation about the Drupal 7 docs.
I'd like to learn more about your preferences for organizing the material on d.o. So far, I like the Diátaxis approach to documentation. It is easy to understand and it promotes incremental fixes as opposed to having a grand design first.
- 🇩🇰Denmark ressa Copenhagen
Thanks for organizing the pages to be migrated here @quietone. The "create a static archive" method works well, I updated the commands 12 months ago. So I have created a page in the new documentation system under https://www.drupal.org/docs/administering-a-drupal-site/creating-a-stati... → .
I agree that the monolithic guides are best avoided, since they easily become silos, with a lot of overlap. So the proposal to using a documentation framework such as Diátaxis is a great idea, since we can use that as a guiding philosophy, to make decisions about which structure and style to use.
- 🇩🇰Denmark ressa Copenhagen
@drumm has previously added redirects from deleted doc pages to the replacement page in the new doc system, perhaps that's possible? I have added checkboxes the two places where it's currently relevant here, but maybe more redirects can be added?
- 🇳🇿New Zealand quietone
@ressa, why did you create a new page for the 'creating a static site' instead of migrating the existing one? I would assume that the migrate process itself would take of making the redirects.
I have added the redirect for that page and updated the IS. So, https://www.drupal.org/node/27882 → can be deleted.
It is hard for me to see the check in the checkbox. Can something else be used?
- 🇩🇰Denmark ressa Copenhagen
I didn't use the Migrate documentation feature, because I didn't know it existed. But I tried following the "migrate this documentation" link, and I wouldn't have been able to place it there anyway, since:
You can only migrate pages into the guide you maintain. To create a guide for your project, edit the project page and follow the links on the "Project documentation" tab.
These are the guides I maintain, I supposes because I created them: Boost, Bootstrap5, Chaos Tool Suite (ctools), Geofield, Leaflet, Matomo Analytics, Open ReadSpeaker, and since I don't maintain "Administering a Drupal site" it's not an option.
The checkboxes are simply emojis, so they can be copied from elsewhere on the page, and replaced as needed. Would you prefer using something like this?
Redirect - 🇩🇰Denmark ressa Copenhagen
I found this section about "Migrating legacy documentation", but it seems like a lot of steps, also resulting in an overly convoluted structure, if you just want to add a page under an existing guide ...
https://www.drupal.org/drupalorg/docs/content/documentation#s-migrating-... →
Would it be possible to allow non-maintainers to migrate a page from the old system into an existing guide, so that under "Documentation guide to migrate page(s) into: *" all guides would be listed? Or maybe the "Migrate X child pages" is the reason for the limitation, to keep things under control, and not getting an existing guide flooded with pages?
- 🇳🇴Norway hansfn
- I deleted 27882.
- I can migrate directly into any module documentation guide, but not the general docs. It would help if drumm relaxed the conditions now to get the pages faster migrated.
- 🇩🇰Denmark ressa Copenhagen
Thanks @hansfn, but it looks like the redirect for /node/27882 got flushed out as well ...
I created 📌 Relax permissions for faster migration of old documentation pages Active .
- 🇳🇴Norway hansfn
it looks like the redirect for /node/27882 got flushed out as well
Not under my control. You can readd the redirect under the settings for the page you created.
- 🇩🇰Denmark ressa Copenhagen
Thanks @quietone, perhaps redirects to the new pages can be added?
- 🇷🇴Romania claudiu.cristea Arad 🇷🇴
Coming here from 📌 Update documentation link on project page Active .
About page 8. ( https://www.drupal.org/node/1919154 → ) I cannot determine but I think the best approach would be to be migrated at https://www.drupal.org/docs/7/modules/organic-groups → , under "Obsolete" ( https://www.drupal.org/docs/7/modules/organic-groups/obsolete → )
- 🇳🇿New Zealand quietone
@claudiu.cristea, I read your comment after I migrated https://www.drupal.org/node/1919154 → to https://www.drupal.org/docs/7/modules/organic-groups/cookbook → . I set it to 'deprecated' and asked for it to be deleted, #3441968-8: Delete several top level pages at TO BE MIGRATED → .
- 🇳🇴Norway hansfn
@claudiu.cristea: Is your wish that we create a new "Obsolete" doc guide (under "Organic Groups") and then place "Mix public and private files with Organic Groups and File (Field) Paths" in that guide? (That was my interpretation.) Holding back on deletion until this is clear.
- 🇺🇸United States drumm NY, US
I missed this issue before, I can take care of the deletions in the issue summary.
- 🇺🇸United States drumm NY, US
Deletions done according to the issue summary.
- 🇺🇸United States drumm NY, US
I was reading this as a choice instead of a checklist:
☐ Delete
☐ RedirectSome of these are now handled.
For Securing your site → , I think we need to go page-by-page. I think these pages in particular have links from elsewhere on the site. Each child page might be:
- Deleted if not relevant today
- Deleted and replaced with a redirect if duplicate documentation already exists
- Migrated using the “migrate this documentation” link on each page
- 🇺🇸United States drumm NY, US
https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal → is probably the destination for the pages in Securing your site that might be kept.
I should update https://www.drupal.org/drupal-security-team → to link to the new documentation
- 🇧🇪Belgium BramDriesen Belgium 🇧🇪
I'm working on "Securing your site". Keeping track of everything that moves or gets deleted.
- 🇳🇿New Zealand quietone
@bramdriesen, thanks for working on the security related pages. I am a bit confused though because all the old pages have been migrated when we have been only migrating what is current and deleting the rest. I now see Drupal 4 and 6 modules in the docs. Will this not confuse other readers as well?
Also, I went through another section.
- 🇧🇪Belgium BramDriesen Belgium 🇧🇪
Yeah correct, I checked with Drumm to migrate them all and then do the cleanup. Still in the progress of doing that cleanup :)
- 🇺🇸United States drumm NY, US
Any old modules mentioned can be deleted any time, before or after migrating.
- 🇺🇸United States drumm NY, US
I completed the page deletions noted in the issue summary
- 🇳🇿New Zealand quietone
Securing your site → redirects to a Security in Drupal → .
- 🇺🇸United States drumm NY, US
Deleted the pages marked in the issue summary. This one is getting close to done!
- 🇳🇿New Zealand quietone
@bramdriesen, thanks.
I took a closer look at the remaining pages and think they can be deleted.
That just leaves a possible followup for about Multisite.