The contact page should clearly indicate how users can contact us for which reason, as listed below. The main concern we are addressing is that currently, users do not know how to reach us for the different topics they require.

link to mockup

• It has to be clear why users are reaching out, there has to be a format for them to add their enquiry, so that we can connect them to the right person
• All topics go to contact.wikibase@ and will be filtered there to reach ComCom or Partnerships accordingly
• The contact page should be easily accessible from anywhere on the platform, i.e. it should be very easy for the user to find how to contact us, this might require multiple references on the platform . The means that we should repurpose the existing contact link in the footer. We should also re-purpose the link on the landing page.
• An FAQ section should be linked to catch the low-hanging fruit recurring questions. Should link to: https://www.mediawiki.org/wiki/Talk:Wikibase/FAQ, Dan is expanding this with more Wikibase.cloud content as we go
• Consider adding a link to the project page for users to keep track of updates: https://meta.wikimedia.org/wiki/Wikibase/Wikibase.cloud
• There should be a link to the Telegram group https://t.me/joinchat/FgqAnxNQYOeAKmyZTIId9g as well to make sure users can join community discussions about Wikibase.cloud, and the mailing list https://lists.wikimedia.org/postorius/lists/wikibase-cloud.lists.wikimedia.org/ as another platform for discussions and updates

A/C:

• There should be a form appearing as described in the mock up
• It should be accessible to logged-in and not-logged-in users
• On submission an email should be sent to contact.wikibase@ email (not on phab to reduce spam)
• The Subject line should always contain [Reason for message]
• The sender email should be adjusted to the Reason for message section (details in backend ticket)
• The contact link in the footer should target the new page
• The contact link on the landing page should target the new page
• It should be protected from spam
• snackbar displays success message when message was successfully submitted

N.B : we expect to be able to break this down into at least two parts (one frontend change and one backend change)
We would also like to make some efforts to integration test this thing being particularly mindful of the difficulties related to relatively unrestricted user input