ENGDOCS-1020

[aevesdocker]

[netlify[bot]]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	9c403f3243c77df1ac41634ac3e6ddfc963bc25d
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/635290d6e20112000acc592d
😎 Deploy Preview	https://deploy-preview-15857--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[hyu]

Looks good! Here are the changes I noticed:

• Simplified and standardized titles in header (nice!)
• Removed "About Docker Desktop" screenshot from overview, since its size was giving it undue importance.
• In Overview, frame install options as 3 scenarios. (I like that this explicit hierarchy directs most users to 1.)
• Removed "where to go next" from plugin install page, making it more consistent with the standalone install page.

All of these seem like solid improvements to me. Let me know if I missed anything, though!

 

Reference

(I found myself wondering what had changed in the recent iterations. Hope this is useful to you too!)

Merged 7/2	Merged 8/26	Current PR
ENGDOCS 711	PR 15494

[hyu]

This is a nit that's possibly out of scope!

...

When a tip box immediately follows a heading, there doesn't seem to be enough vertical space. For example, in this plugin install section:

  The spacing is better elsewhere in docs, where there's a line between the header and the tip. Like on Install Docker Desktop:

[hyu]

Not blocking, but I do wonder whether it's possible to offer a bit more context on why a user would choose to install Compose standalone?

For Scenario two, we do imply that you might want the plugin if you already have Docker Engine and CLI, and don't want to install DD for whatever reason. Is there some extra bit of info we can similarly offer for Scenario three?

(I apologize that I myself don't actually know how to contextualize this! My vague understanding is that we don't much support this install route, but offer it nonetheless for legacy reasons? CCing @StefanScherer in case he might have more context.)

[StefanScherer]

Yes, installing compose v2 standalone is only for legacy reasons, maybe users have lots of scripts that use docker-compose instead of docker compose and don't want to migrate or just don't know that there now is the plugin. The Windows Server use case is also probably a very rare one, that's probably only for test purposes. Another use case might be to have the cli and compose installed on Mac or Windows to use them with a manually local VM or a remote Docker Engine.

Looking at package managers that help installing docker-compose show at least some interest on Mac via homebrew, but on Windows I was never asked to update the docker-compose chocolatey package beyond v1.

[aevesdocker]

Thank you for the feedback @hyu and extra context @StefanScherer.

Re: adding extra context for scenario three. Seeing as we no longer support this option, and there are simply edge cases as to why someone would choose this option, I wonder if it's better simply to add just a warning note saying we no longer support it and make this scenario as unappealing as possible? Users who still decide this is the option for them surely know what they're doing and are advanced users.

Re: tip box formatting @hyu, yes unfortunately out of scope for this PR as it involves mucking around with the CSS. I have a weekly working session with Shadi to fix these kinds of issues throughout the docs, so shall add it to the agenda

[hyu]

This seems like the right approach!

Seeing as we no longer support this option, and there are simply edge cases as to why someone would choose this option, I wonder if it's better simply to add just a warning note saying we no longer support it and make this scenario as unappealing as possible? Users who still decide this is the option for them surely know what they're doing and are advanced users.