DSM 323 and 324 community pages (#196)

* Update community pages

- new product page
- moved feedback guidance onto a separate page
- edited the UCD community page

* Added new page on feedbcak

* Corrected published dates

src/your-community/ask-for-and-give-feedback.md

@@ -0,0 +1,47 @@
+---
+layout: "layouts/guidance.njk"
+section: "Community"
+title: "How to ask for and give feedback"
+description: "Get tips on asking for feedback in community sessions and check how Defence expects you to give feedback."
+dateUpdated: 2024-05-05
+eleventyNavigation:
+  key: "Content"
+  url: "/content/"
+---
+
+As part of the community, you are encouraged to share what you are working on. You can ask to do this on a community call. 
+
+## How to ask for feedback
+
+When you ask the community for feedback, here are a few things you need to do.
+
+### Set the context
+
+Without taking too long, tell the story of your service. Start with what your service does, who your users are and what they are trying to do.
+
+### Say what kind of feedback you want
+
+Tell people what you want to find out. For example, if there are existing patterns you can reuse or how close you are to meeting the GOV.UK Service Standard.
+
+### Do not be defensive
+
+Feedback is about your service, not you. Avoid deflecting questions, it’s okay to say that you’re not sure. Take notes so that you don’t need to respond to every point.
+
+## How to give feedback
+
+In the Ministry of Defence, you are expected to give feedback in a kind and respectful way.
+
+### Give specific and actionable feedback
+
+All feedback should be constructive. Include details of what you’re thinking, what you would change and why. Avoid phrases like "I don't like it" or "That never works".
+
+### Be kind and respectful
+
+You can be honest and specific without using hurtful or aggressive language. Start sentences with phrases like “Have you considered”, “You might like to try” or “Think about”.
+
+### Keep an open mind
+Everyone has different experiences and opinions. Remember that your feedback is just one perspective. Be willing to consider feedback that differs from your own.
+
+### Be present
+The team presenting their service deserves your full attention. Try not to be distracted by other work. In remote sessions, have your camera on and show that you are actively listening.
+

src/your-community/index.md

@@ -19,10 +19,14 @@ Joining a community helps you:
 
 Anyone working in Defence can join a community. 
 
-You can join more than one community.
+You can join more than one of these communities:
 
-- [Content](/your-community/content/)
-- [Software development](/your-community/software-development/)
-- [User-centred design](/your-community/user-centred-design/)
+<ul>
+  <li><a href="/your-community/product/">product</a></li>
+
+  <li><a href="/your-community/software-development/">software development</a></li>
+
+  <li><a href="/your-community/user-centred-design/">user-centred design</a></li>
+</ul>
 
 If you have a community in Defence that meets regularly, we can share the details here. Find out how to [get in touch](/get-in-touch/).

src/your-community/product.md

@@ -0,0 +1,74 @@
+---
+layout: "layouts/guidance.njk"
+section: "Community"
+title: "Content"
+description: "Anyone creating content for digital services in Defence can join the content community. Find out how to get involved."
+dateUpdated: 2024-03-05
+eleventyNavigation:
+  key: "Content"
+  url: "/content/"
+---
+
+Anyone creating content for digital services in Defence can join the content community. 
+
+## Who you will meet
+
+In this community, you will meet:
+
+- content designers
+- content strategists 
+- technical writers 
+- graphic designers
+- other people creating content across Defence
+
+## Community calls
+
+Join the content community call every second Thursday at 2:30pm.
+
+We discuss the latest content news and updates. We share insights, issues and what we’re working on. 
+
+{{ component('inset-text', {
+  html: 'You must only share OFFICIAL information. <a href="/security-classifications/">Find out about security classifications</a>.'
+}) }}
+
+### Ask for an invitation
+
+You need to work in Defence to join the community calls.
+
+Using your Ministry of Defence email, send a message to: [[email protected]](mailto:[email protected]?subject=Join%20content%20community%20calls). 
+
+Include your full name, your role and the project you’re working on.
+
+## Ask for feedback
+
+Community calls are a great place to ask for feedback on your service, a feature or an issue. Here are a few things to remember.
+
+### Set the context
+
+Without taking too long, tell the story of your service. Start with what your service does, who your users are and what they are trying to do.
+
+### Say what kind of feedback you want
+
+Tell people what you want to find out. For example, if there are existing patterns you can reuse or how close you are to meeting the GOV.UK Service Standard.
+
+### Do not be defensive
+
+Feedback is about your service, not you. Avoid deflecting questions, it is okay to say that you are not sure. Take notes so that you do not need to respond to every point.
+
+## How to give feedback
+
+You are expected to give feedback in a kind and respectful way.
+
+### Give specific and actionable feedback
+
+All feedback should be constructive. Include details of what you are thinking, what you would change and why. Avoid phrases like "I don't like it" or "That never works".
+
+### Be kind and respectful
+
+You can be honest and specific without using hurtful or aggressive language. Start sentences with phrases like “Have you considered”, “You might like to try” or “Think about”.
+
+### Keep an open mind
+Everyone has different experiences and opinions. Remember that your feedback is just one perspective. Be willing to consider feedback that differs from your own.
+
+### Be present
+The team presenting their service deserves your full attention. Try not to be distracted by other work. In remote sessions, have your camera on and show that you are actively listening.

src/your-community/user-centred-design.md

@@ -3,73 +3,40 @@ layout: "layouts/guidance.njk"
 section: "Community"
 title: "User-centred design"
 description: "Anyone in a user-centred design role in Defence can join the community. Find out how to get involved."
-dateUpdated: 2024-03-05
+dateUpdated: 2024-06-06
 eleventyNavigation:
   key: "Your community"
   url: "/your-community/"
 ---
 
-Anyone working on digital services in Defence is welcome to join the user-centred design (UCD) community. 
+Anyone working on technology and services in Defence can join the user-centred design (UCD) community. 
 
 ## Who you will meet
 
 In this community, you will meet:
 
-- user researchers and data analysts
-- service designers and product designers
+- content designers and people who publish content
 - interaction and graphic designers
-- content designers, managers and strategists
-- product managers and business analysts working with users
-
-## Community calls
-
-Join the UCD community call on the third Thursday of the month at 2pm. 
-
-Calls are 55 minutes. We discuss things like accessibility, tools available in Defence and cross-government collaboration.
-
-{{ component('inset-text', {
-  html: 'You must only share OFFICIAL information. <a href="/security-classifications/">Find out about security classifications</a>.'
-}) }}
-
-### Ask for an invitation
-
-You need to work in Defence to join the community calls.
-
-Using your Ministry of Defence email, send a message to:
-[[email protected]](mailto:[email protected]?subject=Join%20UCD%20community%20calls). 
-
-Include your full name, your role and the project you’re working on.
-
-## Ask for feedback
-
-Community calls are a great place to ask for feedback on your service, a feature or an issue. Here are a few things to remember.
-
-### Set the context
-
-Without taking too long, tell the story of your service. Start with what your service does, who your users are and what they are trying to do.
-
-### Say what kind of feedback you want
-
-Tell people what you want to find out. For example, if there are existing patterns you can reuse or how close you are to meeting the GOV.UK Service Standard.
+- product owners interested in user-centred design
+- service and product designers
+- user researchers and data analysts
 
-### Do not be defensive
+## Get feedback
 
-Feedback is about your service, not you. Avoid deflecting questions, it is okay to say that you are not sure. Take notes so that you do not need to respond to every point.
+You can ask the user-centred design community to give you feedback on your service, a new feature or an issue. 
 
-## How to give feedback
+For example, you have a new feature and you are not sure which GOV.UK or Defence design patterns you should use. 
 
-You are expected to give feedback in a kind and respectful way.
+Check [how to ask for and give feedback](/your-community/ask-for-and-give-feedback).
 
-### Give specific and actionable feedback
+## Join community calls
 
-All feedback should be constructive. Include details of what you are thinking, what you would change and why. Avoid phrases like "I don't like it" or "That never works".
+We run a monthly UCD call. We discuss topics like accessibility, tools available in Defence and cross-government collaboration.
 
-### Be kind and respectful
+We also run regular calls for content designers, interaction designers and user researchers. 
 
-You can be honest and specific without using hurtful or aggressive language. Start sentences with phrases like “Have you considered”, “You might like to try” or “Think about”.
+To join community calls, you must work in the Ministry of Defence or with one of our suppliers. 
 
-### Keep an open mind
-Everyone has different experiences and opinions. Remember that your feedback is just one perspective. Be willing to consider feedback that differs from your own.
+Using your Ministry of Defence email, [ask to join the community calls](mailto:[email protected]?subject=Join%20UCD%20community%20calls). 
 
-### Be present
-The team presenting their service deserves your full attention. Try not to be distracted by other work. In remote sessions, have your camera on and show that you are actively listening.
+Include your full name, your role and the project you are working on.