[#4341] Add initial Sales page in the Styleguide (#63)

* Add initial Sales page
* Move the two new pages into 'Product' section
* Fix the merge issue from the previous commit to master
* Changes to the Sales pages after review
* Add changes to Sales pages

docs/office/leave.rst

@@ -1,11 +1,9 @@
 Leave / Holiday
 ###############
 
-<<<<<<< HEAD:content/leave.rst
-:menu_order: 020
+.. contents::
+
 
-=======
->>>>>>> master:docs/office/leave.rst
 General
 =======
 

docs/office/onboarding.rst

@@ -1,13 +1,12 @@
 Onboarding
 ##########
 
-<<<<<<< HEAD:content/onboarding.rst
-:menu_order: 018
-:url: /onboarding.html
-:save_as: onboarding.html
+.. contents::
+
+
+Introduction
+------------
 
-=======
->>>>>>> master:docs/office/onboarding.rst
 This page is used to organize tasks and track the onboarding process for new members.
 You can see past/active tasks in the `onboarding repo <hhttps://github.com/chevah/onboarding/>`_.
 

docs/office/security.rst

@@ -1,11 +1,6 @@
 Security
 ########
 
-<<<<<<< HEAD:content/security.rst
-:menu_order: 010
-
-=======
->>>>>>> master:docs/office/security.rst
 .. contents::
 
 

docs/office/work.rst

@@ -1,13 +1,9 @@
 Work
 ####
 
-<<<<<<< HEAD:content/work.rst
-:menu_order: 019
-
-=======
->>>>>>> master:docs/office/work.rst
 .. contents::
 
+
 General
 =======
 

docs/product/sales.rst

@@ -0,0 +1,80 @@
+Sales and Marketing
+###################
+
+.. contents::
+
+
+Introduction
+============
+
+This page briefly describes operational Sales details.
+
+
+Product Demo
+============
+
+
+Demo text template to use
+-------------------------
+
+Please send your criteria of requirements so that we can
+better answer your questions and prepare the session to meet all your
+requirements.
+
+For those involved in procurement, please contact the Sales team.
+
+**Pre-demo session:**
+
+We recommend obtaining the trial version and installing until the
+`initial stage <https://www.sftpplus.com/documentation/sftpplus/latest/getting-started.html>`_
+
+In that way, you are able to continue after the demo session.
+
+Phone bridge is recommended, if not, use a VOIP headset with dedicated headset.
+We do not recommend using the microphone included in laptops due to poor sound
+quality.
+
+
+When demo session is agreed ask for the following:
+--------------------------------------------------
+
+* Dates available
+* Times available (and local timezone, so that we know what GoToMeeting
+  toll free / long distance numbers to provide)
+* Number of attendees (max 4 attendees incl 1 organiser and 1 co-organiser in
+  case or max 5 attendees if 1 organiser)
+* Platform
+* Protocols
+* List or criteria of requirements to know what to set up in advance
+
+
+Sending out demo session details
+--------------------------------
+
+* Wait for people to join in the first 10 minutes. If there are no-shows, the
+  session can be dropped and rescheduled.
+
+
+Marketing / Promotional Materials
+=================================
+
+To save materials, or to obtain past materials, the `design repo <https://github.com/chevah/design>`_ is available.
+
+
+Announcing a new release to the email list
+------------------------------------------
+
+After the website is updated and News item published, we send a newsletter:
+
+1. Go to Campaigns in Mailchimp.
+
+2. Select 'Replicate' besides 'NEW: ACME Release Announcement'.
+   If it is a security release, use the Security Advisories email list.
+
+3. Select the News Announcements email list.
+
+4. Update the subject and email with the News text used to announce the
+   new release. You can use the text in the News article.
+
+5. Select Send. Before sending the final email, preview first by going
+   to 'Preview and Send' on the top menu. Select 'Send a test email'.