> @Stefan> Why are you against adding the old information as a second path? If something fails with oomph users should be> still able to workaround with the manual installation path.
I'm concerned about two things:
1. Having to keep both the manual instructions and oomph setup in sync. If we add a new build dependency or required preference, we don't want the manual instructions to get.
2. We don't want to overload new users with unnecessary extra steps (those who just want to contribute to the code and aren't trying to do anything advanced).
I'd suggest we deal with (1) by auto-generating the manual instructions from the oomph setup files. Since the .setup files are just declarative XML, it shouldn't be too hard to auto-convert them into an HTML page - much like we do with extension point schemas. In that case, there would only be one source of truth - the oomph scripts - but people would still have access to user-readable doc if they want it.
We could deal with (2) by putting the manual steps on a separate page and linking to it from the main page. Right up at the top, it could say "if you don't want to run the installer and would prefer to set up your environment manually, please see <these steps>". That way, anyone scrolling through the page quickly won't be overloaded with instructions but anyone who is actually looking for the manual steps can find them.
- Stefan