|
|
|
|
|
by TuringTest
716 days ago
|
|
I would not remove them, but place them elsewhere, linked from the point you should run them at the install process. It's very useful to have a complete 'getting started' page that get you from zero to working, without assuming that the reader understands what every intermediate step means. But as you said, the parts that are dependencies for other products can be encapsulated so that savvy users can skip them easily. |
|
Focus the energy of your own docs on your own product itself, and let the docs of your dependencies cover most of the general steps regarding those.