Docs: Updates notes around submitting issues

Author: chrispenny

CODE_OF_CONDUCT.md

@@ -1,5 +1,5 @@
 # Contributor Code of Conduct
 
-This project adheres to No Code of Conduct.  We are all adults.  We accept anyone's contributions.  Nothing else matters.
+This project adheres to No Code of Conduct. We are all adults. We accept anyone's contributions. Nothing else matters.
 
 For more information please visit the [No Code of Conduct](https://github.com/domgetter/NCoC) homepage.

CONTRIBUTING.md

@@ -2,10 +2,24 @@
 
 ## Submitting issues
 
-Please don't be scared to raise issues that you find while using this module, but please be sure to perform a quick search through open and closed ticket to see if the same (or similar) issue has already been raised. If you find an existing issue that has been closed, feel free to raise a new issue referencing the old, or you can request that the existing ticket be reopened.
+Please don't be scared to raise issues that you find while using this module, but please be sure to perform a quick
+search through open and closed ticket to see if the same (or similar) issue has already been raised. If you find an
+existing issue that has been closed, feel free to raise a new issue referencing the old, or you can request that the
+existing ticket be reopened.
 
 [Raise an issue](https://github.com/silverstripe-terraformers/silverstripe-embargo-expiry/issues)
 
+### What to include
+
+Please consider adding the following information to your issue:
+
+* What version of E&E is your project using?
+* What version of `silverstripe/framework` is your project using?
+* How are you using E&E? EG: Is E&E applied to your page, or is it applied to (say) the Blocks on the page?
+* Steps to reproduce the issue (ideally including screenshots of each step you take)
+* Any other modules that you believe could be interacting with E&E to cause the issue
+
 ## Contributing code
 
-Please try your best to conform to PHPCS coding standard. We won't get mad if you don't, but it will make your pull requests go a lot faster.
+Please try your best to conform to PHPCS coding standard. We won't get mad if you don't, but it will make your pull
+requests go a lot faster.

docs/en/configuration.md

@@ -2,7 +2,9 @@
 
 ## Allow/disallow editing of content while an Embargo date is set
 
-When a `PublishTargetJob` is run, it will publish whatever the current draft state is. In your project, you might want to allow or disallow the editing of content once an Embargo date is set. Disallowing editing of content will mean that once an Embargo date is set, you'll know that no additional changes have been made to the record.
+When a `PublishTargetJob` is run, it will publish whatever the current draft state is. In your project, you might want
+to allow or disallow the editing of content once an Embargo date is set. Disallowing editing of content will mean that
+once an Embargo date is set, you'll know that no additional changes have been made to the record.
 
 By default, editing while an Embargo date is set is **enabled**.
 
@@ -20,7 +22,9 @@ My\Awesome\DataObject:
 
 ## Enforce sequential Embargo and Expiry dates
 
-When setting an Embargo and Expiry date, you may wish to allow or disallow users setting an Expiry date that is **prior** to the Embargo date. Allowing a user to have dates in either order could be useful if they have a use case for un-publishing an already published page for a small window of time before it is automatically published again.
+When setting an Embargo and Expiry date, you may wish to allow or disallow users setting an Expiry date that is
+**prior** to the Embargo date. Allowing a user to have dates in either order could be useful if they have a use case for
+un-publishing an already published page for a small window of time before it is automatically published again.
 
 By default, sequential dates are **not** enforced (Expiry dates can be for earlier than the Embargo date).
 

docs/en/fluent-support.md

@@ -4,4 +4,5 @@
 
 `EmbargoExpiryFluentExtension` is provided to add support for DataObject that have `FluentVersionedExtension` applied.
 
-The expected behaviour is that you can now set an Embargo & Expiry date in each Locale separately from each other, and when those dates pass, the Jobs will publish/un-publish only the record in that Locale.
+The expected behaviour is that you can now set an Embargo & Expiry date in each Locale separately from each other, and
+when those dates pass, the Jobs will publish/un-publish only the record in that Locale.

docs/en/installation.md

@@ -14,7 +14,8 @@ SilverStripe\CMS\Model\SiteTree:
     - Terraformers\EmbargoExpiry\Extension\EmbargoExpiryExtension
 ```
 
-If you are applying the extension fo a DataObject other than `SiteTree`, ensure it has the `Versioned` extension applied so it can be published/unpublished.
+If you are applying the extension fo a DataObject other than `SiteTree`, ensure it has the `Versioned` extension applied
+so it can be published/unpublished.
 
 ```yml
 MyCustomDataObject:
@@ -25,6 +26,7 @@ MyCustomDataObject:
 
 Now run a `dev/build?flush=all` in your browser, or from the command line via `vendor/bin/sake dev/build flush=all`.
 
-Finally, ensure you've set up [queuedjobs](https://github.com/symbiote/silverstripe-queuedjobs) correctly to execute your jobs periodically.
+Finally, ensure you've set up [queuedjobs](https://github.com/symbiote/silverstripe-queuedjobs) correctly to execute
+your jobs periodically.
 
 For more information please see [configuration](configuration.md).