[workspace]
# Optional key, inferred if not present
-members = ["path/to/member1", "path/to/member2"]
+members = ["path/to/member1", "path/to/member2", "path/to/member3/*"]
# Optional key, empty if not present
exclude = ["path1", "path/to/dir2"]
dependencies residing in the workspace directory become members. You can add
additional packages to the workspace by listing them in the `members` key. Note
that members of the workspaces listed explicitly will also have their path
-dependencies included in the workspace. Finally, the `exclude` key can be used
-to blacklist paths from being included in a workspace. This can be useful if
-some path dependencies aren't desired to be in the workspace at all.
+dependencies included in the workspace. Sometimes a project may have a lot of
+workspace members and it can be onerous to keep up to date. The path dependency
+can also use [globs][globs] to match multiple paths. Finally, the `exclude`
+key can be used to blacklist paths from being included in a workspace. This can
+be useful if some path dependencies aren't desired to be in the workspace at
+all.
The `package.workspace` manifest key (described above) is used in member crates
to point at a workspace's root crate. If this key is omitted then it is inferred