Improve documentation

+1

Anybody interested in helping me to document it?

It would be great to do both online documentation and video tutorials

Moved to Webform Mailchimp namespace

+1

Also some of the information on the landing page is inaccurate, for example

If you want to map extra fields, create a sign-up form at your MailChimp account (Signup forms => General forms). Add as many form items as you want, but take into account "Field tag" of each one. Each field you have configured in your Webform, will be mapped there if the "key" value in the Webform matches "Field tag" value in MailChimp. Don't worry about upper/lowercase.

I am currently using 8.x-5.1, and it seems that configurable field mapping has been added in the webform handler, meaning that rather than matching up the mailchimp field tags with the webform field keys, the mapping must explicitly use tokens to get the submitted values, eg, at admin/structure/webform/manage/webform_mailchimp_/handlers>edit:

TEST_TEXT: '[webform_submission:values:simple_test_field]'
NAME: '[webform_submission:values:name]'

Thanks for posting that @autopoietic

I'd like to suggest:

<ol>
  <li>Unzip the files to the "sites/all/modules" OR "modules" directory and enable the module.</li>
  <li>Go to Webforms list page (admin/structure/webform) and click "Edit" on desired  Webform.</li>
  <li>Click Emails/Handlers secondary tab and then click on "Add handler" button.</li>
  <li>Click on "Add handler" button on "MailChimp" row.</li>
  <li>Fill in the form. You should have at least one list in your MailChimp account, and at least one Email field in your Webform.</li>
  <li>If you want to map additional Webform elements to MailChimp List fields, edit the <strong>MailChimp handler</strong> on your form, and in the <strong>Merge vars</strong> section add a line for each:<br><br>MAILCHIMPFIELDNAME: '[drupal_token]'<br>Example:<br>NAME: '[webform_submission:values:name]'</li>
</ol>

Patch attached that updates the README.txt with the changes needed in comment #5, and some coding standards edits.

The change would still need to be applied to the module home page manually.