<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Wigglesworth on Medium]]></title>
        <description><![CDATA[Stories by Daniel Wigglesworth on Medium]]></description>
        <link>https://medium.com/@dwigglesworth?source=rss-dfd23cede124------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Y-tq74_aNOdBUSVm37-myQ.jpeg</url>
            <title>Stories by Daniel Wigglesworth on Medium</title>
            <link>https://medium.com/@dwigglesworth?source=rss-dfd23cede124------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:17:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dwigglesworth/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Publishing for reach]]></title>
            <link>https://medium.com/inside-jrf/publishing-for-reach-eeab3b2c5499?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeab3b2c5499</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[digital-strategy]]></category>
            <category><![CDATA[content-transformation]]></category>
            <category><![CDATA[content-governance]]></category>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 12:21:36 GMT</pubDate>
            <atom:updated>2025-07-24T15:40:46.039Z</atom:updated>
            <content:encoded><![CDATA[<h4>How and why we publish digital-first at Joseph Rowntree Foundation (JRF).</h4><p>In a world where attention is short and information is abundant, how we present our work matters as much as what we say.</p><p>At JRF we’ve made a deliberate shift to publish our briefings and reports digital-first in a web-native format. This isn’t just a technical decision — it’s a strategic one. It’s about accessibility, discoverability, and impact.</p><h3>Why we publish digital-first</h3><p>A digital-first approach means publishing our content as a webpage rather than a document like a PDF (Portable Document Format) as the primary medium.</p><p>We’re not alone in this. <a href="https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/">Governments</a>, <a href="https://onthinktanks.org/articles/on-technology-and-monotony-automating-tasks-to-save-time-money-and-your-sanity/">think tanks</a>, and media organisations are moving away from PDF.</p><p>In 2014 Christopher Ingraham of the Washington Post’s WonkBlog posed this question:</p><blockquote>“What if someone had already figured out the answers to the world’s most pressing policy problems, but those solutions were buried deep in a PDF, somewhere nobody will ever read them?”</blockquote><p>At JRF we publish digital-first because we want our work to be read, understood, and used.</p><h4><strong>Accessibility</strong></h4><p><a href="https://www.nngroup.com/articles/pdf-unfit-for-human-consumption/">PDFs are often difficult to read</a> on mobile devices and can present barriers for people using assistive technologies. Digital-first content is responsive, readable, and inclusive by design.</p><p>HTML is a good basis for accessibility, because HTML was designed to be displayed in a web browser and be presented in different ways, it can support assistive technologies like screen readers.</p><h4><strong>Discoverability</strong></h4><p>Search engines — and increasingly, AI tools — struggle to extract meaning from static documents. Structured, web-native content is easier to find, cite, and reuse.</p><p>Web pages can be updated in real-time, which allows various systems to access the most current information.</p><h4>Workflow</h4><p>Digital-first has simplified our publishing process and reduced duplication.</p><p>We have a single publishing workflow. We still offer a PDF so that users can print our briefings and reports, however the PDF download is now automatically generated from our web-native content, which has eliminated the need to design for both print and web separately.</p><h4>User experience</h4><p>People don’t read reports cover to cover. They scan, search, and scroll. Digital-first formats allow us to design for how people actually engage with content.</p><h4>Engagement rates</h4><p>Fewer users are downloading PDFs than in previous years. On average 1 in 5 users (22%) download the PDF version of our publications. The data supports the shift, various metrics indicate users are reading digital-first.</p><h3>What user research told us</h3><p>Users want options. Drawing from multiple rounds of usability testing and interviews, here’s what we’ve learned:</p><ul><li>PDFs are still downloaded, often out of habit or for later reading — but they are rarely printed.</li><li>Webpage reading is preferred for ease of access, interactivity, and navigation. Users appreciate clickable links and the ability to skim or scroll.</li><li>Bookmarking is replacing downloading: Users are increasingly saving links rather than files.</li></ul><p>This suggests that digital-first is becoming the preferred experience when executed well. When we’ve asked users if they would prefer a PDF or a webpage we’ve found they want both, so we continue to offer both.</p><h3>What we’ve been up to</h3><p>We’ve built a publishing workflow that puts web at the centre:</p><ul><li>Every publication gets a webpage. This isn’t just a <a href="https://www.nngroup.com/articles/gateway-pages-prevent-pdf-shock/">gateway page</a> — it’s the primary product. It includes author information, a summary, key findings, chapters, our preferred citation style and references.</li><li>We use storytelling tools. We’ve invested in <a href="https://flourish.studio/">Flourish</a>, which we’re using for charting, data visualisations and other interactives. We design content that works on mobile and invites exploration.</li><li>Unless a report is exceptionally long, we don’t publish a fully typeset and highly stylised PDF.</li></ul><h4>Examples</h4><p>We’ve been publishing digital-first since January 2024. In fact, around 95% of what we publish is now digital-first.</p><p>Here’s some exemplar outputs we’ve published:</p><ul><li><a href="https://www.jrf.org.uk/care/a-new-social-contract-in-the-childcare-system">A new social contract in the childcare system</a> | A standard demonstration of our report product.</li><li><a href="https://www.jrf.org.uk/narrative-change/changing-the-narrative-on-wealth-inequality">Changing the narrative on wealth inequality</a> | One of our first web-only content commissions (it was accompanied by a much lengthier literature review product).</li><li><a href="https://www.jrf.org.uk/cost-of-living/jrfs-pre-election-cost-of-living-tracker">The scale of the challenge: JRF’s pre-election cost of living tracker</a> | A shorter 18 minute read data story.</li><li><a href="https://www.jrf.org.uk/uk-poverty-2025-the-essential-guide-to-understanding-poverty-in-the-uk">UK Poverty 2025</a> | At 177 pages our UK Poverty product is far too long to produce fully digital-first. This is a standard demonstration of a digital-first executive summary.</li><li><a href="https://www.jrf.org.uk/public-attitudes/addressing-key-voters-economic-insecurity-is-vital-for-all-parties">Addressing key voters’ economic insecurity is vital for all parties</a> | An effective demonstration of a stat-heavy report.</li><li><a href="https://www.jrf.org.uk/cost-of-living/starmers-missed-milestone-the-outlook-for-living-standards-at-the-spring-statement">Starmer’s missed milestone? The outlook for living standards at the Spring Statement</a> | A consistent, well-structured demonstration of our briefing product.</li><li><a href="https://www.jrf.org.uk/social-security/where-will-cuts-to-sickness-and-disability-benefits-fall-hardest">Where will cuts to sickness and disability benefits fall hardest?</a> | This was an evolving story. The nature of digital-first allowed us to instantly update this briefing iteratively, quickly updating it with new analysis as it arose.</li></ul><h3>Feedback</h3><p>The Digital Product team has received strong internal recognition within JRF of our leadership in embedding digital-first practices.</p><p>We’ve successfully coached teams to adopt new workflows, updated our content creation guidance, and used development budgets to address technical challenges.</p><p>Externally we are hearing themes along the lines of:</p><blockquote>“I’m constantly Googling “narrative change” (and related keywords) and using AI tools to learn how organisations have developed framing resources. JRF is consistently top.”</blockquote><p>This highlights how JRF’s digital-first strategy raises the visibility of JRF’s work and helps shape how others approach their development of communications resources.</p><p>That’s not a coincidence, that’s knowing that writing in a structured, clear, unambiguous way that follows common conventions helps people find and learn patterns in our content.</p><p>External collaborators genuinely express their openness and curiosity about how their work will be adapted for digital-first. They welcome conversations about format and design, showing trust in the team’s expertise.</p><p>For example, we’ve found that shorter content is becoming an increasing preference for users:</p><blockquote>“I prefer things to be short and snappy… I wouldn’t want paragraphs and paragraphs of text…”</blockquote><p>Users prefer short content because it’s easier to digest, providing useful insights without overwhelming detail. They appreciate being able to get to the main points quickly, without needing to read lengthy documents.</p><p>Our shift to digital-first has allowed us to introduce new content formats that would have previously been published as either a briefing or report:</p><blockquote>“Generally, I don’t want to get into a 50-page report, so this is quite useful. Kind of top level. And the way that you know the quotes are pulled out, it’s good just to get that sense of like, well, what’s the actual kind of opinion here or the interesting point that’s being made here?”</blockquote><h3>Barriers to digital-first adoption still exist</h3><p>Despite the positive feedback, research also surfaced one key friction point — sector readiness. Users are not used to accessing a digital-first format for reports:</p><blockquote>“I would guess that this is the summary and then a full report. But you can often have the findings which I guess is like again a summary and then the full report, so I’ll just click on <strong>Download this report</strong> and see what happens…”</blockquote><p>­Users instinctively download the PDF when landing on a report page, after all it’s what they’re used to seeing elsewhere:</p><blockquote>“I was assuming that there would be a short summary on the webpage and a link somewhere to download the report, and I wasn’t expecting to see the whole report on the page …”</blockquote><h3>Helping your organisation shift to a digital-first mindset</h3><p>PDF has long been popular for sharing content online, which has established certain habits and familiarity.</p><p>Transforming your content can be hard — especially when you’re busy and have lots of old content to update with limited time or resources. We’ve found it’s a case of taking things slowly, to test and learn.</p><p>We focussed on the accessibility of our content first and then started making improvements on our previous website — we didn’t fully realise our shift to digital-first until we had integrated our learning into our current websites templates.</p><p>We’re still learning how to scale digital-first efficiently, but these would be my tips if you are looking to adopt a similar mindset:</p><ul><li>focus on accessibility</li><li>bring editorial and content design expertise in earlier to the end-to-end writing and publishing process</li><li>make your editorial templates (in our case Word) closely match the experience on your website (design, style and formats)</li><li>show other people alternatives.</li></ul><h4>Examples of what other people are up to</h4><ul><li><a href="https://www.bankofengland.co.uk/monetary-policy-report/2025/may-2025">Bank of England</a> | Digital-first report with a PDF download.</li><li><a href="https://www.chathamhouse.org/2025/07/why-indo-pacific-should-be-higher-priority-uk">Chatham House</a> | Digital-first report with a PDF download.</li><li><a href="https://www.kingsfund.org.uk/insight-and-analysis/reports/place-based-partnerships-challenges-opportunities">The King’s Fund</a> | Digital-first executive summary with a PDF download.</li><li><a href="https://research.mysociety.org/html/reforming-foi/#top">MySociety</a> | Digital-first report with a PDF download.</li><li><a href="https://www.nesta.org.uk/introduction-our-strategy/">Nesta</a> | Digital-first strategy document in the form of Scrollyteller, a digital storytelling technique that combines the art of storytelling with the interactivity of scrolling. Again this also features a PDF download.</li><li><a href="https://data.gov.scot/poverty/2022/persistent.html">Scottish Government </a>| Digital-first report with a print style sheet. You can use CSS (Cascading Style Sheets) to set different styles for webpages for when they’re printed versus when they’re displayed onscreen.</li><li><a href="https://institute.global/insights/climate-and-energy/ai-and-clean-energy-how-governments-can-unlock-the-power-of-the-twin-transitions">Tony Blair Institute for Global Change</a> | Digital-first report with a PDF download.</li></ul><h3>What’s next</h3><p>We’re not stopping here. Now that more JRF content is “born-digital”, we are looking at providing a way of preserving this information for future generations.</p><p><a href="https://dwigglesworth.medium.com/archiving-retention-and-preservation-e658c69d6cd9">Read more about our approach to archiving, retention and preservation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeab3b2c5499" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-jrf/publishing-for-reach-eeab3b2c5499">Publishing for reach</a> was originally published in <a href="https://medium.com/inside-jrf">Inside the Joseph Rowntree Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Archiving, retention and preservation]]></title>
            <link>https://medium.com/inside-jrf/archiving-retention-and-preservation-e658c69d6cd9?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/e658c69d6cd9</guid>
            <category><![CDATA[content-governance]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[content-auditing]]></category>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Thu, 29 May 2025 13:21:25 GMT</pubDate>
            <atom:updated>2025-05-29T13:43:24.425Z</atom:updated>
            <content:encoded><![CDATA[<h4>A look into the Joseph Rowntree Foundation’s (JRF) digital content life-cycle.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Py9W3B5DxKFn1O1h" /><figcaption>Photo by <a href="https://unsplash.com/@matt__feeney?utm_source=medium&amp;utm_medium=referral">matthew Feeney</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve been looking at this challenge periodically since around 2016, we made strides in 2021, and then one big one in 2024:</p><blockquote>We want our reports and findings available for posterity, however we don’t want <strong>ALL</strong> our reports preserved on the current or future versions of the JRF website.</blockquote><p>We’d kept every report since 1994.</p><p>As a charity, the results of our funding should be available for the public good. As an evidence-led organisation, we should make our evidence freely available. User research showed us that our evidence is vital to the strength of our brand and trusted reputation.</p><p>An accumulated body of knowledge is evidence of our grounding and long-standing interest on certain issues.</p><p>We found that older material was less relevant in the current influencing period and political context, although existing knowledge helped support new work, document trends, and minimise the risk of commissioning duplicate studies.</p><p>Older material forms a fair share of what users visit on the JRF website, some material is high-performing, and some material holds little value. It’s hard to predict what might become useful again in future, many of the issues we are working on as an organisation don’t vanish.</p><p>However, older material was confusing people searching for up-to-date content and was seen as less relevant.</p><h3>How we turned our content retention strategy into a success story</h3><h4>Start small</h4><p>Pretty soon after starting at JRF I was able to implement and set retention policies for all other content types (blogs, news, events, people pages), except for reports.</p><p>Emerging themes from an early audit highlighted some report pages could be removed immediately:</p><ul><li><strong>Reports that were out of print / not available electronically</strong>. These pages tended to summarise old outputs that were no longer available: title, author, publish date, metadata. No actual content</li><li><strong>Report pages that should have been another content type.</strong> These pages should have been published as either events or press releases</li><li><strong>Report pages of short summary text</strong> <strong>linking to external resources</strong> such as books and old externally published reports: title, author, publish date, metadata. Some of which were broken links. No actual content</li><li><strong>Reports that referenced physical products</strong> that we could no longer access, such as CD-ROMs and DVDs.</li></ul><h4>Content audit</h4><p>The early audit indicated that reports older than 10 years made up 20% of our yearly engagement and represented 80% of the material we held. Implementing a retention period of 10 years seemed a reasonable starting point.</p><p>In 2021, we built a content inventory by exporting a spreadsheet from Siteimprove and began reviewing high-performing old content sitting outside of a 10-year period:</p><ul><li>1,430 reports on the JRF website older than 10 years, dating back to 1994</li><li>Certain years performed better than others, volumes of yearly output and publishing format were key factors.</li></ul><p>A tipping-point started to emerge at 8 years, where the material was high-quality but appeared to no longer meet current strategic goals. It’s at this point we decided to run a strategic assessment and defined our audit factors further:</p><ul><li><strong>Keep.</strong> We keep reports that are recent and on strategic themes</li><li><strong>Improve</strong>. We improve material that should be re-purposed</li><li><strong>Archive</strong>. We archive material that is out-of-date and no longer important to JRF</li><li><strong>Delete.</strong> We can delete material that is time-bound on themes that are no longer relevant to anyone</li><li><strong>Delete.</strong> We can delete old Findings (a four page PDF summary product) that reference Full Reports that are available elsewhere.</li></ul><p>We split up as a team and began content sampling over a two week period. We checked in with each other, gave feedback, refining / validating our audit factors and identified that 951 reports were suitable for archival.</p><p>We completed our audit and got in touch with JRF colleagues (internal stakeholders) to assess their needs of this material by running organisational research. The main concern was around retaining open access and having sight of the decisions we’d made.</p><h4>Evaluation of archiving options</h4><p>From organisational research we developed a set of requirements / principles. We began researching archive options, archive tools, gathering costs and made assessment against the following criteria:</p><ul><li><strong>Ease of access</strong></li><li><strong>Searchability</strong></li><li><strong>Longevity</strong></li><li><strong>Maintenance</strong></li><li><strong>Licensing costs</strong></li><li><strong>Ownership</strong></li></ul><p>Following this exercise, we made the recommendation to JRF Directors and Trustees:</p><ul><li><strong>Future publishing</strong>. Top priority outputs, central to our current influencing objectives should be published on the JRF website</li><li><strong>Older reports</strong>. Remove reports older than 8 years from the JRF website on a gradual, systematic basis year by year, and host them on an alternative, publicly accessible, searchable platform within the Borthwick Institute for Archive’s digital archive.</li></ul><h4>Borthwick</h4><p>Based in York (where JRF is headquartered), Borthwick Institute for Archives is one the biggest archive repositories outside of London. Early conversations revealed JRF already had an existing relationship with the Borthwick Institute, as it holds the organisations’ paper archives.</p><p>We got in touch with Borthwick Institute and reviewed status of their platform(s). Borthwick had a number of options, so we explored technical requirements of each platform and established the scale of the work required to make older JRF material publicly accessible through the library catalogue, both online and in-person:</p><ul><li><strong>Workflow</strong>. Is it an easy archival process that is seamless year on year?</li><li><strong>Storage.</strong> Can we host a variety of file formats? Can we order content by theme / topic? Can we host HTML pages, often with no PDF download? Can we host multimedia content, such as images? Is there a limit on how many reports we can archive? Is there a limit to the title length for each article? ​Is there a limit to the number of files each page can have? What additional metadata is needed?</li><li><strong>Access</strong>. Is it open access that doesn’t require a login? Will the entries appear in search engine results? Will PDF content be searchable? Will there be a landing page? Will entries searchable by multiple parameters, date, title, authors, etc?</li><li><strong>Preservation. </strong>Will the digital materials remain complete, unaltered from their original state? How might we ensure long-term access so that information can be accessed and retrieved in the future?</li></ul><p>We made our decision and began to sequence the work to coincide with the launch of a new website for JRF, preparing the deposit by gathering files and metadata to handover to the library team at Borthwick.</p><h3>The result</h3><p><a href="https://yorsearch.york.ac.uk/discovery/collectionDiscovery?vid=44YORK_INST:NUI&amp;inst=44YORK_INST&amp;collectionId=81411059430001381&amp;lang=en">Our archived collection</a> went live in July 2024. In September 2024, we began systematically removing material marked for archival from the JRF website. We also put in place a number of user journeys to allow external audiences access to JRF material by sharing clear instructions / guidance and referring people to the collection:</p><ul><li>We contacted colleagues in our press office, events team and core teams</li><li>We developed a banner component on the no results screen within on-site search. JRF audiences have good understanding of our back catalogue and perennial output</li><li>We updated our 404 not found page</li><li>We updated our contact us page.</li></ul><p>With the solution live we began monitoring external queries, during this phase we realised we could archive an additional 28 reports and made an additional deposit.</p><h3>What’s next?</h3><p>With an effective archive solution live we’ve now been able to put in place a reliable proactive process that allows us to review existing content against quantitative and qualitive audit factors on a quarterly basis. Our next review is in June. We hope to make regular, smaller deposits to the archive.</p><p>Within JRF we’ve introduced the concept of “digital-first”, which means publishing our Reports and publications in HTML with an optional PDF download. 95% of what we’ve been publishing from January 2023 has been in this format. Now that more JRF content is “born digital” we are looking at providing a way of preserving this information for future generations.</p><p>We plan to continue our partnership with Borthwick Institute for Archive’s and put in place a reliable solution that provides free access to browsable, searchable, captured copies of the JRF website in addition to the collection and paper archives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e658c69d6cd9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-jrf/archiving-retention-and-preservation-e658c69d6cd9">Archiving, retention and preservation</a> was originally published in <a href="https://medium.com/inside-jrf">Inside the Joseph Rowntree Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 top tips to improve the accessibility of your website]]></title>
            <link>https://medium.com/inside-jrf/five-top-tips-to-improve-the-accessibility-of-your-website-8f50dbb32263?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f50dbb32263</guid>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Wed, 15 May 2024 08:03:35 GMT</pubDate>
            <atom:updated>2024-05-16T08:25:09.053Z</atom:updated>
            <content:encoded><![CDATA[<p>Tomorrow, Thursday 16 May will be Global Accessibility Awareness Day (GAAD)!</p><p>The aim of GAAD is to get everyone talking, thinking and learning about digital access and inclusion. It’s held every year on the third Thursday of May.</p><p>At the Joseph Rowntree Foundation (JRF), we’ve recently refreshed our brand and rolled out a new website designed to meet modern accessibility standards.</p><p>Last year the Digital Product team within JRF also carried out the same process and launched a new website for our subsidiary<strong> </strong>the Joseph Rowntree Housing Trust (JRHT).</p><p>We are proud to have been recognised as having one of the <a href="https://index.silktide.com/category/uk-charities">top UK charity websites for accessibility</a> and that JRHT sits in the <a href="https://index.silktide.com/category/uk-housing-authority">same position within the housing sector</a>.</p><p>Digital accessibility is focused on specific accommodations for disability. The goal of accessibility is to create products, services and environments that are usable by people with disabilities.</p><h3>Priorities</h3><p>We realised that to make progress towards our mission, we needed to embrace accessibility as a core principle and that this was required to create the best user experience for everyone. Over the last 5 years our priorities have been to:</p><ul><li>raise awareness and knowledge of accessibility with colleagues and stakeholders through an internal accessibility working group within JRF and JRHT</li><li>integrate accessibility at each phase of our product lifecycle</li><li>audit our website products frequently to ensure any changes continue to be usable by people with disabilities</li></ul><h3>5 top tips</h3><p>Improving accessibility is important because it removes barriers from people engaging with your work.</p><p>Since we went live with the refreshed JRF brand, many of our peers have been in touch and asked what they can be doing to make their own websites more accessible. These are our top tips:</p><h4><strong>1.</strong> <strong>Use good colour contrast</strong></h4><p>Colour contrast is the difference in brightness between the foreground and background colours. Good colour contrast makes sure everyone can access your content. Aim for a 4.5:1 ratio for normal text and a ratio of 3:1 for large text.</p><p>There are several tools you can use to assess your website for colour contrast accessibility:</p><ul><li><a href="https://webaim.org/resources/contrastchecker/">WebAIM: Contrast Checker</a></li><li><a href="https://monsido.com/tools/contrast-checker">Monsido Colour Contrast Checker</a></li><li><a href="https://accessibleweb.com/color-contrast-checker/">Web Accessibility Colour Contrast Checker</a></li></ul><h4><strong>2.</strong> <strong>Write in plain English</strong></h4><p>Plain language is accessible language. By writing using plain English, you open up your content so it can be understood quickly, by the most amount of people. Aim to keep your content clear, concise, and quick to comprehend.</p><p>You can read the <a href="https://gds.blog.gov.uk/2014/02/17/guest-post-clarity-is-king-the-evidence-that-reveals-the-desperate-need-to-re-think-the-way-we-write/">research that shows how people with higher literacy prefer plain English</a>.</p><h4><strong>3.</strong> <strong>Break up content with headings</strong></h4><p>Headings and sub-headings are used to structure your content. Individuals who are blind or visually impaired often choose to browse a webpage by headings. A good heading structure helps people orientate themselves within your content quickly.</p><p>By using headings, you are:</p><ul><li>making it easier for people to scan for key information</li><li>organising your content so it’s less overwhelming to read</li></ul><h4><strong>4.</strong> <strong>Write clear and descriptive link text</strong></h4><p>No more “click here”. Using vague and uninformative language can be confusing when read out of context. By writing descriptive link text that clearly and accurately describes the website or resource your link leads to, you are helping people understand the purpose of the link.</p><p>Examples of clear link text:</p><ul><li><a href="https://medium.com/imagination-practice/collective-imagination-practice-fund-year-2-5d7e2db5a2d1">Guidance on making a successful funding application</a></li><li>Read <a href="https://www.jrf.org.uk/privacy">our privacy notice</a></li></ul><p>Examples of unclear link text:</p><ul><li>For information about accessing funding, <a href="https://medium.com/imagination-practice/collective-imagination-practice-fund-year-2-5d7e2db5a2d1">click here</a> to read this blog by Zara Davidson</li><li>Read our privacy notice at <a href="https://www.jrf.org.uk/privacy">https://www.jrf.org.uk/privacy</a></li></ul><h4><strong>5.</strong> <strong>Publish information on the webpage (HTML)</strong></h4><p>HTML is a good basis for accessibility. Because HTML was designed to be displayed in a web browser and can be presented in different ways, it is a great fit for people who use assistive technology. All content being published online should be published as a webpage.</p><p>You can read the <a href="https://www.nngroup.com/articles/pdf-unfit-for-human-consumption/">research that shows document formats like PDF are difficult for on-screen reading</a>.</p><p>If a PDF or Word document is necessary, make sure these documents are designed to meet accessibility standards. Business Disability Forum provide several guides you can use to optimise documents for accessibility:</p><ul><li><a href="https://businessdisabilityforum.org.uk/knowledge-hub/resources/best-practice-guide-creating-accessible-pdfs">Creating accessible PDFs</a></li><li><a href="https://businessdisabilityforum.org.uk/knowledge-hub/resources/making-word-documents-accessible">Making Microsoft Word documents accessible</a></li><li><a href="https://businessdisabilityforum.org.uk/knowledge-hub/resources/best-practice-guide-making-powerpoint-presentations-accessible/">Making PowerPoint presentations accessible</a></li><li><a href="https://businessdisabilityforum.org.uk/knowledge-hub/resources/best-practice-guide-making-powerpoint-presentations-accessible/">Making Excel spreadsheets accessible</a></li></ul><h3>Conclusion</h3><p>If you can focus on clear formatting, clear structure, and presenting web content in a web-native format we believe you’ll be making big strides towards a more accessible website.</p><h3>What’s next at JRF</h3><p>We believe we’ve made a great start at JRF and JRHT, but there’s still plenty to do; accessibility is seemingly never done. This year we plan to look at our content operations afresh and ensure there’s a reliable proactive process that allows us to review and audit the accessibility of our content.</p><p>If you have any feedback on this article, please use the comments section.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f50dbb32263" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-jrf/five-top-tips-to-improve-the-accessibility-of-your-website-8f50dbb32263">5 top tips to improve the accessibility of your website</a> was originally published in <a href="https://medium.com/inside-jrf">Inside the Joseph Rowntree Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JRF.ORG.UK product strategy]]></title>
            <link>https://dwigglesworth.medium.com/jrf-org-uk-product-strategy-f681fa848e75?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/f681fa848e75</guid>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Thu, 19 Oct 2023 10:41:00 GMT</pubDate>
            <atom:updated>2023-12-15T11:24:27.400Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://jrf.org.uk/">jrf.org.uk</a> is the online presence for Joseph Rowntree Foundation (JRF). Our vision is to:</p><ul><li>make it easier for people to understand who we are and how to partner with us</li><li>meet the needs of people looking for up-to-date trustworthy research, insight and provocations.</li></ul><p>Our overall aim is to modernise JRF communications and place <a href="http://jrf.org.uk/">jrf.org.uk</a> at the centre of our digital estate with its own roadmap.</p><p>Here’s what we are doing to deliver that vision.</p><h3>1. Introduce digital-first publishing</h3><p><strong>What</strong>: We’ll publish all our reports, publications, and briefings in an accessible web-native format.</p><p><strong>Why</strong>: This will make it easier for our users to consume content on mobile and easier for search engines and other technologies to index.</p><p><strong>How</strong>: In December 2023, we’ll launch a new version of <a href="http://jrf.org.uk/">jrf.org.uk</a>.</p><p>Our new platform will feature a Publication content type which will house our reports and briefings providing the ability to download and print them if needed.</p><p>We already offer PDF as a download on the current JRF platform, we’ll be releasing a new feature that streamlines our publishing workflow meaning that JRF is no longer required to carry out one process to create a PDF and another process to create a web landing page.</p><p>Next year, we’ll further embed our digital-first publishing workflow.</p><h3>2. Enhance content curation</h3><p><strong>What</strong>: We want to make <a href="http://jrf.org.uk/">jrf.org.uk</a> more accessible and usable for all audiences.</p><p><strong>Why</strong>: JRF is becoming “<a href="https://www.jrf.org.uk/blog/moment-we-are-looking-ahead-2023">a three-horizon organisation</a>”, it’s important that the widest range of users can access and engage with different strands of our work.</p><p><strong>How</strong>: We’re making topic landing pages a key user journey. We’re making the content presented easier to understand, more engaging, and reflective of all the work that we do.</p><p>We already offer topic pages on the current JRF website, we are introducing clarity, structure, and introducing an engagement model that will allow us to cross market content from different strands of work.</p><p>Next year, we’ll be introducing further topics as JRF’s strategy develops.</p><h3>3. Improve content governance</h3><p><strong>What</strong>: We want to make <a href="http://jrf.org.uk/">jrf.org.uk</a> more reflective of JRF’s current strategic priorities.</p><p><strong>Why</strong>: Many of the issues we are working on as an organisation don’t vanish, we want our research available for posterity. However, that doesn’t mean ALL our publications should be preserved on the current or future JRF website.</p><p><strong>How</strong>: We’ll continue to offer retention policies for all our content; however, we’ll be more ruthless when scheduling and retaining material intended as a time-bound response.</p><p>We’ll also remove around 950 publications, material that is no longer relevant to our strategic themes. This material is not necessarily out-of-date, although it should be made available for public good.</p><p>We’ll host this material on an alternative publicly accessible, searchable platform within the Borthwick Institute’s digital archive, which we’ll signpost from the JRF website.</p><p>Next year, we’ll be introducing new processes to audit and archive this material on a more systematic basis.</p><h3>4. Construct new ways to talk about and share our work</h3><p><strong>What</strong>: We want to make the informal information we publish on current events, personal opinion, and news findable, clear and credible.</p><p><strong>Why</strong>: Our readers and colleagues are telling us it’s often unclear what material we host within the current JRF blog versus other external channels.</p><p><strong>How</strong>: Within JRF we’ve introduced discreet propositions for each of our online channels and developed a channel library.</p><p>We’ve also developed a content framework outlining our different content types, to support this we’ll be introducing labelling throughout <a href="http://jrf.org.uk/">jrf.org.uk</a> to differentiate our content products.</p><p>Next year, we’ll be further developing our offer. People who visit <a href="http://jrf.org.uk/">jrf.org.uk</a> engage with our storytelling, high-quality analysis, research, and insight. We’ll be introducing new content types and frameworks that will allow us to publish visual journalism and digital storytelling.</p><h3>5. Make it easier for the team to improve <a href="http://jrf.org.uk/">jrf.org.uk</a></h3><p><strong>What</strong>: We want to create the right conditions for the Digital Product team to operate, with the team having far more scope commissioning content.</p><p><strong>Why</strong>: We want <a href="http://jrf.org.uk/">jrf.org.uk</a> to have its own voice, with a clear proposition compared to other JRF channels.</p><p><strong>How</strong>: We expect all written content to meet basic standards around accessibility and for authors to work closely with the Digital Products team to assess whether the proposed content is genuinely original, insightful, likely to have a longevity of value, and is structured in a clear way.</p><p>Next year, we’ll be developing the Digital Product team’s insight and analytics capability which will allow us to gather better data to power decision making.</p><h3>What’s next?</h3><p>We’ll launch a new version of <a href="http://jrf.org.uk/">jrf.org.uk</a> in December 2023. We’ll be using these strategic objectives to drive decisions about our roadmap throughout 2024 and beyond.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f681fa848e75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playback of our discovery project to shape JRF online]]></title>
            <link>https://medium.com/inside-jrf/playback-of-our-discovery-project-to-shape-jrf-online-cccc3db906b7?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/cccc3db906b7</guid>
            <category><![CDATA[usdc]]></category>
            <category><![CDATA[discovery]]></category>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 15:01:40 GMT</pubDate>
            <atom:updated>2020-11-16T08:45:43.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A blue and orange permanent marker is held up to camera in front of two post-it notes" src="https://cdn-images-1.medium.com/max/1024/0*8ppLOEyI4lLrN5qF" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Our discovery with Snook has finished. This blog is a brief trip into where we have come from, what we’ve achieved, and how we reflected on the lessons learned from the project.</p><p><em>This is a joint blog post on our </em><a href="https://medium.com/inside-jrf/discovery-jrf-online-f4193900d94"><em>discovery into JRF online</em></a><em>, from Louise Mushet (Service Designer at Snook), Ben Stuart (Digital Product Officer at JRF), Laure Duchamp (User Researcher at JRF) and Daniel Wigglesworth (Digital Product Manager at JRF).</em></p><h4>JRF’s journey</h4><p><strong>Daniel</strong>: Over the past two years JRF has made significant progress moving into <a href="https://www.jrf.org.uk/blog/creating-social-change-organisation-leading-foundation">a new outcome-oriented social change organisation</a>.</p><p>At JRF we realised that, to create the most significant real-world impact, we needed to take a long hard look at how we operated. Our previous model, based largely on funding, publishing and communicating research, wasn’t facilitating the change we wanted to see.</p><p>These changes to our strategic direction and external profile led us to our need to establish a starting point for the next version of JRF online. At the moment, the services, content, and channels that people outside of our organisation interact with mainly reflect our old model.</p><p><strong>Jude: </strong>As Daniel mentioned the organisation is changing, and what it does is changing too.</p><p>We knew we didn’t have clarity over what the organisation does now, as well as what it might do in the future. Understanding what the organisation does is vital to designing a website that meets the needs of JRF and its users.</p><p>Part of this project sometimes appeared to be broader than just creating a new website. A year ago, this had been confusing to people, but we’d spent time showing people that discovery was a much broader piece of research so that it made sense when we kicked the project off.</p><h4>Discovery so far</h4><p><strong>Louise</strong>: The project as a whole aimed to define a new purpose for the JRF website, one that supports JRF’s mission as a social change organisation.</p><p>We started with <a href="https://medium.com/inside-jrf/organisation-research-for-web-discovery-understanding-our-services-stakeholders-as-well-as-8e3094b37aa2">organisational research</a>. By interviewing JRF colleagues, we were able to form a series of strong assumptions of the motivations, expectations, and journeys of some of our external stakeholders.</p><figure><img alt="Four key stages to the project: kick-off; organisation research; external stakeholder researc; and, final workshop outputs" src="https://cdn-images-1.medium.com/max/1024/1*CfJYX1SM1rdd58xIBtjc4Q.png" /><figcaption>Project stages</figcaption></figure><p>This was followed by further <a href="https://medium.com/inside-jrf/learning-about-users-and-validating-our-assumptions-2299dc875251">user research, with a range of our external stakeholders</a>, to understand what their experiences and hopes for a new JRF website are.</p><p>We took these findings back to JRF colleagues in a series of four workshops.</p><p>The first looked at agreeing on the role the website could play to communicate JRF’s position, and how it can encourage visitors to take action. The second focused on how to include those with lived experience of poverty. The third explored personalisation of services based on geographic location and need. The last aimed to bring all this together to refine the website’s purpose, stakeholders and services.</p><p>The project was a balancing act between getting what we needed for the website, against using the website to hold conversations and understand how people want to engage with JRF in the context of a much <a href="https://medium.com/inside-jrf/five-changes-at-jrf-in-three-years-84c197fbe3d5">wider transformation</a>.</p><h4>Where are we now?</h4><p><strong>Ben: </strong>To round off the project, we held our final show and tell on 6th October 2020 to communicate what we found. It was a brilliant way to not only show the hard work the team has put in over the past four months, and to thank the wider organisation for their engagement and contribution.</p><p>We engaged around 85 people within JRF throughout the course of discovery, all of whom supported our project greatly. They attended our show and tells, were interviewed for organisational research, helped us recruit participants for our external user research, and kept us honest by asking important questions of us.</p><blockquote><em>We couldn’t have achieved our successes on this project without our supportive and talented colleagues inside JRF.</em></blockquote><p><strong>Daniel: </strong>As with any project, it is important that there is an end result. This meant we dedicated time to bring a single set of discovery findings together, and design ideas for the future.</p><p>By adopting a user-centred approach, conducting this discovery project has reduced risk around the construction of a new website. We’ve taken an evidence-based approach and asked — who are JRF’s users and how can we best meet their needs?</p><figure><img alt="What we found out through this project" src="https://cdn-images-1.medium.com/max/1024/1*2VlpXxbTyzzd7iYFoIdrhg.png" /><figcaption>Summary of what we accomplished</figcaption></figure><p>Our final deliverable shows work that has been accomplished, and can be used as a roadmap to continue areas for delivery and further investigation in the next phase of our work. It includes:</p><ol><li>A vision for JRF online, and how the website can help JRF achieve its mission.</li><li>JRF’s stakeholders. These categories are a helpful way to group needs, and consider what and how services should be delivered to best meet them.</li><li>The current website experience. Users commonly come to the website for JRF’s research. It can be difficult to find what you are looking for, and it’s clear current website doesn’t reflect the new work that JRF does. We need to be clear that a website is part of wider user journeys and clearer on what we want people to do to help reduce poverty.</li><li>JRF services. Through this project, we have developed service categories to help us think about how we meet user needs, and which channels we use.</li><li>JRF’s transformation journey. This project was not about a website alone. It has been about considering how a website is part of JRF’s wider transformation.</li><li>Artefacts from discovery: our research findings; user stories created from our user research; opportunity areas for the next phase; our research prototypes; and, abacklog of items to work through ahead of the next phase.</li></ol><h4>Project reflections and lessons learned</h4><p><strong>Louise: </strong>After an intensive fifteen weeks of working together, we ran a final retrospective to share reflections and lessons learned.</p><p>This was facilitated by JRF’s new Delivery Manager, Holly Clark. It was the perfect forum to think about what had worked well and what we could do differently on a similar project next time. These can be categorised into three main themes:</p><p><strong>Scope and deliverables</strong></p><ul><li>It is important to involve project sponsors in discussions at the beginning; doing so means scope can be agreed clearly, and everyone is aware of the end goal and any potential problems.</li><li>This project was large in scope and multifaceted. We agreed that, if we were to do this again, we would be more realistic about what we can deliver in the project timeframe.</li><li>For the success of the discovery to translate into the build for JRF online, we need the space to start the next stage of work.</li></ul><p><strong>Planning and time</strong></p><ul><li>If there’s a lag between commissioning and starting work, keep in touch, so everyone knows what’s going on, and nobody is surprised by things like changes in staffing and scope.</li><li>Make sure logistics, like annual leave, are dealt with at the start of the project so their impact against deliverables can be mitigated.</li><li>Being resourced on only one project at a time means you can make great progress and be completely focused on the project at hand.</li><li>It’s always worth investing more time in synthesising what you’ve learned during your research, and learning how to turn these learnings into valuable insight statements. One hour of research usually equates to at least one hour of synthesis time.</li></ul><p><strong>Ways of working</strong></p><ul><li>Instead of the project group trying to deliver all of our communications, we found advocates in the organisation to act as cheerleaders and take our messaging forward for us. This gained us greater buy-in across the organisation. We should do more of this.</li><li>Create structure around a project, clarify roles and responsibilities and make sure everyone has a say.</li><li>Give more space to thinking about what skills beyond that of the project team would be valuable, and who outside of the team could be drawn upon for their expertise.</li><li>As is natural in complex projects, conversations can end up going round in circles and disagreements can arise. It’s important when this happens to take a step back and think about what can be done practically to enable the team to continue moving forward.</li><li>Experimenting with different methods of communication means everyone has the same information and is on the same page without constantly having to be in face-to-face meetings.</li></ul><h4>Beyond discovery: the next steps for JRF</h4><p><strong>Daniel: </strong>At the moment, we’re still communicating the outcome of our project whilst working with decision makers within JRF in order to clarify budgets, timelines and scope for the next stages of work.</p><p>Fortunately, working with Snook has given us a shared vision for the purpose of a JRF website, and how it connects with other channels. We have also gained a clearer sense of our services, who our users are across those services, and what they need and want from JRF.</p><p>We have a fantastic platform to provide both a convincing and compelling summary of our findings, and the decisions we have to make as an organisation to support the work. These are important things.</p><p>Keep an eye on <a href="https://medium.com/inside-jrf">Inside JRF medium</a> to see how we get on.</p><h4>And finally…</h4><p><strong>Daniel</strong>: In order to finish our discovery and do justice to the hard work and talent within our small but perfectly formed team, I’d like to share a huge thank you to the members of the core project teams from JRF and Snook who worked on this project remotely during exceptionally challenging external circumstances.</p><p>Snook: Louse Mushet, Rebecca Squirrell and Valerie Carr.</p><p>JRF: Ben Stuart, Daniel Wigglesworth, Jude Webb, Laure Duchamp and Sarah Mace. We would also like to thank Hannah McCulloch and Heather Lister who became honorary members of our team with a watching brief over interdependent work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cccc3db906b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-jrf/playback-of-our-discovery-project-to-shape-jrf-online-cccc3db906b7">Playback of our discovery project to shape JRF online</a> was originally published in <a href="https://medium.com/inside-jrf">Inside the Joseph Rowntree Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovery: JRF online]]></title>
            <link>https://medium.com/inside-jrf/discovery-jrf-online-f4193900d94?source=rss-dfd23cede124------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4193900d94</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[discovery]]></category>
            <category><![CDATA[hcd]]></category>
            <category><![CDATA[usdc]]></category>
            <dc:creator><![CDATA[Daniel Wigglesworth]]></dc:creator>
            <pubDate>Tue, 25 Aug 2020 10:27:34 GMT</pubDate>
            <atom:updated>2020-10-13T11:00:45.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Young girl looks out to sea through binoculars on a pier" src="https://cdn-images-1.medium.com/max/1024/0*-tDCaMRSXouymAoH" /><figcaption>Photo by <a href="https://unsplash.com/@enka80?utm_source=medium&amp;utm_medium=referral">--&gt; paypal.me/ninekoepfer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A look into our discovery to align the Joseph Rowntree Foundation’s (JRF) online presence with our evolution into a social change organisation.</p><h4>Pivot to social change</h4><p>As Claire Ainsley laid out in her blog, over the past two years JRF has made significant progress moving into <a href="https://www.jrf.org.uk/blog/creating-social-change-organisation-leading-foundation">a new outcome oriented social change organisation</a>.</p><p>These changes to our strategic direction and external profile led us to our need to establish a starting point for the next version of JRF online, as the services, content, and channels that people outside of our organisation interact with are still mostly geared towards JRF being a think tank.</p><p>We’ve also been doing a lot of work internally to transform our ways of working: to create a new operating model; form outcome oriented delivery teams; and, create our design principles and playbook. We’re becoming digital from the inside out.</p><p>Our website <a href="http://jrf.org.uk/">jrf.org.uk</a> is a gateway into JRF. Most people who interact with JRF touch the website at some point in their journey. Now we are moving on to transform our external channels.</p><p>In doing discovery, we are also defining the requirements of the JRF website to deliver its strategic outcomes, and define the services that will be delivered on or accessed through the JRF website.</p><p>In addition to this, through discovery we are using our website to hold conversations and understand how people want to engage with JRF and how we need to change our offering. JRF Online is central to our digital transformation; it’s a touchpoint that exemplifies a much wider change for us.</p><p>The insights we find will help us to develop our external channels to showcase our outcomes, solutions and stories in the best possible way to achieve social change.</p><h4>Our discovery with Snook</h4><p>Following a three-part tender process that I led earlier in the year, we selected <a href="https://wearesnook.com/">Snook</a> to partner with us and work alongside our internal team to deliver our discovery using design-led approaches.</p><p>Together we are defining a shared vision for the purpose of the JRF website, what it is for and isn’t for, and how it connects with other channels. We are gaining a clear sense of who our users are across all of our services and what they need and want from JRF.</p><p>Crucially, we are gaining a clearer view of what JRF services are.</p><p>In doing discovery, we are building a shared pool of knowlege to drive our work, to inform design decisions and we are continuing to develop a common language between what is still a recently formed <a href="https://medium.com/@dwigglesworth/were-looking-for-a-content-designer-9fc5cc633eb9">user-centred design team within JRF</a>.</p><p>The discovery started at the end of June, we are currently more than half way through and will be complete by the first week of October.</p><p>We have just completed a phase of organisational research, and have just agreed on priorities for a low-fidelity wireframe prototype.</p><p>Over the next three weeks we will take the prototype into external user research / interviews. This is all very exciting and another step forward for members of the team.</p><h4>One last thing</h4><p>Members of the team working on this discovery, they’ll want to share things they learn as a consequence of discovery too (key insights and observations). If you are interested, do follow our <a href="https://medium.com/inside-jrf">Inside JRF medium</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4193900d94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-jrf/discovery-jrf-online-f4193900d94">Discovery: JRF online</a> was originally published in <a href="https://medium.com/inside-jrf">Inside the Joseph Rowntree Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>