@senzaesclusiva I am also confused. Are you attempting to add a remote image (at /media/add/remote_image) without adding a URL in the "URL" field in the "Media Remote Image URL"?
Please fill in the "Steps to reproduce" section in the issue summary, so that it's clear.
I hope this can be fixed, but if it cannot, we should consider excluding internal links to images.
The original intent of this module was to add remote images using external links. While locally-stored images would normally be added using the core Image Media type, I suppose it may be useful for this module to support internal links as well, for example so that site builders can use just one media type for both their local and remote images, and multiple fields would not need duplicating on both media types.
That feels like an edge-case to me. Is anyone actually using internal links with this module? Does anyone need that functionality?
nick hope → created an issue.
I've updated MR !7 to fix the phpcs errors described in #8 and #14, and to change "Type the remote image url above." to "Enter the remote image URL." per #8.
Also attaching an updated patch (also available at https://git.drupalcode.org/project/media_entity_remote_image/-/merge_req...).
This does not fix #11, which I can confirm, so it still needs work. I think there are wider problems using internal URLs even without this patch, and may open a separate issue after further investigation.
Created MR and attaching patch, if anyone needs it (also available at https://git.drupalcode.org/project/media_entity_remote_image/-/merge_req...).
Add info about what is shown when you click "Create merge request".
Overhaul of the page. Rephrasing and reformatting for readability and clarity. Add detail on how to fill out the New merge request form on GitLab. This should be reviewed by those with expertise in the Drupal/GitLab workflow to check that the information I have given conforms to Drupal.org policy. For example, it's possible that some fields on the form should be left unchanged in all circumstances.
Integrate very brief summary of what a merge request is. Other tweaks for readability.
Add information about the option of creating a new branch along with an issue fork. Add details of which commands are shown under "Show commands". Numerous changes to phrasing and formatting to improve readability and clarity. Add suggestions to create a merge request after completing commits.
Overhaul of the page for readability. Add specific reference and link to GitLab. Revise summary.
Having made many edits to this guide and its child pages, I think it would be better for Obtaining Git access → to come before Configuring Git for Drupal → . I believe a guide maintainer would have to change the weights of those child pages.
For information, it may be worth adding a note-tip at the top of this page (which I can't edit):
If logged into Drupal.org, these Terms of Service may be accepted or declined at https://git.drupalcode.org/-/users/terms. Acceptance is required for Git access.
Overhaul of page to reflect current procedure. Many fixed links. Remove redundant and duplicate instructions and rephrase for accuracy and clarity. Remove out-of-date user profile screen shot. Remove reference to sandbox projects, which are deprecated. Remove list of terms and defer to the Terms of Service itself. Remove link to Randy Fay video, which is 13 years old and out of date.
At the bottom of #9 I wrote:
I do wonder whether the content of Installing Drupal on Windows for local usage → can be integrated into the parent Windows development environment → , to save one page.
I realise now that guides' descriptions are limited to 1000 characters max, which is quite limiting, so that wouldn't be possible.
Remove duplicate Attributes section, accidentally left in after previous edit. Remove http before patch-url to prevent meaningless link being automatically created.
Re-organize, re-order, re-format and re-phrase for accuracy and readability. Correct links.
Rephrase and add links while staying under 1000 character limit.
Overhauled the page. Corrected links. Updated screenshots. Re-ordered resources list. Added GitLab learning links. Replaced GitHub Learning Lab with GitHub Skills. Re-phrasing and grammar correction.
Change link to https://www.drupal.org/docs/develop/issues → and some minor changes.
nick hope → created an issue.
@senzaesclusiva Why were you trying to save a node without inserting a link to a remote image?
There is a merge request and patch on issue https://www.drupal.org/project/media_entity_remote_image/issues/3467675 🐛 Deprecated function: pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated Active that addresses the problem by simply making the URL field required in media_entity_remote_image/config/install/field.field.media.remote_image.field_media_remote_image_url.yml
https://www.drupal.org/project/media_entity_remote_image/issues/3467686 🐛 Should not unset 'title' key in element array Needs review also seems to be caused by the same reason.
There is a merge request and patch on issue https://www.drupal.org/project/media_entity_remote_image/issues/3467675 🐛 Deprecated function: pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated Active that addresses the problem by simply making the URL field required in media_entity_remote_image/config/install/field.field.media.remote_image.field_media_remote_image_url.yml
https://www.drupal.org/project/media_entity_remote_image/issues/3471458 🐛 D10.3.2 Error "The URL field is required when the field is specified" Active seems to be caused by the same reason.
The MR !9 (in #4) address the problem by simply making the URL field required.
This should also address these issues:
- https://www.drupal.org/project/media_entity_remote_image/issues/3467686 🐛 Should not unset 'title' key in element array Needs review
- https://www.drupal.org/project/media_entity_remote_image/issues/3471458 🐛 D10.3.2 Error "The URL field is required when the field is specified" Active
To me, this seems logical. I suppose someone might want to create a media entity as a placeholder, and add the URL later, but I doubt it.
@peachez Was it just an empty URL field that caused the problem? And why were you saving a media item without that value?
If anyone was able to get past the issue and actually create media remote image entities with empty URL fields, we could consider a hook_update_N() to populate empty URL fields with a placeholder value etc.. Does anyone have media remote image entities with empty URL fields?
Also uploading a patch for anyone who wants it.
After applying patch #2, on a D11.1 site I get the following error when I click "Create a new field" on "/admin/structure/media/manage/remote_image/fields":
The website encountered an unexpected error. Try again later.
AssertionError: "General" must be defined in MODULE_NAME.field_type_categories.yml in assert() (line 183 of core/lib/Drupal/Core/Field/FieldTypePluginManager.php).
Drupal\Core\Field\FieldTypePluginManager->getGroupedDefinitions() (Line: 131)
Drupal\field_ui\Form\FieldStorageAddForm->processFieldDefinitions() (Line: 80)
Drupal\field_ui\Form\FieldStorageAddForm->buildForm()
call_user_func_array() (Line: 528)
Drupal\Core\Form\FormBuilder->retrieveForm() (Line: 279)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 73)
Drupal\Core\Controller\FormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 183)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)
This issue on another module is probably helpful: https://www.drupal.org/project/time_field/issues/3477472 🐛 FieldItemBase category cannot be translatable Active
A couple of questions:
- Since it has been redirected, how would one now view https://www.drupal.org/docs/develop/development-tools/develop-on-windows → to see what was on it?
- How does one actually implement such a redirect? I couldn't see such a feature on a page I maintain. Are special privileges required?
Updated branch 3059845-1 to match the latest 2.x.dev code.
Added support for inline widget display compatible with Drupal 10.
Fixed the "Selected (X of Y):" text. I am not sure it was ever working in the inline version.
Made merge Request against 3.x branch: https://git.drupalcode.org/project/entity_reference_tree/-/merge_request...
The patch can be applied to version 2.4.0.
Regarding the proposed resolution to archive https://www.drupal.org/docs/develop/local-server-setup → and redirect it to https://www.drupal.org/docs/getting-started/installing-drupal/install-dr... → , I think there needs to be a parent/landing page that at least mentions and links to the various valid alternatives to DDEV. If https://www.drupal.org/docs/develop/local-server-setup → disappears, where would such a page be?
To address the concerns with Installing Drupal with DDEV in WSL2 on Windows → :
- As I created it, I am listed as the sole maintainer and consider myself still actively maintaining it. I plan to follow it, check it and update it later this year when I install everything on a new laptop.
- It is very difficult or even impossible to defer to a generic installing-Drupal-on-Linux/Ubuntu guide from a Windows/WSL2-specific guide. Despite them both being Linux, the installation procedures are different.
- It is broad, and I understand the argument to simplify it and make it less 'tutorialish', for example removing the zsh stuff, but at this stage it seems a pity to start dismantling it when it's actually a good and comprehensive guide to setting everything up nicely. Many Windows site builders are in very foreign territory when they get into Ubuntu and DDEV and need all the hand-holding they can get. It's no Acquia Dev Desktop! I found the process very challenging, which is partly why I wrote the guide.
- The Drupal best practice settings → page (the final page in the tutorial) is probably already 'cross-platform' (or could be made to be) and could live outside the guide, where it could be linked to from installation guides for each platform. It should certainly be reviewed by more experienced users than me, and there are probably more things that could be added to it. But I don't know where it should live or if any similar pages already exist.
- As well as, or instead of drupal.org, I should probably put the tutorial on YouTube, and/or somewhere more suited to tutorials.
Besides that, I think Set up local server using Bitnami Drupal Stack → can probably be deleted. Nobody's going to miss that, and there is a reference to its replacement in Installing Drupal on Windows for local usage → .
I do wonder whether the content of Installing Drupal on Windows for local usage → can be integrated into the parent Windows development environment → , to save one page.
@quietone Thank you for reverting your change on that page → . I have made a further tweak to explain that it is part of a larger tutorial, which should help guide users to start at the beginning. I hope that's OK and makes sense.
Explain that page is part of a parent tutorial. Remove a rel="nofollow" attribute.
The change @vetchneons made was on the 3.0.x branch. I merged that change into the 3467184-error-call-to and removed some code that was now redundant as a result of the change. I'm not experienced in the gitlab workflow so I hope I've done that correctly.
Uploading a patch corresponding to the MR !7 in #4 for use in a composer workflow.
nick hope → made their first commit to this issue’s fork.
This also affected me when I updated the Quick Tabs module from 8.x-3.0-alpha7 to 4.0.0 in D10.4.1. I solved it by manually enabling the js_cookie (JavaScript Cookie Library) module.
Correct link to Installing Drupal with DDEV in WSL2 on Windows tutorial and other minor changes.
Correct link to Installing Drupal with DDEV in WSL2 on Windows tutorial and other minor changes.
Correct link to Installing Drupal with DDEV in WSL2 on Windows tutorial and other minor changes.
Correct link to Installing Drupal with DDEV in WSL2 on Windows tutorial and other minor changes.
@quiteone To be frank, I thought it was fine as I had written it, but I do understand the wish to defer to a single source of documentation where possible to avoid redundancy/obsolescence. However, IMO, deferring to the documentation on ddev.readthedocs.io leads to a rather convoluted experience.
I think part of the problem is that I wrote Installing Drupal with DDEV in WSL2 on Windows → (the parent of this document) as a complete, 'hand-holding' tutorial, reflecting exactly what I went through myself to get everything set up nicely, because there is no comprehensive guide out there and it was really tough for me, but I guess Drupal Documentation isn't really for such tutorials. I need to find a home for this tutorial elsewhere (perhaps YouTube, when I next undertake the whole process on a new computer).
If the consensus is that the detail is superfluous and should be removed, I'll go along with it.
@quietone Unfortunately the result of removing those details is that it is now more difficult for the user to understand exactly what is required to get DDEV, Docker & Drupal installed in WLS2. By simply linking to the top-level, cross-platform "Install Drupal using DDEV" page, they are thrown into a chain of documentation that contains lots of information that is redundant in this case, and is quite complicated to navigate, with every chance they will either fail to reach https://ddev.readthedocs.io/en/stable/users/install/ddev-installation/#w... (which is where they need to get to), or to mess things up with unnecessary steps along the way. The now-removed detail guided the user concisely through the process and included useful explanation and tips that are now gone.
@aolvera Which version of SHS did you apply patch #12 to and how did it fail? It is probably better to open a new issue, rather than change this closed feature request into a bug report.
#18 works for me. PHP 8.3.2 (DDEV). Drupal 10.2.6. Facets 3.0.0-beta1.
Good spot @ericgsmith. It does indeed seem to be an incompatibility with the Editor Advanced Link module → . If I uninstall that, then this patch works correctly. Apologies for that oversight.
Editor Advanced Link is quite a widely adopted module (109k sites), so this incompatibility should probably be addressed before (if) this feature is added to Linkit. Not sure which side it would need addressing from.
There are also important views and discussion on the related issues ( example ✨ Show entity title after autocomplete selection instead of internal route (e.g., /node/123) Needs work ) that should be considered.
@klidifia Thanks for testing it.
I'm testing with Drupal 10.2.6, Linkit 7.0.0-alpha1 with a patch downloaded from your last MR. I've tried on an old Drupal D10 project and a near-vanilla D10 project. Tried articles, basic pages, basic HTML, full HTML, default Linkit profile, new "Taxonomy Terms" Linkit profile.
I'm finding that the link window will close correctly for the first link I create in an article, but today I'm getting the route before the term name in the anchor text (reverse of yesterday), like this:
<a href="/taxonomy/term/9" data-entity-type="taxonomy_term" data-entity-uuid="2c20c5cb-dee2-4af4-9408-2394309a3c19" data-entity-substitution="canonical" data-entity-title="Thailand">/taxonomy/term/9Thailand</a>
When I try to create a 2nd link in the same article, I get this console error in Chrome (I'm afraid I'm not much use at interpreting it):
ckeditor5-dll.js?v=40.2.0:5 Uncaught TypeError: Cannot read properties of undefined (reading 'attributes')
at Ar.getChanges (ckeditor5-dll.js?v=40.2.0:5:376656)
at html-support.js?v=40.2.0:5:44080
at $r._callPostFixers (ckeditor5-dll.js?v=40.2.0:5:390254)
at $r._handleChangeBlock (ckeditor5-dll.js?v=40.2.0:5:389512)
at Cn._runPendingChanges (ckeditor5-dll.js?v=40.2.0:5:424836)
at Cn.change (ckeditor5-dll.js?v=40.2.0:5:421831)
at r.on.priority (editorAdvancedLink.js?v=10.2.6:1:7035)
at oe.fire (ckeditor5-dll.js?v=40.2.0:5:604093)
at <computed> [as execute] (ckeditor5-dll.js?v=40.2.0:5:607777)
at f.execute (ckeditor5-dll.js?v=40.2.0:5:112967)
rethrowUnexpectedError @ ckeditor5-dll.js?v=40.2.0:5
change @ ckeditor5-dll.js?v=40.2.0:5
r.on.priority @ editorAdvancedLink.js?v=10.2.6:1
fire @ ckeditor5-dll.js?v=40.2.0:5
<computed> @ ckeditor5-dll.js?v=40.2.0:5
execute @ ckeditor5-dll.js?v=40.2.0:5
execute @ ckeditor5-dll.js?v=40.2.0:5
(anonymous) @ link.js?v=40.2.0:5
fire @ ckeditor5-dll.js?v=40.2.0:5
e.listenTo.useCapture @ ckeditor5-dll.js?v=40.2.0:5
fire @ ckeditor5-dll.js?v=40.2.0:5
t @ ckeditor5-dll.js?v=40.2.0:5
I could do a screen recording with a completely fresh D10 project if that would help, so we can see if/where our steps differ.
@klidifia Thanks for the heads-up on the related issue → .
I made a patch out of #10 and patched 7.0.0-alpha1 with it.
In my testing (linking to taxonomy terms only, which is my use case), if a link to a taxonomy term is inserted in an article without first selecting text, the small link window does not dismiss when the green arrow is clicked. I can dismiss that window by clicking outside it, in the body of the article. Then the link is just shown as a vertical bar (like a pipe symbol). When I save the article, the taxonomy term name is shown, but followed by the term route. e.g. Thailand/taxonomy/term/683, where "Thailand" is the term name.
@Andriy Khomych But the problem of missing term_merge is not resolved.
As far as I can tell, one of @arx-e's suggestions in #8 should be done. If you plan not to do either of those, then there should at least be clear instructions in the module description and Readme file that term_merge must be installed and enabled separately.
By the way, the module description still refers to 7.x only with regard to merge: "merging of terms (using the Term merge module in 7.x)".
Personally, I prefer not to have to manually install a separate module to achieve the merge functionality. So I would tend towards the option of adding the dependencies of the submodule in the main module's composer file. But will that cause problems with minimum stability level because term_merge and term_reference_change are both still in beta, and taxonomy_manager is not? (I don't have the experience to know)
Another option might be to make a 2.0.12 that reverts to 2.0.9 (removing merge functionality and dependencies), and also make a 2.1.0-beta1 that includes merge. But care would be needed not to leave users with more config issues. I guess the consensus might be that it is now too late for that approach.
@Andriy Khomych This doesn't seem to be due to config leftovers. The issue happens on a fresh install of Taxonomy Manager on a test site. 'term_merge (missing)' is shown If I expand 'Taxonomy Manager Merge' at /admin/modules. It can be resolved by installing term_merge manually:
composer require 'drupal/term_merge:^2.0@beta'
drush en term_merge
p.s. Thank you for your efforts in improving Taxonomy Manager.
I don't know why composer is not installing term_merge. It is required in taxonomy_manager_merge/composer.json.
Follow-up issue for 'missing module' problems after updating to 2.0.11: https://www.drupal.org/project/taxonomy_manager/issues/3445744 🐛 Missing modules after updating from 2.0.10 to 2.0.11 RTBC
I had the same issue after the troublesome update to 2.0.10 and then 2.0.11, as described in https://www.drupal.org/project/taxonomy_manager/issues/3444071 🐛 Version 2.0.10 breaks existing installations Needs work .
After trying many things without success, I uninstalled and removed Taxonomy Manager completely:
drush pmu taxonomy_manager
drush pmu term_merge
drush pmu term_reference_change
Removed taxonomy_manager from (`composer remove taxonomy_manager` didn't work. I don't know why)
Removed taxonomy_manager
patch
🐛
Version 2.0.10 breaks existing installations
Needs work
from composer.json
composer update
drush updb
drush cr
Then I installed taxonomy_manager 2.0.11 again:
composer require 'drupal/taxonomy_manager:^2.0'
drush en taxonomy_manager
Now I have a new but related issue. If I expand 'Taxonomy Manager Merge' at /admin/modules it says 'term_merge is missing'. I am not sure why that is, because term_merge is required in /taxonomy_manager/modules/taxonomy_manager_merge/composer.json.
Happy to open this as a separate issue if necessary.
Patch #12 works for me.
This was my experience coming from 2.0.9 in Drupal 10.2:
- Updated 2.0.9 to 2.0.10 via `composer update`.
- term_merge and term_reference_change modules got installed with 2.0.10.
- Ran `drush updb` and got the error "Error: Class "Drupal\term_merge\Form\MergeTerms" not found in include() (line 21 of /var/www/html/web/modules/contrib/taxonomy_manager/src/Form/MergeTermsForm.php) #0 /var/www/html/vendor/composer/ClassLoader.php(576): include()"
- Applied patch #12 in Composer with cweagans/composer-patches => `composer update`.
- `drush updb` => 'yes' at the prompt.
- `drush cex` => 'yes' at the prompt.
- `drush cr`
All seems OK.
On a 2nd site, I added the patch before updating and it went smoothly.
Probable duplicate of https://www.drupal.org/project/media_entity_remote_image/issues/3331639 🐛 Alt field ALWAYS required with Multiple Field remote image url Active . The title and description of that issue should be simplified to the most simple case in which this problem occurs (or expanded to include the case in this issue, if different) and then this issue should be closed.
Thanks for the feedback @figarlin and @ptmkenny. As these are instructions for someone contributing code changes, rather than for someone looking for a patch, I rephrased the section closer to my original phrasing, but emphasized "in addition", and linked to 2 different ways of generating a patch. I think the important word is "consider", so it is only a suggestion rather than a recommendation.
Rephrased section about considering uploading a patch file in addition to making a merge request.
@figarlin Could you please add some rationale for deleting the suggestion about creating a patch file as well? I added that note when I overhauled this page, and still find patches easier to install via Composer.
Nick Hope → created an issue.
Removed superfluous introductory paragraph. Numerous grammar, spelling, and other minor corrections. Changed warning text and marked this page as deprecated because it duplicates Windows development environment → but is not as complete or up-to-date. The effort should be on keeping those guides up to date.
This page should probably be deleted at some point but there may be a few fragments of useful information here that could be included in those other guides first.
Changed Windows Terminal from (optional) to (recommended).
Same here. I updated DDEV and it gave me PHP 8.3.2 and now the warning has gone.
Thanks for the feedback. I'm planning to tackle this next week.
Grammar, phrasing, add links to supported web server and database server software.
We should really call it a bare-metal versus a virtual environment.
But if you need to distinguish between a) Docker-based environments, and b) all the other alternatives on Installing Drupal on Windows for local usage → , is AMP-based development environments the best term?
@hansfn Don't feel bad. I'm also fundamentally in agreement and the work I did on that guide won't go to waste.
I'm ready to crack on with moving some content from Installing Docker, DDEV & Drupal in WSL2 to Local Development Guide. I'm talking about, for example, the Extending DDEV → section, which I think has value.
If the consensus is that some of the new material is too much repetition of DDEV documentation (e.g. the DDEV Commands → section), or too peripheral for drupal.org (e.g. the BrowserSync → section), I could strip it out for d.o. and post the whole start-to-finish thing as a more opinionated tutorial offsite.
If Local Development Guide gets too long, it looks like I could make a guide of it (rather than a page) myself and the existing page could be removed.
Will hang on a bit to see if others have input first.
By the way, there was some feedback on the guide from @rfay (the DDEV guy) on the DDEV Discord at https://discord.com/channels/664580571770388500/1068592266752573440/1200... Haven't followed up his points yet.
Re #30, I agree that much of what I've put in the Windows guide about the DDEV & Drupal installation should probably be put into documentation that applies to all platforms.
In practice, that would mean removing much of Installing Docker, DDEV & Drupal in WSL2 → (after the WSL2-specific stuff at the top) and integrating it into Local Development Guide → .
That's quite a lot of detail to add, and some of it is a little opinionated. Is that OK? It would be a pity to lose that detail completely because I think it helps Windows users to have a step-by-step guide from start to finish so they don't get overwhelmed.
In fact, with that much detail added, Local Development Guide may be better as a multi-page guide rather than just a page. Then, for example, the Drupal best practice settings → page I wrote could also be appropriately edited and moved into it (and further modified if need be).
Re #31, probably not, actually. I think the Windows DDEV guide was much more important than for Mac OS / Linux because of the WSL2 factor and specific considerations that introduced (like simply how best to edit text files).
Also, I think the new recommendation that @eojthebrave has added on the Mac OS page should probably also be added to the Linux page, to focus the recommendation on DDEV.
My aforementioned guide is here: Installing Drupal with DDEV in WSL2 on Windows → . It is written from the perspective of a Windows-using site builder with no Linux experience and limited development experience.
It goes quite deep, sometimes into quite peripheral areas (e.g. Zsh), but as DDEV is now the recommended Drupal development environment, there is no escaping the fact that this environment requires some Linux command line skills, which can be daunting. It's not Dev Desktop! So I hope Windows users will appreciate the hand-holding, detail, and effort to make their experience as least intimidating as possible. This is the guide I wish I had when I undertook the process of transitioning from AMP-stack environment to DDEV myself, a process that I found quite complex and time consuming.
Feedback welcome here or in the docs' 'Discuss' threads.
I and others have also spent quite some time signposting various 'development environment' guides back to the DDEV-related pages, initially with warnings, but more recently with 'note-tips'.
Guides to installing Drupal with DDEV on Mac OS and Linux are still needed within the Mac OS guide → and the Linux guide → . They would not need to go into the detail that my DDEV-on-Windows guide does. One-pagers would probably be enough, and this page from my guide → could be a useful reference to start with. It might be quite a straightforward job for Mac/Linux users to do that, or at least get something in place that can be fleshed out.
Add introductory link to the parent guide. Add "Summary & next steps" section.