A common type of page you will want to create is one that shows the most recent articles. Articles are just like pages, but they are structured and organized by date. This allows you to publish information to your GC Articles collection and lets your readers consume the most up to date information about your program or service first, just like other news feeds.

The main fixture of this page is a block called ‘Latest Posts’ You can see it in place below the separator showing the 3 most recent articles.

• Build your article with blocksJanuary 18, 2023

  

• Type you titleDecember 15, 2022
  • Whatever I like
  • And it goes on

  Chief Executive Officer	A/ Anatole P.
  	Chief of Staff	A/ Steph G.
  		Executive Assistant	A/ Nafissa (Emmanuel J-S on secondment)
  		Issues Manager	Steph G.
  	ED / COO	A/ John M
  	Dir. Tal & Ops	A/ Sana Q.
  	Dir. Policy SRE	A/ Nisa M.
  	ED of Partnerships	Wendy L.
  	Dir. of Outreach	Chelsea N.
  	ED of Platform	A/ Leanne Labelle
  	Dir. Strategic Eng.	Alex M.

  

• Add a title to the articleNovember 7, 2022

  Information notice about this page

  Don’t trust it, it’s just dummy data

  

  Type stuff here
• Block editorOctober 28, 2022
  Click here

  	a

  

• Use this editor that’s presented to youOctober 27, 2022

  Start typing right away

  

  Here

  dfsdfsfsf

  sdfsfsdfs

  Got that here

  Here
• Here I can write a title in H1October 24, 2022

  Overall effort

  Vulnerabilities

  One developer assigned to GC Articles on a 20% basis (1 day a week) should be enough to handle the weekly minor and patch upgrades as well as prepare for planned major releases of WordPress Core and its dependencies.

  The only unknown is the release frequency of security fixes, as the number and severity of these is unpredictable.  The Platform Core patching standards outline the response time based on severity and exploitability.  As a result, extra time may be required if a critical fix is released unexpectedly.

  Scaling

  If the growth of GC Articles begins to impact performance, it should take one developer 5 days to performance test and deploy the following:

  • horizontal and vertical scaling changes; and/or
  • CloudFront cache retention updates.

  Note that this estimate is based on the assumption that the GC Articles use case will remain the same:

  • Majority of requests are for static content that can be cached by CloudFront.

  If the use case changes to include a larger number of dynamic, uncacheable requests, more time may be required to make changes to the GC Articles infrastructure.

  Appendix

  

  Figure 1: GC Articles vulnerabilities across all components

  

  Figure 2: GC Articles vulnerabilities in cds-base plugin

• Create a post with just typingOctober 24, 2022
  • xcvxvxvcx

  

  write stuff

