<?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 Nandula Asel Karunasingha on Medium]]></title>
        <description><![CDATA[Stories by Nandula Asel Karunasingha on Medium]]></description>
        <link>https://medium.com/@nandulak?source=rss-afa5ed721928------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AbX7I--DailXrGCNhje2eQ.png</url>
            <title>Stories by Nandula Asel Karunasingha on Medium</title>
            <link>https://medium.com/@nandulak?source=rss-afa5ed721928------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:08:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nandulak/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[Web Development Baseline Essentials for Sri Lankan Research Non‑Profits]]></title>
            <link>https://nandulak.medium.com/web-development-baseline-essentials-for-sri-lankan-research-non-profits-f83a45baa6ee?source=rss-afa5ed721928------2</link>
            <guid isPermaLink="false">https://medium.com/p/f83a45baa6ee</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Nandula Asel Karunasingha]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 17:58:36 GMT</pubDate>
            <atom:updated>2025-11-02T14:51:30.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l8-OaSqkjWBxELOu" /><figcaption>Snapshot from “Thank you for practicing Open Science” by PLOS Media</figcaption></figure><p>Originally published on LinkedIn:</p><p><a href="https://www.linkedin.com/pulse/web-development-baseline-essentials-sri-lankan-karunasingha-3fdrc/">Web Development Baseline Essentials for Sri Lankan Research Non‑Profits</a></p><h3>Doing More with Less in Sri Lanka’s Research Sector</h3><p>Sri Lanka’s research-oriented non-profit organizations face a perfect storm of limited funding and technical capacity. With the recent loss of major donor funding (nearly 50% of NGO funding came from <a href="https://www.linkedin.com/company/usaid/">USAID</a>, roughly LKR 15 billion in the last year, according to an article by <a href="https://www.linkedin.com/in/miriam-alphonsus-959586220/">Miriam Alphonsus</a>), these organizations must maximize every rupee. A strong web presence is no longer optional. It’s essential for global visibility, local outreach and credibility. Crucially, this must be achieved on tight budgets and often without dedicated IT staff. The goal of this article is to outline minimum baseline web development essentials, from performance and accessibility to security and research/ResTech integrations, so that Sri Lankan research non-profits can procure web development services wisely and avoid common pitfalls.</p><h3>1. Performance and Optimization</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lh5IOz4llMeJLldF" /><figcaption>By Hardik Katahari, Opensignal</figcaption></figure><p>In Sri Lanka, internet access is growing but still uneven. As of 2023, only 52% of Sri Lanka’s population is connected to the internet, according to the <a href="https://www.linkedin.com/company/international-telecommunication-union/">International Telecommunication Union</a>, out of which 82.6% spent less than 50% of their time on WiFi, with 37.1% of internet users solely relying on Mobile, according to <a href="https://www.linkedin.com/company/opensignal/">Opensignal</a>. This means research organizations’ websites must be mobile-friendly, lightweight, and fast-loading to reach audiences on smartphones and under inconsistent network conditions. Performance isn’t just nice to have. It directly impacts engagement and even search visibility. <a href="https://www.linkedin.com/company/google/">Google</a>’s <em>Core Web Vitals</em> metrics (developed by <a href="https://www.linkedin.com/showcase/chrome-for-developers/">Chrome for Developers</a>), for example, are a global benchmark for user experience, measuring loading speed, interactivity, and visual performance. Ensuring your site meets these benchmarks (e.g. fast page load: Largest Contentful Paint under 2.5s, quick first input response: First Input Delay under 100ms, and stable layouts: Cumulative Layout Shift &lt;0.1) will keep visitors on your pages and signal professionalism. Basic steps like optimizing images, enabling browser caching, using a Content Delivery Network (CDN), and adopting responsive design all contribute to a performant site. In short, a research non-profit’s website should load quickly even on a basic smartphone. This broad accessibility is part of its mission impact.</p><h3>2. Accessibility and Inclusivity</h3><p>Accessibility is a non-negotiable baseline in modern web development. Globally, the gold standard is the <a href="https://www.linkedin.com/company/w3c/">W3C</a>’s <em>Web Content Accessibility Guidelines (WCAG) 2.1</em>, an internationally recognized standard for making web content usable for people with disabilities. At minimum, sites should aim for WCAG 2.1 Level AA compliance, meaning text alternatives for images, proper color contrast, keyboard navigability, captions for videos, etc., so that content is perceivable and operable for users with visual, auditory, motor or cognitive impairments. An accessible site not only serves differently-abled users but often improves overall usability for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/0*HUr_-fohfVu2Bl3Z" /><figcaption>Hatton trilingual railway sign by Krankman, via Wikimedia Commons</figcaption></figure><p>Inclusivity in Sri Lanka also means addressing language needs. Wherever feasible, research organizations should offer content in Sinhala and Tamil alongside English. Using Unicode for Sinhala/Tamil text is now the norm. Sri Lanka already has hundreds of trilingual government websites using Unicode fonts. A multilingual, accessible website ensures that policymakers, community stakeholders and the general public can engage with research findings in their preferred language. In practice, this could mean at least providing summaries of key research or an “About Us” page in Sinhala and Tamil. It’s both a legal expectation in government contexts and a best practice for non-profits striving to be inclusive in a diverse society.</p><h3>3. Privacy and Data Protection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BaZLfKvdkZaWbyb0" /><figcaption>Title page — Personal Data Protection Act, № 9 of 2022</figcaption></figure><p>Even resource-strapped non-profits must take data privacy seriously. Globally, user privacy is codified in regulations like the EU’s GDPR, and Sri Lanka has followed suit with its own Personal Data Protection Act (PDPA) №9 of 2022, the first comprehensive privacy law in South Asia, modelled closely after GDPR. The PDPA brings Sri Lanka in line with international data privacy movements. For a research non-profit’s website, this translates to a few baseline requirements.</p><h4>3.1. Privacy Policy</h4><p>Have a clear, easily accessible privacy policy detailing what user data you collect (even if just through contact forms or newsletter sign-ups) and how it’s used. Transparency is a key principle under both GDPR and PDPA.</p><h4>3.2. Consent and Minimal Data Collection</h4><p>If your site uses cookies or tracking, implement a consent banner in compliance with the standards of “informed, explicit consent”. Only collect personal data that is strictly necessary for your operations. The PDPA and GDPR both emphasize data minimization and purpose limitation.</p><h4>3.3. Data Security and Accountability</h4><p>Ensure any personal information collected (e.g. emails of newsletter subscribers or survey respondents) is stored securely. Use reputable hosting, encrypt data in transit (HTTPS), and restrict access to sensitive data. Under PDPA, organizations may be required to appoint a Data Protection Officer and must report breaches to authorities. While a small NGO might not formally need a DPO, the spirit is to assign someone responsibility for data protection. Basic steps like password-protecting databases, using updated software, and regular backups go a long way.</p><p>Compliance with privacy standards isn’t just about avoiding penalties. It builds trust with your audience. A research non-profit often gathers information from communities or website visitors. Showing that you guard their privacy will enhance your credibility. Remember, privacy is now a boardroom issue, not just a tech issue. Even donors and partners may vet your data practices.</p><h3>4. Cybersecurity Fundamentals</h3><p>Hand in hand with privacy is basic cybersecurity. Non-profits are not immune to web attacks. In fact, globally, many NGOs have been targets of defacement, data theft, or ransomware due to perceived weaker defences according to <a href="https://www.linkedin.com/company/crowdstrike/">CrowdStrike</a>. Every web development project for your organization should include fundamental security measures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DF7bk4VEgV5gc2dD" /><figcaption>CSF Functions, NIST Cybersecurity Framework 2.0</figcaption></figure><h4>4.1. HTTPS Encryption</h4><p>Your website <em>must</em> have an SSL/TLS certificate (the site should load with “https://” and show a padlock). Encryption is essential to protect data in transit and is now standard practice. Even <a href="https://www.linkedin.com/company/google/">Google</a> uses HTTPS as a ranking signal for websites. Services like <a href="https://www.linkedin.com/company/lets-encrypt/">Let’s Encrypt</a> provide certificates for free, so there’s no excuse for a non-secure site.</p><h4>4.2. Secure Development and Hosting</h4><p>Ensure the developers follow secure coding guidelines. A widely respected reference is the <a href="https://www.linkedin.com/company/owasp/">OWASP® Foundation</a> <em>OWASP Top 10</em>, a globally recognized list of the most critical web application security risks. You don’t need to be a security expert, but you should demand that your vendor or IT team mitigate common vulnerabilities (such as SQL injection, cross-site scripting, etc.). Ask if they conduct security testing before launch. Also, host your site with a reputable provider that offers security features (firewalls, DDoS protection, automated backups).</p><h4>4.3. Software Updates and Maintenance</h4><p>Many research nonprofits use CMS platforms like <a href="https://www.linkedin.com/company/wordpress/">WordPress</a> or <a href="https://www.linkedin.com/company/drupal-project/">Drupal</a> for ease. These are fine, but only if kept up-to-date. Outdated plugins or CMS versions are a top cause of website breaches. Ensure your contract includes periodic maintenance or train someone on your staff to apply updates. This also includes maintaining data backups offline in case of an attack, so you can recover quickly without paying ransoms.</p><h4>4.4. Access Control</h4><p>Use strong passwords for all admin accounts and change them periodically. Limit the number of people with administrator access to the site, following the principle of least privilege. If handing over to a web firm, make sure to reset credentials after the engagement.</p><h4>4.5. Staff Awareness</h4><p>Finally, human error is often the weakest link. Even with minimal staff, establish basic cyber hygiene. For example, don’t reuse passwords, be cautious of email attachments (to prevent malware), and use two-factor authentication where possible. Organizations like the <a href="https://www.linkedin.com/company/the-center-for-internet-security/">Center for Internet Security</a> (CIS) or guides from <a href="https://www.linkedin.com/company/techsoup/">TechSoup</a> for Nonprofits provide simple checklists that non-technical staff can follow.</p><p>By covering these bases, you protect not just your website, but your organization’s reputation and sensitive research data. Cybersecurity might sound technical, but at its core, it’s about risk management, an essential for any entity, whether for-profit or non-profit.</p><h3>5. Integration with Research Platforms (ResTech)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aia50VeXmnEbVtgc" /><figcaption>What is a DOI?, DOI Foundation</figcaption></figure><p>To truly leverage your website as a research non-profit, consider integrating it with a global research infrastructure. This is the “ResTech” piece (research technology) that can amplify your impact. Two key integration points are researcher identities and research outputs:</p><h4>5.1. ORCID for Researcher Profiles</h4><p><a href="https://www.linkedin.com/company/orcid/">ORCID</a> (Open Researcher and Contributor ID) is a global system of unique identifiers for researchers. Encourage your researchers or authors to obtain free ORCID iDs and showcase those on your website (for example, on profile pages or under article authorship). By doing so, you ensure that their publications and contributions are correctly attributed to them worldwide, solving name ambiguity issues. ORCID integration also signals to funders and collaborators that your organization is plugged into international scholarly networks. Many journal submission systems and grant applications now use ORCID. Having it on your site creates a seamless loop of recognition and credibility.</p><h4>5.2. DOIs and Open Access Repositories</h4><p>If your organization publishes research reports, policy briefs, or datasets, use persistent identifiers like DOIs (Digital Object Identifiers governed by the <a href="https://www.linkedin.com/company/doi-foundation-inc/">DOI Foundation</a>) for them. Services like <a href="https://www.linkedin.com/company/crossref/">Crossref</a> can register DOIs for your publications, which makes them easier to find and cite globally. <a href="https://www.linkedin.com/company/crossref/">Crossref</a> is part of the open scholarly infrastructure that links research outputs across the world. You might not manage this directly (if you publish in journals, the journal will handle DOIs), but at least ensure that any publication metadata on your site (titles, authors, abstracts) includes a reference to the DOI or external database link. Also consider using an institutional repository or platforms like Zenodo or <a href="https://www.linkedin.com/company/figshare/">Figshare</a> for sharing datasets and reports openly, then link those on your site. The FAIR principles (Findable, Accessible, Interoperable, Reusable) for research data are a global standard. Your website can help fulfil the “FAIRness” of your outputs by pointing to where data or papers can be accessed.</p><h4>5.3. Integrations for Efficiency</h4><p>Depending on your needs, integrate simple tools that enhance research communication. For instance, embedding a <a href="https://www.linkedin.com/company/google/">Google</a> Scholar profile or citations widget for your publications page can auto-update new entries. If you conduct surveys or field research, linking to data dashboards (e.g. via <a href="https://www.linkedin.com/company/salesforce/">Salesforce</a> <a href="https://www.linkedin.com/company/tableau-software/">Tableau</a>, <a href="https://www.linkedin.com/company/google/">Google</a> Looker Studio or <a href="https://www.linkedin.com/company/microsoft/">Microsoft</a> Power BI) on your site can showcase results dynamically. These integrations should be planned from the start. Discuss with your developer about API integrations or plugins to ensure your site isn’t a dead-end silo but part of a connected research ecosystem.</p><p>In essence, your website should serve as a hub that not only presents information but also connects to global research standards and platforms. This increases your non-profit’s legitimacy and makes life easier for your researchers by reducing duplicate data entry and improving discoverability.</p><h3>6. Sustainable Maintenance and Vendor Management</h3><p>One of the biggest challenges for non-profits is maintaining the website after launch. To avoid being “held hostage” by a vendor or facing exorbitant upkeep costs, keep these baseline practices in mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MhdCEqNM_6MLbwTU" /><figcaption>“The dimensions of maintenance” by E. Burton Swanson</figcaption></figure><h4>6.1. Choose the Right CMS and Tech Stack</h4><p>Opt for widely-used open-source content management systems (CMS) like <a href="https://www.linkedin.com/company/wordpress/">WordPress</a>, <a href="https://www.linkedin.com/company/drupal-project/">Drupal</a>, or <a href="https://www.linkedin.com/company/joomla/">Joomla!</a> unless you have a compelling reason to custom-build. Open-source solutions are free and have large support communities. Importantly, they avoid vendor lock-in. You own and control the code and can move to another vendor if needed. A proprietary platform might tie you to one provider and limit flexibility, which is risky for a small organization.</p><h4>6.2. Own Your Domain and Hosting</h4><p>Always register the website’s domain name under the organization’s account (not the developer’s personal account) and ensure you have full access to the hosting/server control panel. This way, if you part ways with a web developer or agency, you retain control. It’s a simple step that can prevent nightmare scenarios where an ex-vendor “disappears” with your domain or data.</p><h4>6.3. Documentation and Training</h4><p>As part of the web development deliverables, request basic documentation. E.g. how to update content, how to perform backups and any custom features explanation. Also have at least one staff member trained on using the CMS for everyday updates (posting articles, editing text, etc.). Modern CMSs are user-friendly, but a short training session can boost staff confidence and reduce dependence on outside help for minor changes.</p><h4>6.4. Maintenance Plan</h4><p>Websites are like gardens that need regular tending. If you lack internal IT staff, consider budgeting for a maintenance contract (monthly or quarterly) with a freelancer or firm to handle security updates, uptime monitoring, and technical support. Alternatively, set reminders to check for CMS/plugin updates yourself and use managed hosting that provides some automated maintenance. The key is not to launch and forget. A bit of proactive care can prevent major breakdowns (and major costs) later.</p><h4>6.5. Scalability and Future-Proofing</h4><p>While sticking to “baseline essentials”, be mindful of the future. Pick solutions that allow your site to grow. For example, if you foresee adding a publications database or a forum for researchers, ensure the platform you choose can accommodate plugins or extensions for those. Likewise, design with flexibility. Today’s site might be a simple informational hub, but tomorrow you might integrate e-learning modules or a data portal. Planning for extensibility now will save money down the line.</p><p>Finally, beware of anyone who promises the moon for an ultra-low price or conversely, those who push overly complex solutions you don’t need. The checklist below summarizes the core essentials you should require. Use it when discussing with potential web developers or creating an RFP to show that you’re informed and focused on long-term value.</p><h3>Web Development Essentials Checklist for Research Non-Profits</h3><p>Use this checklist when planning a website revamp or hiring a web development service. It encapsulates the baseline features and standards discussed above:</p><h4>✅ Fast, Mobile-Friendly Site</h4><p>Responsive design and optimized performance (meets Core Web Vitals thresholds) for accessibility on all devices.</p><h4>✅ Web Accessibility</h4><p>Conforms to WCAG 2.1 AA guidelines (alt text, proper headings, captions, keyboard navigation) to support users with disabilities.</p><h4>✅ Local Language Support</h4><p>Content available in English + Sinhala/Tamil as needed; Unicode fonts for Sri Lankan scripts to display correctly.</p><h4>✅ HTTPS Security</h4><p>SSL certificate installed site-wide (HTTPS by default) to protect user data and signal trust.</p><h4>✅ Privacy Compliance</h4><p>Privacy policy posted. user data collection minimized and consensual, aligning with Sri Lanka’s PDPA and global GDPR principles.</p><h4>✅ Basic Security Hardening</h4><p>Up-to-date CMS/software, secure admin passwords, limited access accounts, firewall/antivirus on server, and regular backups in place.</p><h4>✅ OWASP Awareness</h4><p>The developer has addressed common vulnerabilities (OWASP Top 10) — e.g., no obvious injection flaws, proper input validation, etc.</p><h4>✅ Research Integrations</h4><p>ORCID iDs for researcher profiles; DOIs or stable links for publications; integration with any relevant research repositories or databases.</p><h4>✅ Ownership &amp; Control</h4><p>Organization holds credentials for the domain name, hosting, and CMS admin. Not solely the vendor.</p><h4>✅ Open-Source CMS</h4><p>Unless requirements dictate otherwise, use an open-source CMS to avoid licensing fees and vendor lock-in.</p><h4>✅ Training &amp; Docs</h4><p>Admin guide or training provided so staff can update content and understand site basics.</p><h4>✅ Maintenance Plan</h4><p>Clear plan for ongoing updates, security patches, and support, whether via internal responsibility or an external maintenance contract.</p><p>By insisting on these baseline essentials, Sri Lankan research non-profits can develop cost-effective, robust websites that further their mission. In an era where funding is scarce and digital reach is crucial, a well-built website is a force multiplier amplifying research impact, engaging stakeholders, and safeguarding the organization’s integrity online. Armed with the above knowledge, non-profit teams can confidently collaborate with web developers to build platforms that stand the test of time. The web should work for you, not against you.</p><h3>Further Reading</h3><h4>Accessibility &amp; Language</h4><ul><li><a href="https://www.linkedin.com/company/w3c/">W3C</a>. (2024, December 12). <em>Web Content Accessibility Guidelines (WCAG) 2.2</em>. <a href="https://www.w3.org/TR/WCAG22/">https://www.w3.org/TR/WCAG22/</a></li><li><a href="https://www.linkedin.com/company/w3c/">W3C</a> Web Accessibility Initiative. (2020, April 28). <em>WCAG-EM Overview: Website accessibility conformance Evaluation Methodology</em>. Web Accessibility Initiative (WAI). <a href="https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/">https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/</a></li><li>The Noto Project Authors. (2022). <em>Noto Sans Sinhala</em>. <a href="https://www.linkedin.com/company/google-fonts/">Google Fonts</a>. <a href="https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala">https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala</a></li><li>The Noto Project Authors. (2022). <em>Noto Sans Tamil</em>. <a href="https://www.linkedin.com/company/google-fonts/">Google Fonts</a>. <a href="https://fonts.google.com/noto/specimen/Noto+Sans+Tamil">https://fonts.google.com/noto/specimen/Noto+Sans+Tamil</a></li></ul><h4>Performance &amp; UX</h4><ul><li><a href="https://www.linkedin.com/company/googlefordevelopers/">Google for Developers</a>. (2025, February 4). <em>Understanding Core Web Vitals and Google search results</em>. <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">https://developers.google.com/search/docs/appearance/core-web-vitals</a></li><li><a href="https://www.linkedin.com/in/waltonphilip/">Philip Walton</a>. (2024, October 31). <em>Web Vitals</em>. <a href="http://web.dev/">web.dev</a>. <a href="https://web.dev/articles/vitals">https://web.dev/articles/vitals</a></li></ul><h4>Security &amp; resilience</h4><ul><li><a href="https://www.linkedin.com/company/nist/">National Institute of Standards and Technology (NIST)</a>. (2023). <em>The NIST Cybersecurity Framework (CSF) 2.0</em>. <a href="https://doi.org/10.6028/nist.cswp.29">https://doi.org/10.6028/nist.cswp.29</a></li><li><a href="https://www.linkedin.com/company/owasp/">OWASP® Foundation</a>. (2025). <em>OWASP Application Security Verification Standard (ASVS)</em>. <a href="https://owasp.org/www-project-application-security-verification-standard/">https://owasp.org/www-project-application-security-verification-standard/</a></li><li><a href="https://www.linkedin.com/company/owasp/">OWASP® Foundation</a>. (2025b, July). <em>OWASP Top Ten</em>. <a href="https://owasp.org/www-project-top-ten/">https://owasp.org/www-project-top-ten/</a></li><li><a href="https://www.linkedin.com/company/cloudflare/">Cloudflare</a>, Inc. (n.d.). <em>What is a WAF? | Web Application Firewall explained</em>. Learning Center. <a href="https://www.cloudflare.com/en-gb/learning/ddos/glossary/web-application-firewall-waf/">https://www.cloudflare.com/en-gb/learning/ddos/glossary/web-application-firewall-waf/</a></li><li><a href="https://www.linkedin.com/company/internet-security-research-group/">Internet Security Research Group (ISRG)</a>. (2025, August 2). <em>How it works</em>. <a href="https://www.linkedin.com/company/lets-encrypt/">Let’s Encrypt</a>. <a href="https://letsencrypt.org/how-it-works/">https://letsencrypt.org/how-it-works/</a></li><li><a href="https://www.linkedin.com/in/robewaschuk/">Rob E.</a> (2016). <em>Monitoring Distributed Systems</em> (<a href="https://www.linkedin.com/in/betsy-beyer/">Betsy Beyer</a>, Ed.). Site Reliability Engineering. <a href="https://sre.google/sre-book/monitoring-distributed-systems/">https://sre.google/sre-book/monitoring-distributed-systems/</a></li></ul><h4>Privacy &amp; data protection</h4><ul><li><a href="https://www.linkedin.com/company/parliament-of-sri-lanka/">Parliament of Sri Lanka</a>. (2022). Personal Data Protection Act, №9 of 2022. Department of Government Printing. <a href="https://documents.gov.lk/view/acts/2022/3/09-2022_E.pdf">https://documents.gov.lk/view/acts/2022/3/09-2022_E.pdf</a></li><li><a href="https://www.linkedin.com/company/european-parliament/">European Parliament</a>, <a href="https://www.linkedin.com/company/eucouncil/">Council of the European Union</a>. (2016). Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (Text with EEA relevance). <em>Official Journal of the European Union</em>, <em>119</em>, 32016R0679. <a href="https://eur-lex.europa.eu/eli/dir/2016/680/oj">https://eur-lex.europa.eu/eli/dir/2016/680/oj</a></li><li><a href="https://www.linkedin.com/company/eu-edpb/">European Data Protection Board</a>. (2020). <em>Guidelines 05/2020 on consent under Regulation 2016/679</em>. <a href="https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_202005_consent_en.pdf">https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_202005_consent_en.pdf</a></li><li>Working Party on the Protection of Individuals with regard to the Processing of Personal Data. (2017). <em>Guidelines on Data Protection Impact Assessment (DPIA) and determining whether processing is “likely to result in a high risk” for the purposes of Regulation 2016/679</em> (wp248rev.01). <a href="https://www.linkedin.com/company/european-commission/">European Commission</a>. <a href="https://ec.europa.eu/newsroom/article29/items/611236/en">https://ec.europa.eu/newsroom/article29/items/611236/en</a></li></ul><h4>Research integrity &amp; discoverability</h4><ul><li><a href="https://www.linkedin.com/in/mark-wilkinson-6656741/">Mark Wilkinson</a>, <a href="https://www.linkedin.com/in/dumontier/">Michel Dumontier</a>, <a href="https://www.linkedin.com/in/ijjaalbersberg/">IJsbrand Jan Aalbersberg</a>, <a href="https://www.linkedin.com/in/gaby-appleton-16a63b/">Gaby Appleton</a>, <a href="https://www.linkedin.com/in/myles-axton-1343682/">Myles Axton</a>, <a href="https://www.linkedin.com/in/arie-baak-368276/">Arie Baak</a>, <a href="https://www.linkedin.com/in/niklas-blomberg-a711167/">Niklas Blomberg</a>, <a href="https://www.linkedin.com/in/jan-willem-boiten-5bba513/">Jan-Willem Boiten</a>, <a href="https://www.linkedin.com/in/luizbonino/">Luiz Olavo Bonino da Silva Santos</a>, <a href="https://www.linkedin.com/in/philip-bourne-b98921/">Philip Bourne</a>, <a href="https://www.linkedin.com/in/jildau-bouwman/">Jildau Bouwman</a>, Anthony J. Brookes, <a href="https://www.linkedin.com/in/timclark/">Tim Clark</a>, <a href="https://www.linkedin.com/in/merce-crosas-9a22776/">Merce Crosas</a>, <a href="https://www.linkedin.com/in/ingriddillo/">Ingrid Dillo</a>, <a href="https://www.linkedin.com/in/olivierdumon/">Olivier Dumon</a>, <a href="https://www.linkedin.com/in/scottcedmunds/">Scott Edmunds</a>, <a href="https://www.linkedin.com/in/chrisevelo/">Chris Evelo</a>, <a href="https://www.linkedin.com/in/richardfinkers/">Richard Finkers</a>, . . . <a href="https://www.linkedin.com/in/barend-mons-a494142/">Barend Mons</a>. (2016). The FAIR Guiding Principles for scientific data management and stewardship. <em>Scientific Data</em>, <em>3</em>(1). <a href="https://doi.org/10.1038/sdata.2016.18">https://doi.org/10.1038/sdata.2016.18</a></li><li><a href="http://schema.org/">Schema.org</a>. (2025, September 4). <em>Dataset — </em><a href="http://schema.org/"><em>Schema.org</em></a><em> Type</em>. <a href="https://schema.org/Dataset">https://schema.org/Dataset</a></li><li><a href="http://schema.org/">Schema.org</a>. (2025, September 4). <em>ScholarlyArticle — </em><a href="http://schema.org/"><em>Schema.org</em></a><em> Type</em>. <a href="https://schema.org/ScholarlyArticle">https://schema.org/ScholarlyArticle</a></li><li><a href="https://www.linkedin.com/company/orcid/">ORCID</a>. (2025, August 6). <em>ORCID for Researchers</em>. <a href="https://info.orcid.org/researchers/">https://info.orcid.org/researchers/</a></li><li><a href="https://www.linkedin.com/in/martyn-rittman/">Martyn Rittman</a>. (2025, March 2). <em>Setting up as a member</em>. Crossref. <a href="https://www.crossref.org/documentation/member-setup/">https://www.crossref.org/documentation/member-setup/</a></li><li><a href="https://www.linkedin.com/company/openaire-eu/">OpenAIRE AMKE</a>. (2023, July 8). <em>Zenodo — A universal repository for all your research outcomes</em>. OpenAIRE. <a href="https://www.openaire.eu/zenodo-guide">https://www.openaire.eu/zenodo-guide</a></li><li><a href="https://www.linkedin.com/company/center-for-open-science/">Center for Open Science</a>. (2023). <em>The Open Science Framework</em>. <a href="https://www.cos.io/products/osf">https://www.cos.io/products/osf</a></li></ul><h4>Domain Name Registration</h4><ul><li><a href="https://www.linkedin.com/company/icann/">ICANN</a>. (2017, June 20). <em>Registering domain names</em>. <a href="https://www.icann.org/resources/pages/register-domain-name-2017-06-20-en">https://www.icann.org/resources/pages/register-domain-name-2017-06-20-en</a></li><li><a href="https://www.linkedin.com/company/lk-domain-registry/">LK Domain Registry</a>. (2023, May). <em>How to register a domain</em>. <a href="https://www.domains.lk/how-to-register-a-domain/">https://www.domains.lk/how-to-register-a-domain/</a></li></ul><h4>SEO, sitemaps &amp; verification</h4><ul><li><a href="https://www.linkedin.com/showcase/googlesearchcentral/">Google Search Central</a>. (2025, February 4). <em>Search Engine Optimization (SEO) Starter Guide</em>. <a href="https://www.linkedin.com/company/googlefordevelopers/">Google for Developers</a>. <a href="https://developers.google.com/search/docs/fundamentals/seo-starter-guide">https://developers.google.com/search/docs/fundamentals/seo-starter-guide</a></li><li><a href="https://www.linkedin.com/showcase/googlesearchcentral/">Google Search Central</a>. (2025, March 6). <em>Learn about sitemaps</em>. <a href="https://www.linkedin.com/company/googlefordevelopers/">Google for Developers</a>. <a href="https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview">https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview</a></li><li><a href="https://www.linkedin.com/company/wordpress/">WordPress</a>. (2025, August 12). <em>Find your sitemap</em>. <a href="http://wordpress.com/">WordPress.com</a> Support. <a href="https://wordpress.com/support/sitemaps/">https://wordpress.com/support/sitemaps/</a></li></ul><h4>WordPress operations</h4><ul><li><a href="https://www.linkedin.com/company/wordpress/">WordPress</a>. (2023, March 28). <em>Hardening WordPress — Advanced Administration handbook</em>. WordPress Developer Resources. <a href="https://developer.wordpress.org/advanced-administration/security/hardening">https://developer.wordpress.org/advanced-administration/security/hardening</a></li><li><a href="https://www.linkedin.com/company/wordpress/">WordPress</a>. (2024, September 20). <em>Roles and capabilities</em>. Documentation. <a href="https://wordpress.org/documentation/article/roles-and-capabilities/">https://wordpress.org/documentation/article/roles-and-capabilities/</a></li><li><a href="https://www.linkedin.com/company/wordpress/">WordPress</a>. (2023, April 14). <em>Revisions</em>. Documentation. <a href="https://wordpress.org/documentation/article/revisions/">https://wordpress.org/documentation/article/revisions/</a></li><li><a href="https://www.linkedin.com/in/parthernstrom/">🧑💻 Pär Thernström</a>. (2025, September 2). <em>Simple History — track, log, and audit WordPress changes</em>. <a href="http://wordpress.org/">WordPress.org</a>. <a href="https://wordpress.org/plugins/simple-history">https://wordpress.org/plugins/simple-history</a></li></ul><h4>Localisation &amp; delivery</h4><ul><li>MDN contributors. (2025, July 11). <em>CDN</em>. <a href="https://www.linkedin.com/company/mozilla-corporation/">Mozilla</a> Developer Network (MDN). <a href="https://developer.mozilla.org/en-US/docs/Glossary/CDN">https://developer.mozilla.org/en-US/docs/Glossary/CDN</a></li></ul><h4>Privacy-preserving analytics &amp; bot protection</h4><ul><li><a href="https://www.linkedin.com/company/matomo/">Matomo</a>. (2025, August 27). <em>Matomo Analytics — Ethical Stats. Powerful Insights.</em> <a href="http://wordpress.org/">WordPress.org</a>. <a href="https://wordpress.org/plugins/matomo/">https://wordpress.org/plugins/matomo/</a></li><li><a href="https://www.linkedin.com/company/cloudflare/">Cloudflare</a>, Inc. (2025, August 20). <em>Cloudflare turnstile</em>. Cloudflare Docs. <a href="https://developers.cloudflare.com/turnstile/">https://developers.cloudflare.com/turnstile/</a></li></ul><p><strong>AI attribution statement:</strong> <a href="https://aiattribution.github.io/statements/AIA-Ph-CeNc-Hin-R-?model=GPT%252D5%252DThinking-v1.0">AIA Primarily human, Content edits, New content, Human-initiated, Reviewed, GPT-5-Thinking v1.0</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f83a45baa6ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>