From eeb203f106143e09c37b021ec96c9182e9b93b56 Mon Sep 17 00:00:00 2001 From: Joe Date: Mon, 13 Nov 2023 22:41:25 +0000 Subject: [PATCH] remove whitespace of some posts and format them ready for Siteleaf --- .siteleaf.yml | 2 ++ ...7-13-how-to-deliver-a-difficult-message.markdown | 13 ++++++++++--- ...-with-intent-a-path-to-embedded-accessibility.md | 11 ++++++++--- ...23-11-06-testing-with-intent-a-technical-view.md | 12 +++++++++--- ...11-07-understand-your-data-requirements.markdown | 5 ++++- ...-09-the-sustainable-computing-ecosystem.markdown | 4 ++-- dhope/atom.xml | 9 +++++---- dhope/feed.xml | 9 +++++---- dhope/index.html | 5 +++-- sgladstone/atom.xml | 1 + sgladstone/feed.xml | 7 ++++--- sgladstone/index.html | 5 +++-- 12 files changed, 56 insertions(+), 27 deletions(-) create mode 100644 .siteleaf.yml rename {fhubin/_posts => _posts}/2020-07-13-how-to-deliver-a-difficult-message.markdown (97%) diff --git a/.siteleaf.yml b/.siteleaf.yml new file mode 100644 index 0000000000..c033b6da4f --- /dev/null +++ b/.siteleaf.yml @@ -0,0 +1,2 @@ +--- +site_id: 62a34ab6d77615482511bc22 diff --git a/fhubin/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown b/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown similarity index 97% rename from fhubin/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown rename to _posts/2020-07-13-how-to-deliver-a-difficult-message.markdown index 8c2fb29c0c..b796d6aa8c 100644 --- a/fhubin/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown +++ b/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown @@ -1,10 +1,17 @@ --- title: How to deliver a difficult message? -author: fhubin -layout: default_post -tags: agile scrum project management stakeholder management +date: 2020-07-13 00:00:00 Z categories: +- fhubin - Delivery +tags: +- agile +- scrum +- project +- management +- stakeholder +author: fhubin +layout: default_post --- In a client-supplier relationship, communication is of paramount importance. And good communication requires transparency. A supplier in charge of a doomed project telling their client that all is going well would not be doing a very good job. Similarly, a client whose budget has been cut telling a supplier that all is well would also not be delivering the right message. diff --git a/_posts/2023-11-06-testing-with-intent-a-path-to-embedded-accessibility.md b/_posts/2023-11-06-testing-with-intent-a-path-to-embedded-accessibility.md index ca634b94e0..10663d004a 100644 --- a/_posts/2023-11-06-testing-with-intent-a-path-to-embedded-accessibility.md +++ b/_posts/2023-11-06-testing-with-intent-a-path-to-embedded-accessibility.md @@ -1,9 +1,8 @@ --- -title: "Testing with Intent: a Path to Embedded Accessibility" +title: 'Testing with Intent: a Path to Embedded Accessibility' date: 2023-11-06 09:45:00 Z categories: - Tech -layout: default_post tags: - Testing - Testing Library @@ -11,7 +10,13 @@ tags: - Testing with Intent - Accessibility - Embedded Accessibility -summary: "In this post, I explore an approach to testing called Testing with Intent. I look what the approach is—testing from the perspective of a user intending to do something—and the positive impacts it can have on both testing and accessibility. I've written this for a broad audience, so I've steered clear of technical details included. Instead, you should come away with an understanding of why this topic is important and how you can benefit from adopting the approach." +layout: default_post +summary: In this post, I explore an approach to testing called Testing with Intent. + I look what the approach is—testing from the perspective of a user intending to + do something—and the positive impacts it can have on both testing and accessibility. + I've written this for a broad audience, so I've steered clear of technical details + included. Instead, you should come away with an understanding of why this topic + is important and how you can benefit from adopting the approach. author: sgladstone --- diff --git a/_posts/2023-11-06-testing-with-intent-a-technical-view.md b/_posts/2023-11-06-testing-with-intent-a-technical-view.md index fbca148143..b67f549be6 100644 --- a/_posts/2023-11-06-testing-with-intent-a-technical-view.md +++ b/_posts/2023-11-06-testing-with-intent-a-technical-view.md @@ -1,9 +1,8 @@ --- -title: "Testing with Intent: a Technical View" +title: 'Testing with Intent: a Technical View' date: 2023-11-06 09:55:00 Z categories: - Tech -layout: default_post tags: - Testing - Testing Library @@ -11,9 +10,16 @@ tags: - Testing with Intent - Accessibility - Embedded Accessibility -summary: "In my previous post, I introduced and approach to testing called Testing with Intent. Essentially, the approach focuses on testing from the perspective of a user intending to do something. Adopting this approach brings you benefits in both your test suites and your products accessibility. That post discussed why the topic is important and how you can benefit if you adopt it. Now, it’s time to look at the technical side of how this actually works in practice. " +layout: default_post +summary: 'In my previous post, I introduced and approach to testing called Testing + with Intent. Essentially, the approach focuses on testing from the perspective of + a user intending to do something. Adopting this approach brings you benefits in + both your test suites and your products accessibility. That post discussed why the + topic is important and how you can benefit if you adopt it. Now, it’s time to look + at the technical side of how this actually works in practice. ' author: sgladstone --- + In [my first post]({{ site.github.url }}/2023/11/06/testing-with-intent-a-path-to-embedded-accessibility.html), I set out why I think we should be *Testing with Intent*. I set out that, if we focus our tests on the intentions of users, we can improve our test suites and start to tackle accessibility. To keep the content accessible to everyone, I chose to not include anything technical. Now, in this post, I’m going to look at the same subject but through a technical lens. The essence of this whole approach to testing can be boiled down to one simple golden rule: “Wherever possible, use `queryByRole`". We’ll take a look at what we mean by this rule, and start to unpack its consequences. diff --git a/_posts/2023-11-07-understand-your-data-requirements.markdown b/_posts/2023-11-07-understand-your-data-requirements.markdown index b65e31d422..590543c2b2 100644 --- a/_posts/2023-11-07-understand-your-data-requirements.markdown +++ b/_posts/2023-11-07-understand-your-data-requirements.markdown @@ -1,5 +1,6 @@ --- title: Understand your data requirements +date: 2023-11-07 00:00:00 Z categories: - Data Engineering tags: @@ -7,7 +8,9 @@ tags: - CDP - Big Data - Data Strategy -summary: This blog discusses the different data requirements that exist in a typical organisation and provides some suggestions over how to classify them and match them to technologies +summary: This blog discusses the different data requirements that exist in a typical + organisation and provides some suggestions over how to classify them and match them + to technologies author: dhope --- diff --git a/_posts/2023-11-09-the-sustainable-computing-ecosystem.markdown b/_posts/2023-11-09-the-sustainable-computing-ecosystem.markdown index 4494320cc2..d677720f74 100644 --- a/_posts/2023-11-09-the-sustainable-computing-ecosystem.markdown +++ b/_posts/2023-11-09-the-sustainable-computing-ecosystem.markdown @@ -8,9 +8,9 @@ tags: - sustainable software - Sustainability - Tech -summary: 'Part of the Conscientious Computing series this blog talks about the emerging +summary: Part of the Conscientious Computing series this blog talks about the emerging ecosystem of organisations that are promoting sustainability within software development, - cloud computing, infrastructure, and digital services.' + cloud computing, infrastructure, and digital services. author: ocronk image: "/uploads/greensoftware-ecosystem-024a11.png" contributors: jhowlett diff --git a/dhope/atom.xml b/dhope/atom.xml index cbafec3529..2de72797e9 100644 --- a/dhope/atom.xml +++ b/dhope/atom.xml @@ -1,4 +1,5 @@ ---- -author: dhope -layout: atom_feed ---- \ No newline at end of file +--- +author: dhope +layout: atom_feed +--- + diff --git a/dhope/feed.xml b/dhope/feed.xml index 94ba84b392..37687aaebf 100644 --- a/dhope/feed.xml +++ b/dhope/feed.xml @@ -1,4 +1,5 @@ ---- -author: dhope -layout: rss_feed ---- \ No newline at end of file +--- +author: dhope +layout: rss_feed +--- + diff --git a/dhope/index.html b/dhope/index.html index edd567b35b..3913faf6f3 100644 --- a/dhope/index.html +++ b/dhope/index.html @@ -1,5 +1,6 @@ --- -author: dhope title: David Hope +author: dhope layout: default_author ---- \ No newline at end of file +--- + diff --git a/sgladstone/atom.xml b/sgladstone/atom.xml index 6fd69cc666..5a00a3d431 100644 --- a/sgladstone/atom.xml +++ b/sgladstone/atom.xml @@ -2,3 +2,4 @@ author: shall layout: atom_feed --- + diff --git a/sgladstone/feed.xml b/sgladstone/feed.xml index 811496572e..a13f7005bc 100644 --- a/sgladstone/feed.xml +++ b/sgladstone/feed.xml @@ -1,4 +1,5 @@ ---- -author: username -layout: rss_feed --- +author: username +layout: rss_feed +--- + diff --git a/sgladstone/index.html b/sgladstone/index.html index efe4c57a39..cd4e1808f4 100644 --- a/sgladstone/index.html +++ b/sgladstone/index.html @@ -1,5 +1,6 @@ --- -author: sgladstone title: Sam Gladstone +author: sgladstone layout: default_author ---- \ No newline at end of file +--- +