File: content/manuals/compose/how-tos/multiple-compose-files/_index.md
Issue
The overview page provides contradictory guidance about which approach is "quickest":
The quickest way to work with multiple Compose files is to merge Compose files using the -f flag in the command line to list out your desired Compose files. However, merging rules means this can soon get quite complicated.
Why this matters
A reader trying to choose between merge, extends, and include would be confused by this guidance. The page says merging is the "quickest way" but immediately warns that it "can soon get quite complicated." This creates uncertainty:
- If it's the quickest, why does it get complicated?
- Should I use it or not?
- Is "quickest" referring to learning curve, implementation time, or something else?
The contradiction undermines the reader's confidence in choosing the right approach for their use case.
Suggested fix
Rewrite this paragraph to be more precise about what "quickest" means and when each approach is appropriate. For example:
"The simplest way to work with multiple Compose files is to merge them using the -f flag. This works well for basic overrides, but merging rules can become complex for larger applications with many services and configuration options.
Docker Compose provides two other options that offer more control for complex scenarios:"
Or, if merge is genuinely the recommended starting point despite complexity:
"You can work with multiple Compose files in three ways. Most users start by merging Compose files using the -f flag, though you may want to use extends or include as your configuration grows more complex."
The key is to remove the contradiction and give clear guidance about when to use each approach.
Found by nightly documentation quality scanner
File:
content/manuals/compose/how-tos/multiple-compose-files/_index.mdIssue
The overview page provides contradictory guidance about which approach is "quickest":
Why this matters
A reader trying to choose between merge, extends, and include would be confused by this guidance. The page says merging is the "quickest way" but immediately warns that it "can soon get quite complicated." This creates uncertainty:
The contradiction undermines the reader's confidence in choosing the right approach for their use case.
Suggested fix
Rewrite this paragraph to be more precise about what "quickest" means and when each approach is appropriate. For example:
"The simplest way to work with multiple Compose files is to merge them using the
-fflag. This works well for basic overrides, but merging rules can become complex for larger applications with many services and configuration options.Docker Compose provides two other options that offer more control for complex scenarios:"
Or, if merge is genuinely the recommended starting point despite complexity:
"You can work with multiple Compose files in three ways. Most users start by merging Compose files using the
-fflag, though you may want to use extends or include as your configuration grows more complex."The key is to remove the contradiction and give clear guidance about when to use each approach.
Found by nightly documentation quality scanner