The guide is a great start! I think it would be fine to even concentrate more on the textual configuration as this is where 1.x users are coming from and what they are familiar with. See e.g. the services/addons.cfg file, where they could simply list the bindings that they currently have in their addons folder - no need to click through a UI for that.
I would definitely say yes! Actually, I wonder if we can somehow achieve a documentation structure where we can show how to do the same thing through the different options. Note that also HABmin is now an official part of the project, so we do not only have text files, Paper UI, but also HABmin. Installing a new addon can therefore be done through at least 3 different options (yeah, openHAB is about flexibility and not a one-size-fits-all approach, this clearly makes some things more complicated…). Actually “command line / shell” might be even a fourths option…
Does anybody have a good idea, how the different options could be dealt with in the documentation? I wouldn’t want to declare ONE way the right one, but really leave the users a choice. Only the tutorials could decide for one way to do it (the 1.x migration rather leaning towards textual, the beginner tutorial towards Paper UI, etc.).
This isn’t correct - they can be configured, but that needs to be done in the text files. So things defined in text are configured in text, things defined through UI are configured through the UI.
What you refer to though is “device configuration” as discussed here. The only binding that does this is to my knowledge Z-Wave, so for now I would document this aspect in the Z-Wave binding documentation specifically.