The workflow approach really depends on the complexity level of your workflows.
I would start with designing the workflow using SharePoint designer.
Then if customizations are necessary the next step would be to look at creating "Custom actions" in visual studio. This way your workflow will still be modifiable using designer, however, you can encapsulate complex logic with custom code and surface
them as steps in the designer. In my experience most workflows can be completed with this level of customization.
After this you have Visual Studio workflows. You will always be able to export the designer workflow and import that into Visual Studio. Note: Once imported into VS you
cannot convert it back to a designer process.
Additionally there are third party tools like Nintex, K2 and others that provide GUI to create workflows.
It all depends what fits in well with your current and any projected future business requirements.
Next you have asked some workflow related questions. The general answer is that these steps are procedural and are the documented approach to work with workflows.
Finally if you are new to creating workflows then my advice would be to pick up a book and spend two to three days simply learning workflows without tying it into your business functionality you are trying to solve. The goal is to first get familiar
with the process using walk throughs in the book. You have mentioned that online resources fall short and this can be frustrating when you are new to a technology area, hence use a book and supplement it with online references, learn the basics of workflows
then it will help you understand how you should proceed with the actual development you need to do.
Hope this serves as a good starting point for you.
Anand