• Findings October 21, 2022

  Using the triangulation approach, some findings were collected to test the hypothesis. With that there was a presentation of findings in a number of meetings, including the Product Brief meeting to share findings to Product Leads, in the Committee to gather some insights as well as in the CDS Platform hall. 2021 12 CX Product Briefing

  Conduct a discovery of Platform Clients 

  Task	Discovery Activities Findings
  To identify and conduct a deep dive on one client profile that is of high-value across platform products and identify if this targeted client is a promoter or a gatekeeper	Current Client is a Developers’ Manager – More details in Miro  Manager of Developers / Communication representatives with mid to high knowledge of tech. The Manager can easily test a platform solution but would need dev/ comm teams to implement it. They get recommendations/ blessings from the Security team on which products are safe/ secure to use. They tend to work in a GC inter-department that is advanced in Digital Transformation. The manager is a promoter to deliver product adoption. Security team could be gatekeepers depending on the relationship and views they have on digital solution and the sensitivity of data that would be gathered depending on the digital solutions
  To identify the themes that make a positive client experience via a Case Study of a client who had positive experiences adopting/ adapting GCNotify	Security compliance teams approved digital solutions Digital Transformation journey was well advanced Active presence of Developers’ Community on GitHubDigital literacy of teams needs to be medium to high Culture of advancing digital solutions was importantDepartment Digital maturity Trust/ Collaboration is important when digital solutions are being adopted. CDS Platform solutions are well received as they are already in the Government that only makes them seem to be secureThe Security Team approved/ blessed which product the client can adopt. Department Data Sensitivity, the data being exposed/ shared using digital solutions determines if they will be easily adopted/ accepted.Dev Community (Niche Market) was specific to GC Notify

  Create an end to end Client journey

  Task	Findings
  To develop a journey map for the platform client selected.	Current Client Journey Map  More details in Miro Insights from the Client  journey map show there was no indication of asking for security compliance documents. Security team members themselves suggested the solutions in most cases. The Clients were more interested in how to adopt the digital solutions in the most efficient way. Their developers teams ended up handling testing, installing and adoption of the product within the department’s systems. CDS Platform Digital solutions being in the public made it trustworthy
  To identify the gaps in the client’s experience across all the Platform touchpoints, for different client interactions.	Client was identified to be Niche driven to Developers community i.e. High Digital Literacy with high presence on GitHub specific to GC NotifyNo training or customer support available for non-tech team even though there could be use cases for non-tech clients/ users Limited use cases of developers communities Self-serve approach prevents  non-tech communities from adopting advanced digital solutions
  To identify actions that can be implemented by the teams to improve the journey.	The importance of implementing team consistency clients’ experience to brand CDS Platform digital solutions was indicated, so it’s consistent in all the different digital solutions. Determine space where Platform Digital services exist. Evaluate  the must haves for a digital solutionsIdentify which GC teams have conditions preventing  adoption of the CDS Platform Digital Solutions to fine-tune actions for implementations Onboarding, training and support for Platform Digital Solutions required

  Conclusions 

  Final thoughts and next steps 

  The Client Experience research activities solidified the need to have a Client Experience team. Pinning down the current client composition identified the need to understand the context of the client and the needs that are supposed to be met. While security compliance is one factor that impacts the adoption of CDS Platform digital solutions, there are other factors that need to be considered to establish a positive client experience throughout the process, as listed below: 

  • Digital Transformation journey is well established  within the team 
  • Digital literacy of teams is considered  medium to high 
  • Active engagement of Developers’ Community on GitHub
  • Culture of advancing digital solutions was important
  • Data security sensitivity is low and security requirements were less 

  Where the Department’s data sensitivity was less of a concern, security requirements were generally less complicated. Having a view of what CDS Platform Digital solutions is working on, would provide insight to clients on requirements, beyond security compliance, that would make the clients’ experience positive and trustworthy. It is at this stage that clients identify other factors that might make product adoption acceptable to security teams and  other teams involved.

  Connecting with Security Compliance Assessors is challenging. Their work is intricate and their time is limited. Recruiting Security Compliance Assessors requires fair compensation and can take  upwards of six months. The clients stated that they hoped to get “the blessing” of the security compliance teams/ assessors to use specific digital products, which made it easy to adopt the products. Being a digital agency within the government also played a big role on how digital products were adopted. It would be more impactful to earn trust and have measures that are digital solutions driven unlike existing paper heavy and long processes.

  Clients rely on the  Security team to suggest and approve digital solutions to be adopted and or adapted. Clients cannot adopt digital solutions that have not been  approved by the Security Team.  To understand Client’s needs, and their context, is key for CDS Platform Digital solutions to be adopted. It’s important to build relationships with clients by sharing what CDS Platform is working on as buy-in for early adoption opportunities, to identify potential questions from security teams and prepare documentation ahead of time. 

  Next steps would be to map out GC department teams with conditions to adopt CDS Digital solutions. This would map segments to which the CDS Platform Business unit could  start collaborating with to identify what works in favorable contexts and adapt to conditions of future clients. 

  Recommendations

  The CX (Client Experience) team is needed to support all product teams developing consistent positive experiences throughout the product adoption cycle. A representative of Client Experience in each team would  help identify security compliance needs and maintain consistency across CDS Platform Digital Solutions. 

  Working with other government agency bodies, like GC(UK), may lead to insights on products in development, along with  increased collaboration and learning from additional government agencies. 

  There was a connection with DND Security team assessors who were willing to work with Platform CDS to share how they perceive the Security Compliance processes in all areas of different product adoption. This would be a great opportunity for the next phase of Client Experience with focus on Security Compliance processes. 

  Lessons Learned

  1. CX (Client Experience) is needed for product development teams to ensure that that our past/current clients have positive experience so as to adopt future CDS Platform products 
  2. Identify a Case Study helped zoom into specific objectives which made this project manageable 
  3. Having an ongoing meeting like the Committee to move the conversation was helpful to build relationships with existing client participants who were open to give honest feedback
  4. The Committee was useful in identifying if clients would adopt other CDS Platform digital solutions and to start thinking about possible roadblocks 
  5. Recruitment of participants was challenging,  especially when you are not from the public sector. Aligning with internal colleagues with existing relationships with public servants was required.  
  6. Creating a pool of participants gathered from all CDS past and current colleagues to maintain relationships would be useful to keep clients engaged.
  7. Security Compliance Assessors were busy and difficult to connect with as their time is severely limited.
  8. Building relationships with Security Assessors and including them in client engagement would be very impactful 

  Artifacts 

  Figure – Mapped out GC Notify Department Adoption 

  Client Experience Journey Map 

  Findings 

  Using the triangulation approach, some findings were collected to test the hypothesis. With that there was a presentation of findings in a number of meetings, including the Product Brief meeting to share findings to Product Leads, in the Committee to gather some insights as well as in the CDS Platform hall. 2021 12 CX Product Briefing

  Conduct a discovery of Platform Clients 

  Task	Discovery Activities Findings
  To identify and conduct a deep dive on one client profile that is of high-value across platform products and identify if this targeted client is a promoter or a gatekeeper	Current Client is a Developers’ Manager – More details in Miro  Manager of Developers / Communication representatives with mid to high knowledge of tech. The Manager can easily test a platform solution but would need dev/ comm teams to implement it. They get recommendations/ blessings from the Security team on which products are safe/ secure to use. They tend to work in a GC inter-department that is advanced in Digital Transformation. The manager is a promoter to deliver product adoption. Security team could be gatekeepers depending on the relationship and views they have on digital solution and the sensitivity of data that would be gathered depending on the digital solutions
  To identify the themes that make a positive client experience via a Case Study of a client who had positive experiences adopting/ adapting GCNotify	Security compliance teams approved digital solutions Digital Transformation journey was well advanced Active presence of Developers’ Community on GitHubDigital literacy of teams needs to be medium to high Culture of advancing digital solutions was importantDepartment Digital maturity Trust/ Collaboration is important when digital solutions are being adopted. CDS Platform solutions are well received as they are already in the Government that only makes them seem to be secureThe Security Team approved/ blessed which product the client can adopt. Department Data Sensitivity, the data being exposed/ shared using digital solutions determines if they will be easily adopted/ accepted.Dev Community (Niche Market) was specific to GC Notify

  Create an end to end Client journey

  Task	Findings
  To develop a journey map for the platform client selected.	Current Client Journey Map  More details in Miro Insights from the Client  journey map show there was no indication of asking for security compliance documents. Security team members themselves suggested the solutions in most cases. The Clients were more interested in how to adopt the digital solutions in the most efficient way. Their developers teams ended up handling testing, installing and adoption of the product within the department’s systems. CDS Platform Digital solutions being in the public made it trustworthy
  To identify the gaps in the client’s experience across all the Platform touchpoints, for different client interactions.	Client was identified to be Niche driven to Developers community i.e. High Digital Literacy with high presence on GitHub specific to GC NotifyNo training or customer support available for non-tech team even though there could be use cases for non-tech clients/ users Limited use cases of developers communities Self-serve approach prevents  non-tech communities from adopting advanced digital solutions
  To identify actions that can be implemented by the teams to improve the journey.	The importance of implementing team consistency clients’ experience to brand CDS Platform digital solutions was indicated, so it’s consistent in all the different digital solutions. Determine space where Platform Digital services exist. Evaluate  the must haves for a digital solutionsIdentify which GC teams have conditions preventing  adoption of the CDS Platform Digital Solutions to fine-tune actions for implementations Onboarding, training and support for Platform Digital Solutions required

  Conclusions 

  Final thoughts and next steps 

  The Client Experience research activities solidified the need to have a Client Experience team. Pinning down the current client composition identified the need to understand the context of the client and the needs that are supposed to be met. While security compliance is one factor that impacts the adoption of CDS Platform digital solutions, there are other factors that need to be considered to establish a positive client experience throughout the process, as listed below: 

  • Digital Transformation journey is well established  within the team 
  • Digital literacy of teams is considered  medium to high 
  • Active engagement of Developers’ Community on GitHub
  • Culture of advancing digital solutions was important
  • Data security sensitivity is low and security requirements were less 

  Where the Department’s data sensitivity was less of a concern, security requirements were generally less complicated. Having a view of what CDS Platform Digital solutions is working on, would provide insight to clients on requirements, beyond security compliance, that would make the clients’ experience positive and trustworthy. It is at this stage that clients identify other factors that might make product adoption acceptable to security teams and  other teams involved.

  Connecting with Security Compliance Assessors is challenging. Their work is intricate and their time is limited. Recruiting Security Compliance Assessors requires fair compensation and can take  upwards of six months. The clients stated that they hoped to get “the blessing” of the security compliance teams/ assessors to use specific digital products, which made it easy to adopt the products. Being a digital agency within the government also played a big role on how digital products were adopted. It would be more impactful to earn trust and have measures that are digital solutions driven unlike existing paper heavy and long processes.

  Clients rely on the  Security team to suggest and approve digital solutions to be adopted and or adapted. Clients cannot adopt digital solutions that have not been  approved by the Security Team.  To understand Client’s needs, and their context, is key for CDS Platform Digital solutions to be adopted. It’s important to build relationships with clients by sharing what CDS Platform is working on as buy-in for early adoption opportunities, to identify potential questions from security teams and prepare documentation ahead of time. 

  Next steps would be to map out GC department teams with conditions to adopt CDS Digital solutions. This would map segments to which the CDS Platform Business unit could  start collaborating with to identify what works in favorable contexts and adapt to conditions of future clients. 

  Recommendations

  The CX (Client Experience) team is needed to support all product teams developing consistent positive experiences throughout the product adoption cycle. A representative of Client Experience in each team would  help identify security compliance needs and maintain consistency across CDS Platform Digital Solutions. 

  Working with other government agency bodies, like GC(UK), may lead to insights on products in development, along with  increased collaboration and learning from additional government agencies. 

  There was a connection with DND Security team assessors who were willing to work with Platform CDS to share how they perceive the Security Compliance processes in all areas of different product adoption. This would be a great opportunity for the next phase of Client Experience with focus on Security Compliance processes. 

  Lessons Learned

  1. CX (Client Experience) is needed for product development teams to ensure that that our past/current clients have positive experience so as to adopt future CDS Platform products 
  2. Identify a Case Study helped zoom into specific objectives which made this project manageable 
  3. Having an ongoing meeting like the Committee to move the conversation was helpful to build relationships with existing client participants who were open to give honest feedback
  4. The Committee was useful in identifying if clients would adopt other CDS Platform digital solutions and to start thinking about possible roadblocks 
  5. Recruitment of participants was challenging,  especially when you are not from the public sector. Aligning with internal colleagues with existing relationships with public servants was required.  
  6. Creating a pool of participants gathered from all CDS past and current colleagues to maintain relationships would be useful to keep clients engaged.
  7. Security Compliance Assessors were busy and difficult to connect with as their time is severely limited.
  8. Building relationships with Security Assessors and including them in client engagement would be very impactful 

  Artifacts 

  Figure – Mapped out GC Notify Department Adoption 

  Client Experience Journey Map 

• Write stuff here and it looks like it’s going to laterOctober 20, 2022

  So I can write whatever I want.

  

  click here

The ‘Latest posts’ block has a number of customizations that one can use. You can see a screen shots of it the columns block below.