From 152fe7941ec0f12455ab98d1b6e546d365117be6 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Thu, 24 Nov 2022 11:01:14 +0000
Subject: [PATCH 01/71] Add base en locales

---
 locales/en/LC_MESSAGES/messages.po | 2716 ++++++++++++++++++++++++++++
 1 file changed, 2716 insertions(+)
 create mode 100644 locales/en/LC_MESSAGES/messages.po

diff --git a/locales/en/LC_MESSAGES/messages.po b/locales/en/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..ac27704a
--- /dev/null
+++ b/locales/en/LC_MESSAGES/messages.po
@@ -0,0 +1,2716 @@
+#
+msgid ""
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 1 (header)
+msgid "order: 2"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 2 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 4 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST include the "
+"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
+"is based on."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include all source code that the policy is based on, "
+"unless used for fraud detection."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 6 (header)
+msgid "Why this is important"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 7 (paragraph)
+msgid ""
+"Access to both the source code and the policy documents is necessary for "
+"understanding and reuse of, as well as collaboration in, a codebase. "
+"Understanding the context and the policies in that context is fundamental to"
+" understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them. To be able to evaluate whether to adopt a codebase in a "
+"new context, an organization will need to understand what process changes it"
+" must choose to make or how to contribute additional configurability to the "
+"existing solution in order to adapt it to the new context."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 8 (header)
+msgid "What this does not do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid "Guarantee that a codebase will reflect the bundled policy."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid ""
+"Make sure packages comply with the local technical infrastructure or legal "
+"framework of a given public organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 10 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 12 (header)
+msgid "Policy makers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Collaborate with developers and designers to ensure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable such as"
+" [Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
+" [Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Track policy with [the same version control](version-control-and-history.md)"
+" and documentation used to track source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed and whether it still matches the [intentions of the "
+"policy](document-objectives.md)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 14 (header)
+msgid "Management: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 16 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Work together with policy makers to ensure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 18 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[Free online tools for building BPMN, CMMN and DMN diagrams at "
+"bmpn.io](https://bpmn.io/) by Camunda."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./code-in-the-open.md:block 1 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./code-in-the-open.md:block 2 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source [code](../glossary.md#code) for any "
+"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT upload sensitive information regarding users, their "
+"organization or third parties to the "
+"[repository](../glossary.md#repository)."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./code-in-the-open.md:block 7 (paragraph)
+msgid "Coding in the open:"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "improves transparency"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "increases code quality"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "facilitates the auditing processes"
+msgstr ""
+
+#: ./code-in-the-open.md:block 9 (paragraph)
+msgid ""
+"These aspects together create more opportunities for citizens to understand "
+"how software and policy impact their interactions with a public "
+"organization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid "Make source code or policy reusable."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid ""
+"Make the [codebase](../glossary.md#codebase) and the code within it "
+"understandable to as many people as possible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase files and commit history do not include sensitive "
+"information."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"Clearly split data and code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 1 (header)
+msgid "order: 12"
+msgstr ""
+
+#: ./continuous-integration.md:block 2 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"All functionality in the source [code](../glossary.md#code) MUST have "
+"automated tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "The codebase MUST have active contributors."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "Using [continuous integration](../glossary.md#continuous-integration):"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "allows you to quickly identify problems with the codebase,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"enables risk taking and focusing on problem solving while minimizing stress "
+"for the contributors,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"lowers barriers for new contributors by reducing the amount of understanding"
+" necessary to suggest changes,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "leads to more maintainable code,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "speeds up the development cycle."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Smaller, more regular contributions are typically easier to evaluate and "
+"lower risk compared to large infrequent changes."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Codebases in active development more reliably provide opportunities for "
+"collaboration and feedback."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid ""
+"Create a fault tolerant infrastructure that will work and scale perfectly."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Create meaningful tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Test for real life situations."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Guarantee the code will deliver exactly the same policy result."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that code coverage tools check that coverage is at 100% of the code."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Check if code coverage data is published."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Involve management as well as developers and designers as early in the "
+"process as possible and keep them engaged throughout development of your "
+"policy."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure the code reflects any changes to the policy (see [Maintain version"
+" control](version-control-and-history.md))."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Plan the work to deliver small parts very often instead of large parts less "
+"frequently."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management structure the work plan such that it can be delivered as "
+"small increments."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Structure code written to handle conditions which are difficult to create in"
+" a test environment in such a way that the conditions can be simulated "
+"during testing. Forms of resource exhaustion such as running out of storage "
+"space and memory allocation failure are typical examples of difficult to "
+"create conditions."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
+"Humble."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 1 (header)
+msgid "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 2 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is ready to use MUST only depend on other codebases that "
+"are also ready to use."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is not yet ready to use MUST have one of the labels: "
+"prototype, alpha, beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./document-maturity.md:block 7 (paragraph)
+msgid ""
+"Clearly signalling a codebase's maturity helps others decide whether to "
+"reuse, invest in or contribute to it."
+msgstr ""
+
+#: ./document-maturity.md:block 9 (unordered list)
+msgid "Guarantee that others will use the [code](../glossary.md#code)."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Confirm that it is clear where to get the newest version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase doesn't depend on any codebases marked with a less"
+" mature status."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
+"beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any code "
+"developed needs to be tested and improved before it can be put into service."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that services only rely on codebases of equal or greater maturity "
+"than the service. For example, don't use a beta codebase in a production "
+"service or a prototype codebase in a beta service."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"If the codebase is not ready for general use, work with the developers to "
+"ensure the codebase is properly labeled:"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"prototype: to test the look and feel, and to internally prove the concept of"
+" the technical possibilities,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid "alpha: to do guided tests with a limited set of users,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"beta: to open up testing to a larger section of the [general "
+"public](../glossary.md#general-public), for example to test if the codebase "
+"works at scale,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"pre-release version: code that is ready to be released but hasn't received "
+"formal approval yet."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Add a prominent header to every interface that indicates the maturity level "
+"of the code."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid "Version all releases."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Especially in 'rolling release' scenarios, the version may be automatically "
+"derived from the [version control](../glossary.md#version-control) system "
+"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
+"describe))."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[What are the Discovery, Alpha, Beta and Live stages in developing a "
+"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
+"the UK Government Digital Service."
+msgstr ""
+
+#: ./document-objectives.md:block 1 (header)
+msgid "order: 8"
+msgstr ""
+
+#: ./document-objectives.md:block 2 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
+"objectives, like a mission and goal statement, that is understandable by "
+"developers and designers so that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./document-objectives.md:block 7 (paragraph)
+msgid "Documenting codebase objectives:"
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"provides an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid "helps scope your own development."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"clearly communicates to other stakeholders and contributors the purpose of "
+"the codebase and the modules of which it is composed."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee that the codebase achieves the stated objective(s)."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee contributions to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid ""
+"Prevent other codebases from attempting to achieve the same objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development like value and ethics based policies, for example accessibility "
+"or equal opportunity."
+msgstr ""
+
+#: ./document-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 18 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 20 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./documenting.md:block 1 (header)
+msgid "order: 9"
+msgstr ""
+
+#: ./documenting.md:block 2 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"All of the functionality of the [codebase](../glossary.md#codebase), "
+"[policy](../glossary.md#policy) as well as source, MUST be described in "
+"language clearly understandable for those that understand the purpose of the"
+" [code](../glossary.md#code)."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the source code."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid "Testing the code by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "Users can start using and contributing more quickly."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid ""
+"You help people discover the codebase, especially people asking 'is there "
+"already code that does something like this'."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "This provides transparency into your organization and processes."
+msgstr ""
+
+#: ./documenting.md:block 9 (unordered list)
+msgid ""
+"Contribute directly to more reusable, portable code (see [Create reusable "
+"and portable code](./reusable-and-portable-codebases.md))."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated from code, and links and images are "
+"tested."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid "Try to use the codebase."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 19 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./findability.md:block 1 (header)
+msgid "order: 14"
+msgstr ""
+
+#: ./findability.md:block 2 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be findable using a search "
+"engine by describing the problem it solves in natural language."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "The codebase MUST be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"Proactiveness is needed; just publishing a codebase and hoping it's found "
+"doesn't work."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid "A metadata description file increases discoverability."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"The more findable a codebase is, the more potential new collaborators will "
+"find it."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"By having well-written metadata containing a unique and persistent "
+"identifer, such as a Wikidata item or FSF software directory listing, and "
+"thus being part of the semantic web, it will be easier for other people to "
+"refer, cite, disambiguate and discover the codebase through third party "
+"tools."
+msgstr ""
+
+#: ./findability.md:block 9 (unordered list)
+msgid "Ensure new collaborators or replicators."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a plain English problem "
+"description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a technical problem description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by the codebase name."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevent conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid "Ensure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Search engine optimization."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Softare Foundation."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./index.md:block 1 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./index.md:block 3 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./index.md:block 4 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 5 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 1 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 2 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
+"that accepts suggestions from anyone."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include instructions for how to privately report security "
+"issues for responsible disclosure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD include instructions for how to report potentially "
+"security sensitive issues on a closed channel."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid ""
+"Enables users to fix problems and add features to the shared codebase "
+"leading to better, more reliable and feature rich software."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Allows collaborative uptake of shared digital infrastructure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Helps users decide to use one codebase over another."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 9 (unordered list)
+msgid "Guarantee others will reuse the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 13 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid ""
+"Keep your management informed of the time and resources you require to "
+"support other contributors."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./open-licenses.md:block 1 (header)
+msgid "order: 13"
+msgstr ""
+
+#: ./open-licenses.md:block 2 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) and documentation MUST be licensed such that"
+" it may be freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid "All code MUST be published with a license file."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Having multiple licenses for different types of code and documentation is "
+"OPTIONAL."
+msgstr ""
+
+#: ./open-licenses.md:block 7 (unordered list)
+msgid ""
+"Makes it possible for anyone to see the code and know that they can and how "
+"they can reuse it."
+msgstr ""
+
+#: ./open-licenses.md:block 9 (unordered list)
+msgid "Prevent use of the code by any specific actors."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires code to be [open "
+"source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their code by publishing it "
+"under an open source license."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./open-standards.md:block 1 (header)
+msgid "order: 11"
+msgstr ""
+
+#: ./open-standards.md:block 2 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"For features of the [codebase](../glossary.md#codebase) that facilitate the "
+"exchange of data the codebase MUST use an [open "
+"standard](../glossary.md#open-standard) that meets the [Open Source "
+"Initiative Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Standards that are machine testable SHOULD be preferred over those that are "
+"not."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Creates interoperability between systems."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Reduces possible vendor lock-in."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid ""
+"Guarantees access to the knowledge required to reuse and contribute to the "
+"codebase."
+msgstr ""
+
+#: ./open-standards.md:block 9 (unordered list)
+msgid "Make it understandable how to use the software."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./open-standards.md:block 15 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in "
+"[code](../glossary.md#code) reviews."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./open-standards.md:block 19 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./open-to-contributions.md:block 1 (header)
+msgid "order: 4"
+msgstr ""
+
+#: ./open-to-contributions.md:block 2 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
+"suggestions for changes to the codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Helps newcomers understand and trust the codebase community's leadership."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Prevents the community that works on a codebase splitting because there is "
+"no way to influence its goals and progress, resulting in diverging "
+"communities."
+msgstr ""
+
+#: ./open-to-contributions.md:block 9 (unordered list)
+msgid "Guarantee others will join the community."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./require-review.md:block 1 (header)
+msgid "order: 7"
+msgstr ""
+
+#: ./require-review.md:block 2 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
+"documentation."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD conform to the standards, architecture and decisions "
+"set out in the codebase in order to pass review."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
+"tests of the codebase."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Increases codebase quality."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Reduces security risks as well as operational risks."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Creates a culture of making every contribution great."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Catches the most obvious mistakes that could happen."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Gives contributors the security that their contributions are only accepted "
+"if they really add value."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Assures contributors of a guaranteed time for feedback or collaborative "
+"improvement."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Prompt reviews increase both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Guarantee the right solution to a problem."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Mean that reviewers are liable."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Absolve a contributor from writing documentation and tests."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Provide you with the right reviewers."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check if reviews cover conformance to standards, architecture and codebase "
+"guidelines."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check with reviewers if they run the code and tests during review."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just code, is reviewed."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make delivering great code a shared objective."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Try to respond to others' requests for code review promptly, initially "
+"providing feedback about the concept of the change."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 1 (header)
+msgid "order: 3"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 2 (header)
+msgid "Create reusable and portable code"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
+"[different contexts](../glossary.md#different-contexts)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed [code](../glossary.md#code) or services for execution "
+"and understanding."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Configuration SHOULD be used to make code adapt to context specific needs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Enables other policy makers, developers and designers to reuse what you've "
+"developed, to test it, to improve it and contribute those improvements back "
+"leading to better quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes the code easier for new people to understand (as it's more general)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes it easier to control the mission, vision and scope of the codebase "
+"because the codebase is thoughtfully and purposefully designed for "
+"reusability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Codebases used by multiple parties are more likely to benefit from a self-"
+"sustaining community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Any contributor is able to test and contribute without relying on the "
+"situation-specific infrastructure of any other contributor or deployment."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Composing a codebase from well documented modules improves reusability and "
+"maintainability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"A module is easier to reuse in another context if its purpose is clearly "
+"documented."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Get others to reuse the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Build a community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid ""
+"Shift responsibility for documentation, support, bug-fixing, etc. to another"
+" party."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Guarantee that modules are generic enough to be reused in any context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"reuse the codebase and what that would entail."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed code or services."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
+msgid ""
+"Ensure that the codebase documentation describes the build-time and runtime "
+"dependencies. If your context requires deploying to proprietary platforms or"
+" using proprietary components, ensure that collaborators can develop, use, "
+"test, and deploy without them."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
+"OpenAPI Initiative defines a standard, programming language-agnostic "
+"interface description for human and machine-readable HTTP APIs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Internationalization techniques: Authoring HTML & "
+"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
+"World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
+"Operating System."
+msgstr ""
+
+#: ./style.md:block 1 (header)
+msgid "order: 15"
+msgstr ""
+
+#: ./style.md:block 2 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST adhere to either a coding or writing style guide, either "
+"the [codebase](../glossary.md#codebase) community's own or an existing one "
+"that is advertised in or part of the codebase."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include inline comments and documentation for non-"
+"trivial sections."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Including sections on [understandable English](understandable-english-"
+"first.md) in the style guide is OPTIONAL."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Enables contributors in different environments to work together on a unified"
+" product."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Unifying vocabularies reduces friction in communication between "
+"contributors."
+msgstr ""
+
+#: ./style.md:block 9 (unordered list)
+msgid "Help contributors write well or effectively explain what they do."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./style.md:block 13 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./style.md:block 15 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./style.md:block 17 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [code](../glossary.md#code) contributions in order for them to"
+" be merged by the maintainers, including source, tests and documentation. "
+"Continually improve upon and expand this documentation with the aim of "
+"evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./style.md:block 18 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
+"Hugo Martins."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./understandable-english-first.md:block 1 (header)
+msgid "order: 10"
+msgstr ""
+
+#: ./understandable-english-first.md:block 2 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [codebase](../glossary.md#codebase) documentation MUST be in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) MUST be in English, except where "
+"[policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Makes the codebase and what it does understandable for a wider variety of "
+"stakeholders in multiple contexts."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid "Helps with the discoverability of the codebase."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Can help you meet the [European Union accessibility "
+"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
+" which requires most public sector information to be accessible."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make explanations of the codebase's functionality understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make your organization's jargon understandable without an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 13 (unordered list)
+msgid ""
+"Frequently test with other management, developers and designers in the "
+"process if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Frequently test with policy makers and management if they understand what "
+"you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
+"readable and understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
+" allows 1000 most common English words."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./version-control-and-history.md:block 1 (header)
+msgid "order: 6"
+msgstr ""
+
+#: ./version-control-and-history.md:block 2 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The community MUST have a way to maintain [version "
+"control](../glossary.md#version-control) for the "
+"[code](../glossary.md#code)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"All files in the [codebase](../glossary.md#codebase) MUST be version "
+"controlled."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "Contributors SHOULD group relevant changes in commits."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Contributors SHOULD prefer file formats where the changes within the files "
+"can be easily viewed and understood in the version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./version-control-and-history.md:block 7 (paragraph)
+msgid ""
+"Version control means keeping track of changes to the code over time. This "
+"allows you to create structured documentation of the history of the "
+"codebase. This is essential for collaboration at scale."
+msgstr ""
+
+#: ./version-control-and-history.md:block 8 (paragraph)
+msgid "Distributed version control enables you to:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "have a full copy of the code and its history"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "revert to an earlier version of the codebase whenever you want to"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"record your changes and the reasons why you made them, to help future "
+"developers understand the process"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "compare two different versions"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "work on changes in parallel as a team before merging them together"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"continue to work when the network is unavailable, merging changes back with "
+"everyone else’s at a later date"
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Substitute for [advertising maturity](document-maturity.md)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee the code executes correctly."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee collaborators."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./version-control-and-history.md:block 16 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 18 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
+" use it or refresh your skills."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""

From c1fa1a47dfecd9d39ca20652e82b5bff16ca7302 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 24 Nov 2022 19:32:15 +0800
Subject: [PATCH 02/71] Added translation using Weblate (Chinese (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..4f8f6e6d
--- /dev/null
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,2 @@
+msgid ""
+msgstr "X-Generator: Weblate\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit"
\ No newline at end of file

From 98f633dc4dba670d4243220ba282e20a19d29a71 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:35:56 +0800
Subject: [PATCH 03/71] Deleted translation using Weblate (Chinese
 (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
deleted file mode 100644
index 4f8f6e6d..00000000
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ /dev/null
@@ -1,2 +0,0 @@
-msgid ""
-msgstr "X-Generator: Weblate\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit"
\ No newline at end of file

From d89f1ebec30a0a811b9624791d717fc29c536e58 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:36:32 +0800
Subject: [PATCH 04/71] Added translation using Weblate (Chinese (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..4f8f6e6d
--- /dev/null
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,2 @@
+msgid ""
+msgstr "X-Generator: Weblate\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit"
\ No newline at end of file

From 276372666454e2163f647f0826e40581056992c6 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:36:51 +0800
Subject: [PATCH 05/71] Deleted translation using Weblate (Chinese
 (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
deleted file mode 100644
index 4f8f6e6d..00000000
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ /dev/null
@@ -1,2 +0,0 @@
-msgid ""
-msgstr "X-Generator: Weblate\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit"
\ No newline at end of file

From cc6cc05750b6c9ce81ec805f04e760526c0445af Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:37:55 +0800
Subject: [PATCH 06/71] Added translation using Weblate (Chinese (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2728 +++++++++++++++++++++++
 1 file changed, 2728 insertions(+)
 create mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..3a866911
--- /dev/null
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,2728 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-12-01 12:37+0800\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: zh_Hant\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Translate Toolkit 3.7.4\n"
+
+#
+
+#: ./bundle-policy-and-code.md:block 1 (header)
+msgid "order: 2"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 2 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 4 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST include the "
+"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
+"is based on."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include all source code that the policy is based on, "
+"unless used for fraud detection."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 6 (header)
+msgid "Why this is important"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 7 (paragraph)
+msgid ""
+"Access to both the source code and the policy documents is necessary for "
+"understanding and reuse of, as well as collaboration in, a codebase. "
+"Understanding the context and the policies in that context is fundamental to"
+" understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them. To be able to evaluate whether to adopt a codebase in a "
+"new context, an organization will need to understand what process changes it"
+" must choose to make or how to contribute additional configurability to the "
+"existing solution in order to adapt it to the new context."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 8 (header)
+msgid "What this does not do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid "Guarantee that a codebase will reflect the bundled policy."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid ""
+"Make sure packages comply with the local technical infrastructure or legal "
+"framework of a given public organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 10 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 12 (header)
+msgid "Policy makers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Collaborate with developers and designers to ensure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable such as"
+" [Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
+" [Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Track policy with [the same version control](version-control-and-history.md)"
+" and documentation used to track source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed and whether it still matches the [intentions of the "
+"policy](document-objectives.md)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 14 (header)
+msgid "Management: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 16 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Work together with policy makers to ensure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 18 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[Free online tools for building BPMN, CMMN and DMN diagrams at "
+"bmpn.io](https://bpmn.io/) by Camunda."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./code-in-the-open.md:block 1 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./code-in-the-open.md:block 2 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source [code](../glossary.md#code) for any "
+"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT upload sensitive information regarding users, their "
+"organization or third parties to the "
+"[repository](../glossary.md#repository)."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./code-in-the-open.md:block 7 (paragraph)
+msgid "Coding in the open:"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "improves transparency"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "increases code quality"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "facilitates the auditing processes"
+msgstr ""
+
+#: ./code-in-the-open.md:block 9 (paragraph)
+msgid ""
+"These aspects together create more opportunities for citizens to understand "
+"how software and policy impact their interactions with a public "
+"organization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid "Make source code or policy reusable."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid ""
+"Make the [codebase](../glossary.md#codebase) and the code within it "
+"understandable to as many people as possible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase files and commit history do not include sensitive "
+"information."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"Clearly split data and code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 1 (header)
+msgid "order: 12"
+msgstr ""
+
+#: ./continuous-integration.md:block 2 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"All functionality in the source [code](../glossary.md#code) MUST have "
+"automated tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "The codebase MUST have active contributors."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "Using [continuous integration](../glossary.md#continuous-integration):"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "allows you to quickly identify problems with the codebase,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"enables risk taking and focusing on problem solving while minimizing stress "
+"for the contributors,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"lowers barriers for new contributors by reducing the amount of understanding"
+" necessary to suggest changes,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "leads to more maintainable code,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "speeds up the development cycle."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Smaller, more regular contributions are typically easier to evaluate and "
+"lower risk compared to large infrequent changes."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Codebases in active development more reliably provide opportunities for "
+"collaboration and feedback."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid ""
+"Create a fault tolerant infrastructure that will work and scale perfectly."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Create meaningful tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Test for real life situations."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Guarantee the code will deliver exactly the same policy result."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that code coverage tools check that coverage is at 100% of the code."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Check if code coverage data is published."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Involve management as well as developers and designers as early in the "
+"process as possible and keep them engaged throughout development of your "
+"policy."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure the code reflects any changes to the policy (see [Maintain version"
+" control](version-control-and-history.md))."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Plan the work to deliver small parts very often instead of large parts less "
+"frequently."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management structure the work plan such that it can be delivered as "
+"small increments."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Structure code written to handle conditions which are difficult to create in"
+" a test environment in such a way that the conditions can be simulated "
+"during testing. Forms of resource exhaustion such as running out of storage "
+"space and memory allocation failure are typical examples of difficult to "
+"create conditions."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
+"Humble."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 1 (header)
+msgid "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 2 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is ready to use MUST only depend on other codebases that "
+"are also ready to use."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is not yet ready to use MUST have one of the labels: "
+"prototype, alpha, beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./document-maturity.md:block 7 (paragraph)
+msgid ""
+"Clearly signalling a codebase's maturity helps others decide whether to "
+"reuse, invest in or contribute to it."
+msgstr ""
+
+#: ./document-maturity.md:block 9 (unordered list)
+msgid "Guarantee that others will use the [code](../glossary.md#code)."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Confirm that it is clear where to get the newest version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase doesn't depend on any codebases marked with a less"
+" mature status."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
+"beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any code "
+"developed needs to be tested and improved before it can be put into service."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that services only rely on codebases of equal or greater maturity "
+"than the service. For example, don't use a beta codebase in a production "
+"service or a prototype codebase in a beta service."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"If the codebase is not ready for general use, work with the developers to "
+"ensure the codebase is properly labeled:"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"prototype: to test the look and feel, and to internally prove the concept of"
+" the technical possibilities,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid "alpha: to do guided tests with a limited set of users,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"beta: to open up testing to a larger section of the [general "
+"public](../glossary.md#general-public), for example to test if the codebase "
+"works at scale,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"pre-release version: code that is ready to be released but hasn't received "
+"formal approval yet."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Add a prominent header to every interface that indicates the maturity level "
+"of the code."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid "Version all releases."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Especially in 'rolling release' scenarios, the version may be automatically "
+"derived from the [version control](../glossary.md#version-control) system "
+"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
+"describe))."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[What are the Discovery, Alpha, Beta and Live stages in developing a "
+"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
+"the UK Government Digital Service."
+msgstr ""
+
+#: ./document-objectives.md:block 1 (header)
+msgid "order: 8"
+msgstr ""
+
+#: ./document-objectives.md:block 2 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
+"objectives, like a mission and goal statement, that is understandable by "
+"developers and designers so that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./document-objectives.md:block 7 (paragraph)
+msgid "Documenting codebase objectives:"
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"provides an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid "helps scope your own development."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"clearly communicates to other stakeholders and contributors the purpose of "
+"the codebase and the modules of which it is composed."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee that the codebase achieves the stated objective(s)."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee contributions to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid ""
+"Prevent other codebases from attempting to achieve the same objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development like value and ethics based policies, for example accessibility "
+"or equal opportunity."
+msgstr ""
+
+#: ./document-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 18 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 20 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./documenting.md:block 1 (header)
+msgid "order: 9"
+msgstr ""
+
+#: ./documenting.md:block 2 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"All of the functionality of the [codebase](../glossary.md#codebase), "
+"[policy](../glossary.md#policy) as well as source, MUST be described in "
+"language clearly understandable for those that understand the purpose of the"
+" [code](../glossary.md#code)."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the source code."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid "Testing the code by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "Users can start using and contributing more quickly."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid ""
+"You help people discover the codebase, especially people asking 'is there "
+"already code that does something like this'."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "This provides transparency into your organization and processes."
+msgstr ""
+
+#: ./documenting.md:block 9 (unordered list)
+msgid ""
+"Contribute directly to more reusable, portable code (see [Create reusable "
+"and portable code](./reusable-and-portable-codebases.md))."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated from code, and links and images are "
+"tested."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid "Try to use the codebase."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 19 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./findability.md:block 1 (header)
+msgid "order: 14"
+msgstr ""
+
+#: ./findability.md:block 2 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be findable using a search "
+"engine by describing the problem it solves in natural language."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "The codebase MUST be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"Proactiveness is needed; just publishing a codebase and hoping it's found "
+"doesn't work."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid "A metadata description file increases discoverability."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"The more findable a codebase is, the more potential new collaborators will "
+"find it."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"By having well-written metadata containing a unique and persistent "
+"identifer, such as a Wikidata item or FSF software directory listing, and "
+"thus being part of the semantic web, it will be easier for other people to "
+"refer, cite, disambiguate and discover the codebase through third party "
+"tools."
+msgstr ""
+
+#: ./findability.md:block 9 (unordered list)
+msgid "Ensure new collaborators or replicators."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a plain English problem "
+"description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a technical problem description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by the codebase name."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevent conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid "Ensure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Search engine optimization."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Softare Foundation."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./index.md:block 1 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./index.md:block 3 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./index.md:block 4 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 5 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 1 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 2 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
+"that accepts suggestions from anyone."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include instructions for how to privately report security "
+"issues for responsible disclosure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD include instructions for how to report potentially "
+"security sensitive issues on a closed channel."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid ""
+"Enables users to fix problems and add features to the shared codebase "
+"leading to better, more reliable and feature rich software."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Allows collaborative uptake of shared digital infrastructure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Helps users decide to use one codebase over another."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 9 (unordered list)
+msgid "Guarantee others will reuse the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 13 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid ""
+"Keep your management informed of the time and resources you require to "
+"support other contributors."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./open-licenses.md:block 1 (header)
+msgid "order: 13"
+msgstr ""
+
+#: ./open-licenses.md:block 2 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) and documentation MUST be licensed such that"
+" it may be freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid "All code MUST be published with a license file."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Having multiple licenses for different types of code and documentation is "
+"OPTIONAL."
+msgstr ""
+
+#: ./open-licenses.md:block 7 (unordered list)
+msgid ""
+"Makes it possible for anyone to see the code and know that they can and how "
+"they can reuse it."
+msgstr ""
+
+#: ./open-licenses.md:block 9 (unordered list)
+msgid "Prevent use of the code by any specific actors."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires code to be [open "
+"source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their code by publishing it "
+"under an open source license."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./open-standards.md:block 1 (header)
+msgid "order: 11"
+msgstr ""
+
+#: ./open-standards.md:block 2 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"For features of the [codebase](../glossary.md#codebase) that facilitate the "
+"exchange of data the codebase MUST use an [open "
+"standard](../glossary.md#open-standard) that meets the [Open Source "
+"Initiative Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Standards that are machine testable SHOULD be preferred over those that are "
+"not."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Creates interoperability between systems."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Reduces possible vendor lock-in."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid ""
+"Guarantees access to the knowledge required to reuse and contribute to the "
+"codebase."
+msgstr ""
+
+#: ./open-standards.md:block 9 (unordered list)
+msgid "Make it understandable how to use the software."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./open-standards.md:block 15 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in "
+"[code](../glossary.md#code) reviews."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./open-standards.md:block 19 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./open-to-contributions.md:block 1 (header)
+msgid "order: 4"
+msgstr ""
+
+#: ./open-to-contributions.md:block 2 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
+"suggestions for changes to the codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Helps newcomers understand and trust the codebase community's leadership."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Prevents the community that works on a codebase splitting because there is "
+"no way to influence its goals and progress, resulting in diverging "
+"communities."
+msgstr ""
+
+#: ./open-to-contributions.md:block 9 (unordered list)
+msgid "Guarantee others will join the community."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./require-review.md:block 1 (header)
+msgid "order: 7"
+msgstr ""
+
+#: ./require-review.md:block 2 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
+"documentation."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD conform to the standards, architecture and decisions "
+"set out in the codebase in order to pass review."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
+"tests of the codebase."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Increases codebase quality."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Reduces security risks as well as operational risks."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Creates a culture of making every contribution great."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Catches the most obvious mistakes that could happen."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Gives contributors the security that their contributions are only accepted "
+"if they really add value."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Assures contributors of a guaranteed time for feedback or collaborative "
+"improvement."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Prompt reviews increase both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Guarantee the right solution to a problem."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Mean that reviewers are liable."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Absolve a contributor from writing documentation and tests."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Provide you with the right reviewers."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check if reviews cover conformance to standards, architecture and codebase "
+"guidelines."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check with reviewers if they run the code and tests during review."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just code, is reviewed."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make delivering great code a shared objective."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Try to respond to others' requests for code review promptly, initially "
+"providing feedback about the concept of the change."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 1 (header)
+msgid "order: 3"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 2 (header)
+msgid "Create reusable and portable code"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
+"[different contexts](../glossary.md#different-contexts)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed [code](../glossary.md#code) or services for execution "
+"and understanding."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Configuration SHOULD be used to make code adapt to context specific needs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Enables other policy makers, developers and designers to reuse what you've "
+"developed, to test it, to improve it and contribute those improvements back "
+"leading to better quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes the code easier for new people to understand (as it's more general)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes it easier to control the mission, vision and scope of the codebase "
+"because the codebase is thoughtfully and purposefully designed for "
+"reusability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Codebases used by multiple parties are more likely to benefit from a self-"
+"sustaining community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Any contributor is able to test and contribute without relying on the "
+"situation-specific infrastructure of any other contributor or deployment."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Composing a codebase from well documented modules improves reusability and "
+"maintainability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"A module is easier to reuse in another context if its purpose is clearly "
+"documented."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Get others to reuse the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Build a community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid ""
+"Shift responsibility for documentation, support, bug-fixing, etc. to another"
+" party."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Guarantee that modules are generic enough to be reused in any context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"reuse the codebase and what that would entail."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed code or services."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
+msgid ""
+"Ensure that the codebase documentation describes the build-time and runtime "
+"dependencies. If your context requires deploying to proprietary platforms or"
+" using proprietary components, ensure that collaborators can develop, use, "
+"test, and deploy without them."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
+"OpenAPI Initiative defines a standard, programming language-agnostic "
+"interface description for human and machine-readable HTTP APIs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Internationalization techniques: Authoring HTML & "
+"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
+"World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
+"Operating System."
+msgstr ""
+
+#: ./style.md:block 1 (header)
+msgid "order: 15"
+msgstr ""
+
+#: ./style.md:block 2 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST adhere to either a coding or writing style guide, either "
+"the [codebase](../glossary.md#codebase) community's own or an existing one "
+"that is advertised in or part of the codebase."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include inline comments and documentation for non-"
+"trivial sections."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Including sections on [understandable English](understandable-english-"
+"first.md) in the style guide is OPTIONAL."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Enables contributors in different environments to work together on a unified"
+" product."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Unifying vocabularies reduces friction in communication between "
+"contributors."
+msgstr ""
+
+#: ./style.md:block 9 (unordered list)
+msgid "Help contributors write well or effectively explain what they do."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./style.md:block 13 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./style.md:block 15 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./style.md:block 17 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [code](../glossary.md#code) contributions in order for them to"
+" be merged by the maintainers, including source, tests and documentation. "
+"Continually improve upon and expand this documentation with the aim of "
+"evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./style.md:block 18 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
+"Hugo Martins."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./understandable-english-first.md:block 1 (header)
+msgid "order: 10"
+msgstr ""
+
+#: ./understandable-english-first.md:block 2 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [codebase](../glossary.md#codebase) documentation MUST be in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) MUST be in English, except where "
+"[policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Makes the codebase and what it does understandable for a wider variety of "
+"stakeholders in multiple contexts."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid "Helps with the discoverability of the codebase."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Can help you meet the [European Union accessibility "
+"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
+" which requires most public sector information to be accessible."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make explanations of the codebase's functionality understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make your organization's jargon understandable without an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 13 (unordered list)
+msgid ""
+"Frequently test with other management, developers and designers in the "
+"process if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Frequently test with policy makers and management if they understand what "
+"you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
+"readable and understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
+" allows 1000 most common English words."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./version-control-and-history.md:block 1 (header)
+msgid "order: 6"
+msgstr ""
+
+#: ./version-control-and-history.md:block 2 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The community MUST have a way to maintain [version "
+"control](../glossary.md#version-control) for the "
+"[code](../glossary.md#code)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"All files in the [codebase](../glossary.md#codebase) MUST be version "
+"controlled."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "Contributors SHOULD group relevant changes in commits."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Contributors SHOULD prefer file formats where the changes within the files "
+"can be easily viewed and understood in the version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./version-control-and-history.md:block 7 (paragraph)
+msgid ""
+"Version control means keeping track of changes to the code over time. This "
+"allows you to create structured documentation of the history of the "
+"codebase. This is essential for collaboration at scale."
+msgstr ""
+
+#: ./version-control-and-history.md:block 8 (paragraph)
+msgid "Distributed version control enables you to:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "have a full copy of the code and its history"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "revert to an earlier version of the codebase whenever you want to"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"record your changes and the reasons why you made them, to help future "
+"developers understand the process"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "compare two different versions"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "work on changes in parallel as a team before merging them together"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"continue to work when the network is unavailable, merging changes back with "
+"everyone else’s at a later date"
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Substitute for [advertising maturity](document-maturity.md)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee the code executes correctly."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee collaborators."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./version-control-and-history.md:block 16 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 18 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
+" use it or refresh your skills."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""

From 59bba8d34d4101c9f5a8717f7e8c11ca205d4f1a Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:38:20 +0800
Subject: [PATCH 07/71] Deleted translation using Weblate (Chinese
 (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2728 -----------------------
 1 file changed, 2728 deletions(-)
 delete mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
deleted file mode 100644
index 3a866911..00000000
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ /dev/null
@@ -1,2728 +0,0 @@
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-12-01 12:37+0800\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: zh_Hant\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Translate Toolkit 3.7.4\n"
-
-#
-
-#: ./bundle-policy-and-code.md:block 1 (header)
-msgid "order: 2"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 2 (header)
-msgid "Bundle policy and source code"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 4 (header)
-msgid "Requirements"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST include the "
-"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
-"is based on."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST include all source code that the policy is based on, "
-"unless used for fraud detection."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 5 (unordered list)
-msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 5 (unordered list)
-msgid ""
-"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
-" validate that the source code and the policy are executed coherently."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 6 (header)
-msgid "Why this is important"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 7 (paragraph)
-msgid ""
-"Access to both the source code and the policy documents is necessary for "
-"understanding and reuse of, as well as collaboration in, a codebase. "
-"Understanding the context and the policies in that context is fundamental to"
-" understanding what problems a codebase is trying to solve and how it sets "
-"out to solve them. To be able to evaluate whether to adopt a codebase in a "
-"new context, an organization will need to understand what process changes it"
-" must choose to make or how to contribute additional configurability to the "
-"existing solution in order to adapt it to the new context."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 8 (header)
-msgid "What this does not do"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 9 (unordered list)
-msgid "Guarantee that a codebase will reflect the bundled policy."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 9 (unordered list)
-msgid ""
-"Make sure packages comply with the local technical infrastructure or legal "
-"framework of a given public organization."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 10 (header)
-msgid "How to test"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 11 (unordered list)
-msgid ""
-"Confirm with a civil servant that all policy that the source code is based "
-"on is included."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 11 (unordered list)
-msgid ""
-"Confirm with a civil servant that all source code that the policy is based "
-"on is included."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 11 (unordered list)
-msgid "Check if policy can be interpreted by a machine."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 11 (unordered list)
-msgid ""
-"Check the continuous integration tests for coherent execution of source code"
-" and policy pass."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 12 (header)
-msgid "Policy makers: what you need to do"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid ""
-"Collaborate with developers and designers to ensure there is no mismatch "
-"between policy code and source code."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid ""
-"Provide the relevant policy texts for inclusion in the "
-"[repository](../glossary.md#repository); if the text is not available in "
-"English, also provide an English summary. Be sure to include standards that "
-"your organization has chosen to adhere to and any organizational processes "
-"which impact the development or the deployment context of the codebase for "
-"your organization."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid "Provide references and links to texts which support the policies."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid ""
-"Document policy in formats that are unambiguous and machine-readable such as"
-" [Business Process Model and "
-"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
-" [Decision Model and "
-"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
-"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid ""
-"Track policy with [the same version control](version-control-and-history.md)"
-" and documentation used to track source code."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 13 (unordered list)
-msgid ""
-"Check in regularly to understand how the non-policy code in the codebase has"
-" changed and whether it still matches the [intentions of the "
-"policy](document-objectives.md)."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 14 (header)
-msgid "Management: what you need to do"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 15 (unordered list)
-msgid ""
-"Keep policy makers, developers and designers involved and connected "
-"throughout the whole development process."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 15 (unordered list)
-msgid ""
-"Make sure policy makers, developers and designers are working to the same "
-"objectives."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 16 (header)
-msgid "Developers and designers: what you need to do"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 17 (unordered list)
-msgid ""
-"Become familiar with and be able to use the process modelling notation that "
-"the policy makers in your organization use."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 17 (unordered list)
-msgid ""
-"Work together with policy makers to ensure there is no mismatch between "
-"policy code and source code."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 17 (unordered list)
-msgid "Give feedback on how to make policy documentation more clear."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 18 (header)
-msgid "Further reading"
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 19 (unordered list)
-msgid ""
-"[Free online tools for building BPMN, CMMN and DMN diagrams at "
-"bmpn.io](https://bpmn.io/) by Camunda."
-msgstr ""
-
-#: ./bundle-policy-and-code.md:block 19 (unordered list)
-msgid ""
-"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
-" Trisotech."
-msgstr ""
-
-#: ./code-in-the-open.md:block 1 (header)
-msgid "order: 1"
-msgstr ""
-
-#: ./code-in-the-open.md:block 2 (header)
-msgid "Code in the open"
-msgstr ""
-
-#: ./code-in-the-open.md:block 5 (unordered list)
-msgid ""
-"All source [code](../glossary.md#code) for any "
-"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
-"MUST be published and publicly accessible."
-msgstr ""
-
-#: ./code-in-the-open.md:block 5 (unordered list)
-msgid ""
-"All source code for any software in use (unless used for fraud detection) "
-"MUST be published and publicly accessible."
-msgstr ""
-
-#: ./code-in-the-open.md:block 5 (unordered list)
-msgid ""
-"Contributors MUST NOT upload sensitive information regarding users, their "
-"organization or third parties to the "
-"[repository](../glossary.md#repository)."
-msgstr ""
-
-#: ./code-in-the-open.md:block 5 (unordered list)
-msgid ""
-"Any source code not currently in use (such as new versions, proposals or "
-"older versions) SHOULD be published."
-msgstr ""
-
-#: ./code-in-the-open.md:block 5 (unordered list)
-msgid ""
-"Documenting which source code or policy underpins any specific interaction "
-"the [general public](../glossary.md#general-public) may have with an "
-"organization is OPTIONAL."
-msgstr ""
-
-#: ./code-in-the-open.md:block 7 (paragraph)
-msgid "Coding in the open:"
-msgstr ""
-
-#: ./code-in-the-open.md:block 8 (unordered list)
-msgid "improves transparency"
-msgstr ""
-
-#: ./code-in-the-open.md:block 8 (unordered list)
-msgid "increases code quality"
-msgstr ""
-
-#: ./code-in-the-open.md:block 8 (unordered list)
-msgid "facilitates the auditing processes"
-msgstr ""
-
-#: ./code-in-the-open.md:block 9 (paragraph)
-msgid ""
-"These aspects together create more opportunities for citizens to understand "
-"how software and policy impact their interactions with a public "
-"organization."
-msgstr ""
-
-#: ./code-in-the-open.md:block 11 (unordered list)
-msgid "Make source code or policy reusable."
-msgstr ""
-
-#: ./code-in-the-open.md:block 11 (unordered list)
-msgid ""
-"Make the [codebase](../glossary.md#codebase) and the code within it "
-"understandable to as many people as possible."
-msgstr ""
-
-#: ./code-in-the-open.md:block 13 (unordered list)
-msgid ""
-"Confirm that the source for each version currently in use is published on "
-"the internet where it can be seen from outside the original contributing "
-"organization and without the need for any form of authentication or "
-"authorization."
-msgstr ""
-
-#: ./code-in-the-open.md:block 13 (unordered list)
-msgid ""
-"Confirm that the codebase files and commit history do not include sensitive "
-"information."
-msgstr ""
-
-#: ./code-in-the-open.md:block 13 (unordered list)
-msgid "Check for the publication of source code not currently in use."
-msgstr ""
-
-#: ./code-in-the-open.md:block 15 (unordered list)
-msgid "Develop policies in the open."
-msgstr ""
-
-#: ./code-in-the-open.md:block 15 (unordered list)
-msgid "Prioritize open and transparent policies."
-msgstr ""
-
-#: ./code-in-the-open.md:block 17 (unordered list)
-msgid "Develop a culture that embraces openness, learning and feedback."
-msgstr ""
-
-#: ./code-in-the-open.md:block 17 (unordered list)
-msgid ""
-"Collaborate with external vendors and freelancers by working in the open."
-msgstr ""
-
-#: ./code-in-the-open.md:block 19 (unordered list)
-msgid ""
-"As a reviewer, for each commit, verify that content does not include "
-"sensitive information such as configurations, usernames or passwords, public"
-" keys or other real credentials used in production systems."
-msgstr ""
-
-#: ./code-in-the-open.md:block 19 (unordered list)
-msgid ""
-"Clearly split data and code, in order to meet the requirement about "
-"sensitive information above."
-msgstr ""
-
-#: ./code-in-the-open.md:block 21 (unordered list)
-msgid ""
-"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
-" by the UK Government Digital Service."
-msgstr ""
-
-#: ./code-in-the-open.md:block 21 (unordered list)
-msgid ""
-"[When code should be open or "
-"closed](https://www.gov.uk/government/publications/open-source-"
-"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
-"Service."
-msgstr ""
-
-#: ./code-in-the-open.md:block 21 (unordered list)
-msgid ""
-"[Security considerations when coding in the "
-"open](https://www.gov.uk/government/publications/open-source-"
-"guidance/security-considerations-when-coding-in-the-open) by the UK "
-"Government Digital Service."
-msgstr ""
-
-#: ./code-in-the-open.md:block 21 (unordered list)
-msgid ""
-"[Deploying software regularly](https://www.gov.uk/service-"
-"manual/technology/deploying-software-regularly) by the UK Government Digital"
-" Service."
-msgstr ""
-
-#: ./code-in-the-open.md:block 21 (unordered list)
-msgid ""
-"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
-"use-github/) by the UK Government Digital Service."
-msgstr ""
-
-#: ./continuous-integration.md:block 1 (header)
-msgid "order: 12"
-msgstr ""
-
-#: ./continuous-integration.md:block 2 (header)
-msgid "Use continuous integration"
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"All functionality in the source [code](../glossary.md#code) MUST have "
-"automated tests."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"Contributions MUST pass all automated tests before they are admitted into "
-"the [codebase](../glossary.md#codebase)."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST have guidelines explaining how to structure contributions."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid "The codebase MUST have active contributors."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"The codebase guidelines SHOULD state that each contribution should focus on "
-"a single issue."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"Testing [policy](../glossary.md#policy) and documentation for consistency "
-"with the source and vice versa is OPTIONAL."
-msgstr ""
-
-#: ./continuous-integration.md:block 5 (unordered list)
-msgid ""
-"Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid "Using [continuous integration](../glossary.md#continuous-integration):"
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid "allows you to quickly identify problems with the codebase,"
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid ""
-"enables risk taking and focusing on problem solving while minimizing stress "
-"for the contributors,"
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid ""
-"lowers barriers for new contributors by reducing the amount of understanding"
-" necessary to suggest changes,"
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid "leads to more maintainable code,"
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid "speeds up the development cycle."
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid ""
-"Smaller, more regular contributions are typically easier to evaluate and "
-"lower risk compared to large infrequent changes."
-msgstr ""
-
-#: ./continuous-integration.md:block 7 (unordered list)
-msgid ""
-"Codebases in active development more reliably provide opportunities for "
-"collaboration and feedback."
-msgstr ""
-
-#: ./continuous-integration.md:block 9 (unordered list)
-msgid ""
-"Create a fault tolerant infrastructure that will work and scale perfectly."
-msgstr ""
-
-#: ./continuous-integration.md:block 9 (unordered list)
-msgid "Create meaningful tests."
-msgstr ""
-
-#: ./continuous-integration.md:block 9 (unordered list)
-msgid "Test for real life situations."
-msgstr ""
-
-#: ./continuous-integration.md:block 9 (unordered list)
-msgid "Guarantee the code will deliver exactly the same policy result."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid "Confirm that there are tests present."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid ""
-"Confirm that code coverage tools check that coverage is at 100% of the code."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid ""
-"Confirm that contributions are only admitted into the codebase after all of "
-"the tests are passed."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid ""
-"Confirm that contribution guidelines explain how to structure contributions."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid ""
-"Confirm that there are contributions from within the last three months."
-msgstr ""
-
-#: ./continuous-integration.md:block 11 (unordered list)
-msgid "Check if code coverage data is published."
-msgstr ""
-
-#: ./continuous-integration.md:block 13 (unordered list)
-msgid ""
-"Involve management as well as developers and designers as early in the "
-"process as possible and keep them engaged throughout development of your "
-"policy."
-msgstr ""
-
-#: ./continuous-integration.md:block 13 (unordered list)
-msgid ""
-"Make sure there are also automated tests set up for policy documentation."
-msgstr ""
-
-#: ./continuous-integration.md:block 13 (unordered list)
-msgid "Fix policy documentation promptly if it fails a test."
-msgstr ""
-
-#: ./continuous-integration.md:block 13 (unordered list)
-msgid ""
-"Make sure the code reflects any changes to the policy (see [Maintain version"
-" control](version-control-and-history.md))."
-msgstr ""
-
-#: ./continuous-integration.md:block 15 (unordered list)
-msgid ""
-"Make sure to test with real end users as quickly and often as possible."
-msgstr ""
-
-#: ./continuous-integration.md:block 15 (unordered list)
-msgid ""
-"Plan the work to deliver small parts very often instead of large parts less "
-"frequently."
-msgstr ""
-
-#: ./continuous-integration.md:block 15 (unordered list)
-msgid ""
-"Procure consultancy services that deliver incrementally aligned with the "
-"plan."
-msgstr ""
-
-#: ./continuous-integration.md:block 15 (unordered list)
-msgid ""
-"After a large failure, encourage publication of incident reports and public "
-"discussion of what was learned."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid ""
-"Help management structure the work plan such that it can be delivered as "
-"small increments."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid ""
-"Help contributors limit the scope of their contributions and feature "
-"requests to be as small as reasonable."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid ""
-"Help management and policy makers test their contributions, for example by "
-"testing their contributions for broken links or style."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid ""
-"Structure code written to handle conditions which are difficult to create in"
-" a test environment in such a way that the conditions can be simulated "
-"during testing. Forms of resource exhaustion such as running out of storage "
-"space and memory allocation failure are typical examples of difficult to "
-"create conditions."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid ""
-"Tune the test code coverage tools to avoid false alarms resulting from "
-"inlining or other optimizations."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid "Deploy often."
-msgstr ""
-
-#: ./continuous-integration.md:block 17 (unordered list)
-msgid "Integrate your work at least once a day."
-msgstr ""
-
-#: ./continuous-integration.md:block 19 (unordered list)
-msgid ""
-"[What is continuous "
-"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
-" by Martin Fowler."
-msgstr ""
-
-#: ./continuous-integration.md:block 19 (unordered list)
-msgid ""
-"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
-"Humble."
-msgstr ""
-
-#: ./continuous-integration.md:block 19 (unordered list)
-msgid ""
-"[Use continuous delivery](https://gds-"
-"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
-"Government Digital Service."
-msgstr ""
-
-#: ./continuous-integration.md:block 19 (unordered list)
-msgid ""
-"[Quality assurance: testing your service "
-"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
-"testing-your-service-regularly) by the UK Government Digital Service."
-msgstr ""
-
-#: ./document-maturity.md:block 1 (header)
-msgid "order: 16 redirect_from: - criteria/advertise-maturity"
-msgstr ""
-
-#: ./document-maturity.md:block 2 (header)
-msgid "Document codebase maturity"
-msgstr ""
-
-#: ./document-maturity.md:block 5 (unordered list)
-msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
-msgstr ""
-
-#: ./document-maturity.md:block 5 (unordered list)
-msgid ""
-"The codebase that is ready to use MUST only depend on other codebases that "
-"are also ready to use."
-msgstr ""
-
-#: ./document-maturity.md:block 5 (unordered list)
-msgid ""
-"The codebase that is not yet ready to use MUST have one of the labels: "
-"prototype, alpha, beta or pre-release version."
-msgstr ""
-
-#: ./document-maturity.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD contain a log of changes from version to version, for "
-"example in the `CHANGELOG`."
-msgstr ""
-
-#: ./document-maturity.md:block 7 (paragraph)
-msgid ""
-"Clearly signalling a codebase's maturity helps others decide whether to "
-"reuse, invest in or contribute to it."
-msgstr ""
-
-#: ./document-maturity.md:block 9 (unordered list)
-msgid "Guarantee that others will use the [code](../glossary.md#code)."
-msgstr ""
-
-#: ./document-maturity.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase has a strategy for versioning which is documented."
-msgstr ""
-
-#: ./document-maturity.md:block 11 (unordered list)
-msgid "Confirm that it is clear where to get the newest version."
-msgstr ""
-
-#: ./document-maturity.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase doesn't depend on any codebases marked with a less"
-" mature status."
-msgstr ""
-
-#: ./document-maturity.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
-"beta or pre-release version."
-msgstr ""
-
-#: ./document-maturity.md:block 11 (unordered list)
-msgid "Check that there is a log of changes."
-msgstr ""
-
-#: ./document-maturity.md:block 13 (unordered list)
-msgid ""
-"When developing [policy](../glossary.md#policy), understand that any code "
-"developed needs to be tested and improved before it can be put into service."
-msgstr ""
-
-#: ./document-maturity.md:block 13 (unordered list)
-msgid ""
-"Consider versioning policy changes, especially when they trigger new "
-"versions of the source code."
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid ""
-"Make sure that services only rely on codebases of equal or greater maturity "
-"than the service. For example, don't use a beta codebase in a production "
-"service or a prototype codebase in a beta service."
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid ""
-"If the codebase is not ready for general use, work with the developers to "
-"ensure the codebase is properly labeled:"
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid ""
-"prototype: to test the look and feel, and to internally prove the concept of"
-" the technical possibilities,"
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid "alpha: to do guided tests with a limited set of users,"
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid ""
-"beta: to open up testing to a larger section of the [general "
-"public](../glossary.md#general-public), for example to test if the codebase "
-"works at scale,"
-msgstr ""
-
-#: ./document-maturity.md:block 15 (unordered list)
-msgid ""
-"pre-release version: code that is ready to be released but hasn't received "
-"formal approval yet."
-msgstr ""
-
-#: ./document-maturity.md:block 17 (unordered list)
-msgid ""
-"Add a prominent header to every interface that indicates the maturity level "
-"of the code."
-msgstr ""
-
-#: ./document-maturity.md:block 17 (unordered list)
-msgid "Version all releases."
-msgstr ""
-
-#: ./document-maturity.md:block 17 (unordered list)
-msgid ""
-"Especially in 'rolling release' scenarios, the version may be automatically "
-"derived from the [version control](../glossary.md#version-control) system "
-"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
-"describe))."
-msgstr ""
-
-#: ./document-maturity.md:block 19 (unordered list)
-msgid ""
-"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
-"advice/build-and-improve-services/service-design-and-delivery-process) by "
-"the Australian Digital Transformation Agency."
-msgstr ""
-
-#: ./document-maturity.md:block 19 (unordered list)
-msgid ""
-"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
-"delivery) by the UK Government Digital Service."
-msgstr ""
-
-#: ./document-maturity.md:block 19 (unordered list)
-msgid ""
-"[Semantic Versioning Specification](https://semver.org/) used by many "
-"codebases to label versions."
-msgstr ""
-
-#: ./document-maturity.md:block 19 (unordered list)
-msgid ""
-"[What are the Discovery, Alpha, Beta and Live stages in developing a "
-"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
-"the UK Government Digital Service."
-msgstr ""
-
-#: ./document-objectives.md:block 1 (header)
-msgid "order: 8"
-msgstr ""
-
-#: ./document-objectives.md:block 2 (header)
-msgid "Document codebase objectives"
-msgstr ""
-
-#: ./document-objectives.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
-"objectives, like a mission and goal statement, that is understandable by "
-"developers and designers so that they can use or contribute to the codebase."
-msgstr ""
-
-#: ./document-objectives.md:block 5 (unordered list)
-msgid ""
-"Codebase documentation SHOULD clearly describe the connections between "
-"[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr ""
-
-#: ./document-objectives.md:block 5 (unordered list)
-msgid ""
-"Documenting the objectives of the codebase for the [general "
-"public](../glossary.md#general-public) is OPTIONAL."
-msgstr ""
-
-#: ./document-objectives.md:block 7 (paragraph)
-msgid "Documenting codebase objectives:"
-msgstr ""
-
-#: ./document-objectives.md:block 8 (unordered list)
-msgid ""
-"provides an easy way for people to decide whether this codebase, or one of "
-"its modules, is interesting for them now or in the future."
-msgstr ""
-
-#: ./document-objectives.md:block 8 (unordered list)
-msgid "helps scope your own development."
-msgstr ""
-
-#: ./document-objectives.md:block 8 (unordered list)
-msgid ""
-"clearly communicates to other stakeholders and contributors the purpose of "
-"the codebase and the modules of which it is composed."
-msgstr ""
-
-#: ./document-objectives.md:block 10 (unordered list)
-msgid "Guarantee that the codebase achieves the stated objective(s)."
-msgstr ""
-
-#: ./document-objectives.md:block 10 (unordered list)
-msgid "Guarantee contributions to the codebase."
-msgstr ""
-
-#: ./document-objectives.md:block 10 (unordered list)
-msgid ""
-"Prevent other codebases from attempting to achieve the same objectives."
-msgstr ""
-
-#: ./document-objectives.md:block 12 (unordered list)
-msgid ""
-"Confirm that the codebase documentation includes the codebase objectives, "
-"mission or goal."
-msgstr ""
-
-#: ./document-objectives.md:block 12 (unordered list)
-msgid ""
-"Check for descriptions of connections between policy objectives and codebase"
-" objectives."
-msgstr ""
-
-#: ./document-objectives.md:block 14 (unordered list)
-msgid ""
-"Add the policy objectives to the codebase documentation, for example in the "
-"`README`."
-msgstr ""
-
-#: ./document-objectives.md:block 14 (unordered list)
-msgid ""
-"Include relevant policies which impact the community, codebase, and "
-"development like value and ethics based policies, for example accessibility "
-"or equal opportunity."
-msgstr ""
-
-#: ./document-objectives.md:block 16 (unordered list)
-msgid ""
-"Add the organizational and business objectives to the codebase "
-"documentation, for example in the `README`."
-msgstr ""
-
-#: ./document-objectives.md:block 18 (unordered list)
-msgid ""
-"Add the technology and design objectives to the codebase documentation, for "
-"example in the `README`."
-msgstr ""
-
-#: ./document-objectives.md:block 20 (unordered list)
-msgid ""
-"[How to write project "
-"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
-" by Marek Hajduczenia."
-msgstr ""
-
-#: ./documenting.md:block 1 (header)
-msgid "order: 9"
-msgstr ""
-
-#: ./documenting.md:block 2 (header)
-msgid "Document the code"
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"All of the functionality of the [codebase](../glossary.md#codebase), "
-"[policy](../glossary.md#policy) as well as source, MUST be described in "
-"language clearly understandable for those that understand the purpose of the"
-" [code](../glossary.md#code)."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation of the codebase MUST contain a description of how to "
-"install and run the source code."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation of the codebase MUST contain examples demonstrating the "
-"key functionality."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation of the codebase SHOULD contain a high level description "
-"that is clearly understandable for a wide audience of stakeholders, like the"
-" [general public](../glossary.md#general-public) and journalists."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation of the codebase SHOULD contain a section describing how to"
-" install and run a standalone version of the source code, including, if "
-"necessary, a test dataset."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation of the codebase SHOULD contain examples for all "
-"functionality."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"The documentation SHOULD describe the key components or modules of the "
-"codebase and their relationships, for example as a high level architectural "
-"diagram."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"There SHOULD be [continuous integration](../glossary.md#continuous-"
-"integration) tests for the quality of the documentation."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid ""
-"Including examples that make users want to immediately start using the "
-"codebase in the documentation of the codebase is OPTIONAL."
-msgstr ""
-
-#: ./documenting.md:block 5 (unordered list)
-msgid "Testing the code by using examples in the documentation is OPTIONAL."
-msgstr ""
-
-#: ./documenting.md:block 7 (unordered list)
-msgid "Users can start using and contributing more quickly."
-msgstr ""
-
-#: ./documenting.md:block 7 (unordered list)
-msgid ""
-"You help people discover the codebase, especially people asking 'is there "
-"already code that does something like this'."
-msgstr ""
-
-#: ./documenting.md:block 7 (unordered list)
-msgid "This provides transparency into your organization and processes."
-msgstr ""
-
-#: ./documenting.md:block 9 (unordered list)
-msgid ""
-"Contribute directly to more reusable, portable code (see [Create reusable "
-"and portable code](./reusable-and-portable-codebases.md))."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Confirm that other stakeholders, professionals from other public "
-"organizations and the general public find the documentation clear and "
-"understandable."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Confirm that the documentation describes how to install and run the source "
-"code."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Confirm that the documentation includes examples of the key functionality."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Check with members of the general public and journalists if they can "
-"understand the high level description."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Check that the instructions for how to install and run a standalone version "
-"of the source code result in a running system."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid "Check that all functionality documented contains an example."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Check that the documentation includes a high level architectural diagram or "
-"similar."
-msgstr ""
-
-#: ./documenting.md:block 11 (unordered list)
-msgid ""
-"Check that the documentation quality is part of integration testing, for "
-"example documentation is generated from code, and links and images are "
-"tested."
-msgstr ""
-
-#: ./documenting.md:block 13 (unordered list)
-msgid ""
-"Check in regularly to understand how the non-policy code in the codebase has"
-" changed."
-msgstr ""
-
-#: ./documenting.md:block 13 (unordered list)
-msgid "Give feedback on how to make non-policy documentation more clear."
-msgstr ""
-
-#: ./documenting.md:block 15 (unordered list)
-msgid "Try to use the codebase."
-msgstr ""
-
-#: ./documenting.md:block 15 (unordered list)
-msgid ""
-"Make sure you understand both the policy and source code as well as the "
-"documentation."
-msgstr ""
-
-#: ./documenting.md:block 17 (unordered list)
-msgid ""
-"Check in regularly to understand how the non-source code in the codebase has"
-" changed."
-msgstr ""
-
-#: ./documenting.md:block 17 (unordered list)
-msgid "Give feedback on how to make non-source documentation more clear."
-msgstr ""
-
-#: ./documenting.md:block 19 (unordered list)
-msgid ""
-"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
-"Docs."
-msgstr ""
-
-#: ./findability.md:block 1 (header)
-msgid "order: 14"
-msgstr ""
-
-#: ./findability.md:block 2 (header)
-msgid "Make the codebase findable"
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST be findable using a search "
-"engine by describing the problem it solves in natural language."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid "The codebase MUST be findable using a search engine by codebase name."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD have a website which describes the problem the codebase "
-"solves using the preferred jargon of different potential users of the "
-"codebase (including technologists, policy experts and managers)."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD have a unique and persistent identifier where the entry "
-"mentions the major contributors, [repository](../glossary.md#repository) "
-"location and website."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD include a machine-readable metadata description, for "
-"example in a "
-"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr ""
-
-#: ./findability.md:block 5 (unordered list)
-msgid "Regular presentations at conferences by the community are OPTIONAL."
-msgstr ""
-
-#: ./findability.md:block 7 (unordered list)
-msgid ""
-"Proactiveness is needed; just publishing a codebase and hoping it's found "
-"doesn't work."
-msgstr ""
-
-#: ./findability.md:block 7 (unordered list)
-msgid "A metadata description file increases discoverability."
-msgstr ""
-
-#: ./findability.md:block 7 (unordered list)
-msgid ""
-"The more findable a codebase is, the more potential new collaborators will "
-"find it."
-msgstr ""
-
-#: ./findability.md:block 7 (unordered list)
-msgid ""
-"By having well-written metadata containing a unique and persistent "
-"identifer, such as a Wikidata item or FSF software directory listing, and "
-"thus being part of the semantic web, it will be easier for other people to "
-"refer, cite, disambiguate and discover the codebase through third party "
-"tools."
-msgstr ""
-
-#: ./findability.md:block 9 (unordered list)
-msgid "Ensure new collaborators or replicators."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase appears in the first set of results on more than "
-"one major search engine when searching by a plain English problem "
-"description."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase appears in the first set of results on more than "
-"one major search engine when searching by a technical problem description."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase appears in the first set of results on more than "
-"one major search engine when searching by the codebase name."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid "Check for the codebase listing in relevant software catalogs."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Check for a codebase website which describes the problem the codebase "
-"solves."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Check unique and persistent identifier entries for mention of the major "
-"contributors."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Check unique and persistent identifier entries for the repository location."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid ""
-"Check unique and persistent identifier entries for the codebase website."
-msgstr ""
-
-#: ./findability.md:block 11 (unordered list)
-msgid "Check for a machine-readable metadata description file."
-msgstr ""
-
-#: ./findability.md:block 13 (unordered list)
-msgid ""
-"Contribute a description of the policy area or problem this codebase acts on"
-" or operates."
-msgstr ""
-
-#: ./findability.md:block 13 (unordered list)
-msgid ""
-"Test your problem description with peers outside of your context who aren't "
-"familiar with the codebase."
-msgstr ""
-
-#: ./findability.md:block 13 (unordered list)
-msgid ""
-"Present on how the codebase implements the [policy](../glossary.md#policy) "
-"at relevent conferences."
-msgstr ""
-
-#: ./findability.md:block 15 (unordered list)
-msgid ""
-"Budget for content design and Search Engine Optimization skills in the team."
-msgstr ""
-
-#: ./findability.md:block 15 (unordered list)
-msgid "Ensure people involved in the project present at relevant conferences."
-msgstr ""
-
-#: ./findability.md:block 15 (unordered list)
-msgid ""
-"Search trademark databases to avoid confusion or infringement before "
-"deciding the name."
-msgstr ""
-
-#: ./findability.md:block 17 (unordered list)
-msgid "Search engine optimization."
-msgstr ""
-
-#: ./findability.md:block 17 (unordered list)
-msgid "Suggest conferences to present at and present at them."
-msgstr ""
-
-#: ./findability.md:block 19 (unordered list)
-msgid ""
-"[Introduction to "
-"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
-"Wikidata community."
-msgstr ""
-
-#: ./findability.md:block 19 (unordered list)
-msgid ""
-"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
-"by the Free Softare Foundation."
-msgstr ""
-
-#: ./findability.md:block 19 (unordered list)
-msgid ""
-"The [FAIR Guiding Principles for scientific data management and "
-"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
-"International Support and Coordination Office provide a nice list of "
-"attributes that make (meta)data more machine actionable (and hence more "
-"findable). Some of these apply directly to codebases, while others may "
-"provoke exploration into what the codebase equivalent would be."
-msgstr ""
-
-#: ./index.md:block 1 (header)
-msgid "Criteria"
-msgstr ""
-
-#: ./index.md:block 3 (paragraph)
-msgid "{% assign sorted = site.pages | sort:\"order\" %}"
-msgstr ""
-
-#: ./index.md:block 4 (paragraph)
-msgid ""
-"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
-"!= \"index.md\" %}{% if page.title %}"
-msgstr ""
-
-#: ./index.md:block 5 (ordered list)
-msgid ""
-"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
-msgstr ""
-
-#: ./make-contributing-easy.md:block 1 (header)
-msgid "order: 5"
-msgstr ""
-
-#: ./make-contributing-easy.md:block 2 (header)
-msgid "Make contributing easy"
-msgstr ""
-
-#: ./make-contributing-easy.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
-"that accepts suggestions from anyone."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST include instructions for how to privately report security "
-"issues for responsible disclosure."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 5 (unordered list)
-msgid ""
-"The documentation MUST link to both the public issue tracker and submitted "
-"codebase changes, for example in a `README` file."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST have communication channels for users and developers, for "
-"example email lists."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 5 (unordered list)
-msgid ""
-"The documentation SHOULD include instructions for how to report potentially "
-"security sensitive issues on a closed channel."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 7 (unordered list)
-msgid ""
-"Enables users to fix problems and add features to the shared codebase "
-"leading to better, more reliable and feature rich software."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 7 (unordered list)
-msgid "Allows collaborative uptake of shared digital infrastructure."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 7 (unordered list)
-msgid "Helps users decide to use one codebase over another."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 9 (unordered list)
-msgid "Guarantee others will reuse the codebase."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 11 (unordered list)
-msgid "Confirm that there is a public issue tracker."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 11 (unordered list)
-msgid ""
-"Confirm that there are instructions for privately reporting security issues."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase contains links to the public issue tracker and "
-"submitted codebase changes."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 11 (unordered list)
-msgid ""
-"Confirm that it is possible to participate in a discussion with other users "
-"and developers about the software using channels described in the codebase."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 13 (unordered list)
-msgid ""
-"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
-"relevant external policy expert can volunteer help."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 15 (unordered list)
-msgid ""
-"Track management issues in the codebase, so that external managers with "
-"relevant experience can volunteer help."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 15 (unordered list)
-msgid ""
-"Support your experienced policy makers, developers and designers to keep "
-"contributing to the codebase for as long as possible."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 17 (unordered list)
-msgid "Respond promptly to requests."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 17 (unordered list)
-msgid ""
-"Keep your management informed of the time and resources you require to "
-"support other contributors."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 19 (unordered list)
-msgid ""
-"[How to inspire exceptional contributions to your open-source "
-"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
-"to-your-open-source-project-1ebf) by Joel Hans."
-msgstr ""
-
-#: ./make-contributing-easy.md:block 19 (unordered list)
-msgid ""
-"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
-"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
-msgstr ""
-
-#: ./open-licenses.md:block 1 (header)
-msgid "order: 13"
-msgstr ""
-
-#: ./open-licenses.md:block 2 (header)
-msgid "Publish with an open license"
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid ""
-"All [code](../glossary.md#code) and documentation MUST be licensed such that"
-" it may be freely reusable, changeable and redistributable."
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid ""
-"Software source code MUST be licensed under an [OSI-approved or FSF "
-"Free/Libre license](https://spdx.org/licenses/)."
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid "All code MUST be published with a license file."
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid ""
-"Contributors MUST NOT be required to transfer copyright of their "
-"contributions to the [codebase](../glossary.md#codebase)."
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid ""
-"All source code files in the codebase SHOULD include a copyright notice and "
-"a license header that are machine-readable."
-msgstr ""
-
-#: ./open-licenses.md:block 5 (unordered list)
-msgid ""
-"Having multiple licenses for different types of code and documentation is "
-"OPTIONAL."
-msgstr ""
-
-#: ./open-licenses.md:block 7 (unordered list)
-msgid ""
-"Makes it possible for anyone to see the code and know that they can and how "
-"they can reuse it."
-msgstr ""
-
-#: ./open-licenses.md:block 9 (unordered list)
-msgid "Prevent use of the code by any specific actors."
-msgstr ""
-
-#: ./open-licenses.md:block 11 (unordered list)
-msgid "Confirm that the codebase is clearly licensed."
-msgstr ""
-
-#: ./open-licenses.md:block 11 (unordered list)
-msgid ""
-"Confirm that the license for the source code is on the [OSI-approved or FSF "
-"Free/Libre license list](https://spdx.org/licenses/) and the license for "
-"documentation [conforms to the Open "
-"Definition](https://opendefinition.org/licenses/)."
-msgstr ""
-
-#: ./open-licenses.md:block 11 (unordered list)
-msgid "Confirm that the licenses used in the codebase are included as files."
-msgstr ""
-
-#: ./open-licenses.md:block 11 (unordered list)
-msgid ""
-"Confirm that contribution guidelines and "
-"[repository](../glossary.md#repository) configuration do not require "
-"transfer of copyright."
-msgstr ""
-
-#: ./open-licenses.md:block 11 (unordered list)
-msgid ""
-"Check for machine-readable license checking in the codebase [continuous "
-"integration](../glossary.md#continuous-integration) tests."
-msgstr ""
-
-#: ./open-licenses.md:block 13 (unordered list)
-msgid ""
-"Develop [policy](../glossary.md#policy) that requires code to be [open "
-"source](../glossary.md#open-source)."
-msgstr ""
-
-#: ./open-licenses.md:block 13 (unordered list)
-msgid ""
-"Develop policy that disincentivizes non-open source code and technology in "
-"procurement."
-msgstr ""
-
-#: ./open-licenses.md:block 15 (unordered list)
-msgid ""
-"Only work with open source vendors that deliver their code by publishing it "
-"under an open source license."
-msgstr ""
-
-#: ./open-licenses.md:block 15 (unordered list)
-msgid ""
-"Beware that even though [Creative Commons "
-"licenses](https://creativecommons.org/licenses/) are great for "
-"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
-"NOT freely reusable, changeable and redistributable and don't fulfill these "
-"requirements."
-msgstr ""
-
-#: ./open-licenses.md:block 17 (unordered list)
-msgid "Add a new `license` file to every new codebase created."
-msgstr ""
-
-#: ./open-licenses.md:block 17 (unordered list)
-msgid ""
-"Add a copyright notice and a license header to every new source code file "
-"created."
-msgstr ""
-
-#: ./open-licenses.md:block 19 (unordered list)
-msgid ""
-"[Open source definition](https://opensource.org/osd) by the Open Source "
-"Initiative, all open source licenses meet this definition."
-msgstr ""
-
-#: ./open-licenses.md:block 19 (unordered list)
-msgid ""
-"[Animated video introduction to Creative "
-"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
-"Creative Commons Aotearoa New Zealand."
-msgstr ""
-
-#: ./open-licenses.md:block 19 (unordered list)
-msgid ""
-"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
-"Software Foundation Europe for unambiguous, human-readable and machine-"
-"readable copyright and licensing information."
-msgstr ""
-
-#: ./open-licenses.md:block 19 (unordered list)
-msgid ""
-"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
-" standardized, machine-readable abbreviations for most licenses."
-msgstr ""
-
-#: ./open-standards.md:block 1 (header)
-msgid "order: 11"
-msgstr ""
-
-#: ./open-standards.md:block 2 (header)
-msgid "Use open standards"
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"For features of the [codebase](../glossary.md#codebase) that facilitate the "
-"exchange of data the codebase MUST use an [open "
-"standard](../glossary.md#open-standard) that meets the [Open Source "
-"Initiative Open Standard Requirements](https://opensource.org/osr)."
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"Any non-open standards used MUST be recorded clearly as such in the "
-"documentation."
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"Any standard chosen for use within the codebase MUST be listed in the "
-"documentation with a link to where it is available."
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"Any non-open standards chosen for use within the codebase MUST NOT hinder "
-"collaboration and reuse."
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"If no existing open standard is available, effort SHOULD be put into "
-"developing one."
-msgstr ""
-
-#: ./open-standards.md:block 5 (unordered list)
-msgid ""
-"Standards that are machine testable SHOULD be preferred over those that are "
-"not."
-msgstr ""
-
-#: ./open-standards.md:block 7 (unordered list)
-msgid "Creates interoperability between systems."
-msgstr ""
-
-#: ./open-standards.md:block 7 (unordered list)
-msgid "Reduces possible vendor lock-in."
-msgstr ""
-
-#: ./open-standards.md:block 7 (unordered list)
-msgid ""
-"Guarantees access to the knowledge required to reuse and contribute to the "
-"codebase."
-msgstr ""
-
-#: ./open-standards.md:block 9 (unordered list)
-msgid "Make it understandable how to use the software."
-msgstr ""
-
-#: ./open-standards.md:block 11 (unordered list)
-msgid "Confirm that data exchange follows an OSI approved open standard."
-msgstr ""
-
-#: ./open-standards.md:block 11 (unordered list)
-msgid ""
-"Confirm that any non-open standards used are clearly documented as such."
-msgstr ""
-
-#: ./open-standards.md:block 11 (unordered list)
-msgid ""
-"Confirm that documentation includes a list of the standards followed within "
-"the codebase, each with a working link, or a statement that no standards "
-"were chosen."
-msgstr ""
-
-#: ./open-standards.md:block 13 (unordered list)
-msgid "Mandate use of open standards everywhere possible."
-msgstr ""
-
-#: ./open-standards.md:block 13 (unordered list)
-msgid "Prohibit procurement of technology that does not use open standards."
-msgstr ""
-
-#: ./open-standards.md:block 15 (unordered list)
-msgid ""
-"Consider including open standard compliance assessment in "
-"[code](../glossary.md#code) reviews."
-msgstr ""
-
-#: ./open-standards.md:block 17 (unordered list)
-msgid ""
-"Add [continuous integration](../glossary.md#continuous-integration) tests "
-"for compliance with the standards."
-msgstr ""
-
-#: ./open-standards.md:block 17 (unordered list)
-msgid ""
-"Review the commits and other [repository](../glossary.md#repository) "
-"resources for references to standards and cross-check those with the "
-"standards listed."
-msgstr ""
-
-#: ./open-standards.md:block 19 (unordered list)
-msgid ""
-"[Open Standards principles](https://www.gov.uk/government/publications/open-"
-"standards-principles/open-standards-principles), "
-"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
-msgstr ""
-
-#: ./open-to-contributions.md:block 1 (header)
-msgid "order: 4"
-msgstr ""
-
-#: ./open-to-contributions.md:block 2 (header)
-msgid "Welcome contributors"
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
-"suggestions for changes to the codebase."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST include contribution guidelines explaining what kinds of "
-"contributions are welcome and how contributors can get involved, for example"
-" in a `CONTRIBUTING` file."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST document the governance of the codebase, contributions and"
-" its community, for example in a `GOVERNANCE` file."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD advertise the committed engagement of involved "
-"organizations in the development and maintenance."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid "The codebase SHOULD publish codebase activity statistics."
-msgstr ""
-
-#: ./open-to-contributions.md:block 5 (unordered list)
-msgid ""
-"Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr ""
-
-#: ./open-to-contributions.md:block 7 (unordered list)
-msgid ""
-"Helps newcomers understand and trust the codebase community's leadership."
-msgstr ""
-
-#: ./open-to-contributions.md:block 7 (unordered list)
-msgid ""
-"Prevents the community that works on a codebase splitting because there is "
-"no way to influence its goals and progress, resulting in diverging "
-"communities."
-msgstr ""
-
-#: ./open-to-contributions.md:block 9 (unordered list)
-msgid "Guarantee others will join the community."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid ""
-"Confirm that it is possible to submit suggestions for changes to the "
-"codebase."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid "Confirm there are contribution guidelines."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase governance is clearly explained, including how to "
-"influence codebase governance."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid "Check for a list of involved organizations."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid "Check for a roadmap."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid "Check for published activity statistics."
-msgstr ""
-
-#: ./open-to-contributions.md:block 11 (unordered list)
-msgid "Check for a code of conduct."
-msgstr ""
-
-#: ./open-to-contributions.md:block 13 (unordered list)
-msgid ""
-"Add a list to the codebase of any other resources that "
-"[policy](../glossary.md#policy) experts, non-governmental organizations and "
-"academics would find useful for understanding or reusing your policy."
-msgstr ""
-
-#: ./open-to-contributions.md:block 13 (unordered list)
-msgid ""
-"Consider adding contact details so that other policy makers considering "
-"collaboration can ask you for advice."
-msgstr ""
-
-#: ./open-to-contributions.md:block 15 (unordered list)
-msgid ""
-"Make sure that the documentation of the governance includes the current "
-"process for how to make changes to the governance."
-msgstr ""
-
-#: ./open-to-contributions.md:block 15 (unordered list)
-msgid ""
-"If the community has some consensus about how the governance should change, "
-"then include those ideas stated as ambitions in the documentation."
-msgstr ""
-
-#: ./open-to-contributions.md:block 15 (unordered list)
-msgid ""
-"Make sure the documentation explains how each organization is involved in "
-"the codebase, what resources it has available for it and for how long."
-msgstr ""
-
-#: ./open-to-contributions.md:block 15 (unordered list)
-msgid ""
-"Support your experienced policy makers, developers and designers to stay "
-"part of the community for as long as possible."
-msgstr ""
-
-#: ./open-to-contributions.md:block 19 (unordered list)
-msgid ""
-"[Building welcoming communities](https://opensource.guide/building-"
-"community/) by Open Source Guides."
-msgstr ""
-
-#: ./open-to-contributions.md:block 19 (unordered list)
-msgid ""
-"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
-"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
-"source-project/) by Mike McQuaid."
-msgstr ""
-
-#: ./open-to-contributions.md:block 19 (unordered list)
-msgid ""
-"[Leadership and governance](https://opensource.guide/leadership-and-"
-"governance/) for growing [open source](../glossary.md#open-source) community"
-" projects, by Open Source Guides."
-msgstr ""
-
-#: ./open-to-contributions.md:block 19 (unordered list)
-msgid ""
-"[Building online communities](http://hintjens.com/blog:117) by Pieter "
-"Hintjens (long read!)."
-msgstr ""
-
-#: ./require-review.md:block 1 (header)
-msgid "order: 7"
-msgstr ""
-
-#: ./require-review.md:block 2 (header)
-msgid "Require review of contributions"
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"All contributions that are accepted or committed to release versions of the "
-"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
-"documentation."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Reviewers MUST provide feedback on all decisions to not accept a "
-"contribution."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Contributions SHOULD conform to the standards, architecture and decisions "
-"set out in the codebase in order to pass review."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
-"tests of the codebase."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Contributions SHOULD be reviewed by someone in a different context than the "
-"contributor."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid ""
-"Version control systems SHOULD NOT accept non-reviewed contributions in "
-"release versions."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid "Reviews SHOULD happen within two business days."
-msgstr ""
-
-#: ./require-review.md:block 5 (unordered list)
-msgid "Performing reviews by multiple reviewers is OPTIONAL."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid "Increases codebase quality."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid "Reduces security risks as well as operational risks."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid "Creates a culture of making every contribution great."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid "Catches the most obvious mistakes that could happen."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid ""
-"Gives contributors the security that their contributions are only accepted "
-"if they really add value."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid ""
-"Assures contributors of a guaranteed time for feedback or collaborative "
-"improvement."
-msgstr ""
-
-#: ./require-review.md:block 7 (unordered list)
-msgid ""
-"Prompt reviews increase both rate of delivery and contributor engagement."
-msgstr ""
-
-#: ./require-review.md:block 9 (unordered list)
-msgid "Guarantee the right solution to a problem."
-msgstr ""
-
-#: ./require-review.md:block 9 (unordered list)
-msgid "Mean that reviewers are liable."
-msgstr ""
-
-#: ./require-review.md:block 9 (unordered list)
-msgid "Absolve a contributor from writing documentation and tests."
-msgstr ""
-
-#: ./require-review.md:block 9 (unordered list)
-msgid "Provide you with the right reviewers."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid ""
-"Confirm that every commit in the history has been reviewed by a different "
-"contributor."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid "Confirm that reviews include source, policy, tests and documentation."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid "Confirm that rejected contributions were appropriately explained."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid ""
-"Check if reviews cover conformance to standards, architecture and codebase "
-"guidelines."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid "Check with reviewers if they run the code and tests during review."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid ""
-"Check with reviewers if commits have been reviewed by a different "
-"contributor in a different context."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid ""
-"Check for use of branch protection in the [version "
-"control](../glossary.md#version-control) system."
-msgstr ""
-
-#: ./require-review.md:block 11 (unordered list)
-msgid "Check the times between contribution submission and review."
-msgstr ""
-
-#: ./require-review.md:block 13 (unordered list)
-msgid ""
-"Institute a 'four eyes' policy where everything, not just code, is reviewed."
-msgstr ""
-
-#: ./require-review.md:block 13 (unordered list)
-msgid ""
-"Use a version control system or methodology that enables review and "
-"feedback."
-msgstr ""
-
-#: ./require-review.md:block 15 (unordered list)
-msgid "Make delivering great code a shared objective."
-msgstr ""
-
-#: ./require-review.md:block 15 (unordered list)
-msgid ""
-"Make sure writing and reviewing contributions to source, policy, "
-"documentation and tests are considered equally valuable."
-msgstr ""
-
-#: ./require-review.md:block 15 (unordered list)
-msgid ""
-"Create a culture where all contributions are welcome and everyone is "
-"empowered to review them."
-msgstr ""
-
-#: ./require-review.md:block 15 (unordered list)
-msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr ""
-
-#: ./require-review.md:block 17 (unordered list)
-msgid ""
-"Ask other contributors on the codebase to review your work, in your "
-"organization or outside of it."
-msgstr ""
-
-#: ./require-review.md:block 17 (unordered list)
-msgid ""
-"Try to respond to others' requests for code review promptly, initially "
-"providing feedback about the concept of the change."
-msgstr ""
-
-#: ./require-review.md:block 19 (unordered list)
-msgid ""
-"[How to review code the GDS way](https://gds-"
-"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
-" Government Digital Service."
-msgstr ""
-
-#: ./require-review.md:block 19 (unordered list)
-msgid ""
-"Branch protection on "
-"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
-"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
-"protected-branches) and "
-"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
-msgstr ""
-
-#: ./require-review.md:block 19 (unordered list)
-msgid ""
-"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
-"gentle-art-of-patch-review/) by Sage Sharp."
-msgstr ""
-
-#: ./require-review.md:block 19 (unordered list)
-msgid ""
-"[Measuring "
-"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
-"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 1 (header)
-msgid "order: 3"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 2 (header)
-msgid "Create reusable and portable code"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid ""
-"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
-"[different contexts](../glossary.md#different-contexts)."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid ""
-"The codebase MUST be independent from any secret, undisclosed, proprietary "
-"or non-open licensed [code](../glossary.md#code) or services for execution "
-"and understanding."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid "The codebase SHOULD be in use by multiple parties."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid ""
-"Configuration SHOULD be used to make code adapt to context specific needs."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid "The codebase SHOULD be localizable."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid ""
-"Code and its documentation SHOULD NOT contain situation-specific "
-"information."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
-msgid ""
-"Codebase modules SHOULD be documented in such a way as to enable reuse in "
-"codebases in other contexts."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Enables other policy makers, developers and designers to reuse what you've "
-"developed, to test it, to improve it and contribute those improvements back "
-"leading to better quality, cheaper maintenance and higher reliability."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Makes the code easier for new people to understand (as it's more general)."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Makes it easier to control the mission, vision and scope of the codebase "
-"because the codebase is thoughtfully and purposefully designed for "
-"reusability."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Codebases used by multiple parties are more likely to benefit from a self-"
-"sustaining community."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Any contributor is able to test and contribute without relying on the "
-"situation-specific infrastructure of any other contributor or deployment."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"Composing a codebase from well documented modules improves reusability and "
-"maintainability."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
-msgid ""
-"A module is easier to reuse in another context if its purpose is clearly "
-"documented."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
-msgid "Get others to reuse the codebase."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
-msgid "Build a community."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
-msgid ""
-"Shift responsibility for documentation, support, bug-fixing, etc. to another"
-" party."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
-msgid "Guarantee that modules are generic enough to be reused in any context."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
-msgid ""
-"Confirm with someone in a similar role at another organization if they can "
-"reuse the codebase and what that would entail."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
-msgid ""
-"Confirm that the codebase can run without using any proprietary or non open-"
-"licensed code or services."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
-msgid ""
-"Check that the codebase is in use by multiple parties or in multiple "
-"contexts."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
-msgid ""
-"Check that the codebase files and commit history do not include situation-"
-"specific data."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
-msgid ""
-"Document your [policy](../glossary.md#policy) with enough clarity and detail"
-" that it can be understood outside of its original context."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
-msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
-msgid ""
-"Make sure that stakeholders and business owners understand that reusability "
-"is an explicit codebase goal as this reduces technical debt and provides "
-"sustainability for the codebase."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
-msgid "Source should be designed:"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
-msgid "for reuse by other users and organizations regardless of locale,"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
-msgid "to solve a general problem instead of a specific one,"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
-msgid "in logically meaningful and isolated modules,"
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
-msgid ""
-"so that someone in a similar organization facing a similar problem would be "
-"able to use (parts of) the solution."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
-msgid ""
-"Ensure that the codebase documentation describes the build-time and runtime "
-"dependencies. If your context requires deploying to proprietary platforms or"
-" using proprietary components, ensure that collaborators can develop, use, "
-"test, and deploy without them."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
-msgid ""
-"For each commit, reviewers verify that content does not include situation-"
-"specific data such as hostnames, personal and organizational data, or tokens"
-" and passwords."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
-msgid ""
-"[Making source code open and reusable](https://www.gov.uk/service-"
-"manual/technology/making-source-code-open-and-reusable) by the UK Government"
-" Digital Service."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
-msgid ""
-"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
-"OpenAPI Initiative defines a standard, programming language-agnostic "
-"interface description for human and machine-readable HTTP APIs."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
-msgid ""
-"[Localization vs. "
-"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
-" the World Wide Web Consortium."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
-msgid ""
-"[Internationalization techniques: Authoring HTML & "
-"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
-"World Wide Web Consortium."
-msgstr ""
-
-#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
-msgid ""
-"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
-"Operating System."
-msgstr ""
-
-#: ./style.md:block 1 (header)
-msgid "order: 15"
-msgstr ""
-
-#: ./style.md:block 2 (header)
-msgid "Use a coherent style"
-msgstr ""
-
-#: ./style.md:block 5 (unordered list)
-msgid ""
-"Contributions MUST adhere to either a coding or writing style guide, either "
-"the [codebase](../glossary.md#codebase) community's own or an existing one "
-"that is advertised in or part of the codebase."
-msgstr ""
-
-#: ./style.md:block 5 (unordered list)
-msgid "Contributions SHOULD pass automated tests on style."
-msgstr ""
-
-#: ./style.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD include inline comments and documentation for non-"
-"trivial sections."
-msgstr ""
-
-#: ./style.md:block 5 (unordered list)
-msgid ""
-"Including sections on [understandable English](understandable-english-"
-"first.md) in the style guide is OPTIONAL."
-msgstr ""
-
-#: ./style.md:block 7 (unordered list)
-msgid ""
-"Enables contributors in different environments to work together on a unified"
-" product."
-msgstr ""
-
-#: ./style.md:block 7 (unordered list)
-msgid ""
-"Unifying vocabularies reduces friction in communication between "
-"contributors."
-msgstr ""
-
-#: ./style.md:block 9 (unordered list)
-msgid "Help contributors write well or effectively explain what they do."
-msgstr ""
-
-#: ./style.md:block 11 (unordered list)
-msgid ""
-"Confirm that contributions are in line with the style guides specified in "
-"the documentation."
-msgstr ""
-
-#: ./style.md:block 11 (unordered list)
-msgid "Check for the presence of automated tests on style."
-msgstr ""
-
-#: ./style.md:block 13 (unordered list)
-msgid ""
-"Create, follow and continually improve on a style guide for "
-"[policy](../glossary.md#policy) and documentation as well as document this "
-"in the codebase, for example in the `CONTRIBUTING` or `README`."
-msgstr ""
-
-#: ./style.md:block 15 (unordered list)
-msgid ""
-"Include written language, source, test and policy standards in your "
-"organizational definition of quality."
-msgstr ""
-
-#: ./style.md:block 17 (paragraph)
-msgid ""
-"If the codebase does not already have engineering guidelines or other "
-"contributor guidance, start by adding documentation to the "
-"[repository](../glossary.md#repository) describing whatever is being done "
-"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
-"the file is to communicate design preferences, naming conventions, and other"
-" aspects machines can't easily check. Guidance should include what would be "
-"expected from [code](../glossary.md#code) contributions in order for them to"
-" be merged by the maintainers, including source, tests and documentation. "
-"Continually improve upon and expand this documentation with the aim of "
-"evolving this documentation into engineering guidelines."
-msgstr ""
-
-#: ./style.md:block 18 (paragraph)
-msgid "Additionally:"
-msgstr ""
-
-#: ./style.md:block 19 (unordered list)
-msgid "Use a linter."
-msgstr ""
-
-#: ./style.md:block 19 (unordered list)
-msgid "Add linter configurations to the codebase."
-msgstr ""
-
-#: ./style.md:block 21 (unordered list)
-msgid ""
-"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
-"Hugo Martins."
-msgstr ""
-
-#: ./style.md:block 21 (unordered list)
-msgid ""
-"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
-"Wikipedia."
-msgstr ""
-
-#: ./understandable-english-first.md:block 1 (header)
-msgid "order: 10"
-msgstr ""
-
-#: ./understandable-english-first.md:block 2 (header)
-msgid "Use plain English"
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"All [codebase](../glossary.md#codebase) documentation MUST be in English."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"All [code](../glossary.md#code) MUST be in English, except where "
-"[policy](../glossary.md#policy) is machine interpreted as code."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"All bundled policy not available in English MUST have an accompanying "
-"summary in English."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"Any translation MUST be up to date with the English version and vice versa."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
-" specific terms in the codebase without an explanation preceding it or a "
-"link to an explanation."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"The name of the codebase SHOULD be descriptive and free from acronyms, "
-"abbreviations, puns or organizational branding."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"Documentation SHOULD aim for a lower secondary education reading level, as "
-"recommended by the [Web Content Accessibility Guidelines "
-"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
-msgstr ""
-
-#: ./understandable-english-first.md:block 5 (unordered list)
-msgid ""
-"Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr ""
-
-#: ./understandable-english-first.md:block 7 (unordered list)
-msgid ""
-"Makes the codebase and what it does understandable for a wider variety of "
-"stakeholders in multiple contexts."
-msgstr ""
-
-#: ./understandable-english-first.md:block 7 (unordered list)
-msgid "Helps with the discoverability of the codebase."
-msgstr ""
-
-#: ./understandable-english-first.md:block 7 (unordered list)
-msgid ""
-"Can help you meet the [European Union accessibility "
-"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
-" which requires most public sector information to be accessible."
-msgstr ""
-
-#: ./understandable-english-first.md:block 9 (unordered list)
-msgid "Make explanations of the codebase's functionality understandable."
-msgstr ""
-
-#: ./understandable-english-first.md:block 9 (unordered list)
-msgid "Make your organization's jargon understandable without an explanation."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid "Confirm that codebase documentation is available in English."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid ""
-"Confirm that source code is in English, or confirm any non-English is policy"
-" or terms with preceding explanations."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid "Confirm any non-English policy has an accompanying summary in English."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid ""
-"Confirm that translations and the English version have the same content."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid ""
-"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
-"English/domain specific terms are in the documentation."
-msgstr ""
-
-#: ./understandable-english-first.md:block 11 (unordered list)
-msgid "Check the spelling, grammar and readability of the documentation."
-msgstr ""
-
-#: ./understandable-english-first.md:block 13 (unordered list)
-msgid ""
-"Frequently test with other management, developers and designers in the "
-"process if they understand what you are delivering and how you document it."
-msgstr ""
-
-#: ./understandable-english-first.md:block 15 (unordered list)
-msgid ""
-"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
-"English/domain specific terms in internal communications in and between "
-"teams and stakeholders. Add any such terms to a glossary and link to it from"
-" the places they are being used."
-msgstr ""
-
-#: ./understandable-english-first.md:block 15 (unordered list)
-msgid ""
-"Be critical of documentation and descriptions in proposals and changes. If "
-"you don't understand something, others will probably also struggle with it."
-msgstr ""
-
-#: ./understandable-english-first.md:block 17 (unordered list)
-msgid ""
-"Frequently test with policy makers and management if they understand what "
-"you are delivering and how you document it."
-msgstr ""
-
-#: ./understandable-english-first.md:block 17 (unordered list)
-msgid ""
-"Ask someone outside of your context if they understand the content (for "
-"example, a developer working on a different codebase)."
-msgstr ""
-
-#: ./understandable-english-first.md:block 19 (unordered list)
-msgid ""
-"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
-"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
-"readable and understandable."
-msgstr ""
-
-#: ./understandable-english-first.md:block 19 (unordered list)
-msgid ""
-"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
-" allows 1000 most common English words."
-msgstr ""
-
-#: ./understandable-english-first.md:block 19 (unordered list)
-msgid ""
-"[Definition of plain "
-"language](https://www.plainlanguage.gov/about/definitions/) by United States"
-" General Services Administration."
-msgstr ""
-
-#: ./version-control-and-history.md:block 1 (header)
-msgid "order: 6"
-msgstr ""
-
-#: ./version-control-and-history.md:block 2 (header)
-msgid "Maintain version control"
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"The community MUST have a way to maintain [version "
-"control](../glossary.md#version-control) for the "
-"[code](../glossary.md#code)."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"All files in the [codebase](../glossary.md#codebase) MUST be version "
-"controlled."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid "All decisions MUST be documented in commit messages."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"Every commit message MUST link to discussions and issues wherever possible."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"The codebase SHOULD be maintained in a distributed version control system."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid "Contributors SHOULD group relevant changes in commits."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"Maintainers SHOULD mark released versions of the codebase, for example using"
-" revision tags or textual labels."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"Contributors SHOULD prefer file formats where the changes within the files "
-"can be easily viewed and understood in the version control system."
-msgstr ""
-
-#: ./version-control-and-history.md:block 5 (unordered list)
-msgid ""
-"It is OPTIONAL for contributors to sign their commits and provide an email "
-"address, so that future contributors are able to contact past contributors "
-"with questions about their work."
-msgstr ""
-
-#: ./version-control-and-history.md:block 7 (paragraph)
-msgid ""
-"Version control means keeping track of changes to the code over time. This "
-"allows you to create structured documentation of the history of the "
-"codebase. This is essential for collaboration at scale."
-msgstr ""
-
-#: ./version-control-and-history.md:block 8 (paragraph)
-msgid "Distributed version control enables you to:"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid "have a full copy of the code and its history"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid "revert to an earlier version of the codebase whenever you want to"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid ""
-"record your changes and the reasons why you made them, to help future "
-"developers understand the process"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid "compare two different versions"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid "work on changes in parallel as a team before merging them together"
-msgstr ""
-
-#: ./version-control-and-history.md:block 9 (unordered list)
-msgid ""
-"continue to work when the network is unavailable, merging changes back with "
-"everyone else’s at a later date"
-msgstr ""
-
-#: ./version-control-and-history.md:block 11 (unordered list)
-msgid "Substitute for [advertising maturity](document-maturity.md)."
-msgstr ""
-
-#: ./version-control-and-history.md:block 11 (unordered list)
-msgid "Guarantee the code executes correctly."
-msgstr ""
-
-#: ./version-control-and-history.md:block 11 (unordered list)
-msgid "Guarantee collaborators."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Confirm that the codebase is kept in version control using software such as "
-"Git."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Review the commit history, confirming that all commit messages explain why "
-"the change was made."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Review the commit history, confirming that where possible all commit "
-"messages include the discussion about the change was or where to find it "
-"(with a URL)."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid "Check if the version control system is distributed."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Review the commit history, check if grouping of relevant changes in "
-"accordance with the contributing guidelines."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Check that it is possible to access a specific version of the codebase, for "
-"example through a revision tag or a textual label."
-msgstr ""
-
-#: ./version-control-and-history.md:block 13 (unordered list)
-msgid ""
-"Check that the file formats used in the codebase are text formats where "
-"possible."
-msgstr ""
-
-#: ./version-control-and-history.md:block 15 (unordered list)
-msgid ""
-"If a new version of the codebase is created because of a "
-"[policy](../glossary.md#policy) change, make sure it's clear in the "
-"documentation:"
-msgstr ""
-
-#: ./version-control-and-history.md:block 15 (unordered list)
-msgid "what the policy change is,"
-msgstr ""
-
-#: ./version-control-and-history.md:block 15 (unordered list)
-msgid "how it's changed the codebase."
-msgstr ""
-
-#: ./version-control-and-history.md:block 16 (paragraph)
-msgid ""
-"For example, adding a new category of applicant to a codebase that manages "
-"granting permits would be considered a policy change."
-msgstr ""
-
-#: ./version-control-and-history.md:block 18 (unordered list)
-msgid ""
-"Support policy makers, developers and designers to be clear about what "
-"improvements they're making to the codebase. Making improvements isn't a "
-"public relations risk."
-msgstr ""
-
-#: ./version-control-and-history.md:block 20 (unordered list)
-msgid ""
-"Write clear commit messages so that it is easy to understand why the commit "
-"was made."
-msgstr ""
-
-#: ./version-control-and-history.md:block 20 (unordered list)
-msgid ""
-"Mark different versions so that it is easy to access a specific version, for"
-" example using revision tags or textual labels."
-msgstr ""
-
-#: ./version-control-and-history.md:block 20 (unordered list)
-msgid "Write clear commit messages so that versions can be usefully compared."
-msgstr ""
-
-#: ./version-control-and-history.md:block 20 (unordered list)
-msgid ""
-"Work with policy makers to describe how the source code was updated after a "
-"policy change."
-msgstr ""
-
-#: ./version-control-and-history.md:block 22 (unordered list)
-msgid ""
-"[Producing OSS: Version Control "
-"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
-"Fogel."
-msgstr ""
-
-#: ./version-control-and-history.md:block 22 (unordered list)
-msgid ""
-"[Maintaining version control in coding](https://www.gov.uk/service-"
-"manual/technology/maintaining-version-control-in-coding) by the UK "
-"Government Digital Service."
-msgstr ""
-
-#: ./version-control-and-history.md:block 22 (unordered list)
-msgid ""
-"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
-" use it or refresh your skills."
-msgstr ""
-
-#: ./version-control-and-history.md:block 22 (unordered list)
-msgid ""
-"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
-"education.pdf) by GitHub, a list with the most common used git commands."
-msgstr ""

From 54e51d9fcd6990c5f609fc04f8edae550d4b1843 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Thu, 1 Dec 2022 12:42:55 +0800
Subject: [PATCH 08/71] Added translation using Weblate (Chinese (Traditional))

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2728 +++++++++++++++++++++++
 1 file changed, 2728 insertions(+)
 create mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..a47881e0
--- /dev/null
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,2728 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-12-01 12:42+0800\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: zh_Hant\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Translate Toolkit 3.7.4\n"
+
+#
+
+#: ./bundle-policy-and-code.md:block 1 (header)
+msgid "order: 2"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 2 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 4 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST include the "
+"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
+"is based on."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include all source code that the policy is based on, "
+"unless used for fraud detection."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 6 (header)
+msgid "Why this is important"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 7 (paragraph)
+msgid ""
+"Access to both the source code and the policy documents is necessary for "
+"understanding and reuse of, as well as collaboration in, a codebase. "
+"Understanding the context and the policies in that context is fundamental to"
+" understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them. To be able to evaluate whether to adopt a codebase in a "
+"new context, an organization will need to understand what process changes it"
+" must choose to make or how to contribute additional configurability to the "
+"existing solution in order to adapt it to the new context."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 8 (header)
+msgid "What this does not do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid "Guarantee that a codebase will reflect the bundled policy."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid ""
+"Make sure packages comply with the local technical infrastructure or legal "
+"framework of a given public organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 10 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 12 (header)
+msgid "Policy makers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Collaborate with developers and designers to ensure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable such as"
+" [Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
+" [Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Track policy with [the same version control](version-control-and-history.md)"
+" and documentation used to track source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed and whether it still matches the [intentions of the "
+"policy](document-objectives.md)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 14 (header)
+msgid "Management: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 16 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Work together with policy makers to ensure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 18 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[Free online tools for building BPMN, CMMN and DMN diagrams at "
+"bmpn.io](https://bpmn.io/) by Camunda."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./code-in-the-open.md:block 1 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./code-in-the-open.md:block 2 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source [code](../glossary.md#code) for any "
+"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT upload sensitive information regarding users, their "
+"organization or third parties to the "
+"[repository](../glossary.md#repository)."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./code-in-the-open.md:block 7 (paragraph)
+msgid "Coding in the open:"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "improves transparency"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "increases code quality"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "facilitates the auditing processes"
+msgstr ""
+
+#: ./code-in-the-open.md:block 9 (paragraph)
+msgid ""
+"These aspects together create more opportunities for citizens to understand "
+"how software and policy impact their interactions with a public "
+"organization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid "Make source code or policy reusable."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid ""
+"Make the [codebase](../glossary.md#codebase) and the code within it "
+"understandable to as many people as possible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase files and commit history do not include sensitive "
+"information."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"Clearly split data and code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 1 (header)
+msgid "order: 12"
+msgstr ""
+
+#: ./continuous-integration.md:block 2 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"All functionality in the source [code](../glossary.md#code) MUST have "
+"automated tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "The codebase MUST have active contributors."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "Using [continuous integration](../glossary.md#continuous-integration):"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "allows you to quickly identify problems with the codebase,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"enables risk taking and focusing on problem solving while minimizing stress "
+"for the contributors,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"lowers barriers for new contributors by reducing the amount of understanding"
+" necessary to suggest changes,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "leads to more maintainable code,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "speeds up the development cycle."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Smaller, more regular contributions are typically easier to evaluate and "
+"lower risk compared to large infrequent changes."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Codebases in active development more reliably provide opportunities for "
+"collaboration and feedback."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid ""
+"Create a fault tolerant infrastructure that will work and scale perfectly."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Create meaningful tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Test for real life situations."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Guarantee the code will deliver exactly the same policy result."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that code coverage tools check that coverage is at 100% of the code."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Check if code coverage data is published."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Involve management as well as developers and designers as early in the "
+"process as possible and keep them engaged throughout development of your "
+"policy."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure the code reflects any changes to the policy (see [Maintain version"
+" control](version-control-and-history.md))."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Plan the work to deliver small parts very often instead of large parts less "
+"frequently."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management structure the work plan such that it can be delivered as "
+"small increments."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Structure code written to handle conditions which are difficult to create in"
+" a test environment in such a way that the conditions can be simulated "
+"during testing. Forms of resource exhaustion such as running out of storage "
+"space and memory allocation failure are typical examples of difficult to "
+"create conditions."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
+"Humble."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 1 (header)
+msgid "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 2 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is ready to use MUST only depend on other codebases that "
+"are also ready to use."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is not yet ready to use MUST have one of the labels: "
+"prototype, alpha, beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./document-maturity.md:block 7 (paragraph)
+msgid ""
+"Clearly signalling a codebase's maturity helps others decide whether to "
+"reuse, invest in or contribute to it."
+msgstr ""
+
+#: ./document-maturity.md:block 9 (unordered list)
+msgid "Guarantee that others will use the [code](../glossary.md#code)."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Confirm that it is clear where to get the newest version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase doesn't depend on any codebases marked with a less"
+" mature status."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
+"beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any code "
+"developed needs to be tested and improved before it can be put into service."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that services only rely on codebases of equal or greater maturity "
+"than the service. For example, don't use a beta codebase in a production "
+"service or a prototype codebase in a beta service."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"If the codebase is not ready for general use, work with the developers to "
+"ensure the codebase is properly labeled:"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"prototype: to test the look and feel, and to internally prove the concept of"
+" the technical possibilities,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid "alpha: to do guided tests with a limited set of users,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"beta: to open up testing to a larger section of the [general "
+"public](../glossary.md#general-public), for example to test if the codebase "
+"works at scale,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"pre-release version: code that is ready to be released but hasn't received "
+"formal approval yet."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Add a prominent header to every interface that indicates the maturity level "
+"of the code."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid "Version all releases."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Especially in 'rolling release' scenarios, the version may be automatically "
+"derived from the [version control](../glossary.md#version-control) system "
+"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
+"describe))."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[What are the Discovery, Alpha, Beta and Live stages in developing a "
+"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
+"the UK Government Digital Service."
+msgstr ""
+
+#: ./document-objectives.md:block 1 (header)
+msgid "order: 8"
+msgstr ""
+
+#: ./document-objectives.md:block 2 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
+"objectives, like a mission and goal statement, that is understandable by "
+"developers and designers so that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./document-objectives.md:block 7 (paragraph)
+msgid "Documenting codebase objectives:"
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"provides an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid "helps scope your own development."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"clearly communicates to other stakeholders and contributors the purpose of "
+"the codebase and the modules of which it is composed."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee that the codebase achieves the stated objective(s)."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee contributions to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid ""
+"Prevent other codebases from attempting to achieve the same objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development like value and ethics based policies, for example accessibility "
+"or equal opportunity."
+msgstr ""
+
+#: ./document-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 18 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 20 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./documenting.md:block 1 (header)
+msgid "order: 9"
+msgstr ""
+
+#: ./documenting.md:block 2 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"All of the functionality of the [codebase](../glossary.md#codebase), "
+"[policy](../glossary.md#policy) as well as source, MUST be described in "
+"language clearly understandable for those that understand the purpose of the"
+" [code](../glossary.md#code)."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the source code."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid "Testing the code by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "Users can start using and contributing more quickly."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid ""
+"You help people discover the codebase, especially people asking 'is there "
+"already code that does something like this'."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "This provides transparency into your organization and processes."
+msgstr ""
+
+#: ./documenting.md:block 9 (unordered list)
+msgid ""
+"Contribute directly to more reusable, portable code (see [Create reusable "
+"and portable code](./reusable-and-portable-codebases.md))."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated from code, and links and images are "
+"tested."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid "Try to use the codebase."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 19 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./findability.md:block 1 (header)
+msgid "order: 14"
+msgstr ""
+
+#: ./findability.md:block 2 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be findable using a search "
+"engine by describing the problem it solves in natural language."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "The codebase MUST be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"Proactiveness is needed; just publishing a codebase and hoping it's found "
+"doesn't work."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid "A metadata description file increases discoverability."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"The more findable a codebase is, the more potential new collaborators will "
+"find it."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"By having well-written metadata containing a unique and persistent "
+"identifer, such as a Wikidata item or FSF software directory listing, and "
+"thus being part of the semantic web, it will be easier for other people to "
+"refer, cite, disambiguate and discover the codebase through third party "
+"tools."
+msgstr ""
+
+#: ./findability.md:block 9 (unordered list)
+msgid "Ensure new collaborators or replicators."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a plain English problem "
+"description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a technical problem description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by the codebase name."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevent conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid "Ensure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Search engine optimization."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Softare Foundation."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./index.md:block 1 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./index.md:block 3 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./index.md:block 4 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 5 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 1 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 2 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
+"that accepts suggestions from anyone."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include instructions for how to privately report security "
+"issues for responsible disclosure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD include instructions for how to report potentially "
+"security sensitive issues on a closed channel."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid ""
+"Enables users to fix problems and add features to the shared codebase "
+"leading to better, more reliable and feature rich software."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Allows collaborative uptake of shared digital infrastructure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Helps users decide to use one codebase over another."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 9 (unordered list)
+msgid "Guarantee others will reuse the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 13 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid ""
+"Keep your management informed of the time and resources you require to "
+"support other contributors."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./open-licenses.md:block 1 (header)
+msgid "order: 13"
+msgstr ""
+
+#: ./open-licenses.md:block 2 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) and documentation MUST be licensed such that"
+" it may be freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid "All code MUST be published with a license file."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Having multiple licenses for different types of code and documentation is "
+"OPTIONAL."
+msgstr ""
+
+#: ./open-licenses.md:block 7 (unordered list)
+msgid ""
+"Makes it possible for anyone to see the code and know that they can and how "
+"they can reuse it."
+msgstr ""
+
+#: ./open-licenses.md:block 9 (unordered list)
+msgid "Prevent use of the code by any specific actors."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires code to be [open "
+"source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their code by publishing it "
+"under an open source license."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./open-standards.md:block 1 (header)
+msgid "order: 11"
+msgstr ""
+
+#: ./open-standards.md:block 2 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"For features of the [codebase](../glossary.md#codebase) that facilitate the "
+"exchange of data the codebase MUST use an [open "
+"standard](../glossary.md#open-standard) that meets the [Open Source "
+"Initiative Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Standards that are machine testable SHOULD be preferred over those that are "
+"not."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Creates interoperability between systems."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Reduces possible vendor lock-in."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid ""
+"Guarantees access to the knowledge required to reuse and contribute to the "
+"codebase."
+msgstr ""
+
+#: ./open-standards.md:block 9 (unordered list)
+msgid "Make it understandable how to use the software."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./open-standards.md:block 15 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in "
+"[code](../glossary.md#code) reviews."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./open-standards.md:block 19 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./open-to-contributions.md:block 1 (header)
+msgid "order: 4"
+msgstr ""
+
+#: ./open-to-contributions.md:block 2 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
+"suggestions for changes to the codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Helps newcomers understand and trust the codebase community's leadership."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Prevents the community that works on a codebase splitting because there is "
+"no way to influence its goals and progress, resulting in diverging "
+"communities."
+msgstr ""
+
+#: ./open-to-contributions.md:block 9 (unordered list)
+msgid "Guarantee others will join the community."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./require-review.md:block 1 (header)
+msgid "order: 7"
+msgstr ""
+
+#: ./require-review.md:block 2 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
+"documentation."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD conform to the standards, architecture and decisions "
+"set out in the codebase in order to pass review."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
+"tests of the codebase."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Increases codebase quality."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Reduces security risks as well as operational risks."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Creates a culture of making every contribution great."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Catches the most obvious mistakes that could happen."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Gives contributors the security that their contributions are only accepted "
+"if they really add value."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Assures contributors of a guaranteed time for feedback or collaborative "
+"improvement."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Prompt reviews increase both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Guarantee the right solution to a problem."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Mean that reviewers are liable."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Absolve a contributor from writing documentation and tests."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Provide you with the right reviewers."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check if reviews cover conformance to standards, architecture and codebase "
+"guidelines."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check with reviewers if they run the code and tests during review."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just code, is reviewed."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make delivering great code a shared objective."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Try to respond to others' requests for code review promptly, initially "
+"providing feedback about the concept of the change."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 1 (header)
+msgid "order: 3"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 2 (header)
+msgid "Create reusable and portable code"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
+"[different contexts](../glossary.md#different-contexts)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed [code](../glossary.md#code) or services for execution "
+"and understanding."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Configuration SHOULD be used to make code adapt to context specific needs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Enables other policy makers, developers and designers to reuse what you've "
+"developed, to test it, to improve it and contribute those improvements back "
+"leading to better quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes the code easier for new people to understand (as it's more general)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes it easier to control the mission, vision and scope of the codebase "
+"because the codebase is thoughtfully and purposefully designed for "
+"reusability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Codebases used by multiple parties are more likely to benefit from a self-"
+"sustaining community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Any contributor is able to test and contribute without relying on the "
+"situation-specific infrastructure of any other contributor or deployment."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Composing a codebase from well documented modules improves reusability and "
+"maintainability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"A module is easier to reuse in another context if its purpose is clearly "
+"documented."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Get others to reuse the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Build a community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid ""
+"Shift responsibility for documentation, support, bug-fixing, etc. to another"
+" party."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Guarantee that modules are generic enough to be reused in any context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"reuse the codebase and what that would entail."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed code or services."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
+msgid ""
+"Ensure that the codebase documentation describes the build-time and runtime "
+"dependencies. If your context requires deploying to proprietary platforms or"
+" using proprietary components, ensure that collaborators can develop, use, "
+"test, and deploy without them."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
+"OpenAPI Initiative defines a standard, programming language-agnostic "
+"interface description for human and machine-readable HTTP APIs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Internationalization techniques: Authoring HTML & "
+"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
+"World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
+"Operating System."
+msgstr ""
+
+#: ./style.md:block 1 (header)
+msgid "order: 15"
+msgstr ""
+
+#: ./style.md:block 2 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST adhere to either a coding or writing style guide, either "
+"the [codebase](../glossary.md#codebase) community's own or an existing one "
+"that is advertised in or part of the codebase."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include inline comments and documentation for non-"
+"trivial sections."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Including sections on [understandable English](understandable-english-"
+"first.md) in the style guide is OPTIONAL."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Enables contributors in different environments to work together on a unified"
+" product."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Unifying vocabularies reduces friction in communication between "
+"contributors."
+msgstr ""
+
+#: ./style.md:block 9 (unordered list)
+msgid "Help contributors write well or effectively explain what they do."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./style.md:block 13 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./style.md:block 15 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./style.md:block 17 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [code](../glossary.md#code) contributions in order for them to"
+" be merged by the maintainers, including source, tests and documentation. "
+"Continually improve upon and expand this documentation with the aim of "
+"evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./style.md:block 18 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
+"Hugo Martins."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./understandable-english-first.md:block 1 (header)
+msgid "order: 10"
+msgstr ""
+
+#: ./understandable-english-first.md:block 2 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [codebase](../glossary.md#codebase) documentation MUST be in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) MUST be in English, except where "
+"[policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Makes the codebase and what it does understandable for a wider variety of "
+"stakeholders in multiple contexts."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid "Helps with the discoverability of the codebase."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Can help you meet the [European Union accessibility "
+"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
+" which requires most public sector information to be accessible."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make explanations of the codebase's functionality understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make your organization's jargon understandable without an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 13 (unordered list)
+msgid ""
+"Frequently test with other management, developers and designers in the "
+"process if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Frequently test with policy makers and management if they understand what "
+"you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
+"readable and understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
+" allows 1000 most common English words."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./version-control-and-history.md:block 1 (header)
+msgid "order: 6"
+msgstr ""
+
+#: ./version-control-and-history.md:block 2 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The community MUST have a way to maintain [version "
+"control](../glossary.md#version-control) for the "
+"[code](../glossary.md#code)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"All files in the [codebase](../glossary.md#codebase) MUST be version "
+"controlled."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "Contributors SHOULD group relevant changes in commits."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Contributors SHOULD prefer file formats where the changes within the files "
+"can be easily viewed and understood in the version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./version-control-and-history.md:block 7 (paragraph)
+msgid ""
+"Version control means keeping track of changes to the code over time. This "
+"allows you to create structured documentation of the history of the "
+"codebase. This is essential for collaboration at scale."
+msgstr ""
+
+#: ./version-control-and-history.md:block 8 (paragraph)
+msgid "Distributed version control enables you to:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "have a full copy of the code and its history"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "revert to an earlier version of the codebase whenever you want to"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"record your changes and the reasons why you made them, to help future "
+"developers understand the process"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "compare two different versions"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "work on changes in parallel as a team before merging them together"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"continue to work when the network is unavailable, merging changes back with "
+"everyone else’s at a later date"
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Substitute for [advertising maturity](document-maturity.md)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee the code executes correctly."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee collaborators."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./version-control-and-history.md:block 16 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 18 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
+" use it or refresh your skills."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""

From 6167e4e9764cf20521b647334d450524d83dd06e Mon Sep 17 00:00:00 2001
From: Tommy Jiang <baptist333@yahoo.com.tw>
Date: Fri, 16 Dec 2022 08:20:07 +0000
Subject: [PATCH 09/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 99.5% (493 of 495 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 1092 ++++++++++++++---------
 1 file changed, 654 insertions(+), 438 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index a47881e0..e68d9d57 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,28 +3,29 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2022-12-22 13:00+0000\n"
+"Last-Translator: Tommy Jiang <baptist333@yahoo.com.tw>\n"
+"Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
+"pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Translate Toolkit 3.7.4\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Generator: Weblate 4.15\n"
 
 #
-
 #: ./bundle-policy-and-code.md:block 1 (header)
 msgid "order: 2"
-msgstr ""
+msgstr "順序：2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr ""
+msgstr "同捆政策與原始碼"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
-msgstr ""
+msgstr "必要條件"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
@@ -32,26 +33,29 @@ msgid ""
 "[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
 "is based on."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)必須包含作為[原始碼](../glossary."
+"md#code)基礎的[政策](../glossary.md#policy)。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include all source code that the policy is based on, "
 "unless used for fraud detection."
-msgstr ""
+msgstr "代碼庫必須包含政策基於的所有原始碼（用於偵測詐騙的原始碼除外）。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr ""
+msgstr "政策必須採用機器可閱讀且非模凌兩可的格式。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
-msgstr ""
+msgstr "[持續整合](../glossary.md#continuous-integration) "
+"測試應該驗證原始碼與政策可一致執行。"
 
 #: ./bundle-policy-and-code.md:block 6 (header)
 msgid "Why this is important"
-msgstr ""
+msgstr "重要的原因"
 
 #: ./bundle-policy-and-code.md:block 7 (paragraph)
 msgid ""
@@ -64,56 +68,60 @@ msgid ""
 " must choose to make or how to contribute additional configurability to the "
 "existing solution in order to adapt it to the new context."
 msgstr ""
+"取得原始碼與政策文件，才能瞭解、重複使用以及在代碼庫中進行協作。瞭解情境以及"
+"政策所在情境，才能瞭解代碼庫想要嘗試解決的問題，以及代碼庫可以如何解決這些問"
+"題。如欲評估是否在新的情境中採用代碼庫，組織需要瞭解必須改變的流程，或是如何"
+"提升現有解決方案的配置性，才能適應新情境。"
 
 #: ./bundle-policy-and-code.md:block 8 (header)
 msgid "What this does not do"
-msgstr ""
+msgstr "沒有以下作用"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid "Guarantee that a codebase will reflect the bundled policy."
-msgstr ""
+msgstr "保證代碼庫能反應同捆政策。"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid ""
 "Make sure packages comply with the local technical infrastructure or legal "
 "framework of a given public organization."
-msgstr ""
+msgstr "確保套件符合本地技術基礎設施或是特定公共組織的法律框架。"
 
 #: ./bundle-policy-and-code.md:block 10 (header)
 msgid "How to test"
-msgstr ""
+msgstr "測試方式"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid ""
 "Confirm with a civil servant that all policy that the source code is based "
 "on is included."
-msgstr ""
+msgstr "與公務人員確認包含作為程式碼基礎的整個政策。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr ""
+msgstr "與公務人員確認包含所有作為政策基礎的原始碼。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
-msgstr ""
+msgstr "確認政策是否由機器詮釋。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid ""
 "Check the continuous integration tests for coherent execution of source code"
 " and policy pass."
-msgstr ""
+msgstr "確認原始碼與政策的一致執行能通過持續整合測試。"
 
 #: ./bundle-policy-and-code.md:block 12 (header)
 msgid "Policy makers: what you need to do"
-msgstr ""
+msgstr "決策者們：您們的責任"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Collaborate with developers and designers to ensure there is no mismatch "
 "between policy code and source code."
-msgstr ""
+msgstr "與開發人員及設計師合作，確保政策程式碼與原始碼沒有錯配。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
@@ -124,10 +132,13 @@ msgid ""
 "which impact the development or the deployment context of the codebase for "
 "your organization."
 msgstr ""
+"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；倘若政策內"
+"文沒有英文版本，請提供英文版摘要。務必包含貴組織選擇遵守的標準，以及影響貴組"
+"織代碼庫開發或部署情境的任何組織流程。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid "Provide references and links to texts which support the policies."
-msgstr ""
+msgstr "請提供政策相關參考資料與連結。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
@@ -138,79 +149,88 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
 msgstr ""
+"政策內容請使用明確且機器可閱讀的文字，像是[業務流程模型與標記法](https://en."
+"wikipedia.org/wiki/"
+"Business_Process_Model_and_Notation)、[決策模型與標記法](https://en.wikipedia"
+".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
+"wikipedia.org/wiki/CMMN)。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Track policy with [the same version control](version-control-and-history.md)"
 " and documentation used to track source code."
-msgstr ""
+msgstr "追蹤政策時，請使用與追蹤原始碼[同樣的版本管控](version-control-and-history."
+"md)。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed and whether it still matches the [intentions of the "
 "policy](document-objectives.md)."
-msgstr ""
+msgstr "定期檢查代碼庫中的非政策程式碼是否有變動，以及是否依舊符合[政策意圖"
+"](document-objectives.md)。"
 
 #: ./bundle-policy-and-code.md:block 14 (header)
 msgid "Management: what you need to do"
-msgstr ""
+msgstr "管理人員：您們的職責"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr ""
+msgstr "讓決策者、開發人員與設計師參與開發並且在整個過程中保持聯繫。"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr ""
+msgstr "確保決策者、開發人員與設計師朝相同目標努力。"
 
 #: ./bundle-policy-and-code.md:block 16 (header)
 msgid "Developers and designers: what you need to do"
-msgstr ""
+msgstr "開發人員與設計師：您們的職責"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr ""
+msgstr "熟悉並且學會使用貴組織決策者所使用的流程模型標記法。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
 "Work together with policy makers to ensure there is no mismatch between "
 "policy code and source code."
-msgstr ""
+msgstr "與決策者合作，確保政策程式碼與原始碼沒有錯配。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid "Give feedback on how to make policy documentation more clear."
-msgstr ""
+msgstr "針對如何讓政策文字更清楚提供意見。"
 
 #: ./bundle-policy-and-code.md:block 18 (header)
 msgid "Further reading"
-msgstr ""
+msgstr "延伸閱讀"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
 "[Free online tools for building BPMN, CMMN and DMN diagrams at "
 "bmpn.io](https://bpmn.io/) by Camunda."
-msgstr ""
+msgstr "Camunda[提供免費線上工具，可用於建構BPMN、CMMN與DMN圖表](https://bpmn.io/)。"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
+"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/"
+"view-bpmn-quick-guide/)。"
 
 #: ./code-in-the-open.md:block 1 (header)
 msgid "order: 1"
-msgstr ""
+msgstr "順序：1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr ""
+msgstr "開放的程式碼"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -218,65 +238,69 @@ msgid ""
 "[policy](../glossary.md#policy) in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
 msgstr ""
+"使用中[政策](../glossary.md#policy)的[原始碼](../glossary."
+"md#code)都必須要公開供民眾使用（用於偵測詐欺的原始碼除外）。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr ""
+msgstr "使用中軟體的所有原始碼都必須要公開供民眾使用（用於偵測詐欺的原始碼除外）。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Contributors MUST NOT upload sensitive information regarding users, their "
 "organization or third parties to the "
 "[repository](../glossary.md#repository)."
-msgstr ""
+msgstr "貢獻者絕對不可上傳有關使用者、其組織或第三方的敏感性資訊到[儲存庫](../glossar"
+"y.md#repository)。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr ""
+msgstr "目前非使用中的原始碼（像是新版本、提案或較舊版本）都應該公開。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Documenting which source code or policy underpins any specific interaction "
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
-msgstr ""
+msgstr "您可以選擇是否要紀錄[一般大眾](../glossary.md#general-"
+"public)與組織互動背後所採用的原始碼或政策。"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
 msgid "Coding in the open:"
-msgstr ""
+msgstr "公開編寫程式碼："
 
 #: ./code-in-the-open.md:block 8 (unordered list)
 msgid "improves transparency"
-msgstr ""
+msgstr "改善資訊透明"
 
 #: ./code-in-the-open.md:block 8 (unordered list)
 msgid "increases code quality"
-msgstr ""
+msgstr "提高程式碼品質"
 
 #: ./code-in-the-open.md:block 8 (unordered list)
 msgid "facilitates the auditing processes"
-msgstr ""
+msgstr "促進稽核流程"
 
 #: ./code-in-the-open.md:block 9 (paragraph)
 msgid ""
 "These aspects together create more opportunities for citizens to understand "
 "how software and policy impact their interactions with a public "
 "organization."
-msgstr ""
+msgstr "這些面向讓市民更有機會瞭解軟體與政策如何影響其與公共組織的互動。"
 
 #: ./code-in-the-open.md:block 11 (unordered list)
 msgid "Make source code or policy reusable."
-msgstr ""
+msgstr "讓原始碼或政策能重複使用。"
 
 #: ./code-in-the-open.md:block 11 (unordered list)
 msgid ""
 "Make the [codebase](../glossary.md#codebase) and the code within it "
 "understandable to as many people as possible."
-msgstr ""
+msgstr "讓更多人瞭解[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
@@ -284,53 +308,57 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr ""
+msgstr "確認使用中的每個版本的原始碼都公布在網路上，且民眾不需要透過任何驗證或授權，"
+"就能在原始貢獻組織之外查看這些原始碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
 "Confirm that the codebase files and commit history do not include sensitive "
 "information."
-msgstr ""
+msgstr "確認代碼庫檔案與提交歷史紀錄不包含敏感性資訊。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid "Check for the publication of source code not currently in use."
-msgstr ""
+msgstr "檢查目前非使用中的原始碼是否有公開。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Develop policies in the open."
-msgstr ""
+msgstr "公開地制定政策。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Prioritize open and transparent policies."
-msgstr ""
+msgstr "以公開透明政策為優先。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid "Develop a culture that embraces openness, learning and feedback."
-msgstr ""
+msgstr "孕育一個重視開放、學習與意見回饋的文化。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid ""
 "Collaborate with external vendors and freelancers by working in the open."
-msgstr ""
+msgstr "公開作業，與外部供應商與自由業者合作。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr ""
+msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含配置、使用者名稱、密碼、公開金"
+"鑰或其他生產系統中的實名資訊等敏感性資訊。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
 "Clearly split data and code, in order to meet the requirement about "
 "sensitive information above."
-msgstr ""
+msgstr "為符合上述敏感性資訊相關規定，請明確分開資料與程式碼。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
 "[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
 " by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[公開編寫程式碼](https://gds.blog.gov.uk/2012/10/12/"
+"coding-in-the-open/)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -339,6 +367,9 @@ msgid ""
 "guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
 "Service."
 msgstr ""
+"英國政府數位服務團的[程式碼應該公開或封閉的時機](https://www.gov.uk/"
+"government/publications/open-source-guidance/when-code-should-be-open-or-"
+"closed)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -347,6 +378,9 @@ msgid ""
 "guidance/security-considerations-when-coding-in-the-open) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[公開編寫程式碼的安全考量](https://www.gov.uk/government/"
+"publications/open-source-guidance/security-considerations-when-coding-in-the-"
+"open)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -354,211 +388,218 @@ msgid ""
 "manual/technology/deploying-software-regularly) by the UK Government Digital"
 " Service."
 msgstr ""
+"英國政府數位服務團的[定期部署軟體](https://www.gov.uk/service-manual/"
+"technology/deploying-software-regularly)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
 "[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
 "use-github/) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[政府數位服務團如何使用GitHub](https://gdstechnology.blog"
+".gov.uk/2014/01/27/how-we-use-github/)。"
 
 #: ./continuous-integration.md:block 1 (header)
 msgid "order: 12"
-msgstr ""
+msgstr "順序：12"
 
 #: ./continuous-integration.md:block 2 (header)
 msgid "Use continuous integration"
-msgstr ""
+msgstr "使用持續整合"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "All functionality in the source [code](../glossary.md#code) MUST have "
 "automated tests."
-msgstr ""
+msgstr "[原始碼](../glossary.md#code)的所有功能都必須有自動化測試。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Contributions MUST pass all automated tests before they are admitted into "
 "the [codebase](../glossary.md#codebase)."
-msgstr ""
+msgstr "所有貢獻內容都必須通過自動化測試，才能上傳至[代碼庫](../glossary."
+"md#codebase)。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST have guidelines explaining how to structure contributions."
-msgstr ""
+msgstr "代碼庫必須有說明貢獻內容結構的準則。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "The codebase MUST have active contributors."
-msgstr ""
+msgstr "代碼庫必須有活躍貢獻者。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr ""
+msgstr "代碼庫準則應該規定每份貢獻內容都應只聚焦在單一議題上。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr ""
+msgstr "應該監督原始碼測試與註解範圍。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr ""
+msgstr "可選擇測試[政策](../glossary.md#policy)與註解，確保與原始碼一致。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr ""
+msgstr "可選擇測試政策與註解的風格以及失效連結。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "Using [continuous integration](../glossary.md#continuous-integration):"
-msgstr ""
+msgstr "使用[持續整合](../glossary.md#continuous-integration)："
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "allows you to quickly identify problems with the codebase,"
-msgstr ""
+msgstr "讓您能迅速找出代碼庫的問題、"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "enables risk taking and focusing on problem solving while minimizing stress "
 "for the contributors,"
-msgstr ""
+msgstr "在減少貢獻者面臨的壓力的同時，可以承擔風險並且專注在解決問題上、"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "lowers barriers for new contributors by reducing the amount of understanding"
 " necessary to suggest changes,"
-msgstr ""
+msgstr "讓新貢獻者能更容易建議變更，降低新貢獻者的門檻、"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "leads to more maintainable code,"
-msgstr ""
+msgstr "程式碼更容易維護、"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "speeds up the development cycle."
-msgstr ""
+msgstr "加快開發速度。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "Smaller, more regular contributions are typically easier to evaluate and "
 "lower risk compared to large infrequent changes."
-msgstr ""
+msgstr "內容較少但更規律提出的貢獻內容，通常較為容易評估，風險也低於內容龐大但鮮少提"
+"出的變更。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "Codebases in active development more reliably provide opportunities for "
 "collaboration and feedback."
-msgstr ""
+msgstr "開發中的代碼庫較能提供協作與提供意見回饋的機會。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid ""
 "Create a fault tolerant infrastructure that will work and scale perfectly."
-msgstr ""
+msgstr "建立能夠順暢作業、擴展且能容錯的基礎架構。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Create meaningful tests."
-msgstr ""
+msgstr "建立有意義的測試。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Test for real life situations."
-msgstr ""
+msgstr "測試現實生活會實際發生的情境。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Guarantee the code will deliver exactly the same policy result."
-msgstr ""
+msgstr "保證程式碼的成果會與政策相同。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid "Confirm that there are tests present."
-msgstr ""
+msgstr "確認有測試可用。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that code coverage tools check that coverage is at 100% of the code."
-msgstr ""
+msgstr "確認程式碼覆蓋率工具能檢查全部的程式碼。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that contributions are only admitted into the codebase after all of "
 "the tests are passed."
-msgstr ""
+msgstr "確認貢獻內容只有在通過所有測試後，才會上傳至代碼庫。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that contribution guidelines explain how to structure contributions."
-msgstr ""
+msgstr "確認貢獻準則說明貢獻內容的結構。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that there are contributions from within the last three months."
-msgstr ""
+msgstr "確認最近三個月內有貢獻內容上傳。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid "Check if code coverage data is published."
-msgstr ""
+msgstr "檢查程式碼覆蓋率數據是否有公佈。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
 "Involve management as well as developers and designers as early in the "
 "process as possible and keep them engaged throughout development of your "
 "policy."
-msgstr ""
+msgstr "儘早讓管理人員、開發人員與設計師參與，並且讓他們全程參與您政策的開發。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
 "Make sure there are also automated tests set up for policy documentation."
-msgstr ""
+msgstr "確保政策註解也有自動化測試。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid "Fix policy documentation promptly if it fails a test."
-msgstr ""
+msgstr "如果政策註解未能通過測試，請立即修正。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
 "Make sure the code reflects any changes to the policy (see [Maintain version"
 " control](version-control-and-history.md))."
-msgstr ""
+msgstr "確保程式碼能反應出政策的任何變動(請參閱[維持版本控制](version-control-and-"
+"history.md))。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Make sure to test with real end users as quickly and often as possible."
-msgstr ""
+msgstr "迅速且頻繁地與真正的終端使用者進行測試。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Plan the work to deliver small parts very often instead of large parts less "
 "frequently."
-msgstr ""
+msgstr "計畫頻繁地提交少量內容，而非久久一次繳交大量內容。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr ""
+msgstr "聘請能逐漸越來越與計畫同步的顧問服務。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "After a large failure, encourage publication of incident reports and public "
 "discussion of what was learned."
-msgstr ""
+msgstr "發生嚴重錯誤後，鼓勵公開事故報告以及公開討論事後學到的教訓。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help management structure the work plan such that it can be delivered as "
 "small increments."
-msgstr ""
+msgstr "鼓勵管理階層擬定工作計畫，逐漸提高提交的內容數量。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help contributors limit the scope of their contributions and feature "
 "requests to be as small as reasonable."
-msgstr ""
+msgstr "協助貢獻者限制其貢獻內容與功能請求範圍。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help management and policy makers test their contributions, for example by "
 "testing their contributions for broken links or style."
-msgstr ""
+msgstr "協助管理人員與決策者測試其貢獻內容，例如測試其貢獻內容的失效連結或風格。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
@@ -567,21 +608,22 @@ msgid ""
 "during testing. Forms of resource exhaustion such as running out of storage "
 "space and memory allocation failure are typical examples of difficult to "
 "create conditions."
-msgstr ""
+msgstr "編排程式碼時，要能夠將難以在測試環境下創造出來的情況，在測試過程中模擬出來。"
+"硬碟空間不足與記憶體配置失敗等資源耗盡情況，都是難以重現的情況。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Tune the test code coverage tools to avoid false alarms resulting from "
 "inlining or other optimizations."
-msgstr ""
+msgstr "調整程式碼覆蓋率測試工具，避免內聯或其他優化問題造成假警報。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid "Deploy often."
-msgstr ""
+msgstr "經常部署。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid "Integrate your work at least once a day."
-msgstr ""
+msgstr "至少每天整合工作內容一次。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
@@ -589,12 +631,14 @@ msgid ""
 "integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
 " by Martin Fowler."
 msgstr ""
+"Martin Fowler的[什麼是持續整合](https://www.martinfowler.com/articles/"
+"continuousIntegration.html)。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
 "[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
 "Humble."
-msgstr ""
+msgstr "Jez Humble的[什麼是持續交付](https://www.continuousdelivery.com/)。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
@@ -602,6 +646,8 @@ msgid ""
 "way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[使用持續交付](https://gds-way.cloudapps.digital/"
+"standards/continuous-delivery.html)。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
@@ -609,129 +655,134 @@ msgid ""
 "regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
 "testing-your-service-regularly) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[品保：定期測試服務](https://www.gov.uk/service-manual/"
+"technology/quality-assurance-testing-your-service-regularly)。"
 
 #: ./document-maturity.md:block 1 (header)
 msgid "order: 16 redirect_from: - criteria/advertise-maturity"
-msgstr ""
+msgstr "順序：16；自「criteria/advertise-maturity」重新導向"
 
 #: ./document-maturity.md:block 2 (header)
 msgid "Document codebase maturity"
-msgstr ""
+msgstr "紀錄代碼庫成熟度"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
-msgstr ""
+msgstr "[代碼庫](../glossary.md#codebase) 必須版本化。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase that is ready to use MUST only depend on other codebases that "
 "are also ready to use."
-msgstr ""
+msgstr "可用的代碼庫只能仰賴其他立即可用的代碼庫。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase that is not yet ready to use MUST have one of the labels: "
 "prototype, alpha, beta or pre-release version."
-msgstr ""
+msgstr "尚未準備好使用的代碼庫必須有這些標籤之一：原型、預覽、測試或發布前版本。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr ""
+msgstr "代碼庫應該包含每次版本變動的紀錄，像是「CHANGELOG」。"
 
 #: ./document-maturity.md:block 7 (paragraph)
 msgid ""
 "Clearly signalling a codebase's maturity helps others decide whether to "
 "reuse, invest in or contribute to it."
-msgstr ""
+msgstr "清楚標示代碼庫的成熟度有助於他人決定是否要重複使用、投資或貢獻該代碼庫。"
 
 #: ./document-maturity.md:block 9 (unordered list)
 msgid "Guarantee that others will use the [code](../glossary.md#code)."
-msgstr ""
+msgstr "保證他人會使用[程式碼](../glossary.md#code)。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase has a strategy for versioning which is documented."
-msgstr ""
+msgstr "確認代碼庫有版本化策略且有文件詳細記載該策略。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Confirm that it is clear where to get the newest version."
-msgstr ""
+msgstr "確認最新版本容易取得。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase doesn't depend on any codebases marked with a less"
 " mature status."
-msgstr ""
+msgstr "確認代碼庫不需要仰賴成熟度標示較低的其他代碼庫。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase is ready to use or labeled as prototype, alpha, "
 "beta or pre-release version."
-msgstr ""
+msgstr "確認代碼庫已準備好使用，或是標示為原型、預覽、測試或發布前版本。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Check that there is a log of changes."
-msgstr ""
+msgstr "檢查是否有變更紀錄。"
 
 #: ./document-maturity.md:block 13 (unordered list)
 msgid ""
 "When developing [policy](../glossary.md#policy), understand that any code "
 "developed needs to be tested and improved before it can be put into service."
-msgstr ""
+msgstr "制定[政策](../glossary."
+"md#policy)時，記住任何開發出來的程式碼都必須經過測試與改善，才能夠實際應用。"
 
 #: ./document-maturity.md:block 13 (unordered list)
 msgid ""
 "Consider versioning policy changes, especially when they trigger new "
 "versions of the source code."
-msgstr ""
+msgstr "考慮到版本化政策的變動，特別是因此產生新版本原始碼的情況時。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "Make sure that services only rely on codebases of equal or greater maturity "
 "than the service. For example, don't use a beta codebase in a production "
 "service or a prototype codebase in a beta service."
-msgstr ""
+msgstr "確保服務使用的代碼庫成熟度等同或高於服務本身。舉例來說，生產服務不要用測試版"
+"代碼庫，測試版服務不要用原型代碼庫。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "If the codebase is not ready for general use, work with the developers to "
 "ensure the codebase is properly labeled:"
-msgstr ""
+msgstr "若代碼庫尚未準備好使用，請與開發人員一起確保該代碼庫具備合適的標籤："
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "prototype: to test the look and feel, and to internally prove the concept of"
 " the technical possibilities,"
-msgstr ""
+msgstr "原型：測試外觀與體驗，並且從內部證明技術可能性的概念、"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid "alpha: to do guided tests with a limited set of users,"
-msgstr ""
+msgstr "預覽：在使用者有限的情況下進行引導測試、"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "beta: to open up testing to a larger section of the [general "
 "public](../glossary.md#general-public), for example to test if the codebase "
 "works at scale,"
-msgstr ""
+msgstr "測試：讓更多[社會大眾](../glossary.md#general-"
+"public)參與測試，例如測試代碼庫在大規模運作下是否依舊順暢、"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "pre-release version: code that is ready to be released but hasn't received "
 "formal approval yet."
-msgstr ""
+msgstr "發布前版本：已經準備好發布但尚未正式獲准的程式碼。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
 "Add a prominent header to every interface that indicates the maturity level "
 "of the code."
-msgstr ""
+msgstr "在每個介面上加上顯著的標頭，標示程式碼的成熟度。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid "Version all releases."
-msgstr ""
+msgstr "所有推出的程式碼都要標示版本。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
@@ -740,6 +791,9 @@ msgid ""
 "metadata (for example by using [git describe](https://git-scm.com/docs/git-"
 "describe))."
 msgstr ""
+"特別是在「滾動發行」的情況時，程式碼的版本資訊可能自動從[版本管控](../glossar"
+"y.md#version-control)系統元資料中擷取(例如使用[git describe](https://git-scm."
+"com/docs/git-describe))。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
@@ -747,18 +801,21 @@ msgid ""
 "advice/build-and-improve-services/service-design-and-delivery-process) by "
 "the Australian Digital Transformation Agency."
 msgstr ""
+"澳洲數位轉型局的[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
+"build-and-improve-services/service-design-and-delivery-process)。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
 "[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
 "delivery) by the UK Government Digital Service."
-msgstr ""
+msgstr "英國政府數位服務團的[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
+"agile-delivery)。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
 "[Semantic Versioning Specification](https://semver.org/) used by many "
 "codebases to label versions."
-msgstr ""
+msgstr "許多代碼庫使用[語意化版本控制規範](https://semver.org/)來標示版本。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
@@ -766,14 +823,16 @@ msgid ""
 "service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
 "the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[什麼是服務開發當中的探索、預覽、測試與上線階段？ [影片 "
+"0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)。"
 
 #: ./document-objectives.md:block 1 (header)
 msgid "order: 8"
-msgstr ""
+msgstr "順序：8"
 
 #: ./document-objectives.md:block 2 (header)
 msgid "Document codebase objectives"
-msgstr ""
+msgstr "記錄代碼庫目標"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
@@ -781,88 +840,92 @@ msgid ""
 "objectives, like a mission and goal statement, that is understandable by "
 "developers and designers so that they can use or contribute to the codebase."
 msgstr ""
+"[代碼庫](../glossary.md#codebase) 必須包含目標註解，像是使命或目標宣言。開發"
+"人員與設計師需要能夠瞭解這些註解，讓他們能使用或對代碼庫做出貢獻。"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr ""
+msgstr "代碼庫註解應該清楚描述[政策](../glossary."
+"md#policy)目標與代碼庫目標之前的關聯。"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr ""
+msgstr "可選擇為[一般民眾](../glossary.md#general-public)紀錄代碼庫目標。"
 
 #: ./document-objectives.md:block 7 (paragraph)
 msgid "Documenting codebase objectives:"
-msgstr ""
+msgstr "紀錄代碼庫目標："
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid ""
 "provides an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
-msgstr ""
+msgstr "更容易決定是否對本代碼庫或其模組有興趣。"
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid "helps scope your own development."
-msgstr ""
+msgstr "幫助劃定您自己開發專案的範圍。"
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid ""
 "clearly communicates to other stakeholders and contributors the purpose of "
 "the codebase and the modules of which it is composed."
-msgstr ""
+msgstr "將代碼庫以及所包含模組的目的清楚告知其他利害關係人與貢獻者。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid "Guarantee that the codebase achieves the stated objective(s)."
-msgstr ""
+msgstr "保證代碼庫能達成其陳述性目標。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid "Guarantee contributions to the codebase."
-msgstr ""
+msgstr "保證會有人貢獻給代碼庫。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid ""
 "Prevent other codebases from attempting to achieve the same objectives."
-msgstr ""
+msgstr "預防其他代碼庫嘗試達成相同的目標。"
 
 #: ./document-objectives.md:block 12 (unordered list)
 msgid ""
 "Confirm that the codebase documentation includes the codebase objectives, "
 "mission or goal."
-msgstr ""
+msgstr "確認代碼庫註解包含代碼庫目標與使命。"
 
 #: ./document-objectives.md:block 12 (unordered list)
 msgid ""
 "Check for descriptions of connections between policy objectives and codebase"
 " objectives."
-msgstr ""
+msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
 
 #: ./document-objectives.md:block 14 (unordered list)
 msgid ""
 "Add the policy objectives to the codebase documentation, for example in the "
 "`README`."
-msgstr ""
+msgstr "將政策目標加入代碼庫文件中，像是「README」。"
 
 #: ./document-objectives.md:block 14 (unordered list)
 msgid ""
 "Include relevant policies which impact the community, codebase, and "
 "development like value and ethics based policies, for example accessibility "
 "or equal opportunity."
-msgstr ""
+msgstr "加入相關政策，這些政策會影響到社群、代碼庫以及無障礙或平等機會等價值或倫理基"
+"礎的政策的制定。"
 
 #: ./document-objectives.md:block 16 (unordered list)
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr ""
+msgstr "將組織或企業目標加入代碼庫文件中，例如「README」。"
 
 #: ./document-objectives.md:block 18 (unordered list)
 msgid ""
 "Add the technology and design objectives to the codebase documentation, for "
 "example in the `README`."
-msgstr ""
+msgstr "將技術與設計目標加入代碼庫文件中，例如「README」。"
 
 #: ./document-objectives.md:block 20 (unordered list)
 msgid ""
@@ -870,14 +933,16 @@ msgid ""
 "objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
 " by Marek Hajduczenia."
 msgstr ""
+"Marek Hajduczenia的[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
+"RTPGE/public/may12/hajduczenia_01_0512.pdf)。"
 
 #: ./documenting.md:block 1 (header)
 msgid "order: 9"
-msgstr ""
+msgstr "順序：9"
 
 #: ./documenting.md:block 2 (header)
 msgid "Document the code"
-msgstr ""
+msgstr "紀錄程式碼"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -886,200 +951,211 @@ msgid ""
 "language clearly understandable for those that understand the purpose of the"
 " [code](../glossary.md#code)."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)、[政策](../glossary."
+"md#policy)以及原始碼的功能性，都必須清楚描述，讓懂[程式碼](../glossary."
+"md#code)目的的人也能夠瞭解。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain a description of how to "
 "install and run the source code."
-msgstr ""
+msgstr "代碼庫註解必須說明如何安裝與執行原始碼。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr ""
+msgstr "代碼庫註解必須示範關鍵功能。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a high level description "
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
-msgstr ""
+msgstr "代碼庫註解應該包含詳盡的說明，讓[一般民眾](../glossary.md#general-"
+"public)與記者等廣泛的利害關係人都能明白。."
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr ""
+msgstr "代碼庫註解中應該有一部分是用來說明如何安裝與執行單機版的原始碼。若有需要，也"
+"應該包含測試資料集。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr ""
+msgstr "代碼庫註解應該包含所有功能的示範。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr ""
+msgstr "註解應該描述代碼庫的主要元件或模組（例如高階建築圖解），以及之間的關係。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "There SHOULD be [continuous integration](../glossary.md#continuous-"
 "integration) tests for the quality of the documentation."
-msgstr ""
+msgstr "應該要有針對註解品質的[持續整合](../glossary.md#continuous-integration)測試。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇在代碼庫註解中，包含讓使用者會想要立即使用代碼庫的範例。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid "Testing the code by using examples in the documentation is OPTIONAL."
-msgstr ""
+msgstr "可選擇使用註解中的範例來測試程式碼。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "Users can start using and contributing more quickly."
-msgstr ""
+msgstr "使用者可以更快速地使用與貢獻給代碼庫。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid ""
 "You help people discover the codebase, especially people asking 'is there "
 "already code that does something like this'."
-msgstr ""
+msgstr "您幫助他人找到這個代碼庫，特別是那些在尋找有如此功能代碼庫的人們。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "This provides transparency into your organization and processes."
-msgstr ""
+msgstr "讓貴組織與其流程資訊更透明。"
 
 #: ./documenting.md:block 9 (unordered list)
 msgid ""
 "Contribute directly to more reusable, portable code (see [Create reusable "
 "and portable code](./reusable-and-portable-codebases.md))."
 msgstr ""
+"直接讓程式碼變得更可重複使用以及容易攜帶(請參閱[編寫可重複使用且容易攜帶的程"
+"式碼](./reusable-and-portable-codebases.md))。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr ""
+msgstr "確認其他利害關係人、其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解註"
+"解內容。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation describes how to install and run the source "
 "code."
-msgstr ""
+msgstr "確認註解說明如何安裝與執行原始碼。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation includes examples of the key functionality."
-msgstr ""
+msgstr "確認註解包含主要功能的示範。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr ""
+msgstr "與一般民眾以及記者確認他們是否能明白註解當中艱深的說明。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the instructions for how to install and run a standalone version "
 "of the source code result in a running system."
-msgstr ""
+msgstr "檢查單機版原始碼的安裝與執行說明，確認能順利執行。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid "Check that all functionality documented contains an example."
-msgstr ""
+msgstr "檢查文件中列舉的所有功能都包含範例。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the documentation includes a high level architectural diagram or "
 "similar."
-msgstr ""
+msgstr "檢查註解是否包含精細的架構圖。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated from code, and links and images are "
 "tested."
-msgstr ""
+msgstr "確認整合測試有包含註解品質，像是檢查註解是自程式碼生成，並且檢查連結與圖片。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed."
-msgstr ""
+msgstr "定期查看代碼庫的非政策程式碼是否有變動。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
-msgstr ""
+msgstr "針對如何讓非政策註解更清楚易懂提供意見回饋。"
 
 #: ./documenting.md:block 15 (unordered list)
 msgid "Try to use the codebase."
-msgstr ""
+msgstr "嘗試使用代碼庫。"
 
 #: ./documenting.md:block 15 (unordered list)
 msgid ""
 "Make sure you understand both the policy and source code as well as the "
 "documentation."
-msgstr ""
+msgstr "確保您了解政策、原始碼以及註解內容。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-source code in the codebase has"
 " changed."
-msgstr ""
+msgstr "定期查看代碼庫的非原始碼是否有變動。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
-msgstr ""
+msgstr "針對如何讓非原始碼註解更清楚易懂提供意見回饋。"
 
 #: ./documenting.md:block 19 (unordered list)
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr ""
+msgstr "Write the Docs的[註解指南](https://www.writethedocs.org/guide/)。"
 
 #: ./findability.md:block 1 (header)
 msgid "order: 14"
-msgstr ""
+msgstr "順序：14"
 
 #: ./findability.md:block 2 (header)
 msgid "Make the codebase findable"
-msgstr ""
+msgstr "讓民眾可以搜尋到此代碼庫"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST be findable using a search "
 "engine by describing the problem it solves in natural language."
-msgstr ""
+msgstr "民眾在使用搜尋引擎時，如果以自然的語言描述代碼庫能解決的問題時，必須能搜尋到["
+"代碼庫](../glossary.md#codebase)。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "The codebase MUST be findable using a search engine by codebase name."
-msgstr ""
+msgstr "民眾用搜尋引擎搜尋代碼庫名稱時，必須能搜尋到代碼庫。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr ""
+msgstr "維護者應該將代碼庫提交至相關軟體型錄上。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr ""
+msgstr "應該要為代碼庫架設網站，上面用潛在使用者(技術人員、政策專家與管理人員)偏好的"
+"術語描述代碼庫能解決的問題。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD have a unique and persistent identifier where the entry "
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
-msgstr ""
+msgstr "代碼庫應該具備永久唯一識別碼，且內容需要提到主要貢獻者、[儲存庫](../glossary."
+"md#repository)、地點與網站。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
@@ -1087,30 +1163,32 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
+"代碼庫應該包含機器可閱讀的元資料說明，像是[publiccode.yml](https://github."
+"com/publiccodeyml/publiccode.yml)檔案這樣。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇為代碼庫設定專屬網域名稱。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "Regular presentations at conferences by the community are OPTIONAL."
-msgstr ""
+msgstr "可選擇定期在社群舉辦的會議中進行簡報。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
 "Proactiveness is needed; just publishing a codebase and hoping it's found "
 "doesn't work."
-msgstr ""
+msgstr "必須主動出擊，不能只是發布代碼庫然後盼望網民會找到這個代碼庫。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid "A metadata description file increases discoverability."
-msgstr ""
+msgstr "元資料說明檔案會讓代碼庫更容易被發現。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
 "The more findable a codebase is, the more potential new collaborators will "
 "find it."
-msgstr ""
+msgstr "代碼庫越容易被發現，更多的潛在協作者也會發現。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
@@ -1120,113 +1198,120 @@ msgid ""
 "refer, cite, disambiguate and discover the codebase through third party "
 "tools."
 msgstr ""
+"內容豐富且包含永久唯一識別碼的元資料(像是刊載在維基數據或是FSF網站上)，讓代碼"
+"庫成為語意網的一部份。如此一來，他人就能更容易地透過第三方工具參考、引用、解"
+"釋與發現代碼庫。"
 
 #: ./findability.md:block 9 (unordered list)
 msgid "Ensure new collaborators or replicators."
-msgstr ""
+msgstr "帶來新協作者或複製者。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by a plain English problem "
 "description."
-msgstr ""
+msgstr "確認在多個常用的搜尋引擎上，用直白的英文敘述問題，按下搜尋後代碼庫會出現在搜"
+"尋結果的第一頁。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by a technical problem description."
-msgstr ""
+msgstr "確認在多個常用的搜尋引擎上，用技術性文字敘述問題，按下搜尋後代碼庫會出現在搜"
+"尋結果的第一頁。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by the codebase name."
-msgstr ""
+msgstr "確認在多個常用的搜尋引擎上，搜尋代碼庫名字後，代碼庫會出現在搜尋結果的第一頁"
+"。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid "Check for the codebase listing in relevant software catalogs."
-msgstr ""
+msgstr "檢查代碼庫有刊登在相關軟體型錄上。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check for a codebase website which describes the problem the codebase "
 "solves."
-msgstr ""
+msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for mention of the major "
 "contributors."
-msgstr ""
+msgstr "檢查永久唯一識別碼有提到主要貢獻者。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the repository location."
-msgstr ""
+msgstr "檢查永久唯一識別碼是否包含儲存庫地點。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the codebase website."
-msgstr ""
+msgstr "檢查永久唯一識別碼是否有列出代碼庫網站。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid "Check for a machine-readable metadata description file."
-msgstr ""
+msgstr "檢查元資料說明檔案具有機器可讀的格式。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
 "Contribute a description of the policy area or problem this codebase acts on"
 " or operates."
-msgstr ""
+msgstr "描述可應用此代碼庫的政策或問題。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
 "Test your problem description with peers outside of your context who aren't "
 "familiar with the codebase."
-msgstr ""
+msgstr "請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
 "Present on how the codebase implements the [policy](../glossary.md#policy) "
 "at relevent conferences."
-msgstr ""
+msgstr "在相關會議上介紹代碼庫如何執行[政策](../glossary.md#policy)。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid ""
 "Budget for content design and Search Engine Optimization skills in the team."
-msgstr ""
+msgstr "為團隊編列內容設計與搜尋引擎優化技能的預算。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid "Ensure people involved in the project present at relevant conferences."
-msgstr ""
+msgstr "確保專案人員在相關會議上介紹本專案。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid ""
 "Search trademark databases to avoid confusion or infringement before "
 "deciding the name."
-msgstr ""
+msgstr "決定名稱之前，先搜尋商標資料庫，避免名稱造成混淆或侵權的問題。"
 
 #: ./findability.md:block 17 (unordered list)
 msgid "Search engine optimization."
-msgstr ""
+msgstr "搜尋引擎優化。"
 
 #: ./findability.md:block 17 (unordered list)
 msgid "Suggest conferences to present at and present at them."
-msgstr ""
+msgstr "建議適合用來簡報的會議並且在這些會議中介紹代碼庫。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
 "[Introduction to "
 "Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
 "Wikidata community."
-msgstr ""
+msgstr "維基數據社群的[維基數據簡介](https://www.wikidata.org/wiki/"
+"Wikidata:Introduction)。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
 "[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
 "by the Free Softare Foundation."
-msgstr ""
+msgstr "自由軟體基金會的[FSF軟體型錄清單](https://directory.fsf.org/wiki/Main_Page)。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
@@ -1237,130 +1322,142 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
+"GO FAIR國際支援與合作辦公室的 "
+"[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-principles/"
+")，提出詳盡的清單，解釋哪些屬性會讓(元)資料更容易讓機器採取行動(也因此更容易"
+"被找到)。當中部分屬性可直接套用在代碼庫上，無法直接套用的，我們也需要研究代碼"
+"庫中與其對照的屬性。"
 
 #: ./index.md:block 1 (header)
 msgid "Criteria"
-msgstr ""
+msgstr "標準"
 
 #: ./index.md:block 3 (paragraph)
 msgid "{% assign sorted = site.pages | sort:\"order\" %}"
-msgstr ""
+msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
 
 #: ./index.md:block 4 (paragraph)
+#, fuzzy
 msgid ""
 "{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
 "!= \"index.md\" %}{% if page.title %}"
 msgstr ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 5 (ordered list)
+#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 
 #: ./make-contributing-easy.md:block 1 (header)
 msgid "order: 5"
-msgstr ""
+msgstr "順序：5"
 
 #: ./make-contributing-easy.md:block 2 (header)
 msgid "Make contributing easy"
-msgstr ""
+msgstr "讓對代碼庫貢獻代碼變得更容易"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
 "that accepts suggestions from anyone."
-msgstr ""
+msgstr "[代碼庫](../glossary.md#codebase) 必須具備接受任何人建議的公共議題追蹤器。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include instructions for how to privately report security "
 "issues for responsible disclosure."
-msgstr ""
+msgstr "代碼庫必須說明如何私下回報安全問題， 達到負責任的揭露。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr ""
+msgstr "文件必須與公共議題追蹤器以及已提交的代碼庫變動連結，例如「README」檔案。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr ""
+msgstr "代碼庫必須有與使用者以及開發人員的溝通管道，像是電子郵件清單。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The documentation SHOULD include instructions for how to report potentially "
 "security sensitive issues on a closed channel."
-msgstr ""
+msgstr "文件應該說明如何透過封閉的管道通報潛在的安全與敏感性問題。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid ""
 "Enables users to fix problems and add features to the shared codebase "
 "leading to better, more reliable and feature rich software."
-msgstr ""
+msgstr "讓使用者能夠修復問題以及新增共享代碼庫的功能，讓軟體更好、更可靠且功能更豐富"
+"。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid "Allows collaborative uptake of shared digital infrastructure."
-msgstr ""
+msgstr "允許共同使用共享數位基礎設施。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid "Helps users decide to use one codebase over another."
-msgstr ""
+msgstr "幫助使用者在代碼庫間做出選擇。"
 
 #: ./make-contributing-easy.md:block 9 (unordered list)
 msgid "Guarantee others will reuse the codebase."
-msgstr ""
+msgstr "保證其他人會重複使用代碼庫。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid "Confirm that there is a public issue tracker."
-msgstr ""
+msgstr "確認有公共議題追蹤器。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that there are instructions for privately reporting security issues."
-msgstr ""
+msgstr "確認有說明如何私下通報安全問題。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase contains links to the public issue tracker and "
 "submitted codebase changes."
-msgstr ""
+msgstr "確認代碼庫有公共議題追蹤器以及已提交的代碼庫變動的連結。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that it is possible to participate in a discussion with other users "
 "and developers about the software using channels described in the codebase."
-msgstr ""
+msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員討論。"
 
 #: ./make-contributing-easy.md:block 13 (unordered list)
 msgid ""
 "Track [policy](../glossary.md#policy) issues in the codebase, so that a "
 "relevant external policy expert can volunteer help."
-msgstr ""
+msgstr "追蹤代碼庫中的[政策](../glossary."
+"md#policy)問題，讓相關外部政策專家也能自願協助。"
 
 #: ./make-contributing-easy.md:block 15 (unordered list)
 msgid ""
 "Track management issues in the codebase, so that external managers with "
 "relevant experience can volunteer help."
-msgstr ""
+msgstr "追蹤代碼庫中的管理問題，讓相關外部政策專家也能自願協助。"
 
 #: ./make-contributing-easy.md:block 15 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr ""
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師來持續貢獻代碼給代碼庫。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid "Respond promptly to requests."
-msgstr ""
+msgstr "迅速回應要求。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid ""
 "Keep your management informed of the time and resources you require to "
 "support other contributors."
-msgstr ""
+msgstr "持續告知管階層您需要用來支援其他貢獻者的時間與資源。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
@@ -1368,68 +1465,75 @@ msgid ""
 "project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
 "to-your-open-source-project-1ebf) by Joel Hans."
 msgstr ""
+"Joel Hans的[如何鼓勵他人貢獻一流的代碼給您的開源專案](https://dev.to/"
+"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
+"project-1ebf)。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
 "[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
 "benefits-of-coding-in-the-open/) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[公開編寫程式碼的好處](https://gds.blog.gov.uk/2017/09/"
+"04/the-benefits-of-coding-in-the-open/)。"
 
 #: ./open-licenses.md:block 1 (header)
 msgid "order: 13"
-msgstr ""
+msgstr "順序：13"
 
 #: ./open-licenses.md:block 2 (header)
 msgid "Publish with an open license"
-msgstr ""
+msgstr "取得公開授權並公布程式碼"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "All [code](../glossary.md#code) and documentation MUST be licensed such that"
 " it may be freely reusable, changeable and redistributable."
-msgstr ""
+msgstr "必須取得所有[程式碼](../glossary."
+"md#code)與文件的授權，讓所有人可以免費重複利用、變更與散布。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Software source code MUST be licensed under an [OSI-approved or FSF "
 "Free/Libre license](https://spdx.org/licenses/)."
-msgstr ""
+msgstr "軟體原始碼必須取得[開放原始碼促進會認證或FSF Free/Libre授權](https://spdx."
+"org/licenses/)。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid "All code MUST be published with a license file."
-msgstr ""
+msgstr "所有程式碼都必須放在授權檔案中發布。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the [codebase](../glossary.md#codebase)."
-msgstr ""
+msgstr "不得要求貢獻者將其貢獻代碼的著作權轉移給[代碼庫](../glossary.md#codebase)。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr ""
+msgstr "代碼庫中所有原始碼檔案都應該包含機器可判讀的著作權與授權聲明。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Having multiple licenses for different types of code and documentation is "
 "OPTIONAL."
-msgstr ""
+msgstr "可選擇為不同類型的程式碼與文件取得多個授權。"
 
 #: ./open-licenses.md:block 7 (unordered list)
 msgid ""
 "Makes it possible for anyone to see the code and know that they can and how "
 "they can reuse it."
-msgstr ""
+msgstr "讓任何看到程式碼的人，都能知道可以與如何重複利用這些程式碼。"
 
 #: ./open-licenses.md:block 9 (unordered list)
 msgid "Prevent use of the code by any specific actors."
-msgstr ""
+msgstr "預防任何特定行為人使用程式碼。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid "Confirm that the codebase is clearly licensed."
-msgstr ""
+msgstr "確認代碼庫確實有取得授權。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
@@ -1438,41 +1542,47 @@ msgid ""
 "documentation [conforms to the Open "
 "Definition](https://opendefinition.org/licenses/)."
 msgstr ""
+"確認原始碼授權有在[開放原始碼促進會認證或FSF Free/Libre授權清單](https://spdx"
+".org/licenses/)，以及文件授權[符合開放定義](https://opendefinition.org/"
+"licenses/)。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid "Confirm that the licenses used in the codebase are included as files."
-msgstr ""
+msgstr "確認代碼庫有包含其使用授權的檔案。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
 "Confirm that contribution guidelines and "
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
-msgstr ""
+msgstr "確認貢獻指南以及[儲存庫](../glossary."
+"md#repository)的設定不要求貢獻者轉移著作權。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
 "Check for machine-readable license checking in the codebase [continuous "
 "integration](../glossary.md#continuous-integration) tests."
-msgstr ""
+msgstr "在代碼庫[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查機器可判讀授權的功能。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
 "Develop [policy](../glossary.md#policy) that requires code to be [open "
 "source](../glossary.md#open-source)."
-msgstr ""
+msgstr "制定要求程式碼為 [開源](../glossary.md#open-source)的[政策](../glossary."
+"md#policy)。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
 "Develop policy that disincentivizes non-open source code and technology in "
 "procurement."
-msgstr ""
+msgstr "制定政策，減少採購非開源的程式碼與科技。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
 "Only work with open source vendors that deliver their code by publishing it "
 "under an open source license."
-msgstr ""
+msgstr "只與透過開源授權發布其程式碼的開源供應商合作。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
@@ -1482,22 +1592,25 @@ msgid ""
 "NOT freely reusable, changeable and redistributable and don't fulfill these "
 "requirements."
 msgstr ""
+"請注意：雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件上"
+"，具有非商業性或禁止改作的授權代表不得免費重複使用、變更與散布，因此不符合規"
+"定。"
 
 #: ./open-licenses.md:block 17 (unordered list)
 msgid "Add a new `license` file to every new codebase created."
-msgstr ""
+msgstr "建立新的代碼庫時，都要加入新的「授權」檔案。"
 
 #: ./open-licenses.md:block 17 (unordered list)
 msgid ""
 "Add a copyright notice and a license header to every new source code file "
 "created."
-msgstr ""
+msgstr "建立新的原始碼檔案時，都要加入著作權與授權聲明。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
 "[Open source definition](https://opensource.org/osd) by the Open Source "
 "Initiative, all open source licenses meet this definition."
-msgstr ""
+msgstr "所有開源授權都符合開放原始碼促進會的[開源定義](https://opensource.org/osd)。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
@@ -1505,6 +1618,8 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
+"紐西蘭CC Aotearoa的[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
@@ -1512,20 +1627,23 @@ msgid ""
 "Software Foundation Europe for unambiguous, human-readable and machine-"
 "readable copyright and licensing information."
 msgstr ""
+"歐洲自由軟體基金會的[REUSE倡議規範](https://reuse.software/spec/"
+")，是規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
 "[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
 " standardized, machine-readable abbreviations for most licenses."
-msgstr ""
+msgstr "Linux基金會的[SPDX授權清單](https://spdx.org/licenses/"
+")，提供多數授權的標準化且機器可讀的縮寫。"
 
 #: ./open-standards.md:block 1 (header)
 msgid "order: 11"
-msgstr ""
+msgstr "順序：11"
 
 #: ./open-standards.md:block 2 (header)
 msgid "Use open standards"
-msgstr ""
+msgstr "使用開源標準"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
@@ -1534,97 +1652,102 @@ msgid ""
 "standard](../glossary.md#open-standard) that meets the [Open Source "
 "Initiative Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)要能進行資料交換，就必須使用符合 "
+"[開放原始碼促進會開源標準規定](https://opensource.org/"
+"osr)的[開源標準](../glossary.md#open-standard)。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any non-open standards used MUST be recorded clearly as such in the "
 "documentation."
-msgstr ""
+msgstr "若使用非開源標準，就必須在文件中清楚標示。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr ""
+msgstr "代碼庫使用的任何標準必須在文件中清楚標示，並且附上該標準的連結。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr ""
+msgstr "代碼庫使用的非開源標準不得妨礙代碼庫的協作與重複使用。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "If no existing open standard is available, effort SHOULD be put into "
 "developing one."
-msgstr ""
+msgstr "如果沒有開源標準可用，則應該開發新標準。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Standards that are machine testable SHOULD be preferred over those that are "
 "not."
-msgstr ""
+msgstr "應該優先選擇可用機器測試的標準。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid "Creates interoperability between systems."
-msgstr ""
+msgstr "讓系統可以互通。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid "Reduces possible vendor lock-in."
-msgstr ""
+msgstr "降低可能的廠商陷阱。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid ""
 "Guarantees access to the knowledge required to reuse and contribute to the "
 "codebase."
-msgstr ""
+msgstr "保證讓每個人都能獲得相關知識，學會重複利用以及貢獻代碼給代碼庫。"
 
 #: ./open-standards.md:block 9 (unordered list)
 msgid "Make it understandable how to use the software."
-msgstr ""
+msgstr "說明如何使用軟體。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid "Confirm that data exchange follows an OSI approved open standard."
-msgstr ""
+msgstr "確認資料交換遵守OSI認證的開源標準。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid ""
 "Confirm that any non-open standards used are clearly documented as such."
-msgstr ""
+msgstr "確認若有使用非開源標準，都有清楚標示。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr ""
+msgstr "確認文件包含代碼庫使用的標準清單，以及所有標準的連結。若是沒有使用標準，也須"
+"清楚標示。"
 
 #: ./open-standards.md:block 13 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
-msgstr ""
+msgstr "盡可能規定要求使用開源標準。"
 
 #: ./open-standards.md:block 13 (unordered list)
 msgid "Prohibit procurement of technology that does not use open standards."
-msgstr ""
+msgstr "禁止採購不支援開源標準的科技。"
 
 #: ./open-standards.md:block 15 (unordered list)
 msgid ""
 "Consider including open standard compliance assessment in "
 "[code](../glossary.md#code) reviews."
-msgstr ""
+msgstr "考慮在[程式碼](../glossary.md#code)審核中加入開源標準遵循評估。"
 
 #: ./open-standards.md:block 17 (unordered list)
 msgid ""
 "Add [continuous integration](../glossary.md#continuous-integration) tests "
 "for compliance with the standards."
-msgstr ""
+msgstr "在標準遵循方面，加入[持續整合](../glossary.md#continuous-integration)測試。"
 
 #: ./open-standards.md:block 17 (unordered list)
 msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr ""
+msgstr "檢查提交說明與其他[儲存庫](../glossary.md#repository)資源是否有提到開源標準，"
+"並且 再次確認有列出標準的內容。"
 
 #: ./open-standards.md:block 19 (unordered list)
 msgid ""
@@ -1632,100 +1755,105 @@ msgid ""
 "standards-principles/open-standards-principles), "
 "[policy](../glossary.md#policy) paper of the UK Cabinet Office."
 msgstr ""
+"英國內閣辦公室的[開源標準原則](https://www.gov.uk/government/publications/"
+"open-standards-principles/open-standards-principles)與[政策](../glossary."
+"md#policy)論文。"
 
 #: ./open-to-contributions.md:block 1 (header)
 msgid "order: 4"
-msgstr ""
+msgstr "順序：4"
 
 #: ./open-to-contributions.md:block 2 (header)
 msgid "Welcome contributors"
-msgstr ""
+msgstr "歡迎貢獻者"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
 "suggestions for changes to the codebase."
-msgstr ""
+msgstr "[代碼庫](../glossary.md#codebase)必須允許任何人針對代碼庫提出變更建議。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr ""
+msgstr "代碼庫必須包含貢獻指引，像是在「CONTRIBUTING」檔案中說明歡迎貢獻者貢獻的內容"
+"類型，以及貢獻者可如何參與代碼庫。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr ""
+msgstr "代碼庫必須說明代碼庫、貢獻內容與社群的治理方式，可利用「GOVERNANCE」檔案來說"
+"明。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr ""
+msgstr "代碼庫應該宣傳參與其開發與維護且承諾持續參與其營運的組織。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr ""
+msgstr "代碼庫應該要有公開的路徑圖。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid "The codebase SHOULD publish codebase activity statistics."
-msgstr ""
+msgstr "代碼庫應該公布代碼庫的活動統計數據。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇制定代碼庫貢獻者的行為準則。"
 
 #: ./open-to-contributions.md:block 7 (unordered list)
 msgid ""
 "Helps newcomers understand and trust the codebase community's leadership."
-msgstr ""
+msgstr "幫助新來者瞭解並且信任代碼庫社群的領導。"
 
 #: ./open-to-contributions.md:block 7 (unordered list)
 msgid ""
 "Prevents the community that works on a codebase splitting because there is "
 "no way to influence its goals and progress, resulting in diverging "
 "communities."
-msgstr ""
+msgstr "避免因為無法影響代碼庫的目標與進展，造成代碼庫的社群分裂成分歧的社群。"
 
 #: ./open-to-contributions.md:block 9 (unordered list)
 msgid "Guarantee others will join the community."
-msgstr ""
+msgstr "保證別人會加入社群。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid ""
 "Confirm that it is possible to submit suggestions for changes to the "
 "codebase."
-msgstr ""
+msgstr "確認可以提交變動建議給代碼庫。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Confirm there are contribution guidelines."
-msgstr ""
+msgstr "確認代碼庫有貢獻指引。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr ""
+msgstr "確認代碼庫有清楚解釋其治理方式，包括如何影響代碼庫的治理。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a list of involved organizations."
-msgstr ""
+msgstr "檢查是否有參與組織名單。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a roadmap."
-msgstr ""
+msgstr "檢查是否有路徑圖。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for published activity statistics."
-msgstr ""
+msgstr "檢查是否有公布活動統計數據。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a code of conduct."
-msgstr ""
+msgstr "檢查是否有行為準則。"
 
 #: ./open-to-contributions.md:block 13 (unordered list)
 msgid ""
@@ -1733,42 +1861,47 @@ msgid ""
 "[policy](../glossary.md#policy) experts, non-governmental organizations and "
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
+"為代碼庫新增其他資源清單，上面資源都是能幫助[政策](../glossary."
+"md#policy)專家、非政府組織與學者更瞭解或學會重複利用您的政策。"
 
 #: ./open-to-contributions.md:block 13 (unordered list)
 msgid ""
 "Consider adding contact details so that other policy makers considering "
 "collaboration can ask you for advice."
-msgstr ""
+msgstr "考慮新增聯絡資訊，讓其他考慮合作的決策者能徵詢您的意見。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Make sure that the documentation of the governance includes the current "
 "process for how to make changes to the governance."
-msgstr ""
+msgstr "確保治理文件內容包含如何改變治理方式的現有流程。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "If the community has some consensus about how the governance should change, "
 "then include those ideas stated as ambitions in the documentation."
-msgstr ""
+msgstr "如果社群對於治理方式應該如何改變有共識，應該將此構想列在文件中並且標示為「願"
+"景」。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr ""
+msgstr "確認文件解釋每個組織參與本代碼庫的方式、提供代碼庫哪些資源以及參與的時間長度"
+"。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to stay "
 "part of the community for as long as possible."
-msgstr ""
+msgstr "支持經驗豐富的決策者、開發人員與設計師參與代碼庫社群，且時間越長越好。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr ""
+msgstr "開源軟體指南的[打造熱情友好的社群](https://opensource.guide/"
+"building-community/)。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1776,6 +1909,9 @@ msgid ""
 "open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
 "source-project/) by Mike McQuaid."
 msgstr ""
+"Mike McQuaid的[開源貢獻者漏斗](https://mikemcquaid.com/2018/08/14/the-open-so"
+"urce-contributor-funnel-why-people-dont-contribute-to-your-open-source-projec"
+"t/)。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1783,202 +1919,207 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
+"開源軟體指南的[以領導與治理](https://opensource.guide/"
+"leadership-and-governance/)幫助[開源](../glossary.md#open-"
+"source)社群成長的專案。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
 "[Building online communities](http://hintjens.com/blog:117) by Pieter "
 "Hintjens (long read!)."
-msgstr ""
+msgstr "Pieter Hintjens的[打造網路社群](http://hintjens.com/blog:117)(內容很長！)。"
 
 #: ./require-review.md:block 1 (header)
 msgid "order: 7"
-msgstr ""
+msgstr "順序：7"
 
 #: ./require-review.md:block 2 (header)
 msgid "Require review of contributions"
-msgstr ""
+msgstr "要求審查貢獻內容"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
-msgstr ""
+msgstr "所有被接受或是提交給完成版[代碼庫](../glossary."
+"md#codebase)的貢獻內容，都必須由另一位貢獻者審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Reviews MUST include source, [policy](../glossary.md#policy), tests and "
 "documentation."
-msgstr ""
+msgstr "審查必須包含來源、[政策](../glossary.md#policy)、測試與文件。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Reviewers MUST provide feedback on all decisions to not accept a "
 "contribution."
-msgstr ""
+msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Contributions SHOULD conform to the standards, architecture and decisions "
 "set out in the codebase in order to pass review."
-msgstr ""
+msgstr "貢獻內容應該遵循代碼庫的標準、架構與決策，才能通過審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Reviews SHOULD include running both the [code](../glossary.md#code) and the "
 "tests of the codebase."
-msgstr ""
+msgstr "審查方式應該包括執行[程式碼](../glossary.md#code)與代碼庫測試。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Contributions SHOULD be reviewed by someone in a different context than the "
 "contributor."
-msgstr ""
+msgstr "貢獻內容應該由與貢獻者不同領域的人來審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr ""
+msgstr "版本管控系統在完成版的代碼庫中，不應該接受未經審查的貢獻內容。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
-msgstr ""
+msgstr "審查應在兩個工作天內進行。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid "Performing reviews by multiple reviewers is OPTIONAL."
-msgstr ""
+msgstr "可選擇由多位審查人員進行審查。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Increases codebase quality."
-msgstr ""
+msgstr "提升代碼庫品質。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Reduces security risks as well as operational risks."
-msgstr ""
+msgstr "降低安全風險與營運風險。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Creates a culture of making every contribution great."
-msgstr ""
+msgstr "打造讓每則貢獻內容豐富的文化。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Catches the most obvious mistakes that could happen."
-msgstr ""
+msgstr "找出可能發生的明顯問題。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Gives contributors the security that their contributions are only accepted "
 "if they really add value."
-msgstr ""
+msgstr "讓貢獻者知道，只有能為代碼庫帶來價值的貢獻內容才會被接受。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Assures contributors of a guaranteed time for feedback or collaborative "
 "improvement."
-msgstr ""
+msgstr "向貢獻者保證會有提供意見回饋或是改善協作的時間。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Prompt reviews increase both rate of delivery and contributor engagement."
-msgstr ""
+msgstr "迅速的審查能提高貢獻者貢獻內容的頻率以及參與。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Guarantee the right solution to a problem."
-msgstr ""
+msgstr "保證能找到解決問題的方法。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Mean that reviewers are liable."
-msgstr ""
+msgstr "代表審查人員必須負責。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Absolve a contributor from writing documentation and tests."
-msgstr ""
+msgstr "貢獻者在編寫文件與測試上免責。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Provide you with the right reviewers."
-msgstr ""
+msgstr "提供您合適的審查人員。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Confirm that every commit in the history has been reviewed by a different "
 "contributor."
-msgstr ""
+msgstr "確認所有不同版本都由不同貢獻者審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
-msgstr ""
+msgstr "確認審查包含來源、政策、測試與文件。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that rejected contributions were appropriately explained."
-msgstr ""
+msgstr "針對未被採用的貢獻內容，確認有詳盡解釋原因。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check if reviews cover conformance to standards, architecture and codebase "
 "guidelines."
-msgstr ""
+msgstr "檢查審查包含貢獻內容是否遵循標準、架構與代碼庫指引。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check with reviewers if they run the code and tests during review."
-msgstr ""
+msgstr "檢查審查人員在審查時是否有執行程式碼與測試。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check with reviewers if commits have been reviewed by a different "
 "contributor in a different context."
-msgstr ""
+msgstr "與審查人員確認代碼庫的不同版本是否由不同領域的另一位貢獻者來審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check for use of branch protection in the [version "
 "control](../glossary.md#version-control) system."
-msgstr ""
+msgstr "檢查[版本管控](../glossary.md#version-control)系統是否有採用分支保護。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check the times between contribution submission and review."
-msgstr ""
+msgstr "檢查貢獻代碼提交與審查的時間。"
 
 #: ./require-review.md:block 13 (unordered list)
 msgid ""
 "Institute a 'four eyes' policy where everything, not just code, is reviewed."
-msgstr ""
+msgstr "審查程式碼與其他一切事物時，都要遵守「四眼原則」。"
 
 #: ./require-review.md:block 13 (unordered list)
 msgid ""
 "Use a version control system or methodology that enables review and "
 "feedback."
-msgstr ""
+msgstr "使用具有審查與意見回饋功能的版本管控系統或方法。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make delivering great code a shared objective."
-msgstr ""
+msgstr "讓所有人以寫出好的程式碼為目標。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid ""
 "Make sure writing and reviewing contributions to source, policy, "
 "documentation and tests are considered equally valuable."
-msgstr ""
+msgstr "確保同樣重視撰寫與審查貢獻內容，與編寫原始碼、政策、文件與測試。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid ""
 "Create a culture where all contributions are welcome and everyone is "
 "empowered to review them."
-msgstr ""
+msgstr "建立一個歡迎所有貢獻且每個人都能審查貢獻內容的文化。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr ""
+msgstr "確保貢獻者在貢獻內容給代碼庫時，有獲得適當的注意。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
 "Ask other contributors on the codebase to review your work, in your "
 "organization or outside of it."
-msgstr ""
+msgstr "請代碼庫的其他貢獻者審查您在貴組織內外的工作成果。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
 "Try to respond to others' requests for code review promptly, initially "
 "providing feedback about the concept of the change."
-msgstr ""
+msgstr "別人要求您審查他們的程式碼時，請盡快回覆，並且提出程式碼需要修正處背後的概念"
+"。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -1986,6 +2127,8 @@ msgid ""
 "way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
 " Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[英國政府數位服務團程式碼審查方式](https://gds-way."
+"cloudapps.digital/manuals/code-review-guidelines.html#content)。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -1995,12 +2138,19 @@ msgid ""
 "protected-branches) and "
 "[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
 msgstr ""
+"[GitHub](https://docs.github.com/en/repositories/"
+"configuring-branches-and-merges-in-your-repository/"
+"defining-the-mergeability-of-pull-requests/about-protected-"
+"branches)與[GitLab](https://about.gitlab.com/2014/11/26/"
+"keeping-your-code-protected/)的分支保護。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
 "[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
 "gentle-art-of-patch-review/) by Sage Sharp."
 msgstr ""
+"Sage Sharp的[Patch審查的藝術](https://sage.thesharps.us/2014/09/01/"
+"the-gentle-art-of-patch-review/)。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -2008,180 +2158,190 @@ msgid ""
 "Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
 "mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
 msgstr ""
+"Mozilla的[評估參與程度](https://docs.google.com/presentation/d/"
+"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)。"
 
 #: ./reusable-and-portable-codebases.md:block 1 (header)
 msgid "order: 3"
-msgstr ""
+msgstr "順序：3"
 
 #: ./reusable-and-portable-codebases.md:block 2 (header)
 msgid "Create reusable and portable code"
-msgstr ""
+msgstr "編寫可重複使用且可攜式的程式碼"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
 "[different contexts](../glossary.md#different-contexts)."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)在編寫時必須以能在[不同情境](../glossary.md"
+"#different-contexts)使用為前提。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed [code](../glossary.md#code) or services for execution "
 "and understanding."
-msgstr ""
+msgstr "代碼庫的執行與理解必須不仰賴任何秘密、未公開、專屬或非開源授權的[程式碼](../g"
+"lossary.md#code)。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be in use by multiple parties."
-msgstr ""
+msgstr "代碼庫應該由多方使用。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
-msgstr ""
+msgstr "路徑圖應該顯示各方的需求。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Configuration SHOULD be used to make code adapt to context specific needs."
-msgstr ""
+msgstr "應該使用配置針對各情境特定需求來調整程式碼。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be localizable."
-msgstr ""
+msgstr "代碼庫應該能夠本地化。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Code and its documentation SHOULD NOT contain situation-specific "
 "information."
-msgstr ""
+msgstr "程式碼與文件不應該包含僅適用於特定情況的資訊。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr ""
+msgstr "代碼庫模組的編寫方式應該讓其能在其他情境的代碼庫中重複利用。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Enables other policy makers, developers and designers to reuse what you've "
 "developed, to test it, to improve it and contribute those improvements back "
 "leading to better quality, cheaper maintenance and higher reliability."
-msgstr ""
+msgstr "讓其他決策者、開發人員與設計師能夠重複利用您編寫的程式碼，並且測試與改善該程"
+"式碼，然後提供改善意見，讓程式碼品質更高、維護成本下滑且更可靠。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Makes the code easier for new people to understand (as it's more general)."
-msgstr ""
+msgstr "讓新來者更容易瞭解此程式碼(因為更淺顯易懂)。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Makes it easier to control the mission, vision and scope of the codebase "
 "because the codebase is thoughtfully and purposefully designed for "
 "reusability."
-msgstr ""
+msgstr "隨著代碼庫是以重複利用為前提來編寫，因此控制其使命、願景與範圍也更容易。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Codebases used by multiple parties are more likely to benefit from a self-"
 "sustaining community."
-msgstr ""
+msgstr "多方使用的代碼庫更可以從自我維持的社群獲益。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Any contributor is able to test and contribute without relying on the "
 "situation-specific infrastructure of any other contributor or deployment."
-msgstr ""
+msgstr "任何貢獻者都能夠測試與貢獻給代碼庫，且不需要仰賴其他貢獻者或部署底下特定情況"
+"專用的基礎架構。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Composing a codebase from well documented modules improves reusability and "
 "maintainability."
-msgstr ""
+msgstr "使用註解清楚的模組來建立代碼庫，代碼庫更能被重複使用，也更容易維護。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "A module is easier to reuse in another context if its purpose is clearly "
 "documented."
-msgstr ""
+msgstr "清楚標示其目的的模組，更容易在另一個情境中重複利用。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Get others to reuse the codebase."
-msgstr ""
+msgstr "讓他人重複利用代碼庫。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Build a community."
-msgstr ""
+msgstr "建立社群。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid ""
 "Shift responsibility for documentation, support, bug-fixing, etc. to another"
 " party."
-msgstr ""
+msgstr "將註解、支援與除錯等責任轉移至他人。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Guarantee that modules are generic enough to be reused in any context."
-msgstr ""
+msgstr "保證模組在任何情境下都可通用。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "reuse the codebase and what that would entail."
-msgstr ""
+msgstr "尋找另一組織角色與您相似的人，與其確認他們是否能重複利用代碼庫，又是透過什麼"
+"樣的方式。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed code or services."
-msgstr ""
+msgstr "確認代碼庫不需要使用專屬或非開源授權的程式碼貨服務，就能順利執行。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase is in use by multiple parties or in multiple "
 "contexts."
-msgstr ""
+msgstr "檢查是否有多方使用代碼庫，或是在多種情境下使用代碼庫。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr ""
+msgstr "確認代碼庫檔案與提交歷史紀錄沒有包含僅適用特定情況的數據。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid ""
 "Document your [policy](../glossary.md#policy) with enough clarity and detail"
 " that it can be understood outside of its original context."
-msgstr ""
+msgstr "為您的[政策](../glossary."
+"md#policy)加上清楚明確的註解，讓他人在不同情境下也能理解。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr ""
+msgstr "確保代碼庫將貴組織列為已知用戶。"
 
 #: ./reusable-and-portable-codebases.md:block 15 (unordered list)
 msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr ""
+msgstr "確認利害關係人與企業業主瞭解代碼庫就是以重複利用為目標，因為這能減少程式碼負"
+"債，並且讓代碼庫能永續發展。"
 
 #: ./reusable-and-portable-codebases.md:block 17 (paragraph)
 msgid "Source should be designed:"
-msgstr ""
+msgstr "原始碼的設計："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr ""
+msgstr "讓其他使用者與組織可重複利用，不受地點影響、"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "to solve a general problem instead of a specific one,"
-msgstr ""
+msgstr "解決通用問題，而非特定問題、"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "in logically meaningful and isolated modules,"
-msgstr ""
+msgstr "採用邏輯上具有意義且獨立的模組、"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid ""
 "so that someone in a similar organization facing a similar problem would be "
 "able to use (parts of) the solution."
-msgstr ""
+msgstr "讓在類似相同組織且面對類似問題的人，能夠使用同樣的解決方案(或當中的一部份)。"
 
 #: ./reusable-and-portable-codebases.md:block 19 (paragraph)
 msgid ""
@@ -2190,13 +2350,16 @@ msgid ""
 " using proprietary components, ensure that collaborators can develop, use, "
 "test, and deploy without them."
 msgstr ""
+"確保代碼庫註解說明建置當下時間與執行時期相依性。若您的情境需要您部署至專屬平"
+"台或使用專屬元件，確保協作者可以在不用這兩者的情況下開發、使用、測試與部署。"
 
 #: ./reusable-and-portable-codebases.md:block 20 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr ""
+msgstr "在每個版本上，審查人員確認內容不會包含專屬特定情況的資料，像是主機名稱、個人"
+"與組織資料或是token與密碼。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2204,6 +2367,8 @@ msgid ""
 "manual/technology/making-source-code-open-and-reusable) by the UK Government"
 " Digital Service."
 msgstr ""
+"英國政府數位服務團的[開源與可重複使用的原始碼](https://www.gov.uk/"
+"service-manual/technology/making-source-code-open-and-reusable)。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2211,6 +2376,8 @@ msgid ""
 "OpenAPI Initiative defines a standard, programming language-agnostic "
 "interface description for human and machine-readable HTTP APIs."
 msgstr ""
+"OpenAPI Initiative組織的[OpenAPI規範](https://spec.openapis.org/oas/latest."
+"html)為人機可讀的HTTP API定義標準、不受程式語言種類限制的介面描述。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2218,6 +2385,8 @@ msgid ""
 "Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
 " the World Wide Web Consortium."
 msgstr ""
+"全球資訊網協會的[本土化 vs. 國際化](https://www.w3.org/International/"
+"questions/qa-i18n)。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2225,20 +2394,24 @@ msgid ""
 "CSS](https://www.w3.org/International/techniques/authoring-html) by the "
 "World Wide Web Consortium."
 msgstr ""
+"全球資訊網協會的[國際化技巧：編寫HTML與CSS](https://www.w3.org/International/"
+"techniques/authoring-html)。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
 "[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
 "Operating System."
 msgstr ""
+"GNU作業系統的[GNU gettext](https://www.gnu.org/software/gettext/gettext."
+"html)。"
 
 #: ./style.md:block 1 (header)
 msgid "order: 15"
-msgstr ""
+msgstr "順序：15"
 
 #: ./style.md:block 2 (header)
 msgid "Use a coherent style"
-msgstr ""
+msgstr "風格前後一致"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
@@ -2246,48 +2419,50 @@ msgid ""
 "the [codebase](../glossary.md#codebase) community's own or an existing one "
 "that is advertised in or part of the codebase."
 msgstr ""
+"貢獻代碼必須遵守程式碼編寫或寫作風格指南，可以是來自[代碼庫](../glossary."
+"md#codebase)社群或是代碼庫中使用的現有風格。"
 
 #: ./style.md:block 5 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
-msgstr ""
+msgstr "貢獻代碼應該通過自動化的風格測試。"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD include inline comments and documentation for non-"
 "trivial sections."
-msgstr ""
+msgstr "代碼庫當中，複雜的程式碼應該包含註解。"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
 "Including sections on [understandable English](understandable-english-"
 "first.md) in the style guide is OPTIONAL."
-msgstr ""
+msgstr "風格指南可選擇加入[可理解英文](understandable-english-first.md)章節。"
 
 #: ./style.md:block 7 (unordered list)
 msgid ""
 "Enables contributors in different environments to work together on a unified"
 " product."
-msgstr ""
+msgstr "讓不同環境的貢獻者們可在同一個產品上合作。"
 
 #: ./style.md:block 7 (unordered list)
 msgid ""
 "Unifying vocabularies reduces friction in communication between "
 "contributors."
-msgstr ""
+msgstr "用詞統一，能減少貢獻者之間在溝通上的摩擦。"
 
 #: ./style.md:block 9 (unordered list)
 msgid "Help contributors write well or effectively explain what they do."
-msgstr ""
+msgstr "幫助貢獻者寫好程式碼，或者精準解釋他們的目的。"
 
 #: ./style.md:block 11 (unordered list)
 msgid ""
 "Confirm that contributions are in line with the style guides specified in "
 "the documentation."
-msgstr ""
+msgstr "確認貢獻代碼遵循註解當中的風格指南。"
 
 #: ./style.md:block 11 (unordered list)
 msgid "Check for the presence of automated tests on style."
-msgstr ""
+msgstr "檢查是否有自動化的風格測試。"
 
 #: ./style.md:block 13 (unordered list)
 msgid ""
@@ -2295,12 +2470,14 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
+"為[政策](../glossary.md#policy)與註解建立與遵守風格指南，並且持續改善，同時可"
+"在代碼庫的「CONTRIBUTING」或「README」檔案中註明。"
 
 #: ./style.md:block 15 (unordered list)
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr ""
+msgstr "貴組織對品質的定義中，應該涵蓋書面語言、原始碼、測試與政策標準。"
 
 #: ./style.md:block 17 (paragraph)
 msgid ""
@@ -2315,73 +2492,84 @@ msgid ""
 "Continually improve upon and expand this documentation with the aim of "
 "evolving this documentation into engineering guidelines."
 msgstr ""
+"代碼庫若沒有工程指南或其他貢獻者指南，先在[儲存庫](../glossary.md#repository)"
+"中的「CONTRIBUTING」或「README」檔案加入註解，描述目前在指南方面的進展。註解"
+"主要目的在於表達設計偏好、命名規則等機器不容易檢查的內容。指南應該包含貢獻[程"
+"式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括原始"
+"碼、測試與註解。持續改善與增加註解內容，目標在於讓該註解成為工程指南。"
 
 #: ./style.md:block 18 (paragraph)
 msgid "Additionally:"
-msgstr ""
+msgstr "此外："
 
 #: ./style.md:block 19 (unordered list)
 msgid "Use a linter."
-msgstr ""
+msgstr "使用程式碼品質分析工具。"
 
 #: ./style.md:block 19 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr ""
+msgstr "在代碼庫中加入程式碼品質分析工具配置。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
 "[List of linters](https://github.com/caramelomartins/awesome-linters) by "
 "Hugo Martins."
 msgstr ""
+"Hugo Martins的[程式碼品質分析工具清單](https://github.com/caramelomartins/"
+"awesome-linters)。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
 "[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
 "Wikipedia."
-msgstr ""
+msgstr "維基百科上的[代碼風格](https://en.wikipedia.org/wiki/Programming_style)。"
 
 #: ./understandable-english-first.md:block 1 (header)
 msgid "order: 10"
-msgstr ""
+msgstr "順序：10"
 
 #: ./understandable-english-first.md:block 2 (header)
 msgid "Use plain English"
-msgstr ""
+msgstr "使用簡明英語"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All [codebase](../glossary.md#codebase) documentation MUST be in English."
-msgstr ""
+msgstr "[代碼庫](../glossary.md#codebase)所有註解都必須使用英語。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All [code](../glossary.md#code) MUST be in English, except where "
 "[policy](../glossary.md#policy) is machine interpreted as code."
 msgstr ""
+"所有[程式碼](../glossary.md#code)都必須使用英語，除了[政策](../glossary."
+"md#policy)當中由機器判讀為程式碼的部分。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All bundled policy not available in English MUST have an accompanying "
 "summary in English."
-msgstr ""
+msgstr "同捆政策如果沒有英語版本，則必須提供英語版摘要。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Any translation MUST be up to date with the English version and vice versa."
-msgstr ""
+msgstr "任何翻譯版本與英語版本都必須保持在最新版本狀態。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
-msgstr ""
+msgstr "代碼庫中，不得使用字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙。若有，則"
+"需要在這些用語前面標註，或是附上解釋該用語的網頁連結。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr ""
+msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫、縮寫、雙關語或組織品牌文字"
+"。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
@@ -2389,21 +2577,23 @@ msgid ""
 "recommended by the [Web Content Accessibility Guidelines "
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
+"根據[網頁內容無障礙指南2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)的建議，註解內容應該以國中閱讀水平為主。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr ""
+msgstr "可選擇提供任何程式碼、註解或測試的翻譯版本。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
 "Makes the codebase and what it does understandable for a wider variety of "
 "stakeholders in multiple contexts."
-msgstr ""
+msgstr "讓不同情境的各種利害關係人，都能理解代碼庫以及其功用。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid "Helps with the discoverability of the codebase."
-msgstr ""
+msgstr "讓代碼庫更容易被發現。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
@@ -2411,49 +2601,53 @@ msgid ""
 "directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
 " which requires most public sector information to be accessible."
 msgstr ""
+"能幫助您遵守[歐盟無障礙指令](https://ec.europa.eu/digital-single-market/en/"
+"web-accessibility)，該指令規定所有人都應該能夠獲得多數公領域資訊。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make explanations of the codebase's functionality understandable."
-msgstr ""
+msgstr "讓代碼庫功能解說更容易理解。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make your organization's jargon understandable without an explanation."
-msgstr ""
+msgstr "幫助他人在沒有額外解釋下就能理解貴組織術語。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
-msgstr ""
+msgstr "確認代碼庫註解有英語版本。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid ""
 "Confirm that source code is in English, or confirm any non-English is policy"
 " or terms with preceding explanations."
-msgstr ""
+msgstr "確認原始碼為英語，或是任何非英語內容都是政策或術語，且有加註說明。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm any non-English policy has an accompanying summary in English."
-msgstr ""
+msgstr "確認非英語政策都有英語版摘要。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid ""
 "Confirm that translations and the English version have the same content."
-msgstr ""
+msgstr "確認翻譯版與英語版內容相同。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr ""
+msgstr "確認註解當中，任何字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙都有加註說"
+"明。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
-msgstr ""
+msgstr "檢查註解的拼字、文法與易讀性。"
 
 #: ./understandable-english-first.md:block 13 (unordered list)
 msgid ""
 "Frequently test with other management, developers and designers in the "
 "process if they understand what you are delivering and how you document it."
-msgstr ""
+msgstr "在整個過程中，經常與其他管理人員、開發人員與設計師討論，瞭解他們是否理解您程"
+"式碼與其註解的內容。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
 msgid ""
@@ -2462,24 +2656,27 @@ msgid ""
 "teams and stakeholders. Add any such terms to a glossary and link to it from"
 " the places they are being used."
 msgstr ""
+"在團隊與利害關係人內部以及彼此間的溝通中，試著限制字首縮寫、縮寫、雙關語或法"
+"律/非英語/網域專屬詞彙的使用。將這些詞彙加入至詞彙表，並且在使用這些詞彙的地"
+"方，加上詞彙表連結。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr ""
+msgstr "嚴謹看待註解與變更當中的註解與描述。若有東西您看不懂，其他人很可能也一樣。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
 "Frequently test with policy makers and management if they understand what "
 "you are delivering and how you document it."
-msgstr ""
+msgstr "經常測試決策者與管理人員，瞭解他們是否理解您程式碼與其註解的內容。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
 "Ask someone outside of your context if they understand the content (for "
 "example, a developer working on a different codebase)."
-msgstr ""
+msgstr "請教情境不同的人(例如另一個代碼庫的開發人員)是否理解您的程式碼。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
@@ -2487,27 +2684,32 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
 "readable and understandable."
 msgstr ""
+"全球資訊網協會的[網頁內容無障礙指南2.1與3.1(可讀性)](https://www.w3.org/TR/"
+"WCAG21/#readable)，讓文字內容更容易閱讀與理解。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
 "[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
 " allows 1000 most common English words."
 msgstr ""
+"Theo Sanderson的[Upgoer 5文字編輯軟體](https://splasho.com/upgoer5/"
+")僅允許1,000最常用的英文單字。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
 "[Definition of plain "
 "language](https://www.plainlanguage.gov/about/definitions/) by United States"
 " General Services Administration."
-msgstr ""
+msgstr "美國總務署的[簡明語言定義](https://www.plainlanguage.gov/about/definitions/"
+")。"
 
 #: ./version-control-and-history.md:block 1 (header)
 msgid "order: 6"
-msgstr ""
+msgstr "順序：6"
 
 #: ./version-control-and-history.md:block 2 (header)
 msgid "Maintain version control"
-msgstr ""
+msgstr "維持版本控制"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
@@ -2515,191 +2717,198 @@ msgid ""
 "control](../glossary.md#version-control) for the "
 "[code](../glossary.md#code)."
 msgstr ""
+"社群必須有方法來維持[程式碼](../glossary.md#code)的[版本控制](../glossary.md"
+"#version-control)。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "All files in the [codebase](../glossary.md#codebase) MUST be version "
 "controlled."
-msgstr ""
+msgstr "必須控制[代碼庫](../glossary.md#codebase)所有檔案的版本。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid "All decisions MUST be documented in commit messages."
-msgstr ""
+msgstr "在所有版本訊息中，必須紀錄所有決策。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Every commit message MUST link to discussions and issues wherever possible."
-msgstr ""
+msgstr "每份版本訊息，都必須附上討論與議題的連結(若有)。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD be maintained in a distributed version control system."
-msgstr ""
+msgstr "代碼庫應該以分散式版本控制系統來維護。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid "Contributors SHOULD group relevant changes in commits."
-msgstr ""
+msgstr "貢獻者應該在提交的版本中，將相關變動分類。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Maintainers SHOULD mark released versions of the codebase, for example using"
 " revision tags or textual labels."
-msgstr ""
+msgstr "維護人員應該使用修訂標籤或文字標籤標示代碼庫的完成版本。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Contributors SHOULD prefer file formats where the changes within the files "
 "can be easily viewed and understood in the version control system."
-msgstr ""
+msgstr "貢獻者應該偏好能在版本控制系統中，輕易看出與理解程式碼變動的檔案格式。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr ""
+msgstr "貢獻者可選擇在提交版本中簽名並附上電子郵件信箱，未來貢獻者如果有疑問可以與其"
+"聯絡。"
 
 #: ./version-control-and-history.md:block 7 (paragraph)
 msgid ""
 "Version control means keeping track of changes to the code over time. This "
 "allows you to create structured documentation of the history of the "
 "codebase. This is essential for collaboration at scale."
-msgstr ""
+msgstr "版本控制代表追蹤程式碼歷來的變動，讓您能清楚註解代碼庫的變動歷史，也是大規模"
+"協作的要素。"
 
 #: ./version-control-and-history.md:block 8 (paragraph)
 msgid "Distributed version control enables you to:"
-msgstr ""
+msgstr "分散式版本控制系統讓您可以："
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "have a full copy of the code and its history"
-msgstr ""
+msgstr "擁有完整的程式碼與版本歷史"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "revert to an earlier version of the codebase whenever you want to"
-msgstr ""
+msgstr "想要時可以將代碼庫恢復至先前版本"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid ""
 "record your changes and the reasons why you made them, to help future "
 "developers understand the process"
-msgstr ""
+msgstr "紀錄變動與變動原因，幫助未來開發人員瞭解整個流程"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "compare two different versions"
-msgstr ""
+msgstr "比較兩個不同版本"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "work on changes in parallel as a team before merging them together"
-msgstr ""
+msgstr "團隊可分兩邊研究程式碼需要變動的部分，之後再將內容整合"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid ""
 "continue to work when the network is unavailable, merging changes back with "
 "everyone else’s at a later date"
-msgstr ""
+msgstr "沒有網路時，也能夠持續研究程式碼，之後所有人都上線時再整合程式碼變動部分"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Substitute for [advertising maturity](document-maturity.md)."
-msgstr ""
+msgstr "替代[廣告成熟度](document-maturity.md)。"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Guarantee the code executes correctly."
-msgstr ""
+msgstr "保證程式碼能正確執行。"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Guarantee collaborators."
-msgstr ""
+msgstr "保證會有人協作。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Confirm that the codebase is kept in version control using software such as "
 "Git."
-msgstr ""
+msgstr "確認使用Git等軟體，控制代碼庫的版本。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Review the commit history, confirming that all commit messages explain why "
 "the change was made."
-msgstr ""
+msgstr "審查提交版本紀錄，確認過去所有訊息都有解釋程式碼變動原因。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Review the commit history, confirming that where possible all commit "
 "messages include the discussion about the change was or where to find it "
 "(with a URL)."
-msgstr ""
+msgstr "審查提交版本紀錄，確認過去所有訊息中，都有包含程式碼變動的討論以及資訊位置(提"
+"供連結)。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid "Check if the version control system is distributed."
-msgstr ""
+msgstr "檢查版本控制系統是否為分散式。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Review the commit history, check if grouping of relevant changes in "
 "accordance with the contributing guidelines."
-msgstr ""
+msgstr "審查提交版本紀錄，檢查是否有根據分散指南，將相關程式碼變動分類。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Check that it is possible to access a specific version of the codebase, for "
 "example through a revision tag or a textual label."
-msgstr ""
+msgstr "檢查是否有可能透過修正標籤或文字標籤存取代碼庫的特定版本。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr ""
+msgstr "檢查代碼庫在允許的情況下，是否都採用文字格式。"
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid ""
 "If a new version of the codebase is created because of a "
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
-msgstr ""
+msgstr "如果因為[政策](../glossary."
+"md#policy)變動而更新代碼庫版本，請在註解中清楚標示："
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "what the policy change is,"
-msgstr ""
+msgstr "政策變動內容、"
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "how it's changed the codebase."
-msgstr ""
+msgstr "代碼庫如何因此而改變。"
 
 #: ./version-control-and-history.md:block 16 (paragraph)
 msgid ""
 "For example, adding a new category of applicant to a codebase that manages "
 "granting permits would be considered a policy change."
-msgstr ""
+msgstr "舉例來說，管理許可權指派的代碼庫，如果新增申請方類別，就會被視為政策變動。"
 
 #: ./version-control-and-history.md:block 18 (unordered list)
 msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr ""
+msgstr "支持決策者、開發人員與設計師明確公開他們如何改善代碼庫。代碼庫改善並非公關風"
+"險。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Write clear commit messages so that it is easy to understand why the commit "
 "was made."
-msgstr ""
+msgstr "提交版本時的訊息內容要清楚，讓人一看就能理解提出新版本的原因。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Mark different versions so that it is easy to access a specific version, for"
 " example using revision tags or textual labels."
-msgstr ""
+msgstr "使用修訂標籤或文字標籤標示不同版本，存取特定版本就更容易。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."
-msgstr ""
+msgstr "提交版本的訊息要清楚，方便之後比較各版本。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Work with policy makers to describe how the source code was updated after a "
 "policy change."
-msgstr ""
+msgstr "在政策變動後，與決策者合作說明原始碼的更新內容。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
@@ -2707,6 +2916,8 @@ msgid ""
 "Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
 "Fogel."
 msgstr ""
+"Karl Fogel的[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html"
+"#vc-vocabulary)。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
@@ -2714,15 +2925,20 @@ msgid ""
 "manual/technology/maintaining-version-control-in-coding) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團的[維持程式碼版本控制](https://www.gov.uk/service-manual/"
+"technology/maintaining-version-control-in-coding)。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
 "[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
 " use it or refresh your skills."
-msgstr ""
+msgstr "GitHub的[GitHub學習實驗室](https://lab.github.com/"
+")，學習如何使用GitHub或是溫故知新。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
 "[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
 "education.pdf) by GitHub, a list with the most common used git commands."
 msgstr ""
+"GitHub的[Git備忘條](https://education.github.com/git-cheat-sheet-education."
+"pdf)，列出最常用的git指令。"

From 82d20443653fc87a9eb940292e31daed81ebf786 Mon Sep 17 00:00:00 2001
From: WILT <interpreter.wilt@gmail.com>
Date: Sun, 1 Jan 2023 05:19:05 +0000
Subject: [PATCH 10/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 99.6% (589 of 591 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 209 ++++++++++++------------
 1 file changed, 106 insertions(+), 103 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index e68d9d57..536a1883 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2022-12-22 13:00+0000\n"
-"Last-Translator: Tommy Jiang <baptist333@yahoo.com.tw>\n"
+"PO-Revision-Date: 2023-01-02 13:14+0000\n"
+"Last-Translator: WILT <interpreter.wilt@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -71,11 +71,11 @@ msgstr ""
 "取得原始碼與政策文件，才能瞭解、重複使用以及在代碼庫中進行協作。瞭解情境以及"
 "政策所在情境，才能瞭解代碼庫想要嘗試解決的問題，以及代碼庫可以如何解決這些問"
 "題。如欲評估是否在新的情境中採用代碼庫，組織需要瞭解必須改變的流程，或是如何"
-"提升現有解決方案的配置性，才能適應新情境。"
+"提升現有解決方案的設定，才能適應新情境。"
 
 #: ./bundle-policy-and-code.md:block 8 (header)
 msgid "What this does not do"
-msgstr "沒有以下作用"
+msgstr "不包含的功能"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid "Guarantee that a codebase will reflect the bundled policy."
@@ -111,11 +111,11 @@ msgstr "確認政策是否由機器詮釋。"
 msgid ""
 "Check the continuous integration tests for coherent execution of source code"
 " and policy pass."
-msgstr "確認原始碼與政策的一致執行能通過持續整合測試。"
+msgstr "確認原始碼與政策的執行能一致通過持續整合測試。"
 
 #: ./bundle-policy-and-code.md:block 12 (header)
 msgid "Policy makers: what you need to do"
-msgstr "決策者們：您們的責任"
+msgstr "決策者們：你們要執行的工作"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
@@ -149,7 +149,7 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
 msgstr ""
-"政策內容請使用明確且機器可閱讀的文字，像是[業務流程模型與標記法](https://en."
+"政策內容請使用明確且機器可閱讀的格式，像是[業務流程模型與標記法](https://en."
 "wikipedia.org/wiki/"
 "Business_Process_Model_and_Notation)、[決策模型與標記法](https://en.wikipedia"
 ".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
@@ -159,7 +159,7 @@ msgstr ""
 msgid ""
 "Track policy with [the same version control](version-control-and-history.md)"
 " and documentation used to track source code."
-msgstr "追蹤政策時，請使用與追蹤原始碼[同樣的版本管控](version-control-and-history."
+msgstr "追蹤政策時，請使用與追蹤原始碼[同樣的版本控制](version-control-and-history."
 "md)。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
@@ -167,12 +167,12 @@ msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed and whether it still matches the [intentions of the "
 "policy](document-objectives.md)."
-msgstr "定期檢查代碼庫中的非政策程式碼是否有變動，以及是否依舊符合[政策意圖"
-"](document-objectives.md)。"
+msgstr "定期檢查代碼庫中非政策程式碼的變動，以及是否依舊符合[政策意圖](document-"
+"objectives.md)。"
 
 #: ./bundle-policy-and-code.md:block 14 (header)
 msgid "Management: what you need to do"
-msgstr "管理人員：您們的職責"
+msgstr "管理人員：需要做的事"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
@@ -188,7 +188,7 @@ msgstr "確保決策者、開發人員與設計師朝相同目標努力。"
 
 #: ./bundle-policy-and-code.md:block 16 (header)
 msgid "Developers and designers: what you need to do"
-msgstr "開發人員與設計師：您們的職責"
+msgstr "開發人員與設計師：需要做的事"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
@@ -214,7 +214,8 @@ msgstr "延伸閱讀"
 msgid ""
 "[Free online tools for building BPMN, CMMN and DMN diagrams at "
 "bmpn.io](https://bpmn.io/) by Camunda."
-msgstr "Camunda[提供免費線上工具，可用於建構BPMN、CMMN與DMN圖表](https://bpmn.io/)。"
+msgstr "Camunda [於 bmpn.io "
+"提供免費線上工具，可用於建構BPMN、CMMN與DMN圖表](https://bpmn.io/)。"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
@@ -230,7 +231,7 @@ msgstr "順序：1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "開放的程式碼"
+msgstr "以開放精神編寫原始碼"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -271,7 +272,7 @@ msgstr "您可以選擇是否要紀錄[一般大眾](../glossary.md#general-"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
 msgid "Coding in the open:"
-msgstr "公開編寫程式碼："
+msgstr "以開放精神編寫原始碼："
 
 #: ./code-in-the-open.md:block 8 (unordered list)
 msgid "improves transparency"
@@ -300,7 +301,7 @@ msgstr "讓原始碼或政策能重複使用。"
 msgid ""
 "Make the [codebase](../glossary.md#codebase) and the code within it "
 "understandable to as many people as possible."
-msgstr "讓更多人瞭解[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
+msgstr "讓更多人清楚瞭解[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
@@ -308,8 +309,8 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr "確認使用中的每個版本的原始碼都公布在網路上，且民眾不需要透過任何驗證或授權，"
-"就能在原始貢獻組織之外查看這些原始碼。"
+msgstr "確認使用中的每個版本都公布原始碼在網路上，且民眾不需要透過任何驗證或授權，就"
+"能在原始貢獻組織之外查看這些原始碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
@@ -323,7 +324,7 @@ msgstr "檢查目前非使用中的原始碼是否有公開。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Develop policies in the open."
-msgstr "公開地制定政策。"
+msgstr "以開放精神開發政策。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Prioritize open and transparent policies."
@@ -343,7 +344,7 @@ msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含配置、使用者名稱、密碼、公開金"
+msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含設定、使用者名稱、密碼、公開金"
 "鑰或其他生產系統中的實名資訊等敏感性資訊。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
@@ -357,8 +358,8 @@ msgid ""
 "[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
 " by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[公開編寫程式碼](https://gds.blog.gov.uk/2012/10/12/"
-"coding-in-the-open/)。"
+"英國政府數位服務團的[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
+"12/coding-in-the-open/)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -378,9 +379,9 @@ msgid ""
 "guidance/security-considerations-when-coding-in-the-open) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[公開編寫程式碼的安全考量](https://www.gov.uk/government/"
-"publications/open-source-guidance/security-considerations-when-coding-in-the-"
-"open)。"
+"英國政府數位服務團的[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
+"government/publications/open-source-guidance/security-considerations-when-"
+"coding-in-the-open)。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -437,18 +438,18 @@ msgstr "代碼庫準則應該規定每份貢獻內容都應只聚焦在單一議
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr "應該監督原始碼測試與註解範圍。"
+msgstr "應該監督原始碼測試與文件涵蓋的範圍。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr "可選擇測試[政策](../glossary.md#policy)與註解，確保與原始碼一致。"
+msgstr "可選擇是否測試[政策](../glossary.md#policy)跟文件與原始碼的一致性。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr "可選擇測試政策與註解的風格以及失效連結。"
+msgstr "可選擇是否測試政策跟文件的風格以及失效連結。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "Using [continuous integration](../glossary.md#continuous-integration):"
@@ -456,23 +457,23 @@ msgstr "使用[持續整合](../glossary.md#continuous-integration)："
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "allows you to quickly identify problems with the codebase,"
-msgstr "讓您能迅速找出代碼庫的問題、"
+msgstr "讓您能迅速找出代碼庫的問題，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "enables risk taking and focusing on problem solving while minimizing stress "
 "for the contributors,"
-msgstr "在減少貢獻者面臨的壓力的同時，可以承擔風險並且專注在解決問題上、"
+msgstr "在減少貢獻者面臨的壓力的同時，允許承擔風險並且專注在解決問題上，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "lowers barriers for new contributors by reducing the amount of understanding"
 " necessary to suggest changes,"
-msgstr "讓新貢獻者能更容易建議變更，降低新貢獻者的門檻、"
+msgstr "降低新貢獻者對整體內容理解的門檻，讓他們更容易建議變更，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "leads to more maintainable code,"
-msgstr "程式碼更容易維護、"
+msgstr "讓程式碼更容易維護，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "speeds up the development cycle."
@@ -502,7 +503,7 @@ msgstr "建立有意義的測試。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Test for real life situations."
-msgstr "測試現實生活會實際發生的情境。"
+msgstr "測試實際會發生的情境。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Guarantee the code will deliver exactly the same policy result."
@@ -515,7 +516,7 @@ msgstr "確認有測試可用。"
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that code coverage tools check that coverage is at 100% of the code."
-msgstr "確認程式碼覆蓋率工具能檢查全部的程式碼。"
+msgstr "確認程式碼覆蓋率工具能檢查100%的程式碼。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
@@ -547,11 +548,11 @@ msgstr "儘早讓管理人員、開發人員與設計師參與，並且讓他們
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
 "Make sure there are also automated tests set up for policy documentation."
-msgstr "確保政策註解也有自動化測試。"
+msgstr "確保政策文件也有自動化測試。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid "Fix policy documentation promptly if it fails a test."
-msgstr "如果政策註解未能通過測試，請立即修正。"
+msgstr "如果政策文件未能通過測試，請立即修正。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
@@ -575,7 +576,7 @@ msgstr "計畫頻繁地提交少量內容，而非久久一次繳交大量內容
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr "聘請能逐漸越來越與計畫同步的顧問服務。"
+msgstr "聘請能漸進式與計畫同步的顧問服務。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
@@ -615,7 +616,7 @@ msgstr "編排程式碼時，要能夠將難以在測試環境下創造出來的
 msgid ""
 "Tune the test code coverage tools to avoid false alarms resulting from "
 "inlining or other optimizations."
-msgstr "調整程式碼覆蓋率測試工具，避免內聯或其他優化問題造成假警報。"
+msgstr "調整程式碼覆蓋率測試工具，避免在整合入單一檔案或優化時造成假警報。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid "Deploy often."
@@ -660,7 +661,7 @@ msgstr ""
 
 #: ./document-maturity.md:block 1 (header)
 msgid "order: 16 redirect_from: - criteria/advertise-maturity"
-msgstr "順序：16；自「criteria/advertise-maturity」重新導向"
+msgstr "order: 16 redirect_from: - criteria/advertise-maturity"
 
 #: ./document-maturity.md:block 2 (header)
 msgid "Document codebase maturity"
@@ -668,13 +669,13 @@ msgstr "紀錄代碼庫成熟度"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
-msgstr "[代碼庫](../glossary.md#codebase) 必須版本化。"
+msgstr "[代碼庫](../glossary.md#codebase) 必須註明版本。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase that is ready to use MUST only depend on other codebases that "
 "are also ready to use."
-msgstr "可用的代碼庫只能仰賴其他立即可用的代碼庫。"
+msgstr "與可用代碼庫具相依性的代碼庫必須也是立即可用。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
@@ -741,8 +742,8 @@ msgid ""
 "Make sure that services only rely on codebases of equal or greater maturity "
 "than the service. For example, don't use a beta codebase in a production "
 "service or a prototype codebase in a beta service."
-msgstr "確保服務使用的代碼庫成熟度等同或高於服務本身。舉例來說，生產服務不要用測試版"
-"代碼庫，測試版服務不要用原型代碼庫。"
+msgstr "要確認服務使用的代碼庫成熟度等同或高於服務本身。舉例來說，生產服務不要用測試"
+"版代碼庫，測試版服務不要用原型代碼庫。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
@@ -782,7 +783,7 @@ msgstr "在每個介面上加上顯著的標頭，標示程式碼的成熟度。
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid "Version all releases."
-msgstr "所有推出的程式碼都要標示版本。"
+msgstr "所有釋出的程式碼都要註明版本。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
@@ -840,14 +841,14 @@ msgid ""
 "objectives, like a mission and goal statement, that is understandable by "
 "developers and designers so that they can use or contribute to the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase) 必須包含目標註解，像是使命或目標宣言。開發"
+"[代碼庫](../glossary.md#codebase) 必須包含目標文件，像是使命或目標宣言。開發"
 "人員與設計師需要能夠瞭解這些註解，讓他們能使用或對代碼庫做出貢獻。"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr "代碼庫註解應該清楚描述[政策](../glossary."
+msgstr "代碼庫文件應該清楚描述[政策](../glossary."
 "md#policy)目標與代碼庫目標之前的關聯。"
 
 #: ./document-objectives.md:block 5 (unordered list)
@@ -893,7 +894,7 @@ msgstr "預防其他代碼庫嘗試達成相同的目標。"
 msgid ""
 "Confirm that the codebase documentation includes the codebase objectives, "
 "mission or goal."
-msgstr "確認代碼庫註解包含代碼庫目標與使命。"
+msgstr "確認代碼庫文件包含代碼庫目標與使命。"
 
 #: ./document-objectives.md:block 12 (unordered list)
 msgid ""
@@ -959,20 +960,20 @@ msgstr ""
 msgid ""
 "The documentation of the codebase MUST contain a description of how to "
 "install and run the source code."
-msgstr "代碼庫註解必須說明如何安裝與執行原始碼。"
+msgstr "代碼庫文件必須說明如何安裝與執行原始碼。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr "代碼庫註解必須示範關鍵功能。"
+msgstr "代碼庫文件必須示範關鍵功能。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a high level description "
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
-msgstr "代碼庫註解應該包含詳盡的說明，讓[一般民眾](../glossary.md#general-"
+msgstr "代碼庫文件應該包含詳盡的說明，讓[一般民眾](../glossary.md#general-"
 "public)與記者等廣泛的利害關係人都能明白。."
 
 #: ./documenting.md:block 5 (unordered list)
@@ -980,37 +981,38 @@ msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr "代碼庫註解中應該有一部分是用來說明如何安裝與執行單機版的原始碼。若有需要，也"
+msgstr "代碼庫文件中應該有一部分是用來說明如何安裝與執行單機版的原始碼。若有需要，也"
 "應該包含測試資料集。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr "代碼庫註解應該包含所有功能的示範。"
+msgstr "代碼庫文件應該包含所有功能的示範。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr "註解應該描述代碼庫的主要元件或模組（例如高階建築圖解），以及之間的關係。"
+msgstr "程式碼文件應該描述代碼庫的主要元件或模組（例如高階建築圖解），以及之間的關係"
+"。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "There SHOULD be [continuous integration](../glossary.md#continuous-"
 "integration) tests for the quality of the documentation."
-msgstr "應該要有針對註解品質的[持續整合](../glossary.md#continuous-integration)測試。"
+msgstr "應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr "可選擇在代碼庫註解中，包含讓使用者會想要立即使用代碼庫的範例。"
+msgstr "可選擇在代碼庫文件中，包含讓使用者會想要立即使用代碼庫的範例。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid "Testing the code by using examples in the documentation is OPTIONAL."
-msgstr "可選擇使用註解中的範例來測試程式碼。"
+msgstr "可選擇使用文件中的範例來測試程式碼。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "Users can start using and contributing more quickly."
@@ -1039,25 +1041,25 @@ msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr "確認其他利害關係人、其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解註"
-"解內容。"
+msgstr "確認其他利害關係人、其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解文"
+"件內容。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation describes how to install and run the source "
 "code."
-msgstr "確認註解說明如何安裝與執行原始碼。"
+msgstr "確認文件說明如何安裝與執行原始碼。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation includes examples of the key functionality."
-msgstr "確認註解包含主要功能的示範。"
+msgstr "確認文件包含主要功能的示範。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr "與一般民眾以及記者確認他們是否能明白註解當中艱深的說明。"
+msgstr "與一般民眾以及記者確認他們是否能明白文件當中艱深的說明。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
@@ -1073,14 +1075,15 @@ msgstr "檢查文件中列舉的所有功能都包含範例。"
 msgid ""
 "Check that the documentation includes a high level architectural diagram or "
 "similar."
-msgstr "檢查註解是否包含精細的架構圖。"
+msgstr "檢查文件是否包含精細的架構圖。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated from code, and links and images are "
 "tested."
-msgstr "確認整合測試有包含註解品質，像是檢查註解是自程式碼生成，並且檢查連結與圖片。"
+msgstr "確認整合測試有包含程式碼文件品質，例如確認文件是由程式碼生成，並檢查連結與圖"
+"片。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid ""
@@ -1090,7 +1093,7 @@ msgstr "定期查看代碼庫的非政策程式碼是否有變動。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
-msgstr "針對如何讓非政策註解更清楚易懂提供意見回饋。"
+msgstr "針對如何讓非政策文件更清楚易懂提供意見回饋。"
 
 #: ./documenting.md:block 15 (unordered list)
 msgid "Try to use the codebase."
@@ -1100,7 +1103,7 @@ msgstr "嘗試使用代碼庫。"
 msgid ""
 "Make sure you understand both the policy and source code as well as the "
 "documentation."
-msgstr "確保您了解政策、原始碼以及註解內容。"
+msgstr "確保您了解政策、原始碼以及文件內容。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid ""
@@ -1110,13 +1113,13 @@ msgstr "定期查看代碼庫的非原始碼是否有變動。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
-msgstr "針對如何讓非原始碼註解更清楚易懂提供意見回饋。"
+msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
 
 #: ./documenting.md:block 19 (unordered list)
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr "Write the Docs的[註解指南](https://www.writethedocs.org/guide/)。"
+msgstr "Write the Docs的[文件指南](https://www.writethedocs.org/guide/)。"
 
 #: ./findability.md:block 1 (header)
 msgid "order: 14"
@@ -1139,7 +1142,7 @@ msgstr "民眾用搜尋引擎搜尋代碼庫名稱時，必須能搜尋到代碼
 
 #: ./findability.md:block 5 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr "維護者應該將代碼庫提交至相關軟體型錄上。"
+msgstr "維護者應該將代碼庫提交至相關軟體目錄上。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
@@ -1204,7 +1207,7 @@ msgstr ""
 
 #: ./findability.md:block 9 (unordered list)
 msgid "Ensure new collaborators or replicators."
-msgstr "帶來新協作者或複製者。"
+msgstr "確認新協作者或複製者。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
@@ -1474,8 +1477,8 @@ msgid ""
 "[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
 "benefits-of-coding-in-the-open/) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[公開編寫程式碼的好處](https://gds.blog.gov.uk/2017/09/"
-"04/the-benefits-of-coding-in-the-open/)。"
+"英國政府數位服務團的[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
+"2017/09/04/the-benefits-of-coding-in-the-open/)。"
 
 #: ./open-licenses.md:block 1 (header)
 msgid "order: 13"
@@ -1746,8 +1749,8 @@ msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr "檢查提交說明與其他[儲存庫](../glossary.md#repository)資源是否有提到開源標準，"
-"並且 再次確認有列出標準的內容。"
+msgstr "檢查提交說明與其他[儲存庫](../glossary."
+"md#repository)資源是否有提到開源標準，並且再次確認有列出標準的內容。"
 
 #: ./open-standards.md:block 19 (unordered list)
 msgid ""
@@ -1880,8 +1883,8 @@ msgstr "確保治理文件內容包含如何改變治理方式的現有流程。
 msgid ""
 "If the community has some consensus about how the governance should change, "
 "then include those ideas stated as ambitions in the documentation."
-msgstr "如果社群對於治理方式應該如何改變有共識，應該將此構想列在文件中並且標示為「願"
-"景」。"
+msgstr "如果社群對於治理方式應該如何改變有共識，應該將此構想寫入程式碼文件中並且標示"
+"為「願景」。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
@@ -1972,7 +1975,7 @@ msgstr "審查方式應該包括執行[程式碼](../glossary.md#code)與代碼
 msgid ""
 "Contributions SHOULD be reviewed by someone in a different context than the "
 "contributor."
-msgstr "貢獻內容應該由與貢獻者不同領域的人來審查。"
+msgstr "貢獻內容應該由與貢獻者不同背景的人來審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
@@ -2041,7 +2044,7 @@ msgstr "提供您合適的審查人員。"
 msgid ""
 "Confirm that every commit in the history has been reviewed by a different "
 "contributor."
-msgstr "確認所有不同版本都由不同貢獻者審查。"
+msgstr "確認版本歷史中提交的更新都由不同貢獻者審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
@@ -2065,13 +2068,13 @@ msgstr "檢查審查人員在審查時是否有執行程式碼與測試。"
 msgid ""
 "Check with reviewers if commits have been reviewed by a different "
 "contributor in a different context."
-msgstr "與審查人員確認代碼庫的不同版本是否由不同領域的另一位貢獻者來審查。"
+msgstr "與審查人員確認提交的更新是否已由不同背景的貢獻者來審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check for use of branch protection in the [version "
 "control](../glossary.md#version-control) system."
-msgstr "檢查[版本管控](../glossary.md#version-control)系統是否有採用分支保護。"
+msgstr "檢查[版本控制](../glossary.md#version-control)系統是否有採用分支保護。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check the times between contribution submission and review."
@@ -2196,7 +2199,7 @@ msgstr "路徑圖應該顯示各方的需求。"
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Configuration SHOULD be used to make code adapt to context specific needs."
-msgstr "應該使用配置針對各情境特定需求來調整程式碼。"
+msgstr "設定應該使程式碼適用各情境的特定需求。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be localizable."
@@ -2212,7 +2215,7 @@ msgstr "程式碼與文件不應該包含僅適用於特定情況的資訊。"
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr "代碼庫模組的編寫方式應該讓其能在其他情境的代碼庫中重複利用。"
+msgstr "代碼庫模組在文件記載的方式應該讓其能在其他情境的代碼庫中重複利用。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
@@ -2251,7 +2254,7 @@ msgstr "任何貢獻者都能夠測試與貢獻給代碼庫，且不需要仰賴
 msgid ""
 "Composing a codebase from well documented modules improves reusability and "
 "maintainability."
-msgstr "使用註解清楚的模組來建立代碼庫，代碼庫更能被重複使用，也更容易維護。"
+msgstr "使用文件清楚的模組來建立代碼庫，代碼庫更能被重複使用，也更容易維護。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
@@ -2271,7 +2274,7 @@ msgstr "建立社群。"
 msgid ""
 "Shift responsibility for documentation, support, bug-fixing, etc. to another"
 " party."
-msgstr "將註解、支援與除錯等責任轉移至他人。"
+msgstr "將文件、支援與除錯等責任轉移至他人。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Guarantee that modules are generic enough to be reused in any context."
@@ -2307,7 +2310,7 @@ msgid ""
 "Document your [policy](../glossary.md#policy) with enough clarity and detail"
 " that it can be understood outside of its original context."
 msgstr "為您的[政策](../glossary."
-"md#policy)加上清楚明確的註解，讓他人在不同情境下也能理解。"
+"md#policy)加上清楚明確的文件，讓他人在不同情境下也能理解。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid "Make sure your organization is listed as a known user by the codebase."
@@ -2350,8 +2353,8 @@ msgid ""
 " using proprietary components, ensure that collaborators can develop, use, "
 "test, and deploy without them."
 msgstr ""
-"確保代碼庫註解說明建置當下時間與執行時期相依性。若您的情境需要您部署至專屬平"
-"台或使用專屬元件，確保協作者可以在不用這兩者的情況下開發、使用、測試與部署。"
+"確保代碼庫文件說明建置當下時間與執行期相依性。若您的情境需要您部署至專屬平台"
+"或使用專屬元件，請確保協作者可以在不用這兩者的情況下開發、使用、測試與部署。"
 
 #: ./reusable-and-portable-codebases.md:block 20 (paragraph)
 msgid ""
@@ -2430,7 +2433,7 @@ msgstr "貢獻代碼應該通過自動化的風格測試。"
 msgid ""
 "The codebase SHOULD include inline comments and documentation for non-"
 "trivial sections."
-msgstr "代碼庫當中，複雜的程式碼應該包含註解。"
+msgstr "代碼庫當中，複雜的程式碼應該包含註解與文件。"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
@@ -2458,7 +2461,7 @@ msgstr "幫助貢獻者寫好程式碼，或者精準解釋他們的目的。"
 msgid ""
 "Confirm that contributions are in line with the style guides specified in "
 "the documentation."
-msgstr "確認貢獻代碼遵循註解當中的風格指南。"
+msgstr "確認貢獻代碼遵循文件當中的風格指南。"
 
 #: ./style.md:block 11 (unordered list)
 msgid "Check for the presence of automated tests on style."
@@ -2470,7 +2473,7 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
-"為[政策](../glossary.md#policy)與註解建立與遵守風格指南，並且持續改善，同時可"
+"為[政策](../glossary.md#policy)與文件建立與遵守風格指南，並且持續改善，同時可"
 "在代碼庫的「CONTRIBUTING」或「README」檔案中註明。"
 
 #: ./style.md:block 15 (unordered list)
@@ -2493,10 +2496,10 @@ msgid ""
 "evolving this documentation into engineering guidelines."
 msgstr ""
 "代碼庫若沒有工程指南或其他貢獻者指南，先在[儲存庫](../glossary.md#repository)"
-"中的「CONTRIBUTING」或「README」檔案加入註解，描述目前在指南方面的進展。註解"
+"中的「CONTRIBUTING」或「README」檔案加入文件，描述目前在指南方面的進展。文件"
 "主要目的在於表達設計偏好、命名規則等機器不容易檢查的內容。指南應該包含貢獻[程"
 "式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括原始"
-"碼、測試與註解。持續改善與增加註解內容，目標在於讓該註解成為工程指南。"
+"碼、測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
 
 #: ./style.md:block 18 (paragraph)
 msgid "Additionally:"
@@ -2508,7 +2511,7 @@ msgstr "使用程式碼品質分析工具。"
 
 #: ./style.md:block 19 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入程式碼品質分析工具配置。"
+msgstr "在代碼庫中加入程式碼品質分析工具設定。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
@@ -2535,7 +2538,7 @@ msgstr "使用簡明英語"
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All [codebase](../glossary.md#codebase) documentation MUST be in English."
-msgstr "[代碼庫](../glossary.md#codebase)所有註解都必須使用英語。"
+msgstr "[代碼庫](../glossary.md#codebase)所有文件都必須使用英語。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
@@ -2578,12 +2581,12 @@ msgid ""
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
 "根據[網頁內容無障礙指南2](https://www.w3.org/WAI/WCAG21/quickref/"
-"?showtechniques=315#readable)的建議，註解內容應該以國中閱讀水平為主。"
+"?showtechniques=315#readable)的建議，文件內容應該以國中閱讀水平為主。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr "可選擇提供任何程式碼、註解或測試的翻譯版本。"
+msgstr "可選擇提供任何程式碼、文件或測試的翻譯版本。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
@@ -2614,7 +2617,7 @@ msgstr "幫助他人在沒有額外解釋下就能理解貴組織術語。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
-msgstr "確認代碼庫註解有英語版本。"
+msgstr "確認代碼庫文件有英語版本。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid ""
@@ -2635,19 +2638,19 @@ msgstr "確認翻譯版與英語版內容相同。"
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr "確認註解當中，任何字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙都有加註說"
+msgstr "確認文件當中，任何字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙都有加註說"
 "明。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
-msgstr "檢查註解的拼字、文法與易讀性。"
+msgstr "檢查文件的拼字、文法與易讀性。"
 
 #: ./understandable-english-first.md:block 13 (unordered list)
 msgid ""
 "Frequently test with other management, developers and designers in the "
 "process if they understand what you are delivering and how you document it."
 msgstr "在整個過程中，經常與其他管理人員、開發人員與設計師討論，瞭解他們是否理解您程"
-"式碼與其註解的內容。"
+"式碼與其文件的內容。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
 msgid ""
@@ -2664,13 +2667,13 @@ msgstr ""
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr "嚴謹看待註解與變更當中的註解與描述。若有東西您看不懂，其他人很可能也一樣。"
+msgstr "嚴謹看待提案與變更當中的文件與描述。若有東西您看不懂，其他人很可能也一樣。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
 "Frequently test with policy makers and management if they understand what "
 "you are delivering and how you document it."
-msgstr "經常測試決策者與管理人員，瞭解他們是否理解您程式碼與其註解的內容。"
+msgstr "經常測試決策者與管理人員，瞭解他們是否理解您程式碼與其文件的內容。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
@@ -2769,7 +2772,7 @@ msgid ""
 "Version control means keeping track of changes to the code over time. This "
 "allows you to create structured documentation of the history of the "
 "codebase. This is essential for collaboration at scale."
-msgstr "版本控制代表追蹤程式碼歷來的變動，讓您能清楚註解代碼庫的變動歷史，也是大規模"
+msgstr "版本控制代表追蹤程式碼歷來的變動，讓您能建立代碼庫文件的變動歷史，這是大規模"
 "協作的要素。"
 
 #: ./version-control-and-history.md:block 8 (paragraph)
@@ -2864,7 +2867,7 @@ msgid ""
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
 msgstr "如果因為[政策](../glossary."
-"md#policy)變動而更新代碼庫版本，請在註解中清楚標示："
+"md#policy)變動而更新代碼庫版本，請在文件中清楚標示："
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "what the policy change is,"

From b4d4f9e50b80b4ba2ccc78220974c7c2d39ed503 Mon Sep 17 00:00:00 2001
From: WILT <interpreter.wilt@gmail.com>
Date: Tue, 10 Jan 2023 13:33:36 +0000
Subject: [PATCH 11/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 99.6% (592 of 594 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 138 ++++++++++++------------
 1 file changed, 69 insertions(+), 69 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 536a1883..d9680ff4 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-02 13:14+0000\n"
+"PO-Revision-Date: 2023-01-11 14:37+0000\n"
 "Last-Translator: WILT <interpreter.wilt@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -68,7 +68,7 @@ msgid ""
 " must choose to make or how to contribute additional configurability to the "
 "existing solution in order to adapt it to the new context."
 msgstr ""
-"取得原始碼與政策文件，才能瞭解、重複使用以及在代碼庫中進行協作。瞭解情境以及"
+"取得原始碼與政策文件，才能瞭解，重複使用以及在代碼庫中進行協作。瞭解情境以及"
 "政策所在情境，才能瞭解代碼庫想要嘗試解決的問題，以及代碼庫可以如何解決這些問"
 "題。如欲評估是否在新的情境中採用代碼庫，組織需要瞭解必須改變的流程，或是如何"
 "提升現有解決方案的設定，才能適應新情境。"
@@ -151,7 +151,7 @@ msgid ""
 msgstr ""
 "政策內容請使用明確且機器可閱讀的格式，像是[業務流程模型與標記法](https://en."
 "wikipedia.org/wiki/"
-"Business_Process_Model_and_Notation)、[決策模型與標記法](https://en.wikipedia"
+"Business_Process_Model_and_Notation)，[決策模型與標記法](https://en.wikipedia"
 ".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
 "wikipedia.org/wiki/CMMN)。"
 
@@ -178,13 +178,13 @@ msgstr "管理人員：需要做的事"
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr "讓決策者、開發人員與設計師參與開發並且在整個過程中保持聯繫。"
+msgstr "讓決策者，開發人員與設計師參與開發並且在整個過程中保持聯繫。"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr "確保決策者、開發人員與設計師朝相同目標努力。"
+msgstr "確保決策者，開發人員與設計師朝相同目標努力。"
 
 #: ./bundle-policy-and-code.md:block 16 (header)
 msgid "Developers and designers: what you need to do"
@@ -215,7 +215,7 @@ msgid ""
 "[Free online tools for building BPMN, CMMN and DMN diagrams at "
 "bmpn.io](https://bpmn.io/) by Camunda."
 msgstr "Camunda [於 bmpn.io "
-"提供免費線上工具，可用於建構BPMN、CMMN與DMN圖表](https://bpmn.io/)。"
+"提供免費線上工具，可用於建構BPMN，CMMN與DMN圖表](https://bpmn.io/)。"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
@@ -253,14 +253,14 @@ msgid ""
 "Contributors MUST NOT upload sensitive information regarding users, their "
 "organization or third parties to the "
 "[repository](../glossary.md#repository)."
-msgstr "貢獻者絕對不可上傳有關使用者、其組織或第三方的敏感性資訊到[儲存庫](../glossar"
+msgstr "貢獻者絕對不可上傳有關使用者，其組織或第三方的敏感性資訊到[儲存庫](../glossar"
 "y.md#repository)。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr "目前非使用中的原始碼（像是新版本、提案或較舊版本）都應該公開。"
+msgstr "目前非使用中的原始碼（像是新版本，提案或較舊版本）都應該公開。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -332,7 +332,7 @@ msgstr "以公開透明政策為優先。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid "Develop a culture that embraces openness, learning and feedback."
-msgstr "孕育一個重視開放、學習與意見回饋的文化。"
+msgstr "孕育一個重視開放，學習與意見回饋的文化。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid ""
@@ -344,7 +344,7 @@ msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含設定、使用者名稱、密碼、公開金"
+msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含設定，使用者名稱，密碼，公開金"
 "鑰或其他生產系統中的實名資訊等敏感性資訊。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
@@ -495,7 +495,7 @@ msgstr "開發中的代碼庫較能提供協作與提供意見回饋的機會。
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid ""
 "Create a fault tolerant infrastructure that will work and scale perfectly."
-msgstr "建立能夠順暢作業、擴展且能容錯的基礎架構。"
+msgstr "建立能夠順暢作業，擴展且能容錯的基礎架構。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Create meaningful tests."
@@ -543,7 +543,7 @@ msgid ""
 "Involve management as well as developers and designers as early in the "
 "process as possible and keep them engaged throughout development of your "
 "policy."
-msgstr "儘早讓管理人員、開發人員與設計師參與，並且讓他們全程參與您政策的開發。"
+msgstr "儘早讓管理人員，開發人員與設計師參與，並且讓他們全程參與您政策的開發。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
@@ -681,7 +681,7 @@ msgstr "與可用代碼庫具相依性的代碼庫必須也是立即可用。"
 msgid ""
 "The codebase that is not yet ready to use MUST have one of the labels: "
 "prototype, alpha, beta or pre-release version."
-msgstr "尚未準備好使用的代碼庫必須有這些標籤之一：原型、預覽、測試或發布前版本。"
+msgstr "尚未準備好使用的代碼庫必須有這些標籤之一：原型，預覽，測試或準完成版本。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
@@ -693,7 +693,7 @@ msgstr "代碼庫應該包含每次版本變動的紀錄，像是「CHANGELOG」
 msgid ""
 "Clearly signalling a codebase's maturity helps others decide whether to "
 "reuse, invest in or contribute to it."
-msgstr "清楚標示代碼庫的成熟度有助於他人決定是否要重複使用、投資或貢獻該代碼庫。"
+msgstr "清楚標示代碼庫的成熟度有助於他人決定是否要重複使用，投資或貢獻給該代碼庫。"
 
 #: ./document-maturity.md:block 9 (unordered list)
 msgid "Guarantee that others will use the [code](../glossary.md#code)."
@@ -706,7 +706,7 @@ msgstr "確認代碼庫有版本化策略且有文件詳細記載該策略。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Confirm that it is clear where to get the newest version."
-msgstr "確認最新版本容易取得。"
+msgstr "確認有註明最新版本的取得方法。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
@@ -718,7 +718,7 @@ msgstr "確認代碼庫不需要仰賴成熟度標示較低的其他代碼庫。
 msgid ""
 "Confirm that the codebase is ready to use or labeled as prototype, alpha, "
 "beta or pre-release version."
-msgstr "確認代碼庫已準備好使用，或是標示為原型、預覽、測試或發布前版本。"
+msgstr "確認代碼庫已準備好使用，或是標示為原型，預覽，測試或準完成版本。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Check that there is a log of changes."
@@ -729,13 +729,13 @@ msgid ""
 "When developing [policy](../glossary.md#policy), understand that any code "
 "developed needs to be tested and improved before it can be put into service."
 msgstr "制定[政策](../glossary."
-"md#policy)時，記住任何開發出來的程式碼都必須經過測試與改善，才能夠實際應用。"
+"md#policy)時，記住任何開發出來的程式碼都必須經過測試與改善，才能夠投入服務。"
 
 #: ./document-maturity.md:block 13 (unordered list)
 msgid ""
 "Consider versioning policy changes, especially when they trigger new "
 "versions of the source code."
-msgstr "考慮到版本化政策的變動，特別是因此產生新版本原始碼的情況時。"
+msgstr "考慮版本化政策的變動，特別是因此產生新版本原始碼的情況時。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
@@ -755,11 +755,11 @@ msgstr "若代碼庫尚未準備好使用，請與開發人員一起確保該代
 msgid ""
 "prototype: to test the look and feel, and to internally prove the concept of"
 " the technical possibilities,"
-msgstr "原型：測試外觀與體驗，並且從內部證明技術可能性的概念、"
+msgstr "原型：測試外觀與體驗，並且從內部證明技術可能性的概念，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid "alpha: to do guided tests with a limited set of users,"
-msgstr "預覽：在使用者有限的情況下進行引導測試、"
+msgstr "預覽：在使用者有限的情況下進行引導測試，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
@@ -767,7 +767,7 @@ msgid ""
 "public](../glossary.md#general-public), for example to test if the codebase "
 "works at scale,"
 msgstr "測試：讓更多[社會大眾](../glossary.md#general-"
-"public)參與測試，例如測試代碼庫在大規模運作下是否依舊順暢、"
+"public)參與測試，例如測試代碼庫在大規模運作下是否依舊順暢，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
@@ -824,7 +824,7 @@ msgid ""
 "service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
 "the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[什麼是服務開發當中的探索、預覽、測試與上線階段？ [影片 "
+"英國政府數位服務團的[什麼是服務開發當中的探索、預覽，測試與上線階段？ [影片 "
 "0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)。"
 
 #: ./document-objectives.md:block 1 (header)
@@ -913,7 +913,7 @@ msgid ""
 "Include relevant policies which impact the community, codebase, and "
 "development like value and ethics based policies, for example accessibility "
 "or equal opportunity."
-msgstr "加入相關政策，這些政策會影響到社群、代碼庫以及無障礙或平等機會等價值或倫理基"
+msgstr "加入相關政策，這些政策會影響到社群，代碼庫以及無障礙或平等機會等價值或倫理基"
 "礎的政策的制定。"
 
 #: ./document-objectives.md:block 16 (unordered list)
@@ -952,7 +952,7 @@ msgid ""
 "language clearly understandable for those that understand the purpose of the"
 " [code](../glossary.md#code)."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)、[政策](../glossary."
+"[代碼庫](../glossary.md#codebase)，[政策](../glossary."
 "md#policy)以及原始碼的功能性，都必須清楚描述，讓懂[程式碼](../glossary."
 "md#code)目的的人也能夠瞭解。"
 
@@ -1041,7 +1041,7 @@ msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr "確認其他利害關係人、其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解文"
+msgstr "確認其他利害關係人，其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解文"
 "件內容。"
 
 #: ./documenting.md:block 11 (unordered list)
@@ -1103,7 +1103,7 @@ msgstr "嘗試使用代碼庫。"
 msgid ""
 "Make sure you understand both the policy and source code as well as the "
 "documentation."
-msgstr "確保您了解政策、原始碼以及文件內容。"
+msgstr "確保您了解政策，原始碼以及文件內容。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid ""
@@ -1149,7 +1149,7 @@ msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr "應該要為代碼庫架設網站，上面用潛在使用者(技術人員、政策專家與管理人員)偏好的"
+msgstr "應該要為代碼庫架設網站，上面用潛在使用者(技術人員，政策專家與管理人員)偏好的"
 "術語描述代碼庫能解決的問題。"
 
 #: ./findability.md:block 5 (unordered list)
@@ -1157,8 +1157,8 @@ msgid ""
 "The codebase SHOULD have a unique and persistent identifier where the entry "
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
-msgstr "代碼庫應該具備永久唯一識別碼，且內容需要提到主要貢獻者、[儲存庫](../glossary."
-"md#repository)、地點與網站。"
+msgstr "代碼庫應該具備永久唯一識別碼，且內容需要提到主要貢獻者，[儲存庫](../glossary."
+"md#repository)，地點與網站。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
@@ -1202,7 +1202,7 @@ msgid ""
 "tools."
 msgstr ""
 "內容豐富且包含永久唯一識別碼的元資料(像是刊載在維基數據或是FSF網站上)，讓代碼"
-"庫成為語意網的一部份。如此一來，他人就能更容易地透過第三方工具參考、引用、解"
+"庫成為語意網的一部份。如此一來，他人就能更容易地透過第三方工具參考，引用，解"
 "釋與發現代碼庫。"
 
 #: ./findability.md:block 9 (unordered list)
@@ -1397,7 +1397,7 @@ msgstr "文件應該說明如何透過封閉的管道通報潛在的安全與敏
 msgid ""
 "Enables users to fix problems and add features to the shared codebase "
 "leading to better, more reliable and feature rich software."
-msgstr "讓使用者能夠修復問題以及新增共享代碼庫的功能，讓軟體更好、更可靠且功能更豐富"
+msgstr "讓使用者能夠修復問題以及新增共享代碼庫的功能，讓軟體更好，更可靠且功能更豐富"
 "。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
@@ -1450,7 +1450,7 @@ msgstr "追蹤代碼庫中的管理問題，讓相關外部政策專家也能自
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr "支持您經驗豐富的政策制定者、開發人員與設計師來持續貢獻代碼給代碼庫。"
+msgstr "支持您經驗豐富的政策制定者，開發人員與設計師來持續貢獻代碼給代碼庫。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid "Respond promptly to requests."
@@ -1493,7 +1493,7 @@ msgid ""
 "All [code](../glossary.md#code) and documentation MUST be licensed such that"
 " it may be freely reusable, changeable and redistributable."
 msgstr "必須取得所有[程式碼](../glossary."
-"md#code)與文件的授權，讓所有人可以免費重複利用、變更與散布。"
+"md#code)與文件的授權，讓所有人可以免費重複利用，變更與散布。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
@@ -1596,7 +1596,7 @@ msgid ""
 "requirements."
 msgstr ""
 "請注意：雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件上"
-"，具有非商業性或禁止改作的授權代表不得免費重複使用、變更與散布，因此不符合規"
+"，具有非商業性或禁止改作的授權代表不得免費重複使用，變更與散布，因此不符合規"
 "定。"
 
 #: ./open-licenses.md:block 17 (unordered list)
@@ -1631,7 +1631,7 @@ msgid ""
 "readable copyright and licensing information."
 msgstr ""
 "歐洲自由軟體基金會的[REUSE倡議規範](https://reuse.software/spec/"
-")，是規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
+")，是規範明確，人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
@@ -1788,7 +1788,7 @@ msgstr "代碼庫必須包含貢獻指引，像是在「CONTRIBUTING」檔案中
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr "代碼庫必須說明代碼庫、貢獻內容與社群的治理方式，可利用「GOVERNANCE」檔案來說"
+msgstr "代碼庫必須說明代碼庫，貢獻內容與社群的治理方式，可利用「GOVERNANCE」檔案來說"
 "明。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
@@ -1865,7 +1865,7 @@ msgid ""
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
 "為代碼庫新增其他資源清單，上面資源都是能幫助[政策](../glossary."
-"md#policy)專家、非政府組織與學者更瞭解或學會重複利用您的政策。"
+"md#policy)專家，非政府組織與學者更瞭解或學會重複利用您的政策。"
 
 #: ./open-to-contributions.md:block 13 (unordered list)
 msgid ""
@@ -1890,14 +1890,14 @@ msgstr "如果社群對於治理方式應該如何改變有共識，應該將此
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr "確認文件解釋每個組織參與本代碼庫的方式、提供代碼庫哪些資源以及參與的時間長度"
+msgstr "確認文件解釋每個組織參與本代碼庫的方式，提供代碼庫哪些資源以及參與的時間長度"
 "。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to stay "
 "part of the community for as long as possible."
-msgstr "支持經驗豐富的決策者、開發人員與設計師參與代碼庫社群，且時間越長越好。"
+msgstr "支持經驗豐富的決策者，開發人員與設計師參與代碼庫社群，且時間越長越好。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1951,7 +1951,7 @@ msgstr "所有被接受或是提交給完成版[代碼庫](../glossary."
 msgid ""
 "Reviews MUST include source, [policy](../glossary.md#policy), tests and "
 "documentation."
-msgstr "審查必須包含來源、[政策](../glossary.md#policy)、測試與文件。"
+msgstr "審查必須包含來源，[政策](../glossary.md#policy)，測試與文件。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
@@ -1963,7 +1963,7 @@ msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
 msgid ""
 "Contributions SHOULD conform to the standards, architecture and decisions "
 "set out in the codebase in order to pass review."
-msgstr "貢獻內容應該遵循代碼庫的標準、架構與決策，才能通過審查。"
+msgstr "貢獻內容應該遵循代碼庫的標準，架構與決策，才能通過審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
@@ -2048,7 +2048,7 @@ msgstr "確認版本歷史中提交的更新都由不同貢獻者審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
-msgstr "確認審查包含來源、政策、測試與文件。"
+msgstr "確認審查包含來源，政策，測試與文件。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that rejected contributions were appropriately explained."
@@ -2058,7 +2058,7 @@ msgstr "針對未被採用的貢獻內容，確認有詳盡解釋原因。"
 msgid ""
 "Check if reviews cover conformance to standards, architecture and codebase "
 "guidelines."
-msgstr "檢查審查包含貢獻內容是否遵循標準、架構與代碼庫指引。"
+msgstr "檢查審查包含貢獻內容是否遵循標準，架構與代碼庫指引。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check with reviewers if they run the code and tests during review."
@@ -2099,7 +2099,7 @@ msgstr "讓所有人以寫出好的程式碼為目標。"
 msgid ""
 "Make sure writing and reviewing contributions to source, policy, "
 "documentation and tests are considered equally valuable."
-msgstr "確保同樣重視撰寫與審查貢獻內容，與編寫原始碼、政策、文件與測試。"
+msgstr "確保同樣重視撰寫與審查貢獻內容，與編寫原始碼，政策，文件與測試。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid ""
@@ -2185,7 +2185,7 @@ msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed [code](../glossary.md#code) or services for execution "
 "and understanding."
-msgstr "代碼庫的執行與理解必須不仰賴任何秘密、未公開、專屬或非開源授權的[程式碼](../g"
+msgstr "代碼庫的執行與理解必須不仰賴任何秘密，未公開，專屬或非開源授權的[程式碼](../g"
 "lossary.md#code)。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
@@ -2222,8 +2222,8 @@ msgid ""
 "Enables other policy makers, developers and designers to reuse what you've "
 "developed, to test it, to improve it and contribute those improvements back "
 "leading to better quality, cheaper maintenance and higher reliability."
-msgstr "讓其他決策者、開發人員與設計師能夠重複利用您編寫的程式碼，並且測試與改善該程"
-"式碼，然後提供改善意見，讓程式碼品質更高、維護成本下滑且更可靠。"
+msgstr "讓其他決策者，開發人員與設計師能夠重複利用您編寫的程式碼，並且測試與改善該程"
+"式碼，然後提供改善意見，讓程式碼品質更高，維護成本下滑且更可靠。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
@@ -2235,7 +2235,7 @@ msgid ""
 "Makes it easier to control the mission, vision and scope of the codebase "
 "because the codebase is thoughtfully and purposefully designed for "
 "reusability."
-msgstr "隨著代碼庫是以重複利用為前提來編寫，因此控制其使命、願景與範圍也更容易。"
+msgstr "讓代碼庫以重複利用為前提來編寫，因此控制其使命、願景與範圍也更容易。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
@@ -2274,7 +2274,7 @@ msgstr "建立社群。"
 msgid ""
 "Shift responsibility for documentation, support, bug-fixing, etc. to another"
 " party."
-msgstr "將文件、支援與除錯等責任轉移至他人。"
+msgstr "將文件，支援與除錯等責任轉移至他人。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Guarantee that modules are generic enough to be reused in any context."
@@ -2330,15 +2330,15 @@ msgstr "原始碼的設計："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr "讓其他使用者與組織可重複利用，不受地點影響、"
+msgstr "讓其他使用者與組織可重複利用，不受地點影響，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "to solve a general problem instead of a specific one,"
-msgstr "解決通用問題，而非特定問題、"
+msgstr "解決通用問題，而非特定問題，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "in logically meaningful and isolated modules,"
-msgstr "採用邏輯上具有意義且獨立的模組、"
+msgstr "採用邏輯上具有意義且獨立的模組，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid ""
@@ -2354,15 +2354,15 @@ msgid ""
 "test, and deploy without them."
 msgstr ""
 "確保代碼庫文件說明建置當下時間與執行期相依性。若您的情境需要您部署至專屬平台"
-"或使用專屬元件，請確保協作者可以在不用這兩者的情況下開發、使用、測試與部署。"
+"或使用專屬元件，請確保協作者可以在不用這兩者的情況下開發，使用，測試與部署。"
 
 #: ./reusable-and-portable-codebases.md:block 20 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr "在每個版本上，審查人員確認內容不會包含專屬特定情況的資料，像是主機名稱、個人"
-"與組織資料或是token與密碼。"
+msgstr "在每個版本上，審查人員確認內容不會包含專屬特定情況的資料，像是主機名稱，個人"
+"與組織資料或是代符與密碼。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2380,7 +2380,7 @@ msgid ""
 "interface description for human and machine-readable HTTP APIs."
 msgstr ""
 "OpenAPI Initiative組織的[OpenAPI規範](https://spec.openapis.org/oas/latest."
-"html)為人機可讀的HTTP API定義標準、不受程式語言種類限制的介面描述。"
+"html)為人機可讀的HTTP API定義標準，不受程式語言種類限制的介面描述。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2480,7 +2480,7 @@ msgstr ""
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr "貴組織對品質的定義中，應該涵蓋書面語言、原始碼、測試與政策標準。"
+msgstr "貴組織對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
 
 #: ./style.md:block 17 (paragraph)
 msgid ""
@@ -2497,9 +2497,9 @@ msgid ""
 msgstr ""
 "代碼庫若沒有工程指南或其他貢獻者指南，先在[儲存庫](../glossary.md#repository)"
 "中的「CONTRIBUTING」或「README」檔案加入文件，描述目前在指南方面的進展。文件"
-"主要目的在於表達設計偏好、命名規則等機器不容易檢查的內容。指南應該包含貢獻[程"
+"主要目的在於表達設計偏好，命名規則等機器不容易檢查的內容。指南應該包含貢獻[程"
 "式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括原始"
-"碼、測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
+"碼，測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
 
 #: ./style.md:block 18 (paragraph)
 msgid "Additionally:"
@@ -2564,14 +2564,14 @@ msgid ""
 "There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
-msgstr "代碼庫中，不得使用字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙。若有，則"
+msgstr "代碼庫中，不得使用字首縮寫，縮寫，雙關語或法律/非英語/網域專屬詞彙。若有，則"
 "需要在這些用語前面標註，或是附上解釋該用語的網頁連結。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫、縮寫、雙關語或組織品牌文字"
+msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或組織品牌文字"
 "。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
@@ -2586,7 +2586,7 @@ msgstr ""
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr "可選擇提供任何程式碼、文件或測試的翻譯版本。"
+msgstr "可選擇提供任何程式碼，文件或測試的翻譯版本。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
@@ -2638,18 +2638,18 @@ msgstr "確認翻譯版與英語版內容相同。"
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr "確認文件當中，任何字首縮寫、縮寫、雙關語或法律/非英語/網域專屬詞彙都有加註說"
+msgstr "確認文件當中，任何字首縮寫，縮寫，雙關語或法律/非英語/網域專屬詞彙都有加註說"
 "明。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
-msgstr "檢查文件的拼字、文法與易讀性。"
+msgstr "檢查文件的拼字，文法與易讀性。"
 
 #: ./understandable-english-first.md:block 13 (unordered list)
 msgid ""
 "Frequently test with other management, developers and designers in the "
 "process if they understand what you are delivering and how you document it."
-msgstr "在整個過程中，經常與其他管理人員、開發人員與設計師討論，瞭解他們是否理解您程"
+msgstr "在整個過程中，經常與其他管理人員，開發人員與設計師討論，瞭解他們是否理解您程"
 "式碼與其文件的內容。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
@@ -2659,7 +2659,7 @@ msgid ""
 "teams and stakeholders. Add any such terms to a glossary and link to it from"
 " the places they are being used."
 msgstr ""
-"在團隊與利害關係人內部以及彼此間的溝通中，試著限制字首縮寫、縮寫、雙關語或法"
+"在團隊與利害關係人內部以及彼此間的溝通中，試著限制字首縮寫，縮寫，雙關語或法"
 "律/非英語/網域專屬詞彙的使用。將這些詞彙加入至詞彙表，並且在使用這些詞彙的地"
 "方，加上詞彙表連結。"
 
@@ -2871,7 +2871,7 @@ msgstr "如果因為[政策](../glossary."
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "what the policy change is,"
-msgstr "政策變動內容、"
+msgstr "政策變動內容，"
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "how it's changed the codebase."
@@ -2888,8 +2888,8 @@ msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr "支持決策者、開發人員與設計師明確公開他們如何改善代碼庫。代碼庫改善並非公關風"
-"險。"
+msgstr "支持決策者，開發人員與設計師，明確公開他們如何改善代碼庫。代碼庫改善並非公關"
+"風險。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""

From 0cd2d5de10e1f01c2c53eadd434b961c93f2fba4 Mon Sep 17 00:00:00 2001
From: WILT <interpreter.wilt@gmail.com>
Date: Thu, 12 Jan 2023 07:28:51 +0000
Subject: [PATCH 12/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (594 of 594 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 67 ++++++++++++-------------
 1 file changed, 33 insertions(+), 34 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index d9680ff4..a4ef7a93 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-11 14:37+0000\n"
+"PO-Revision-Date: 2023-01-12 09:06+0000\n"
 "Last-Translator: WILT <interpreter.wilt@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -661,7 +661,7 @@ msgstr ""
 
 #: ./document-maturity.md:block 1 (header)
 msgid "order: 16 redirect_from: - criteria/advertise-maturity"
-msgstr "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr "順序：16 redirect_from: - criteria/advertise-maturity"
 
 #: ./document-maturity.md:block 2 (header)
 msgid "Document codebase maturity"
@@ -773,7 +773,7 @@ msgstr "測試：讓更多[社會大眾](../glossary.md#general-"
 msgid ""
 "pre-release version: code that is ready to be released but hasn't received "
 "formal approval yet."
-msgstr "發布前版本：已經準備好發布但尚未正式獲准的程式碼。"
+msgstr "準完成版本：已經準備好發布但尚未正式獲准的程式碼。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
@@ -792,7 +792,7 @@ msgid ""
 "metadata (for example by using [git describe](https://git-scm.com/docs/git-"
 "describe))."
 msgstr ""
-"特別是在「滾動發行」的情況時，程式碼的版本資訊可能自動從[版本管控](../glossar"
+"特別是在「滾動發行」的情況時，程式碼的版本資訊可能自動從[版本控制](../glossar"
 "y.md#version-control)系統元資料中擷取(例如使用[git describe](https://git-scm."
 "com/docs/git-describe))。"
 
@@ -824,7 +824,7 @@ msgid ""
 "service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
 "the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[什麼是服務開發當中的探索、預覽，測試與上線階段？ [影片 "
+"英國政府數位服務團的[什麼是服務開發當中的探索，預覽，測試與上線階段？ [影片 "
 "0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)。"
 
 #: ./document-objectives.md:block 1 (header)
@@ -865,7 +865,7 @@ msgstr "紀錄代碼庫目標："
 msgid ""
 "provides an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
-msgstr "更容易決定是否對本代碼庫或其模組有興趣。"
+msgstr "提供簡易方法讓人判斷是否在當下或未來會對本代碼庫或其模組感興趣。"
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid "helps scope your own development."
@@ -906,7 +906,7 @@ msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
 msgid ""
 "Add the policy objectives to the codebase documentation, for example in the "
 "`README`."
-msgstr "將政策目標加入代碼庫文件中，像是「README」。"
+msgstr "將政策目標加入代碼庫文件中，例如在「README」當中。"
 
 #: ./document-objectives.md:block 14 (unordered list)
 msgid ""
@@ -920,13 +920,13 @@ msgstr "加入相關政策，這些政策會影響到社群，代碼庫以及無
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr "將組織或企業目標加入代碼庫文件中，例如「README」。"
+msgstr "將組織或企業目標加入代碼庫文件中，例如在「README」當中。"
 
 #: ./document-objectives.md:block 18 (unordered list)
 msgid ""
 "Add the technology and design objectives to the codebase documentation, for "
 "example in the `README`."
-msgstr "將技術與設計目標加入代碼庫文件中，例如「README」。"
+msgstr "將技術與設計目標加入代碼庫文件中，例如在「README」當中。"
 
 #: ./document-objectives.md:block 20 (unordered list)
 msgid ""
@@ -1022,7 +1022,7 @@ msgstr "使用者可以更快速地使用與貢獻給代碼庫。"
 msgid ""
 "You help people discover the codebase, especially people asking 'is there "
 "already code that does something like this'."
-msgstr "您幫助他人找到這個代碼庫，特別是那些在尋找有如此功能代碼庫的人們。"
+msgstr "幫助他人找到這個代碼庫，特別是那些在尋找有如此功能代碼庫的人們。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "This provides transparency into your organization and processes."
@@ -1033,8 +1033,8 @@ msgid ""
 "Contribute directly to more reusable, portable code (see [Create reusable "
 "and portable code](./reusable-and-portable-codebases.md))."
 msgstr ""
-"直接讓程式碼變得更可重複使用以及容易攜帶(請參閱[編寫可重複使用且容易攜帶的程"
-"式碼](./reusable-and-portable-codebases.md))。"
+"直接貢獻給更可重複使用以及容易攜帶的程式碼(請參閱[編寫可重複使用且容易攜帶的"
+"程式碼](./reusable-and-portable-codebases.md))。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
@@ -1089,7 +1089,7 @@ msgstr "確認整合測試有包含程式碼文件品質，例如確認文件是
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed."
-msgstr "定期查看代碼庫的非政策程式碼是否有變動。"
+msgstr "定期查看代碼庫的非政策程式碼的變動情況。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
@@ -1109,7 +1109,7 @@ msgstr "確保您了解政策，原始碼以及文件內容。"
 msgid ""
 "Check in regularly to understand how the non-source code in the codebase has"
 " changed."
-msgstr "定期查看代碼庫的非原始碼是否有變動。"
+msgstr "定期查看代碼庫的非原始碼的變動情況。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
@@ -1340,7 +1340,6 @@ msgid "{% assign sorted = site.pages | sort:\"order\" %}"
 msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
 
 #: ./index.md:block 4 (paragraph)
-#, fuzzy
 msgid ""
 "{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
 "!= \"index.md\" %}{% if page.title %}"
@@ -1349,7 +1348,6 @@ msgstr ""
 "!= \"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 5 (ordered list)
-#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 msgstr ""
@@ -1379,7 +1377,8 @@ msgstr "代碼庫必須說明如何私下回報安全問題， 達到負責任
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件必須與公共議題追蹤器以及已提交的代碼庫變動連結，例如「README」檔案。"
+msgstr "文件必須有與公共議題追蹤器以及已提交的代碼庫變動的連結，例如記錄在「README」"
+"檔案中。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
@@ -1721,8 +1720,8 @@ msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr "確認文件包含代碼庫使用的標準清單，以及所有標準的連結。若是沒有使用標準，也須"
-"清楚標示。"
+msgstr "確認文件有清單列出代碼庫使用的標準，而且代碼庫都有對應的連結可用。若是沒有使"
+"用標準，也須清楚標示。"
 
 #: ./open-standards.md:block 13 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
@@ -1981,7 +1980,7 @@ msgstr "貢獻內容應該由與貢獻者不同背景的人來審查。"
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr "版本管控系統在完成版的代碼庫中，不應該接受未經審查的貢獻內容。"
+msgstr "版本控制系統在完成版的代碼庫中，不應該接受未經審查的貢獻內容。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
@@ -2089,7 +2088,7 @@ msgstr "審查程式碼與其他一切事物時，都要遵守「四眼原則」
 msgid ""
 "Use a version control system or methodology that enables review and "
 "feedback."
-msgstr "使用具有審查與意見回饋功能的版本管控系統或方法。"
+msgstr "使用具有審查與意見回饋功能的版本控制系統或方法。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make delivering great code a shared objective."
@@ -2109,7 +2108,7 @@ msgstr "建立一個歡迎所有貢獻且每個人都能審查貢獻內容的文
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr "確保貢獻者在貢獻內容給代碼庫時，有獲得適當的注意。"
+msgstr "確保貢獻者在貢獻內容給代碼庫時，有獲得適當的協助。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
@@ -2152,7 +2151,7 @@ msgid ""
 "[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
 "gentle-art-of-patch-review/) by Sage Sharp."
 msgstr ""
-"Sage Sharp的[Patch審查的藝術](https://sage.thesharps.us/2014/09/01/"
+"Sage Sharp的[修補程式審查的藝術](https://sage.thesharps.us/2014/09/01/"
 "the-gentle-art-of-patch-review/)。"
 
 #: ./require-review.md:block 19 (unordered list)
@@ -2303,7 +2302,7 @@ msgstr "檢查是否有多方使用代碼庫，或是在多種情境下使用代
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr "確認代碼庫檔案與提交歷史紀錄沒有包含僅適用特定情況的數據。"
+msgstr "確認代碼庫檔案與提交歷史紀錄，沒有包含僅適用特定情況的數據。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid ""
@@ -2321,12 +2320,12 @@ msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr "確認利害關係人與企業業主瞭解代碼庫就是以重複利用為目標，因為這能減少程式碼負"
-"債，並且讓代碼庫能永續發展。"
+msgstr "確認利害關係人與企業業主瞭解，代碼庫就是以重複利用為目標，因為這能減少程式碼"
+"負債，並且讓代碼庫能永續發展。"
 
 #: ./reusable-and-portable-codebases.md:block 17 (paragraph)
 msgid "Source should be designed:"
-msgstr "原始碼的設計："
+msgstr "原始碼應經過設計："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
@@ -2388,7 +2387,7 @@ msgid ""
 "Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
 " the World Wide Web Consortium."
 msgstr ""
-"全球資訊網協會的[本土化 vs. 國際化](https://www.w3.org/International/"
+"全球資訊網協會的[本地化 vs. 國際化](https://www.w3.org/International/"
 "questions/qa-i18n)。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
@@ -2439,7 +2438,7 @@ msgstr "代碼庫當中，複雜的程式碼應該包含註解與文件。"
 msgid ""
 "Including sections on [understandable English](understandable-english-"
 "first.md) in the style guide is OPTIONAL."
-msgstr "風格指南可選擇加入[可理解英文](understandable-english-first.md)章節。"
+msgstr "風格指南可選擇加入[可理解的英文](understandable-english-first.md)章節。"
 
 #: ./style.md:block 7 (unordered list)
 msgid ""
@@ -2533,7 +2532,7 @@ msgstr "順序：10"
 
 #: ./understandable-english-first.md:block 2 (header)
 msgid "Use plain English"
-msgstr "使用簡明英語"
+msgstr "使用簡明的英語"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
@@ -2679,7 +2678,7 @@ msgstr "經常測試決策者與管理人員，瞭解他們是否理解您程式
 msgid ""
 "Ask someone outside of your context if they understand the content (for "
 "example, a developer working on a different codebase)."
-msgstr "請教情境不同的人(例如另一個代碼庫的開發人員)是否理解您的程式碼。"
+msgstr "請教身處不同情境的人(例如另一個代碼庫的開發人員)是否理解您的程式碼。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
@@ -2736,7 +2735,7 @@ msgstr "在所有版本訊息中，必須紀錄所有決策。"
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Every commit message MUST link to discussions and issues wherever possible."
-msgstr "每份版本訊息，都必須附上討論與議題的連結(若有)。"
+msgstr "每份版本訊息，都必須盡可能附上討論與議題的連結。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
@@ -2799,7 +2798,7 @@ msgstr "比較兩個不同版本"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "work on changes in parallel as a team before merging them together"
-msgstr "團隊可分兩邊研究程式碼需要變動的部分，之後再將內容整合"
+msgstr "團隊可以平行比對程式碼需要變動的部分，之後再將內容整合"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid ""
@@ -2888,7 +2887,7 @@ msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr "支持決策者，開發人員與設計師，明確公開他們如何改善代碼庫。代碼庫改善並非公關"
+msgstr "支持決策者，開發人員與設計師清楚表達其如何改善代碼庫。改善代碼庫不會造成公關"
 "風險。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)

From dcbedfc9ea8dfc2cf9bb1094f2267345215493c3 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Fri, 13 Jan 2023 15:07:03 +0000
Subject: [PATCH 13/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index a4ef7a93..929653b9 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-12 09:06+0000\n"
-"Last-Translator: WILT <interpreter.wilt@gmail.com>\n"
+"PO-Revision-Date: 2023-01-14 10:41+0000\n"
+"Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -25,7 +25,7 @@ msgstr "同捆政策與原始碼"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
-msgstr "必要條件"
+msgstr "需求規範"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""

From a092e725c51c740434e69327b6d6a22184e33e27 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Sat, 14 Jan 2023 16:37:56 +0000
Subject: [PATCH 14/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 234 ++++++++++++------------
 1 file changed, 122 insertions(+), 112 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 929653b9..b70de71f 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-14 10:41+0000\n"
+"PO-Revision-Date: 2023-01-14 16:42+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -17,11 +17,11 @@ msgstr ""
 #
 #: ./bundle-policy-and-code.md:block 1 (header)
 msgid "order: 2"
-msgstr "順序：2"
+msgstr "order: 2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr "同捆政策與原始碼"
+msgstr "合捆政策與原始碼"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
@@ -33,29 +33,29 @@ msgid ""
 "[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
 "is based on."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)必須包含作為[原始碼](../glossary."
-"md#code)基礎的[政策](../glossary.md#policy)。"
+"[代碼庫](../glossary.md#codebase)必須包含[原始碼](../glossary."
+"md#code)所根據的[政策](../glossary.md#policy)。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include all source code that the policy is based on, "
 "unless used for fraud detection."
-msgstr "代碼庫必須包含政策基於的所有原始碼（用於偵測詐騙的原始碼除外）。"
+msgstr "代碼庫必須包含所根據政策的所有原始碼，用於偵測詐騙的原始碼則可除外。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr "政策必須採用機器可閱讀且非模凌兩可的格式。"
+msgstr "政策應該採用機器可讀取且明確的格式。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
 msgstr "[持續整合](../glossary.md#continuous-integration) "
-"測試應該驗證原始碼與政策可一致執行。"
+"測試應該驗證原始碼與政策能一致執行。"
 
 #: ./bundle-policy-and-code.md:block 6 (header)
 msgid "Why this is important"
-msgstr "重要的原因"
+msgstr "此措施為何重要"
 
 #: ./bundle-policy-and-code.md:block 7 (paragraph)
 msgid ""
@@ -68,24 +68,25 @@ msgid ""
 " must choose to make or how to contribute additional configurability to the "
 "existing solution in order to adapt it to the new context."
 msgstr ""
-"取得原始碼與政策文件，才能瞭解，重複使用以及在代碼庫中進行協作。瞭解情境以及"
-"政策所在情境，才能瞭解代碼庫想要嘗試解決的問題，以及代碼庫可以如何解決這些問"
-"題。如欲評估是否在新的情境中採用代碼庫，組織需要瞭解必須改變的流程，或是如何"
-"提升現有解決方案的設定，才能適應新情境。"
+"如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼"
+"與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的"
+"問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼"
+"庫，則單位組織需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出的"
+"額外調整與設定，以適應新的情境。"
 
 #: ./bundle-policy-and-code.md:block 8 (header)
 msgid "What this does not do"
-msgstr "不包含的功能"
+msgstr "此措施辦不到的事"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid "Guarantee that a codebase will reflect the bundled policy."
-msgstr "保證代碼庫能反應同捆政策。"
+msgstr "保證代碼庫能反應合捆的政策。"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid ""
 "Make sure packages comply with the local technical infrastructure or legal "
 "framework of a given public organization."
-msgstr "確保套件符合本地技術基礎設施或是特定公共組織的法律框架。"
+msgstr "確保合捆套組內容符合地方性技術基礎設施，或是特定公共組織的法律框架。"
 
 #: ./bundle-policy-and-code.md:block 10 (header)
 msgid "How to test"
@@ -95,33 +96,33 @@ msgstr "測試方式"
 msgid ""
 "Confirm with a civil servant that all policy that the source code is based "
 "on is included."
-msgstr "與公務人員確認包含作為程式碼基礎的整個政策。"
+msgstr "與公務人員確認程式碼根據的所有政策內容都有包含在內。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr "與公務人員確認包含所有作為政策基礎的原始碼。"
+msgstr "與公務人員確認根據該政策的所有原始碼都有包含在內。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
-msgstr "確認政策是否由機器詮釋。"
+msgstr "確認政策內容是否能在機器上解讀。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid ""
 "Check the continuous integration tests for coherent execution of source code"
 " and policy pass."
-msgstr "確認原始碼與政策的執行能一致通過持續整合測試。"
+msgstr "確認原始碼與政策間的執行一致性能通過持續整合測試。"
 
 #: ./bundle-policy-and-code.md:block 12 (header)
 msgid "Policy makers: what you need to do"
-msgstr "決策者們：你們要執行的工作"
+msgstr "政策制定人員：需要的工作"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Collaborate with developers and designers to ensure there is no mismatch "
 "between policy code and source code."
-msgstr "與開發人員及設計師合作，確保政策程式碼與原始碼沒有錯配。"
+msgstr "與開發人員及設計師合作，確保政策法規與程式原始碼之間沒有不相符之處。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
@@ -132,9 +133,9 @@ msgid ""
 "which impact the development or the deployment context of the codebase for "
 "your organization."
 msgstr ""
-"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；倘若政策內"
-"文沒有英文版本，請提供英文版摘要。務必包含貴組織選擇遵守的標準，以及影響貴組"
-"織代碼庫開發或部署情境的任何組織流程。"
+"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
+"文沒有英文版，請提供英文版摘要。務必也同時包含貴單位組織所選擇遵守的各項標準"
+"，以及影響貴組織代碼庫開發或部署情境的任何組織流程。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -159,48 +160,48 @@ msgstr ""
 msgid ""
 "Track policy with [the same version control](version-control-and-history.md)"
 " and documentation used to track source code."
-msgstr "追蹤政策時，請使用與追蹤原始碼[同樣的版本控制](version-control-and-history."
-"md)。"
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](version-control-and-history."
+"md)與文件。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed and whether it still matches the [intentions of the "
 "policy](document-objectives.md)."
-msgstr "定期檢查代碼庫中非政策程式碼的變動，以及是否依舊符合[政策意圖](document-"
+msgstr "定期檢查代碼庫中非政策程式碼的變動，以及確認是否仍符合[政策意圖](document-"
 "objectives.md)。"
 
 #: ./bundle-policy-and-code.md:block 14 (header)
 msgid "Management: what you need to do"
-msgstr "管理人員：需要做的事"
+msgstr "管理人員：需要的工作"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr "讓決策者，開發人員與設計師參與開發並且在整個過程中保持聯繫。"
+msgstr "讓政策制定人員、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr "確保決策者，開發人員與設計師朝相同目標努力。"
+msgstr "確保政策制定人員、開發人員與設計師朝相同目標努力。"
 
 #: ./bundle-policy-and-code.md:block 16 (header)
 msgid "Developers and designers: what you need to do"
-msgstr "開發人員與設計師：需要做的事"
+msgstr "開發人員與設計師：需要的工作"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr "熟悉並且學會使用貴組織決策者所使用的流程模型標記法。"
+msgstr "熟悉並且學會貴組織政策制定人員所使用的流程模型標記法。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
 "Work together with policy makers to ensure there is no mismatch between "
 "policy code and source code."
-msgstr "與決策者合作，確保政策程式碼與原始碼沒有錯配。"
+msgstr "與政策制定人員一同合作，確保政策法規與程式原始碼之間沒有不相符之處。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid "Give feedback on how to make policy documentation more clear."
@@ -214,24 +215,25 @@ msgstr "延伸閱讀"
 msgid ""
 "[Free online tools for building BPMN, CMMN and DMN diagrams at "
 "bmpn.io](https://bpmn.io/) by Camunda."
-msgstr "Camunda [於 bmpn.io "
-"提供免費線上工具，可用於建構BPMN，CMMN與DMN圖表](https://bpmn.io/)。"
+msgstr ""
+"Camunda [於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN "
+"等模型與表記法圖表](https://bpmn.io/)。"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
-"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/"
+"Trisotech 提供的 [BPMN 快速指南](https://www.bpmnquickguide.com/"
 "view-bpmn-quick-guide/)。"
 
 #: ./code-in-the-open.md:block 1 (header)
 msgid "order: 1"
-msgstr "順序：1"
+msgstr "order: 1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "以開放精神編寫原始碼"
+msgstr "原始碼開放"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -239,36 +241,38 @@ msgid ""
 "[policy](../glossary.md#policy) in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
 msgstr ""
-"使用中[政策](../glossary.md#policy)的[原始碼](../glossary."
-"md#code)都必須要公開供民眾使用（用於偵測詐欺的原始碼除外）。"
+"任何使用中[政策](../glossary.md#policy)的所有程式[原始碼](../glossary."
+"md#code)都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "使用中軟體的所有原始碼都必須要公開供民眾使用（用於偵測詐欺的原始碼除外）。"
+msgstr "任何使用中軟體的所有程式原始碼都必須要公開（用於偵測詐欺的原始碼除外），且供"
+"民眾使用。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Contributors MUST NOT upload sensitive information regarding users, their "
 "organization or third parties to the "
 "[repository](../glossary.md#repository)."
-msgstr "貢獻者絕對不可上傳有關使用者，其組織或第三方的敏感性資訊到[儲存庫](../glossar"
-"y.md#repository)。"
+msgstr "貢獻者絕對禁止上傳與使用者及其單位組織，或與第三方相關的敏感性資訊到[儲存庫]("
+"../glossary.md#repository)中。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr "目前非使用中的原始碼（像是新版本，提案或較舊版本）都應該公開。"
+msgstr "目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Documenting which source code or policy underpins any specific interaction "
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
-msgstr "您可以選擇是否要紀錄[一般大眾](../glossary.md#general-"
-"public)與組織互動背後所採用的原始碼或政策。"
+msgstr ""
+"可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與單位組織之間"
+"可能發生的任何特定互動，其背後所採用的程式原始碼或支持的政策。"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
 msgid "Coding in the open:"
@@ -291,17 +295,17 @@ msgid ""
 "These aspects together create more opportunities for citizens to understand "
 "how software and policy impact their interactions with a public "
 "organization."
-msgstr "這些面向讓市民更有機會瞭解軟體與政策如何影響其與公共組織的互動。"
+msgstr "這些面向讓公民更有機會瞭解軟體與政策如何影響其與公共組織的互動。"
 
 #: ./code-in-the-open.md:block 11 (unordered list)
 msgid "Make source code or policy reusable."
-msgstr "讓原始碼或政策能重複使用。"
+msgstr "讓原始碼或政策可以重複使用。"
 
 #: ./code-in-the-open.md:block 11 (unordered list)
 msgid ""
 "Make the [codebase](../glossary.md#codebase) and the code within it "
 "understandable to as many people as possible."
-msgstr "讓更多人清楚瞭解[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
+msgstr "讓盡可能越多人能讀懂[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
@@ -309,8 +313,8 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr "確認使用中的每個版本都公布原始碼在網路上，且民眾不需要透過任何驗證或授權，就"
-"能在原始貢獻組織之外查看這些原始碼。"
+msgstr "確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形"
+"式的身分核對或授權，就能在原始貢獻組織之外，查看這些原始碼。"
 
 #: ./code-in-the-open.md:block 13 (unordered list)
 msgid ""
@@ -324,42 +328,42 @@ msgstr "檢查目前非使用中的原始碼是否有公開。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Develop policies in the open."
-msgstr "以開放精神開發政策。"
+msgstr "以開放精神發展政策。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Prioritize open and transparent policies."
-msgstr "以公開透明政策為優先。"
+msgstr "以公開透明的政策為優先。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid "Develop a culture that embraces openness, learning and feedback."
-msgstr "孕育一個重視開放，學習與意見回饋的文化。"
+msgstr "孕育擁抱開放、重視學習、歡迎意見回饋的文化。"
 
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid ""
 "Collaborate with external vendors and freelancers by working in the open."
-msgstr "公開作業，與外部供應商與自由業者合作。"
+msgstr "與外部供應商和自由業者以開放精神的方式協作。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr "審查人員提交歷史紀錄時，都應該確認內容沒有包含設定，使用者名稱，密碼，公開金"
-"鑰或其他生產系統中的實名資訊等敏感性資訊。"
+msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含設定、使用者名稱"
+"或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
 "Clearly split data and code, in order to meet the requirement about "
 "sensitive information above."
-msgstr "為符合上述敏感性資訊相關規定，請明確分開資料與程式碼。"
+msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
 "[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
 " by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
-"12/coding-in-the-open/)。"
+"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
+"12/coding-in-the-open/)》。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -368,9 +372,9 @@ msgid ""
 "guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
 "Service."
 msgstr ""
-"英國政府數位服務團的[程式碼應該公開或封閉的時機](https://www.gov.uk/"
+"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/"
 "government/publications/open-source-guidance/when-code-should-be-open-or-"
-"closed)。"
+"closed)》。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -379,9 +383,9 @@ msgid ""
 "guidance/security-considerations-when-coding-in-the-open) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
+"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
 "government/publications/open-source-guidance/security-considerations-when-"
-"coding-in-the-open)。"
+"coding-in-the-open)》。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
@@ -389,20 +393,20 @@ msgid ""
 "manual/technology/deploying-software-regularly) by the UK Government Digital"
 " Service."
 msgstr ""
-"英國政府數位服務團的[定期部署軟體](https://www.gov.uk/service-manual/"
-"technology/deploying-software-regularly)。"
+"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/"
+"technology/deploying-software-regularly)》。"
 
 #: ./code-in-the-open.md:block 21 (unordered list)
 msgid ""
 "[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
 "use-github/) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[政府數位服務團如何使用GitHub](https://gdstechnology.blog"
-".gov.uk/2014/01/27/how-we-use-github/)。"
+"英國政府數位服務團《[政府數位服務團如何使用 GitHub](https://gdstechnology."
+"blog.gov.uk/2014/01/27/how-we-use-github/)》。"
 
 #: ./continuous-integration.md:block 1 (header)
 msgid "order: 12"
-msgstr "順序：12"
+msgstr "order: 12"
 
 #: ./continuous-integration.md:block 2 (header)
 msgid "Use continuous integration"
@@ -412,19 +416,19 @@ msgstr "使用持續整合"
 msgid ""
 "All functionality in the source [code](../glossary.md#code) MUST have "
 "automated tests."
-msgstr "[原始碼](../glossary.md#code)的所有功能都必須有自動化測試。"
+msgstr "[原始碼](../glossary.md#code)中的所有功能都必須有自動化測試。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Contributions MUST pass all automated tests before they are admitted into "
 "the [codebase](../glossary.md#codebase)."
-msgstr "所有貢獻內容都必須通過自動化測試，才能上傳至[代碼庫](../glossary."
+msgstr "所有貢獻內容都必須先通過自動化測試，才能上傳至[代碼庫](../glossary."
 "md#codebase)。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST have guidelines explaining how to structure contributions."
-msgstr "代碼庫必須有說明貢獻內容結構的準則。"
+msgstr "代碼庫必須有說明貢獻內容結構的相關準則。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "The codebase MUST have active contributors."
@@ -434,22 +438,23 @@ msgstr "代碼庫必須有活躍貢獻者。"
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr "代碼庫準則應該規定每份貢獻內容都應只聚焦在單一議題上。"
+msgstr "代碼庫準則應該規定每次做出貢獻時都應只聚焦在單一議題上。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr "應該監督原始碼測試與文件涵蓋的範圍。"
+msgstr "應該監督原始碼測試與文件的涵蓋範圍。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr "可選擇是否測試[政策](../glossary.md#policy)跟文件與原始碼的一致性。"
+msgstr "可選擇是否測試[政策](../glossary."
+"md#policy)和文件，是否與原始碼間有一致性，或是反之亦然。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr "可選擇是否測試政策跟文件的風格以及失效連結。"
+msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結是否失效。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "Using [continuous integration](../glossary.md#continuous-integration):"
@@ -457,19 +462,19 @@ msgstr "使用[持續整合](../glossary.md#continuous-integration)："
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "allows you to quickly identify problems with the codebase,"
-msgstr "讓您能迅速找出代碼庫的問題，"
+msgstr "可以讓您快速找出代碼庫的問題所在，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "enables risk taking and focusing on problem solving while minimizing stress "
 "for the contributors,"
-msgstr "在減少貢獻者面臨的壓力的同時，允許承擔風險並且專注在解決問題上，"
+msgstr "能在降低貢獻者面臨壓力的同時，允許承擔風險並且專注在解決問題上，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "lowers barriers for new contributors by reducing the amount of understanding"
 " necessary to suggest changes,"
-msgstr "降低新貢獻者對整體內容理解的門檻，讓他們更容易建議變更，"
+msgstr "可降低新貢獻者對整體內容理解的門檻，讓他們更容易提出修改，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "leads to more maintainable code,"
@@ -477,25 +482,25 @@ msgstr "讓程式碼更容易維護，"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "speeds up the development cycle."
-msgstr "加快開發速度。"
+msgstr "能加速開發週期。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "Smaller, more regular contributions are typically easier to evaluate and "
 "lower risk compared to large infrequent changes."
-msgstr "內容較少但更規律提出的貢獻內容，通常較為容易評估，風險也低於內容龐大但鮮少提"
-"出的變更。"
+msgstr "修改內容較少，而時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大，累積"
+"很久才一次提出的變更。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
 "Codebases in active development more reliably provide opportunities for "
 "collaboration and feedback."
-msgstr "開發中的代碼庫較能提供協作與提供意見回饋的機會。"
+msgstr "活躍開發中的代碼庫較能提供協作與意見回饋的機會。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid ""
 "Create a fault tolerant infrastructure that will work and scale perfectly."
-msgstr "建立能夠順暢作業，擴展且能容錯的基礎架構。"
+msgstr "建立能夠順暢作業、可擴展，且能容錯的基礎架構。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Create meaningful tests."
@@ -507,7 +512,7 @@ msgstr "測試實際會發生的情境。"
 
 #: ./continuous-integration.md:block 9 (unordered list)
 msgid "Guarantee the code will deliver exactly the same policy result."
-msgstr "保證程式碼的成果會與政策相同。"
+msgstr "保證交付的程式碼與政策期望的成果確實相同。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid "Confirm that there are tests present."
@@ -516,18 +521,18 @@ msgstr "確認有測試可用。"
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that code coverage tools check that coverage is at 100% of the code."
-msgstr "確認程式碼覆蓋率工具能檢查100%的程式碼。"
+msgstr "確認程式碼覆蓋率工具能檢查到 100% 的程式碼。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that contributions are only admitted into the codebase after all of "
 "the tests are passed."
-msgstr "確認貢獻內容只有在通過所有測試後，才會上傳至代碼庫。"
+msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
 "Confirm that contribution guidelines explain how to structure contributions."
-msgstr "確認貢獻準則說明貢獻內容的結構。"
+msgstr "確認有貢獻準則說明貢獻內容的結構。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid ""
@@ -543,12 +548,13 @@ msgid ""
 "Involve management as well as developers and designers as early in the "
 "process as possible and keep them engaged throughout development of your "
 "policy."
-msgstr "儘早讓管理人員，開發人員與設計師參與，並且讓他們全程參與您政策的開發。"
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的發展程序"
+"。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
 "Make sure there are also automated tests set up for policy documentation."
-msgstr "確保政策文件也有自動化測試。"
+msgstr "確保政策文件也有設好自動化測試。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid "Fix policy documentation promptly if it fails a test."
@@ -558,49 +564,50 @@ msgstr "如果政策文件未能通過測試，請立即修正。"
 msgid ""
 "Make sure the code reflects any changes to the policy (see [Maintain version"
 " control](version-control-and-history.md))."
-msgstr "確保程式碼能反應出政策的任何變動(請參閱[維持版本控制](version-control-and-"
-"history.md))。"
+msgstr "確保程式碼能反映出政策的任何變動（請參閱[維護版本控制](version-control-and-"
+"history.md)）。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Make sure to test with real end users as quickly and often as possible."
-msgstr "迅速且頻繁地與真正的終端使用者進行測試。"
+msgstr "確保能儘快且經常給真正的終端使用者進行測試。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Plan the work to deliver small parts very often instead of large parts less "
 "frequently."
-msgstr "計畫頻繁地提交少量內容，而非久久一次繳交大量內容。"
+msgstr "以頻繁交付少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr "聘請能漸進式與計畫同步的顧問服務。"
+msgstr "聘請有能力處理漸進式交付並與跟上規劃進度的顧問服務。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
 "After a large failure, encourage publication of incident reports and public "
 "discussion of what was learned."
-msgstr "發生嚴重錯誤後，鼓勵公開事故報告以及公開討論事後學到的教訓。"
+msgstr "發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help management structure the work plan such that it can be delivered as "
 "small increments."
-msgstr "鼓勵管理階層擬定工作計畫，逐漸提高提交的內容數量。"
+msgstr "協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次交付。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help contributors limit the scope of their contributions and feature "
 "requests to be as small as reasonable."
-msgstr "協助貢獻者限制其貢獻內容與功能請求範圍。"
+msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Help management and policy makers test their contributions, for example by "
 "testing their contributions for broken links or style."
-msgstr "協助管理人員與決策者測試其貢獻內容，例如測試其貢獻內容的失效連結或風格。"
+msgstr "協助管理人員與政策制定人員測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣"
+"式。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
@@ -609,14 +616,16 @@ msgid ""
 "during testing. Forms of resource exhaustion such as running out of storage "
 "space and memory allocation failure are typical examples of difficult to "
 "create conditions."
-msgstr "編排程式碼時，要能夠將難以在測試環境下創造出來的情況，在測試過程中模擬出來。"
-"硬碟空間不足與記憶體配置失敗等資源耗盡情況，都是難以重現的情況。"
+msgstr ""
+"編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
+"來。例如硬碟空間不足、記憶體配置失敗敗等資源耗盡情況，都是難以創造的典型案例"
+"。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
 "Tune the test code coverage tools to avoid false alarms resulting from "
 "inlining or other optimizations."
-msgstr "調整程式碼覆蓋率測試工具，避免在整合入單一檔案或優化時造成假警報。"
+msgstr "調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid "Deploy often."
@@ -632,14 +641,14 @@ msgid ""
 "integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
 " by Martin Fowler."
 msgstr ""
-"Martin Fowler的[什麼是持續整合](https://www.martinfowler.com/articles/"
-"continuousIntegration.html)。"
+"Martin Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/"
+"continuousIntegration.html)》。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
 "[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
 "Humble."
-msgstr "Jez Humble的[什麼是持續交付](https://www.continuousdelivery.com/)。"
+msgstr "Jez Humble《[什麼是持續交付](https://www.continuousdelivery.com/)》。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
@@ -647,8 +656,8 @@ msgid ""
 "way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[使用持續交付](https://gds-way.cloudapps.digital/"
-"standards/continuous-delivery.html)。"
+"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/"
+"standards/continuous-delivery.html)》。"
 
 #: ./continuous-integration.md:block 19 (unordered list)
 msgid ""
@@ -656,12 +665,13 @@ msgid ""
 "regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
 "testing-your-service-regularly) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[品保：定期測試服務](https://www.gov.uk/service-manual/"
-"technology/quality-assurance-testing-your-service-regularly)。"
+"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/"
+"service-manual/technology/quality-assurance-testing-your-service-"
+"regularly)》。"
 
 #: ./document-maturity.md:block 1 (header)
 msgid "order: 16 redirect_from: - criteria/advertise-maturity"
-msgstr "順序：16 redirect_from: - criteria/advertise-maturity"
+msgstr "order: 16 redirect_from: - criteria/advertise-maturity"
 
 #: ./document-maturity.md:block 2 (header)
 msgid "Document codebase maturity"
@@ -2551,7 +2561,7 @@ msgstr ""
 msgid ""
 "All bundled policy not available in English MUST have an accompanying "
 "summary in English."
-msgstr "同捆政策如果沒有英語版本，則必須提供英語版摘要。"
+msgstr "任何合捆的政策如果沒有英語版本，則必須提供英語版摘要。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""

From c34184d0502da15019a9d14d6015b9c089c46f61 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Sat, 14 Jan 2023 17:23:29 +0000
Subject: [PATCH 15/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 503 +++++++++++++-----------
 1 file changed, 263 insertions(+), 240 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index b70de71f..0624b74a 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-14 16:42+0000\n"
+"PO-Revision-Date: 2023-01-16 16:59+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -21,7 +21,7 @@ msgstr "order: 2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr "合捆政策與原始碼"
+msgstr "政策與原始碼要合捆"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
@@ -50,8 +50,8 @@ msgstr "政策應該採用機器可讀取且明確的格式。"
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
-msgstr "[持續整合](../glossary.md#continuous-integration) "
-"測試應該驗證原始碼與政策能一致執行。"
+msgstr "[持續整合](../glossary.md#continuous-"
+"integration)測試應該驗證原始碼與政策能一致執行。"
 
 #: ./bundle-policy-and-code.md:block 6 (header)
 msgid "Why this is important"
@@ -86,7 +86,7 @@ msgstr "保證代碼庫能反應合捆的政策。"
 msgid ""
 "Make sure packages comply with the local technical infrastructure or legal "
 "framework of a given public organization."
-msgstr "確保合捆套組內容符合地方性技術基礎設施，或是特定公共組織的法律框架。"
+msgstr "確保合捆套組內容符合地方性技術基礎建設，或是特定公共組織的法律框架。"
 
 #: ./bundle-policy-and-code.md:block 10 (header)
 msgid "How to test"
@@ -102,7 +102,7 @@ msgstr "與公務人員確認程式碼根據的所有政策內容都有包含在
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr "與公務人員確認根據該政策的所有原始碼都有包含在內。"
+msgstr "與公務人員確認根據該政策而來的所有原始碼都有包含在內。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
@@ -150,7 +150,7 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
 msgstr ""
-"政策內容請使用明確且機器可閱讀的格式，像是[業務流程模型與標記法](https://en."
+"政策內容請使用明確且機器可讀取的格式，像是[業務流程模型與標記法](https://en."
 "wikipedia.org/wiki/"
 "Business_Process_Model_and_Notation)，[決策模型與標記法](https://en.wikipedia"
 ".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
@@ -217,7 +217,7 @@ msgid ""
 "bmpn.io](https://bpmn.io/) by Camunda."
 msgstr ""
 "Camunda [於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN "
-"等模型與表記法圖表](https://bpmn.io/)。"
+"等模型與表記法圖表](https://bpmn.io/)的免費線上工具。"
 
 #: ./bundle-policy-and-code.md:block 19 (unordered list)
 msgid ""
@@ -233,7 +233,7 @@ msgstr "order: 1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "原始碼開放"
+msgstr "原始碼要開放"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -248,16 +248,16 @@ msgstr ""
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "任何使用中軟體的所有程式原始碼都必須要公開（用於偵測詐欺的原始碼除外），且供"
-"民眾使用。"
+msgstr "任何使用中軟體的所有程式原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能"
+"供民眾取用。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "Contributors MUST NOT upload sensitive information regarding users, their "
 "organization or third parties to the "
 "[repository](../glossary.md#repository)."
-msgstr "貢獻者絕對禁止上傳與使用者及其單位組織，或與第三方相關的敏感性資訊到[儲存庫]("
-"../glossary.md#repository)中。"
+msgstr "貢獻者不得上傳與使用者及其單位組織，或與第三方相關的敏感性資訊到[儲存庫](../g"
+"lossary.md#repository)中。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -328,7 +328,7 @@ msgstr "檢查目前非使用中的原始碼是否有公開。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Develop policies in the open."
-msgstr "以開放精神發展政策。"
+msgstr "制定合乎開放精神的政策。"
 
 #: ./code-in-the-open.md:block 15 (unordered list)
 msgid "Prioritize open and transparent policies."
@@ -449,12 +449,12 @@ msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
 msgstr "可選擇是否測試[政策](../glossary."
-"md#policy)和文件，是否與原始碼間有一致性，或是反之亦然。"
+"md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結是否失效。"
+msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid "Using [continuous integration](../glossary.md#continuous-integration):"
@@ -548,7 +548,7 @@ msgid ""
 "Involve management as well as developers and designers as early in the "
 "process as possible and keep them engaged throughout development of your "
 "policy."
-msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的發展程序"
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序"
 "。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
@@ -582,7 +582,7 @@ msgstr "以頻繁交付少量部分內容的方式做專案規劃，而非久久
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr "聘請有能力處理漸進式交付並與跟上規劃進度的顧問服務。"
+msgstr "聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。"
 
 #: ./continuous-integration.md:block 15 (unordered list)
 msgid ""
@@ -679,56 +679,59 @@ msgstr "紀錄代碼庫成熟度"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
-msgstr "[代碼庫](../glossary.md#codebase) 必須註明版本。"
+msgstr "[代碼庫](../glossary.md#codebase)必須註明版本編號。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase that is ready to use MUST only depend on other codebases that "
 "are also ready to use."
-msgstr "與可用代碼庫具相依性的代碼庫必須也是立即可用。"
+msgstr "準備完成可供使用的代碼庫，必須只能依賴其他也已經準備完成可供使用的代碼庫。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase that is not yet ready to use MUST have one of the labels: "
 "prototype, alpha, beta or pre-release version."
-msgstr "尚未準備好使用的代碼庫必須有這些標籤之一：原型，預覽，測試或準完成版本。"
+msgstr "尚未準備好使用的代碼庫，必須有所列標籤之一：prototype、alpha、beta、pre-"
+"release 等版本進度。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr "代碼庫應該包含每次版本變動的紀錄，像是「CHANGELOG」。"
+msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔紀錄。"
 
 #: ./document-maturity.md:block 7 (paragraph)
 msgid ""
 "Clearly signalling a codebase's maturity helps others decide whether to "
 "reuse, invest in or contribute to it."
-msgstr "清楚標示代碼庫的成熟度有助於他人決定是否要重複使用，投資或貢獻給該代碼庫。"
+msgstr "清楚標示代碼庫的成熟度，有助於他人決定是否要重複使用、投資，或為該代碼庫做出"
+"貢獻。"
 
 #: ./document-maturity.md:block 9 (unordered list)
 msgid "Guarantee that others will use the [code](../glossary.md#code)."
-msgstr "保證他人會使用[程式碼](../glossary.md#code)。"
+msgstr "保證他人會來使用[程式碼](../glossary.md#code)。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase has a strategy for versioning which is documented."
-msgstr "確認代碼庫有版本化策略且有文件詳細記載該策略。"
+msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Confirm that it is clear where to get the newest version."
-msgstr "確認有註明最新版本的取得方法。"
+msgstr "確認有清楚表明最新版的取得位置。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase doesn't depend on any codebases marked with a less"
 " mature status."
-msgstr "確認代碼庫不需要仰賴成熟度標示較低的其他代碼庫。"
+msgstr "確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase is ready to use or labeled as prototype, alpha, "
 "beta or pre-release version."
-msgstr "確認代碼庫已準備好使用，或是標示為原型，預覽，測試或準完成版本。"
+msgstr "確認代碼庫已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-release "
+"等開發中版本。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Check that there is a log of changes."
@@ -738,62 +741,66 @@ msgstr "檢查是否有變更紀錄。"
 msgid ""
 "When developing [policy](../glossary.md#policy), understand that any code "
 "developed needs to be tested and improved before it can be put into service."
-msgstr "制定[政策](../glossary."
-"md#policy)時，記住任何開發出來的程式碼都必須經過測試與改善，才能夠投入服務。"
+msgstr "制定[政策](../glossary.md#policy)時，請記住任何開發出來的程式碼都必須先經過測"
+"試與改善，才能夠投入服務。"
 
 #: ./document-maturity.md:block 13 (unordered list)
 msgid ""
 "Consider versioning policy changes, especially when they trigger new "
 "versions of the source code."
-msgstr "考慮版本化政策的變動，特別是因此產生新版本原始碼的情況時。"
+msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "Make sure that services only rely on codebases of equal or greater maturity "
 "than the service. For example, don't use a beta codebase in a production "
 "service or a prototype codebase in a beta service."
-msgstr "要確認服務使用的代碼庫成熟度等同或高於服務本身。舉例來說，生產服務不要用測試"
-"版代碼庫，測試版服務不要用原型代碼庫。"
+msgstr ""
+"要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 測試版代碼庫，測試版服務不要使用 prototype "
+"原型代碼庫。"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "If the codebase is not ready for general use, work with the developers to "
 "ensure the codebase is properly labeled:"
-msgstr "若代碼庫尚未準備好使用，請與開發人員一起確保該代碼庫具備合適的標籤："
+msgstr "若代碼庫尚未準備好供一般使用，請與開發人員一起確保該代碼庫是否有標示適當標籤"
+"："
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "prototype: to test the look and feel, and to internally prove the concept of"
 " the technical possibilities,"
-msgstr "原型：測試外觀與體驗，並且從內部證明技術可能性的概念，"
+msgstr "prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術可行性的概念，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid "alpha: to do guided tests with a limited set of users,"
-msgstr "預覽：在使用者有限的情況下進行引導測試，"
+msgstr "alpha：內部測試，在限制的一群使用者中進行引導性測試，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "beta: to open up testing to a larger section of the [general "
 "public](../glossary.md#general-public), for example to test if the codebase "
 "works at scale,"
-msgstr "測試：讓更多[社會大眾](../glossary.md#general-"
-"public)參與測試，例如測試代碼庫在大規模運作下是否依舊順暢，"
+msgstr ""
+"beta：公開測試，讓更多[一般大眾](../glossary.md#general-"
+"public)參與測試，例如測試代碼庫在大規模操作下是否仍能運作，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid ""
 "pre-release version: code that is ready to be released but hasn't received "
 "formal approval yet."
-msgstr "準完成版本：已經準備好發布但尚未正式獲准的程式碼。"
+msgstr "pre-release：準發行版，已經準備好發行，但尚未獲得正式批准的程式碼。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
 "Add a prominent header to every interface that indicates the maturity level "
 "of the code."
-msgstr "在每個介面上加上顯著的標頭，標示程式碼的成熟度。"
+msgstr "在每個指示程式碼成熟度的介面中加上明顯的標頭。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid "Version all releases."
-msgstr "所有釋出的程式碼都要註明版本。"
+msgstr "所有發行的程式碼都要有版本編號。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
@@ -802,9 +809,9 @@ msgid ""
 "metadata (for example by using [git describe](https://git-scm.com/docs/git-"
 "describe))."
 msgstr ""
-"特別是在「滾動發行」的情況時，程式碼的版本資訊可能自動從[版本控制](../glossar"
-"y.md#version-control)系統元資料中擷取(例如使用[git describe](https://git-scm."
-"com/docs/git-describe))。"
+"特別是在採用「滾動發行」的情況下，程式碼的版本資訊可以根據[版本控制](../gloss"
+"ary.md#version-control)系統的中介資料自動衍生（例如使用[git describe](https"
+"://git-scm.com/docs/git-describe)）。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
@@ -812,21 +819,22 @@ msgid ""
 "advice/build-and-improve-services/service-design-and-delivery-process) by "
 "the Australian Digital Transformation Agency."
 msgstr ""
-"澳洲數位轉型局的[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
-"build-and-improve-services/service-design-and-delivery-process)。"
+"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
+"build-and-improve-services/service-design-and-delivery-process)》。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
 "[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
 "delivery) by the UK Government Digital Service."
-msgstr "英國政府數位服務團的[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
-"agile-delivery)。"
+msgstr ""
+"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
+"agile-delivery)》。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
 "[Semantic Versioning Specification](https://semver.org/) used by many "
 "codebases to label versions."
-msgstr "許多代碼庫使用[語意化版本控制規範](https://semver.org/)來標示版本。"
+msgstr "許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。"
 
 #: ./document-maturity.md:block 19 (unordered list)
 msgid ""
@@ -834,16 +842,16 @@ msgid ""
 "service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
 "the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[什麼是服務開發當中的探索，預覽，測試與上線階段？ [影片 "
-"0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)。"
+"英國政府數位服務團《[什麼是服務開發當中的探索、Alpha、Beta、上線階段？ [影片 "
+"0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)》。"
 
 #: ./document-objectives.md:block 1 (header)
 msgid "order: 8"
-msgstr "順序：8"
+msgstr "order: 8"
 
 #: ./document-objectives.md:block 2 (header)
 msgid "Document codebase objectives"
-msgstr "記錄代碼庫目標"
+msgstr "有代碼庫目標文件"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
@@ -851,8 +859,9 @@ msgid ""
 "objectives, like a mission and goal statement, that is understandable by "
 "developers and designers so that they can use or contribute to the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase) 必須包含目標文件，像是使命或目標宣言。開發"
-"人員與設計師需要能夠瞭解這些註解，讓他們能使用或對代碼庫做出貢獻。"
+"[代碼庫](../glossary.md#codebase)必須包含描寫目標的文件，像是主旨、使命或目標"
+"陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢"
+"獻。"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
@@ -865,17 +874,18 @@ msgstr "代碼庫文件應該清楚描述[政策](../glossary."
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr "可選擇為[一般民眾](../glossary.md#general-public)紀錄代碼庫目標。"
+msgstr "可選擇是否以文件紀錄給[一般民眾](../glossary.md#general-"
+"public)看的代碼庫目標。"
 
 #: ./document-objectives.md:block 7 (paragraph)
 msgid "Documenting codebase objectives:"
-msgstr "紀錄代碼庫目標："
+msgstr "以文件紀錄代碼庫目標："
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid ""
 "provides an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
-msgstr "提供簡易方法讓人判斷是否在當下或未來會對本代碼庫或其模組感興趣。"
+msgstr "提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。"
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid "helps scope your own development."
@@ -885,26 +895,26 @@ msgstr "幫助劃定您自己開發專案的範圍。"
 msgid ""
 "clearly communicates to other stakeholders and contributors the purpose of "
 "the codebase and the modules of which it is composed."
-msgstr "將代碼庫以及所包含模組的目的清楚告知其他利害關係人與貢獻者。"
+msgstr "將代碼庫以及所包含模組的目的用途，清楚告知其他利害關係人與貢獻者。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid "Guarantee that the codebase achieves the stated objective(s)."
-msgstr "保證代碼庫能達成其陳述性目標。"
+msgstr "保證代碼庫能達成其陳述的目標。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid "Guarantee contributions to the codebase."
-msgstr "保證會有人貢獻給代碼庫。"
+msgstr "保證會有人為代碼庫做出貢獻。"
 
 #: ./document-objectives.md:block 10 (unordered list)
 msgid ""
 "Prevent other codebases from attempting to achieve the same objectives."
-msgstr "預防其他代碼庫嘗試達成相同的目標。"
+msgstr "預防其他代碼庫試圖達成相同目標。"
 
 #: ./document-objectives.md:block 12 (unordered list)
 msgid ""
 "Confirm that the codebase documentation includes the codebase objectives, "
 "mission or goal."
-msgstr "確認代碼庫文件包含代碼庫目標與使命。"
+msgstr "確認代碼庫文件有包含代碼庫目標，或主旨、使命等。"
 
 #: ./document-objectives.md:block 12 (unordered list)
 msgid ""
@@ -916,27 +926,27 @@ msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
 msgid ""
 "Add the policy objectives to the codebase documentation, for example in the "
 "`README`."
-msgstr "將政策目標加入代碼庫文件中，例如在「README」當中。"
+msgstr "將政策目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./document-objectives.md:block 14 (unordered list)
 msgid ""
 "Include relevant policies which impact the community, codebase, and "
 "development like value and ethics based policies, for example accessibility "
 "or equal opportunity."
-msgstr "加入相關政策，這些政策會影響到社群，代碼庫以及無障礙或平等機會等價值或倫理基"
-"礎的政策的制定。"
+msgstr "納入會影響社會群體、代碼庫與開發目標的相關政策，例如可近用無障礙環境，或機會"
+"平等等價值或倫理取向的政策。"
 
 #: ./document-objectives.md:block 16 (unordered list)
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr "將組織或企業目標加入代碼庫文件中，例如在「README」當中。"
+msgstr "將組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./document-objectives.md:block 18 (unordered list)
 msgid ""
 "Add the technology and design objectives to the codebase documentation, for "
 "example in the `README`."
-msgstr "將技術與設計目標加入代碼庫文件中，例如在「README」當中。"
+msgstr "將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./document-objectives.md:block 20 (unordered list)
 msgid ""
@@ -944,16 +954,16 @@ msgid ""
 "objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
 " by Marek Hajduczenia."
 msgstr ""
-"Marek Hajduczenia的[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
-"RTPGE/public/may12/hajduczenia_01_0512.pdf)。"
+"Marek Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
+"RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
 
 #: ./documenting.md:block 1 (header)
 msgid "order: 9"
-msgstr "順序：9"
+msgstr "order: 9"
 
 #: ./documenting.md:block 2 (header)
 msgid "Document the code"
-msgstr "紀錄程式碼"
+msgstr "有程式碼文件"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -962,9 +972,9 @@ msgid ""
 "language clearly understandable for those that understand the purpose of the"
 " [code](../glossary.md#code)."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)，[政策](../glossary."
-"md#policy)以及原始碼的功能性，都必須清楚描述，讓懂[程式碼](../glossary."
-"md#code)目的的人也能夠瞭解。"
+"[代碼庫](../glossary.md#codebase)的所有功能、[政策](../glossary."
+"md#policy)及其來源，都必須以可清楚瞭解的用語描述，讓懂[程式碼](../glossary."
+"md#code)目的用途的人也能夠理解。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -976,37 +986,38 @@ msgstr "代碼庫文件必須說明如何安裝與執行原始碼。"
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr "代碼庫文件必須示範關鍵功能。"
+msgstr "代碼庫文件必須為關鍵功能舉出範例。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a high level description "
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
-msgstr "代碼庫文件應該包含詳盡的說明，讓[一般民眾](../glossary.md#general-"
-"public)與記者等廣泛的利害關係人都能明白。."
+msgstr ""
+"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-"
+"public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr "代碼庫文件中應該有一部分是用來說明如何安裝與執行單機版的原始碼。若有需要，也"
+msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也"
 "應該包含測試資料集。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr "代碼庫文件應該包含所有功能的示範。"
+msgstr "代碼庫文件應該包含所有功能的範例。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr "程式碼文件應該描述代碼庫的主要元件或模組（例如高階建築圖解），以及之間的關係"
-"。"
+msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架"
+"構圖表示。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -1018,21 +1029,22 @@ msgstr "應該要有針對文件品質的[持續整合](../glossary.md#continuou
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr "可選擇在代碼庫文件中，包含讓使用者會想要立即使用代碼庫的範例。"
+msgstr "可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid "Testing the code by using examples in the documentation is OPTIONAL."
-msgstr "可選擇使用文件中的範例來測試程式碼。"
+msgstr "可選擇是否以文件中的範例來測試程式碼。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "Users can start using and contributing more quickly."
-msgstr "使用者可以更快速地使用與貢獻給代碼庫。"
+msgstr "使用者可以更快速上手代碼庫的使用並做出貢獻。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid ""
 "You help people discover the codebase, especially people asking 'is there "
 "already code that does something like this'."
-msgstr "幫助他人找到這個代碼庫，特別是那些在尋找有如此功能代碼庫的人們。"
+msgstr "能幫助他人找到這個代碼庫，特別是那些在問「是不是已經有提供某某功能的程式碼」"
+"的人。"
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "This provides transparency into your organization and processes."
@@ -1043,39 +1055,39 @@ msgid ""
 "Contribute directly to more reusable, portable code (see [Create reusable "
 "and portable code](./reusable-and-portable-codebases.md))."
 msgstr ""
-"直接貢獻給更可重複使用以及容易攜帶的程式碼(請參閱[編寫可重複使用且容易攜帶的"
-"程式碼](./reusable-and-portable-codebases.md))。"
+"直接貢獻更可重複使用，以及更具可攜性的程式碼（請參閱[編寫可重複使用且具可攜性"
+"的程式碼](./reusable-and-portable-codebases.md)）。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr "確認其他利害關係人，其他公共組織的專業人士以及一般民眾，都能輕易閱讀與瞭解文"
-"件內容。"
+msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以"
+"清楚明白。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation describes how to install and run the source "
 "code."
-msgstr "確認文件說明如何安裝與執行原始碼。"
+msgstr "確認文件有說明如何安裝與執行原始碼。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Confirm that the documentation includes examples of the key functionality."
-msgstr "確認文件包含主要功能的示範。"
+msgstr "確認文件有包含主要功能的範例。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr "與一般民眾以及記者確認他們是否能明白文件當中艱深的說明。"
+msgstr "向一般民眾的成員以及記者確認他們是否能明白文件當中的精要說明。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the instructions for how to install and run a standalone version "
 "of the source code result in a running system."
-msgstr "檢查單機版原始碼的安裝與執行說明，確認能順利執行。"
+msgstr "檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid "Check that all functionality documented contains an example."
@@ -1085,15 +1097,15 @@ msgstr "檢查文件中列舉的所有功能都包含範例。"
 msgid ""
 "Check that the documentation includes a high level architectural diagram or "
 "similar."
-msgstr "檢查文件是否包含精細的架構圖。"
+msgstr "檢查文件中是否包含高層架構圖，或類似的組件關係圖表。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated from code, and links and images are "
 "tested."
-msgstr "確認整合測試有包含程式碼文件品質，例如確認文件是由程式碼生成，並檢查連結與圖"
-"片。"
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認由程式碼生成的文件，並檢查連結與"
+"圖片等。"
 
 #: ./documenting.md:block 13 (unordered list)
 msgid ""
@@ -1113,13 +1125,13 @@ msgstr "嘗試使用代碼庫。"
 msgid ""
 "Make sure you understand both the policy and source code as well as the "
 "documentation."
-msgstr "確保您了解政策，原始碼以及文件內容。"
+msgstr "確保您同時瞭解政策、原始碼以及文件內容。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-source code in the codebase has"
 " changed."
-msgstr "定期查看代碼庫的非原始碼的變動情況。"
+msgstr "定期查看代碼庫中非原始碼部分的變動情況。"
 
 #: ./documenting.md:block 17 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
@@ -1129,46 +1141,46 @@ msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr "Write the Docs的[文件指南](https://www.writethedocs.org/guide/)。"
+msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
 
 #: ./findability.md:block 1 (header)
 msgid "order: 14"
-msgstr "順序：14"
+msgstr "order: 14"
 
 #: ./findability.md:block 2 (header)
 msgid "Make the codebase findable"
-msgstr "讓民眾可以搜尋到此代碼庫"
+msgstr "可查詢得到代碼庫"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST be findable using a search "
 "engine by describing the problem it solves in natural language."
-msgstr "民眾在使用搜尋引擎時，如果以自然的語言描述代碼庫能解決的問題時，必須能搜尋到["
-"代碼庫](../glossary.md#codebase)。"
+msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，必須能搜尋得到[代碼"
+"庫](../glossary.md#codebase)。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "The codebase MUST be findable using a search engine by codebase name."
-msgstr "民眾用搜尋引擎搜尋代碼庫名稱時，必須能搜尋到代碼庫。"
+msgstr "在搜尋引擎查找代碼庫名稱時，必須能搜尋得到代碼庫。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr "維護者應該將代碼庫提交至相關軟體目錄上。"
+msgstr "維護人員應該將代碼庫提交至相關的軟體目錄上。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr "應該要為代碼庫架設網站，上面用潛在使用者(技術人員，政策專家與管理人員)偏好的"
-"術語描述代碼庫能解決的問題。"
+msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理"
+"人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD have a unique and persistent identifier where the entry "
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
-msgstr "代碼庫應該具備永久唯一識別碼，且內容需要提到主要貢獻者，[儲存庫](../glossary."
-"md#repository)，地點與網站。"
+msgstr "代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../gloss"
+"ary.md#repository)、位置、網站等。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
@@ -1176,32 +1188,32 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
-"代碼庫應該包含機器可閱讀的元資料說明，像是[publiccode.yml](https://github."
-"com/publiccodeyml/publiccode.yml)檔案這樣。"
+"代碼庫應該包含機器可讀取的中介資料說明，例如採用 [publiccode."
+"yml](https://github.com/publiccodeyml/publiccode.yml) 格式的檔案。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr "可選擇為代碼庫設定專屬網域名稱。"
+msgstr "可選擇是否為代碼庫設定專用的網域名稱。"
 
 #: ./findability.md:block 5 (unordered list)
 msgid "Regular presentations at conferences by the community are OPTIONAL."
-msgstr "可選擇定期在社群舉辦的會議中進行簡報。"
+msgstr "可選擇是否在社群舉辦的會議中定期進行簡報。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
 "Proactiveness is needed; just publishing a codebase and hoping it's found "
 "doesn't work."
-msgstr "必須主動出擊，不能只是發布代碼庫然後盼望網民會找到這個代碼庫。"
+msgstr "必須主動積極；不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid "A metadata description file increases discoverability."
-msgstr "元資料說明檔案會讓代碼庫更容易被發現。"
+msgstr "有中介資料說明檔案會讓代碼庫更容易被發現。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
 "The more findable a codebase is, the more potential new collaborators will "
 "find it."
-msgstr "代碼庫越容易被發現，更多的潛在協作者也會發現。"
+msgstr "一旦代碼庫越容易被發現，更多的潛在協作者也就找得到它。"
 
 #: ./findability.md:block 7 (unordered list)
 msgid ""
@@ -1211,35 +1223,35 @@ msgid ""
 "refer, cite, disambiguate and discover the codebase through third party "
 "tools."
 msgstr ""
-"內容豐富且包含永久唯一識別碼的元資料(像是刊載在維基數據或是FSF網站上)，讓代碼"
-"庫成為語意網的一部份。如此一來，他人就能更容易地透過第三方工具參考，引用，解"
-"釋與發現代碼庫。"
+"撰寫出良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，"
+"或是放到 FSF 自由軟體基金會的軟體目錄列表之中，使代碼庫成為語意網路中的一部份"
+"。如此一來，他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。"
 
 #: ./findability.md:block 9 (unordered list)
 msgid "Ensure new collaborators or replicators."
-msgstr "確認新協作者或複製者。"
+msgstr "確認新的協作人員或複製者。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by a plain English problem "
 "description."
-msgstr "確認在多個常用的搜尋引擎上，用直白的英文敘述問題，按下搜尋後代碼庫會出現在搜"
-"尋結果的第一頁。"
+msgstr "確認以白話英文敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
+"庫放在搜尋結果的第一頁中。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by a technical problem description."
-msgstr "確認在多個常用的搜尋引擎上，用技術性文字敘述問題，按下搜尋後代碼庫會出現在搜"
-"尋結果的第一頁。"
+msgstr "確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代"
+"碼庫放在搜尋結果的第一頁中。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by the codebase name."
-msgstr "確認在多個常用的搜尋引擎上，搜尋代碼庫名字後，代碼庫會出現在搜尋結果的第一頁"
-"。"
+msgstr "確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋"
+"結果的第一頁中。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid "Check for the codebase listing in relevant software catalogs."
@@ -1255,27 +1267,27 @@ msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
 msgid ""
 "Check unique and persistent identifier entries for mention of the major "
 "contributors."
-msgstr "檢查永久唯一識別碼有提到主要貢獻者。"
+msgstr "檢查永久唯一識別碼條目有提及主要貢獻者。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the repository location."
-msgstr "檢查永久唯一識別碼是否包含儲存庫地點。"
+msgstr "檢查永久唯一識別碼條目中有包含儲存庫位置。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the codebase website."
-msgstr "檢查永久唯一識別碼是否有列出代碼庫網站。"
+msgstr "檢查永久唯一識別碼條目有列出代碼庫網站。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid "Check for a machine-readable metadata description file."
-msgstr "檢查元資料說明檔案具有機器可讀的格式。"
+msgstr "檢查中介資料說明檔案是機器可讀取的格式。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
 "Contribute a description of the policy area or problem this codebase acts on"
 " or operates."
-msgstr "描述可應用此代碼庫的政策或問題。"
+msgstr "貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
@@ -1287,44 +1299,46 @@ msgstr "請對代碼庫不熟悉且不同領域的同儕來測試您的問題描
 msgid ""
 "Present on how the codebase implements the [policy](../glossary.md#policy) "
 "at relevent conferences."
-msgstr "在相關會議上介紹代碼庫如何執行[政策](../glossary.md#policy)。"
+msgstr "在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid ""
 "Budget for content design and Search Engine Optimization skills in the team."
-msgstr "為團隊編列內容設計與搜尋引擎優化技能的預算。"
+msgstr "為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid "Ensure people involved in the project present at relevant conferences."
-msgstr "確保專案人員在相關會議上介紹本專案。"
+msgstr "確保專案參與人員出席相關會議或作簡報介紹。"
 
 #: ./findability.md:block 15 (unordered list)
 msgid ""
 "Search trademark databases to avoid confusion or infringement before "
 "deciding the name."
-msgstr "決定名稱之前，先搜尋商標資料庫，避免名稱造成混淆或侵權的問題。"
+msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。"
 
 #: ./findability.md:block 17 (unordered list)
 msgid "Search engine optimization."
-msgstr "搜尋引擎優化。"
+msgstr "搜尋引擎最佳化。"
 
 #: ./findability.md:block 17 (unordered list)
 msgid "Suggest conferences to present at and present at them."
-msgstr "建議適合用來簡報的會議並且在這些會議中介紹代碼庫。"
+msgstr "推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
 "[Introduction to "
 "Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
 "Wikidata community."
-msgstr "維基數據社群的[維基數據簡介](https://www.wikidata.org/wiki/"
-"Wikidata:Introduction)。"
+msgstr ""
+"Wikidata 維基數據社群撰寫，《[維基數據簡介](https://www.wikidata.org/wiki/"
+"Wikidata:Introduction)》。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
 "[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
 "by the Free Softare Foundation."
-msgstr "自由軟體基金會的[FSF軟體型錄清單](https://directory.fsf.org/wiki/Main_Page)。"
+msgstr "FSF 自由軟體基金會，《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
+"Main_Page)》。"
 
 #: ./findability.md:block 19 (unordered list)
 msgid ""
@@ -1335,15 +1349,15 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
-"GO FAIR國際支援與合作辦公室的 "
-"[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-principles/"
-")，提出詳盡的清單，解釋哪些屬性會讓(元)資料更容易讓機器採取行動(也因此更容易"
-"被找到)。當中部分屬性可直接套用在代碼庫上，無法直接套用的，我們也需要研究代碼"
-"庫中與其對照的屬性。"
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
+"tps://www.go-fair.org/fair-principles/)》中，提供一份滿好的特性清單，解說哪些"
+"特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的"
+"部分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與"
+"其對應的特性要怎麼處理。"
 
 #: ./index.md:block 1 (header)
 msgid "Criteria"
-msgstr "標準"
+msgstr "準則"
 
 #: ./index.md:block 3 (paragraph)
 msgid "{% assign sorted = site.pages | sort:\"order\" %}"
@@ -1365,53 +1379,54 @@ msgstr ""
 
 #: ./make-contributing-easy.md:block 1 (header)
 msgid "order: 5"
-msgstr "順序：5"
+msgstr "order: 5"
 
 #: ./make-contributing-easy.md:block 2 (header)
 msgid "Make contributing easy"
-msgstr "讓對代碼庫貢獻代碼變得更容易"
+msgstr "做出貢獻要容易"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
 "that accepts suggestions from anyone."
-msgstr "[代碼庫](../glossary.md#codebase) 必須具備接受任何人建議的公共議題追蹤器。"
+msgstr "[代碼庫](../glossary.md#codebase)必須有個可以公開接受任何人建議的議題追蹤器。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include instructions for how to privately report security "
 "issues for responsible disclosure."
-msgstr "代碼庫必須說明如何私下回報安全問題， 達到負責任的揭露。"
+msgstr "代碼庫必須說明，如何私下回報安全性問題來達成負責任的揭露。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件必須有與公共議題追蹤器以及已提交的代碼庫變動的連結，例如記錄在「README」"
-"檔案中。"
+msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在"
+"「`README`」檔案中。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr "代碼庫必須有與使用者以及開發人員的溝通管道，像是電子郵件清單。"
+msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵遞"
+"論壇）。"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
 "The documentation SHOULD include instructions for how to report potentially "
 "security sensitive issues on a closed channel."
-msgstr "文件應該說明如何透過封閉的管道通報潛在的安全與敏感性問題。"
+msgstr "文件應該說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid ""
 "Enables users to fix problems and add features to the shared codebase "
 "leading to better, more reliable and feature rich software."
-msgstr "讓使用者能夠修復問題以及新增共享代碼庫的功能，讓軟體更好，更可靠且功能更豐富"
-"。"
+msgstr "讓使用者能夠為共享的代碼庫修復問題與新增功能，能讓軟體變得更好、更可靠、功能"
+"更豐富。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid "Allows collaborative uptake of shared digital infrastructure."
-msgstr "允許共同使用共享數位基礎設施。"
+msgstr "讓人們能以協作方式採用共享的數位基礎建設。"
 
 #: ./make-contributing-easy.md:block 7 (unordered list)
 msgid "Helps users decide to use one codebase over another."
@@ -1423,53 +1438,54 @@ msgstr "保證其他人會重複使用代碼庫。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid "Confirm that there is a public issue tracker."
-msgstr "確認有公共議題追蹤器。"
+msgstr "確認有公開的議題追蹤器。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that there are instructions for privately reporting security issues."
-msgstr "確認有說明如何私下通報安全問題。"
+msgstr "確認有說明如何私下通報安全性問題。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase contains links to the public issue tracker and "
 "submitted codebase changes."
-msgstr "確認代碼庫有公共議題追蹤器以及已提交的代碼庫變動的連結。"
+msgstr "確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。"
 
 #: ./make-contributing-easy.md:block 11 (unordered list)
 msgid ""
 "Confirm that it is possible to participate in a discussion with other users "
 "and developers about the software using channels described in the codebase."
-msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員討論。"
+msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
 
 #: ./make-contributing-easy.md:block 13 (unordered list)
 msgid ""
 "Track [policy](../glossary.md#policy) issues in the codebase, so that a "
 "relevant external policy expert can volunteer help."
 msgstr "追蹤代碼庫中的[政策](../glossary."
-"md#policy)問題，讓相關外部政策專家也能自願協助。"
+"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
 
 #: ./make-contributing-easy.md:block 15 (unordered list)
 msgid ""
 "Track management issues in the codebase, so that external managers with "
 "relevant experience can volunteer help."
-msgstr "追蹤代碼庫中的管理問題，讓相關外部政策專家也能自願協助。"
+msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
 
 #: ./make-contributing-easy.md:block 15 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr "支持您經驗豐富的政策制定者，開發人員與設計師來持續貢獻代碼給代碼庫。"
+msgstr "支持您經驗豐富的政策制定人員、開發人員與設計師，盡可能使其為代碼庫持續做出長"
+"久貢獻。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid "Respond promptly to requests."
-msgstr "迅速回應要求。"
+msgstr "快速回應請求。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid ""
 "Keep your management informed of the time and resources you require to "
 "support other contributors."
-msgstr "持續告知管階層您需要用來支援其他貢獻者的時間與資源。"
+msgstr "持續告知管理階層您在支援其他貢獻者時所需要的時間與資源。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
@@ -1477,67 +1493,68 @@ msgid ""
 "project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
 "to-your-open-source-project-1ebf) by Joel Hans."
 msgstr ""
-"Joel Hans的[如何鼓勵他人貢獻一流的代碼給您的開源專案](https://dev.to/"
-"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
-"project-1ebf)。"
+"Joel Hans《[如何引發他人為您的開源專案做出優秀貢獻](https://dev.to/joelhans/"
+"how-to-inspire-exceptional-contributions-to-your-open-source-project-"
+"1ebf)》。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
 "[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
 "benefits-of-coding-in-the-open/) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
-"2017/09/04/the-benefits-of-coding-in-the-open/)。"
+"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
+"2017/09/04/the-benefits-of-coding-in-the-open/)》。"
 
 #: ./open-licenses.md:block 1 (header)
 msgid "order: 13"
-msgstr "順序：13"
+msgstr "order: 13"
 
 #: ./open-licenses.md:block 2 (header)
 msgid "Publish with an open license"
-msgstr "取得公開授權並公布程式碼"
+msgstr "採用開放授權發行"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "All [code](../glossary.md#code) and documentation MUST be licensed such that"
 " it may be freely reusable, changeable and redistributable."
-msgstr "必須取得所有[程式碼](../glossary."
-"md#code)與文件的授權，讓所有人可以免費重複利用，變更與散布。"
+msgstr "所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以可自由重複使用、可"
+"自由修改、可自由再次散布的授權條款。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Software source code MUST be licensed under an [OSI-approved or FSF "
 "Free/Libre license](https://spdx.org/licenses/)."
-msgstr "軟體原始碼必須取得[開放原始碼促進會認證或FSF Free/Libre授權](https://spdx."
-"org/licenses/)。"
+msgstr ""
+"軟體原始碼必須採用[經 OSI 開源促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid "All code MUST be published with a license file."
-msgstr "所有程式碼都必須放在授權檔案中發布。"
+msgstr "所有程式碼皆必須搭配授權條款檔案一併發行。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the [codebase](../glossary.md#codebase)."
-msgstr "不得要求貢獻者將其貢獻代碼的著作權轉移給[代碼庫](../glossary.md#codebase)。"
+msgstr "不得要求貢獻者將其貢獻的程式碼著作權轉讓給[代碼庫](../glossary.md#codebase)。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr "代碼庫中所有原始碼檔案都應該包含機器可判讀的著作權與授權聲明。"
+msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀取的著作權聲明與授權條款標頭內容。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
 "Having multiple licenses for different types of code and documentation is "
 "OPTIONAL."
-msgstr "可選擇為不同類型的程式碼與文件取得多個授權。"
+msgstr "可選擇是否為不同類型的程式碼與文件採用多重授權條款。"
 
 #: ./open-licenses.md:block 7 (unordered list)
 msgid ""
 "Makes it possible for anyone to see the code and know that they can and how "
 "they can reuse it."
-msgstr "讓任何看到程式碼的人，都能知道可以與如何重複利用這些程式碼。"
+msgstr "讓任何人都可以查看程式碼，並知道他們可以與該如何重複利用這些程式碼。"
 
 #: ./open-licenses.md:block 9 (unordered list)
 msgid "Prevent use of the code by any specific actors."
@@ -1545,7 +1562,7 @@ msgstr "預防任何特定行為人使用程式碼。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid "Confirm that the codebase is clearly licensed."
-msgstr "確認代碼庫確實有取得授權。"
+msgstr "確認代碼庫有清楚給予授權條款。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
@@ -1554,47 +1571,50 @@ msgid ""
 "documentation [conforms to the Open "
 "Definition](https://opendefinition.org/licenses/)."
 msgstr ""
-"確認原始碼授權有在[開放原始碼促進會認證或FSF Free/Libre授權清單](https://spdx"
-".org/licenses/)，以及文件授權[符合開放定義](https://opendefinition.org/"
+"確認原始碼的授權條款有列於[經 OSI 開源促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/"
+")，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/"
 "licenses/)。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid "Confirm that the licenses used in the codebase are included as files."
-msgstr "確認代碼庫有包含其使用授權的檔案。"
+msgstr "確認代碼庫中有包含其採用的授權條款檔案。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
 "Confirm that contribution guidelines and "
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
-msgstr "確認貢獻指南以及[儲存庫](../glossary."
-"md#repository)的設定不要求貢獻者轉移著作權。"
+msgstr "確認貢獻指南中，以及[儲存庫](../glossary."
+"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
 
 #: ./open-licenses.md:block 11 (unordered list)
 msgid ""
 "Check for machine-readable license checking in the codebase [continuous "
 "integration](../glossary.md#continuous-integration) tests."
-msgstr "在代碼庫[持續整合](../glossary.md#continuous-"
-"integration)測試中，確認是否有檢查機器可判讀授權的功能。"
+msgstr ""
+"在代碼庫[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查授權內容為機器可讀取的檢查項目。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
 "Develop [policy](../glossary.md#policy) that requires code to be [open "
 "source](../glossary.md#open-source)."
-msgstr "制定要求程式碼為 [開源](../glossary.md#open-source)的[政策](../glossary."
-"md#policy)。"
+msgstr ""
+"制定要求程式碼必須採用[開源](../glossary.md#open-"
+"source)授權的[政策](../glossary.md#policy)。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
 "Develop policy that disincentivizes non-open source code and technology in "
 "procurement."
-msgstr "制定政策，減少採購非開源的程式碼與科技。"
+msgstr "制定抑制採購非開源授權程式碼與非開放科技的政策。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
 "Only work with open source vendors that deliver their code by publishing it "
 "under an open source license."
-msgstr "只與透過開源授權發布其程式碼的開源供應商合作。"
+msgstr "只與能採用開源授權交付與發行其程式碼的開源軟體供應商合作。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
@@ -1604,25 +1624,26 @@ msgid ""
 "NOT freely reusable, changeable and redistributable and don't fulfill these "
 "requirements."
 msgstr ""
-"請注意：雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件上"
-"，具有非商業性或禁止改作的授權代表不得免費重複使用，變更與散布，因此不符合規"
-"定。"
+"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作"
+"品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用"
+"、自由修改、自由再次散布等，因此未能符合規定。"
 
 #: ./open-licenses.md:block 17 (unordered list)
 msgid "Add a new `license` file to every new codebase created."
-msgstr "建立新的代碼庫時，都要加入新的「授權」檔案。"
+msgstr "每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。"
 
 #: ./open-licenses.md:block 17 (unordered list)
 msgid ""
 "Add a copyright notice and a license header to every new source code file "
 "created."
-msgstr "建立新的原始碼檔案時，都要加入著作權與授權聲明。"
+msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
 "[Open source definition](https://opensource.org/osd) by the Open Source "
 "Initiative, all open source licenses meet this definition."
-msgstr "所有開源授權都符合開放原始碼促進會的[開源定義](https://opensource.org/osd)。"
+msgstr "開源促進會所發表的《[開放原始碼定義](https://opensource.org/"
+"osd)》，所有開放原始碼授權條款皆符合這套定義。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
@@ -1630,8 +1651,8 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
-"紐西蘭CC Aotearoa的[創用CC介紹動畫影片](https://creativecommons.org/about/"
-"videos/creative-commons-kiwi)。"
+"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)》。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
@@ -1639,23 +1660,24 @@ msgid ""
 "Software Foundation Europe for unambiguous, human-readable and machine-"
 "readable copyright and licensing information."
 msgstr ""
-"歐洲自由軟體基金會的[REUSE倡議規範](https://reuse.software/spec/"
-")，是規範明確，人類可讀以及機器可讀的著作權與授權資訊。"
+"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
+")》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./open-licenses.md:block 19 (unordered list)
 msgid ""
 "[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
 " standardized, machine-readable abbreviations for most licenses."
-msgstr "Linux基金會的[SPDX授權清單](https://spdx.org/licenses/"
-")，提供多數授權的標準化且機器可讀的縮寫。"
+msgstr ""
+"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
+")提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
 
 #: ./open-standards.md:block 1 (header)
 msgid "order: 11"
-msgstr "順序：11"
+msgstr "order: 11"
 
 #: ./open-standards.md:block 2 (header)
 msgid "Use open standards"
-msgstr "使用開源標準"
+msgstr "採用開放標準"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
@@ -1664,102 +1686,103 @@ msgid ""
 "standard](../glossary.md#open-standard) that meets the [Open Source "
 "Initiative Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)要能進行資料交換，就必須使用符合 "
-"[開放原始碼促進會開源標準規定](https://opensource.org/"
-"osr)的[開源標準](../glossary.md#open-standard)。"
+"[代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合["
+"開源促進會其開放標準需求規範](https://opensource.org/"
+"osr)的[開放標準](../glossary.md#open-standard)。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any non-open standards used MUST be recorded clearly as such in the "
 "documentation."
-msgstr "若使用非開源標準，就必須在文件中清楚標示。"
+msgstr "如果有使用到任何的非開放標準，則必須在文件中清楚記錄。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr "代碼庫使用的任何標準必須在文件中清楚標示，並且附上該標準的連結。"
+msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的"
+"連結。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr "代碼庫使用的非開源標準不得妨礙代碼庫的協作與重複使用。"
+msgstr "代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "If no existing open standard is available, effort SHOULD be put into "
 "developing one."
-msgstr "如果沒有開源標準可用，則應該開發新標準。"
+msgstr "如果還沒有已存在的開放標準可採用，則應該投入開發新標準。"
 
 #: ./open-standards.md:block 5 (unordered list)
 msgid ""
 "Standards that are machine testable SHOULD be preferred over those that are "
 "not."
-msgstr "應該優先選擇可用機器測試的標準。"
+msgstr "採用標準時，應該優先選擇可經機器測試的標準。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid "Creates interoperability between systems."
-msgstr "讓系統可以互通。"
+msgstr "為不同的系統之間建立互通性。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid "Reduces possible vendor lock-in."
-msgstr "降低可能的廠商陷阱。"
+msgstr "降低廠商套牢的可能性。"
 
 #: ./open-standards.md:block 7 (unordered list)
 msgid ""
 "Guarantees access to the knowledge required to reuse and contribute to the "
 "codebase."
-msgstr "保證讓每個人都能獲得相關知識，學會重複利用以及貢獻代碼給代碼庫。"
+msgstr "保證可以取得重複利用與貢獻代碼庫所需的知識。"
 
 #: ./open-standards.md:block 9 (unordered list)
 msgid "Make it understandable how to use the software."
-msgstr "說明如何使用軟體。"
+msgstr "讓軟體的操作方法變得可以瞭解。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid "Confirm that data exchange follows an OSI approved open standard."
-msgstr "確認資料交換遵守OSI認證的開源標準。"
+msgstr "確認資料交換遵守 OSI 開源促進會批准的開放標準。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid ""
 "Confirm that any non-open standards used are clearly documented as such."
-msgstr "確認若有使用非開源標準，都有清楚標示。"
+msgstr "確認若有採用任何的非開放標準，皆有清楚記錄在文件中。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr "確認文件有清單列出代碼庫使用的標準，而且代碼庫都有對應的連結可用。若是沒有使"
-"用標準，也須清楚標示。"
+msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的生效連結；或沒有採用"
+"任何標準時，則留下聲明。"
 
 #: ./open-standards.md:block 13 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
-msgstr "盡可能規定要求使用開源標準。"
+msgstr "以政策要求盡可能在任何情況下使用開放標準。"
 
 #: ./open-standards.md:block 13 (unordered list)
 msgid "Prohibit procurement of technology that does not use open standards."
-msgstr "禁止採購不支援開源標準的科技。"
+msgstr "禁止採購不採用開放標準的技術科技。"
 
 #: ./open-standards.md:block 15 (unordered list)
 msgid ""
 "Consider including open standard compliance assessment in "
 "[code](../glossary.md#code) reviews."
-msgstr "考慮在[程式碼](../glossary.md#code)審核中加入開源標準遵循評估。"
+msgstr "考慮在[程式碼](../glossary.md#code)審核中納入開放標準依循評估。"
 
 #: ./open-standards.md:block 17 (unordered list)
 msgid ""
 "Add [continuous integration](../glossary.md#continuous-integration) tests "
 "for compliance with the standards."
-msgstr "在標準遵循方面，加入[持續整合](../glossary.md#continuous-integration)測試。"
+msgstr "將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。"
 
 #: ./open-standards.md:block 17 (unordered list)
 msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr "檢查提交說明與其他[儲存庫](../glossary."
-"md#repository)資源是否有提到開源標準，並且再次確認有列出標準的內容。"
+msgstr "審查提交紀錄與其他[儲存庫](../glossary."
+"md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
 
 #: ./open-standards.md:block 19 (unordered list)
 msgid ""
@@ -1767,13 +1790,13 @@ msgid ""
 "standards-principles/open-standards-principles), "
 "[policy](../glossary.md#policy) paper of the UK Cabinet Office."
 msgstr ""
-"英國內閣辦公室的[開源標準原則](https://www.gov.uk/government/publications/"
-"open-standards-principles/open-standards-principles)與[政策](../glossary."
-"md#policy)論文。"
+"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/"
+"publications/open-standards-principles/open-standards-"
+"principles)》[政策](../glossary.md#policy)報告。"
 
 #: ./open-to-contributions.md:block 1 (header)
 msgid "order: 4"
-msgstr "順序：4"
+msgstr "order: 4"
 
 #: ./open-to-contributions.md:block 2 (header)
 msgid "Welcome contributors"
@@ -2483,7 +2506,7 @@ msgid ""
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
 "為[政策](../glossary.md#policy)與文件建立與遵守風格指南，並且持續改善，同時可"
-"在代碼庫的「CONTRIBUTING」或「README」檔案中註明。"
+"在代碼庫的「`CONTRIBUTING`」或「`README`」檔案中註明。"
 
 #: ./style.md:block 15 (unordered list)
 msgid ""
@@ -2505,10 +2528,10 @@ msgid ""
 "evolving this documentation into engineering guidelines."
 msgstr ""
 "代碼庫若沒有工程指南或其他貢獻者指南，先在[儲存庫](../glossary.md#repository)"
-"中的「CONTRIBUTING」或「README」檔案加入文件，描述目前在指南方面的進展。文件"
-"主要目的在於表達設計偏好，命名規則等機器不容易檢查的內容。指南應該包含貢獻[程"
-"式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括原始"
-"碼，測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
+"中的「`CONTRIBUTING`」或「`README`」檔案加入文件，描述目前在指南方面的進展。"
+"文件主要目的在於表達設計偏好，命名規則等機器不容易檢查的內容。指南應該包含貢"
+"獻[程式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括"
+"原始碼，測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
 
 #: ./style.md:block 18 (paragraph)
 msgid "Additionally:"

From bbb66b8d0e8e0e14b8ecec991bc4702663eb9317 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 17 Jan 2023 03:26:58 +0000
Subject: [PATCH 16/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 157 ++++++++++++------------
 1 file changed, 79 insertions(+), 78 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 0624b74a..a1714e99 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-16 16:59+0000\n"
+"PO-Revision-Date: 2023-01-17 04:14+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -21,7 +21,7 @@ msgstr "order: 2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr "政策與原始碼要合捆"
+msgstr "合捆政策與原始碼"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
@@ -40,11 +40,11 @@ msgstr ""
 msgid ""
 "The codebase MUST include all source code that the policy is based on, "
 "unless used for fraud detection."
-msgstr "代碼庫必須包含所根據政策的所有原始碼，用於偵測詐騙的原始碼則可除外。"
+msgstr "代碼庫必須包含根據政策而來的所有原始碼，用於偵測詐騙的原始碼則可除外。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr "政策應該採用機器可讀取且明確的格式。"
+msgstr "政策應該採用機器可讀且明確的格式。"
 
 #: ./bundle-policy-and-code.md:block 5 (unordered list)
 msgid ""
@@ -71,8 +71,8 @@ msgstr ""
 "如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼"
 "與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的"
 "問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼"
-"庫，則單位組織需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出的"
-"額外調整與設定，以適應新的情境。"
+"庫，則單位組織需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額"
+"外調整與設定，以適應新的情境。"
 
 #: ./bundle-policy-and-code.md:block 8 (header)
 msgid "What this does not do"
@@ -86,7 +86,7 @@ msgstr "保證代碼庫能反應合捆的政策。"
 msgid ""
 "Make sure packages comply with the local technical infrastructure or legal "
 "framework of a given public organization."
-msgstr "確保合捆套組內容符合地方性技術基礎建設，或是特定公共組織的法律框架。"
+msgstr "確保成套合捆內容符合地方性技術基礎建設，或是特定公共組織的法律架構。"
 
 #: ./bundle-policy-and-code.md:block 10 (header)
 msgid "How to test"
@@ -102,7 +102,7 @@ msgstr "與公務人員確認程式碼根據的所有政策內容都有包含在
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr "與公務人員確認根據該政策而來的所有原始碼都有包含在內。"
+msgstr "與公務人員確認根據政策而來的所有原始碼都有包含在內。"
 
 #: ./bundle-policy-and-code.md:block 11 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
@@ -116,13 +116,13 @@ msgstr "確認原始碼與政策間的執行一致性能通過持續整合測試
 
 #: ./bundle-policy-and-code.md:block 12 (header)
 msgid "Policy makers: what you need to do"
-msgstr "政策制定人員：需要的工作"
+msgstr "政策制定者：需要的工作"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
 "Collaborate with developers and designers to ensure there is no mismatch "
 "between policy code and source code."
-msgstr "與開發人員及設計師合作，確保政策法規與程式原始碼之間沒有不相符之處。"
+msgstr "與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid ""
@@ -135,7 +135,7 @@ msgid ""
 msgstr ""
 "提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
 "文沒有英文版，請提供英文版摘要。務必也同時包含貴單位組織所選擇遵守的各項標準"
-"，以及影響貴組織代碼庫開發或部署情境的任何組織流程。"
+"，以及影響貴單位組織代碼庫開發或部署情境的任何組織流程。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -150,7 +150,7 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
 msgstr ""
-"政策內容請使用明確且機器可讀取的格式，像是[業務流程模型與標記法](https://en."
+"政策內容請使用明確且機器可讀的格式，像是[業務流程模型與標記法](https://en."
 "wikipedia.org/wiki/"
 "Business_Process_Model_and_Notation)，[決策模型與標記法](https://en.wikipedia"
 ".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
@@ -179,13 +179,13 @@ msgstr "管理人員：需要的工作"
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr "讓政策制定人員、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
+msgstr "讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
 
 #: ./bundle-policy-and-code.md:block 15 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr "確保政策制定人員、開發人員與設計師朝相同目標努力。"
+msgstr "確保政策制定者、開發人員與設計師朝相同目標努力。"
 
 #: ./bundle-policy-and-code.md:block 16 (header)
 msgid "Developers and designers: what you need to do"
@@ -195,13 +195,13 @@ msgstr "開發人員與設計師：需要的工作"
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr "熟悉並且學會貴組織政策制定人員所使用的流程模型標記法。"
+msgstr "熟悉並且學會貴單位組織政策制定者所使用的流程模型標記法。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
 "Work together with policy makers to ensure there is no mismatch between "
 "policy code and source code."
-msgstr "與政策制定人員一同合作，確保政策法規與程式原始碼之間沒有不相符之處。"
+msgstr "與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid "Give feedback on how to make policy documentation more clear."
@@ -233,7 +233,7 @@ msgstr "order: 1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "原始碼要開放"
+msgstr "將原始碼開放"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -241,15 +241,15 @@ msgid ""
 "[policy](../glossary.md#policy) in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
 msgstr ""
-"任何使用中[政策](../glossary.md#policy)的所有程式[原始碼](../glossary."
+"任何使用中的[政策](../glossary.md#policy)所有[原始碼](../glossary."
 "md#code)都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "任何使用中軟體的所有程式原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能"
-"供民眾取用。"
+msgstr "任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
+"眾取用。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -272,7 +272,7 @@ msgid ""
 "organization is OPTIONAL."
 msgstr ""
 "可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與單位組織之間"
-"可能發生的任何特定互動，其背後所採用的程式原始碼或支持的政策。"
+"可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
 msgid "Coding in the open:"
@@ -606,8 +606,8 @@ msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡
 msgid ""
 "Help management and policy makers test their contributions, for example by "
 "testing their contributions for broken links or style."
-msgstr "協助管理人員與政策制定人員測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣"
-"式。"
+msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式"
+"。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
@@ -940,7 +940,7 @@ msgstr "納入會影響社會群體、代碼庫與開發目標的相關政策，
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr "將組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
+msgstr "將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./document-objectives.md:block 18 (unordered list)
 msgid ""
@@ -1048,7 +1048,7 @@ msgstr "能幫助他人找到這個代碼庫，特別是那些在問「是不是
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "This provides transparency into your organization and processes."
-msgstr "讓貴組織與其流程資訊更透明。"
+msgstr "讓貴單位組織與其流程資訊更透明。"
 
 #: ./documenting.md:block 9 (unordered list)
 msgid ""
@@ -1188,7 +1188,7 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
-"代碼庫應該包含機器可讀取的中介資料說明，例如採用 [publiccode."
+"代碼庫應該包含機器可讀的中介資料說明，例如採用 [publiccode."
 "yml](https://github.com/publiccodeyml/publiccode.yml) 格式的檔案。"
 
 #: ./findability.md:block 5 (unordered list)
@@ -1281,7 +1281,7 @@ msgstr "檢查永久唯一識別碼條目有列出代碼庫網站。"
 
 #: ./findability.md:block 11 (unordered list)
 msgid "Check for a machine-readable metadata description file."
-msgstr "檢查中介資料說明檔案是機器可讀取的格式。"
+msgstr "檢查中介資料說明檔案是機器可讀的格式。"
 
 #: ./findability.md:block 13 (unordered list)
 msgid ""
@@ -1337,7 +1337,7 @@ msgstr ""
 msgid ""
 "[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
 "by the Free Softare Foundation."
-msgstr "FSF 自由軟體基金會，《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
+msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
 "Main_Page)》。"
 
 #: ./findability.md:block 19 (unordered list)
@@ -1474,8 +1474,8 @@ msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr "支持您經驗豐富的政策制定人員、開發人員與設計師，盡可能使其為代碼庫持續做出長"
-"久貢獻。"
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久"
+"貢獻。"
 
 #: ./make-contributing-easy.md:block 17 (unordered list)
 msgid "Respond promptly to requests."
@@ -1542,7 +1542,7 @@ msgstr "不得要求貢獻者將其貢獻的程式碼著作權轉讓給[代碼
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀取的著作權聲明與授權條款標頭內容。"
+msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
@@ -1594,7 +1594,7 @@ msgid ""
 "integration](../glossary.md#continuous-integration) tests."
 msgstr ""
 "在代碼庫[持續整合](../glossary.md#continuous-"
-"integration)測試中，確認是否有檢查授權內容為機器可讀取的檢查項目。"
+"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
@@ -1768,7 +1768,7 @@ msgstr "禁止採購不採用開放標準的技術科技。"
 msgid ""
 "Consider including open standard compliance assessment in "
 "[code](../glossary.md#code) reviews."
-msgstr "考慮在[程式碼](../glossary.md#code)審核中納入開放標準依循評估。"
+msgstr "考慮在[程式碼](../glossary.md#code)審查中納入開放標準依循評估。"
 
 #: ./open-standards.md:block 17 (unordered list)
 msgid ""
@@ -1806,32 +1806,32 @@ msgstr "歡迎貢獻者"
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
 "suggestions for changes to the codebase."
-msgstr "[代碼庫](../glossary.md#codebase)必須允許任何人針對代碼庫提出變更建議。"
+msgstr "[代碼庫](../glossary.md#codebase)必須允許任何人針對代碼庫提出修改建議。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr "代碼庫必須包含貢獻指引，像是在「CONTRIBUTING」檔案中說明歡迎貢獻者貢獻的內容"
-"類型，以及貢獻者可如何參與代碼庫。"
+msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開"
+"發，例如以「`CONTRIBUTING`」檔案說明。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr "代碼庫必須說明代碼庫，貢獻內容與社群的治理方式，可利用「GOVERNANCE」檔案來說"
-"明。"
+msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
+"RNANCE」檔案來說明。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr "代碼庫應該宣傳參與其開發與維護且承諾持續參與其營運的組織。"
+msgstr "代碼庫應該宣布投入其開發與維護工作的參與單位組織。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr "代碼庫應該要有公開的路徑圖。"
+msgstr "代碼庫應該要有可公開取得的發展路線圖。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid "The codebase SHOULD publish codebase activity statistics."
@@ -1840,29 +1840,29 @@ msgstr "代碼庫應該公布代碼庫的活動統計數據。"
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr "可選擇制定代碼庫貢獻者的行為準則。"
+msgstr "可選擇是否列入代碼庫的貢獻者行為準則。"
 
 #: ./open-to-contributions.md:block 7 (unordered list)
 msgid ""
 "Helps newcomers understand and trust the codebase community's leadership."
-msgstr "幫助新來者瞭解並且信任代碼庫社群的領導。"
+msgstr "幫助新參與者瞭解並且信任代碼庫社群的領導。"
 
 #: ./open-to-contributions.md:block 7 (unordered list)
 msgid ""
 "Prevents the community that works on a codebase splitting because there is "
 "no way to influence its goals and progress, resulting in diverging "
 "communities."
-msgstr "避免因為無法影響代碼庫的目標與進展，造成代碼庫的社群分裂成分歧的社群。"
+msgstr "避免因為參與者無法影響代碼庫的目標與進展，造成代碼庫的社群分裂成分歧的社群。"
 
 #: ./open-to-contributions.md:block 9 (unordered list)
 msgid "Guarantee others will join the community."
-msgstr "保證別人會加入社群。"
+msgstr "保證他人會參與社群。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid ""
 "Confirm that it is possible to submit suggestions for changes to the "
 "codebase."
-msgstr "確認可以提交變動建議給代碼庫。"
+msgstr "確認可以提交修改建議給代碼庫。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Confirm there are contribution guidelines."
@@ -1872,15 +1872,15 @@ msgstr "確認代碼庫有貢獻指引。"
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr "確認代碼庫有清楚解釋其治理方式，包括如何影響代碼庫的治理。"
+msgstr "確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a list of involved organizations."
-msgstr "檢查是否有參與組織名單。"
+msgstr "檢查是否有參與的單位組織名單。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a roadmap."
-msgstr "檢查是否有路徑圖。"
+msgstr "檢查是否有發展路線圖。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for published activity statistics."
@@ -1896,47 +1896,47 @@ msgid ""
 "[policy](../glossary.md#policy) experts, non-governmental organizations and "
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
-"為代碼庫新增其他資源清單，上面資源都是能幫助[政策](../glossary."
-"md#policy)專家，非政府組織與學者更瞭解或學會重複利用您的政策。"
+"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary."
+"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
 
 #: ./open-to-contributions.md:block 13 (unordered list)
 msgid ""
 "Consider adding contact details so that other policy makers considering "
 "collaboration can ask you for advice."
-msgstr "考慮新增聯絡資訊，讓其他考慮合作的決策者能徵詢您的意見。"
+msgstr "考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Make sure that the documentation of the governance includes the current "
 "process for how to make changes to the governance."
-msgstr "確保治理文件內容包含如何改變治理方式的現有流程。"
+msgstr "確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "If the community has some consensus about how the governance should change, "
 "then include those ideas stated as ambitions in the documentation."
-msgstr "如果社群對於治理方式應該如何改變有共識，應該將此構想寫入程式碼文件中並且標示"
-"為「願景」。"
+msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中"
+"。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr "確認文件解釋每個組織參與本代碼庫的方式，提供代碼庫哪些資源以及參與的時間長度"
-"。"
+msgstr "確認文件有解釋每個參與單位組織所投入的內容，例如提供代碼庫哪些資源，以及參與"
+"的時間長度等。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to stay "
 "part of the community for as long as possible."
-msgstr "支持經驗豐富的決策者，開發人員與設計師參與代碼庫社群，且時間越長越好。"
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr "開源軟體指南的[打造熱情友好的社群](https://opensource.guide/"
-"building-community/)。"
+msgstr "開源指南所提供的《[營造友善的社群](https://opensource.guide/"
+"building-community/)》。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1944,9 +1944,9 @@ msgid ""
 "open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
 "source-project/) by Mike McQuaid."
 msgstr ""
-"Mike McQuaid的[開源貢獻者漏斗](https://mikemcquaid.com/2018/08/14/the-open-so"
+"Mike McQuaid《[開源貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-so"
 "urce-contributor-funnel-why-people-dont-contribute-to-your-open-source-projec"
-"t/)。"
+"t/)》。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1954,9 +1954,9 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
-"開源軟體指南的[以領導與治理](https://opensource.guide/"
-"leadership-and-governance/)幫助[開源](../glossary.md#open-"
-"source)社群成長的專案。"
+"開源指南為成長中的[開源](../glossary.md#open-"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
+"leadership-and-governance/)》。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1966,7 +1966,7 @@ msgstr "Pieter Hintjens的[打造網路社群](http://hintjens.com/blog:117)(內
 
 #: ./require-review.md:block 1 (header)
 msgid "order: 7"
-msgstr "順序：7"
+msgstr "order: 7"
 
 #: ./require-review.md:block 2 (header)
 msgid "Require review of contributions"
@@ -2147,7 +2147,7 @@ msgstr "確保貢獻者在貢獻內容給代碼庫時，有獲得適當的協助
 msgid ""
 "Ask other contributors on the codebase to review your work, in your "
 "organization or outside of it."
-msgstr "請代碼庫的其他貢獻者審查您在貴組織內外的工作成果。"
+msgstr "請代碼庫的其他貢獻者審查您在貴單位組織內外的工作成果。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
@@ -2316,8 +2316,8 @@ msgstr "保證模組在任何情境下都可通用。"
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "reuse the codebase and what that would entail."
-msgstr "尋找另一組織角色與您相似的人，與其確認他們是否能重複利用代碼庫，又是透過什麼"
-"樣的方式。"
+msgstr "尋找另一單位組織角色與您相似的人，與其確認他們是否能重複利用代碼庫，又是透過"
+"什麼樣的方式。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
@@ -2346,7 +2346,7 @@ msgstr "為您的[政策](../glossary."
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr "確保代碼庫將貴組織列為已知用戶。"
+msgstr "確保代碼庫將貴單位組織列為已知用戶。"
 
 #: ./reusable-and-portable-codebases.md:block 15 (unordered list)
 msgid ""
@@ -2362,7 +2362,7 @@ msgstr "原始碼應經過設計："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr "讓其他使用者與組織可重複利用，不受地點影響，"
+msgstr "讓其他使用者與單位組織可重複利用，不受地點影響，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "to solve a general problem instead of a specific one,"
@@ -2376,7 +2376,8 @@ msgstr "採用邏輯上具有意義且獨立的模組，"
 msgid ""
 "so that someone in a similar organization facing a similar problem would be "
 "able to use (parts of) the solution."
-msgstr "讓在類似相同組織且面對類似問題的人，能夠使用同樣的解決方案(或當中的一部份)。"
+msgstr "讓在類似相同單位組織且面對類似問題的人，能夠使用同樣的解決方案(或當中的一部份"
+")。"
 
 #: ./reusable-and-portable-codebases.md:block 19 (paragraph)
 msgid ""
@@ -2394,7 +2395,7 @@ msgid ""
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
 msgstr "在每個版本上，審查人員確認內容不會包含專屬特定情況的資料，像是主機名稱，個人"
-"與組織資料或是代符與密碼。"
+"與單位組織資料或是代符與密碼。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2411,8 +2412,8 @@ msgid ""
 "OpenAPI Initiative defines a standard, programming language-agnostic "
 "interface description for human and machine-readable HTTP APIs."
 msgstr ""
-"OpenAPI Initiative組織的[OpenAPI規範](https://spec.openapis.org/oas/latest."
-"html)為人機可讀的HTTP API定義標準，不受程式語言種類限制的介面描述。"
+"OpenAPI 促進會定義的《[OpenAPI 規範](https://spec.openapis.org/oas/latest."
+"html)》為人機可讀的HTTP API定義標準，不受程式語言種類限制的介面描述。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2512,7 +2513,7 @@ msgstr ""
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr "貴組織對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
+msgstr "貴單位組織對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
 
 #: ./style.md:block 17 (paragraph)
 msgid ""
@@ -2603,8 +2604,8 @@ msgstr "代碼庫中，不得使用字首縮寫，縮寫，雙關語或法律/
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或組織品牌文字"
-"。"
+msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或單位組織品牌"
+"文字。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
@@ -2645,7 +2646,7 @@ msgstr "讓代碼庫功能解說更容易理解。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make your organization's jargon understandable without an explanation."
-msgstr "幫助他人在沒有額外解釋下就能理解貴組織術語。"
+msgstr "幫助他人在沒有額外解釋下就能理解貴單位組織術語。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm that codebase documentation is available in English."

From 5aeb3c1a7611e083a5024b02de9701e6c063ab94 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 17 Jan 2023 08:04:39 +0000
Subject: [PATCH 17/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 255 ++++++++++++------------
 1 file changed, 130 insertions(+), 125 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index a1714e99..281fded2 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-17 04:14+0000\n"
+"PO-Revision-Date: 2023-01-17 10:33+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -71,8 +71,8 @@ msgstr ""
 "如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼"
 "與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的"
 "問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼"
-"庫，則單位組織需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額"
-"外調整與設定，以適應新的情境。"
+"庫，則組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額"
+"外調整設定，以適應新的情境。"
 
 #: ./bundle-policy-and-code.md:block 8 (header)
 msgid "What this does not do"
@@ -134,8 +134,8 @@ msgid ""
 "your organization."
 msgstr ""
 "提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
-"文沒有英文版，請提供英文版摘要。務必也同時包含貴單位組織所選擇遵守的各項標準"
-"，以及影響貴單位組織代碼庫開發或部署情境的任何組織流程。"
+"文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
+"，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -195,7 +195,7 @@ msgstr "開發人員與設計師：需要的工作"
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr "熟悉並且學會貴單位組織政策制定者所使用的流程模型標記法。"
+msgstr "熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。"
 
 #: ./bundle-policy-and-code.md:block 17 (unordered list)
 msgid ""
@@ -256,7 +256,7 @@ msgid ""
 "Contributors MUST NOT upload sensitive information regarding users, their "
 "organization or third parties to the "
 "[repository](../glossary.md#repository)."
-msgstr "貢獻者不得上傳與使用者及其單位組織，或與第三方相關的敏感性資訊到[儲存庫](../g"
+msgstr "貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到[儲存庫](../g"
 "lossary.md#repository)中。"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
@@ -271,7 +271,7 @@ msgid ""
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
 msgstr ""
-"可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與單位組織之間"
+"可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與組織單位之間"
 "可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
@@ -348,8 +348,8 @@ msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含設定、使用者名稱"
-"或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
+msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者"
+"名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
@@ -800,7 +800,7 @@ msgstr "在每個指示程式碼成熟度的介面中加上明顯的標頭。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid "Version all releases."
-msgstr "所有發行的程式碼都要有版本編號。"
+msgstr "所有正式發行的程式碼都要有版本編號。"
 
 #: ./document-maturity.md:block 17 (unordered list)
 msgid ""
@@ -973,7 +973,7 @@ msgid ""
 " [code](../glossary.md#code)."
 msgstr ""
 "[代碼庫](../glossary.md#codebase)的所有功能、[政策](../glossary."
-"md#policy)及其來源，都必須以可清楚瞭解的用語描述，讓懂[程式碼](../glossary."
+"md#policy)及原始碼，都必須以可清楚瞭解的用語描述，讓懂[程式碼](../glossary."
 "md#code)目的用途的人也能夠理解。"
 
 #: ./documenting.md:block 5 (unordered list)
@@ -1048,7 +1048,7 @@ msgstr "能幫助他人找到這個代碼庫，特別是那些在問「是不是
 
 #: ./documenting.md:block 7 (unordered list)
 msgid "This provides transparency into your organization and processes."
-msgstr "讓貴單位組織與其流程資訊更透明。"
+msgstr "讓貴組織單位與其流程資訊更透明。"
 
 #: ./documenting.md:block 9 (unordered list)
 msgid ""
@@ -1827,7 +1827,7 @@ msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr "代碼庫應該宣布投入其開發與維護工作的參與單位組織。"
+msgstr "代碼庫應該宣布投入其開發與維護工作的參與組織單位。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
@@ -1876,7 +1876,7 @@ msgstr "確認代碼庫有清楚解釋治理架構，並包含如何影響代碼
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a list of involved organizations."
-msgstr "檢查是否有參與的單位組織名單。"
+msgstr "檢查是否有參與的組織單位名單。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a roadmap."
@@ -1922,7 +1922,7 @@ msgstr "如果社群對於治理架構應該如何改變有共識，則應該將
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr "確認文件有解釋每個參與單位組織所投入的內容，例如提供代碼庫哪些資源，以及參與"
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與"
 "的時間長度等。"
 
 #: ./open-to-contributions.md:block 15 (unordered list)
@@ -1976,14 +1976,14 @@ msgstr "要求審查貢獻內容"
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
-msgstr "所有被接受或是提交給完成版[代碼庫](../glossary."
-"md#codebase)的貢獻內容，都必須由另一位貢獻者審查。"
+msgstr "所有被接受或是提交給[代碼庫](../glossary."
+"md#codebase)正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Reviews MUST include source, [policy](../glossary.md#policy), tests and "
 "documentation."
-msgstr "審查必須包含來源，[政策](../glossary.md#policy)，測試與文件。"
+msgstr "審查必須包含原始碼、[政策](../glossary.md#policy)、測試、文件等。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
@@ -1995,33 +1995,33 @@ msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
 msgid ""
 "Contributions SHOULD conform to the standards, architecture and decisions "
 "set out in the codebase in order to pass review."
-msgstr "貢獻內容應該遵循代碼庫的標準，架構與決策，才能通過審查。"
+msgstr "貢獻內容應該遵循代碼庫的標準、架構、決策安排等，以通過審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Reviews SHOULD include running both the [code](../glossary.md#code) and the "
 "tests of the codebase."
-msgstr "審查方式應該包括執行[程式碼](../glossary.md#code)與代碼庫測試。"
+msgstr "審查內容應該包含執行[程式碼](../glossary.md#code)與執行代碼庫測試。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Contributions SHOULD be reviewed by someone in a different context than the "
 "contributor."
-msgstr "貢獻內容應該由與貢獻者不同背景的人來審查。"
+msgstr "貢獻內容應該由與貢獻者不同背景情境的人來審查。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr "版本控制系統在完成版的代碼庫中，不應該接受未經審查的貢獻內容。"
+msgstr "版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
-msgstr "審查應在兩個工作天內進行。"
+msgstr "審查應該在兩個工作天內進行。"
 
 #: ./require-review.md:block 5 (unordered list)
 msgid "Performing reviews by multiple reviewers is OPTIONAL."
-msgstr "可選擇由多位審查人員進行審查。"
+msgstr "可選擇是否由多位審查人員進行審查。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Increases codebase quality."
@@ -2029,68 +2029,68 @@ msgstr "提升代碼庫品質。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Reduces security risks as well as operational risks."
-msgstr "降低安全風險與營運風險。"
+msgstr "降低安全性風險與營運風險。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Creates a culture of making every contribution great."
-msgstr "打造讓每則貢獻內容豐富的文化。"
+msgstr "打造每份貢獻內容皆能有品質的文化。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid "Catches the most obvious mistakes that could happen."
-msgstr "找出可能發生的明顯問題。"
+msgstr "揪出可能發生的極明顯錯誤。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Gives contributors the security that their contributions are only accepted "
 "if they really add value."
-msgstr "讓貢獻者知道，只有能為代碼庫帶來價值的貢獻內容才會被接受。"
+msgstr "只有真正能為代碼庫提升價值的貢獻內容才會被接受，可以給予貢獻者安全感。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Assures contributors of a guaranteed time for feedback or collaborative "
 "improvement."
-msgstr "向貢獻者保證會有提供意見回饋或是改善協作的時間。"
+msgstr "向貢獻者保證在一段時間內提供意見回饋或是合作改善。"
 
 #: ./require-review.md:block 7 (unordered list)
 msgid ""
 "Prompt reviews increase both rate of delivery and contributor engagement."
-msgstr "迅速的審查能提高貢獻者貢獻內容的頻率以及參與。"
+msgstr "快速審查能提高貢獻者交付貢獻內容的頻率以及參與熱度。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Guarantee the right solution to a problem."
-msgstr "保證能找到解決問題的方法。"
+msgstr "保證能找到問題的合適解決方案。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Mean that reviewers are liable."
-msgstr "代表審查人員必須負責。"
+msgstr "代表審查人員必須承擔責任。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Absolve a contributor from writing documentation and tests."
-msgstr "貢獻者在編寫文件與測試上免責。"
+msgstr "貢獻者從編寫文件與測試中免除責任。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Provide you with the right reviewers."
-msgstr "提供您合適的審查人員。"
+msgstr "提供您合適的審查人選。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Confirm that every commit in the history has been reviewed by a different "
 "contributor."
-msgstr "確認版本歷史中提交的更新都由不同貢獻者審查。"
+msgstr "確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
-msgstr "確認審查包含來源，政策，測試與文件。"
+msgstr "確認審查內容包含原始碼、政策、測試、文件等。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Confirm that rejected contributions were appropriately explained."
-msgstr "針對未被採用的貢獻內容，確認有詳盡解釋原因。"
+msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check if reviews cover conformance to standards, architecture and codebase "
 "guidelines."
-msgstr "檢查審查包含貢獻內容是否遵循標準，架構與代碼庫指引。"
+msgstr "檢查審查範圍有涵蓋是否遵循標準、架構、代碼庫指引等。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check with reviewers if they run the code and tests during review."
@@ -2100,61 +2100,60 @@ msgstr "檢查審查人員在審查時是否有執行程式碼與測試。"
 msgid ""
 "Check with reviewers if commits have been reviewed by a different "
 "contributor in a different context."
-msgstr "與審查人員確認提交的更新是否已由不同背景的貢獻者來審查。"
+msgstr "與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid ""
 "Check for use of branch protection in the [version "
 "control](../glossary.md#version-control) system."
-msgstr "檢查[版本控制](../glossary.md#version-control)系統是否有採用分支保護。"
+msgstr "檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。"
 
 #: ./require-review.md:block 11 (unordered list)
 msgid "Check the times between contribution submission and review."
-msgstr "檢查貢獻代碼提交與審查的時間。"
+msgstr "檢查貢獻提交與審查之間的時間間隔。"
 
 #: ./require-review.md:block 13 (unordered list)
 msgid ""
 "Institute a 'four eyes' policy where everything, not just code, is reviewed."
-msgstr "審查程式碼與其他一切事物時，都要遵守「四眼原則」。"
+msgstr "制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。"
 
 #: ./require-review.md:block 13 (unordered list)
 msgid ""
 "Use a version control system or methodology that enables review and "
 "feedback."
-msgstr "使用具有審查與意見回饋功能的版本控制系統或方法。"
+msgstr "採用具有審查與意見回饋功能的版本控制系統或作業流程。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make delivering great code a shared objective."
-msgstr "讓所有人以寫出好的程式碼為目標。"
+msgstr "將交付妥善程式碼作為共同目標。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid ""
 "Make sure writing and reviewing contributions to source, policy, "
 "documentation and tests are considered equally valuable."
-msgstr "確保同樣重視撰寫與審查貢獻內容，與編寫原始碼，政策，文件與測試。"
+msgstr "確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid ""
 "Create a culture where all contributions are welcome and everyone is "
 "empowered to review them."
-msgstr "建立一個歡迎所有貢獻且每個人都能審查貢獻內容的文化。"
+msgstr "創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。"
 
 #: ./require-review.md:block 15 (unordered list)
 msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr "確保貢獻者在貢獻內容給代碼庫時，有獲得適當的協助。"
+msgstr "確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
 "Ask other contributors on the codebase to review your work, in your "
 "organization or outside of it."
-msgstr "請代碼庫的其他貢獻者審查您在貴單位組織內外的工作成果。"
+msgstr "請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。"
 
 #: ./require-review.md:block 17 (unordered list)
 msgid ""
 "Try to respond to others' requests for code review promptly, initially "
 "providing feedback about the concept of the change."
-msgstr "別人要求您審查他們的程式碼時，請盡快回覆，並且提出程式碼需要修正處背後的概念"
-"。"
+msgstr "當他人請求您審查程式碼時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -2162,8 +2161,8 @@ msgid ""
 "way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
 " Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[英國政府數位服務團程式碼審查方式](https://gds-way."
-"cloudapps.digital/manuals/code-review-guidelines.html#content)。"
+"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way."
+"cloudapps.digital/manuals/code-review-guidelines.html#content)》。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -2175,17 +2174,17 @@ msgid ""
 msgstr ""
 "[GitHub](https://docs.github.com/en/repositories/"
 "configuring-branches-and-merges-in-your-repository/"
-"defining-the-mergeability-of-pull-requests/about-protected-"
-"branches)與[GitLab](https://about.gitlab.com/2014/11/26/"
-"keeping-your-code-protected/)的分支保護。"
+"defining-the-mergeability-of-pull-requests/about-protected-branches) 與 "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/) "
+"撰寫的分支保護說明。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
 "[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
 "gentle-art-of-patch-review/) by Sage Sharp."
 msgstr ""
-"Sage Sharp的[修補程式審查的藝術](https://sage.thesharps.us/2014/09/01/"
-"the-gentle-art-of-patch-review/)。"
+"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/"
+"the-gentle-art-of-patch-review/)》。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -2193,106 +2192,109 @@ msgid ""
 "Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
 "mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
 msgstr ""
-"Mozilla的[評估參與程度](https://docs.google.com/presentation/d/"
-"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)。"
+"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/"
+"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id."
+"g43d857af8_0177)》。"
 
 #: ./reusable-and-portable-codebases.md:block 1 (header)
 msgid "order: 3"
-msgstr "順序：3"
+msgstr "order: 3"
 
 #: ./reusable-and-portable-codebases.md:block 2 (header)
 msgid "Create reusable and portable code"
-msgstr "編寫可重複使用且可攜式的程式碼"
+msgstr "編寫可重複使用且可攜的程式碼"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
 "[different contexts](../glossary.md#different-contexts)."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)在編寫時必須以能在[不同情境](../glossary.md"
-"#different-contexts)使用為前提。"
+"[代碼庫](../glossary.md#codebase)必須開發成能在[不同情境](../glossary.md"
+"#different-contexts)中重複使用。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed [code](../glossary.md#code) or services for execution "
 "and understanding."
-msgstr "代碼庫的執行與理解必須不仰賴任何秘密，未公開，專屬或非開源授權的[程式碼](../g"
-"lossary.md#code)。"
+msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的[程"
+"式碼](../glossary.md#code)或服務。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be in use by multiple parties."
-msgstr "代碼庫應該由多方使用。"
+msgstr "代碼庫應該有多方單位使用。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
-msgstr "路徑圖應該顯示各方的需求。"
+msgstr "發展路線圖應該有多方單位的需求影響。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Configuration SHOULD be used to make code adapt to context specific needs."
-msgstr "設定應該使程式碼適用各情境的特定需求。"
+msgstr "應該使用組態設定方式將程式碼調整成能適應各情境的特定需求。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be localizable."
-msgstr "代碼庫應該能夠本地化。"
+msgstr "代碼庫應該能夠在地化。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Code and its documentation SHOULD NOT contain situation-specific "
 "information."
-msgstr "程式碼與文件不應該包含僅適用於特定情況的資訊。"
+msgstr "程式碼與其文件不應該包含特定情況專用的資訊。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr "代碼庫模組在文件記載的方式應該讓其能在其他情境的代碼庫中重複利用。"
+msgstr "代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Enables other policy makers, developers and designers to reuse what you've "
 "developed, to test it, to improve it and contribute those improvements back "
 "leading to better quality, cheaper maintenance and higher reliability."
-msgstr "讓其他決策者，開發人員與設計師能夠重複利用您編寫的程式碼，並且測試與改善該程"
-"式碼，然後提供改善意見，讓程式碼品質更高，維護成本下滑且更可靠。"
+msgstr ""
+"讓其他政策制定者、開發人員與設計師等，能夠重複利用您所開發的內容，以及測試它"
+"、改善它，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Makes the code easier for new people to understand (as it's more general)."
-msgstr "讓新來者更容易瞭解此程式碼(因為更淺顯易懂)。"
+msgstr "讓新進人員能更容易瞭解程式碼（因為用途更廣泛通用）。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Makes it easier to control the mission, vision and scope of the codebase "
 "because the codebase is thoughtfully and purposefully designed for "
 "reusability."
-msgstr "讓代碼庫以重複利用為前提來編寫，因此控制其使命、願景與範圍也更容易。"
+msgstr "由於代碼庫以重複利用為前提籌劃設計，因此要調控代碼庫的目標使命、願景與範圍等"
+"也更容易。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Codebases used by multiple parties are more likely to benefit from a self-"
 "sustaining community."
-msgstr "多方使用的代碼庫更可以從自我維持的社群獲益。"
+msgstr "多方使用的代碼庫更可以從能自我運作的社群中獲益。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Any contributor is able to test and contribute without relying on the "
 "situation-specific infrastructure of any other contributor or deployment."
-msgstr "任何貢獻者都能夠測試與貢獻給代碼庫，且不需要仰賴其他貢獻者或部署底下特定情況"
-"專用的基礎架構。"
+msgstr "任何貢獻者都能測試與貢獻給代碼庫，不需要仰賴任何其他貢獻者或部署底下的特定情"
+"況專用基礎架構。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "Composing a codebase from well documented modules improves reusability and "
 "maintainability."
-msgstr "使用文件清楚的模組來建立代碼庫，代碼庫更能被重複使用，也更容易維護。"
+msgstr "以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。"
 
 #: ./reusable-and-portable-codebases.md:block 7 (unordered list)
 msgid ""
 "A module is easier to reuse in another context if its purpose is clearly "
 "documented."
-msgstr "清楚標示其目的的模組，更容易在另一個情境中重複利用。"
+msgstr "以文件清楚記錄用途的模組，更容易在另一種情境中重複利用。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Get others to reuse the codebase."
@@ -2306,78 +2308,78 @@ msgstr "建立社群。"
 msgid ""
 "Shift responsibility for documentation, support, bug-fixing, etc. to another"
 " party."
-msgstr "將文件，支援與除錯等責任轉移至他人。"
+msgstr "將文件、支援、修正錯誤⋯⋯等責任轉移給其他單位。"
 
 #: ./reusable-and-portable-codebases.md:block 9 (unordered list)
 msgid "Guarantee that modules are generic enough to be reused in any context."
-msgstr "保證模組在任何情境下都可通用。"
+msgstr "保證模組在任何情境下都足以通用。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "reuse the codebase and what that would entail."
-msgstr "尋找另一單位組織角色與您相似的人，與其確認他們是否能重複利用代碼庫，又是透過"
-"什麼樣的方式。"
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能重複利用代碼庫，以及需要怎麼"
+"進行。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed code or services."
-msgstr "確認代碼庫不需要使用專屬或非開源授權的程式碼貨服務，就能順利執行。"
+msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務就能夠執行。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase is in use by multiple parties or in multiple "
 "contexts."
-msgstr "檢查是否有多方使用代碼庫，或是在多種情境下使用代碼庫。"
+msgstr "檢查是否有多方單位或是有在多種情境下正使用代碼庫。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr "確認代碼庫檔案與提交歷史紀錄，沒有包含僅適用特定情況的數據。"
+msgstr "檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid ""
 "Document your [policy](../glossary.md#policy) with enough clarity and detail"
 " that it can be understood outside of its original context."
-msgstr "為您的[政策](../glossary."
-"md#policy)加上清楚明確的文件，讓他人在不同情境下也能理解。"
+msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處"
+"於同個原始背景情境也能夠理解。"
 
 #: ./reusable-and-portable-codebases.md:block 13 (unordered list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr "確保代碼庫將貴單位組織列為已知用戶。"
+msgstr "確保代碼庫有將貴組織單位列為已知用戶。"
 
 #: ./reusable-and-portable-codebases.md:block 15 (unordered list)
 msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr "確認利害關係人與企業業主瞭解，代碼庫就是以重複利用為目標，因為這能減少程式碼"
-"負債，並且讓代碼庫能永續發展。"
+msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式"
+"碼技術債，並讓代碼庫可以永續發展。"
 
 #: ./reusable-and-portable-codebases.md:block 17 (paragraph)
 msgid "Source should be designed:"
-msgstr "原始碼應經過設計："
+msgstr "原始碼應該設計成："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr "讓其他使用者與單位組織可重複利用，不受地點影響，"
+msgstr "能讓其他使用者與組織單位可以重複利用，不受其地方環境影響，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "to solve a general problem instead of a specific one,"
-msgstr "解決通用問題，而非特定問題，"
+msgstr "能解決通用性質問題，而非特定問題，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "in logically meaningful and isolated modules,"
-msgstr "採用邏輯上具有意義且獨立的模組，"
+msgstr "以邏輯上具有意義且獨立的模組構成，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid ""
 "so that someone in a similar organization facing a similar problem would be "
 "able to use (parts of) the solution."
-msgstr "讓在類似相同單位組織且面對類似問題的人，能夠使用同樣的解決方案(或當中的一部份"
-")。"
+msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份"
+"）。"
 
 #: ./reusable-and-portable-codebases.md:block 19 (paragraph)
 msgid ""
@@ -2386,16 +2388,17 @@ msgid ""
 " using proprietary components, ensure that collaborators can develop, use, "
 "test, and deploy without them."
 msgstr ""
-"確保代碼庫文件說明建置當下時間與執行期相依性。若您的情境需要您部署至專屬平台"
-"或使用專屬元件，請確保協作者可以在不用這兩者的情況下開發，使用，測試與部署。"
+"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要"
+"將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者"
+"的情況下，就能進行開發、使用、測試、部署等。"
 
 #: ./reusable-and-portable-codebases.md:block 20 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr "在每個版本上，審查人員確認內容不會包含專屬特定情況的資料，像是主機名稱，個人"
-"與單位組織資料或是代符與密碼。"
+msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
+"人與組織單位資料、代符與密碼等。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2403,8 +2406,8 @@ msgid ""
 "manual/technology/making-source-code-open-and-reusable) by the UK Government"
 " Digital Service."
 msgstr ""
-"英國政府數位服務團的[開源與可重複使用的原始碼](https://www.gov.uk/"
-"service-manual/technology/making-source-code-open-and-reusable)。"
+"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/"
+"service-manual/technology/making-source-code-open-and-reusable)》。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2413,7 +2416,7 @@ msgid ""
 "interface description for human and machine-readable HTTP APIs."
 msgstr ""
 "OpenAPI 促進會定義的《[OpenAPI 規範](https://spec.openapis.org/oas/latest."
-"html)》為人機可讀的HTTP API定義標準，不受程式語言種類限制的介面描述。"
+"html)》，為人機可讀的 HTTP API 標準，不受程式語言種類限制的介面描述。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2421,8 +2424,8 @@ msgid ""
 "Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
 " the World Wide Web Consortium."
 msgstr ""
-"全球資訊網協會的[本地化 vs. 國際化](https://www.w3.org/International/"
-"questions/qa-i18n)。"
+"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/"
+"questions/qa-i18n)》。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
@@ -2430,20 +2433,20 @@ msgid ""
 "CSS](https://www.w3.org/International/techniques/authoring-html) by the "
 "World Wide Web Consortium."
 msgstr ""
-"全球資訊網協會的[國際化技巧：編寫HTML與CSS](https://www.w3.org/International/"
-"techniques/authoring-html)。"
+"全球資訊網協會《[國際化技巧：編寫 HTML 與 CSS](https://www.w3.org/"
+"International/techniques/authoring-html)》。"
 
 #: ./reusable-and-portable-codebases.md:block 22 (unordered list)
 msgid ""
 "[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
 "Operating System."
 msgstr ""
-"GNU作業系統的[GNU gettext](https://www.gnu.org/software/gettext/gettext."
+"GNU 作業系統的 [GNU gettext](https://www.gnu.org/software/gettext/gettext."
 "html)。"
 
 #: ./style.md:block 1 (header)
 msgid "order: 15"
-msgstr "順序：15"
+msgstr "order: 15"
 
 #: ./style.md:block 2 (header)
 msgid "Use a coherent style"
@@ -2455,46 +2458,48 @@ msgid ""
 "the [codebase](../glossary.md#codebase) community's own or an existing one "
 "that is advertised in or part of the codebase."
 msgstr ""
-"貢獻代碼必須遵守程式碼編寫或寫作風格指南，可以是來自[代碼庫](../glossary."
-"md#codebase)社群或是代碼庫中使用的現有風格。"
+"貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是[代碼庫](../glo"
+"ssary.md#codebase)社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既"
+"有風格。"
 
 #: ./style.md:block 5 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
-msgstr "貢獻代碼應該通過自動化的風格測試。"
+msgstr "貢獻內容應該通過自動化的風格測試。"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD include inline comments and documentation for non-"
 "trivial sections."
-msgstr "代碼庫當中，複雜的程式碼應該包含註解與文件。"
+msgstr "代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""
 "Including sections on [understandable English](understandable-english-"
 "first.md) in the style guide is OPTIONAL."
-msgstr "風格指南可選擇加入[可理解的英文](understandable-english-first.md)章節。"
+msgstr "可選擇是否將[可理解的英文](understandable-english-first."
+"md)小節加入風格指南之中。"
 
 #: ./style.md:block 7 (unordered list)
 msgid ""
 "Enables contributors in different environments to work together on a unified"
 " product."
-msgstr "讓不同環境的貢獻者們可在同一個產品上合作。"
+msgstr "讓不同環境的貢獻者可以在統合的產品上合作。"
 
 #: ./style.md:block 7 (unordered list)
 msgid ""
 "Unifying vocabularies reduces friction in communication between "
 "contributors."
-msgstr "用詞統一，能減少貢獻者之間在溝通上的摩擦。"
+msgstr "用詞統一能減少貢獻者之間在溝通上的摩擦。"
 
 #: ./style.md:block 9 (unordered list)
 msgid "Help contributors write well or effectively explain what they do."
-msgstr "幫助貢獻者寫好程式碼，或者精準解釋他們的目的。"
+msgstr "幫助貢獻者寫好程式碼，或者精確說明他們在做什麼。"
 
 #: ./style.md:block 11 (unordered list)
 msgid ""
 "Confirm that contributions are in line with the style guides specified in "
 "the documentation."
-msgstr "確認貢獻代碼遵循文件當中的風格指南。"
+msgstr "確認貢獻內容有遵循文件中指定的風格指南。"
 
 #: ./style.md:block 11 (unordered list)
 msgid "Check for the presence of automated tests on style."
@@ -2513,7 +2518,7 @@ msgstr ""
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr "貴單位組織對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
+msgstr "貴組織單位對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
 
 #: ./style.md:block 17 (paragraph)
 msgid ""
@@ -2544,7 +2549,7 @@ msgstr "使用程式碼品質分析工具。"
 
 #: ./style.md:block 19 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入程式碼品質分析工具設定。"
+msgstr "在代碼庫中加入程式碼品質分析工具組態設定。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
@@ -2604,7 +2609,7 @@ msgstr "代碼庫中，不得使用字首縮寫，縮寫，雙關語或法律/
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或單位組織品牌"
+msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或組織單位品牌"
 "文字。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
@@ -2646,7 +2651,7 @@ msgstr "讓代碼庫功能解說更容易理解。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make your organization's jargon understandable without an explanation."
-msgstr "幫助他人在沒有額外解釋下就能理解貴單位組織術語。"
+msgstr "幫助他人在沒有額外解釋下就能理解貴組織單位術語。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm that codebase documentation is available in English."

From 158a6ebf5c07ba96a1d653ed194e3355f4e6adaa Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 17 Jan 2023 10:40:04 +0000
Subject: [PATCH 18/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 281fded2..ad677853 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-17 10:33+0000\n"
+"PO-Revision-Date: 2023-01-17 10:40+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -21,7 +21,7 @@ msgstr "order: 2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr "合捆政策與原始碼"
+msgstr "政策與原始碼合捆"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
@@ -233,7 +233,7 @@ msgstr "order: 1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "將原始碼開放"
+msgstr "原始碼開放"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -851,7 +851,7 @@ msgstr "order: 8"
 
 #: ./document-objectives.md:block 2 (header)
 msgid "Document codebase objectives"
-msgstr "有代碼庫目標文件"
+msgstr "代碼庫有目標文件"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
@@ -963,7 +963,7 @@ msgstr "order: 9"
 
 #: ./documenting.md:block 2 (header)
 msgid "Document the code"
-msgstr "有程式碼文件"
+msgstr "程式碼有文件"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -1383,7 +1383,7 @@ msgstr "order: 5"
 
 #: ./make-contributing-easy.md:block 2 (header)
 msgid "Make contributing easy"
-msgstr "做出貢獻要容易"
+msgstr "貢獻要容易"
 
 #: ./make-contributing-easy.md:block 5 (unordered list)
 msgid ""
@@ -2202,7 +2202,7 @@ msgstr "order: 3"
 
 #: ./reusable-and-portable-codebases.md:block 2 (header)
 msgid "Create reusable and portable code"
-msgstr "編寫可重複使用且可攜的程式碼"
+msgstr "程式碼編寫要可重複使用且可攜"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
@@ -2450,7 +2450,7 @@ msgstr "order: 15"
 
 #: ./style.md:block 2 (header)
 msgid "Use a coherent style"
-msgstr "風格前後一致"
+msgstr "風格要前後一致"
 
 #: ./style.md:block 5 (unordered list)
 msgid ""

From 8124b025aa10847c26e64ec9a4576bb6ee389f94 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 17 Jan 2023 12:00:49 +0000
Subject: [PATCH 19/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 185 +++++++++++++-----------
 1 file changed, 97 insertions(+), 88 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index ad677853..13764bf3 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-17 10:40+0000\n"
+"PO-Revision-Date: 2023-01-17 13:12+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -21,7 +21,7 @@ msgstr "order: 2"
 
 #: ./bundle-policy-and-code.md:block 2 (header)
 msgid "Bundle policy and source code"
-msgstr "政策與原始碼合捆"
+msgstr "政策與原始碼要合捆"
 
 #: ./bundle-policy-and-code.md:block 4 (header)
 msgid "Requirements"
@@ -233,7 +233,7 @@ msgstr "order: 1"
 
 #: ./code-in-the-open.md:block 2 (header)
 msgid "Code in the open"
-msgstr "原始碼開放"
+msgstr "原始碼要開放"
 
 #: ./code-in-the-open.md:block 5 (unordered list)
 msgid ""
@@ -1149,7 +1149,7 @@ msgstr "order: 14"
 
 #: ./findability.md:block 2 (header)
 msgid "Make the codebase findable"
-msgstr "可查詢得到代碼庫"
+msgstr "代碼庫可查詢得到"
 
 #: ./findability.md:block 5 (unordered list)
 msgid ""
@@ -1511,7 +1511,7 @@ msgstr "order: 13"
 
 #: ./open-licenses.md:block 2 (header)
 msgid "Publish with an open license"
-msgstr "採用開放授權發行"
+msgstr "發行採用開放授權"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
@@ -2202,7 +2202,7 @@ msgstr "order: 3"
 
 #: ./reusable-and-portable-codebases.md:block 2 (header)
 msgid "Create reusable and portable code"
-msgstr "程式碼編寫要可重複使用且可攜"
+msgstr "程式碼要可重複使用且可攜"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
@@ -2511,14 +2511,14 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
-"為[政策](../glossary.md#policy)與文件建立與遵守風格指南，並且持續改善，同時可"
-"在代碼庫的「`CONTRIBUTING`」或「`README`」檔案中註明。"
+"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄"
+"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
 
 #: ./style.md:block 15 (unordered list)
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr "貴組織單位對品質的定義中，應該涵蓋書面語言，原始碼，測試與政策標準。"
+msgstr "將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。"
 
 #: ./style.md:block 17 (paragraph)
 msgid ""
@@ -2533,11 +2533,12 @@ msgid ""
 "Continually improve upon and expand this documentation with the aim of "
 "evolving this documentation into engineering guidelines."
 msgstr ""
-"代碼庫若沒有工程指南或其他貢獻者指南，先在[儲存庫](../glossary.md#repository)"
-"中的「`CONTRIBUTING`」或「`README`」檔案加入文件，描述目前在指南方面的進展。"
-"文件主要目的在於表達設計偏好，命名規則等機器不容易檢查的內容。指南應該包含貢"
-"獻[程式碼](../glossary.md#code)該符合哪些要求，才會被維護人員加入代碼庫，包括"
-"原始碼，測試與文件。持續改善與增加文件內容，目標在於讓該文件成為工程指南。"
+"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#r"
+"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
+"前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
+"以及機器不容易檢查的其他層面。指南應該包含貢獻的[程式碼](../glossary.md#code)"
+"預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目"
+"。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
 
 #: ./style.md:block 18 (paragraph)
 msgid "Additionally:"
@@ -2545,72 +2546,74 @@ msgstr "此外："
 
 #: ./style.md:block 19 (unordered list)
 msgid "Use a linter."
-msgstr "使用程式碼品質分析工具。"
+msgstr "使用程式碼品質分析工具 (linter)。"
 
 #: ./style.md:block 19 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入程式碼品質分析工具組態設定。"
+msgstr "在代碼庫中加入程式碼品質分析工具的組態設定。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
 "[List of linters](https://github.com/caramelomartins/awesome-linters) by "
 "Hugo Martins."
 msgstr ""
-"Hugo Martins的[程式碼品質分析工具清單](https://github.com/caramelomartins/"
-"awesome-linters)。"
+"Hugo Martins《[程式碼品質分析工具清單](https://github.com/caramelomartins/"
+"awesome-linters)》。"
 
 #: ./style.md:block 21 (unordered list)
 msgid ""
 "[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
 "Wikipedia."
-msgstr "維基百科上的[代碼風格](https://en.wikipedia.org/wiki/Programming_style)。"
+msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/"
+"Programming_style)》條目。"
 
 #: ./understandable-english-first.md:block 1 (header)
 msgid "order: 10"
-msgstr "順序：10"
+msgstr "order: 10"
 
 #: ./understandable-english-first.md:block 2 (header)
 msgid "Use plain English"
-msgstr "使用簡明的英語"
+msgstr "使用白話的英語"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All [codebase](../glossary.md#codebase) documentation MUST be in English."
-msgstr "[代碼庫](../glossary.md#codebase)所有文件都必須使用英語。"
+msgstr "[代碼庫](../glossary.md#codebase)的所有文件都必須使用英語。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All [code](../glossary.md#code) MUST be in English, except where "
 "[policy](../glossary.md#policy) is machine interpreted as code."
 msgstr ""
-"所有[程式碼](../glossary.md#code)都必須使用英語，除了[政策](../glossary."
-"md#policy)當中由機器判讀為程式碼的部分。"
+"所有[程式碼](../glossary.md#code)都必須使用英語編寫，其中[政策](../glossary."
+"md#policy)是由機器解讀當作程式碼的部分則除外。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "All bundled policy not available in English MUST have an accompanying "
 "summary in English."
-msgstr "任何合捆的政策如果沒有英語版本，則必須提供英語版摘要。"
+msgstr "任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Any translation MUST be up to date with the English version and vice versa."
-msgstr "任何翻譯版本與英語版本都必須保持在最新版本狀態。"
+msgstr "任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
-msgstr "代碼庫中，不得使用字首縮寫，縮寫，雙關語或法律/非英語/網域專屬詞彙。若有，則"
-"需要在這些用語前面標註，或是附上解釋該用語的網頁連結。"
+msgstr ""
+"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果"
+"有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該能描述其特性，且不包含任何字首縮寫，縮寫，雙關語或組織單位品牌"
-"文字。"
+msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或"
+"組織單位品牌名稱或抬頭等。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
@@ -2618,23 +2621,23 @@ msgid ""
 "recommended by the [Web Content Accessibility Guidelines "
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
-"根據[網頁內容無障礙指南2](https://www.w3.org/WAI/WCAG21/quickref/"
-"?showtechniques=315#readable)的建議，文件內容應該以國中閱讀水平為主。"
+"根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
 
 #: ./understandable-english-first.md:block 5 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr "可選擇提供任何程式碼，文件或測試的翻譯版本。"
+msgstr "可選擇是否提供任何程式碼、文件、測試等的翻譯版。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
 "Makes the codebase and what it does understandable for a wider variety of "
 "stakeholders in multiple contexts."
-msgstr "讓不同情境的各種利害關係人，都能理解代碼庫以及其功用。"
+msgstr "讓不同情境的廣大利害關係人，都能瞭解代碼庫以及其用途。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid "Helps with the discoverability of the codebase."
-msgstr "讓代碼庫更容易被發現。"
+msgstr "讓代碼庫更容易被找到。"
 
 #: ./understandable-english-first.md:block 7 (unordered list)
 msgid ""
@@ -2642,16 +2645,17 @@ msgid ""
 "directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
 " which requires most public sector information to be accessible."
 msgstr ""
-"能幫助您遵守[歐盟無障礙指令](https://ec.europa.eu/digital-single-market/en/"
-"web-accessibility)，該指令規定所有人都應該能夠獲得多數公領域資訊。"
+"能幫助您達成《[歐盟無障礙環境命令](https://ec.europa.eu/"
+"digital-single-market/en/web-"
+"accessibility)》，內容要求大多數的公家機關資訊都要能夠近用以滿足無障礙環境。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make explanations of the codebase's functionality understandable."
-msgstr "讓代碼庫功能解說更容易理解。"
+msgstr "讓代碼庫功能解說更容易瞭解。"
 
 #: ./understandable-english-first.md:block 9 (unordered list)
 msgid "Make your organization's jargon understandable without an explanation."
-msgstr "幫助他人在沒有額外解釋下就能理解貴組織單位術語。"
+msgstr "幫助他人在沒有額外解釋之下，就能理解貴組織單位的業內用語。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
@@ -2661,11 +2665,12 @@ msgstr "確認代碼庫文件有英語版本。"
 msgid ""
 "Confirm that source code is in English, or confirm any non-English is policy"
 " or terms with preceding explanations."
-msgstr "確認原始碼為英語，或是任何非英語內容都是政策或術語，且有加註說明。"
+msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等"
+"。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Confirm any non-English policy has an accompanying summary in English."
-msgstr "確認非英語政策都有英語版摘要。"
+msgstr "確認任何非英語政策都有隨附英語版摘要。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid ""
@@ -2676,19 +2681,19 @@ msgstr "確認翻譯版與英語版內容相同。"
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr "確認文件當中，任何字首縮寫，縮寫，雙關語或法律/非英語/網域專屬詞彙都有加註說"
-"明。"
+msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業"
+"特定詞彙等。"
 
 #: ./understandable-english-first.md:block 11 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
-msgstr "檢查文件的拼字，文法與易讀性。"
+msgstr "檢查文件的拼字、文法與易讀性等。"
 
 #: ./understandable-english-first.md:block 13 (unordered list)
 msgid ""
 "Frequently test with other management, developers and designers in the "
 "process if they understand what you are delivering and how you document it."
-msgstr "在整個過程中，經常與其他管理人員，開發人員與設計師討論，瞭解他們是否理解您程"
-"式碼與其文件的內容。"
+msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交"
+"付的程式碼與其文件的內容。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
 msgid ""
@@ -2697,27 +2702,29 @@ msgid ""
 "teams and stakeholders. Add any such terms to a glossary and link to it from"
 " the places they are being used."
 msgstr ""
-"在團隊與利害關係人內部以及彼此間的溝通中，試著限制字首縮寫，縮寫，雙關語或法"
-"律/非英語/網域專屬詞彙的使用。將這些詞彙加入至詞彙表，並且在使用這些詞彙的地"
-"方，加上詞彙表連結。"
+"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，"
+"或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，"
+"並且在使用這些詞彙的地方加上詞彙表連結。"
 
 #: ./understandable-english-first.md:block 15 (unordered list)
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr "嚴謹看待提案與變更當中的文件與描述。若有東西您看不懂，其他人很可能也一樣。"
+msgstr "嚴謹看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同"
+"樣迷濛。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
 "Frequently test with policy makers and management if they understand what "
 "you are delivering and how you document it."
-msgstr "經常測試決策者與管理人員，瞭解他們是否理解您程式碼與其文件的內容。"
+msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件"
+"的內容。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
 "Ask someone outside of your context if they understand the content (for "
 "example, a developer working on a different codebase)."
-msgstr "請教身處不同情境的人(例如另一個代碼庫的開發人員)是否理解您的程式碼。"
+msgstr "詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
@@ -2725,32 +2732,33 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
 "readable and understandable."
 msgstr ""
-"全球資訊網協會的[網頁內容無障礙指南2.1與3.1(可讀性)](https://www.w3.org/TR/"
-"WCAG21/#readable)，讓文字內容更容易閱讀與理解。"
+"根據 W3C 全球資訊網協會的《[網頁內容近用性無障礙指南 2.1 與 3.1 "
+"之可讀性](https://www.w3.org/TR/WCAG21/"
+"#readable)》的內文，撰寫的文字內容要更容易閱讀與理解。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
 "[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
 " allows 1000 most common English words."
 msgstr ""
-"Theo Sanderson的[Upgoer 5文字編輯軟體](https://splasho.com/upgoer5/"
-")僅允許1,000最常用的英文單字。"
+"Theo Sanderson 所發表的「[Upgoer 5 文字編輯軟體](https://splasho.com/upgoer5/"
+")」只允許使用最常用的 1000 個英文單字。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
 "[Definition of plain "
 "language](https://www.plainlanguage.gov/about/definitions/) by United States"
 " General Services Administration."
-msgstr "美國總務署的[簡明語言定義](https://www.plainlanguage.gov/about/definitions/"
-")。"
+msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/"
+")》。"
 
 #: ./version-control-and-history.md:block 1 (header)
 msgid "order: 6"
-msgstr "順序：6"
+msgstr "order: 6"
 
 #: ./version-control-and-history.md:block 2 (header)
 msgid "Maintain version control"
-msgstr "維持版本控制"
+msgstr "維護版本控制"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
@@ -2758,78 +2766,79 @@ msgid ""
 "control](../glossary.md#version-control) for the "
 "[code](../glossary.md#code)."
 msgstr ""
-"社群必須有方法來維持[程式碼](../glossary.md#code)的[版本控制](../glossary.md"
+"社群必須要有方法為[程式碼](../glossary.md#code)維護[版本控制](../glossary.md"
 "#version-control)。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "All files in the [codebase](../glossary.md#codebase) MUST be version "
 "controlled."
-msgstr "必須控制[代碼庫](../glossary.md#codebase)所有檔案的版本。"
+msgstr "[代碼庫](../glossary.md#codebase)中的所有檔案皆必須有版本控制。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid "All decisions MUST be documented in commit messages."
-msgstr "在所有版本訊息中，必須紀錄所有決策。"
+msgstr "所有決定皆必須記錄成提交訊息。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Every commit message MUST link to discussions and issues wherever possible."
-msgstr "每份版本訊息，都必須盡可能附上討論與議題的連結。"
+msgstr "每份提交訊息皆必須盡可能附上討論與議題連結。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "The codebase SHOULD be maintained in a distributed version control system."
-msgstr "代碼庫應該以分散式版本控制系統來維護。"
+msgstr "代碼庫應該以分散式版本控制系統作維護。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid "Contributors SHOULD group relevant changes in commits."
-msgstr "貢獻者應該在提交的版本中，將相關變動分類。"
+msgstr "貢獻者應該將相關的修改變動提交內容作群組分類。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Maintainers SHOULD mark released versions of the codebase, for example using"
 " revision tags or textual labels."
-msgstr "維護人員應該使用修訂標籤或文字標籤標示代碼庫的完成版本。"
+msgstr "維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "Contributors SHOULD prefer file formats where the changes within the files "
 "can be easily viewed and understood in the version control system."
-msgstr "貢獻者應該偏好能在版本控制系統中，輕易看出與理解程式碼變動的檔案格式。"
+msgstr "貢獻者應該偏好使用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔"
+"案格式。"
 
 #: ./version-control-and-history.md:block 5 (unordered list)
 msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr "貢獻者可選擇在提交版本中簽名並附上電子郵件信箱，未來貢獻者如果有疑問可以與其"
-"聯絡。"
+msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內"
+"容有疑問時，可以與之前的貢獻者聯絡。"
 
 #: ./version-control-and-history.md:block 7 (paragraph)
 msgid ""
 "Version control means keeping track of changes to the code over time. This "
 "allows you to create structured documentation of the history of the "
 "codebase. This is essential for collaboration at scale."
-msgstr "版本控制代表追蹤程式碼歷來的變動，讓您能建立代碼庫文件的變動歷史，這是大規模"
-"協作的要素。"
+msgstr "版本控制代表追蹤程式碼歷來的變動。這能讓您為代碼庫製作有條理的變動歷史文件。"
+"這是大規模協作能運作的要素。"
 
 #: ./version-control-and-history.md:block 8 (paragraph)
 msgid "Distributed version control enables you to:"
-msgstr "分散式版本控制系統讓您可以："
+msgstr "分散式版本控制能讓您："
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "have a full copy of the code and its history"
-msgstr "擁有完整的程式碼與版本歷史"
+msgstr "擁有完整的程式碼副本與其版本歷史"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "revert to an earlier version of the codebase whenever you want to"
-msgstr "想要時可以將代碼庫恢復至先前版本"
+msgstr "在需要時可以將代碼庫恢復至先前版本"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid ""
 "record your changes and the reasons why you made them, to help future "
 "developers understand the process"
-msgstr "紀錄變動與變動原因，幫助未來開發人員瞭解整個流程"
+msgstr "紀錄變動與變動的原因，可幫助未來開發人員瞭解整個過程"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "compare two different versions"
@@ -2837,17 +2846,17 @@ msgstr "比較兩個不同版本"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid "work on changes in parallel as a team before merging them together"
-msgstr "團隊可以平行比對程式碼需要變動的部分，之後再將內容整合"
+msgstr "在將修改內容合併回代碼庫之前，各團隊可以針對修改變動平行作業"
 
 #: ./version-control-and-history.md:block 9 (unordered list)
 msgid ""
 "continue to work when the network is unavailable, merging changes back with "
 "everyone else’s at a later date"
-msgstr "沒有網路時，也能夠持續研究程式碼，之後所有人都上線時再整合程式碼變動部分"
+msgstr "在沒有網路時也能繼續作業，可以日後再將修改變動合併回代碼庫與其他人整合"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Substitute for [advertising maturity](document-maturity.md)."
-msgstr "替代[廣告成熟度](document-maturity.md)。"
+msgstr "可代替[成熟度宣告](document-maturity.md)。"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Guarantee the code executes correctly."
@@ -2855,27 +2864,27 @@ msgstr "保證程式碼能正確執行。"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Guarantee collaborators."
-msgstr "保證會有人協作。"
+msgstr "保證有人加入協作。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Confirm that the codebase is kept in version control using software such as "
 "Git."
-msgstr "確認使用Git等軟體，控制代碼庫的版本。"
+msgstr "確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Review the commit history, confirming that all commit messages explain why "
 "the change was made."
-msgstr "審查提交版本紀錄，確認過去所有訊息都有解釋程式碼變動原因。"
+msgstr "審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Review the commit history, confirming that where possible all commit "
 "messages include the discussion about the change was or where to find it "
 "(with a URL)."
-msgstr "審查提交版本紀錄，確認過去所有訊息中，都有包含程式碼變動的討論以及資訊位置(提"
-"供連結)。"
+msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方"
+"，包含變動內容以及連結位置（提供網址）。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid "Check if the version control system is distributed."
@@ -2885,19 +2894,19 @@ msgstr "檢查版本控制系統是否為分散式。"
 msgid ""
 "Review the commit history, check if grouping of relevant changes in "
 "accordance with the contributing guidelines."
-msgstr "審查提交版本紀錄，檢查是否有根據分散指南，將相關程式碼變動分類。"
+msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Check that it is possible to access a specific version of the codebase, for "
 "example through a revision tag or a textual label."
-msgstr "檢查是否有可能透過修正標籤或文字標籤存取代碼庫的特定版本。"
+msgstr "檢查是否可能透過像是修訂版號標記，或文字標籤，來存取代碼庫中的特定版本。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr "檢查代碼庫在允許的情況下，是否都採用文字格式。"
+msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid ""
@@ -2966,7 +2975,7 @@ msgid ""
 "manual/technology/maintaining-version-control-in-coding) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[維持程式碼版本控制](https://www.gov.uk/service-manual/"
+"英國政府數位服務團的[維護程式碼版本控制](https://www.gov.uk/service-manual/"
 "technology/maintaining-version-control-in-coding)。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)

From 6dec27e716104d3eba0ea9df24090fba6e86820e Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 17 Jan 2023 13:20:05 +0000
Subject: [PATCH 20/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (726 of 726 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 40 +++++++++++++------------
 1 file changed, 21 insertions(+), 19 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 13764bf3..2ac6e3ff 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-17 13:12+0000\n"
+"PO-Revision-Date: 2023-01-17 13:32+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -2914,51 +2914,52 @@ msgid ""
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
 msgstr "如果因為[政策](../glossary."
-"md#policy)變動而更新代碼庫版本，請在文件中清楚標示："
+"md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "what the policy change is,"
-msgstr "政策變動內容，"
+msgstr "政策改變的地方，"
 
 #: ./version-control-and-history.md:block 15 (unordered list)
 msgid "how it's changed the codebase."
-msgstr "代碼庫如何因此而改變。"
+msgstr "代碼庫如何因應而改變。"
 
 #: ./version-control-and-history.md:block 16 (paragraph)
 msgid ""
 "For example, adding a new category of applicant to a codebase that manages "
 "granting permits would be considered a policy change."
-msgstr "舉例來說，管理許可權指派的代碼庫，如果新增申請方類別，就會被視為政策變動。"
+msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政"
+"策變動。"
 
 #: ./version-control-and-history.md:block 18 (unordered list)
 msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr "支持決策者，開發人員與設計師清楚表達其如何改善代碼庫。改善代碼庫不會造成公關"
-"風險。"
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保"
+"改善代碼庫不會有公關風險。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Write clear commit messages so that it is easy to understand why the commit "
 "was made."
-msgstr "提交版本時的訊息內容要清楚，讓人一看就能理解提出新版本的原因。"
+msgstr "提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Mark different versions so that it is easy to access a specific version, for"
 " example using revision tags or textual labels."
-msgstr "使用修訂標籤或文字標籤標示不同版本，存取特定版本就更容易。"
+msgstr "使用像是修訂版號標記，或文字標籤來標示不同版本，以方便存取特定版本。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."
-msgstr "提交版本的訊息要清楚，方便之後比較各版本。"
+msgstr "提交內容的訊息要寫清楚，方便之後比較各版本。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid ""
 "Work with policy makers to describe how the source code was updated after a "
 "policy change."
-msgstr "在政策變動後，與決策者合作說明原始碼的更新內容。"
+msgstr "在政策改變以後與政策制定者合作，說明原始碼更新的內容。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
@@ -2966,8 +2967,8 @@ msgid ""
 "Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
 "Fogel."
 msgstr ""
-"Karl Fogel的[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html"
-"#vc-vocabulary)。"
+"Karl Fogel《[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html"
+"#vc-vocabulary)》。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
@@ -2975,20 +2976,21 @@ msgid ""
 "manual/technology/maintaining-version-control-in-coding) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團的[維護程式碼版本控制](https://www.gov.uk/service-manual/"
-"technology/maintaining-version-control-in-coding)。"
+"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/"
+"technology/maintaining-version-control-in-coding)》。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
 "[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
 " use it or refresh your skills."
-msgstr "GitHub的[GitHub學習實驗室](https://lab.github.com/"
-")，學習如何使用GitHub或是溫故知新。"
+msgstr ""
+"GitHub 提供的「[GitHub學習實驗室](https://lab.github.com/)」，可學習如何使用 "
+"GitHub，或是重溫您的技巧。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""
 "[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
 "education.pdf) by GitHub, a list with the most common used git commands."
 msgstr ""
-"GitHub的[Git備忘條](https://education.github.com/git-cheat-sheet-education."
-"pdf)，列出最常用的git指令。"
+"GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-"
+"education.pdf)」列出了最常用的 git 指令。"

From 53df8abecbba943de063c78192f69b9d9740bec4 Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Wed, 18 Jan 2023 03:18:17 +0000
Subject: [PATCH 21/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1221 of 1221 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 2ac6e3ff..af7a3c54 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-17 13:32+0000\n"
-"Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
+"PO-Revision-Date: 2023-01-19 03:35+0000\n"
+"Last-Translator: Weblate Admin <toomore0929@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"

From e859d1d856124b5962a23a7c4d556e43afd978db Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Thu, 29 Dec 2022 10:49:22 +0000
Subject: [PATCH 22/71] Move to source

---
 {criteria => criteria_source}/bundle-policy-and-code.md          | 0
 {criteria => criteria_source}/code-in-the-open.md                | 0
 {criteria => criteria_source}/continuous-integration.md          | 0
 {criteria => criteria_source}/document-maturity.md               | 0
 {criteria => criteria_source}/document-objectives.md             | 0
 {criteria => criteria_source}/documenting.md                     | 0
 {criteria => criteria_source}/findability.md                     | 0
 {criteria => criteria_source}/index.md                           | 0
 {criteria => criteria_source}/make-contributing-easy.md          | 0
 {criteria => criteria_source}/open-licenses.md                   | 0
 {criteria => criteria_source}/open-standards.md                  | 0
 {criteria => criteria_source}/open-to-contributions.md           | 0
 {criteria => criteria_source}/require-review.md                  | 0
 {criteria => criteria_source}/reusable-and-portable-codebases.md | 0
 {criteria => criteria_source}/style.md                           | 0
 {criteria => criteria_source}/understandable-english-first.md    | 0
 {criteria => criteria_source}/version-control-and-history.md     | 0
 17 files changed, 0 insertions(+), 0 deletions(-)
 rename {criteria => criteria_source}/bundle-policy-and-code.md (100%)
 rename {criteria => criteria_source}/code-in-the-open.md (100%)
 rename {criteria => criteria_source}/continuous-integration.md (100%)
 rename {criteria => criteria_source}/document-maturity.md (100%)
 rename {criteria => criteria_source}/document-objectives.md (100%)
 rename {criteria => criteria_source}/documenting.md (100%)
 rename {criteria => criteria_source}/findability.md (100%)
 rename {criteria => criteria_source}/index.md (100%)
 rename {criteria => criteria_source}/make-contributing-easy.md (100%)
 rename {criteria => criteria_source}/open-licenses.md (100%)
 rename {criteria => criteria_source}/open-standards.md (100%)
 rename {criteria => criteria_source}/open-to-contributions.md (100%)
 rename {criteria => criteria_source}/require-review.md (100%)
 rename {criteria => criteria_source}/reusable-and-portable-codebases.md (100%)
 rename {criteria => criteria_source}/style.md (100%)
 rename {criteria => criteria_source}/understandable-english-first.md (100%)
 rename {criteria => criteria_source}/version-control-and-history.md (100%)

diff --git a/criteria/bundle-policy-and-code.md b/criteria_source/bundle-policy-and-code.md
similarity index 100%
rename from criteria/bundle-policy-and-code.md
rename to criteria_source/bundle-policy-and-code.md
diff --git a/criteria/code-in-the-open.md b/criteria_source/code-in-the-open.md
similarity index 100%
rename from criteria/code-in-the-open.md
rename to criteria_source/code-in-the-open.md
diff --git a/criteria/continuous-integration.md b/criteria_source/continuous-integration.md
similarity index 100%
rename from criteria/continuous-integration.md
rename to criteria_source/continuous-integration.md
diff --git a/criteria/document-maturity.md b/criteria_source/document-maturity.md
similarity index 100%
rename from criteria/document-maturity.md
rename to criteria_source/document-maturity.md
diff --git a/criteria/document-objectives.md b/criteria_source/document-objectives.md
similarity index 100%
rename from criteria/document-objectives.md
rename to criteria_source/document-objectives.md
diff --git a/criteria/documenting.md b/criteria_source/documenting.md
similarity index 100%
rename from criteria/documenting.md
rename to criteria_source/documenting.md
diff --git a/criteria/findability.md b/criteria_source/findability.md
similarity index 100%
rename from criteria/findability.md
rename to criteria_source/findability.md
diff --git a/criteria/index.md b/criteria_source/index.md
similarity index 100%
rename from criteria/index.md
rename to criteria_source/index.md
diff --git a/criteria/make-contributing-easy.md b/criteria_source/make-contributing-easy.md
similarity index 100%
rename from criteria/make-contributing-easy.md
rename to criteria_source/make-contributing-easy.md
diff --git a/criteria/open-licenses.md b/criteria_source/open-licenses.md
similarity index 100%
rename from criteria/open-licenses.md
rename to criteria_source/open-licenses.md
diff --git a/criteria/open-standards.md b/criteria_source/open-standards.md
similarity index 100%
rename from criteria/open-standards.md
rename to criteria_source/open-standards.md
diff --git a/criteria/open-to-contributions.md b/criteria_source/open-to-contributions.md
similarity index 100%
rename from criteria/open-to-contributions.md
rename to criteria_source/open-to-contributions.md
diff --git a/criteria/require-review.md b/criteria_source/require-review.md
similarity index 100%
rename from criteria/require-review.md
rename to criteria_source/require-review.md
diff --git a/criteria/reusable-and-portable-codebases.md b/criteria_source/reusable-and-portable-codebases.md
similarity index 100%
rename from criteria/reusable-and-portable-codebases.md
rename to criteria_source/reusable-and-portable-codebases.md
diff --git a/criteria/style.md b/criteria_source/style.md
similarity index 100%
rename from criteria/style.md
rename to criteria_source/style.md
diff --git a/criteria/understandable-english-first.md b/criteria_source/understandable-english-first.md
similarity index 100%
rename from criteria/understandable-english-first.md
rename to criteria_source/understandable-english-first.md
diff --git a/criteria/version-control-and-history.md b/criteria_source/version-control-and-history.md
similarity index 100%
rename from criteria/version-control-and-history.md
rename to criteria_source/version-control-and-history.md

From dc3afcd1445dde080560fd45b158d5f1423113f2 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Fri, 30 Dec 2022 04:01:22 +0000
Subject: [PATCH 23/71] Change to demo serve

---
 script/serve.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/script/serve.sh b/script/serve.sh
index 33cf55dd..e2b0b9fc 100755
--- a/script/serve.sh
+++ b/script/serve.sh
@@ -12,4 +12,5 @@ if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
 export PAGES_REPO_NWO=publiccodenet/standard
 fi
 
-bundle exec jekyll serve --livereload
+#bundle exec jekyll serve --livereload --host 127.0.0.1 --port 6015
+bundle exec jekyll serve --host https://lyzez5.toomore.net --port 6015

From 7abd4ce74d3eeaeae376bb15b74dd6cb95aca9df Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Thu, 19 Jan 2023 06:15:02 +0000
Subject: [PATCH 24/71] Add translate bash

---
 _transed.sh | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 _transed.sh

diff --git a/_transed.sh b/_transed.sh
new file mode 100644
index 00000000..0848341f
--- /dev/null
+++ b/_transed.sh
@@ -0,0 +1,4 @@
+mkdir ./criteria
+for file in ./criteria_source/*; do
+    po2md -p ./locales/zh_Hant/LC_MESSAGES/messages.po -s ./criteria/`basename "$file"` $file
+done

From 391bba18bf33ae3379c57c4968d887af8c488a87 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Thu, 19 Jan 2023 06:38:02 +0000
Subject: [PATCH 25/71] Update gen docs

---
 _transed.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/_transed.sh b/_transed.sh
index 0848341f..057d9b53 100644
--- a/_transed.sh
+++ b/_transed.sh
@@ -2,3 +2,4 @@ mkdir ./criteria
 for file in ./criteria_source/*; do
     po2md -p ./locales/zh_Hant/LC_MESSAGES/messages.po -s ./criteria/`basename "$file"` $file
 done
+bundle exec jekyll build

From 800e90d568a5014d8c3a797862ba36ba03398970 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Thu, 19 Jan 2023 17:07:53 +0000
Subject: [PATCH 26/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1221 of 1221 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 87 ++++++++++++-------------
 1 file changed, 43 insertions(+), 44 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index af7a3c54..e92780c4 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-19 03:35+0000\n"
-"Last-Translator: Weblate Admin <toomore0929@gmail.com>\n"
+"PO-Revision-Date: 2023-01-19 18:55+0000\n"
+"Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -80,7 +80,7 @@ msgstr "此措施辦不到的事"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid "Guarantee that a codebase will reflect the bundled policy."
-msgstr "保證代碼庫能反應合捆的政策。"
+msgstr "保證代碼庫能反映合捆的政策。"
 
 #: ./bundle-policy-and-code.md:block 9 (unordered list)
 msgid ""
@@ -152,8 +152,8 @@ msgid ""
 msgstr ""
 "政策內容請使用明確且機器可讀的格式，像是[業務流程模型與標記法](https://en."
 "wikipedia.org/wiki/"
-"Business_Process_Model_and_Notation)，[決策模型與標記法](https://en.wikipedia"
-".org/wiki/Decision_Model_and_Notation)以及[案例管理模型標記法](https://en."
+"Business_Process_Model_and_Notation)、[決策模型與標記法](https://en.wikipedia"
+".org/wiki/Decision_Model_and_Notation)，以及[案例管理模型標記法](https://en."
 "wikipedia.org/wiki/CMMN)。"
 
 #: ./bundle-policy-and-code.md:block 13 (unordered list)
@@ -341,7 +341,7 @@ msgstr "孕育擁抱開放、重視學習、歡迎意見回饋的文化。"
 #: ./code-in-the-open.md:block 17 (unordered list)
 msgid ""
 "Collaborate with external vendors and freelancers by working in the open."
-msgstr "與外部供應商和自由業者以開放精神的方式協作。"
+msgstr "與外部供應商和自由工作者以開放精神的方式協作。"
 
 #: ./code-in-the-open.md:block 19 (unordered list)
 msgid ""
@@ -438,7 +438,7 @@ msgstr "代碼庫必須有活躍貢獻者。"
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr "代碼庫準則應該規定每次做出貢獻時都應只聚焦在單一議題上。"
+msgstr "代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。"
 
 #: ./continuous-integration.md:block 5 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
@@ -488,8 +488,8 @@ msgstr "能加速開發週期。"
 msgid ""
 "Smaller, more regular contributions are typically easier to evaluate and "
 "lower risk compared to large infrequent changes."
-msgstr "修改內容較少，而時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大，累積"
-"很久才一次提出的變更。"
+msgstr "修改內容較少、時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大、累積很"
+"久才一次提出的變更。"
 
 #: ./continuous-integration.md:block 7 (unordered list)
 msgid ""
@@ -541,7 +541,7 @@ msgstr "確認最近三個月內有貢獻內容上傳。"
 
 #: ./continuous-integration.md:block 11 (unordered list)
 msgid "Check if code coverage data is published."
-msgstr "檢查程式碼覆蓋率數據是否有公佈。"
+msgstr "檢查程式碼覆蓋率數據是否有公布。"
 
 #: ./continuous-integration.md:block 13 (unordered list)
 msgid ""
@@ -618,8 +618,7 @@ msgid ""
 "create conditions."
 msgstr ""
 "編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
-"來。例如硬碟空間不足、記憶體配置失敗敗等資源耗盡情況，都是難以創造的典型案例"
-"。"
+"來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
 
 #: ./continuous-integration.md:block 17 (unordered list)
 msgid ""
@@ -685,7 +684,7 @@ msgstr "[代碼庫](../glossary.md#codebase)必須註明版本編號。"
 msgid ""
 "The codebase that is ready to use MUST only depend on other codebases that "
 "are also ready to use."
-msgstr "準備完成可供使用的代碼庫，必須只能依賴其他也已經準備完成可供使用的代碼庫。"
+msgstr "準備好可供使用的代碼庫，必須只能依賴其他也已經準備好可供使用的代碼庫。"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid ""
@@ -698,7 +697,7 @@ msgstr "尚未準備好使用的代碼庫，必須有所列標籤之一：protot
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔紀錄。"
+msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
 
 #: ./document-maturity.md:block 7 (paragraph)
 msgid ""
@@ -730,8 +729,8 @@ msgstr "確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。
 msgid ""
 "Confirm that the codebase is ready to use or labeled as prototype, alpha, "
 "beta or pre-release version."
-msgstr "確認代碼庫已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-release "
-"等開發中版本。"
+msgstr "確認代碼庫是已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-"
+"release 等開發中版本。"
 
 #: ./document-maturity.md:block 11 (unordered list)
 msgid "Check that there is a log of changes."
@@ -757,7 +756,7 @@ msgid ""
 "service or a prototype codebase in a beta service."
 msgstr ""
 "要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，"
-"正式上線的服務不要使用 beta 測試版代碼庫，測試版服務不要使用 prototype "
+"正式上線的服務不要使用 beta 公測版代碼庫，公測版服務不要使用 prototype "
 "原型代碼庫。"
 
 #: ./document-maturity.md:block 15 (unordered list)
@@ -771,7 +770,7 @@ msgstr "若代碼庫尚未準備好供一般使用，請與開發人員一起確
 msgid ""
 "prototype: to test the look and feel, and to internally prove the concept of"
 " the technical possibilities,"
-msgstr "prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術可行性的概念，"
+msgstr "prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術的可行性概念，"
 
 #: ./document-maturity.md:block 15 (unordered list)
 msgid "alpha: to do guided tests with a limited set of users,"
@@ -1055,8 +1054,8 @@ msgid ""
 "Contribute directly to more reusable, portable code (see [Create reusable "
 "and portable code](./reusable-and-portable-codebases.md))."
 msgstr ""
-"直接貢獻更可重複使用，以及更具可攜性的程式碼（請參閱[編寫可重複使用且具可攜性"
-"的程式碼](./reusable-and-portable-codebases.md)）。"
+"直接貢獻出更可重複使用，以及更具可攜性的程式碼（請參閱[編寫可重複使用且具可攜"
+"性的程式碼](./reusable-and-portable-codebases.md)）。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
@@ -1081,7 +1080,7 @@ msgstr "確認文件有包含主要功能的範例。"
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr "向一般民眾的成員以及記者確認他們是否能明白文件當中的精要說明。"
+msgstr "向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
 
 #: ./documenting.md:block 11 (unordered list)
 msgid ""
@@ -1330,7 +1329,7 @@ msgid ""
 "Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
 "Wikidata community."
 msgstr ""
-"Wikidata 維基數據社群撰寫，《[維基數據簡介](https://www.wikidata.org/wiki/"
+"Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/"
 "Wikidata:Introduction)》。"
 
 #: ./findability.md:block 19 (unordered list)
@@ -1350,10 +1349,10 @@ msgid ""
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
 "GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
-"tps://www.go-fair.org/fair-principles/)》中，提供一份滿好的特性清單，解說哪些"
-"特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的"
-"部分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與"
-"其對應的特性要怎麼處理。"
+"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
+"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
+"分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
+"對應的特性要怎麼處理。"
 
 #: ./index.md:block 1 (header)
 msgid "Criteria"
@@ -1485,7 +1484,7 @@ msgstr "快速回應請求。"
 msgid ""
 "Keep your management informed of the time and resources you require to "
 "support other contributors."
-msgstr "持續告知管理階層您在支援其他貢獻者時所需要的時間與資源。"
+msgstr "持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
@@ -1517,8 +1516,8 @@ msgstr "發行採用開放授權"
 msgid ""
 "All [code](../glossary.md#code) and documentation MUST be licensed such that"
 " it may be freely reusable, changeable and redistributable."
-msgstr "所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以可自由重複使用、可"
-"自由修改、可自由再次散布的授權條款。"
+msgstr "所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以自由重複使用、自由"
+"修改、自由再次散布的授權條款。"
 
 #: ./open-licenses.md:block 5 (unordered list)
 msgid ""
@@ -1753,7 +1752,7 @@ msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的生效連結；或沒有採用"
+msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用"
 "任何標準時，則留下聲明。"
 
 #: ./open-standards.md:block 13 (unordered list)
@@ -1821,7 +1820,7 @@ msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
 msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
-"RNANCE」檔案來說明。"
+"RNANCE`」檔案來說明。"
 
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
@@ -1840,7 +1839,7 @@ msgstr "代碼庫應該公布代碼庫的活動統計數據。"
 #: ./open-to-contributions.md:block 5 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr "可選擇是否列入代碼庫的貢獻者行為準則。"
+msgstr "可選擇是否為代碼庫加入貢獻者的行為準則。"
 
 #: ./open-to-contributions.md:block 7 (unordered list)
 msgid ""
@@ -1852,7 +1851,7 @@ msgid ""
 "Prevents the community that works on a codebase splitting because there is "
 "no way to influence its goals and progress, resulting in diverging "
 "communities."
-msgstr "避免因為參與者無法影響代碼庫的目標與進展，造成代碼庫的社群分裂成分歧的社群。"
+msgstr "避免參與者因為無法影響代碼庫的目標與進展，而造成代碼庫社群分裂成分歧的社群。"
 
 #: ./open-to-contributions.md:block 9 (unordered list)
 msgid "Guarantee others will join the community."
@@ -1872,7 +1871,7 @@ msgstr "確認代碼庫有貢獻指引。"
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr "確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理。"
+msgstr "確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。"
 
 #: ./open-to-contributions.md:block 11 (unordered list)
 msgid "Check for a list of involved organizations."
@@ -1962,7 +1961,7 @@ msgstr ""
 msgid ""
 "[Building online communities](http://hintjens.com/blog:117) by Pieter "
 "Hintjens (long read!)."
-msgstr "Pieter Hintjens的[打造網路社群](http://hintjens.com/blog:117)(內容很長！)。"
+msgstr "Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。"
 
 #: ./require-review.md:block 1 (header)
 msgid "order: 7"
@@ -2176,7 +2175,7 @@ msgstr ""
 "configuring-branches-and-merges-in-your-repository/"
 "defining-the-mergeability-of-pull-requests/about-protected-branches) 與 "
 "[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/) "
-"撰寫的分支保護說明。"
+"平臺的分支保護說明。"
 
 #: ./require-review.md:block 19 (unordered list)
 msgid ""
@@ -2231,7 +2230,7 @@ msgstr "發展路線圖應該有多方單位的需求影響。"
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid ""
 "Configuration SHOULD be used to make code adapt to context specific needs."
-msgstr "應該使用組態設定方式將程式碼調整成能適應各情境的特定需求。"
+msgstr "應該使用組態設定方式以將程式碼調整成能適應各情境的特定需求。"
 
 #: ./reusable-and-portable-codebases.md:block 5 (unordered list)
 msgid "The codebase SHOULD be localizable."
@@ -2325,7 +2324,7 @@ msgstr "與另一組織單位角色與您相似的人確認，看他們是否能
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed code or services."
-msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務就能夠執行。"
+msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。"
 
 #: ./reusable-and-portable-codebases.md:block 11 (unordered list)
 msgid ""
@@ -2364,7 +2363,7 @@ msgstr "原始碼應該設計成："
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr "能讓其他使用者與組織單位可以重複利用，不受其地方環境影響，"
+msgstr "能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，"
 
 #: ./reusable-and-portable-codebases.md:block 18 (unordered list)
 msgid "to solve a general problem instead of a specific one,"
@@ -2710,8 +2709,8 @@ msgstr ""
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr "嚴謹看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同"
-"樣迷濛。"
+msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其"
+"他人也同樣迷惘。"
 
 #: ./understandable-english-first.md:block 17 (unordered list)
 msgid ""
@@ -2732,9 +2731,9 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
 "readable and understandable."
 msgstr ""
-"根據 W3C 全球資訊網協會的《[網頁內容近用性無障礙指南 2.1 與 3.1 "
+"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 "
 "之可讀性](https://www.w3.org/TR/WCAG21/"
-"#readable)》的內文，撰寫的文字內容要更容易閱讀與理解。"
+"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
 
 #: ./understandable-english-first.md:block 19 (unordered list)
 msgid ""
@@ -2856,7 +2855,7 @@ msgstr "在沒有網路時也能繼續作業，可以日後再將修改變動合
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Substitute for [advertising maturity](document-maturity.md)."
-msgstr "可代替[成熟度宣告](document-maturity.md)。"
+msgstr "代替[成熟度宣告](document-maturity.md)。"
 
 #: ./version-control-and-history.md:block 11 (unordered list)
 msgid "Guarantee the code executes correctly."

From f584e006d2125b38fbe47be4e7c15adda22259b8 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Thu, 19 Jan 2023 18:57:13 +0000
Subject: [PATCH 27/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1221 of 1221 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index e92780c4..209af3bf 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-19 18:55+0000\n"
+"PO-Revision-Date: 2023-01-19 18:57+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -2899,7 +2899,7 @@ msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相
 msgid ""
 "Check that it is possible to access a specific version of the codebase, for "
 "example through a revision tag or a textual label."
-msgstr "檢查是否可能透過像是修訂版號標記，或文字標籤，來存取代碼庫中的特定版本。"
+msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。"
 
 #: ./version-control-and-history.md:block 13 (unordered list)
 msgid ""
@@ -2948,7 +2948,7 @@ msgstr "提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改
 msgid ""
 "Mark different versions so that it is easy to access a specific version, for"
 " example using revision tags or textual labels."
-msgstr "使用像是修訂版號標記，或文字標籤來標示不同版本，以方便存取特定版本。"
+msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。"
 
 #: ./version-control-and-history.md:block 20 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."

From 3ef9de9364d8ff4b2b2ed3610bece83298ca9619 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <pswo10680@gmail.com>
Date: Tue, 31 Jan 2023 08:49:02 +0000
Subject: [PATCH 28/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1221 of 1221 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 28 ++++++++++++-------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 209af3bf..9b9194cc 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-01-19 18:57+0000\n"
+"PO-Revision-Date: 2023-02-01 08:52+0000\n"
 "Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
@@ -12,7 +12,7 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
-"X-Generator: Weblate 4.15\n"
+"X-Generator: Weblate 4.15.2\n"
 
 #
 #: ./bundle-policy-and-code.md:block 1 (header)
@@ -271,12 +271,12 @@ msgid ""
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
 msgstr ""
-"可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與組織單位之間"
+"可選擇是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間"
 "可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
 
 #: ./code-in-the-open.md:block 7 (paragraph)
 msgid "Coding in the open:"
-msgstr "以開放精神編寫原始碼："
+msgstr "以開放精神編寫原始碼能："
 
 #: ./code-in-the-open.md:block 8 (unordered list)
 msgid "improves transparency"
@@ -295,7 +295,7 @@ msgid ""
 "These aspects together create more opportunities for citizens to understand "
 "how software and policy impact their interactions with a public "
 "organization."
-msgstr "這些面向讓公民更有機會瞭解軟體與政策如何影響其與公共組織的互動。"
+msgstr "這些面向讓公民更有機會能瞭解，軟體與政策如何影響他們與公共組織的互動。"
 
 #: ./code-in-the-open.md:block 11 (unordered list)
 msgid "Make source code or policy reusable."
@@ -674,7 +674,7 @@ msgstr "order: 16 redirect_from: - criteria/advertise-maturity"
 
 #: ./document-maturity.md:block 2 (header)
 msgid "Document codebase maturity"
-msgstr "紀錄代碼庫成熟度"
+msgstr "記錄代碼庫成熟度"
 
 #: ./document-maturity.md:block 5 (unordered list)
 msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
@@ -850,7 +850,7 @@ msgstr "order: 8"
 
 #: ./document-objectives.md:block 2 (header)
 msgid "Document codebase objectives"
-msgstr "代碼庫有目標文件"
+msgstr "代碼庫要有目標文件"
 
 #: ./document-objectives.md:block 5 (unordered list)
 msgid ""
@@ -873,12 +873,12 @@ msgstr "代碼庫文件應該清楚描述[政策](../glossary."
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr "可選擇是否以文件紀錄給[一般民眾](../glossary.md#general-"
+msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-"
 "public)看的代碼庫目標。"
 
 #: ./document-objectives.md:block 7 (paragraph)
 msgid "Documenting codebase objectives:"
-msgstr "以文件紀錄代碼庫目標："
+msgstr "以文件記錄代碼庫目標："
 
 #: ./document-objectives.md:block 8 (unordered list)
 msgid ""
@@ -962,7 +962,7 @@ msgstr "order: 9"
 
 #: ./documenting.md:block 2 (header)
 msgid "Document the code"
-msgstr "程式碼有文件"
+msgstr "程式碼要有文件"
 
 #: ./documenting.md:block 5 (unordered list)
 msgid ""
@@ -1235,7 +1235,7 @@ msgid ""
 "Confirm that the codebase appears in the first set of results on more than "
 "one major search engine when searching by a plain English problem "
 "description."
-msgstr "確認以白話英文敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
+msgstr "確認以白話英語敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
 "庫放在搜尋結果的第一頁中。"
 
 #: ./findability.md:block 11 (unordered list)
@@ -1351,7 +1351,7 @@ msgstr ""
 "GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
 "tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
 "性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
-"分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
+"分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
 "對應的特性要怎麼處理。"
 
 #: ./index.md:block 1 (header)
@@ -2065,7 +2065,7 @@ msgstr "代表審查人員必須承擔責任。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Absolve a contributor from writing documentation and tests."
-msgstr "貢獻者從編寫文件與測試中免除責任。"
+msgstr "貢獻者能從編寫文件與測試中免除責任。"
 
 #: ./require-review.md:block 9 (unordered list)
 msgid "Provide you with the right reviewers."
@@ -2475,7 +2475,7 @@ msgstr "代碼庫當中較複雜的程式碼區段，應該包含列內註解與
 msgid ""
 "Including sections on [understandable English](understandable-english-"
 "first.md) in the style guide is OPTIONAL."
-msgstr "可選擇是否將[可理解的英文](understandable-english-first."
+msgstr "可選擇是否將[可理解的白話英語](understandable-english-first."
 "md)小節加入風格指南之中。"
 
 #: ./style.md:block 7 (unordered list)

From c654642009193adc6e6946395df149e165c71a8c Mon Sep 17 00:00:00 2001
From: Weblate Admin <toomore0929@gmail.com>
Date: Wed, 3 May 2023 08:47:49 +0000
Subject: [PATCH 29/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1221 of 1221 strings)

Translation: Standard for Public code/Standard for Public Codec
Translate-URL: https://weblate.toomore.net/projects/pmpc/standard-for-public-codec/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 42 ++++++++++++-------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 9b9194cc..46cd90c3 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-12-01 12:42+0800\n"
-"PO-Revision-Date: 2023-02-01 08:52+0000\n"
-"Last-Translator: Cheng-Chia Tseng <pswo10680@gmail.com>\n"
+"PO-Revision-Date: 2023-05-05 03:50+0000\n"
+"Last-Translator: Weblate Admin <toomore0929@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
 "pmpc/standard-for-public-codec/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -12,7 +12,7 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
-"X-Generator: Weblate 4.15.2\n"
+"X-Generator: Weblate 4.16.4\n"
 
 #
 #: ./bundle-policy-and-code.md:block 1 (header)
@@ -1492,9 +1492,9 @@ msgid ""
 "project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
 "to-your-open-source-project-1ebf) by Joel Hans."
 msgstr ""
-"Joel Hans《[如何引發他人為您的開源專案做出優秀貢獻](https://dev.to/joelhans/"
-"how-to-inspire-exceptional-contributions-to-your-open-source-project-"
-"1ebf)》。"
+"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/"
+"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
+"project-1ebf)》。"
 
 #: ./make-contributing-easy.md:block 19 (unordered list)
 msgid ""
@@ -1524,7 +1524,7 @@ msgid ""
 "Software source code MUST be licensed under an [OSI-approved or FSF "
 "Free/Libre license](https://spdx.org/licenses/)."
 msgstr ""
-"軟體原始碼必須採用[經 OSI 開源促進會所批准，或由 FSF "
+"軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
 "自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
 
 #: ./open-licenses.md:block 5 (unordered list)
@@ -1570,7 +1570,7 @@ msgid ""
 "documentation [conforms to the Open "
 "Definition](https://opendefinition.org/licenses/)."
 msgstr ""
-"確認原始碼的授權條款有列於[經 OSI 開源促進會所批准，或由 FSF "
+"確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF "
 "自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/"
 ")，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/"
 "licenses/)。"
@@ -1600,20 +1600,20 @@ msgid ""
 "Develop [policy](../glossary.md#policy) that requires code to be [open "
 "source](../glossary.md#open-source)."
 msgstr ""
-"制定要求程式碼必須採用[開源](../glossary.md#open-"
+"制定要求程式碼必須採用[開放原始碼](../glossary.md#open-"
 "source)授權的[政策](../glossary.md#policy)。"
 
 #: ./open-licenses.md:block 13 (unordered list)
 msgid ""
 "Develop policy that disincentivizes non-open source code and technology in "
 "procurement."
-msgstr "制定抑制採購非開源授權程式碼與非開放科技的政策。"
+msgstr "制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
 "Only work with open source vendors that deliver their code by publishing it "
 "under an open source license."
-msgstr "只與能採用開源授權交付與發行其程式碼的開源軟體供應商合作。"
+msgstr "只與能採用開放原始碼授權交付與發行其程式碼的開放原始碼軟體供應商合作。"
 
 #: ./open-licenses.md:block 15 (unordered list)
 msgid ""
@@ -1641,7 +1641,7 @@ msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授
 msgid ""
 "[Open source definition](https://opensource.org/osd) by the Open Source "
 "Initiative, all open source licenses meet this definition."
-msgstr "開源促進會所發表的《[開放原始碼定義](https://opensource.org/"
+msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/"
 "osd)》，所有開放原始碼授權條款皆符合這套定義。"
 
 #: ./open-licenses.md:block 19 (unordered list)
@@ -1686,7 +1686,7 @@ msgid ""
 "Initiative Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
 "[代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合["
-"開源促進會其開放標準需求規範](https://opensource.org/"
+"開放原始碼促進會其開放標準需求規範](https://opensource.org/"
 "osr)的[開放標準](../glossary.md#open-standard)。"
 
 #: ./open-standards.md:block 5 (unordered list)
@@ -1740,7 +1740,7 @@ msgstr "讓軟體的操作方法變得可以瞭解。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid "Confirm that data exchange follows an OSI approved open standard."
-msgstr "確認資料交換遵守 OSI 開源促進會批准的開放標準。"
+msgstr "確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。"
 
 #: ./open-standards.md:block 11 (unordered list)
 msgid ""
@@ -1934,7 +1934,7 @@ msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr "開源指南所提供的《[營造友善的社群](https://opensource.guide/"
+msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/"
 "building-community/)》。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
@@ -1943,9 +1943,9 @@ msgid ""
 "open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
 "source-project/) by Mike McQuaid."
 msgstr ""
-"Mike McQuaid《[開源貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-so"
-"urce-contributor-funnel-why-people-dont-contribute-to-your-open-source-projec"
-"t/)》。"
+"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-o"
+"pen-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
+"project/)》。"
 
 #: ./open-to-contributions.md:block 19 (unordered list)
 msgid ""
@@ -1953,7 +1953,7 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
-"開源指南為成長中的[開源](../glossary.md#open-"
+"開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-"
 "source)社群專案所寫的《[領導與治理](https://opensource.guide/"
 "leadership-and-governance/)》。"
 
@@ -2966,8 +2966,8 @@ msgid ""
 "Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
 "Fogel."
 msgstr ""
-"Karl Fogel《[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html"
-"#vc-vocabulary)》。"
+"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc"
+".html#vc-vocabulary)》。"
 
 #: ./version-control-and-history.md:block 22 (unordered list)
 msgid ""

From 65982c424bdf1c42efaf5296a2d083f3f9f2f7e9 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Fri, 5 May 2023 04:15:28 +0000
Subject: [PATCH 30/71] Save all files in criteria

Signed-off-by: Toomore Chiang <toomore0929@gmail.com>
---
 criteria/bundle-policy-and-code.md          | 57 ++++++++++++++++
 criteria/code-in-the-open.md                | 59 ++++++++++++++++
 criteria/continuous-integration.md          | 76 +++++++++++++++++++++
 criteria/document-maturity.md               | 61 +++++++++++++++++
 criteria/document-objectives.md             | 49 +++++++++++++
 criteria/documenting.md                     | 61 +++++++++++++++++
 criteria/findability.md                     | 67 ++++++++++++++++++
 criteria/index.md                           | 11 +++
 criteria/make-contributing-easy.md          | 51 ++++++++++++++
 criteria/open-licenses.md                   | 55 +++++++++++++++
 criteria/open-standards.md                  | 53 ++++++++++++++
 criteria/open-to-contributions.md           | 63 +++++++++++++++++
 criteria/require-review.md                  | 74 ++++++++++++++++++++
 criteria/reusable-and-portable-codebases.md | 74 ++++++++++++++++++++
 criteria/style.md                           | 54 +++++++++++++++
 criteria/understandable-english-first.md    | 60 ++++++++++++++++
 criteria/version-control-and-history.md     | 76 +++++++++++++++++++++
 17 files changed, 1001 insertions(+)
 create mode 100644 criteria/bundle-policy-and-code.md
 create mode 100644 criteria/code-in-the-open.md
 create mode 100644 criteria/continuous-integration.md
 create mode 100644 criteria/document-maturity.md
 create mode 100644 criteria/document-objectives.md
 create mode 100644 criteria/documenting.md
 create mode 100644 criteria/findability.md
 create mode 100644 criteria/index.md
 create mode 100644 criteria/make-contributing-easy.md
 create mode 100644 criteria/open-licenses.md
 create mode 100644 criteria/open-standards.md
 create mode 100644 criteria/open-to-contributions.md
 create mode 100644 criteria/require-review.md
 create mode 100644 criteria/reusable-and-portable-codebases.md
 create mode 100644 criteria/style.md
 create mode 100644 criteria/understandable-english-first.md
 create mode 100644 criteria/version-control-and-history.md

diff --git a/criteria/bundle-policy-and-code.md b/criteria/bundle-policy-and-code.md
new file mode 100644
index 00000000..57fa7bf2
--- /dev/null
+++ b/criteria/bundle-policy-and-code.md
@@ -0,0 +1,57 @@
+---
+order: 2
+---
+# 政策與原始碼要合捆
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須包含[原始碼](../glossary.md#code)所根據的[政策](../glossary.md#policy)。
+* 代碼庫必須包含根據政策而來的所有原始碼，用於偵測詐騙的原始碼則可除外。
+* 政策應該採用機器可讀且明確的格式。
+* [持續整合](../glossary.md#continuous-integration)測試應該驗證原始碼與政策能一致執行。
+
+## 此措施為何重要
+
+如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼庫，則組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境。
+
+## 此措施辦不到的事
+
+* 保證代碼庫能反映合捆的政策。
+* 確保成套合捆內容符合地方性技術基礎建設，或是特定公共組織的法律架構。
+
+## 測試方式
+
+* 與公務人員確認程式碼根據的所有政策內容都有包含在內。
+* 與公務人員確認根據政策而來的所有原始碼都有包含在內。
+* 確認政策內容是否能在機器上解讀。
+* 確認原始碼與政策間的執行一致性能通過持續整合測試。
+
+## 政策制定者：需要的工作
+
+* 與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。
+* 提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。
+* 請提供政策相關參考資料與連結。
+* 政策內容請使用明確且機器可讀的格式，像是[業務流程模型與標記法](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)、
+[決策模型與標記法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)，以及
+[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。
+* 追蹤政策時，請使用與追蹤原始碼[相同的版本控制](version-control-and-history.md)與文件。
+* 定期檢查代碼庫中非政策程式碼的變動，以及確認是否仍符合[政策意圖](document-objectives.md)。
+
+## 管理人員：需要的工作
+
+* 讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。
+* 確保政策制定者、開發人員與設計師朝相同目標努力。
+
+## 開發人員與設計師：需要的工作
+
+* 熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。
+* 與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。
+* 針對如何讓政策文字更清楚提供意見。
+
+## 延伸閱讀
+
+* Camunda [於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN 等模型與表記法圖表](https://bpmn.io/)的免費線上工具。
+* Trisotech 提供的 [BPMN 快速指南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。
diff --git a/criteria/code-in-the-open.md b/criteria/code-in-the-open.md
new file mode 100644
index 00000000..aec6c077
--- /dev/null
+++ b/criteria/code-in-the-open.md
@@ -0,0 +1,59 @@
+---
+order: 1
+---
+# 原始碼要開放
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 任何使用中的[政策](../glossary.md#policy)所有[原始碼](../glossary.md#code)都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
+* 任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
+* 貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到[儲存庫](../glossary.md#repository)中。
+* 目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。
+* 可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。
+
+## 此措施為何重要
+
+以開放精神編寫原始碼：
+
+* 改善資訊透明
+* 提高程式碼品質
+* 促進稽核流程
+
+這些面向讓公民更有機會瞭解軟體與政策如何影響其與公共組織的互動。
+
+## 此措施辦不到的事
+
+* 讓原始碼或政策可以重複使用。
+* 讓盡可能越多人能讀懂[代碼庫](../glossary.md#codebase)以及當中的程式碼。
+
+## 測試方式
+
+* 確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織之外，查看這些原始碼。
+* 確認代碼庫檔案與提交歷史紀錄不包含敏感性資訊。
+* 檢查目前非使用中的原始碼是否有公開。
+
+## 政策制定者：需要的工作
+
+* 制定合乎開放精神的政策。
+* 以公開透明的政策為優先。
+
+## 管理人員：需要的工作
+
+* 孕育擁抱開放、重視學習、歡迎意見回饋的文化。
+* 與外部供應商和自由工作者以開放精神的方式協作。
+
+## 開發人員與設計師：需要的工作
+
+* 審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。
+* 為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。
+
+## 延伸閱讀
+
+* 英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)》。
+* 英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed)》。
+* 英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open)》。
+* 英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/technology/deploying-software-regularly)》。
+* 英國政府數位服務團《[政府數位服務團如何使用 GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/)》。
diff --git a/criteria/continuous-integration.md b/criteria/continuous-integration.md
new file mode 100644
index 00000000..4506b880
--- /dev/null
+++ b/criteria/continuous-integration.md
@@ -0,0 +1,76 @@
+---
+order: 12
+---
+# 使用持續整合
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [原始碼](../glossary.md#code)中的所有功能都必須有自動化測試。
+* 所有貢獻內容都必須先通過自動化測試，才能上傳至[代碼庫](../glossary.md#codebase)。
+* 代碼庫必須有說明貢獻內容結構的相關準則。
+* 代碼庫必須有活躍貢獻者。
+* 代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。
+* 應該監督原始碼測試與文件的涵蓋範圍。
+* 可選擇是否測試[政策](../glossary.md#policy)和文件，與原始碼間有無一致性，或是反之亦然。
+* 可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。
+
+## 此措施為何重要
+
+* 使用[持續整合](../glossary.md#continuous-integration)：
+   * 可以讓您快速找出代碼庫的問題所在，
+   * 能在降低貢獻者面臨壓力的同時，允許承擔風險並且專注在解決問題上，
+   * 可降低新貢獻者對整體內容理解的門檻，讓他們更容易提出修改，
+   * 讓程式碼更容易維護，
+   * 能加速開發週期。
+* 修改內容較少、時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大、累積很久才一次提出的變更。
+* 活躍開發中的代碼庫較能提供協作與意見回饋的機會。
+
+## 此措施辦不到的事
+
+* 建立能夠順暢作業、可擴展，且能容錯的基礎架構。
+* 建立有意義的測試。
+* 測試實際會發生的情境。
+* 保證交付的程式碼與政策期望的成果確實相同。
+
+## 測試方式
+
+* 確認有測試可用。
+* 確認程式碼覆蓋率工具能檢查到 100% 的程式碼。
+* 確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。
+* 確認有貢獻準則說明貢獻內容的結構。
+* 確認最近三個月內有貢獻內容上傳。
+* 檢查程式碼覆蓋率數據是否有公布。
+
+## 政策制定者：需要的工作
+
+* 儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。
+* 確保政策文件也有設好自動化測試。
+* 如果政策文件未能通過測試，請立即修正。
+* 確保程式碼能反映出政策的任何變動（請參閱[維護版本控制](version-control-and-history.md)）。
+
+## 管理人員：需要的工作
+
+* 確保能儘快且經常給真正的終端使用者進行測試。
+* 以頻繁交付少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。
+* 聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。
+* 發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。
+
+## 開發人員與設計師：需要的工作
+
+* 協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次交付。
+* 協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。
+* 協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。
+* 編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。
+* 調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。
+* 經常部署。
+* 至少每天整合工作內容一次。
+
+## 延伸閱讀
+
+* Martin Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/continuousIntegration.html)》。
+* Jez Humble《[什麼是持續交付](https://www.continuousdelivery.com/)》。
+* 英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/standards/continuous-delivery.html)》。
+* 英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly)》。
diff --git a/criteria/document-maturity.md b/criteria/document-maturity.md
new file mode 100644
index 00000000..4a9703a5
--- /dev/null
+++ b/criteria/document-maturity.md
@@ -0,0 +1,61 @@
+---
+order: 16
+redirect_from:
+    - criteria/advertise-maturity
+---
+# 紀錄代碼庫成熟度
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須註明版本編號。
+* 準備好可供使用的代碼庫，必須只能依賴其他也已經準備好可供使用的代碼庫。
+* 尚未準備好使用的代碼庫，必須有所列標籤之一：prototype、alpha、beta、pre-release 等版本進度。
+* 代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
+
+## 此措施為何重要
+
+清楚標示代碼庫的成熟度，有助於他人決定是否要重複使用、投資，或為該代碼庫做出貢獻。
+
+## 此措施辦不到的事
+
+* 保證他人會來使用[程式碼](../glossary.md#code)。
+
+## 測試方式
+
+* 確認代碼庫有版本編號策略，且有文件記載該策略。
+* 確認有清楚表明最新版的取得位置。
+* 確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。
+* 確認代碼庫是已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-release 等開發中版本。
+* 檢查是否有變更紀錄。
+
+## 政策制定者：需要的工作
+
+* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的程式碼都必須先經過測試與改善，才能夠投入服務。
+* 考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。
+
+## 管理人員：需要的工作
+
+* 要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫，公測版服務不要使用 prototype
+原型代碼庫。
+* 若代碼庫尚未準備好供一般使用，請與開發人員一起確保該代碼庫是否有標示適當標籤：
+   * prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術的可行性概念，
+   * alpha：內部測試，在限制的一群使用者中進行引導性測試，
+   * beta：公開測試，讓更多[一般大眾](../glossary.md#general-public)參與測試，例如測試代碼庫在大規模操作下是否仍能運作，
+   * pre-release：準發行版，已經準備好發行，但尚未獲得正式批准的程式碼。
+
+## 開發人員與設計師：需要的工作
+
+* 在每個指示程式碼成熟度的介面中加上明顯的標頭。
+* 所有正式發行的程式碼都要有版本編號。
+* 特別是在採用「滾動發行」的情況下，程式碼的版本資訊可以根據[版本控制](../glossary.md#version-control)系統的中介資料自動衍生（例如使用
+[git describe](https://git-scm.com/docs/git-describe)）。
+
+## 延伸閱讀
+
+* 澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process)》。
+* 英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/agile-delivery)》。
+* 許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。
+* 英國政府數位服務團《[什麼是服務開發當中的探索、Alpha、Beta、上線階段？ [影片 0'0"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)》。
diff --git a/criteria/document-objectives.md b/criteria/document-objectives.md
new file mode 100644
index 00000000..90346b5b
--- /dev/null
+++ b/criteria/document-objectives.md
@@ -0,0 +1,49 @@
+---
+order: 8
+---
+# 代碼庫有目標文件
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
+* 代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
+* 可選擇是否以文件紀錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。
+
+## 此措施為何重要
+
+以文件紀錄代碼庫目標：
+
+* 提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。
+* 幫助劃定您自己開發專案的範圍。
+* 將代碼庫以及所包含模組的目的用途，清楚告知其他利害關係人與貢獻者。
+
+## 此措施辦不到的事
+
+* 保證代碼庫能達成其陳述的目標。
+* 保證會有人為代碼庫做出貢獻。
+* 預防其他代碼庫試圖達成相同目標。
+
+## 測試方式
+
+* 確認代碼庫文件有包含代碼庫目標，或主旨、使命等。
+* 查看政策目標與代碼庫目標之間關聯的描述。
+
+## 政策制定者：需要的工作
+
+* 將政策目標加入代碼庫文件中，例如「`README`」文件當中。
+* 納入會影響社會群體、代碼庫與開發目標的相關政策，例如可近用無障礙環境，或機會平等等價值或倫理取向的政策。
+
+## 管理人員：需要的工作
+
+* 將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。
+
+## 開發人員與設計師：需要的工作
+
+* 將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。
+
+## 延伸閱讀
+
+* Marek Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)》。
diff --git a/criteria/documenting.md b/criteria/documenting.md
new file mode 100644
index 00000000..e89a4af6
--- /dev/null
+++ b/criteria/documenting.md
@@ -0,0 +1,61 @@
+---
+order: 9
+---
+# 程式碼有文件
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)的所有功能、[政策](../glossary.md#policy)及原始碼，都必須以可清楚瞭解的用語描述，讓懂
+[程式碼](../glossary.md#code)目的用途的人也能夠理解。
+* 代碼庫文件必須說明如何安裝與執行原始碼。
+* 代碼庫文件必須為關鍵功能舉出範例。
+* 代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
+* 代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。
+* 代碼庫文件應該包含所有功能的範例。
+* 程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
+* 應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。
+* 可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。
+* 可選擇是否以文件中的範例來測試程式碼。
+
+## 此措施為何重要
+
+* 使用者可以更快速上手代碼庫的使用並做出貢獻。
+* 能幫助他人找到這個代碼庫，特別是那些在問「是不是已經有提供某某功能的程式碼」的人。
+* 讓貴組織單位與其流程資訊更透明。
+
+## 此措施辦不到的事
+
+* 直接貢獻出更可重複使用，以及更具可攜性的程式碼（請參閱[編寫可重複使用且具可攜性的程式碼](./reusable-and-portable-codebases.md)）。
+
+## 測試方式
+
+* 確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。
+* 確認文件有說明如何安裝與執行原始碼。
+* 確認文件有包含主要功能的範例。
+* 向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。
+* 檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。
+* 檢查文件中列舉的所有功能都包含範例。
+* 檢查文件中是否包含高層架構圖，或類似的組件關係圖表。
+* 確認整合測試有包含到程式碼文件品質，例如確認由程式碼生成的文件，並檢查連結與圖片等。
+
+## 政策制定者：需要的工作
+
+* 定期查看代碼庫的非政策程式碼的變動情況。
+* 針對如何讓非政策文件更清楚易懂提供意見回饋。
+
+## 管理人員：需要的工作
+
+* 嘗試使用代碼庫。
+* 確保您同時瞭解政策、原始碼以及文件內容。
+
+## 開發人員與設計師：需要的工作
+
+* 定期查看代碼庫中非原始碼部分的變動情況。
+* 針對如何讓非原始碼文件更清楚易懂提供意見回饋。
+
+## 延伸閱讀
+
+* Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。
diff --git a/criteria/findability.md b/criteria/findability.md
new file mode 100644
index 00000000..3feb6913
--- /dev/null
+++ b/criteria/findability.md
@@ -0,0 +1,67 @@
+---
+order: 14
+---
+# 代碼庫可查詢得到
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，必須能搜尋得到[代碼庫](../glossary.md#codebase)。
+* 在搜尋引擎查找代碼庫名稱時，必須能搜尋得到代碼庫。
+* 維護人員應該將代碼庫提交至相關的軟體目錄上。
+* 代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。
+* 代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
+* 代碼庫應該包含機器可讀的中介資料說明，例如採用 [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)
+格式的檔案。
+* 可選擇是否為代碼庫設定專用的網域名稱。
+* 可選擇是否在社群舉辦的會議中定期進行簡報。
+
+## 此措施為何重要
+
+* 必須主動積極；不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫。
+* 有中介資料說明檔案會讓代碼庫更容易被發現。
+* 一旦代碼庫越容易被發現，更多的潛在協作者也就找得到它。
+* 撰寫出良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF
+自由軟體基金會的軟體目錄列表之中，使代碼庫成為語意網路中的一部份。如此一來，他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。
+
+## 此措施辦不到的事
+
+* 確認新的協作人員或複製者。
+
+## 測試方式
+
+* 確認以白話英文敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 檢查代碼庫有刊登在相關軟體型錄上。
+* 檢查代碼庫的網站有描述代碼庫能夠解決的問題。
+* 檢查永久唯一識別碼條目有提及主要貢獻者。
+* 檢查永久唯一識別碼條目中有包含儲存庫位置。
+* 檢查永久唯一識別碼條目有列出代碼庫網站。
+* 檢查中介資料說明檔案是機器可讀的格式。
+
+## 政策制定者：需要的工作
+
+* 貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。
+* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
+* 在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。
+
+## 管理人員：需要的工作
+
+* 為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。
+* 確保專案參與人員出席相關會議或作簡報介紹。
+* 在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。
+
+## 開發人員與設計師：需要的工作
+
+* 搜尋引擎最佳化。
+* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
+* 推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。
+
+## 延伸閱讀
+
+* Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
+* FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
+* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。
diff --git a/criteria/index.md b/criteria/index.md
new file mode 100644
index 00000000..7891057e
--- /dev/null
+++ b/criteria/index.md
@@ -0,0 +1,11 @@
+# 準則
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+{% assign sorted = site.pages | sort:"order" %}
+
+{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name !=
+"index.md" %}{% if page.title %}
+
+1. [{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
new file mode 100644
index 00000000..3be804c6
--- /dev/null
+++ b/criteria/make-contributing-easy.md
@@ -0,0 +1,51 @@
+---
+order: 5
+---
+# 貢獻要容易
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須有個可以公開接受任何人建議的議題追蹤器。
+* 代碼庫必須說明，如何私下回報安全性問題來達成負責任的揭露。
+* 文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。
+* 代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵遞論壇）。
+* 文件應該說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。
+
+## 此措施為何重要
+
+* 讓使用者能夠為共享的代碼庫修復問題與新增功能，能讓軟體變得更好、更可靠、功能更豐富。
+* 讓人們能以協作方式採用共享的數位基礎建設。
+* 幫助使用者在代碼庫間做出選擇。
+
+## 此措施辦不到的事
+
+* 保證其他人會重複使用代碼庫。
+
+## 測試方式
+
+* 確認有公開的議題追蹤器。
+* 確認有說明如何私下通報安全性問題。
+* 確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。
+* 確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。
+
+## 政策制定者：需要的工作
+
+* 追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。
+
+## 管理人員：需要的工作
+
+* 追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。
+* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。
+
+## 開發人員與設計師：需要的工作
+
+* 快速回應請求。
+* 持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。
+
+## 延伸閱讀
+
+* Joel Hans《[如何引發他人為您的開源專案做出優秀貢獻](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf)》。
+* 英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/)》。
diff --git a/criteria/open-licenses.md b/criteria/open-licenses.md
new file mode 100644
index 00000000..7dc4c462
--- /dev/null
+++ b/criteria/open-licenses.md
@@ -0,0 +1,55 @@
+---
+order: 13
+---
+# 發行採用開放授權
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。
+* 軟體原始碼必須採用[經 OSI 開源促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。
+* 所有程式碼皆必須搭配授權條款檔案一併發行。
+* 不得要求貢獻者將其貢獻的程式碼著作權轉讓給[代碼庫](../glossary.md#codebase)。
+* 代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。
+* 可選擇是否為不同類型的程式碼與文件採用多重授權條款。
+
+## 此措施為何重要
+
+* 讓任何人都可以查看程式碼，並知道他們可以與該如何重複利用這些程式碼。
+
+## 此措施辦不到的事
+
+* 預防任何特定行為人使用程式碼。
+
+## 測試方式
+
+* 確認代碼庫有清楚給予授權條款。
+* 確認原始碼的授權條款有列於[經 OSI 開源促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/)，以及文件的授權條款有
+[符合「開放定義」](https://opendefinition.org/licenses/)。
+* 確認代碼庫中有包含其採用的授權條款檔案。
+* 確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
+* 在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。
+
+## 政策制定者：需要的工作
+
+* 制定要求程式碼必須採用[開源](../glossary.md#open-source)授權的[政策](../glossary.md#policy)。
+* 制定抑制採購非開源授權程式碼與非開放科技的政策。
+
+## 管理人員：需要的工作
+
+* 只與能採用開源授權交付與發行其程式碼的開源軟體供應商合作。
+* 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
+
+## 開發人員與設計師：需要的工作
+
+* 每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。
+* 每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。
+
+## 延伸閱讀
+
+* 開源促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
+* 紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/videos/creative-commons-kiwi)》。
+* 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。
+* Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示法。
diff --git a/criteria/open-standards.md b/criteria/open-standards.md
new file mode 100644
index 00000000..ba436234
--- /dev/null
+++ b/criteria/open-standards.md
@@ -0,0 +1,53 @@
+---
+order: 11
+---
+
+# 採用開放標準
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合[開源促進會其開放標準需求規範](https://opensource.org/osr)的
+[開放標準](../glossary.md#open-standard)。
+* 如果有使用到任何的非開放標準，則必須在文件中清楚記錄。
+* 代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。
+* 代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。
+* 如果還沒有已存在的開放標準可採用，則應該投入開發新標準。
+* 採用標準時，應該優先選擇可經機器測試的標準。
+
+## 此措施為何重要
+
+* 為不同的系統之間建立互通性。
+* 降低廠商套牢的可能性。
+* 保證可以取得重複利用與貢獻代碼庫所需的知識。
+
+## 此措施辦不到的事
+
+* 讓軟體的操作方法變得可以瞭解。
+
+## 測試方式
+
+* 確認資料交換遵守 OSI 開源促進會批准的開放標準。
+* 確認若有採用任何的非開放標準，皆有清楚記錄在文件中。
+* 確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
+
+## 政策制定者：需要的工作
+
+* 以政策要求盡可能在任何情況下使用開放標準。
+* 禁止採購不採用開放標準的技術科技。
+
+## 管理人員：需要的工作
+
+* 考慮在[程式碼](../glossary.md#code)審查中納入開放標準依循評估。
+
+## 開發人員與設計師：需要的工作
+
+* 將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。
+* 審查提交紀錄與其他[儲存庫](../glossary.md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。
+
+## 延伸閱讀
+
+* 英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles)》
+[政策](../glossary.md#policy)報告。
diff --git a/criteria/open-to-contributions.md b/criteria/open-to-contributions.md
new file mode 100644
index 00000000..2a0b24a9
--- /dev/null
+++ b/criteria/open-to-contributions.md
@@ -0,0 +1,63 @@
+---
+order: 4
+---
+
+# 歡迎貢獻者
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須允許任何人針對代碼庫提出修改建議。
+* 代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
+* 代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
+* 代碼庫應該宣布投入其開發與維護工作的參與組織單位。
+* 代碼庫應該要有可公開取得的發展路線圖。
+* 代碼庫應該公布代碼庫的活動統計數據。
+* 可選擇是否為代碼庫加入貢獻者的行為準則。
+
+## 此措施為何重要
+
+* 幫助新參與者瞭解並且信任代碼庫社群的領導。
+* 避免參與者因為無法影響代碼庫的目標與進展，而造成代碼庫社群分裂成分歧的社群。
+* 幫助使用者在代碼庫間做出選擇。
+
+## 此措施辦不到的事
+
+* 保證他人會參與社群。
+* 保證其他人會重複使用代碼庫。
+
+## 測試方式
+
+* 確認可以提交修改建議給代碼庫。
+* 確認代碼庫有貢獻指引。
+* 確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。
+* 檢查是否有參與的組織單位名單。
+* 檢查是否有發展路線圖。
+* 檢查是否有公布活動統計數據。
+* 檢查是否有行為準則。
+
+## 政策制定者：需要的工作
+
+* 為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。
+* 考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。
+
+## 管理人員：需要的工作
+
+* 確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。
+* 如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。
+* 確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。
+* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
+
+## 開發人員與設計師：需要的工作
+
+* 快速回應請求。
+* 持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。
+
+## 延伸閱讀
+
+* 開源指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
+* Mike McQuaid《[開源貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
+* 開源指南為成長中的[開源](../glossary.md#open-source)社群專案所寫的《[領導與治理](https://opensource.guide/leadership-and-governance/)》。
+* Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。
diff --git a/criteria/require-review.md b/criteria/require-review.md
new file mode 100644
index 00000000..16e37f9c
--- /dev/null
+++ b/criteria/require-review.md
@@ -0,0 +1,74 @@
+---
+order: 7
+---
+
+# 要求審查貢獻內容
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 所有被接受或是提交給[代碼庫](../glossary.md#codebase)正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。
+* 審查必須包含原始碼、[政策](../glossary.md#policy)、測試、文件等。
+* 如果不接受貢獻內容，審查人員必須提供意見回饋。
+* 貢獻內容應該遵循代碼庫的標準、架構、決策安排等，以通過審查。
+* 審查內容應該包含執行[程式碼](../glossary.md#code)與執行代碼庫測試。
+* 貢獻內容應該由與貢獻者不同背景情境的人來審查。
+* 版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。
+* 審查應該在兩個工作天內進行。
+* 可選擇是否由多位審查人員進行審查。
+
+## 此措施為何重要
+
+* 提升代碼庫品質。
+* 降低安全性風險與營運風險。
+* 打造每份貢獻內容皆能有品質的文化。
+* 揪出可能發生的極明顯錯誤。
+* 只有真正能為代碼庫提升價值的貢獻內容才會被接受，可以給予貢獻者安全感。
+* 向貢獻者保證在一段時間內提供意見回饋或是合作改善。
+* 快速審查能提高貢獻者交付貢獻內容的頻率以及參與熱度。
+
+## 此措施辦不到的事
+
+* 保證能找到問題的合適解決方案。
+* 代表審查人員必須承擔責任。
+* 貢獻者從編寫文件與測試中免除責任。
+* 提供您合適的審查人選。
+
+## 測試方式
+
+* 確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。
+* 確認審查內容包含原始碼、政策、測試、文件等。
+* 針對未被採用的貢獻內容，確認有適當解釋原因。
+* 檢查審查範圍有涵蓋是否遵循標準、架構、代碼庫指引等。
+* 檢查審查人員在審查時是否有執行程式碼與測試。
+* 與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。
+* 檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。
+* 檢查貢獻提交與審查之間的時間間隔。
+
+## 政策制定者：需要的工作
+
+* 制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。
+* 採用具有審查與意見回饋功能的版本控制系統或作業流程。
+
+## 管理人員：需要的工作
+
+* 將交付妥善程式碼作為共同目標。
+* 確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。
+* 創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。
+* 確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。
+
+## 開發人員與設計師：需要的工作
+
+* 請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。
+* 當他人請求您審查程式碼時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。
+
+## 延伸閱讀
+
+* 英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content)》。
+* [GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)
+與 [GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)
+平臺的分支保護說明。
+* Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/)》。
+* Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)》。
diff --git a/criteria/reusable-and-portable-codebases.md b/criteria/reusable-and-portable-codebases.md
new file mode 100644
index 00000000..c164d4db
--- /dev/null
+++ b/criteria/reusable-and-portable-codebases.md
@@ -0,0 +1,74 @@
+---
+order: 3
+---
+
+# 程式碼要可重複使用且可攜
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)必須開發成能在[不同情境](../glossary.md#different-contexts)中重複使用。
+* 執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的[程式碼](../glossary.md#code)或服務。
+* 代碼庫應該有多方單位使用。
+* 發展路線圖應該有多方單位的需求影響。
+* 應該使用組態設定方式以將程式碼調整成能適應各情境的特定需求。
+* 代碼庫應該能夠在地化。
+* 程式碼與其文件不應該包含特定情況專用的資訊。
+* 代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。
+
+## 此措施為何重要
+
+* 讓其他政策制定者、開發人員與設計師等，能夠重複利用您所開發的內容，以及測試它、改善它，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。
+* 讓新進人員能更容易瞭解程式碼（因為用途更廣泛通用）。
+* 由於代碼庫以重複利用為前提籌劃設計，因此要調控代碼庫的目標使命、願景與範圍等也更容易。
+* 多方使用的代碼庫更可以從能自我運作的社群中獲益。
+* 任何貢獻者都能測試與貢獻給代碼庫，不需要仰賴任何其他貢獻者或部署底下的特定情況專用基礎架構。
+* 以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。
+* 以文件清楚記錄用途的模組，更容易在另一種情境中重複利用。
+
+## 此措施辦不到的事
+
+* 讓他人重複利用代碼庫。
+* 建立社群。
+* 將文件、支援、修正錯誤⋯⋯等責任轉移給其他單位。
+* 保證模組在任何情境下都足以通用。
+
+## 測試方式
+
+* 與另一組織單位角色與您相似的人確認，看他們是否能重複利用代碼庫，以及需要怎麼進行。
+* 確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。
+* 檢查是否有多方單位或是有在多種情境下正使用代碼庫。
+* 檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。
+
+## 政策制定者：需要的工作
+
+* 為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。
+* 確保代碼庫有將貴組織單位列為已知用戶。
+
+## 管理人員：需要的工作
+
+* 確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。
+
+## 開發人員與設計師：需要的工作
+
+原始碼應該設計成：
+
+* 能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，
+* 能解決通用性質問題，而非特定問題，
+* 以邏輯上具有意義且獨立的模組構成，
+* 如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。
+
+確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行開發、使用、測試、部署等。
+
+在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。
+
+## 延伸閱讀
+
+* 英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable)》。
+* OpenAPI 促進會定義的《[OpenAPI 規範](https://spec.openapis.org/oas/latest.html)》，為人機可讀的
+HTTP API 標準，不受程式語言種類限制的介面描述。
+* W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/questions/qa-i18n)》。
+* 全球資訊網協會《[國際化技巧：編寫 HTML 與 CSS](https://www.w3.org/International/techniques/authoring-html)》。
+* GNU 作業系統的 [GNU gettext](https://www.gnu.org/software/gettext/gettext.html)。
diff --git a/criteria/style.md b/criteria/style.md
new file mode 100644
index 00000000..8437f4e3
--- /dev/null
+++ b/criteria/style.md
@@ -0,0 +1,54 @@
+---
+order: 15
+---
+
+# 風格要前後一致
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是[代碼庫](../glossary.md#codebase)社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既有風格。
+* 貢獻內容應該通過自動化的風格測試。
+* 代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。
+* 可選擇是否將[可理解的英文](understandable-english-first.md)小節加入風格指南之中。
+
+## 此措施為何重要
+
+* 讓不同環境的貢獻者可以在統合的產品上合作。
+* 用詞統一能減少貢獻者之間在溝通上的摩擦。
+
+## 此措施辦不到的事
+
+* 幫助貢獻者寫好程式碼，或者精確說明他們在做什麼。
+
+## 測試方式
+
+* 確認貢獻內容有遵循文件中指定的風格指南。
+* 檢查是否有自動化的風格測試。
+
+## 政策制定者：需要的工作
+
+* 為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或「
+`README`」檔案。
+
+## 管理人員：需要的工作
+
+* 將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。
+
+## 開發人員與設計師：需要的工作
+
+如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是「
+`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查的其他層面。指南應該包含貢獻的
+[程式碼](../glossary.md#code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。
+
+此外：
+
+* 使用程式碼品質分析工具 (linter)。
+* 在代碼庫中加入程式碼品質分析工具的組態設定。
+
+## 延伸閱讀
+
+* Hugo Martins《[程式碼品質分析工具清單](https://github.com/caramelomartins/awesome-linters)》。
+* 維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。
diff --git a/criteria/understandable-english-first.md b/criteria/understandable-english-first.md
new file mode 100644
index 00000000..b7278299
--- /dev/null
+++ b/criteria/understandable-english-first.md
@@ -0,0 +1,60 @@
+---
+order: 10
+---
+
+# 使用白話的英語
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* [代碼庫](../glossary.md#codebase)的所有文件都必須使用英語。
+* 所有[程式碼](../glossary.md#code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀當作程式碼的部分則除外。
+* 任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。
+* 任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。
+* 代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
+* 代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
+* 根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。
+* 可選擇是否提供任何程式碼、文件、測試等的翻譯版。
+
+## 此措施為何重要
+
+* 讓不同情境的廣大利害關係人，都能瞭解代碼庫以及其用途。
+* 讓代碼庫更容易被找到。
+* 能幫助您達成《[歐盟無障礙環境命令](https://ec.europa.eu/digital-single-market/en/web-accessibility)》，內容要求大多數的公家機關資訊都要能夠近用以滿足無障礙環境。
+
+## 此措施辦不到的事
+
+* 讓代碼庫功能解說更容易瞭解。
+* 幫助他人在沒有額外解釋之下，就能理解貴組織單位的業內用語。
+
+## 測試方式
+
+* 確認代碼庫文件有英語版本。
+* 確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。
+* 確認任何非英語政策都有隨附英語版摘要。
+* 確認翻譯版與英語版內容相同。
+* 確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。
+* 檢查文件的拼字、文法與易讀性等。
+
+## 政策制定者：需要的工作
+
+* 在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
+
+## 管理人員：需要的工作
+
+* 在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在使用這些詞彙的地方加上詞彙表連結。
+* 以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。
+
+## 開發人員與設計師：需要的工作
+
+* 經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
+* 詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。
+
+## 延伸閱讀
+
+* 根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 之可讀性](https://www.w3.org/TR/WCAG21/#readable)》內文，撰寫的文字內容要更容易閱讀與理解。
+* Theo Sanderson 所發表的「[Upgoer 5 文字編輯軟體](https://splasho.com/upgoer5/)」只允許使用最常用的
+1000 個英文單字。
+* 美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/)》。
diff --git a/criteria/version-control-and-history.md b/criteria/version-control-and-history.md
new file mode 100644
index 00000000..ac2fa147
--- /dev/null
+++ b/criteria/version-control-and-history.md
@@ -0,0 +1,76 @@
+---
+order: 6
+---
+
+# 維護版本控制
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## 需求規範
+
+* 社群必須要有方法為[程式碼](../glossary.md#code)維護[版本控制](../glossary.md#version-control)。
+* [代碼庫](../glossary.md#codebase)中的所有檔案皆必須有版本控制。
+* 所有決定皆必須記錄成提交訊息。
+* 每份提交訊息皆必須盡可能附上討論與議題連結。
+* 代碼庫應該以分散式版本控制系統作維護。
+* 貢獻者應該將相關的修改變動提交內容作群組分類。
+* 維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。
+* 貢獻者應該偏好使用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。
+* 貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
+
+## 此措施為何重要
+
+版本控制代表追蹤程式碼歷來的變動。這能讓您為代碼庫製作有條理的變動歷史文件。這是大規模協作能運作的要素。
+
+分散式版本控制能讓您：
+
+* 擁有完整的程式碼副本與其版本歷史
+* 在需要時可以將代碼庫恢復至先前版本
+* 紀錄變動與變動的原因，可幫助未來開發人員瞭解整個過程
+* 比較兩個不同版本
+* 在將修改內容合併回代碼庫之前，各團隊可以針對修改變動平行作業
+* 在沒有網路時也能繼續作業，可以日後再將修改變動合併回代碼庫與其他人整合
+
+## 此措施辦不到的事
+
+* 代替[成熟度宣告](document-maturity.md)。
+* 保證程式碼能正確執行。
+* 保證有人加入協作。
+
+## 測試方式
+
+* 確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。
+* 審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。
+* 審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。
+* 檢查版本控制系統是否為分散式。
+* 審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。
+* 檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。
+* 檢查代碼庫在可能的情況下，檔案都是採用文字格式。
+
+## 政策制定者：需要的工作
+
+* 如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
+   * 政策改變的地方，
+   * 代碼庫如何因應而改變。
+
+舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。
+
+## 管理人員：需要的工作
+
+* 支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。
+
+## 開發人員與設計師：需要的工作
+
+* 提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。
+* 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。
+* 提交內容的訊息要寫清楚，方便之後比較各版本。
+* 在政策改變以後與政策制定者合作，說明原始碼更新的內容。
+
+## 延伸閱讀
+
+* Karl Fogel《[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html#vc-vocabulary)》。
+* 英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding)》。
+* GitHub 提供的「[GitHub學習實驗室](https://lab.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
+* GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-education.pdf)」列出了最常用的
+git 指令。

From a4175945740e09f1f2eec5bc12342f0c17ee6c28 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Fri, 5 May 2023 04:31:44 +0000
Subject: [PATCH 31/71] Update

Signed-off-by: Toomore Chiang <toomore0929@gmail.com>
---
 criteria/code-in-the-open.md            |  6 +++---
 criteria/document-objectives.md         |  4 ++--
 criteria/findability.md                 |  4 ++--
 criteria/make-contributing-easy.md      |  2 +-
 criteria/open-licenses.md               | 12 ++++++------
 criteria/open-standards.md              |  4 ++--
 criteria/open-to-contributions.md       |  6 +++---
 criteria/require-review.md              |  2 +-
 criteria/style.md                       |  2 +-
 criteria/version-control-and-history.md |  2 +-
 10 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/criteria/code-in-the-open.md b/criteria/code-in-the-open.md
index aec6c077..e19c1a54 100644
--- a/criteria/code-in-the-open.md
+++ b/criteria/code-in-the-open.md
@@ -12,17 +12,17 @@ order: 1
 * 任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
 * 貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到[儲存庫](../glossary.md#repository)中。
 * 目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。
-* 可選擇是否要以文件紀錄[一般大眾](../glossary.md#general-public)與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。
+* 可選擇是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。
 
 ## 此措施為何重要
 
-以開放精神編寫原始碼：
+以開放精神編寫原始碼能：
 
 * 改善資訊透明
 * 提高程式碼品質
 * 促進稽核流程
 
-這些面向讓公民更有機會瞭解軟體與政策如何影響其與公共組織的互動。
+這些面向讓公民更有機會能瞭解，軟體與政策如何影響他們與公共組織的互動。
 
 ## 此措施辦不到的事
 
diff --git a/criteria/document-objectives.md b/criteria/document-objectives.md
index 90346b5b..959cd61a 100644
--- a/criteria/document-objectives.md
+++ b/criteria/document-objectives.md
@@ -10,11 +10,11 @@ order: 8
 
 * [代碼庫](../glossary.md#codebase)必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
 * 代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
-* 可選擇是否以文件紀錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。
+* 可選擇是否以文件記錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。
 
 ## 此措施為何重要
 
-以文件紀錄代碼庫目標：
+以文件記錄代碼庫目標：
 
 * 提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。
 * 幫助劃定您自己開發專案的範圍。
diff --git a/criteria/findability.md b/criteria/findability.md
index 3feb6913..0f35ae8d 100644
--- a/criteria/findability.md
+++ b/criteria/findability.md
@@ -32,7 +32,7 @@ order: 14
 
 ## 測試方式
 
-* 確認以白話英文敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 確認以白話英語敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
 * 確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
 * 確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
 * 檢查代碼庫有刊登在相關軟體型錄上。
@@ -64,4 +64,4 @@ order: 14
 
 * Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
 * FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
-* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分屬性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。
+* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
index 3be804c6..161bec67 100644
--- a/criteria/make-contributing-easy.md
+++ b/criteria/make-contributing-easy.md
@@ -47,5 +47,5 @@ order: 5
 
 ## 延伸閱讀
 
-* Joel Hans《[如何引發他人為您的開源專案做出優秀貢獻](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf)》。
+* Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf)》。
 * 英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/)》。
diff --git a/criteria/open-licenses.md b/criteria/open-licenses.md
index 7dc4c462..b67889f5 100644
--- a/criteria/open-licenses.md
+++ b/criteria/open-licenses.md
@@ -9,7 +9,7 @@ order: 13
 ## 需求規範
 
 * 所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。
-* 軟體原始碼必須採用[經 OSI 開源促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。
+* 軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。
 * 所有程式碼皆必須搭配授權條款檔案一併發行。
 * 不得要求貢獻者將其貢獻的程式碼著作權轉讓給[代碼庫](../glossary.md#codebase)。
 * 代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。
@@ -26,7 +26,7 @@ order: 13
 ## 測試方式
 
 * 確認代碼庫有清楚給予授權條款。
-* 確認原始碼的授權條款有列於[經 OSI 開源促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/)，以及文件的授權條款有
+* 確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/)，以及文件的授權條款有
 [符合「開放定義」](https://opendefinition.org/licenses/)。
 * 確認代碼庫中有包含其採用的授權條款檔案。
 * 確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
@@ -34,12 +34,12 @@ order: 13
 
 ## 政策制定者：需要的工作
 
-* 制定要求程式碼必須採用[開源](../glossary.md#open-source)授權的[政策](../glossary.md#policy)。
-* 制定抑制採購非開源授權程式碼與非開放科技的政策。
+* 制定要求程式碼必須採用[開放原始碼](../glossary.md#open-source)授權的[政策](../glossary.md#policy)。
+* 制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。
 
 ## 管理人員：需要的工作
 
-* 只與能採用開源授權交付與發行其程式碼的開源軟體供應商合作。
+* 只與能採用開放原始碼授權交付與發行其程式碼的開放原始碼軟體供應商合作。
 * 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
 
 ## 開發人員與設計師：需要的工作
@@ -49,7 +49,7 @@ order: 13
 
 ## 延伸閱讀
 
-* 開源促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
+* 開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
 * 紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/videos/creative-commons-kiwi)》。
 * 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。
 * Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示法。
diff --git a/criteria/open-standards.md b/criteria/open-standards.md
index ba436234..0c243dcd 100644
--- a/criteria/open-standards.md
+++ b/criteria/open-standards.md
@@ -9,7 +9,7 @@ order: 11
 
 ## 需求規範
 
-* [代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合[開源促進會其開放標準需求規範](https://opensource.org/osr)的
+* [代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的
 [開放標準](../glossary.md#open-standard)。
 * 如果有使用到任何的非開放標準，則必須在文件中清楚記錄。
 * 代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。
@@ -29,7 +29,7 @@ order: 11
 
 ## 測試方式
 
-* 確認資料交換遵守 OSI 開源促進會批准的開放標準。
+* 確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。
 * 確認若有採用任何的非開放標準，皆有清楚記錄在文件中。
 * 確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
 
diff --git a/criteria/open-to-contributions.md b/criteria/open-to-contributions.md
index 2a0b24a9..4f967d29 100644
--- a/criteria/open-to-contributions.md
+++ b/criteria/open-to-contributions.md
@@ -57,7 +57,7 @@ order: 4
 
 ## 延伸閱讀
 
-* 開源指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
-* Mike McQuaid《[開源貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
-* 開源指南為成長中的[開源](../glossary.md#open-source)社群專案所寫的《[領導與治理](https://opensource.guide/leadership-and-governance/)》。
+* 開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
+* Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
+* 開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治理](https://opensource.guide/leadership-and-governance/)》。
 * Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。
diff --git a/criteria/require-review.md b/criteria/require-review.md
index 16e37f9c..d6789e4d 100644
--- a/criteria/require-review.md
+++ b/criteria/require-review.md
@@ -33,7 +33,7 @@ order: 7
 
 * 保證能找到問題的合適解決方案。
 * 代表審查人員必須承擔責任。
-* 貢獻者從編寫文件與測試中免除責任。
+* 貢獻者能從編寫文件與測試中免除責任。
 * 提供您合適的審查人選。
 
 ## 測試方式
diff --git a/criteria/style.md b/criteria/style.md
index 8437f4e3..a0f6b3e5 100644
--- a/criteria/style.md
+++ b/criteria/style.md
@@ -12,7 +12,7 @@ order: 15
 * 貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是[代碼庫](../glossary.md#codebase)社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既有風格。
 * 貢獻內容應該通過自動化的風格測試。
 * 代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。
-* 可選擇是否將[可理解的英文](understandable-english-first.md)小節加入風格指南之中。
+* 可選擇是否將[可理解的白話英語](understandable-english-first.md)小節加入風格指南之中。
 
 ## 此措施為何重要
 
diff --git a/criteria/version-control-and-history.md b/criteria/version-control-and-history.md
index ac2fa147..9e230a27 100644
--- a/criteria/version-control-and-history.md
+++ b/criteria/version-control-and-history.md
@@ -69,7 +69,7 @@ order: 6
 
 ## 延伸閱讀
 
-* Karl Fogel《[製作開源軟體：版本控制字彙](https://producingoss.com/en/vc.html#vc-vocabulary)》。
+* Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc.html#vc-vocabulary)》。
 * 英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding)》。
 * GitHub 提供的「[GitHub學習實驗室](https://lab.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
 * GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-education.pdf)」列出了最常用的

From 14e56d6b15d40c9ed877fa0f1a69e233af4c8550 Mon Sep 17 00:00:00 2001
From: Toomore Chiang <toomore0929@gmail.com>
Date: Fri, 5 May 2023 04:35:57 +0000
Subject: [PATCH 32/71] Add `_site` files

Signed-off-by: Toomore Chiang <toomore0929@gmail.com>
---
 _site/404.html                                |  287 ++
 _site/AUTHORS.html                            |  324 ++
 _site/AUTHORS.md                              |   35 +
 _site/CHANGELOG.html                          |  487 +++
 _site/CHANGELOG.md                            |  163 +
 _site/CODE_OF_CONDUCT.html                    |  302 ++
 _site/CODE_OF_CONDUCT.md                      |   15 +
 _site/CONTRIBUTING.html                       |  393 +++
 _site/CONTRIBUTING.md                         |   87 +
 _site/GOVERNANCE.html                         |  301 ++
 _site/GOVERNANCE.md                           |   14 +
 _site/LICENSE                                 |  121 +
 _site/README.html                             |  347 ++
 _site/README.md                               |   55 +
 _site/assets/cc-zero-badge.svg                |   12 +
 _site/assets/codebase.svg                     |  134 +
 _site/assets/collaboration.svg                |   37 +
 _site/assets/collaborative-developement.svg   |   50 +
 _site/assets/dpg-badge.svg                    |   53 +
 _site/assets/eco-system.svg                   |   57 +
 _site/assets/github-markdown.css              |  695 ++++
 _site/assets/hand-point.svg                   |    6 +
 _site/assets/hands-shake.svg                  |   15 +
 _site/assets/rouge-highlight.css              |  210 ++
 _site/assets/style.css                        |  873 +++++
 _site/assets/unlock.svg                       |   36 +
 _site/criteria/advertise-maturity.html        |   11 +
 _site/criteria/bundle-policy-and-code.html    |  562 ++++
 _site/criteria/code-in-the-open.html          |  558 +++
 _site/criteria/continuous-integration.html    |  586 ++++
 _site/criteria/document-maturity.html         |  559 +++
 _site/criteria/document-objectives.html       |  556 +++
 _site/criteria/documenting.html               |  568 ++++
 _site/criteria/findability.html               |  574 ++++
 _site/criteria/index.html                     |  342 ++
 _site/criteria/index.md                       |   11 +
 _site/criteria/make-contributing-easy.html    |  558 +++
 _site/criteria/open-licenses.html             |  562 ++++
 _site/criteria/open-standards.html            |  559 +++
 _site/criteria/open-to-contributions.html     |  569 ++++
 _site/criteria/require-review.html            |  580 ++++
 .../reusable-and-portable-codebases.html      |  580 ++++
 _site/criteria/style.html                     |  560 +++
 .../understandable-english-first.html         |  566 ++++
 .../criteria/version-control-and-history.html |  585 ++++
 .../bundle-policy-and-code.html               |  364 ++
 _site/criteria_source/code-in-the-open.html   |  368 ++
 .../continuous-integration.html               |  388 +++
 _site/criteria_source/document-maturity.html  |  367 ++
 .../criteria_source/document-objectives.html  |  358 ++
 _site/criteria_source/documenting.html        |  369 ++
 _site/criteria_source/findability.html        |  374 ++
 _site/criteria_source/index.html              |  342 ++
 _site/criteria_source/index.md                |   10 +
 .../make-contributing-easy.html               |  360 ++
 _site/criteria_source/open-licenses.html      |  363 ++
 _site/criteria_source/open-standards.html     |  359 ++
 .../open-to-contributions.html                |  371 ++
 _site/criteria_source/require-review.html     |  380 +++
 .../reusable-and-portable-codebases.html      |  382 +++
 _site/criteria_source/style.html              |  362 ++
 .../understandable-english-first.html         |  367 ++
 .../version-control-and-history.html          |  386 +++
 _site/docs/printing.html                      |  309 ++
 _site/docs/printing.md                        |   20 +
 _site/docs/releasing.html                     |  384 +++
 _site/docs/releasing.md                       |   56 +
 _site/docs/review-template.html               | 1086 ++++++
 _site/docs/review-template.md                 |  222 ++
 _site/docs/roadmap.html                       |  330 ++
 _site/docs/roadmap.md                         |   33 +
 _site/docs/standard-for-public-code.html      | 1120 ++++++
 _site/docs/standard-for-public-code.md        |  224 ++
 _site/glossary.html                           |  379 +++
 _site/glossary.md                             |   78 +
 _site/images/audit-flow.dot                   |  198 ++
 _site/images/audit-flow.svg                   |  348 ++
 _site/index.html                              |  331 ++
 _site/index.md                                |   39 +
 _site/introduction.html                       |  511 +++
 _site/introduction.md                         |  172 +
 _site/license.html                            |  400 +++
 _site/locales/en/LC_MESSAGES/messages.po      | 2716 +++++++++++++++
 _site/locales/zh_Hant/LC_MESSAGES/messages.po | 2995 +++++++++++++++++
 _site/print-cover.html                        |  294 ++
 _site/print-review-template.html              |  925 +++++
 _site/print.html                              | 2529 ++++++++++++++
 _site/publiccode.yml                          |   74 +
 _site/readers-guide.html                      |  353 ++
 _site/readers-guide.md                        |   56 +
 _site/redirects.json                          |    1 +
 _site/script/check-new-links.sh               |   61 +
 _site/script/find-missing-spdx.sh             |   26 +
 _site/script/generate-review-template.sh      |   53 +
 _site/script/missing-glossary-links.sh        |   95 +
 _site/script/pdf.sh                           |   14 +
 _site/script/serve.sh                         |   16 +
 _site/script/test-all.sh                      |   19 +
 _site/script/test-markdown.sh                 |   17 +
 _site/script/test-with-link-check.sh          |   55 +
 _site/script/test-without-link-check.sh       |   33 +
 _site/script/to-archive-org.sh                |   82 +
 102 files changed, 37479 insertions(+)
 create mode 100644 _site/404.html
 create mode 100644 _site/AUTHORS.html
 create mode 100644 _site/AUTHORS.md
 create mode 100644 _site/CHANGELOG.html
 create mode 100644 _site/CHANGELOG.md
 create mode 100644 _site/CODE_OF_CONDUCT.html
 create mode 100644 _site/CODE_OF_CONDUCT.md
 create mode 100644 _site/CONTRIBUTING.html
 create mode 100644 _site/CONTRIBUTING.md
 create mode 100644 _site/GOVERNANCE.html
 create mode 100644 _site/GOVERNANCE.md
 create mode 100644 _site/LICENSE
 create mode 100644 _site/README.html
 create mode 100644 _site/README.md
 create mode 100644 _site/assets/cc-zero-badge.svg
 create mode 100644 _site/assets/codebase.svg
 create mode 100644 _site/assets/collaboration.svg
 create mode 100644 _site/assets/collaborative-developement.svg
 create mode 100644 _site/assets/dpg-badge.svg
 create mode 100644 _site/assets/eco-system.svg
 create mode 100644 _site/assets/github-markdown.css
 create mode 100644 _site/assets/hand-point.svg
 create mode 100644 _site/assets/hands-shake.svg
 create mode 100644 _site/assets/rouge-highlight.css
 create mode 100644 _site/assets/style.css
 create mode 100644 _site/assets/unlock.svg
 create mode 100644 _site/criteria/advertise-maturity.html
 create mode 100644 _site/criteria/bundle-policy-and-code.html
 create mode 100644 _site/criteria/code-in-the-open.html
 create mode 100644 _site/criteria/continuous-integration.html
 create mode 100644 _site/criteria/document-maturity.html
 create mode 100644 _site/criteria/document-objectives.html
 create mode 100644 _site/criteria/documenting.html
 create mode 100644 _site/criteria/findability.html
 create mode 100644 _site/criteria/index.html
 create mode 100644 _site/criteria/index.md
 create mode 100644 _site/criteria/make-contributing-easy.html
 create mode 100644 _site/criteria/open-licenses.html
 create mode 100644 _site/criteria/open-standards.html
 create mode 100644 _site/criteria/open-to-contributions.html
 create mode 100644 _site/criteria/require-review.html
 create mode 100644 _site/criteria/reusable-and-portable-codebases.html
 create mode 100644 _site/criteria/style.html
 create mode 100644 _site/criteria/understandable-english-first.html
 create mode 100644 _site/criteria/version-control-and-history.html
 create mode 100644 _site/criteria_source/bundle-policy-and-code.html
 create mode 100644 _site/criteria_source/code-in-the-open.html
 create mode 100644 _site/criteria_source/continuous-integration.html
 create mode 100644 _site/criteria_source/document-maturity.html
 create mode 100644 _site/criteria_source/document-objectives.html
 create mode 100644 _site/criteria_source/documenting.html
 create mode 100644 _site/criteria_source/findability.html
 create mode 100644 _site/criteria_source/index.html
 create mode 100644 _site/criteria_source/index.md
 create mode 100644 _site/criteria_source/make-contributing-easy.html
 create mode 100644 _site/criteria_source/open-licenses.html
 create mode 100644 _site/criteria_source/open-standards.html
 create mode 100644 _site/criteria_source/open-to-contributions.html
 create mode 100644 _site/criteria_source/require-review.html
 create mode 100644 _site/criteria_source/reusable-and-portable-codebases.html
 create mode 100644 _site/criteria_source/style.html
 create mode 100644 _site/criteria_source/understandable-english-first.html
 create mode 100644 _site/criteria_source/version-control-and-history.html
 create mode 100644 _site/docs/printing.html
 create mode 100644 _site/docs/printing.md
 create mode 100644 _site/docs/releasing.html
 create mode 100644 _site/docs/releasing.md
 create mode 100644 _site/docs/review-template.html
 create mode 100644 _site/docs/review-template.md
 create mode 100644 _site/docs/roadmap.html
 create mode 100644 _site/docs/roadmap.md
 create mode 100644 _site/docs/standard-for-public-code.html
 create mode 100644 _site/docs/standard-for-public-code.md
 create mode 100644 _site/glossary.html
 create mode 100644 _site/glossary.md
 create mode 100644 _site/images/audit-flow.dot
 create mode 100644 _site/images/audit-flow.svg
 create mode 100644 _site/index.html
 create mode 100644 _site/index.md
 create mode 100644 _site/introduction.html
 create mode 100644 _site/introduction.md
 create mode 100644 _site/license.html
 create mode 100644 _site/locales/en/LC_MESSAGES/messages.po
 create mode 100644 _site/locales/zh_Hant/LC_MESSAGES/messages.po
 create mode 100644 _site/print-cover.html
 create mode 100644 _site/print-review-template.html
 create mode 100644 _site/print.html
 create mode 100644 _site/publiccode.yml
 create mode 100644 _site/readers-guide.html
 create mode 100644 _site/readers-guide.md
 create mode 100644 _site/redirects.json
 create mode 100755 _site/script/check-new-links.sh
 create mode 100755 _site/script/find-missing-spdx.sh
 create mode 100755 _site/script/generate-review-template.sh
 create mode 100755 _site/script/missing-glossary-links.sh
 create mode 100755 _site/script/pdf.sh
 create mode 100755 _site/script/serve.sh
 create mode 100755 _site/script/test-all.sh
 create mode 100755 _site/script/test-markdown.sh
 create mode 100755 _site/script/test-with-link-check.sh
 create mode 100755 _site/script/test-without-link-check.sh
 create mode 100755 _site/script/to-archive-org.sh

diff --git a/_site/404.html b/_site/404.html
new file mode 100644
index 00000000..7acd12b8
--- /dev/null
+++ b/_site/404.html
@@ -0,0 +1,287 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Page not found, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/404.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class=" ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/404.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `404.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>If you typed the web address, check it is correct.</p>
+
+<p>If you pasted the web address, check you copied the entire address.</p>
+
+<p>If the web address is correct or you selected a link or button, email the <a href="mailto:info@publiccode.net">Foundation for Public Code staff</a> so we’ll be able to help you out, as well as correct our mistake.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/AUTHORS.html b/_site/AUTHORS.html
new file mode 100644
index 00000000..71200113
--- /dev/null
+++ b/_site/AUTHORS.html
@@ -0,0 +1,324 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Authors, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/AUTHORS.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/AUTHORS.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `AUTHORS.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="authors">Authors</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<ul>
+  <li>Alba Roza, <a href="https://publiccode.net">The Foundation for Public Code</a></li>
+  <li>Arnout Engelen</li>
+  <li>Arnout Schuijff, The Foundation for Public Code</li>
+  <li>Audrey Tang, <a href="https://digitalminister.tw/">digitalminister.tw</a></li>
+  <li>Ben Cerveny, The Foundation for Public Code</li>
+  <li>Bert Spaan</li>
+  <li>Boris van Hoytema, The Foundation for Public Code</li>
+  <li>Charlotte Heikendorf</li>
+  <li>Claus Mullie, The Foundation for Public Code</li>
+  <li>David Barberi</li>
+  <li>Edo Plantinga, <a href="https://codefor.nl/">Code For NL</a></li>
+  <li>Elena Findley-de Regt, The Foundation for Public Code</li>
+  <li>Eric Herman, The Foundation for Public Code</li>
+  <li>Felix Faassen, The Foundation for Public Code</li>
+  <li>Floris Deerenberg</li>
+  <li>Jan Ainali, The Foundation for Public Code</li>
+  <li>Johan Groenen, Code For NL</li>
+  <li>Marcus Klaas de Vries</li>
+  <li>Mark van der Net, <a href="https://www.amsterdam.nl/en/">Gemeente Amsterdam</a></li>
+  <li>Martijn de Waal, <a href="https://www.amsterdamuas.com/">Amsterdam University of Applied Sciences (AUAS)</a>, Faculty of Digital Media and Creative Industries, Lectorate of Play &amp; Civic Media</li>
+  <li>Mauko Quiroga</li>
+  <li>Maurice Hendriks, Gemeente Amsterdam</li>
+  <li>Maurits van der Schee, Gemeente Amsterdam</li>
+  <li>Mirjam van Tiel, The Foundation for Public Code</li>
+  <li>Ngô Ngọc Đức Huy</li>
+  <li>Paul Keller</li>
+  <li>Petteri Kivimäki, <a href="https://niis.org">Nordic Institute for Interoperability Solutions (NIIS)</a></li>
+  <li>Sky Bristol</li>
+  <li>Tamas Erkelens, Gemeente Amsterdam</li>
+  <li>Timo Slinger</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/AUTHORS.md b/_site/AUTHORS.md
new file mode 100644
index 00000000..54ff8fe5
--- /dev/null
+++ b/_site/AUTHORS.md
@@ -0,0 +1,35 @@
+# Authors
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+* Alba Roza, [The Foundation for Public Code](https://publiccode.net)
+* Arnout Engelen
+* Arnout Schuijff, The Foundation for Public Code
+* Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)
+* Ben Cerveny, The Foundation for Public Code
+* Bert Spaan
+* Boris van Hoytema, The Foundation for Public Code
+* Charlotte Heikendorf
+* Claus Mullie, The Foundation for Public Code
+* David Barberi
+* Edo Plantinga, [Code For NL](https://codefor.nl/)
+* Elena Findley-de Regt, The Foundation for Public Code
+* Eric Herman, The Foundation for Public Code
+* Felix Faassen, The Foundation for Public Code
+* Floris Deerenberg
+* Jan Ainali, The Foundation for Public Code
+* Johan Groenen, Code For NL
+* Marcus Klaas de Vries
+* Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)
+* Martijn de Waal, [Amsterdam University of Applied Sciences (AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and Creative Industries, Lectorate of Play & Civic Media
+* Mauko Quiroga
+* Maurice Hendriks, Gemeente Amsterdam
+* Maurits van der Schee, Gemeente Amsterdam
+* Mirjam van Tiel, The Foundation for Public Code
+* Ngô Ngọc Đức Huy
+* Paul Keller
+* Petteri Kivimäki, [Nordic Institute for Interoperability Solutions (NIIS)](https://niis.org)
+* Sky Bristol
+* Tamas Erkelens, Gemeente Amsterdam
+* Timo Slinger
diff --git a/_site/CHANGELOG.html b/_site/CHANGELOG.html
new file mode 100644
index 00000000..30660ff5
--- /dev/null
+++ b/_site/CHANGELOG.html
@@ -0,0 +1,487 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Version history, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CHANGELOG.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#version-040">Version 0.4.0</a></li>
+  <li><a href="#version-030">Version 0.3.0</a></li>
+  <li><a href="#version-023">Version 0.2.3</a></li>
+  <li><a href="#version-022">Version 0.2.2</a></li>
+  <li><a href="#version-021">Version 0.2.1</a></li>
+  <li><a href="#version-020">Version 0.2.0</a></li>
+  <li><a href="#version-014">Version 0.1.4</a></li>
+  <li><a href="#version-013">Version 0.1.3</a></li>
+  <li><a href="#version-012">Version 0.1.2</a></li>
+  <li><a href="#version-011">Version 0.1.1</a></li>
+  <li><a href="#version-010">Version 0.1.0</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/CHANGELOG.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `CHANGELOG.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="version-history">Version history</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="version-040">Version 0.4.0</h2>
+
+<p>September 7th 2022: 🔭 the eleventh draft adds a new findability criterion.</p>
+
+<ul>
+  <li>Introduce new criterion: Make the codebase findable.</li>
+  <li>Improve How to test section for most criteria.</li>
+  <li>New requirement in Welcome contributors about publishing activity statistics.</li>
+  <li>Removed redundant requirement about portable and reusable code.</li>
+  <li>Expand open license definition to include both OSI and FSF approved licenses.</li>
+  <li>Rephrase MAY requirements to use the keyword OPTIONAL for clarity.</li>
+  <li>Expressed intent that the Standard for Public Code should meet its own requirements where applicable and added assessment.</li>
+  <li>Add SPDX license identifiers to files.</li>
+  <li>Introduced new Code of Conduct.</li>
+  <li>Clarify distinction between source code and policy text.</li>
+  <li>Restructuring of requirements with bullet point lists.</li>
+  <li>Acknowledge the importance of codebase modularity for reuse.</li>
+  <li>Move requirements related to Findability to the new criterion.</li>
+  <li>Clarify the role of non-open standards when used in a codebase.</li>
+  <li>Additional guidance about build-time and runtime dependencies.</li>
+  <li>Added roadmap for the development of the Standard for Public Code.</li>
+  <li>Update structure of Authors file.</li>
+  <li>Add Audrey Tang to Authors.</li>
+  <li>Added a list of criteria to the print edition.</li>
+  <li>Clarify what the standard means with policymakers, managers, developers and designers.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+  <li>Some hyperlinks updated.</li>
+</ul>
+
+<h2 id="version-030">Version 0.3.0</h2>
+
+<p>May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization.</p>
+
+<ul>
+  <li>Requirement for localization made explicit in Create reusable and portable code.</li>
+  <li>Documentation of governance changed from a SHOULD to a MUST.</li>
+  <li>Replace the very subjective (and hard to test) “contributions MUST be small” with requirement to document expectation in contributing guidelines and focus on a single issue.</li>
+  <li>Community translations now linked in the footer.</li>
+  <li>Revert “Replace BPMN svg with Mermaid flowchart”.</li>
+  <li>Many minor clarifications to language and sentences made more simple.</li>
+  <li>Some hyperlinks updated.</li>
+</ul>
+
+<h2 id="version-023">Version 0.2.3</h2>
+
+<p>March 15th 2022: 📜 the ninth draft allows English summaries for policy lacking an official translation.</p>
+
+<ul>
+  <li>Relax the criterion Use plain English by adding a new requirement allows bundled policy not available in English to have an accompanying summary in English instead of translating the full text.</li>
+  <li>Similarly, allow for English summaries for policies not available in English in Bundle policy and code.</li>
+  <li>Clarify that term ‘policy’ includes processes which impact development and deployment in Bundle policy and code.</li>
+  <li>Emphasize reusability also on parts of the solutions in Create reusable and portable code.</li>
+  <li>Expand guidance to Developers and designers in Create reusable and portable code about deploying to proprietary platforms.</li>
+  <li>Add nuance to use of non-English terms in what management need to do in Use plain English.</li>
+  <li>Change the pull request process diagram to use Mermaid instead of BPMN to make <a href="https://github.com/publiccodenet/community-translations-standard">community translations</a> easier.</li>
+  <li>Added Maurice Hendriks to AUTHORS.</li>
+  <li>Added OpenApi Specification to further reading.</li>
+  <li>Made the attributions in further reading sections clearer.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-022">Version 0.2.2</h2>
+
+<p>November 29th 2021: 🏛 the eighth draft recognizes that policy which executes as code may not be in English.</p>
+
+<ul>
+  <li>Document exception to “All code MUST be in English” where policy is interpreted as code.</li>
+  <li>Add MAY requirement regarding committer email addresses in Maintain version control.</li>
+  <li>Expand guidance to Policy Makers in Bundle policy and code.</li>
+  <li>Expand guidance to Developers and designers in Use a coherent style.</li>
+  <li>Add “Different contexts” to glossary.</li>
+  <li>Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS.</li>
+  <li>Add Digital Public Goods approval badge.</li>
+  <li>Added “next” and “previous” links to criteria pages of web version.</li>
+  <li>Add Open Standards principles to further reading.</li>
+  <li>Add Definition of plain language to further reading.</li>
+  <li>Move the Semantic Versioning Specification further reading reference.</li>
+  <li>Clarify that publiccode.yml is one example of a machine-readable metadata description.</li>
+  <li>Changed “your codebase” and “your organization” to be less possessive.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+  <li>Add instructions for creating a print version.</li>
+</ul>
+
+<h2 id="version-021">Version 0.2.1</h2>
+
+<p>March 1st 2021: 🧽 the seventh draft has minor cleaning up after version 0.2.0.</p>
+
+<ul>
+  <li>New SHOULD requirement on using a distributed version control system and why distributed is important.</li>
+  <li>Feedback requirements for rejected contributions are more strict than accepted ones.</li>
+  <li>Specify that copyright and license notices should also be machine-readable.</li>
+  <li>Advice on how to test that notices be machine-readable.</li>
+  <li>Clarify guidance for rolling releases.</li>
+  <li>Clear up definition of version control in glossary.</li>
+  <li>Add further reading encouraging contribution, SPDX, Git and reviewing contributions.</li>
+  <li>Add links to videos about the concept of public code.</li>
+  <li>Update BPMN link.</li>
+  <li>Reduce link duplication.</li>
+  <li>Add Alba Roza and Ngô Ngọc Đức Huy to authors.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-020">Version 0.2.0</h2>
+
+<p>October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity.</p>
+
+<ul>
+  <li>Split “Welcome contributions” criterion into “Make contributing easy” and “Welcome contributors”.</li>
+  <li>Rename criterion “Pay attention to codebase maturity” to “Document codebase maturity”.</li>
+  <li>Changed MUST to SHOULD for requirement of codebase in use by multiple parties.</li>
+  <li>Add MUST NOT requirement regarding copyright assignment.</li>
+  <li>Clarify role of configuration in reusable code requirement.</li>
+  <li>Glossary additions: continuous integration, policy, repository, and version control.</li>
+  <li>Replace references to ‘cities’ with ‘public organizations’.</li>
+  <li>Clarify aspects of sensitive code by separating contributor and reviewer requirements into separate items.</li>
+  <li>Expand further reading, and guidance to policy makers, developers and designers.</li>
+  <li>Add Felix Faassen and Arnout Engelen to authors.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-014">Version 0.1.4</h2>
+
+<p>November 27th 2019: 🧹 the fifth draft consists mostly of additional minor fixes.</p>
+
+<ul>
+  <li>Linked License.md file.</li>
+  <li>Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors.</li>
+  <li>Made punctuation more consistent, especially for bullet lists.</li>
+  <li>Made some minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-013">Version 0.1.3</h2>
+
+<p>October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for the autumn cleaning</p>
+
+<ul>
+  <li>Renamed continuous delivery to continuous integration.</li>
+  <li>Referencing accessibility guidelines in the language standard.</li>
+  <li>A bunch of style and consistency fixes.</li>
+</ul>
+
+<h2 id="version-012">Version 0.1.2</h2>
+
+<p>August 22th 2019: 🌠 the third draft focuses on better text and takes community input</p>
+
+<ul>
+  <li>With some great new contributors comes a fresh author list.</li>
+  <li>All links are now HTTPS.</li>
+  <li>General proofreading, wording clarifications, and smashed typos.</li>
+  <li>Updated criteria:
+    <ul>
+      <li>Requirement for reuse in different contexts</li>
+      <li>Recommendation for explicit versioning</li>
+      <li>Recommendation for multi party development</li>
+      <li>Recommendation for license headers in files</li>
+      <li>Recommendation for vulnerability reporting</li>
+      <li>Recommendation for explicit documentation of governance</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="version-011">Version 0.1.1</h2>
+
+<p>May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a lot of typos</p>
+
+<ul>
+  <li>Removed references to the Foundation for Public Code, we’re going to have to change the name in becoming an association.</li>
+  <li>Updated the introduction.</li>
+  <li>Updated the glossary.</li>
+  <li>Added the code of conduct.</li>
+  <li>We’ve recommended using the publiccode.yml standard for easier reuse.</li>
+</ul>
+
+<h2 id="version-010">Version 0.1.0</h2>
+
+<p>April 16th 2019: 🎉 the first draft is ready, it is all brand new and has snazzy new ideas in it</p>
+
+<ul>
+  <li>14 criteria with their requirements and how to operationalize them.</li>
+  <li>An introduction with a high level background, what this standard is, and how the Foundation for Public Code will use it.</li>
+</ul>
+
+<p>This first version was produced together with the Amsterdam University of Applied Sciences and the City of Amsterdam as a part of the <a href="https://smartcities.publiccode.net/">Smart Cities? Public Code! project</a>.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CHANGELOG.md b/_site/CHANGELOG.md
new file mode 100644
index 00000000..3fd80eae
--- /dev/null
+++ b/_site/CHANGELOG.md
@@ -0,0 +1,163 @@
+# Version history
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## Version 0.4.0
+
+September 7th 2022: 🔭 the eleventh draft adds a new findability criterion.
+
+* Introduce new criterion: Make the codebase findable.
+* Improve How to test section for most criteria.
+* New requirement in Welcome contributors about publishing activity statistics.
+* Removed redundant requirement about portable and reusable code.
+* Expand open license definition to include both OSI and FSF approved licenses.
+* Rephrase MAY requirements to use the keyword OPTIONAL for clarity.
+* Expressed intent that the Standard for Public Code should meet its own requirements where applicable and added assessment.
+* Add SPDX license identifiers to files.
+* Introduced new Code of Conduct.
+* Clarify distinction between source code and policy text.
+* Restructuring of requirements with bullet point lists.
+* Acknowledge the importance of codebase modularity for reuse.
+* Move requirements related to Findability to the new criterion.
+* Clarify the role of non-open standards when used in a codebase.
+* Additional guidance about build-time and runtime dependencies.
+* Added roadmap for the development of the Standard for Public Code.
+* Update structure of Authors file.
+* Add Audrey Tang to Authors.
+* Added a list of criteria to the print edition.
+* Clarify what the standard means with policymakers, managers, developers and designers.
+* Made additional minor changes to text for clarity.
+* Some hyperlinks updated.
+
+## Version 0.3.0
+
+May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization.
+
+* Requirement for localization made explicit in Create reusable and portable code.
+* Documentation of governance changed from a SHOULD to a MUST.
+* Replace the very subjective (and hard to test) "contributions MUST be small" with requirement to document expectation in contributing guidelines and focus on a single issue.
+* Community translations now linked in the footer.
+* Revert "Replace BPMN svg with Mermaid flowchart".
+* Many minor clarifications to language and sentences made more simple.
+* Some hyperlinks updated.
+
+## Version 0.2.3
+
+March 15th 2022: 📜 the ninth draft allows English summaries for policy lacking an official translation.
+
+* Relax the criterion Use plain English by adding a new requirement allows bundled policy not available in English to have an accompanying summary in English instead of translating the full text.
+* Similarly, allow for English summaries for policies not available in English in Bundle policy and code.
+* Clarify that term 'policy' includes processes which impact development and deployment in Bundle policy and code.
+* Emphasize reusability also on parts of the solutions in Create reusable and portable code.
+* Expand guidance to Developers and designers in Create reusable and portable code about deploying to proprietary platforms.
+* Add nuance to use of non-English terms in what management need to do in Use plain English.
+* Change the pull request process diagram to use Mermaid instead of BPMN to make [community translations](https://github.com/publiccodenet/community-translations-standard) easier.
+* Added Maurice Hendriks to AUTHORS.
+* Added OpenApi Specification to further reading.
+* Made the attributions in further reading sections clearer.
+* Made additional minor changes to text for clarity.
+
+## Version 0.2.2
+
+November 29th 2021: 🏛 the eighth draft recognizes that policy which executes as code may not be in English.
+
+* Document exception to "All code MUST be in English" where policy is interpreted as code.
+* Add MAY requirement regarding committer email addresses in Maintain version control.
+* Expand guidance to Policy Makers in Bundle policy and code.
+* Expand guidance to Developers and designers in Use a coherent style.
+* Add "Different contexts" to glossary.
+* Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS.
+* Add Digital Public Goods approval badge.
+* Added "next" and "previous" links to criteria pages of web version.
+* Add Open Standards principles to further reading.
+* Add Definition of plain language to further reading.
+* Move the Semantic Versioning Specification further reading reference.
+* Clarify that publiccode.yml is one example of a machine-readable metadata description.
+* Changed "your codebase" and "your organization" to be less possessive.
+* Made additional minor changes to text for clarity.
+* Add instructions for creating a print version.
+
+## Version 0.2.1
+
+March 1st 2021: 🧽 the seventh draft has minor cleaning up after version 0.2.0.
+
+* New SHOULD requirement on using a distributed version control system and why distributed is important.
+* Feedback requirements for rejected contributions are more strict than accepted ones.
+* Specify that copyright and license notices should also be machine-readable.
+* Advice on how to test that notices be machine-readable.
+* Clarify guidance for rolling releases.
+* Clear up definition of version control in glossary.
+* Add further reading encouraging contribution, SPDX, Git and reviewing contributions.
+* Add links to videos about the concept of public code.
+* Update BPMN link.
+* Reduce link duplication.
+* Add Alba Roza and Ngô Ngọc Đức Huy to authors.
+* Made additional minor changes to text for clarity.
+
+## Version 0.2.0
+
+October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity.
+
+* Split "Welcome contributions" criterion into "Make contributing easy" and "Welcome contributors".
+* Rename criterion "Pay attention to codebase maturity" to "Document codebase maturity".
+* Changed MUST to SHOULD for requirement of codebase in use by multiple parties.
+* Add MUST NOT requirement regarding copyright assignment.
+* Clarify role of configuration in reusable code requirement.
+* Glossary additions: continuous integration, policy, repository, and version control.
+* Replace references to 'cities' with 'public organizations'.
+* Clarify aspects of sensitive code by separating contributor and reviewer requirements into separate items.
+* Expand further reading, and guidance to policy makers, developers and designers.
+* Add Felix Faassen and Arnout Engelen to authors.
+* Made additional minor changes to text for clarity.
+
+## Version 0.1.4
+
+November 27th 2019: 🧹 the fifth draft consists mostly of additional minor fixes.
+
+* Linked License.md file.
+* Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors.
+* Made punctuation more consistent, especially for bullet lists.
+* Made some minor changes to text for clarity.
+
+## Version 0.1.3
+
+October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for the autumn cleaning
+
+* Renamed continuous delivery to continuous integration.
+* Referencing accessibility guidelines in the language standard.
+* A bunch of style and consistency fixes.
+
+## Version 0.1.2
+
+August 22th 2019: 🌠 the third draft focuses on better text and takes community input
+
+* With some great new contributors comes a fresh author list.
+* All links are now HTTPS.
+* General proofreading, wording clarifications, and smashed typos.
+* Updated criteria:
+  * Requirement for reuse in different contexts
+  * Recommendation for explicit versioning
+  * Recommendation for multi party development
+  * Recommendation for license headers in files
+  * Recommendation for vulnerability reporting
+  * Recommendation for explicit documentation of governance
+
+## Version 0.1.1
+
+May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a lot of typos
+
+* Removed references to the Foundation for Public Code, we're going to have to change the name in becoming an association.
+* Updated the introduction.
+* Updated the glossary.
+* Added the code of conduct.
+* We've recommended using the publiccode.yml standard for easier reuse.
+
+## Version 0.1.0
+
+April 16th 2019: 🎉 the first draft is ready, it is all brand new and has snazzy new ideas in it
+
+* 14 criteria with their requirements and how to operationalize them.
+* An introduction with a high level background, what this standard is, and how the Foundation for Public Code will use it.
+
+This first version was produced together with the Amsterdam University of Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? Public Code! project](https://smartcities.publiccode.net/).
diff --git a/_site/CODE_OF_CONDUCT.html b/_site/CODE_OF_CONDUCT.html
new file mode 100644
index 00000000..218d7bf5
--- /dev/null
+++ b/_site/CODE_OF_CONDUCT.html
@@ -0,0 +1,302 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Code of Conduct, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CODE_OF_CONDUCT.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/CODE_OF_CONDUCT.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `CODE_OF_CONDUCT.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="code-of-conduct">Code of Conduct</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2021-2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Many community members are from civic or professional environments with behavioral codes yet some individuals are not.
+This document expresses expectations of all community members and all interactions regardless of communication channel.</p>
+
+<p>Be here to collaborate.</p>
+
+<p>Be considerate, respectful, and patient.</p>
+
+<p>Strive to be as constructive as possible.</p>
+
+<p>To raise a concern, please email directors@publiccode.net.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CODE_OF_CONDUCT.md b/_site/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..b0ccfaab
--- /dev/null
+++ b/_site/CODE_OF_CONDUCT.md
@@ -0,0 +1,15 @@
+# Code of Conduct
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2021-2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+Many community members are from civic or professional environments with behavioral codes yet some individuals are not.
+This document expresses expectations of all community members and all interactions regardless of communication channel.
+
+Be here to collaborate.
+
+Be considerate, respectful, and patient.
+
+Strive to be as constructive as possible.
+
+To raise a concern, please email directors@publiccode.net.
diff --git a/_site/CONTRIBUTING.html b/_site/CONTRIBUTING.html
new file mode 100644
index 00000000..2b7d3891
--- /dev/null
+++ b/_site/CONTRIBUTING.html
@@ -0,0 +1,393 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Contributing to this standard, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CONTRIBUTING.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#problems-suggestions-and-questions-in-issues">Problems, suggestions and questions in issues</a></li>
+  <li><a href="#documentation-and-code-in-pull-requests">Documentation and code in pull requests</a>
+    <ol>
+      <li><a href="#1-make-your-changes">1. Make your changes</a>
+        <ol>
+          <li><a href="#style">Style</a></li>
+          <li><a href="#standards-to-follow">Standards to follow</a></li>
+        </ol>
+      </li>
+      <li><a href="#2-pull-request">2. Pull request</a></li>
+      <li><a href="#3-improve">3. Improve</a></li>
+      <li><a href="#4-celebrate">4. Celebrate</a></li>
+    </ol>
+  </li>
+  <li><a href="#translations-in-other-languages">Translations in other languages</a></li>
+  <li><a href="#releases">Releases</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/CONTRIBUTING.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `CONTRIBUTING.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="contributing-to-this-standard">Contributing to this standard</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>🙇‍♀️ Thank you for contributing!</p>
+
+<p>We understand that a standard like this can only be set in collaboration with as many public technologists, policy makers and interested folk as possible. Thus we appreciate your input, enjoy feedback and welcome improvements to this project and are very open to collaboration.</p>
+
+<p>We love issues and pull requests from everyone. If you’re not comfortable with GitHub, you can email use your feedback at <a href="mailto:info@publiccode.net">info@publiccode.net</a>.</p>
+
+<h2 id="problems-suggestions-and-questions-in-issues">Problems, suggestions and questions in issues</h2>
+
+<p>A high-level overview of the development that we already have sketched out can be seen in the <a href="/docs/roadmap.html">roadmap</a>.
+Please help development by reporting problems, suggesting changes and asking questions.
+To do this, you can <a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue">create a GitHub issue</a> for this project in the <a href="https://github.com/publiccodenet/standard/issues">GitHub Issues for the Standard for Public Code</a>.</p>
+
+<p>Or, sign up to the <a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">mailing list</a> and send an email to
+<a href="mailto:standard@lists.publiccode.net">standard@lists.publiccode.net</a>.</p>
+
+<p>You don’t need to change any of our code or documentation to be a contributor!</p>
+
+<h2 id="documentation-and-code-in-pull-requests">Documentation and code in pull requests</h2>
+
+<p>If you want to add to the documentation or code of one of our projects you should make a pull request.</p>
+
+<p>If you never used GitHub, get up to speed with <a href="https://docs.github.com/en/get-started/quickstart/github-flow">Understanding the GitHub flow</a> or follow one of the great free interactive courses in the <a href="https://lab.github.com/">GitHub learning lab</a> on working with GitHub and working with MarkDown, the syntax this project’s documentation is in.</p>
+
+<p>This project is licensed Creative Commons Zero v1.0 Universal, which essentially means that the project, along with your contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it.</p>
+
+<h3 id="1-make-your-changes">1. Make your changes</h3>
+
+<p>Contributions should <a href="/docs/standard-for-public-code.html">follow</a> the requirements set out in the criteria of the Standard for Public code itself.
+Reviewers will also be ensuring that contributions are aligned with the <a href="/introduction.html#values-of-public-code">values of public code</a>.</p>
+
+<p>This project uses the <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow branching model and workflow</a>. When you’ve forked this repository, please make sure to create a feature branch following the GitFlow model.</p>
+
+<p>Add your changes in commits <a href="https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message">with a message that explains them</a>.
+If more than one type of change is needed, group logically related changes into separate commits.
+For example, white-space fixes could be a separate commit from text content changes.
+Document choices or decisions you make in the commit message, this will enable everyone to be informed of your choices in the future.</p>
+
+<p>If you are adding code, make sure you’ve added and updated the relevant documentation and tests before you submit your pull request. Make sure to write tests that show the behavior of the newly added or changed code.</p>
+
+<h4 id="style">Style</h4>
+
+<p>The Standard for Public Code aims to <a href="https://standard.publiccode.net/criteria/understandable-english-first.html">use plain English</a> and we have chosen American English for spelling.
+However, we want to emphasize that it is more important that you make your contribution than worry about spelling and typography.
+We will help you get it right in our review process and we also have a separate quality check before <a href="/docs/releasing.html">making a new release</a>.</p>
+
+<h4 id="standards-to-follow">Standards to follow</h4>
+
+<p>These are the standards that the Standard for Public Code uses.
+Please make sure that your contributions are aligned with them so that they easier can be merged.</p>
+
+<ul>
+  <li><a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a> - for requirement level keywords</li>
+  <li><a href="https://www.w3.org/TR/WCAG21/#readable">Web Content Accessibility Guidelines 2.1</a> - for readibility</li>
+</ul>
+
+<h3 id="2-pull-request">2. Pull request</h3>
+
+<p>When submitting the pull request, please accompany it with a description of the problem you are trying to solve and the issue number that this pull request fixes.
+It is preferred for each pull request to address a single issue where possible.
+In some cases a single set of changes may address multiple issues, in which case be sure to list all issue numbers fixed.</p>
+
+<h3 id="3-improve">3. Improve</h3>
+
+<p>All contributions have to be reviewed by someone.</p>
+
+<p>It could be that your contribution can be merged immediately by a maintainer. However, usually, a new pull request needs some improvements before it can be merged. Other contributors (or helper robots) might have feedback. If this is the case the reviewing maintainer will help you improve your documentation and code.</p>
+
+<p>If your documentation and code have passed human review, it is merged.</p>
+
+<h3 id="4-celebrate">4. Celebrate</h3>
+
+<p>Your ideas, documentation and code have become an integral part of this project. You are the open source hero we need!</p>
+
+<p>In fact, feel free to open a pull request to add your name to the <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS</code></a> file and get eternal attribution.</p>
+
+<h2 id="translations-in-other-languages">Translations in other languages</h2>
+
+<p>While the Standard does not have any official translations, you can help maintain existing and add new <a href="https://github.com/publiccodenet/community-translations-standard">community translations of the Standard</a>.</p>
+
+<h2 id="releases">Releases</h2>
+
+<p>We have dedicated documentation for creating <a href="/docs/releasing.html">new releases</a> and <a href="/docs/printing.html">ordering printed standards</a>.</p>
+
+<p>For more information on how to use and contribute to this project, please read the <a href="/README.html"><code class="language-plaintext highlighter-rouge">README</code></a>.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CONTRIBUTING.md b/_site/CONTRIBUTING.md
new file mode 100644
index 00000000..2c2f292c
--- /dev/null
+++ b/_site/CONTRIBUTING.md
@@ -0,0 +1,87 @@
+# Contributing to this standard
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+🙇‍♀️ Thank you for contributing!
+
+We understand that a standard like this can only be set in collaboration with as many public technologists, policy makers and interested folk as possible. Thus we appreciate your input, enjoy feedback and welcome improvements to this project and are very open to collaboration.
+
+We love issues and pull requests from everyone. If you're not comfortable with GitHub, you can email use your feedback at <info@publiccode.net>.
+
+## Problems, suggestions and questions in issues
+
+A high-level overview of the development that we already have sketched out can be seen in the [roadmap](/docs/roadmap.md).
+Please help development by reporting problems, suggesting changes and asking questions.
+To do this, you can [create a GitHub issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue) for this project in the [GitHub Issues for the Standard for Public Code](https://github.com/publiccodenet/standard/issues).
+
+Or, sign up to the [mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) and send an email to
+[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net).
+
+You don't need to change any of our code or documentation to be a contributor!
+
+## Documentation and code in pull requests
+
+If you want to add to the documentation or code of one of our projects you should make a pull request.
+
+If you never used GitHub, get up to speed with [Understanding the GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) or follow one of the great free interactive courses in the [GitHub learning lab](https://lab.github.com/) on working with GitHub and working with MarkDown, the syntax this project's documentation is in.
+
+This project is licensed Creative Commons Zero v1.0 Universal, which essentially means that the project, along with your contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it.
+
+### 1. Make your changes
+
+Contributions should [follow](docs/standard-for-public-code.md) the requirements set out in the criteria of the Standard for Public code itself.
+Reviewers will also be ensuring that contributions are aligned with the [values of public code](introduction.md#values-of-public-code).
+
+This project uses the [GitFlow branching model and workflow](https://nvie.com/posts/a-successful-git-branching-model/). When you've forked this repository, please make sure to create a feature branch following the GitFlow model.
+
+Add your changes in commits [with a message that explains them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message).
+If more than one type of change is needed, group logically related changes into separate commits.
+For example, white-space fixes could be a separate commit from text content changes.
+Document choices or decisions you make in the commit message, this will enable everyone to be informed of your choices in the future.
+
+If you are adding code, make sure you've added and updated the relevant documentation and tests before you submit your pull request. Make sure to write tests that show the behavior of the newly added or changed code.
+
+#### Style
+
+The Standard for Public Code aims to [use plain English](https://standard.publiccode.net/criteria/understandable-english-first.html) and we have chosen American English for spelling.
+However, we want to emphasize that it is more important that you make your contribution than worry about spelling and typography.
+We will help you get it right in our review process and we also have a separate quality check before [making a new release](docs/releasing.md).
+
+#### Standards to follow
+
+These are the standards that the Standard for Public Code uses.
+Please make sure that your contributions are aligned with them so that they easier can be merged.
+
+* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level keywords
+* [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/#readable) - for readibility
+
+### 2. Pull request
+
+When submitting the pull request, please accompany it with a description of the problem you are trying to solve and the issue number that this pull request fixes.
+It is preferred for each pull request to address a single issue where possible.
+In some cases a single set of changes may address multiple issues, in which case be sure to list all issue numbers fixed.
+
+### 3. Improve
+
+All contributions have to be reviewed by someone.
+
+It could be that your contribution can be merged immediately by a maintainer. However, usually, a new pull request needs some improvements before it can be merged. Other contributors (or helper robots) might have feedback. If this is the case the reviewing maintainer will help you improve your documentation and code.
+
+If your documentation and code have passed human review, it is merged.
+
+### 4. Celebrate
+
+Your ideas, documentation and code have become an integral part of this project. You are the open source hero we need!
+
+In fact, feel free to open a pull request to add your name to the [`AUTHORS`](AUTHORS.md) file and get eternal attribution.
+
+## Translations in other languages
+
+While the Standard does not have any official translations, you can help maintain existing and add new [community translations of the Standard](https://github.com/publiccodenet/community-translations-standard).
+
+## Releases
+
+We have dedicated documentation for creating [new releases](/docs/releasing.md) and [ordering printed standards](/docs/printing.md).
+
+For more information on how to use and contribute to this project, please read the [`README`](README.md).
diff --git a/_site/GOVERNANCE.html b/_site/GOVERNANCE.html
new file mode 100644
index 00000000..0251eb6c
--- /dev/null
+++ b/_site/GOVERNANCE.html
@@ -0,0 +1,301 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Governance, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/GOVERNANCE.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/GOVERNANCE.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `GOVERNANCE.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="governance">Governance</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>This standard lies at the core of the codebase stewardship provided by the <a href="https://publiccode.net/">Foundation for Public Code</a>. We decide if a codebase is ready for community co-development based on this document.</p>
+
+<p>The standard is maintained by Foundation for Public Code staff.</p>
+
+<p><a href="/CONTRIBUTING.html">We welcome contributions, such as suggestions for changes or general feedback, from anyone.</a></p>
+
+<p>Because of the important role that the Standard for Public Code has in our core process we require the highest standards from the Standard.</p>
+
+<p>We will try to respond promptly to all pull requests. The pull request is an opportunity to work together to improve our methods and the Standard. We may not accept all changes, but we will explain our logic.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/GOVERNANCE.md b/_site/GOVERNANCE.md
new file mode 100644
index 00000000..a6b7595f
--- /dev/null
+++ b/_site/GOVERNANCE.md
@@ -0,0 +1,14 @@
+# Governance
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+This standard lies at the core of the codebase stewardship provided by the [Foundation for Public Code](https://publiccode.net/). We decide if a codebase is ready for community co-development based on this document.
+
+The standard is maintained by Foundation for Public Code staff.
+
+[We welcome contributions, such as suggestions for changes or general feedback, from anyone.](/CONTRIBUTING.md)
+
+Because of the important role that the Standard for Public Code has in our core process we require the highest standards from the Standard.
+
+We will try to respond promptly to all pull requests. The pull request is an opportunity to work together to improve our methods and the Standard. We may not accept all changes, but we will explain our logic.
diff --git a/_site/LICENSE b/_site/LICENSE
new file mode 100644
index 00000000..0e259d42
--- /dev/null
+++ b/_site/LICENSE
@@ -0,0 +1,121 @@
+Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
diff --git a/_site/README.html b/_site/README.html
new file mode 100644
index 00000000..448e69ed
--- /dev/null
+++ b/_site/README.html
@@ -0,0 +1,347 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/README.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#request-for-contributions">Request for contributions</a></li>
+  <li><a href="#help-improve-this-standard">Help improve this standard</a></li>
+  <li><a href="#preview-build-and-deploy">Preview, build and deploy</a></li>
+  <li><a href="#generating-a-pdf-of-the-standard-for-public-code">Generating a PDF of the Standard for Public Code</a></li>
+  <li><a href="#license">License</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/README.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `README.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="standard-for-public-code">Standard for Public Code</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard for Public Code gives public organizations a model for preparing open source solutions to enable collaborations with similar public organizations in other places.
+It includes guidance for policy makers, city administrators, developers and vendors.</p>
+
+<p><img src="https://img.shields.io/badge/version-0.4.0-yellow.svg" alt="version 0.4.0" />
+<img src="https://github.com/publiccodenet/standard/workflows/Test/badge.svg" alt="Test" />
+<img src="https://github.com/publiccodenet/standard/workflows/Scheduled%20link%20check/badge.svg" alt="Scheduled link check" /></p>
+
+<p>The Standard for Public Code is in a draft format.
+We are preparing it for a version 1.0 release.
+Currently, we are testing it on a small number of codebases.</p>
+
+<h2 id="request-for-contributions">Request for contributions</h2>
+
+<p>We believe public policy and software should be inclusive, usable, open, legible, accountable, accessible and sustainable. This means we need a new way of designing, developing and procuring both the source code and policy documentation.</p>
+
+<p>This standard sets a quality level for codebases that meets the needs of public organizations, institutions and administrations as well as other critical infrastructural services.</p>
+
+<p>The standard lives at <a href="https://standard.publiccode.net/">standard.publiccode.net</a>. See <a href="/"><code class="language-plaintext highlighter-rouge">index.md</code></a> for an overview of all content.</p>
+
+<p><a href="https://www.youtube.com/watch?v=QWt6vB-cipE"><img src="https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg" alt="Thumbnail for the video on the Standard for Public Code: a printed version lying on a table between two hands" /></a></p>
+
+<p><a href="https://www.youtube.com/watch?v=QWt6vB-cipE">A video introduction to Standard for Public Code</a> from Creative Commons Global Summit 2020 (4:12) on YouTube.</p>
+
+<h2 id="help-improve-this-standard">Help improve this standard</h2>
+
+<p>The Foundation for Public Code is committed to maintaining and developing the Standard for Public Code at a level of quality that meets the standard itself.</p>
+
+<p>We are looking for people like you to <a href="/CONTRIBUTING.html">contribute</a> to this project by suggesting improvements and helping develop it. 😊 Get started by reading our <a href="/CONTRIBUTING.html">contributors guide</a>. Since it is such a core document we will accept contributions when they add significant value. We’ve described how we govern the standard in the <a href="/GOVERNANCE.html">governance statement</a>.</p>
+
+<p>Please note that this project is released with a <a href="/CODE_OF_CONDUCT.html">code of conduct</a>. By participating in this project you agree to abide by its terms. Please be lovely to all other community members.</p>
+
+<h2 id="preview-build-and-deploy">Preview, build and deploy</h2>
+
+<p>The repository builds to a static site deployed at <a href="https://standard.publiccode.net/">standard.publiccode.net</a>. It is built with <a href="https://pages.github.com">GitHub pages</a> and <a href="https://jekyllrb.com/">Jekyll</a>.</p>
+
+<p>See the scripts in the <a href="https://github.com/publiccodenet/standard/tree/main/script">script</a> folder.</p>
+
+<h2 id="generating-a-pdf-of-the-standard-for-public-code">Generating a PDF of the Standard for Public Code</h2>
+
+<p>Using <a href="https://weasyprint.org/">Weasyprint</a> the file <code class="language-plaintext highlighter-rouge">print.html</code> can be converted to a nice looking PDF.</p>
+
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>weasyprint http://localhost:4000/print.html standard.pdf
+</code></pre></div></div>
+
+<h2 id="license">License</h2>
+
+<p>© <a href="/AUTHORS.html">The authors and contributors</a></p>
+
+<p>The standard is <a href="/LICENSE">licensed</a> under CC 0, which also applies to all illustrations and the documentation. This means anyone can do anything with it. If you contribute you also grant these rights to others. You can read more about how to help in the <a href="/CONTRIBUTING.html">contributing guide</a>.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/README.md b/_site/README.md
new file mode 100644
index 00000000..3ac24864
--- /dev/null
+++ b/_site/README.md
@@ -0,0 +1,55 @@
+# Standard for Public Code
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+The Standard for Public Code gives public organizations a model for preparing open source solutions to enable collaborations with similar public organizations in other places.
+It includes guidance for policy makers, city administrators, developers and vendors.
+
+![version 0.4.0](https://img.shields.io/badge/version-0.4.0-yellow.svg)
+![Test](https://github.com/publiccodenet/standard/workflows/Test/badge.svg)
+![Scheduled link check](https://github.com/publiccodenet/standard/workflows/Scheduled%20link%20check/badge.svg)
+
+The Standard for Public Code is in a draft format.
+We are preparing it for a version 1.0 release.
+Currently, we are testing it on a small number of codebases.
+
+## Request for contributions
+
+We believe public policy and software should be inclusive, usable, open, legible, accountable, accessible and sustainable. This means we need a new way of designing, developing and procuring both the source code and policy documentation.
+
+This standard sets a quality level for codebases that meets the needs of public organizations, institutions and administrations as well as other critical infrastructural services.
+
+The standard lives at [standard.publiccode.net](https://standard.publiccode.net/). See [`index.md`](index.md) for an overview of all content.
+
+[![Thumbnail for the video on the Standard for Public Code: a printed version lying on a table between two hands](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)
+
+[A video introduction to Standard for Public Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube.
+
+## Help improve this standard
+
+The Foundation for Public Code is committed to maintaining and developing the Standard for Public Code at a level of quality that meets the standard itself.
+
+We are looking for people like you to [contribute](CONTRIBUTING.md) to this project by suggesting improvements and helping develop it. 😊 Get started by reading our [contributors guide](CONTRIBUTING.md). Since it is such a core document we will accept contributions when they add significant value. We've described how we govern the standard in the [governance statement](GOVERNANCE.md).
+
+Please note that this project is released with a [code of conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. Please be lovely to all other community members.
+
+## Preview, build and deploy
+
+The repository builds to a static site deployed at [standard.publiccode.net](https://standard.publiccode.net/). It is built with [GitHub pages](https://pages.github.com) and [Jekyll](https://jekyllrb.com/).
+
+See the scripts in the [script](https://github.com/publiccodenet/standard/tree/main/script) folder.
+
+## Generating a PDF of the Standard for Public Code
+
+Using [Weasyprint](https://weasyprint.org/) the file `print.html` can be converted to a nice looking PDF.
+
+```bash
+weasyprint http://localhost:4000/print.html standard.pdf
+```
+
+## License
+
+© [The authors and contributors](AUTHORS.md)
+
+The standard is [licensed](LICENSE) under CC 0, which also applies to all illustrations and the documentation. This means anyone can do anything with it. If you contribute you also grant these rights to others. You can read more about how to help in the [contributing guide](CONTRIBUTING.md).
diff --git a/_site/assets/cc-zero-badge.svg b/_site/assets/cc-zero-badge.svg
new file mode 100644
index 00000000..9a925204
--- /dev/null
+++ b/_site/assets/cc-zero-badge.svg
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1 Basic//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11-basic.dtd">
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="88" height="31" viewBox="0 0 88 31" baseProfile="basic" version="1.1">
+<g id="surface1">
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(66.666667%,69.803922%,67.058824%);fill-opacity:1;" d="M 2.300781 0.570313 L 85.429688 0.71875 C 86.589844 0.71875 87.628906 0.546875 87.628906 3.039063 L 87.527344 30.414063 L 0.203125 30.414063 L 0.203125 2.9375 C 0.203125 1.707031 0.324219 0.570313 2.300781 0.570313 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 86.351563 0.199219 L 1.648438 0.199219 C 0.738281 0.199219 0 0.9375 0 1.847656 L 0 30.628906 C 0 30.832031 0.167969 31 0.371094 31 L 87.628906 31 C 87.832031 31 88 30.832031 88 30.628906 L 88 1.847656 C 88 0.9375 87.261719 0.199219 86.351563 0.199219 Z M 1.648438 0.945313 L 86.351563 0.945313 C 86.851563 0.945313 87.253906 1.347656 87.253906 1.847656 C 87.253906 1.847656 87.253906 13.46875 87.253906 21.851563 L 26.515625 21.851563 C 24.296875 25.863281 20.023438 28.585938 15.117188 28.585938 C 10.207031 28.585938 5.933594 25.863281 3.714844 21.851563 L 0.746094 21.851563 C 0.746094 13.46875 0.746094 1.847656 0.746094 1.847656 C 0.746094 1.347656 1.148438 0.945313 1.648438 0.945313 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 46.753906 23.984375 L 50.832031 23.984375 L 50.832031 24.738281 L 48.230469 27.886719 L 50.90625 27.886719 L 50.90625 28.832031 L 46.679688 28.832031 L 46.679688 28.074219 L 49.28125 24.925781 L 46.753906 24.925781 L 46.753906 23.984375 M 51.8125 23.984375 L 55.183594 23.984375 L 55.183594 24.925781 L 53.0625 24.925781 L 53.0625 25.832031 L 55.058594 25.832031 L 55.058594 26.773438 L 53.0625 26.773438 L 53.0625 27.886719 L 55.253906 27.886719 L 55.253906 28.832031 L 51.8125 28.832031 L 51.8125 23.984375 M 58.132813 26.132813 C 58.394531 26.132813 58.582031 26.082031 58.695313 25.984375 C 58.808594 25.890625 58.867188 25.730469 58.867188 25.503906 C 58.867188 25.285156 58.808594 25.125 58.695313 25.03125 C 58.582031 24.9375 58.394531 24.890625 58.132813 24.890625 L 57.605469 24.890625 L 57.605469 26.132813 L 58.132813 26.132813 M 57.605469 26.996094 L 57.605469 28.832031 L 56.355469 28.832031 L 56.355469 23.984375 L 58.265625 23.984375 C 58.902344 23.984375 59.371094 24.089844 59.667969 24.304688 C 59.964844 24.519531 60.117188 24.855469 60.117188 25.320313 C 60.117188 25.640625 60.039063 25.902344 59.882813 26.109375 C 59.730469 26.316406 59.496094 26.464844 59.183594 26.5625 C 59.355469 26.601563 59.507813 26.691406 59.640625 26.832031 C 59.777344 26.964844 59.914063 27.175781 60.054688 27.453125 L 60.734375 28.832031 L 59.402344 28.832031 L 58.8125 27.625 C 58.691406 27.382813 58.570313 27.21875 58.445313 27.128906 C 58.324219 27.039063 58.164063 26.996094 57.960938 26.996094 L 57.605469 26.996094 M 63.6875 24.800781 C 63.304688 24.800781 63.011719 24.941406 62.800781 25.222656 C 62.589844 25.503906 62.484375 25.902344 62.484375 26.410156 C 62.484375 26.921875 62.589844 27.316406 62.800781 27.597656 C 63.011719 27.878906 63.304688 28.019531 63.6875 28.019531 C 64.070313 28.019531 64.367188 27.878906 64.578125 27.597656 C 64.785156 27.316406 64.890625 26.921875 64.890625 26.410156 C 64.890625 25.902344 64.785156 25.503906 64.578125 25.222656 C 64.367188 24.941406 64.070313 24.800781 63.6875 24.800781 M 63.6875 23.894531 C 64.464844 23.894531 65.078125 24.117188 65.519531 24.5625 C 65.960938 25.011719 66.179688 25.625 66.179688 26.410156 C 66.179688 27.195313 65.960938 27.808594 65.519531 28.253906 C 65.078125 28.703125 64.464844 28.925781 63.6875 28.925781 C 62.910156 28.925781 62.300781 28.703125 61.855469 28.253906 C 61.414063 27.808594 61.195313 27.195313 61.195313 26.410156 C 61.195313 25.625 61.414063 25.011719 61.855469 24.5625 C 62.300781 24.117188 62.910156 23.894531 63.6875 23.894531 "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 25.121094 14.578125 C 25.125 20.097656 20.648438 24.578125 15.125 24.582031 C 9.605469 24.585938 5.125 20.113281 5.121094 14.589844 C 5.121094 14.585938 5.121094 14.582031 5.121094 14.578125 C 5.117188 9.054688 9.59375 4.578125 15.113281 4.574219 C 20.636719 4.570313 25.117188 9.042969 25.121094 14.566406 C 25.121094 14.570313 25.121094 14.574219 25.121094 14.578125 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 23.25 6.433594 C 25.464844 8.652344 26.574219 11.367188 26.574219 14.578125 C 26.574219 17.789063 25.484375 20.476563 23.304688 22.636719 C 20.992188 24.910156 18.261719 26.046875 15.105469 26.046875 C 11.992188 26.046875 9.304688 24.921875 7.050781 22.664063 C 4.792969 20.410156 3.667969 17.714844 3.667969 14.578125 C 3.667969 11.441406 4.792969 8.726563 7.050781 6.433594 C 9.246094 4.214844 11.933594 3.109375 15.105469 3.109375 C 18.316406 3.109375 21.03125 4.214844 23.25 6.433594 Z M 8.542969 7.925781 C 6.667969 9.820313 5.730469 12.035156 5.730469 14.582031 C 5.730469 17.125 6.660156 19.324219 8.511719 21.175781 C 10.367188 23.03125 12.578125 23.960938 15.140625 23.960938 C 17.703125 23.960938 19.929688 23.023438 21.824219 21.148438 C 23.621094 19.410156 24.519531 17.21875 24.519531 14.582031 C 24.519531 11.960938 23.605469 9.738281 21.78125 7.910156 C 19.953125 6.085938 17.742188 5.171875 15.140625 5.171875 C 12.539063 5.171875 10.339844 6.089844 8.542969 7.925781 Z M 13.476563 13.460938 C 13.1875 12.835938 12.761719 12.523438 12.1875 12.523438 C 11.175781 12.523438 10.671875 13.207031 10.671875 14.566406 C 10.671875 15.925781 11.175781 16.605469 12.1875 16.605469 C 12.855469 16.605469 13.332031 16.277344 13.617188 15.613281 L 15.019531 16.359375 C 14.351563 17.542969 13.351563 18.136719 12.015625 18.136719 C 10.984375 18.136719 10.15625 17.824219 9.539063 17.191406 C 8.917969 16.558594 8.609375 15.6875 8.609375 14.578125 C 8.609375 13.488281 8.925781 12.621094 9.566406 11.980469 C 10.207031 11.335938 11.003906 11.015625 11.957031 11.015625 C 13.371094 11.015625 14.378906 11.574219 14.992188 12.6875 Z M 20.066406 13.460938 C 19.78125 12.835938 19.359375 12.523438 18.808594 12.523438 C 17.777344 12.523438 17.261719 13.207031 17.261719 14.566406 C 17.261719 15.925781 17.777344 16.605469 18.808594 16.605469 C 19.476563 16.605469 19.945313 16.277344 20.210938 15.613281 L 21.644531 16.359375 C 20.976563 17.542969 19.976563 18.136719 18.644531 18.136719 C 17.613281 18.136719 16.789063 17.824219 16.171875 17.191406 C 15.550781 16.558594 15.242188 15.6875 15.242188 14.578125 C 15.242188 13.488281 15.554688 12.621094 16.183594 11.980469 C 16.8125 11.335938 17.613281 11.015625 18.585938 11.015625 C 19.996094 11.015625 21.003906 11.574219 21.613281 12.6875 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 60.03125 10.878906 C 60.03125 15.128906 58.308594 18.578125 56.183594 18.578125 C 54.054688 18.578125 52.332031 15.128906 52.332031 10.878906 C 52.332031 6.625 54.054688 3.179688 56.183594 3.179688 C 58.308594 3.179688 60.03125 6.625 60.03125 10.878906 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 56.429688 2.417969 C 51.582031 2.417969 50.359375 6.996094 50.359375 10.875 C 50.359375 14.757813 51.582031 19.332031 56.429688 19.332031 C 61.28125 19.332031 62.5 14.757813 62.5 10.875 C 62.5 6.996094 61.28125 2.417969 56.429688 2.417969 Z M 56.429688 5.609375 C 56.628906 5.609375 56.808594 5.636719 56.976563 5.679688 C 57.324219 5.980469 57.496094 6.394531 57.160156 6.976563 L 53.929688 12.914063 C 53.832031 12.160156 53.816406 11.425781 53.816406 10.875 C 53.816406 9.167969 53.9375 5.609375 56.429688 5.609375 Z M 58.847656 8.34375 C 59.019531 9.257813 59.042969 10.207031 59.042969 10.875 C 59.042969 12.585938 58.925781 16.144531 56.429688 16.144531 C 56.234375 16.144531 56.054688 16.125 55.886719 16.082031 C 55.851563 16.074219 55.824219 16.0625 55.792969 16.050781 C 55.742188 16.035156 55.6875 16.019531 55.640625 16 C 55.082031 15.765625 54.734375 15.335938 55.238281 14.582031 Z "/>
+</g>
+</svg>
diff --git a/_site/assets/codebase.svg b/_site/assets/codebase.svg
new file mode 100644
index 00000000..bdd5de50
--- /dev/null
+++ b/_site/assets/codebase.svg
@@ -0,0 +1,134 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>Public code codebase</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<g clip-path="url(#clip0)">
+<rect width="595" height="842" fill="#00BA8D"/>
+<path d="M275.383 549.165L275.383 602.307C275.383 608.457 272.553 614.265 267.71 618.056L233.53 644.809C228.299 648.903 225.243 655.177 225.243 661.82V661.82C225.243 667.785 220.407 672.621 214.442 672.621L-121 672.621" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M280.755 549.165L280.755 603.744C280.755 609.061 278.638 614.16 274.871 617.913L247.245 645.433C243.478 649.186 241.36 654.285 241.36 659.602L241.36 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M296.872 549.165L296.872 612.05L296.44 651.296L296.44 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M291.5 549.165L291.5 608.832C291.5 610.964 291.159 613.082 290.49 615.106L279.542 648.24C278.874 650.264 278.533 652.382 278.533 654.514L278.533 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M286.126 549.165L286.126 605.779C286.126 609.862 284.877 613.847 282.546 617.198L262.414 646.147C260.083 649.499 258.834 653.484 258.834 657.566L258.834 671.068C258.834 682.114 249.88 691.068 238.834 691.068L156.487 691.068C150.964 691.068 146.487 695.545 146.487 701.068L146.487 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M179.125 691.068L85.1144 691.068C79.6284 691.068 75.1812 695.516 75.1812 701.002V701.002C75.1812 706.488 70.7339 710.935 65.2479 710.935L-18.8297 710.935C-24.3157 710.935 -28.7629 715.382 -28.7629 720.868V720.868" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M325.523 549.165L325.523 602.307C325.523 608.457 328.352 614.265 333.195 618.056L367.989 645.29C372.832 649.081 375.662 654.889 375.662 661.039L375.662 844.324" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M320.15 549.165L320.151 603.739C320.151 609.057 322.268 614.156 326.035 617.908L353.661 645.429C357.428 649.182 359.546 654.281 359.546 659.598L359.546 850" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M304.034 549.165L304.467 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M309.406 549.165L309.406 610.226C309.406 611.44 309.517 612.651 309.736 613.844L319.36 666.172C321.106 675.663 329.38 682.554 339.03 682.554L533.75 682.554C544.795 682.554 553.75 691.509 553.75 702.554L553.75 720.159L553.75 844.324" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M314.779 549.165L314.779 605.78C314.779 609.862 316.028 613.847 318.359 617.198L336.103 642.714C339.842 648.09 345.975 651.296 352.523 651.296L723.324 651.296" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="121.655" cy="672.621" r="4.25709" fill="#FFF500"/>
+<circle cx="476.412" cy="682.554" r="4.25709" fill="#FFF500"/>
+<circle cx="571.488" cy="651.336" r="4.25709" fill="#FFF500"/>
+<circle cx="279.167" cy="654.174" r="4.25709" fill="#FFF500"/>
+<circle cx="459.384" cy="651.336" r="2.83806" fill="#FFF500"/>
+<circle cx="304" cy="639.274" r="3.54758" fill="#FFF500"/>
+<circle cx="296.195" cy="678.297" r="2.83806" fill="#FFF500"/>
+<circle cx="487.765" cy="651.336" r="2.83806" fill="#FFF500"/>
+<circle cx="551.621" cy="651.336" r="2.83806" fill="#FFF500"/>
+<path d="M380.411 0V237.001C380.411 243.005 377.713 248.692 373.063 252.49L356.557 265.972C351.907 269.77 349.209 275.457 349.209 281.462V317.154" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M387.345 0V241.521C387.345 247.45 384.714 253.073 380.163 256.873L363.903 270.449C359.352 274.249 356.721 279.873 356.721 285.802V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M374.633 0V241.521C374.633 247.45 372.002 253.073 367.451 256.873L351.191 270.449C346.64 274.249 344.009 279.873 344.009 285.802V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M394.856 0V246.3C394.856 252.322 392.142 258.024 387.468 261.822L371.043 275.168C366.369 278.966 363.655 284.668 363.655 290.69V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M368.855 0V246.3C368.855 252.322 366.141 258.024 361.467 261.822L345.041 275.168C340.367 278.966 337.653 284.668 337.653 290.69V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M402.368 0V250.835C402.368 256.857 399.654 262.558 394.981 266.356L378.553 279.706C373.88 283.504 371.166 289.206 371.166 295.228V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M363.655 0V250.835C363.655 256.857 360.941 262.558 356.268 266.356L339.84 279.706C335.166 283.504 332.453 289.206 332.453 295.228V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M409.302 0V255.78C409.302 261.707 406.672 267.329 402.123 271.129L385.857 284.716C381.307 288.516 378.678 294.138 378.678 300.066V326.762" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M356.721 0V255.78C356.721 261.707 354.092 267.329 349.542 271.129L333.276 284.716C328.727 288.516 326.097 294.138 326.097 300.066V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M416.813 0V260.419C416.813 266.428 414.111 272.119 409.454 275.917L392.971 289.362C388.314 293.16 385.611 298.851 385.611 304.86V331.019" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M351.521 0V260.419C351.521 266.428 348.818 272.119 344.162 275.917L327.678 289.362C323.021 293.16 320.319 298.851 320.319 304.86V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M226.17 0V155.161C226.17 158.539 227.026 161.862 228.658 164.821L254.884 212.367C256.516 215.325 257.372 218.649 257.372 222.027V317.154" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M219.236 0V164.999C219.236 168.315 220.061 171.579 221.635 174.497L247.461 222.356C249.036 225.274 249.86 228.538 249.86 231.854V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M231.948 0V164.999C231.948 168.315 232.773 171.579 234.347 174.497L260.173 222.356C261.748 225.274 262.572 228.538 262.572 231.854V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M211.725 0V175.847C211.725 179.24 212.588 182.578 214.234 185.546L240.417 232.764C242.063 235.732 242.927 239.07 242.927 242.463V316.433" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M237.726 0V175.847C237.726 179.24 238.59 182.578 240.235 185.546L266.419 232.764C268.065 235.732 268.928 239.07 268.928 242.463V316.433" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M204.213 0V185.911C204.213 189.304 205.077 192.642 206.722 195.609L232.907 242.838C234.552 245.806 235.415 249.143 235.415 252.536V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M242.926 0V185.911C242.926 189.304 243.79 192.642 245.435 195.609L271.62 242.838C273.265 245.806 274.128 249.143 274.128 252.536V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M197.28 0V196.644C197.28 199.958 198.104 203.221 199.677 206.139L225.506 254.021C227.08 256.939 227.904 260.202 227.904 263.516V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M249.86 0V196.644C249.86 199.958 250.684 203.221 252.258 206.139L278.087 254.021C279.66 256.939 280.484 260.202 280.484 263.516V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M189.768 0V207.151C189.768 210.533 190.626 213.861 192.262 216.822L218.476 264.277C220.112 267.238 220.97 270.565 220.97 273.948V330.634" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M255.061 0V207.151C255.061 210.533 255.918 213.861 257.554 216.822L283.769 264.277C285.404 267.238 286.262 270.565 286.262 273.948V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="403.332" cy="207.888" r="3.54758" fill="#FFF500"/>
+<circle cx="189.768" cy="211.436" r="4.25709" fill="#FFF500"/>
+<circle cx="219.568" cy="244.073" r="4.25709" fill="#FFF500"/>
+<circle cx="224.534" cy="203.631" r="2.12855" fill="#FFF500"/>
+<circle cx="197.573" cy="124.165" r="2.12855" fill="#FFF500"/>
+<circle cx="246.529" cy="221.369" r="4.25709" fill="#FFF500"/>
+<circle cx="257.172" cy="284.516" r="3.54758" fill="#FFF500"/>
+<circle cx="363.599" cy="305.801" r="3.54758" fill="#FFF500"/>
+<path d="M-121 493.823L27.0723 493.823C33.4516 493.823 39.4483 490.78 43.2146 485.631L87.2815 425.387C91.0478 420.239 97.0445 417.195 103.424 417.195L194.025 417.195" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 510.851L37.7624 510.851C44.0562 510.851 49.983 507.889 53.7602 502.854L98.1875 443.64C101.965 438.605 107.891 435.643 114.185 435.643L194.025 435.643" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 479.633L37.1175 479.633C43.434 479.633 49.3792 476.649 53.1538 471.584L97.2088 412.472C100.983 407.408 106.929 404.424 113.245 404.424L194.025 404.424" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 529.299L48.5065 529.299C54.892 529.299 60.8938 526.25 64.6592 521.092L108.624 460.877C112.389 455.72 118.391 452.671 124.777 452.671L194.025 452.671" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 465.442L47.7296 465.442C54.0633 465.442 60.0227 462.442 63.7951 457.354L108.619 396.902C112.391 391.815 118.35 388.815 124.684 388.815L194.025 388.815" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 547.746L58.514 547.746C64.899 547.746 70.9003 544.698 74.6658 539.541L118.639 479.324C122.405 474.167 128.406 471.118 134.791 471.118L194.025 471.118" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 452.671L56.9474 452.671C63.2844 452.671 69.2466 449.668 73.0185 444.576L117.787 384.139C121.559 379.047 127.521 376.043 133.858 376.043L194.025 376.043" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 564.775L69.2272 564.775C75.5198 564.775 81.4454 561.813 85.2228 556.78L129.672 497.56C133.449 492.527 139.375 489.566 145.667 489.566L194.025 489.566" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 435.643L69.2272 435.643C75.5198 435.643 81.4454 432.681 85.2228 427.648L129.672 368.428C133.449 363.395 139.375 360.434 145.667 360.434H194.025" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 583.222L79.6379 583.222C86.0107 583.222 92.002 580.185 95.7692 575.045L139.945 514.771C143.712 509.631 149.703 506.594 156.076 506.594L193.309 506.594" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M208.216 346.244H156.488C150.192 346.244 144.265 349.208 140.488 354.244L95.0169 414.871C91.2398 419.907 85.312 422.871 79.0169 422.871L-32.0732 422.871C-44.1226 422.871 -55.7667 418.52 -64.8632 410.618L-85.6531 392.558C-97.8729 381.943 -90.3655 361.853 -74.1789 361.853V361.853C-57.8228 361.853 -50.41 382.297 -62.9651 392.78L-85.0885 411.252C-94.0797 418.759 -105.421 422.871 -117.134 422.871L-121 422.871" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="33.6746" cy="547.746" r="2.83806" fill="#FFF500"/>
+<circle cx="73.4075" cy="446.995" r="4.25709" fill="#FFF500"/>
+<circle cx="147.197" cy="435.643" r="4.25709" fill="#FFF500"/>
+<path d="M723.324 353.458L572.459 353.458C568.063 353.458 563.791 354.906 560.301 357.578L515.326 392.011C511.836 394.683 507.563 396.131 503.168 396.131L411.137 396.131" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 343.975L562.744 343.975C558.421 343.975 554.214 345.376 550.754 347.967L505.495 381.865C502.035 384.457 497.829 385.858 493.506 385.858L411.847 385.858" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 361.36L562.744 361.36C558.421 361.36 554.214 362.761 550.754 365.352L505.495 399.251C502.035 401.842 497.829 403.243 493.506 403.243L411.847 403.243" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 333.702L552.081 333.702C547.668 333.702 543.379 335.161 539.882 337.853L495.224 372.224C491.727 374.915 487.439 376.375 483.026 376.375L411.847 376.375" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 369.263L552.081 369.263C547.668 369.263 543.379 370.722 539.882 373.413L495.224 407.785C491.727 410.476 487.439 411.936 483.026 411.936L411.847 411.936" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 323.429L648.19 323.429C646.189 323.429 644.568 321.807 644.568 319.806V319.806C644.568 316.885 641.287 315.166 638.885 316.827L631.483 321.948C630.088 322.912 628.433 323.429 626.738 323.429L542.163 323.429C537.751 323.429 533.463 324.888 529.966 327.579L485.298 361.952C481.802 364.643 477.513 366.102 473.101 366.102L411.847 366.102" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M721.195 376.375L542.163 376.375C537.751 376.375 533.463 377.834 529.966 380.525L485.298 414.898C481.802 417.589 477.513 419.048 473.101 419.048L411.847 419.048" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 313.946L665.199 313.946C660.074 313.946 655.92 309.791 655.92 304.667V304.667C655.92 296.417 645.961 292.269 640.105 298.08L628.772 309.324C625.789 312.285 621.756 313.946 617.553 313.946L531.563 313.946C527.241 313.946 523.036 315.346 519.576 317.936L474.294 351.839C470.834 354.429 466.629 355.829 462.307 355.829L411.847 355.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M722.614 385.858L531.563 385.858C527.241 385.858 523.036 387.257 519.576 389.848L474.294 423.75C470.834 426.34 466.629 427.74 462.307 427.74L411.847 427.74" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M721.905 303.673L687.001 303.673C678.064 303.673 670.82 296.428 670.82 287.492V287.492C670.82 272.683 652.576 265.655 642.641 276.635L624.131 297.092C620.339 301.282 614.952 303.673 609.301 303.673L521.232 303.673C516.832 303.673 512.554 305.124 509.062 307.801L464.175 342.217C460.684 344.895 456.406 346.346 452.006 346.346L392.69 346.346" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 392.97L521.232 392.97C516.832 392.97 512.554 394.421 509.063 397.098L464.176 431.514C460.684 434.192 456.406 435.643 452.006 435.643L411.847 435.643" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="571.488" cy="313.606" r="2.83806" fill="#FFF500"/>
+<path d="M79.0835 95.0751H152.873V201.503H79.0835V95.0751Z" fill="#5B57CA"/>
+<path d="M81.9215 97.9132H155.711V204.341H81.9215V97.9132Z" fill="#5B57CA"/>
+<path d="M84.7596 100.751H158.549V207.179H84.7596V100.751Z" fill="#5B57CA"/>
+<path d="M87.5977 103.589H161.387V210.017H87.5977V103.589Z" fill="#5B57CA"/>
+<path d="M90.4357 106.427H164.225V212.855H90.4357V106.427Z" fill="#5B57CA"/>
+<path d="M93.2738 109.265H167.063V215.693H93.2738V109.265Z" fill="#5B57CA"/>
+<path d="M130.352 181.098L130.352 181.098L129.675 181.011L129.796 181.683L129.796 181.683L129.796 181.683L129.797 181.684L129.798 181.69L129.802 181.718C129.806 181.744 129.813 181.785 129.82 181.838C129.835 181.946 129.855 182.106 129.873 182.311C129.91 182.722 129.941 183.313 129.917 184.023C129.87 185.447 129.605 187.332 128.739 189.211C127.877 191.082 126.415 192.955 123.955 194.366C121.489 195.78 117.991 196.745 113.033 196.745H112.948H112.864H112.779H112.695H112.61H112.524H112.439H112.353H112.268H112.182H112.096H112.01H111.923H111.837H111.75H111.663H111.576H111.489H111.402H111.314H111.226H111.139H111.051H110.962H110.874H110.786H110.697H110.608H110.52H110.431H110.341H110.252H110.163H110.073H109.983H109.893H109.803H109.713H109.623H109.533H109.442H109.351H109.261H109.17H109.079H108.988H108.896H108.805H108.713H108.622H108.53H108.438H108.346H108.254H108.162H108.07H107.977H107.885H107.792H107.699H107.606H107.513H107.42H107.327H107.234H107.141H107.047H106.954H106.86H106.766H106.673H106.579H106.485H106.391H106.297H106.202H106.108H106.014H105.919H105.825H105.73H105.636H105.541H105.446H105.351H105.256H105.161H105.066H104.971H104.876H104.78H104.685H104.59H104.494H104.399H104.303H104.207H104.112H104.016H103.92H103.824H103.728H103.633H103.537H103.441H103.345H103.248H103.152H103.056H102.96H102.864H102.768H102.671H102.575H102.479H102.382H102.286H102.189H102.093H101.996H101.9H101.803H101.707H101.61H101.514H101.417H101.32H101.224H101.127H101.031H100.934H100.837H100.741H100.644H100.547H100.451H100.354H100.257H100.161H100.064H99.9675H99.8709H99.7743H99.6777H99.5811H99.4845H99.3879H99.2914H99.1949H99.0983H99.0019H98.9054H98.8089H98.7125H98.6161H98.5197H98.4234H98.3271H98.2308H98.1345H98.0383H97.9421H97.846H97.7499H97.6538H97.5578H97.4618H97.3658H97.2699H97.1741H97.0783H96.9825H96.8868H96.7911H96.6955H96.6H96.5045H96.409H96.3137H96.2183H96.1231H96.0279H95.9327H95.8377H95.7427H95.6477H95.5529H95.4581H95.3633H95.2687H95.1741H95.0796H94.9852H94.8908H94.7966H94.7024H94.6083H94.5143H94.4203H94.3265H94.2327H94.1391H94.0455H93.952H93.8586H93.7653H93.6721H93.579H93.486H93.3931H93.3003H93.2076H93.115H93.0225H92.9302H92.8379H92.7457H92.6537H92.5617H92.4699H92.3782H92.2866H92.1951H92.1038H92.0125H91.9214H91.8304H91.7396H91.6488H91.5582H91.4678H91.3774H91.2872H91.1971H91.1071H91.0173H90.9277H90.8381H90.7487H90.6595H90.5703H90.4814H90.3925H90.3039H90.2153H90.127H90.0387H89.9506H89.8627H89.7749H89.6873H89.5999H89.5126H89.4254H89.3385H89.2516H89.165H89.0785H88.9922H88.9061H88.8201H88.7343H88.6486H88.5632H88.4779H88.3928H88.3079H88.2231H88.1385H88.0542H87.9699H87.8859H87.8021H87.7185H87.635H87.5517H87.4687H87.3858H87.3031H87.2206H87.1383H87.0562H86.9743H86.8926H86.8111H86.7298H86.6488H86.5679H86.4872H86.4067H86.3265H86.2465H86.1666H86.087H86.0076H85.9285H85.8495H85.7708H85.6923H85.614H85.5359H85.4581H85.3805H85.3031H85.2259H85.149H85.0723H84.9958H84.9196H84.8436H84.7679H84.6924H84.6171H84.5421H84.4673H84.3928H84.3185H84.2444H84.1706H84.0971H84.0238H83.9508H83.878H83.8055H83.7332H83.6612H83.5894H83.5179H83.4467H83.3757H83.305H83.2346H83.1644H83.0945H83.0249H82.9555H82.8865H82.8177H82.7491H82.6809H82.6129H82.5452H82.4778H82.4107H82.3438H82.2773H82.211H82.145H82.0793H82.0139H81.9488H81.884H81.8194H81.7552H81.6913H81.6277H81.5643H81.5013H81.4386H81.3762H81.3141H81.2523H81.1908H81.1296H81.0687H81.0081H80.9479H80.888H80.8284H80.7691H80.7101H80.6514H80.5931H80.5351H80.4774H80.42H80.363H80.3063H80.25H80.1939H80.1382H80.0828H80.0278H79.9731H79.9188H79.8647H79.8111H79.7577H79.7047H79.6521H79.5998H79.5479H79.4963H79.445H79.3941H79.3436H79.2934H79.2436H79.1941H79.145H79.0962H79.0479H78.9998H78.9522H78.9049H78.8579H78.8114H78.7652H78.7194H78.6739H78.6289H78.5842H78.5399H78.4959H78.4524H78.4092H78.3664H78.324H78.282H78.2403H78.1991H78.1582H78.1177H78.0776H78.038H77.9987H77.9598H77.9213H77.8832H77.8455H77.8082H77.7713H77.7348H77.6987H77.663H77.6277H77.5929H77.5584H77.5244H77.4908H77.4576H77.4248H77.3924H77.3604H77.3289H77.2978H77.2671H77.2368H77.207H77.1776H77.1486H77.12H77.0919H77.0642H77.037H77.0101H76.9838H76.9578H76.9323H76.9072H76.8826H76.8584H76.8347H76.8114H76.7886H76.7662H76.7454V91.318H149.535V91.3349V91.3719V91.4101V91.4495V91.4901V91.5319V91.575V91.6192V91.6647V91.7113V91.7591V91.8082V91.8584V91.9098V91.9623V92.0161V92.071V92.127V92.1842V92.2426V92.3021V92.3628V92.4246V92.4875V92.5516V92.6167V92.683V92.7504V92.819V92.8886V92.9593V93.0312V93.1041V93.1781V93.2532V93.3294V93.4066V93.4849V93.5643V93.6447V93.7262V93.8088V93.8924V93.977V94.0627V94.1494V94.2371V94.3259V94.4156V94.5064V94.5982V94.691V94.7848V94.8796V94.9754V95.0722V95.17V95.2687V95.3684V95.4691V95.5708V95.6734V95.7769V95.8815V95.9869V96.0933V96.2007V96.3089V96.4181V96.5283V96.6393V96.7513V96.8641V96.9779V97.0926V97.2082V97.3246V97.442V97.5602V97.6793V97.7993V97.9201V98.0418V98.1644V98.2878V98.4121V98.5372V98.6632V98.79V98.9177V99.0461V99.1754V99.3055V99.4364V99.5681V99.7007V99.834V99.9681V100.103V100.239V100.375V100.513V100.651V100.789V100.929V101.069V101.21V101.352V101.495V101.638V101.782V101.927V102.072V102.219V102.366V102.513V102.662V102.811V102.961V103.111V103.262V103.414V103.567V103.72V103.874V104.028V104.183V104.339V104.496V104.653V104.811V104.969V105.128V105.288V105.449V105.61V105.771V105.933V106.096V106.26V106.424V106.588V106.753V106.919V107.086V107.253V107.42V107.588V107.757V107.926V108.096V108.266V108.437V108.609V108.78V108.953V109.126V109.299V109.474V109.648V109.823V109.999V110.175V110.351V110.528V110.706V110.884V111.062V111.241V111.421V111.601V111.781V111.962V112.143V112.325V112.507V112.69V112.873V113.056V113.24V113.424V113.609V113.794V113.979V114.165V114.352V114.538V114.725V114.913V115.101V115.289V115.477V115.666V115.856V116.045V116.235V116.425V116.616V116.807V116.998V117.19V117.382V117.574V117.767V117.96V118.153V118.347V118.54V118.735V118.929V119.124V119.319V119.514V119.709V119.905V120.101V120.297V120.494V120.69V120.887V121.085V121.282V121.48V121.678V121.876V122.074V122.273V122.471V122.67V122.869V123.069V123.268V123.468V123.668V123.868V124.068V124.268V124.469V124.67V124.87V125.071V125.272V125.474V125.675V125.876V126.078V126.28V126.482V126.684V126.886V127.088V127.29V127.492V127.695V127.897V128.1V128.302V128.505V128.708V128.911V129.113V129.316V129.519V129.722V129.925V130.128V130.331V130.535V130.738V130.941V131.144V131.347V131.55V131.753V131.956V132.16V132.363V132.566V132.769V132.972V133.175V133.378V133.58V133.783V133.986V134.189V134.391V134.594V134.796V134.999V135.201V135.403V135.605V135.807V136.009V136.211V136.413V136.615V136.816V137.017V137.219V137.42V137.621V137.821V138.022V138.223V138.423V138.623V138.823V139.023V139.223V139.422V139.621V139.82V140.019V140.218V140.417V140.615V140.813V141.011V141.209V141.406V141.603V141.8V141.997V142.193V142.39V142.586V142.781V142.977V143.172V143.367V143.561V143.756V143.95V144.144V144.337V144.53V144.723V144.916V145.108V145.3V145.492V145.683V145.874V146.065V146.255V146.445V146.634V146.824V147.013V147.201V147.389V147.577V147.764V147.952V148.138V148.324V148.51V148.696V148.881V149.065V149.25V149.434V149.617V149.8V149.982V150.165V150.346V150.527V150.708V150.889V151.068V151.248V151.427V151.605V151.783V151.961V152.138V152.314V152.49V152.666V152.841V153.015V153.189V153.363V153.536V153.708V153.88V154.051V154.222V154.392V154.562V154.731V154.9V155.068V155.236V155.402V155.569V155.735V155.9V156.064V156.228V156.392V156.554V156.717V156.878V157.039V157.199V157.359V157.518V157.677V157.834V157.991V158.148V158.304V158.459V158.613V158.767V158.92V159.073V159.225V159.376V159.526V159.676V159.825V159.973V160.121V160.268V160.414V160.559V160.704V160.848V160.991V161.134V161.276V161.417V161.557V161.697V161.835V161.973V162.11V162.247V162.382V162.517V162.651V162.785V162.917V163.049V163.18V163.31V163.439V163.567V163.695V163.822V163.948V164.073V164.197V164.32V164.443V164.564V164.685V164.805V164.924V165.042V165.159V165.276V165.391V165.506V165.62V165.732V165.844V165.955V166.065V166.174V166.283V166.39V166.496V166.602V166.706V166.81V166.912V167.014V167.114V167.214C149.535 171.34 148.334 174.233 146.571 176.273C144.801 178.32 142.428 179.549 140.018 180.271C137.609 180.993 135.19 181.201 133.367 181.227C132.457 181.24 131.699 181.207 131.171 181.172C130.906 181.154 130.7 181.135 130.56 181.121C130.49 181.114 130.437 181.108 130.402 181.104L130.363 181.1L130.354 181.099L130.352 181.098L130.352 181.098Z" stroke="#FFF500"/>
+<path d="M76.2454 90.818L76.7454 90.818L76.7454 91.318L76.2454 91.318L76.2454 90.818ZM49.2838 90.818L49.2838 91.318L49.2838 90.818ZM49.2838 37.3948C34.6694 37.3948 22.8222 49.2421 22.8222 63.8564L21.8222 63.8564C21.8222 48.6898 34.1171 36.3948 49.2838 36.3948L49.2838 37.3948ZM75.7454 63.8564C75.7454 49.2421 63.8981 37.3948 49.2838 37.3948L49.2838 36.3948C64.4504 36.3948 76.7454 48.6898 76.7454 63.8564L75.7454 63.8564ZM75.7454 90.818L75.7454 63.8564L76.7454 63.8564L76.7454 90.818L75.7454 90.818ZM49.2838 90.318L76.2454 90.318L76.2454 91.318L49.2838 91.318L49.2838 90.318ZM22.8222 63.8564C22.8222 78.4708 34.6694 90.318 49.2838 90.318L49.2838 91.318C34.1171 91.318 21.8222 79.023 21.8222 63.8564L22.8222 63.8564Z" fill="#FFF500"/>
+<rect x="36.1882" y="60.7751" width="6.16265" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<rect x="46.2025" y="60.7751" width="6.16265" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<rect x="56.2168" y="60.7751" width="6.16266" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<line x1="113.64" y1="115.442" x2="113.64" y2="172.622" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="0.5" y1="-0.5" x2="52.0137" y2="-0.5" transform="matrix(-0.999819 -0.0190427 0 -1 140.102 144.322)" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="125.578" y1="155.048" x2="103.207" y2="132.677" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="124.866" y1="132.677" x2="102.495" y2="155.048" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M115.269 215.693V329.925V329.925C115.269 346.285 134.981 354.555 146.653 343.091L149.184 340.606C152.913 336.943 157.93 334.891 163.157 334.891H218.149" stroke="#FFF500"/>
+<circle cx="115.269" cy="216.402" r="4.96661" fill="#FFF500"/>
+<circle cx="304.71" cy="414.357" r="252.588" fill="#FFF500" fill-opacity="0.1"/>
+<circle cx="304.71" cy="414.357" r="201.502" fill="#FFF500" fill-opacity="0.1"/>
+<circle cx="301.872" cy="421.452" r="146.16" fill="#FFF500"/>
+<rect x="480.97" y="121.396" width="94.7708" height="61.0451" fill="#5B57CA"/>
+<rect x="480.97" y="121.396" width="30.8005" height="16.6487" fill="#FF0F00"/>
+<path d="M490.921 125.36L486.499 129.799L490.921 134.238" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M501.845 125.36L506.267 129.799L501.845 134.238" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="0.5" y1="-0.5" x2="9.41277" y2="-0.5" transform="matrix(-0.498561 0.866854 -0.865192 -0.50144 498.415 125.36)" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="417" y="77" width="94.7708" height="61.0452" stroke="#FFF500"/>
+<path d="M511.771 92.0631L511.271 92.0631L511.271 92.5631L511.771 92.5631L511.771 92.0631ZM526.776 62.4369C534.785 62.4369 541.281 68.9552 541.281 77L542.281 77C542.281 68.4066 535.341 61.4369 526.776 61.4369L526.776 62.4369ZM512.271 77C512.271 68.9552 518.767 62.4369 526.776 62.4369L526.776 61.4369C518.211 61.4369 511.271 68.4066 511.271 77L512.271 77ZM512.271 92.0631L512.271 77L511.271 77L511.271 92.0631L512.271 92.0631ZM526.776 91.5631L511.771 91.5631L511.771 92.5631L526.776 92.5631L526.776 91.5631ZM541.281 77C541.281 85.0448 534.785 91.5631 526.776 91.5631L526.776 92.5631C535.341 92.5631 542.281 85.5935 542.281 77L541.281 77Z" fill="#5B57CA"/>
+<rect width="3.4298" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 534.064 75.2785)" fill="#5B57CA"/>
+<rect width="3.42979" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 528.491 75.2785)" fill="#5B57CA"/>
+<rect width="3.42981" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 523.098 75.4144)" fill="#5B57CA"/>
+<path d="M291.339 580.795L161.653 519.09C156.069 516.433 154.397 509.279 158.225 504.422C164.225 496.809 174.203 493.533 183.548 496.107L277.795 522.075C285.614 524.229 293.973 523.126 300.966 519.015L414.444 452.313C419.354 449.426 416.389 441.888 410.828 443.121L370.7 452.013C363.596 453.587 356.342 454.381 349.065 454.381L290.213 454.381C282.723 454.381 276.238 449.177 274.618 441.864C272.756 433.462 277.885 425.095 286.218 422.942L335.318 410.258C351.699 406.026 367.402 399.506 381.963 390.889L424.413 365.769C441.932 355.403 462.196 350.629 482.5 352.087L609.463 361.201L609.463 497.377L524.106 497.377C515.98 497.377 507.938 499.028 500.468 502.229L316.047 581.279C308.124 584.675 299.123 584.498 291.339 580.795Z" fill="#5B57CA"/>
+<path d="M572.907 354.791C572.907 352.03 575.145 349.791 577.907 349.791H723.324V539.193L577.116 515.783C574.691 515.394 572.907 513.302 572.907 510.845V354.791Z" fill="#5F5AE0"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="595" height="842" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/collaboration.svg b/_site/assets/collaboration.svg
new file mode 100644
index 00000000..deec655b
--- /dev/null
+++ b/_site/assets/collaboration.svg
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+    <rdf:RDF>
+       <cc:Work rdf:about="">
+          <dc:format>image/svg+xml</dc:format>
+            <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+            <dc:title>Collaboration on public code</dc:title>
+            <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+       </cc:Work>
+       <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+            <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+            <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+            <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+       </cc:License>
+    </rdf:RDF>
+</metadata>
+<g clip-path="url(#clip0)">
+<rect width="595" height="842" fill="#56CCF2"/>
+<path d="M353.189 555.208L596 582L596 468.549L375.081 490.445C346.189 493.309 317.545 483.002 297.102 462.386L280.734 445.879C274.147 439.236 262.932 441.355 259.222 449.943C254.345 461.237 243.221 468.549 230.92 468.549L188.2 468.549C185.843 468.549 183.559 469.369 181.739 470.867L180.733 471.695C176.705 475.011 175.332 480.578 177.356 485.386C178.721 488.63 178.035 492.374 175.609 494.923L172.819 497.854C168.788 502.089 168.074 508.491 171.072 513.511C172.851 516.49 172.917 520.189 171.243 523.229L170.434 524.699C167.735 529.602 168.162 535.631 171.525 540.105C173.964 543.351 174.9 547.484 174.097 551.464L173.976 552.066C172.729 558.246 176.606 564.302 182.74 565.758L236.333 578.475C246.015 580.773 256.162 580.129 265.476 576.627L307.025 561.003C321.744 555.469 337.559 553.484 353.189 555.208Z" fill="#FFB7B7"/>
+<path d="M415.414 384.398L425.148 146L307.616 146L333.953 380.337C336.452 402.571 329.684 424.852 315.241 441.94L306.017 452.853C300.035 459.93 302.585 470.774 311.093 474.445C322.902 479.54 330.549 491.168 330.549 504.029L330.549 552.818C330.549 555.176 331.37 557.461 332.87 559.282L333.692 560.28C337.011 564.306 342.577 565.679 347.386 563.657C350.63 562.293 354.374 562.978 356.925 565.403L359.852 568.187C364.089 572.215 370.49 572.929 375.511 569.933C378.49 568.156 382.189 568.09 385.229 569.762L386.701 570.571C391.603 573.267 397.631 572.841 402.105 569.482C405.351 567.044 409.483 566.109 413.463 566.911L413.986 567.016C420.179 568.264 426.228 564.313 427.574 558.141L440.85 497.278C442.906 487.854 442.192 478.036 438.794 469.008L421.741 423.707C417.019 411.161 414.867 397.793 415.414 384.398Z" fill="#683838"/>
+<path d="M242.649 292.789L1.15043e-05 266L-4.95358e-09 379.451L220.785 357.556C249.666 354.691 278.299 364.999 298.729 385.613L315.084 402.116C321.669 408.76 332.883 406.642 336.59 398.054C341.464 386.763 352.584 379.451 364.882 379.451L411.81 379.451C414.167 379.451 416.452 378.631 418.272 377.132L419.274 376.306C423.301 372.989 424.674 367.423 422.651 362.614C421.286 359.37 421.972 355.626 424.397 353.076L427.184 350.147C431.213 345.911 431.927 339.509 428.931 334.489C427.152 331.51 427.087 327.811 428.76 324.771L429.569 323.3C432.266 318.397 431.839 312.369 428.479 307.895C426.04 304.649 425.105 300.516 425.907 296.537L426.018 295.983C427.266 289.795 423.344 283.744 417.186 282.356L359.216 269.29C349.694 267.144 339.752 267.832 330.616 271.269L288.836 286.988C274.111 292.528 258.287 294.515 242.649 292.789Z" fill="#FF7F80"/>
+<path d="M181.287 458.539L182.792 688L284.685 688L262.513 458.648C260.537 438.205 265.946 417.73 277.761 400.93L285.809 389.487C291.066 382.013 288.126 371.595 279.738 367.971C267.424 362.652 259.451 350.522 259.451 337.109L259.451 296.204C259.451 293.847 258.632 291.563 257.134 289.744L256.304 288.735C252.989 284.707 247.422 283.334 242.614 285.358C239.37 286.724 235.626 286.038 233.077 283.611L230.146 280.82C225.911 276.789 219.509 276.075 214.489 279.073C211.51 280.853 207.811 280.918 204.771 279.245L203.301 278.435C198.398 275.736 192.368 276.163 187.895 279.526C184.649 281.966 180.515 282.902 176.535 282.099L175.933 281.978C169.754 280.731 163.698 284.607 162.243 290.741L149.922 342.676C147.379 353.396 148.447 364.656 152.962 374.706L172.508 418.22C178.206 430.903 181.195 444.635 181.287 458.539Z" fill="#391F1F"/>
+<path d="M264.628 576.801L295.184 565.306C315.528 557.653 329 538.192 329 516.455C329 502.693 323.565 489.488 313.876 479.713L280.345 445.883C273.76 439.239 262.545 441.357 258.837 449.946C253.963 461.237 242.841 468.549 230.543 468.549L182.193 468.549C179.835 468.549 177.551 469.369 175.731 470.868L174.728 471.694C170.701 475.011 169.328 480.577 171.351 485.386C172.715 488.63 172.03 492.374 169.604 494.924L166.817 497.853C162.787 502.089 162.073 508.491 165.07 513.511C166.849 516.49 166.914 520.189 165.241 523.229L164.432 524.7C161.734 529.603 162.161 535.631 165.522 540.105C167.961 543.351 168.897 547.484 168.094 551.464L167.986 552.002C166.737 558.192 170.674 564.242 176.839 565.608L236.388 578.805C245.797 580.89 255.608 580.193 264.628 576.801Z" fill="#FFB7B7"/>
+<path d="M298.622 149.215C296.448 148.813 294.797 147.031 294.561 144.833L279 0L443 6.24721e-06L432.741 168.358C432.558 171.356 429.792 173.517 426.839 172.97L298.622 149.215Z" fill="black"/>
+<path d="M596 454L596 593L467.549 581.356C464.973 581.123 463 578.963 463 576.377L463 472.679C463 470.123 464.928 467.978 467.47 467.707L596 454Z" fill="#FF776E"/>
+<path d="M279.923 650C282.508 650 284.667 651.971 284.902 654.546L299 809L178 809C175.239 809 173 806.761 173 804L173 655C173 652.239 175.239 650 178 650L279.923 650Z" fill="white"/>
+<path d="M287.025 682C289.6 682 291.754 683.956 292.001 686.52L307 842L178 842C175.239 842 173 839.761 173 837L173 687C173 684.239 175.239 682 178 682L287.025 682Z" fill="#0000FF"/>
+<path d="M122 266C124.761 266 127 268.239 127 271L127 376C127 378.761 124.761 381 122 381L79 381L79 266L122 266Z" fill="#9F9F9F"/>
+<path d="M93 256C95.7614 256 98 258.239 98 261L98 386C98 388.761 95.7614 391 93 391L1.72836e-06 391L7.62939e-06 256L93 256Z" fill="#C4C4C4"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="595" height="842" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/collaborative-developement.svg b/_site/assets/collaborative-developement.svg
new file mode 100644
index 00000000..61961e20
--- /dev/null
+++ b/_site/assets/collaborative-developement.svg
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>collaborative public code development</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="white"/>
+<rect width="595" height="842" fill="#FDBBAB"/>
+<rect x="132" y="324" width="200" height="150" fill="black"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M463 364C463 344.67 447.33 329 428 329C408.67 329 393 344.67 393 364L393 398C393 398.552 393.448 399 394 399L428 399C447.33 399 463 383.33 463 364Z" fill="black"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 444 360)" stroke="white"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 431 360)" stroke="white"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 418 360)" stroke="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M262 289C262 269.67 277.67 254 297 254C316.33 254 332 269.67 332 289L332 323C332 323.552 331.552 324 331 324L297 324C277.67 324 262 308.33 262 289Z" fill="#5B57CA"/>
+<rect x="280.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="293.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="306.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="232" y="399" width="200" height="150" fill="#5B57CA"/>
+<rect x="232" y="399" width="100" height="75" fill="#FF0F00"/>
+<path d="M264.316 423L250 437.316L264.316 451.632" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M299.684 423L314 437.316L299.684 451.632" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="288.945" y1="424.366" x2="273.945" y2="450.347" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="343" y="419" width="78" height="2" rx="1" fill="black"/>
+<rect x="343" y="430.721" width="21" height="2" rx="1" fill="black"/>
+<rect x="388" y="442.442" width="21" height="2" rx="1" fill="black"/>
+<rect x="371" y="430.721" width="50" height="2" rx="1" fill="black"/>
+<rect width="21" height="2" rx="1" transform="matrix(-1 0 0 1 421 455.14)" fill="black"/>
+<rect width="50" height="2" rx="1" transform="matrix(-1 0 0 1 393 455.14)" fill="black"/>
+<rect x="343" y="442.442" width="39" height="2" rx="1" fill="black"/>
+<rect x="414" y="442.442" width="7" height="2" rx="1" fill="black"/>
+<rect x="143" y="419" width="78" height="2" rx="1" fill="white"/>
+<rect x="143" y="430.721" width="21" height="2" rx="1" fill="white"/>
+<rect x="188" y="442.442" width="21" height="2" rx="1" fill="white"/>
+<rect x="171" y="430.721" width="50" height="2" rx="1" fill="white"/>
+<rect width="21" height="2" rx="1" transform="matrix(-1 0 0 1 221 455.14)" fill="white"/>
+<rect width="50" height="2" rx="1" transform="matrix(-1 0 0 1 193 455.14)" fill="white"/>
+<rect x="143" y="442.442" width="39" height="2" rx="1" fill="white"/>
+<rect x="214" y="442.442" width="7" height="2" rx="1" fill="white"/>
+</svg>
diff --git a/_site/assets/dpg-badge.svg b/_site/assets/dpg-badge.svg
new file mode 100644
index 00000000..96e97b1d
--- /dev/null
+++ b/_site/assets/dpg-badge.svg
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 25.2.3, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 92.19 46.47" style="enable-background:new 0 0 92.19 46.47;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#2C269A;}
+	.st1{fill:#82DBE1;}
+	.st2{fill:none;stroke:#FFFFFF;stroke-miterlimit:10;}
+</style>
+<g>
+	<g>
+		<g>
+			<g>
+				<g>
+					<path class="st0" d="M73.52,44.58H8.51L1.24,30.55l0.16-0.34L14.71,1.89l64.95,0l7.25,14.07L73.52,44.58z M9.42,43.08h63.14
+						l12.68-27.08l-6.49-12.6H15.67L2.91,30.52L9.42,43.08z"/>
+				</g>
+			</g>
+		</g>
+	</g>
+	<g>
+		<g>
+			<g>
+				<g>
+					<path class="st1" d="M73.52,44.58H8.51L1.24,30.55l0.16-0.34L14.71,1.89l64.95,0l7.25,14.07L73.52,44.58z M9.42,43.08h63.14
+						l12.68-27.08l-6.49-12.6H15.67L2.91,30.52L9.42,43.08z"/>
+				</g>
+			</g>
+		</g>
+	</g>
+	<polygon class="st1" points="14.71,1.89 78.75,1.89 85.24,15.99 72.56,43.08 9.42,43.08 2.91,30.52 	"/>
+	<g>
+		<g>
+			<path class="st0" d="M18.05,15.4h4.11c4.14,0,7.52,3.36,7.52,7.52s-3.38,7.52-7.52,7.52h-4.11V15.4z M22.14,28.84
+				c3.34,0,5.94-2.53,5.94-5.92S25.48,17,22.14,17h-2.51v11.83H22.14z"/>
+			<path class="st0" d="M42.33,19.58c0,2.33-1.86,4.16-4.19,4.16h-3.79v6.7h-1.6V15.4h5.39C40.47,15.4,42.33,17.28,42.33,19.58z
+				 M40.73,19.61c0-1.6-1.23-2.66-2.73-2.66h-3.64v5.27h3.64C39.5,22.22,40.73,21.26,40.73,19.61z"/>
+			<path class="st0" d="M59.51,22.47v0.45c0,4.26-3.46,7.72-7.72,7.72c-4.29,0-7.72-3.46-7.72-7.72c0-4.26,3.44-7.72,7.72-7.72
+				c2.88,0,5.39,1.58,6.69,3.91l-1.38,0.78c-1.03-1.86-3.03-3.08-5.31-3.08c-3.39,0-6.12,2.71-6.12,6.12s2.73,6.12,6.12,6.12
+				c3.03,0,5.54-2.16,6.02-5.07h-6.04v-1.5H59.51z"/>
+		</g>
+	</g>
+	<g>
+		<g>
+			<rect x="67.42" y="11.04" class="st0" width="19.92" height="19.92"/>
+			
+				<rect x="67.38" y="10.96" transform="matrix(0.866 0.5 -0.5 0.866 20.8201 -35.8665)" class="st0" width="19.92" height="19.92"/>
+			<rect x="67.38" y="10.96" transform="matrix(0.866 -0.5 0.5 0.866 -0.0975 41.4714)" class="st0" width="19.92" height="19.92"/>
+		</g>
+		<polyline class="st2" points="72.34,21.15 76.12,24.93 83.48,17.57 		"/>
+	</g>
+</g>
+</svg>
diff --git a/_site/assets/eco-system.svg b/_site/assets/eco-system.svg
new file mode 100644
index 00000000..02706113
--- /dev/null
+++ b/_site/assets/eco-system.svg
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>ecosystem around public code development</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="#FDBBAB"/>
+<g transform="scale(1.4) translate(0 75)">
+    <circle cx="352.5" cy="88.5" r="22.5" fill="#FFF500"/>
+    <path d="M324 117L323 117L323 118L324 118L324 117ZM352.5 61C367.688 61 380 73.3122 380 88.5L382 88.5C382 72.2076 368.792 59 352.5 59L352.5 61ZM325 88.5C325 73.3122 337.312 61 352.5 61L352.5 59C336.208 59 323 72.2076 323 88.5L325 88.5ZM325 117L325 88.5L323 88.5L323 117L325 117ZM352.5 116L324 116L324 118L352.5 118L352.5 116ZM380 88.5C380 103.688 367.688 116 352.5 116L352.5 118C368.792 118 382 104.792 382 88.5L380 88.5Z" fill="#5B57CA"/>
+    <path d="M344.364 86.3492C344.05 85.8955 343.427 85.7829 342.973 86.0977C342.519 86.4126 342.406 87.0356 342.721 87.4894L344.364 86.3492ZM350.855 97.4571L350.033 98.0272C350.227 98.307 350.551 98.4688 350.891 98.4565C351.231 98.4442 351.542 98.2595 351.715 97.9665L350.855 97.4571ZM362.318 80.0522C362.599 79.5769 362.442 78.9636 361.966 78.6823C361.491 78.401 360.878 78.5582 360.597 79.0335L362.318 80.0522ZM342.721 87.4894L350.033 98.0272L351.676 96.8871L344.364 86.3492L342.721 87.4894ZM351.715 97.9665L362.318 80.0522L360.597 79.0335L349.994 96.9478L351.715 97.9665Z" fill="#5B57CA"/>
+    <path d="M160.915 108.133L163.003 120.061C163.276 121.623 162.24 123.113 160.681 123.402C159.422 123.635 158.159 123.011 157.579 121.87L152.417 111.721C149.754 106.485 143.713 103.922 138.097 105.644L132.207 107.45C127.792 108.804 123.034 106.861 120.829 102.804L114.609 91.3608L147.998 95.7539C154.546 96.6154 159.776 101.628 160.915 108.133Z" fill="#0D06C1"/>
+    <path d="M172.397 108.556L176.264 129.116C176.605 130.927 175.409 132.669 173.598 133.003C172.133 133.273 170.667 132.536 170.009 131.2L162.92 116.788C157.62 106.015 145.304 100.657 133.809 104.125L129.021 105.57C122.644 107.494 116.204 102.763 116.133 96.1031L116.023 85.8799L150.764 88.9444C161.555 89.8963 170.395 97.9104 172.397 108.556Z" fill="#241ED3"/>
+    <path d="M173.559 102.552L187.461 124.065C188.586 125.806 188.037 128.133 186.253 129.186C184.77 130.062 182.878 129.781 181.712 128.514L166.482 111.948C158.659 103.44 146.644 100.182 135.595 103.573L129.123 105.559C122.733 107.52 116.254 102.78 116.189 96.096L116.101 86.9952L151.969 89.7161C160.777 90.3843 168.765 95.1336 173.559 102.552Z" fill="#403ADD"/>
+    <path d="M217 301.057C195.471 301.057 174.608 293.592 157.965 279.934C141.323 266.276 129.931 247.27 125.731 226.155C121.531 205.039 124.782 183.12 134.931 164.133C145.08 145.146 161.498 130.265 181.389 122.027C201.279 113.788 223.411 112.7 244.013 118.95C264.615 125.2 282.413 138.399 294.374 156.3C306.335 174.201 311.719 195.696 309.609 217.121C307.499 238.547 298.025 258.578 282.801 273.801L217 208L217 301.057Z" fill="#FF6666"/>
+    <path d="M217 150.614C227.073 150.614 236.969 153.265 245.693 158.302C254.417 163.339 261.661 170.583 266.698 179.307C271.735 188.031 274.386 197.927 274.386 208C274.386 218.073 271.735 227.969 266.698 236.693C261.661 245.417 254.417 252.661 245.693 257.698C236.969 262.735 227.073 265.386 217 265.386C206.927 265.386 197.031 262.735 188.307 257.698C179.583 252.661 172.339 245.417 167.302 236.693L217 208L217 150.614Z" fill="#FFF500"/>
+    <path d="M217 228C213.044 228 209.178 226.827 205.889 224.629C202.6 222.432 200.036 219.308 198.522 215.654C197.009 211.999 196.613 207.978 197.384 204.098C198.156 200.219 200.061 196.655 202.858 193.858C205.655 191.061 209.219 189.156 213.098 188.384C216.978 187.613 220.999 188.009 224.654 189.522C228.308 191.036 231.432 193.6 233.629 196.889C235.827 200.178 237 204.044 237 208L217 208L217 228Z" fill="#5B57CA"/>
+    <path d="M240.846 338.808L230.88 313.476C230.014 311.274 231.091 308.786 233.289 307.91C235.313 307.104 237.62 307.94 238.658 309.855L243.653 319.073C250.138 331.041 263.45 337.635 276.9 335.542L294.731 332.766L282.229 358.794L266.76 357.758C255.184 356.984 245.093 349.604 240.846 338.808Z" fill="#0D06C1"/>
+    <path d="M230.062 348.809L201.522 322.841C199.553 321.05 199.76 317.894 201.946 316.375C203.314 315.425 205.118 315.386 206.526 316.278L216.409 322.538C230.056 331.181 245.837 335.858 261.99 336.047L284.449 336.308L278.525 364.883L242.767 355.671C238.037 354.452 233.675 352.097 230.062 348.809Z" fill="#241ED3"/>
+    <path d="M228.222 356.834L182.375 335.491C180.456 334.598 179.457 332.455 180.004 330.411C180.637 328.051 183.083 326.672 185.429 327.352L215.834 336.17C226.445 339.248 237.431 340.845 248.479 340.917L275.724 341.094L276.818 363.72L237.641 359.46C234.379 359.106 231.197 358.218 228.222 356.834Z" fill="#403ADD"/>
+    <path d="M224.679 364.935L183.047 349.069C180.573 348.127 179.213 345.466 179.898 342.909C180.62 340.215 183.352 338.581 186.067 339.22L225.434 348.48C230.065 349.57 234.89 349.542 239.508 348.4L267.282 341.529C270.542 340.722 270.804 336.189 267.658 335.013L263.649 333.514C259.35 331.906 254.817 331.01 250.23 330.86L234.755 330.356C231.524 330.251 229.001 327.528 229.142 324.299C229.266 321.48 231.398 319.158 234.196 318.794L271.356 313.967C282.595 312.507 294 312.968 305.084 315.331L363.332 327.746C372.469 329.694 379 337.764 379 347.106C379 358.039 370.138 366.901 359.205 366.901L305 366.901L235.362 366.901C231.711 366.901 228.091 366.235 224.679 364.935Z" fill="#5B57CA"/>
+    <circle cx="98.5" cy="205.5" r="7.5" fill="#FFF500"/>
+    <circle cx="335.5" cy="205.5" r="7.5" fill="#FFF500"/>
+    <ellipse cx="217.5" cy="208" rx="118.5" ry="119" stroke="#5B57CA" stroke-width="2"/>
+    <path fill-rule="evenodd" clip-rule="evenodd" d="M36 333C36 313.67 51.67 298 71 298C90.33 298 106 313.67 106 333L106 367C106 367.552 105.552 368 105 368L71 368C51.67 368 36 352.33 36 333Z" fill="#5B57CA"/>
+    <rect x="54.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <rect x="67.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <rect x="80.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <circle cx="216.5" cy="88.5" r="13.5" fill="#FFF500"/>
+    <path d="M199.737 42L189 52.5L199.737 63" stroke="#FFF500" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+    <path d="M234.263 42L245 52.5L234.263 63" stroke="#FFF500" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+    <circle cx="216.5" cy="52.5" r="7.5" fill="#FFF500"/>
+    <ellipse cx="217" cy="207.5" rx="30" ry="29.5" stroke="#5B57CA" stroke-width="2"/>
+    <circle cx="99" cy="206" r="44" stroke="#5B57CA" stroke-width="2"/>
+    <circle cx="217" cy="208" r="6" fill="#FF6666"/>
+    <circle cx="216" cy="327" r="12" fill="#FFF500"/>
+    <path d="M345 345.996C344.448 345.996 344 346.444 344 346.996C344 347.549 344.448 347.996 345 347.996V345.996ZM368.993 347.996C369.545 347.996 369.993 347.549 369.993 346.996C369.993 346.444 369.545 345.996 368.993 345.996V347.996ZM345 347.996L368.993 347.996V345.996L345 345.996V347.996Z" fill="#F55C5C"/>
+    <path d="M357.996 335C357.996 334.448 357.549 334 356.996 334C356.444 334 355.996 334.448 355.996 335H357.996ZM355.996 358.993C355.996 359.545 356.444 359.993 356.996 359.993C357.549 359.993 357.996 359.545 357.996 358.993H355.996ZM355.996 335V358.993H357.996V335H355.996Z" fill="#F55C5C"/>
+    <path d="M99.1344 161.009C98.5871 160.935 98.0833 161.318 98.0091 161.866C97.9349 162.413 98.3184 162.917 98.8656 162.991L99.1344 161.009ZM216.866 178.991C217.413 179.065 217.917 178.682 217.991 178.134C218.065 177.587 217.682 177.083 217.134 177.009L216.866 178.991ZM98.8656 162.991L216.866 178.991L217.134 177.009L99.1344 161.009L98.8656 162.991Z" fill="#5B57CA"/>
+    <path d="M212.886 236.007C213.434 235.943 213.93 236.337 213.993 236.886C214.057 237.434 213.663 237.93 213.114 237.993L212.886 236.007ZM100.114 250.993C99.5656 251.057 99.0697 250.663 99.0065 250.114C98.9434 249.566 99.337 249.07 99.8857 249.007L100.114 250.993ZM213.114 237.993L100.114 250.993L99.8857 249.007L212.886 236.007L213.114 237.993Z" fill="#5B57CA"/>
+    <circle cx="128.5" cy="205.5" r="11.5" fill="#FFF500"/>
+    <path d="M174.899 97.1398L196.049 118.96C197.809 120.776 197.408 123.76 195.23 125.046C193.909 125.827 192.253 125.762 190.997 124.88L170.387 110.422C162.846 105.131 153.292 103.598 144.474 106.265L129.864 110.683C125.582 111.977 124.97 117.787 128.888 119.946L148.457 130.731C151.409 132.358 152.263 136.207 150.275 138.929C148.954 140.739 146.68 141.586 144.496 141.081L110.523 133.224C95.3408 129.346 81.4885 121.438 70.4298 110.337L46.4595 86.2757C37.6089 77.3914 39.5035 62.5471 50.3018 56.1705C56.9223 52.261 65.236 52.6747 71.4357 57.2221L91.2365 71.7455C99.0407 77.4698 108.114 81.2212 117.682 82.6796L159.1 88.9928C165.115 89.9096 170.664 92.7712 174.899 97.1398Z" fill="#5B57CA"/>
+    <path d="M61.2287 62C61.2287 61.4477 60.781 61 60.2287 61C59.6764 61 59.2287 61.4477 59.2287 62L61.2287 62ZM59.2287 82.4574C59.2287 83.0097 59.6764 83.4574 60.2287 83.4574C60.781 83.4574 61.2287 83.0097 61.2287 82.4574L59.2287 82.4574ZM59.2287 62L59.2287 82.4574L61.2287 82.4574L61.2287 62L59.2287 62Z" fill="#F55C5C"/>
+    <path d="M70.4574 73.2288C71.0097 73.2288 71.4574 72.781 71.4574 72.2288C71.4574 71.6765 71.0097 71.2288 70.4574 71.2288L70.4574 73.2288ZM50 71.2288C49.4477 71.2288 49 71.6765 49 72.2288C49 72.781 49.4477 73.2288 50 73.2288L50 71.2288ZM70.4574 71.2288L50 71.2288L50 73.2288L70.4574 73.2288L70.4574 71.2288Z" fill="#F55C5C"/>
+</g>
+</svg>
diff --git a/_site/assets/github-markdown.css b/_site/assets/github-markdown.css
new file mode 100644
index 00000000..bc9c3901
--- /dev/null
+++ b/_site/assets/github-markdown.css
@@ -0,0 +1,695 @@
+@font-face {
+  font-family: octicons-link;
+  src: url(data:font/woff;charset=utf-8;base64,d09GRgABAAAAAAZwABAAAAAACFQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABEU0lHAAAGaAAAAAgAAAAIAAAAAUdTVUIAAAZcAAAACgAAAAoAAQAAT1MvMgAAAyQAAABJAAAAYFYEU3RjbWFwAAADcAAAAEUAAACAAJThvmN2dCAAAATkAAAABAAAAAQAAAAAZnBnbQAAA7gAAACyAAABCUM+8IhnYXNwAAAGTAAAABAAAAAQABoAI2dseWYAAAFsAAABPAAAAZwcEq9taGVhZAAAAsgAAAA0AAAANgh4a91oaGVhAAADCAAAABoAAAAkCA8DRGhtdHgAAAL8AAAADAAAAAwGAACfbG9jYQAAAsAAAAAIAAAACABiATBtYXhwAAACqAAAABgAAAAgAA8ASm5hbWUAAAToAAABQgAAAlXu73sOcG9zdAAABiwAAAAeAAAAME3QpOBwcmVwAAAEbAAAAHYAAAB/aFGpk3jaTY6xa8JAGMW/O62BDi0tJLYQincXEypYIiGJjSgHniQ6umTsUEyLm5BV6NDBP8Tpts6F0v+k/0an2i+itHDw3v2+9+DBKTzsJNnWJNTgHEy4BgG3EMI9DCEDOGEXzDADU5hBKMIgNPZqoD3SilVaXZCER3/I7AtxEJLtzzuZfI+VVkprxTlXShWKb3TBecG11rwoNlmmn1P2WYcJczl32etSpKnziC7lQyWe1smVPy/Lt7Kc+0vWY/gAgIIEqAN9we0pwKXreiMasxvabDQMM4riO+qxM2ogwDGOZTXxwxDiycQIcoYFBLj5K3EIaSctAq2kTYiw+ymhce7vwM9jSqO8JyVd5RH9gyTt2+J/yUmYlIR0s04n6+7Vm1ozezUeLEaUjhaDSuXHwVRgvLJn1tQ7xiuVv/ocTRF42mNgZGBgYGbwZOBiAAFGJBIMAAizAFoAAABiAGIAznjaY2BkYGAA4in8zwXi+W2+MjCzMIDApSwvXzC97Z4Ig8N/BxYGZgcgl52BCSQKAA3jCV8CAABfAAAAAAQAAEB42mNgZGBg4f3vACQZQABIMjKgAmYAKEgBXgAAeNpjYGY6wTiBgZWBg2kmUxoDA4MPhGZMYzBi1AHygVLYQUCaawqDA4PChxhmh/8ODDEsvAwHgMKMIDnGL0x7gJQCAwMAJd4MFwAAAHjaY2BgYGaA4DAGRgYQkAHyGMF8NgYrIM3JIAGVYYDT+AEjAwuDFpBmA9KMDEwMCh9i/v8H8sH0/4dQc1iAmAkALaUKLgAAAHjaTY9LDsIgEIbtgqHUPpDi3gPoBVyRTmTddOmqTXThEXqrob2gQ1FjwpDvfwCBdmdXC5AVKFu3e5MfNFJ29KTQT48Ob9/lqYwOGZxeUelN2U2R6+cArgtCJpauW7UQBqnFkUsjAY/kOU1cP+DAgvxwn1chZDwUbd6CFimGXwzwF6tPbFIcjEl+vvmM/byA48e6tWrKArm4ZJlCbdsrxksL1AwWn/yBSJKpYbq8AXaaTb8AAHja28jAwOC00ZrBeQNDQOWO//sdBBgYGRiYWYAEELEwMTE4uzo5Zzo5b2BxdnFOcALxNjA6b2ByTswC8jYwg0VlNuoCTWAMqNzMzsoK1rEhNqByEyerg5PMJlYuVueETKcd/89uBpnpvIEVomeHLoMsAAe1Id4AAAAAAAB42oWQT07CQBTGv0JBhagk7HQzKxca2sJCE1hDt4QF+9JOS0nbaaYDCQfwCJ7Au3AHj+LO13FMmm6cl7785vven0kBjHCBhfpYuNa5Ph1c0e2Xu3jEvWG7UdPDLZ4N92nOm+EBXuAbHmIMSRMs+4aUEd4Nd3CHD8NdvOLTsA2GL8M9PODbcL+hD7C1xoaHeLJSEao0FEW14ckxC+TU8TxvsY6X0eLPmRhry2WVioLpkrbp84LLQPGI7c6sOiUzpWIWS5GzlSgUzzLBSikOPFTOXqly7rqx0Z1Q5BAIoZBSFihQYQOOBEdkCOgXTOHA07HAGjGWiIjaPZNW13/+lm6S9FT7rLHFJ6fQbkATOG1j2OFMucKJJsxIVfQORl+9Jyda6Sl1dUYhSCm1dyClfoeDve4qMYdLEbfqHf3O/AdDumsjAAB42mNgYoAAZQYjBmyAGYQZmdhL8zLdDEydARfoAqIAAAABAAMABwAKABMAB///AA8AAQAAAAAAAAAAAAAAAAABAAAAAA==) format('woff');
+}
+
+.markdown-body {
+  -ms-text-size-adjust: 100%;
+  -webkit-text-size-adjust: 100%;
+  line-height: 1.5;
+  color: #24292e;
+  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";
+  font-size: 16px;
+  line-height: 1.5;
+  word-wrap: break-word;
+}
+
+.markdown-body .pl-c {
+  color: #6a737d;
+}
+
+.markdown-body .pl-c1,
+.markdown-body .pl-s .pl-v {
+  color: #005cc5;
+}
+
+.markdown-body .pl-e,
+.markdown-body .pl-en {
+  color: #6f42c1;
+}
+
+.markdown-body .pl-smi,
+.markdown-body .pl-s .pl-s1 {
+  color: #24292e;
+}
+
+.markdown-body .pl-ent {
+  color: #22863a;
+}
+
+.markdown-body .pl-k {
+  color: #d73a49;
+}
+
+.markdown-body .pl-s,
+.markdown-body .pl-pds,
+.markdown-body .pl-s .pl-pse .pl-s1,
+.markdown-body .pl-sr,
+.markdown-body .pl-sr .pl-cce,
+.markdown-body .pl-sr .pl-sre,
+.markdown-body .pl-sr .pl-sra {
+  color: #032f62;
+}
+
+.markdown-body .pl-v,
+.markdown-body .pl-smw {
+  color: #e36209;
+}
+
+.markdown-body .pl-bu {
+  color: #b31d28;
+}
+
+.markdown-body .pl-ii {
+  color: #fafbfc;
+  background-color: #b31d28;
+}
+
+.markdown-body .pl-c2 {
+  color: #fafbfc;
+  background-color: #d73a49;
+}
+
+.markdown-body .pl-c2::before {
+  content: "^M";
+}
+
+.markdown-body .pl-sr .pl-cce {
+  font-weight: bold;
+  color: #22863a;
+}
+
+.markdown-body .pl-ml {
+  color: #735c0f;
+}
+
+.markdown-body .pl-mh,
+.markdown-body .pl-mh .pl-en,
+.markdown-body .pl-ms {
+  font-weight: bold;
+  color: #005cc5;
+}
+
+.markdown-body .pl-mi {
+  font-style: italic;
+  color: #24292e;
+}
+
+.markdown-body .pl-mb {
+  font-weight: bold;
+  color: #24292e;
+}
+
+.markdown-body .pl-md {
+  color: #b31d28;
+  background-color: #ffeef0;
+}
+
+.markdown-body .pl-mi1 {
+  color: #22863a;
+  background-color: #f0fff4;
+}
+
+.markdown-body .pl-mc {
+  color: #e36209;
+  background-color: #ffebda;
+}
+
+.markdown-body .pl-mi2 {
+  color: #f6f8fa;
+  background-color: #005cc5;
+}
+
+.markdown-body .pl-mdr {
+  font-weight: bold;
+  color: #6f42c1;
+}
+
+.markdown-body .pl-ba {
+  color: #586069;
+}
+
+.markdown-body .pl-sg {
+  color: #959da5;
+}
+
+.markdown-body .pl-corl {
+  text-decoration: underline;
+  color: #032f62;
+}
+
+.markdown-body .octicon {
+  display: inline-block;
+  vertical-align: text-top;
+  fill: currentColor;
+}
+
+.markdown-body a {
+  background-color: transparent;
+}
+
+.markdown-body a:active,
+.markdown-body a:hover {
+  outline-width: 0;
+}
+
+.markdown-body strong {
+  font-weight: inherit;
+}
+
+.markdown-body strong {
+  font-weight: bolder;
+}
+
+.markdown-body h1 {
+  font-size: 2em;
+  margin: 0.67em 0;
+}
+
+.markdown-body img {
+  border-style: none;
+}
+
+.markdown-body code,
+.markdown-body kbd,
+.markdown-body pre {
+  font-family: monospace, monospace;
+  font-size: 1em;
+}
+
+.markdown-body hr {
+  box-sizing: content-box;
+  height: 0;
+  overflow: visible;
+}
+
+.markdown-body input {
+  font: inherit;
+  margin: 0;
+}
+
+.markdown-body input {
+  overflow: visible;
+}
+
+.markdown-body [type="checkbox"] {
+  box-sizing: border-box;
+  padding: 0;
+}
+
+.markdown-body * {
+  box-sizing: border-box;
+}
+
+.markdown-body input {
+  font-family: inherit;
+  font-size: inherit;
+  line-height: inherit;
+}
+
+.markdown-body a {
+  color: #0366d6;
+  text-decoration: none;
+}
+
+.markdown-body a:hover {
+  text-decoration: underline;
+}
+
+.markdown-body strong {
+  font-weight: 600;
+}
+
+.markdown-body hr {
+  height: 0;
+  margin: 15px 0;
+  overflow: hidden;
+  background: transparent;
+  border: 0;
+  border-bottom: 1px solid #dfe2e5;
+}
+
+.markdown-body hr::before {
+  display: table;
+  content: "";
+}
+
+.markdown-body hr::after {
+  display: table;
+  clear: both;
+  content: "";
+}
+
+.markdown-body table {
+  border-spacing: 0;
+  border-collapse: collapse;
+}
+
+.markdown-body td,
+.markdown-body th {
+  padding: 0;
+}
+
+.markdown-body h1,
+.markdown-body h2,
+.markdown-body h3,
+.markdown-body h4,
+.markdown-body h5,
+.markdown-body h6 {
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body h1 {
+  font-size: 32px;
+  font-weight: 600;
+}
+
+.markdown-body h2 {
+  font-size: 24px;
+  font-weight: 600;
+}
+
+.markdown-body h3 {
+  font-size: 20px;
+  font-weight: 600;
+}
+
+.markdown-body h4 {
+  font-size: 16px;
+  font-weight: 600;
+}
+
+.markdown-body h5 {
+  font-size: 14px;
+  font-weight: 600;
+}
+
+.markdown-body h6 {
+  font-size: 12px;
+  font-weight: 600;
+}
+
+.markdown-body p {
+  margin-top: 0;
+  margin-bottom: 10px;
+}
+
+.markdown-body blockquote {
+  margin: 0;
+}
+
+.markdown-body ul,
+.markdown-body ol {
+  padding-left: 0;
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body ol ol,
+.markdown-body ul ol {
+  list-style-type: lower-roman;
+}
+
+.markdown-body ul ul ol,
+.markdown-body ul ol ol,
+.markdown-body ol ul ol,
+.markdown-body ol ol ol {
+  list-style-type: lower-alpha;
+}
+
+.markdown-body dd {
+  margin-left: 0;
+}
+
+.markdown-body code {
+  font-family: "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  font-size: 12px;
+}
+
+.markdown-body pre {
+  margin-top: 0;
+  margin-bottom: 0;
+  font-family: "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  font-size: 12px;
+}
+
+.markdown-body .octicon {
+  vertical-align: text-bottom;
+}
+
+.markdown-body .pl-0 {
+  padding-left: 0 !important;
+}
+
+.markdown-body .pl-1 {
+  padding-left: 4px !important;
+}
+
+.markdown-body .pl-2 {
+  padding-left: 8px !important;
+}
+
+.markdown-body .pl-3 {
+  padding-left: 16px !important;
+}
+
+.markdown-body .pl-4 {
+  padding-left: 24px !important;
+}
+
+.markdown-body .pl-5 {
+  padding-left: 32px !important;
+}
+
+.markdown-body .pl-6 {
+  padding-left: 40px !important;
+}
+
+.markdown-body::before {
+  display: table;
+  content: "";
+}
+
+.markdown-body::after {
+  display: table;
+  clear: both;
+  content: "";
+}
+
+.markdown-body>*:first-child {
+  margin-top: 0 !important;
+}
+
+.markdown-body>*:last-child {
+  margin-bottom: 0 !important;
+}
+
+.markdown-body a:not([href]) {
+  color: inherit;
+  text-decoration: none;
+}
+
+.markdown-body .anchor {
+  float: left;
+  padding-right: 4px;
+  margin-left: -20px;
+  line-height: 1;
+}
+
+.markdown-body .anchor:focus {
+  outline: none;
+}
+
+.markdown-body p,
+.markdown-body blockquote,
+.markdown-body ul,
+.markdown-body ol,
+.markdown-body dl,
+.markdown-body table,
+.markdown-body pre {
+  margin-top: 0;
+  margin-bottom: 16px;
+}
+
+.markdown-body hr {
+  height: 0.25em;
+  padding: 0;
+  margin: 24px 0;
+  background-color: #e1e4e8;
+  border: 0;
+}
+
+.markdown-body blockquote {
+  padding: 0 1em;
+  color: #6a737d;
+  border-left: 0.25em solid #dfe2e5;
+}
+
+.markdown-body blockquote>:first-child {
+  margin-top: 0;
+}
+
+.markdown-body blockquote>:last-child {
+  margin-bottom: 0;
+}
+
+.markdown-body kbd {
+  display: inline-block;
+  padding: 3px 5px;
+  font-size: 11px;
+  line-height: 10px;
+  color: #444d56;
+  vertical-align: middle;
+  background-color: #fafbfc;
+  border: solid 1px #c6cbd1;
+  border-bottom-color: #959da5;
+  border-radius: 3px;
+  box-shadow: inset 0 -1px 0 #959da5;
+}
+
+.markdown-body h1,
+.markdown-body h2,
+.markdown-body h3,
+.markdown-body h4,
+.markdown-body h5,
+.markdown-body h6 {
+  margin-top: 24px;
+  margin-bottom: 16px;
+  font-weight: 600;
+  line-height: 1.25;
+}
+
+.markdown-body h1 .octicon-link,
+.markdown-body h2 .octicon-link,
+.markdown-body h3 .octicon-link,
+.markdown-body h4 .octicon-link,
+.markdown-body h5 .octicon-link,
+.markdown-body h6 .octicon-link {
+  color: #1b1f23;
+  vertical-align: middle;
+  visibility: hidden;
+}
+
+.markdown-body h1:hover .anchor,
+.markdown-body h2:hover .anchor,
+.markdown-body h3:hover .anchor,
+.markdown-body h4:hover .anchor,
+.markdown-body h5:hover .anchor,
+.markdown-body h6:hover .anchor {
+  text-decoration: none;
+}
+
+.markdown-body h1:hover .anchor .octicon-link,
+.markdown-body h2:hover .anchor .octicon-link,
+.markdown-body h3:hover .anchor .octicon-link,
+.markdown-body h4:hover .anchor .octicon-link,
+.markdown-body h5:hover .anchor .octicon-link,
+.markdown-body h6:hover .anchor .octicon-link {
+  visibility: visible;
+}
+
+.markdown-body h1 {
+  padding-bottom: 0.3em;
+  font-size: 2em;
+  border-bottom: 1px solid #eaecef;
+}
+
+.markdown-body h2 {
+  padding-bottom: 0.3em;
+  font-size: 1.5em;
+  border-bottom: 1px solid #eaecef;
+}
+
+.markdown-body h3 {
+  font-size: 1.25em;
+}
+
+.markdown-body h4 {
+  font-size: 1em;
+}
+
+.markdown-body h5 {
+  font-size: 0.875em;
+}
+
+.markdown-body h6 {
+  font-size: 0.85em;
+  color: #6a737d;
+}
+
+.markdown-body ul,
+.markdown-body ol {
+  padding-left: 2em;
+}
+
+.markdown-body ul ul,
+.markdown-body ul ol,
+.markdown-body ol ol,
+.markdown-body ol ul {
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body li {
+  word-wrap: break-all;
+}
+
+.markdown-body li>p {
+  margin-top: 16px;
+}
+
+.markdown-body li+li {
+  margin-top: 0.25em;
+}
+
+.markdown-body dl {
+  padding: 0;
+}
+
+.markdown-body dl dt {
+  padding: 0;
+  margin-top: 16px;
+  font-size: 1em;
+  font-style: italic;
+  font-weight: 600;
+}
+
+.markdown-body dl dd {
+  padding: 0 16px;
+  margin-bottom: 16px;
+}
+
+.markdown-body table {
+  display: block;
+  width: 100%;
+  overflow: auto;
+}
+
+.markdown-body table th {
+  font-weight: 600;
+}
+
+.markdown-body table th,
+.markdown-body table td {
+  padding: 6px 13px;
+  border: 1px solid #dfe2e5;
+}
+
+.markdown-body table tr {
+  background-color: #fff;
+  border-top: 1px solid #c6cbd1;
+}
+
+.markdown-body table tr:nth-child(2n) {
+  background-color: #f6f8fa;
+}
+
+.markdown-body img {
+  max-width: 100%;
+  box-sizing: content-box;
+  /* background-color: #fff; */
+}
+
+.markdown-body img[align=right] {
+  padding-left: 20px;
+}
+
+.markdown-body img[align=left] {
+  padding-right: 20px;
+}
+
+.markdown-body code {
+  padding: 0.2em 0.4em;
+  margin: 0;
+  font-size: 85%;
+  background-color: rgba(27,31,35,0.05);
+  border-radius: 3px;
+}
+
+.markdown-body pre {
+  word-wrap: normal;
+}
+
+.markdown-body pre>code {
+  padding: 0;
+  margin: 0;
+  font-size: 100%;
+  word-break: normal;
+  white-space: pre;
+  background: transparent;
+  border: 0;
+}
+
+.markdown-body .highlight {
+  margin-bottom: 16px;
+}
+
+.markdown-body .highlight pre {
+  margin-bottom: 0;
+  word-break: normal;
+}
+
+.markdown-body .highlight pre,
+.markdown-body pre {
+  padding: 16px;
+  overflow: auto;
+  font-size: 85%;
+  line-height: 1.45;
+  background-color: #f6f8fa;
+  border-radius: 3px;
+}
+
+.markdown-body pre code {
+  display: inline;
+  max-width: auto;
+  padding: 0;
+  margin: 0;
+  overflow: visible;
+  line-height: inherit;
+  word-wrap: normal;
+  background-color: transparent;
+  border: 0;
+}
+
+.markdown-body .full-commit .btn-outline:not(:disabled):hover {
+  color: #005cc5;
+  border-color: #005cc5;
+}
+
+.markdown-body kbd {
+  display: inline-block;
+  padding: 3px 5px;
+  font: 11px "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  line-height: 10px;
+  color: #444d56;
+  vertical-align: middle;
+  background-color: #fafbfc;
+  border: solid 1px #d1d5da;
+  border-bottom-color: #c6cbd1;
+  border-radius: 3px;
+  box-shadow: inset 0 -1px 0 #c6cbd1;
+}
+
+.markdown-body :checked+.radio-label {
+  position: relative;
+  z-index: 1;
+  border-color: #0366d6;
+}
+
+.markdown-body .task-list-item {
+  list-style-type: none;
+}
+
+.markdown-body .task-list-item+.task-list-item {
+  margin-top: 3px;
+}
+
+.markdown-body .task-list-item input {
+  margin: 0 0.2em 0.25em -1.6em;
+  vertical-align: middle;
+}
+
+.markdown-body hr {
+  border-bottom-color: #eee;
+}
diff --git a/_site/assets/hand-point.svg b/_site/assets/hand-point.svg
new file mode 100644
index 00000000..beaa6645
--- /dev/null
+++ b/_site/assets/hand-point.svg
@@ -0,0 +1,6 @@
+<svg width="506" height="182" viewBox="0 0 506 182" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M130.914 32.0168L168.738 140.874C171.006 147.4 177.438 151.533 184.316 150.884L240.857 145.549L240.857 87.8457C240.857 81.303 235.553 75.999 229.01 75.999C221.486 75.999 215.868 82.9216 217.417 90.2844L221.022 107.42C221.708 110.683 219.218 113.75 215.884 113.75C213.398 113.75 211.253 112.006 210.745 109.573L204.97 81.8926C203.525 74.9685 209.529 68.7741 216.495 70.0019L250.519 75.999L292.941 10.7653L146.027 10.7653C135.021 10.7653 127.301 21.6203 130.914 32.0168Z" fill="#FF7F80"/>
+<path d="M223.392 69.9115C223.731 67.0178 220.962 64.7437 218.19 65.6393L211.779 67.7102C211.189 67.9007 210.563 67.9515 209.951 67.8588L193.515 65.3701C189.822 64.8109 187.446 69.1684 189.915 71.97L198.888 82.1492C202.841 86.634 204.31 92.7889 202.807 98.5754L199.437 111.555C198.69 114.434 201.515 116.95 204.288 115.875V115.875C208.53 114.23 213.234 114.23 217.477 115.875L217.983 116.071C220.756 117.146 223.671 114.871 223.303 111.921L220.869 92.4222C220.829 92.1031 220.828 91.7803 220.865 91.4609L223.392 69.9115Z" fill="#FF6666"/>
+<path d="M188.255 9.00011L16.4893 9.00001C7.54843 9 0.456482 16.5346 0.997192 25.4591C1.44373 32.8295 7.02103 38.8649 14.3333 39.8905L216.269 68.2159C228.915 69.9897 236.682 82.9993 232.244 94.9731L215.638 139.776C213.167 146.442 213.568 153.833 216.747 160.192C222.487 171.677 235.825 177.161 247.983 173.035L356.527 136.207C370.397 131.501 385.206 130.251 399.669 132.566L510 150.224V9.00011L414.161 9L188.255 9.00011Z" fill="#FF9999"/>
+<path d="M505.802 5.61211C505.802 2.85069 503.564 0.612122 500.802 0.612122H419.506C416.745 0.612122 414.506 2.8507 414.506 5.61212V145.853C414.506 148.024 415.908 149.948 417.975 150.613L499.272 176.755C502.499 177.792 505.802 175.385 505.802 171.995V5.61211Z" fill="#0000FF"/>
+</svg>
diff --git a/_site/assets/hands-shake.svg b/_site/assets/hands-shake.svg
new file mode 100644
index 00000000..b855bb40
--- /dev/null
+++ b/_site/assets/hands-shake.svg
@@ -0,0 +1,15 @@
+<svg width="614" height="200" viewBox="0 0 614 200" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0)">
+<path d="M352.33 50.0618C345.872 47.4623 342.742 40.1193 345.339 33.6607V33.6607C347.936 27.2021 355.276 24.0736 361.733 26.6731L365.027 27.9991C372.864 31.1539 375.443 40.9751 370.166 47.5713V47.5713C366.692 51.9139 360.783 53.4648 355.624 51.3878L352.33 50.0618Z" fill="#FF6666"/>
+<path d="M380.89 21.3972C389.463 21.3972 396.414 28.3475 396.414 36.9212L396.414 79.6875C396.414 89.6091 388.371 97.6522 378.449 97.6522V97.6522C367.718 97.6522 359.38 88.3053 360.601 77.6437L365.466 35.155C366.364 27.3159 372.999 21.3972 380.89 21.3972V21.3972Z" fill="#FF7F80"/>
+<path d="M279.17 186.353L299.773 196.535C306.307 199.764 314.08 199.183 320.062 195.019L409.334 132.868C414.766 129.087 418.154 123.015 418.521 116.407L421.998 53.7794C422.45 45.6246 416.695 38.435 408.639 37.0912C400.246 35.6913 392.224 41.0973 390.37 49.4017L376.69 110.687L320.556 140.832C314.251 144.218 306.618 143.977 300.54 140.201L286.909 131.734L279.17 186.353Z" fill="#FF9999"/>
+<path d="M257.369 3.54956L202.356 31.0729C194.07 35.2185 192.537 46.3952 199.401 52.6171C202.725 55.6301 207.354 56.7442 211.685 55.5737L252.327 44.5905C263.423 41.5918 275.257 45.1966 282.795 53.8721L308.541 83.4994C314.681 90.5654 308.614 101.441 299.375 99.9281L219.125 86.7861C210.896 85.4384 202.945 90.4106 200.553 98.4001C198.106 106.573 202.258 115.268 210.151 118.503L375.56 186.298C399.691 196.188 425.684 200.716 451.739 199.568L614.778 192.385L614.778 48.5263L474.211 79.919C461.125 82.8415 447.437 81.2964 435.332 75.5302L283.693 3.29448C275.348 -0.680748 265.636 -0.586645 257.369 3.54956Z" fill="#683838"/>
+<path d="M169.603 130.572L279.523 186.065L313.136 174.209L264.509 123.189C258.74 117.136 262.508 107.094 270.835 106.329L371.87 97.045C379.95 96.3026 386.434 90.0536 387.476 82.0061C388.622 73.1547 382.86 64.8819 374.162 62.89L174.826 17.2398C165.283 15.0542 155.576 13.6511 145.804 13.0446L-2.40968 3.84655L-2.4097 162.306L126.446 126.345C140.857 122.323 156.249 123.83 169.603 130.572Z" fill="#FF9999"/>
+<path d="M219.135 86.8177L337.414 106.433C337.85 106.506 338.242 106.738 338.514 107.086C358.547 132.707 331.609 168.284 301.515 155.95L209.749 118.339C202.084 115.197 198.052 106.753 200.428 98.8164L200.548 98.4145C202.941 90.4209 210.904 85.4527 219.135 86.8177Z" fill="#683838"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="614" height="200" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/rouge-highlight.css b/_site/assets/rouge-highlight.css
new file mode 100644
index 00000000..f1877f20
--- /dev/null
+++ b/_site/assets/rouge-highlight.css
@@ -0,0 +1,210 @@
+
+.highlight table td { padding: 5px; }
+.highlight table pre { margin: 0; }
+.highlight .cm {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .cp {
+  color: #797676;
+  font-weight: bold;
+}
+.highlight .c1 {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .cs {
+  color: #797676;
+  font-weight: bold;
+  font-style: italic;
+}
+.highlight .c, .highlight .cd {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .err {
+  color: #a61717;
+  background-color: #e3d2d2;
+}
+.highlight .gd {
+  color: #000000;
+  background-color: #ffdddd;
+}
+.highlight .ge {
+  color: #000000;
+  font-style: italic;
+}
+.highlight .gr {
+  color: #aa0000;
+}
+.highlight .gh {
+  color: #797676;
+}
+.highlight .gi {
+  color: #000000;
+  background-color: #ddffdd;
+}
+.highlight .go {
+  color: #888888;
+}
+.highlight .gp {
+  color: #555555;
+}
+.highlight .gs {
+  font-weight: bold;
+}
+.highlight .gu {
+  color: #aaaaaa;
+}
+.highlight .gt {
+  color: #aa0000;
+}
+.highlight .kc {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kd {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kn {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kp {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kr {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kt {
+  color: #445588;
+  font-weight: bold;
+}
+.highlight .k, .highlight .kv {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .mf {
+  color: #009999;
+}
+.highlight .mh {
+  color: #009999;
+}
+.highlight .il {
+  color: #009999;
+}
+.highlight .mi {
+  color: #009999;
+}
+.highlight .mo {
+  color: #009999;
+}
+.highlight .m, .highlight .mb, .highlight .mx {
+  color: #009999;
+}
+.highlight .sb {
+  color: #d14;
+}
+.highlight .sc {
+  color: #d14;
+}
+.highlight .sd {
+  color: #d14;
+}
+.highlight .s2 {
+  color: #d14;
+}
+.highlight .se {
+  color: #d14;
+}
+.highlight .sh {
+  color: #d14;
+}
+.highlight .si {
+  color: #d14;
+}
+.highlight .sx {
+  color: #d14;
+}
+.highlight .sr {
+  color: #009926;
+}
+.highlight .s1 {
+  color: #d14;
+}
+.highlight .ss {
+  color: #990073;
+}
+.highlight .s {
+  color: #d14;
+}
+.highlight .na {
+  color: #008080;
+}
+.highlight .bp {
+  color: #797676;
+}
+.highlight .nb {
+  color: #0086B3;
+}
+.highlight .nc {
+  color: #445588;
+  font-weight: bold;
+}
+.highlight .no {
+  color: #008080;
+}
+.highlight .nd {
+  color: #3c5d5d;
+  font-weight: bold;
+}
+.highlight .ni {
+  color: #800080;
+}
+.highlight .ne {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nf {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nl {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nn {
+  color: #555555;
+}
+.highlight .nt {
+  color: #000080;
+}
+.highlight .vc {
+  color: #008080;
+}
+.highlight .vg {
+  color: #008080;
+}
+.highlight .vi {
+  color: #008080;
+}
+.highlight .nv {
+  color: #008080;
+}
+.highlight .ow {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .o {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .w {
+  color: #bbbbbb;
+}
+.highlight {
+  background-color: #f8f8f8;
+}
diff --git a/_site/assets/style.css b/_site/assets/style.css
new file mode 100644
index 00000000..9470766b
--- /dev/null
+++ b/_site/assets/style.css
@@ -0,0 +1,873 @@
+@import url("github-markdown.css");
+@import url("rouge-highlight.css");
+@import url('https://fonts.googleapis.com/css?family=Muli:400,400i,700');
+
+
+/*
+ * HTML and Body elements
+*/
+
+body, html {
+  font-family: 'Muli', sans-serif;
+  margin: 0;
+}
+
+@media screen {
+  body {
+    background: whitesmoke;
+  }
+}
+
+@media print {
+  html {
+    font-size: 12pt;
+  }
+
+  @page {
+    /* A4 with, for printing presses add a (3mm to each side) bleed here */
+    size: 21cm 29.7cm;
+    margin: 2cm 1cm;
+    orphans:4;
+    widows:4;
+    @bottom-center {
+      background: whitesmoke;
+      font-size: 75%;
+      content: counter(page);
+      margin-top: 0.25cm;
+      height: 1cm;
+      width: 1cm;
+      text-align: center;
+    }
+  }
+}
+
+/*
+ * General elements and ground rules
+*/
+
+hr {
+  border: none;
+  border-bottom: 1px solid lightgrey;
+}
+
+@media screen {
+  p, h1, h2, h3, h4, h5, ul, pre, blockquote, .highlight {
+    max-width: 35em;
+    max-width: calc(30rem + 5em);
+  }
+}
+@media print {
+  p, ul {
+    max-width: 12cm;
+    max-width: 60vw;
+    box-sizing: border-box;
+  }
+}
+
+h1, h2, h3, h4, h5 {
+  page-break-after: avoid;
+}
+img, code {
+  break-inside: avoid;
+  page-break-inside: avoid;
+  overflow: wrap;
+}
+
+@media print {
+  ul, ol {
+    page-break-inside: avoid;
+  }
+  ul li, ol li {
+    margin: .5em 0;
+  }
+}
+
+/*
+ * Links
+*/
+
+a:link, a:visited {
+  text-decoration: underline;
+  color: black;
+}
+a:link {
+  text-decoration-color: blue;
+}
+a:visited {
+  text-decoration-color: purple;
+}
+a:link[href^='#'], a:visited[href^='#'] {
+  text-decoration-color: darkgrey;
+}
+a:hover {
+  background: whitesmoke;
+}
+
+@media print {
+  a:link, a:visited {
+    text-decoration: none !important;
+  }
+  a:link:after, a:visited:after {
+    color: grey;
+    border-left: 2px solid whitesmoke;
+    page-break-inside: avoid;
+    break-inside: avoid;
+    display: block;
+    right: 0;
+    width: 6cm;
+    width: 30vw;
+    margin-right: -7cm;
+    margin-right: -30vw;
+    padding: 0 0 0.25em .25em;
+    margin-bottom: .25em;
+    line-height: 1.25;
+    text-align: left;
+    float: right;
+    clear: both;
+    text-decoration: none;
+    font-weight: normal;
+  }
+  /* Add `[href^="http"]` for limiting to external sites */
+  a[href^="http"]:link {
+    color: black;
+    text-decoration: underline;
+  }
+  a[href^="http"]:after {
+    content: "" attr(href) "";
+    font-size: .75rem;
+  }
+  a[href^="/"]:after {
+    /* content: "" attr(href) "";
+    font-size: .75rem; */
+    display: none;
+  }
+  a[href^="#"]:after {
+    content: "" target-counter(attr(href), page);
+    color: black;
+    background-color: whitesmoke;
+    width: 1cm;
+    padding: 0.2cm;
+    text-align: right;
+  }
+}
+
+/*
+Buttons
+*/
+
+button, input {
+  font-family: inherit;
+  font-size: inherit;
+  margin-bottom: 0.5em;
+  padding: 0.5em;
+  display: inline-block;
+  background: none;
+  border: 1px solid lightgrey;
+  border-radius: 2px;
+  white-space: nowrap;
+}
+input:focus, button:focus {
+  border: 1px solid black;
+  background: whitesmoke;
+}
+button:hover {
+  background: whitesmoke;
+}
+button svg {
+  vertical-align: -2px;
+}
+
+/*
+ * general layout
+*/
+
+body>hr {
+  margin: 0;
+}
+
+@media screen {
+  body>nav.theme-nav, body>header, body>footer {
+    padding: 1em;
+  }
+  body>header, body>footer#site-footer {
+    background-color: white;
+  }
+  body>*:not(hr) {
+    box-sizing: border-box;
+    max-width: 80em;
+    margin: auto;
+  }
+  body.with-site-nav>*:not(hr) {
+    max-width: 100em;
+  }
+}
+
+@media screen and (min-width:68em) {
+  body>nav.theme-nav, body>header, body>footer {
+    padding: 2em 4em;
+  }
+}
+
+/*
+ * Foundation Navigation
+*/
+
+@media screen {
+  nav.theme-nav {
+    display: flex;
+    flex-direction: row;
+    align-items: center;
+    flex-wrap: wrap;
+    padding-bottom: 1rem;
+    background: none;
+  }
+}
+@media screen and (min-width:400px) {
+  nav.theme-nav {
+    padding: 1rem;
+  }
+}
+@media screen and (min-width:64em) {
+  nav.theme-nav {
+    padding: 1rem 4em;
+  }
+}
+@media print {
+  nav.theme-nav {
+    display: block;
+  }
+  nav.theme-nav ul {
+    display: none;
+  }
+}
+
+nav.theme-nav ul {
+  list-style: none;
+  margin: 0 0 12px;
+  padding-inline-start: 0px;
+  max-width: none;
+}
+nav.theme-nav ul li {
+  padding: 5px 0;
+  display: inline-block;
+}
+
+nav.theme-nav a:link, header a:visited {
+  font-weight: normal;
+  border-bottom: none;
+}
+@media screen {
+  nav.theme-nav a:link, header a:visited {
+    padding: 1rem;
+  }
+}
+@media print {
+  nav.theme-nav a:link:after, header a:visited:after {
+    display: none;
+  }
+}
+
+nav.theme-nav a.logo-mark {
+  display: flex;
+  flex-direction: row;
+  align-items: center;
+  flex: 1;
+  text-decoration: none;
+  margin-right: 40px;
+}
+
+@media screen and (max-width:640px) {
+  nav.theme-nav {
+    align-items: flex-start;
+  }
+  nav.theme-nav a.logo-mark {
+    margin-right: 0px;
+  }
+  nav.theme-nav ul  {
+    margin: 16px 15px 16px 0;
+  }
+  nav.theme-nav ul li  {
+    display:block;
+  }
+}
+
+@media screen and (min-width:520px) {
+  nav.theme-nav a.logo-mark {
+    font-size: 2em;
+  }
+}
+@media screen and (min-width:400px) and (max-width:520px) {
+  nav.theme-nav a.logo-mark {
+    font-size: 1.5em;
+  }
+}
+
+@media screen and (max-width:440px) {
+  nav.theme-nav {
+    flex-direction: column;
+  }
+  nav.theme-nav {
+    align-items: flex-start;
+  }
+}
+
+
+nav.theme-nav a.logo-mark>img {
+  height: 2em;
+  margin-right: 0.5em;
+}
+nav.theme-nav a.logo-mark>p {
+  font-weight: bold;
+  margin: 0;
+}
+
+@media print {
+  nav.theme-nav+hr {
+    display: none;
+  }
+  nav.theme-nav a.logo-mark {
+    font-size: 1.5em;
+  }
+  nav.theme-nav a.logo-mark>img {
+    margin-right: 0.9rem;
+  }
+}
+
+/*
+ * Site header
+*/
+
+@media screen {
+  header .site-title {
+    padding: 1em 1rem;
+    font-size: 1.5em;
+  }
+}
+@media screen and (min-width:400px) {
+  header .site-title {
+    font-size: 2em;
+    padding: 1.5em 2rem;
+  }
+}
+@media screen and (min-width:700px) {
+  header .site-title.home {
+    font-size: 4em;
+  }
+}
+
+header .site-title a {
+  text-decoration: none;
+}
+header .site-title a:hover {
+  text-decoration: underline;
+}
+
+@media print {
+  header .site-title a:after {
+    display: none;
+  }
+  header .site-title {
+    font-size: 1.5em;
+    margin-left: 3.5rem;
+  }
+  header+hr {
+    margin: 2em 0;
+  }
+}
+
+/*
+ * Site navigation
+*/
+
+input#show-site-nav {
+  display: none;
+}
+input#show-site-nav ~ label:before {
+  content: 'Open '
+}
+input#show-site-nav:checked ~ label:before {
+  content: 'Close '
+}
+
+nav#site-nav {
+  padding: 1rem;
+}
+nav#site-nav>ul {
+  display: none;
+}
+label[for=show-site-nav] {
+  display: block;
+}
+nav#site-nav a.active {
+  font-weight: bold;
+}
+
+input#show-site-nav ~ label {
+  margin: 1em;
+  padding: 1rem;
+  text-decoration: none;
+  border: 1px solid grey;
+  border-radius: 2px;
+  display: block;
+}
+input#show-site-nav ~ label:hover, input#show-site-nav:checked ~ label {
+  background: lightgrey;
+}
+input#show-site-nav:checked ~ ul {
+  display: block;
+}
+
+@media print {
+  nav#site-nav, input#show-site-nav {
+    display: none !important;
+    /* Hide navigation from all print */
+  }
+}
+
+/*
+ * Main content
+*/
+
+@media screen {
+  main {
+    display: flex;
+    flex-direction: row;
+    flex-wrap: wrap;
+    background: white;
+  }
+  main>* {
+    padding: 2rem;
+    box-sizing: border-box;
+    max-width: 100%;
+    order: 2;
+  }
+  main>*>* {
+    max-width: 100%;
+  }
+  main #theme-breadcrumbs {
+    flex-basis: 100%;
+    order: 0;
+  }
+  main .theme-prev-next {
+    flex-basis: 100%;
+    order: 0;
+  }
+  main .theme-prev-next-prev {
+    float:left;
+    margin-right: 5px;
+  }
+  main .theme-prev-next-next {
+    float:right;
+    margin-left: 5px;
+  }
+  main>h1 {
+    flex-basis: 100%;
+    margin: 0;
+    order: 1;
+  }
+  main .content {
+    flex: 2 2 60%;
+  }
+  main .page-information {
+    flex: 1 1 33%;
+    order: 3;
+  }
+}
+
+@media screen and (min-width:68em) {
+  main {
+    padding: 4em;
+  }
+  main>h1 {
+    font-size: 3em;
+    margin-bottom: .25em;
+  }
+}
+
+@media print {
+  main {
+    display: block !important;
+    page-break-after: always;
+  }
+  main+hr {
+    display: none;
+  }
+  main>h1 {
+    padding: 1em 3.5rem;
+    font-size: 3em;
+  }
+  main .page-information {
+    page-break-after: always;
+  }
+}
+
+/*
+ * Content
+ */
+
+#bpmn-canvas {
+  height: 50vh;
+  border: 1px solid lightgrey;
+  border-radius: 2px;
+  max-width: 50em;
+  max-height: 50vw;
+  margin-bottom: 1em;
+  page-break-inside: avoid;
+}
+#bpmn-canvas .bjs-powered-by {
+  display: none;
+}
+
+main .content>article>:first-child:not(h1):not(h2):not(ol):not(ul) {
+  font-size: 1.15em;
+}
+
+/*
+ * Markdown content
+ */
+
+@media print {
+  .markdown-body {
+    font-family: "Muli"
+  }
+
+  .markdown-body h1, .markdown-body h2, .markdown-body h3 {
+    font-weight: normal;
+    position: relative;
+  }
+  .markdown-body h1 {
+    font-size: 1.5cm;
+    border-bottom: none;
+  }
+  .markdown-body h2 {
+    font-size: 1.5em;
+  }
+  .markdown-body h3 {
+    font-size: 1em;
+    font-weight: bold;
+  }
+  .markdown-body h4 {
+    font-size: 1em;
+    font-weight: normal;
+  }
+  .markdown-body h4 {
+    font-weight: bold;
+  }
+}
+
+/*
+ * Page information section
+ */
+
+ @media screen {
+  main section.page-information {
+    flex: 1 2 300px;
+    box-sizing: border-box;
+    display: flex;
+    flex-direction: column;
+  }
+}
+
+/*
+ * Table of contents
+*/
+
+/*
+ * Navigation lists
+*/
+
+@media screen {
+  nav#site-nav>ul:before {
+    color: lightgrey;
+    text-align: center;
+    font-size: 1em;
+    line-height: 2;
+    display: block;
+    border-bottom: 1px solid;
+  }
+  ol.table-of-contents, nav#site-nav>ul {
+    list-style: none;
+    flex: 1 1 auto;
+    overflow: hidden;
+    margin: 0 0;
+    padding: 0;
+    box-sizing: border-box;
+  }
+
+  ol.table-of-contents li, nav#site-nav>ul li {
+    margin: .5em 0;
+  }
+  ol.table-of-contents>li, nav#site-nav>ul>li {
+    font-size: 1.15rem;
+    padding-bottom: 0.5em;
+  }
+  ol.table-of-contents>li ol, nav#site-nav>ul>li ul {
+    padding-left: 1em;
+    list-style: none;
+  }
+  ol.table-of-contents>li>ol>li, nav#site-nav>ul>li>ul>li {
+    font-size: 1rem;
+  }
+}
+
+@media print {
+  nav#site-nav>ul:before {
+    font-size: 1.5em;
+    font-weight: bold;
+    padding-left: 0;
+  }
+}
+
+/*
+ * Breadcrumbs
+ */
+
+#theme-breadcrumbs {
+  padding-top: 0;
+  padding-bottom: 0;
+  background-color: white;
+}
+
+#theme-breadcrumbs ul {
+  padding: 0;
+  margin: 0;
+  list-style: none;
+  line-height: 2em;
+}
+#theme-breadcrumbs li {
+  display: inline-block;
+  margin: -1.15em 0;
+  max-width: 100%;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+  overflow: hidden;
+}
+
+#theme-breadcrumbs li::after {
+  content: '›';
+  display: inline-block;
+  opacity: 0.3;
+  font-size: 1em;
+  padding: .5em;
+  line-height: 0;
+}
+
+@media print {
+  #theme-breadcrumbs {
+    display: none;
+  }
+}
+
+/*
+ * Edit links
+*/
+
+main .edit-links {
+  padding-left: 0;
+}
+main .edit-links li {
+  list-style-type: none;
+}
+main .edit-links li a {
+  margin-bottom: 0.5em;
+  padding: 0.5em;
+  text-decoration: none;
+  border-radius: 2px;
+  display: inline-block;
+  border: 1px solid lightgrey;
+}
+main .edit-links li a:link {
+  border-bottom: 1px solid blue;
+}
+main .edit-links li a:visited {
+  border-bottom: 1px solid purple;
+}
+main .edit-links a svg {
+  vertical-align: -2px;
+}
+@media print {
+  h3#page-edit-links, main .edit-links {
+    display: none;
+  }
+}
+
+/*
+ * Metadata display
+ */
+
+.metadata tbody {
+  width: 100%;
+}
+.metadata tr {
+  margin: .25em 0 0 0;
+}
+.metadata .expired {
+  color: red;
+}
+.metadata td, .metadata th {
+  padding: 0, 0.5em, 0.5em, 0;
+  text-align: left;
+  vertical-align: top;
+}
+
+/*
+ * Footer
+ */
+
+@media screen {
+  .footer-trio {
+    width: 100%;
+    display: flex;
+    flex-direction: row;
+    justify-content: space-between;
+  }
+  .footer-trio section {
+    background: white;
+    width: calc(33.33% - 15px);
+    max-width: none;
+    padding: 30px;
+    box-sizing: border-box;
+    display: flex;
+    flex-direction: column;
+    justify-content: space-between;
+  }
+  .footer-trio h2 {
+    margin: 0px;
+  }
+  .footer-links {
+    text-align: right;
+  }
+  .footer-trio section a {
+    font-weight: 700;
+    text-decoration: none;
+    display: inline-block;
+    clear: both;
+    float: right;
+    margin-top: 15px;
+  }
+  .footer-trio section a:after {
+    content: '>';
+    padding-left: 8px;
+  }
+
+  .footer-duo {
+    width: 100%;
+    margin: 50px 0px;
+    display: flex;
+    flex-direction: row;
+    justify-content: space-between;
+  }
+  .footer-contact {
+    width: calc(33.33% - 15px);
+    max-width: none;
+    padding-left: 30px;
+    box-sizing: border-box;
+  }
+  .footer-contact dl {
+    width: 100%;
+    display: flex;
+    flex-flow: row;
+    flex-wrap: wrap;
+    overflow: visible;
+  }
+  .footer-contact dt {
+    font-weight: 700;
+    flex: 0 0 100px;
+  }
+  .footer-contact dd {
+    margin-left: auto;
+    text-align: left;
+    flex: 0 0 calc(100% - 100px);
+    display: block;
+    padding-bottom: 1em;
+  }
+  .footer-contact dd a {
+  }
+  .footer-contact dd address {
+    font-style: normal;
+  }
+
+  .footer-notes {
+    width: calc(66.67% - 7.5px);
+    max-width: none;
+    padding-left: 30px;
+    box-sizing: border-box;
+  }
+  .footer-note-cluster {
+    margin-top: 30px;
+  }
+  .footer-last-updated::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve' aria-hidden='true'%3e%3cpath fill-rule='evenodd' fill='black' d='M1.5 8a6.5 6.5 0 1113 0 6.5 6.5 0 01-13 0zM8 0a8 8 0 100 16A8 8 0 008 0zm.5 4.75a.75.75 0 00-1.5 0v3.5a.75.75 0 00.471.696l2.5 1a.75.75 0 00.557-1.392L8.5 7.742V4.75z'%3e%3c/path%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+  .footer-copyright::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve' aria-hidden='true'%3e%3cpath fill='black' d='M1.5,8c0-1.7,0.7-3.4,1.9-4.6C4.6,2.2,6.3,1.5,8,1.5s3.4,0.7,4.6,1.9c1.2,1.2,1.9,2.9,1.9,4.6s-0.7,3.4-1.9,4.6 S9.7,14.5,8,14.5s-3.4-0.7-4.6-1.9C2.2,11.4,1.5,9.7,1.5,8z M8,0C5.9,0,3.8,0.8,2.3,2.3C0.8,3.8,0,5.9,0,8c0,2.1,0.8,4.2,2.3,5.7 C3.8,15.2,5.9,16,8,16c2.1,0,4.2-0.8,5.7-2.3C15.2,12.2,16,10.1,16,8c0-2.1-0.8-4.2-2.3-5.7C12.2,0.8,10.1,0,8,0z'/%3e%3cpath fill='black' class='st0' d='M8,5.8c-1.2,0-2.2,1-2.2,2.2s1,2.2,2.2,2.2c0.6,0,1.1-0.2,1.5-0.6c0.3-0.3,0.8-0.3,1.1,0c0.3,0.3,0.3,0.8,0,1.1 c-0.7,0.6-1.6,1-2.6,1c-2.1,0-3.7-1.7-3.7-3.8c0-2.1,1.6-3.8,3.7-3.8c1,0,1.9,0.4,2.6,1c0.3,0.3,0.3,0.8,0,1.1 c-0.3,0.3-0.8,0.3-1.1,0C9.1,6,8.5,5.8,8,5.8z'/%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+  .footer-license::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve'  aria-hidden='true'%3e%3cpath fill-rule='evenodd' fill='black' d='M8.75.75a.75.75 0 00-1.5 0V2h-.984c-.305 0-.604.08-.869.23l-1.288.737A.25.25 0 013.984 3H1.75a.75.75 0 000 1.5h.428L.066 9.192a.75.75 0 00.154.838l.53-.53-.53.53v.001l.002.002.002.002.006.006.016.015.045.04a3.514 3.514 0 00.686.45A4.492 4.492 0 003 11c.88 0 1.556-.22 2.023-.454a3.515 3.515 0 00.686-.45l.045-.04.016-.015.006-.006.002-.002.001-.002L5.25 9.5l.53.53a.75.75 0 00.154-.838L3.822 4.5h.162c.305 0 .604-.08.869-.23l1.289-.737a.25.25 0 01.124-.033h.984V13h-2.5a.75.75 0 000 1.5h6.5a.75.75 0 000-1.5h-2.5V3.5h.984a.25.25 0 01.124.033l1.29.736c.264.152.563.231.868.231h.162l-2.112 4.692a.75.75 0 00.154.838l.53-.53-.53.53v.001l.002.002.002.002.006.006.016.015.045.04a3.517 3.517 0 00.686.45A4.492 4.492 0 0013 11c.88 0 1.556-.22 2.023-.454a3.512 3.512 0 00.686-.45l.045-.04.01-.01.006-.005.006-.006.002-.002.001-.002-.529-.531.53.53a.75.75 0 00.154-.838L13.823 4.5h.427a.75.75 0 000-1.5h-2.234a.25.25 0 01-.124-.033l-1.29-.736A1.75 1.75 0 009.735 2H8.75V.75zM1.695 9.227c.285.135.718.273 1.305.273s1.02-.138 1.305-.273L3 6.327l-1.305 2.9zm10 0c.285.135.718.273 1.305.273s1.02-.138 1.305-.273L13 6.327l-1.305 2.9z'%3e%3c/path%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+
+  #search-repository>button {
+    border-bottom-color: blue;
+  }
+
+  @media screen and (max-width: 1000px) {
+    .footer-contact dl {
+      flex-flow: column;
+    }
+    .footer-contact dt {
+      flex: 0 0 auto;
+    }
+    .footer-contact dd {
+      margin-left: 0;
+      flex: 0 0 auto;
+    }
+  }
+
+  @media screen and (max-width: 800px) {
+    .footer-trio {
+      flex-direction: column;
+    }
+    .footer-trio section {
+      width: 100%;
+      margin-bottom: 20px;
+    }
+    .footer-duo {
+      flex-direction: column;
+    }
+    .footer-duo section {
+      width: 100%;
+    }
+  }
+}
+@media print {
+  footer {
+    page-break-after: always;
+  }
+  #search-repository {
+    display: none;
+  }
+}
diff --git a/_site/assets/unlock.svg b/_site/assets/unlock.svg
new file mode 100644
index 00000000..6510b4d6
--- /dev/null
+++ b/_site/assets/unlock.svg
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>Unlock public code</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="white"/>
+<rect width="595" height="842" fill="#5B57CA"/>
+<rect x="268" y="405" width="200" height="150" fill="#FFF500"/>
+<rect x="128" y="315" width="200" height="150" fill="#FF776E"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M232.377 392.651C232.275 392.199 232.499 391.74 232.9 391.509C236.453 389.461 238.844 385.624 238.844 381.228C238.844 374.679 233.535 369.37 226.986 369.37C220.437 369.37 215.128 374.679 215.128 381.228C215.128 385.778 217.69 389.729 221.45 391.718C221.872 391.941 222.114 392.413 222.009 392.879L216.218 418.489C216.077 419.114 216.552 419.709 217.194 419.709H237.243C237.885 419.709 238.36 419.114 238.219 418.489L232.377 392.651Z" fill="black"/>
+<rect x="386" y="460" width="22" height="36" rx="11" stroke="#FF6666" stroke-width="7" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="337" y="493" width="12" height="6" fill="#D95047"/>
+<rect x="333" y="493" width="13" height="6" fill="#F55C5C"/>
+<rect x="337" y="481" width="12" height="6" fill="#D95047"/>
+<rect x="333" y="481" width="13" height="6" fill="#F55C5C"/>
+<rect x="339" y="487" width="13" height="6" fill="#D95047"/>
+<rect x="337" y="487" width="12" height="6" fill="#F55C5C"/>
+<line x1="383.5" y1="478.5" x2="331.5" y2="478.5" stroke="#FF6666" stroke-width="7" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="268" y="405" width="60" height="60" fill="#0000FF"/>
+<path d="M301 428.483H308.241C312.526 428.483 316 431.956 316 436.241V436.241C316 440.526 312.526 444 308.241 444H288.637C283.867 444 280 440.133 280 435.363V435.363C280 431.337 282.782 427.845 286.706 426.944L293 425.5" stroke="white" stroke-width="5"/>
+<path d="M297.5 418.875V411M302.375 420L307.625 414.75M292.625 420L287.375 414.75" stroke="#FFF500" stroke-width="3"/>
+<line x1="308" y1="435.5" x2="328" y2="435.5" stroke="white" stroke-width="5"/>
+<line x1="268" y1="435.5" x2="288" y2="435.5" stroke="white" stroke-width="5"/>
+</svg>
diff --git a/_site/criteria/advertise-maturity.html b/_site/criteria/advertise-maturity.html
new file mode 100644
index 00000000..4d97f928
--- /dev/null
+++ b/_site/criteria/advertise-maturity.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/document-maturity.html">
+  <script>location="/criteria/document-maturity.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/document-maturity.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/document-maturity.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/bundle-policy-and-code.html b/_site/criteria/bundle-policy-and-code.html
new file mode 100644
index 00000000..3172136b
--- /dev/null
+++ b/_site/criteria/bundle-policy-and-code.html
@@ -0,0 +1,562 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>政策與原始碼要合捆, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/bundle-policy-and-code.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/code-in-the-open.html"
+		     >&#8592; Code in the open</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/code-in-the-open.html"
+		     >&#8592; 原始碼要開放</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/reusable-and-portable-codebases.html"
+		     >Create reusable and portable code &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/reusable-and-portable-codebases.html"
+		     >程式碼要可重複使用且可攜 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/bundle-policy-and-code.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/bundle-policy-and-code.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="政策與原始碼要合捆">政策與原始碼要合捆</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須包含<a href="/glossary.html#code">原始碼</a>所根據的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>代碼庫必須包含根據政策而來的所有原始碼，用於偵測詐騙的原始碼則可除外。</li>
+  <li>政策應該採用機器可讀且明確的格式。</li>
+  <li><a href="/glossary.html#continuous-integration">持續整合</a>測試應該驗證原始碼與政策能一致執行。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼庫，則組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證代碼庫能反映合捆的政策。</li>
+  <li>確保成套合捆內容符合地方性技術基礎建設，或是特定公共組織的法律架構。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與公務人員確認程式碼根據的所有政策內容都有包含在內。</li>
+  <li>與公務人員確認根據政策而來的所有原始碼都有包含在內。</li>
+  <li>確認政策內容是否能在機器上解讀。</li>
+  <li>確認原始碼與政策間的執行一致性能通過持續整合測試。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>提供相關政策內文，以便收錄於<a href="/glossary.html#repository">儲存庫</a>中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。</li>
+  <li>請提供政策相關參考資料與連結。</li>
+  <li>政策內容請使用明確且機器可讀的格式，像是<a href="https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation">業務流程模型與標記法</a>、
+<a href="https://en.wikipedia.org/wiki/Decision_Model_and_Notation">決策模型與標記法</a>，以及
+<a href="https://en.wikipedia.org/wiki/CMMN">案例管理模型標記法</a>。</li>
+  <li>追蹤政策時，請使用與追蹤原始碼<a href="/criteria/version-control-and-history.html">相同的版本控制</a>與文件。</li>
+  <li>定期檢查代碼庫中非政策程式碼的變動，以及確認是否仍符合<a href="/criteria/document-objectives.html">政策意圖</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。</li>
+  <li>確保政策制定者、開發人員與設計師朝相同目標努力。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。</li>
+  <li>與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>針對如何讓政策文字更清楚提供意見。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Camunda <a href="https://bpmn.io/">於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN 等模型與表記法圖表</a>的免費線上工具。</li>
+  <li>Trisotech 提供的 <a href="https://www.bpmnquickguide.com/view-bpmn-quick-guide/">BPMN 快速指南</a>。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/code-in-the-open.html b/_site/criteria/code-in-the-open.html
new file mode 100644
index 00000000..e73ae1ca
--- /dev/null
+++ b/_site/criteria/code-in-the-open.html
@@ -0,0 +1,558 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>原始碼要開放, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/code-in-the-open.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/bundle-policy-and-code.html"
+		     >Bundle policy and source code &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/bundle-policy-and-code.html"
+		     >政策與原始碼要合捆 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/code-in-the-open.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/code-in-the-open.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="原始碼要開放">原始碼要開放</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>任何使用中的<a href="/glossary.html#policy">政策</a>所有<a href="/glossary.html#code">原始碼</a>都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到<a href="/glossary.html#repository">儲存庫</a>中。</li>
+  <li>目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。</li>
+  <li>可選擇是否要以文件記錄<a href="/glossary.html#general-public">一般大眾</a>與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>以開放精神編寫原始碼能：</p>
+
+<ul>
+  <li>改善資訊透明</li>
+  <li>提高程式碼品質</li>
+  <li>促進稽核流程</li>
+</ul>
+
+<p>這些面向讓公民更有機會能瞭解，軟體與政策如何影響他們與公共組織的互動。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓原始碼或政策可以重複使用。</li>
+  <li>讓盡可能越多人能讀懂<a href="/glossary.html#codebase">代碼庫</a>以及當中的程式碼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織之外，查看這些原始碼。</li>
+  <li>確認代碼庫檔案與提交歷史紀錄不包含敏感性資訊。</li>
+  <li>檢查目前非使用中的原始碼是否有公開。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定合乎開放精神的政策。</li>
+  <li>以公開透明的政策為優先。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>孕育擁抱開放、重視學習、歡迎意見回饋的文化。</li>
+  <li>與外部供應商和自由工作者以開放精神的方式協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。</li>
+  <li>為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">以開放精神編寫原始碼</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed">程式碼應該開放或封閉的時機</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open">以開放精神編寫原始碼的資安考量</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/deploying-software-regularly">定期部署軟體</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">政府數位服務團如何使用 GitHub</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/continuous-integration.html b/_site/criteria/continuous-integration.html
new file mode 100644
index 00000000..e975e789
--- /dev/null
+++ b/_site/criteria/continuous-integration.html
@@ -0,0 +1,586 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>使用持續整合, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/continuous-integration.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/open-standards.html"
+		     >&#8592; Use open standards</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/open-standards.html"
+		     >&#8592; 採用開放標準</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/open-licenses.html"
+		     >Publish with an open license &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/open-licenses.html"
+		     >發行採用開放授權 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/continuous-integration.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/continuous-integration.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="使用持續整合">使用持續整合</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#code">原始碼</a>中的所有功能都必須有自動化測試。</li>
+  <li>所有貢獻內容都必須先通過自動化測試，才能上傳至<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>代碼庫必須有說明貢獻內容結構的相關準則。</li>
+  <li>代碼庫必須有活躍貢獻者。</li>
+  <li>代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。</li>
+  <li>應該監督原始碼測試與文件的涵蓋範圍。</li>
+  <li>可選擇是否測試<a href="/glossary.html#policy">政策</a>和文件，與原始碼間有無一致性，或是反之亦然。</li>
+  <li>可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>使用<a href="/glossary.html#continuous-integration">持續整合</a>：
+    <ul>
+      <li>可以讓您快速找出代碼庫的問題所在，</li>
+      <li>能在降低貢獻者面臨壓力的同時，允許承擔風險並且專注在解決問題上，</li>
+      <li>可降低新貢獻者對整體內容理解的門檻，讓他們更容易提出修改，</li>
+      <li>讓程式碼更容易維護，</li>
+      <li>能加速開發週期。</li>
+    </ul>
+  </li>
+  <li>修改內容較少、時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大、累積很久才一次提出的變更。</li>
+  <li>活躍開發中的代碼庫較能提供協作與意見回饋的機會。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>建立能夠順暢作業、可擴展，且能容錯的基礎架構。</li>
+  <li>建立有意義的測試。</li>
+  <li>測試實際會發生的情境。</li>
+  <li>保證交付的程式碼與政策期望的成果確實相同。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有測試可用。</li>
+  <li>確認程式碼覆蓋率工具能檢查到 100% 的程式碼。</li>
+  <li>確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。</li>
+  <li>確認有貢獻準則說明貢獻內容的結構。</li>
+  <li>確認最近三個月內有貢獻內容上傳。</li>
+  <li>檢查程式碼覆蓋率數據是否有公布。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。</li>
+  <li>確保政策文件也有設好自動化測試。</li>
+  <li>如果政策文件未能通過測試，請立即修正。</li>
+  <li>確保程式碼能反映出政策的任何變動（請參閱<a href="/criteria/version-control-and-history.html">維護版本控制</a>）。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保能儘快且經常給真正的終端使用者進行測試。</li>
+  <li>以頻繁交付少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。</li>
+  <li>聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。</li>
+  <li>發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次交付。</li>
+  <li>協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。</li>
+  <li>協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。</li>
+  <li>編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。</li>
+  <li>調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。</li>
+  <li>經常部署。</li>
+  <li>至少每天整合工作內容一次。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Martin Fowler《<a href="https://www.martinfowler.com/articles/continuousIntegration.html">什麼是持續整合</a>》。</li>
+  <li>Jez Humble《<a href="https://www.continuousdelivery.com/">什麼是持續交付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/standards/continuous-delivery.html">使用持續交付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly">品質保證：定期測試您的服務</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/document-maturity.html b/_site/criteria/document-maturity.html
new file mode 100644
index 00000000..17e4624a
--- /dev/null
+++ b/_site/criteria/document-maturity.html
@@ -0,0 +1,559 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>紀錄代碼庫成熟度, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/document-maturity.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/style.html"
+		     >&#8592; Use a coherent style</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/style.html"
+		     >&#8592; 風格要前後一致</a></span>
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/document-maturity.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/document-maturity.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="紀錄代碼庫成熟度">紀錄代碼庫成熟度</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須註明版本編號。</li>
+  <li>準備好可供使用的代碼庫，必須只能依賴其他也已經準備好可供使用的代碼庫。</li>
+  <li>尚未準備好使用的代碼庫，必須有所列標籤之一：prototype、alpha、beta、pre-release 等版本進度。</li>
+  <li>代碼庫應該包含每次版本的變動紀錄，像是以「<code class="language-plaintext highlighter-rouge">CHANGELOG</code>」日誌格式檔記錄。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>清楚標示代碼庫的成熟度，有助於他人決定是否要重複使用、投資，或為該代碼庫做出貢獻。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證他人會來使用<a href="/glossary.html#code">程式碼</a>。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫有版本編號策略，且有文件記載該策略。</li>
+  <li>確認有清楚表明最新版的取得位置。</li>
+  <li>確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。</li>
+  <li>確認代碼庫是已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-release 等開發中版本。</li>
+  <li>檢查是否有變更紀錄。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定<a href="/glossary.html#policy">政策</a>時，請記住任何開發出來的程式碼都必須先經過測試與改善，才能夠投入服務。</li>
+  <li>考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫，公測版服務不要使用 prototype
+原型代碼庫。</li>
+  <li>若代碼庫尚未準備好供一般使用，請與開發人員一起確保該代碼庫是否有標示適當標籤：
+    <ul>
+      <li>prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術的可行性概念，</li>
+      <li>alpha：內部測試，在限制的一群使用者中進行引導性測試，</li>
+      <li>beta：公開測試，讓更多<a href="/glossary.html#general-public">一般大眾</a>參與測試，例如測試代碼庫在大規模操作下是否仍能運作，</li>
+      <li>pre-release：準發行版，已經準備好發行，但尚未獲得正式批准的程式碼。</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>在每個指示程式碼成熟度的介面中加上明顯的標頭。</li>
+  <li>所有正式發行的程式碼都要有版本編號。</li>
+  <li>特別是在採用「滾動發行」的情況下，程式碼的版本資訊可以根據<a href="/glossary.html#version-control">版本控制</a>系統的中介資料自動衍生（例如使用
+<a href="https://git-scm.com/docs/git-describe">git describe</a>）。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>澳洲數位轉型局《<a href="https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process">服務設計與交付流程</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/agile-delivery">敏捷交付服務手冊</a>》。</li>
+  <li>許多代碼庫使用「<a href="https://semver.org/">語意化版本控制規範</a>」來標示版本。</li>
+  <li>英國政府數位服務團《<a href="https://www.youtube.com/watch?v=_cyI7DMhgYc">什麼是服務開發當中的探索、Alpha、Beta、上線階段？ [影片 0’0”59]</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/document-objectives.html b/_site/criteria/document-objectives.html
new file mode 100644
index 00000000..e15cbafe
--- /dev/null
+++ b/_site/criteria/document-objectives.html
@@ -0,0 +1,556 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>代碼庫有目標文件, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/document-objectives.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/require-review.html"
+		     >&#8592; Require review of contributions</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/require-review.html"
+		     >&#8592; 要求審查貢獻內容</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/documenting.html"
+		     >Document the code &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/documenting.html"
+		     >程式碼有文件 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/document-objectives.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/document-objectives.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="代碼庫有目標文件">代碼庫有目標文件</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。</li>
+  <li>代碼庫文件應該清楚描述<a href="/glossary.html#policy">政策</a>目標與代碼庫目標之前的關聯。</li>
+  <li>可選擇是否以文件記錄給<a href="/glossary.html#general-public">一般民眾</a>看的代碼庫目標。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>以文件記錄代碼庫目標：</p>
+
+<ul>
+  <li>提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。</li>
+  <li>幫助劃定您自己開發專案的範圍。</li>
+  <li>將代碼庫以及所包含模組的目的用途，清楚告知其他利害關係人與貢獻者。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證代碼庫能達成其陳述的目標。</li>
+  <li>保證會有人為代碼庫做出貢獻。</li>
+  <li>預防其他代碼庫試圖達成相同目標。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫文件有包含代碼庫目標，或主旨、使命等。</li>
+  <li>查看政策目標與代碼庫目標之間關聯的描述。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>將政策目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>納入會影響社會群體、代碼庫與開發目標的相關政策，例如可近用無障礙環境，或機會平等等價值或倫理取向的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將單位目標、組織目標或業務目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將技術與設計目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Marek Hajduczenia《<a href="http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf">如何撰寫專案目標</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/documenting.html b/_site/criteria/documenting.html
new file mode 100644
index 00000000..2b8d8257
--- /dev/null
+++ b/_site/criteria/documenting.html
@@ -0,0 +1,568 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式碼有文件, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/documenting.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/document-objectives.html"
+		     >&#8592; Document codebase objectives</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/document-objectives.html"
+		     >&#8592; 代碼庫有目標文件</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/understandable-english-first.html"
+		     >Use plain English &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/understandable-english-first.html"
+		     >使用白話的英語 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/documenting.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/documenting.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式碼有文件">程式碼有文件</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>的所有功能、<a href="/glossary.html#policy">政策</a>及原始碼，都必須以可清楚瞭解的用語描述，讓懂
+<a href="/glossary.html#code">程式碼</a>目的用途的人也能夠理解。</li>
+  <li>代碼庫文件必須說明如何安裝與執行原始碼。</li>
+  <li>代碼庫文件必須為關鍵功能舉出範例。</li>
+  <li>代碼庫文件應該包含精要的說明，讓<a href="/glossary.html#general-public">一般民眾</a>和記者等廣泛的利害關係人都能清楚明白。</li>
+  <li>代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。</li>
+  <li>代碼庫文件應該包含所有功能的範例。</li>
+  <li>程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。</li>
+  <li>應該要有針對文件品質的<a href="/glossary.html#continuous-integration">持續整合</a>測試。</li>
+  <li>可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。</li>
+  <li>可選擇是否以文件中的範例來測試程式碼。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>使用者可以更快速上手代碼庫的使用並做出貢獻。</li>
+  <li>能幫助他人找到這個代碼庫，特別是那些在問「是不是已經有提供某某功能的程式碼」的人。</li>
+  <li>讓貴組織單位與其流程資訊更透明。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>直接貢獻出更可重複使用，以及更具可攜性的程式碼（請參閱<a href="/criteria/reusable-and-portable-codebases.html">編寫可重複使用且具可攜性的程式碼</a>）。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。</li>
+  <li>確認文件有說明如何安裝與執行原始碼。</li>
+  <li>確認文件有包含主要功能的範例。</li>
+  <li>向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。</li>
+  <li>檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。</li>
+  <li>檢查文件中列舉的所有功能都包含範例。</li>
+  <li>檢查文件中是否包含高層架構圖，或類似的組件關係圖表。</li>
+  <li>確認整合測試有包含到程式碼文件品質，例如確認由程式碼生成的文件，並檢查連結與圖片等。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>定期查看代碼庫的非政策程式碼的變動情況。</li>
+  <li>針對如何讓非政策文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>嘗試使用代碼庫。</li>
+  <li>確保您同時瞭解政策、原始碼以及文件內容。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>定期查看代碼庫中非原始碼部分的變動情況。</li>
+  <li>針對如何讓非原始碼文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Write the Docs《<a href="https://www.writethedocs.org/guide/">文件指南</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/findability.html b/_site/criteria/findability.html
new file mode 100644
index 00000000..27d24a5c
--- /dev/null
+++ b/_site/criteria/findability.html
@@ -0,0 +1,574 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>代碼庫可查詢得到, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/findability.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/open-licenses.html"
+		     >&#8592; Publish with an open license</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/open-licenses.html"
+		     >&#8592; 發行採用開放授權</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/style.html"
+		     >Use a coherent style &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/style.html"
+		     >風格要前後一致 &#8594;</a></span>
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/findability.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/findability.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="代碼庫可查詢得到">代碼庫可查詢得到</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，必須能搜尋得到<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>在搜尋引擎查找代碼庫名稱時，必須能搜尋得到代碼庫。</li>
+  <li>維護人員應該將代碼庫提交至相關的軟體目錄上。</li>
+  <li>代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。</li>
+  <li>代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、<a href="/glossary.html#repository">儲存庫</a>、位置、網站等。</li>
+  <li>代碼庫應該包含機器可讀的中介資料說明，例如採用 <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a>
+格式的檔案。</li>
+  <li>可選擇是否為代碼庫設定專用的網域名稱。</li>
+  <li>可選擇是否在社群舉辦的會議中定期進行簡報。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>必須主動積極；不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫。</li>
+  <li>有中介資料說明檔案會讓代碼庫更容易被發現。</li>
+  <li>一旦代碼庫越容易被發現，更多的潛在協作者也就找得到它。</li>
+  <li>撰寫出良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF
+自由軟體基金會的軟體目錄列表之中，使代碼庫成為語意網路中的一部份。如此一來，他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>確認新的協作人員或複製者。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認以白話英語敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>檢查代碼庫有刊登在相關軟體型錄上。</li>
+  <li>檢查代碼庫的網站有描述代碼庫能夠解決的問題。</li>
+  <li>檢查永久唯一識別碼條目有提及主要貢獻者。</li>
+  <li>檢查永久唯一識別碼條目中有包含儲存庫位置。</li>
+  <li>檢查永久唯一識別碼條目有列出代碼庫網站。</li>
+  <li>檢查中介資料說明檔案是機器可讀的格式。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。</li>
+  <li>請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。</li>
+  <li>在相關會議上作簡報介紹代碼庫如何執行<a href="/glossary.html#policy">政策</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。</li>
+  <li>確保專案參與人員出席相關會議或作簡報介紹。</li>
+  <li>在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>搜尋引擎最佳化。</li>
+  <li>請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。</li>
+  <li>推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Wikidata 維基數據社群《<a href="https://www.wikidata.org/wiki/Wikidata:Introduction">維基數據簡介</a>》。</li>
+  <li>FSF 自由軟體基金會《<a href="https://directory.fsf.org/wiki/Main_Page">FSF 軟體目錄列表</a>》。</li>
+  <li>GO FAIR 國際支援與合作辦公室所撰寫的《<a href="https://www.go-fair.org/fair-principles/">FAIR科學資料管理與盡職治理指導原則</a>》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/index.html b/_site/criteria/index.html
new file mode 100644
index 00000000..d72ad98b
--- /dev/null
+++ b/_site/criteria/index.html
@@ -0,0 +1,342 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>準則, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/index.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/index.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="準則">準則</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<ol>
+  <li>
+    <p><a href="/criteria/code-in-the-open.html">原始碼要開放</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/bundle-policy-and-code.html">政策與原始碼要合捆</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/reusable-and-portable-codebases.html">程式碼要可重複使用且可攜</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-to-contributions.html">歡迎貢獻者</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/make-contributing-easy.html">貢獻要容易</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/version-control-and-history.html">維護版本控制</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/require-review.html">要求審查貢獻內容</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-objectives.html">代碼庫有目標文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/documenting.html">程式碼有文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/understandable-english-first.html">使用白話的英語</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-standards.html">採用開放標準</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/continuous-integration.html">使用持續整合</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-licenses.html">發行採用開放授權</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/findability.html">代碼庫可查詢得到</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/style.html">風格要前後一致</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-maturity.html">紀錄代碼庫成熟度</a></p>
+  </li>
+</ol>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/index.md b/_site/criteria/index.md
new file mode 100644
index 00000000..7891057e
--- /dev/null
+++ b/_site/criteria/index.md
@@ -0,0 +1,11 @@
+# 準則
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+{% assign sorted = site.pages | sort:"order" %}
+
+{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name !=
+"index.md" %}{% if page.title %}
+
+1. [{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}
diff --git a/_site/criteria/make-contributing-easy.html b/_site/criteria/make-contributing-easy.html
new file mode 100644
index 00000000..692c0214
--- /dev/null
+++ b/_site/criteria/make-contributing-easy.html
@@ -0,0 +1,558 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>貢獻要容易, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/make-contributing-easy.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/open-to-contributions.html"
+		     >&#8592; Welcome contributors</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/open-to-contributions.html"
+		     >&#8592; 歡迎貢獻者</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/version-control-and-history.html"
+		     >Maintain version control &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/version-control-and-history.html"
+		     >維護版本控制 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/make-contributing-easy.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/make-contributing-easy.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="貢獻要容易">貢獻要容易</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須有個可以公開接受任何人建議的議題追蹤器。</li>
+  <li>代碼庫必須說明，如何私下回報安全性問題來達成負責任的揭露。</li>
+  <li>文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「<code class="language-plaintext highlighter-rouge">README</code>」檔案中。</li>
+  <li>代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵遞論壇）。</li>
+  <li>文件應該說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓使用者能夠為共享的代碼庫修復問題與新增功能，能讓軟體變得更好、更可靠、功能更豐富。</li>
+  <li>讓人們能以協作方式採用共享的數位基礎建設。</li>
+  <li>幫助使用者在代碼庫間做出選擇。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證其他人會重複使用代碼庫。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有公開的議題追蹤器。</li>
+  <li>確認有說明如何私下通報安全性問題。</li>
+  <li>確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。</li>
+  <li>確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>追蹤代碼庫中的<a href="/glossary.html#policy">政策</a>問題，讓相關的外部政策專家如果自願也能夠協助。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Joel Hans《<a href="https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf">如何引發他人為您的開放原始碼專案做出優秀貢獻</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">以開放精神編寫原始碼的好處</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/open-licenses.html b/_site/criteria/open-licenses.html
new file mode 100644
index 00000000..b89394f0
--- /dev/null
+++ b/_site/criteria/open-licenses.html
@@ -0,0 +1,562 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>發行採用開放授權, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/open-licenses.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/continuous-integration.html"
+		     >&#8592; Use continuous integration</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/continuous-integration.html"
+		     >&#8592; 使用持續整合</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/findability.html"
+		     >Make the codebase findable &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/findability.html"
+		     >代碼庫可查詢得到 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/open-licenses.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/open-licenses.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="發行採用開放授權">發行採用開放授權</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>所有<a href="/glossary.html#code">程式碼</a>與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。</li>
+  <li>軟體原始碼必須採用<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款</a>。</li>
+  <li>所有程式碼皆必須搭配授權條款檔案一併發行。</li>
+  <li>不得要求貢獻者將其貢獻的程式碼著作權轉讓給<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。</li>
+  <li>可選擇是否為不同類型的程式碼與文件採用多重授權條款。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓任何人都可以查看程式碼，並知道他們可以與該如何重複利用這些程式碼。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>預防任何特定行為人使用程式碼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫有清楚給予授權條款。</li>
+  <li>確認原始碼的授權條款有列於<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清單</a>，以及文件的授權條款有
+<a href="https://opendefinition.org/licenses/">符合「開放定義」</a>。</li>
+  <li>確認代碼庫中有包含其採用的授權條款檔案。</li>
+  <li>確認貢獻指南中，以及<a href="/glossary.html#repository">儲存庫</a>的組態設定中，沒有求貢獻者轉讓著作權。</li>
+  <li>在代碼庫<a href="/glossary.html#continuous-integration">持續整合</a>測試中，確認是否有檢查授權內容為機器可讀的檢查項目。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定要求程式碼必須採用<a href="/glossary.html#open-source">開放原始碼</a>授權的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>只與能採用開放原始碼授權交付與發行其程式碼的開放原始碼軟體供應商合作。</li>
+  <li>請注意，雖然<a href="https://creativecommons.org/licenses/">創用CC授權</a>適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>每當建立新的代碼庫時，都要加入新的「<code class="language-plaintext highlighter-rouge">license</code>」授權條款檔案。</li>
+  <li>每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼促進會所發表的《<a href="https://opensource.org/osd">開放原始碼定義</a>》，所有開放原始碼授權條款皆符合這套定義。</li>
+  <li>紐西蘭CC Aotearoa《<a href="https://creativecommons.org/about/videos/creative-commons-kiwi">創用CC介紹動畫影片</a>》。</li>
+  <li>歐洲自由軟體基金會所發表的《<a href="https://reuse.software/spec/">REUSE 倡議規範</a>》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。</li>
+  <li>Linux 基金會所發表的 <a href="https://spdx.org/licenses/">SPDX 授權條款清單</a>提供經標準化、且機器可讀的大多數授權條款縮寫表示法。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/open-standards.html b/_site/criteria/open-standards.html
new file mode 100644
index 00000000..c59735da
--- /dev/null
+++ b/_site/criteria/open-standards.html
@@ -0,0 +1,559 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>採用開放標準, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/open-standards.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/understandable-english-first.html"
+		     >&#8592; Use plain English</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/understandable-english-first.html"
+		     >&#8592; 使用白話的英語</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/continuous-integration.html"
+		     >Use continuous integration &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/continuous-integration.html"
+		     >使用持續整合 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/open-standards.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/open-standards.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="採用開放標準">採用開放標準</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>如要達成促進資料交換的特性，就必須採用符合<a href="https://opensource.org/osr">開放原始碼促進會其開放標準需求規範</a>的
+<a href="/glossary.html#open-standard">開放標準</a>。</li>
+  <li>如果有使用到任何的非開放標準，則必須在文件中清楚記錄。</li>
+  <li>代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。</li>
+  <li>代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。</li>
+  <li>如果還沒有已存在的開放標準可採用，則應該投入開發新標準。</li>
+  <li>採用標準時，應該優先選擇可經機器測試的標準。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>為不同的系統之間建立互通性。</li>
+  <li>降低廠商套牢的可能性。</li>
+  <li>保證可以取得重複利用與貢獻代碼庫所需的知識。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓軟體的操作方法變得可以瞭解。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。</li>
+  <li>確認若有採用任何的非開放標準，皆有清楚記錄在文件中。</li>
+  <li>確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>以政策要求盡可能在任何情況下使用開放標準。</li>
+  <li>禁止採購不採用開放標準的技術科技。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>考慮在<a href="/glossary.html#code">程式碼</a>審查中納入開放標準依循評估。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將是否依循標準加入<a href="/glossary.html#continuous-integration">持續整合</a>測試中。</li>
+  <li>審查提交紀錄與其他<a href="/glossary.html#repository">儲存庫</a>資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國內閣辦公室發表的《<a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">開放標準原則</a>》
+<a href="/glossary.html#policy">政策</a>報告。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/open-to-contributions.html b/_site/criteria/open-to-contributions.html
new file mode 100644
index 00000000..f60f4736
--- /dev/null
+++ b/_site/criteria/open-to-contributions.html
@@ -0,0 +1,569 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>歡迎貢獻者, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/open-to-contributions.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/reusable-and-portable-codebases.html"
+		     >&#8592; Create reusable and portable code</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/reusable-and-portable-codebases.html"
+		     >&#8592; 程式碼要可重複使用且可攜</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/make-contributing-easy.html"
+		     >Make contributing easy &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/make-contributing-easy.html"
+		     >貢獻要容易 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/open-to-contributions.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/open-to-contributions.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="歡迎貢獻者">歡迎貢獻者</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須允許任何人針對代碼庫提出修改建議。</li>
+  <li>代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」檔案說明。</li>
+  <li>代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「<code class="language-plaintext highlighter-rouge">GOVERNANCE</code>」檔案來說明。</li>
+  <li>代碼庫應該宣布投入其開發與維護工作的參與組織單位。</li>
+  <li>代碼庫應該要有可公開取得的發展路線圖。</li>
+  <li>代碼庫應該公布代碼庫的活動統計數據。</li>
+  <li>可選擇是否為代碼庫加入貢獻者的行為準則。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>幫助新參與者瞭解並且信任代碼庫社群的領導。</li>
+  <li>避免參與者因為無法影響代碼庫的目標與進展，而造成代碼庫社群分裂成分歧的社群。</li>
+  <li>幫助使用者在代碼庫間做出選擇。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證他人會參與社群。</li>
+  <li>保證其他人會重複使用代碼庫。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認可以提交修改建議給代碼庫。</li>
+  <li>確認代碼庫有貢獻指引。</li>
+  <li>確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。</li>
+  <li>檢查是否有參與的組織單位名單。</li>
+  <li>檢查是否有發展路線圖。</li>
+  <li>檢查是否有公布活動統計數據。</li>
+  <li>檢查是否有行為準則。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為代碼庫加入其他資源的清單，而這些資源可幫助<a href="/glossary.html#policy">政策</a>專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。</li>
+  <li>考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。</li>
+  <li>如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。</li>
+  <li>確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼指南所提供的《<a href="https://opensource.guide/building-community/">營造友善的社群</a>》。</li>
+  <li>Mike McQuaid《<a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/">開放原始碼貢獻者瓶頸</a>》。</li>
+  <li>開放原始碼指南為成長中的<a href="/glossary.html#open-source">開放原始碼</a>社群專案所寫的《<a href="https://opensource.guide/leadership-and-governance/">領導與治理</a>》。</li>
+  <li>Pieter Hintjens《<a href="http://hintjens.com/blog:117">打造網路社群</a>》(長篇文章！)。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/require-review.html b/_site/criteria/require-review.html
new file mode 100644
index 00000000..51b4a1f2
--- /dev/null
+++ b/_site/criteria/require-review.html
@@ -0,0 +1,580 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>要求審查貢獻內容, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/require-review.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/version-control-and-history.html"
+		     >&#8592; Maintain version control</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/version-control-and-history.html"
+		     >&#8592; 維護版本控制</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/document-objectives.html"
+		     >Document codebase objectives &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/document-objectives.html"
+		     >代碼庫有目標文件 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/require-review.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/require-review.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="要求審查貢獻內容">要求審查貢獻內容</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>所有被接受或是提交給<a href="/glossary.html#codebase">代碼庫</a>正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。</li>
+  <li>審查必須包含原始碼、<a href="/glossary.html#policy">政策</a>、測試、文件等。</li>
+  <li>如果不接受貢獻內容，審查人員必須提供意見回饋。</li>
+  <li>貢獻內容應該遵循代碼庫的標準、架構、決策安排等，以通過審查。</li>
+  <li>審查內容應該包含執行<a href="/glossary.html#code">程式碼</a>與執行代碼庫測試。</li>
+  <li>貢獻內容應該由與貢獻者不同背景情境的人來審查。</li>
+  <li>版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。</li>
+  <li>審查應該在兩個工作天內進行。</li>
+  <li>可選擇是否由多位審查人員進行審查。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>提升代碼庫品質。</li>
+  <li>降低安全性風險與營運風險。</li>
+  <li>打造每份貢獻內容皆能有品質的文化。</li>
+  <li>揪出可能發生的極明顯錯誤。</li>
+  <li>只有真正能為代碼庫提升價值的貢獻內容才會被接受，可以給予貢獻者安全感。</li>
+  <li>向貢獻者保證在一段時間內提供意見回饋或是合作改善。</li>
+  <li>快速審查能提高貢獻者交付貢獻內容的頻率以及參與熱度。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證能找到問題的合適解決方案。</li>
+  <li>代表審查人員必須承擔責任。</li>
+  <li>貢獻者能從編寫文件與測試中免除責任。</li>
+  <li>提供您合適的審查人選。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。</li>
+  <li>確認審查內容包含原始碼、政策、測試、文件等。</li>
+  <li>針對未被採用的貢獻內容，確認有適當解釋原因。</li>
+  <li>檢查審查範圍有涵蓋是否遵循標準、架構、代碼庫指引等。</li>
+  <li>檢查審查人員在審查時是否有執行程式碼與測試。</li>
+  <li>與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。</li>
+  <li>檢查<a href="/glossary.html#version-control">版本控制</a>系統中是否有採用分支保護。</li>
+  <li>檢查貢獻提交與審查之間的時間間隔。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。</li>
+  <li>採用具有審查與意見回饋功能的版本控制系統或作業流程。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將交付妥善程式碼作為共同目標。</li>
+  <li>確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。</li>
+  <li>創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。</li>
+  <li>確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。</li>
+  <li>當他人請求您審查程式碼時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content">英國政府數位服務團程式碼審查程序</a>》。</li>
+  <li><a href="https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches">GitHub</a>
+與 <a href="https://about.gitlab.com/2014/11/26/keeping-your-code-protected/">GitLab</a>
+平臺的分支保護說明。</li>
+  <li>Sage Sharp《<a href="https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/">程式修補審查的和善藝術</a>》。</li>
+  <li>Mozilla《<a href="https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177">參與度評測成果</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/reusable-and-portable-codebases.html b/_site/criteria/reusable-and-portable-codebases.html
new file mode 100644
index 00000000..94acdda2
--- /dev/null
+++ b/_site/criteria/reusable-and-portable-codebases.html
@@ -0,0 +1,580 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式碼要可重複使用且可攜, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/reusable-and-portable-codebases.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/bundle-policy-and-code.html"
+		     >&#8592; Bundle policy and source code</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/bundle-policy-and-code.html"
+		     >&#8592; 政策與原始碼要合捆</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/open-to-contributions.html"
+		     >Welcome contributors &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/open-to-contributions.html"
+		     >歡迎貢獻者 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/reusable-and-portable-codebases.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/reusable-and-portable-codebases.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式碼要可重複使用且可攜">程式碼要可重複使用且可攜</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須開發成能在<a href="/glossary.html#different-contexts">不同情境</a>中重複使用。</li>
+  <li>執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的<a href="/glossary.html#code">程式碼</a>或服務。</li>
+  <li>代碼庫應該有多方單位使用。</li>
+  <li>發展路線圖應該有多方單位的需求影響。</li>
+  <li>應該使用組態設定方式以將程式碼調整成能適應各情境的特定需求。</li>
+  <li>代碼庫應該能夠在地化。</li>
+  <li>程式碼與其文件不應該包含特定情況專用的資訊。</li>
+  <li>代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓其他政策制定者、開發人員與設計師等，能夠重複利用您所開發的內容，以及測試它、改善它，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。</li>
+  <li>讓新進人員能更容易瞭解程式碼（因為用途更廣泛通用）。</li>
+  <li>由於代碼庫以重複利用為前提籌劃設計，因此要調控代碼庫的目標使命、願景與範圍等也更容易。</li>
+  <li>多方使用的代碼庫更可以從能自我運作的社群中獲益。</li>
+  <li>任何貢獻者都能測試與貢獻給代碼庫，不需要仰賴任何其他貢獻者或部署底下的特定情況專用基礎架構。</li>
+  <li>以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。</li>
+  <li>以文件清楚記錄用途的模組，更容易在另一種情境中重複利用。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓他人重複利用代碼庫。</li>
+  <li>建立社群。</li>
+  <li>將文件、支援、修正錯誤⋯⋯等責任轉移給其他單位。</li>
+  <li>保證模組在任何情境下都足以通用。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與另一組織單位角色與您相似的人確認，看他們是否能重複利用代碼庫，以及需要怎麼進行。</li>
+  <li>確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。</li>
+  <li>檢查是否有多方單位或是有在多種情境下正使用代碼庫。</li>
+  <li>檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為您的<a href="/glossary.html#policy">政策</a>撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。</li>
+  <li>確保代碼庫有將貴組織單位列為已知用戶。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>原始碼應該設計成：</p>
+
+<ul>
+  <li>能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，</li>
+  <li>能解決通用性質問題，而非特定問題，</li>
+  <li>以邏輯上具有意義且獨立的模組構成，</li>
+  <li>如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。</li>
+</ul>
+
+<p>確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行開發、使用、測試、部署等。</p>
+
+<p>在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable">讓原始碼開放且可重複利用</a>》。</li>
+  <li>OpenAPI 促進會定義的《<a href="https://spec.openapis.org/oas/latest.html">OpenAPI 規範</a>》，為人機可讀的
+HTTP API 標準，不受程式語言種類限制的介面描述。</li>
+  <li>W3C 全球資訊網協會《<a href="https://www.w3.org/International/questions/qa-i18n">在地化與國際化</a>》。</li>
+  <li>全球資訊網協會《<a href="https://www.w3.org/International/techniques/authoring-html">國際化技巧：編寫 HTML 與 CSS</a>》。</li>
+  <li>GNU 作業系統的 <a href="https://www.gnu.org/software/gettext/gettext.html">GNU gettext</a>。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/style.html b/_site/criteria/style.html
new file mode 100644
index 00000000..5a40748d
--- /dev/null
+++ b/_site/criteria/style.html
@@ -0,0 +1,560 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>風格要前後一致, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/style.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/findability.html"
+		     >&#8592; Make the codebase findable</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/findability.html"
+		     >&#8592; 代碼庫可查詢得到</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/document-maturity.html"
+		     >Document codebase maturity &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/document-maturity.html"
+		     >紀錄代碼庫成熟度 &#8594;</a></span>
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/style.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/style.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="風格要前後一致">風格要前後一致</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是<a href="/glossary.html#codebase">代碼庫</a>社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既有風格。</li>
+  <li>貢獻內容應該通過自動化的風格測試。</li>
+  <li>代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。</li>
+  <li>可選擇是否將<a href="/criteria/understandable-english-first.html">可理解的白話英語</a>小節加入風格指南之中。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓不同環境的貢獻者可以在統合的產品上合作。</li>
+  <li>用詞統一能減少貢獻者之間在溝通上的摩擦。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>幫助貢獻者寫好程式碼，或者精確說明他們在做什麼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認貢獻內容有遵循文件中指定的風格指南。</li>
+  <li>檢查是否有自動化的風格測試。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為<a href="/glossary.html#policy">政策</a>與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「
+<code class="language-plaintext highlighter-rouge">README</code>」檔案。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在<a href="/glossary.html#repository">儲存庫</a>中加入相關文件，像是「
+<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「<code class="language-plaintext highlighter-rouge">README</code>」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查的其他層面。指南應該包含貢獻的
+<a href="/glossary.html#code">程式碼</a>預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。</p>
+
+<p>此外：</p>
+
+<ul>
+  <li>使用程式碼品質分析工具 (linter)。</li>
+  <li>在代碼庫中加入程式碼品質分析工具的組態設定。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Hugo Martins《<a href="https://github.com/caramelomartins/awesome-linters">程式碼品質分析工具清單</a>》。</li>
+  <li>維基百科上的《<a href="https://en.wikipedia.org/wiki/Programming_style">代碼風格</a>》條目。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/understandable-english-first.html b/_site/criteria/understandable-english-first.html
new file mode 100644
index 00000000..9a756e1e
--- /dev/null
+++ b/_site/criteria/understandable-english-first.html
@@ -0,0 +1,566 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>使用白話的英語, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/understandable-english-first.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/documenting.html"
+		     >&#8592; Document the code</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/documenting.html"
+		     >&#8592; 程式碼有文件</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/open-standards.html"
+		     >Use open standards &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/open-standards.html"
+		     >採用開放標準 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/understandable-english-first.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/understandable-english-first.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="使用白話的英語">使用白話的英語</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>的所有文件都必須使用英語。</li>
+  <li>所有<a href="/glossary.html#code">程式碼</a>都必須使用英語編寫，其中<a href="/glossary.html#policy">政策</a>是由機器解讀當作程式碼的部分則除外。</li>
+  <li>任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。</li>
+  <li>任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。</li>
+  <li>代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。</li>
+  <li>代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。</li>
+  <li>根據《<a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">網頁內容近用性無障礙指南 2</a>》的建議，文件內容應該以國中識讀程度為主。</li>
+  <li>可選擇是否提供任何程式碼、文件、測試等的翻譯版。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓不同情境的廣大利害關係人，都能瞭解代碼庫以及其用途。</li>
+  <li>讓代碼庫更容易被找到。</li>
+  <li>能幫助您達成《<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟無障礙環境命令</a>》，內容要求大多數的公家機關資訊都要能夠近用以滿足無障礙環境。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓代碼庫功能解說更容易瞭解。</li>
+  <li>幫助他人在沒有額外解釋之下，就能理解貴組織單位的業內用語。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫文件有英語版本。</li>
+  <li>確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。</li>
+  <li>確認任何非英語政策都有隨附英語版摘要。</li>
+  <li>確認翻譯版與英語版內容相同。</li>
+  <li>確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。</li>
+  <li>檢查文件的拼字、文法與易讀性等。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在使用這些詞彙的地方加上詞彙表連結。</li>
+  <li>以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+  <li>詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>根據 W3C 全球資訊網協會《<a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容近用性無障礙指南 2.1 與 3.1 之可讀性</a>》內文，撰寫的文字內容要更容易閱讀與理解。</li>
+  <li>Theo Sanderson 所發表的「<a href="https://splasho.com/upgoer5/">Upgoer 5 文字編輯軟體</a>」只允許使用最常用的
+1000 個英文單字。</li>
+  <li>美國總務署《<a href="https://www.plainlanguage.gov/about/definitions/">白話語言定義</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/version-control-and-history.html b/_site/criteria/version-control-and-history.html
new file mode 100644
index 00000000..269ff91e
--- /dev/null
+++ b/_site/criteria/version-control-and-history.html
@@ -0,0 +1,585 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>維護版本控制, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/version-control-and-history.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria_source/make-contributing-easy.html"
+		     >&#8592; Make contributing easy</a></span>
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/make-contributing-easy.html"
+		     >&#8592; 貢獻要容易</a></span>
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria_source/require-review.html"
+		     >Require review of contributions &#8594;</a></span>
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/require-review.html"
+		     >要求審查貢獻內容 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規範">需求規範</a></li>
+  <li><a href="#此措施為何重要">此措施為何重要</a></li>
+  <li><a href="#此措施辦不到的事">此措施辦不到的事</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#政策制定者需要的工作">政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria/version-control-and-history.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria/version-control-and-history.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="維護版本控制">維護版本控制</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>社群必須要有方法為<a href="/glossary.html#code">程式碼</a>維護<a href="/glossary.html#version-control">版本控制</a>。</li>
+  <li><a href="/glossary.html#codebase">代碼庫</a>中的所有檔案皆必須有版本控制。</li>
+  <li>所有決定皆必須記錄成提交訊息。</li>
+  <li>每份提交訊息皆必須盡可能附上討論與議題連結。</li>
+  <li>代碼庫應該以分散式版本控制系統作維護。</li>
+  <li>貢獻者應該將相關的修改變動提交內容作群組分類。</li>
+  <li>維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。</li>
+  <li>貢獻者應該偏好使用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。</li>
+  <li>貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>版本控制代表追蹤程式碼歷來的變動。這能讓您為代碼庫製作有條理的變動歷史文件。這是大規模協作能運作的要素。</p>
+
+<p>分散式版本控制能讓您：</p>
+
+<ul>
+  <li>擁有完整的程式碼副本與其版本歷史</li>
+  <li>在需要時可以將代碼庫恢復至先前版本</li>
+  <li>紀錄變動與變動的原因，可幫助未來開發人員瞭解整個過程</li>
+  <li>比較兩個不同版本</li>
+  <li>在將修改內容合併回代碼庫之前，各團隊可以針對修改變動平行作業</li>
+  <li>在沒有網路時也能繼續作業，可以日後再將修改變動合併回代碼庫與其他人整合</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>代替<a href="/criteria/document-maturity.html">成熟度宣告</a>。</li>
+  <li>保證程式碼能正確執行。</li>
+  <li>保證有人加入協作。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。</li>
+  <li>審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。</li>
+  <li>審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。</li>
+  <li>檢查版本控制系統是否為分散式。</li>
+  <li>審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。</li>
+  <li>檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。</li>
+  <li>檢查代碼庫在可能的情況下，檔案都是採用文字格式。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>如果因為<a href="/glossary.html#policy">政策</a>改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
+    <ul>
+      <li>政策改變的地方，</li>
+      <li>代碼庫如何因應而改變。</li>
+    </ul>
+  </li>
+</ul>
+
+<p>舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。</li>
+  <li>使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。</li>
+  <li>提交內容的訊息要寫清楚，方便之後比較各版本。</li>
+  <li>在政策改變以後與政策制定者合作，說明原始碼更新的內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Karl Fogel《<a href="https://producingoss.com/en/vc.html#vc-vocabulary">製作開放原始碼軟體：版本控制字彙</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding">維護程式碼的版本控制</a>》。</li>
+  <li>GitHub 提供的「<a href="https://lab.github.com/">GitHub學習實驗室</a>」，可學習如何使用 GitHub，或是重溫您的技巧。</li>
+  <li>GitHub 提供的「<a href="https://education.github.com/git-cheat-sheet-education.pdf">Git 密技表</a>」列出了最常用的
+git 指令。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/bundle-policy-and-code.html b/_site/criteria_source/bundle-policy-and-code.html
new file mode 100644
index 00000000..d66773ff
--- /dev/null
+++ b/_site/criteria_source/bundle-policy-and-code.html
@@ -0,0 +1,364 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Bundle policy and source code, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/bundle-policy-and-code.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/bundle-policy-and-code.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/bundle-policy-and-code.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="bundle-policy-and-source-code">Bundle policy and source code</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST include the <a href="/glossary.html#policy">policy</a> that the source <a href="/glossary.html#code">code</a> is based on.</li>
+  <li>The codebase MUST include all source code that the policy is based on, unless used for fraud detection.</li>
+  <li>Policy SHOULD be provided in machine readable and unambiguous formats.</li>
+  <li><a href="/glossary.html#continuous-integration">Continuous integration</a> tests SHOULD validate that the source code and the policy are executed coherently.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>Access to both the source code and the policy documents is necessary for understanding and reuse of, as well as collaboration in, a codebase.
+Understanding the context and the policies in that context is fundamental to understanding what problems a codebase is trying to solve and how it sets out to solve them.
+To be able to evaluate whether to adopt a codebase in a new context, an organization will need to understand what process changes it must choose to make or how to contribute additional configurability to the existing solution in order to adapt it to the new context.</p>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee that a codebase will reflect the bundled policy.</li>
+  <li>Make sure packages comply with the local technical infrastructure or legal framework of a given public organization.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm with a civil servant that all policy that the source code is based on is included.</li>
+  <li>Confirm with a civil servant that all source code that the policy is based on is included.</li>
+  <li>Check if policy can be interpreted by a machine.</li>
+  <li>Check the continuous integration tests for coherent execution of source code and policy pass.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Collaborate with developers and designers to ensure there is no mismatch between policy code and source code.</li>
+  <li>Provide the relevant policy texts for inclusion in the <a href="/glossary.html#repository">repository</a>; if the text is not available in English, also provide an English summary. Be sure to include standards that your organization has chosen to adhere to and any organizational processes which impact the development or the deployment context of the codebase for your organization.</li>
+  <li>Provide references and links to texts which support the policies.</li>
+  <li>Document policy in formats that are unambiguous and machine-readable such as <a href="https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation">Business Process Model and Notation</a>, <a href="https://en.wikipedia.org/wiki/Decision_Model_and_Notation">Decision Model and Notation</a> and <a href="https://en.wikipedia.org/wiki/CMMN">Case Management Model Notation</a>.</li>
+  <li>Track policy with <a href="/criteria_source/version-control-and-history.html">the same version control</a> and documentation used to track source code.</li>
+  <li>Check in regularly to understand how the non-policy code in the codebase has changed and whether it still matches the <a href="/criteria_source/document-objectives.html">intentions of the policy</a>.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Keep policy makers, developers and designers involved and connected throughout the whole development process.</li>
+  <li>Make sure policy makers, developers and designers are working to the same objectives.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Become familiar with and be able to use the process modelling notation that the policy makers in your organization use.</li>
+  <li>Work together with policy makers to ensure there is no mismatch between policy code and source code.</li>
+  <li>Give feedback on how to make policy documentation more clear.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://bpmn.io/">Free online tools for building BPMN, CMMN and DMN diagrams at bmpn.io</a> by Camunda.</li>
+  <li><a href="https://www.bpmnquickguide.com/view-bpmn-quick-guide/">BPMN Quick Guide</a> by Trisotech.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/code-in-the-open.html b/_site/criteria_source/code-in-the-open.html
new file mode 100644
index 00000000..281564f6
--- /dev/null
+++ b/_site/criteria_source/code-in-the-open.html
@@ -0,0 +1,368 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Code in the open, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/code-in-the-open.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/code-in-the-open.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/code-in-the-open.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="code-in-the-open">Code in the open</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All source <a href="/glossary.html#code">code</a> for any <a href="/glossary.html#policy">policy</a> in use (unless used for fraud detection) MUST be published and publicly accessible.</li>
+  <li>All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.</li>
+  <li>Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the <a href="/glossary.html#repository">repository</a>.</li>
+  <li>Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.</li>
+  <li>Documenting which source code or policy underpins any specific interaction the <a href="/glossary.html#general-public">general public</a> may have with an organization is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>Coding in the open:</p>
+
+<ul>
+  <li>improves transparency</li>
+  <li>increases code quality</li>
+  <li>facilitates the auditing processes</li>
+</ul>
+
+<p>These aspects together create more opportunities for citizens to understand how software and policy impact their interactions with a public organization.</p>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Make source code or policy reusable.</li>
+  <li>Make the <a href="/glossary.html#codebase">codebase</a> and the code within it understandable to as many people as possible.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the source for each version currently in use is published on the internet where it can be seen from outside the original contributing organization and without the need for any form of authentication or authorization.</li>
+  <li>Confirm that the codebase files and commit history do not include sensitive information.</li>
+  <li>Check for the publication of source code not currently in use.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Develop policies in the open.</li>
+  <li>Prioritize open and transparent policies.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Develop a culture that embraces openness, learning and feedback.</li>
+  <li>Collaborate with external vendors and freelancers by working in the open.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>As a reviewer, for each commit, verify that content does not include sensitive information such as configurations, usernames or passwords, public keys or other real credentials used in production systems.</li>
+  <li>Clearly split data and code, in order to meet the requirement about sensitive information above.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">Coding in the open</a> by the UK Government Digital Service.</li>
+  <li><a href="https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed">When code should be open or closed</a> by the UK Government Digital Service.</li>
+  <li><a href="https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open">Security considerations when coding in the open</a> by the UK Government Digital Service.</li>
+  <li><a href="https://www.gov.uk/service-manual/technology/deploying-software-regularly">Deploying software regularly</a> by the UK Government Digital Service.</li>
+  <li><a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">How GDS uses GitHub</a> by the UK Government Digital Service.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/continuous-integration.html b/_site/criteria_source/continuous-integration.html
new file mode 100644
index 00000000..4c069e3d
--- /dev/null
+++ b/_site/criteria_source/continuous-integration.html
@@ -0,0 +1,388 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Use continuous integration, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/continuous-integration.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/continuous-integration.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/continuous-integration.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="use-continuous-integration">Use continuous integration</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All functionality in the source <a href="/glossary.html#code">code</a> MUST have automated tests.</li>
+  <li>Contributions MUST pass all automated tests before they are admitted into the <a href="/glossary.html#codebase">codebase</a>.</li>
+  <li>The codebase MUST have guidelines explaining how to structure contributions.</li>
+  <li>The codebase MUST have active contributors.</li>
+  <li>The codebase guidelines SHOULD state that each contribution should focus on a single issue.</li>
+  <li>Source code test and documentation coverage SHOULD be monitored.</li>
+  <li>Testing <a href="/glossary.html#policy">policy</a> and documentation for consistency with the source and vice versa is OPTIONAL.</li>
+  <li>Testing policy and documentation for style and broken links is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Using <a href="/glossary.html#continuous-integration">continuous integration</a>:
+    <ul>
+      <li>allows you to quickly identify problems with the codebase,</li>
+      <li>enables risk taking and focusing on problem solving while minimizing stress for the contributors,</li>
+      <li>lowers barriers for new contributors by reducing the amount of understanding necessary to suggest changes,</li>
+      <li>leads to more maintainable code,</li>
+      <li>speeds up the development cycle.</li>
+    </ul>
+  </li>
+  <li>Smaller, more regular contributions are typically easier to evaluate and lower risk compared to large infrequent changes.</li>
+  <li>Codebases in active development more reliably provide opportunities for collaboration and feedback.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Create a fault tolerant infrastructure that will work and scale perfectly.</li>
+  <li>Create meaningful tests.</li>
+  <li>Test for real life situations.</li>
+  <li>Guarantee the code will deliver exactly the same policy result.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that there are tests present.</li>
+  <li>Confirm that code coverage tools check that coverage is at 100% of the code.</li>
+  <li>Confirm that contributions are only admitted into the codebase after all of the tests are passed.</li>
+  <li>Confirm that contribution guidelines explain how to structure contributions.</li>
+  <li>Confirm that there are contributions from within the last three months.</li>
+  <li>Check if code coverage data is published.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Involve management as well as developers and designers as early in the process as possible and keep them engaged throughout development of your policy.</li>
+  <li>Make sure there are also automated tests set up for policy documentation.</li>
+  <li>Fix policy documentation promptly if it fails a test.</li>
+  <li>Make sure the code reflects any changes to the policy (see <a href="/criteria_source/version-control-and-history.html">Maintain version control</a>).</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Make sure to test with real end users as quickly and often as possible.</li>
+  <li>Plan the work to deliver small parts very often instead of large parts less frequently.</li>
+  <li>Procure consultancy services that deliver incrementally aligned with the plan.</li>
+  <li>After a large failure, encourage publication of incident reports and public discussion of what was learned.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Help management structure the work plan such that it can be delivered as small increments.</li>
+  <li>Help contributors limit the scope of their contributions and feature requests to be as small as reasonable.</li>
+  <li>Help management and policy makers test their contributions, for example by testing their contributions for broken links or style.</li>
+  <li>Structure code written to handle conditions which are difficult to create in a test environment in such a way that the conditions can be simulated during testing. Forms of resource exhaustion such as running out of storage space and memory allocation failure are typical examples of difficult to create conditions.</li>
+  <li>Tune the test code coverage tools to avoid false alarms resulting from inlining or other optimizations.</li>
+  <li>Deploy often.</li>
+  <li>Integrate your work at least once a day.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.martinfowler.com/articles/continuousIntegration.html">What is continuous integration</a> by Martin Fowler.</li>
+  <li><a href="https://www.continuousdelivery.com/">What is continuous delivery</a> by Jez Humble.</li>
+  <li><a href="https://gds-way.cloudapps.digital/standards/continuous-delivery.html">Use continuous delivery</a> by the UK Government Digital Service.</li>
+  <li><a href="https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly">Quality assurance: testing your service regularly</a> by the UK Government Digital Service.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/document-maturity.html b/_site/criteria_source/document-maturity.html
new file mode 100644
index 00000000..04c412b7
--- /dev/null
+++ b/_site/criteria_source/document-maturity.html
@@ -0,0 +1,367 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Document codebase maturity, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/document-maturity.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/document-maturity.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/document-maturity.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="document-codebase-maturity">Document codebase maturity</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST be versioned.</li>
+  <li>The codebase that is ready to use MUST only depend on other codebases that are also ready to use.</li>
+  <li>The codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version.</li>
+  <li>The codebase SHOULD contain a log of changes from version to version, for example in the <code class="language-plaintext highlighter-rouge">CHANGELOG</code>.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>Clearly signalling a codebase’s maturity helps others decide whether to reuse, invest in or contribute to it.</p>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee that others will use the <a href="/glossary.html#code">code</a>.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the codebase has a strategy for versioning which is documented.</li>
+  <li>Confirm that it is clear where to get the newest version.</li>
+  <li>Confirm that the codebase doesn’t depend on any codebases marked with a less mature status.</li>
+  <li>Confirm that the codebase is ready to use or labeled as prototype, alpha, beta or pre-release version.</li>
+  <li>Check that there is a log of changes.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>When developing <a href="/glossary.html#policy">policy</a>, understand that any code developed needs to be tested and improved before it can be put into service.</li>
+  <li>Consider versioning policy changes, especially when they trigger new versions of the source code.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Make sure that services only rely on codebases of equal or greater maturity than the service. For example, don’t use a beta codebase in a production service or a prototype codebase in a beta service.</li>
+  <li>If the codebase is not ready for general use, work with the developers to ensure the codebase is properly labeled:
+    <ul>
+      <li>prototype: to test the look and feel, and to internally prove the concept of the technical possibilities,</li>
+      <li>alpha: to do guided tests with a limited set of users,</li>
+      <li>beta: to open up testing to a larger section of the <a href="/glossary.html#general-public">general public</a>, for example to test if the codebase works at scale,</li>
+      <li>pre-release version: code that is ready to be released but hasn’t received formal approval yet.</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Add a prominent header to every interface that indicates the maturity level of the code.</li>
+  <li>Version all releases.</li>
+  <li>Especially in ‘rolling release’ scenarios, the version may be automatically derived from the <a href="/glossary.html#version-control">version control</a> system metadata (for example by using <a href="https://git-scm.com/docs/git-describe">git describe</a>).</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process">Service Design and Delivery Process</a> by the Australian Digital Transformation Agency.</li>
+  <li><a href="https://www.gov.uk/service-manual/agile-delivery">Service Manual on Agile Delivery</a> by the UK Government Digital Service.</li>
+  <li><a href="https://semver.org/">Semantic Versioning Specification</a> used by many codebases to label versions.</li>
+  <li><a href="https://www.youtube.com/watch?v=_cyI7DMhgYc">What are the Discovery, Alpha, Beta and Live stages in developing a service? [Video 0’0”59]</a> by the UK Government Digital Service.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/document-objectives.html b/_site/criteria_source/document-objectives.html
new file mode 100644
index 00000000..02db715b
--- /dev/null
+++ b/_site/criteria_source/document-objectives.html
@@ -0,0 +1,358 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Document codebase objectives, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/document-objectives.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/document-objectives.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/document-objectives.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="document-codebase-objectives">Document codebase objectives</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.</li>
+  <li>Codebase documentation SHOULD clearly describe the connections between <a href="/glossary.html#policy">policy</a> objectives and codebase objectives.</li>
+  <li>Documenting the objectives of the codebase for the <a href="/glossary.html#general-public">general public</a> is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>Documenting codebase objectives:</p>
+
+<ul>
+  <li>provides an easy way for people to decide whether this codebase, or one of its modules, is interesting for them now or in the future.</li>
+  <li>helps scope your own development.</li>
+  <li>clearly communicates to other stakeholders and contributors the purpose of the codebase and the modules of which it is composed.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee that the codebase achieves the stated objective(s).</li>
+  <li>Guarantee contributions to the codebase.</li>
+  <li>Prevent other codebases from attempting to achieve the same objectives.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the codebase documentation includes the codebase objectives, mission or goal.</li>
+  <li>Check for descriptions of connections between policy objectives and codebase objectives.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Add the policy objectives to the codebase documentation, for example in the <code class="language-plaintext highlighter-rouge">README</code>.</li>
+  <li>Include relevant policies which impact the community, codebase, and development like value and ethics based policies, for example accessibility or equal opportunity.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Add the organizational and business objectives to the codebase documentation, for example in the <code class="language-plaintext highlighter-rouge">README</code>.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Add the technology and design objectives to the codebase documentation, for example in the <code class="language-plaintext highlighter-rouge">README</code>.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf">How to write project objectives</a> by Marek Hajduczenia.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/documenting.html b/_site/criteria_source/documenting.html
new file mode 100644
index 00000000..3baea1c1
--- /dev/null
+++ b/_site/criteria_source/documenting.html
@@ -0,0 +1,369 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Document the code, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/documenting.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/documenting.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/documenting.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="document-the-code">Document the code</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All of the functionality of the <a href="/glossary.html#codebase">codebase</a>, <a href="/glossary.html#policy">policy</a> as well as source, MUST be described in language clearly understandable for those that understand the purpose of the <a href="/glossary.html#code">code</a>.</li>
+  <li>The documentation of the codebase MUST contain a description of how to install and run the source code.</li>
+  <li>The documentation of the codebase MUST contain examples demonstrating the key functionality.</li>
+  <li>The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the <a href="/glossary.html#general-public">general public</a> and journalists.</li>
+  <li>The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.</li>
+  <li>The documentation of the codebase SHOULD contain examples for all functionality.</li>
+  <li>The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.</li>
+  <li>There SHOULD be <a href="/glossary.html#continuous-integration">continuous integration</a> tests for the quality of the documentation.</li>
+  <li>Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.</li>
+  <li>Testing the code by using examples in the documentation is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Users can start using and contributing more quickly.</li>
+  <li>You help people discover the codebase, especially people asking ‘is there already code that does something like this’.</li>
+  <li>This provides transparency into your organization and processes.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Contribute directly to more reusable, portable code (see <a href="/criteria_source/reusable-and-portable-codebases.html">Create reusable and portable code</a>).</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that other stakeholders, professionals from other public organizations and the general public find the documentation clear and understandable.</li>
+  <li>Confirm that the documentation describes how to install and run the source code.</li>
+  <li>Confirm that the documentation includes examples of the key functionality.</li>
+  <li>Check with members of the general public and journalists if they can understand the high level description.</li>
+  <li>Check that the instructions for how to install and run a standalone version of the source code result in a running system.</li>
+  <li>Check that all functionality documented contains an example.</li>
+  <li>Check that the documentation includes a high level architectural diagram or similar.</li>
+  <li>Check that the documentation quality is part of integration testing, for example documentation is generated from code, and links and images are tested.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Check in regularly to understand how the non-policy code in the codebase has changed.</li>
+  <li>Give feedback on how to make non-policy documentation more clear.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Try to use the codebase.</li>
+  <li>Make sure you understand both the policy and source code as well as the documentation.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Check in regularly to understand how the non-source code in the codebase has changed.</li>
+  <li>Give feedback on how to make non-source documentation more clear.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.writethedocs.org/guide/">Documentation guide</a> by Write the Docs.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/findability.html b/_site/criteria_source/findability.html
new file mode 100644
index 00000000..81c126de
--- /dev/null
+++ b/_site/criteria_source/findability.html
@@ -0,0 +1,374 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Make the codebase findable, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/findability.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/findability.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/findability.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="make-the-codebase-findable">Make the codebase findable</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST be findable using a search engine by describing the problem it solves in natural language.</li>
+  <li>The codebase MUST be findable using a search engine by codebase name.</li>
+  <li>Maintainers SHOULD submit the codebase to relevant software catalogs.</li>
+  <li>The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).</li>
+  <li>The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, <a href="/glossary.html#repository">repository</a> location and website.</li>
+  <li>The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.</li>
+  <li>A dedicated domain name for the codebase is OPTIONAL.</li>
+  <li>Regular presentations at conferences by the community are OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Proactiveness is needed; just publishing a codebase and hoping it’s found doesn’t work.</li>
+  <li>A metadata description file increases discoverability.</li>
+  <li>The more findable a codebase is, the more potential new collaborators will find it.</li>
+  <li>By having well-written metadata containing a unique and persistent identifer, such as a Wikidata item or FSF software directory listing, and thus being part of the semantic web, it will be easier for other people to refer, cite, disambiguate and discover the codebase through third party tools.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Ensure new collaborators or replicators.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the codebase appears in the first set of results on more than one major search engine when searching by a plain English problem description.</li>
+  <li>Confirm that the codebase appears in the first set of results on more than one major search engine when searching by a technical problem description.</li>
+  <li>Confirm that the codebase appears in the first set of results on more than one major search engine when searching by the codebase name.</li>
+  <li>Check for the codebase listing in relevant software catalogs.</li>
+  <li>Check for a codebase website which describes the problem the codebase solves.</li>
+  <li>Check unique and persistent identifier entries for mention of the major contributors.</li>
+  <li>Check unique and persistent identifier entries for the repository location.</li>
+  <li>Check unique and persistent identifier entries for the codebase website.</li>
+  <li>Check for a machine-readable metadata description file.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Contribute a description of the policy area or problem this codebase acts on or operates.</li>
+  <li>Test your problem description with peers outside of your context who aren’t familiar with the codebase.</li>
+  <li>Present on how the codebase implements the <a href="/glossary.html#policy">policy</a> at relevent conferences.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Budget for content design and Search Engine Optimization skills in the team.</li>
+  <li>Ensure people involved in the project present at relevant conferences.</li>
+  <li>Search trademark databases to avoid confusion or infringement before deciding the name.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Search engine optimization.</li>
+  <li>Test your problem description with peers outside of your context who aren’t familiar with the codebase.</li>
+  <li>Suggest conferences to present at and present at them.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.wikidata.org/wiki/Wikidata:Introduction">Introduction to Wikidata</a> by the Wikidata community.</li>
+  <li><a href="https://directory.fsf.org/wiki/Main_Page">FSF software directory listing</a> by the Free Softare Foundation.</li>
+  <li>The <a href="https://www.go-fair.org/fair-principles/">FAIR Guiding Principles for scientific data management and stewardship</a> by the GO FAIR International Support and Coordination Office provide a nice list of attributes that make (meta)data more machine actionable (and hence more findable). Some of these apply directly to codebases, while others may provoke exploration into what the codebase equivalent would be.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/index.html b/_site/criteria_source/index.html
new file mode 100644
index 00000000..0943eb16
--- /dev/null
+++ b/_site/criteria_source/index.html
@@ -0,0 +1,342 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Criteria, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/index.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/index.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="criteria">Criteria</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<ol>
+  <li>
+    <p><a href="/criteria/code-in-the-open.html">原始碼要開放</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/bundle-policy-and-code.html">政策與原始碼要合捆</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/reusable-and-portable-codebases.html">程式碼要可重複使用且可攜</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-to-contributions.html">歡迎貢獻者</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/make-contributing-easy.html">貢獻要容易</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/version-control-and-history.html">維護版本控制</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/require-review.html">要求審查貢獻內容</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-objectives.html">代碼庫有目標文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/documenting.html">程式碼有文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/understandable-english-first.html">使用白話的英語</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-standards.html">採用開放標準</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/continuous-integration.html">使用持續整合</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/open-licenses.html">發行採用開放授權</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/findability.html">代碼庫可查詢得到</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/style.html">風格要前後一致</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-maturity.html">紀錄代碼庫成熟度</a></p>
+  </li>
+</ol>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/index.md b/_site/criteria_source/index.md
new file mode 100644
index 00000000..a76e29e4
--- /dev/null
+++ b/_site/criteria_source/index.md
@@ -0,0 +1,10 @@
+# Criteria
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+{% assign sorted = site.pages | sort:"order" %}
+
+{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
+
+1. [{{page.title}}]({{page.url}}){% endif%}    {% endif%}  {% endif%}{% endfor %}
diff --git a/_site/criteria_source/make-contributing-easy.html b/_site/criteria_source/make-contributing-easy.html
new file mode 100644
index 00000000..dbf18b6b
--- /dev/null
+++ b/_site/criteria_source/make-contributing-easy.html
@@ -0,0 +1,360 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Make contributing easy, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/make-contributing-easy.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/make-contributing-easy.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/make-contributing-easy.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="make-contributing-easy">Make contributing easy</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST have a public issue tracker that accepts suggestions from anyone.</li>
+  <li>The codebase MUST include instructions for how to privately report security issues for responsible disclosure.</li>
+  <li>The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a <code class="language-plaintext highlighter-rouge">README</code> file.</li>
+  <li>The codebase MUST have communication channels for users and developers, for example email lists.</li>
+  <li>The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Enables users to fix problems and add features to the shared codebase leading to better, more reliable and feature rich software.</li>
+  <li>Allows collaborative uptake of shared digital infrastructure.</li>
+  <li>Helps users decide to use one codebase over another.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee others will reuse the codebase.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that there is a public issue tracker.</li>
+  <li>Confirm that there are instructions for privately reporting security issues.</li>
+  <li>Confirm that the codebase contains links to the public issue tracker and submitted codebase changes.</li>
+  <li>Confirm that it is possible to participate in a discussion with other users and developers about the software using channels described in the codebase.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Track <a href="/glossary.html#policy">policy</a> issues in the codebase, so that a relevant external policy expert can volunteer help.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Track management issues in the codebase, so that external managers with relevant experience can volunteer help.</li>
+  <li>Support your experienced policy makers, developers and designers to keep contributing to the codebase for as long as possible.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Respond promptly to requests.</li>
+  <li>Keep your management informed of the time and resources you require to support other contributors.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf">How to inspire exceptional contributions to your open-source project</a> by Joel Hans.</li>
+  <li><a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">The benefits of coding in the open</a> by the UK Government Digital Service.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/open-licenses.html b/_site/criteria_source/open-licenses.html
new file mode 100644
index 00000000..fa2b267f
--- /dev/null
+++ b/_site/criteria_source/open-licenses.html
@@ -0,0 +1,363 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Publish with an open license, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/open-licenses.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/open-licenses.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/open-licenses.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="publish-with-an-open-license">Publish with an open license</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All <a href="/glossary.html#code">code</a> and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.</li>
+  <li>Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.</li>
+  <li>All code MUST be published with a license file.</li>
+  <li>Contributors MUST NOT be required to transfer copyright of their contributions to the <a href="/glossary.html#codebase">codebase</a>.</li>
+  <li>All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.</li>
+  <li>Having multiple licenses for different types of code and documentation is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Makes it possible for anyone to see the code and know that they can and how they can reuse it.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Prevent use of the code by any specific actors.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the codebase is clearly licensed.</li>
+  <li>Confirm that the license for the source code is on the <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license list</a> and the license for documentation <a href="https://opendefinition.org/licenses/">conforms to the Open Definition</a>.</li>
+  <li>Confirm that the licenses used in the codebase are included as files.</li>
+  <li>Confirm that contribution guidelines and <a href="/glossary.html#repository">repository</a> configuration do not require transfer of copyright.</li>
+  <li>Check for machine-readable license checking in the codebase <a href="/glossary.html#continuous-integration">continuous integration</a> tests.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Develop <a href="/glossary.html#policy">policy</a> that requires code to be <a href="/glossary.html#open-source">open source</a>.</li>
+  <li>Develop policy that disincentivizes non-open source code and technology in procurement.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Only work with open source vendors that deliver their code by publishing it under an open source license.</li>
+  <li>Beware that even though <a href="https://creativecommons.org/licenses/">Creative Commons licenses</a> are great for documentation, licenses that stipulate Non-Commercial or No Derivatives are NOT freely reusable, changeable and redistributable and don’t fulfill these requirements.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Add a new <code class="language-plaintext highlighter-rouge">license</code> file to every new codebase created.</li>
+  <li>Add a copyright notice and a license header to every new source code file created.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://opensource.org/osd">Open source definition</a> by the Open Source Initiative, all open source licenses meet this definition.</li>
+  <li><a href="https://creativecommons.org/about/videos/creative-commons-kiwi">Animated video introduction to Creative Commons</a> by Creative Commons Aotearoa New Zealand.</li>
+  <li><a href="https://reuse.software/spec/">REUSE Initiative specification</a> by Free Software Foundation Europe for unambiguous, human-readable and machine-readable copyright and licensing information.</li>
+  <li><a href="https://spdx.org/licenses/">SPDX License List</a> by the Linux Foundation with standardized, machine-readable abbreviations for most licenses.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/open-standards.html b/_site/criteria_source/open-standards.html
new file mode 100644
index 00000000..d4b648fa
--- /dev/null
+++ b/_site/criteria_source/open-standards.html
@@ -0,0 +1,359 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Use open standards, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/open-standards.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/open-standards.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/open-standards.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="use-open-standards">Use open standards</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>For features of the <a href="/glossary.html#codebase">codebase</a> that facilitate the exchange of data the codebase MUST use an <a href="/glossary.html#open-standard">open standard</a> that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.</li>
+  <li>Any non-open standards used MUST be recorded clearly as such in the documentation.</li>
+  <li>Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.</li>
+  <li>Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.</li>
+  <li>If no existing open standard is available, effort SHOULD be put into developing one.</li>
+  <li>Standards that are machine testable SHOULD be preferred over those that are not.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Creates interoperability between systems.</li>
+  <li>Reduces possible vendor lock-in.</li>
+  <li>Guarantees access to the knowledge required to reuse and contribute to the codebase.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Make it understandable how to use the software.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that data exchange follows an OSI approved open standard.</li>
+  <li>Confirm that any non-open standards used are clearly documented as such.</li>
+  <li>Confirm that documentation includes a list of the standards followed within the codebase, each with a working link, or a statement that no standards were chosen.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Mandate use of open standards everywhere possible.</li>
+  <li>Prohibit procurement of technology that does not use open standards.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Consider including open standard compliance assessment in <a href="/glossary.html#code">code</a> reviews.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Add <a href="/glossary.html#continuous-integration">continuous integration</a> tests for compliance with the standards.</li>
+  <li>Review the commits and other <a href="/glossary.html#repository">repository</a> resources for references to standards and cross-check those with the standards listed.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">Open Standards principles</a>, <a href="/glossary.html#policy">policy</a> paper of the UK Cabinet Office.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/open-to-contributions.html b/_site/criteria_source/open-to-contributions.html
new file mode 100644
index 00000000..b1390e5c
--- /dev/null
+++ b/_site/criteria_source/open-to-contributions.html
@@ -0,0 +1,371 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Welcome contributors, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/open-to-contributions.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/open-to-contributions.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/open-to-contributions.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="welcome-contributors">Welcome contributors</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST allow anyone to submit suggestions for changes to the codebase.</li>
+  <li>The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> file.</li>
+  <li>The codebase MUST document the governance of the codebase, contributions and its community, for example in a <code class="language-plaintext highlighter-rouge">GOVERNANCE</code> file.</li>
+  <li>The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.</li>
+  <li>The codebase SHOULD have a publicly available roadmap.</li>
+  <li>The codebase SHOULD publish codebase activity statistics.</li>
+  <li>Including a code of conduct for contributors in the codebase is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Helps newcomers understand and trust the codebase community’s leadership.</li>
+  <li>Prevents the community that works on a codebase splitting because there is no way to influence its goals and progress, resulting in diverging communities.</li>
+  <li>Helps users decide to use one codebase over another.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee others will join the community.</li>
+  <li>Guarantee others will reuse the codebase.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that it is possible to submit suggestions for changes to the codebase.</li>
+  <li>Confirm there are contribution guidelines.</li>
+  <li>Confirm that the codebase governance is clearly explained, including how to influence codebase governance.</li>
+  <li>Check for a list of involved organizations.</li>
+  <li>Check for a roadmap.</li>
+  <li>Check for published activity statistics.</li>
+  <li>Check for a code of conduct.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Add a list to the codebase of any other resources that <a href="/glossary.html#policy">policy</a> experts, non-governmental organizations and academics would find useful for understanding or reusing your policy.</li>
+  <li>Consider adding contact details so that other policy makers considering collaboration can ask you for advice.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Make sure that the documentation of the governance includes the current process for how to make changes to the governance.</li>
+  <li>If the community has some consensus about how the governance should change, then include those ideas stated as ambitions in the documentation.</li>
+  <li>Make sure the documentation explains how each organization is involved in the codebase, what resources it has available for it and for how long.</li>
+  <li>Support your experienced policy makers, developers and designers to stay part of the community for as long as possible.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Respond promptly to requests.</li>
+  <li>Keep your management informed of the time and resources you require to support other contributors.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://opensource.guide/building-community/">Building welcoming communities</a> by Open Source Guides.</li>
+  <li><a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/">The Open Source Contributor Funnel</a> by Mike McQuaid.</li>
+  <li><a href="https://opensource.guide/leadership-and-governance/">Leadership and governance</a> for growing <a href="/glossary.html#open-source">open source</a> community projects, by Open Source Guides.</li>
+  <li><a href="http://hintjens.com/blog:117">Building online communities</a> by Pieter Hintjens (long read!).</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/require-review.html b/_site/criteria_source/require-review.html
new file mode 100644
index 00000000..4ee8ff7f
--- /dev/null
+++ b/_site/criteria_source/require-review.html
@@ -0,0 +1,380 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Require review of contributions, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/require-review.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/require-review.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/require-review.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="require-review-of-contributions">Require review of contributions</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All contributions that are accepted or committed to release versions of the <a href="/glossary.html#codebase">codebase</a> MUST be reviewed by another contributor.</li>
+  <li>Reviews MUST include source, <a href="/glossary.html#policy">policy</a>, tests and documentation.</li>
+  <li>Reviewers MUST provide feedback on all decisions to not accept a contribution.</li>
+  <li>Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review.</li>
+  <li>Reviews SHOULD include running both the <a href="/glossary.html#code">code</a> and the tests of the codebase.</li>
+  <li>Contributions SHOULD be reviewed by someone in a different context than the contributor.</li>
+  <li>Version control systems SHOULD NOT accept non-reviewed contributions in release versions.</li>
+  <li>Reviews SHOULD happen within two business days.</li>
+  <li>Performing reviews by multiple reviewers is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Increases codebase quality.</li>
+  <li>Reduces security risks as well as operational risks.</li>
+  <li>Creates a culture of making every contribution great.</li>
+  <li>Catches the most obvious mistakes that could happen.</li>
+  <li>Gives contributors the security that their contributions are only accepted if they really add value.</li>
+  <li>Assures contributors of a guaranteed time for feedback or collaborative improvement.</li>
+  <li>Prompt reviews increase both rate of delivery and contributor engagement.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Guarantee the right solution to a problem.</li>
+  <li>Mean that reviewers are liable.</li>
+  <li>Absolve a contributor from writing documentation and tests.</li>
+  <li>Provide you with the right reviewers.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that every commit in the history has been reviewed by a different contributor.</li>
+  <li>Confirm that reviews include source, policy, tests and documentation.</li>
+  <li>Confirm that rejected contributions were appropriately explained.</li>
+  <li>Check if reviews cover conformance to standards, architecture and codebase guidelines.</li>
+  <li>Check with reviewers if they run the code and tests during review.</li>
+  <li>Check with reviewers if commits have been reviewed by a different contributor in a different context.</li>
+  <li>Check for use of branch protection in the <a href="/glossary.html#version-control">version control</a> system.</li>
+  <li>Check the times between contribution submission and review.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Institute a ‘four eyes’ policy where everything, not just code, is reviewed.</li>
+  <li>Use a version control system or methodology that enables review and feedback.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Make delivering great code a shared objective.</li>
+  <li>Make sure writing and reviewing contributions to source, policy, documentation and tests are considered equally valuable.</li>
+  <li>Create a culture where all contributions are welcome and everyone is empowered to review them.</li>
+  <li>Make sure no contributor is ever alone in contributing to a codebase.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Ask other contributors on the codebase to review your work, in your organization or outside of it.</li>
+  <li>Try to respond to others’ requests for code review promptly, initially providing feedback about the concept of the change.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content">How to review code the GDS way</a> by the UK Government Digital Service.</li>
+  <li>Branch protection on <a href="https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches">GitHub</a> and <a href="https://about.gitlab.com/2014/11/26/keeping-your-code-protected/">GitLab</a>.</li>
+  <li><a href="https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/">The Gentle Art of Patch Review</a> by Sage Sharp.</li>
+  <li><a href="https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177">Measuring Engagement</a> by Mozilla.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/reusable-and-portable-codebases.html b/_site/criteria_source/reusable-and-portable-codebases.html
new file mode 100644
index 00000000..ca82bae3
--- /dev/null
+++ b/_site/criteria_source/reusable-and-portable-codebases.html
@@ -0,0 +1,382 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Create reusable and portable code, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/reusable-and-portable-codebases.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/reusable-and-portable-codebases.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/reusable-and-portable-codebases.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="create-reusable-and-portable-code">Create reusable and portable code</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The <a href="/glossary.html#codebase">codebase</a> MUST be developed to be reusable in <a href="/glossary.html#different-contexts">different contexts</a>.</li>
+  <li>The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed <a href="/glossary.html#code">code</a> or services for execution and understanding.</li>
+  <li>The codebase SHOULD be in use by multiple parties.</li>
+  <li>The roadmap SHOULD be influenced by the needs of multiple parties.</li>
+  <li>Configuration SHOULD be used to make code adapt to context specific needs.</li>
+  <li>The codebase SHOULD be localizable.</li>
+  <li>Code and its documentation SHOULD NOT contain situation-specific information.</li>
+  <li>Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Enables other policy makers, developers and designers to reuse what you’ve developed, to test it, to improve it and contribute those improvements back leading to better quality, cheaper maintenance and higher reliability.</li>
+  <li>Makes the code easier for new people to understand (as it’s more general).</li>
+  <li>Makes it easier to control the mission, vision and scope of the codebase because the codebase is thoughtfully and purposefully designed for reusability.</li>
+  <li>Codebases used by multiple parties are more likely to benefit from a self-sustaining community.</li>
+  <li>Any contributor is able to test and contribute without relying on the situation-specific infrastructure of any other contributor or deployment.</li>
+  <li>Composing a codebase from well documented modules improves reusability and maintainability.</li>
+  <li>A module is easier to reuse in another context if its purpose is clearly documented.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Get others to reuse the codebase.</li>
+  <li>Build a community.</li>
+  <li>Shift responsibility for documentation, support, bug-fixing, etc. to another party.</li>
+  <li>Guarantee that modules are generic enough to be reused in any context.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm with someone in a similar role at another organization if they can reuse the codebase and what that would entail.</li>
+  <li>Confirm that the codebase can run without using any proprietary or non open-licensed code or services.</li>
+  <li>Check that the codebase is in use by multiple parties or in multiple contexts.</li>
+  <li>Check that the codebase files and commit history do not include situation-specific data.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Document your <a href="/glossary.html#policy">policy</a> with enough clarity and detail that it can be understood outside of its original context.</li>
+  <li>Make sure your organization is listed as a known user by the codebase.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Make sure that stakeholders and business owners understand that reusability is an explicit codebase goal as this reduces technical debt and provides sustainability for the codebase.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<p>Source should be designed:</p>
+
+<ul>
+  <li>for reuse by other users and organizations regardless of locale,</li>
+  <li>to solve a general problem instead of a specific one,</li>
+  <li>in logically meaningful and isolated modules,</li>
+  <li>so that someone in a similar organization facing a similar problem would be able to use (parts of) the solution.</li>
+</ul>
+
+<p>Ensure that the codebase documentation describes the build-time and runtime dependencies.
+If your context requires deploying to proprietary platforms or using proprietary components, ensure that collaborators can develop, use, test, and deploy without them.</p>
+
+<p>For each commit, reviewers verify that content does not include situation-specific data such as hostnames, personal and organizational data, or tokens and passwords.</p>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable">Making source code open and reusable</a> by the UK Government Digital Service.</li>
+  <li><a href="https://spec.openapis.org/oas/latest.html">OpenAPI Specification</a> by the OpenAPI Initiative defines a standard, programming language-agnostic interface description for human and machine-readable HTTP APIs.</li>
+  <li><a href="https://www.w3.org/International/questions/qa-i18n">Localization vs. Internationalization</a> by the World Wide Web Consortium.</li>
+  <li><a href="https://www.w3.org/International/techniques/authoring-html">Internationalization techniques: Authoring HTML &amp; CSS</a> by the World Wide Web Consortium.</li>
+  <li><a href="https://www.gnu.org/software/gettext/gettext.html">GNU gettext</a> of the GNU Operating System.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/style.html b/_site/criteria_source/style.html
new file mode 100644
index 00000000..6275c4ff
--- /dev/null
+++ b/_site/criteria_source/style.html
@@ -0,0 +1,362 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Use a coherent style, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/style.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/style.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/style.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="use-a-coherent-style">Use a coherent style</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>Contributions MUST adhere to either a coding or writing style guide, either the <a href="/glossary.html#codebase">codebase</a> community’s own or an existing one that is advertised in or part of the codebase.</li>
+  <li>Contributions SHOULD pass automated tests on style.</li>
+  <li>The codebase SHOULD include inline comments and documentation for non-trivial sections.</li>
+  <li>Including sections on <a href="/criteria_source/understandable-english-first.html">understandable English</a> in the style guide is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Enables contributors in different environments to work together on a unified product.</li>
+  <li>Unifying vocabularies reduces friction in communication between contributors.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Help contributors write well or effectively explain what they do.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that contributions are in line with the style guides specified in the documentation.</li>
+  <li>Check for the presence of automated tests on style.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Create, follow and continually improve on a style guide for <a href="/glossary.html#policy">policy</a> and documentation as well as document this in the codebase, for example in the <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> or <code class="language-plaintext highlighter-rouge">README</code>.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Include written language, source, test and policy standards in your organizational definition of quality.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<p>If the codebase does not already have engineering guidelines or other contributor guidance, start by adding documentation to the <a href="/glossary.html#repository">repository</a> describing whatever is being done now, for example in the <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> or <code class="language-plaintext highlighter-rouge">README</code>.
+An important purpose of the file is to communicate design preferences, naming conventions, and other aspects machines can’t easily check.
+Guidance should include what would be expected from <a href="/glossary.html#code">code</a> contributions in order for them to be merged by the maintainers, including source, tests and documentation.
+Continually improve upon and expand this documentation with the aim of evolving this documentation into engineering guidelines.</p>
+
+<p>Additionally:</p>
+
+<ul>
+  <li>Use a linter.</li>
+  <li>Add linter configurations to the codebase.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://github.com/caramelomartins/awesome-linters">List of linters</a> by Hugo Martins.</li>
+  <li><a href="https://en.wikipedia.org/wiki/Programming_style">Programming style</a> on Wikipedia.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/understandable-english-first.html b/_site/criteria_source/understandable-english-first.html
new file mode 100644
index 00000000..f09974cd
--- /dev/null
+++ b/_site/criteria_source/understandable-english-first.html
@@ -0,0 +1,367 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Use plain English, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/understandable-english-first.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/understandable-english-first.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/understandable-english-first.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="use-plain-english">Use plain English</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>All <a href="/glossary.html#codebase">codebase</a> documentation MUST be in English.</li>
+  <li>All <a href="/glossary.html#code">code</a> MUST be in English, except where <a href="/glossary.html#policy">policy</a> is machine interpreted as code.</li>
+  <li>All bundled policy not available in English MUST have an accompanying summary in English.</li>
+  <li>Any translation MUST be up to date with the English version and vice versa.</li>
+  <li>There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.</li>
+  <li>The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.</li>
+  <li>Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.</li>
+  <li>Providing a translation of any code, documentation or tests is OPTIONAL.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<ul>
+  <li>Makes the codebase and what it does understandable for a wider variety of stakeholders in multiple contexts.</li>
+  <li>Helps with the discoverability of the codebase.</li>
+  <li>Can help you meet the <a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">European Union accessibility directive</a>, which requires most public sector information to be accessible.</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Make explanations of the codebase’s functionality understandable.</li>
+  <li>Make your organization’s jargon understandable without an explanation.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that codebase documentation is available in English.</li>
+  <li>Confirm that source code is in English, or confirm any non-English is policy or terms with preceding explanations.</li>
+  <li>Confirm any non-English policy has an accompanying summary in English.</li>
+  <li>Confirm that translations and the English version have the same content.</li>
+  <li>Check that no unexplained acronyms, abbreviations, puns or legal/non-English/domain specific terms are in the documentation.</li>
+  <li>Check the spelling, grammar and readability of the documentation.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>Frequently test with other management, developers and designers in the process if they understand what you are delivering and how you document it.</li>
+</ul>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Try to limit the use of acronyms, abbreviations, puns or legal/non-English/domain specific terms in internal communications in and between teams and stakeholders. Add any such terms to a glossary and link to it from the places they are being used.</li>
+  <li>Be critical of documentation and descriptions in proposals and changes. If you don’t understand something, others will probably also struggle with it.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Frequently test with policy makers and management if they understand what you are delivering and how you document it.</li>
+  <li>Ask someone outside of your context if they understand the content (for example, a developer working on a different codebase).</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li>Text of the <a href="https://www.w3.org/TR/WCAG21/#readable">Web Content Accessibilty Guidelines 2.1, Guideline 3.1 Readable</a> by W3C, make text content readable and understandable.</li>
+  <li><a href="https://splasho.com/upgoer5/">Upgoer 5 text editor</a> by Theo Sanderson, only allows 1000 most common English words.</li>
+  <li><a href="https://www.plainlanguage.gov/about/definitions/">Definition of plain language</a> by United States General Services Administration.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria_source/version-control-and-history.html b/_site/criteria_source/version-control-and-history.html
new file mode 100644
index 00000000..b993bb01
--- /dev/null
+++ b/_site/criteria_source/version-control-and-history.html
@@ -0,0 +1,386 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Maintain version control, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria_source/version-control-and-history.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+  <li><a href="#further-reading">Further reading</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/criteria_source/version-control-and-history.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `criteria_source/version-control-and-history.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="maintain-version-control">Maintain version control</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="requirements">Requirements</h2>
+
+<ul>
+  <li>The community MUST have a way to maintain <a href="/glossary.html#version-control">version control</a> for the <a href="/glossary.html#code">code</a>.</li>
+  <li>All files in the <a href="/glossary.html#codebase">codebase</a> MUST be version controlled.</li>
+  <li>All decisions MUST be documented in commit messages.</li>
+  <li>Every commit message MUST link to discussions and issues wherever possible.</li>
+  <li>The codebase SHOULD be maintained in a distributed version control system.</li>
+  <li>Contributors SHOULD group relevant changes in commits.</li>
+  <li>Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.</li>
+  <li>Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system.</li>
+  <li>It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.</li>
+</ul>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>Version control means keeping track of changes to the code over time. This allows you to create structured documentation of the history of the codebase. This is essential for collaboration at scale.</p>
+
+<p>Distributed version control enables you to:</p>
+
+<ul>
+  <li>have a full copy of the code and its history</li>
+  <li>revert to an earlier version of the codebase whenever you want to</li>
+  <li>record your changes and the reasons why you made them, to help future developers understand the process</li>
+  <li>compare two different versions</li>
+  <li>work on changes in parallel as a team before merging them together</li>
+  <li>continue to work when the network is unavailable, merging changes back with everyone else’s at a later date</li>
+</ul>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<ul>
+  <li>Substitute for <a href="/criteria_source/document-maturity.html">advertising maturity</a>.</li>
+  <li>Guarantee the code executes correctly.</li>
+  <li>Guarantee collaborators.</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<ul>
+  <li>Confirm that the codebase is kept in version control using software such as Git.</li>
+  <li>Review the commit history, confirming that all commit messages explain why the change was made.</li>
+  <li>Review the commit history, confirming that where possible all commit messages include the discussion about the change was or where to find it (with a URL).</li>
+  <li>Check if the version control system is distributed.</li>
+  <li>Review the commit history, check if grouping of relevant changes in accordance with the contributing guidelines.</li>
+  <li>Check that it is possible to access a specific version of the codebase, for example through a revision tag or a textual label.</li>
+  <li>Check that the file formats used in the codebase are text formats where possible.</li>
+</ul>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<ul>
+  <li>If a new version of the codebase is created because of a <a href="/glossary.html#policy">policy</a> change, make sure it’s clear in the documentation:
+    <ul>
+      <li>what the policy change is,</li>
+      <li>how it’s changed the codebase.</li>
+    </ul>
+  </li>
+</ul>
+
+<p>For example, adding a new category of applicant to a codebase that manages granting permits would be considered a policy change.</p>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<ul>
+  <li>Support policy makers, developers and designers to be clear about what improvements they’re making to the codebase. Making improvements isn’t a public relations risk.</li>
+</ul>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<ul>
+  <li>Write clear commit messages so that it is easy to understand why the commit was made.</li>
+  <li>Mark different versions so that it is easy to access a specific version, for example using revision tags or textual labels.</li>
+  <li>Write clear commit messages so that versions can be usefully compared.</li>
+  <li>Work with policy makers to describe how the source code was updated after a policy change.</li>
+</ul>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://producingoss.com/en/vc.html#vc-vocabulary">Producing OSS: Version Control Vocabulary</a> by Karl Fogel.</li>
+  <li><a href="https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding">Maintaining version control in coding</a> by the UK Government Digital Service.</li>
+  <li><a href="https://lab.github.com/">GitHub Learning Lab</a> by GitHub for learning how to use it or refresh your skills.</li>
+  <li><a href="https://education.github.com/git-cheat-sheet-education.pdf">Git Cheat Sheet</a> by GitHub, a list with the most common used git commands.</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/printing.html b/_site/docs/printing.html
new file mode 100644
index 00000000..850f6550
--- /dev/null
+++ b/_site/docs/printing.html
@@ -0,0 +1,309 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/printing.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/docs/printing.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `docs/printing.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<h1 id="printing">Printing</h1>
+
+<p>The printed Standard for Public Code is printed by Reclameland. This guide tries to provide the relevant information to print it there or somewhere else.</p>
+
+<p>Details, mostly in order they are on the Reclameland page with the Dutch if necessary:</p>
+
+<ul>
+  <li>Form: Softcover book (<a href="https://www.reclameland.nl/drukken/softcover-boeken">Reclameland product page</a>)</li>
+  <li>Format: A4</li>
+  <li>Portrait or landscape: Portrait (Staand)</li>
+  <li>Printing inside: 4/4 dual sided full color</li>
+  <li>Inside material: 90 grams biotop</li>
+  <li>Cover: 350 grams cover</li>
+  <li>Printing cover: 4/0 one sided full cover</li>
+  <li>Cover treatment: one sided matt foliated (Enke)</li>
+  <li>Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a multiple of 4</li>
+  <li>Individually sealed: no</li>
+</ul>
+
+<p>When these details are chosen, the cover and insides are uploaded and the order is placed payment can happen (payment ahead) after which printing starts.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/printing.md b/_site/docs/printing.md
new file mode 100644
index 00000000..66540d4e
--- /dev/null
+++ b/_site/docs/printing.md
@@ -0,0 +1,20 @@
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+# Printing
+
+The printed Standard for Public Code is printed by Reclameland. This guide tries to provide the relevant information to print it there or somewhere else.
+
+Details, mostly in order they are on the Reclameland page with the Dutch if necessary:
+
+* Form: Softcover book ([Reclameland product page](https://www.reclameland.nl/drukken/softcover-boeken))
+* Format: A4
+* Portrait or landscape: Portrait (Staand)
+* Printing inside: 4/4 dual sided full color
+* Inside material: 90 grams biotop
+* Cover: 350 grams cover
+* Printing cover: 4/0 one sided full cover
+* Cover treatment: one sided matt foliated (Enke)
+* Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a multiple of 4
+* Individually sealed: no
+
+When these details are chosen, the cover and insides are uploaded and the order is placed payment can happen (payment ahead) after which printing starts.
diff --git a/_site/docs/releasing.html b/_site/docs/releasing.html
new file mode 100644
index 00000000..0db30ecc
--- /dev/null
+++ b/_site/docs/releasing.html
@@ -0,0 +1,384 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/releasing.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/docs/releasing.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `docs/releasing.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<h1 id="releasing-a-new-version-of-the-standard-for-public-code">Releasing a new version of the Standard for public code</h1>
+
+<ol>
+  <li>Review state of the ‘develop’ branch
+    <ul>
+      <li>Ensure all changes intended for release are merged</li>
+      <li>Invite a proofread of the current state of the branch
+        <ul>
+          <li>If new dashes are introduced, check if the language can be simplified to remove them in favor of more simple sentences. If a complex sentece is needed, see if the dash can be replaced with other punction. If a dash is truly the best expression of ideas, then follow the <a href="https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash">Chicago Manual of Style</a>.</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>Create a release branch
+    <ul>
+      <li>From ‘develop’, <code class="language-plaintext highlighter-rouge">git checkout -b "release-$MAJOR.$MINOR.$PATCH"</code></li>
+      <li>Push the branch, <code class="language-plaintext highlighter-rouge">git push -u origin release-$MAJOR.$MINOR.$PATCH</code></li>
+    </ul>
+  </li>
+  <li>Update the new release
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Update version number in <code class="language-plaintext highlighter-rouge">_config.yml</code> and <code class="language-plaintext highlighter-rouge">README.md</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Update <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS.md</code></a> with new contributors</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Update <a href="/CHANGELOG.html"><code class="language-plaintext highlighter-rouge">CHANGELOG.md</code></a></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Perform extra pass on diff to the ‘main’ branch
+        <ul>
+          <li>run <code class="language-plaintext highlighter-rouge">script/generate-review-template.sh</code> and commit updated <code class="language-plaintext highlighter-rouge">docs/review-template.md</code></li>
+          <li>Reread any section or paragraph to ensure wording changes still fit the whole and do not contain grammar or spelling errors</li>
+          <li>Ensure no link collisions exist in the rendered pdf using <code class="language-plaintext highlighter-rouge">script/pdf.sh</code></li>
+          <li>If needed, commit fixes and repeat extra pass</li>
+        </ul>
+      </li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Push branch, open a pull request to the ‘main’ branch
+        <ul>
+          <li>Request review from multiple reviewers, especially a proofreader</li>
+          <li>Reviewers will create issues for shortcomings found which would not prevent release</li>
+          <li>If needed for release, reviewers may create PRs to resolve issues</li>
+          <li>Re-request reviews if additional PRs are merged into release branch</li>
+        </ul>
+      </li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Run the to-archive-org.sh script</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Once reviews are complete, merge to ‘main’</li>
+    </ul>
+  </li>
+  <li>Create GitHub release with the release notes and version number
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Switch to the ‘main’ branch, <code class="language-plaintext highlighter-rouge">git pull</code> and <code class="language-plaintext highlighter-rouge">git status</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git tag $MAJOR.$MINOR.$PATCH</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git push --tags</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />From <a href="https://github.com/publiccodenet/standard/tags">tags</a> select “create release”
+        <ul>
+          <li>Title the release: ‘Nth update’</li>
+          <li>Add changelog bullets</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>Trigger a rebuild of gh-pages
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git checkout -b rebuild-gh-pages-$MAJOR.$MINOR.$PATCH</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git commit --allow-empty -m"Rebuild GH Pages $MAJOR.$MINOR.$PATCH"</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Open a pull request from this branch to <code class="language-plaintext highlighter-rouge">main</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Approve and merge PR (containing empty commit)</li>
+    </ul>
+  </li>
+  <li>PDF Generation
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Generate new PDFs
+        <ul>
+          <li>Ensure <a href="https://brand.publiccode.net/typography/">fonts</a> are installed</li>
+          <li>Serve html content with <code class="language-plaintext highlighter-rouge">script/serve.sh</code></li>
+          <li>Optionally, for a visual pre-check, navigate to <a href="http://127.0.0.1:4000/">http://127.0.0.1:4000</a> in a browser</li>
+          <li>In a separate terminal than <code class="language-plaintext highlighter-rouge">script/serve.sh</code>, generate <code class="language-plaintext highlighter-rouge">standard.pdf</code>, <code class="language-plaintext highlighter-rouge">standard-cover.pdf</code> and <code class="language-plaintext highlighter-rouge">review-template.pdf</code> with <code class="language-plaintext highlighter-rouge">script/pdf.sh</code></li>
+          <li>Rename <code class="language-plaintext highlighter-rouge">standard.pdf</code> to <code class="language-plaintext highlighter-rouge">standard-for-public-code-$MAJOR.$MINOR.$PATCH.pdf</code></li>
+          <li>Rename <code class="language-plaintext highlighter-rouge">standard-cover.pdf</code> to <code class="language-plaintext highlighter-rouge">standard-cover-$MAJOR.$MINOR.$PATCH.pdf</code></li>
+          <li>Rename <code class="language-plaintext highlighter-rouge">review-template.pdf</code> to <code class="language-plaintext highlighter-rouge">review-template-$MAJOR.$MINOR.$PATCH.pdf</code></li>
+        </ul>
+      </li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Add PDFs to release
+        <ul>
+          <li>In a browser navigate to the release and ‘edit’</li>
+          <li>Drag-and-drop the three generated .pdfs into the assets</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>Update ‘develop’ with a merge from ‘main’</li>
+  <li><a href="/docs/printing.html">Send the files for print to the printer</a>
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Cover file</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />Inside pages PDF</li>
+    </ul>
+  </li>
+</ol>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/releasing.md b/_site/docs/releasing.md
new file mode 100644
index 00000000..a9039d88
--- /dev/null
+++ b/_site/docs/releasing.md
@@ -0,0 +1,56 @@
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+# Releasing a new version of the Standard for public code
+
+1. Review state of the 'develop' branch
+    - Ensure all changes intended for release are merged
+    - Invite a proofread of the current state of the branch
+        - If new dashes are introduced, check if the language can be simplified to remove them in favor of more simple sentences. If a complex sentece is needed, see if the dash can be replaced with other punction. If a dash is truly the best expression of ideas, then follow the [Chicago Manual of Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash).
+2. Create a release branch
+    - From 'develop', `git checkout -b "release-$MAJOR.$MINOR.$PATCH"`
+    - Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`
+3. Update the new release
+    - [ ] Update version number in `_config.yml` and `README.md`
+    - [ ] Update [`AUTHORS.md`](../AUTHORS.md) with new contributors
+    - [ ] Update [`CHANGELOG.md`](../CHANGELOG.md)
+    - [ ] Perform extra pass on diff to the 'main' branch
+        - run `script/generate-review-template.sh` and commit updated `docs/review-template.md`
+        - Reread any section or paragraph to ensure wording changes still fit the whole and do not contain grammar or spelling errors
+        - Ensure no link collisions exist in the rendered pdf using `script/pdf.sh`
+        - If needed, commit fixes and repeat extra pass
+    - [ ] Push branch, open a pull request to the 'main' branch
+        - Request review from multiple reviewers, especially a proofreader
+        - Reviewers will create issues for shortcomings found which would not prevent release
+        - If needed for release, reviewers may create PRs to resolve issues
+        - Re-request reviews if additional PRs are merged into release branch
+    - [ ] Run the to-archive-org.sh script
+    - [ ] Once reviews are complete, merge to 'main'
+4. Create GitHub release with the release notes and version number
+    - [ ] Switch to the 'main' branch, `git pull` and `git status`
+    - [ ] `git tag $MAJOR.$MINOR.$PATCH`
+    - [ ] `git push --tags`
+    - [ ] From [tags](https://github.com/publiccodenet/standard/tags) select "create release"
+        - Title the release: 'Nth update'
+        - Add changelog bullets
+5. Trigger a rebuild of gh-pages
+    - [ ] `git checkout -b rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`
+    - [ ] `git commit --allow-empty -m"Rebuild GH Pages $MAJOR.$MINOR.$PATCH"`
+    - [ ] `git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`
+    - [ ] Open a pull request from this branch to `main`
+    - [ ] Approve and merge PR (containing empty commit)
+6. PDF Generation
+    - [ ] Generate new PDFs
+        - Ensure [fonts](https://brand.publiccode.net/typography/) are installed
+        - Serve html content with `script/serve.sh`
+        - Optionally, for a visual pre-check, navigate to [http://127.0.0.1:4000](http://127.0.0.1:4000/) in a browser
+        - In a separate terminal than `script/serve.sh`, generate `standard.pdf`, `standard-cover.pdf` and `review-template.pdf` with `script/pdf.sh`
+        - Rename `standard.pdf` to `standard-for-public-code-$MAJOR.$MINOR.$PATCH.pdf`
+        - Rename `standard-cover.pdf` to `standard-cover-$MAJOR.$MINOR.$PATCH.pdf`
+        - Rename `review-template.pdf` to `review-template-$MAJOR.$MINOR.$PATCH.pdf`
+    - [ ] Add PDFs to release
+        - In a browser navigate to the release and 'edit'
+        - Drag-and-drop the three generated .pdfs into the assets
+7. Update 'develop' with a merge from 'main'
+8. [Send the files for print to the printer](printing.md)
+    - [ ] Cover file
+    - [ ] Inside pages PDF
diff --git a/_site/docs/review-template.html b/_site/docs/review-template.html
new file mode 100644
index 00000000..ddaaa5a0
--- /dev/null
+++ b/_site/docs/review-template.html
@@ -0,0 +1,1086 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>________ and the Standard for Public Code version 0.4.0, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/review-template.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#code-in-the-open">Code in the open</a></li>
+  <li><a href="#bundle-policy-and-source-code">Bundle policy and source code</a></li>
+  <li><a href="#create-reusable-and-portable-code">Create reusable and portable code</a></li>
+  <li><a href="#welcome-contributors">Welcome contributors</a></li>
+  <li><a href="#make-contributing-easy">Make contributing easy</a></li>
+  <li><a href="#maintain-version-control">Maintain version control</a></li>
+  <li><a href="#require-review-of-contributions">Require review of contributions</a></li>
+  <li><a href="#document-codebase-objectives">Document codebase objectives</a></li>
+  <li><a href="#document-the-code">Document the code</a></li>
+  <li><a href="#use-plain-english">Use plain English</a></li>
+  <li><a href="#use-open-standards">Use open standards</a></li>
+  <li><a href="#use-continuous-integration">Use continuous integration</a></li>
+  <li><a href="#publish-with-an-open-license">Publish with an open license</a></li>
+  <li><a href="#make-the-codebase-findable">Make the codebase findable</a></li>
+  <li><a href="#use-a-coherent-style">Use a coherent style</a></li>
+  <li><a href="#document-codebase-maturity">Document codebase maturity</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/docs/review-template.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `docs/review-template.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="________-and-the-standard-for-public-code-version-040">________ and the Standard for Public Code version 0.4.0</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Link to commitment to meet the Standard for Public Code:</p>
+
+<h2 id="code-in-the-open"><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the repository.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="bundle-policy-and-source-code"><a href="https://standard.publiccode.net/criteria/bundle-policy-and-code.html">Bundle policy and source code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST include the policy that the source code is based on.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include all source code that the policy is based on, unless used for fraud detection.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Policy SHOULD be provided in machine readable and unambiguous formats.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="create-reusable-and-portable-code"><a href="https://standard.publiccode.net/criteria/reusable-and-portable-codebases.html">Create reusable and portable code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be developed to be reusable in different contexts.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed code or services for execution and understanding.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be in use by multiple parties.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The roadmap SHOULD be influenced by the needs of multiple parties.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Configuration SHOULD be used to make code adapt to context specific needs.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be localizable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Code and its documentation SHOULD NOT contain situation-specific information.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="welcome-contributors"><a href="https://standard.publiccode.net/criteria/open-to-contributions.html">Welcome contributors</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST allow anyone to submit suggestions for changes to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST document the governance of the codebase, contributions and its community, for example in a <code class="language-plaintext highlighter-rouge">GOVERNANCE</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a publicly available roadmap.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD publish codebase activity statistics.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including a code of conduct for contributors in the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-contributing-easy"><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST have a public issue tracker that accepts suggestions from anyone.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include instructions for how to privately report security issues for responsible disclosure.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a <code class="language-plaintext highlighter-rouge">README</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have communication channels for users and developers, for example email lists.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="maintain-version-control"><a href="https://standard.publiccode.net/criteria/version-control-and-history.html">Maintain version control</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The community MUST have a way to maintain version control for the code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All files in the codebase MUST be version controlled.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All decisions MUST be documented in commit messages.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Every commit message MUST link to discussions and issues wherever possible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be maintained in a distributed version control system.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD group relevant changes in commits.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="require-review-of-contributions"><a href="https://standard.publiccode.net/criteria/require-review.html">Require review of contributions</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews MUST include source, policy, tests and documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviewers MUST provide feedback on all decisions to not accept a contribution.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD include running both the code and the tests of the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD be reviewed by someone in a different context than the contributor.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Version control systems SHOULD NOT accept non-reviewed contributions in release versions.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD happen within two business days.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Performing reviews by multiple reviewers is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-objectives"><a href="https://standard.publiccode.net/criteria/document-objectives.html">Document codebase objectives</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documenting the objectives of the codebase for the general public is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-the-code"><a href="https://standard.publiccode.net/criteria/documenting.html">Document the code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All of the functionality of the codebase, policy as well as source, MUST be described in language clearly understandable for those that understand the purpose of the code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain a description of how to install and run the source code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain examples demonstrating the key functionality.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain examples for all functionality.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>There SHOULD be continuous integration tests for the quality of the documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing the code by using examples in the documentation is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-plain-english"><a href="https://standard.publiccode.net/criteria/understandable-english-first.html">Use plain English</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All codebase documentation MUST be in English.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All code MUST be in English, except where policy is machine interpreted as code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All bundled policy not available in English MUST have an accompanying summary in English.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any translation MUST be up to date with the English version and vice versa.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Providing a translation of any code, documentation or tests is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-open-standards"><a href="https://standard.publiccode.net/criteria/open-standards.html">Use open standards</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any non-open standards used MUST be recorded clearly as such in the documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>If no existing open standard is available, effort SHOULD be put into developing one.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Standards that are machine testable SHOULD be preferred over those that are not.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-continuous-integration"><a href="https://standard.publiccode.net/criteria/continuous-integration.html">Use continuous integration</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All functionality in the source code MUST have automated tests.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions MUST pass all automated tests before they are admitted into the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have guidelines explaining how to structure contributions.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have active contributors.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase guidelines SHOULD state that each contribution should focus on a single issue.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Source code test and documentation coverage SHOULD be monitored.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for consistency with the source and vice versa is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for style and broken links is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="publish-with-an-open-license"><a href="https://standard.publiccode.net/criteria/open-licenses.html">Publish with an open license</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All code MUST be published with a license file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Having multiple licenses for different types of code and documentation is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-the-codebase-findable"><a href="https://standard.publiccode.net/criteria/findability.html">Make the codebase findable</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by describing the problem it solves in natural language.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by codebase name.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD submit the codebase to relevant software catalogs.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A dedicated domain name for the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Regular presentations at conferences by the community are OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-a-coherent-style"><a href="https://standard.publiccode.net/criteria/style.html">Use a coherent style</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Contributions MUST adhere to either a coding or writing style guide, either the codebase community’s own or an existing one that is advertised in or part of the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD pass automated tests on style.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include inline comments and documentation for non-trivial sections.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including sections on <a href="https://standard.publiccode.net/criteria/understandable-english-first.html">understandable English</a> in the style guide is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-maturity"><a href="https://standard.publiccode.net/criteria/document-maturity.html">Document codebase maturity</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be versioned.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase that is ready to use MUST only depend on other codebases that are also ready to use.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD contain a log of changes from version to version, for example in the <code class="language-plaintext highlighter-rouge">CHANGELOG</code>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/review-template.md b/_site/docs/review-template.md
new file mode 100644
index 00000000..179c7a70
--- /dev/null
+++ b/_site/docs/review-template.md
@@ -0,0 +1,222 @@
+# &#95;&#95;&#95;&#95;&#95;&#95;&#95;&#95; and the Standard for Public Code version 0.4.0
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+Link to commitment to meet the Standard for Public Code:
+
+## [Code in the open](https://standard.publiccode.net/criteria/code-in-the-open.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible. |  |
+All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible. |  |
+Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the repository. |  |
+Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published. |  |
+Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL. |  |
+
+## [Bundle policy and source code](https://standard.publiccode.net/criteria/bundle-policy-and-code.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST include the policy that the source code is based on. |  |
+The codebase MUST include all source code that the policy is based on, unless used for fraud detection. |  |
+Policy SHOULD be provided in machine readable and unambiguous formats. |  |
+Continuous integration tests SHOULD validate that the source code and the policy are executed coherently. |  |
+
+## [Create reusable and portable code](https://standard.publiccode.net/criteria/reusable-and-portable-codebases.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST be developed to be reusable in different contexts. |  |
+The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed code or services for execution and understanding. |  |
+The codebase SHOULD be in use by multiple parties. |  |
+The roadmap SHOULD be influenced by the needs of multiple parties. |  |
+Configuration SHOULD be used to make code adapt to context specific needs. |  |
+The codebase SHOULD be localizable. |  |
+Code and its documentation SHOULD NOT contain situation-specific information. |  |
+Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts. |  |
+
+## [Welcome contributors](https://standard.publiccode.net/criteria/open-to-contributions.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST allow anyone to submit suggestions for changes to the codebase. |  |
+The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file. |  |
+The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file. |  |
+The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance. |  |
+The codebase SHOULD have a publicly available roadmap. |  |
+The codebase SHOULD publish codebase activity statistics. |  |
+Including a code of conduct for contributors in the codebase is OPTIONAL. |  |
+
+## [Make contributing easy](https://standard.publiccode.net/criteria/make-contributing-easy.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST have a public issue tracker that accepts suggestions from anyone. |  |
+The codebase MUST include instructions for how to privately report security issues for responsible disclosure. |  |
+The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file. |  |
+The codebase MUST have communication channels for users and developers, for example email lists. |  |
+The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel. |  |
+
+## [Maintain version control](https://standard.publiccode.net/criteria/version-control-and-history.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The community MUST have a way to maintain version control for the code. |  |
+All files in the codebase MUST be version controlled. |  |
+All decisions MUST be documented in commit messages. |  |
+Every commit message MUST link to discussions and issues wherever possible. |  |
+The codebase SHOULD be maintained in a distributed version control system. |  |
+Contributors SHOULD group relevant changes in commits. |  |
+Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels. |  |
+Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system. |  |
+It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work. |  |
+
+## [Require review of contributions](https://standard.publiccode.net/criteria/require-review.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor. |  |
+Reviews MUST include source, policy, tests and documentation. |  |
+Reviewers MUST provide feedback on all decisions to not accept a contribution. |  |
+Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review. |  |
+Reviews SHOULD include running both the code and the tests of the codebase. |  |
+Contributions SHOULD be reviewed by someone in a different context than the contributor. |  |
+Version control systems SHOULD NOT accept non-reviewed contributions in release versions. |  |
+Reviews SHOULD happen within two business days. |  |
+Performing reviews by multiple reviewers is OPTIONAL. |  |
+
+## [Document codebase objectives](https://standard.publiccode.net/criteria/document-objectives.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase. |  |
+Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives. |  |
+Documenting the objectives of the codebase for the general public is OPTIONAL. |  |
+
+## [Document the code](https://standard.publiccode.net/criteria/documenting.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All of the functionality of the codebase, policy as well as source, MUST be described in language clearly understandable for those that understand the purpose of the code. |  |
+The documentation of the codebase MUST contain a description of how to install and run the source code. |  |
+The documentation of the codebase MUST contain examples demonstrating the key functionality. |  |
+The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists. |  |
+The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset. |  |
+The documentation of the codebase SHOULD contain examples for all functionality. |  |
+The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram. |  |
+There SHOULD be continuous integration tests for the quality of the documentation. |  |
+Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL. |  |
+Testing the code by using examples in the documentation is OPTIONAL. |  |
+
+## [Use plain English](https://standard.publiccode.net/criteria/understandable-english-first.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All codebase documentation MUST be in English. |  |
+All code MUST be in English, except where policy is machine interpreted as code. |  |
+All bundled policy not available in English MUST have an accompanying summary in English. |  |
+Any translation MUST be up to date with the English version and vice versa. |  |
+There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation. |  |
+The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding. |  |
+Documentation SHOULD aim for a lower secondary education reading level, as recommended by the [Web Content Accessibility Guidelines 2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable). |  |
+Providing a translation of any code, documentation or tests is OPTIONAL. |  |
+
+## [Use open standards](https://standard.publiccode.net/criteria/open-standards.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the [Open Source Initiative Open Standard Requirements](https://opensource.org/osr). |  |
+Any non-open standards used MUST be recorded clearly as such in the documentation. |  |
+Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available. |  |
+Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse. |  |
+If no existing open standard is available, effort SHOULD be put into developing one. |  |
+Standards that are machine testable SHOULD be preferred over those that are not. |  |
+
+## [Use continuous integration](https://standard.publiccode.net/criteria/continuous-integration.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All functionality in the source code MUST have automated tests. |  |
+Contributions MUST pass all automated tests before they are admitted into the codebase. |  |
+The codebase MUST have guidelines explaining how to structure contributions. |  |
+The codebase MUST have active contributors. |  |
+The codebase guidelines SHOULD state that each contribution should focus on a single issue. |  |
+Source code test and documentation coverage SHOULD be monitored. |  |
+Testing policy and documentation for consistency with the source and vice versa is OPTIONAL. |  |
+Testing policy and documentation for style and broken links is OPTIONAL. |  |
+
+## [Publish with an open license](https://standard.publiccode.net/criteria/open-licenses.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+All code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable. |  |
+Software source code MUST be licensed under an [OSI-approved or FSF Free/Libre license](https://spdx.org/licenses/). |  |
+All code MUST be published with a license file. |  |
+Contributors MUST NOT be required to transfer copyright of their contributions to the codebase. |  |
+All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable. |  |
+Having multiple licenses for different types of code and documentation is OPTIONAL. |  |
+
+## [Make the codebase findable](https://standard.publiccode.net/criteria/findability.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST be findable using a search engine by describing the problem it solves in natural language. |  |
+The codebase MUST be findable using a search engine by codebase name. |  |
+Maintainers SHOULD submit the codebase to relevant software catalogs. |  |
+The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers). |  |
+The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website. |  |
+The codebase SHOULD include a machine-readable metadata description, for example in a [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file. |  |
+A dedicated domain name for the codebase is OPTIONAL. |  |
+Regular presentations at conferences by the community are OPTIONAL. |  |
+
+## [Use a coherent style](https://standard.publiccode.net/criteria/style.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+Contributions MUST adhere to either a coding or writing style guide, either the codebase community's own or an existing one that is advertised in or part of the codebase. |  |
+Contributions SHOULD pass automated tests on style. |  |
+The codebase SHOULD include inline comments and documentation for non-trivial sections. |  |
+Including sections on [understandable English](https://standard.publiccode.net/criteria/understandable-english-first.html) in the style guide is OPTIONAL. |  |
+
+## [Document codebase maturity](https://standard.publiccode.net/criteria/document-maturity.html)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+The codebase MUST be versioned. |  |
+The codebase that is ready to use MUST only depend on other codebases that are also ready to use. |  |
+The codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version. |  |
+The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`. |  |
diff --git a/_site/docs/roadmap.html b/_site/docs/roadmap.html
new file mode 100644
index 00000000..5f0f24fd
--- /dev/null
+++ b/_site/docs/roadmap.html
@@ -0,0 +1,330 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Roadmap, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/roadmap.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#current-work">Current work</a></li>
+  <li><a href="#near-term">Near term</a></li>
+  <li><a href="#longer-term">Longer term</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/docs/roadmap.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `docs/roadmap.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="roadmap">Roadmap</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Last updated: 2022-07-11</p>
+
+<p>This document intends to shed light on the current development plans of the team.
+Plans change constantly as new information is absorbed by the team.</p>
+
+<p>Codebase stewards review the roadmap monthly as part of our <a href="https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html">backlog pruning session</a>.</p>
+
+<h2 id="current-work">Current work</h2>
+
+<ul>
+  <li>Work through the issue backlog</li>
+  <li>Separate executive summary</li>
+</ul>
+
+<h2 id="near-term">Near term</h2>
+
+<ul>
+  <li>Put “Why is this important” before requirements</li>
+  <li>Possibly: add in the illustrations for each criterion</li>
+  <li>As far as possible, make the standard Standard-compliant</li>
+</ul>
+
+<h2 id="longer-term">Longer term</h2>
+
+<ul>
+  <li>Certification badges</li>
+  <li>Physical paper checklist</li>
+  <li>Becoming validated by multiple codebases</li>
+  <li>Update criteria URLs</li>
+  <li>Linkable requirements</li>
+  <li>New cover art</li>
+  <li>Register for ISBN</li>
+  <li>List with an on-demand book printing service</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/roadmap.md b/_site/docs/roadmap.md
new file mode 100644
index 00000000..b56f87e8
--- /dev/null
+++ b/_site/docs/roadmap.md
@@ -0,0 +1,33 @@
+# Roadmap
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+Last updated: 2022-07-11
+
+This document intends to shed light on the current development plans of the team.
+Plans change constantly as new information is absorbed by the team.
+
+Codebase stewards review the roadmap monthly as part of our [backlog pruning session](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html).
+
+## Current work
+
+* Work through the issue backlog
+* Separate executive summary
+
+## Near term
+
+* Put "Why is this important" before requirements
+* Possibly: add in the illustrations for each criterion
+* As far as possible, make the standard Standard-compliant
+
+## Longer term
+
+* Certification badges
+* Physical paper checklist
+* Becoming validated by multiple codebases
+* Update criteria URLs
+* Linkable requirements
+* New cover art
+* Register for ISBN
+* List with an on-demand book printing service
diff --git a/_site/docs/standard-for-public-code.html b/_site/docs/standard-for-public-code.html
new file mode 100644
index 00000000..151e4c82
--- /dev/null
+++ b/_site/docs/standard-for-public-code.html
@@ -0,0 +1,1120 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>The Standard for Public Code’s compliance to the criteria and requirements of the Standard for Public Code version 0.4.0, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/standard-for-public-code.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#code-in-the-open">Code in the open</a></li>
+  <li><a href="#bundle-policy-and-source-code">Bundle policy and source code</a></li>
+  <li><a href="#create-reusable-and-portable-code">Create reusable and portable code</a></li>
+  <li><a href="#welcome-contributors">Welcome contributors</a></li>
+  <li><a href="#make-contributing-easy">Make contributing easy</a></li>
+  <li><a href="#maintain-version-control">Maintain version control</a></li>
+  <li><a href="#require-review-of-contributions">Require review of contributions</a></li>
+  <li><a href="#document-codebase-objectives">Document codebase objectives</a></li>
+  <li><a href="#document-the-code">Document the code</a></li>
+  <li><a href="#use-plain-english">Use plain English</a></li>
+  <li><a href="#use-open-standards">Use open standards</a></li>
+  <li><a href="#use-continuous-integration">Use continuous integration</a></li>
+  <li><a href="#publish-with-an-open-license">Publish with an open license</a></li>
+  <li><a href="#make-the-codebase-findable">Make the codebase findable</a></li>
+  <li><a href="#use-a-coherent-style">Use a coherent style</a></li>
+  <li><a href="#document-codebase-maturity">Document codebase maturity</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/docs/standard-for-public-code.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `docs/standard-for-public-code.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="the-standard-for-public-codes-compliance-to-the-criteria-and-requirements-of-the-standard-for-public-code-version-040">The Standard for Public Code’s compliance to the criteria and requirements of the Standard for Public Code version 0.4.0</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard for Public Code is not a codebase created in the context of a policy mandate, thus some criteria do not apply directly.</p>
+
+<p>Link to commitment to meet the Standard for Public Code: <a href="/CONTRIBUTING.html#1-make-your-changes">CONTRIBUTING.md</a></p>
+
+<h2 id="code-in-the-open"><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td>N/A</td>
+      <td><a href="https://github.com/publiccodenet/standard/">GitHub repository</a>, no official policy at this time</td>
+    </tr>
+    <tr>
+      <td>All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td>N/A</td>
+      <td><a href="https://github.com/publiccodenet/standard/">GitHub repository</a>, not software</td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the repository.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/releases">GitHub releases</a></td>
+    </tr>
+    <tr>
+      <td>Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="bundle-policy-and-source-code"><a href="https://standard.publiccode.net/criteria/bundle-policy-and-code.html">Bundle policy and source code</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A codebase MUST include the policy that the source code is based on.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A codebase MUST include all source code that the policy is based on, unless used for fraud detection.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Policy SHOULD be provided in machine readable and unambiguous formats.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="create-reusable-and-portable-code"><a href="https://standard.publiccode.net/criteria/reusable-and-portable-codebases.html">Create reusable and portable code</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be developed to be reusable in different contexts.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed code or services for execution and understanding.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be in use by multiple parties.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/Amsterdam/signals/blob/master/docs/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship">Signalen</a>, <a href="https://github.com/open-zaak/open-zaak/blob/main/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship">OpenZaak</a>, <a href="https://github.com/Algoritmeregister/standard#standard-for-public-code-compliance">Algoritmeregister</a>, <a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#1-make-your-changes">Standard for Public Code</a></td>
+    </tr>
+    <tr>
+      <td>The roadmap SHOULD be influenced by the needs of multiple parties.</td>
+      <td>Ok</td>
+      <td>Community calls influenced initial roadmap</td>
+    </tr>
+    <tr>
+      <td>Configuration SHOULD be used to make code adapt to context specific needs.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be localizable.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Code and its documentation SHOULD NOT contain situation-specific information.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="welcome-contributors"><a href="https://standard.publiccode.net/criteria/open-to-contributions.html">Welcome contributors</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST allow anyone to submit suggestions for changes to the codebase.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> file.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md">CONTRIBUTING</a></td>
+    </tr>
+    <tr>
+      <td>The codebase MUST document the governance of the codebase, contributions and its community, for example in a <code class="language-plaintext highlighter-rouge">GOVERNANCE</code> file.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/GOVERNANCE.md">GOVERNANCE</a></td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a publicly available roadmap.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/docs/roadmap.md">Roadmap</a></td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD publish codebase activity statistics.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/pulse">GitHub Pulse</a></td>
+    </tr>
+    <tr>
+      <td>Including a code of conduct for contributors in the codebase is OPTIONAL.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/CODE_OF_CONDUCT.md">CODE OF CONDUCT</a></td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-contributing-easy"><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST have a public issue tracker that accepts suggestions from anyone.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/issues">GitHub Issues</a></td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include instructions for how to privately report security issues for responsible disclosure.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a <code class="language-plaintext highlighter-rouge">README</code> file.</td>
+      <td>Ok</td>
+      <td>Via GitHub</td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have communication channels for users and developers, for example email lists.</td>
+      <td>Ok</td>
+      <td><a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">Mailing list</a></td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="maintain-version-control"><a href="https://standard.publiccode.net/criteria/version-control-and-history.html">Maintain version control</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The community MUST have a way to maintain version control for the code.</td>
+      <td>Ok</td>
+      <td>git</td>
+    </tr>
+    <tr>
+      <td>All files in a codebase MUST be version controlled.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All decisions MUST be documented in commit messages.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Every commit message MUST link to discussions and issues wherever possible.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be maintained in a distributed version control system.</td>
+      <td>Ok</td>
+      <td>git</td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD group relevant changes in commits.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.</td>
+      <td>Ok</td>
+      <td>GitHub releases</td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system.</td>
+      <td>Ok</td>
+      <td>(bpmn is an exception)</td>
+    </tr>
+    <tr>
+      <td>It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="require-review-of-contributions"><a href="https://standard.publiccode.net/criteria/require-review.html">Require review of contributions</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews MUST include source, policy, tests and documentation.</td>
+      <td>Ok</td>
+      <td>policy does not apply</td>
+    </tr>
+    <tr>
+      <td>Reviewers MUST provide feedback on all decisions to not accept a contribution.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD include running both the code and the tests of the codebase.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/actions">GitHub Actions</a></td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD be reviewed by someone in a different context than the contributor.</td>
+      <td>Ok</td>
+      <td>Usually in the same context, rarely get reviews from other contexts, currently no other contexts regularly available</td>
+    </tr>
+    <tr>
+      <td>Version control systems SHOULD NOT accept non-reviewed contributions in release versions.</td>
+      <td>Ok</td>
+      <td>the <code class="language-plaintext highlighter-rouge">main</code> branch is “protected”</td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD happen within two business days.</td>
+      <td>Ok</td>
+      <td>very few exceptions</td>
+    </tr>
+    <tr>
+      <td>Performing reviews by multiple reviewers is OPTIONAL.</td>
+      <td>Ok</td>
+      <td>for larger contributions</td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-objectives"><a href="https://standard.publiccode.net/criteria/document-objectives.html">Document codebase objectives</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documenting the objectives of the codebase for the general public is OPTIONAL.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-the-code"><a href="https://standard.publiccode.net/criteria/documenting.html">Document the code</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All of the functionality of the codebase, policy as well as source, MUST be described in language clearly understandable for those that understand the purpose of the code.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain a description of how to install and run the source code.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain examples demonstrating the key functionality.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain examples for all functionality.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>There SHOULD be continuous integration tests for the quality of the documentation.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/actions">GitHub Actions</a></td>
+    </tr>
+    <tr>
+      <td>Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td>We’re not linking to examples</td>
+    </tr>
+    <tr>
+      <td>Testing the code by using examples in the documentation is OPTIONAL.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-plain-english"><a href="https://standard.publiccode.net/criteria/understandable-english-first.html">Use plain English</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All codebase documentation MUST be in English.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All code MUST be in English, except where policy is machine interpreted as code.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All bundled policy not available in English MUST have an accompanying summary in English.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any translation MUST be up to date with the English version and vice versa.</td>
+      <td>N/A</td>
+      <td>Community translations lag</td>
+    </tr>
+    <tr>
+      <td>There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#style">CONTRIBUTING</a></td>
+    </tr>
+    <tr>
+      <td>Providing a translation of any code, documentation or tests is OPTIONAL.</td>
+      <td>We have <a href="https://publiccodenet.github.io/community-translations-standard/">Community translations</a></td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-open-standards"><a href="https://standard.publiccode.net/criteria/open-standards.html">Use open standards</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>For features of a codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any non-open standards used MUST be recorded clearly as such in the documentation.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.</td>
+      <td>Ok</td>
+      <td><a href="/CONTRIBUTING.html#standards-to-follow">CONTRIBUTING</a></td>
+    </tr>
+    <tr>
+      <td>Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>If no existing open standard is available, effort SHOULD be put into developing one.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Standards that are machine testable SHOULD be preferred over those that are not.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-continuous-integration"><a href="https://standard.publiccode.net/criteria/continuous-integration.html">Use continuous integration</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All functionality in the source code MUST have automated tests.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions MUST pass all automated tests before they are admitted into the codebase.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have guidelines explaining how to structure contributions.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have active contributors.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase guidelines SHOULD state that each contribution should focus on a single issue.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Source code test and documentation coverage SHOULD be monitored.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for consistency with the source and vice versa is OPTIONAL.</td>
+      <td>N/A</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for style and broken links is OPTIONAL.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="publish-with-an-open-license"><a href="https://standard.publiccode.net/criteria/open-licenses.html">Publish with an open license</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" checked="checked" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/LICENSE">CC 0</a></td>
+    </tr>
+    <tr>
+      <td>Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.</td>
+      <td>Ok</td>
+      <td>CC 0</td>
+    </tr>
+    <tr>
+      <td>All code MUST be published with a license file.</td>
+      <td>Ok</td>
+      <td>CC 0</td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Having multiple licenses for different types of code and documentation is OPTIONAL.</td>
+      <td>Ok</td>
+      <td>CC0</td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-the-codebase-findable"><a href="https://standard.publiccode.net/criteria/findability.html">Make the codebase findable</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by describing the problem it solves in natural language.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by codebase name.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD submit the codebase to relevant software catalogs.</td>
+      <td>Ok</td>
+      <td>In the <a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html">DPG registry</a></td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website.</td>
+      <td>Ok</td>
+      <td><a href="https://www.wikidata.org/wiki/Q68006929">Q68006929</a> on Wikidata</td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A dedicated domain name for the codebase is OPTIONAL.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Regular presentations at conferences by the community are OPTIONAL.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-a-coherent-style"><a href="https://standard.publiccode.net/criteria/style.html">Use a coherent style</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Contributions MUST adhere to either a coding or writing style guide, either the codebase community’s own or an existing one that is advertised in or part of the codebase.</td>
+      <td> </td>
+      <td>Some guidance, could be made clearer in the CONTRIBUTING</td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD pass automated tests on style.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include inline comments and documentation for non-trivial sections.</td>
+      <td>N/A</td>
+      <td>maybe some of the Jekyll could apply</td>
+    </tr>
+    <tr>
+      <td>Including sections on <a href="https://standard.publiccode.net/criteria/understandable-english-first.html">understandable English</a> in the style guide is OPTIONAL.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-maturity"><a href="https://standard.publiccode.net/criteria/document-maturity.html">Document codebase maturity</a></h2>
+
+<ul class="task-list">
+  <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />criterion met.</li>
+</ul>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th>links and notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A codebase MUST be versioned.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A codebase that is ready to use MUST only depend on other codebases that are also ready to use.</td>
+      <td>Ok</td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version.</td>
+      <td> </td>
+      <td>labled as “draft”, consider adding “beta” label?</td>
+    </tr>
+    <tr>
+      <td>A codebase SHOULD contain a log of changes from version to version, for example in the <code class="language-plaintext highlighter-rouge">CHANGELOG</code>.</td>
+      <td>Ok</td>
+      <td><a href="https://github.com/publiccodenet/standard/blob/develop/CHANGELOG.md">CHANGELOG</a></td>
+    </tr>
+  </tbody>
+</table>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/standard-for-public-code.md b/_site/docs/standard-for-public-code.md
new file mode 100644
index 00000000..efff89dc
--- /dev/null
+++ b/_site/docs/standard-for-public-code.md
@@ -0,0 +1,224 @@
+# The Standard for Public Code's compliance to the criteria and requirements of the Standard for Public Code version 0.4.0
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+The Standard for Public Code is not a codebase created in the context of a policy mandate, thus some criteria do not apply directly.
+
+Link to commitment to meet the Standard for Public Code: [CONTRIBUTING.md](../CONTRIBUTING.md#1-make-your-changes)
+
+## [Code in the open](https://standard.publiccode.net/criteria/code-in-the-open.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible. | N/A | [GitHub repository](https://github.com/publiccodenet/standard/), no official policy at this time
+All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible. | N/A | [GitHub repository](https://github.com/publiccodenet/standard/), not software
+Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the repository. | Ok |
+Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published. | Ok | [GitHub releases](https://github.com/publiccodenet/standard/releases)
+Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL. | N/A |
+
+## [Bundle policy and source code](https://standard.publiccode.net/criteria/bundle-policy-and-code.html)
+
+- [ ] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+A codebase MUST include the policy that the source code is based on. | N/A |
+A codebase MUST include all source code that the policy is based on, unless used for fraud detection. | N/A |
+Policy SHOULD be provided in machine readable and unambiguous formats. | N/A |
+Continuous integration tests SHOULD validate that the source code and the policy are executed coherently. | N/A |
+
+## [Create reusable and portable code](https://standard.publiccode.net/criteria/reusable-and-portable-codebases.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The codebase MUST be developed to be reusable in different contexts. | Ok |
+The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed code or services for execution and understanding. | Ok |
+The codebase SHOULD be in use by multiple parties. | Ok | [Signalen](https://github.com/Amsterdam/signals/blob/master/docs/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship), [OpenZaak](https://github.com/open-zaak/open-zaak/blob/main/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship), [Algoritmeregister](https://github.com/Algoritmeregister/standard#standard-for-public-code-compliance), [Standard for Public Code](https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#1-make-your-changes)
+The roadmap SHOULD be influenced by the needs of multiple parties. | Ok | Community calls influenced initial roadmap
+Configuration SHOULD be used to make code adapt to context specific needs. | N/A |
+The codebase SHOULD be localizable. | Ok |
+Code and its documentation SHOULD NOT contain situation-specific information. | Ok |
+Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts. | N/A |
+
+## [Welcome contributors](https://standard.publiccode.net/criteria/open-to-contributions.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The codebase MUST allow anyone to submit suggestions for changes to the codebase. | Ok |
+The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file. | Ok | [CONTRIBUTING](https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md)
+The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file. | Ok | [GOVERNANCE](https://github.com/publiccodenet/standard/blob/develop/GOVERNANCE.md)
+The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance. | Ok |
+The codebase SHOULD have a publicly available roadmap. | Ok | [Roadmap](https://github.com/publiccodenet/standard/blob/develop/docs/roadmap.md)
+The codebase SHOULD publish codebase activity statistics. | Ok | [GitHub Pulse](https://github.com/publiccodenet/standard/pulse)
+Including a code of conduct for contributors in the codebase is OPTIONAL. | Ok | [CODE OF CONDUCT](https://github.com/publiccodenet/standard/blob/develop/CODE_OF_CONDUCT.md)
+
+## [Make contributing easy](https://standard.publiccode.net/criteria/make-contributing-easy.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The codebase MUST have a public issue tracker that accepts suggestions from anyone. | Ok | [GitHub Issues](https://github.com/publiccodenet/standard/issues)
+The codebase MUST include instructions for how to privately report security issues for responsible disclosure. | N/A |
+The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file. | Ok | Via GitHub
+The codebase MUST have communication channels for users and developers, for example email lists. | Ok | [Mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)
+The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel. | N/A |
+
+## [Maintain version control](https://standard.publiccode.net/criteria/version-control-and-history.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The community MUST have a way to maintain version control for the code. | Ok | git
+All files in a codebase MUST be version controlled. | Ok |
+All decisions MUST be documented in commit messages. | Ok |
+Every commit message MUST link to discussions and issues wherever possible. | Ok |
+The codebase SHOULD be maintained in a distributed version control system. | Ok | git
+Contributors SHOULD group relevant changes in commits. | Ok |
+Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels. | Ok | GitHub releases
+Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system. | Ok | (bpmn is an exception)
+It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work. | Ok |
+
+## [Require review of contributions](https://standard.publiccode.net/criteria/require-review.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor. | Ok |
+Reviews MUST include source, policy, tests and documentation. | Ok | policy does not apply
+Reviewers MUST provide feedback on all decisions to not accept a contribution. | Ok |
+Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review. | Ok |
+Reviews SHOULD include running both the code and the tests of the codebase. | Ok | [GitHub Actions](https://github.com/publiccodenet/standard/actions)
+Contributions SHOULD be reviewed by someone in a different context than the contributor. | Ok | Usually in the same context, rarely get reviews from other contexts, currently no other contexts regularly available
+Version control systems SHOULD NOT accept non-reviewed contributions in release versions. | Ok | the `main` branch is "protected"
+Reviews SHOULD happen within two business days. | Ok | very few exceptions
+Performing reviews by multiple reviewers is OPTIONAL. | Ok | for larger contributions
+
+## [Document codebase objectives](https://standard.publiccode.net/criteria/document-objectives.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase. | Ok |
+Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives. | N/A |
+Documenting the objectives of the codebase for the general public is OPTIONAL. | Ok |
+
+## [Document the code](https://standard.publiccode.net/criteria/documenting.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All of the functionality of the codebase, policy as well as source, MUST be described in language clearly understandable for those that understand the purpose of the code. | Ok |
+The documentation of the codebase MUST contain a description of how to install and run the source code. | N/A |
+The documentation of the codebase MUST contain examples demonstrating the key functionality. | N/A |
+The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists. | Ok |
+The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset. | N/A |
+The documentation of the codebase SHOULD contain examples for all functionality. | N/A |
+The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram. | N/A |
+There SHOULD be continuous integration tests for the quality of the documentation. | Ok | [GitHub Actions](https://github.com/publiccodenet/standard/actions)
+Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL. |  | We're not linking to examples
+Testing the code by using examples in the documentation is OPTIONAL. | N/A |
+
+## [Use plain English](https://standard.publiccode.net/criteria/understandable-english-first.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All codebase documentation MUST be in English. | Ok |
+All code MUST be in English, except where policy is machine interpreted as code. | Ok |
+All bundled policy not available in English MUST have an accompanying summary in English. | N/A |
+Any translation MUST be up to date with the English version and vice versa. | N/A | Community translations lag
+There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation. | Ok |
+The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding. | Ok |
+Documentation SHOULD aim for a lower secondary education reading level, as recommended by the [Web Content Accessibility Guidelines 2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable). | Ok | [CONTRIBUTING](https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#style)
+Providing a translation of any code, documentation or tests is OPTIONAL. | We have [Community translations](https://publiccodenet.github.io/community-translations-standard/)
+
+## [Use open standards](https://standard.publiccode.net/criteria/open-standards.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+For features of a codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the [Open Source Initiative Open Standard Requirements](https://opensource.org/osr). | N/A |
+Any non-open standards used MUST be recorded clearly as such in the documentation. | N/A |
+Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available. | Ok | [CONTRIBUTING](../CONTRIBUTING.md#standards-to-follow)
+Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse. | N/A |
+If no existing open standard is available, effort SHOULD be put into developing one. | N/A |
+Standards that are machine testable SHOULD be preferred over those that are not. | N/A |
+
+## [Use continuous integration](https://standard.publiccode.net/criteria/continuous-integration.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All functionality in the source code MUST have automated tests. | Ok |
+Contributions MUST pass all automated tests before they are admitted into the codebase. | Ok |
+The codebase MUST have guidelines explaining how to structure contributions. | Ok |
+The codebase MUST have active contributors. | Ok |
+The codebase guidelines SHOULD state that each contribution should focus on a single issue. | Ok |
+Source code test and documentation coverage SHOULD be monitored. | N/A |
+Testing policy and documentation for consistency with the source and vice versa is OPTIONAL. | N/A |
+Testing policy and documentation for style and broken links is OPTIONAL. | Ok |
+
+## [Publish with an open license](https://standard.publiccode.net/criteria/open-licenses.html)
+
+- [x] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+All code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable. | Ok | [CC 0](https://github.com/publiccodenet/standard/blob/develop/LICENSE)
+Software source code MUST be licensed under an [OSI-approved or FSF Free/Libre license](https://spdx.org/licenses/). | Ok | CC 0
+All code MUST be published with a license file. | Ok | CC 0
+Contributors MUST NOT be required to transfer copyright of their contributions to the codebase. | Ok |
+All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable. | Ok |
+Having multiple licenses for different types of code and documentation is OPTIONAL. | Ok | CC0
+
+## [Make the codebase findable](https://standard.publiccode.net/criteria/findability.html)
+
+- [ ] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+The codebase MUST be findable using a search engine by describing the problem it solves in natural language. |  |
+The codebase MUST be findable using a search engine by codebase name. | Ok |
+Maintainers SHOULD submit the codebase to relevant software catalogs. | Ok | In the [DPG registry](https://digitalpublicgoods.net/registry/standard-for-public-code.html)
+The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers). | Ok |
+The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website. | Ok | [Q68006929](https://www.wikidata.org/wiki/Q68006929) on Wikidata
+The codebase SHOULD include a machine-readable metadata description, for example in a [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file. |  |
+A dedicated domain name for the codebase is OPTIONAL. | Ok |
+Regular presentations at conferences by the community are OPTIONAL. | Ok |
+
+## [Use a coherent style](https://standard.publiccode.net/criteria/style.html)
+
+- [ ] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+Contributions MUST adhere to either a coding or writing style guide, either the codebase community's own or an existing one that is advertised in or part of the codebase. |  | Some guidance, could be made clearer in the CONTRIBUTING
+Contributions SHOULD pass automated tests on style. | Ok |
+The codebase SHOULD include inline comments and documentation for non-trivial sections. | N/A | maybe some of the Jekyll could apply
+Including sections on [understandable English](https://standard.publiccode.net/criteria/understandable-english-first.html) in the style guide is OPTIONAL. | Ok |
+
+## [Document codebase maturity](https://standard.publiccode.net/criteria/document-maturity.html)
+
+- [ ] criterion met.
+
+Requirement | meets | links and notes
+-----|-----|-----
+A codebase MUST be versioned. | Ok |
+A codebase that is ready to use MUST only depend on other codebases that are also ready to use. | Ok |
+A codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version. |  | labled as "draft", consider adding "beta" label?
+A codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`. | Ok | [CHANGELOG](https://github.com/publiccodenet/standard/blob/develop/CHANGELOG.md)
diff --git a/_site/glossary.html b/_site/glossary.html
new file mode 100644
index 00000000..b4a5982c
--- /dev/null
+++ b/_site/glossary.html
@@ -0,0 +1,379 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Glossary, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/glossary.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#code">Code</a></li>
+  <li><a href="#codebase">Codebase</a></li>
+  <li><a href="#continuous-integration">Continuous integration</a></li>
+  <li><a href="#different-contexts">Different contexts</a></li>
+  <li><a href="#general-public">General public</a></li>
+  <li><a href="#open-source">Open source</a></li>
+  <li><a href="#open-standard">Open standard</a></li>
+  <li><a href="#policy">Policy</a></li>
+  <li><a href="#public-code">Public code</a></li>
+  <li><a href="#repository">Repository</a></li>
+  <li><a href="#version-control">Version control</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/glossary.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `glossary.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="glossary">Glossary</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="code">Code</h2>
+
+<p>Any explicitly described system of rules. This includes laws, policy and ordinances, as well as source code that is used to build software. Both of these are rules, some executed by humans and others by machines.</p>
+
+<h2 id="codebase">Codebase</h2>
+
+<p>Any discrete package of code (both source and policy), the tests and the documentation required to implement a piece of policy or software.</p>
+
+<p>This can be, for example, a document or a version-control repository.</p>
+
+<h2 id="continuous-integration">Continuous integration</h2>
+
+<p>In software engineering, continuous integration (CI) is the practice of merging all developers’ working copies to a development branch of a codebase as frequently as reasonable.</p>
+
+<h2 id="different-contexts">Different contexts</h2>
+
+<p>Two contexts are different if they are different public organizations or different departments for which there is not one decision maker that could make collaboration happen naturally.</p>
+
+<h2 id="general-public">General public</h2>
+
+<p>The public at large: end users of the code and the services based upon it.</p>
+
+<p>For example, a city’s residents are considered end users of a city’s services and of all code that powers these services.</p>
+
+<h2 id="open-source">Open source</h2>
+
+<p>Open source is defined by the Open Source Initiative in their <a href="https://opensource.org/osd-annotated">Open Source Definition</a>.</p>
+
+<h2 id="open-standard">Open standard</h2>
+
+<p>An open standard is any standard that meets the Open Source Initiative’s <a href="https://opensource.org/osr">Open Standard Requirements</a>.</p>
+
+<h2 id="policy">Policy</h2>
+
+<p>A policy is a deliberate system of principles to guide decisions and achieve rational outcomes.
+A policy is a statement of intent, and is implemented as a procedure or protocol.
+Policies are generally adopted by a governance body within an organization.
+Policies can assist in both subjective and objective decision making.</p>
+
+<p>Public policy is the process by which governments translate their political vision into programs and actions to deliver outcomes.</p>
+
+<p>At the national level, policy and legislation (the law) are usually separate. The distinction is often more blurred in local government.</p>
+
+<p>In the Standard the word ‘policy’ refers to policy created and adopted by public organizations such as governments and municipalities.</p>
+
+<h2 id="public-code">Public code</h2>
+
+<p>Public code is open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.</p>
+
+<p>Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.</p>
+
+<p>Public code serves the public interest, is open, legible, accountable, accessible and sustainable.</p>
+
+<p>By developing public code independently from but still implementable in the local context for which it was developed, as well as documenting the development process openly, public code can provide a building block for others to:</p>
+
+<ul>
+  <li>re-implement in their local context</li>
+  <li>take as a starting point to continue development</li>
+  <li>use as a basis for learning</li>
+</ul>
+
+<p>To facilitate reuse, public code is either released into the public domain or licensed with an open license that permits others to view and reuse the work freely and to produce derivative works.</p>
+
+<h2 id="repository">Repository</h2>
+
+<p>A repository is a storage location used by version control tools for files and metadata of a codebase.
+Repositories allow multiple developers to work on the same set of files.
+Repositories are able to store multiple versions of sets of files.</p>
+
+<h2 id="version-control">Version control</h2>
+
+<p>Version control is the management of changes to source code and the files associated with it.
+Changes are usually identified by a code, termed the <em>revision number</em> (or similar).
+Each revision is associated with the time it was made and the person making the change, thus making it easier to retrace the evolution of the code.
+Revision control systems can be used to compare different versions with each other and to see how content has changed over time.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/glossary.md b/_site/glossary.md
new file mode 100644
index 00000000..6205b910
--- /dev/null
+++ b/_site/glossary.md
@@ -0,0 +1,78 @@
+# Glossary
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+## Code
+
+Any explicitly described system of rules. This includes laws, policy and ordinances, as well as source code that is used to build software. Both of these are rules, some executed by humans and others by machines.
+
+## Codebase
+
+Any discrete package of code (both source and policy), the tests and the documentation required to implement a piece of policy or software.
+
+This can be, for example, a document or a version-control repository.
+
+## Continuous integration
+
+In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a development branch of a codebase as frequently as reasonable.
+
+## Different contexts
+
+Two contexts are different if they are different public organizations or different departments for which there is not one decision maker that could make collaboration happen naturally.
+
+## General public
+
+The public at large: end users of the code and the services based upon it.
+
+For example, a city's residents are considered end users of a city's services and of all code that powers these services.
+
+## Open source
+
+Open source is defined by the Open Source Initiative in their [Open Source Definition](https://opensource.org/osd-annotated).
+
+## Open standard
+
+An open standard is any standard that meets the Open Source Initiative's [Open Standard Requirements](https://opensource.org/osr).
+
+## Policy
+
+A policy is a deliberate system of principles to guide decisions and achieve rational outcomes.
+A policy is a statement of intent, and is implemented as a procedure or protocol.
+Policies are generally adopted by a governance body within an organization.
+Policies can assist in both subjective and objective decision making.
+
+Public policy is the process by which governments translate their political vision into programs and actions to deliver outcomes.
+
+At the national level, policy and legislation (the law) are usually separate. The distinction is often more blurred in local government.
+
+In the Standard the word 'policy' refers to policy created and adopted by public organizations such as governments and municipalities.
+
+## Public code
+
+Public code is open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+
+Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+
+Public code serves the public interest, is open, legible, accountable, accessible and sustainable.
+
+By developing public code independently from but still implementable in the local context for which it was developed, as well as documenting the development process openly, public code can provide a building block for others to:
+
+* re-implement in their local context
+* take as a starting point to continue development
+* use as a basis for learning
+
+To facilitate reuse, public code is either released into the public domain or licensed with an open license that permits others to view and reuse the work freely and to produce derivative works.
+
+## Repository
+
+A repository is a storage location used by version control tools for files and metadata of a codebase.
+Repositories allow multiple developers to work on the same set of files.
+Repositories are able to store multiple versions of sets of files.
+
+## Version control
+
+Version control is the management of changes to source code and the files associated with it.
+Changes are usually identified by a code, termed the *revision number* (or similar).
+Each revision is associated with the time it was made and the person making the change, thus making it easier to retrace the evolution of the code.
+Revision control systems can be used to compare different versions with each other and to see how content has changed over time.
diff --git a/_site/images/audit-flow.dot b/_site/images/audit-flow.dot
new file mode 100644
index 00000000..553b2747
--- /dev/null
+++ b/_site/images/audit-flow.dot
@@ -0,0 +1,198 @@
+/* audit-flow-dot */
+/* SPDX-License-Identifier: CC0-1.0 */
+/* 2022 The Foundation for Public Code <info@publiccode.net> */
+
+/* To generate the audit-flow.svg, run the following command: */
+/* dot audit-flow.dot -Tsvg -o audit-flow.svg */
+
+digraph {
+	fontname = "Arial";
+
+	contrib_context [
+		fontname = "Arial"
+		label = "Merge request to a\n'protected branch' or\nFoundation for\nPublic Code\nmanaged codebase"
+	];
+	contrib_submit [
+		fontname = "Arial"
+		label = "Contributor submits\na merge request"
+	];
+	contrib_fix [
+		fontname = "Arial"
+		label = "Make new commits to the code to\nresolve review and audit issues"
+	];
+	contrib_update [
+		fontname = "Arial"
+		label = "Request\nupdated"
+	];
+
+	audit_assign [
+		fontname = "Arial"
+		label = "Auditor team member\nassigns merge request\nto themselves within\n2 business days"
+	];
+	audit_check [
+		fontname = "Arial"
+		label = "Check changes for\ncodebase governance and\nStandard for Public Code\ncompliance"
+	];
+	audit_check_fail [
+		fontname = "Arial"
+		label = "Post what needs to be\ndone so the contributor\ncan make the changes"
+	];
+	maint_check_fail [
+		fontname = "Arial"
+		label = "Post what needs to be\ndone so the contributor\ncan make the changes"
+	];
+	audit_changes_requested [
+		fontname = "Arial"
+		label = "Set request status to\n'Changes requested'"
+	];
+	maint_changes_requested [
+		fontname = "Arial"
+		label = "Set request status to\n'Changes requested'"
+	];
+	audit_check_pass [
+		fontname = "Arial"
+		label = "Set request status\nto 'approved' and\npost positively"
+	];
+	maint_check_pass [
+		fontname = "Arial"
+		label = "Set request status\nto 'approved' and\npost positively"
+	];
+	maint_check [
+		fontname = "Arial"
+		label = "Maintainer checks changes\nfor usefulness,\nvalue added and\n'mergeability'"
+	];
+	maint_merge [
+		fontname = "Arial"
+		label = "Merge"
+	];
+	maint_check_reject [
+		fontname = "Arial"
+		label = "Post why the request\ncannot be merged\nand close it"
+	];
+	maint_request_rejected [
+		fontname = "Arial"
+		label = "Merge\nrequest\nrejected"
+	];
+	maint_request_merged [
+		fontname = "Arial"
+		label = "Merge\nrequest\nmerged"
+	];
+
+
+	subgraph cluster_contrib {
+		fontname = "Arial";
+		label = "Contributor";
+
+		contrib_context [ shape = "rectangle" ];
+		contrib_submit;
+		subgraph cluster_contrib_update {
+			label = "";
+			style = "invis";
+			contrib_fix;
+			contrib_update;
+			contrib_submit_join;
+		}
+	}
+
+	subgraph cluster_audit {
+		fontname = "Arial";
+		label = "Auditor\n(staff)";
+
+		audit_assign;
+		audit_check;
+		audit_check_branch;
+		audit_check_pass;
+		audit_check_fail;
+		audit_changes_requested;
+		audit_changes_req_join;
+	}
+
+	subgraph cluster_maint {
+		fontname = "Arial";
+		label = "Maintainers\n(community or staff)";
+
+		maint_check;
+		maint_check_branch;
+		maint_check_pass;
+		maint_pass_join;
+		maint_merge;
+		maint_request_merged [ shape = "circle" style = "bold" ];
+		maint_check_fail;
+		maint_changes_requested;
+		maint_check_reject;
+		maint_request_rejected [ shape = "circle" style = "bold" ];
+	}
+
+	contrib_submit_join [
+		shape = "diamond"
+		fontname = "Arial"
+		label = "+"
+	];
+	audit_check_branch [
+		shape = "diamond"
+		fontname = "Arial"
+		label = "X"
+	];
+	audit_changes_req_join [
+		shape = "diamond"
+		fontname = "Arial"
+		label = "O"
+	];
+	maint_pass_join [
+		shape = "diamond"
+		fontname = "Arial"
+		label = "+"
+	];
+	maint_check_branch [
+		shape = "diamond"
+		fontname = "Arial"
+		label = "X"
+	];
+
+	/* graph connections (edges) */
+	contrib_context -> contrib_submit [
+		style = "dashed"
+		arrowhead = "none"
+	];
+	contrib_submit -> contrib_submit_join;
+	contrib_submit_join -> audit_assign;
+	contrib_submit_join -> maint_check;
+	contrib_fix -> contrib_update;
+	contrib_update -> contrib_submit_join;
+
+	audit_assign -> audit_check;
+	audit_check -> audit_check_branch;
+	audit_check_branch -> audit_check_pass [
+		fontname = "Arial"
+		label = "Compliant"
+	];
+	audit_check_branch -> audit_check_fail [
+		fontname = "Arial"
+		label = "Not compliant"
+	];
+	audit_check_pass -> maint_pass_join;
+	audit_check_fail -> audit_changes_requested;
+	audit_changes_requested -> audit_changes_req_join;
+	audit_changes_req_join -> contrib_fix;
+
+	maint_check -> maint_check_branch;
+	maint_check_branch -> maint_check_pass [
+		fontname = "Arial"
+		label = "Can\nbe merged"
+	];
+	maint_check_branch -> maint_check_fail [
+		fontname = "Arial"
+		label = "Needs\nchanges"
+	];
+	maint_check_branch -> maint_check_reject [
+		fontname = "Arial"
+		label = "Cannot\nbe merged"
+	];
+	maint_check_pass -> maint_pass_join;
+	maint_pass_join -> maint_merge;
+	maint_merge -> maint_request_merged;
+	maint_check_fail -> maint_changes_requested;
+	maint_changes_requested -> audit_changes_req_join;
+	maint_check_reject -> maint_request_rejected;
+
+}
diff --git a/_site/images/audit-flow.svg b/_site/images/audit-flow.svg
new file mode 100644
index 00000000..5c3f89b2
--- /dev/null
+++ b/_site/images/audit-flow.svg
@@ -0,0 +1,348 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
+ "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+<!-- Generated by graphviz version 2.43.0 (0)
+ -->
+<!-- Title: %3 Pages: 1 -->
+<svg width="1125pt" height="1117pt"
+ viewBox="0.00 0.00 1125.00 1117.05" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+<g id="graph0" class="graph" transform="scale(1 1) rotate(0) translate(4 1113.05)">
+<title>%3</title>
+<polygon fill="white" stroke="transparent" points="-4,4 -4,-1113.05 1121,-1113.05 1121,4 -4,4"/>
+<g id="clust1" class="cluster">
+<title>cluster_contrib</title>
+<polygon fill="none" stroke="black" points="117,-741.22 117,-1101.05 659,-1101.05 659,-741.22 117,-741.22"/>
+<text text-anchor="middle" x="388" y="-1085.85" font-family="Arial" font-size="14.00">Contributor</text>
+</g>
+<g id="clust2" class="cluster">
+<title>cluster_contrib_update</title>
+</g>
+<g id="clust3" class="cluster">
+<title>cluster_audit</title>
+<polygon fill="none" stroke="black" points="667,-134.1 667,-869.31 1097,-869.31 1097,-134.1 667,-134.1"/>
+<text text-anchor="middle" x="882" y="-854.11" font-family="Arial" font-size="14.00">Auditor</text>
+<text text-anchor="middle" x="882" y="-839.11" font-family="Arial" font-size="14.00">(staff)</text>
+</g>
+<g id="clust4" class="cluster">
+<title>cluster_maint</title>
+<polygon fill="none" stroke="black" points="8,-8 8,-700.14 659,-700.14 659,-8 8,-8"/>
+<text text-anchor="middle" x="333.5" y="-684.94" font-family="Arial" font-size="14.00">Maintainers</text>
+<text text-anchor="middle" x="333.5" y="-669.94" font-family="Arial" font-size="14.00">(community or staff)</text>
+</g>
+<!-- contrib_context -->
+<g id="node1" class="node">
+<title>contrib_context</title>
+<polygon fill="none" stroke="black" points="290,-1070.05 150,-1070.05 150,-987.05 290,-987.05 290,-1070.05"/>
+<text text-anchor="middle" x="220" y="-1054.85" font-family="Arial" font-size="14.00">Merge request to a</text>
+<text text-anchor="middle" x="220" y="-1039.85" font-family="Arial" font-size="14.00">&#39;protected branch&#39; or</text>
+<text text-anchor="middle" x="220" y="-1024.85" font-family="Arial" font-size="14.00">Foundation for</text>
+<text text-anchor="middle" x="220" y="-1009.85" font-family="Arial" font-size="14.00">Public Code</text>
+<text text-anchor="middle" x="220" y="-994.85" font-family="Arial" font-size="14.00">managed codebase</text>
+</g>
+<!-- contrib_submit -->
+<g id="node2" class="node">
+<title>contrib_submit</title>
+<ellipse fill="none" stroke="black" cx="220" cy="-923.18" rx="94.51" ry="26.74"/>
+<text text-anchor="middle" x="220" y="-926.98" font-family="Arial" font-size="14.00">Contributor submits</text>
+<text text-anchor="middle" x="220" y="-911.98" font-family="Arial" font-size="14.00">a merge request</text>
+</g>
+<!-- contrib_context&#45;&gt;contrib_submit -->
+<g id="edge1" class="edge">
+<title>contrib_context&#45;&gt;contrib_submit</title>
+<path fill="none" stroke="black" stroke-dasharray="5,2" d="M220,-986.99C220,-974.66 220,-961.44 220,-950.33"/>
+</g>
+<!-- contrib_submit_join -->
+<g id="node18" class="node">
+<title>contrib_submit_join</title>
+<polygon fill="none" stroke="black" points="422,-793.22 395,-775.22 422,-757.22 449,-775.22 422,-793.22"/>
+<text text-anchor="middle" x="422" y="-771.52" font-family="Arial" font-size="14.00">+</text>
+</g>
+<!-- contrib_submit&#45;&gt;contrib_submit_join -->
+<g id="edge2" class="edge">
+<title>contrib_submit&#45;&gt;contrib_submit_join</title>
+<path fill="none" stroke="black" d="M253.81,-897.75C295.88,-867.35 366.4,-816.4 401.23,-791.23"/>
+<polygon fill="black" stroke="black" points="403.62,-793.82 409.67,-785.13 399.52,-788.15 403.62,-793.82"/>
+</g>
+<!-- contrib_fix -->
+<g id="node3" class="node">
+<title>contrib_fix</title>
+<ellipse fill="none" stroke="black" cx="487" cy="-1028.55" rx="155.63" ry="26.74"/>
+<text text-anchor="middle" x="487" y="-1032.35" font-family="Arial" font-size="14.00">Make new commits to the code to</text>
+<text text-anchor="middle" x="487" y="-1017.35" font-family="Arial" font-size="14.00">resolve review and audit issues</text>
+</g>
+<!-- contrib_update -->
+<g id="node4" class="node">
+<title>contrib_update</title>
+<ellipse fill="none" stroke="black" cx="463" cy="-923.18" rx="47.25" ry="26.74"/>
+<text text-anchor="middle" x="463" y="-926.98" font-family="Arial" font-size="14.00">Request</text>
+<text text-anchor="middle" x="463" y="-911.98" font-family="Arial" font-size="14.00">updated</text>
+</g>
+<!-- contrib_fix&#45;&gt;contrib_update -->
+<g id="edge5" class="edge">
+<title>contrib_fix&#45;&gt;contrib_update</title>
+<path fill="none" stroke="black" d="M481.48,-1001.44C479.23,-991.03 476.56,-978.96 474,-968.05 473.38,-965.41 472.73,-962.69 472.07,-959.96"/>
+<polygon fill="black" stroke="black" points="475.44,-959 469.65,-950.13 468.64,-960.67 475.44,-959"/>
+</g>
+<!-- contrib_update&#45;&gt;contrib_submit_join -->
+<g id="edge6" class="edge">
+<title>contrib_update&#45;&gt;contrib_submit_join</title>
+<path fill="none" stroke="black" d="M455.76,-896.42C448.13,-869.25 436.21,-826.79 428.76,-800.28"/>
+<polygon fill="black" stroke="black" points="432.13,-799.33 426.05,-790.65 425.39,-801.22 432.13,-799.33"/>
+</g>
+<!-- audit_assign -->
+<g id="node5" class="node">
+<title>audit_assign</title>
+<ellipse fill="none" stroke="black" cx="788" cy="-775.22" rx="108.79" ry="48.17"/>
+<text text-anchor="middle" x="788" y="-794.02" font-family="Arial" font-size="14.00">Auditor team member</text>
+<text text-anchor="middle" x="788" y="-779.02" font-family="Arial" font-size="14.00">assigns merge request</text>
+<text text-anchor="middle" x="788" y="-764.02" font-family="Arial" font-size="14.00">to themselves within</text>
+<text text-anchor="middle" x="788" y="-749.02" font-family="Arial" font-size="14.00">2 business days</text>
+</g>
+<!-- audit_check -->
+<g id="node6" class="node">
+<title>audit_check</title>
+<ellipse fill="none" stroke="black" cx="799" cy="-606.06" rx="124.4" ry="48.17"/>
+<text text-anchor="middle" x="799" y="-624.86" font-family="Arial" font-size="14.00">Check changes for</text>
+<text text-anchor="middle" x="799" y="-609.86" font-family="Arial" font-size="14.00">codebase governance and</text>
+<text text-anchor="middle" x="799" y="-594.86" font-family="Arial" font-size="14.00">Standard for Public Code</text>
+<text text-anchor="middle" x="799" y="-579.86" font-family="Arial" font-size="14.00">compliance</text>
+</g>
+<!-- audit_assign&#45;&gt;audit_check -->
+<g id="edge7" class="edge">
+<title>audit_assign&#45;&gt;audit_check</title>
+<path fill="none" stroke="black" d="M791.12,-726.77C792.4,-707.36 793.89,-684.74 795.23,-664.42"/>
+<polygon fill="black" stroke="black" points="798.72,-664.55 795.89,-654.34 791.74,-664.09 798.72,-664.55"/>
+</g>
+<!-- audit_check_branch -->
+<g id="node19" class="node">
+<title>audit_check_branch</title>
+<polygon fill="none" stroke="black" points="799,-520.97 772,-502.97 799,-484.97 826,-502.97 799,-520.97"/>
+<text text-anchor="middle" x="799" y="-499.27" font-family="Arial" font-size="14.00">X</text>
+</g>
+<!-- audit_check&#45;&gt;audit_check_branch -->
+<g id="edge8" class="edge">
+<title>audit_check&#45;&gt;audit_check_branch</title>
+<path fill="none" stroke="black" d="M799,-557.77C799,-548.62 799,-539.33 799,-531.11"/>
+<polygon fill="black" stroke="black" points="802.5,-531.01 799,-521.01 795.5,-531.01 802.5,-531.01"/>
+</g>
+<!-- audit_check_fail -->
+<g id="node7" class="node">
+<title>audit_check_fail</title>
+<ellipse fill="none" stroke="black" cx="979" cy="-381.5" rx="109.7" ry="37.45"/>
+<text text-anchor="middle" x="979" y="-392.8" font-family="Arial" font-size="14.00">Post what needs to be</text>
+<text text-anchor="middle" x="979" y="-377.8" font-family="Arial" font-size="14.00">done so the contributor</text>
+<text text-anchor="middle" x="979" y="-362.8" font-family="Arial" font-size="14.00">can make the changes</text>
+</g>
+<!-- audit_changes_requested -->
+<g id="node9" class="node">
+<title>audit_changes_requested</title>
+<ellipse fill="none" stroke="black" cx="979" cy="-261.06" rx="98.99" ry="26.74"/>
+<text text-anchor="middle" x="979" y="-264.86" font-family="Arial" font-size="14.00">Set request status to</text>
+<text text-anchor="middle" x="979" y="-249.86" font-family="Arial" font-size="14.00">&#39;Changes requested&#39;</text>
+</g>
+<!-- audit_check_fail&#45;&gt;audit_changes_requested -->
+<g id="edge12" class="edge">
+<title>audit_check_fail&#45;&gt;audit_changes_requested</title>
+<path fill="none" stroke="black" d="M979,-343.99C979,-329.45 979,-312.74 979,-298.23"/>
+<polygon fill="black" stroke="black" points="982.5,-298.11 979,-288.11 975.5,-298.11 982.5,-298.11"/>
+</g>
+<!-- maint_check_fail -->
+<g id="node8" class="node">
+<title>maint_check_fail</title>
+<ellipse fill="none" stroke="black" cx="541" cy="-381.5" rx="109.7" ry="37.45"/>
+<text text-anchor="middle" x="541" y="-392.8" font-family="Arial" font-size="14.00">Post what needs to be</text>
+<text text-anchor="middle" x="541" y="-377.8" font-family="Arial" font-size="14.00">done so the contributor</text>
+<text text-anchor="middle" x="541" y="-362.8" font-family="Arial" font-size="14.00">can make the changes</text>
+</g>
+<!-- maint_changes_requested -->
+<g id="node10" class="node">
+<title>maint_changes_requested</title>
+<ellipse fill="none" stroke="black" cx="549" cy="-261.06" rx="98.99" ry="26.74"/>
+<text text-anchor="middle" x="549" y="-264.86" font-family="Arial" font-size="14.00">Set request status to</text>
+<text text-anchor="middle" x="549" y="-249.86" font-family="Arial" font-size="14.00">&#39;Changes requested&#39;</text>
+</g>
+<!-- maint_check_fail&#45;&gt;maint_changes_requested -->
+<g id="edge22" class="edge">
+<title>maint_check_fail&#45;&gt;maint_changes_requested</title>
+<path fill="none" stroke="black" d="M543.47,-343.99C544.45,-329.45 545.58,-312.74 546.56,-298.23"/>
+<polygon fill="black" stroke="black" points="550.06,-298.32 547.24,-288.11 543.07,-297.85 550.06,-298.32"/>
+</g>
+<!-- audit_changes_req_join -->
+<g id="node20" class="node">
+<title>audit_changes_req_join</title>
+<polygon fill="none" stroke="black" points="979,-178.1 952,-160.1 979,-142.1 1006,-160.1 979,-178.1"/>
+<text text-anchor="middle" x="979" y="-156.4" font-family="Arial" font-size="14.00">O</text>
+</g>
+<!-- audit_changes_requested&#45;&gt;audit_changes_req_join -->
+<g id="edge13" class="edge">
+<title>audit_changes_requested&#45;&gt;audit_changes_req_join</title>
+<path fill="none" stroke="black" d="M979,-234.06C979,-220 979,-202.65 979,-188.4"/>
+<polygon fill="black" stroke="black" points="982.5,-188.21 979,-178.21 975.5,-188.21 982.5,-188.21"/>
+</g>
+<!-- maint_changes_requested&#45;&gt;audit_changes_req_join -->
+<g id="edge23" class="edge">
+<title>maint_changes_requested&#45;&gt;audit_changes_req_join</title>
+<path fill="none" stroke="black" d="M599.02,-237.74C618.66,-229.67 641.59,-221.08 663,-215.1 764.43,-186.76 888.56,-170.81 946.42,-164.42"/>
+<polygon fill="black" stroke="black" points="946.86,-167.89 956.43,-163.33 946.11,-160.93 946.86,-167.89"/>
+</g>
+<!-- audit_check_pass -->
+<g id="node11" class="node">
+<title>audit_check_pass</title>
+<ellipse fill="none" stroke="black" cx="763" cy="-381.5" rx="88.28" ry="37.45"/>
+<text text-anchor="middle" x="763" y="-392.8" font-family="Arial" font-size="14.00">Set request status</text>
+<text text-anchor="middle" x="763" y="-377.8" font-family="Arial" font-size="14.00">to &#39;approved&#39; and</text>
+<text text-anchor="middle" x="763" y="-362.8" font-family="Arial" font-size="14.00">post positively</text>
+</g>
+<!-- maint_pass_join -->
+<g id="node22" class="node">
+<title>maint_pass_join</title>
+<polygon fill="none" stroke="black" points="384,-279.06 357,-261.06 384,-243.06 411,-261.06 384,-279.06"/>
+<text text-anchor="middle" x="384" y="-257.36" font-family="Arial" font-size="14.00">+</text>
+</g>
+<!-- audit_check_pass&#45;&gt;maint_pass_join -->
+<g id="edge11" class="edge">
+<title>audit_check_pass&#45;&gt;maint_pass_join</title>
+<path fill="none" stroke="black" d="M699.54,-355.36C687.53,-351.17 674.97,-347.17 663,-344.02 566.27,-318.55 532.48,-347.49 441,-307.02 426.3,-300.52 412.11,-289.34 401.56,-279.76"/>
+<polygon fill="black" stroke="black" points="403.92,-277.17 394.25,-272.84 399.11,-282.26 403.92,-277.17"/>
+</g>
+<!-- maint_check_pass -->
+<g id="node12" class="node">
+<title>maint_check_pass</title>
+<ellipse fill="none" stroke="black" cx="325" cy="-381.5" rx="88.28" ry="37.45"/>
+<text text-anchor="middle" x="325" y="-392.8" font-family="Arial" font-size="14.00">Set request status</text>
+<text text-anchor="middle" x="325" y="-377.8" font-family="Arial" font-size="14.00">to &#39;approved&#39; and</text>
+<text text-anchor="middle" x="325" y="-362.8" font-family="Arial" font-size="14.00">post positively</text>
+</g>
+<!-- maint_check_pass&#45;&gt;maint_pass_join -->
+<g id="edge19" class="edge">
+<title>maint_check_pass&#45;&gt;maint_pass_join</title>
+<path fill="none" stroke="black" d="M342.86,-344.64C352.67,-324.95 364.53,-301.15 372.99,-284.17"/>
+<polygon fill="black" stroke="black" points="376.21,-285.55 377.53,-275.04 369.94,-282.43 376.21,-285.55"/>
+</g>
+<!-- maint_check -->
+<g id="node13" class="node">
+<title>maint_check</title>
+<ellipse fill="none" stroke="black" cx="394" cy="-606.06" rx="127.97" ry="48.17"/>
+<text text-anchor="middle" x="394" y="-624.86" font-family="Arial" font-size="14.00">Maintainer checks changes</text>
+<text text-anchor="middle" x="394" y="-609.86" font-family="Arial" font-size="14.00">for usefulness,</text>
+<text text-anchor="middle" x="394" y="-594.86" font-family="Arial" font-size="14.00">value added and</text>
+<text text-anchor="middle" x="394" y="-579.86" font-family="Arial" font-size="14.00">&#39;mergeability&#39;</text>
+</g>
+<!-- maint_check_branch -->
+<g id="node21" class="node">
+<title>maint_check_branch</title>
+<polygon fill="none" stroke="black" points="334,-520.97 307,-502.97 334,-484.97 361,-502.97 334,-520.97"/>
+<text text-anchor="middle" x="334" y="-499.27" font-family="Arial" font-size="14.00">X</text>
+</g>
+<!-- maint_check&#45;&gt;maint_check_branch -->
+<g id="edge15" class="edge">
+<title>maint_check&#45;&gt;maint_check_branch</title>
+<path fill="none" stroke="black" d="M366.63,-558.95C359.61,-547.11 352.39,-534.95 346.53,-525.08"/>
+<polygon fill="black" stroke="black" points="349.5,-523.22 341.38,-516.41 343.48,-526.8 349.5,-523.22"/>
+</g>
+<!-- maint_merge -->
+<g id="node14" class="node">
+<title>maint_merge</title>
+<ellipse fill="none" stroke="black" cx="384" cy="-160.1" rx="36.29" ry="18"/>
+<text text-anchor="middle" x="384" y="-156.4" font-family="Arial" font-size="14.00">Merge</text>
+</g>
+<!-- maint_request_merged -->
+<g id="node17" class="node">
+<title>maint_request_merged</title>
+<ellipse fill="none" stroke="black" stroke-width="2" cx="384" cy="-60.55" rx="44.6" ry="44.6"/>
+<text text-anchor="middle" x="384" y="-71.85" font-family="Arial" font-size="14.00">Merge</text>
+<text text-anchor="middle" x="384" y="-56.85" font-family="Arial" font-size="14.00">request</text>
+<text text-anchor="middle" x="384" y="-41.85" font-family="Arial" font-size="14.00">merged</text>
+</g>
+<!-- maint_merge&#45;&gt;maint_request_merged -->
+<g id="edge21" class="edge">
+<title>maint_merge&#45;&gt;maint_request_merged</title>
+<path fill="none" stroke="black" d="M384,-141.66C384,-134.17 384,-124.98 384,-115.52"/>
+<polygon fill="black" stroke="black" points="387.5,-115.22 384,-105.22 380.5,-115.22 387.5,-115.22"/>
+</g>
+<!-- maint_check_reject -->
+<g id="node15" class="node">
+<title>maint_check_reject</title>
+<ellipse fill="none" stroke="black" cx="117" cy="-381.5" rx="101.23" ry="37.45"/>
+<text text-anchor="middle" x="117" y="-392.8" font-family="Arial" font-size="14.00">Post why the request</text>
+<text text-anchor="middle" x="117" y="-377.8" font-family="Arial" font-size="14.00">cannot be merged</text>
+<text text-anchor="middle" x="117" y="-362.8" font-family="Arial" font-size="14.00">and close it</text>
+</g>
+<!-- maint_request_rejected -->
+<g id="node16" class="node">
+<title>maint_request_rejected</title>
+<ellipse fill="none" stroke="black" stroke-width="2" cx="117" cy="-261.06" rx="45.92" ry="45.92"/>
+<text text-anchor="middle" x="117" y="-272.36" font-family="Arial" font-size="14.00">Merge</text>
+<text text-anchor="middle" x="117" y="-257.36" font-family="Arial" font-size="14.00">request</text>
+<text text-anchor="middle" x="117" y="-242.36" font-family="Arial" font-size="14.00">rejected</text>
+</g>
+<!-- maint_check_reject&#45;&gt;maint_request_rejected -->
+<g id="edge24" class="edge">
+<title>maint_check_reject&#45;&gt;maint_request_rejected</title>
+<path fill="none" stroke="black" d="M117,-343.99C117,-335.6 117,-326.49 117,-317.49"/>
+<polygon fill="black" stroke="black" points="120.5,-317.43 117,-307.43 113.5,-317.43 120.5,-317.43"/>
+</g>
+<!-- contrib_submit_join&#45;&gt;audit_assign -->
+<g id="edge3" class="edge">
+<title>contrib_submit_join&#45;&gt;audit_assign</title>
+<path fill="none" stroke="black" d="M449.16,-775.22C522.27,-775.22 595.38,-775.22 668.49,-775.22"/>
+<polygon fill="black" stroke="black" points="668.8,-778.72 678.8,-775.22 668.8,-771.72 668.8,-778.72"/>
+</g>
+<!-- contrib_submit_join&#45;&gt;maint_check -->
+<g id="edge4" class="edge">
+<title>contrib_submit_join&#45;&gt;maint_check</title>
+<path fill="none" stroke="black" d="M419.42,-758.8C415.85,-737.48 409.21,-697.87 403.61,-664.46"/>
+<polygon fill="black" stroke="black" points="407.02,-663.6 401.92,-654.32 400.12,-664.76 407.02,-663.6"/>
+</g>
+<!-- audit_check_branch&#45;&gt;audit_check_fail -->
+<g id="edge10" class="edge">
+<title>audit_check_branch&#45;&gt;audit_check_fail</title>
+<path fill="none" stroke="black" d="M812.18,-493.73C823.36,-486.7 839.8,-476.28 854,-466.97 876.62,-452.13 901.34,-435.52 922.78,-420.97"/>
+<polygon fill="black" stroke="black" points="924.82,-423.81 931.13,-415.3 920.89,-418.02 924.82,-423.81"/>
+<text text-anchor="middle" x="940" y="-448.27" font-family="Arial" font-size="14.00">Not compliant</text>
+</g>
+<!-- audit_check_branch&#45;&gt;audit_check_pass -->
+<g id="edge9" class="edge">
+<title>audit_check_branch&#45;&gt;audit_check_pass</title>
+<path fill="none" stroke="black" d="M794.73,-487.8C790.34,-473.23 783.27,-449.76 776.91,-428.67"/>
+<polygon fill="black" stroke="black" points="780.2,-427.44 773.96,-418.88 773.5,-429.46 780.2,-427.44"/>
+<text text-anchor="middle" x="819" y="-448.27" font-family="Arial" font-size="14.00">Compliant</text>
+</g>
+<!-- audit_changes_req_join&#45;&gt;contrib_fix -->
+<g id="edge14" class="edge">
+<title>audit_changes_req_join&#45;&gt;contrib_fix</title>
+<path fill="none" stroke="black" d="M998.19,-165.33C1036.11,-174.96 1117,-202.27 1117,-260.06 1117,-924.18 1117,-924.18 1117,-924.18 1117,-972.3 827.03,-1002.71 640.54,-1017.28"/>
+<polygon fill="black" stroke="black" points="640.05,-1013.81 630.35,-1018.07 640.59,-1020.79 640.05,-1013.81"/>
+</g>
+<!-- maint_check_branch&#45;&gt;maint_check_fail -->
+<g id="edge17" class="edge">
+<title>maint_check_branch&#45;&gt;maint_check_fail</title>
+<path fill="none" stroke="black" d="M348.78,-494.58C362.45,-487.67 383.27,-476.94 401,-466.97 427.34,-452.17 455.97,-435.07 480.44,-420.15"/>
+<polygon fill="black" stroke="black" points="482.55,-422.96 489.26,-414.76 478.9,-416.99 482.55,-422.96"/>
+<text text-anchor="middle" x="477" y="-455.77" font-family="Arial" font-size="14.00">Needs</text>
+<text text-anchor="middle" x="477" y="-440.77" font-family="Arial" font-size="14.00">changes</text>
+</g>
+<!-- maint_check_branch&#45;&gt;maint_check_pass -->
+<g id="edge16" class="edge">
+<title>maint_check_branch&#45;&gt;maint_check_pass</title>
+<path fill="none" stroke="black" d="M332.75,-485.36C331.65,-470.84 330.01,-449.03 328.52,-429.23"/>
+<polygon fill="black" stroke="black" points="332,-428.81 327.76,-419.1 325.02,-429.34 332,-428.81"/>
+<text text-anchor="middle" x="364" y="-455.77" font-family="Arial" font-size="14.00">Can</text>
+<text text-anchor="middle" x="364" y="-440.77" font-family="Arial" font-size="14.00">be merged</text>
+</g>
+<!-- maint_check_branch&#45;&gt;maint_check_reject -->
+<g id="edge18" class="edge">
+<title>maint_check_branch&#45;&gt;maint_check_reject</title>
+<path fill="none" stroke="black" d="M318.26,-495.18C302.93,-488.43 279.07,-477.59 259,-466.97 231.22,-452.27 201.2,-434.68 175.95,-419.36"/>
+<polygon fill="black" stroke="black" points="177.59,-416.26 167.23,-414.05 173.95,-422.24 177.59,-416.26"/>
+<text text-anchor="middle" x="292" y="-455.77" font-family="Arial" font-size="14.00">Cannot</text>
+<text text-anchor="middle" x="292" y="-440.77" font-family="Arial" font-size="14.00">be merged</text>
+</g>
+<!-- maint_pass_join&#45;&gt;maint_merge -->
+<g id="edge20" class="edge">
+<title>maint_pass_join&#45;&gt;maint_merge</title>
+<path fill="none" stroke="black" d="M384,-242.82C384,-227.78 384,-205.69 384,-188.27"/>
+<polygon fill="black" stroke="black" points="387.5,-188.14 384,-178.14 380.5,-188.14 387.5,-188.14"/>
+</g>
+</g>
+</svg>
diff --git a/_site/index.html b/_site/index.html
new file mode 100644
index 00000000..b40e6023
--- /dev/null
+++ b/_site/index.html
@@ -0,0 +1,331 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Contents, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title  home ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/index.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `index.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="contents">Contents</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Welcome to the Standard for Public Code.</p>
+
+<p>We define ‘public code’ as open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.</p>
+
+<p>The Standard for Public Code gives public organizations a model for building their own open source solutions to enable successful future reuse by similar public organizations in other places. It includes guidance for policy makers, city administrators, developers and vendors.</p>
+
+<p>There are also unofficial <a href="https://publiccodenet.github.io/community-translations-standard/">community translations of the Standard</a> in other languages.</p>
+
+<ul>
+  <li><a href="/introduction.html">Introduction and background</a></li>
+  <li><a href="/readers-guide.html">Readers guide: how to interpret this standard</a></li>
+  <li><a href="/glossary.html">Glossary</a></li>
+  <li><a href="criteria/">Criteria</a>
+    <ul>
+      <li><a href="/criteria/code-in-the-open.html">Code in the open</a></li>
+      <li><a href="/criteria/bundle-policy-and-code.html">Bundle policy and source code</a></li>
+      <li><a href="/criteria/reusable-and-portable-codebases.html">Create reusable and portable code</a></li>
+      <li><a href="/criteria/open-to-contributions.html">Welcome contributors</a></li>
+      <li><a href="/criteria/make-contributing-easy.html">Make contributing easy</a></li>
+      <li><a href="/criteria/version-control-and-history.html">Maintain version control</a></li>
+      <li><a href="/criteria/require-review.html">Require review of contributions</a></li>
+      <li><a href="/criteria/document-objectives.html">Document codebase objectives</a></li>
+      <li><a href="/criteria/documenting.html">Document the code</a></li>
+      <li><a href="/criteria/understandable-english-first.html">Use plain English</a></li>
+      <li><a href="/criteria/open-standards.html">Use open standards</a></li>
+      <li><a href="/criteria/continuous-integration.html">Use continuous integration</a></li>
+      <li><a href="/criteria/open-licenses.html">Publish with an open license</a></li>
+      <li><a href="/criteria/findability.html">Make the codebase findable</a></li>
+      <li><a href="/criteria/style.html">Use a coherent style</a></li>
+      <li><a href="/criteria/document-maturity.html">Document codebase maturity</a></li>
+    </ul>
+  </li>
+  <li><a href="/AUTHORS.html">Authors</a></li>
+  <li><a href="/CONTRIBUTING.html">Contributing guide</a></li>
+  <li><a href="/CODE_OF_CONDUCT.html">Code of conduct</a></li>
+  <li><a href="/GOVERNANCE.html">Governance</a></li>
+  <li><a href="/CHANGELOG.html">Version history</a></li>
+  <li><a href="/license.html">License</a></li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/index.md b/_site/index.md
new file mode 100644
index 00000000..79c865af
--- /dev/null
+++ b/_site/index.md
@@ -0,0 +1,39 @@
+# Contents
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+Welcome to the Standard for Public Code.
+
+We define ‘public code’ as open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+
+The Standard for Public Code gives public organizations a model for building their own open source solutions to enable successful future reuse by similar public organizations in other places. It includes guidance for policy makers, city administrators, developers and vendors.
+
+There are also unofficial [community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/) in other languages.
+
+* [Introduction and background](introduction.md)
+* [Readers guide: how to interpret this standard](readers-guide.md)
+* [Glossary](glossary.md)
+* [Criteria](criteria/)
+  * [Code in the open](criteria/code-in-the-open.md)
+  * [Bundle policy and source code](criteria/bundle-policy-and-code.md)
+  * [Create reusable and portable code](criteria/reusable-and-portable-codebases.md)
+  * [Welcome contributors](criteria/open-to-contributions.md)
+  * [Make contributing easy](criteria/make-contributing-easy.md)
+  * [Maintain version control](criteria/version-control-and-history.md)
+  * [Require review of contributions](criteria/require-review.md)
+  * [Document codebase objectives](criteria/document-objectives.md)
+  * [Document the code](criteria/documenting.md)
+  * [Use plain English](criteria/understandable-english-first.md)
+  * [Use open standards](criteria/open-standards.md)
+  * [Use continuous integration](criteria/continuous-integration.md)
+  * [Publish with an open license](criteria/open-licenses.md)
+  * [Make the codebase findable](criteria/findability.md)
+  * [Use a coherent style](criteria/style.md)
+  * [Document codebase maturity](criteria/document-maturity.md)
+* [Authors](AUTHORS.md)
+* [Contributing guide](CONTRIBUTING.md)
+* [Code of conduct](CODE_OF_CONDUCT.md)
+* [Governance](GOVERNANCE.md)
+* [Version history](CHANGELOG.md)
+* [License](license.html)
diff --git a/_site/introduction.html b/_site/introduction.html
new file mode 100644
index 00000000..eadf7025
--- /dev/null
+++ b/_site/introduction.html
@@ -0,0 +1,511 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Introduction, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/introduction.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#definition-of-public-code">Definition of public code</a></li>
+  <li><a href="#reasons-for-public-code">Reasons for public code</a>
+    <ol>
+      <li><a href="#software-code--legal-code">Software code == legal code</a></li>
+      <li><a href="#traditional-public-software-procurement">Traditional public software procurement</a></li>
+      <li><a href="#technological-sovereignty-and-democratic-accountability">Technological sovereignty and democratic accountability</a></li>
+      <li><a href="#designing-truly-public-software">Designing truly public software</a></li>
+      <li><a href="#values-of-public-code">Values of public code</a></li>
+    </ol>
+  </li>
+  <li><a href="#how-public-code-works">How public code works</a>
+    <ol>
+      <li><a href="#economics-of-public-code">Economics of public code</a></li>
+      <li><a href="#procuring-public-code">Procuring public code</a></li>
+    </ol>
+  </li>
+  <li><a href="#standard-compliance-or-certification-process">Standard compliance or certification process</a>
+    <ol>
+      <li><a href="#how-the-process-works">How the process works</a></li>
+      <li><a href="#certifying-an-entire-codebase-versus-a-contribution">Certifying an entire codebase versus a contribution</a></li>
+    </ol>
+  </li>
+  <li><a href="#the-goals-for-the-standard-for-public-code">The goals for the Standard for Public Code</a>
+    <ol>
+      <li><a href="#who-this-is-for">Who this is for</a></li>
+    </ol>
+  </li>
+  <li><a href="#further-reading">Further reading</a>
+    <ol>
+      <li><a href="#videos-on-public-code">Videos on public code</a></li>
+    </ol>
+  </li>
+  <li><a href="#get-involved">Get involved</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/introduction.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `introduction.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="introduction">Introduction</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together.</p>
+
+<p>Anyone developing software or policy for a public purpose can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control.</p>
+
+<p>This introduction introduces the term public code, explains why this is important, and introduces the process through which software and policy code can become certified public code.</p>
+
+<h2 id="definition-of-public-code">Definition of public code</h2>
+
+<p>Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+It encompasses the software built to operate with and as public infrastructure, along with the arrangements for its production.
+Public code is explicitly distinct from regular software because it operates under fundamentally different circumstances and expectations.</p>
+
+<h2 id="reasons-for-public-code">Reasons for public code</h2>
+
+<p>There are many reasons for why public code is relevant now.</p>
+
+<h3 id="software-code--legal-code">Software code == legal code</h3>
+
+<p>Software is public infrastructure.</p>
+
+<p>In the 21st century, software can be considered vital public infrastructure. It is increasingly not just the expression of existing policy but the originator of new policy, for example where algorithms decide which districts need extra social services or policing.</p>
+
+<p>Software mechanics, algorithms and data collection have become key elements in the execution of public policies. Computer code now executes policies that have been codified in legal code through democratic procedures. Both forms of code set conditions for society to function according to democratically set public values, the latter executed by humans, the former by machines. In other words, software code has increasingly started to equal legal code.</p>
+
+<p>Software should therefore be subject to the principles of democratic governance.</p>
+
+<h3 id="traditional-public-software-procurement">Traditional public software procurement</h3>
+
+<p>Current public software production methods have not served public service delivery very well.</p>
+
+<p>In the last decade, public organizations that purchased complete software solutions have sometimes been surprised to discover that they:</p>
+
+<ul>
+  <li>can’t change their software to reflect changing policy or take advantage of new technology</li>
+  <li>don’t have access to their data as it’s locked into proprietary systems</li>
+  <li>are asked to pay ever increasing license fees</li>
+</ul>
+
+<h3 id="technological-sovereignty-and-democratic-accountability">Technological sovereignty and democratic accountability</h3>
+
+<p>Public institutions, civil servants and residents deserve better.</p>
+
+<p>We believe the software that runs our society can no longer be a black box, controlled by outside companies that keep the underlying logic on which their software operates hidden in proprietary codebases. Instead, governments and the people they serve need technological sovereignty. This allows them to set and control the functioning of public software, just like they are able to set and control policy that is legally formulated in laws. Citizens and civil society actors need this software to be transparent and accountable.</p>
+
+<p>The design of software as essential civic infrastructure should honor digital citizens’ rights.</p>
+
+<h3 id="designing-truly-public-software">Designing truly public software</h3>
+
+<p>Public code is at the core of modern public institutions, shapes the work of civil servants and affects the lives of almost all residents.</p>
+
+<p>Public software must therefore be:</p>
+
+<ul>
+  <li>transparent</li>
+  <li>accountable</li>
+  <li>understandable for its constituents</li>
+</ul>
+
+<p>It must reflect the values of the society it serves, for example by being inclusive and non-discriminatory.</p>
+
+<p>Most proprietary software systems currently used by public organizations do not meet these requirements. Public code does.</p>
+
+<h3 id="values-of-public-code">Values of public code</h3>
+
+<p>We consider public code to have these core values:</p>
+
+<ul>
+  <li>Inclusive</li>
+  <li>Usable</li>
+  <li>Open</li>
+  <li>Legible</li>
+  <li>Accountable</li>
+  <li>Accessible</li>
+  <li>Sustainable</li>
+</ul>
+
+<h2 id="how-public-code-works">How public code works</h2>
+
+<p>Public code is open source software meant for fulfilling the essential role of public organizations. Through use, other administrations contribute back to the software, so that its development and maintenance become truly collaborative.</p>
+
+<p>Being open unlocks many other things.</p>
+
+<p>Local responsibility and democratic accountability are ensured when a public organization implements and maintains their own public code. By being open and with a broader contributor base, the software is more secure as it benefits from many eyes spotting potential flaws. Many contributors share the maintenance work to keep it functional and modern, which reduces future technical debt. The shared workload is more sustainable now and in the future. Its openness makes the code and its data more easily adaptable in the future. The code will be easier to retool, repurpose or retire. This all results in lower risk public infrastructure.</p>
+
+<p>This pooling of resources lets public administrations give extra attention to how to customize the software so it works best in each local context, creating better user experiences for their end users (residents or citizens).</p>
+
+<h3 id="economics-of-public-code">Economics of public code</h3>
+
+<p>Public code offers a better economic model for public organizations as well as for commercial companies. It’s an alternative to traditional software procurement which increases local control and economic opportunity.</p>
+
+<p>Designed from the start to be open, adaptable and with data portability, it can be developed by in-house staff or trusted vendors. Because the code is open, the public administration can change vendors if they need to. Open code increases opportunities for public learning and scrutiny, allowing the public administration to procure smaller contracts. Smaller procurements are easier for local small and medium enterprises to bid upon. Public administrations can use their own software purchasing to stimulate innovation and competition in their local economy.</p>
+
+<p>This can be seen as investment leading to future economic growth. More vendors will be necessary due to growing technology demand.</p>
+
+<h3 id="procuring-public-code">Procuring public code</h3>
+
+<p>Public code can be used and developed by permanent in-house development teams, contractors or outsourced suppliers. Vendors to public organizations can include public code in their bids for contracts.</p>
+
+<p>To use existing public code, you need to specify in your budget and project design that your new solution will use that codebase. To encourage an innovative approach to adapting the public code to your context, you could describe the service or outcome in your contract.</p>
+
+<h2 id="standard-compliance-or-certification-process">Standard compliance or certification process</h2>
+
+<p>The Foundation for Public Code ensures that codebases under its stewardship (and not in incubation or the attic) are compliant with the Standard for Public Code. This makes clear to potential users and contributors that the codebase is of high quality, and updates will be too.</p>
+
+<p>The audit performed by the Foundation for Public Code is meant to complement machine testing, as machines are great at testing things like syntax and whether outcomes align with expectations. Things meant for humans, such as testing whether documentation is actually understandable and accessible in context, the commit messages make sense, and whether community guidelines are being followed are impossible for machines to test.</p>
+
+<p>The audit tests the entire codebase, including source code, policy, documentation and conversation for compliance with both the standards set out by the Foundation for Public Code and the standards set out in the codebase itself.</p>
+
+<h3 id="how-the-process-works">How the process works</h3>
+
+<p>Every time a contribution is suggested to a codebase, through for instance a merge request, the <a href="https://about.publiccode.net/roles/">codebase stewards</a> of the Foundation for Public Code will audit the contribution for compliance with the Standard for Public Code. New contributions can only be adopted into the codebase after they have been approved as compliant with the Standard for Public Code, and have been reviewed by another contributor.</p>
+
+<p>The audit is presented as a review of the contribution. The codebase steward gives line by line feedback and compliance, helping the contributor to improve their contribution. The merge request cannot be fulfilled until the codebase stewards have approved the contribution.</p>
+
+<p><img src="/images/audit-flow.svg" alt="Pull Request Acceptance process" /></p>
+
+<h3 id="certifying-an-entire-codebase-versus-a-contribution">Certifying an entire codebase versus a contribution</h3>
+
+<p>For the codebase to be completely certified every meaningful line of code, and the commits behind the code, need to meet the Standard.</p>
+
+<p>If codebases have been completely audited from the first merge request they can be immediately certified as compliant with the Standard for Public Code.</p>
+
+<p>If the audit process is added to an existing codebase, the new merge requests can be certified, but the existing code cannot be certified. By auditing every new merge request the codebase can move incrementally towards being completely certified.</p>
+
+<h2 id="the-goals-for-the-standard-for-public-code">The goals for the Standard for Public Code</h2>
+
+<p>This Standard supports developers, designers, business management and policy makers to:</p>
+
+<ul>
+  <li>develop high quality software and policy for better public service delivery</li>
+  <li>develop codebases that can be reused across contexts and collaboratively maintained</li>
+  <li>reduce technical debt and project failure rate</li>
+  <li>have more granular control over, and ability to make decisions about, their IT systems</li>
+  <li>improve vendor relationships with a better economic model</li>
+</ul>
+
+<p><a href="https://publiccode.net/">The Foundation for Public Code</a> helps public organizations share and adopt open source software, build sustainable developer communities and create a thriving ecosystem for public code. It does this through codebase stewardship. For this process the codebase stewards use the Standard for Public Code to make sure the code it stewards is high quality as well as collaboratively maintainable.</p>
+
+<p>Potential users of codebases tested against the Standard for Public Code can expect them to be highly reusable, easily maintainable and of high quality.</p>
+
+<p>The Standard for Public Code does this by:</p>
+
+<ul>
+  <li>setting out a common terminology for public code development</li>
+  <li>establishing measures to help develop high quality public code</li>
+  <li>providing guidance on how to fulfill its criteria and operationalize compliance</li>
+</ul>
+
+<p>The Standard for Public Code is meant to be time and technology independent.</p>
+
+<h3 id="who-this-is-for">Who this is for</h3>
+
+<p>The Standard for Public Code is for the people who create and reuse public code:</p>
+
+<ul>
+  <li>policy makers</li>
+  <li>business and project management</li>
+  <li>developers and designers</li>
+</ul>
+
+<p>These people work at:</p>
+
+<ul>
+  <li>institutions, organizations and administrations in the public sector</li>
+  <li>consultancies and vendors of information technology and policy services to public organizations</li>
+</ul>
+
+<p>It is not aimed at public organizations’ end users (residents or citizens), journalists or academics.</p>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf">“Modernising Public Infrastructure with Free Software” whitepaper</a> by the Free Software Foundation Europe.</li>
+</ul>
+
+<h3 id="videos-on-public-code">Videos on public code</h3>
+
+<ul>
+  <li><a href="https://www.youtube.com/watch?v=cnJtnZ9Cx1o">Collaborative Code is the Future of Cities @ DecidimFest 2019</a>. Talk by Ben Cerveny on the background behind the Foundation for Public Code.</li>
+  <li><a href="https://youtube.com/watch?v=QHFkD4xfd6c">Public Money? Public Code! - Panel @ Nextcloud Conference 2019</a>. Touches on topics like procurement, law and more.</li>
+</ul>
+
+<h2 id="get-involved">Get involved</h2>
+
+<p>This standard is a living document. <a href="/CONTRIBUTING.html">Read our contributor guide</a> to learn how you can make it better.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/introduction.md b/_site/introduction.md
new file mode 100644
index 00000000..12407f02
--- /dev/null
+++ b/_site/introduction.md
@@ -0,0 +1,172 @@
+# Introduction
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together.
+
+Anyone developing software or policy for a public purpose can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control.
+
+This introduction introduces the term public code, explains why this is important, and introduces the process through which software and policy code can become certified public code.
+
+## Definition of public code
+
+Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+It encompasses the software built to operate with and as public infrastructure, along with the arrangements for its production.
+Public code is explicitly distinct from regular software because it operates under fundamentally different circumstances and expectations.
+
+## Reasons for public code
+
+There are many reasons for why public code is relevant now.
+
+### Software code == legal code
+
+Software is public infrastructure.
+
+In the 21st century, software can be considered vital public infrastructure. It is increasingly not just the expression of existing policy but the originator of new policy, for example where algorithms decide which districts need extra social services or policing.
+
+Software mechanics, algorithms and data collection have become key elements in the execution of public policies. Computer code now executes policies that have been codified in legal code through democratic procedures. Both forms of code set conditions for society to function according to democratically set public values, the latter executed by humans, the former by machines. In other words, software code has increasingly started to equal legal code.
+
+Software should therefore be subject to the principles of democratic governance.
+
+### Traditional public software procurement
+
+Current public software production methods have not served public service delivery very well.
+
+In the last decade, public organizations that purchased complete software solutions have sometimes been surprised to discover that they:
+
+* can’t change their software to reflect changing policy or take advantage of new technology
+* don’t have access to their data as it's locked into proprietary systems
+* are asked to pay ever increasing license fees
+
+### Technological sovereignty and democratic accountability
+
+Public institutions, civil servants and residents deserve better.
+
+We believe the software that runs our society can no longer be a black box, controlled by outside companies that keep the underlying logic on which their software operates hidden in proprietary codebases. Instead, governments and the people they serve need technological sovereignty. This allows them to set and control the functioning of public software, just like they are able to set and control policy that is legally formulated in laws. Citizens and civil society actors need this software to be transparent and accountable.
+
+The design of software as essential civic infrastructure should honor digital citizens’ rights.
+
+### Designing truly public software
+
+Public code is at the core of modern public institutions, shapes the work of civil servants and affects the lives of almost all residents.
+
+Public software must therefore be:
+
+* transparent
+* accountable
+* understandable for its constituents
+
+It must reflect the values of the society it serves, for example by being inclusive and non-discriminatory.
+
+Most proprietary software systems currently used by public organizations do not meet these requirements. Public code does.
+
+### Values of public code
+
+We consider public code to have these core values:
+
+* Inclusive
+* Usable
+* Open
+* Legible
+* Accountable
+* Accessible
+* Sustainable
+
+## How public code works
+
+Public code is open source software meant for fulfilling the essential role of public organizations. Through use, other administrations contribute back to the software, so that its development and maintenance become truly collaborative.
+
+Being open unlocks many other things.
+
+Local responsibility and democratic accountability are ensured when a public organization implements and maintains their own public code. By being open and with a broader contributor base, the software is more secure as it benefits from many eyes spotting potential flaws. Many contributors share the maintenance work to keep it functional and modern, which reduces future technical debt. The shared workload is more sustainable now and in the future. Its openness makes the code and its data more easily adaptable in the future. The code will be easier to retool, repurpose or retire. This all results in lower risk public infrastructure.
+
+This pooling of resources lets public administrations give extra attention to how to customize the software so it works best in each local context, creating better user experiences for their end users (residents or citizens).
+
+### Economics of public code
+
+Public code offers a better economic model for public organizations as well as for commercial companies. It's an alternative to traditional software procurement which increases local control and economic opportunity.
+
+Designed from the start to be open, adaptable and with data portability, it can be developed by in-house staff or trusted vendors. Because the code is open, the public administration can change vendors if they need to. Open code increases opportunities for public learning and scrutiny, allowing the public administration to procure smaller contracts. Smaller procurements are easier for local small and medium enterprises to bid upon. Public administrations can use their own software purchasing to stimulate innovation and competition in their local economy.
+
+This can be seen as investment leading to future economic growth. More vendors will be necessary due to growing technology demand.
+
+### Procuring public code
+
+Public code can be used and developed by permanent in-house development teams, contractors or outsourced suppliers. Vendors to public organizations can include public code in their bids for contracts.
+
+To use existing public code, you need to specify in your budget and project design that your new solution will use that codebase. To encourage an innovative approach to adapting the public code to your context, you could describe the service or outcome in your contract.
+
+## Standard compliance or certification process
+
+The Foundation for Public Code ensures that codebases under its stewardship (and not in incubation or the attic) are compliant with the Standard for Public Code. This makes clear to potential users and contributors that the codebase is of high quality, and updates will be too.
+
+The audit performed by the Foundation for Public Code is meant to complement machine testing, as machines are great at testing things like syntax and whether outcomes align with expectations. Things meant for humans, such as testing whether documentation is actually understandable and accessible in context, the commit messages make sense, and whether community guidelines are being followed are impossible for machines to test.
+
+The audit tests the entire codebase, including source code, policy, documentation and conversation for compliance with both the standards set out by the Foundation for Public Code and the standards set out in the codebase itself.
+
+### How the process works
+
+Every time a contribution is suggested to a codebase, through for instance a merge request, the [codebase stewards](https://about.publiccode.net/roles/) of the Foundation for Public Code will audit the contribution for compliance with the Standard for Public Code. New contributions can only be adopted into the codebase after they have been approved as compliant with the Standard for Public Code, and have been reviewed by another contributor.
+
+The audit is presented as a review of the contribution. The codebase steward gives line by line feedback and compliance, helping the contributor to improve their contribution. The merge request cannot be fulfilled until the codebase stewards have approved the contribution.
+
+![Pull Request Acceptance process](images/audit-flow.svg)
+
+### Certifying an entire codebase versus a contribution
+
+For the codebase to be completely certified every meaningful line of code, and the commits behind the code, need to meet the Standard.
+
+If codebases have been completely audited from the first merge request they can be immediately certified as compliant with the Standard for Public Code.
+
+If the audit process is added to an existing codebase, the new merge requests can be certified, but the existing code cannot be certified. By auditing every new merge request the codebase can move incrementally towards being completely certified.
+
+## The goals for the Standard for Public Code
+
+This Standard supports developers, designers, business management and policy makers to:
+
+* develop high quality software and policy for better public service delivery
+* develop codebases that can be reused across contexts and collaboratively maintained
+* reduce technical debt and project failure rate
+* have more granular control over, and ability to make decisions about, their IT systems
+* improve vendor relationships with a better economic model
+
+[The Foundation for Public Code](https://publiccode.net/) helps public organizations share and adopt open source software, build sustainable developer communities and create a thriving ecosystem for public code. It does this through codebase stewardship. For this process the codebase stewards use the Standard for Public Code to make sure the code it stewards is high quality as well as collaboratively maintainable.
+
+Potential users of codebases tested against the Standard for Public Code can expect them to be highly reusable, easily maintainable and of high quality.
+
+The Standard for Public Code does this by:
+
+* setting out a common terminology for public code development
+* establishing measures to help develop high quality public code
+* providing guidance on how to fulfill its criteria and operationalize compliance
+
+The Standard for Public Code is meant to be time and technology independent.
+
+### Who this is for
+
+The Standard for Public Code is for the people who create and reuse public code:
+
+* policy makers
+* business and project management
+* developers and designers
+
+These people work at:
+
+* institutions, organizations and administrations in the public sector
+* consultancies and vendors of information technology and policy services to public organizations
+
+It is not aimed at public organizations' end users (residents or citizens), journalists or academics.
+
+## Further reading
+
+* ["Modernising Public Infrastructure with Free Software" whitepaper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) by the Free Software Foundation Europe.
+
+### Videos on public code
+
+* [Collaborative Code is the Future of Cities @ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on the background behind the Foundation for Public Code.
+* [Public Money? Public Code! - Panel @ Nextcloud Conference 2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like procurement, law and more.
+
+## Get involved
+
+This standard is a living document. [Read our contributor guide](/CONTRIBUTING.md) to learn how you can make it better.
diff --git a/_site/license.html b/_site/license.html
new file mode 100644
index 00000000..5216c061
--- /dev/null
+++ b/_site/license.html
@@ -0,0 +1,400 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <link rel="stylesheet" href="assets/github-markdown.css">
+  <title>Standard for Public Code</title>
+  <style>
+    html, .markdown-body {
+      font-family: Mulish;
+      font-size: 11pt;
+    }
+
+    .markdown-body h1, .markdown-body h2, .markdown-body h3 {
+      font-weight: normal;
+      position: relative;
+    }
+    .markdown-body h1 {
+      margin-top: 0;
+      font-size: 1.5cm;
+      border-bottom: none;
+    }
+    .markdown-body h2 {
+      font-size: 1.5em;
+    }
+    .markdown-body h3 {
+      font-size: 1em;
+      font-weight: bold;
+    }
+    .markdown-body h4 {
+      font-size: 1em;
+      font-weight: italic;
+    }
+    .markdown-body h4 {
+      font-weight: bold;
+      font-weight: normal;
+    }
+
+    article>p, article>ul, article>ol {
+      position: relative;
+      max-width: 27rem;
+    }
+
+    article {
+      clear: both;
+    }
+
+    a:link {
+      color: inherit;
+      text-decoration: none;
+    }
+
+    a:link:after {
+      color: grey;
+      page-break-inside: avoid;
+      margin-left: .25em;
+      break-inside: avoid;
+      display: block;
+      right: 0;
+      width: 6cm;
+      margin-right: -7cm;
+      padding: 0.25rem;
+      line-height: 1.25;
+      text-align: left;
+      float: right;
+      clear: both;
+      word-break: normal;
+      text-decoration: none;
+    }
+    a[href^="http"]:link {
+      color: black;
+      text-decoration: none;
+      word-wrap: normal;
+    }
+    a[href^="http"]:after {
+      content: "" attr(href) "";
+      font-size: .75em;
+    }
+    a[href^="#"] {
+      color: black;
+      text-decoration: none;
+    }
+    a[href^="#"]:after {
+      content: "" target-counter(attr(href), page);
+      color: black;
+      background-color: whitesmoke;
+      display: inline;
+      width: 0.6cm;
+      padding: 0.2cm;
+      text-align: right;
+    }
+
+    img {
+      max-width: 155% !important;
+    }
+
+    ol, ul {
+      margin-bottom: 2em;
+    }
+
+    li, p {
+      clear: both;
+    }
+
+    /* Headings */
+
+    .markdown-body [id$="policy-makers-what-you-need-to-do"]:before,
+    .markdown-body [id$="management-what-you-need-to-do"]:before,
+    .markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+      display: block;
+      position: absolute;
+      content: 'A';
+      text-align: center;
+      width: 1cm;
+      height: 1cm;
+      background-color: black;
+      border: 1px solid black;
+      color: white;
+      display: inline-block;
+      margin-left: -1.2cm;
+      box-sizing: border-box;
+      padding: 0.12cm;
+      font-size: 0.5cm;
+      font-weight: 900;
+    }
+    .markdown-body [id$="policy-makers-what-you-need-to-do"]:before {
+      background-color: #00EFB5;
+      border-color: #00EFB5;
+      content: 'P';
+    }
+    .markdown-body [id$="management-what-you-need-to-do"]:before {
+      background-color: #FF6D1C;
+      border-color: #FF6D1C;
+      content: 'M';
+    }
+    .markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+      background-color: #8626FF;
+      border-color: #8626FF;
+      content: 'D';
+    }
+
+    /* First page */
+
+    h1.title {
+      font-size: 5em;
+      font-weight: 700;
+      margin-bottom: 1cm;
+    }
+
+    ul.first-page-audiences {
+      max-width: none;
+      list-style: none;
+      font-size: 1.25em;
+      padding-left: 0;
+    }
+    .first-page-audiences li, .first-page-audiences lh {
+      display: block;
+      margin-bottom: .5cm;
+    }
+    .first-page-audiences lh {
+      margin-bottom: 1cm;
+    }
+    .first-page-audiences li {
+      padding-left: 1.2cm;
+    }
+    .first-page-audiences li::before {
+      margin-top: -.15cm;
+    }
+    #section-first-page>img {
+      width: 100%;
+    }
+    
+    /* Print specific */
+
+    @media print {
+      /* html { page-break-before: left } */
+      @page {
+        /* A4 with a 3mm bleed on every side */
+        size: 21.6cm 30.3cm;
+        margin: 2cm 0;
+        orphans:4;
+        widows:4;
+      }
+      @page :left {
+        margin-right: 1cm;
+        @top-left {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+          padding-left: 0.5cm;
+        }
+      }
+      @page :right {
+        margin-left: 1cm;
+        @top-right {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+          padding-right: 0.5cm;
+        }
+      }
+      figure {
+        page: image;
+      }
+      figure>img {
+        width: 100%;
+        height: 100%;
+      }
+      @page image {
+        margin-top: 0 !important;
+        margin-left: -1.5cm !important;
+        margin-right: -1.5cm !important;
+        margin-bottom: 0 !important;
+        padding: 0 0 0 0 !important;
+      }
+
+      article {
+        margin: 0 2cm;
+        break-before: left;
+      }
+      article:first-of-type {
+        break-before: avoid;
+      }
+      h1, h2, h3, h4 {
+        page-break-after: avoid;
+      }
+      img {
+        page-break-inside: avoid;
+      }
+      #table-of-contents {
+        line-height: 0.9;
+      }
+      
+      #section-first-page>img {
+        width: 21.6cm;
+        margin: 1cm 0 1cm -3.21cm; /* This value for the left margin was done by eye */
+      }
+    }
+
+    @media screen {
+      body {
+        background-color: whitesmoke;
+        margin: 0; padding: 0;
+      }
+      article {
+        display: block;
+        background-color: white;
+        padding: 1cm;
+        min-height: 29.7cm;
+        max-width: 50em;
+        max-width: 21cm;
+        box-sizing: border-box;
+        margin: 2cm 0;
+      }
+    }
+
+  </style>
+</head>
+<body class="markdown-body">
+
+  <article id="section-license">
+
+    <p>This license is the legal contract that allows anyone to do anything they like with the content in this entire document.</p>
+    <h1>CC0 1.0 Universal</h1>
+    <pre>Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
+</pre>
+
+  </article>
+
+</body>
+</html>
diff --git a/_site/locales/en/LC_MESSAGES/messages.po b/_site/locales/en/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..ac27704a
--- /dev/null
+++ b/_site/locales/en/LC_MESSAGES/messages.po
@@ -0,0 +1,2716 @@
+#
+msgid ""
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 1 (header)
+msgid "order: 2"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 2 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 4 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST include the "
+"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
+"is based on."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include all source code that the policy is based on, "
+"unless used for fraud detection."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 6 (header)
+msgid "Why this is important"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 7 (paragraph)
+msgid ""
+"Access to both the source code and the policy documents is necessary for "
+"understanding and reuse of, as well as collaboration in, a codebase. "
+"Understanding the context and the policies in that context is fundamental to"
+" understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them. To be able to evaluate whether to adopt a codebase in a "
+"new context, an organization will need to understand what process changes it"
+" must choose to make or how to contribute additional configurability to the "
+"existing solution in order to adapt it to the new context."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 8 (header)
+msgid "What this does not do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid "Guarantee that a codebase will reflect the bundled policy."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid ""
+"Make sure packages comply with the local technical infrastructure or legal "
+"framework of a given public organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 10 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 12 (header)
+msgid "Policy makers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Collaborate with developers and designers to ensure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable such as"
+" [Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
+" [Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Track policy with [the same version control](version-control-and-history.md)"
+" and documentation used to track source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed and whether it still matches the [intentions of the "
+"policy](document-objectives.md)."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 14 (header)
+msgid "Management: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 16 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Work together with policy makers to ensure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 18 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[Free online tools for building BPMN, CMMN and DMN diagrams at "
+"bmpn.io](https://bpmn.io/) by Camunda."
+msgstr ""
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./code-in-the-open.md:block 1 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./code-in-the-open.md:block 2 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source [code](../glossary.md#code) for any "
+"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT upload sensitive information regarding users, their "
+"organization or third parties to the "
+"[repository](../glossary.md#repository)."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./code-in-the-open.md:block 7 (paragraph)
+msgid "Coding in the open:"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "improves transparency"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "increases code quality"
+msgstr ""
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "facilitates the auditing processes"
+msgstr ""
+
+#: ./code-in-the-open.md:block 9 (paragraph)
+msgid ""
+"These aspects together create more opportunities for citizens to understand "
+"how software and policy impact their interactions with a public "
+"organization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid "Make source code or policy reusable."
+msgstr ""
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid ""
+"Make the [codebase](../glossary.md#codebase) and the code within it "
+"understandable to as many people as possible."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase files and commit history do not include sensitive "
+"information."
+msgstr ""
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"Clearly split data and code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 1 (header)
+msgid "order: 12"
+msgstr ""
+
+#: ./continuous-integration.md:block 2 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"All functionality in the source [code](../glossary.md#code) MUST have "
+"automated tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "The codebase MUST have active contributors."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "Using [continuous integration](../glossary.md#continuous-integration):"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "allows you to quickly identify problems with the codebase,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"enables risk taking and focusing on problem solving while minimizing stress "
+"for the contributors,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"lowers barriers for new contributors by reducing the amount of understanding"
+" necessary to suggest changes,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "leads to more maintainable code,"
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "speeds up the development cycle."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Smaller, more regular contributions are typically easier to evaluate and "
+"lower risk compared to large infrequent changes."
+msgstr ""
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Codebases in active development more reliably provide opportunities for "
+"collaboration and feedback."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid ""
+"Create a fault tolerant infrastructure that will work and scale perfectly."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Create meaningful tests."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Test for real life situations."
+msgstr ""
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Guarantee the code will deliver exactly the same policy result."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that code coverage tools check that coverage is at 100% of the code."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Check if code coverage data is published."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Involve management as well as developers and designers as early in the "
+"process as possible and keep them engaged throughout development of your "
+"policy."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure the code reflects any changes to the policy (see [Maintain version"
+" control](version-control-and-history.md))."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Plan the work to deliver small parts very often instead of large parts less "
+"frequently."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management structure the work plan such that it can be delivered as "
+"small increments."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Structure code written to handle conditions which are difficult to create in"
+" a test environment in such a way that the conditions can be simulated "
+"during testing. Forms of resource exhaustion such as running out of storage "
+"space and memory allocation failure are typical examples of difficult to "
+"create conditions."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
+"Humble."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 1 (header)
+msgid "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 2 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is ready to use MUST only depend on other codebases that "
+"are also ready to use."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is not yet ready to use MUST have one of the labels: "
+"prototype, alpha, beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./document-maturity.md:block 7 (paragraph)
+msgid ""
+"Clearly signalling a codebase's maturity helps others decide whether to "
+"reuse, invest in or contribute to it."
+msgstr ""
+
+#: ./document-maturity.md:block 9 (unordered list)
+msgid "Guarantee that others will use the [code](../glossary.md#code)."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Confirm that it is clear where to get the newest version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase doesn't depend on any codebases marked with a less"
+" mature status."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
+"beta or pre-release version."
+msgstr ""
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any code "
+"developed needs to be tested and improved before it can be put into service."
+msgstr ""
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that services only rely on codebases of equal or greater maturity "
+"than the service. For example, don't use a beta codebase in a production "
+"service or a prototype codebase in a beta service."
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"If the codebase is not ready for general use, work with the developers to "
+"ensure the codebase is properly labeled:"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"prototype: to test the look and feel, and to internally prove the concept of"
+" the technical possibilities,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid "alpha: to do guided tests with a limited set of users,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"beta: to open up testing to a larger section of the [general "
+"public](../glossary.md#general-public), for example to test if the codebase "
+"works at scale,"
+msgstr ""
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"pre-release version: code that is ready to be released but hasn't received "
+"formal approval yet."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Add a prominent header to every interface that indicates the maturity level "
+"of the code."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid "Version all releases."
+msgstr ""
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Especially in 'rolling release' scenarios, the version may be automatically "
+"derived from the [version control](../glossary.md#version-control) system "
+"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
+"describe))."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[What are the Discovery, Alpha, Beta and Live stages in developing a "
+"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
+"the UK Government Digital Service."
+msgstr ""
+
+#: ./document-objectives.md:block 1 (header)
+msgid "order: 8"
+msgstr ""
+
+#: ./document-objectives.md:block 2 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
+"objectives, like a mission and goal statement, that is understandable by "
+"developers and designers so that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./document-objectives.md:block 7 (paragraph)
+msgid "Documenting codebase objectives:"
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"provides an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid "helps scope your own development."
+msgstr ""
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"clearly communicates to other stakeholders and contributors the purpose of "
+"the codebase and the modules of which it is composed."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee that the codebase achieves the stated objective(s)."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee contributions to the codebase."
+msgstr ""
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid ""
+"Prevent other codebases from attempting to achieve the same objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development like value and ethics based policies, for example accessibility "
+"or equal opportunity."
+msgstr ""
+
+#: ./document-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 18 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./document-objectives.md:block 20 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./documenting.md:block 1 (header)
+msgid "order: 9"
+msgstr ""
+
+#: ./documenting.md:block 2 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"All of the functionality of the [codebase](../glossary.md#codebase), "
+"[policy](../glossary.md#policy) as well as source, MUST be described in "
+"language clearly understandable for those that understand the purpose of the"
+" [code](../glossary.md#code)."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the source code."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 5 (unordered list)
+msgid "Testing the code by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "Users can start using and contributing more quickly."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid ""
+"You help people discover the codebase, especially people asking 'is there "
+"already code that does something like this'."
+msgstr ""
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "This provides transparency into your organization and processes."
+msgstr ""
+
+#: ./documenting.md:block 9 (unordered list)
+msgid ""
+"Contribute directly to more reusable, portable code (see [Create reusable "
+"and portable code](./reusable-and-portable-codebases.md))."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated from code, and links and images are "
+"tested."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 13 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid "Try to use the codebase."
+msgstr ""
+
+#: ./documenting.md:block 15 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./documenting.md:block 17 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./documenting.md:block 19 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./findability.md:block 1 (header)
+msgid "order: 14"
+msgstr ""
+
+#: ./findability.md:block 2 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be findable using a search "
+"engine by describing the problem it solves in natural language."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "The codebase MUST be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"Proactiveness is needed; just publishing a codebase and hoping it's found "
+"doesn't work."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid "A metadata description file increases discoverability."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"The more findable a codebase is, the more potential new collaborators will "
+"find it."
+msgstr ""
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"By having well-written metadata containing a unique and persistent "
+"identifer, such as a Wikidata item or FSF software directory listing, and "
+"thus being part of the semantic web, it will be easier for other people to "
+"refer, cite, disambiguate and discover the codebase through third party "
+"tools."
+msgstr ""
+
+#: ./findability.md:block 9 (unordered list)
+msgid "Ensure new collaborators or replicators."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a plain English problem "
+"description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a technical problem description."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by the codebase name."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevent conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid "Ensure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Search engine optimization."
+msgstr ""
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Softare Foundation."
+msgstr ""
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./index.md:block 1 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./index.md:block 3 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./index.md:block 4 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 5 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 1 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 2 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
+"that accepts suggestions from anyone."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include instructions for how to privately report security "
+"issues for responsible disclosure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD include instructions for how to report potentially "
+"security sensitive issues on a closed channel."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid ""
+"Enables users to fix problems and add features to the shared codebase "
+"leading to better, more reliable and feature rich software."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Allows collaborative uptake of shared digital infrastructure."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Helps users decide to use one codebase over another."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 9 (unordered list)
+msgid "Guarantee others will reuse the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 13 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid ""
+"Keep your management informed of the time and resources you require to "
+"support other contributors."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./open-licenses.md:block 1 (header)
+msgid "order: 13"
+msgstr ""
+
+#: ./open-licenses.md:block 2 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) and documentation MUST be licensed such that"
+" it may be freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid "All code MUST be published with a license file."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Having multiple licenses for different types of code and documentation is "
+"OPTIONAL."
+msgstr ""
+
+#: ./open-licenses.md:block 7 (unordered list)
+msgid ""
+"Makes it possible for anyone to see the code and know that they can and how "
+"they can reuse it."
+msgstr ""
+
+#: ./open-licenses.md:block 9 (unordered list)
+msgid "Prevent use of the code by any specific actors."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires code to be [open "
+"source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their code by publishing it "
+"under an open source license."
+msgstr ""
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./open-standards.md:block 1 (header)
+msgid "order: 11"
+msgstr ""
+
+#: ./open-standards.md:block 2 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"For features of the [codebase](../glossary.md#codebase) that facilitate the "
+"exchange of data the codebase MUST use an [open "
+"standard](../glossary.md#open-standard) that meets the [Open Source "
+"Initiative Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Standards that are machine testable SHOULD be preferred over those that are "
+"not."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Creates interoperability between systems."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Reduces possible vendor lock-in."
+msgstr ""
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid ""
+"Guarantees access to the knowledge required to reuse and contribute to the "
+"codebase."
+msgstr ""
+
+#: ./open-standards.md:block 9 (unordered list)
+msgid "Make it understandable how to use the software."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./open-standards.md:block 15 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in "
+"[code](../glossary.md#code) reviews."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./open-standards.md:block 19 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./open-to-contributions.md:block 1 (header)
+msgid "order: 4"
+msgstr ""
+
+#: ./open-to-contributions.md:block 2 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
+"suggestions for changes to the codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Helps newcomers understand and trust the codebase community's leadership."
+msgstr ""
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Prevents the community that works on a codebase splitting because there is "
+"no way to influence its goals and progress, resulting in diverging "
+"communities."
+msgstr ""
+
+#: ./open-to-contributions.md:block 9 (unordered list)
+msgid "Guarantee others will join the community."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./require-review.md:block 1 (header)
+msgid "order: 7"
+msgstr ""
+
+#: ./require-review.md:block 2 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
+"documentation."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD conform to the standards, architecture and decisions "
+"set out in the codebase in order to pass review."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
+"tests of the codebase."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Increases codebase quality."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Reduces security risks as well as operational risks."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Creates a culture of making every contribution great."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Catches the most obvious mistakes that could happen."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Gives contributors the security that their contributions are only accepted "
+"if they really add value."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Assures contributors of a guaranteed time for feedback or collaborative "
+"improvement."
+msgstr ""
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Prompt reviews increase both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Guarantee the right solution to a problem."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Mean that reviewers are liable."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Absolve a contributor from writing documentation and tests."
+msgstr ""
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Provide you with the right reviewers."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check if reviews cover conformance to standards, architecture and codebase "
+"guidelines."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check with reviewers if they run the code and tests during review."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just code, is reviewed."
+msgstr ""
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make delivering great code a shared objective."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Try to respond to others' requests for code review promptly, initially "
+"providing feedback about the concept of the change."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 1 (header)
+msgid "order: 3"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 2 (header)
+msgid "Create reusable and portable code"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
+"[different contexts](../glossary.md#different-contexts)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed [code](../glossary.md#code) or services for execution "
+"and understanding."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Configuration SHOULD be used to make code adapt to context specific needs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Enables other policy makers, developers and designers to reuse what you've "
+"developed, to test it, to improve it and contribute those improvements back "
+"leading to better quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes the code easier for new people to understand (as it's more general)."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes it easier to control the mission, vision and scope of the codebase "
+"because the codebase is thoughtfully and purposefully designed for "
+"reusability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Codebases used by multiple parties are more likely to benefit from a self-"
+"sustaining community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Any contributor is able to test and contribute without relying on the "
+"situation-specific infrastructure of any other contributor or deployment."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Composing a codebase from well documented modules improves reusability and "
+"maintainability."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"A module is easier to reuse in another context if its purpose is clearly "
+"documented."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Get others to reuse the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Build a community."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid ""
+"Shift responsibility for documentation, support, bug-fixing, etc. to another"
+" party."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Guarantee that modules are generic enough to be reused in any context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"reuse the codebase and what that would entail."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed code or services."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
+msgid ""
+"Ensure that the codebase documentation describes the build-time and runtime "
+"dependencies. If your context requires deploying to proprietary platforms or"
+" using proprietary components, ensure that collaborators can develop, use, "
+"test, and deploy without them."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
+"OpenAPI Initiative defines a standard, programming language-agnostic "
+"interface description for human and machine-readable HTTP APIs."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Internationalization techniques: Authoring HTML & "
+"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
+"World Wide Web Consortium."
+msgstr ""
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
+"Operating System."
+msgstr ""
+
+#: ./style.md:block 1 (header)
+msgid "order: 15"
+msgstr ""
+
+#: ./style.md:block 2 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST adhere to either a coding or writing style guide, either "
+"the [codebase](../glossary.md#codebase) community's own or an existing one "
+"that is advertised in or part of the codebase."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include inline comments and documentation for non-"
+"trivial sections."
+msgstr ""
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Including sections on [understandable English](understandable-english-"
+"first.md) in the style guide is OPTIONAL."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Enables contributors in different environments to work together on a unified"
+" product."
+msgstr ""
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Unifying vocabularies reduces friction in communication between "
+"contributors."
+msgstr ""
+
+#: ./style.md:block 9 (unordered list)
+msgid "Help contributors write well or effectively explain what they do."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./style.md:block 11 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./style.md:block 13 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./style.md:block 15 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./style.md:block 17 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [code](../glossary.md#code) contributions in order for them to"
+" be merged by the maintainers, including source, tests and documentation. "
+"Continually improve upon and expand this documentation with the aim of "
+"evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./style.md:block 18 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./style.md:block 19 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
+"Hugo Martins."
+msgstr ""
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./understandable-english-first.md:block 1 (header)
+msgid "order: 10"
+msgstr ""
+
+#: ./understandable-english-first.md:block 2 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [codebase](../glossary.md#codebase) documentation MUST be in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) MUST be in English, except where "
+"[policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Makes the codebase and what it does understandable for a wider variety of "
+"stakeholders in multiple contexts."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid "Helps with the discoverability of the codebase."
+msgstr ""
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Can help you meet the [European Union accessibility "
+"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
+" which requires most public sector information to be accessible."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make explanations of the codebase's functionality understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make your organization's jargon understandable without an explanation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./understandable-english-first.md:block 13 (unordered list)
+msgid ""
+"Frequently test with other management, developers and designers in the "
+"process if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Frequently test with policy makers and management if they understand what "
+"you are delivering and how you document it."
+msgstr ""
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
+"readable and understandable."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
+" allows 1000 most common English words."
+msgstr ""
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./version-control-and-history.md:block 1 (header)
+msgid "order: 6"
+msgstr ""
+
+#: ./version-control-and-history.md:block 2 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The community MUST have a way to maintain [version "
+"control](../glossary.md#version-control) for the "
+"[code](../glossary.md#code)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"All files in the [codebase](../glossary.md#codebase) MUST be version "
+"controlled."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "Contributors SHOULD group relevant changes in commits."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Contributors SHOULD prefer file formats where the changes within the files "
+"can be easily viewed and understood in the version control system."
+msgstr ""
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./version-control-and-history.md:block 7 (paragraph)
+msgid ""
+"Version control means keeping track of changes to the code over time. This "
+"allows you to create structured documentation of the history of the "
+"codebase. This is essential for collaboration at scale."
+msgstr ""
+
+#: ./version-control-and-history.md:block 8 (paragraph)
+msgid "Distributed version control enables you to:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "have a full copy of the code and its history"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "revert to an earlier version of the codebase whenever you want to"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"record your changes and the reasons why you made them, to help future "
+"developers understand the process"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "compare two different versions"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "work on changes in parallel as a team before merging them together"
+msgstr ""
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"continue to work when the network is unavailable, merging changes back with "
+"everyone else’s at a later date"
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Substitute for [advertising maturity](document-maturity.md)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee the code executes correctly."
+msgstr ""
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee collaborators."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./version-control-and-history.md:block 16 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 18 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
+" use it or refresh your skills."
+msgstr ""
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
diff --git a/_site/locales/zh_Hant/LC_MESSAGES/messages.po b/_site/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..46cd90c3
--- /dev/null
+++ b/_site/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,2995 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-12-01 12:42+0800\n"
+"PO-Revision-Date: 2023-05-05 03:50+0000\n"
+"Last-Translator: Weblate Admin <toomore0929@gmail.com>\n"
+"Language-Team: Chinese (Traditional) <https://weblate.toomore.net/projects/"
+"pmpc/standard-for-public-codec/zh_Hant/>\n"
+"Language: zh_Hant\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Generator: Weblate 4.16.4\n"
+
+#
+#: ./bundle-policy-and-code.md:block 1 (header)
+msgid "order: 2"
+msgstr "order: 2"
+
+#: ./bundle-policy-and-code.md:block 2 (header)
+msgid "Bundle policy and source code"
+msgstr "政策與原始碼要合捆"
+
+#: ./bundle-policy-and-code.md:block 4 (header)
+msgid "Requirements"
+msgstr "需求規範"
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST include the "
+"[policy](../glossary.md#policy) that the source [code](../glossary.md#code) "
+"is based on."
+msgstr ""
+"[代碼庫](../glossary.md#codebase)必須包含[原始碼](../glossary."
+"md#code)所根據的[政策](../glossary.md#policy)。"
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include all source code that the policy is based on, "
+"unless used for fraud detection."
+msgstr "代碼庫必須包含根據政策而來的所有原始碼，用於偵測詐騙的原始碼則可除外。"
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr "政策應該採用機器可讀且明確的格式。"
+
+#: ./bundle-policy-and-code.md:block 5 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr "[持續整合](../glossary.md#continuous-"
+"integration)測試應該驗證原始碼與政策能一致執行。"
+
+#: ./bundle-policy-and-code.md:block 6 (header)
+msgid "Why this is important"
+msgstr "此措施為何重要"
+
+#: ./bundle-policy-and-code.md:block 7 (paragraph)
+msgid ""
+"Access to both the source code and the policy documents is necessary for "
+"understanding and reuse of, as well as collaboration in, a codebase. "
+"Understanding the context and the policies in that context is fundamental to"
+" understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them. To be able to evaluate whether to adopt a codebase in a "
+"new context, an organization will need to understand what process changes it"
+" must choose to make or how to contribute additional configurability to the "
+"existing solution in order to adapt it to the new context."
+msgstr ""
+"如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼"
+"與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的"
+"問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼"
+"庫，則組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額"
+"外調整設定，以適應新的情境。"
+
+#: ./bundle-policy-and-code.md:block 8 (header)
+msgid "What this does not do"
+msgstr "此措施辦不到的事"
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid "Guarantee that a codebase will reflect the bundled policy."
+msgstr "保證代碼庫能反映合捆的政策。"
+
+#: ./bundle-policy-and-code.md:block 9 (unordered list)
+msgid ""
+"Make sure packages comply with the local technical infrastructure or legal "
+"framework of a given public organization."
+msgstr "確保成套合捆內容符合地方性技術基礎建設，或是特定公共組織的法律架構。"
+
+#: ./bundle-policy-and-code.md:block 10 (header)
+msgid "How to test"
+msgstr "測試方式"
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr "與公務人員確認程式碼根據的所有政策內容都有包含在內。"
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr "與公務人員確認根據政策而來的所有原始碼都有包含在內。"
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr "確認政策內容是否能在機器上解讀。"
+
+#: ./bundle-policy-and-code.md:block 11 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr "確認原始碼與政策間的執行一致性能通過持續整合測試。"
+
+#: ./bundle-policy-and-code.md:block 12 (header)
+msgid "Policy makers: what you need to do"
+msgstr "政策制定者：需要的工作"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Collaborate with developers and designers to ensure there is no mismatch "
+"between policy code and source code."
+msgstr "與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
+"文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
+"，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr "請提供政策相關參考資料與連結。"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable such as"
+" [Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation),"
+" [Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) and "
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN)."
+msgstr ""
+"政策內容請使用明確且機器可讀的格式，像是[業務流程模型與標記法](https://en."
+"wikipedia.org/wiki/"
+"Business_Process_Model_and_Notation)、[決策模型與標記法](https://en.wikipedia"
+".org/wiki/Decision_Model_and_Notation)，以及[案例管理模型標記法](https://en."
+"wikipedia.org/wiki/CMMN)。"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Track policy with [the same version control](version-control-and-history.md)"
+" and documentation used to track source code."
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](version-control-and-history."
+"md)與文件。"
+
+#: ./bundle-policy-and-code.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed and whether it still matches the [intentions of the "
+"policy](document-objectives.md)."
+msgstr "定期檢查代碼庫中非政策程式碼的變動，以及確認是否仍符合[政策意圖](document-"
+"objectives.md)。"
+
+#: ./bundle-policy-and-code.md:block 14 (header)
+msgid "Management: what you need to do"
+msgstr "管理人員：需要的工作"
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr "讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
+
+#: ./bundle-policy-and-code.md:block 15 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr "確保政策制定者、開發人員與設計師朝相同目標努力。"
+
+#: ./bundle-policy-and-code.md:block 16 (header)
+msgid "Developers and designers: what you need to do"
+msgstr "開發人員與設計師：需要的工作"
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr "熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。"
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid ""
+"Work together with policy makers to ensure there is no mismatch between "
+"policy code and source code."
+msgstr "與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。"
+
+#: ./bundle-policy-and-code.md:block 17 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr "針對如何讓政策文字更清楚提供意見。"
+
+#: ./bundle-policy-and-code.md:block 18 (header)
+msgid "Further reading"
+msgstr "延伸閱讀"
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[Free online tools for building BPMN, CMMN and DMN diagrams at "
+"bmpn.io](https://bpmn.io/) by Camunda."
+msgstr ""
+"Camunda [於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN "
+"等模型與表記法圖表](https://bpmn.io/)的免費線上工具。"
+
+#: ./bundle-policy-and-code.md:block 19 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+"Trisotech 提供的 [BPMN 快速指南](https://www.bpmnquickguide.com/"
+"view-bpmn-quick-guide/)。"
+
+#: ./code-in-the-open.md:block 1 (header)
+msgid "order: 1"
+msgstr "order: 1"
+
+#: ./code-in-the-open.md:block 2 (header)
+msgid "Code in the open"
+msgstr "原始碼要開放"
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source [code](../glossary.md#code) for any "
+"[policy](../glossary.md#policy) in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+"任何使用中的[政策](../glossary.md#policy)所有[原始碼](../glossary."
+"md#code)都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。"
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr "任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
+"眾取用。"
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT upload sensitive information regarding users, their "
+"organization or third parties to the "
+"[repository](../glossary.md#repository)."
+msgstr "貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到[儲存庫](../g"
+"lossary.md#repository)中。"
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr "目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。"
+
+#: ./code-in-the-open.md:block 5 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+"可選擇是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間"
+"可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
+
+#: ./code-in-the-open.md:block 7 (paragraph)
+msgid "Coding in the open:"
+msgstr "以開放精神編寫原始碼能："
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "improves transparency"
+msgstr "改善資訊透明"
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "increases code quality"
+msgstr "提高程式碼品質"
+
+#: ./code-in-the-open.md:block 8 (unordered list)
+msgid "facilitates the auditing processes"
+msgstr "促進稽核流程"
+
+#: ./code-in-the-open.md:block 9 (paragraph)
+msgid ""
+"These aspects together create more opportunities for citizens to understand "
+"how software and policy impact their interactions with a public "
+"organization."
+msgstr "這些面向讓公民更有機會能瞭解，軟體與政策如何影響他們與公共組織的互動。"
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid "Make source code or policy reusable."
+msgstr "讓原始碼或政策可以重複使用。"
+
+#: ./code-in-the-open.md:block 11 (unordered list)
+msgid ""
+"Make the [codebase](../glossary.md#codebase) and the code within it "
+"understandable to as many people as possible."
+msgstr "讓盡可能越多人能讀懂[代碼庫](../glossary.md#codebase)以及當中的程式碼。"
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr "確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形"
+"式的身分核對或授權，就能在原始貢獻組織之外，查看這些原始碼。"
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase files and commit history do not include sensitive "
+"information."
+msgstr "確認代碼庫檔案與提交歷史紀錄不包含敏感性資訊。"
+
+#: ./code-in-the-open.md:block 13 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr "檢查目前非使用中的原始碼是否有公開。"
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Develop policies in the open."
+msgstr "制定合乎開放精神的政策。"
+
+#: ./code-in-the-open.md:block 15 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr "以公開透明的政策為優先。"
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr "孕育擁抱開放、重視學習、歡迎意見回饋的文化。"
+
+#: ./code-in-the-open.md:block 17 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr "與外部供應商和自由工作者以開放精神的方式協作。"
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者"
+"名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
+
+#: ./code-in-the-open.md:block 19 (unordered list)
+msgid ""
+"Clearly split data and code, in order to meet the requirement about "
+"sensitive information above."
+msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。"
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
+"12/coding-in-the-open/)》。"
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/"
+"government/publications/open-source-guidance/when-code-should-be-open-or-"
+"closed)》。"
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
+"government/publications/open-source-guidance/security-considerations-when-"
+"coding-in-the-open)》。"
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/"
+"technology/deploying-software-regularly)》。"
+
+#: ./code-in-the-open.md:block 21 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[政府數位服務團如何使用 GitHub](https://gdstechnology."
+"blog.gov.uk/2014/01/27/how-we-use-github/)》。"
+
+#: ./continuous-integration.md:block 1 (header)
+msgid "order: 12"
+msgstr "order: 12"
+
+#: ./continuous-integration.md:block 2 (header)
+msgid "Use continuous integration"
+msgstr "使用持續整合"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"All functionality in the source [code](../glossary.md#code) MUST have "
+"automated tests."
+msgstr "[原始碼](../glossary.md#code)中的所有功能都必須有自動化測試。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the [codebase](../glossary.md#codebase)."
+msgstr "所有貢獻內容都必須先通過自動化測試，才能上傳至[代碼庫](../glossary."
+"md#codebase)。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr "代碼庫必須有說明貢獻內容結構的相關準則。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "The codebase MUST have active contributors."
+msgstr "代碼庫必須有活躍貢獻者。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr "代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr "應該監督原始碼測試與文件的涵蓋範圍。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr "可選擇是否測試[政策](../glossary."
+"md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
+
+#: ./continuous-integration.md:block 5 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "Using [continuous integration](../glossary.md#continuous-integration):"
+msgstr "使用[持續整合](../glossary.md#continuous-integration)："
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "allows you to quickly identify problems with the codebase,"
+msgstr "可以讓您快速找出代碼庫的問題所在，"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"enables risk taking and focusing on problem solving while minimizing stress "
+"for the contributors,"
+msgstr "能在降低貢獻者面臨壓力的同時，允許承擔風險並且專注在解決問題上，"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"lowers barriers for new contributors by reducing the amount of understanding"
+" necessary to suggest changes,"
+msgstr "可降低新貢獻者對整體內容理解的門檻，讓他們更容易提出修改，"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "leads to more maintainable code,"
+msgstr "讓程式碼更容易維護，"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid "speeds up the development cycle."
+msgstr "能加速開發週期。"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Smaller, more regular contributions are typically easier to evaluate and "
+"lower risk compared to large infrequent changes."
+msgstr "修改內容較少、時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大、累積很"
+"久才一次提出的變更。"
+
+#: ./continuous-integration.md:block 7 (unordered list)
+msgid ""
+"Codebases in active development more reliably provide opportunities for "
+"collaboration and feedback."
+msgstr "活躍開發中的代碼庫較能提供協作與意見回饋的機會。"
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid ""
+"Create a fault tolerant infrastructure that will work and scale perfectly."
+msgstr "建立能夠順暢作業、可擴展，且能容錯的基礎架構。"
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Create meaningful tests."
+msgstr "建立有意義的測試。"
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Test for real life situations."
+msgstr "測試實際會發生的情境。"
+
+#: ./continuous-integration.md:block 9 (unordered list)
+msgid "Guarantee the code will deliver exactly the same policy result."
+msgstr "保證交付的程式碼與政策期望的成果確實相同。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr "確認有測試可用。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that code coverage tools check that coverage is at 100% of the code."
+msgstr "確認程式碼覆蓋率工具能檢查到 100% 的程式碼。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr "確認有貢獻準則說明貢獻內容的結構。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr "確認最近三個月內有貢獻內容上傳。"
+
+#: ./continuous-integration.md:block 11 (unordered list)
+msgid "Check if code coverage data is published."
+msgstr "檢查程式碼覆蓋率數據是否有公布。"
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Involve management as well as developers and designers as early in the "
+"process as possible and keep them engaged throughout development of your "
+"policy."
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序"
+"。"
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr "確保政策文件也有設好自動化測試。"
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr "如果政策文件未能通過測試，請立即修正。"
+
+#: ./continuous-integration.md:block 13 (unordered list)
+msgid ""
+"Make sure the code reflects any changes to the policy (see [Maintain version"
+" control](version-control-and-history.md))."
+msgstr "確保程式碼能反映出政策的任何變動（請參閱[維護版本控制](version-control-and-"
+"history.md)）。"
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr "確保能儘快且經常給真正的終端使用者進行測試。"
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Plan the work to deliver small parts very often instead of large parts less "
+"frequently."
+msgstr "以頻繁交付少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。"
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr "聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。"
+
+#: ./continuous-integration.md:block 15 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr "發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management structure the work plan such that it can be delivered as "
+"small increments."
+msgstr "協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次交付。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Help management and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式"
+"。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Structure code written to handle conditions which are difficult to create in"
+" a test environment in such a way that the conditions can be simulated "
+"during testing. Forms of resource exhaustion such as running out of storage "
+"space and memory allocation failure are typical examples of difficult to "
+"create conditions."
+msgstr ""
+"編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
+"來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr "調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Deploy often."
+msgstr "經常部署。"
+
+#: ./continuous-integration.md:block 17 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr "至少每天整合工作內容一次。"
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+"Martin Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/"
+"continuousIntegration.html)》。"
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[What is continuous delivery](https://www.continuousdelivery.com/) by Jez "
+"Humble."
+msgstr "Jez Humble《[什麼是持續交付](https://www.continuousdelivery.com/)》。"
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/"
+"standards/continuous-delivery.html)》。"
+
+#: ./continuous-integration.md:block 19 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/"
+"service-manual/technology/quality-assurance-testing-your-service-"
+"regularly)》。"
+
+#: ./document-maturity.md:block 1 (header)
+msgid "order: 16 redirect_from: - criteria/advertise-maturity"
+msgstr "order: 16 redirect_from: - criteria/advertise-maturity"
+
+#: ./document-maturity.md:block 2 (header)
+msgid "Document codebase maturity"
+msgstr "記錄代碼庫成熟度"
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid "The [codebase](../glossary.md#codebase) MUST be versioned."
+msgstr "[代碼庫](../glossary.md#codebase)必須註明版本編號。"
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is ready to use MUST only depend on other codebases that "
+"are also ready to use."
+msgstr "準備好可供使用的代碼庫，必須只能依賴其他也已經準備好可供使用的代碼庫。"
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase that is not yet ready to use MUST have one of the labels: "
+"prototype, alpha, beta or pre-release version."
+msgstr "尚未準備好使用的代碼庫，必須有所列標籤之一：prototype、alpha、beta、pre-"
+"release 等版本進度。"
+
+#: ./document-maturity.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
+
+#: ./document-maturity.md:block 7 (paragraph)
+msgid ""
+"Clearly signalling a codebase's maturity helps others decide whether to "
+"reuse, invest in or contribute to it."
+msgstr "清楚標示代碼庫的成熟度，有助於他人決定是否要重複使用、投資，或為該代碼庫做出"
+"貢獻。"
+
+#: ./document-maturity.md:block 9 (unordered list)
+msgid "Guarantee that others will use the [code](../glossary.md#code)."
+msgstr "保證他人會來使用[程式碼](../glossary.md#code)。"
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Confirm that it is clear where to get the newest version."
+msgstr "確認有清楚表明最新版的取得位置。"
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase doesn't depend on any codebases marked with a less"
+" mature status."
+msgstr "確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。"
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase is ready to use or labeled as prototype, alpha, "
+"beta or pre-release version."
+msgstr "確認代碼庫是已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-"
+"release 等開發中版本。"
+
+#: ./document-maturity.md:block 11 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr "檢查是否有變更紀錄。"
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any code "
+"developed needs to be tested and improved before it can be put into service."
+msgstr "制定[政策](../glossary.md#policy)時，請記住任何開發出來的程式碼都必須先經過測"
+"試與改善，才能夠投入服務。"
+
+#: ./document-maturity.md:block 13 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。"
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that services only rely on codebases of equal or greater maturity "
+"than the service. For example, don't use a beta codebase in a production "
+"service or a prototype codebase in a beta service."
+msgstr ""
+"要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 公測版代碼庫，公測版服務不要使用 prototype "
+"原型代碼庫。"
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"If the codebase is not ready for general use, work with the developers to "
+"ensure the codebase is properly labeled:"
+msgstr "若代碼庫尚未準備好供一般使用，請與開發人員一起確保該代碼庫是否有標示適當標籤"
+"："
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"prototype: to test the look and feel, and to internally prove the concept of"
+" the technical possibilities,"
+msgstr "prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術的可行性概念，"
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid "alpha: to do guided tests with a limited set of users,"
+msgstr "alpha：內部測試，在限制的一群使用者中進行引導性測試，"
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"beta: to open up testing to a larger section of the [general "
+"public](../glossary.md#general-public), for example to test if the codebase "
+"works at scale,"
+msgstr ""
+"beta：公開測試，讓更多[一般大眾](../glossary.md#general-"
+"public)參與測試，例如測試代碼庫在大規模操作下是否仍能運作，"
+
+#: ./document-maturity.md:block 15 (unordered list)
+msgid ""
+"pre-release version: code that is ready to be released but hasn't received "
+"formal approval yet."
+msgstr "pre-release：準發行版，已經準備好發行，但尚未獲得正式批准的程式碼。"
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Add a prominent header to every interface that indicates the maturity level "
+"of the code."
+msgstr "在每個指示程式碼成熟度的介面中加上明顯的標頭。"
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid "Version all releases."
+msgstr "所有正式發行的程式碼都要有版本編號。"
+
+#: ./document-maturity.md:block 17 (unordered list)
+msgid ""
+"Especially in 'rolling release' scenarios, the version may be automatically "
+"derived from the [version control](../glossary.md#version-control) system "
+"metadata (for example by using [git describe](https://git-scm.com/docs/git-"
+"describe))."
+msgstr ""
+"特別是在採用「滾動發行」的情況下，程式碼的版本資訊可以根據[版本控制](../gloss"
+"ary.md#version-control)系統的中介資料自動衍生（例如使用[git describe](https"
+"://git-scm.com/docs/git-describe)）。"
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
+"build-and-improve-services/service-design-and-delivery-process)》。"
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
+"agile-delivery)》。"
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr "許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。"
+
+#: ./document-maturity.md:block 19 (unordered list)
+msgid ""
+"[What are the Discovery, Alpha, Beta and Live stages in developing a "
+"service? [Video 0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc) by "
+"the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[什麼是服務開發當中的探索、Alpha、Beta、上線階段？ [影片 "
+"0'0\"59]](https://www.youtube.com/watch?v=_cyI7DMhgYc)》。"
+
+#: ./document-objectives.md:block 1 (header)
+msgid "order: 8"
+msgstr "order: 8"
+
+#: ./document-objectives.md:block 2 (header)
+msgid "Document codebase objectives"
+msgstr "代碼庫要有目標文件"
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST contain documentation of its "
+"objectives, like a mission and goal statement, that is understandable by "
+"developers and designers so that they can use or contribute to the codebase."
+msgstr ""
+"[代碼庫](../glossary.md#codebase)必須包含描寫目標的文件，像是主旨、使命或目標"
+"陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢"
+"獻。"
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr "代碼庫文件應該清楚描述[政策](../glossary."
+"md#policy)目標與代碼庫目標之前的關聯。"
+
+#: ./document-objectives.md:block 5 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-"
+"public)看的代碼庫目標。"
+
+#: ./document-objectives.md:block 7 (paragraph)
+msgid "Documenting codebase objectives:"
+msgstr "以文件記錄代碼庫目標："
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"provides an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr "提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。"
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid "helps scope your own development."
+msgstr "幫助劃定您自己開發專案的範圍。"
+
+#: ./document-objectives.md:block 8 (unordered list)
+msgid ""
+"clearly communicates to other stakeholders and contributors the purpose of "
+"the codebase and the modules of which it is composed."
+msgstr "將代碼庫以及所包含模組的目的用途，清楚告知其他利害關係人與貢獻者。"
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee that the codebase achieves the stated objective(s)."
+msgstr "保證代碼庫能達成其陳述的目標。"
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid "Guarantee contributions to the codebase."
+msgstr "保證會有人為代碼庫做出貢獻。"
+
+#: ./document-objectives.md:block 10 (unordered list)
+msgid ""
+"Prevent other codebases from attempting to achieve the same objectives."
+msgstr "預防其他代碼庫試圖達成相同目標。"
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr "確認代碼庫文件有包含代碼庫目標，或主旨、使命等。"
+
+#: ./document-objectives.md:block 12 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr "將政策目標加入代碼庫文件中，例如「`README`」文件當中。"
+
+#: ./document-objectives.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development like value and ethics based policies, for example accessibility "
+"or equal opportunity."
+msgstr "納入會影響社會群體、代碼庫與開發目標的相關政策，例如可近用無障礙環境，或機會"
+"平等等價值或倫理取向的政策。"
+
+#: ./document-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr "將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
+
+#: ./document-objectives.md:block 18 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr "將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。"
+
+#: ./document-objectives.md:block 20 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+"Marek Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
+"RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
+
+#: ./documenting.md:block 1 (header)
+msgid "order: 9"
+msgstr "order: 9"
+
+#: ./documenting.md:block 2 (header)
+msgid "Document the code"
+msgstr "程式碼要有文件"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"All of the functionality of the [codebase](../glossary.md#codebase), "
+"[policy](../glossary.md#policy) as well as source, MUST be described in "
+"language clearly understandable for those that understand the purpose of the"
+" [code](../glossary.md#code)."
+msgstr ""
+"[代碼庫](../glossary.md#codebase)的所有功能、[政策](../glossary."
+"md#policy)及原始碼，都必須以可清楚瞭解的用語描述，讓懂[程式碼](../glossary."
+"md#code)目的用途的人也能夠理解。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the source code."
+msgstr "代碼庫文件必須說明如何安裝與執行原始碼。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr "代碼庫文件必須為關鍵功能舉出範例。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-"
+"public)和記者等廣泛的利害關係人都能清楚明白。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也"
+"應該包含測試資料集。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr "代碼庫文件應該包含所有功能的範例。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架"
+"構圖表示。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr "應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr "可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
+
+#: ./documenting.md:block 5 (unordered list)
+msgid "Testing the code by using examples in the documentation is OPTIONAL."
+msgstr "可選擇是否以文件中的範例來測試程式碼。"
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "Users can start using and contributing more quickly."
+msgstr "使用者可以更快速上手代碼庫的使用並做出貢獻。"
+
+#: ./documenting.md:block 7 (unordered list)
+msgid ""
+"You help people discover the codebase, especially people asking 'is there "
+"already code that does something like this'."
+msgstr "能幫助他人找到這個代碼庫，特別是那些在問「是不是已經有提供某某功能的程式碼」"
+"的人。"
+
+#: ./documenting.md:block 7 (unordered list)
+msgid "This provides transparency into your organization and processes."
+msgstr "讓貴組織單位與其流程資訊更透明。"
+
+#: ./documenting.md:block 9 (unordered list)
+msgid ""
+"Contribute directly to more reusable, portable code (see [Create reusable "
+"and portable code](./reusable-and-portable-codebases.md))."
+msgstr ""
+"直接貢獻出更可重複使用，以及更具可攜性的程式碼（請參閱[編寫可重複使用且具可攜"
+"性的程式碼](./reusable-and-portable-codebases.md)）。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以"
+"清楚明白。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr "確認文件有說明如何安裝與執行原始碼。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr "確認文件有包含主要功能的範例。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr "向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr "檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr "檢查文件中列舉的所有功能都包含範例。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr "檢查文件中是否包含高層架構圖，或類似的組件關係圖表。"
+
+#: ./documenting.md:block 11 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated from code, and links and images are "
+"tested."
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認由程式碼生成的文件，並檢查連結與"
+"圖片等。"
+
+#: ./documenting.md:block 13 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr "定期查看代碼庫的非政策程式碼的變動情況。"
+
+#: ./documenting.md:block 13 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr "針對如何讓非政策文件更清楚易懂提供意見回饋。"
+
+#: ./documenting.md:block 15 (unordered list)
+msgid "Try to use the codebase."
+msgstr "嘗試使用代碼庫。"
+
+#: ./documenting.md:block 15 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr "確保您同時瞭解政策、原始碼以及文件內容。"
+
+#: ./documenting.md:block 17 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr "定期查看代碼庫中非原始碼部分的變動情況。"
+
+#: ./documenting.md:block 17 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
+
+#: ./documenting.md:block 19 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
+
+#: ./findability.md:block 1 (header)
+msgid "order: 14"
+msgstr "order: 14"
+
+#: ./findability.md:block 2 (header)
+msgid "Make the codebase findable"
+msgstr "代碼庫可查詢得到"
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be findable using a search "
+"engine by describing the problem it solves in natural language."
+msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，必須能搜尋得到[代碼"
+"庫](../glossary.md#codebase)。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid "The codebase MUST be findable using a search engine by codebase name."
+msgstr "在搜尋引擎查找代碼庫名稱時，必須能搜尋得到代碼庫。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr "維護人員應該將代碼庫提交至相關的軟體目錄上。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理"
+"人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr "代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../gloss"
+"ary.md#repository)、位置、網站等。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+"代碼庫應該包含機器可讀的中介資料說明，例如採用 [publiccode."
+"yml](https://github.com/publiccodeyml/publiccode.yml) 格式的檔案。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr "可選擇是否為代碼庫設定專用的網域名稱。"
+
+#: ./findability.md:block 5 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr "可選擇是否在社群舉辦的會議中定期進行簡報。"
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"Proactiveness is needed; just publishing a codebase and hoping it's found "
+"doesn't work."
+msgstr "必須主動積極；不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫。"
+
+#: ./findability.md:block 7 (unordered list)
+msgid "A metadata description file increases discoverability."
+msgstr "有中介資料說明檔案會讓代碼庫更容易被發現。"
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"The more findable a codebase is, the more potential new collaborators will "
+"find it."
+msgstr "一旦代碼庫越容易被發現，更多的潛在協作者也就找得到它。"
+
+#: ./findability.md:block 7 (unordered list)
+msgid ""
+"By having well-written metadata containing a unique and persistent "
+"identifer, such as a Wikidata item or FSF software directory listing, and "
+"thus being part of the semantic web, it will be easier for other people to "
+"refer, cite, disambiguate and discover the codebase through third party "
+"tools."
+msgstr ""
+"撰寫出良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，"
+"或是放到 FSF 自由軟體基金會的軟體目錄列表之中，使代碼庫成為語意網路中的一部份"
+"。如此一來，他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。"
+
+#: ./findability.md:block 9 (unordered list)
+msgid "Ensure new collaborators or replicators."
+msgstr "確認新的協作人員或複製者。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a plain English problem "
+"description."
+msgstr "確認以白話英語敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
+"庫放在搜尋結果的第一頁中。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by a technical problem description."
+msgstr "確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代"
+"碼庫放在搜尋結果的第一頁中。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase appears in the first set of results on more than "
+"one major search engine when searching by the codebase name."
+msgstr "確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋"
+"結果的第一頁中。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr "檢查代碼庫有刊登在相關軟體型錄上。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr "檢查永久唯一識別碼條目有提及主要貢獻者。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr "檢查永久唯一識別碼條目中有包含儲存庫位置。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr "檢查永久唯一識別碼條目有列出代碼庫網站。"
+
+#: ./findability.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr "檢查中介資料說明檔案是機器可讀的格式。"
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr "貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。"
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr "請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。"
+
+#: ./findability.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevent conferences."
+msgstr "在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。"
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr "為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。"
+
+#: ./findability.md:block 15 (unordered list)
+msgid "Ensure people involved in the project present at relevant conferences."
+msgstr "確保專案參與人員出席相關會議或作簡報介紹。"
+
+#: ./findability.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。"
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Search engine optimization."
+msgstr "搜尋引擎最佳化。"
+
+#: ./findability.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr "推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。"
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+"Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/"
+"Wikidata:Introduction)》。"
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Softare Foundation."
+msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
+"Main_Page)》。"
+
+#: ./findability.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
+"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
+"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
+"分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
+"對應的特性要怎麼處理。"
+
+#: ./index.md:block 1 (header)
+msgid "Criteria"
+msgstr "準則"
+
+#: ./index.md:block 3 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
+
+#: ./index.md:block 4 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+
+#: ./index.md:block 5 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+
+#: ./make-contributing-easy.md:block 1 (header)
+msgid "order: 5"
+msgstr "order: 5"
+
+#: ./make-contributing-easy.md:block 2 (header)
+msgid "Make contributing easy"
+msgstr "貢獻要容易"
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST have a public issue tracker "
+"that accepts suggestions from anyone."
+msgstr "[代碼庫](../glossary.md#codebase)必須有個可以公開接受任何人建議的議題追蹤器。"
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include instructions for how to privately report security "
+"issues for responsible disclosure."
+msgstr "代碼庫必須說明，如何私下回報安全性問題來達成負責任的揭露。"
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在"
+"「`README`」檔案中。"
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵遞"
+"論壇）。"
+
+#: ./make-contributing-easy.md:block 5 (unordered list)
+msgid ""
+"The documentation SHOULD include instructions for how to report potentially "
+"security sensitive issues on a closed channel."
+msgstr "文件應該說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。"
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid ""
+"Enables users to fix problems and add features to the shared codebase "
+"leading to better, more reliable and feature rich software."
+msgstr "讓使用者能夠為共享的代碼庫修復問題與新增功能，能讓軟體變得更好、更可靠、功能"
+"更豐富。"
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Allows collaborative uptake of shared digital infrastructure."
+msgstr "讓人們能以協作方式採用共享的數位基礎建設。"
+
+#: ./make-contributing-easy.md:block 7 (unordered list)
+msgid "Helps users decide to use one codebase over another."
+msgstr "幫助使用者在代碼庫間做出選擇。"
+
+#: ./make-contributing-easy.md:block 9 (unordered list)
+msgid "Guarantee others will reuse the codebase."
+msgstr "保證其他人會重複使用代碼庫。"
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr "確認有公開的議題追蹤器。"
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr "確認有說明如何私下通報安全性問題。"
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr "確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。"
+
+#: ./make-contributing-easy.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
+
+#: ./make-contributing-easy.md:block 13 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr "追蹤代碼庫中的[政策](../glossary."
+"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
+
+#: ./make-contributing-easy.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久"
+"貢獻。"
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid "Respond promptly to requests."
+msgstr "快速回應請求。"
+
+#: ./make-contributing-easy.md:block 17 (unordered list)
+msgid ""
+"Keep your management informed of the time and resources you require to "
+"support other contributors."
+msgstr "持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。"
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/"
+"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
+"project-1ebf)》。"
+
+#: ./make-contributing-easy.md:block 19 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
+"2017/09/04/the-benefits-of-coding-in-the-open/)》。"
+
+#: ./open-licenses.md:block 1 (header)
+msgid "order: 13"
+msgstr "order: 13"
+
+#: ./open-licenses.md:block 2 (header)
+msgid "Publish with an open license"
+msgstr "發行採用開放授權"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) and documentation MUST be licensed such that"
+" it may be freely reusable, changeable and redistributable."
+msgstr "所有[程式碼](../glossary.md#code)與文件，皆必須採用使其得以自由重複使用、自由"
+"修改、自由再次散布的授權條款。"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+"軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid "All code MUST be published with a license file."
+msgstr "所有程式碼皆必須搭配授權條款檔案一併發行。"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the [codebase](../glossary.md#codebase)."
+msgstr "不得要求貢獻者將其貢獻的程式碼著作權轉讓給[代碼庫](../glossary.md#codebase)。"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。"
+
+#: ./open-licenses.md:block 5 (unordered list)
+msgid ""
+"Having multiple licenses for different types of code and documentation is "
+"OPTIONAL."
+msgstr "可選擇是否為不同類型的程式碼與文件採用多重授權條款。"
+
+#: ./open-licenses.md:block 7 (unordered list)
+msgid ""
+"Makes it possible for anyone to see the code and know that they can and how "
+"they can reuse it."
+msgstr "讓任何人都可以查看程式碼，並知道他們可以與該如何重複利用這些程式碼。"
+
+#: ./open-licenses.md:block 9 (unordered list)
+msgid "Prevent use of the code by any specific actors."
+msgstr "預防任何特定行為人使用程式碼。"
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr "確認代碼庫有清楚給予授權條款。"
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+"確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/"
+")，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/"
+"licenses/)。"
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr "確認代碼庫中有包含其採用的授權條款檔案。"
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr "確認貢獻指南中，以及[儲存庫](../glossary."
+"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
+
+#: ./open-licenses.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+"在代碼庫[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires code to be [open "
+"source](../glossary.md#open-source)."
+msgstr ""
+"制定要求程式碼必須採用[開放原始碼](../glossary.md#open-"
+"source)授權的[政策](../glossary.md#policy)。"
+
+#: ./open-licenses.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr "制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。"
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their code by publishing it "
+"under an open source license."
+msgstr "只與能採用開放原始碼授權交付與發行其程式碼的開放原始碼軟體供應商合作。"
+
+#: ./open-licenses.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作"
+"品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用"
+"、自由修改、自由再次散布等，因此未能符合規定。"
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr "每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。"
+
+#: ./open-licenses.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。"
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/"
+"osd)》，所有開放原始碼授權條款皆符合這套定義。"
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)》。"
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
+")》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
+
+#: ./open-licenses.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
+")提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
+
+#: ./open-standards.md:block 1 (header)
+msgid "order: 11"
+msgstr "order: 11"
+
+#: ./open-standards.md:block 2 (header)
+msgid "Use open standards"
+msgstr "採用開放標準"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"For features of the [codebase](../glossary.md#codebase) that facilitate the "
+"exchange of data the codebase MUST use an [open "
+"standard](../glossary.md#open-standard) that meets the [Open Source "
+"Initiative Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+"[代碼庫](../glossary.md#codebase)如要達成促進資料交換的特性，就必須採用符合["
+"開放原始碼促進會其開放標準需求規範](https://opensource.org/"
+"osr)的[開放標準](../glossary.md#open-standard)。"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr "如果有使用到任何的非開放標準，則必須在文件中清楚記錄。"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的"
+"連結。"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr "代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr "如果還沒有已存在的開放標準可採用，則應該投入開發新標準。"
+
+#: ./open-standards.md:block 5 (unordered list)
+msgid ""
+"Standards that are machine testable SHOULD be preferred over those that are "
+"not."
+msgstr "採用標準時，應該優先選擇可經機器測試的標準。"
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Creates interoperability between systems."
+msgstr "為不同的系統之間建立互通性。"
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid "Reduces possible vendor lock-in."
+msgstr "降低廠商套牢的可能性。"
+
+#: ./open-standards.md:block 7 (unordered list)
+msgid ""
+"Guarantees access to the knowledge required to reuse and contribute to the "
+"codebase."
+msgstr "保證可以取得重複利用與貢獻代碼庫所需的知識。"
+
+#: ./open-standards.md:block 9 (unordered list)
+msgid "Make it understandable how to use the software."
+msgstr "讓軟體的操作方法變得可以瞭解。"
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr "確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。"
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr "確認若有採用任何的非開放標準，皆有清楚記錄在文件中。"
+
+#: ./open-standards.md:block 11 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用"
+"任何標準時，則留下聲明。"
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr "以政策要求盡可能在任何情況下使用開放標準。"
+
+#: ./open-standards.md:block 13 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr "禁止採購不採用開放標準的技術科技。"
+
+#: ./open-standards.md:block 15 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in "
+"[code](../glossary.md#code) reviews."
+msgstr "考慮在[程式碼](../glossary.md#code)審查中納入開放標準依循評估。"
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr "將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。"
+
+#: ./open-standards.md:block 17 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr "審查提交紀錄與其他[儲存庫](../glossary."
+"md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
+
+#: ./open-standards.md:block 19 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/"
+"publications/open-standards-principles/open-standards-"
+"principles)》[政策](../glossary.md#policy)報告。"
+
+#: ./open-to-contributions.md:block 1 (header)
+msgid "order: 4"
+msgstr "order: 4"
+
+#: ./open-to-contributions.md:block 2 (header)
+msgid "Welcome contributors"
+msgstr "歡迎貢獻者"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST allow anyone to submit "
+"suggestions for changes to the codebase."
+msgstr "[代碼庫](../glossary.md#codebase)必須允許任何人針對代碼庫提出修改建議。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開"
+"發，例如以「`CONTRIBUTING`」檔案說明。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
+"RNANCE`」檔案來說明。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr "代碼庫應該宣布投入其開發與維護工作的參與組織單位。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr "代碼庫應該要有可公開取得的發展路線圖。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr "代碼庫應該公布代碼庫的活動統計數據。"
+
+#: ./open-to-contributions.md:block 5 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr "可選擇是否為代碼庫加入貢獻者的行為準則。"
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Helps newcomers understand and trust the codebase community's leadership."
+msgstr "幫助新參與者瞭解並且信任代碼庫社群的領導。"
+
+#: ./open-to-contributions.md:block 7 (unordered list)
+msgid ""
+"Prevents the community that works on a codebase splitting because there is "
+"no way to influence its goals and progress, resulting in diverging "
+"communities."
+msgstr "避免參與者因為無法影響代碼庫的目標與進展，而造成代碼庫社群分裂成分歧的社群。"
+
+#: ./open-to-contributions.md:block 9 (unordered list)
+msgid "Guarantee others will join the community."
+msgstr "保證他人會參與社群。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr "確認可以提交修改建議給代碼庫。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr "確認代碼庫有貢獻指引。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr "確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr "檢查是否有參與的組織單位名單。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a roadmap."
+msgstr "檢查是否有發展路線圖。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for published activity statistics."
+msgstr "檢查是否有公布活動統計數據。"
+
+#: ./open-to-contributions.md:block 11 (unordered list)
+msgid "Check for a code of conduct."
+msgstr "檢查是否有行為準則。"
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary."
+"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
+
+#: ./open-to-contributions.md:block 13 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr "考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。"
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr "確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。"
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中"
+"。"
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與"
+"的時間長度等。"
+
+#: ./open-to-contributions.md:block 15 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。"
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/"
+"building-community/)》。"
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-o"
+"pen-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
+"project/)》。"
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+"開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
+"leadership-and-governance/)》。"
+
+#: ./open-to-contributions.md:block 19 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr "Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。"
+
+#: ./require-review.md:block 1 (header)
+msgid "order: 7"
+msgstr "order: 7"
+
+#: ./require-review.md:block 2 (header)
+msgid "Require review of contributions"
+msgstr "要求審查貢獻內容"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"[codebase](../glossary.md#codebase) MUST be reviewed by another contributor."
+msgstr "所有被接受或是提交給[代碼庫](../glossary."
+"md#codebase)正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews MUST include source, [policy](../glossary.md#policy), tests and "
+"documentation."
+msgstr "審查必須包含原始碼、[政策](../glossary.md#policy)、測試、文件等。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD conform to the standards, architecture and decisions "
+"set out in the codebase in order to pass review."
+msgstr "貢獻內容應該遵循代碼庫的標準、架構、決策安排等，以通過審查。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the [code](../glossary.md#code) and the "
+"tests of the codebase."
+msgstr "審查內容應該包含執行[程式碼](../glossary.md#code)與執行代碼庫測試。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr "貢獻內容應該由與貢獻者不同背景情境的人來審查。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr "版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr "審查應該在兩個工作天內進行。"
+
+#: ./require-review.md:block 5 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr "可選擇是否由多位審查人員進行審查。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Increases codebase quality."
+msgstr "提升代碼庫品質。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Reduces security risks as well as operational risks."
+msgstr "降低安全性風險與營運風險。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Creates a culture of making every contribution great."
+msgstr "打造每份貢獻內容皆能有品質的文化。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid "Catches the most obvious mistakes that could happen."
+msgstr "揪出可能發生的極明顯錯誤。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Gives contributors the security that their contributions are only accepted "
+"if they really add value."
+msgstr "只有真正能為代碼庫提升價值的貢獻內容才會被接受，可以給予貢獻者安全感。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Assures contributors of a guaranteed time for feedback or collaborative "
+"improvement."
+msgstr "向貢獻者保證在一段時間內提供意見回饋或是合作改善。"
+
+#: ./require-review.md:block 7 (unordered list)
+msgid ""
+"Prompt reviews increase both rate of delivery and contributor engagement."
+msgstr "快速審查能提高貢獻者交付貢獻內容的頻率以及參與熱度。"
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Guarantee the right solution to a problem."
+msgstr "保證能找到問題的合適解決方案。"
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Mean that reviewers are liable."
+msgstr "代表審查人員必須承擔責任。"
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Absolve a contributor from writing documentation and tests."
+msgstr "貢獻者能從編寫文件與測試中免除責任。"
+
+#: ./require-review.md:block 9 (unordered list)
+msgid "Provide you with the right reviewers."
+msgstr "提供您合適的審查人選。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr "確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr "確認審查內容包含原始碼、政策、測試、文件等。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check if reviews cover conformance to standards, architecture and codebase "
+"guidelines."
+msgstr "檢查審查範圍有涵蓋是否遵循標準、架構、代碼庫指引等。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check with reviewers if they run the code and tests during review."
+msgstr "檢查審查人員在審查時是否有執行程式碼與測試。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr "與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr "檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。"
+
+#: ./require-review.md:block 11 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr "檢查貢獻提交與審查之間的時間間隔。"
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just code, is reviewed."
+msgstr "制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。"
+
+#: ./require-review.md:block 13 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr "採用具有審查與意見回饋功能的版本控制系統或作業流程。"
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make delivering great code a shared objective."
+msgstr "將交付妥善程式碼作為共同目標。"
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr "確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。"
+
+#: ./require-review.md:block 15 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr "創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。"
+
+#: ./require-review.md:block 15 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr "確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。"
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr "請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。"
+
+#: ./require-review.md:block 17 (unordered list)
+msgid ""
+"Try to respond to others' requests for code review promptly, initially "
+"providing feedback about the concept of the change."
+msgstr "當他人請求您審查程式碼時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。"
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way."
+"cloudapps.digital/manuals/code-review-guidelines.html#content)》。"
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/)."
+msgstr ""
+"[GitHub](https://docs.github.com/en/repositories/"
+"configuring-branches-and-merges-in-your-repository/"
+"defining-the-mergeability-of-pull-requests/about-protected-branches) 與 "
+"[GitLab](https://about.gitlab.com/2014/11/26/keeping-your-code-protected/) "
+"平臺的分支保護說明。"
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/"
+"the-gentle-art-of-patch-review/)》。"
+
+#: ./require-review.md:block 19 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/"
+"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id."
+"g43d857af8_0177)》。"
+
+#: ./reusable-and-portable-codebases.md:block 1 (header)
+msgid "order: 3"
+msgstr "order: 3"
+
+#: ./reusable-and-portable-codebases.md:block 2 (header)
+msgid "Create reusable and portable code"
+msgstr "程式碼要可重複使用且可攜"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST be developed to be reusable in "
+"[different contexts](../glossary.md#different-contexts)."
+msgstr ""
+"[代碼庫](../glossary.md#codebase)必須開發成能在[不同情境](../glossary.md"
+"#different-contexts)中重複使用。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed [code](../glossary.md#code) or services for execution "
+"and understanding."
+msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的[程"
+"式碼](../glossary.md#code)或服務。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr "代碼庫應該有多方單位使用。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr "發展路線圖應該有多方單位的需求影響。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Configuration SHOULD be used to make code adapt to context specific needs."
+msgstr "應該使用組態設定方式以將程式碼調整成能適應各情境的特定需求。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid "The codebase SHOULD be localizable."
+msgstr "代碼庫應該能夠在地化。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr "程式碼與其文件不應該包含特定情況專用的資訊。"
+
+#: ./reusable-and-portable-codebases.md:block 5 (unordered list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr "代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Enables other policy makers, developers and designers to reuse what you've "
+"developed, to test it, to improve it and contribute those improvements back "
+"leading to better quality, cheaper maintenance and higher reliability."
+msgstr ""
+"讓其他政策制定者、開發人員與設計師等，能夠重複利用您所開發的內容，以及測試它"
+"、改善它，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes the code easier for new people to understand (as it's more general)."
+msgstr "讓新進人員能更容易瞭解程式碼（因為用途更廣泛通用）。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Makes it easier to control the mission, vision and scope of the codebase "
+"because the codebase is thoughtfully and purposefully designed for "
+"reusability."
+msgstr "由於代碼庫以重複利用為前提籌劃設計，因此要調控代碼庫的目標使命、願景與範圍等"
+"也更容易。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Codebases used by multiple parties are more likely to benefit from a self-"
+"sustaining community."
+msgstr "多方使用的代碼庫更可以從能自我運作的社群中獲益。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Any contributor is able to test and contribute without relying on the "
+"situation-specific infrastructure of any other contributor or deployment."
+msgstr "任何貢獻者都能測試與貢獻給代碼庫，不需要仰賴任何其他貢獻者或部署底下的特定情"
+"況專用基礎架構。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"Composing a codebase from well documented modules improves reusability and "
+"maintainability."
+msgstr "以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。"
+
+#: ./reusable-and-portable-codebases.md:block 7 (unordered list)
+msgid ""
+"A module is easier to reuse in another context if its purpose is clearly "
+"documented."
+msgstr "以文件清楚記錄用途的模組，更容易在另一種情境中重複利用。"
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Get others to reuse the codebase."
+msgstr "讓他人重複利用代碼庫。"
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Build a community."
+msgstr "建立社群。"
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid ""
+"Shift responsibility for documentation, support, bug-fixing, etc. to another"
+" party."
+msgstr "將文件、支援、修正錯誤⋯⋯等責任轉移給其他單位。"
+
+#: ./reusable-and-portable-codebases.md:block 9 (unordered list)
+msgid "Guarantee that modules are generic enough to be reused in any context."
+msgstr "保證模組在任何情境下都足以通用。"
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"reuse the codebase and what that would entail."
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能重複利用代碼庫，以及需要怎麼"
+"進行。"
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed code or services."
+msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。"
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr "檢查是否有多方單位或是有在多種情境下正使用代碼庫。"
+
+#: ./reusable-and-portable-codebases.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr "檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。"
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處"
+"於同個原始背景情境也能夠理解。"
+
+#: ./reusable-and-portable-codebases.md:block 13 (unordered list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr "確保代碼庫有將貴組織單位列為已知用戶。"
+
+#: ./reusable-and-portable-codebases.md:block 15 (unordered list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式"
+"碼技術債，並讓代碼庫可以永續發展。"
+
+#: ./reusable-and-portable-codebases.md:block 17 (paragraph)
+msgid "Source should be designed:"
+msgstr "原始碼應該設計成："
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr "能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，"
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr "能解決通用性質問題，而非特定問題，"
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid "in logically meaningful and isolated modules,"
+msgstr "以邏輯上具有意義且獨立的模組構成，"
+
+#: ./reusable-and-portable-codebases.md:block 18 (unordered list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份"
+"）。"
+
+#: ./reusable-and-portable-codebases.md:block 19 (paragraph)
+msgid ""
+"Ensure that the codebase documentation describes the build-time and runtime "
+"dependencies. If your context requires deploying to proprietary platforms or"
+" using proprietary components, ensure that collaborators can develop, use, "
+"test, and deploy without them."
+msgstr ""
+"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要"
+"將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者"
+"的情況下，就能進行開發、使用、測試、部署等。"
+
+#: ./reusable-and-portable-codebases.md:block 20 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
+"人與組織單位資料、代符與密碼等。"
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/"
+"service-manual/technology/making-source-code-open-and-reusable)》。"
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[OpenAPI Specification](https://spec.openapis.org/oas/latest.html) by the "
+"OpenAPI Initiative defines a standard, programming language-agnostic "
+"interface description for human and machine-readable HTTP APIs."
+msgstr ""
+"OpenAPI 促進會定義的《[OpenAPI 規範](https://spec.openapis.org/oas/latest."
+"html)》，為人機可讀的 HTTP API 標準，不受程式語言種類限制的介面描述。"
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/"
+"questions/qa-i18n)》。"
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[Internationalization techniques: Authoring HTML & "
+"CSS](https://www.w3.org/International/techniques/authoring-html) by the "
+"World Wide Web Consortium."
+msgstr ""
+"全球資訊網協會《[國際化技巧：編寫 HTML 與 CSS](https://www.w3.org/"
+"International/techniques/authoring-html)》。"
+
+#: ./reusable-and-portable-codebases.md:block 22 (unordered list)
+msgid ""
+"[GNU gettext](https://www.gnu.org/software/gettext/gettext.html) of the GNU "
+"Operating System."
+msgstr ""
+"GNU 作業系統的 [GNU gettext](https://www.gnu.org/software/gettext/gettext."
+"html)。"
+
+#: ./style.md:block 1 (header)
+msgid "order: 15"
+msgstr "order: 15"
+
+#: ./style.md:block 2 (header)
+msgid "Use a coherent style"
+msgstr "風格要前後一致"
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Contributions MUST adhere to either a coding or writing style guide, either "
+"the [codebase](../glossary.md#codebase) community's own or an existing one "
+"that is advertised in or part of the codebase."
+msgstr ""
+"貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是[代碼庫](../glo"
+"ssary.md#codebase)社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既"
+"有風格。"
+
+#: ./style.md:block 5 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr "貢獻內容應該通過自動化的風格測試。"
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD include inline comments and documentation for non-"
+"trivial sections."
+msgstr "代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。"
+
+#: ./style.md:block 5 (unordered list)
+msgid ""
+"Including sections on [understandable English](understandable-english-"
+"first.md) in the style guide is OPTIONAL."
+msgstr "可選擇是否將[可理解的白話英語](understandable-english-first."
+"md)小節加入風格指南之中。"
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Enables contributors in different environments to work together on a unified"
+" product."
+msgstr "讓不同環境的貢獻者可以在統合的產品上合作。"
+
+#: ./style.md:block 7 (unordered list)
+msgid ""
+"Unifying vocabularies reduces friction in communication between "
+"contributors."
+msgstr "用詞統一能減少貢獻者之間在溝通上的摩擦。"
+
+#: ./style.md:block 9 (unordered list)
+msgid "Help contributors write well or effectively explain what they do."
+msgstr "幫助貢獻者寫好程式碼，或者精確說明他們在做什麼。"
+
+#: ./style.md:block 11 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr "確認貢獻內容有遵循文件中指定的風格指南。"
+
+#: ./style.md:block 11 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr "檢查是否有自動化的風格測試。"
+
+#: ./style.md:block 13 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄"
+"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
+
+#: ./style.md:block 15 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr "將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。"
+
+#: ./style.md:block 17 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [code](../glossary.md#code) contributions in order for them to"
+" be merged by the maintainers, including source, tests and documentation. "
+"Continually improve upon and expand this documentation with the aim of "
+"evolving this documentation into engineering guidelines."
+msgstr ""
+"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#r"
+"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
+"前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
+"以及機器不容易檢查的其他層面。指南應該包含貢獻的[程式碼](../glossary.md#code)"
+"預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目"
+"。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
+
+#: ./style.md:block 18 (paragraph)
+msgid "Additionally:"
+msgstr "此外："
+
+#: ./style.md:block 19 (unordered list)
+msgid "Use a linter."
+msgstr "使用程式碼品質分析工具 (linter)。"
+
+#: ./style.md:block 19 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr "在代碼庫中加入程式碼品質分析工具的組態設定。"
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[List of linters](https://github.com/caramelomartins/awesome-linters) by "
+"Hugo Martins."
+msgstr ""
+"Hugo Martins《[程式碼品質分析工具清單](https://github.com/caramelomartins/"
+"awesome-linters)》。"
+
+#: ./style.md:block 21 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/"
+"Programming_style)》條目。"
+
+#: ./understandable-english-first.md:block 1 (header)
+msgid "order: 10"
+msgstr "order: 10"
+
+#: ./understandable-english-first.md:block 2 (header)
+msgid "Use plain English"
+msgstr "使用白話的英語"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [codebase](../glossary.md#codebase) documentation MUST be in English."
+msgstr "[代碼庫](../glossary.md#codebase)的所有文件都必須使用英語。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All [code](../glossary.md#code) MUST be in English, except where "
+"[policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+"所有[程式碼](../glossary.md#code)都必須使用英語編寫，其中[政策](../glossary."
+"md#policy)是由機器解讀當作程式碼的部分則除外。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr "任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr "任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果"
+"有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或"
+"組織單位品牌名稱或抬頭等。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+"根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
+
+#: ./understandable-english-first.md:block 5 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr "可選擇是否提供任何程式碼、文件、測試等的翻譯版。"
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Makes the codebase and what it does understandable for a wider variety of "
+"stakeholders in multiple contexts."
+msgstr "讓不同情境的廣大利害關係人，都能瞭解代碼庫以及其用途。"
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid "Helps with the discoverability of the codebase."
+msgstr "讓代碼庫更容易被找到。"
+
+#: ./understandable-english-first.md:block 7 (unordered list)
+msgid ""
+"Can help you meet the [European Union accessibility "
+"directive](https://ec.europa.eu/digital-single-market/en/web-accessibility),"
+" which requires most public sector information to be accessible."
+msgstr ""
+"能幫助您達成《[歐盟無障礙環境命令](https://ec.europa.eu/"
+"digital-single-market/en/web-"
+"accessibility)》，內容要求大多數的公家機關資訊都要能夠近用以滿足無障礙環境。"
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make explanations of the codebase's functionality understandable."
+msgstr "讓代碼庫功能解說更容易瞭解。"
+
+#: ./understandable-english-first.md:block 9 (unordered list)
+msgid "Make your organization's jargon understandable without an explanation."
+msgstr "幫助他人在沒有額外解釋之下，就能理解貴組織單位的業內用語。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr "確認代碼庫文件有英語版本。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等"
+"。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr "確認任何非英語政策都有隨附英語版摘要。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr "確認翻譯版與英語版內容相同。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業"
+"特定詞彙等。"
+
+#: ./understandable-english-first.md:block 11 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr "檢查文件的拼字、文法與易讀性等。"
+
+#: ./understandable-english-first.md:block 13 (unordered list)
+msgid ""
+"Frequently test with other management, developers and designers in the "
+"process if they understand what you are delivering and how you document it."
+msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交"
+"付的程式碼與其文件的內容。"
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，"
+"或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，"
+"並且在使用這些詞彙的地方加上詞彙表連結。"
+
+#: ./understandable-english-first.md:block 15 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其"
+"他人也同樣迷惘。"
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Frequently test with policy makers and management if they understand what "
+"you are delivering and how you document it."
+msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件"
+"的內容。"
+
+#: ./understandable-english-first.md:block 17 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr "詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。"
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"Text of the [Web Content Accessibilty Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C, make text content "
+"readable and understandable."
+msgstr ""
+"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 "
+"之可讀性](https://www.w3.org/TR/WCAG21/"
+"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Upgoer 5 text editor](https://splasho.com/upgoer5/) by Theo Sanderson, only"
+" allows 1000 most common English words."
+msgstr ""
+"Theo Sanderson 所發表的「[Upgoer 5 文字編輯軟體](https://splasho.com/upgoer5/"
+")」只允許使用最常用的 1000 個英文單字。"
+
+#: ./understandable-english-first.md:block 19 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/"
+")》。"
+
+#: ./version-control-and-history.md:block 1 (header)
+msgid "order: 6"
+msgstr "order: 6"
+
+#: ./version-control-and-history.md:block 2 (header)
+msgid "Maintain version control"
+msgstr "維護版本控制"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The community MUST have a way to maintain [version "
+"control](../glossary.md#version-control) for the "
+"[code](../glossary.md#code)."
+msgstr ""
+"社群必須要有方法為[程式碼](../glossary.md#code)維護[版本控制](../glossary.md"
+"#version-control)。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"All files in the [codebase](../glossary.md#codebase) MUST be version "
+"controlled."
+msgstr "[代碼庫](../glossary.md#codebase)中的所有檔案皆必須有版本控制。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr "所有決定皆必須記錄成提交訊息。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr "每份提交訊息皆必須盡可能附上討論與議題連結。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr "代碼庫應該以分散式版本控制系統作維護。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid "Contributors SHOULD group relevant changes in commits."
+msgstr "貢獻者應該將相關的修改變動提交內容作群組分類。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr "維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"Contributors SHOULD prefer file formats where the changes within the files "
+"can be easily viewed and understood in the version control system."
+msgstr "貢獻者應該偏好使用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔"
+"案格式。"
+
+#: ./version-control-and-history.md:block 5 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內"
+"容有疑問時，可以與之前的貢獻者聯絡。"
+
+#: ./version-control-and-history.md:block 7 (paragraph)
+msgid ""
+"Version control means keeping track of changes to the code over time. This "
+"allows you to create structured documentation of the history of the "
+"codebase. This is essential for collaboration at scale."
+msgstr "版本控制代表追蹤程式碼歷來的變動。這能讓您為代碼庫製作有條理的變動歷史文件。"
+"這是大規模協作能運作的要素。"
+
+#: ./version-control-and-history.md:block 8 (paragraph)
+msgid "Distributed version control enables you to:"
+msgstr "分散式版本控制能讓您："
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "have a full copy of the code and its history"
+msgstr "擁有完整的程式碼副本與其版本歷史"
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "revert to an earlier version of the codebase whenever you want to"
+msgstr "在需要時可以將代碼庫恢復至先前版本"
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"record your changes and the reasons why you made them, to help future "
+"developers understand the process"
+msgstr "紀錄變動與變動的原因，可幫助未來開發人員瞭解整個過程"
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "compare two different versions"
+msgstr "比較兩個不同版本"
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid "work on changes in parallel as a team before merging them together"
+msgstr "在將修改內容合併回代碼庫之前，各團隊可以針對修改變動平行作業"
+
+#: ./version-control-and-history.md:block 9 (unordered list)
+msgid ""
+"continue to work when the network is unavailable, merging changes back with "
+"everyone else’s at a later date"
+msgstr "在沒有網路時也能繼續作業，可以日後再將修改變動合併回代碼庫與其他人整合"
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Substitute for [advertising maturity](document-maturity.md)."
+msgstr "代替[成熟度宣告](document-maturity.md)。"
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee the code executes correctly."
+msgstr "保證程式碼能正確執行。"
+
+#: ./version-control-and-history.md:block 11 (unordered list)
+msgid "Guarantee collaborators."
+msgstr "保證有人加入協作。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr "確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr "審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方"
+"，包含變動內容以及連結位置（提供網址）。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr "檢查版本控制系統是否為分散式。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。"
+
+#: ./version-control-and-history.md:block 13 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr "如果因為[政策](../glossary."
+"md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "what the policy change is,"
+msgstr "政策改變的地方，"
+
+#: ./version-control-and-history.md:block 15 (unordered list)
+msgid "how it's changed the codebase."
+msgstr "代碼庫如何因應而改變。"
+
+#: ./version-control-and-history.md:block 16 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政"
+"策變動。"
+
+#: ./version-control-and-history.md:block 18 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保"
+"改善代碼庫不會有公關風險。"
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr "提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。"
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。"
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr "提交內容的訊息要寫清楚，方便之後比較各版本。"
+
+#: ./version-control-and-history.md:block 20 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr "在政策改變以後與政策制定者合作，說明原始碼更新的內容。"
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc"
+".html#vc-vocabulary)》。"
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/"
+"technology/maintaining-version-control-in-coding)》。"
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[GitHub Learning Lab](https://lab.github.com/) by GitHub for learning how to"
+" use it or refresh your skills."
+msgstr ""
+"GitHub 提供的「[GitHub學習實驗室](https://lab.github.com/)」，可學習如何使用 "
+"GitHub，或是重溫您的技巧。"
+
+#: ./version-control-and-history.md:block 22 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
+"GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-"
+"education.pdf)」列出了最常用的 git 指令。"
diff --git a/_site/print-cover.html b/_site/print-cover.html
new file mode 100644
index 00000000..3c91d36a
--- /dev/null
+++ b/_site/print-cover.html
@@ -0,0 +1,294 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<html lang="en">
+
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <title>Standard for Public Code</title>
+  <style>
+    html {
+      font-family: Mulish;
+      font-size: 16pt;
+      margin: 0;
+      padding: 0;
+    }
+
+    *,
+    * {
+      box-sizing: border-box;
+      margin: 0;
+      padding: 0;
+    }
+
+    article {
+      position: relative;
+    }
+
+    article>section {
+      width: 21.6cm;
+      height: 30.3cm;
+      top: 0;
+      bottom: 0;
+      position: absolute;
+    }
+
+    #back {
+      left: 0;
+    }
+
+    #back>* {
+      position: absolute;
+      left: 2.3cm;
+      width: 16cm;
+    }
+
+    #front {
+      right: 0;
+    }
+
+    #front>* {
+      position: absolute;
+      left: 2cm;
+      width: 16cm;
+    }
+
+    /* Back */
+
+    #back-text {
+      position: absolute;
+      top: 2.3cm;
+    }
+
+    #back-text>p {
+      margin-bottom: 1em;
+    }
+
+    #back img[alt="hand pointing"] {
+      right: 0;
+      top: 18cm;
+      width: 18cm;
+      left: auto;
+    }
+
+    #logo {
+      bottom: 2cm;
+    }
+
+    #logo>img {
+      height: 2cm;
+    }
+
+    ol {
+      column-count: 2;
+      font-size: 12pt;
+      list-style-position: inside;
+    }
+
+    /* Front */
+
+    div#title-block {
+      position: absolute;
+      top: 2.3cm;
+    }
+
+    h1.title {
+      font-size: 3.5em;
+      font-weight: 700;
+    }
+
+    /* Audience blocks */
+
+    ul.audiences {
+      position: absolute;
+      top: 10cm;
+      list-style: none;
+      font-size: 1.25em;
+      padding-left: 0;
+    }
+
+    .audiences li,
+    .audiences lh {
+      display: block;
+      margin-bottom: .5cm;
+    }
+
+    .audiences lh {
+      margin-bottom: 1cm;
+    }
+
+    .audiences li {
+      padding-left: 1.2cm;
+    }
+
+    .audiences li::before {
+      margin-top: -.03cm;
+    }
+
+    [id$="policy-makers-what-you-need-to-do"]:before,
+    [id$="management-what-you-need-to-do"]:before,
+    [id$="developers-and-designers-what-you-need-to-do"]:before {
+      display: block;
+      position: absolute;
+      content: 'A';
+      text-align: center;
+      width: 1cm;
+      height: 1cm;
+      color: white;
+      display: inline-block;
+      margin-left: -1.2cm;
+      box-sizing: border-box;
+      padding: 0.20cm;
+      font-size: .5cm;
+      font-weight: 900;
+    }
+
+    [id$="policy-makers-what-you-need-to-do"]:before {
+      background-color: #00EFB5;
+      content: 'P';
+    }
+
+    [id$="management-what-you-need-to-do"]:before {
+      background-color: #FF6D1C;
+      content: 'M';
+    }
+
+    [id$="developers-and-designers-what-you-need-to-do"]:before {
+      background-color: #8626FF;
+      content: 'D';
+    }
+
+    /* Hands */
+
+    #front img[alt="hands shaking"] {
+      left: 0;
+      right: 0;
+      top: 18cm;
+      width: 21.6cm;
+    }
+
+    /* Version info */
+
+    #version-info {
+      bottom: 2cm;
+      font-size: .75em;
+    }
+
+    /* Print specific */
+
+    @media print {
+      @page {
+        /* A4 times 2 plus a back of about 6mm and a 3mm bleed on every side */
+        size: 43.2cm 30.3cm;
+        margin: 0;
+        padding: 0;
+        background-color: white;
+      }
+    }
+
+    /* Screen mock-up when using a browser */
+
+    @media screen {
+      body {
+        background-color: whitesmoke;
+      }
+
+      article {
+        display: block;
+        background-color: white;
+        min-height: 30.3cm;
+        max-height: 30.3cm;
+        min-width: 43.2cm;
+        max-width: 43.2cm;
+      }
+    }
+  </style>
+</head>
+
+<body>
+
+  <article>
+    <section id="back">
+      <div id="back-text">
+        <p>
+          The Standard for Public Code supports the collaborative creation of codebases that are usable, open, legible, accountable, accessible and sustainable.
+          The Standard includes guidance to policymakers, managers, designers and developers creating and managing codebases.
+        </p>
+        <p>
+          The standard specifies the criteria:
+          
+          <ol>
+            
+              
+                
+            <li>原始碼要開放</li>
+              
+            <li>政策與原始碼要合捆</li>
+              
+            <li>程式碼要可重複使用且可攜</li>
+              
+            <li>歡迎貢獻者</li>
+              
+            <li>貢獻要容易</li>
+              
+            <li>維護版本控制</li>
+              
+            <li>要求審查貢獻內容</li>
+              
+            <li>代碼庫有目標文件</li>
+              
+            <li>程式碼有文件</li>
+              
+            <li>使用白話的英語</li>
+              
+            <li>採用開放標準</li>
+              
+            <li>使用持續整合</li>
+              
+            <li>發行採用開放授權</li>
+              
+            <li>代碼庫可查詢得到</li>
+              
+            <li>風格要前後一致</li>
+              
+            <li>紀錄代碼庫成熟度</li>
+              
+          </ol>
+        </p>
+      </div>
+
+      <img src="assets/hand-point.svg" alt="hand pointing">
+
+      <section id="logo">
+        <img src="https://brand.publiccode.net/logo/mark-and-name-over-two-lines.svg" alt="Foundation for Public Code logo">
+      </section>
+    </section>
+
+    <section id="front">
+      <div id="title-block">
+        <p>Request for contributions</p>
+        <h1 class="title">Standard for Public Code</h1>
+      </div>
+
+      <ul class="audiences">
+        <lh>What public code is and how to implement it for:</lh>
+        <li id="first-page-policy-makers-what-you-need-to-do">Policy makers</li>
+        <li id="first-page-management-what-you-need-to-do">Management</li>
+        <li id="first-page-developers-and-designers-what-you-need-to-do">Developers and designers</li>
+      </ul>
+
+      <img src="assets/hands-shake.svg" alt="hands shaking">
+
+      <div id="version-info">
+        <p><strong>Draft</strong><br/>Version 0.4.0</p>
+        <p><img src="/assets/cc-zero-badge.svg" alt="Licensed CC0" height="46"> <img src="/assets/dpg-badge.svg" alt="Digital Public Goods approval badge" width="92" height="46"></p>
+        <p>https://standard.publiccode.net/</p>
+      </div>
+    </section>
+  </article>
+
+</body>
+
+</html>
diff --git a/_site/print-review-template.html b/_site/print-review-template.html
new file mode 100644
index 00000000..7d5cbde2
--- /dev/null
+++ b/_site/print-review-template.html
@@ -0,0 +1,925 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <link rel="stylesheet" href="assets/github-markdown.css">
+  <title>Standard for Public Code</title>
+  <style>
+    html, .markdown-body {
+      font-family: Mulish;
+      font-size: 11pt;
+    }
+
+    .markdown-body h1, .markdown-body h2 {
+      font-weight: normal;
+      position: relative;
+    }
+    .markdown-body h1 {
+      margin-top: 0;
+      font-size: 1.6rem;
+      border-bottom: none;
+    }
+    .markdown-body h2 {
+      font-size: 1.4em;
+    }
+
+    article>p, article>ul, article>ol {
+      position: relative;
+      max-width: 27rem;
+    }
+
+    article {
+      clear: both;
+    }
+
+    a:link {
+      color: inherit;
+      text-decoration: none;
+    }
+
+    a[href^="http"]:link {
+      color: black;
+      text-decoration: none;
+      word-wrap: normal;
+    }
+
+    a[href^="#"] {
+      color: black;
+      text-decoration: none;
+    }
+    a[href^="#"]:after {
+      content: "" target-counter(attr(href), page);
+      color: black;
+      background-color: whitesmoke;
+      display: inline;
+      width: 0.6cm;
+      padding: 0.2cm;
+      text-align: right;
+    }
+
+    p {
+      clear: both;
+    }
+    
+    /* Print specific */
+
+    @media print {
+      /* html { page-break-before: left } */
+      @page {
+        /* A4 with a 3mm bleed on every side */
+        size: 21.6cm 30.3cm;
+        margin: 1cm 0;
+        orphans:4;
+        widows:4;
+      }
+      @page :left {
+        @top-left {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+
+        }
+      }
+      @page :right {
+        @top-right {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+        }
+      }
+
+      article {
+        margin: 0 2cm;
+        break-before: left;
+      }
+      article:first-of-type {
+        break-before: avoid;
+      }
+      h1, h2 {
+        page-break-after: avoid;
+      }
+      table {
+        font-size: 80%;
+      }
+
+    }
+
+    @media screen {
+      body {
+        background-color: whitesmoke;
+        margin: 0; padding: 0;
+      }
+      article {
+        display: block;
+        background-color: white;
+        padding: 1cm;
+        min-height: 29.7cm;
+        max-width: 50em;
+        max-width: 21cm;
+        box-sizing: border-box;
+        margin: 2cm 0;
+      }
+    }
+
+  </style>
+</head>
+<body class="markdown-body">
+  <article id="review-template">
+
+    <h1 id="________-and-the-standard-for-public-code-version-040">________ and the Standard for Public Code version 0.4.0</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Link to commitment to meet the Standard for Public Code:</p>
+
+<h2 id="code-in-the-open"><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT upload sensitive information regarding users, their organization or third parties to the repository.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="bundle-policy-and-source-code"><a href="https://standard.publiccode.net/criteria/bundle-policy-and-code.html">Bundle policy and source code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST include the policy that the source code is based on.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include all source code that the policy is based on, unless used for fraud detection.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Policy SHOULD be provided in machine readable and unambiguous formats.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="create-reusable-and-portable-code"><a href="https://standard.publiccode.net/criteria/reusable-and-portable-codebases.html">Create reusable and portable code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be developed to be reusable in different contexts.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed code or services for execution and understanding.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be in use by multiple parties.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The roadmap SHOULD be influenced by the needs of multiple parties.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Configuration SHOULD be used to make code adapt to context specific needs.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be localizable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Code and its documentation SHOULD NOT contain situation-specific information.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="welcome-contributors"><a href="https://standard.publiccode.net/criteria/open-to-contributions.html">Welcome contributors</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST allow anyone to submit suggestions for changes to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a <code class="language-plaintext highlighter-rouge">CONTRIBUTING</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST document the governance of the codebase, contributions and its community, for example in a <code class="language-plaintext highlighter-rouge">GOVERNANCE</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a publicly available roadmap.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD publish codebase activity statistics.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including a code of conduct for contributors in the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-contributing-easy"><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST have a public issue tracker that accepts suggestions from anyone.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST include instructions for how to privately report security issues for responsible disclosure.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a <code class="language-plaintext highlighter-rouge">README</code> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have communication channels for users and developers, for example email lists.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD include instructions for how to report potentially security sensitive issues on a closed channel.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="maintain-version-control"><a href="https://standard.publiccode.net/criteria/version-control-and-history.html">Maintain version control</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The community MUST have a way to maintain version control for the code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All files in the codebase MUST be version controlled.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All decisions MUST be documented in commit messages.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Every commit message MUST link to discussions and issues wherever possible.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD be maintained in a distributed version control system.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD group relevant changes in commits.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors SHOULD prefer file formats where the changes within the files can be easily viewed and understood in the version control system.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="require-review-of-contributions"><a href="https://standard.publiccode.net/criteria/require-review.html">Require review of contributions</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews MUST include source, policy, tests and documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviewers MUST provide feedback on all decisions to not accept a contribution.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD conform to the standards, architecture and decisions set out in the codebase in order to pass review.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD include running both the code and the tests of the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD be reviewed by someone in a different context than the contributor.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Version control systems SHOULD NOT accept non-reviewed contributions in release versions.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Reviews SHOULD happen within two business days.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Performing reviews by multiple reviewers is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-objectives"><a href="https://standard.publiccode.net/criteria/document-objectives.html">Document codebase objectives</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documenting the objectives of the codebase for the general public is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-the-code"><a href="https://standard.publiccode.net/criteria/documenting.html">Document the code</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All of the functionality of the codebase, policy as well as source, MUST be described in language clearly understandable for those that understand the purpose of the code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain a description of how to install and run the source code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase MUST contain examples demonstrating the key functionality.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation of the codebase SHOULD contain examples for all functionality.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>There SHOULD be continuous integration tests for the quality of the documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing the code by using examples in the documentation is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-plain-english"><a href="https://standard.publiccode.net/criteria/understandable-english-first.html">Use plain English</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All codebase documentation MUST be in English.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All code MUST be in English, except where policy is machine interpreted as code.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All bundled policy not available in English MUST have an accompanying summary in English.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any translation MUST be up to date with the English version and vice versa.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Providing a translation of any code, documentation or tests is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-open-standards"><a href="https://standard.publiccode.net/criteria/open-standards.html">Use open standards</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any non-open standards used MUST be recorded clearly as such in the documentation.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>If no existing open standard is available, effort SHOULD be put into developing one.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Standards that are machine testable SHOULD be preferred over those that are not.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-continuous-integration"><a href="https://standard.publiccode.net/criteria/continuous-integration.html">Use continuous integration</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All functionality in the source code MUST have automated tests.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions MUST pass all automated tests before they are admitted into the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have guidelines explaining how to structure contributions.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST have active contributors.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase guidelines SHOULD state that each contribution should focus on a single issue.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Source code test and documentation coverage SHOULD be monitored.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for consistency with the source and vice versa is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Testing policy and documentation for style and broken links is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="publish-with-an-open-license"><a href="https://standard.publiccode.net/criteria/open-licenses.html">Publish with an open license</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>All code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All code MUST be published with a license file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Having multiple licenses for different types of code and documentation is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="make-the-codebase-findable"><a href="https://standard.publiccode.net/criteria/findability.html">Make the codebase findable</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by describing the problem it solves in natural language.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase MUST be findable using a search engine by codebase name.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Maintainers SHOULD submit the codebase to relevant software catalogs.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>A dedicated domain name for the codebase is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Regular presentations at conferences by the community are OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="use-a-coherent-style"><a href="https://standard.publiccode.net/criteria/style.html">Use a coherent style</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Contributions MUST adhere to either a coding or writing style guide, either the codebase community’s own or an existing one that is advertised in or part of the codebase.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Contributions SHOULD pass automated tests on style.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD include inline comments and documentation for non-trivial sections.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>Including sections on <a href="https://standard.publiccode.net/criteria/understandable-english-first.html">understandable English</a> in the style guide is OPTIONAL.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="document-codebase-maturity"><a href="https://standard.publiccode.net/criteria/document-maturity.html">Document codebase maturity</a></h2>
+
+<p>☐ criterion met.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Requirement</th>
+      <th>meets</th>
+      <th> links and notes </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>The codebase MUST be versioned.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase that is ready to use MUST only depend on other codebases that are also ready to use.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase that is not yet ready to use MUST have one of the labels: prototype, alpha, beta or pre-release version.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+    <tr>
+      <td>The codebase SHOULD contain a log of changes from version to version, for example in the <code class="language-plaintext highlighter-rouge">CHANGELOG</code>.</td>
+      <td> </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table>
+
+
+  </article>
+</body>
+</html>
diff --git a/_site/print.html b/_site/print.html
new file mode 100644
index 00000000..d2c6fde6
--- /dev/null
+++ b/_site/print.html
@@ -0,0 +1,2529 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <link rel="stylesheet" href="assets/github-markdown.css">
+  <title>Standard for Public Code</title>
+  <style>
+    html, .markdown-body {
+      font-family: Mulish;
+      font-size: 11pt;
+    }
+
+    .markdown-body h1, .markdown-body h2, .markdown-body h3 {
+      font-weight: normal;
+      position: relative;
+    }
+    .markdown-body h1 {
+      margin-top: 0;
+      font-size: 1.5cm;
+      border-bottom: none;
+    }
+    .markdown-body h2 {
+      font-size: 1.5em;
+    }
+    .markdown-body h3 {
+      font-size: 1em;
+      font-weight: bold;
+    }
+    .markdown-body h4 {
+      font-size: 1em;
+      font-weight: italic;
+    }
+    .markdown-body h4 {
+      font-weight: bold;
+      font-weight: normal;
+    }
+
+    article>p, article>ul, article>ol {
+      position: relative;
+      max-width: 27rem;
+    }
+
+    article {
+      clear: both;
+    }
+
+    a:link {
+      color: inherit;
+      text-decoration: none;
+    }
+
+    a:link:after {
+      color: grey;
+      page-break-inside: avoid;
+      margin-left: .25em;
+      break-inside: avoid;
+      display: block;
+      right: 0;
+      width: 6cm;
+      margin-right: -7cm;
+      padding: 0.25rem;
+      line-height: 1.25;
+      text-align: left;
+      float: right;
+      clear: both;
+      word-break: normal;
+      text-decoration: none;
+    }
+    a[href^="http"]:link {
+      color: black;
+      text-decoration: none;
+      word-wrap: normal;
+    }
+    a[href^="http"]:after {
+      content: "" attr(href) "";
+      font-size: .75em;
+    }
+    a[href^="#"] {
+      color: black;
+      text-decoration: none;
+    }
+    a[href^="#"]:after {
+      content: "" target-counter(attr(href), page);
+      color: black;
+      background-color: whitesmoke;
+      display: inline;
+      width: 0.6cm;
+      padding: 0.2cm;
+      text-align: right;
+    }
+
+    img {
+      max-width: 155% !important;
+    }
+
+    ol, ul {
+      margin-bottom: 2em;
+    }
+
+    li, p {
+      clear: both;
+    }
+
+    /* Headings */
+
+    .markdown-body [id$="policy-makers-what-you-need-to-do"]:before,
+    .markdown-body [id$="management-what-you-need-to-do"]:before,
+    .markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+      display: block;
+      position: absolute;
+      content: 'A';
+      text-align: center;
+      width: 1cm;
+      height: 1cm;
+      background-color: black;
+      border: 1px solid black;
+      color: white;
+      display: inline-block;
+      margin-left: -1.2cm;
+      box-sizing: border-box;
+      padding: 0.12cm;
+      font-size: 0.5cm;
+      font-weight: 900;
+    }
+    .markdown-body [id$="policy-makers-what-you-need-to-do"]:before {
+      background-color: #00EFB5;
+      border-color: #00EFB5;
+      content: 'P';
+    }
+    .markdown-body [id$="management-what-you-need-to-do"]:before {
+      background-color: #FF6D1C;
+      border-color: #FF6D1C;
+      content: 'M';
+    }
+    .markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+      background-color: #8626FF;
+      border-color: #8626FF;
+      content: 'D';
+    }
+
+    /* First page */
+
+    h1.title {
+      font-size: 5em;
+      font-weight: 700;
+      margin-bottom: 1cm;
+    }
+
+    ul.first-page-audiences {
+      max-width: none;
+      list-style: none;
+      font-size: 1.25em;
+      padding-left: 0;
+    }
+    .first-page-audiences li, .first-page-audiences lh {
+      display: block;
+      margin-bottom: .5cm;
+    }
+    .first-page-audiences lh {
+      margin-bottom: 1cm;
+    }
+    .first-page-audiences li {
+      padding-left: 1.2cm;
+    }
+    .first-page-audiences li::before {
+      margin-top: -.15cm;
+    }
+    #section-first-page>img {
+      width: 100%;
+    }
+    
+    /* Print specific */
+
+    @media print {
+      /* html { page-break-before: left } */
+      @page {
+        /* A4 with a 3mm bleed on every side */
+        size: 21.6cm 30.3cm;
+        margin: 2cm 0;
+        orphans:4;
+        widows:4;
+      }
+      @page :left {
+        margin-right: 1cm;
+        @top-left {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+          padding-left: 0.5cm;
+        }
+      }
+      @page :right {
+        margin-left: 1cm;
+        @top-right {
+          background: whitesmoke;
+          font-size: 75%;
+          content: counter(page);
+          height: 1cm;
+          width: 1.23cm;
+          text-align: center;
+          padding-right: 0.5cm;
+        }
+      }
+      figure {
+        page: image;
+      }
+      figure>img {
+        width: 100%;
+        height: 100%;
+      }
+      @page image {
+        margin-top: 0 !important;
+        margin-left: -1.5cm !important;
+        margin-right: -1.5cm !important;
+        margin-bottom: 0 !important;
+        padding: 0 0 0 0 !important;
+      }
+
+      article {
+        margin: 0 2cm;
+        break-before: left;
+      }
+      article:first-of-type {
+        break-before: avoid;
+      }
+      h1, h2, h3, h4 {
+        page-break-after: avoid;
+      }
+      img {
+        page-break-inside: avoid;
+      }
+      #table-of-contents {
+        line-height: 0.9;
+      }
+      
+      #section-first-page>img {
+        width: 21.6cm;
+        margin: 1cm 0 1cm -3.21cm; /* This value for the left margin was done by eye */
+      }
+    }
+
+    @media screen {
+      body {
+        background-color: whitesmoke;
+        margin: 0; padding: 0;
+      }
+      article {
+        display: block;
+        background-color: white;
+        padding: 1cm;
+        min-height: 29.7cm;
+        max-width: 50em;
+        max-width: 21cm;
+        box-sizing: border-box;
+        margin: 2cm 0;
+      }
+    }
+
+  </style>
+</head>
+<body class="markdown-body">
+
+  <article id="section-first-page">
+    <p>Request for contributions</p>
+    <h1 class="title">Standard for Public Code</h1>
+
+    <ul class="first-page-audiences">
+      <lh>What public code is and how to implement it for:</lh>
+      <li id="first-page-policy-makers-what-you-need-to-do">Policy makers</li>
+      <li id="first-page-management-what-you-need-to-do">Management</li>
+      <li id="first-page-developers-and-designers-what-you-need-to-do">Developers and designers</li>
+    </ul>
+
+    <img src="assets/hands-shake.svg" alt="hands shaking">
+
+    <p><strong>Draft</strong><br/>Version 0.4.0</p>
+    <p><img src="/assets/cc-zero-badge.svg" alt="Licensed CC0" height="46"> <img src="/assets/dpg-badge.svg" alt="Digital Public Goods approval badge" width="92" height="46"></p>
+    <p>github.com/publiccodenet/standard</p>
+  </article>
+
+  <article id="section-authors">
+
+    <h1 id="authors">Authors</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<ul>
+  <li>Alba Roza, <a href="https://publiccode.net">The Foundation for Public Code</a></li>
+  <li>Arnout Engelen</li>
+  <li>Arnout Schuijff, The Foundation for Public Code</li>
+  <li>Audrey Tang, <a href="https://digitalminister.tw/">digitalminister.tw</a></li>
+  <li>Ben Cerveny, The Foundation for Public Code</li>
+  <li>Bert Spaan</li>
+  <li>Boris van Hoytema, The Foundation for Public Code</li>
+  <li>Charlotte Heikendorf</li>
+  <li>Claus Mullie, The Foundation for Public Code</li>
+  <li>David Barberi</li>
+  <li>Edo Plantinga, <a href="https://codefor.nl/">Code For NL</a></li>
+  <li>Elena Findley-de Regt, The Foundation for Public Code</li>
+  <li>Eric Herman, The Foundation for Public Code</li>
+  <li>Felix Faassen, The Foundation for Public Code</li>
+  <li>Floris Deerenberg</li>
+  <li>Jan Ainali, The Foundation for Public Code</li>
+  <li>Johan Groenen, Code For NL</li>
+  <li>Marcus Klaas de Vries</li>
+  <li>Mark van der Net, <a href="https://www.amsterdam.nl/en/">Gemeente Amsterdam</a></li>
+  <li>Martijn de Waal, <a href="https://www.amsterdamuas.com/">Amsterdam University of Applied Sciences (AUAS)</a>, Faculty of Digital Media and Creative Industries, Lectorate of Play &amp; Civic Media</li>
+  <li>Mauko Quiroga</li>
+  <li>Maurice Hendriks, Gemeente Amsterdam</li>
+  <li>Maurits van der Schee, Gemeente Amsterdam</li>
+  <li>Mirjam van Tiel, The Foundation for Public Code</li>
+  <li>Ngô Ngọc Đức Huy</li>
+  <li>Paul Keller</li>
+  <li>Petteri Kivimäki, <a href="https://niis.org">Nordic Institute for Interoperability Solutions (NIIS)</a></li>
+  <li>Sky Bristol</li>
+  <li>Tamas Erkelens, Gemeente Amsterdam</li>
+  <li>Timo Slinger</li>
+</ul>
+
+
+  </article>
+
+  <article id="table-of-contents">
+
+    <h1>Table of Contents</h1>
+
+    <ol>
+      <li><a href="#section-authors">Authors</a></li>
+      <li><a href="#section-introduction">Introduction</a></li>
+      <li><a href="#section-readers-guide">Readers guide</a></li>
+      <li><a href="#section-glossary">Glossary</a></li>
+      <li><a href="#section-criteria">Criteria</a>
+        
+        <ol>
+        
+          
+            
+          <li><a href="#section-criteria-code-in-the-open.md">原始碼要開放</a></li>
+          
+          <li><a href="#section-criteria-bundle-policy-and-code.md">政策與原始碼要合捆</a></li>
+          
+          <li><a href="#section-criteria-reusable-and-portable-codebases.md">程式碼要可重複使用且可攜</a></li>
+          
+          <li><a href="#section-criteria-open-to-contributions.md">歡迎貢獻者</a></li>
+          
+          <li><a href="#section-criteria-make-contributing-easy.md">貢獻要容易</a></li>
+          
+          <li><a href="#section-criteria-version-control-and-history.md">維護版本控制</a></li>
+          
+          <li><a href="#section-criteria-require-review.md">要求審查貢獻內容</a></li>
+          
+          <li><a href="#section-criteria-document-objectives.md">代碼庫有目標文件</a></li>
+          
+          <li><a href="#section-criteria-documenting.md">程式碼有文件</a></li>
+          
+          <li><a href="#section-criteria-understandable-english-first.md">使用白話的英語</a></li>
+          
+          <li><a href="#section-criteria-open-standards.md">採用開放標準</a></li>
+          
+          <li><a href="#section-criteria-continuous-integration.md">使用持續整合</a></li>
+          
+          <li><a href="#section-criteria-open-licenses.md">發行採用開放授權</a></li>
+          
+          <li><a href="#section-criteria-findability.md">代碼庫可查詢得到</a></li>
+          
+          <li><a href="#section-criteria-style.md">風格要前後一致</a></li>
+          
+          <li><a href="#section-criteria-document-maturity.md">紀錄代碼庫成熟度</a></li>
+          
+        </ol>
+      </li>
+      <li><a href="#section-contributing">Contributing guide</a></li>
+      <li><a href="#section-code_of_conduct">Code of conduct</a></li>
+      <li><a href="#section-governance">Governance</a></li>
+      <li><a href="#section-changelog">Version history</a></li>
+      <li><a href="#section-license">License</a></li>
+      <li><a href="#section-contact">Contact</a></li>
+    </ol>
+
+  </article>
+
+  <figure>
+    <img src="/assets/codebase.svg" alt="codebase">
+  </figure>
+
+  <article id="section-introduction">
+
+    <h1 id="introduction">Introduction</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together.</p>
+
+<p>Anyone developing software or policy for a public purpose can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control.</p>
+
+<p>This introduction introduces the term public code, explains why this is important, and introduces the process through which software and policy code can become certified public code.</p>
+
+<h2 id="definition-of-public-code">Definition of public code</h2>
+
+<p>Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+It encompasses the software built to operate with and as public infrastructure, along with the arrangements for its production.
+Public code is explicitly distinct from regular software because it operates under fundamentally different circumstances and expectations.</p>
+
+<h2 id="reasons-for-public-code">Reasons for public code</h2>
+
+<p>There are many reasons for why public code is relevant now.</p>
+
+<h3 id="software-code--legal-code">Software code == legal code</h3>
+
+<p>Software is public infrastructure.</p>
+
+<p>In the 21st century, software can be considered vital public infrastructure. It is increasingly not just the expression of existing policy but the originator of new policy, for example where algorithms decide which districts need extra social services or policing.</p>
+
+<p>Software mechanics, algorithms and data collection have become key elements in the execution of public policies. Computer code now executes policies that have been codified in legal code through democratic procedures. Both forms of code set conditions for society to function according to democratically set public values, the latter executed by humans, the former by machines. In other words, software code has increasingly started to equal legal code.</p>
+
+<p>Software should therefore be subject to the principles of democratic governance.</p>
+
+<h3 id="traditional-public-software-procurement">Traditional public software procurement</h3>
+
+<p>Current public software production methods have not served public service delivery very well.</p>
+
+<p>In the last decade, public organizations that purchased complete software solutions have sometimes been surprised to discover that they:</p>
+
+<ul>
+  <li>can’t change their software to reflect changing policy or take advantage of new technology</li>
+  <li>don’t have access to their data as it’s locked into proprietary systems</li>
+  <li>are asked to pay ever increasing license fees</li>
+</ul>
+
+<h3 id="technological-sovereignty-and-democratic-accountability">Technological sovereignty and democratic accountability</h3>
+
+<p>Public institutions, civil servants and residents deserve better.</p>
+
+<p>We believe the software that runs our society can no longer be a black box, controlled by outside companies that keep the underlying logic on which their software operates hidden in proprietary codebases. Instead, governments and the people they serve need technological sovereignty. This allows them to set and control the functioning of public software, just like they are able to set and control policy that is legally formulated in laws. Citizens and civil society actors need this software to be transparent and accountable.</p>
+
+<p>The design of software as essential civic infrastructure should honor digital citizens’ rights.</p>
+
+<h3 id="designing-truly-public-software">Designing truly public software</h3>
+
+<p>Public code is at the core of modern public institutions, shapes the work of civil servants and affects the lives of almost all residents.</p>
+
+<p>Public software must therefore be:</p>
+
+<ul>
+  <li>transparent</li>
+  <li>accountable</li>
+  <li>understandable for its constituents</li>
+</ul>
+
+<p>It must reflect the values of the society it serves, for example by being inclusive and non-discriminatory.</p>
+
+<p>Most proprietary software systems currently used by public organizations do not meet these requirements. Public code does.</p>
+
+<h3 id="values-of-public-code">Values of public code</h3>
+
+<p>We consider public code to have these core values:</p>
+
+<ul>
+  <li>Inclusive</li>
+  <li>Usable</li>
+  <li>Open</li>
+  <li>Legible</li>
+  <li>Accountable</li>
+  <li>Accessible</li>
+  <li>Sustainable</li>
+</ul>
+
+<h2 id="how-public-code-works">How public code works</h2>
+
+<p>Public code is open source software meant for fulfilling the essential role of public organizations. Through use, other administrations contribute back to the software, so that its development and maintenance become truly collaborative.</p>
+
+<p>Being open unlocks many other things.</p>
+
+<p>Local responsibility and democratic accountability are ensured when a public organization implements and maintains their own public code. By being open and with a broader contributor base, the software is more secure as it benefits from many eyes spotting potential flaws. Many contributors share the maintenance work to keep it functional and modern, which reduces future technical debt. The shared workload is more sustainable now and in the future. Its openness makes the code and its data more easily adaptable in the future. The code will be easier to retool, repurpose or retire. This all results in lower risk public infrastructure.</p>
+
+<p>This pooling of resources lets public administrations give extra attention to how to customize the software so it works best in each local context, creating better user experiences for their end users (residents or citizens).</p>
+
+<h3 id="economics-of-public-code">Economics of public code</h3>
+
+<p>Public code offers a better economic model for public organizations as well as for commercial companies. It’s an alternative to traditional software procurement which increases local control and economic opportunity.</p>
+
+<p>Designed from the start to be open, adaptable and with data portability, it can be developed by in-house staff or trusted vendors. Because the code is open, the public administration can change vendors if they need to. Open code increases opportunities for public learning and scrutiny, allowing the public administration to procure smaller contracts. Smaller procurements are easier for local small and medium enterprises to bid upon. Public administrations can use their own software purchasing to stimulate innovation and competition in their local economy.</p>
+
+<p>This can be seen as investment leading to future economic growth. More vendors will be necessary due to growing technology demand.</p>
+
+<h3 id="procuring-public-code">Procuring public code</h3>
+
+<p>Public code can be used and developed by permanent in-house development teams, contractors or outsourced suppliers. Vendors to public organizations can include public code in their bids for contracts.</p>
+
+<p>To use existing public code, you need to specify in your budget and project design that your new solution will use that codebase. To encourage an innovative approach to adapting the public code to your context, you could describe the service or outcome in your contract.</p>
+
+<h2 id="standard-compliance-or-certification-process">Standard compliance or certification process</h2>
+
+<p>The Foundation for Public Code ensures that codebases under its stewardship (and not in incubation or the attic) are compliant with the Standard for Public Code. This makes clear to potential users and contributors that the codebase is of high quality, and updates will be too.</p>
+
+<p>The audit performed by the Foundation for Public Code is meant to complement machine testing, as machines are great at testing things like syntax and whether outcomes align with expectations. Things meant for humans, such as testing whether documentation is actually understandable and accessible in context, the commit messages make sense, and whether community guidelines are being followed are impossible for machines to test.</p>
+
+<p>The audit tests the entire codebase, including source code, policy, documentation and conversation for compliance with both the standards set out by the Foundation for Public Code and the standards set out in the codebase itself.</p>
+
+<h3 id="how-the-process-works">How the process works</h3>
+
+<p>Every time a contribution is suggested to a codebase, through for instance a merge request, the <a href="https://about.publiccode.net/roles/">codebase stewards</a> of the Foundation for Public Code will audit the contribution for compliance with the Standard for Public Code. New contributions can only be adopted into the codebase after they have been approved as compliant with the Standard for Public Code, and have been reviewed by another contributor.</p>
+
+<p>The audit is presented as a review of the contribution. The codebase steward gives line by line feedback and compliance, helping the contributor to improve their contribution. The merge request cannot be fulfilled until the codebase stewards have approved the contribution.</p>
+
+<p><img src="/images/audit-flow.svg" alt="Pull Request Acceptance process" /></p>
+
+<h3 id="certifying-an-entire-codebase-versus-a-contribution">Certifying an entire codebase versus a contribution</h3>
+
+<p>For the codebase to be completely certified every meaningful line of code, and the commits behind the code, need to meet the Standard.</p>
+
+<p>If codebases have been completely audited from the first merge request they can be immediately certified as compliant with the Standard for Public Code.</p>
+
+<p>If the audit process is added to an existing codebase, the new merge requests can be certified, but the existing code cannot be certified. By auditing every new merge request the codebase can move incrementally towards being completely certified.</p>
+
+<h2 id="the-goals-for-the-standard-for-public-code">The goals for the Standard for Public Code</h2>
+
+<p>This Standard supports developers, designers, business management and policy makers to:</p>
+
+<ul>
+  <li>develop high quality software and policy for better public service delivery</li>
+  <li>develop codebases that can be reused across contexts and collaboratively maintained</li>
+  <li>reduce technical debt and project failure rate</li>
+  <li>have more granular control over, and ability to make decisions about, their IT systems</li>
+  <li>improve vendor relationships with a better economic model</li>
+</ul>
+
+<p><a href="https://publiccode.net/">The Foundation for Public Code</a> helps public organizations share and adopt open source software, build sustainable developer communities and create a thriving ecosystem for public code. It does this through codebase stewardship. For this process the codebase stewards use the Standard for Public Code to make sure the code it stewards is high quality as well as collaboratively maintainable.</p>
+
+<p>Potential users of codebases tested against the Standard for Public Code can expect them to be highly reusable, easily maintainable and of high quality.</p>
+
+<p>The Standard for Public Code does this by:</p>
+
+<ul>
+  <li>setting out a common terminology for public code development</li>
+  <li>establishing measures to help develop high quality public code</li>
+  <li>providing guidance on how to fulfill its criteria and operationalize compliance</li>
+</ul>
+
+<p>The Standard for Public Code is meant to be time and technology independent.</p>
+
+<h3 id="who-this-is-for">Who this is for</h3>
+
+<p>The Standard for Public Code is for the people who create and reuse public code:</p>
+
+<ul>
+  <li>policy makers</li>
+  <li>business and project management</li>
+  <li>developers and designers</li>
+</ul>
+
+<p>These people work at:</p>
+
+<ul>
+  <li>institutions, organizations and administrations in the public sector</li>
+  <li>consultancies and vendors of information technology and policy services to public organizations</li>
+</ul>
+
+<p>It is not aimed at public organizations’ end users (residents or citizens), journalists or academics.</p>
+
+<h2 id="further-reading">Further reading</h2>
+
+<ul>
+  <li><a href="https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf">“Modernising Public Infrastructure with Free Software” whitepaper</a> by the Free Software Foundation Europe.</li>
+</ul>
+
+<h3 id="videos-on-public-code">Videos on public code</h3>
+
+<ul>
+  <li><a href="https://www.youtube.com/watch?v=cnJtnZ9Cx1o">Collaborative Code is the Future of Cities @ DecidimFest 2019</a>. Talk by Ben Cerveny on the background behind the Foundation for Public Code.</li>
+  <li><a href="https://youtube.com/watch?v=QHFkD4xfd6c">Public Money? Public Code! - Panel @ Nextcloud Conference 2019</a>. Touches on topics like procurement, law and more.</li>
+</ul>
+
+<h2 id="get-involved">Get involved</h2>
+
+<p>This standard is a living document. <a href="/CONTRIBUTING.html">Read our contributor guide</a> to learn how you can make it better.</p>
+
+
+  </article>
+
+  <article id="section-readers-guide">
+
+    <h1 id="readers-guide">Readers guide</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard describes a number of criteria.
+All criteria have consistent sections that make it clear how to create great public code.</p>
+
+<p>References to “policy makers”, “management”, and “developers and designers” apply to anyone performing duties associated with these roles, regardless of their job title.
+It is common for individuals to have duties which span multiple roles.</p>
+
+<p>Below is a brief explanation of each of these sections and how they are used within the criteria of the Standard.</p>
+
+<h2 id="requirements">Requirements</h2>
+
+<p>This section lists what needs to be done in order to comply with the standard.</p>
+
+<p>In order to limit ambiguity, the key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
+NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”,  “MAY”, and “OPTIONAL” in this document are to be interpreted as described in <a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a>.</p>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>This section explains why it is important for the users and contributors of this codebase that these requirements are followed.</p>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<p>This section manages expectations by explaining what following the requirements will not save you from.</p>
+
+<p>This helps:</p>
+
+<ul>
+  <li>with applying the Standard correctly</li>
+  <li>make sure no unexpected things pop up</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<p>This section offers actions you can take to see if a contribution is compliant with the Standard. This is key if you want to operationalize the Standard.</p>
+
+<p>We’ve tried to word it so that someone who is not intimately acquainted with the subject matter can still do a basic check for compliance.</p>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<p>This section tries to specifically speak to policy makers by offering them concrete actions they can perform in their role.</p>
+
+<p>Policy makers set the priorities and goals of projects and may be less technologically experienced.</p>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<p>This section tries to specifically speak to management by offering concrete actions they can perform in their role.</p>
+
+<p>Management is responsible for on-time project delivery, stakeholder management and continued delivery of the service. For this they are wholly reliant on both policy makers as well as developers and designers. They need to create the right culture, line up the right resources and provide the right structures to deliver great services.</p>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<p>This section tries to specifically speak to developers and designers by offering them concrete actions they can perform in their role.</p>
+
+<p>Developers are usually more technically aligned and have more impact on the delivery of services than the previous groups.</p>
+
+
+  </article>
+
+  <article id="section-glossary">
+
+    <h1 id="glossary">Glossary</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="code">Code</h2>
+
+<p>Any explicitly described system of rules. This includes laws, policy and ordinances, as well as source code that is used to build software. Both of these are rules, some executed by humans and others by machines.</p>
+
+<h2 id="codebase">Codebase</h2>
+
+<p>Any discrete package of code (both source and policy), the tests and the documentation required to implement a piece of policy or software.</p>
+
+<p>This can be, for example, a document or a version-control repository.</p>
+
+<h2 id="continuous-integration">Continuous integration</h2>
+
+<p>In software engineering, continuous integration (CI) is the practice of merging all developers’ working copies to a development branch of a codebase as frequently as reasonable.</p>
+
+<h2 id="different-contexts">Different contexts</h2>
+
+<p>Two contexts are different if they are different public organizations or different departments for which there is not one decision maker that could make collaboration happen naturally.</p>
+
+<h2 id="general-public">General public</h2>
+
+<p>The public at large: end users of the code and the services based upon it.</p>
+
+<p>For example, a city’s residents are considered end users of a city’s services and of all code that powers these services.</p>
+
+<h2 id="open-source">Open source</h2>
+
+<p>Open source is defined by the Open Source Initiative in their <a href="https://opensource.org/osd-annotated">Open Source Definition</a>.</p>
+
+<h2 id="open-standard">Open standard</h2>
+
+<p>An open standard is any standard that meets the Open Source Initiative’s <a href="https://opensource.org/osr">Open Standard Requirements</a>.</p>
+
+<h2 id="policy">Policy</h2>
+
+<p>A policy is a deliberate system of principles to guide decisions and achieve rational outcomes.
+A policy is a statement of intent, and is implemented as a procedure or protocol.
+Policies are generally adopted by a governance body within an organization.
+Policies can assist in both subjective and objective decision making.</p>
+
+<p>Public policy is the process by which governments translate their political vision into programs and actions to deliver outcomes.</p>
+
+<p>At the national level, policy and legislation (the law) are usually separate. The distinction is often more blurred in local government.</p>
+
+<p>In the Standard the word ‘policy’ refers to policy created and adopted by public organizations such as governments and municipalities.</p>
+
+<h2 id="public-code">Public code</h2>
+
+<p>Public code is open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.</p>
+
+<p>Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.</p>
+
+<p>Public code serves the public interest, is open, legible, accountable, accessible and sustainable.</p>
+
+<p>By developing public code independently from but still implementable in the local context for which it was developed, as well as documenting the development process openly, public code can provide a building block for others to:</p>
+
+<ul>
+  <li>re-implement in their local context</li>
+  <li>take as a starting point to continue development</li>
+  <li>use as a basis for learning</li>
+</ul>
+
+<p>To facilitate reuse, public code is either released into the public domain or licensed with an open license that permits others to view and reuse the work freely and to produce derivative works.</p>
+
+<h2 id="repository">Repository</h2>
+
+<p>A repository is a storage location used by version control tools for files and metadata of a codebase.
+Repositories allow multiple developers to work on the same set of files.
+Repositories are able to store multiple versions of sets of files.</p>
+
+<h2 id="version-control">Version control</h2>
+
+<p>Version control is the management of changes to source code and the files associated with it.
+Changes are usually identified by a code, termed the <em>revision number</em> (or similar).
+Each revision is associated with the time it was made and the person making the change, thus making it easier to retrace the evolution of the code.
+Revision control systems can be used to compare different versions with each other and to see how content has changed over time.</p>
+
+
+  </article>
+
+  <article id="section-criteria">
+    <h1>Criteria</h1>
+    
+    <ol>
+    
+      
+        
+      <li><a href="#section-criteria-code-in-the-open.md">原始碼要開放</a></li>
+      
+      <li><a href="#section-criteria-bundle-policy-and-code.md">政策與原始碼要合捆</a></li>
+      
+      <li><a href="#section-criteria-reusable-and-portable-codebases.md">程式碼要可重複使用且可攜</a></li>
+      
+      <li><a href="#section-criteria-open-to-contributions.md">歡迎貢獻者</a></li>
+      
+      <li><a href="#section-criteria-make-contributing-easy.md">貢獻要容易</a></li>
+      
+      <li><a href="#section-criteria-version-control-and-history.md">維護版本控制</a></li>
+      
+      <li><a href="#section-criteria-require-review.md">要求審查貢獻內容</a></li>
+      
+      <li><a href="#section-criteria-document-objectives.md">代碼庫有目標文件</a></li>
+      
+      <li><a href="#section-criteria-documenting.md">程式碼有文件</a></li>
+      
+      <li><a href="#section-criteria-understandable-english-first.md">使用白話的英語</a></li>
+      
+      <li><a href="#section-criteria-open-standards.md">採用開放標準</a></li>
+      
+      <li><a href="#section-criteria-continuous-integration.md">使用持續整合</a></li>
+      
+      <li><a href="#section-criteria-open-licenses.md">發行採用開放授權</a></li>
+      
+      <li><a href="#section-criteria-findability.md">代碼庫可查詢得到</a></li>
+      
+      <li><a href="#section-criteria-style.md">風格要前後一致</a></li>
+      
+      <li><a href="#section-criteria-document-maturity.md">紀錄代碼庫成熟度</a></li>
+      
+    </ol>
+  </article>
+
+  <figure>
+    <img src="/assets/unlock.svg" alt="unlock">
+  </figure>
+
+  
+  
+    
+      
+    <article id="section-criteria-code-in-the-open.md">
+      <h1 id="原始碼要開放">原始碼要開放</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>任何使用中的<a href="/glossary.html#policy">政策</a>所有<a href="/glossary.html#code">原始碼</a>都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>貢獻者不得上傳與使用者及其組織單位，或與第三方相關的敏感性資訊到<a href="/glossary.html#repository">儲存庫</a>中。</li>
+  <li>目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都應該公開。</li>
+  <li>可選擇是否要以文件記錄<a href="/glossary.html#general-public">一般大眾</a>與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>以開放精神編寫原始碼能：</p>
+
+<ul>
+  <li>改善資訊透明</li>
+  <li>提高程式碼品質</li>
+  <li>促進稽核流程</li>
+</ul>
+
+<p>這些面向讓公民更有機會能瞭解，軟體與政策如何影響他們與公共組織的互動。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓原始碼或政策可以重複使用。</li>
+  <li>讓盡可能越多人能讀懂<a href="/glossary.html#codebase">代碼庫</a>以及當中的程式碼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織之外，查看這些原始碼。</li>
+  <li>確認代碼庫檔案與提交歷史紀錄不包含敏感性資訊。</li>
+  <li>檢查目前非使用中的原始碼是否有公開。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定合乎開放精神的政策。</li>
+  <li>以公開透明的政策為優先。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>孕育擁抱開放、重視學習、歡迎意見回饋的文化。</li>
+  <li>與外部供應商和自由工作者以開放精神的方式協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。</li>
+  <li>為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">以開放精神編寫原始碼</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed">程式碼應該開放或封閉的時機</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open">以開放精神編寫原始碼的資安考量</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/deploying-software-regularly">定期部署軟體</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">政府數位服務團如何使用 GitHub</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-bundle-policy-and-code.md">
+      <h1 id="政策與原始碼要合捆">政策與原始碼要合捆</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須包含<a href="/glossary.html#code">原始碼</a>所根據的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>代碼庫必須包含根據政策而來的所有原始碼，用於偵測詐騙的原始碼則可除外。</li>
+  <li>政策應該採用機器可讀且明確的格式。</li>
+  <li><a href="/glossary.html#continuous-integration">持續整合</a>測試應該驗證原始碼與政策能一致執行。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>如果要瞭解、重複利用程式碼，還有在代碼庫中互相協作，就必須要能同時取用原始碼與政策文件。瞭解使用情境與該情境的政策是基本原則，才能瞭解代碼庫試圖想解決的問題，以及程式碼解決這些問題的出發點。如果想評估是否能在新的情境中採用該代碼庫，則組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證代碼庫能反映合捆的政策。</li>
+  <li>確保成套合捆內容符合地方性技術基礎建設，或是特定公共組織的法律架構。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與公務人員確認程式碼根據的所有政策內容都有包含在內。</li>
+  <li>與公務人員確認根據政策而來的所有原始碼都有包含在內。</li>
+  <li>確認政策內容是否能在機器上解讀。</li>
+  <li>確認原始碼與政策間的執行一致性能通過持續整合測試。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>提供相關政策內文，以便收錄於<a href="/glossary.html#repository">儲存庫</a>中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。</li>
+  <li>請提供政策相關參考資料與連結。</li>
+  <li>政策內容請使用明確且機器可讀的格式，像是<a href="https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation">業務流程模型與標記法</a>、
+<a href="https://en.wikipedia.org/wiki/Decision_Model_and_Notation">決策模型與標記法</a>，以及
+<a href="https://en.wikipedia.org/wiki/CMMN">案例管理模型標記法</a>。</li>
+  <li>追蹤政策時，請使用與追蹤原始碼<a href="/criteria/version-control-and-history.html">相同的版本控制</a>與文件。</li>
+  <li>定期檢查代碼庫中非政策程式碼的變動，以及確認是否仍符合<a href="/criteria/document-objectives.html">政策意圖</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。</li>
+  <li>確保政策制定者、開發人員與設計師朝相同目標努力。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。</li>
+  <li>與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>針對如何讓政策文字更清楚提供意見。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Camunda <a href="https://bpmn.io/">於 bmpn.io 網站提供可協助製作業務流程 BPMN、案例管理 CMMN、決策 DMN 等模型與表記法圖表</a>的免費線上工具。</li>
+  <li>Trisotech 提供的 <a href="https://www.bpmnquickguide.com/view-bpmn-quick-guide/">BPMN 快速指南</a>。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-reusable-and-portable-codebases.md">
+      <h1 id="程式碼要可重複使用且可攜">程式碼要可重複使用且可攜</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須開發成能在<a href="/glossary.html#different-contexts">不同情境</a>中重複使用。</li>
+  <li>執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的<a href="/glossary.html#code">程式碼</a>或服務。</li>
+  <li>代碼庫應該有多方單位使用。</li>
+  <li>發展路線圖應該有多方單位的需求影響。</li>
+  <li>應該使用組態設定方式以將程式碼調整成能適應各情境的特定需求。</li>
+  <li>代碼庫應該能夠在地化。</li>
+  <li>程式碼與其文件不應該包含特定情況專用的資訊。</li>
+  <li>代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓其他政策制定者、開發人員與設計師等，能夠重複利用您所開發的內容，以及測試它、改善它，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。</li>
+  <li>讓新進人員能更容易瞭解程式碼（因為用途更廣泛通用）。</li>
+  <li>由於代碼庫以重複利用為前提籌劃設計，因此要調控代碼庫的目標使命、願景與範圍等也更容易。</li>
+  <li>多方使用的代碼庫更可以從能自我運作的社群中獲益。</li>
+  <li>任何貢獻者都能測試與貢獻給代碼庫，不需要仰賴任何其他貢獻者或部署底下的特定情況專用基礎架構。</li>
+  <li>以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。</li>
+  <li>以文件清楚記錄用途的模組，更容易在另一種情境中重複利用。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓他人重複利用代碼庫。</li>
+  <li>建立社群。</li>
+  <li>將文件、支援、修正錯誤⋯⋯等責任轉移給其他單位。</li>
+  <li>保證模組在任何情境下都足以通用。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與另一組織單位角色與您相似的人確認，看他們是否能重複利用代碼庫，以及需要怎麼進行。</li>
+  <li>確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。</li>
+  <li>檢查是否有多方單位或是有在多種情境下正使用代碼庫。</li>
+  <li>檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為您的<a href="/glossary.html#policy">政策</a>撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。</li>
+  <li>確保代碼庫有將貴組織單位列為已知用戶。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>原始碼應該設計成：</p>
+
+<ul>
+  <li>能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，</li>
+  <li>能解決通用性質問題，而非特定問題，</li>
+  <li>以邏輯上具有意義且獨立的模組構成，</li>
+  <li>如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。</li>
+</ul>
+
+<p>確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行開發、使用、測試、部署等。</p>
+
+<p>在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable">讓原始碼開放且可重複利用</a>》。</li>
+  <li>OpenAPI 促進會定義的《<a href="https://spec.openapis.org/oas/latest.html">OpenAPI 規範</a>》，為人機可讀的
+HTTP API 標準，不受程式語言種類限制的介面描述。</li>
+  <li>W3C 全球資訊網協會《<a href="https://www.w3.org/International/questions/qa-i18n">在地化與國際化</a>》。</li>
+  <li>全球資訊網協會《<a href="https://www.w3.org/International/techniques/authoring-html">國際化技巧：編寫 HTML 與 CSS</a>》。</li>
+  <li>GNU 作業系統的 <a href="https://www.gnu.org/software/gettext/gettext.html">GNU gettext</a>。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-open-to-contributions.md">
+      <h1 id="歡迎貢獻者">歡迎貢獻者</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須允許任何人針對代碼庫提出修改建議。</li>
+  <li>代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」檔案說明。</li>
+  <li>代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「<code class="language-plaintext highlighter-rouge">GOVERNANCE</code>」檔案來說明。</li>
+  <li>代碼庫應該宣布投入其開發與維護工作的參與組織單位。</li>
+  <li>代碼庫應該要有可公開取得的發展路線圖。</li>
+  <li>代碼庫應該公布代碼庫的活動統計數據。</li>
+  <li>可選擇是否為代碼庫加入貢獻者的行為準則。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>幫助新參與者瞭解並且信任代碼庫社群的領導。</li>
+  <li>避免參與者因為無法影響代碼庫的目標與進展，而造成代碼庫社群分裂成分歧的社群。</li>
+  <li>幫助使用者在代碼庫間做出選擇。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證他人會參與社群。</li>
+  <li>保證其他人會重複使用代碼庫。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認可以提交修改建議給代碼庫。</li>
+  <li>確認代碼庫有貢獻指引。</li>
+  <li>確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。</li>
+  <li>檢查是否有參與的組織單位名單。</li>
+  <li>檢查是否有發展路線圖。</li>
+  <li>檢查是否有公布活動統計數據。</li>
+  <li>檢查是否有行為準則。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為代碼庫加入其他資源的清單，而這些資源可幫助<a href="/glossary.html#policy">政策</a>專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。</li>
+  <li>考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。</li>
+  <li>如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。</li>
+  <li>確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼指南所提供的《<a href="https://opensource.guide/building-community/">營造友善的社群</a>》。</li>
+  <li>Mike McQuaid《<a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/">開放原始碼貢獻者瓶頸</a>》。</li>
+  <li>開放原始碼指南為成長中的<a href="/glossary.html#open-source">開放原始碼</a>社群專案所寫的《<a href="https://opensource.guide/leadership-and-governance/">領導與治理</a>》。</li>
+  <li>Pieter Hintjens《<a href="http://hintjens.com/blog:117">打造網路社群</a>》(長篇文章！)。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-make-contributing-easy.md">
+      <h1 id="貢獻要容易">貢獻要容易</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須有個可以公開接受任何人建議的議題追蹤器。</li>
+  <li>代碼庫必須說明，如何私下回報安全性問題來達成負責任的揭露。</li>
+  <li>文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「<code class="language-plaintext highlighter-rouge">README</code>」檔案中。</li>
+  <li>代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵遞論壇）。</li>
+  <li>文件應該說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓使用者能夠為共享的代碼庫修復問題與新增功能，能讓軟體變得更好、更可靠、功能更豐富。</li>
+  <li>讓人們能以協作方式採用共享的數位基礎建設。</li>
+  <li>幫助使用者在代碼庫間做出選擇。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證其他人會重複使用代碼庫。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有公開的議題追蹤器。</li>
+  <li>確認有說明如何私下通報安全性問題。</li>
+  <li>確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。</li>
+  <li>確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>追蹤代碼庫中的<a href="/glossary.html#policy">政策</a>問題，讓相關的外部政策專家如果自願也能夠協助。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>持續告知管理階層，您在支援其他貢獻者時所需要的時間與資源。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Joel Hans《<a href="https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf">如何引發他人為您的開放原始碼專案做出優秀貢獻</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">以開放精神編寫原始碼的好處</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-version-control-and-history.md">
+      <h1 id="維護版本控制">維護版本控制</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>社群必須要有方法為<a href="/glossary.html#code">程式碼</a>維護<a href="/glossary.html#version-control">版本控制</a>。</li>
+  <li><a href="/glossary.html#codebase">代碼庫</a>中的所有檔案皆必須有版本控制。</li>
+  <li>所有決定皆必須記錄成提交訊息。</li>
+  <li>每份提交訊息皆必須盡可能附上討論與議題連結。</li>
+  <li>代碼庫應該以分散式版本控制系統作維護。</li>
+  <li>貢獻者應該將相關的修改變動提交內容作群組分類。</li>
+  <li>維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。</li>
+  <li>貢獻者應該偏好使用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。</li>
+  <li>貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>版本控制代表追蹤程式碼歷來的變動。這能讓您為代碼庫製作有條理的變動歷史文件。這是大規模協作能運作的要素。</p>
+
+<p>分散式版本控制能讓您：</p>
+
+<ul>
+  <li>擁有完整的程式碼副本與其版本歷史</li>
+  <li>在需要時可以將代碼庫恢復至先前版本</li>
+  <li>紀錄變動與變動的原因，可幫助未來開發人員瞭解整個過程</li>
+  <li>比較兩個不同版本</li>
+  <li>在將修改內容合併回代碼庫之前，各團隊可以針對修改變動平行作業</li>
+  <li>在沒有網路時也能繼續作業，可以日後再將修改變動合併回代碼庫與其他人整合</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>代替<a href="/criteria/document-maturity.html">成熟度宣告</a>。</li>
+  <li>保證程式碼能正確執行。</li>
+  <li>保證有人加入協作。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。</li>
+  <li>審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。</li>
+  <li>審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。</li>
+  <li>檢查版本控制系統是否為分散式。</li>
+  <li>審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。</li>
+  <li>檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。</li>
+  <li>檢查代碼庫在可能的情況下，檔案都是採用文字格式。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>如果因為<a href="/glossary.html#policy">政策</a>改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
+    <ul>
+      <li>政策改變的地方，</li>
+      <li>代碼庫如何因應而改變。</li>
+    </ul>
+  </li>
+</ul>
+
+<p>舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。</li>
+  <li>使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。</li>
+  <li>提交內容的訊息要寫清楚，方便之後比較各版本。</li>
+  <li>在政策改變以後與政策制定者合作，說明原始碼更新的內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Karl Fogel《<a href="https://producingoss.com/en/vc.html#vc-vocabulary">製作開放原始碼軟體：版本控制字彙</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding">維護程式碼的版本控制</a>》。</li>
+  <li>GitHub 提供的「<a href="https://lab.github.com/">GitHub學習實驗室</a>」，可學習如何使用 GitHub，或是重溫您的技巧。</li>
+  <li>GitHub 提供的「<a href="https://education.github.com/git-cheat-sheet-education.pdf">Git 密技表</a>」列出了最常用的
+git 指令。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-require-review.md">
+      <h1 id="要求審查貢獻內容">要求審查貢獻內容</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>所有被接受或是提交給<a href="/glossary.html#codebase">代碼庫</a>正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。</li>
+  <li>審查必須包含原始碼、<a href="/glossary.html#policy">政策</a>、測試、文件等。</li>
+  <li>如果不接受貢獻內容，審查人員必須提供意見回饋。</li>
+  <li>貢獻內容應該遵循代碼庫的標準、架構、決策安排等，以通過審查。</li>
+  <li>審查內容應該包含執行<a href="/glossary.html#code">程式碼</a>與執行代碼庫測試。</li>
+  <li>貢獻內容應該由與貢獻者不同背景情境的人來審查。</li>
+  <li>版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。</li>
+  <li>審查應該在兩個工作天內進行。</li>
+  <li>可選擇是否由多位審查人員進行審查。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>提升代碼庫品質。</li>
+  <li>降低安全性風險與營運風險。</li>
+  <li>打造每份貢獻內容皆能有品質的文化。</li>
+  <li>揪出可能發生的極明顯錯誤。</li>
+  <li>只有真正能為代碼庫提升價值的貢獻內容才會被接受，可以給予貢獻者安全感。</li>
+  <li>向貢獻者保證在一段時間內提供意見回饋或是合作改善。</li>
+  <li>快速審查能提高貢獻者交付貢獻內容的頻率以及參與熱度。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證能找到問題的合適解決方案。</li>
+  <li>代表審查人員必須承擔責任。</li>
+  <li>貢獻者能從編寫文件與測試中免除責任。</li>
+  <li>提供您合適的審查人選。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。</li>
+  <li>確認審查內容包含原始碼、政策、測試、文件等。</li>
+  <li>針對未被採用的貢獻內容，確認有適當解釋原因。</li>
+  <li>檢查審查範圍有涵蓋是否遵循標準、架構、代碼庫指引等。</li>
+  <li>檢查審查人員在審查時是否有執行程式碼與測試。</li>
+  <li>與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。</li>
+  <li>檢查<a href="/glossary.html#version-control">版本控制</a>系統中是否有採用分支保護。</li>
+  <li>檢查貢獻提交與審查之間的時間間隔。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。</li>
+  <li>採用具有審查與意見回饋功能的版本控制系統或作業流程。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將交付妥善程式碼作為共同目標。</li>
+  <li>確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。</li>
+  <li>創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。</li>
+  <li>確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。</li>
+  <li>當他人請求您審查程式碼時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content">英國政府數位服務團程式碼審查程序</a>》。</li>
+  <li><a href="https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches">GitHub</a>
+與 <a href="https://about.gitlab.com/2014/11/26/keeping-your-code-protected/">GitLab</a>
+平臺的分支保護說明。</li>
+  <li>Sage Sharp《<a href="https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/">程式修補審查的和善藝術</a>》。</li>
+  <li>Mozilla《<a href="https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177">參與度評測成果</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-document-objectives.md">
+      <h1 id="代碼庫有目標文件">代碼庫有目標文件</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。</li>
+  <li>代碼庫文件應該清楚描述<a href="/glossary.html#policy">政策</a>目標與代碼庫目標之前的關聯。</li>
+  <li>可選擇是否以文件記錄給<a href="/glossary.html#general-public">一般民眾</a>看的代碼庫目標。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>以文件記錄代碼庫目標：</p>
+
+<ul>
+  <li>提供簡易方法讓人方便判斷是否在當下或未來，會對此代碼庫或其模組感興趣。</li>
+  <li>幫助劃定您自己開發專案的範圍。</li>
+  <li>將代碼庫以及所包含模組的目的用途，清楚告知其他利害關係人與貢獻者。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證代碼庫能達成其陳述的目標。</li>
+  <li>保證會有人為代碼庫做出貢獻。</li>
+  <li>預防其他代碼庫試圖達成相同目標。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫文件有包含代碼庫目標，或主旨、使命等。</li>
+  <li>查看政策目標與代碼庫目標之間關聯的描述。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>將政策目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>納入會影響社會群體、代碼庫與開發目標的相關政策，例如可近用無障礙環境，或機會平等等價值或倫理取向的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將單位目標、組織目標或業務目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將技術與設計目標加入代碼庫文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Marek Hajduczenia《<a href="http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf">如何撰寫專案目標</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-documenting.md">
+      <h1 id="程式碼有文件">程式碼有文件</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>的所有功能、<a href="/glossary.html#policy">政策</a>及原始碼，都必須以可清楚瞭解的用語描述，讓懂
+<a href="/glossary.html#code">程式碼</a>目的用途的人也能夠理解。</li>
+  <li>代碼庫文件必須說明如何安裝與執行原始碼。</li>
+  <li>代碼庫文件必須為關鍵功能舉出範例。</li>
+  <li>代碼庫文件應該包含精要的說明，讓<a href="/glossary.html#general-public">一般民眾</a>和記者等廣泛的利害關係人都能清楚明白。</li>
+  <li>代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。</li>
+  <li>代碼庫文件應該包含所有功能的範例。</li>
+  <li>程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。</li>
+  <li>應該要有針對文件品質的<a href="/glossary.html#continuous-integration">持續整合</a>測試。</li>
+  <li>可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。</li>
+  <li>可選擇是否以文件中的範例來測試程式碼。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>使用者可以更快速上手代碼庫的使用並做出貢獻。</li>
+  <li>能幫助他人找到這個代碼庫，特別是那些在問「是不是已經有提供某某功能的程式碼」的人。</li>
+  <li>讓貴組織單位與其流程資訊更透明。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>直接貢獻出更可重複使用，以及更具可攜性的程式碼（請參閱<a href="/criteria/reusable-and-portable-codebases.html">編寫可重複使用且具可攜性的程式碼</a>）。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。</li>
+  <li>確認文件有說明如何安裝與執行原始碼。</li>
+  <li>確認文件有包含主要功能的範例。</li>
+  <li>向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。</li>
+  <li>檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。</li>
+  <li>檢查文件中列舉的所有功能都包含範例。</li>
+  <li>檢查文件中是否包含高層架構圖，或類似的組件關係圖表。</li>
+  <li>確認整合測試有包含到程式碼文件品質，例如確認由程式碼生成的文件，並檢查連結與圖片等。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>定期查看代碼庫的非政策程式碼的變動情況。</li>
+  <li>針對如何讓非政策文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>嘗試使用代碼庫。</li>
+  <li>確保您同時瞭解政策、原始碼以及文件內容。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>定期查看代碼庫中非原始碼部分的變動情況。</li>
+  <li>針對如何讓非原始碼文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Write the Docs《<a href="https://www.writethedocs.org/guide/">文件指南</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-understandable-english-first.md">
+      <h1 id="使用白話的英語">使用白話的英語</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>的所有文件都必須使用英語。</li>
+  <li>所有<a href="/glossary.html#code">程式碼</a>都必須使用英語編寫，其中<a href="/glossary.html#policy">政策</a>是由機器解讀當作程式碼的部分則除外。</li>
+  <li>任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。</li>
+  <li>任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。</li>
+  <li>代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。</li>
+  <li>代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。</li>
+  <li>根據《<a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">網頁內容近用性無障礙指南 2</a>》的建議，文件內容應該以國中識讀程度為主。</li>
+  <li>可選擇是否提供任何程式碼、文件、測試等的翻譯版。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓不同情境的廣大利害關係人，都能瞭解代碼庫以及其用途。</li>
+  <li>讓代碼庫更容易被找到。</li>
+  <li>能幫助您達成《<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟無障礙環境命令</a>》，內容要求大多數的公家機關資訊都要能夠近用以滿足無障礙環境。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓代碼庫功能解說更容易瞭解。</li>
+  <li>幫助他人在沒有額外解釋之下，就能理解貴組織單位的業內用語。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫文件有英語版本。</li>
+  <li>確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。</li>
+  <li>確認任何非英語政策都有隨附英語版摘要。</li>
+  <li>確認翻譯版與英語版內容相同。</li>
+  <li>確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。</li>
+  <li>檢查文件的拼字、文法與易讀性等。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在使用這些詞彙的地方加上詞彙表連結。</li>
+  <li>以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+  <li>詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>根據 W3C 全球資訊網協會《<a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容近用性無障礙指南 2.1 與 3.1 之可讀性</a>》內文，撰寫的文字內容要更容易閱讀與理解。</li>
+  <li>Theo Sanderson 所發表的「<a href="https://splasho.com/upgoer5/">Upgoer 5 文字編輯軟體</a>」只允許使用最常用的
+1000 個英文單字。</li>
+  <li>美國總務署《<a href="https://www.plainlanguage.gov/about/definitions/">白話語言定義</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-open-standards.md">
+      <h1 id="採用開放標準">採用開放標準</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>如要達成促進資料交換的特性，就必須採用符合<a href="https://opensource.org/osr">開放原始碼促進會其開放標準需求規範</a>的
+<a href="/glossary.html#open-standard">開放標準</a>。</li>
+  <li>如果有使用到任何的非開放標準，則必須在文件中清楚記錄。</li>
+  <li>代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。</li>
+  <li>代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。</li>
+  <li>如果還沒有已存在的開放標準可採用，則應該投入開發新標準。</li>
+  <li>採用標準時，應該優先選擇可經機器測試的標準。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>為不同的系統之間建立互通性。</li>
+  <li>降低廠商套牢的可能性。</li>
+  <li>保證可以取得重複利用與貢獻代碼庫所需的知識。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>讓軟體的操作方法變得可以瞭解。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。</li>
+  <li>確認若有採用任何的非開放標準，皆有清楚記錄在文件中。</li>
+  <li>確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>以政策要求盡可能在任何情況下使用開放標準。</li>
+  <li>禁止採購不採用開放標準的技術科技。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>考慮在<a href="/glossary.html#code">程式碼</a>審查中納入開放標準依循評估。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將是否依循標準加入<a href="/glossary.html#continuous-integration">持續整合</a>測試中。</li>
+  <li>審查提交紀錄與其他<a href="/glossary.html#repository">儲存庫</a>資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國內閣辦公室發表的《<a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">開放標準原則</a>》
+<a href="/glossary.html#policy">政策</a>報告。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-continuous-integration.md">
+      <h1 id="使用持續整合">使用持續整合</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#code">原始碼</a>中的所有功能都必須有自動化測試。</li>
+  <li>所有貢獻內容都必須先通過自動化測試，才能上傳至<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>代碼庫必須有說明貢獻內容結構的相關準則。</li>
+  <li>代碼庫必須有活躍貢獻者。</li>
+  <li>代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。</li>
+  <li>應該監督原始碼測試與文件的涵蓋範圍。</li>
+  <li>可選擇是否測試<a href="/glossary.html#policy">政策</a>和文件，與原始碼間有無一致性，或是反之亦然。</li>
+  <li>可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>使用<a href="/glossary.html#continuous-integration">持續整合</a>：
+    <ul>
+      <li>可以讓您快速找出代碼庫的問題所在，</li>
+      <li>能在降低貢獻者面臨壓力的同時，允許承擔風險並且專注在解決問題上，</li>
+      <li>可降低新貢獻者對整體內容理解的門檻，讓他們更容易提出修改，</li>
+      <li>讓程式碼更容易維護，</li>
+      <li>能加速開發週期。</li>
+    </ul>
+  </li>
+  <li>修改內容較少、時常提出的貢獻，通常較為容易評估，其風險也低於內容龐大、累積很久才一次提出的變更。</li>
+  <li>活躍開發中的代碼庫較能提供協作與意見回饋的機會。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>建立能夠順暢作業、可擴展，且能容錯的基礎架構。</li>
+  <li>建立有意義的測試。</li>
+  <li>測試實際會發生的情境。</li>
+  <li>保證交付的程式碼與政策期望的成果確實相同。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有測試可用。</li>
+  <li>確認程式碼覆蓋率工具能檢查到 100% 的程式碼。</li>
+  <li>確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。</li>
+  <li>確認有貢獻準則說明貢獻內容的結構。</li>
+  <li>確認最近三個月內有貢獻內容上傳。</li>
+  <li>檢查程式碼覆蓋率數據是否有公布。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。</li>
+  <li>確保政策文件也有設好自動化測試。</li>
+  <li>如果政策文件未能通過測試，請立即修正。</li>
+  <li>確保程式碼能反映出政策的任何變動（請參閱<a href="/criteria/version-control-and-history.html">維護版本控制</a>）。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保能儘快且經常給真正的終端使用者進行測試。</li>
+  <li>以頻繁交付少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。</li>
+  <li>聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。</li>
+  <li>發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次交付。</li>
+  <li>協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。</li>
+  <li>協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。</li>
+  <li>編排程式碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。</li>
+  <li>調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。</li>
+  <li>經常部署。</li>
+  <li>至少每天整合工作內容一次。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Martin Fowler《<a href="https://www.martinfowler.com/articles/continuousIntegration.html">什麼是持續整合</a>》。</li>
+  <li>Jez Humble《<a href="https://www.continuousdelivery.com/">什麼是持續交付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/standards/continuous-delivery.html">使用持續交付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly">品質保證：定期測試您的服務</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-open-licenses.md">
+      <h1 id="發行採用開放授權">發行採用開放授權</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>所有<a href="/glossary.html#code">程式碼</a>與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。</li>
+  <li>軟體原始碼必須採用<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款</a>。</li>
+  <li>所有程式碼皆必須搭配授權條款檔案一併發行。</li>
+  <li>不得要求貢獻者將其貢獻的程式碼著作權轉讓給<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。</li>
+  <li>可選擇是否為不同類型的程式碼與文件採用多重授權條款。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓任何人都可以查看程式碼，並知道他們可以與該如何重複利用這些程式碼。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>預防任何特定行為人使用程式碼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫有清楚給予授權條款。</li>
+  <li>確認原始碼的授權條款有列於<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清單</a>，以及文件的授權條款有
+<a href="https://opendefinition.org/licenses/">符合「開放定義」</a>。</li>
+  <li>確認代碼庫中有包含其採用的授權條款檔案。</li>
+  <li>確認貢獻指南中，以及<a href="/glossary.html#repository">儲存庫</a>的組態設定中，沒有求貢獻者轉讓著作權。</li>
+  <li>在代碼庫<a href="/glossary.html#continuous-integration">持續整合</a>測試中，確認是否有檢查授權內容為機器可讀的檢查項目。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定要求程式碼必須採用<a href="/glossary.html#open-source">開放原始碼</a>授權的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>只與能採用開放原始碼授權交付與發行其程式碼的開放原始碼軟體供應商合作。</li>
+  <li>請注意，雖然<a href="https://creativecommons.org/licenses/">創用CC授權</a>適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>每當建立新的代碼庫時，都要加入新的「<code class="language-plaintext highlighter-rouge">license</code>」授權條款檔案。</li>
+  <li>每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼促進會所發表的《<a href="https://opensource.org/osd">開放原始碼定義</a>》，所有開放原始碼授權條款皆符合這套定義。</li>
+  <li>紐西蘭CC Aotearoa《<a href="https://creativecommons.org/about/videos/creative-commons-kiwi">創用CC介紹動畫影片</a>》。</li>
+  <li>歐洲自由軟體基金會所發表的《<a href="https://reuse.software/spec/">REUSE 倡議規範</a>》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。</li>
+  <li>Linux 基金會所發表的 <a href="https://spdx.org/licenses/">SPDX 授權條款清單</a>提供經標準化、且機器可讀的大多數授權條款縮寫表示法。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-findability.md">
+      <h1 id="代碼庫可查詢得到">代碼庫可查詢得到</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，必須能搜尋得到<a href="/glossary.html#codebase">代碼庫</a>。</li>
+  <li>在搜尋引擎查找代碼庫名稱時，必須能搜尋得到代碼庫。</li>
+  <li>維護人員應該將代碼庫提交至相關的軟體目錄上。</li>
+  <li>代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。</li>
+  <li>代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、<a href="/glossary.html#repository">儲存庫</a>、位置、網站等。</li>
+  <li>代碼庫應該包含機器可讀的中介資料說明，例如採用 <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a>
+格式的檔案。</li>
+  <li>可選擇是否為代碼庫設定專用的網域名稱。</li>
+  <li>可選擇是否在社群舉辦的會議中定期進行簡報。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>必須主動積極；不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫。</li>
+  <li>有中介資料說明檔案會讓代碼庫更容易被發現。</li>
+  <li>一旦代碼庫越容易被發現，更多的潛在協作者也就找得到它。</li>
+  <li>撰寫出良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF
+自由軟體基金會的軟體目錄列表之中，使代碼庫成為語意網路中的一部份。如此一來，他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>確認新的協作人員或複製者。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認以白話英語敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>確認以技術性文字敘述相關問題來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>確認以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。</li>
+  <li>檢查代碼庫有刊登在相關軟體型錄上。</li>
+  <li>檢查代碼庫的網站有描述代碼庫能夠解決的問題。</li>
+  <li>檢查永久唯一識別碼條目有提及主要貢獻者。</li>
+  <li>檢查永久唯一識別碼條目中有包含儲存庫位置。</li>
+  <li>檢查永久唯一識別碼條目有列出代碼庫網站。</li>
+  <li>檢查中介資料說明檔案是機器可讀的格式。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。</li>
+  <li>請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。</li>
+  <li>在相關會議上作簡報介紹代碼庫如何執行<a href="/glossary.html#policy">政策</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。</li>
+  <li>確保專案參與人員出席相關會議或作簡報介紹。</li>
+  <li>在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>搜尋引擎最佳化。</li>
+  <li>請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。</li>
+  <li>推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Wikidata 維基數據社群《<a href="https://www.wikidata.org/wiki/Wikidata:Introduction">維基數據簡介</a>》。</li>
+  <li>FSF 自由軟體基金會《<a href="https://directory.fsf.org/wiki/Main_Page">FSF 軟體目錄列表</a>》。</li>
+  <li>GO FAIR 國際支援與合作辦公室所撰寫的《<a href="https://www.go-fair.org/fair-principles/">FAIR科學資料管理與盡職治理指導原則</a>》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-style.md">
+      <h1 id="風格要前後一致">風格要前後一致</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li>貢獻內容必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是<a href="/glossary.html#codebase">代碼庫</a>社群自身的風格指南，或是代碼庫所宣布的或其中部分有採用的既有風格。</li>
+  <li>貢獻內容應該通過自動化的風格測試。</li>
+  <li>代碼庫當中較複雜的程式碼區段，應該包含列內註解與說明文件。</li>
+  <li>可選擇是否將<a href="/criteria/understandable-english-first.html">可理解的白話英語</a>小節加入風格指南之中。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<ul>
+  <li>讓不同環境的貢獻者可以在統合的產品上合作。</li>
+  <li>用詞統一能減少貢獻者之間在溝通上的摩擦。</li>
+</ul>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>幫助貢獻者寫好程式碼，或者精確說明他們在做什麼。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認貢獻內容有遵循文件中指定的風格指南。</li>
+  <li>檢查是否有自動化的風格測試。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為<a href="/glossary.html#policy">政策</a>與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「
+<code class="language-plaintext highlighter-rouge">README</code>」檔案。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在<a href="/glossary.html#repository">儲存庫</a>中加入相關文件，像是「
+<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「<code class="language-plaintext highlighter-rouge">README</code>」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查的其他層面。指南應該包含貢獻的
+<a href="/glossary.html#code">程式碼</a>預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。</p>
+
+<p>此外：</p>
+
+<ul>
+  <li>使用程式碼品質分析工具 (linter)。</li>
+  <li>在代碼庫中加入程式碼品質分析工具的組態設定。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Hugo Martins《<a href="https://github.com/caramelomartins/awesome-linters">程式碼品質分析工具清單</a>》。</li>
+  <li>維基百科上的《<a href="https://en.wikipedia.org/wiki/Programming_style">代碼風格</a>》條目。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-document-maturity.md">
+      <h1 id="紀錄代碼庫成熟度">紀錄代碼庫成熟度</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="需求規範">需求規範</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">代碼庫</a>必須註明版本編號。</li>
+  <li>準備好可供使用的代碼庫，必須只能依賴其他也已經準備好可供使用的代碼庫。</li>
+  <li>尚未準備好使用的代碼庫，必須有所列標籤之一：prototype、alpha、beta、pre-release 等版本進度。</li>
+  <li>代碼庫應該包含每次版本的變動紀錄，像是以「<code class="language-plaintext highlighter-rouge">CHANGELOG</code>」日誌格式檔記錄。</li>
+</ul>
+
+<h2 id="此措施為何重要">此措施為何重要</h2>
+
+<p>清楚標示代碼庫的成熟度，有助於他人決定是否要重複使用、投資，或為該代碼庫做出貢獻。</p>
+
+<h2 id="此措施辦不到的事">此措施辦不到的事</h2>
+
+<ul>
+  <li>保證他人會來使用<a href="/glossary.html#code">程式碼</a>。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認代碼庫有版本編號策略，且有文件記載該策略。</li>
+  <li>確認有清楚表明最新版的取得位置。</li>
+  <li>確認代碼庫不依賴其他成熟度標示較低的任何代碼庫。</li>
+  <li>確認代碼庫是已準備好可供使用，還是仍標示為 prototype、alpha、beta、pre-release 等開發中版本。</li>
+  <li>檢查是否有變更紀錄。</li>
+</ul>
+
+<h2 id="政策制定者需要的工作">政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定<a href="/glossary.html#policy">政策</a>時，請記住任何開發出來的程式碼都必須先經過測試與改善，才能夠投入服務。</li>
+  <li>考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫，公測版服務不要使用 prototype
+原型代碼庫。</li>
+  <li>若代碼庫尚未準備好供一般使用，請與開發人員一起確保該代碼庫是否有標示適當標籤：
+    <ul>
+      <li>prototype：原型概念，測試外觀與感覺體驗，並且從內部證明技術的可行性概念，</li>
+      <li>alpha：內部測試，在限制的一群使用者中進行引導性測試，</li>
+      <li>beta：公開測試，讓更多<a href="/glossary.html#general-public">一般大眾</a>參與測試，例如測試代碼庫在大規模操作下是否仍能運作，</li>
+      <li>pre-release：準發行版，已經準備好發行，但尚未獲得正式批准的程式碼。</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>在每個指示程式碼成熟度的介面中加上明顯的標頭。</li>
+  <li>所有正式發行的程式碼都要有版本編號。</li>
+  <li>特別是在採用「滾動發行」的情況下，程式碼的版本資訊可以根據<a href="/glossary.html#version-control">版本控制</a>系統的中介資料自動衍生（例如使用
+<a href="https://git-scm.com/docs/git-describe">git describe</a>）。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>澳洲數位轉型局《<a href="https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process">服務設計與交付流程</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/agile-delivery">敏捷交付服務手冊</a>》。</li>
+  <li>許多代碼庫使用「<a href="https://semver.org/">語意化版本控制規範</a>」來標示版本。</li>
+  <li>英國政府數位服務團《<a href="https://www.youtube.com/watch?v=_cyI7DMhgYc">什麼是服務開發當中的探索、Alpha、Beta、上線階段？ [影片 0’0”59]</a>》。</li>
+</ul>
+
+    </article>
+    
+
+  <article id="section-contributing">
+
+    <h1 id="contributing-to-this-standard">Contributing to this standard</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>🙇‍♀️ Thank you for contributing!</p>
+
+<p>We understand that a standard like this can only be set in collaboration with as many public technologists, policy makers and interested folk as possible. Thus we appreciate your input, enjoy feedback and welcome improvements to this project and are very open to collaboration.</p>
+
+<p>We love issues and pull requests from everyone. If you’re not comfortable with GitHub, you can email use your feedback at <a href="mailto:info@publiccode.net">info@publiccode.net</a>.</p>
+
+<h2 id="problems-suggestions-and-questions-in-issues">Problems, suggestions and questions in issues</h2>
+
+<p>A high-level overview of the development that we already have sketched out can be seen in the <a href="/docs/roadmap.html">roadmap</a>.
+Please help development by reporting problems, suggesting changes and asking questions.
+To do this, you can <a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue">create a GitHub issue</a> for this project in the <a href="https://github.com/publiccodenet/standard/issues">GitHub Issues for the Standard for Public Code</a>.</p>
+
+<p>Or, sign up to the <a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">mailing list</a> and send an email to
+<a href="mailto:standard@lists.publiccode.net">standard@lists.publiccode.net</a>.</p>
+
+<p>You don’t need to change any of our code or documentation to be a contributor!</p>
+
+<h2 id="documentation-and-code-in-pull-requests">Documentation and code in pull requests</h2>
+
+<p>If you want to add to the documentation or code of one of our projects you should make a pull request.</p>
+
+<p>If you never used GitHub, get up to speed with <a href="https://docs.github.com/en/get-started/quickstart/github-flow">Understanding the GitHub flow</a> or follow one of the great free interactive courses in the <a href="https://lab.github.com/">GitHub learning lab</a> on working with GitHub and working with MarkDown, the syntax this project’s documentation is in.</p>
+
+<p>This project is licensed Creative Commons Zero v1.0 Universal, which essentially means that the project, along with your contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it.</p>
+
+<h3 id="1-make-your-changes">1. Make your changes</h3>
+
+<p>Contributions should <a href="/docs/standard-for-public-code.html">follow</a> the requirements set out in the criteria of the Standard for Public code itself.
+Reviewers will also be ensuring that contributions are aligned with the <a href="/introduction.html#values-of-public-code">values of public code</a>.</p>
+
+<p>This project uses the <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow branching model and workflow</a>. When you’ve forked this repository, please make sure to create a feature branch following the GitFlow model.</p>
+
+<p>Add your changes in commits <a href="https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message">with a message that explains them</a>.
+If more than one type of change is needed, group logically related changes into separate commits.
+For example, white-space fixes could be a separate commit from text content changes.
+Document choices or decisions you make in the commit message, this will enable everyone to be informed of your choices in the future.</p>
+
+<p>If you are adding code, make sure you’ve added and updated the relevant documentation and tests before you submit your pull request. Make sure to write tests that show the behavior of the newly added or changed code.</p>
+
+<h4 id="style">Style</h4>
+
+<p>The Standard for Public Code aims to <a href="https://standard.publiccode.net/criteria/understandable-english-first.html">use plain English</a> and we have chosen American English for spelling.
+However, we want to emphasize that it is more important that you make your contribution than worry about spelling and typography.
+We will help you get it right in our review process and we also have a separate quality check before <a href="/docs/releasing.html">making a new release</a>.</p>
+
+<h4 id="standards-to-follow">Standards to follow</h4>
+
+<p>These are the standards that the Standard for Public Code uses.
+Please make sure that your contributions are aligned with them so that they easier can be merged.</p>
+
+<ul>
+  <li><a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a> - for requirement level keywords</li>
+  <li><a href="https://www.w3.org/TR/WCAG21/#readable">Web Content Accessibility Guidelines 2.1</a> - for readibility</li>
+</ul>
+
+<h3 id="2-pull-request">2. Pull request</h3>
+
+<p>When submitting the pull request, please accompany it with a description of the problem you are trying to solve and the issue number that this pull request fixes.
+It is preferred for each pull request to address a single issue where possible.
+In some cases a single set of changes may address multiple issues, in which case be sure to list all issue numbers fixed.</p>
+
+<h3 id="3-improve">3. Improve</h3>
+
+<p>All contributions have to be reviewed by someone.</p>
+
+<p>It could be that your contribution can be merged immediately by a maintainer. However, usually, a new pull request needs some improvements before it can be merged. Other contributors (or helper robots) might have feedback. If this is the case the reviewing maintainer will help you improve your documentation and code.</p>
+
+<p>If your documentation and code have passed human review, it is merged.</p>
+
+<h3 id="4-celebrate">4. Celebrate</h3>
+
+<p>Your ideas, documentation and code have become an integral part of this project. You are the open source hero we need!</p>
+
+<p>In fact, feel free to open a pull request to add your name to the <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS</code></a> file and get eternal attribution.</p>
+
+<h2 id="translations-in-other-languages">Translations in other languages</h2>
+
+<p>While the Standard does not have any official translations, you can help maintain existing and add new <a href="https://github.com/publiccodenet/community-translations-standard">community translations of the Standard</a>.</p>
+
+<h2 id="releases">Releases</h2>
+
+<p>We have dedicated documentation for creating <a href="/docs/releasing.html">new releases</a> and <a href="/docs/printing.html">ordering printed standards</a>.</p>
+
+<p>For more information on how to use and contribute to this project, please read the <a href="/README.html"><code class="language-plaintext highlighter-rouge">README</code></a>.</p>
+
+
+  </article>
+
+  <figure>
+      <img src="/assets/collaborative-developement.svg" alt="collaborative-developement">
+    </figure>
+
+  <article id="section-code_of_conduct">
+
+    <h1 id="code-of-conduct">Code of Conduct</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- 2021-2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>Many community members are from civic or professional environments with behavioral codes yet some individuals are not.
+This document expresses expectations of all community members and all interactions regardless of communication channel.</p>
+
+<p>Be here to collaborate.</p>
+
+<p>Be considerate, respectful, and patient.</p>
+
+<p>Strive to be as constructive as possible.</p>
+
+<p>To raise a concern, please email directors@publiccode.net.</p>
+
+
+  </article>
+
+  <figure>
+    <img src="/assets/collaboration.svg" alt="collaboration">
+  </figure>
+
+  <article id="section-governance">
+
+    <h1 id="governance">Governance</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>This standard lies at the core of the codebase stewardship provided by the <a href="https://publiccode.net/">Foundation for Public Code</a>. We decide if a codebase is ready for community co-development based on this document.</p>
+
+<p>The standard is maintained by Foundation for Public Code staff.</p>
+
+<p><a href="/CONTRIBUTING.html">We welcome contributions, such as suggestions for changes or general feedback, from anyone.</a></p>
+
+<p>Because of the important role that the Standard for Public Code has in our core process we require the highest standards from the Standard.</p>
+
+<p>We will try to respond promptly to all pull requests. The pull request is an opportunity to work together to improve our methods and the Standard. We may not accept all changes, but we will explain our logic.</p>
+
+
+  </article>
+
+  <figure>
+    <img src="/assets/eco-system.svg" alt="ecosystem">
+  </figure>
+
+  <article id="section-changelog">
+
+    <h1 id="version-history">Version history</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<h2 id="version-040">Version 0.4.0</h2>
+
+<p>September 7th 2022: 🔭 the eleventh draft adds a new findability criterion.</p>
+
+<ul>
+  <li>Introduce new criterion: Make the codebase findable.</li>
+  <li>Improve How to test section for most criteria.</li>
+  <li>New requirement in Welcome contributors about publishing activity statistics.</li>
+  <li>Removed redundant requirement about portable and reusable code.</li>
+  <li>Expand open license definition to include both OSI and FSF approved licenses.</li>
+  <li>Rephrase MAY requirements to use the keyword OPTIONAL for clarity.</li>
+  <li>Expressed intent that the Standard for Public Code should meet its own requirements where applicable and added assessment.</li>
+  <li>Add SPDX license identifiers to files.</li>
+  <li>Introduced new Code of Conduct.</li>
+  <li>Clarify distinction between source code and policy text.</li>
+  <li>Restructuring of requirements with bullet point lists.</li>
+  <li>Acknowledge the importance of codebase modularity for reuse.</li>
+  <li>Move requirements related to Findability to the new criterion.</li>
+  <li>Clarify the role of non-open standards when used in a codebase.</li>
+  <li>Additional guidance about build-time and runtime dependencies.</li>
+  <li>Added roadmap for the development of the Standard for Public Code.</li>
+  <li>Update structure of Authors file.</li>
+  <li>Add Audrey Tang to Authors.</li>
+  <li>Added a list of criteria to the print edition.</li>
+  <li>Clarify what the standard means with policymakers, managers, developers and designers.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+  <li>Some hyperlinks updated.</li>
+</ul>
+
+<h2 id="version-030">Version 0.3.0</h2>
+
+<p>May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization.</p>
+
+<ul>
+  <li>Requirement for localization made explicit in Create reusable and portable code.</li>
+  <li>Documentation of governance changed from a SHOULD to a MUST.</li>
+  <li>Replace the very subjective (and hard to test) “contributions MUST be small” with requirement to document expectation in contributing guidelines and focus on a single issue.</li>
+  <li>Community translations now linked in the footer.</li>
+  <li>Revert “Replace BPMN svg with Mermaid flowchart”.</li>
+  <li>Many minor clarifications to language and sentences made more simple.</li>
+  <li>Some hyperlinks updated.</li>
+</ul>
+
+<h2 id="version-023">Version 0.2.3</h2>
+
+<p>March 15th 2022: 📜 the ninth draft allows English summaries for policy lacking an official translation.</p>
+
+<ul>
+  <li>Relax the criterion Use plain English by adding a new requirement allows bundled policy not available in English to have an accompanying summary in English instead of translating the full text.</li>
+  <li>Similarly, allow for English summaries for policies not available in English in Bundle policy and code.</li>
+  <li>Clarify that term ‘policy’ includes processes which impact development and deployment in Bundle policy and code.</li>
+  <li>Emphasize reusability also on parts of the solutions in Create reusable and portable code.</li>
+  <li>Expand guidance to Developers and designers in Create reusable and portable code about deploying to proprietary platforms.</li>
+  <li>Add nuance to use of non-English terms in what management need to do in Use plain English.</li>
+  <li>Change the pull request process diagram to use Mermaid instead of BPMN to make <a href="https://github.com/publiccodenet/community-translations-standard">community translations</a> easier.</li>
+  <li>Added Maurice Hendriks to AUTHORS.</li>
+  <li>Added OpenApi Specification to further reading.</li>
+  <li>Made the attributions in further reading sections clearer.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-022">Version 0.2.2</h2>
+
+<p>November 29th 2021: 🏛 the eighth draft recognizes that policy which executes as code may not be in English.</p>
+
+<ul>
+  <li>Document exception to “All code MUST be in English” where policy is interpreted as code.</li>
+  <li>Add MAY requirement regarding committer email addresses in Maintain version control.</li>
+  <li>Expand guidance to Policy Makers in Bundle policy and code.</li>
+  <li>Expand guidance to Developers and designers in Use a coherent style.</li>
+  <li>Add “Different contexts” to glossary.</li>
+  <li>Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS.</li>
+  <li>Add Digital Public Goods approval badge.</li>
+  <li>Added “next” and “previous” links to criteria pages of web version.</li>
+  <li>Add Open Standards principles to further reading.</li>
+  <li>Add Definition of plain language to further reading.</li>
+  <li>Move the Semantic Versioning Specification further reading reference.</li>
+  <li>Clarify that publiccode.yml is one example of a machine-readable metadata description.</li>
+  <li>Changed “your codebase” and “your organization” to be less possessive.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+  <li>Add instructions for creating a print version.</li>
+</ul>
+
+<h2 id="version-021">Version 0.2.1</h2>
+
+<p>March 1st 2021: 🧽 the seventh draft has minor cleaning up after version 0.2.0.</p>
+
+<ul>
+  <li>New SHOULD requirement on using a distributed version control system and why distributed is important.</li>
+  <li>Feedback requirements for rejected contributions are more strict than accepted ones.</li>
+  <li>Specify that copyright and license notices should also be machine-readable.</li>
+  <li>Advice on how to test that notices be machine-readable.</li>
+  <li>Clarify guidance for rolling releases.</li>
+  <li>Clear up definition of version control in glossary.</li>
+  <li>Add further reading encouraging contribution, SPDX, Git and reviewing contributions.</li>
+  <li>Add links to videos about the concept of public code.</li>
+  <li>Update BPMN link.</li>
+  <li>Reduce link duplication.</li>
+  <li>Add Alba Roza and Ngô Ngọc Đức Huy to authors.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-020">Version 0.2.0</h2>
+
+<p>October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity.</p>
+
+<ul>
+  <li>Split “Welcome contributions” criterion into “Make contributing easy” and “Welcome contributors”.</li>
+  <li>Rename criterion “Pay attention to codebase maturity” to “Document codebase maturity”.</li>
+  <li>Changed MUST to SHOULD for requirement of codebase in use by multiple parties.</li>
+  <li>Add MUST NOT requirement regarding copyright assignment.</li>
+  <li>Clarify role of configuration in reusable code requirement.</li>
+  <li>Glossary additions: continuous integration, policy, repository, and version control.</li>
+  <li>Replace references to ‘cities’ with ‘public organizations’.</li>
+  <li>Clarify aspects of sensitive code by separating contributor and reviewer requirements into separate items.</li>
+  <li>Expand further reading, and guidance to policy makers, developers and designers.</li>
+  <li>Add Felix Faassen and Arnout Engelen to authors.</li>
+  <li>Made additional minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-014">Version 0.1.4</h2>
+
+<p>November 27th 2019: 🧹 the fifth draft consists mostly of additional minor fixes.</p>
+
+<ul>
+  <li>Linked License.md file.</li>
+  <li>Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors.</li>
+  <li>Made punctuation more consistent, especially for bullet lists.</li>
+  <li>Made some minor changes to text for clarity.</li>
+</ul>
+
+<h2 id="version-013">Version 0.1.3</h2>
+
+<p>October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for the autumn cleaning</p>
+
+<ul>
+  <li>Renamed continuous delivery to continuous integration.</li>
+  <li>Referencing accessibility guidelines in the language standard.</li>
+  <li>A bunch of style and consistency fixes.</li>
+</ul>
+
+<h2 id="version-012">Version 0.1.2</h2>
+
+<p>August 22th 2019: 🌠 the third draft focuses on better text and takes community input</p>
+
+<ul>
+  <li>With some great new contributors comes a fresh author list.</li>
+  <li>All links are now HTTPS.</li>
+  <li>General proofreading, wording clarifications, and smashed typos.</li>
+  <li>Updated criteria:
+    <ul>
+      <li>Requirement for reuse in different contexts</li>
+      <li>Recommendation for explicit versioning</li>
+      <li>Recommendation for multi party development</li>
+      <li>Recommendation for license headers in files</li>
+      <li>Recommendation for vulnerability reporting</li>
+      <li>Recommendation for explicit documentation of governance</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="version-011">Version 0.1.1</h2>
+
+<p>May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a lot of typos</p>
+
+<ul>
+  <li>Removed references to the Foundation for Public Code, we’re going to have to change the name in becoming an association.</li>
+  <li>Updated the introduction.</li>
+  <li>Updated the glossary.</li>
+  <li>Added the code of conduct.</li>
+  <li>We’ve recommended using the publiccode.yml standard for easier reuse.</li>
+</ul>
+
+<h2 id="version-010">Version 0.1.0</h2>
+
+<p>April 16th 2019: 🎉 the first draft is ready, it is all brand new and has snazzy new ideas in it</p>
+
+<ul>
+  <li>14 criteria with their requirements and how to operationalize them.</li>
+  <li>An introduction with a high level background, what this standard is, and how the Foundation for Public Code will use it.</li>
+</ul>
+
+<p>This first version was produced together with the Amsterdam University of Applied Sciences and the City of Amsterdam as a part of the <a href="https://smartcities.publiccode.net/">Smart Cities? Public Code! project</a>.</p>
+
+
+  </article>
+
+  <article id="section-license">
+
+    <p>This license is the legal contract that allows anyone to do anything they like with the content in this entire document.</p>
+    <h1>CC0 1.0 Universal</h1>
+    <pre>Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
+</pre>
+
+  </article>
+
+  <article id="section-contact">
+
+    <h1>Contact</h1>
+
+    <p>For questions and more information about the Foundation for Public Code you can find us at <a href="https://publiccode.net">our website</a>, email us at info@publiccode.net, or call us at +31 20 2 444 500</p>
+
+  </article>
+
+</body>
+</html>
diff --git a/_site/publiccode.yml b/_site/publiccode.yml
new file mode 100644
index 00000000..6f784ad9
--- /dev/null
+++ b/_site/publiccode.yml
@@ -0,0 +1,74 @@
+# SPDX-License-Identifier: CC0-1.0
+# 2022 by The Foundation for Public Code <info@publiccode.net>
+# This repository adheres to the publiccode.yml standard by including this 
+# metadata file that makes public software easily discoverable.
+# More info at https://github.com/italia/publiccode.yml
+
+publiccodeYmlVersion: '0.2'
+categories:
+  - collaboration
+  - project-collaboration
+description:
+  en:
+    features:
+      - enables collabration
+      - enables successful future reuse
+      - |-
+        gives public organizations a model for building their own open source
+        solutions
+      - |-
+        gives guidance for policy makers, city administrators, developers and
+        vendors
+    genericName: standard
+    localisedName: Standard for Public Code
+    longDescription: |
+      The Standard for Public Code gives public organizations a model for
+      preparing open source solutions to enable collaborations with similar
+      public organizations in other places. It includes guidance for policy
+      makers, city administrators, developers and vendors.
+
+
+      We define ‘public code’ as open source software developed by public
+      organizations, together with the policy and guidance needed for
+      collaboration and reuse.
+
+
+      The Standard is recognized as a [Digital Public
+      Good](https://digitalpublicgoods.net/registry/standard-for-public-code.html)
+      by the [Digital Public Goods Alliance](https://digitalpublicgoods.net/).
+    shortDescription: |-
+      It gives public organizations a model for preparing open source solutions
+      to enable collaborations with similar public organizations in other
+      places.
+    videos:
+      - 'https://www.youtube.com/watch?v=QWt6vB-cipE'
+developmentStatus: beta
+landingURL: 'https://standard.publiccode.net'
+legal:
+  authorsFile: 'https://raw.githubusercontent.com/publiccodenet/standard/master/AUTHORS.md'
+  license: CC0-1.0
+  mainCopyrightOwner: Foundation for Public Code
+  repoOwner: Foundation for Public Code
+localisation:
+  availableLanguages:
+    - en
+  localisationReady: false
+maintenance:
+  contacts:
+    - affiliation: Foundation for Public Code
+      email: eric@publiccode.net
+      name: Eric Herman
+    - affiliation: Foundation for Public Code
+      email: jan@publiccode.net
+      name: Jan Ainali
+  type: internal
+name: Standard for Public Code
+platforms:
+  - web
+releaseDate: '2022-09-07'
+roadmap: 'https://github.com/publiccodenet/standard/blob/develop/docs/roadmap.md'
+softwareType: standalone/other
+softwareVersion: 0.4.0
+url: 'https://github.com/publiccodenet/standard'
+usedBy:
+  - Provincie Zuid-Holland
diff --git a/_site/readers-guide.html b/_site/readers-guide.html
new file mode 100644
index 00000000..7d9eb387
--- /dev/null
+++ b/_site/readers-guide.html
@@ -0,0 +1,353 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Readers guide, Standard for Public Code</title>
+  <meta name="description" content="The Standard for Public Code - a model for public organizations to build their own open source solutions to enable successful future reuse by and collaboration with similar public organizations in other places.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/readers-guide.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="Codebase Stewardship">Stewardship</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">Resources</a></li>
+    <li><a href="https://publiccode.net/team/">Who we are</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">Join us</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="The Foundation for Public Code on Mastodon"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="The Foundation for Public Code on Twitter"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="The Foundation for Public Code on Github"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">Contents</h3>
+      <ol class="table-of-contents">
+  <li><a href="#requirements">Requirements</a></li>
+  <li><a href="#why-this-is-important">Why this is important</a></li>
+  <li><a href="#what-this-does-not-do">What this does not do</a></li>
+  <li><a href="#how-to-test">How to test</a></li>
+  <li><a href="#policy-makers-what-you-need-to-do">Policy makers: what you need to do</a></li>
+  <li><a href="#management-what-you-need-to-do">Management: what you need to do</a></li>
+  <li><a href="#developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">Contribute on GitHub</h3>
+    <ul class="edit-links">
+      <!-- The default branch is develop, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/standard/edit/develop/readers-guide.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ Edit this page</a></li>
+      <li><a href="https://github.com/publiccodenet/standard/issues/new?body=I'd like to report an issue in `readers-guide.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ File an Issue</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="readers-guide">Readers guide</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+<p>The Standard describes a number of criteria.
+All criteria have consistent sections that make it clear how to create great public code.</p>
+
+<p>References to “policy makers”, “management”, and “developers and designers” apply to anyone performing duties associated with these roles, regardless of their job title.
+It is common for individuals to have duties which span multiple roles.</p>
+
+<p>Below is a brief explanation of each of these sections and how they are used within the criteria of the Standard.</p>
+
+<h2 id="requirements">Requirements</h2>
+
+<p>This section lists what needs to be done in order to comply with the standard.</p>
+
+<p>In order to limit ambiguity, the key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
+NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”,  “MAY”, and “OPTIONAL” in this document are to be interpreted as described in <a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a>.</p>
+
+<h2 id="why-this-is-important">Why this is important</h2>
+
+<p>This section explains why it is important for the users and contributors of this codebase that these requirements are followed.</p>
+
+<h2 id="what-this-does-not-do">What this does not do</h2>
+
+<p>This section manages expectations by explaining what following the requirements will not save you from.</p>
+
+<p>This helps:</p>
+
+<ul>
+  <li>with applying the Standard correctly</li>
+  <li>make sure no unexpected things pop up</li>
+</ul>
+
+<h2 id="how-to-test">How to test</h2>
+
+<p>This section offers actions you can take to see if a contribution is compliant with the Standard. This is key if you want to operationalize the Standard.</p>
+
+<p>We’ve tried to word it so that someone who is not intimately acquainted with the subject matter can still do a basic check for compliance.</p>
+
+<h2 id="policy-makers-what-you-need-to-do">Policy makers: what you need to do</h2>
+
+<p>This section tries to specifically speak to policy makers by offering them concrete actions they can perform in their role.</p>
+
+<p>Policy makers set the priorities and goals of projects and may be less technologically experienced.</p>
+
+<h2 id="management-what-you-need-to-do">Management: what you need to do</h2>
+
+<p>This section tries to specifically speak to management by offering concrete actions they can perform in their role.</p>
+
+<p>Management is responsible for on-time project delivery, stakeholder management and continued delivery of the service. For this they are wholly reliant on both policy makers as well as developers and designers. They need to create the right culture, line up the right resources and provide the right structures to deliver great services.</p>
+
+<h2 id="developers-and-designers-what-you-need-to-do">Developers and designers: what you need to do</h2>
+
+<p>This section tries to specifically speak to developers and designers by offering them concrete actions they can perform in their role.</p>
+
+<p>Developers are usually more technically aligned and have more impact on the delivery of services than the previous groups.</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+    <section>
+      
+
+      <h3>Version 0.6.0 (pre-release)</h3>
+      <p>Published <a href="https://github.com/publiccodenet/standard/releases/tag/0.6.0">20 April 2023 on GitHub</a></p>
+      <p>0.6.0</p>
+
+      <ul>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-cover-0.6.0.pdf" download><code>standard-cover-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.epub" download><code>standard-for-public-code-0.6.0.epub</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-for-public-code-0.6.0.pdf" download><code>standard-for-public-code-0.6.0.pdf</code></a>
+          </li>
+        
+          <li>
+            <a href="https://github.com/publiccodenet/standard/releases/download/0.6.0/standard-review-template-0.6.0.pdf" download><code>standard-review-template-0.6.0.pdf</code></a>
+          </li>
+        
+        <li>
+            <a href="https://github.com/publiccodenet/standard/releases">All releases</a>
+        </li>
+        <li>
+          Source archive in 
+          <a href="https://api.github.com/repos/publiccodenet/standard/zipball/0.6.0" download><code>.zip</code></a>
+          or
+          <a href="https://api.github.com/repos/publiccodenet/standard/tarball/0.6.0" download><code>.tar.gz</code></a>
+        </li>
+      </ul>
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2021 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html"><img src="/assets/dpg-badge.svg" width="92" height="46" alt="Digital Public Goods approval" /></a></p>
+
+      
+      
+      <!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2022 by The Foundation for Public Code <info@publiccode.net> -->
+<p><a href="https://publiccodenet.github.io/community-translations-standard/">Translations</a> of the Standard for Public Code</p>
+
+      
+    </section>
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>This site on GitHub</h3>
+      <p>This site was last published 05 May 2023 from the <a href="https://github.com/publiccodenet/standard">publiccodenet/standard</a> repository on GitHub.</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/standard/search" method="GET">
+        <input name="q" type="text" placeholder="Search source on GitHub">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> Search</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>Copyright and license</h3>
+      <p>
+        © 2023 
+        
+        
+        <a href="/AUTHORS.html">
+           The Authors
+        </a>
+      </p>
+      <p>
+        
+        
+        Creative Commons Zero v1.0 Universal
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Homepage of the Foundation for Public Code" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="The mark of the Foundation for Public Code looks like a little greek temple, or government building, in a hexagon">
+    <p>Foundation for Public Code</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>About us</h2>
+        <p>All of our staff information, decision-making rules and processes. Our staff manual is developed collaboratively with the community and can be reused by everyone.</p>
+        <p>Read more about our activities, organization, and the glossary of terms and concepts.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">How we work</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Project resources</h2>
+        <p>Open products we're researching or developing to further our mission. We rely on these resources for our everyday work. You can, too!</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">Free to use and modify</a>
+        <a href="https://github.com/publiccodenet">See all our work on Github</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>Careers</h2>
+        <p>Calling all publicly minded open source people! Find out about working with us, and join our staff.</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">Open positions</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>Contact</h2>
+      <dl>
+          <dt>Newsletter:</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">Join our mailing list</a></dd>
+
+          <dt>Phone:</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>Email:</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>Address:</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google Maps">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>Organizational notes</h2>
+      <p>Foundation for Public Code vereniging (met volledige rechtsbevoegdheid) <a href="https://about.publiccode.net/organization/governance-model.html" title="Governance model">is a member owned association</a> registered under <a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="KVK registration">chamber of commerce (KvK) registration 74996452</a> and with identification number (RSIN) 860102294.</p>
+      <p>We're recognized as a <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="public benefit organization (ANBI)">public benefit organization (ANBI)</a> by the Dutch Tax and Customs Administration. See <a href="https://about.publiccode.net/organization/" title="our ANBI information">our ANBI information</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">Last updated 05 May 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">All content licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero v1.0 Universal" rel="license">Creative Commons Zero v1.0 Universal</a>, unless otherwise noted</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/readers-guide.md b/_site/readers-guide.md
new file mode 100644
index 00000000..8a35b0c0
--- /dev/null
+++ b/_site/readers-guide.md
@@ -0,0 +1,56 @@
+# Readers guide
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- written in 2019 - 2022 by The Foundation for Public Code <info@publiccode.net> -->
+
+The Standard describes a number of criteria.
+All criteria have consistent sections that make it clear how to create great public code.
+
+References to "policy makers", "management", and "developers and designers" apply to anyone performing duties associated with these roles, regardless of their job title.
+It is common for individuals to have duties which span multiple roles.
+
+Below is a brief explanation of each of these sections and how they are used within the criteria of the Standard.
+
+## Requirements
+
+This section lists what needs to be done in order to comply with the standard.
+
+In order to limit ambiguity, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
+NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119).
+
+## Why this is important
+
+This section explains why it is important for the users and contributors of this codebase that these requirements are followed.
+
+## What this does not do
+
+This section manages expectations by explaining what following the requirements will not save you from.
+
+This helps:
+
+* with applying the Standard correctly
+* make sure no unexpected things pop up
+
+## How to test
+
+This section offers actions you can take to see if a contribution is compliant with the Standard. This is key if you want to operationalize the Standard.
+
+We've tried to word it so that someone who is not intimately acquainted with the subject matter can still do a basic check for compliance.
+
+## Policy makers: what you need to do
+
+This section tries to specifically speak to policy makers by offering them concrete actions they can perform in their role.
+
+Policy makers set the priorities and goals of projects and may be less technologically experienced.
+
+## Management: what you need to do
+
+This section tries to specifically speak to management by offering concrete actions they can perform in their role.
+
+Management is responsible for on-time project delivery, stakeholder management and continued delivery of the service. For this they are wholly reliant on both policy makers as well as developers and designers. They need to create the right culture, line up the right resources and provide the right structures to deliver great services.
+
+## Developers and designers: what you need to do
+
+This section tries to specifically speak to developers and designers by offering them concrete actions they can perform in their role.
+
+Developers are usually more technically aligned and have more impact on the delivery of services than the previous groups.
diff --git a/_site/redirects.json b/_site/redirects.json
new file mode 100644
index 00000000..efabfc13
--- /dev/null
+++ b/_site/redirects.json
@@ -0,0 +1 @@
+{"/criteria/advertise-maturity":"/criteria/document-maturity.html"}
\ No newline at end of file
diff --git a/_site/script/check-new-links.sh b/_site/script/check-new-links.sh
new file mode 100755
index 00000000..1e924e98
--- /dev/null
+++ b/_site/script/check-new-links.sh
@@ -0,0 +1,61 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# 2021-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that new links are valid. This script is intended to aid in that process.
+# Rather than checking all links with an incoming contribution, only the links
+# added by that contribution should be checked.
+
+NOT_OK_COUNT=0
+SKIP_PATTERNS=(
+	'github\.com/.*/edit' # links may not exist yet
+	'twitter\.com' # twitter is broken
+	'http://127.0.0.1' # local host
+	'http://localhost' # local host
+)
+
+if [ "_${VERBOSE}_" == "__" ]; then VERBOSE=0; fi
+
+for URL in $(git diff develop |
+		grep '^+' |
+		grep -Eo '(http|https)://[^ )"><]+'); do
+	SKIP_URL=0
+	for PATTERN in "${SKIP_PATTERNS[@]}"; do
+		if echo "$URL" | grep --quiet --extended-regexp "$PATTERN"
+		then
+			if [ $VERBOSE -gt 0 ]; then
+				echo "'$URL' matches '$PATTERN'"
+			fi
+			SKIP_URL=1
+		fi
+	done
+	if [ $SKIP_URL -eq 1 ]
+	then
+		if [ $VERBOSE -gt 0 ]; then
+			echo "(ignoring '$URL')"
+		fi
+	elif curl --fail --show-error --silent --head --location $URL \
+		> url_head 2>&1
+	then
+		if [ $VERBOSE -gt 0 ]
+		then
+			echo "$URL"
+			head -n1 url_head
+		fi
+	else
+		let "NOT_OK_COUNT+=1"
+		echo $URL
+		head -n1 url_head
+	fi
+	rm -f url_head
+done
+
+if [ $NOT_OK_COUNT -gt 0 ]; then
+	echo "FAIL: $NOT_OK_COUNT new URLs were not OK"
+	EXIT_FAILURE=1
+	exit $EXIT_FAILURE
+fi
diff --git a/_site/script/find-missing-spdx.sh b/_site/script/find-missing-spdx.sh
new file mode 100755
index 00000000..0bc7459a
--- /dev/null
+++ b/_site/script/find-missing-spdx.sh
@@ -0,0 +1,26 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# 2022 by The Foundation for Public Code <info@publiccode.net>
+
+function git_list_files() {
+		# -r Recurse into sub-trees.
+	git ls-tree \
+		--full-tree \
+		-r \
+		--name-only \
+		HEAD
+}
+
+IGNORE_PATTERN='\.svg\|\.json\|CNAME\|Gemfile\|LICENSE'
+
+MISSING=0
+for FILE in $(git_list_files | grep --invert-match $IGNORE_PATTERN); do
+	if ! grep --quiet SPDX-License-Identifier $FILE; then
+		MISSING=$(( 1 + $MISSING ))
+		echo $FILE
+	fi
+done
+
+if [ $MISSING -ne 0 ]; then
+	exit 1
+fi
diff --git a/_site/script/generate-review-template.sh b/_site/script/generate-review-template.sh
new file mode 100755
index 00000000..6c9b1466
--- /dev/null
+++ b/_site/script/generate-review-template.sh
@@ -0,0 +1,53 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# Written 2022 by The Foundation for Public Code <info@publiccode.net>
+
+TEMPLATE=docs/review-template.md
+THIS_YEAR=$(date +%Y)
+STANDARD_VERSION=$(grep version: _config.yml | cut -f2 -d':' | xargs)
+cat << EOF > $TEMPLATE
+# &#95;&#95;&#95;&#95;&#95;&#95;&#95;&#95; and the Standard for Public Code version $STANDARD_VERSION
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- generated $THIS_YEAR by The Foundation for Public Code <info@publiccode.net> -->
+
+Link to commitment to meet the Standard for Public Code:
+EOF
+
+# the index.md contains the criteria in order, we shall follow that.
+# grep and cuts extract the filename from between the link parenthesis
+CRITERIA_FILES=$(cat index.md \
+	| grep 'criteria/[a-z\-]\+\.md' \
+	| cut --fields=2 --delimiter='(' \
+	| cut --fields=1 --delimiter=')')
+
+for FILE in $CRITERIA_FILES; do
+	# echo $FILE
+	FILE_BASE=$(basename --suffix=.md $FILE)
+	# Strip the '#' off of the H1
+	CRITERIA_TITLE=$(grep '^# [A-Z]' $FILE \
+		| cut --fields=2- --delimiter=' ')
+	CRITERIA_LINK=https://standard.publiccode.net/criteria/${FILE_BASE}.html
+	cat << EOF >> $TEMPLATE
+
+## [$CRITERIA_TITLE]($CRITERIA_LINK)
+
+&#9744; criterion met.
+
+Requirement | meets | &nbsp;links&nbsp;and&nbsp;notes&nbsp;
+-----|-----|-----
+EOF
+	# awk will process each line of file
+	# set 'p' to 1 if we are in the "## Requirements" section, or skip line
+	# set 's' to be all the words except the leading "*" of requirement
+	# if not a blank line, print 's' and the column pipe delimiters
+	awk 'BEGIN {p=0}; /## Requirements/ {p=1 ; next}; /##/ {p=0 ; next}; \
+		p { s = ""; for (i = 2; i <= NF; i++) s = s $i " "; \
+		if (length(s) > 0) print s "|  |"}' $FILE >> $TEMPLATE
+done
+
+# fully qualify local links in requirement lines
+# by looking for links lacking a colon
+sed -i -e's@\[\([^]]*\)\](\([^:)]*\).md)@[\1](https://standard.publiccode.net/criteria/\2.html)@g' $TEMPLATE
+
+ls -l $TEMPLATE
diff --git a/_site/script/missing-glossary-links.sh b/_site/script/missing-glossary-links.sh
new file mode 100755
index 00000000..642b2340
--- /dev/null
+++ b/_site/script/missing-glossary-links.sh
@@ -0,0 +1,95 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# 2022 Foundation for Public Code <info@publiccode.net>
+
+# This script extracts the glossary terms from glossary.md
+# for each file in the criteria directory, it looks for the use of a term
+# if the term is found, it checks to see if a link exists
+# if no link is found, it prints the TODO list
+
+if [ "_${VERBOSE}_" == "__" ]; then
+	VERBOSE=0
+fi
+
+if [ $VERBOSE -gt 1 ]; then
+	set -x
+fi
+
+MISSING=0;
+
+# grep for heading in glossary
+# strip the hashes off
+# strip off the leading space
+# convert space to hyphen
+# transform upper case to lower case
+GLOSSARY_ANCHORS=$( grep '## ' glossary.md \
+	| cut -f3- -d"#" \
+	| sed -e 's/^ //g' \
+	| sed -e 's/ /-/g' \
+	| tr A-Z a-z )
+
+function glossary_pass_list() {
+	GLOSSARY_ANCHOR=$1
+	FILE=$2
+
+	# "version control" correctly links to the criterion
+	# rather than the glossary entry
+	if [ "$GLOSSARY_ANCHOR" == "version-control" ] &&
+	   [ "$FILE" == "criteria/bundle-policy-and-code.md" ]; then
+		return 0
+	fi
+	if [ "$GLOSSARY_ANCHOR" == "version-control" ] &&
+	   [ "$FILE" == "criteria/continuous-integration.md" ]; then
+		return 0
+	fi
+
+	# "Open Source Initiative" would be a false positive
+	if [ "$GLOSSARY_ANCHOR" == "open-source" ] &&
+	   [ "$FILE" == "criteria/open-standards.md" ]; then
+		return 0
+	fi
+
+	# repository inside of a link would be a false positive
+	if [ "$GLOSSARY_ANCHOR" == "repository" ] &&
+	   [ "$FILE" == "criteria/require-review.md" ]; then
+		return 0
+	fi
+
+	return 1
+}
+
+for GLOSSARY_ANCHOR in $GLOSSARY_ANCHORS; do
+	GLOSSARY_TERM=$(echo $GLOSSARY_ANCHOR | sed -e 's/-/ /g')
+
+	if [ $VERBOSE -gt 0 ]; then
+		echo GLOSSARY_ANCHOR: $GLOSSARY_ANCHOR
+		echo GLOSSARY_TERM:   $GLOSSARY_TERM
+	fi
+	if [ "_${GLOSSARY_TERM}_" == "_public code_" ]; then
+		GLOSSARY_TERM='Public code\|public code'
+		GREP="grep -lr"
+	else
+		GLOSSARY_TERM="$GLOSSARY_TERM"
+		#case insensitive
+		GREP="grep -ilr"
+	fi
+	for FILE in $( $GREP "$GLOSSARY_TERM" criteria/ | grep -v index); do
+		if glossary_pass_list "$GLOSSARY_ANCHOR" "$FILE"; then
+			continue
+		fi
+
+		if grep -q "glossary.md\#$GLOSSARY_ANCHOR" $FILE; then
+			if [ $VERBOSE -gt 0 ]; then
+				echo Found link $GLOSSARY_ANCHOR $FILE
+			fi
+		else
+			MISSING=$(( $MISSING + 1 ))
+			echo to-do: $GLOSSARY_ANCHOR $FILE
+		fi
+	done
+done
+
+if [ $MISSING -gt 0 ]; then
+	echo Missing $MISSING links
+	exit 1
+fi
diff --git a/_site/script/pdf.sh b/_site/script/pdf.sh
new file mode 100755
index 00000000..97866815
--- /dev/null
+++ b/_site/script/pdf.sh
@@ -0,0 +1,14 @@
+#!/bin/sh
+# SPDX-License-Identifier: CC0-1.0
+# 2021-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is used to generate a PDF from the html generated by Jekyll.
+
+# The 'serve.sh' script should be called prior to this script in order to
+# create and serve html content on localhost:4000
+
+# This script is used during the release process (see ../docs/releasing.md)
+
+weasyprint http://localhost:4000/print.html standard.pdf --presentational-hints
+weasyprint http://localhost:4000/print-cover.html standard-cover.pdf --presentational-hints
+weasyprint http://localhost:4000/print-review-template.html review-template.pdf --presentational-hints
diff --git a/_site/script/serve.sh b/_site/script/serve.sh
new file mode 100755
index 00000000..e2b0b9fc
--- /dev/null
+++ b/_site/script/serve.sh
@@ -0,0 +1,16 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# 2019-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# The serve.sh script can be used to preview how Jekyll will build the site.
+# See also: pdf.sh
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+#bundle exec jekyll serve --livereload --host 127.0.0.1 --port 6015
+bundle exec jekyll serve --host https://lyzez5.toomore.net --port 6015
diff --git a/_site/script/test-all.sh b/_site/script/test-all.sh
new file mode 100755
index 00000000..4d242091
--- /dev/null
+++ b/_site/script/test-all.sh
@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# 2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is provided for local development,
+# it is not used by continuous integration
+
+# $ help set
+#      -e  Exit immediately if a command exits with a non-zero status.
+#      -x  Print commands and their arguments as they are executed.
+set -x
+set -e
+
+./script/find-missing-spdx.sh
+./script/test-markdown.sh
+./script/test-without-link-check.sh
+./script/missing-glossary-links.sh
+./script/check-new-links.sh
+./script/test-with-link-check.sh
diff --git a/_site/script/test-markdown.sh b/_site/script/test-markdown.sh
new file mode 100755
index 00000000..ea61b402
--- /dev/null
+++ b/_site/script/test-markdown.sh
@@ -0,0 +1,17 @@
+#!/bin/sh
+# SPDX-License-Identifier: CC0-1.0
+# 2021-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that new Markdown is valid and conforms to the repository guidelines. This
+# script is intended to aid in that process.
+
+# Lint markdown using the Markdownlint gem with the default ruleset except for:
+# MD007 Unordered list indentation: we allow sub-lists to also have bullets
+# MD013 Line length: we allow long lines
+# MD029 Ordered list item prefix: we allow lists to be sequentially numbered
+#
+bundle exec mdl -r ~MD007,~MD013,~MD029 -i -g '.'
diff --git a/_site/script/test-with-link-check.sh b/_site/script/test-with-link-check.sh
new file mode 100755
index 00000000..58426a71
--- /dev/null
+++ b/_site/script/test-with-link-check.sh
@@ -0,0 +1,55 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# 2021-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is referenced by .github/workflows/link-check.yml which
+# executes daily.
+
+# Failures reported by this script are addressed on a case-by-case basis.
+
+set -e # halt script on error
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+# Build the site
+bundle exec jekyll build
+
+# bundle exec htmlproofer --help | grep url-ignore
+#  --url-ignore link1,[link2,...]  A comma-separated list of
+#    Strings or RegExps containing URLs that are safe to ignore.
+# * github.com/foo/edit/ : may reference yet-to-exist pages
+# * docs.github.com/en : blocked by github DDoS protection
+# * plausible.io/js/plausible.js : does not serve to scripts
+# * opensource.org : gives "failed: 503 No error" when run as GitHub workflow
+# * reclameland.nl : often "failed: 403 No error" when run as GitHub workflow
+# * www.dta.gov.au : often "failed: 403 No error" when run as GitHub workflow
+# * 127.0.0.1 : localhost does not need to be checked
+#
+URL_IGNORE_REGEXES="\
+/github\.com\/.*\/edit\//\
+,/docs\.github\.com\/en\//\
+,/plausible\.io\/js\/plausible\.js/\
+,/opensource\.org/\
+,/reclameland\.nl\/drukken\/softcover-boeken/\
+,/www\.dta\.gov\.au\/help-and-advice/\
+,/127\.0\.0\.1:/\
+"
+
+# ignore request rate limit errors (HTTP 429)
+# --http_status_ignore "429" \
+
+# Check for broken links and missing alt tags:
+# jekyll does not require extensions like HTML
+# ignoring problem urls (see above)
+# set an extra long timout for test-servers with poor connectivity
+# using the files in Jekylls build folder
+bundle exec htmlproofer \
+    --assume-extension \
+    --url-ignore $URL_IGNORE_REGEXES \
+    --typhoeus-config '{"timeout":60,"ssl_verifypeer":false,"ssl_verifyhost":"0"}' \
+    ./_site
diff --git a/_site/script/test-without-link-check.sh b/_site/script/test-without-link-check.sh
new file mode 100755
index 00000000..53279b60
--- /dev/null
+++ b/_site/script/test-without-link-check.sh
@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# 2021-2022 by The Foundation for Public Code <info@publiccode.net>
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that html is valid and conforms to the repository guidelines. This script is
+# intended to aid in that process.
+
+set -e # halt script on error
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+# Build the site
+bundle exec jekyll build
+
+# Check for broken links and missing alt tags:
+# jekyll does not require extentions like HTML
+# run only "ScriptCheck" and "ImageCheck"; skip "LinkCheck"
+# set an extra long timout for test-servers with poor connectivity
+# ignore request rate limit errors (HTTP 429)
+# using the files in Jekylls build folder
+bundle exec htmlproofer \
+    --assume-extension \
+    --disable-external \
+    ./_site
diff --git a/_site/script/to-archive-org.sh b/_site/script/to-archive-org.sh
new file mode 100755
index 00000000..63f8f9bf
--- /dev/null
+++ b/_site/script/to-archive-org.sh
@@ -0,0 +1,82 @@
+#!/bin/bash
+# SPDX-License-Identifier: LGPL-2.1-or-later
+# to-archive-org.sh : send referenced URLs to the wayback machine
+# Copyright (C) 2020 Eric Herman <eric@freesa.org>
+
+# TODO FIXXXME: use something better than bash
+
+if [ "_${ARCHIVER_LOG_FILE}_" == "__" ]; then
+	NOW=$(date --utc +%Y%m%dT%H%M%SZ)
+	ARCHIVER_LOG_FILE=/tmp/to-archive-org.sh.${NOW}.log
+fi
+echo "ARCHIVER_LOG_FILE=$ARCHIVER_LOG_FILE"
+
+if [ "_${ARCHIVER_USER_AGENT}_" == "__" ]; then
+	GIT_USER_NAME=$(git config --get user.name)
+	GIT_USER_EMAIL=$(git config --get user.email)
+	RUN_BY="$GIT_USER_NAME ( $GIT_USER_EMAIL )"
+	REMOTE=$(git remote -v | head -n1 | cut -f1 -d$'\t')
+	REPO_URL=$(git config --get remote.${REMOTE}.url)
+	ARCHIVER_USER_AGENT="'url-archiver run by $RUN_BY for $REPO_URL'"
+fi
+echo "ARCHIVER_USER_AGENT=$ARCHIVER_USER_AGENT"
+
+rm -f urls.txt
+
+# find . -type f -name '*.md' -print0 |
+# while IFS= read -r -d '' FILE; do
+
+BRANCH_NAME=$(git branch | grep \* | cut -d ' ' -f2)
+for FILE in $(git ls-tree -r --name-only $BRANCH_NAME); do
+	# URLs inside parens
+	grep '(http[s]\?:' "$FILE" \
+		| sed -e's/.*[(]\(http[s]*:[^)]*\).*/\1/' \
+		>> urls.txt
+	# URLs inside angle brackets
+	grep '<http[s]\?:' "$FILE" \
+		| sed -e's/.*<\(http[s]*:[^>]*\).*/\1/' \
+		>> urls.txt
+	# URLs inside double-quotes
+	grep '"http[s]\?:' "$FILE" \
+		| sed -e's/.*"\(http[s]*:[^"]*\).*/\1/' \
+		>> urls.txt
+done
+
+# create a list of unique URLs, excluding archive.org
+cat urls.txt \
+	| cut -f1 -d'#' \
+	| grep -v '^https://web.archive.org' \
+	| sort -u \
+	> urls-sorted.txt
+
+URLS_TOTAL=$(wc -l urls-sorted.txt | cut -f1 -d' ')
+
+# cat urls-sorted.txt
+
+MAX_PER_MINUTE=5
+echo "sending $URLS_TOTAL URLs to the wayback machine,"
+echo "        throttled to $MAX_PER_MINUTE per minute..."
+PAUSE_TIME=$(( 1 + (60 / $MAX_PER_MINUTE) ))
+URLS_COUNT=0
+for URL in $(cat urls-sorted.txt); do
+	echo sleeping for $PAUSE_TIME ....
+	sleep $PAUSE_TIME
+	# $ sudo apt-get install gridsite-clients
+	ENCODED=`urlencode $URL`
+	echo ""
+	URLS_COUNT=$(( $URLS_COUNT + 1 ))
+	echo "$URLS_COUNT of $URLS_TOTAL"
+	echo URL: $URL
+	echo encoded: $ENCODED
+
+	echo "" >> $ARCHIVER_LOG_FILE
+	echo "----------" >> $ARCHIVER_LOG_FILE
+	echo $URL >> $ARCHIVER_LOG_FILE
+	ARC_ORG_URL=https://web.archive.org/save/$ENCODED
+	echo $ARC_ORG_URL >> $ARCHIVER_LOG_FILE
+	curl --user-agent "$ARCHIVER_USER_AGENT" \
+		$ARC_ORG_URL >> $ARCHIVER_LOG_FILE
+	echo "" >> $ARCHIVER_LOG_FILE
+	echo "----------" >> $ARCHIVER_LOG_FILE
+done
+echo "done"

From 6d557ca360c6c6a39d38bf2b05696285c937285d Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Tue, 18 Jul 2023 09:59:35 +0800
Subject: [PATCH 33/71] add steps's Dockerfile

---
 Dockerfile | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
 docker.sh  |  6 ++++++
 2 files changed, 56 insertions(+)
 create mode 100644 Dockerfile
 create mode 100644 docker.sh

diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 00000000..e4552ba3
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,50 @@
+# OS: Ubuntu 22.04
+
+FROM ubuntu:22.04
+
+WORKDIR /var/www/html
+
+ENV TZ="Asia/Taipei"
+
+ENV GIT_COMPLETION_URL="https://raw.githubusercontent.com/git/git/master/contrib/completion/git-completion.bash"
+
+RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone
+
+RUN apt-get update && apt-get upgrade -y \
+    && apt-get install -y software-properties-common ca-certificates lsb-release apt-transport-https \
+    && apt-get install -y zip unzip curl vim wget cron
+
+RUN add-apt-repository ppa:ondrej/php \
+    && apt-get update
+
+RUN apt-get install -y apache2 apache2-utils
+
+RUN apt-get install -y git curl autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm6 libgdbm-dev libdb-dev
+
+RUN curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash
+RUN echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
+RUN echo 'eval "$(rbenv init -)"' >> ~/.bashrc
+
+RUN ~/.rbenv/bin/rbenv init -
+RUN ~/.rbenv/bin/rbenv install 3.1.3
+RUN ~/.rbenv/bin/rbenv global 3.1.3
+
+RUN ~/.rbenv/shims/gem install bundler jekyll
+
+# 中文語系顯示
+RUN apt-get install -y locales language-pack-zh-hans
+RUN locale-gen zh_TW.UTF-8
+
+RUN apt-get -y autoremove \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
+RUN a2enmod rewrite && a2enmod proxy && a2enmod proxy_http
+
+# 中文語系顯示
+RUN echo "export LANG=zh_TW.UTF-8" >> /root/.bashrc
+RUN echo "export LC_ALL=zh_TW.UTF-8" >> /root/.bashrc
+RUN echo 'PS1="\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\u@\h:\W\$ "' >> /root/.bashrc
+
+CMD ["apache2ctl", "-D", "FOREGROUND"]
+EXPOSE 80
+
diff --git a/docker.sh b/docker.sh
new file mode 100644
index 00000000..08acd8f3
--- /dev/null
+++ b/docker.sh
@@ -0,0 +1,6 @@
+#!/bin/bash
+docker run -d \
+    -v ./:/var/www/html \
+    -p 8090:80 \
+    --name=standard \
+    steps/standard

From f1576f2df66f2cf8c932792cbc85ddd4522e6863 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Tue, 18 Jul 2023 11:58:05 +0800
Subject: [PATCH 34/71] add locales: en, zh_Hant

---
 locales/en/LC_MESSAGES/messages.po      | 5583 +++++++++++++++++++++++
 locales/zh_Hant/LC_MESSAGES/messages.po | 5583 +++++++++++++++++++++++
 2 files changed, 11166 insertions(+)
 create mode 100644 locales/en/LC_MESSAGES/messages.po
 create mode 100644 locales/zh_Hant/LC_MESSAGES/messages.po

diff --git a/locales/en/LC_MESSAGES/messages.po b/locales/en/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..46615c34
--- /dev/null
+++ b/locales/en/LC_MESSAGES/messages.po
@@ -0,0 +1,5583 @@
+#
+msgid ""
+msgstr ""
+
+#: ./404.md:block 1 (header)
+msgid "SPDX-License-Identifier: CC0-1.0"
+msgstr ""
+
+#: ./404.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./404.md:block 3 (header)
+msgid ""
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
+msgstr ""
+
+#: ./404.md:block 4 (header)
+msgid "404 Not Found"
+msgstr ""
+
+#: ./404.md:block 5 (paragraph)
+msgid "If you typed the web address, check it is correct."
+msgstr ""
+
+#: ./404.md:block 6 (paragraph)
+msgid "If you pasted the web address, check you copied the entire address."
+msgstr ""
+
+#: ./404.md:block 7 (paragraph)
+msgid ""
+"If the web address is correct or you followed a link or button, email the "
+"[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
+"able to help you out, as well as correct our mistake."
+msgstr ""
+
+#: ./AUTHORS.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./AUTHORS.md:block 3 (header)
+msgid "Authors"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Engelen"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Schuijff, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ben Cerveny, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Bert Spaan"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Boris van Hoytema, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Charlotte Heikendorf"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Claus Mullie, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "David Barberi"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Edo Plantinga, [Code For NL](https://codefor.nl/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Elena Findley-de Regt, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Eric Herman, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Felix Faassen, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Floris Deerenberg"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Jan Ainali, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Johan Groenen, Code For NL"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Marcus Klaas de Vries"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Martijn de Waal, [Amsterdam University of Applied Sciences "
+"(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
+"Creative Industries, Lectorate of Play & Civic Media"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Matti Schneider"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mauko Quiroga"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurice Hendriks, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurits van der Schee, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mirjam van Tiel, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ngô Ngọc Đức Huy"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Paul Keller"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
+"(NIIS)](https://niis.org)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Sky Bristol"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Tamas Erkelens, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Timo Slinger"
+msgstr ""
+
+#: ./CC0-1.0.md:block 3 (header)
+msgid "toc: false redirect_from: - license.html - LICENSE.html"
+msgstr ""
+
+#: ./CC0-1.0.md:block 4 (header)
+msgid "Creative Commons Zero v1.0 Universal"
+msgstr ""
+
+#: ./CC0-1.0.md:block 6 (paragraph)
+msgid ""
+"This license is the legal contract that allows anyone to do anything they "
+"like with the content in this entire document."
+msgstr ""
+
+#: ./CHANGELOG.md:block 3 (header)
+msgid "Version history"
+msgstr ""
+
+#: ./CHANGELOG.md:block 5 (header)
+msgid "Version 0.7.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 6 (paragraph)
+msgid ""
+"May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
+"review funding and clarifies review process requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Add requirement to document who is expected to cover the cost of reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Add requirement to have a short description of the codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Change the focus of contributions adhering to standards to focus on the "
+"review of contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Review template now in HTML format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Introduction converted to foreword."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved contributing guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved documentation of scripts."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (header)
+msgid "Version 0.6.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 9 (paragraph)
+msgid ""
+"April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
+"portability and tests and an introduction to each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about the development "
+"being a collaboration between multiple parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about being dependent "
+"on a single vendor."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Use continuous integration about publishing results for "
+"automated tests."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Differentiating the two requirements about security to clearly be about "
+"providing a method and having documentation about it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Rephrased requirements to focus on the codebase rather than contributor "
+"behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Removed the sections Why this is important and What this does not do and "
+"replaced with an introduction in each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added general What this does not do section in the introduction of the "
+"Standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for public policy makers about related policies and license "
+"compatibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for developers and designers about version controlling files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Clarified guidance for developers and designers about prompt responses and "
+"search engine optimization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added Further reading about accessibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Aligned criteria URLs with criteria names."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Improved navigation in the web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved tools in Further reading sections to the community implementation "
+"guide."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved compliance or certification process to "
+"[publiccode.net](https://publiccode.net)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Change format of the review template to make it easier to update after a new"
+" release."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Improved the text on the landing page and added links to related resources."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added spell checker automated test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Made minor changes to text for clarity and consistency."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Moved SPDX headers to yaml header."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (header)
+msgid "Version 0.5.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 12 (paragraph)
+msgid ""
+"January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
+"guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust the coding style requirement to focus on the codebase using a style "
+"guide rather than contributor behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement for codebase names to Make the codebase findable from Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement about testing the code by using examples to Use continuous"
+" integration from Document the code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Split requirement about machine testable standards to clarify that open is "
+"more important than testable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust how to test findability requirements to be less reliant on search "
+"engine algorithms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (header)
+msgid "Version 0.4.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 15 (paragraph)
+msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity focuses on whether or not versions of the codebase are "
+"ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity no longer requires specific labels for codebases that are "
+"not ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Audit flow image now generated from an easier to translate format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Improved guidance on How to test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add publiccode.yml file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add review template."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Consistently link glossary terms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add practices and standards to follow in CONTRIBUTING."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add Matti Schneider to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add remaining SPDX headers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Made additional minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Some hyperlinks updated."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Moved examples to the [Community implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (header)
+msgid "Version 0.4.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 18 (paragraph)
+msgid ""
+"September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduce new criterion: Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Improve How to test section for most criteria."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"New requirement in Welcome contributors about publishing activity "
+"statistics."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Removed redundant requirement about portable and reusable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expand open license definition to include both OSI and FSF approved "
+"licenses."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expressed intent that the Standard for Public Code should meet its own "
+"requirements where applicable and added assessment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add SPDX license identifiers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduced new Code of Conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify distinction between source code and policy text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Restructuring of requirements with bullet point lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Acknowledge the importance of codebase modularity for reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Move requirements related to Findability to the new criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify the role of non-open standards when used in a codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Additional guidance about build-time and runtime dependencies."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added roadmap for the development of the Standard for Public Code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Update structure of Authors file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add Audrey Tang to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added a list of criteria to the print edition."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Clarify what the standard means with policymakers, managers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (header)
+msgid "Version 0.3.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 21 (paragraph)
+msgid ""
+"May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Requirement for localization made explicit in Create reusable and portable "
+"code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Documentation of governance changed from a SHOULD to a MUST."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Replace the very subjective (and hard to test) \"contributions MUST be "
+"small\" with requirement to document expectation in contributing guidelines "
+"and focus on a single issue."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Community translations now linked in the footer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Many minor clarifications to language and sentences made more simple."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (header)
+msgid "Version 0.2.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 24 (paragraph)
+msgid ""
+"March 15th 2022: 📜 the ninth draft allows English summaries for policy "
+"lacking an official translation."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Relax the criterion Use plain English by adding a new requirement allows "
+"bundled policy not available in English to have an accompanying summary in "
+"English instead of translating the full text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Similarly, allow for English summaries for policies not available in English"
+" in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Clarify that term 'policy' includes processes which impact development and "
+"deployment in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Emphasize reusability also on parts of the solutions in Create reusable and "
+"portable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Expand guidance to Developers and designers in Create reusable and portable "
+"code about deploying to proprietary platforms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Add nuance to use of non-English terms in what management need to do in Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Change the pull request process diagram to use Mermaid instead of BPMN to "
+"make [community translations](https://github.com/publiccodenet/community-"
+"translations-standard) easier."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added Maurice Hendriks to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added OpenApi Specification to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Made the attributions in further reading sections clearer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (header)
+msgid "Version 0.2.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 27 (paragraph)
+msgid ""
+"November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
+" as code may not be in English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Document exception to \"All code MUST be in English\" where policy is "
+"interpreted as code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Add MAY requirement regarding committer email addresses in Maintain version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Policy Makers in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Developers and designers in Use a coherent style."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add \"Different contexts\" to glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Digital Public Goods approval badge."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Open Standards principles to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Definition of plain language to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Move the Semantic Versioning Specification further reading reference."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Clarify that publiccode.yml is one example of a machine-readable metadata "
+"description."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add instructions for creating a print version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (header)
+msgid "Version 0.2.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 30 (paragraph)
+msgid ""
+"March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
+"0.2.0."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"New SHOULD requirement on using a distributed version control system and why"
+" distributed is important."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Feedback requirements for rejected contributions are more strict than "
+"accepted ones."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Specify that copyright and license notices should also be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Advice on how to test that notices be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clarify guidance for rolling releases."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clear up definition of version control in glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Add further reading encouraging contribution, SPDX, Git and reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add links to videos about the concept of public code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Update BPMN link."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Reduce link duplication."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (header)
+msgid "Version 0.2.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 33 (paragraph)
+msgid ""
+"October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
+"and \"Welcome contributors\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Rename criterion \"Pay attention to codebase maturity\" to \"Document "
+"codebase maturity\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Changed MUST to SHOULD for requirement of codebase in use by multiple "
+"parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add MUST NOT requirement regarding copyright assignment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Clarify role of configuration in reusable code requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Glossary additions: continuous integration, policy, repository, and version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Replace references to 'cities' with 'public organizations'."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Clarify aspects of sensitive code by separating contributor and reviewer "
+"requirements into separate items."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Expand further reading, and guidance to policy makers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add Felix Faassen and Arnout Engelen to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (header)
+msgid "Version 0.1.4"
+msgstr ""
+
+#: ./CHANGELOG.md:block 36 (paragraph)
+msgid ""
+"November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
+"fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Linked License.md file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made punctuation more consistent, especially for bullet lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made some minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (header)
+msgid "Version 0.1.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 39 (paragraph)
+msgid ""
+"October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
+" the autumn cleaning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Renamed continuous delivery to continuous integration."
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Referencing accessibility guidelines in the language standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "A bunch of style and consistency fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (header)
+msgid "Version 0.1.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 42 (paragraph)
+msgid ""
+"August 22th 2019: 🌠 the third draft focuses on better text and takes "
+"community input"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "With some great new contributors comes a fresh author list."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "All links are now HTTPS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "General proofreading, wording clarifications, and smashed typos."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Updated criteria:"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Requirement for reuse in different contexts"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit versioning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for multi party development"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for license headers in files"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for vulnerability reporting"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit documentation of governance"
+msgstr ""
+
+#: ./CHANGELOG.md:block 44 (header)
+msgid "Version 0.1.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 45 (paragraph)
+msgid ""
+"May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
+"lot of typos"
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid ""
+"Removed references to the Foundation for Public Code, we're going to have to"
+" change the name in becoming an association."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the introduction."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Added the code of conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "We've recommended using the publiccode.yml standard for easier reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (header)
+msgid "Version 0.1.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 48 (paragraph)
+msgid ""
+"April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
+"snazzy new ideas in it"
+msgstr ""
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid "14 criteria with their requirements and how to operationalize them."
+msgstr ""
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid ""
+"An introduction with a high level background, what this standard is, and how"
+" the Foundation for Public Code will use it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (paragraph)
+msgid ""
+"This first version was produced together with the Amsterdam University of "
+"Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
+"Public Code! project](https://smartcities.publiccode.net/)."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 1 (header)
+msgid "Code of Conduct"
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 3 (paragraph)
+msgid ""
+"Many community members are from civic or professional environments with "
+"behavioral codes yet some individuals are not. This document expresses "
+"expectations of all community members and all interactions regardless of "
+"communication channel."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
+msgid "Be here to collaborate."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
+msgid "Be considerate, respectful, and patient."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
+msgid "Strive to be as constructive as possible."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
+msgid "To raise a concern, please email directors@publiccode.net."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 1 (header)
+msgid "Contributing to this standard"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 3 (paragraph)
+msgid "🙇‍♀️ Thank you for contributing!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 4 (paragraph)
+msgid ""
+"We understand that a standard like this can only be set in collaboration "
+"with as many public technologists, policy makers and interested folk as "
+"possible. Thus we appreciate your input, enjoy feedback and welcome "
+"improvements to this project and are very open to collaboration."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 5 (paragraph)
+msgid ""
+"We love issues and pull requests from everyone. If you're not comfortable "
+"with GitHub, you can email use your feedback at "
+"[info@publiccode.net](mailto:info@publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 6 (header)
+msgid "Problems, suggestions and questions in issues"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 7 (paragraph)
+msgid ""
+"A high-level overview of the development that we already have sketched out "
+"can be seen in the [roadmap](/docs/roadmap.md). Please help development by "
+"reporting problems, suggesting changes and asking questions. To do this, you"
+" can [create a GitHub issue](https://docs.github.com/en/issues/tracking-"
+"your-work-with-issues/creating-an-issue) for this project in the [GitHub "
+"Issues for the Standard for Public "
+"Code](https://github.com/publiccodenet/standard/issues)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 8 (paragraph)
+msgid ""
+"Or, sign up to the [mailing "
+"list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)"
+" and send an email to "
+"[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 9 (paragraph)
+msgid ""
+"You don't need to change any of our code or documentation to be a "
+"contributor!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 10 (header)
+msgid "Documentation and code in pull requests"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 11 (paragraph)
+msgid ""
+"If you want to add to the documentation or code of one of our projects you "
+"should make a pull request."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 12 (paragraph)
+msgid ""
+"If you never used GitHub, get up to speed with [Understanding the GitHub "
+"flow](https://docs.github.com/en/get-started/quickstart/github-flow) or "
+"follow one of the great free interactive courses in [GitHub "
+"Skills](https://skills.github.com/) on working with GitHub and working with "
+"MarkDown, the syntax this project's documentation is in."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 13 (paragraph)
+msgid ""
+"This project is licensed Creative Commons Zero v1.0 Universal, which "
+"essentially means that the project, along with your contributions is in the "
+"public domain in whatever jurisdiction possible, and everyone can do "
+"whatever they want with it."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 14 (header)
+msgid "1. Make your changes"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 15 (paragraph)
+msgid ""
+"Contributions should [follow](docs/standard-for-public-code.html) the "
+"requirements set out in the criteria of the Standard for Public code itself."
+" Reviewers will also be ensuring that contributions are aligned with the "
+"[values of public code](foreword.md#values-of-public-code). Furthermore, "
+"they will review that the contribution conforms to the "
+"[standards](#standards-to-follow) and remains coherent with the overall "
+"work."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 16 (paragraph)
+msgid ""
+"This project uses the [GitFlow branching model and "
+"workflow](https://nvie.com/posts/a-successful-git-branching-model/). When "
+"you've forked this repository, please make sure to create a feature branch "
+"following the GitFlow model."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 17 (paragraph)
+msgid ""
+"Add your changes in commits [with a message that explains "
+"them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-"
+"message). If more than one type of change is needed, group logically related"
+" changes into separate commits. For example, white-space fixes could be a "
+"separate commit from text content changes. When adding new files, select "
+"file formats that are easily viewed in a `diff`, for instance, `.svg` is "
+"preferable to a binary image. Document choices or decisions you make in the "
+"commit message, this will enable everyone to be informed of your choices in "
+"the future."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 18 (paragraph)
+msgid ""
+"If you are adding code, make sure you've added and updated the relevant "
+"documentation and tests before you submit your pull request. Make sure to "
+"write tests that show the behavior of the newly added or changed code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 19 (header)
+msgid "Applicable policy"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 20 (paragraph)
+msgid ""
+"Currently, the Standard for Public Code is not implementing any specific "
+"public policy."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 21 (header)
+msgid "Style"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 22 (paragraph)
+msgid ""
+"The Standard for Public Code aims to [use plain English](criteria/use-plain-"
+"english.md) and we have chosen American English for spelling. Text content "
+"should typically follow one line per sentence, with no line-wrap, in order "
+"to make `diff` output easier to view. However, we want to emphasize that it "
+"is more important that you make your contribution than worry about spelling "
+"and typography. We will help you get it right in our review process and we "
+"also have a separate quality check before [making a new "
+"release](docs/releasing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 23 (header)
+msgid "Standards to follow"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 24 (paragraph)
+msgid ""
+"These are the standards that the Standard for Public Code uses. Please make "
+"sure that your contributions are aligned with them so that they can be "
+"merged more easily."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
+" keywords"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[Web Content Accessibility Guidelines "
+"2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 26 (header)
+msgid "2. Pull request"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 27 (paragraph)
+msgid ""
+"When submitting the pull request, please accompany it with a description of "
+"the problem you are trying to solve and the issue number that this pull "
+"request fixes. It is preferred for each pull request to address a single "
+"issue where possible. In some cases a single set of changes may address "
+"multiple issues, in which case be sure to list all issue numbers fixed."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 28 (header)
+msgid "3. Improve"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 29 (paragraph)
+msgid ""
+"All contributions have to be reviewed by someone. The Foundation for Public "
+"Code has committed to make sure that maintainers are available to review "
+"contributions with an aim to provide feedback within two business days."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 30 (paragraph)
+msgid ""
+"It could be that your contribution can be merged immediately by a "
+"maintainer. However, usually, a new pull request needs some improvements "
+"before it can be merged. Other contributors (or helper robots) might have "
+"feedback. If this is the case the reviewing maintainer will help you improve"
+" your documentation and code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 31 (paragraph)
+msgid "If your documentation and code have passed human review, it is merged."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 32 (header)
+msgid "4. Celebrate"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 33 (paragraph)
+msgid ""
+"Your ideas, documentation and code have become an integral part of this "
+"project. You are the open source hero we need!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 34 (paragraph)
+msgid ""
+"In fact, feel free to open a pull request to add your name to the "
+"[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 35 (header)
+msgid "Translations in other languages"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 36 (paragraph)
+msgid ""
+"While the Standard does not have any official translations, you can help "
+"maintain existing and add new [community translations of the "
+"Standard](https://github.com/publiccodenet/community-translations-standard)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 37 (header)
+msgid "Releases"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 38 (paragraph)
+msgid ""
+"We have dedicated documentation for creating [new "
+"releases](/docs/releasing.md) and [ordering printed "
+"standards](/docs/printing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 39 (paragraph)
+msgid ""
+"For more information on how to use and contribute to this project, please "
+"read the [`README`](README.md)."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 3 (header)
+msgid "Governance"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 4 (paragraph)
+msgid ""
+"This standard lies at the core of the codebase stewardship provided by the "
+"[Foundation for Public Code](https://publiccode.net/). We decide if a "
+"codebase is ready for community co-development based on this document."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 5 (paragraph)
+msgid "The standard is maintained by Foundation for Public Code staff."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 6 (paragraph)
+msgid ""
+"[We welcome contributions, such as suggestions for changes or general "
+"feedback, from anyone.](/CONTRIBUTING.md)"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 7 (paragraph)
+msgid ""
+"Because of the important role that the Standard for Public Code has in our "
+"core process we require the highest standards from the Standard."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 8 (paragraph)
+msgid ""
+"We will try to respond promptly to all pull requests. The pull request is an"
+" opportunity to work together to improve our methods and the Standard. We "
+"may not accept all changes, but we will explain our logic."
+msgstr ""
+
+#: ./README.md:block 1 (header)
+msgid "Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 3 (paragraph)
+msgid ""
+"The Standard for Public Code gives public organizations a model for "
+"preparing open source solutions to enable collaborations with similar public"
+" organizations in other places. It includes guidance for policy makers, city"
+" administrators, developers and vendors."
+msgstr ""
+
+#: ./README.md:block 4 (paragraph)
+msgid ""
+"![version 0.7.0](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
+msgstr ""
+
+#: ./README.md:block 5 (paragraph)
+msgid ""
+"[![pages-build-"
+"deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-"
+"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-deployment) "
+"[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
+" [![standard main badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
+"url-check/standard.publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net-"
+"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
+"check/standard.publiccode.net-develop-url-check-look.json)"
+msgstr ""
+
+#: ./README.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is in a draft format. We are preparing it for a"
+" version 1.0 release. Currently, we are testing it on a small number of "
+"codebases."
+msgstr ""
+
+#: ./README.md:block 7 (header)
+msgid "Applying the Standard for Public Code to your codebase"
+msgstr ""
+
+#: ./README.md:block 8 (paragraph)
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. To see how ready "
+"your codebase is, you can do a quick [eligibility self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility) that "
+"will give you a rough idea of how much work you may need to do to meet all "
+"criteria."
+msgstr ""
+
+#: ./README.md:block 9 (paragraph)
+msgid ""
+"The standard *should* be mostly self-explanatory in how to apply it to your "
+"codebase. If anything in the standard is unclear, we encourage you to open "
+"an issue here so that we can help you and anyone else who feels the same as "
+"you. For inspiration, look at the [community built implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/) which contains examples and other tips."
+msgstr ""
+
+#: ./README.md:block 10 (paragraph)
+msgid ""
+"If there are any breaking changes in a new version of the Standard for "
+"Public Code, the codebase stewards at the Foundation for Public Code will "
+"help any implementers of the standard understand how the gaps can be closed."
+msgstr ""
+
+#: ./README.md:block 11 (paragraph)
+msgid ""
+"If you want to commit your codebase to become fully compliant to the "
+"standard for future certification, please contact us at "
+"[info@publiccode.net](mailto:info@publiccode.net) to initiate a formal "
+"[assessment](https://about.publiccode.net/activities/codebase-"
+"stewardship/lifecycle-diagram.html#assessment)."
+msgstr ""
+
+#: ./README.md:block 12 (header)
+msgid "Request for contributions"
+msgstr ""
+
+#: ./README.md:block 13 (paragraph)
+msgid ""
+"We believe public policy and software should be inclusive, usable, open, "
+"legible, accountable, accessible and sustainable. This means we need a new "
+"way of designing, developing and procuring both the source code and policy "
+"documentation."
+msgstr ""
+
+#: ./README.md:block 14 (paragraph)
+msgid ""
+"This standard sets a quality level for codebases that meets the needs of "
+"public organizations, institutions and administrations as well as other "
+"critical infrastructural services."
+msgstr ""
+
+#: ./README.md:block 15 (paragraph)
+msgid ""
+"The standard lives at "
+"[standard.publiccode.net](https://standard.publiccode.net/). See "
+"[`index.md`](index.md) for an overview of all content."
+msgstr ""
+
+#: ./README.md:block 16 (paragraph)
+msgid ""
+"[![Thumbnail for the video on the Standard for Public Code: a printed "
+"version lying on a table between two "
+"hands](https://img.youtube.com/vi/QWt6vB-"
+"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+msgstr ""
+
+#: ./README.md:block 17 (paragraph)
+msgid ""
+"[A video introduction to Standard for Public "
+"Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
+"Global Summit 2020 (4:12) on YouTube."
+msgstr ""
+
+#: ./README.md:block 18 (header)
+msgid "Help improve this standard"
+msgstr ""
+
+#: ./README.md:block 19 (paragraph)
+msgid ""
+"The Foundation for Public Code is committed to maintaining and developing "
+"the Standard for Public Code at a level of quality that meets the standard "
+"itself."
+msgstr ""
+
+#: ./README.md:block 20 (paragraph)
+msgid ""
+"We are looking for people like you to [contribute](CONTRIBUTING.md) to this "
+"project by suggesting improvements and helping develop it. 😊 Get started by "
+"reading our [contributors guide](CONTRIBUTING.md). Since it is such a core "
+"document we will accept contributions when they add significant value. We've"
+" described how we govern the standard in the [governance "
+"statement](GOVERNANCE.md)."
+msgstr ""
+
+#: ./README.md:block 21 (paragraph)
+msgid ""
+"Please note that this project is released with a [code of "
+"conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
+"abide by its terms. Please be lovely to all other community members."
+msgstr ""
+
+#: ./README.md:block 22 (header)
+msgid "Preview, build and deploy"
+msgstr ""
+
+#: ./README.md:block 23 (paragraph)
+msgid ""
+"The repository builds to a static site deployed at "
+"[standard.publiccode.net](https://standard.publiccode.net/). It is built "
+"with [GitHub pages](https://pages.github.com) and "
+"[Jekyll](https://jekyllrb.com/)."
+msgstr ""
+
+#: ./README.md:block 24 (paragraph)
+msgid ""
+"The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
+"means you will need ruby and ruby-bundler installed, for example:"
+msgstr ""
+
+#: ./README.md:block 26 (paragraph)
+msgid ""
+"If `ruby` and `bundle` are installed, one can run `bundle install` after "
+"which the site can be rendered with the `script/serve.sh` script."
+msgstr ""
+
+#: ./README.md:block 27 (header)
+msgid "Testing"
+msgstr ""
+
+#: ./README.md:block 28 (paragraph)
+msgid ""
+"A variety of test scripts are included. The script `script/test-all.sh` "
+"wraps running of all local tests."
+msgstr ""
+
+#: ./README.md:block 29 (paragraph)
+msgid ""
+"See the scripts in the "
+"[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
+msgstr ""
+
+#: ./README.md:block 30 (header)
+msgid "Generating a PDF of the Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 31 (paragraph)
+msgid ""
+"In addition to Jekyll, generating PDFs relies upon "
+"[Weasyprint](https://weasyprint.org/) and "
+"[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
+"used to transform PDFs into `.epub`."
+msgstr ""
+
+#: ./README.md:block 32 (paragraph)
+msgid ""
+"To generate these kinds of files, the dependencies should be installed, for "
+"example:"
+msgstr ""
+
+#: ./README.md:block 34 (paragraph)
+msgid ""
+"The file `standard-print.html` can be converted to a nice looking PDF, along"
+" with the other release files, using:"
+msgstr ""
+
+#: ./README.md:block 36 (header)
+msgid "License"
+msgstr ""
+
+#: ./README.md:block 37 (paragraph)
+msgid "© [The authors and contributors](AUTHORS.md)"
+msgstr ""
+
+#: ./README.md:block 38 (paragraph)
+msgid ""
+"The standard is [licensed](LICENSE) under CC 0, which also applies to all "
+"illustrations and the documentation. This means anyone can do anything with "
+"it. If you contribute you also grant these rights to others. You can read "
+"more about how to help in the [contributing guide](CONTRIBUTING.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
+msgid "order: 2 redirect_from:"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 4 (unordered list)
+msgid "criteria/bundle-policy-and-code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
+msgid ""
+"Access to both [source code](../glossary.md#source-code) and "
+"[policy](../glossary.md#policy) documentation provides building blocks for "
+"anyone to implement the codebase in their local context or contribute to the"
+" further development of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
+msgid ""
+"Understanding the domain and policies within that domain is fundamental to "
+"understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
+msgid ""
+"To be able to evaluate whether to implement a codebase in a new context, an "
+"organization needs to understand what process changes it must choose to make"
+" or how to contribute additional configurability to the existing solution in"
+" order to adapt it to the new context."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "The codebase MUST include the policy that the source code is based on."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"If a policy is based on source code, that source code MUST be included in "
+"the codebase, unless used for fraud detection."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
+msgid "Public policy makers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Collaborate with developers and designers to make sure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable, such "
+"as those published by the [Object Management "
+"Group](https://www.omg.org/spec/)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Track policy with [the same version control](maintain-version-control.md) "
+"and documentation used to track source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Check in regularly to understand how the source code in the codebase has "
+"changed and whether it still matches the [intentions of the "
+"policy](document-codebase-objectives.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development, including legal obligations like the [General Data Protection "
+"Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web "
+"Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-"
+"accessibility), or human rights policies, like a public organization's "
+"commitment to equal opportunity."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
+msgid "Managers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Work together with policy makers to make sure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
+" on Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 3 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 4 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 5 (paragraph)
+msgid ""
+"Coding in the open improves transparency, increases [source "
+"code](../glossary.md#source-code) quality, makes the source code easier to "
+"audit, and enables collaboration."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 6 (paragraph)
+msgid ""
+"Together, this creates more opportunities for citizens to understand how "
+"software and [policy](../glossary.md#policy) impact their interactions with "
+"a public organization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any policy in use (unless used for fraud detection) MUST"
+" be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST NOT contain sensitive information regarding users, their "
+"organization or third parties."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the [codebase](../glossary.md#codebase) files and commit "
+"history do not include sensitive information."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"Clearly split data and source code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 3 (header)
+msgid ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 4 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
+msgid ""
+"Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps "
+"others decide whether to use and contribute to it. A codebase version's "
+"maturity includes the maturity of its dependencies. Understanding how a "
+"codebase has evolved is key to understanding the codebase and how to "
+"contribute to it."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The codebase MUST be versioned."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase MUST prominently document whether or not there are versions of "
+"the codebase that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"Codebase versions that are ready to use MUST only depend on versions of "
+"other codebases that are also ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The method for assigning version identifiers SHOULD be documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "It is OPTIONAL to use semantic versioning."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that it is obvious to policy makers, managers, developers and "
+"designers whether the codebase has versions that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that ready to use versions of the codebase do not depend on any "
+"versions of other codebases that are not ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Check that the versioning scheme of the codebase is documented and followed."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any [source"
+" code](../glossary.md#source-code) developed needs to be tested and improved"
+" before it can be put into service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
+msgid ""
+"Make sure that services only rely on versions of codebases of equal or "
+"greater maturity than the service. For example, don't use a beta version of "
+"a codebase in a production service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that the codebase versioning approach is followed for all "
+"releases."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Software release life "
+"cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
+msgid "order: 8 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
+msgid "criteria/document-objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 5 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
+msgid ""
+"Clearly documenting [codebase](../glossary.md#codebase) objectives "
+"communicates the purpose of the codebase. It helps stakeholders and "
+"contributors scope the development of the codebase. The objectives also "
+"provide an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST contain documentation of its objectives, like a mission "
+"and goal statement, that is understandable by developers and designers so "
+"that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Make sure that all your codebase objectives have links or references to "
+"supporting policy documents added to meet the [Bundle policy and source "
+"code](bundle-policy-and-source-code.md) criterion."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 3 (paragraph)
+msgid "order: 9 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 4 (unordered list)
+msgid "criteria/documenting"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 5 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 6 (paragraph)
+msgid ""
+"Well documented [source code](../glossary.md#source-code) helps people to "
+"understand what the source code does and how to use it. Documentation is "
+"essential for people to start using the [codebase](../glossary.md#codebase) "
+"and contributing to it more quickly."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"All of the functionality of the codebase, [policy](../glossary.md#policy) as"
+" well as source code, MUST be described in language clearly understandable "
+"for those that understand the purpose of the codebase."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the software."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated correctly, and links and images are "
+"tested."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Try to use the codebase, so your feedback can improve how clearly the policy"
+" and source code are documented. For example, is the current documentation "
+"sufficient to persuade a manager at another public organization to use this "
+"codebase?"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 18 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./criteria/index.md:block 3 (header)
+msgid "order: 0"
+msgstr ""
+
+#: ./criteria/index.md:block 4 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./criteria/index.md:block 5 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./criteria/index.md:block 6 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./criteria/index.md:block 7 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 3 (paragraph)
+msgid "order: 6 redirect_from:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 4 (unordered list)
+msgid "criteria/version-control-and-history"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 5 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 6 (paragraph)
+msgid ""
+"[Version control](../glossary.md#version-control) means keeping track of "
+"changes to the [source code](../glossary.md#source-code) and other files of "
+"the [codebase](../glossary.md#codebase) over time. This allows you to "
+"maintain structured documentation of the history of the codebase. This is "
+"essential for collaboration at scale, as it enables developers to work on "
+"changes in parallel and helps future developers to understand the reasons "
+"for changes."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All files in the codebase MUST be version controlled."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD require contributors to group relevant "
+"changes in commits."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD encourage file formats where the changes "
+"within the files can be easily viewed and understood in the version control "
+"system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 13 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 15 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Make sure that all files required to understand the code, build and deploy "
+"are in the version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
+"use GitHub or refresh your skills."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 3 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 4 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 5 (paragraph)
+msgid ""
+"To develop better, more reliable and feature rich software, users need to be"
+" able to fix problems, add features, and address security issues of the "
+"shared [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 6 (paragraph)
+msgid ""
+"A shared digital infrastructure makes it easier to make collaborative "
+"contributions. The less effort it takes to make contributions that are "
+"accepted by the codebase, the more likely users are to become contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have a public issue tracker that accepts suggestions from "
+"anyone."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"There MUST be a way to report security issues for responsible disclosure "
+"over a closed channel."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST include instructions for how to report potentially "
+"security sensitive issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a closed channel for reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 12 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Just like for [reviews](require-review-of-contributions.md), make sure to "
+"respond to requests promptly."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Keep your managers informed of the time and resources you require to support"
+" other contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate communication channels for asking maintainers and"
+" stakeholders questions are easy to locate, for instance in the README."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate contact details are included in the metadata, for"
+" instance in the publiccode.yml file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
+msgid "order: 14 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
+msgid "criteria/findability"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 5 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
+msgid ""
+"The more findable a [codebase](../glossary.md#codebase) is, the more "
+"potential new collaborators will find it. Just publishing a codebase and "
+"hoping it is found does not work, instead proactiveness is needed."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
+msgid ""
+"A metadata description file increases discoverability. Well-written metadata"
+" containing a unique and persistent identifier, such as a Wikidata item or "
+"FSF software directory listing (thus being part of the semantic web), makes "
+"the codebase easier for people to refer, cite, disambiguate and discover "
+"through third party tools."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a short description that helps someone understand "
+"what the codebase is for or what it does."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by describing the "
+"problem it solves in natural language."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check that the codebase name is descriptive and free of puns."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of acronyms and abbreviations or that "
+"the acronyms or abbreviations in the name are more universally known than "
+"the longer forms."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of organizational branding, unless that"
+" organization is of the codebase community itself."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase repository has a short description of the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by the codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by using natural language, for instance, using the "
+"short description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as social media account descriptions."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Make sure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Search engine optimization, for instance adding a "
+"[sitemap](https://www.sitemaps.org/protocol.html)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as the repository description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Software Foundation."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
+msgid "order: 3 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/reusable-and-portable-codebases"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/create-reusable-and-portable-code"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
+msgid "Make the codebase reusable and portable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
+msgid ""
+"Creating reusable and portable [code](../glossary.md#code) enables policy "
+"makers, developers and designers to reuse what has been developed, test it, "
+"improve it and contribute those improvements back, leading to better "
+"quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
+msgid ""
+"Thoughtfully and purposefully designing a "
+"[codebase](../glossary.md#codebase) for reusability allows for the mission, "
+"vision and scope of the codebase to be shared by multiple parties. Codebases"
+" developed and used by multiple parties are more likely to benefit from a "
+"self-sustaining community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
+msgid ""
+"Organizing a codebase such that it is composed of well documented modules "
+"improves reusability and maintainability. A module is easier to reuse in "
+"[another context](../glossary.md#different-contexts) if its purpose is "
+"clearly documented."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
+msgid ""
+"Source code which does not rely on the situation-specific infrastructure of "
+"any contributor, vendor or deployment can be tested by any other "
+"contributor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase MUST be developed to be reusable in different contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed software or services for execution and understanding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The development of the codebase SHOULD be a collaboration between multiple "
+"parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Configuration SHOULD be used to make [source code](../glossary.md#source-"
+"code) adapt to context specific needs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Source code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The software SHOULD NOT require services or platforms available from only a "
+"single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"use the codebase and what that would entail."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed software or services."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"If the codebase is in early development before a production-ready release, "
+"then check for evidence of ambition to obtain collaborators."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Or if the codebase is very mature and stable with very infrequent fixes, "
+"patches, or contributions:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check for documented and budgeted commitments of collaboration."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Otherwise:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check that the codebase contributors are from multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the software can be deployed and run without services or "
+"platforms available from a single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Identify other organizations for your teams to collaborate with."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid "Make sure that your teams are collaborating with other teams."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
+msgid ""
+"Make sure that the codebase documentation describes the build-time and "
+"runtime dependencies. If your context requires deploying to proprietary "
+"platforms or using proprietary components, make sure that collaborators can "
+"develop, use, test, and deploy without them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
+msgid "order: 13 redirect_from:"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
+msgid "criteria/open-licenses"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 5 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 6 (paragraph)
+msgid ""
+"An open and well known license makes it possible for anyone to see the "
+"[source code](../glossary.md#source-code) in order to understand how it "
+"works, to use it freely and to contribute to the "
+"[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
+"emerge around the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
+msgid ""
+"Clearly indicating the license for each file within a codebase facilitates "
+"correct reuse and attribution of parts of a codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code and documentation MUST be licensed such that it may be "
+"freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid "All source code MUST be published with a license file."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Having multiple licenses for different types of source code and "
+"documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires source code to be "
+"[open source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their source code by "
+"publishing it under an open source license."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"When source code is being reused by the codebase, make sure that it has a "
+"license that is compatible with the license or licenses of the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
+msgid "order: 7 redirect_from:"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
+msgid "criteria/require-review"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 5 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 6 (paragraph)
+msgid ""
+"Peer-review of contributions is essential for [source "
+"code](../glossary.md#source-code) quality, reducing security risks and "
+"operational risks."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
+msgid ""
+"Requiring thorough review of contributions encourages a culture of making "
+"sure every contribution is of high quality, completeness and value. Source "
+"code review increases the chance of discovering and fixing potential bugs or"
+" mistakes before they are added to the [codebase](../glossary.md#codebase). "
+"Knowing that all source code was reviewed discourages a culture of blaming "
+"individuals, and encourages a culture of focusing on solutions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
+msgid ""
+"A [policy](../glossary.md#policy) of prompt reviews assures contributors of "
+"a guaranteed time for feedback or collaborative improvement, which increases"
+" both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"codebase MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews MUST include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"The review process SHOULD confirm that a contribution conforms to the "
+"standards, architecture and decisions set out in the codebase in order to "
+"pass review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the software and the tests of the "
+"codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check if guidelines for reviewers include instructions to review for "
+"conformance to standards, architecture and codebase guidelines."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check with reviewers if they run the software and tests during review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just source code, is "
+"reviewed."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make delivering great software a shared objective."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Try to respond to others' requests for review promptly, initially providing "
+"feedback about the concept of the change."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/)."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
+msgid "order: 15 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
+msgid "criteria/style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 5 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 6 (paragraph)
+msgid ""
+"Following a consistent and coherent style enables contributors in different "
+"environments to work together. Unifying vocabularies reduces friction in "
+"communication between contributors."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST use a coding or writing style "
+"guide, either the codebase community's own or an existing one referred to in"
+" the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The style guide SHOULD include expectations for inline comments and "
+"documentation for non-trivial sections."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"Including expectations for [understandable English](use-plain-english.md) in"
+" the style guide is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 12 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 16 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [source code](../glossary.md#source-code) contributions in "
+"order for them to be merged by the maintainers, including source, tests and "
+"documentation. Continually improve upon and expand this documentation with "
+"the aim of evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 3 (paragraph)
+msgid "order: 12 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 4 (unordered list)
+msgid "criteria/continuous-integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 5 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 6 (paragraph)
+msgid ""
+"Asynchronous collaboration is enabled by developers merging their work to a "
+"shared branch frequently, verified by automated tests. The more frequent the"
+" merging and the smaller the contribution, the easier it is to resolve merge"
+" conflicts."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 7 (paragraph)
+msgid ""
+"Automated testing of all functionality provides confidence that "
+"contributions are working as intended and have not introduced errors, and "
+"allows reviewers to focus on the structure and approach of the contribution."
+" The more focused the test, the easier it is to clearly identify and "
+"understand errors as they arise."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 8 (paragraph)
+msgid ""
+"Documenting a codebase's [continuous integration](../glossary.md#continuous-"
+"integration) workflow helps contributors understand the expectations of "
+"contributions. Continuous integration allows for an easier monitoring of the"
+" state of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"All functionality in the [source code](../glossary.md#source-code) MUST have"
+" automated tests."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the codebase."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have active contributors who can review contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Automated test results for contributions SHOULD be public."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing the software by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code coverage tools check that coverage is at 100% of "
+"the source code."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check that test results are viewable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check if source code coverage data is published."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Involve managers as well as developers and designers as early in the process"
+" as possible and keep them engaged throughout development of your policy."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure the source code reflects any changes to the policy (see [Maintain "
+"version control](maintain-version-control.md))."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Plan the work to integrate small parts very often instead of large parts "
+"less frequently."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers structure the work plan such that it can be integrated as "
+"small increments."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Structure source code written to handle conditions which are difficult to "
+"create in a test environment in such a way that the conditions can be "
+"simulated during testing. Forms of resource exhaustion such as running out "
+"of storage space and memory allocation failure are typical examples of "
+"difficult to create conditions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 3 (paragraph)
+msgid "order: 11 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 4 (unordered list)
+msgid "criteria/open-standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 5 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 6 (paragraph)
+msgid ""
+"[Open standards](../glossary.md#open-standard) guarantee access to the "
+"knowledge required to use and contribute to the "
+"[codebase](../glossary.md#codebase). They enable interoperability between "
+"systems and reduce the risk of vendor lock-in. Open standards which are "
+"unambiguous allow for independent development of either side of data "
+"exchange."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"For features of the codebase that facilitate the exchange of data the "
+"codebase MUST use an open standard that meets the [Open Source Initiative "
+"Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Open standards that are machine testable SHOULD be preferred over open "
+"standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Non-open standards that are machine testable SHOULD be preferred over non-"
+"open standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 14 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in [source "
+"code](../glossary.md#source-code) reviews."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 18 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 3 (paragraph)
+msgid "order: 10 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 4 (unordered list)
+msgid "criteria/understandable-english-first"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 5 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 6 (paragraph)
+msgid ""
+"English is the <i>de facto</i> language of collaboration in software "
+"development."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 7 (paragraph)
+msgid ""
+"Public sector information needs to be accessible to all its constituents. "
+"Plain and simple language makes the [code](../glossary.md#code) and what it "
+"does easier to understand for a wider variety of people."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 8 (paragraph)
+msgid ""
+"Translations further increase the possible reach of a "
+"[codebase](../glossary.md#codebase). Language that is easy to understand "
+"lowers the cost of creating and maintaining translations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid "All codebase documentation MUST be in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All [source code](../glossary.md#source-code) MUST be in English, except "
+"where [policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 14 (unordered list)
+msgid ""
+"Frequently test with other managers, developers and designers in the process"
+" if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Frequently test with policy makers and managers if they understand what you "
+"are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
+"readable and understandable."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"The[European Union accessibility directive](https://ec.europa.eu/digital-"
+"single-market/en/web-accessibility) by the European Commission, is an "
+"example of regulation requiring high accessibility."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 3 (paragraph)
+msgid "order: 4 redirect_from:"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 4 (unordered list)
+msgid "criteria/open-to-contributions"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 5 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 6 (paragraph)
+msgid ""
+"The atmosphere in a [codebase](../glossary.md#codebase) community helps "
+"users decide to use one codebase over another. Welcoming anyone as a "
+"contributor enables the community to grow and sustain itself over time. A "
+"community where contributors have clear ways to influence codebase and "
+"community goals and progress is less likely to split and end up in diverging"
+" communities. Newcomers need to understand and trust the codebase "
+"community’s governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST allow anyone to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The contribution guidelines SHOULD document who is expected to cover the "
+"costs of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Check that contributing guidelines cover who is expected to cover the costs "
+"of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If needed, make sure you have allocated budget for the contributions review "
+"process as agreed by the codebase community."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid ""
+"Communicate clearly to contributors what they need to do make sure their "
+"contribution can be integrated."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./docs/printing.md:block 1 (header)
+msgid "Printing"
+msgstr ""
+
+#: ./docs/printing.md:block 3 (paragraph)
+msgid ""
+"The printed Standard for Public Code is printed by Reclameland. This guide "
+"tries to provide the relevant information to print it there or somewhere "
+"else."
+msgstr ""
+
+#: ./docs/printing.md:block 4 (paragraph)
+msgid ""
+"Details, mostly in order they are on the Reclameland page with the Dutch if "
+"necessary:"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Form: Softcover book ([Reclameland product "
+"page](https://www.reclameland.nl/drukken/softcover-boeken))"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Format: A4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Portrait or landscape: Portrait (Staand)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing inside: 4/4 dual sided full color"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Inside material: 90 grams biotop"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover: 350 grams cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing cover: 4/0 one sided full cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover treatment: one sided matt foliated (Enke)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
+" multiple of 4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Individually sealed: no"
+msgstr ""
+
+#: ./docs/printing.md:block 6 (paragraph)
+msgid ""
+"When these details are chosen, the cover and insides are uploaded and the "
+"order is placed payment can happen (payment ahead) after which printing "
+"starts."
+msgstr ""
+
+#: ./docs/releasing.md:block 1 (header)
+msgid "Releasing a new version of the Standard for public code"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Review state of the 'develop' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure all changes intended for release are merged"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Invite a proofread of the current state of the branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If new dashes are introduced, check if the language can be simplified to "
+"remove them in favor of more simple sentences. If a complex sentence is "
+"needed, see if the dash can be replaced with other punctuation. If a dash is"
+" truly the best expression of ideas, then follow the [Chicago Manual of "
+"Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create a release branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update the new release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update releaseDate in `publiccode.yml`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Perform extra pass on diff to the 'main' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"run `script/generate-review-template.sh` and commit updated `docs/review-"
+"template.html`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"update `docs/standard-for-public-code.md` with the new text from the review "
+"template, updating any status changes as a result"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reread any section or paragraph to ensure wording changes still fit the "
+"whole and do not contain grammar or spelling errors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
+" `script/ensure-font.sh`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure no link collisions exist"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Check the page breaks, possibly removing or adding page-break CSS, for "
+"example: `<p style=\"page-break-after: always;\"></p>`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "If needed, commit fixes and repeat extra pass"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push branch, open a pull request to the 'main' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Request review from multiple reviewers, especially a proofreader"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reviewers will create issues for shortcomings found which would not prevent "
+"release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If needed for release, reviewers may create pull requests to resolve issues"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Re-request reviews if additional pull requests are merged into release "
+"branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Run the to-archive-org.sh script"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Once reviews are complete, merge to 'main'"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create GitHub release with the release notes and version number"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Switch to the 'main' branch, `git pull` and `git status`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git tag $MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Trigger a rebuild of gh-pages"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Open a pull request from this branch to `main`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Approve and merge PR (containing empty commit)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update 'develop' with a merge from 'main'"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "[Send the files for print to the printer](printing.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Cover file"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Inside pages PDF"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ping [translation](https://github.com/publiccodenet/community-translations-"
+"standard) contributors"
+msgstr ""
+
+#: ./docs/roadmap.md:block 1 (header)
+msgid "Roadmap"
+msgstr ""
+
+#: ./docs/roadmap.md:block 3 (paragraph)
+msgid "Last updated: 2023-03-08"
+msgstr ""
+
+#: ./docs/roadmap.md:block 4 (paragraph)
+msgid ""
+"This document intends to shed light on the current development plans of the "
+"team. Plans change constantly as new information is absorbed by the team."
+msgstr ""
+
+#: ./docs/roadmap.md:block 5 (paragraph)
+msgid ""
+"Codebase stewards review the roadmap monthly as part of our [backlog pruning"
+" session](https://about.publiccode.net/activities/standard-"
+"maintenance/backlog-pruning.html)."
+msgstr ""
+
+#: ./docs/roadmap.md:block 6 (header)
+msgid "Current work"
+msgstr ""
+
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "As far as possible, make the standard Standard-compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 8 (header)
+msgid "Near term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Separate executive summary"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid ""
+"Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
+" issue #208"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Possibly: add in the illustrations for each criterion"
+msgstr ""
+
+#: ./docs/roadmap.md:block 10 (header)
+msgid "Longer term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Certification badges"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid ""
+"Add to README and index.md information (and eventually statistics) on "
+"adoption and use (issue #438)"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Physical paper checklist"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Becoming validated by multiple codebases"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Release version 1.0.0 after a few codebases are compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Linkable requirements"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "New cover art"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Register for ISBN"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "List with an on-demand book printing service"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "QR codes for external links in print version"
+msgstr ""
+
+#: ./foreword.md:block 3 (paragraph)
+msgid "redirect_from:"
+msgstr ""
+
+#: ./foreword.md:block 4 (unordered list)
+msgid "introduction"
+msgstr ""
+
+#: ./foreword.md:block 5 (header)
+msgid "Foreword"
+msgstr ""
+
+#: ./foreword.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that support public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./foreword.md:block 7 (paragraph)
+msgid ""
+"Anyone developing public-purpose software or policy can use this standard to"
+" work towards higher quality public services that are more cost effective, "
+"with less risk and more control."
+msgstr ""
+
+#: ./foreword.md:block 8 (paragraph)
+msgid ""
+"This foreword introduces the term public code and explains why this is "
+"important."
+msgstr ""
+
+#: ./foreword.md:block 9 (header)
+msgid "Definition of public code"
+msgstr ""
+
+#: ./foreword.md:block 10 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines. It "
+"encompasses the software built to operate with and as public infrastructure,"
+" along with the arrangements for its production. Public code is explicitly "
+"distinct from regular software because it operates under fundamentally "
+"different circumstances and expectations."
+msgstr ""
+
+#: ./foreword.md:block 11 (header)
+msgid "Reasons for public code"
+msgstr ""
+
+#: ./foreword.md:block 12 (paragraph)
+msgid "There are many reasons for why public code is relevant now."
+msgstr ""
+
+#: ./foreword.md:block 13 (header)
+msgid "Software code == legal code"
+msgstr ""
+
+#: ./foreword.md:block 14 (paragraph)
+msgid "Software is public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 15 (paragraph)
+msgid ""
+"In the 21st century, software can be considered vital public infrastructure."
+" It is increasingly not just the expression of existing policy but the "
+"originator of new policy, for example where algorithms decide which "
+"districts need extra social services or policing."
+msgstr ""
+
+#: ./foreword.md:block 16 (paragraph)
+msgid ""
+"Software mechanics, algorithms and data collection have become key elements "
+"in the execution of public policies. Computer code now executes policies "
+"that have been codified in legal code through democratic procedures. Both "
+"forms of code set conditions for society to function according to "
+"democratically set public values, the latter executed by humans, the former "
+"by machines. In other words, software code has increasingly started to equal"
+" legal code."
+msgstr ""
+
+#: ./foreword.md:block 17 (paragraph)
+msgid ""
+"Software should therefore be subject to the principles of democratic "
+"governance."
+msgstr ""
+
+#: ./foreword.md:block 18 (header)
+msgid "Traditional public software procurement"
+msgstr ""
+
+#: ./foreword.md:block 19 (paragraph)
+msgid ""
+"Current public software production methods have not served public service "
+"delivery very well."
+msgstr ""
+
+#: ./foreword.md:block 20 (paragraph)
+msgid ""
+"In the last decade, public organizations that purchased complete software "
+"solutions have sometimes been surprised to discover that they:"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"can’t change their software to reflect changing policy or take advantage of "
+"new technology"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"don’t have access to their data as it's locked into proprietary systems"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid "are asked to pay ever increasing license fees"
+msgstr ""
+
+#: ./foreword.md:block 22 (header)
+msgid "Technological sovereignty and democratic accountability"
+msgstr ""
+
+#: ./foreword.md:block 23 (paragraph)
+msgid "Public institutions, civil servants and residents deserve better."
+msgstr ""
+
+#: ./foreword.md:block 24 (paragraph)
+msgid ""
+"We believe the software that runs our society can no longer be a black box, "
+"controlled by outside companies that keep the underlying logic on which "
+"their software operates hidden in proprietary codebases. Instead, "
+"governments and the people they serve need technological sovereignty. This "
+"allows them to set and control the functioning of public software, just like"
+" they are able to set and control policy that is legally formulated in laws."
+" Citizens and civil society actors need this software to be transparent and "
+"accountable."
+msgstr ""
+
+#: ./foreword.md:block 25 (paragraph)
+msgid ""
+"The design of software as essential civic infrastructure should honor "
+"digital citizens’ rights."
+msgstr ""
+
+#: ./foreword.md:block 26 (header)
+msgid "Designing truly public software"
+msgstr ""
+
+#: ./foreword.md:block 27 (paragraph)
+msgid ""
+"Public code is at the core of modern public institutions, shapes the work of"
+" civil servants and affects the lives of almost all residents."
+msgstr ""
+
+#: ./foreword.md:block 28 (paragraph)
+msgid "Public software must therefore be:"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "transparent"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "accountable"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "understandable for its constituents"
+msgstr ""
+
+#: ./foreword.md:block 30 (paragraph)
+msgid ""
+"It must reflect the values of the society it serves, for example by being "
+"inclusive and non-discriminatory."
+msgstr ""
+
+#: ./foreword.md:block 31 (paragraph)
+msgid ""
+"Most proprietary software systems currently used by public organizations do "
+"not meet these requirements. Public code does."
+msgstr ""
+
+#: ./foreword.md:block 32 (header)
+msgid "Values of public code"
+msgstr ""
+
+#: ./foreword.md:block 33 (paragraph)
+msgid "We consider public code to have these core values:"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Inclusive"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Usable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Open"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Legible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accountable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accessible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Sustainable"
+msgstr ""
+
+#: ./foreword.md:block 35 (header)
+msgid "How public code works"
+msgstr ""
+
+#: ./foreword.md:block 36 (paragraph)
+msgid ""
+"Public code is open source software meant for fulfilling the essential role "
+"of public organizations. Through use, other administrations contribute back "
+"to the software, so that its development and maintenance become truly "
+"collaborative."
+msgstr ""
+
+#: ./foreword.md:block 37 (paragraph)
+msgid "Being open unlocks many other things."
+msgstr ""
+
+#: ./foreword.md:block 38 (paragraph)
+msgid ""
+"Local responsibility and democratic accountability are ensured when a public"
+" organization implements and maintains their own public code. By being open "
+"and with a broader contributor base, the software is more secure as it "
+"benefits from many eyes spotting potential flaws. Many contributors share "
+"the maintenance work to keep it functional and modern, which reduces future "
+"technical debt. The shared workload is more sustainable now and in the "
+"future. Its openness makes both the code and its data more easily adaptable "
+"in the future. The code will be easier to retool, repurpose or retire. This "
+"all results in lower risk public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 39 (paragraph)
+msgid ""
+"This pooling of resources lets public administrations give extra attention "
+"to how to customize the software so it works best in each local context, "
+"creating better user experiences for their end users (residents or "
+"citizens)."
+msgstr ""
+
+#: ./foreword.md:block 40 (header)
+msgid "Economics of public code"
+msgstr ""
+
+#: ./foreword.md:block 41 (paragraph)
+msgid ""
+"Public code offers a better economic model for public organizations as well "
+"as for commercial companies. It's an alternative to traditional software "
+"procurement which increases local control and economic opportunity."
+msgstr ""
+
+#: ./foreword.md:block 42 (paragraph)
+msgid ""
+"Designed from the start to be open, adaptable and with data portability, it "
+"can be developed by in-house staff or trusted vendors. Because the code is "
+"open, the public administration can change vendors if they need to. Open "
+"code increases opportunities for public learning and scrutiny, allowing the "
+"public administration to procure smaller contracts. Smaller procurements are"
+" easier for local small and medium enterprises to bid upon. Public "
+"administrations can use their own software purchasing to stimulate "
+"innovation and competition in their local economy."
+msgstr ""
+
+#: ./foreword.md:block 43 (paragraph)
+msgid ""
+"This can be seen as investment leading to future economic growth. More "
+"vendors will be necessary due to growing technology demand."
+msgstr ""
+
+#: ./foreword.md:block 44 (header)
+msgid "Procuring public code"
+msgstr ""
+
+#: ./foreword.md:block 45 (paragraph)
+msgid ""
+"Public code can be used and developed by permanent in-house development "
+"teams, contractors or outsourced suppliers. Vendors to public organizations "
+"can include public code in their bids for contracts."
+msgstr ""
+
+#: ./foreword.md:block 46 (paragraph)
+msgid ""
+"To use existing public code, you need to specify in your budget and project "
+"design that your new solution will use that codebase. To encourage an "
+"innovative approach to adapting the public code to your context, you could "
+"describe the service or outcome in your contract."
+msgstr ""
+
+#: ./foreword.md:block 47 (header)
+msgid "The goals for the Standard for Public Code"
+msgstr ""
+
+#: ./foreword.md:block 48 (paragraph)
+msgid ""
+"This Standard supports developers, designers, managers and public policy "
+"makers to:"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop high quality software and policy for better public service delivery"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop codebases that can be reused across contexts and collaboratively "
+"maintained"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "reduce technical debt and project failure rate"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"have more granular control over, and ability to make decisions about, their "
+"IT systems"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "improve vendor relationships with a better economic model"
+msgstr ""
+
+#: ./foreword.md:block 50 (paragraph)
+msgid ""
+"Potential users of codebases tested against the Standard for Public Code can"
+" expect them to be highly reusable, easily maintainable and of high quality."
+msgstr ""
+
+#: ./foreword.md:block 51 (paragraph)
+msgid "The Standard for Public Code does this by:"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "setting out a common terminology for public code development"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "establishing measures to help develop high quality public code"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid ""
+"providing guidance on how to fulfill its criteria and operationalize "
+"compliance"
+msgstr ""
+
+#: ./foreword.md:block 53 (paragraph)
+msgid ""
+"The Standard for Public Code is meant to be time and technology independent."
+msgstr ""
+
+#: ./foreword.md:block 54 (header)
+msgid "Who this is for"
+msgstr ""
+
+#: ./foreword.md:block 55 (paragraph)
+msgid ""
+"The Standard for Public Code is for the people who create and reuse public "
+"code:"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "public policy makers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "business and project managers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "developers and designers"
+msgstr ""
+
+#: ./foreword.md:block 57 (paragraph)
+msgid "These people work at:"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid "institutions, organizations and administrations in the public sector"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid ""
+"consultancies and vendors of information technology and policy services to "
+"public organizations"
+msgstr ""
+
+#: ./foreword.md:block 59 (paragraph)
+msgid ""
+"It is not aimed at public organizations' end users (residents or citizens), "
+"journalists or academics."
+msgstr ""
+
+#: ./foreword.md:block 61 (unordered list)
+msgid ""
+"[\"Modernising Public Infrastructure with Free Software\" white "
+"paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
+"Software.pdf) by the Free Software Foundation Europe."
+msgstr ""
+
+#: ./foreword.md:block 62 (header)
+msgid "Videos on public code"
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Collaborative Code is the Future of Cities @ DecidimFest "
+"2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
+"the background behind the Foundation for Public Code."
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Public Money? Public Code! - Panel @ Nextcloud Conference "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
+"procurement, law and more."
+msgstr ""
+
+#: ./foreword.md:block 64 (header)
+msgid "Get involved"
+msgstr ""
+
+#: ./foreword.md:block 65 (paragraph)
+msgid ""
+"This standard is a living document. [Read our contributor "
+"guide](/CONTRIBUTING.md) to learn how you can make it better."
+msgstr ""
+
+#: ./foreword.md:block 66 (header)
+msgid "Contact"
+msgstr ""
+
+#: ./foreword.md:block 67 (paragraph)
+msgid ""
+"For questions and more information about the Foundation for Public Code you "
+"can find us at [our website](https://publiccode.net/), email us at "
+"info@publiccode.net, or call us at +31 20 2 444 500."
+msgstr ""
+
+#: ./glossary.md:block 3 (header)
+msgid "Glossary"
+msgstr ""
+
+#: ./glossary.md:block 4 (header)
+msgid "Code"
+msgstr ""
+
+#: ./glossary.md:block 5 (paragraph)
+msgid ""
+"Any explicitly described system of rules. This includes laws, policy and "
+"ordinances, as well as source code that is used to build software. Both of "
+"these are rules, some executed by humans and others by machines."
+msgstr ""
+
+#: ./glossary.md:block 6 (header)
+msgid "Codebase"
+msgstr ""
+
+#: ./glossary.md:block 7 (paragraph)
+msgid ""
+"Any discrete package of code (both source and policy), the tests and the "
+"documentation required to implement a piece of policy or software."
+msgstr ""
+
+#: ./glossary.md:block 8 (paragraph)
+msgid "This can be, for example, a document or a version-control repository."
+msgstr ""
+
+#: ./glossary.md:block 9 (header)
+msgid "Continuous integration"
+msgstr ""
+
+#: ./glossary.md:block 10 (paragraph)
+msgid ""
+"In software engineering, continuous integration (CI) is the practice of "
+"merging all developers' working copies to a development branch of a codebase"
+" as frequently as reasonable."
+msgstr ""
+
+#: ./glossary.md:block 11 (header)
+msgid "Different contexts"
+msgstr ""
+
+#: ./glossary.md:block 12 (paragraph)
+msgid ""
+"Two contexts are different if they are different public organizations or "
+"different departments for which there is not one decision maker that could "
+"make collaboration happen naturally."
+msgstr ""
+
+#: ./glossary.md:block 13 (header)
+msgid "General public"
+msgstr ""
+
+#: ./glossary.md:block 14 (paragraph)
+msgid ""
+"The public at large: end users of the code and the services based upon it."
+msgstr ""
+
+#: ./glossary.md:block 15 (paragraph)
+msgid ""
+"For example, a city's residents are considered end users of a city's "
+"services and of all code that powers these services."
+msgstr ""
+
+#: ./glossary.md:block 16 (header)
+msgid "Open source"
+msgstr ""
+
+#: ./glossary.md:block 17 (paragraph)
+msgid ""
+"Open source is defined by the Open Source Initiative in their [Open Source "
+"Definition](https://opensource.org/osd-annotated)."
+msgstr ""
+
+#: ./glossary.md:block 18 (header)
+msgid "Open standard"
+msgstr ""
+
+#: ./glossary.md:block 19 (paragraph)
+msgid ""
+"An open standard is any standard that meets the Open Source Initiative's "
+"[Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./glossary.md:block 20 (header)
+msgid "Policy"
+msgstr ""
+
+#: ./glossary.md:block 21 (paragraph)
+msgid ""
+"A policy is a deliberate system of principles to guide decisions and achieve"
+" rational outcomes. A policy is a statement of intent, and is implemented as"
+" a procedure or protocol. Policies are generally adopted by a governance "
+"body within an organization. Policies can assist in both subjective and "
+"objective decision making."
+msgstr ""
+
+#: ./glossary.md:block 22 (paragraph)
+msgid ""
+"Public policy is the process by which governments translate their political "
+"vision into programs and actions to deliver outcomes."
+msgstr ""
+
+#: ./glossary.md:block 23 (paragraph)
+msgid ""
+"At the national level, policy and legislation (the law) are usually "
+"separate. The distinction is often more blurred in local government."
+msgstr ""
+
+#: ./glossary.md:block 24 (paragraph)
+msgid ""
+"In the Standard the word 'policy' refers to policy created and adopted by "
+"public organizations such as governments and municipalities."
+msgstr ""
+
+#: ./glossary.md:block 25 (header)
+msgid "Public code"
+msgstr ""
+
+#: ./glossary.md:block 26 (paragraph)
+msgid ""
+"Public code is open source software developed by public organizations, "
+"together with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./glossary.md:block 27 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines."
+msgstr ""
+
+#: ./glossary.md:block 28 (paragraph)
+msgid ""
+"Public code serves the public interest, is open, legible, accountable, "
+"accessible and sustainable."
+msgstr ""
+
+#: ./glossary.md:block 29 (paragraph)
+msgid ""
+"By developing public code independently from but still implementable in the "
+"local context for which it was developed, as well as documenting the "
+"development process openly, public code can provide a building block for "
+"others to:"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "re-implement in their local context"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "take as a starting point to continue development"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "use as a basis for learning"
+msgstr ""
+
+#: ./glossary.md:block 31 (paragraph)
+msgid ""
+"To facilitate reuse, public code is either released into the public domain "
+"or licensed with an open license that permits others to view and reuse the "
+"work freely and to produce derivative works."
+msgstr ""
+
+#: ./glossary.md:block 32 (header)
+msgid "Repository"
+msgstr ""
+
+#: ./glossary.md:block 33 (paragraph)
+msgid ""
+"A repository is a storage location used by version control tools for files "
+"and metadata of a codebase. Repositories allow multiple contributors to work"
+" on the same set of files. Repositories are able to store multiple versions "
+"of sets of files."
+msgstr ""
+
+#: ./glossary.md:block 34 (header)
+msgid "Source Code"
+msgstr ""
+
+#: ./glossary.md:block 35 (paragraph)
+msgid ""
+"Human readable text of a computer program which can be translated into "
+"machine instructions."
+msgstr ""
+
+#: ./glossary.md:block 36 (header)
+msgid "Version control"
+msgstr ""
+
+#: ./glossary.md:block 37 (paragraph)
+msgid ""
+"Version control is the management of changes to source code and the files "
+"associated with it. Changes are usually identified by a code, termed the "
+"*revision number* (or similar). Each revision is associated with the time it"
+" was made and the person making the change, thus making it easier to retrace"
+" the evolution of the code. Revision control systems can be used to compare "
+"different versions with each other and to see how content has changed over "
+"time."
+msgstr ""
+
+#: ./index.md:block 3 (header)
+msgid "toc: false"
+msgstr ""
+
+#: ./index.md:block 4 (header)
+msgid "Guidance for government open source collaboration"
+msgstr ""
+
+#: ./index.md:block 5 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that supports public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./index.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code provides guidance to public organizations "
+"building their own open source solutions to enable successful future "
+"collaboration and reuse by similar organizations in the public sector in "
+"other places. It includes advice for policy makers, government managers, "
+"developers and vendors. The Standard for Public Code supports the "
+"collaborative creation of codebases that are usable, open, legible, "
+"accountable, accessible and sustainable. It is meant to be applicable to "
+"codebases for all levels of government, from supranational to municipal."
+msgstr ""
+
+#: ./index.md:block 7 (paragraph)
+msgid ""
+"The Standard for Public Code defines ‘[public code](glossary.md#public-"
+"code)’ as open source software developed by public organizations, together "
+"with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./index.md:block 8 (paragraph)
+msgid ""
+"The criteria of the Standard for Public Code are aligned with guidelines and"
+" best practices of open source software development."
+msgstr ""
+
+#: ./index.md:block 9 (paragraph)
+msgid ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} Additional"
+" context and background can be found in the [foreword](foreword.md). {% "
+"endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 10 (header)
+msgid "Contents"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Glossary](glossary.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[Criteria](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for"
+" page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Authors](AUTHORS.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Contributing guide](CONTRIBUTING.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Governance](GOVERNANCE.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Version history](CHANGELOG.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[License](license.html)"
+msgstr ""
+
+#: ./index.md:block 12 (header)
+msgid "Community calls"
+msgstr ""
+
+#: ./index.md:block 13 (paragraph)
+msgid ""
+"We usually have a community call on the first Thursday of the month at 15:00"
+" (CET/CEST). [The agenda](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code) is updated roughly a week before the call. It is "
+"possible to [sign "
+"up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
+" to get a call invitation emailed to you."
+msgstr ""
+
+#: ./index.md:block 14 (header)
+msgid "Other resources"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"Unofficial [community translations of the "
+"Standard](https://publiccodenet.github.io/community-translations-standard/) "
+"in other languages"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard compliance self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
+"public sector open source codebases"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard criteria "
+"checklist](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
+"template.html) used by Foundation for Public Code stewards for codebase "
+"review"
+msgstr ""
+
+#: ./readers-guide.md:block 3 (header)
+msgid "Readers guide"
+msgstr ""
+
+#: ./readers-guide.md:block 4 (paragraph)
+msgid ""
+"The Standard describes a number of criteria. All criteria have consistent "
+"sections that make it clear how to create great public code."
+msgstr ""
+
+#: ./readers-guide.md:block 5 (paragraph)
+msgid ""
+"References to \"policy makers\", \"managers\", and \"developers and "
+"designers\" apply to anyone performing duties associated with these roles, "
+"regardless of their job title. It is common for individuals to have duties "
+"which span multiple roles."
+msgstr ""
+
+#: ./readers-guide.md:block 6 (paragraph)
+msgid ""
+"Below is a brief explanation of each of these sections and how they are used"
+" within the criteria of the Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 7 (header)
+msgid "Introduction"
+msgstr ""
+
+#: ./readers-guide.md:block 8 (paragraph)
+msgid ""
+"This section explains what the criterion aims to achieve and why it is "
+"important for a codebase's users and contributors."
+msgstr ""
+
+#: ./readers-guide.md:block 10 (paragraph)
+msgid ""
+"This section lists what needs to be done in order to comply with the "
+"standard."
+msgstr ""
+
+#: ./readers-guide.md:block 11 (paragraph)
+msgid ""
+"The following keywords in this document are to be interpreted as described "
+"in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "REQUIRED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "RECOMMENDED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MAY"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "OPTIONAL"
+msgstr ""
+
+#: ./readers-guide.md:block 14 (paragraph)
+msgid ""
+"This section offers actions you can take to see if a contribution is "
+"compliant with the Standard. This is key if you want to operationalize the "
+"Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 15 (paragraph)
+msgid ""
+"We've tried to word it so that someone who is not intimately acquainted with"
+" the subject matter can still do a basic check for compliance."
+msgstr ""
+
+#: ./readers-guide.md:block 17 (paragraph)
+msgid ""
+"This section tries to specifically speak to policy makers by offering them "
+"concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 18 (paragraph)
+msgid ""
+"Public policy makers set the priorities and goals of projects and may be "
+"less technologically experienced."
+msgstr ""
+
+#: ./readers-guide.md:block 20 (paragraph)
+msgid ""
+"This section tries to specifically speak to managers by offering concrete "
+"actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 21 (paragraph)
+msgid ""
+"Managers are responsible for on-time project delivery, stakeholder "
+"management and continued delivery of the service. For this they are wholly "
+"reliant on both policy makers as well as developers and designers. They need"
+" to create the right culture, line up the right resources and provide the "
+"right structures to deliver great services."
+msgstr ""
+
+#: ./readers-guide.md:block 23 (paragraph)
+msgid ""
+"This section tries to specifically speak to developers and designers by "
+"offering them concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 24 (paragraph)
+msgid ""
+"Developers are usually more technically aligned and have more impact on the "
+"delivery of services than the previous groups."
+msgstr ""
+
+#: ./readers-guide.md:block 25 (header)
+msgid "Limitation of scope"
+msgstr ""
+
+#: ./readers-guide.md:block 26 (paragraph)
+msgid ""
+"The Standard for Public Code is not meant to cover individual "
+"implementations of a codebase. This means the standard does not tell "
+"implementers how to comply with their organization's local technical "
+"infrastructure or legal framework."
+msgstr ""
+
+#: ./readers-guide.md:block 27 (paragraph)
+msgid ""
+"Also, while the Standard for Public Code refers to several standards and has"
+" considerable overlap with others, its purpose is to enable collaboration. "
+"Therefore, it does not aim to replace quality standards, like the ISO 25000 "
+"series, or those focusing on security, like the [OpenSSF Best Practices "
+"Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
+"synergize well with them."
+msgstr ""
+
+#: ./readers-guide.md:block 28 (paragraph)
+msgid ""
+"And while the purpose includes enabling collaboration, it will not guarantee"
+" that a community will spring into existence. That still requires "
+"proactiveness and ambition beyond making the codebase collaboration ready."
+msgstr ""
diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..46615c34
--- /dev/null
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,5583 @@
+#
+msgid ""
+msgstr ""
+
+#: ./404.md:block 1 (header)
+msgid "SPDX-License-Identifier: CC0-1.0"
+msgstr ""
+
+#: ./404.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./404.md:block 3 (header)
+msgid ""
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
+msgstr ""
+
+#: ./404.md:block 4 (header)
+msgid "404 Not Found"
+msgstr ""
+
+#: ./404.md:block 5 (paragraph)
+msgid "If you typed the web address, check it is correct."
+msgstr ""
+
+#: ./404.md:block 6 (paragraph)
+msgid "If you pasted the web address, check you copied the entire address."
+msgstr ""
+
+#: ./404.md:block 7 (paragraph)
+msgid ""
+"If the web address is correct or you followed a link or button, email the "
+"[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
+"able to help you out, as well as correct our mistake."
+msgstr ""
+
+#: ./AUTHORS.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./AUTHORS.md:block 3 (header)
+msgid "Authors"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Engelen"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Schuijff, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ben Cerveny, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Bert Spaan"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Boris van Hoytema, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Charlotte Heikendorf"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Claus Mullie, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "David Barberi"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Edo Plantinga, [Code For NL](https://codefor.nl/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Elena Findley-de Regt, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Eric Herman, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Felix Faassen, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Floris Deerenberg"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Jan Ainali, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Johan Groenen, Code For NL"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Marcus Klaas de Vries"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Martijn de Waal, [Amsterdam University of Applied Sciences "
+"(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
+"Creative Industries, Lectorate of Play & Civic Media"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Matti Schneider"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mauko Quiroga"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurice Hendriks, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurits van der Schee, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mirjam van Tiel, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ngô Ngọc Đức Huy"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Paul Keller"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
+"(NIIS)](https://niis.org)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Sky Bristol"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Tamas Erkelens, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Timo Slinger"
+msgstr ""
+
+#: ./CC0-1.0.md:block 3 (header)
+msgid "toc: false redirect_from: - license.html - LICENSE.html"
+msgstr ""
+
+#: ./CC0-1.0.md:block 4 (header)
+msgid "Creative Commons Zero v1.0 Universal"
+msgstr ""
+
+#: ./CC0-1.0.md:block 6 (paragraph)
+msgid ""
+"This license is the legal contract that allows anyone to do anything they "
+"like with the content in this entire document."
+msgstr ""
+
+#: ./CHANGELOG.md:block 3 (header)
+msgid "Version history"
+msgstr ""
+
+#: ./CHANGELOG.md:block 5 (header)
+msgid "Version 0.7.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 6 (paragraph)
+msgid ""
+"May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
+"review funding and clarifies review process requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Add requirement to document who is expected to cover the cost of reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Add requirement to have a short description of the codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Change the focus of contributions adhering to standards to focus on the "
+"review of contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Review template now in HTML format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Introduction converted to foreword."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved contributing guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved documentation of scripts."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (header)
+msgid "Version 0.6.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 9 (paragraph)
+msgid ""
+"April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
+"portability and tests and an introduction to each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about the development "
+"being a collaboration between multiple parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about being dependent "
+"on a single vendor."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Use continuous integration about publishing results for "
+"automated tests."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Differentiating the two requirements about security to clearly be about "
+"providing a method and having documentation about it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Rephrased requirements to focus on the codebase rather than contributor "
+"behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Removed the sections Why this is important and What this does not do and "
+"replaced with an introduction in each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added general What this does not do section in the introduction of the "
+"Standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for public policy makers about related policies and license "
+"compatibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for developers and designers about version controlling files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Clarified guidance for developers and designers about prompt responses and "
+"search engine optimization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added Further reading about accessibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Aligned criteria URLs with criteria names."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Improved navigation in the web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved tools in Further reading sections to the community implementation "
+"guide."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved compliance or certification process to "
+"[publiccode.net](https://publiccode.net)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Change format of the review template to make it easier to update after a new"
+" release."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Improved the text on the landing page and added links to related resources."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added spell checker automated test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Made minor changes to text for clarity and consistency."
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Moved SPDX headers to yaml header."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (header)
+msgid "Version 0.5.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 12 (paragraph)
+msgid ""
+"January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
+"guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust the coding style requirement to focus on the codebase using a style "
+"guide rather than contributor behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement for codebase names to Make the codebase findable from Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement about testing the code by using examples to Use continuous"
+" integration from Document the code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Split requirement about machine testable standards to clarify that open is "
+"more important than testable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust how to test findability requirements to be less reliant on search "
+"engine algorithms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (header)
+msgid "Version 0.4.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 15 (paragraph)
+msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity focuses on whether or not versions of the codebase are "
+"ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity no longer requires specific labels for codebases that are "
+"not ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Audit flow image now generated from an easier to translate format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Improved guidance on How to test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add publiccode.yml file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add review template."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Consistently link glossary terms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add practices and standards to follow in CONTRIBUTING."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add Matti Schneider to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add remaining SPDX headers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Made additional minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Some hyperlinks updated."
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Moved examples to the [Community implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (header)
+msgid "Version 0.4.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 18 (paragraph)
+msgid ""
+"September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduce new criterion: Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Improve How to test section for most criteria."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"New requirement in Welcome contributors about publishing activity "
+"statistics."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Removed redundant requirement about portable and reusable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expand open license definition to include both OSI and FSF approved "
+"licenses."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expressed intent that the Standard for Public Code should meet its own "
+"requirements where applicable and added assessment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add SPDX license identifiers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduced new Code of Conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify distinction between source code and policy text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Restructuring of requirements with bullet point lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Acknowledge the importance of codebase modularity for reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Move requirements related to Findability to the new criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify the role of non-open standards when used in a codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Additional guidance about build-time and runtime dependencies."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added roadmap for the development of the Standard for Public Code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Update structure of Authors file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add Audrey Tang to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added a list of criteria to the print edition."
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Clarify what the standard means with policymakers, managers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (header)
+msgid "Version 0.3.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 21 (paragraph)
+msgid ""
+"May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Requirement for localization made explicit in Create reusable and portable "
+"code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Documentation of governance changed from a SHOULD to a MUST."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Replace the very subjective (and hard to test) \"contributions MUST be "
+"small\" with requirement to document expectation in contributing guidelines "
+"and focus on a single issue."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Community translations now linked in the footer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Many minor clarifications to language and sentences made more simple."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (header)
+msgid "Version 0.2.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 24 (paragraph)
+msgid ""
+"March 15th 2022: 📜 the ninth draft allows English summaries for policy "
+"lacking an official translation."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Relax the criterion Use plain English by adding a new requirement allows "
+"bundled policy not available in English to have an accompanying summary in "
+"English instead of translating the full text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Similarly, allow for English summaries for policies not available in English"
+" in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Clarify that term 'policy' includes processes which impact development and "
+"deployment in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Emphasize reusability also on parts of the solutions in Create reusable and "
+"portable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Expand guidance to Developers and designers in Create reusable and portable "
+"code about deploying to proprietary platforms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Add nuance to use of non-English terms in what management need to do in Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Change the pull request process diagram to use Mermaid instead of BPMN to "
+"make [community translations](https://github.com/publiccodenet/community-"
+"translations-standard) easier."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added Maurice Hendriks to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added OpenApi Specification to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Made the attributions in further reading sections clearer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (header)
+msgid "Version 0.2.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 27 (paragraph)
+msgid ""
+"November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
+" as code may not be in English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Document exception to \"All code MUST be in English\" where policy is "
+"interpreted as code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Add MAY requirement regarding committer email addresses in Maintain version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Policy Makers in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Developers and designers in Use a coherent style."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add \"Different contexts\" to glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Digital Public Goods approval badge."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Open Standards principles to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Definition of plain language to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Move the Semantic Versioning Specification further reading reference."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Clarify that publiccode.yml is one example of a machine-readable metadata "
+"description."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add instructions for creating a print version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (header)
+msgid "Version 0.2.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 30 (paragraph)
+msgid ""
+"March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
+"0.2.0."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"New SHOULD requirement on using a distributed version control system and why"
+" distributed is important."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Feedback requirements for rejected contributions are more strict than "
+"accepted ones."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Specify that copyright and license notices should also be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Advice on how to test that notices be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clarify guidance for rolling releases."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clear up definition of version control in glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Add further reading encouraging contribution, SPDX, Git and reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add links to videos about the concept of public code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Update BPMN link."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Reduce link duplication."
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (header)
+msgid "Version 0.2.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 33 (paragraph)
+msgid ""
+"October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
+"and \"Welcome contributors\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Rename criterion \"Pay attention to codebase maturity\" to \"Document "
+"codebase maturity\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Changed MUST to SHOULD for requirement of codebase in use by multiple "
+"parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add MUST NOT requirement regarding copyright assignment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Clarify role of configuration in reusable code requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Glossary additions: continuous integration, policy, repository, and version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Replace references to 'cities' with 'public organizations'."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Clarify aspects of sensitive code by separating contributor and reviewer "
+"requirements into separate items."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Expand further reading, and guidance to policy makers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add Felix Faassen and Arnout Engelen to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (header)
+msgid "Version 0.1.4"
+msgstr ""
+
+#: ./CHANGELOG.md:block 36 (paragraph)
+msgid ""
+"November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
+"fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Linked License.md file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made punctuation more consistent, especially for bullet lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made some minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (header)
+msgid "Version 0.1.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 39 (paragraph)
+msgid ""
+"October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
+" the autumn cleaning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Renamed continuous delivery to continuous integration."
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Referencing accessibility guidelines in the language standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "A bunch of style and consistency fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (header)
+msgid "Version 0.1.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 42 (paragraph)
+msgid ""
+"August 22th 2019: 🌠 the third draft focuses on better text and takes "
+"community input"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "With some great new contributors comes a fresh author list."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "All links are now HTTPS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "General proofreading, wording clarifications, and smashed typos."
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Updated criteria:"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Requirement for reuse in different contexts"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit versioning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for multi party development"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for license headers in files"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for vulnerability reporting"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit documentation of governance"
+msgstr ""
+
+#: ./CHANGELOG.md:block 44 (header)
+msgid "Version 0.1.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 45 (paragraph)
+msgid ""
+"May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
+"lot of typos"
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid ""
+"Removed references to the Foundation for Public Code, we're going to have to"
+" change the name in becoming an association."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the introduction."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Added the code of conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "We've recommended using the publiccode.yml standard for easier reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (header)
+msgid "Version 0.1.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 48 (paragraph)
+msgid ""
+"April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
+"snazzy new ideas in it"
+msgstr ""
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid "14 criteria with their requirements and how to operationalize them."
+msgstr ""
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid ""
+"An introduction with a high level background, what this standard is, and how"
+" the Foundation for Public Code will use it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (paragraph)
+msgid ""
+"This first version was produced together with the Amsterdam University of "
+"Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
+"Public Code! project](https://smartcities.publiccode.net/)."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 1 (header)
+msgid "Code of Conduct"
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 3 (paragraph)
+msgid ""
+"Many community members are from civic or professional environments with "
+"behavioral codes yet some individuals are not. This document expresses "
+"expectations of all community members and all interactions regardless of "
+"communication channel."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
+msgid "Be here to collaborate."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
+msgid "Be considerate, respectful, and patient."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
+msgid "Strive to be as constructive as possible."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
+msgid "To raise a concern, please email directors@publiccode.net."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 1 (header)
+msgid "Contributing to this standard"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 3 (paragraph)
+msgid "🙇‍♀️ Thank you for contributing!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 4 (paragraph)
+msgid ""
+"We understand that a standard like this can only be set in collaboration "
+"with as many public technologists, policy makers and interested folk as "
+"possible. Thus we appreciate your input, enjoy feedback and welcome "
+"improvements to this project and are very open to collaboration."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 5 (paragraph)
+msgid ""
+"We love issues and pull requests from everyone. If you're not comfortable "
+"with GitHub, you can email use your feedback at "
+"[info@publiccode.net](mailto:info@publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 6 (header)
+msgid "Problems, suggestions and questions in issues"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 7 (paragraph)
+msgid ""
+"A high-level overview of the development that we already have sketched out "
+"can be seen in the [roadmap](/docs/roadmap.md). Please help development by "
+"reporting problems, suggesting changes and asking questions. To do this, you"
+" can [create a GitHub issue](https://docs.github.com/en/issues/tracking-"
+"your-work-with-issues/creating-an-issue) for this project in the [GitHub "
+"Issues for the Standard for Public "
+"Code](https://github.com/publiccodenet/standard/issues)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 8 (paragraph)
+msgid ""
+"Or, sign up to the [mailing "
+"list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)"
+" and send an email to "
+"[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 9 (paragraph)
+msgid ""
+"You don't need to change any of our code or documentation to be a "
+"contributor!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 10 (header)
+msgid "Documentation and code in pull requests"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 11 (paragraph)
+msgid ""
+"If you want to add to the documentation or code of one of our projects you "
+"should make a pull request."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 12 (paragraph)
+msgid ""
+"If you never used GitHub, get up to speed with [Understanding the GitHub "
+"flow](https://docs.github.com/en/get-started/quickstart/github-flow) or "
+"follow one of the great free interactive courses in [GitHub "
+"Skills](https://skills.github.com/) on working with GitHub and working with "
+"MarkDown, the syntax this project's documentation is in."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 13 (paragraph)
+msgid ""
+"This project is licensed Creative Commons Zero v1.0 Universal, which "
+"essentially means that the project, along with your contributions is in the "
+"public domain in whatever jurisdiction possible, and everyone can do "
+"whatever they want with it."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 14 (header)
+msgid "1. Make your changes"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 15 (paragraph)
+msgid ""
+"Contributions should [follow](docs/standard-for-public-code.html) the "
+"requirements set out in the criteria of the Standard for Public code itself."
+" Reviewers will also be ensuring that contributions are aligned with the "
+"[values of public code](foreword.md#values-of-public-code). Furthermore, "
+"they will review that the contribution conforms to the "
+"[standards](#standards-to-follow) and remains coherent with the overall "
+"work."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 16 (paragraph)
+msgid ""
+"This project uses the [GitFlow branching model and "
+"workflow](https://nvie.com/posts/a-successful-git-branching-model/). When "
+"you've forked this repository, please make sure to create a feature branch "
+"following the GitFlow model."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 17 (paragraph)
+msgid ""
+"Add your changes in commits [with a message that explains "
+"them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-"
+"message). If more than one type of change is needed, group logically related"
+" changes into separate commits. For example, white-space fixes could be a "
+"separate commit from text content changes. When adding new files, select "
+"file formats that are easily viewed in a `diff`, for instance, `.svg` is "
+"preferable to a binary image. Document choices or decisions you make in the "
+"commit message, this will enable everyone to be informed of your choices in "
+"the future."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 18 (paragraph)
+msgid ""
+"If you are adding code, make sure you've added and updated the relevant "
+"documentation and tests before you submit your pull request. Make sure to "
+"write tests that show the behavior of the newly added or changed code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 19 (header)
+msgid "Applicable policy"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 20 (paragraph)
+msgid ""
+"Currently, the Standard for Public Code is not implementing any specific "
+"public policy."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 21 (header)
+msgid "Style"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 22 (paragraph)
+msgid ""
+"The Standard for Public Code aims to [use plain English](criteria/use-plain-"
+"english.md) and we have chosen American English for spelling. Text content "
+"should typically follow one line per sentence, with no line-wrap, in order "
+"to make `diff` output easier to view. However, we want to emphasize that it "
+"is more important that you make your contribution than worry about spelling "
+"and typography. We will help you get it right in our review process and we "
+"also have a separate quality check before [making a new "
+"release](docs/releasing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 23 (header)
+msgid "Standards to follow"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 24 (paragraph)
+msgid ""
+"These are the standards that the Standard for Public Code uses. Please make "
+"sure that your contributions are aligned with them so that they can be "
+"merged more easily."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
+" keywords"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[Web Content Accessibility Guidelines "
+"2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 26 (header)
+msgid "2. Pull request"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 27 (paragraph)
+msgid ""
+"When submitting the pull request, please accompany it with a description of "
+"the problem you are trying to solve and the issue number that this pull "
+"request fixes. It is preferred for each pull request to address a single "
+"issue where possible. In some cases a single set of changes may address "
+"multiple issues, in which case be sure to list all issue numbers fixed."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 28 (header)
+msgid "3. Improve"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 29 (paragraph)
+msgid ""
+"All contributions have to be reviewed by someone. The Foundation for Public "
+"Code has committed to make sure that maintainers are available to review "
+"contributions with an aim to provide feedback within two business days."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 30 (paragraph)
+msgid ""
+"It could be that your contribution can be merged immediately by a "
+"maintainer. However, usually, a new pull request needs some improvements "
+"before it can be merged. Other contributors (or helper robots) might have "
+"feedback. If this is the case the reviewing maintainer will help you improve"
+" your documentation and code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 31 (paragraph)
+msgid "If your documentation and code have passed human review, it is merged."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 32 (header)
+msgid "4. Celebrate"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 33 (paragraph)
+msgid ""
+"Your ideas, documentation and code have become an integral part of this "
+"project. You are the open source hero we need!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 34 (paragraph)
+msgid ""
+"In fact, feel free to open a pull request to add your name to the "
+"[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 35 (header)
+msgid "Translations in other languages"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 36 (paragraph)
+msgid ""
+"While the Standard does not have any official translations, you can help "
+"maintain existing and add new [community translations of the "
+"Standard](https://github.com/publiccodenet/community-translations-standard)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 37 (header)
+msgid "Releases"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 38 (paragraph)
+msgid ""
+"We have dedicated documentation for creating [new "
+"releases](/docs/releasing.md) and [ordering printed "
+"standards](/docs/printing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 39 (paragraph)
+msgid ""
+"For more information on how to use and contribute to this project, please "
+"read the [`README`](README.md)."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 3 (header)
+msgid "Governance"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 4 (paragraph)
+msgid ""
+"This standard lies at the core of the codebase stewardship provided by the "
+"[Foundation for Public Code](https://publiccode.net/). We decide if a "
+"codebase is ready for community co-development based on this document."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 5 (paragraph)
+msgid "The standard is maintained by Foundation for Public Code staff."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 6 (paragraph)
+msgid ""
+"[We welcome contributions, such as suggestions for changes or general "
+"feedback, from anyone.](/CONTRIBUTING.md)"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 7 (paragraph)
+msgid ""
+"Because of the important role that the Standard for Public Code has in our "
+"core process we require the highest standards from the Standard."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 8 (paragraph)
+msgid ""
+"We will try to respond promptly to all pull requests. The pull request is an"
+" opportunity to work together to improve our methods and the Standard. We "
+"may not accept all changes, but we will explain our logic."
+msgstr ""
+
+#: ./README.md:block 1 (header)
+msgid "Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 3 (paragraph)
+msgid ""
+"The Standard for Public Code gives public organizations a model for "
+"preparing open source solutions to enable collaborations with similar public"
+" organizations in other places. It includes guidance for policy makers, city"
+" administrators, developers and vendors."
+msgstr ""
+
+#: ./README.md:block 4 (paragraph)
+msgid ""
+"![version 0.7.0](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
+msgstr ""
+
+#: ./README.md:block 5 (paragraph)
+msgid ""
+"[![pages-build-"
+"deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-"
+"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-deployment) "
+"[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
+" [![standard main badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
+"url-check/standard.publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net-"
+"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
+"check/standard.publiccode.net-develop-url-check-look.json)"
+msgstr ""
+
+#: ./README.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is in a draft format. We are preparing it for a"
+" version 1.0 release. Currently, we are testing it on a small number of "
+"codebases."
+msgstr ""
+
+#: ./README.md:block 7 (header)
+msgid "Applying the Standard for Public Code to your codebase"
+msgstr ""
+
+#: ./README.md:block 8 (paragraph)
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. To see how ready "
+"your codebase is, you can do a quick [eligibility self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility) that "
+"will give you a rough idea of how much work you may need to do to meet all "
+"criteria."
+msgstr ""
+
+#: ./README.md:block 9 (paragraph)
+msgid ""
+"The standard *should* be mostly self-explanatory in how to apply it to your "
+"codebase. If anything in the standard is unclear, we encourage you to open "
+"an issue here so that we can help you and anyone else who feels the same as "
+"you. For inspiration, look at the [community built implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/) which contains examples and other tips."
+msgstr ""
+
+#: ./README.md:block 10 (paragraph)
+msgid ""
+"If there are any breaking changes in a new version of the Standard for "
+"Public Code, the codebase stewards at the Foundation for Public Code will "
+"help any implementers of the standard understand how the gaps can be closed."
+msgstr ""
+
+#: ./README.md:block 11 (paragraph)
+msgid ""
+"If you want to commit your codebase to become fully compliant to the "
+"standard for future certification, please contact us at "
+"[info@publiccode.net](mailto:info@publiccode.net) to initiate a formal "
+"[assessment](https://about.publiccode.net/activities/codebase-"
+"stewardship/lifecycle-diagram.html#assessment)."
+msgstr ""
+
+#: ./README.md:block 12 (header)
+msgid "Request for contributions"
+msgstr ""
+
+#: ./README.md:block 13 (paragraph)
+msgid ""
+"We believe public policy and software should be inclusive, usable, open, "
+"legible, accountable, accessible and sustainable. This means we need a new "
+"way of designing, developing and procuring both the source code and policy "
+"documentation."
+msgstr ""
+
+#: ./README.md:block 14 (paragraph)
+msgid ""
+"This standard sets a quality level for codebases that meets the needs of "
+"public organizations, institutions and administrations as well as other "
+"critical infrastructural services."
+msgstr ""
+
+#: ./README.md:block 15 (paragraph)
+msgid ""
+"The standard lives at "
+"[standard.publiccode.net](https://standard.publiccode.net/). See "
+"[`index.md`](index.md) for an overview of all content."
+msgstr ""
+
+#: ./README.md:block 16 (paragraph)
+msgid ""
+"[![Thumbnail for the video on the Standard for Public Code: a printed "
+"version lying on a table between two "
+"hands](https://img.youtube.com/vi/QWt6vB-"
+"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+msgstr ""
+
+#: ./README.md:block 17 (paragraph)
+msgid ""
+"[A video introduction to Standard for Public "
+"Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
+"Global Summit 2020 (4:12) on YouTube."
+msgstr ""
+
+#: ./README.md:block 18 (header)
+msgid "Help improve this standard"
+msgstr ""
+
+#: ./README.md:block 19 (paragraph)
+msgid ""
+"The Foundation for Public Code is committed to maintaining and developing "
+"the Standard for Public Code at a level of quality that meets the standard "
+"itself."
+msgstr ""
+
+#: ./README.md:block 20 (paragraph)
+msgid ""
+"We are looking for people like you to [contribute](CONTRIBUTING.md) to this "
+"project by suggesting improvements and helping develop it. 😊 Get started by "
+"reading our [contributors guide](CONTRIBUTING.md). Since it is such a core "
+"document we will accept contributions when they add significant value. We've"
+" described how we govern the standard in the [governance "
+"statement](GOVERNANCE.md)."
+msgstr ""
+
+#: ./README.md:block 21 (paragraph)
+msgid ""
+"Please note that this project is released with a [code of "
+"conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
+"abide by its terms. Please be lovely to all other community members."
+msgstr ""
+
+#: ./README.md:block 22 (header)
+msgid "Preview, build and deploy"
+msgstr ""
+
+#: ./README.md:block 23 (paragraph)
+msgid ""
+"The repository builds to a static site deployed at "
+"[standard.publiccode.net](https://standard.publiccode.net/). It is built "
+"with [GitHub pages](https://pages.github.com) and "
+"[Jekyll](https://jekyllrb.com/)."
+msgstr ""
+
+#: ./README.md:block 24 (paragraph)
+msgid ""
+"The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
+"means you will need ruby and ruby-bundler installed, for example:"
+msgstr ""
+
+#: ./README.md:block 26 (paragraph)
+msgid ""
+"If `ruby` and `bundle` are installed, one can run `bundle install` after "
+"which the site can be rendered with the `script/serve.sh` script."
+msgstr ""
+
+#: ./README.md:block 27 (header)
+msgid "Testing"
+msgstr ""
+
+#: ./README.md:block 28 (paragraph)
+msgid ""
+"A variety of test scripts are included. The script `script/test-all.sh` "
+"wraps running of all local tests."
+msgstr ""
+
+#: ./README.md:block 29 (paragraph)
+msgid ""
+"See the scripts in the "
+"[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
+msgstr ""
+
+#: ./README.md:block 30 (header)
+msgid "Generating a PDF of the Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 31 (paragraph)
+msgid ""
+"In addition to Jekyll, generating PDFs relies upon "
+"[Weasyprint](https://weasyprint.org/) and "
+"[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
+"used to transform PDFs into `.epub`."
+msgstr ""
+
+#: ./README.md:block 32 (paragraph)
+msgid ""
+"To generate these kinds of files, the dependencies should be installed, for "
+"example:"
+msgstr ""
+
+#: ./README.md:block 34 (paragraph)
+msgid ""
+"The file `standard-print.html` can be converted to a nice looking PDF, along"
+" with the other release files, using:"
+msgstr ""
+
+#: ./README.md:block 36 (header)
+msgid "License"
+msgstr ""
+
+#: ./README.md:block 37 (paragraph)
+msgid "© [The authors and contributors](AUTHORS.md)"
+msgstr ""
+
+#: ./README.md:block 38 (paragraph)
+msgid ""
+"The standard is [licensed](LICENSE) under CC 0, which also applies to all "
+"illustrations and the documentation. This means anyone can do anything with "
+"it. If you contribute you also grant these rights to others. You can read "
+"more about how to help in the [contributing guide](CONTRIBUTING.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
+msgid "order: 2 redirect_from:"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 4 (unordered list)
+msgid "criteria/bundle-policy-and-code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
+msgid ""
+"Access to both [source code](../glossary.md#source-code) and "
+"[policy](../glossary.md#policy) documentation provides building blocks for "
+"anyone to implement the codebase in their local context or contribute to the"
+" further development of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
+msgid ""
+"Understanding the domain and policies within that domain is fundamental to "
+"understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
+msgid ""
+"To be able to evaluate whether to implement a codebase in a new context, an "
+"organization needs to understand what process changes it must choose to make"
+" or how to contribute additional configurability to the existing solution in"
+" order to adapt it to the new context."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "The codebase MUST include the policy that the source code is based on."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"If a policy is based on source code, that source code MUST be included in "
+"the codebase, unless used for fraud detection."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
+msgid "Public policy makers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Collaborate with developers and designers to make sure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable, such "
+"as those published by the [Object Management "
+"Group](https://www.omg.org/spec/)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Track policy with [the same version control](maintain-version-control.md) "
+"and documentation used to track source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Check in regularly to understand how the source code in the codebase has "
+"changed and whether it still matches the [intentions of the "
+"policy](document-codebase-objectives.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development, including legal obligations like the [General Data Protection "
+"Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web "
+"Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-"
+"accessibility), or human rights policies, like a public organization's "
+"commitment to equal opportunity."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
+msgid "Managers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Work together with policy makers to make sure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
+" on Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 3 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 4 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 5 (paragraph)
+msgid ""
+"Coding in the open improves transparency, increases [source "
+"code](../glossary.md#source-code) quality, makes the source code easier to "
+"audit, and enables collaboration."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 6 (paragraph)
+msgid ""
+"Together, this creates more opportunities for citizens to understand how "
+"software and [policy](../glossary.md#policy) impact their interactions with "
+"a public organization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any policy in use (unless used for fraud detection) MUST"
+" be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST NOT contain sensitive information regarding users, their "
+"organization or third parties."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the [codebase](../glossary.md#codebase) files and commit "
+"history do not include sensitive information."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"Clearly split data and source code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 3 (header)
+msgid ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 4 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
+msgid ""
+"Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps "
+"others decide whether to use and contribute to it. A codebase version's "
+"maturity includes the maturity of its dependencies. Understanding how a "
+"codebase has evolved is key to understanding the codebase and how to "
+"contribute to it."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The codebase MUST be versioned."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase MUST prominently document whether or not there are versions of "
+"the codebase that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"Codebase versions that are ready to use MUST only depend on versions of "
+"other codebases that are also ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The method for assigning version identifiers SHOULD be documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "It is OPTIONAL to use semantic versioning."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that it is obvious to policy makers, managers, developers and "
+"designers whether the codebase has versions that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that ready to use versions of the codebase do not depend on any "
+"versions of other codebases that are not ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Check that the versioning scheme of the codebase is documented and followed."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any [source"
+" code](../glossary.md#source-code) developed needs to be tested and improved"
+" before it can be put into service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
+msgid ""
+"Make sure that services only rely on versions of codebases of equal or "
+"greater maturity than the service. For example, don't use a beta version of "
+"a codebase in a production service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that the codebase versioning approach is followed for all "
+"releases."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Software release life "
+"cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
+msgid "order: 8 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
+msgid "criteria/document-objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 5 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
+msgid ""
+"Clearly documenting [codebase](../glossary.md#codebase) objectives "
+"communicates the purpose of the codebase. It helps stakeholders and "
+"contributors scope the development of the codebase. The objectives also "
+"provide an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST contain documentation of its objectives, like a mission "
+"and goal statement, that is understandable by developers and designers so "
+"that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Make sure that all your codebase objectives have links or references to "
+"supporting policy documents added to meet the [Bundle policy and source "
+"code](bundle-policy-and-source-code.md) criterion."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 3 (paragraph)
+msgid "order: 9 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 4 (unordered list)
+msgid "criteria/documenting"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 5 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 6 (paragraph)
+msgid ""
+"Well documented [source code](../glossary.md#source-code) helps people to "
+"understand what the source code does and how to use it. Documentation is "
+"essential for people to start using the [codebase](../glossary.md#codebase) "
+"and contributing to it more quickly."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"All of the functionality of the codebase, [policy](../glossary.md#policy) as"
+" well as source code, MUST be described in language clearly understandable "
+"for those that understand the purpose of the codebase."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the software."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated correctly, and links and images are "
+"tested."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Try to use the codebase, so your feedback can improve how clearly the policy"
+" and source code are documented. For example, is the current documentation "
+"sufficient to persuade a manager at another public organization to use this "
+"codebase?"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 18 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./criteria/index.md:block 3 (header)
+msgid "order: 0"
+msgstr ""
+
+#: ./criteria/index.md:block 4 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./criteria/index.md:block 5 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./criteria/index.md:block 6 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./criteria/index.md:block 7 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 3 (paragraph)
+msgid "order: 6 redirect_from:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 4 (unordered list)
+msgid "criteria/version-control-and-history"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 5 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 6 (paragraph)
+msgid ""
+"[Version control](../glossary.md#version-control) means keeping track of "
+"changes to the [source code](../glossary.md#source-code) and other files of "
+"the [codebase](../glossary.md#codebase) over time. This allows you to "
+"maintain structured documentation of the history of the codebase. This is "
+"essential for collaboration at scale, as it enables developers to work on "
+"changes in parallel and helps future developers to understand the reasons "
+"for changes."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All files in the codebase MUST be version controlled."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD require contributors to group relevant "
+"changes in commits."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD encourage file formats where the changes "
+"within the files can be easily viewed and understood in the version control "
+"system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 13 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 15 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Make sure that all files required to understand the code, build and deploy "
+"are in the version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
+"use GitHub or refresh your skills."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 3 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 4 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 5 (paragraph)
+msgid ""
+"To develop better, more reliable and feature rich software, users need to be"
+" able to fix problems, add features, and address security issues of the "
+"shared [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 6 (paragraph)
+msgid ""
+"A shared digital infrastructure makes it easier to make collaborative "
+"contributions. The less effort it takes to make contributions that are "
+"accepted by the codebase, the more likely users are to become contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have a public issue tracker that accepts suggestions from "
+"anyone."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"There MUST be a way to report security issues for responsible disclosure "
+"over a closed channel."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST include instructions for how to report potentially "
+"security sensitive issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a closed channel for reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 12 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Just like for [reviews](require-review-of-contributions.md), make sure to "
+"respond to requests promptly."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Keep your managers informed of the time and resources you require to support"
+" other contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate communication channels for asking maintainers and"
+" stakeholders questions are easy to locate, for instance in the README."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate contact details are included in the metadata, for"
+" instance in the publiccode.yml file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
+msgid "order: 14 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
+msgid "criteria/findability"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 5 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
+msgid ""
+"The more findable a [codebase](../glossary.md#codebase) is, the more "
+"potential new collaborators will find it. Just publishing a codebase and "
+"hoping it is found does not work, instead proactiveness is needed."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
+msgid ""
+"A metadata description file increases discoverability. Well-written metadata"
+" containing a unique and persistent identifier, such as a Wikidata item or "
+"FSF software directory listing (thus being part of the semantic web), makes "
+"the codebase easier for people to refer, cite, disambiguate and discover "
+"through third party tools."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a short description that helps someone understand "
+"what the codebase is for or what it does."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by describing the "
+"problem it solves in natural language."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check that the codebase name is descriptive and free of puns."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of acronyms and abbreviations or that "
+"the acronyms or abbreviations in the name are more universally known than "
+"the longer forms."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of organizational branding, unless that"
+" organization is of the codebase community itself."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase repository has a short description of the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by the codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by using natural language, for instance, using the "
+"short description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as social media account descriptions."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Make sure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Search engine optimization, for instance adding a "
+"[sitemap](https://www.sitemaps.org/protocol.html)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as the repository description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Software Foundation."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
+msgid "order: 3 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/reusable-and-portable-codebases"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/create-reusable-and-portable-code"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
+msgid "Make the codebase reusable and portable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
+msgid ""
+"Creating reusable and portable [code](../glossary.md#code) enables policy "
+"makers, developers and designers to reuse what has been developed, test it, "
+"improve it and contribute those improvements back, leading to better "
+"quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
+msgid ""
+"Thoughtfully and purposefully designing a "
+"[codebase](../glossary.md#codebase) for reusability allows for the mission, "
+"vision and scope of the codebase to be shared by multiple parties. Codebases"
+" developed and used by multiple parties are more likely to benefit from a "
+"self-sustaining community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
+msgid ""
+"Organizing a codebase such that it is composed of well documented modules "
+"improves reusability and maintainability. A module is easier to reuse in "
+"[another context](../glossary.md#different-contexts) if its purpose is "
+"clearly documented."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
+msgid ""
+"Source code which does not rely on the situation-specific infrastructure of "
+"any contributor, vendor or deployment can be tested by any other "
+"contributor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase MUST be developed to be reusable in different contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed software or services for execution and understanding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The development of the codebase SHOULD be a collaboration between multiple "
+"parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Configuration SHOULD be used to make [source code](../glossary.md#source-"
+"code) adapt to context specific needs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Source code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The software SHOULD NOT require services or platforms available from only a "
+"single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"use the codebase and what that would entail."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed software or services."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"If the codebase is in early development before a production-ready release, "
+"then check for evidence of ambition to obtain collaborators."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Or if the codebase is very mature and stable with very infrequent fixes, "
+"patches, or contributions:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check for documented and budgeted commitments of collaboration."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Otherwise:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check that the codebase contributors are from multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the software can be deployed and run without services or "
+"platforms available from a single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Identify other organizations for your teams to collaborate with."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid "Make sure that your teams are collaborating with other teams."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
+msgid ""
+"Make sure that the codebase documentation describes the build-time and "
+"runtime dependencies. If your context requires deploying to proprietary "
+"platforms or using proprietary components, make sure that collaborators can "
+"develop, use, test, and deploy without them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
+msgid "order: 13 redirect_from:"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
+msgid "criteria/open-licenses"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 5 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 6 (paragraph)
+msgid ""
+"An open and well known license makes it possible for anyone to see the "
+"[source code](../glossary.md#source-code) in order to understand how it "
+"works, to use it freely and to contribute to the "
+"[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
+"emerge around the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
+msgid ""
+"Clearly indicating the license for each file within a codebase facilitates "
+"correct reuse and attribution of parts of a codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code and documentation MUST be licensed such that it may be "
+"freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid "All source code MUST be published with a license file."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Having multiple licenses for different types of source code and "
+"documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires source code to be "
+"[open source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their source code by "
+"publishing it under an open source license."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"When source code is being reused by the codebase, make sure that it has a "
+"license that is compatible with the license or licenses of the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
+msgid "order: 7 redirect_from:"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
+msgid "criteria/require-review"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 5 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 6 (paragraph)
+msgid ""
+"Peer-review of contributions is essential for [source "
+"code](../glossary.md#source-code) quality, reducing security risks and "
+"operational risks."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
+msgid ""
+"Requiring thorough review of contributions encourages a culture of making "
+"sure every contribution is of high quality, completeness and value. Source "
+"code review increases the chance of discovering and fixing potential bugs or"
+" mistakes before they are added to the [codebase](../glossary.md#codebase). "
+"Knowing that all source code was reviewed discourages a culture of blaming "
+"individuals, and encourages a culture of focusing on solutions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
+msgid ""
+"A [policy](../glossary.md#policy) of prompt reviews assures contributors of "
+"a guaranteed time for feedback or collaborative improvement, which increases"
+" both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"codebase MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews MUST include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"The review process SHOULD confirm that a contribution conforms to the "
+"standards, architecture and decisions set out in the codebase in order to "
+"pass review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the software and the tests of the "
+"codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check if guidelines for reviewers include instructions to review for "
+"conformance to standards, architecture and codebase guidelines."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check with reviewers if they run the software and tests during review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just source code, is "
+"reviewed."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make delivering great software a shared objective."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Try to respond to others' requests for review promptly, initially providing "
+"feedback about the concept of the change."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/)."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
+msgid "order: 15 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
+msgid "criteria/style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 5 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 6 (paragraph)
+msgid ""
+"Following a consistent and coherent style enables contributors in different "
+"environments to work together. Unifying vocabularies reduces friction in "
+"communication between contributors."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST use a coding or writing style "
+"guide, either the codebase community's own or an existing one referred to in"
+" the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The style guide SHOULD include expectations for inline comments and "
+"documentation for non-trivial sections."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"Including expectations for [understandable English](use-plain-english.md) in"
+" the style guide is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 12 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 16 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [source code](../glossary.md#source-code) contributions in "
+"order for them to be merged by the maintainers, including source, tests and "
+"documentation. Continually improve upon and expand this documentation with "
+"the aim of evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 3 (paragraph)
+msgid "order: 12 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 4 (unordered list)
+msgid "criteria/continuous-integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 5 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 6 (paragraph)
+msgid ""
+"Asynchronous collaboration is enabled by developers merging their work to a "
+"shared branch frequently, verified by automated tests. The more frequent the"
+" merging and the smaller the contribution, the easier it is to resolve merge"
+" conflicts."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 7 (paragraph)
+msgid ""
+"Automated testing of all functionality provides confidence that "
+"contributions are working as intended and have not introduced errors, and "
+"allows reviewers to focus on the structure and approach of the contribution."
+" The more focused the test, the easier it is to clearly identify and "
+"understand errors as they arise."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 8 (paragraph)
+msgid ""
+"Documenting a codebase's [continuous integration](../glossary.md#continuous-"
+"integration) workflow helps contributors understand the expectations of "
+"contributions. Continuous integration allows for an easier monitoring of the"
+" state of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"All functionality in the [source code](../glossary.md#source-code) MUST have"
+" automated tests."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the codebase."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have active contributors who can review contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Automated test results for contributions SHOULD be public."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing the software by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code coverage tools check that coverage is at 100% of "
+"the source code."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check that test results are viewable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check if source code coverage data is published."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Involve managers as well as developers and designers as early in the process"
+" as possible and keep them engaged throughout development of your policy."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure the source code reflects any changes to the policy (see [Maintain "
+"version control](maintain-version-control.md))."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Plan the work to integrate small parts very often instead of large parts "
+"less frequently."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers structure the work plan such that it can be integrated as "
+"small increments."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Structure source code written to handle conditions which are difficult to "
+"create in a test environment in such a way that the conditions can be "
+"simulated during testing. Forms of resource exhaustion such as running out "
+"of storage space and memory allocation failure are typical examples of "
+"difficult to create conditions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 3 (paragraph)
+msgid "order: 11 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 4 (unordered list)
+msgid "criteria/open-standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 5 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 6 (paragraph)
+msgid ""
+"[Open standards](../glossary.md#open-standard) guarantee access to the "
+"knowledge required to use and contribute to the "
+"[codebase](../glossary.md#codebase). They enable interoperability between "
+"systems and reduce the risk of vendor lock-in. Open standards which are "
+"unambiguous allow for independent development of either side of data "
+"exchange."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"For features of the codebase that facilitate the exchange of data the "
+"codebase MUST use an open standard that meets the [Open Source Initiative "
+"Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Open standards that are machine testable SHOULD be preferred over open "
+"standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Non-open standards that are machine testable SHOULD be preferred over non-"
+"open standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 14 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in [source "
+"code](../glossary.md#source-code) reviews."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 18 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 3 (paragraph)
+msgid "order: 10 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 4 (unordered list)
+msgid "criteria/understandable-english-first"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 5 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 6 (paragraph)
+msgid ""
+"English is the <i>de facto</i> language of collaboration in software "
+"development."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 7 (paragraph)
+msgid ""
+"Public sector information needs to be accessible to all its constituents. "
+"Plain and simple language makes the [code](../glossary.md#code) and what it "
+"does easier to understand for a wider variety of people."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 8 (paragraph)
+msgid ""
+"Translations further increase the possible reach of a "
+"[codebase](../glossary.md#codebase). Language that is easy to understand "
+"lowers the cost of creating and maintaining translations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid "All codebase documentation MUST be in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All [source code](../glossary.md#source-code) MUST be in English, except "
+"where [policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 14 (unordered list)
+msgid ""
+"Frequently test with other managers, developers and designers in the process"
+" if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Frequently test with policy makers and managers if they understand what you "
+"are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
+"readable and understandable."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"The[European Union accessibility directive](https://ec.europa.eu/digital-"
+"single-market/en/web-accessibility) by the European Commission, is an "
+"example of regulation requiring high accessibility."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 3 (paragraph)
+msgid "order: 4 redirect_from:"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 4 (unordered list)
+msgid "criteria/open-to-contributions"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 5 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 6 (paragraph)
+msgid ""
+"The atmosphere in a [codebase](../glossary.md#codebase) community helps "
+"users decide to use one codebase over another. Welcoming anyone as a "
+"contributor enables the community to grow and sustain itself over time. A "
+"community where contributors have clear ways to influence codebase and "
+"community goals and progress is less likely to split and end up in diverging"
+" communities. Newcomers need to understand and trust the codebase "
+"community’s governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST allow anyone to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The contribution guidelines SHOULD document who is expected to cover the "
+"costs of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Check that contributing guidelines cover who is expected to cover the costs "
+"of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If needed, make sure you have allocated budget for the contributions review "
+"process as agreed by the codebase community."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid ""
+"Communicate clearly to contributors what they need to do make sure their "
+"contribution can be integrated."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./docs/printing.md:block 1 (header)
+msgid "Printing"
+msgstr ""
+
+#: ./docs/printing.md:block 3 (paragraph)
+msgid ""
+"The printed Standard for Public Code is printed by Reclameland. This guide "
+"tries to provide the relevant information to print it there or somewhere "
+"else."
+msgstr ""
+
+#: ./docs/printing.md:block 4 (paragraph)
+msgid ""
+"Details, mostly in order they are on the Reclameland page with the Dutch if "
+"necessary:"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Form: Softcover book ([Reclameland product "
+"page](https://www.reclameland.nl/drukken/softcover-boeken))"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Format: A4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Portrait or landscape: Portrait (Staand)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing inside: 4/4 dual sided full color"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Inside material: 90 grams biotop"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover: 350 grams cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing cover: 4/0 one sided full cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover treatment: one sided matt foliated (Enke)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
+" multiple of 4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Individually sealed: no"
+msgstr ""
+
+#: ./docs/printing.md:block 6 (paragraph)
+msgid ""
+"When these details are chosen, the cover and insides are uploaded and the "
+"order is placed payment can happen (payment ahead) after which printing "
+"starts."
+msgstr ""
+
+#: ./docs/releasing.md:block 1 (header)
+msgid "Releasing a new version of the Standard for public code"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Review state of the 'develop' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure all changes intended for release are merged"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Invite a proofread of the current state of the branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If new dashes are introduced, check if the language can be simplified to "
+"remove them in favor of more simple sentences. If a complex sentence is "
+"needed, see if the dash can be replaced with other punctuation. If a dash is"
+" truly the best expression of ideas, then follow the [Chicago Manual of "
+"Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create a release branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update the new release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update releaseDate in `publiccode.yml`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Perform extra pass on diff to the 'main' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"run `script/generate-review-template.sh` and commit updated `docs/review-"
+"template.html`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"update `docs/standard-for-public-code.md` with the new text from the review "
+"template, updating any status changes as a result"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reread any section or paragraph to ensure wording changes still fit the "
+"whole and do not contain grammar or spelling errors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
+" `script/ensure-font.sh`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure no link collisions exist"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Check the page breaks, possibly removing or adding page-break CSS, for "
+"example: `<p style=\"page-break-after: always;\"></p>`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "If needed, commit fixes and repeat extra pass"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push branch, open a pull request to the 'main' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Request review from multiple reviewers, especially a proofreader"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reviewers will create issues for shortcomings found which would not prevent "
+"release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If needed for release, reviewers may create pull requests to resolve issues"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Re-request reviews if additional pull requests are merged into release "
+"branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Run the to-archive-org.sh script"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Once reviews are complete, merge to 'main'"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create GitHub release with the release notes and version number"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Switch to the 'main' branch, `git pull` and `git status`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git tag $MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Trigger a rebuild of gh-pages"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Open a pull request from this branch to `main`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Approve and merge PR (containing empty commit)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update 'develop' with a merge from 'main'"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "[Send the files for print to the printer](printing.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Cover file"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Inside pages PDF"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ping [translation](https://github.com/publiccodenet/community-translations-"
+"standard) contributors"
+msgstr ""
+
+#: ./docs/roadmap.md:block 1 (header)
+msgid "Roadmap"
+msgstr ""
+
+#: ./docs/roadmap.md:block 3 (paragraph)
+msgid "Last updated: 2023-03-08"
+msgstr ""
+
+#: ./docs/roadmap.md:block 4 (paragraph)
+msgid ""
+"This document intends to shed light on the current development plans of the "
+"team. Plans change constantly as new information is absorbed by the team."
+msgstr ""
+
+#: ./docs/roadmap.md:block 5 (paragraph)
+msgid ""
+"Codebase stewards review the roadmap monthly as part of our [backlog pruning"
+" session](https://about.publiccode.net/activities/standard-"
+"maintenance/backlog-pruning.html)."
+msgstr ""
+
+#: ./docs/roadmap.md:block 6 (header)
+msgid "Current work"
+msgstr ""
+
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "As far as possible, make the standard Standard-compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 8 (header)
+msgid "Near term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Separate executive summary"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid ""
+"Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
+" issue #208"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Possibly: add in the illustrations for each criterion"
+msgstr ""
+
+#: ./docs/roadmap.md:block 10 (header)
+msgid "Longer term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Certification badges"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid ""
+"Add to README and index.md information (and eventually statistics) on "
+"adoption and use (issue #438)"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Physical paper checklist"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Becoming validated by multiple codebases"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Release version 1.0.0 after a few codebases are compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Linkable requirements"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "New cover art"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Register for ISBN"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "List with an on-demand book printing service"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "QR codes for external links in print version"
+msgstr ""
+
+#: ./foreword.md:block 3 (paragraph)
+msgid "redirect_from:"
+msgstr ""
+
+#: ./foreword.md:block 4 (unordered list)
+msgid "introduction"
+msgstr ""
+
+#: ./foreword.md:block 5 (header)
+msgid "Foreword"
+msgstr ""
+
+#: ./foreword.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that support public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./foreword.md:block 7 (paragraph)
+msgid ""
+"Anyone developing public-purpose software or policy can use this standard to"
+" work towards higher quality public services that are more cost effective, "
+"with less risk and more control."
+msgstr ""
+
+#: ./foreword.md:block 8 (paragraph)
+msgid ""
+"This foreword introduces the term public code and explains why this is "
+"important."
+msgstr ""
+
+#: ./foreword.md:block 9 (header)
+msgid "Definition of public code"
+msgstr ""
+
+#: ./foreword.md:block 10 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines. It "
+"encompasses the software built to operate with and as public infrastructure,"
+" along with the arrangements for its production. Public code is explicitly "
+"distinct from regular software because it operates under fundamentally "
+"different circumstances and expectations."
+msgstr ""
+
+#: ./foreword.md:block 11 (header)
+msgid "Reasons for public code"
+msgstr ""
+
+#: ./foreword.md:block 12 (paragraph)
+msgid "There are many reasons for why public code is relevant now."
+msgstr ""
+
+#: ./foreword.md:block 13 (header)
+msgid "Software code == legal code"
+msgstr ""
+
+#: ./foreword.md:block 14 (paragraph)
+msgid "Software is public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 15 (paragraph)
+msgid ""
+"In the 21st century, software can be considered vital public infrastructure."
+" It is increasingly not just the expression of existing policy but the "
+"originator of new policy, for example where algorithms decide which "
+"districts need extra social services or policing."
+msgstr ""
+
+#: ./foreword.md:block 16 (paragraph)
+msgid ""
+"Software mechanics, algorithms and data collection have become key elements "
+"in the execution of public policies. Computer code now executes policies "
+"that have been codified in legal code through democratic procedures. Both "
+"forms of code set conditions for society to function according to "
+"democratically set public values, the latter executed by humans, the former "
+"by machines. In other words, software code has increasingly started to equal"
+" legal code."
+msgstr ""
+
+#: ./foreword.md:block 17 (paragraph)
+msgid ""
+"Software should therefore be subject to the principles of democratic "
+"governance."
+msgstr ""
+
+#: ./foreword.md:block 18 (header)
+msgid "Traditional public software procurement"
+msgstr ""
+
+#: ./foreword.md:block 19 (paragraph)
+msgid ""
+"Current public software production methods have not served public service "
+"delivery very well."
+msgstr ""
+
+#: ./foreword.md:block 20 (paragraph)
+msgid ""
+"In the last decade, public organizations that purchased complete software "
+"solutions have sometimes been surprised to discover that they:"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"can’t change their software to reflect changing policy or take advantage of "
+"new technology"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"don’t have access to their data as it's locked into proprietary systems"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid "are asked to pay ever increasing license fees"
+msgstr ""
+
+#: ./foreword.md:block 22 (header)
+msgid "Technological sovereignty and democratic accountability"
+msgstr ""
+
+#: ./foreword.md:block 23 (paragraph)
+msgid "Public institutions, civil servants and residents deserve better."
+msgstr ""
+
+#: ./foreword.md:block 24 (paragraph)
+msgid ""
+"We believe the software that runs our society can no longer be a black box, "
+"controlled by outside companies that keep the underlying logic on which "
+"their software operates hidden in proprietary codebases. Instead, "
+"governments and the people they serve need technological sovereignty. This "
+"allows them to set and control the functioning of public software, just like"
+" they are able to set and control policy that is legally formulated in laws."
+" Citizens and civil society actors need this software to be transparent and "
+"accountable."
+msgstr ""
+
+#: ./foreword.md:block 25 (paragraph)
+msgid ""
+"The design of software as essential civic infrastructure should honor "
+"digital citizens’ rights."
+msgstr ""
+
+#: ./foreword.md:block 26 (header)
+msgid "Designing truly public software"
+msgstr ""
+
+#: ./foreword.md:block 27 (paragraph)
+msgid ""
+"Public code is at the core of modern public institutions, shapes the work of"
+" civil servants and affects the lives of almost all residents."
+msgstr ""
+
+#: ./foreword.md:block 28 (paragraph)
+msgid "Public software must therefore be:"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "transparent"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "accountable"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "understandable for its constituents"
+msgstr ""
+
+#: ./foreword.md:block 30 (paragraph)
+msgid ""
+"It must reflect the values of the society it serves, for example by being "
+"inclusive and non-discriminatory."
+msgstr ""
+
+#: ./foreword.md:block 31 (paragraph)
+msgid ""
+"Most proprietary software systems currently used by public organizations do "
+"not meet these requirements. Public code does."
+msgstr ""
+
+#: ./foreword.md:block 32 (header)
+msgid "Values of public code"
+msgstr ""
+
+#: ./foreword.md:block 33 (paragraph)
+msgid "We consider public code to have these core values:"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Inclusive"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Usable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Open"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Legible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accountable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accessible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Sustainable"
+msgstr ""
+
+#: ./foreword.md:block 35 (header)
+msgid "How public code works"
+msgstr ""
+
+#: ./foreword.md:block 36 (paragraph)
+msgid ""
+"Public code is open source software meant for fulfilling the essential role "
+"of public organizations. Through use, other administrations contribute back "
+"to the software, so that its development and maintenance become truly "
+"collaborative."
+msgstr ""
+
+#: ./foreword.md:block 37 (paragraph)
+msgid "Being open unlocks many other things."
+msgstr ""
+
+#: ./foreword.md:block 38 (paragraph)
+msgid ""
+"Local responsibility and democratic accountability are ensured when a public"
+" organization implements and maintains their own public code. By being open "
+"and with a broader contributor base, the software is more secure as it "
+"benefits from many eyes spotting potential flaws. Many contributors share "
+"the maintenance work to keep it functional and modern, which reduces future "
+"technical debt. The shared workload is more sustainable now and in the "
+"future. Its openness makes both the code and its data more easily adaptable "
+"in the future. The code will be easier to retool, repurpose or retire. This "
+"all results in lower risk public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 39 (paragraph)
+msgid ""
+"This pooling of resources lets public administrations give extra attention "
+"to how to customize the software so it works best in each local context, "
+"creating better user experiences for their end users (residents or "
+"citizens)."
+msgstr ""
+
+#: ./foreword.md:block 40 (header)
+msgid "Economics of public code"
+msgstr ""
+
+#: ./foreword.md:block 41 (paragraph)
+msgid ""
+"Public code offers a better economic model for public organizations as well "
+"as for commercial companies. It's an alternative to traditional software "
+"procurement which increases local control and economic opportunity."
+msgstr ""
+
+#: ./foreword.md:block 42 (paragraph)
+msgid ""
+"Designed from the start to be open, adaptable and with data portability, it "
+"can be developed by in-house staff or trusted vendors. Because the code is "
+"open, the public administration can change vendors if they need to. Open "
+"code increases opportunities for public learning and scrutiny, allowing the "
+"public administration to procure smaller contracts. Smaller procurements are"
+" easier for local small and medium enterprises to bid upon. Public "
+"administrations can use their own software purchasing to stimulate "
+"innovation and competition in their local economy."
+msgstr ""
+
+#: ./foreword.md:block 43 (paragraph)
+msgid ""
+"This can be seen as investment leading to future economic growth. More "
+"vendors will be necessary due to growing technology demand."
+msgstr ""
+
+#: ./foreword.md:block 44 (header)
+msgid "Procuring public code"
+msgstr ""
+
+#: ./foreword.md:block 45 (paragraph)
+msgid ""
+"Public code can be used and developed by permanent in-house development "
+"teams, contractors or outsourced suppliers. Vendors to public organizations "
+"can include public code in their bids for contracts."
+msgstr ""
+
+#: ./foreword.md:block 46 (paragraph)
+msgid ""
+"To use existing public code, you need to specify in your budget and project "
+"design that your new solution will use that codebase. To encourage an "
+"innovative approach to adapting the public code to your context, you could "
+"describe the service or outcome in your contract."
+msgstr ""
+
+#: ./foreword.md:block 47 (header)
+msgid "The goals for the Standard for Public Code"
+msgstr ""
+
+#: ./foreword.md:block 48 (paragraph)
+msgid ""
+"This Standard supports developers, designers, managers and public policy "
+"makers to:"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop high quality software and policy for better public service delivery"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop codebases that can be reused across contexts and collaboratively "
+"maintained"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "reduce technical debt and project failure rate"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"have more granular control over, and ability to make decisions about, their "
+"IT systems"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "improve vendor relationships with a better economic model"
+msgstr ""
+
+#: ./foreword.md:block 50 (paragraph)
+msgid ""
+"Potential users of codebases tested against the Standard for Public Code can"
+" expect them to be highly reusable, easily maintainable and of high quality."
+msgstr ""
+
+#: ./foreword.md:block 51 (paragraph)
+msgid "The Standard for Public Code does this by:"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "setting out a common terminology for public code development"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "establishing measures to help develop high quality public code"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid ""
+"providing guidance on how to fulfill its criteria and operationalize "
+"compliance"
+msgstr ""
+
+#: ./foreword.md:block 53 (paragraph)
+msgid ""
+"The Standard for Public Code is meant to be time and technology independent."
+msgstr ""
+
+#: ./foreword.md:block 54 (header)
+msgid "Who this is for"
+msgstr ""
+
+#: ./foreword.md:block 55 (paragraph)
+msgid ""
+"The Standard for Public Code is for the people who create and reuse public "
+"code:"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "public policy makers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "business and project managers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "developers and designers"
+msgstr ""
+
+#: ./foreword.md:block 57 (paragraph)
+msgid "These people work at:"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid "institutions, organizations and administrations in the public sector"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid ""
+"consultancies and vendors of information technology and policy services to "
+"public organizations"
+msgstr ""
+
+#: ./foreword.md:block 59 (paragraph)
+msgid ""
+"It is not aimed at public organizations' end users (residents or citizens), "
+"journalists or academics."
+msgstr ""
+
+#: ./foreword.md:block 61 (unordered list)
+msgid ""
+"[\"Modernising Public Infrastructure with Free Software\" white "
+"paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
+"Software.pdf) by the Free Software Foundation Europe."
+msgstr ""
+
+#: ./foreword.md:block 62 (header)
+msgid "Videos on public code"
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Collaborative Code is the Future of Cities @ DecidimFest "
+"2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
+"the background behind the Foundation for Public Code."
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Public Money? Public Code! - Panel @ Nextcloud Conference "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
+"procurement, law and more."
+msgstr ""
+
+#: ./foreword.md:block 64 (header)
+msgid "Get involved"
+msgstr ""
+
+#: ./foreword.md:block 65 (paragraph)
+msgid ""
+"This standard is a living document. [Read our contributor "
+"guide](/CONTRIBUTING.md) to learn how you can make it better."
+msgstr ""
+
+#: ./foreword.md:block 66 (header)
+msgid "Contact"
+msgstr ""
+
+#: ./foreword.md:block 67 (paragraph)
+msgid ""
+"For questions and more information about the Foundation for Public Code you "
+"can find us at [our website](https://publiccode.net/), email us at "
+"info@publiccode.net, or call us at +31 20 2 444 500."
+msgstr ""
+
+#: ./glossary.md:block 3 (header)
+msgid "Glossary"
+msgstr ""
+
+#: ./glossary.md:block 4 (header)
+msgid "Code"
+msgstr ""
+
+#: ./glossary.md:block 5 (paragraph)
+msgid ""
+"Any explicitly described system of rules. This includes laws, policy and "
+"ordinances, as well as source code that is used to build software. Both of "
+"these are rules, some executed by humans and others by machines."
+msgstr ""
+
+#: ./glossary.md:block 6 (header)
+msgid "Codebase"
+msgstr ""
+
+#: ./glossary.md:block 7 (paragraph)
+msgid ""
+"Any discrete package of code (both source and policy), the tests and the "
+"documentation required to implement a piece of policy or software."
+msgstr ""
+
+#: ./glossary.md:block 8 (paragraph)
+msgid "This can be, for example, a document or a version-control repository."
+msgstr ""
+
+#: ./glossary.md:block 9 (header)
+msgid "Continuous integration"
+msgstr ""
+
+#: ./glossary.md:block 10 (paragraph)
+msgid ""
+"In software engineering, continuous integration (CI) is the practice of "
+"merging all developers' working copies to a development branch of a codebase"
+" as frequently as reasonable."
+msgstr ""
+
+#: ./glossary.md:block 11 (header)
+msgid "Different contexts"
+msgstr ""
+
+#: ./glossary.md:block 12 (paragraph)
+msgid ""
+"Two contexts are different if they are different public organizations or "
+"different departments for which there is not one decision maker that could "
+"make collaboration happen naturally."
+msgstr ""
+
+#: ./glossary.md:block 13 (header)
+msgid "General public"
+msgstr ""
+
+#: ./glossary.md:block 14 (paragraph)
+msgid ""
+"The public at large: end users of the code and the services based upon it."
+msgstr ""
+
+#: ./glossary.md:block 15 (paragraph)
+msgid ""
+"For example, a city's residents are considered end users of a city's "
+"services and of all code that powers these services."
+msgstr ""
+
+#: ./glossary.md:block 16 (header)
+msgid "Open source"
+msgstr ""
+
+#: ./glossary.md:block 17 (paragraph)
+msgid ""
+"Open source is defined by the Open Source Initiative in their [Open Source "
+"Definition](https://opensource.org/osd-annotated)."
+msgstr ""
+
+#: ./glossary.md:block 18 (header)
+msgid "Open standard"
+msgstr ""
+
+#: ./glossary.md:block 19 (paragraph)
+msgid ""
+"An open standard is any standard that meets the Open Source Initiative's "
+"[Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./glossary.md:block 20 (header)
+msgid "Policy"
+msgstr ""
+
+#: ./glossary.md:block 21 (paragraph)
+msgid ""
+"A policy is a deliberate system of principles to guide decisions and achieve"
+" rational outcomes. A policy is a statement of intent, and is implemented as"
+" a procedure or protocol. Policies are generally adopted by a governance "
+"body within an organization. Policies can assist in both subjective and "
+"objective decision making."
+msgstr ""
+
+#: ./glossary.md:block 22 (paragraph)
+msgid ""
+"Public policy is the process by which governments translate their political "
+"vision into programs and actions to deliver outcomes."
+msgstr ""
+
+#: ./glossary.md:block 23 (paragraph)
+msgid ""
+"At the national level, policy and legislation (the law) are usually "
+"separate. The distinction is often more blurred in local government."
+msgstr ""
+
+#: ./glossary.md:block 24 (paragraph)
+msgid ""
+"In the Standard the word 'policy' refers to policy created and adopted by "
+"public organizations such as governments and municipalities."
+msgstr ""
+
+#: ./glossary.md:block 25 (header)
+msgid "Public code"
+msgstr ""
+
+#: ./glossary.md:block 26 (paragraph)
+msgid ""
+"Public code is open source software developed by public organizations, "
+"together with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./glossary.md:block 27 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines."
+msgstr ""
+
+#: ./glossary.md:block 28 (paragraph)
+msgid ""
+"Public code serves the public interest, is open, legible, accountable, "
+"accessible and sustainable."
+msgstr ""
+
+#: ./glossary.md:block 29 (paragraph)
+msgid ""
+"By developing public code independently from but still implementable in the "
+"local context for which it was developed, as well as documenting the "
+"development process openly, public code can provide a building block for "
+"others to:"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "re-implement in their local context"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "take as a starting point to continue development"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "use as a basis for learning"
+msgstr ""
+
+#: ./glossary.md:block 31 (paragraph)
+msgid ""
+"To facilitate reuse, public code is either released into the public domain "
+"or licensed with an open license that permits others to view and reuse the "
+"work freely and to produce derivative works."
+msgstr ""
+
+#: ./glossary.md:block 32 (header)
+msgid "Repository"
+msgstr ""
+
+#: ./glossary.md:block 33 (paragraph)
+msgid ""
+"A repository is a storage location used by version control tools for files "
+"and metadata of a codebase. Repositories allow multiple contributors to work"
+" on the same set of files. Repositories are able to store multiple versions "
+"of sets of files."
+msgstr ""
+
+#: ./glossary.md:block 34 (header)
+msgid "Source Code"
+msgstr ""
+
+#: ./glossary.md:block 35 (paragraph)
+msgid ""
+"Human readable text of a computer program which can be translated into "
+"machine instructions."
+msgstr ""
+
+#: ./glossary.md:block 36 (header)
+msgid "Version control"
+msgstr ""
+
+#: ./glossary.md:block 37 (paragraph)
+msgid ""
+"Version control is the management of changes to source code and the files "
+"associated with it. Changes are usually identified by a code, termed the "
+"*revision number* (or similar). Each revision is associated with the time it"
+" was made and the person making the change, thus making it easier to retrace"
+" the evolution of the code. Revision control systems can be used to compare "
+"different versions with each other and to see how content has changed over "
+"time."
+msgstr ""
+
+#: ./index.md:block 3 (header)
+msgid "toc: false"
+msgstr ""
+
+#: ./index.md:block 4 (header)
+msgid "Guidance for government open source collaboration"
+msgstr ""
+
+#: ./index.md:block 5 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that supports public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./index.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code provides guidance to public organizations "
+"building their own open source solutions to enable successful future "
+"collaboration and reuse by similar organizations in the public sector in "
+"other places. It includes advice for policy makers, government managers, "
+"developers and vendors. The Standard for Public Code supports the "
+"collaborative creation of codebases that are usable, open, legible, "
+"accountable, accessible and sustainable. It is meant to be applicable to "
+"codebases for all levels of government, from supranational to municipal."
+msgstr ""
+
+#: ./index.md:block 7 (paragraph)
+msgid ""
+"The Standard for Public Code defines ‘[public code](glossary.md#public-"
+"code)’ as open source software developed by public organizations, together "
+"with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./index.md:block 8 (paragraph)
+msgid ""
+"The criteria of the Standard for Public Code are aligned with guidelines and"
+" best practices of open source software development."
+msgstr ""
+
+#: ./index.md:block 9 (paragraph)
+msgid ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} Additional"
+" context and background can be found in the [foreword](foreword.md). {% "
+"endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 10 (header)
+msgid "Contents"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Glossary](glossary.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[Criteria](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for"
+" page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Authors](AUTHORS.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Contributing guide](CONTRIBUTING.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Governance](GOVERNANCE.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Version history](CHANGELOG.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[License](license.html)"
+msgstr ""
+
+#: ./index.md:block 12 (header)
+msgid "Community calls"
+msgstr ""
+
+#: ./index.md:block 13 (paragraph)
+msgid ""
+"We usually have a community call on the first Thursday of the month at 15:00"
+" (CET/CEST). [The agenda](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code) is updated roughly a week before the call. It is "
+"possible to [sign "
+"up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
+" to get a call invitation emailed to you."
+msgstr ""
+
+#: ./index.md:block 14 (header)
+msgid "Other resources"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"Unofficial [community translations of the "
+"Standard](https://publiccodenet.github.io/community-translations-standard/) "
+"in other languages"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard compliance self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
+"public sector open source codebases"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard criteria "
+"checklist](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
+"template.html) used by Foundation for Public Code stewards for codebase "
+"review"
+msgstr ""
+
+#: ./readers-guide.md:block 3 (header)
+msgid "Readers guide"
+msgstr ""
+
+#: ./readers-guide.md:block 4 (paragraph)
+msgid ""
+"The Standard describes a number of criteria. All criteria have consistent "
+"sections that make it clear how to create great public code."
+msgstr ""
+
+#: ./readers-guide.md:block 5 (paragraph)
+msgid ""
+"References to \"policy makers\", \"managers\", and \"developers and "
+"designers\" apply to anyone performing duties associated with these roles, "
+"regardless of their job title. It is common for individuals to have duties "
+"which span multiple roles."
+msgstr ""
+
+#: ./readers-guide.md:block 6 (paragraph)
+msgid ""
+"Below is a brief explanation of each of these sections and how they are used"
+" within the criteria of the Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 7 (header)
+msgid "Introduction"
+msgstr ""
+
+#: ./readers-guide.md:block 8 (paragraph)
+msgid ""
+"This section explains what the criterion aims to achieve and why it is "
+"important for a codebase's users and contributors."
+msgstr ""
+
+#: ./readers-guide.md:block 10 (paragraph)
+msgid ""
+"This section lists what needs to be done in order to comply with the "
+"standard."
+msgstr ""
+
+#: ./readers-guide.md:block 11 (paragraph)
+msgid ""
+"The following keywords in this document are to be interpreted as described "
+"in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "REQUIRED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "RECOMMENDED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MAY"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "OPTIONAL"
+msgstr ""
+
+#: ./readers-guide.md:block 14 (paragraph)
+msgid ""
+"This section offers actions you can take to see if a contribution is "
+"compliant with the Standard. This is key if you want to operationalize the "
+"Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 15 (paragraph)
+msgid ""
+"We've tried to word it so that someone who is not intimately acquainted with"
+" the subject matter can still do a basic check for compliance."
+msgstr ""
+
+#: ./readers-guide.md:block 17 (paragraph)
+msgid ""
+"This section tries to specifically speak to policy makers by offering them "
+"concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 18 (paragraph)
+msgid ""
+"Public policy makers set the priorities and goals of projects and may be "
+"less technologically experienced."
+msgstr ""
+
+#: ./readers-guide.md:block 20 (paragraph)
+msgid ""
+"This section tries to specifically speak to managers by offering concrete "
+"actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 21 (paragraph)
+msgid ""
+"Managers are responsible for on-time project delivery, stakeholder "
+"management and continued delivery of the service. For this they are wholly "
+"reliant on both policy makers as well as developers and designers. They need"
+" to create the right culture, line up the right resources and provide the "
+"right structures to deliver great services."
+msgstr ""
+
+#: ./readers-guide.md:block 23 (paragraph)
+msgid ""
+"This section tries to specifically speak to developers and designers by "
+"offering them concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 24 (paragraph)
+msgid ""
+"Developers are usually more technically aligned and have more impact on the "
+"delivery of services than the previous groups."
+msgstr ""
+
+#: ./readers-guide.md:block 25 (header)
+msgid "Limitation of scope"
+msgstr ""
+
+#: ./readers-guide.md:block 26 (paragraph)
+msgid ""
+"The Standard for Public Code is not meant to cover individual "
+"implementations of a codebase. This means the standard does not tell "
+"implementers how to comply with their organization's local technical "
+"infrastructure or legal framework."
+msgstr ""
+
+#: ./readers-guide.md:block 27 (paragraph)
+msgid ""
+"Also, while the Standard for Public Code refers to several standards and has"
+" considerable overlap with others, its purpose is to enable collaboration. "
+"Therefore, it does not aim to replace quality standards, like the ISO 25000 "
+"series, or those focusing on security, like the [OpenSSF Best Practices "
+"Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
+"synergize well with them."
+msgstr ""
+
+#: ./readers-guide.md:block 28 (paragraph)
+msgid ""
+"And while the purpose includes enabling collaboration, it will not guarantee"
+" that a community will spring into existence. That still requires "
+"proactiveness and ambition beyond making the codebase collaboration ready."
+msgstr ""

From 2b146ccd55a9e386d07f9873d12de10d97a887e3 Mon Sep 17 00:00:00 2001
From: Tommy JIang <baptist333@yahoo.com.tw>
Date: Sat, 29 Jul 2023 14:30:15 +0000
Subject: [PATCH 35/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 0.2% (3 of 1023 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 28 +++++++++++++++++++------
 1 file changed, 22 insertions(+), 6 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 46615c34..5dc64b77 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -1,10 +1,26 @@
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2023-07-30 22:44+0800\n"
+"PO-Revision-Date: 2023-07-30 14:44+0000\n"
+"Last-Translator: Tommy JIang <baptist333@yahoo.com.tw>\n"
+"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
+"standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
+"Language: zh_Hant\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: ENCODING\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Generator: Weblate 4.18.2\n"
+
 #
-msgid ""
-msgstr ""
 
 #: ./404.md:block 1 (header)
+#, fuzzy
 msgid "SPDX-License-Identifier: CC0-1.0"
-msgstr ""
+msgstr "SPDX-License-Identifier: CC0-1.0"
 
 #: ./404.md:block 2 (header)
 msgid ""
@@ -185,7 +201,7 @@ msgstr ""
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
-msgstr ""
+msgstr "CC Zero v1.0 Universal授權"
 
 #: ./CC0-1.0.md:block 6 (paragraph)
 msgid ""
@@ -5069,7 +5085,7 @@ msgstr ""
 
 #: ./foreword.md:block 66 (header)
 msgid "Contact"
-msgstr ""
+msgstr "聯絡方式"
 
 #: ./foreword.md:block 67 (paragraph)
 msgid ""
@@ -5329,7 +5345,7 @@ msgstr ""
 
 #: ./index.md:block 10 (header)
 msgid "Contents"
-msgstr ""
+msgstr "內容"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"

From 72ea7b19efdd6ce96fcc148bb69f0e50a188edc4 Mon Sep 17 00:00:00 2001
From: Tommy JIang <baptist333@yahoo.com.tw>
Date: Mon, 31 Jul 2023 01:31:23 +0000
Subject: [PATCH 36/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 88.0% (901 of 1023 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 2197 ++++++++++++++---------
 1 file changed, 1378 insertions(+), 819 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 5dc64b77..20c0421d 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -1,33 +1,35 @@
-#, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-07-30 14:44+0000\n"
+"PO-Revision-Date: 2023-08-06 17:44+0000\n"
 "Last-Translator: Tommy JIang <baptist333@yahoo.com.tw>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: ENCODING\n"
+"Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 "X-Generator: Weblate 4.18.2\n"
 
 #
-
 #: ./404.md:block 1 (header)
 #, fuzzy
 msgid "SPDX-License-Identifier: CC0-1.0"
 msgstr "SPDX-License-Identifier: CC0-1.0"
 
 #: ./404.md:block 2 (header)
+#, fuzzy
 msgid ""
 "SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
+"publiccode.net/AUTHORS"
 
 #: ./404.md:block 3 (header)
 msgid ""
@@ -35,18 +37,21 @@ msgid ""
 "title: Page not found\n"
 "toc: false"
 msgstr ""
+"版型：預設\n"
+"標題：找不到網頁\n"
+"目錄：否"
 
 #: ./404.md:block 4 (header)
 msgid "404 Not Found"
-msgstr ""
+msgstr "404找不到網頁"
 
 #: ./404.md:block 5 (paragraph)
 msgid "If you typed the web address, check it is correct."
-msgstr ""
+msgstr "如果您手動輸入網址，請確認網址是否正確。"
 
 #: ./404.md:block 6 (paragraph)
 msgid "If you pasted the web address, check you copied the entire address."
-msgstr ""
+msgstr "如果您複製貼上此網址，請確認是否有複製到完整的網址。"
 
 #: ./404.md:block 7 (paragraph)
 msgid ""
@@ -54,93 +59,106 @@ msgid ""
 "[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
 "able to help you out, as well as correct our mistake."
 msgstr ""
+"若網址正確或是您按下連結或按鈕，請寫信給 "
+"[公共程式基金會人員](mailto:info@publiccode."
+"net)，讓我們能夠協助您，並且修正我們的錯誤。"
 
 #: ./AUTHORS.md:block 2 (header)
+#, fuzzy
 msgid ""
 "SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
+"publiccode.net/AUTHORS"
 
 #: ./AUTHORS.md:block 3 (header)
 msgid "Authors"
-msgstr ""
+msgstr "作者群"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
-msgstr ""
+msgstr "Alba Roza，[公共程式基金會](https://publiccode.net/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Arnout Engelen"
-msgstr ""
+msgstr "Arnout Engelen"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Arnout Schuijff, The Foundation for Public Code"
-msgstr ""
+msgstr "Arnout Schuijff，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
-msgstr ""
+msgstr "唐鳳，[digitalminister.tw](https://digitalminister.tw/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Ben Cerveny, The Foundation for Public Code"
-msgstr ""
+msgstr "Ben Cerveny， 公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Bert Spaan"
-msgstr ""
+msgstr "Bert Spaan"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Boris van Hoytema, The Foundation for Public Code"
-msgstr ""
+msgstr "Boris van Hoytema，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Charlotte Heikendorf"
-msgstr ""
+msgstr "Charlotte Heikendorf"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Claus Mullie, The Foundation for Public Code"
-msgstr ""
+msgstr "Claus Mullie，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "David Barberi"
-msgstr ""
+msgstr "David Barberi"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Edo Plantinga, [Code For NL](https://codefor.nl/)"
-msgstr ""
+msgstr "Edo Plantinga，[Code For NL](https://codefor.nl/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Elena Findley-de Regt, The Foundation for Public Code"
-msgstr ""
+msgstr "Elena Findley-de Regt，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Eric Herman, The Foundation for Public Code"
-msgstr ""
+msgstr "Eric Herman，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Felix Faassen, The Foundation for Public Code"
-msgstr ""
+msgstr "Felix Faassen，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Floris Deerenberg"
-msgstr ""
+msgstr "Floris Deerenberg"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Jan Ainali, The Foundation for Public Code"
-msgstr ""
+msgstr "Jan Ainali，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Johan Groenen, Code For NL"
-msgstr ""
+msgstr "Johan Groenen，荷蘭程式碼社群"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Marcus Klaas de Vries"
-msgstr ""
+msgstr "Marcus Klaas de Vries"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)"
-msgstr ""
+msgstr "Mark van der Net，[阿姆斯特丹市政府](https://www.amsterdam.nl/en/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid ""
@@ -148,56 +166,65 @@ msgid ""
 "(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
 "Creative Industries, Lectorate of Play & Civic Media"
 msgstr ""
+"Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas."
+"com/)，數位媒體與創意產業學院劇場與公民媒體系講師"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Matti Schneider"
-msgstr ""
+msgstr "Matti Schneider"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Mauko Quiroga"
-msgstr ""
+msgstr "Mauko Quiroga"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Maurice Hendriks, Gemeente Amsterdam"
-msgstr ""
+msgstr "Maurice Hendriks， 阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Maurits van der Schee, Gemeente Amsterdam"
-msgstr ""
+msgstr "Maurits van der Schee，阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Mirjam van Tiel, The Foundation for Public Code"
-msgstr ""
+msgstr "Mirjam van Tiel，公共程式基金會"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Ngô Ngọc Đức Huy"
-msgstr ""
+msgstr "Ngô Ngọc Đức Huy"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Paul Keller"
-msgstr ""
+msgstr "Paul Keller"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid ""
 "Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
 "(NIIS)](https://niis.org)"
-msgstr ""
+msgstr "Petteri Kivimäki， [北歐互通解決方案機構(NIIS)](https://niis.org)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Sky Bristol"
-msgstr ""
+msgstr "Sky Bristol"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Tamas Erkelens, Gemeente Amsterdam"
-msgstr ""
+msgstr "Tamas Erkelens，阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
+#, fuzzy
 msgid "Timo Slinger"
-msgstr ""
+msgstr "Timo Slinger"
 
 #: ./CC0-1.0.md:block 3 (header)
+#, fuzzy
 msgid "toc: false redirect_from: - license.html - LICENSE.html"
-msgstr ""
+msgstr "toc: false redirect_from: - license.html - LICENSE.html"
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
@@ -207,273 +234,273 @@ msgstr "CC Zero v1.0 Universal授權"
 msgid ""
 "This license is the legal contract that allows anyone to do anything they "
 "like with the content in this entire document."
-msgstr ""
+msgstr "此授權為法律合約，允許任何人任意使用本文件任何內容。"
 
 #: ./CHANGELOG.md:block 3 (header)
 msgid "Version history"
-msgstr ""
+msgstr "版本紀錄"
 
 #: ./CHANGELOG.md:block 5 (header)
 msgid "Version 0.7.0"
-msgstr ""
+msgstr "0.7.0版"
 
 #: ./CHANGELOG.md:block 6 (paragraph)
 msgid ""
 "May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
 "review funding and clarifies review process requirement."
-msgstr ""
+msgstr "2023年5月31日：📑第十五版新增募資審查紀錄新規定，並且釐清審查流程規定。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid ""
 "Add requirement to document who is expected to cover the cost of reviewing "
 "contributions."
-msgstr ""
+msgstr "新增規定，紀錄由誰負擔審核貢獻內容費用。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
-msgstr ""
+msgstr "新增規定，代碼庫必須要有簡短說明。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid ""
 "Change the focus of contributions adhering to standards to focus on the "
 "review of contributions."
-msgstr ""
+msgstr "原本專注在貢獻內容是否符合標準，現在應該專注在貢獻內容審查。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr ""
+msgstr "許多「必須」的規定變更為「應該」的規定，讓代碼庫更容易找到。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
-msgstr ""
+msgstr "審查HTML格式的範本。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Introduction converted to foreword."
-msgstr ""
+msgstr "「簡介」轉變為「序」。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved contributing guidelines."
-msgstr ""
+msgstr "改善貢獻指南。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved documentation of scripts."
-msgstr ""
+msgstr "改善腳本註解。"
 
 #: ./CHANGELOG.md:block 8 (header)
 msgid "Version 0.6.0"
-msgstr ""
+msgstr "0.6.0版"
 
 #: ./CHANGELOG.md:block 9 (paragraph)
 msgid ""
 "April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
 "portability and tests and an introduction to each criterion."
-msgstr ""
+msgstr "2023年4月20日：🔀第十四版新增可移植性與測試的規定，並且介紹每個標準。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about the development "
 "being a collaboration between multiple parties."
-msgstr ""
+msgstr "新增規定，針對多方合作的開發案，編寫可重複使用且可移植的程式碼。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about being dependent "
 "on a single vendor."
-msgstr ""
+msgstr "新增規定，針對依賴單一供應商編寫可重複使用且可移植的程式碼。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Use continuous integration about publishing results for "
 "automated tests."
-msgstr ""
+msgstr "新增規定，公布自動化測試結果時，必須使用持續整合。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Differentiating the two requirements about security to clearly be about "
 "providing a method and having documentation about it."
-msgstr ""
+msgstr "區分兩個安全性規定，一個是有關提供辦法，另一個則是有關安全性的註解。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Rephrased requirements to focus on the codebase rather than contributor "
 "behavior."
-msgstr ""
+msgstr "重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
-msgstr ""
+msgstr "移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added general What this does not do section in the introduction of the "
 "Standard."
-msgstr ""
+msgstr "在標準簡介中，新增「不具備以下作用」段落。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for public policy makers about related policies and license "
 "compatibility."
-msgstr ""
+msgstr "新增有關相關政策與授權相容性的公共政策決策者指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for developers and designers about version controlling files."
-msgstr ""
+msgstr "新增有關版本控制檔案的開發人員與設計師指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Clarified guidance for developers and designers about prompt responses and "
 "search engine optimization."
-msgstr ""
+msgstr "釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added Further reading about accessibility."
-msgstr ""
+msgstr "新增「進一步閱讀無障礙」。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Aligned criteria URLs with criteria names."
-msgstr ""
+msgstr "將各標準的連結與其名稱同步。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Improved navigation in the web version."
-msgstr ""
+msgstr "改善網頁版的導覽功能。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved tools in Further reading sections to the community implementation "
 "guide."
-msgstr ""
+msgstr "將「進一步閱讀」章節的工具移到社群實施指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved compliance or certification process to "
 "[publiccode.net](https://publiccode.net)."
-msgstr ""
+msgstr "將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Change format of the review template to make it easier to update after a new"
 " release."
-msgstr ""
+msgstr "變更審查範本格式，讓範本在新版本推出後後更容易更新。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Improved the text on the landing page and added links to related resources."
-msgstr ""
+msgstr "改善到達網頁文字，加入相關資源的連結。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added spell checker automated test."
-msgstr ""
+msgstr "新增拼字檢查自動化測試。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Made minor changes to text for clarity and consistency."
-msgstr ""
+msgstr "稍微調整文字，讓文字更明確與一致。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Moved SPDX headers to yaml header."
-msgstr ""
+msgstr "將SPDX標題換成yaml標題。"
 
 #: ./CHANGELOG.md:block 11 (header)
 msgid "Version 0.5.0"
-msgstr ""
+msgstr "0.5.0版"
 
 #: ./CHANGELOG.md:block 12 (paragraph)
 msgid ""
 "January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
 "guidelines."
-msgstr ""
+msgstr "2023年1月25日：🎨第十三版焦點在於紀錄風格指南。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Adjust the coding style requirement to focus on the codebase using a style "
 "guide rather than contributor behavior."
-msgstr ""
+msgstr "調整編碼風格要求，專注在代碼庫上面，而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
-msgstr ""
+msgstr "變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement about testing the code by using examples to Use continuous"
 " integration from Document the code."
-msgstr ""
+msgstr "變更使用範例測試程式碼的規定，改為使用持續整合來測試。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Split requirement about machine testable standards to clarify that open is "
 "more important than testable."
-msgstr ""
+msgstr "調整機讀標準規定，強調程式碼的開放性比可測試性更重要。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Adjust how to test findability requirements to be less reliant on search "
 "engine algorithms."
-msgstr ""
+msgstr "調整可查找性的測試規定，減少對搜尋引擎演算法的依賴。"
 
 #: ./CHANGELOG.md:block 14 (header)
 msgid "Version 0.4.1"
-msgstr ""
+msgstr "0.4.1版"
 
 #: ./CHANGELOG.md:block 15 (paragraph)
 msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
-msgstr ""
+msgstr "2022年12月5日：📝第十二版闡明文件成熟度。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
 "Document maturity focuses on whether or not versions of the codebase are "
 "ready to use."
-msgstr ""
+msgstr "文件成熟度端看該版本的代碼庫是否已經可以使用。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
 "Document maturity no longer requires specific labels for codebases that are "
 "not ready to use."
-msgstr ""
+msgstr "文件成熟度再也不需要看尚未無法使用的代碼庫是否具有特定標籤。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Audit flow image now generated from an easier to translate format."
-msgstr ""
+msgstr "現在的審計流程圖格式更容易解讀。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Improved guidance on How to test."
-msgstr ""
+msgstr "改善「測試方式」指南。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add publiccode.yml file."
-msgstr ""
+msgstr "新增publiccode.yml檔案。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add review template."
-msgstr ""
+msgstr "新增審查範本。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Consistently link glossary terms."
-msgstr ""
+msgstr "一貫連結詞彙。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add practices and standards to follow in CONTRIBUTING."
-msgstr ""
+msgstr "新增「貢獻」的實務與標準。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add Matti Schneider to Authors."
-msgstr ""
+msgstr "Matti Schneider加入作者群。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add remaining SPDX headers to files."
-msgstr ""
+msgstr "將剩餘SPDX標題加入檔案中。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Made additional minor changes to text for clarity."
-msgstr ""
+msgstr "稍微修改文字，讓文字更明確。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Some hyperlinks updated."
-msgstr ""
+msgstr "更新部分超連結。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
@@ -481,188 +508,194 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
+"將範例移動到[社群實施指南](https://publiccodenet.github.io/"
+"community-implementation-guide-standard/)。"
 
 #: ./CHANGELOG.md:block 17 (header)
 msgid "Version 0.4.0"
-msgstr ""
+msgstr "0.4.0版"
 
 #: ./CHANGELOG.md:block 18 (paragraph)
 msgid ""
 "September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
-msgstr ""
+msgstr "2022年9月7日：🔭第十一版新增全新的可查找性標準。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduce new criterion: Make the codebase findable."
-msgstr ""
+msgstr "推出新標準：使代碼庫變得容易查找。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Improve How to test section for most criteria."
-msgstr ""
+msgstr "改善多數標準的「測試方式」章節。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "New requirement in Welcome contributors about publishing activity "
 "statistics."
-msgstr ""
+msgstr "「歡迎貢獻者」章節中有關發佈活動統計的新規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Removed redundant requirement about portable and reusable code."
-msgstr ""
+msgstr "移除有關可移植與可重複使用的程式碼的多餘規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expand open license definition to include both OSI and FSF approved "
 "licenses."
-msgstr ""
+msgstr "開放授權的定義中，加入OSI與FSF認證的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr ""
+msgstr "重新編寫選擇性規定，加入「非必須」一詞，讓規定更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr ""
+msgstr "表示公共程式標準在適用時應該符合自身規定，並且新增評估。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
-msgstr ""
+msgstr "將SPDC license identifier加入檔案中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduced new Code of Conduct."
-msgstr ""
+msgstr "推出新行為守則。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify distinction between source code and policy text."
-msgstr ""
+msgstr "解釋原始碼與政策內文的差異。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Restructuring of requirements with bullet point lists."
-msgstr ""
+msgstr "將規定改為要點清單的格式。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
+#, fuzzy
 msgid "Acknowledge the importance of codebase modularity for reuse."
-msgstr ""
+msgstr "承認代碼庫成熟度在重複使用上的重要性。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Move requirements related to Findability to the new criterion."
-msgstr ""
+msgstr "將可查找性相關規定移動到新標準。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify the role of non-open standards when used in a codebase."
-msgstr ""
+msgstr "釐清非開放性標準在代碼庫中的角色。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Additional guidance about build-time and runtime dependencies."
-msgstr ""
+msgstr "關於建制時期與執行階段相依性的額外指南。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
-msgstr ""
+msgstr "新增公共程式標準開發路徑圖。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Update structure of Authors file."
-msgstr ""
+msgstr "更新作者檔案結構。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add Audrey Tang to Authors."
-msgstr ""
+msgstr "將唐鳳加入作者群。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added a list of criteria to the print edition."
-msgstr ""
+msgstr "在印刷版中新增標準清單。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Clarify what the standard means with policymakers, managers, developers and "
 "designers."
-msgstr ""
+msgstr "釐清標準對政策制定者、管理者、開發人員與設計師的意義。"
 
 #: ./CHANGELOG.md:block 20 (header)
 msgid "Version 0.3.0"
-msgstr ""
+msgstr "0.3.0版"
 
 #: ./CHANGELOG.md:block 21 (paragraph)
 msgid ""
 "May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
-msgstr ""
+msgstr "2022年5月23日：🗎第十版加強註解與本土化。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Requirement for localization made explicit in Create reusable and portable "
 "code."
-msgstr ""
+msgstr "「編寫可重複使用與可移植程式碼」章節有明確的本土化規定。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
-msgstr ""
+msgstr "治理註解從「應該」變成「必須」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
-msgstr ""
+msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須有限」規定，改為必須紀錄貢"
+"獻的期望，專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
-msgstr ""
+msgstr "社群翻譯現在連結到頁尾中。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
-msgstr ""
+msgstr "還原「用Mermaid流程圖取代BPMN svg」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Many minor clarifications to language and sentences made more simple."
-msgstr ""
+msgstr "細微調整用詞，讓句子更簡單。"
 
 #: ./CHANGELOG.md:block 23 (header)
 msgid "Version 0.2.3"
-msgstr ""
+msgstr "0.2.3版"
 
 #: ./CHANGELOG.md:block 24 (paragraph)
 msgid ""
 "March 15th 2022: 📜 the ninth draft allows English summaries for policy "
 "lacking an official translation."
-msgstr ""
+msgstr "2022年3月15日：📜第九版在沒有官方翻譯的政策加入英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Relax the criterion Use plain English by adding a new requirement allows "
 "bundled policy not available in English to have an accompanying summary in "
 "English instead of translating the full text."
-msgstr ""
+msgstr "放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入"
+"英文版摘要，不用翻譯全文。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Similarly, allow for English summaries for policies not available in English"
 " in Bundle policy and code."
-msgstr ""
+msgstr "同樣地，允許同捆政策與程式碼當中，沒有英文版的政策只需要英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Clarify that term 'policy' includes processes which impact development and "
 "deployment in Bundle policy and code."
-msgstr ""
+msgstr "釐清「政策」包括能影響同捆政策與程式碼開發與部署的流程。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Emphasize reusability also on parts of the solutions in Create reusable and "
 "portable code."
-msgstr ""
+msgstr "強調「編寫可重複使用與移植的程式碼」解決方案部分內容的可重複使用性。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Expand guidance to Developers and designers in Create reusable and portable "
 "code about deploying to proprietary platforms."
-msgstr ""
+msgstr "將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到"
+"不同專屬平台的內容。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Add nuance to use of non-English terms in what management need to do in Use "
 "plain English."
-msgstr ""
+msgstr "在「使用簡單英文」中，加入管理人員需要使用的非英文詞彙。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -670,362 +703,364 @@ msgid ""
 "make [community translations](https://github.com/publiccodenet/community-"
 "translations-standard) easier."
 msgstr ""
+"變更拉取請求流程圖，從BPMN改用Mermaid，讓[社群翻譯](https://github.com/"
+"publiccodenet/community-translations-standard)更容易。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added Maurice Hendriks to AUTHORS."
-msgstr ""
+msgstr "將Maurice Hendriks加入作者群。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added OpenApi Specification to further reading."
-msgstr ""
+msgstr "將「OpenApi規格」加入「深入閱讀」。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Made the attributions in further reading sections clearer."
-msgstr ""
+msgstr "將「深入閱讀」當中的歸因變得更明確。"
 
 #: ./CHANGELOG.md:block 26 (header)
 msgid "Version 0.2.2"
-msgstr ""
+msgstr "0.2.2版"
 
 #: ./CHANGELOG.md:block 27 (paragraph)
 msgid ""
 "November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
 " as code may not be in English."
-msgstr ""
+msgstr "2021年11月29日：🏛第八版承認當作程式碼來執行的政策，不一定是英文。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Document exception to \"All code MUST be in English\" where policy is "
 "interpreted as code."
-msgstr ""
+msgstr "標示當政策被詮釋為程式碼時，則不用遵守「僅限英文程式碼」的規則。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Add MAY requirement regarding committer email addresses in Maintain version "
 "control."
-msgstr ""
+msgstr "在「版本管控」中，新增關於提交者電子郵件的「得以」規定。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Policy Makers in Bundle policy and code."
-msgstr ""
+msgstr "將政策制定者加入「同捆政策與程式碼」指南。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Developers and designers in Use a coherent style."
-msgstr ""
+msgstr "將開發人員與設計師加入「風格一致」指南。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add \"Different contexts\" to glossary."
-msgstr ""
+msgstr "新增「不同脈絡」到詞彙表中。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
-msgstr ""
+msgstr "將Mauko Quiroga與Charlotte Heikendorf加入作者群。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Digital Public Goods approval badge."
-msgstr ""
+msgstr "新增「數位公共財」認證標章。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
-msgstr ""
+msgstr "加入網頁版「標準」頁面的「上一頁」與「下一頁」連結。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Open Standards principles to further reading."
-msgstr ""
+msgstr "將「開放標準原則」加入「深入閱讀」。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Definition of plain language to further reading."
-msgstr ""
+msgstr "將「簡單語言定義」加入「深入閱讀」。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Move the Semantic Versioning Specification further reading reference."
-msgstr ""
+msgstr "移動「語意化版本規格」引用的「深入閱讀」。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Clarify that publiccode.yml is one example of a machine-readable metadata "
 "description."
-msgstr ""
+msgstr "釐清publiccode.yml是描述機讀元資料的名稱之一。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
-msgstr ""
+msgstr "將「您的代碼庫」與「貴組織」改為較不具有所有格的寫法。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add instructions for creating a print version."
-msgstr ""
+msgstr "新增印刷版的建立說明。"
 
 #: ./CHANGELOG.md:block 29 (header)
 msgid "Version 0.2.1"
-msgstr ""
+msgstr "0.2.1版"
 
 #: ./CHANGELOG.md:block 30 (paragraph)
 msgid ""
 "March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
 "0.2.0."
-msgstr ""
+msgstr "2021年3月1日：🧽跟0.2.0版相較之下，第七版做了些微改善。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "New SHOULD requirement on using a distributed version control system and why"
 " distributed is important."
-msgstr ""
+msgstr "針對使用分散版本控制系統制定新的「應該」規定，並解釋分散的重要性。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "Feedback requirements for rejected contributions are more strict than "
 "accepted ones."
-msgstr ""
+msgstr "針對被拒絕的貢獻的回饋，比被接受的貢獻的回饋規定更嚴苛。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "Specify that copyright and license notices should also be machine-readable."
-msgstr ""
+msgstr "明確指出著作權與授權聲明也應該要可機讀。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Advice on how to test that notices be machine-readable."
-msgstr ""
+msgstr "聲明是否為可機讀的測試方式建議。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Clarify guidance for rolling releases."
-msgstr ""
+msgstr "釐清滾動發行的指南。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Clear up definition of version control in glossary."
-msgstr ""
+msgstr "釐清詞彙表中「版本控制」的定義。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "Add further reading encouraging contribution, SPDX, Git and reviewing "
 "contributions."
-msgstr ""
+msgstr "新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git以及審查貢獻。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add links to videos about the concept of public code."
-msgstr ""
+msgstr "新增有關公共程式概念的影片連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Update BPMN link."
-msgstr ""
+msgstr "更新BPMN連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Reduce link duplication."
-msgstr ""
+msgstr "減少重複連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
-msgstr ""
+msgstr "將Alba Roza與Ngô Ngọc Đức Huy加入作者群。"
 
 #: ./CHANGELOG.md:block 32 (header)
 msgid "Version 0.2.0"
-msgstr ""
+msgstr "0.2.0版"
 
 #: ./CHANGELOG.md:block 33 (paragraph)
 msgid ""
 "October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
-msgstr ""
+msgstr "2020年10月26日：🎊第六版分拆一項規定並且釐清內容。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
 "and \"Welcome contributors\"."
-msgstr ""
+msgstr "將「歡迎貢獻」標準分拆為「讓貢獻更容易」以及「歡迎貢獻者」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Rename criterion \"Pay attention to codebase maturity\" to \"Document "
 "codebase maturity\"."
-msgstr ""
+msgstr "將「注意代碼庫成熟度」標準改名為「註解代碼庫成熟度」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
-msgstr ""
+msgstr "針對多方使用的代碼庫，將「必須」規定調整為「應該」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
-msgstr ""
+msgstr "針對著作權讓與，新增「不得」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
-msgstr ""
+msgstr "在可重複使用程式碼規定中，釐清組態的角色。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Glossary additions: continuous integration, policy, repository, and version "
 "control."
-msgstr ""
+msgstr "新增詞彙：持續整合、政策、儲存庫與版本控制。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Replace references to 'cities' with 'public organizations'."
-msgstr ""
+msgstr "將「城市」都替換成「公共組織」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Clarify aspects of sensitive code by separating contributor and reviewer "
 "requirements into separate items."
-msgstr ""
+msgstr "將貢獻者與審查規定分開，藉此釐清程式碼敏感的地方。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Expand further reading, and guidance to policy makers, developers and "
 "designers."
-msgstr ""
+msgstr "將政策制定者、開發人員與設計師加入「深入閱讀」與指南中。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add Felix Faassen and Arnout Engelen to authors."
-msgstr ""
+msgstr "將Felix Faassen與Arnout Engelen加入作者群。"
 
 #: ./CHANGELOG.md:block 35 (header)
 msgid "Version 0.1.4"
-msgstr ""
+msgstr "0.1.4版"
 
 #: ./CHANGELOG.md:block 36 (paragraph)
 msgid ""
 "November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
 "fixes."
-msgstr ""
+msgstr "2019年11月27日：🧹第五版主要內容是額外的細部修復。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Linked License.md file."
-msgstr ""
+msgstr "連結的License.md檔案。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
-msgstr ""
+msgstr "將Sky Bristol、Marcus Klaas de Vries與Jan Ainali加入作者群。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Made punctuation more consistent, especially for bullet lists."
-msgstr ""
+msgstr "讓標點符號更連貫，特別是項目符號列表。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Made some minor changes to text for clarity."
-msgstr ""
+msgstr "細部調整文字，讓內容更明確。"
 
 #: ./CHANGELOG.md:block 38 (header)
 msgid "Version 0.1.3"
-msgstr ""
+msgstr "0.1.3版"
 
 #: ./CHANGELOG.md:block 39 (paragraph)
 msgid ""
 "October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
 " the autumn cleaning"
-msgstr ""
+msgstr "2019年10月8日：🍂第四版僅針對秋季的清理修復小問題"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "Renamed continuous delivery to continuous integration."
-msgstr ""
+msgstr "將「持續交付」改名為「持續整合」。"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "Referencing accessibility guidelines in the language standard."
-msgstr ""
+msgstr "在語言標準中引述無障礙指導原則。"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "A bunch of style and consistency fixes."
-msgstr ""
+msgstr "改善樣式與一致性。"
 
 #: ./CHANGELOG.md:block 41 (header)
 msgid "Version 0.1.2"
-msgstr ""
+msgstr "0.1.2版"
 
 #: ./CHANGELOG.md:block 42 (paragraph)
 msgid ""
 "August 22th 2019: 🌠 the third draft focuses on better text and takes "
 "community input"
-msgstr ""
+msgstr "2019年8月22日：🌠第三版專注在提升文字品質，並且傾聽社群的意見"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "With some great new contributors comes a fresh author list."
-msgstr ""
+msgstr "一群很棒的貢獻者，讓我們作者群加入許多新血。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "All links are now HTTPS."
-msgstr ""
+msgstr "所有連結開頭都是HTTPS。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "General proofreading, wording clarifications, and smashed typos."
-msgstr ""
+msgstr "一般校對、釐清用字與修改拼字錯誤。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Updated criteria:"
-msgstr ""
+msgstr "更新標準："
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Requirement for reuse in different contexts"
-msgstr ""
+msgstr "在不同脈絡下重複使用的規定"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for explicit versioning"
-msgstr ""
+msgstr "明確版本控制建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for multi party development"
-msgstr ""
+msgstr "多方部署建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for license headers in files"
-msgstr ""
+msgstr "檔案授權標題建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for vulnerability reporting"
-msgstr ""
+msgstr "脆弱性回報建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for explicit documentation of governance"
-msgstr ""
+msgstr "明確治理註解建議"
 
 #: ./CHANGELOG.md:block 44 (header)
 msgid "Version 0.1.1"
-msgstr ""
+msgstr "0.1.1版"
 
 #: ./CHANGELOG.md:block 45 (paragraph)
 msgid ""
 "May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
 "lot of typos"
-msgstr ""
+msgstr "2019年5月9日：🤔第二版修復基本的疏忽以及許多拼字錯誤"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid ""
 "Removed references to the Foundation for Public Code, we're going to have to"
 " change the name in becoming an association."
-msgstr ""
+msgstr "移除出現「公共程式基金會」的地方，我們必須改名才能成為協會。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the introduction."
-msgstr ""
+msgstr "更新前言。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the glossary."
-msgstr ""
+msgstr "更新詞彙表。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Added the code of conduct."
-msgstr ""
+msgstr "新增行為守則。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "We've recommended using the publiccode.yml standard for easier reuse."
-msgstr ""
+msgstr "我們建議使用publiccode.yml標準，方便重複使用。"
 
 #: ./CHANGELOG.md:block 47 (header)
 msgid "Version 0.1.0"
-msgstr ""
+msgstr "0.1.0版"
 
 #: ./CHANGELOG.md:block 48 (paragraph)
 msgid ""
 "April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
 "snazzy new ideas in it"
-msgstr ""
+msgstr "2019年4月16日：🎉初版已經就緒，內容全新且有許多有趣的全新構想"
 
 #: ./CHANGELOG.md:block 49 (unordered list)
 msgid "14 criteria with their requirements and how to operationalize them."
-msgstr ""
+msgstr "14個標準、其規定以及實施方式。"
 
 #: ./CHANGELOG.md:block 49 (unordered list)
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
-msgstr ""
+msgstr "清楚明確的背景介紹、介紹本標準以及公共程式基金會會如何使用此標準。"
 
 #: ./CHANGELOG.md:block 50 (paragraph)
 msgid ""
@@ -1033,10 +1068,12 @@ msgid ""
 "Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
 "Public Code! project](https://smartcities.publiccode.net/)."
 msgstr ""
+"第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於["
+"智慧城市？公共程式！專案](https://smartcities.publiccode.net/)。"
 
 #: ./CODE_OF_CONDUCT.md:block 1 (header)
 msgid "Code of Conduct"
-msgstr ""
+msgstr "行為守則"
 
 #: ./CODE_OF_CONDUCT.md:block 3 (paragraph)
 msgid ""
@@ -1044,31 +1081,32 @@ msgid ""
 "behavioral codes yet some individuals are not. This document expresses "
 "expectations of all community members and all interactions regardless of "
 "communication channel."
-msgstr ""
+msgstr "社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基"
+"金會對所有社群成員以及互動（不管溝通管道）的期望。"
 
 #: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
 msgid "Be here to collaborate."
-msgstr ""
+msgstr "到這裡來是為了協作。"
 
 #: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
 msgid "Be considerate, respectful, and patient."
-msgstr ""
+msgstr "對彼此體貼、尊重以及有耐心。"
 
 #: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
 msgid "Strive to be as constructive as possible."
-msgstr ""
+msgstr "努力做出建設性的貢獻。"
 
 #: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
 msgid "To raise a concern, please email directors@publiccode.net."
-msgstr ""
+msgstr "若有問題，請寄送電子郵件到directors@publiccode.net。"
 
 #: ./CONTRIBUTING.md:block 1 (header)
 msgid "Contributing to this standard"
-msgstr ""
+msgstr "貢獻給此標準"
 
 #: ./CONTRIBUTING.md:block 3 (paragraph)
 msgid "🙇‍♀️ Thank you for contributing!"
-msgstr ""
+msgstr "🙇‍♀️ 感謝您的貢獻！"
 
 #: ./CONTRIBUTING.md:block 4 (paragraph)
 msgid ""
@@ -1077,6 +1115,8 @@ msgid ""
 "possible. Thus we appreciate your input, enjoy feedback and welcome "
 "improvements to this project and are very open to collaboration."
 msgstr ""
+"我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因"
+"此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。"
 
 #: ./CONTRIBUTING.md:block 5 (paragraph)
 msgid ""
@@ -1084,10 +1124,13 @@ msgid ""
 "with GitHub, you can email use your feedback at "
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
+"我們歡迎每個人提出的議題與提取請求。如果您對GitHub不放心，"
+"歡迎將意見用電子郵件傳送到 [info@publiccode.net](mailto:info@publiccode."
+"net)。"
 
 #: ./CONTRIBUTING.md:block 6 (header)
 msgid "Problems, suggestions and questions in issues"
-msgstr ""
+msgstr "問題、建議與議題中的問題"
 
 #: ./CONTRIBUTING.md:block 7 (paragraph)
 msgid ""
@@ -1099,6 +1142,11 @@ msgid ""
 "Issues for the Standard for Public "
 "Code](https://github.com/publiccodenet/standard/issues)."
 msgstr ""
+"[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以"
+"及發問，幫助推動本開發案。您可以到[GitHub的公共程式標準議題](https://github."
+"com/publiccodenet/standard/"
+"issues)頁面中，為此專案[在GitHub上建立議題](https://docs.github.com/en/"
+"issues/tracking-your-work-with-issues/creating-an-issue)。"
 
 #: ./CONTRIBUTING.md:block 8 (paragraph)
 msgid ""
@@ -1107,22 +1155,25 @@ msgid ""
 " and send an email to "
 "[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
 msgstr ""
+"或者加入[郵寄清單](https://lists.publiccode.net/mailman/postorius/lists/"
+"standard.lists.publiccode.net/)並且傳送電子郵件到[standard@lists.publiccode."
+"net](mailto:standard@lists.publiccode.net)。"
 
 #: ./CONTRIBUTING.md:block 9 (paragraph)
 msgid ""
 "You don't need to change any of our code or documentation to be a "
 "contributor!"
-msgstr ""
+msgstr "不需要修改我們的程式碼或註解也能成為貢獻者！"
 
 #: ./CONTRIBUTING.md:block 10 (header)
 msgid "Documentation and code in pull requests"
-msgstr ""
+msgstr "提取請求中的註解與程式碼"
 
 #: ./CONTRIBUTING.md:block 11 (paragraph)
 msgid ""
 "If you want to add to the documentation or code of one of our projects you "
 "should make a pull request."
-msgstr ""
+msgstr "如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出提取請求。"
 
 #: ./CONTRIBUTING.md:block 12 (paragraph)
 msgid ""
@@ -1132,6 +1183,10 @@ msgid ""
 "Skills](https://skills.github.com/) on working with GitHub and working with "
 "MarkDown, the syntax this project's documentation is in."
 msgstr ""
+"若您從未使用過GitHub，歡迎先[認識GitHub flow](https://docs.github.com/en/"
+"get-started/quickstart/github-flow)，或是參加[GitHub Skills](https://skills."
+"github.com/)的免費且優質的互動性課程，當中介紹如何使用GitHub以及MarkDown（本"
+"專案註解所使用的語法）。"
 
 #: ./CONTRIBUTING.md:block 13 (paragraph)
 msgid ""
@@ -1139,11 +1194,12 @@ msgid ""
 "essentially means that the project, along with your contributions is in the "
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
-msgstr ""
+msgstr "本專案獲得CC Zero v1.0 Universal授權，基本上代表本專案與您的貢獻，都屬於公眾"
+"領域，任何人都可以任意使用。"
 
 #: ./CONTRIBUTING.md:block 14 (header)
 msgid "1. Make your changes"
-msgstr ""
+msgstr "1. 作出變更"
 
 #: ./CONTRIBUTING.md:block 15 (paragraph)
 msgid ""
@@ -1155,6 +1211,10 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
+"貢獻應該[遵守](docs/standard-for-public-code.html)公共程式標準當中列出的標準"
+"。審查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-"
+"code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-"
+"follow)且與整體專案有連貫。"
 
 #: ./CONTRIBUTING.md:block 16 (paragraph)
 msgid ""
@@ -1163,6 +1223,9 @@ msgid ""
 "you've forked this repository, please make sure to create a feature branch "
 "following the GitFlow model."
 msgstr ""
+"本專案使用[GitFlow分支與工作流程](https://nvie.com/posts/"
+"a-successful-git-branching-model/"
+")。當您複製了此存放庫，請務必依照GitFlow模型建立功能分支。"
 
 #: ./CONTRIBUTING.md:block 17 (paragraph)
 msgid ""
@@ -1176,27 +1239,34 @@ msgid ""
 "commit message, this will enable everyone to be informed of your choices in "
 "the future."
 msgstr ""
+"將您變更內容加入到提交版本[並且附上說明](https://robots.thoughtbot.com/5"
+"-useful-tips-for-a-better-commit-message)。如果需要不只一種變更，將相關變更分"
+"類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不"
+"同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格式。像是「svg」格式就"
+"勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選"
+"擇。"
 
 #: ./CONTRIBUTING.md:block 18 (paragraph)
 msgid ""
 "If you are adding code, make sure you've added and updated the relevant "
 "documentation and tests before you submit your pull request. Make sure to "
 "write tests that show the behavior of the newly added or changed code."
-msgstr ""
+msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出提取請求。請"
+"務必用文字描述新增或修改後的程式碼的作用。"
 
 #: ./CONTRIBUTING.md:block 19 (header)
 msgid "Applicable policy"
-msgstr ""
+msgstr "適用政策"
 
 #: ./CONTRIBUTING.md:block 20 (paragraph)
 msgid ""
 "Currently, the Standard for Public Code is not implementing any specific "
 "public policy."
-msgstr ""
+msgstr "公共程式標準目前沒有執行任何特定的公共政策。"
 
 #: ./CONTRIBUTING.md:block 21 (header)
 msgid "Style"
-msgstr ""
+msgstr "風格"
 
 #: ./CONTRIBUTING.md:block 22 (paragraph)
 msgid ""
@@ -1209,33 +1279,38 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
+"公共程式標準目標是[使用簡單英文](criteria/use-plain-english.md)，拼字採用美式"
+"英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們"
+"要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修"
+"正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
-msgstr ""
+msgstr "遵守的標準"
 
 #: ./CONTRIBUTING.md:block 24 (paragraph)
 msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr ""
+msgstr "這些是公共程式標準所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併"
+"。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
 "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
 " keywords"
-msgstr ""
+msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 「必要性」層級的關鍵字"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
 "[Web Content Accessibility Guidelines "
 "2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
-msgstr ""
+msgstr "[網頁無障礙性指導原則 2.1](https://www.w3.org/TR/WCAG21/#readable) - 可讀性"
 
 #: ./CONTRIBUTING.md:block 26 (header)
 msgid "2. Pull request"
-msgstr ""
+msgstr "2. 提取請求"
 
 #: ./CONTRIBUTING.md:block 27 (paragraph)
 msgid ""
@@ -1245,17 +1320,21 @@ msgid ""
 "issue where possible. In some cases a single set of changes may address "
 "multiple issues, in which case be sure to list all issue numbers fixed."
 msgstr ""
+"提出提取請求時，請附帶描述您想要解決的問題以及該提取請求能修復的議題編號。建"
+"議讓一個提取請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議"
+"題編號。"
 
 #: ./CONTRIBUTING.md:block 28 (header)
 msgid "3. Improve"
-msgstr ""
+msgstr "3. 改善"
 
 #: ./CONTRIBUTING.md:block 29 (paragraph)
 msgid ""
 "All contributions have to be reviewed by someone. The Foundation for Public "
 "Code has committed to make sure that maintainers are available to review "
 "contributions with an aim to provide feedback within two business days."
-msgstr ""
+msgstr "所有貢獻都必須接受審查。公共程式基金會承諾將確保有維護人員來審查貢獻，目標是"
+"在兩個工作日內提供意見回饋。"
 
 #: ./CONTRIBUTING.md:block 30 (paragraph)
 msgid ""
@@ -1265,30 +1344,34 @@ msgid ""
 "feedback. If this is the case the reviewing maintainer will help you improve"
 " your documentation and code."
 msgstr ""
+"維護人員可能可以立即合併您的貢獻。但是通常新提取請求需要改善，才能夠合併。其"
+"他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人"
+"員，將負責協助改善您的註解與程式碼。"
 
 #: ./CONTRIBUTING.md:block 31 (paragraph)
 msgid "If your documentation and code have passed human review, it is merged."
-msgstr ""
+msgstr "若您的註解與程式碼通過人工審查，就會被合併。"
 
 #: ./CONTRIBUTING.md:block 32 (header)
 msgid "4. Celebrate"
-msgstr ""
+msgstr "4. 慶祝"
 
 #: ./CONTRIBUTING.md:block 33 (paragraph)
 msgid ""
 "Your ideas, documentation and code have become an integral part of this "
 "project. You are the open source hero we need!"
-msgstr ""
+msgstr "您的構思、註解與程式碼將成為本專案的一部份。您就是我們所需要的開源英雄！"
 
 #: ./CONTRIBUTING.md:block 34 (paragraph)
 msgid ""
 "In fact, feel free to open a pull request to add your name to the "
 "[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
-msgstr ""
+msgstr "歡迎您提出提取請求，將您的名字加入到[`作者`](AUTHORS."
+"md)檔案中，您的名字可以永遠留在本專案中。"
 
 #: ./CONTRIBUTING.md:block 35 (header)
 msgid "Translations in other languages"
-msgstr ""
+msgstr "其他語言的翻譯"
 
 #: ./CONTRIBUTING.md:block 36 (paragraph)
 msgid ""
@@ -1296,23 +1379,26 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
+"公共程式標準雖然沒有官方翻譯，您可以幫助維護現有以及新增[公共程式標準社群翻譯"
+"](https://github.com/publiccodenet/community-translations-standard)。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
-msgstr ""
+msgstr "版本"
 
 #: ./CONTRIBUTING.md:block 38 (paragraph)
 msgid ""
 "We have dedicated documentation for creating [new "
 "releases](/docs/releasing.md) and [ordering printed "
 "standards](/docs/printing.md)."
-msgstr ""
+msgstr "建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing."
+"md)有專用註解。"
 
 #: ./CONTRIBUTING.md:block 39 (paragraph)
 msgid ""
 "For more information on how to use and contribute to this project, please "
 "read the [`README`](README.md)."
-msgstr ""
+msgstr "若要進一步瞭解如何使用與貢獻本專案，請參閱 [`讀我`](README.md)。"
 
 #: ./GOVERNANCE.md:block 2 (header)
 msgid ""
@@ -1320,10 +1406,12 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
+"SPDX-FileCopyrightText: 2019-2022 公共程式基金會[info@publiccode."
+"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./GOVERNANCE.md:block 3 (header)
 msgid "Governance"
-msgstr ""
+msgstr "治理"
 
 #: ./GOVERNANCE.md:block 4 (paragraph)
 msgid ""
@@ -1331,22 +1419,25 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
+"此標準是[公共程式基金會](https://publiccode.net/"
+")代碼庫管理的核心。我們依照本文件來判斷代碼庫是否已經準備好讓社群參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
-msgstr ""
+msgstr "本標準由公共程式基金會人員負責維護。"
 
 #: ./GOVERNANCE.md:block 6 (paragraph)
 msgid ""
 "[We welcome contributions, such as suggestions for changes or general "
 "feedback, from anyone.](/CONTRIBUTING.md)"
-msgstr ""
+msgstr "[我們歡迎任何人提供修改的建議或是一般意見回饋等貢獻。](/CONTRIBUTING.md)"
 
 #: ./GOVERNANCE.md:block 7 (paragraph)
 msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
-msgstr ""
+msgstr "由於公共程式標準在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守公共程"
+"式標準中最嚴苛的標準。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1354,10 +1445,13 @@ msgid ""
 " opportunity to work together to improve our methods and the Standard. We "
 "may not accept all changes, but we will explain our logic."
 msgstr ""
+"我們會努力儘速回覆所有提取請求。提取請求讓我們有機會一起合作，改善我們的方法"
+"與公共程式標準。我們可能不會接受貢獻者提出的所有修改，但我們會解釋背後的邏輯"
+"。"
 
 #: ./README.md:block 1 (header)
 msgid "Standard for Public Code"
-msgstr ""
+msgstr "公共程式標準"
 
 #: ./README.md:block 3 (paragraph)
 msgid ""
@@ -1366,6 +1460,8 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
+"公共程式標準提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公"
+"共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供應商的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1373,6 +1469,9 @@ msgid ""
 "CC0-1.0](https://img.shields.io/badge/License-"
 "CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
 msgstr ""
+"![0.7.0版](assets/version-badge.svg) [![授權：CC0-1.0](https://img.shields."
+"io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/"
+"publicdomain/zero/1.0/)"
 
 #: ./README.md:block 5 (paragraph)
 msgid ""
@@ -1390,17 +1489,29 @@ msgid ""
 "develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
 "check/standard.publiccode.net-develop-url-check-look.json)"
 msgstr ""
+"[![頁面-建造-部署](https://github.com/publiccodenet/standard/actions/"
+"workflows/pages/pages-build-deployment/badge.svg)](https://github.com/"
+"publiccodenet/standard/actions/workflows/pages/pages-build-deployment) "
+"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test."
+"yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/"
+"test.yml) [![標準主徽章](https://publiccodenet.github.io/"
+"publiccodenet-url-check/badges/standard.publiccode.net."
+"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
+"publiccode.net-url-check-look.json) [![標準開發徽章](https://publiccodenet."
+"github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop."
+"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
+"publiccode.net-develop-url-check-look.json)"
 
 #: ./README.md:block 6 (paragraph)
 msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr ""
+msgstr "公共程式標準目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr ""
+msgstr "將公共程式標準套用在您的代碼庫"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1411,6 +1522,10 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
+"若您想要將公共程式標準套用在您的代碼庫，不需要任何猶豫，因為公共程式標準是開"
+"放性標準，任何人都可以免費使用。若要瞭解您代碼庫是否就緒，可以進行[資格自我評"
+"估](https://publiccodenet.github.io/assessment-"
+"eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
 
 #: ./README.md:block 9 (paragraph)
 msgid ""
@@ -1421,13 +1536,18 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
+"將公共程式標準套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不"
+"明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與您抱持同樣看法的民"
+"眾。如需靈感，請參閱[社群打造的實施指南](https://publiccodenet.github.io/"
+"community-implementation-guide-standard/)，當中包括範例與其他訣竅。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
 "If there are any breaking changes in a new version of the Standard for "
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
-msgstr ""
+msgstr "若新版的公共程式標準有突破性的修改，公共程式基金會的代碼庫管理人員會幫助公共"
+"程式標準用戶彌補不同版之間的差異。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1437,10 +1557,14 @@ msgid ""
 "[assessment](https://about.publiccode.net/activities/codebase-"
 "stewardship/lifecycle-diagram.html#assessment)."
 msgstr ""
+"若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與"
+"我們聯繫：[info@publiccode.net](mailto:info@publiccode."
+"net)，並開始正式[評估](https://about.publiccode.net/activities/"
+"codebase-stewardship/lifecycle-diagram.html#assessment)。"
 
 #: ./README.md:block 12 (header)
 msgid "Request for contributions"
-msgstr ""
+msgstr "徵求貢獻"
 
 #: ./README.md:block 13 (paragraph)
 msgid ""
@@ -1448,14 +1572,16 @@ msgid ""
 "legible, accountable, accessible and sustainable. This means we need a new "
 "way of designing, developing and procuring both the source code and policy "
 "documentation."
-msgstr ""
+msgstr "我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特"
+"性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。"
 
 #: ./README.md:block 14 (paragraph)
 msgid ""
 "This standard sets a quality level for codebases that meets the needs of "
 "public organizations, institutions and administrations as well as other "
 "critical infrastructural services."
-msgstr ""
+msgstr "本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需"
+"求。"
 
 #: ./README.md:block 15 (paragraph)
 msgid ""
@@ -1463,6 +1589,8 @@ msgid ""
 "[standard.publiccode.net](https://standard.publiccode.net/). See "
 "[`index.md`](index.md) for an overview of all content."
 msgstr ""
+"公共程式標準就在[standard.publiccode.net](https://standard.publiccode.net/"
+")。內容概覽請參閱[`index.md`](index.md)。"
 
 #: ./README.md:block 16 (paragraph)
 msgid ""
@@ -1471,6 +1599,9 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
+"[![公共程式標準YouTube影片縮圖：兩隻手中間放著一本印刷版公共程式標準](https:/"
+"/img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/"
+"watch?v=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
 msgid ""
@@ -1478,17 +1609,19 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
+"[公共程式標準介紹影片](https://www.youtube.com/watch?v=QWt6vB-cipE) from "
+"Creative Commons Global Summit 2020 (4:12) on YouTube."
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
-msgstr ""
+msgstr "幫忙改善本標準"
 
 #: ./README.md:block 19 (paragraph)
 msgid ""
 "The Foundation for Public Code is committed to maintaining and developing "
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
-msgstr ""
+msgstr "公共程式基金會致力於維護與開發公共程式標準，且品質也會符合該標準本身的品質。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -1499,17 +1632,22 @@ msgid ""
 " described how we govern the standard in the [governance "
 "statement](GOVERNANCE.md)."
 msgstr ""
+"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及"
+"協助開發。😊若要開始，請先參閱我們的[貢獻者指南](CONTRIBUTING.md)。由於這是相"
+"當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE."
+"md)提到我們管理該標準的方式。"
 
 #: ./README.md:block 21 (paragraph)
 msgid ""
 "Please note that this project is released with a [code of "
 "conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
 "abide by its terms. Please be lovely to all other community members."
-msgstr ""
+msgstr "請注意，本專案有其[行為準則](CODE_OF_CONDUCT."
+"md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。"
 
 #: ./README.md:block 22 (header)
 msgid "Preview, build and deploy"
-msgstr ""
+msgstr "預覽、建造與部署"
 
 #: ./README.md:block 23 (paragraph)
 msgid ""
@@ -1518,38 +1656,46 @@ msgid ""
 "with [GitHub pages](https://pages.github.com) and "
 "[Jekyll](https://jekyllrb.com/)."
 msgstr ""
+"存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode."
+"net/)的靜態網站，使用的是[GitHub pages](https://pages.github."
+"com)與[Jekyll](https://jekyllrb.com/)。"
 
 #: ./README.md:block 24 (paragraph)
 msgid ""
 "The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
 "means you will need ruby and ruby-bundler installed, for example:"
 msgstr ""
+"當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構"
+"，換句話說您需要安裝ruby與ruby-bundler，像是："
 
 #: ./README.md:block 26 (paragraph)
 msgid ""
 "If `ruby` and `bundle` are installed, one can run `bundle install` after "
 "which the site can be rendered with the `script/serve.sh` script."
-msgstr ""
+msgstr "如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` "
+"腳本來渲染網站。"
 
 #: ./README.md:block 27 (header)
 msgid "Testing"
-msgstr ""
+msgstr "測試"
 
 #: ./README.md:block 28 (paragraph)
 msgid ""
 "A variety of test scripts are included. The script `script/test-all.sh` "
 "wraps running of all local tests."
-msgstr ""
+msgstr "本標準包含許多測試腳本。`script/test-all.sh`腳本則會開始執行所有本機測試。"
 
 #: ./README.md:block 29 (paragraph)
 msgid ""
 "See the scripts in the "
 "[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
 msgstr ""
+"所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/"
+"script)檔案夾。"
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
-msgstr ""
+msgstr "生成公共程式標準PDF檔案"
 
 #: ./README.md:block 31 (paragraph)
 msgid ""
@@ -1558,26 +1704,30 @@ msgid ""
 "[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
 "used to transform PDFs into `.epub`."
 msgstr ""
+"除了Jekyll以外，要生成PDF檔案也需要仰賴[Weasyprint](https://weasyprint.org/"
+")以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/"
+")可以將PDF轉換成`.epub`檔案。"
 
 #: ./README.md:block 32 (paragraph)
 msgid ""
 "To generate these kinds of files, the dependencies should be installed, for "
 "example:"
-msgstr ""
+msgstr "若要生成這些種類的檔案，則需要安裝類似下列的依附元件："
 
 #: ./README.md:block 34 (paragraph)
 msgid ""
 "The file `standard-print.html` can be converted to a nice looking PDF, along"
 " with the other release files, using:"
-msgstr ""
+msgstr "使用以下腳本，可以將`standard-print.html` "
+"檔案以及其他的版本檔案轉換成美觀的PDF："
 
 #: ./README.md:block 36 (header)
 msgid "License"
-msgstr ""
+msgstr "授權"
 
 #: ./README.md:block 37 (paragraph)
 msgid "© [The authors and contributors](AUTHORS.md)"
-msgstr ""
+msgstr "© [作者與貢獻者](AUTHORS.md)"
 
 #: ./README.md:block 38 (paragraph)
 msgid ""
@@ -1586,18 +1736,22 @@ msgid ""
 "it. If you contribute you also grant these rights to others. You can read "
 "more about how to help in the [contributing guide](CONTRIBUTING.md)."
 msgstr ""
+"公共程式標準採用CC 0[授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任"
+"何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一"
+"步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 2 redirect_from:"
-msgstr ""
+msgstr "order: 2 redirect_from:"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 4 (unordered list)
 msgid "criteria/bundle-policy-and-code"
-msgstr ""
+msgstr "criteria/bundle-policy-and-code"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
 msgid "Bundle policy and source code"
-msgstr ""
+msgstr "同捆政策與原始碼"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
 msgid ""
@@ -1606,13 +1760,16 @@ msgid ""
 "anyone to implement the codebase in their local context or contribute to the"
 " further development of the [codebase](../glossary.md#codebase)."
 msgstr ""
+"使用[原始碼](../glossary.md#source-code)以及[政策](../glossary.md#policy)註解"
+"，提供基石給想在當地脈絡使用代碼庫的人或是想要對[代碼庫](../glossary."
+"md#codebase)進一步發展有所貢獻的人。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
 msgid ""
 "Understanding the domain and policies within that domain is fundamental to "
 "understanding what problems a codebase is trying to solve and how it sets "
 "out to solve them."
-msgstr ""
+msgstr "瞭解網域與其政策，才能瞭解代碼庫想要解決的問題以及解決方式。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
 msgid ""
@@ -1620,67 +1777,70 @@ msgid ""
 "organization needs to understand what process changes it must choose to make"
 " or how to contribute additional configurability to the existing solution in"
 " order to adapt it to the new context."
-msgstr ""
+msgstr "組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在"
+"現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
 msgid "Requirements"
-msgstr ""
+msgstr "規定"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "The codebase MUST include the policy that the source code is based on."
-msgstr ""
+msgstr "代碼庫「必須」包含做為原始碼基礎的政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr ""
+msgstr "若一個政策以原始碼為基礎，該原始碼「必須」包含在代碼庫內（用於詐騙偵測的原始"
+"碼除外）。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr ""
+msgstr "政策格式「應該」可以機讀且明確。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
-msgstr ""
+msgstr "[持續整合](../glossary.md#continuous-integration) "
+"測試「應該」驗證原始碼與政策是否有一致執行。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
 msgid "How to test"
-msgstr ""
+msgstr "測試方式"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid ""
 "Confirm with a civil servant that all policy that the source code is based "
 "on is included."
-msgstr ""
+msgstr "與公務人員確認有收錄做為原始碼基礎的完整政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr ""
+msgstr "與公務人員確認有收錄做為政策基礎的完成原始碼。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
-msgstr ""
+msgstr "確認政策是否可由機器判讀。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid ""
 "Check the continuous integration tests for coherent execution of source code"
 " and policy pass."
-msgstr ""
+msgstr "透過持續整合測試，確認原始碼與政策的一致執行。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
 msgid "Public policy makers: what you need to do"
-msgstr ""
+msgstr "公共政策制定者：您的責任"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Collaborate with developers and designers to make sure there is no mismatch "
 "between policy code and source code."
-msgstr ""
+msgstr "與開發人員及設計師合作，確認政策程式碼與原始碼沒有錯配。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1691,30 +1851,36 @@ msgid ""
 "which impact the development or the deployment context of the codebase for "
 "your organization."
 msgstr ""
+"提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有"
+"英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標準，以及影響貴機構代碼"
+"庫開發或部署脈絡的組織流程。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid "Provide references and links to texts which support the policies."
-msgstr ""
+msgstr "引用支持政策的文字並附上連結。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Document policy in formats that are unambiguous and machine-readable, such "
 "as those published by the [Object Management "
 "Group](https://www.omg.org/spec/)."
-msgstr ""
+msgstr "用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/"
+")發佈的格式）來紀錄政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Track policy with [the same version control](maintain-version-control.md) "
 "and documentation used to track source code."
-msgstr ""
+msgstr "利用[相同的版本控制l](maintain-version-control."
+"md)以及用來追蹤原始碼的註解，來追蹤政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Check in regularly to understand how the source code in the codebase has "
 "changed and whether it still matches the [intentions of the "
 "policy](document-codebase-objectives.md)."
-msgstr ""
+msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-"
+"codebase-objectives.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1725,46 +1891,50 @@ msgid ""
 "accessibility), or human rights policies, like a public organization's "
 "commitment to equal opportunity."
 msgstr ""
+"納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-lex."
+"europa.eu/eli/reg/2016/679/oj)或是 [歐盟無障礙指令](https://ec.europa.eu/"
+"digital-single-market/en/web-"
+"accessibility)這些法律義務，或是人權政策（像是公共組織對機會平等的承諾。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
-msgstr ""
+msgstr "管理人員：您的義務"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr ""
+msgstr "在整個開發流程中，讓政策制定者、開發人員與設計師全程參與。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr ""
+msgstr "確保政策制定者、開發人員與設計師有同樣的目標。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
 msgid "Developers and designers: what you need to do"
-msgstr ""
+msgstr "開發人員與設計師：您的責任"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr ""
+msgstr "熟悉並且學會使用貴機構的政策制定者所使用的流程模型標記法。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid ""
 "Work together with policy makers to make sure there is no mismatch between "
 "policy code and source code."
-msgstr ""
+msgstr "與政策制定者合作，確保政策程式碼與原始碼沒有錯配。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid "Give feedback on how to make policy documentation more clear."
-msgstr ""
+msgstr "針對如何讓政策註解更明確提供意見回饋。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
 msgid "Further reading"
-msgstr ""
+msgstr "延伸閱讀"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
@@ -1772,12 +1942,16 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
 " on Wikipedia."
 msgstr ""
+"維基百科的[商業流程模型與標記法](https://en.wikipedia.org/wiki/"
+"Business_Process_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
+"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/"
+"view-bpmn-quick-guide/)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
@@ -1785,65 +1959,73 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
 "Wikipedia."
 msgstr ""
+"維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/"
+"Decision_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
 "Wikipedia."
-msgstr ""
+msgstr "維基百科的[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。"
 
 #: ./criteria/code-in-the-open.md:block 3 (header)
+#, fuzzy
 msgid "order: 1"
-msgstr ""
+msgstr "order: 1"
 
 #: ./criteria/code-in-the-open.md:block 4 (header)
 msgid "Code in the open"
-msgstr ""
+msgstr "以開放精神編寫原始碼"
 
 #: ./criteria/code-in-the-open.md:block 5 (paragraph)
 msgid ""
 "Coding in the open improves transparency, increases [source "
 "code](../glossary.md#source-code) quality, makes the source code easier to "
 "audit, and enables collaboration."
-msgstr ""
+msgstr "開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-"
+"code)品質、讓原始碼更容易稽查，並且讓協作更容易。"
 
 #: ./criteria/code-in-the-open.md:block 6 (paragraph)
 msgid ""
 "Together, this creates more opportunities for citizens to understand how "
 "software and [policy](../glossary.md#policy) impact their interactions with "
 "a public organization."
-msgstr ""
+msgstr "這讓市民更能夠瞭解軟體與[政策](../glossary."
+"md#policy)如何影響他們與公共組織的互動。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any policy in use (unless used for fraud detection) MUST"
 " be published and publicly accessible."
-msgstr ""
+msgstr "任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用"
+"。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr ""
+msgstr "任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用"
+"。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST NOT contain sensitive information regarding users, their "
 "organization or third parties."
-msgstr ""
+msgstr "代碼庫「不允許」包含使用者、使用者機構或第三方的敏感資料。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr ""
+msgstr "目前沒有使用的任何原始碼(像是新版本、提案或舊版本)都「應該」公佈。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "Documenting which source code or policy underpins any specific interaction "
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-"
+"public)與任何組織互動的原始碼或政策。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
@@ -1851,53 +2033,57 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr ""
+msgstr "確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須"
+"任何形式的驗證或認證也可以看到。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
 "Confirm that the [codebase](../glossary.md#codebase) files and commit "
 "history do not include sensitive information."
-msgstr ""
+msgstr "確認[代碼庫](../glossary.md#codebase)檔案與提交紀錄不包含敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid "Check for the publication of source code not currently in use."
-msgstr ""
+msgstr "檢查現在沒有使用的原始碼是否有公開。"
 
 #: ./criteria/code-in-the-open.md:block 12 (unordered list)
 msgid "Develop policies in the open."
-msgstr ""
+msgstr "以開放精神制定政策。"
 
 #: ./criteria/code-in-the-open.md:block 12 (unordered list)
 msgid "Prioritize open and transparent policies."
-msgstr ""
+msgstr "以公開透明的政策為優先。"
 
 #: ./criteria/code-in-the-open.md:block 14 (unordered list)
 msgid "Develop a culture that embraces openness, learning and feedback."
-msgstr ""
+msgstr "孕育擁抱開放、重視學習、歡迎意見回饋的文化。"
 
 #: ./criteria/code-in-the-open.md:block 14 (unordered list)
 msgid ""
 "Collaborate with external vendors and freelancers by working in the open."
-msgstr ""
+msgstr "與外部供應商和自由工作者以開放精神的方式協作。"
 
 #: ./criteria/code-in-the-open.md:block 16 (unordered list)
 msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr ""
+msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者"
+"名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 16 (unordered list)
 msgid ""
 "Clearly split data and source code, in order to meet the requirement about "
 "sensitive information above."
-msgstr ""
+msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
 "[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
 " by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
+"12/coding-in-the-open/)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -1906,6 +2092,9 @@ msgid ""
 "guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
 "Service."
 msgstr ""
+"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/"
+"government/publications/open-source-guidance/when-code-should-be-open-or-"
+"closed)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -1914,6 +2103,9 @@ msgid ""
 "guidance/security-considerations-when-coding-in-the-open) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
+"government/publications/open-source-guidance/security-considerations-when-"
+"coding-in-the-open)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -1921,22 +2113,29 @@ msgid ""
 "manual/technology/deploying-software-regularly) by the UK Government Digital"
 " Service."
 msgstr ""
+"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/"
+"technology/deploying-software-regularly)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
 "[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
 "use-github/) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[政府數位服務團如何使用 GitHub](https://gdstechnology."
+"blog.gov.uk/2014/01/27/how-we-use-github/)》。"
 
 #: ./criteria/document-codebase-maturity.md:block 3 (header)
+#, fuzzy
 msgid ""
 "order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
 "maturity"
 msgstr ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
 
 #: ./criteria/document-codebase-maturity.md:block 4 (header)
 msgid "Document codebase maturity"
-msgstr ""
+msgstr "記錄代碼庫成熟度"
 
 #: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
 msgid ""
@@ -1946,62 +2145,68 @@ msgid ""
 "codebase has evolved is key to understanding the codebase and how to "
 "contribute to it."
 msgstr ""
+"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或"
+"為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解代碼庫的演變，才"
+"能真正認識該代碼庫並且做出貢獻。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The codebase MUST be versioned."
-msgstr ""
+msgstr "代碼庫必須註明版本編號。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase MUST prominently document whether or not there are versions of "
 "the codebase that are ready to use."
-msgstr ""
+msgstr "代碼庫必須明確標示是否有已經準備好使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "Codebase versions that are ready to use MUST only depend on versions of "
 "other codebases that are also ready to use."
-msgstr ""
+msgstr "準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本"
+"。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr ""
+msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The method for assigning version identifiers SHOULD be documented."
-msgstr ""
+msgstr "應該有文件記錄分配版本識別碼的方式。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "It is OPTIONAL to use semantic versioning."
-msgstr ""
+msgstr "可選擇是否使用語意化版本控制。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that the codebase has a strategy for versioning which is documented."
-msgstr ""
+msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that it is obvious to policy makers, managers, developers and "
 "designers whether the codebase has versions that are ready to use."
-msgstr ""
+msgstr "確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使"
+"用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that ready to use versions of the codebase do not depend on any "
 "versions of other codebases that are not ready to use."
-msgstr ""
+msgstr "確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何"
+"版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Check that the versioning scheme of the codebase is documented and followed."
-msgstr ""
+msgstr "確認有記錄並遵守代碼庫的版本控制方式。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid "Check that there is a log of changes."
-msgstr ""
+msgstr "確認是否有版本的變動紀錄。"
 
 #: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
 msgid ""
@@ -2009,37 +2214,40 @@ msgid ""
 " code](../glossary.md#source-code) developed needs to be tested and improved"
 " before it can be put into service."
 msgstr ""
+"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 "
+"[程式碼](../glossary.md#source-code) 都必須先經過測試與改善，才能夠投入服務。"
 
 #: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
 msgid ""
 "Consider versioning policy changes, especially when they trigger new "
 "versions of the source code."
-msgstr ""
+msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。"
 
 #: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
 msgid ""
 "Make sure that services only rely on versions of codebases of equal or "
 "greater maturity than the service. For example, don't use a beta version of "
 "a codebase in a production service."
-msgstr ""
+msgstr "要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 公測版代碼庫。"
 
 #: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
 msgid ""
 "Make sure that the codebase versioning approach is followed for all "
 "releases."
-msgstr ""
+msgstr "確認所有發行都遵守代碼庫版本控制方式。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Semantic Versioning Specification](https://semver.org/) used by many "
 "codebases to label versions."
-msgstr ""
+msgstr "許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Software release life "
 "cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
-msgstr ""
+msgstr "[軟體發行生命週期](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
@@ -2047,24 +2255,30 @@ msgid ""
 "advice/build-and-improve-services/service-design-and-delivery-process) by "
 "the Australian Digital Transformation Agency."
 msgstr ""
+"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
+"build-and-improve-services/service-design-and-delivery-process)》。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
 "delivery) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
+"agile-delivery)》。"
 
 #: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 8 redirect_from:"
-msgstr ""
+msgstr "order: 8 redirect_from:"
 
 #: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/document-objectives"
-msgstr ""
+msgstr "criteria/document-objectives"
 
 #: ./criteria/document-codebase-objectives.md:block 5 (header)
 msgid "Document codebase objectives"
-msgstr ""
+msgstr "記錄代碼庫目標"
 
 #: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
 msgid ""
@@ -2074,43 +2288,49 @@ msgid ""
 "provide an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
 msgstr ""
+"清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害"
+"關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷目前或未來是否會"
+"對此代碼庫（或其模組之一）有興趣。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST contain documentation of its objectives, like a mission "
 "and goal statement, that is understandable by developers and designers so "
 "that they can use or contribute to the codebase."
-msgstr ""
+msgstr "代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要"
+"能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr ""
+msgstr "代碼庫文件應該清楚描述[政策](../glossary."
+"md#policy)目標與代碼庫目標之前的關聯。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-"
+"public)看的代碼庫目標。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase documentation includes the codebase objectives, "
 "mission or goal."
-msgstr ""
+msgstr "確認代碼庫文件有包含代碼庫目標，或主旨、使命等。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
 "Check for descriptions of connections between policy objectives and codebase"
 " objectives."
-msgstr ""
+msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
 
 #: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
 msgid ""
 "Add the policy objectives to the codebase documentation, for example in the "
 "`README`."
-msgstr ""
+msgstr "將政策目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
 msgid ""
@@ -2118,18 +2338,20 @@ msgid ""
 "supporting policy documents added to meet the [Bundle policy and source "
 "code](bundle-policy-and-source-code.md) criterion."
 msgstr ""
+"確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼"
+"要合捆](bundle-policy-and-source-code.md)的標準。"
 
 #: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr ""
+msgstr "將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
 msgid ""
 "Add the technology and design objectives to the codebase documentation, for "
 "example in the `README`."
-msgstr ""
+msgstr "將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
 msgid ""
@@ -2137,18 +2359,22 @@ msgid ""
 "objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
 " by Marek Hajduczenia."
 msgstr ""
+"Marek Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
+"RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
 
 #: ./criteria/document-the-code.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 9 redirect_from:"
-msgstr ""
+msgstr "order: 9 redirect_from:"
 
 #: ./criteria/document-the-code.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/documenting"
-msgstr ""
+msgstr "criteria/documenting"
 
 #: ./criteria/document-the-code.md:block 5 (header)
 msgid "Document the code"
-msgstr ""
+msgstr "記錄程式碼"
 
 #: ./criteria/document-the-code.md:block 6 (paragraph)
 msgid ""
@@ -2157,6 +2383,9 @@ msgid ""
 "essential for people to start using the [codebase](../glossary.md#codebase) "
 "and contributing to it more quickly."
 msgstr ""
+"詳細記錄的[程式碼](../glossary.md#source-code)幫助民眾瞭解該原始碼的作用與使"
+"用方式。記錄文件是幫助民眾開始使用[代碼庫](../glossary."
+"md#codebase)並且更快做出貢獻的關鍵。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2164,18 +2393,20 @@ msgid ""
 " well as source code, MUST be described in language clearly understandable "
 "for those that understand the purpose of the codebase."
 msgstr ""
+"代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的"
+"用語描述，讓懂代碼庫目的用途的人也能夠理解。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain a description of how to "
 "install and run the software."
-msgstr ""
+msgstr "代碼庫文件必須說明如何安裝與執行軟體。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr ""
+msgstr "代碼庫文件必須為關鍵功能舉出範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2183,95 +2414,101 @@ msgid ""
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
 msgstr ""
+"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-"
+"public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr ""
+msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也"
+"應該包含測試資料集。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr ""
+msgstr "代碼庫文件應該包含所有功能的範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr ""
+msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架"
+"構圖表示。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "There SHOULD be [continuous integration](../glossary.md#continuous-"
 "integration) tests for the quality of the documentation."
-msgstr ""
+msgstr "應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr ""
+msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以"
+"清楚明白。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Confirm that the documentation describes how to install and run the source "
 "code."
-msgstr ""
+msgstr "確認文件有說明如何安裝與執行原始碼。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Confirm that the documentation includes examples of the key functionality."
-msgstr ""
+msgstr "確認文件有包含主要功能的範例。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr ""
+msgstr "向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Check that the instructions for how to install and run a standalone version "
 "of the source code result in a running system."
-msgstr ""
+msgstr "檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid "Check that all functionality documented contains an example."
-msgstr ""
+msgstr "檢查文件中列舉的所有功能都包含範例。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Check that the documentation includes a high level architectural diagram or "
 "similar."
-msgstr ""
+msgstr "檢查文件中是否包含高層架構圖，或類似的組件關係圖表。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated correctly, and links and images are "
 "tested."
-msgstr ""
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與"
+"圖片等。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed."
-msgstr ""
+msgstr "定期檢查代碼庫中非政策程式碼的變動。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
-msgstr ""
+msgstr "針對如何讓非政策文字更清楚提供意見。"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -2279,64 +2516,74 @@ msgid ""
 " and source code are documented. For example, is the current documentation "
 "sufficient to persuade a manager at another public organization to use this "
 "codebase?"
-msgstr ""
+msgstr "嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的"
+"文件是否足以說服另一個公共組織的管理人員使用本代碼庫？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
 "Make sure you understand both the policy and source code as well as the "
 "documentation."
-msgstr ""
+msgstr "確保您同時瞭解政策、原始碼以及文件內容。"
 
 #: ./criteria/document-the-code.md:block 16 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-source code in the codebase has"
 " changed."
-msgstr ""
+msgstr "定期查看代碼庫中非原始碼部分的變動情況。"
 
 #: ./criteria/document-the-code.md:block 16 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
-msgstr ""
+msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
 
 #: ./criteria/document-the-code.md:block 18 (unordered list)
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr ""
+msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
 
 #: ./criteria/index.md:block 3 (header)
+#, fuzzy
 msgid "order: 0"
-msgstr ""
+msgstr "order: 0"
 
 #: ./criteria/index.md:block 4 (header)
 msgid "Criteria"
-msgstr ""
+msgstr "標準"
 
 #: ./criteria/index.md:block 5 (paragraph)
+#, fuzzy
 msgid "{% assign sorted = site.pages | sort:\"order\" %}"
-msgstr ""
+msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
 
 #: ./criteria/index.md:block 6 (paragraph)
+#, fuzzy
 msgid ""
 "{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
 "!= \"index.md\" %}{% if page.title %}"
 msgstr ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
 
 #: ./criteria/index.md:block 7 (ordered list)
+#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 
 #: ./criteria/maintain-version-control.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 6 redirect_from:"
-msgstr ""
+msgstr "order: 6 redirect_from:"
 
 #: ./criteria/maintain-version-control.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/version-control-and-history"
-msgstr ""
+msgstr "criteria/version-control-and-history"
 
 #: ./criteria/maintain-version-control.md:block 5 (header)
 msgid "Maintain version control"
-msgstr ""
+msgstr "維護版本控制"
 
 #: ./criteria/maintain-version-control.md:block 6 (paragraph)
 msgid ""
@@ -2348,147 +2595,156 @@ msgid ""
 "changes in parallel and helps future developers to understand the reasons "
 "for changes."
 msgstr ""
+"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md"
+"#source-code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓"
+"您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人"
+"員針對修改變動平行作業，幫助未來的開發人員瞭解修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All files in the codebase MUST be version controlled."
-msgstr ""
+msgstr "代碼庫中的所有檔案皆必須有版本控制。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All decisions MUST be documented in commit messages."
-msgstr ""
+msgstr "所有決定皆必須記錄成提交訊息。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Every commit message MUST link to discussions and issues wherever possible."
-msgstr ""
+msgstr "每份提交訊息皆必須盡可能附上討論與議題連結。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "The codebase SHOULD be maintained in a distributed version control system."
-msgstr ""
+msgstr "代碼庫應該以分散式版本控制系統作維護。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Contribution guidelines SHOULD require contributors to group relevant "
 "changes in commits."
-msgstr ""
+msgstr "貢獻準則應該要求貢獻者將相關的修改變動提交內容作群組分類。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Maintainers SHOULD mark released versions of the codebase, for example using"
 " revision tags or textual labels."
-msgstr ""
+msgstr "維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Contribution guidelines SHOULD encourage file formats where the changes "
 "within the files can be easily viewed and understood in the version control "
 "system."
-msgstr ""
+msgstr "貢獻準則應該鼓勵採用方便版本控制系統檢視檔案修改內容的檔案格式。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr ""
+msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內"
+"容有疑問時，可以與之前的貢獻者聯絡。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase is kept in version control using software such as "
 "Git."
-msgstr ""
+msgstr "確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Review the commit history, confirming that all commit messages explain why "
 "the change was made."
-msgstr ""
+msgstr "審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Review the commit history, confirming that where possible all commit "
 "messages include the discussion about the change was or where to find it "
 "(with a URL)."
-msgstr ""
+msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方"
+"，包含變動內容以及連結位置（提供網址）。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid "Check if the version control system is distributed."
-msgstr ""
+msgstr "檢查版本控制系統是否為分散式。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Review the commit history, check if grouping of relevant changes in "
 "accordance with the contributing guidelines."
-msgstr ""
+msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Check that it is possible to access a specific version of the codebase, for "
 "example through a revision tag or a textual label."
-msgstr ""
+msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr ""
+msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid ""
 "If a new version of the codebase is created because of a "
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
-msgstr ""
+msgstr "如果因為[政策](../glossary."
+"md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid "what the policy change is,"
-msgstr ""
+msgstr "政策改變的地方，"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid "how it's changed the codebase."
-msgstr ""
+msgstr "代碼庫如何因應而改變。"
 
 #: ./criteria/maintain-version-control.md:block 13 (paragraph)
 msgid ""
 "For example, adding a new category of applicant to a codebase that manages "
 "granting permits would be considered a policy change."
-msgstr ""
+msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政"
+"策變動。"
 
 #: ./criteria/maintain-version-control.md:block 15 (unordered list)
 msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr ""
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保"
+"改善代碼庫不會有公關風險。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Make sure that all files required to understand the code, build and deploy "
 "are in the version control system."
-msgstr ""
+msgstr "確認版本控制系統具有瞭解程式碼、組建與部署所需的所有檔案。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Write clear commit messages so that it is easy to understand why the commit "
 "was made."
-msgstr ""
+msgstr "提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Mark different versions so that it is easy to access a specific version, for"
 " example using revision tags or textual labels."
-msgstr ""
+msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."
-msgstr ""
+msgstr "提交內容的訊息要寫清楚，方便之後比較各版本。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Work with policy makers to describe how the source code was updated after a "
 "policy change."
-msgstr ""
+msgstr "在政策改變以後與政策制定者合作，說明原始碼更新的內容。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2496,6 +2752,8 @@ msgid ""
 "Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
 "Fogel."
 msgstr ""
+"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc"
+".html#vc-vocabulary)》。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2503,26 +2761,33 @@ msgid ""
 "manual/technology/maintaining-version-control-in-coding) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/"
+"technology/maintaining-version-control-in-coding)》。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
 "[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
 "use GitHub or refresh your skills."
 msgstr ""
+"GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 "
+"GitHub，或是重溫您的技巧。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
 "[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
 "education.pdf) by GitHub, a list with the most common used git commands."
 msgstr ""
+"GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-"
+"education.pdf)」列出了最常用的 git 指令。"
 
 #: ./criteria/make-contributing-easy.md:block 3 (header)
+#, fuzzy
 msgid "order: 5"
-msgstr ""
+msgstr "order: 5"
 
 #: ./criteria/make-contributing-easy.md:block 4 (header)
 msgid "Make contributing easy"
-msgstr ""
+msgstr "貢獻要容易"
 
 #: ./criteria/make-contributing-easy.md:block 5 (paragraph)
 msgid ""
@@ -2530,110 +2795,118 @@ msgid ""
 " able to fix problems, add features, and address security issues of the "
 "shared [codebase](../glossary.md#codebase)."
 msgstr ""
+"若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫]("
+"../glossary.md#codebase)修復問題與新增功能。"
 
 #: ./criteria/make-contributing-easy.md:block 6 (paragraph)
 msgid ""
 "A shared digital infrastructure makes it easier to make collaborative "
 "contributions. The less effort it takes to make contributions that are "
 "accepted by the codebase, the more likely users are to become contributors."
-msgstr ""
+msgstr "共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者"
+"越可能成為貢獻者。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have a public issue tracker that accepts suggestions from "
 "anyone."
-msgstr ""
+msgstr "代碼庫必須有個可以公開接受任何人建議的議題追蹤器。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr ""
+msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在"
+"「`README`」檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr ""
+msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵寄"
+"清單）。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "There MUST be a way to report security issues for responsible disclosure "
 "over a closed channel."
-msgstr ""
+msgstr "必須有辦法透過封閉的管道通報安全性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The documentation MUST include instructions for how to report potentially "
 "security sensitive issues."
-msgstr ""
+msgstr "文件必須說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid "Confirm that there is a public issue tracker."
-msgstr ""
+msgstr "確認有公開的議題追蹤器。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase contains links to the public issue tracker and "
 "submitted codebase changes."
-msgstr ""
+msgstr "確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid ""
 "Confirm that it is possible to participate in a discussion with other users "
 "and developers about the software using channels described in the codebase."
-msgstr ""
+msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid "Confirm that there is a closed channel for reporting security issues."
-msgstr ""
+msgstr "確認有封閉的管道通報安全性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid ""
 "Confirm that there are instructions for privately reporting security issues."
-msgstr ""
+msgstr "確認有說明如何私下通報安全性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 12 (unordered list)
 msgid ""
 "Track [policy](../glossary.md#policy) issues in the codebase, so that a "
 "relevant external policy expert can volunteer help."
-msgstr ""
+msgstr "追蹤代碼庫中的[政策](../glossary."
+"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
 
 #: ./criteria/make-contributing-easy.md:block 14 (unordered list)
 msgid ""
 "Track management issues in the codebase, so that external managers with "
 "relevant experience can volunteer help."
-msgstr ""
+msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
 
 #: ./criteria/make-contributing-easy.md:block 14 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr ""
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久"
+"貢獻。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Just like for [reviews](require-review-of-contributions.md), make sure to "
 "respond to requests promptly."
-msgstr ""
+msgstr "跟[審查](require-review-of-contributions.md)一樣，務必迅速回應請求。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Keep your managers informed of the time and resources you require to support"
 " other contributors."
-msgstr ""
+msgstr "告知管理人員您支持其他貢獻者時所需的時間與資源。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Make sure that appropriate communication channels for asking maintainers and"
 " stakeholders questions are easy to locate, for instance in the README."
-msgstr ""
+msgstr "確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`"
+"」文件當中。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Make sure that appropriate contact details are included in the metadata, for"
 " instance in the publiccode.yml file."
-msgstr ""
+msgstr "確保中介資料包含合適的聯絡資訊，例如在publiccode.yml檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 18 (unordered list)
 msgid ""
@@ -2641,24 +2914,31 @@ msgid ""
 "project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
 "to-your-open-source-project-1ebf) by Joel Hans."
 msgstr ""
+"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/"
+"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
+"project-1ebf)》。"
 
 #: ./criteria/make-contributing-easy.md:block 18 (unordered list)
 msgid ""
 "[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
 "benefits-of-coding-in-the-open/) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
+"2017/09/04/the-benefits-of-coding-in-the-open/)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 14 redirect_from:"
-msgstr ""
+msgstr "order: 14 redirect_from:"
 
 #: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/findability"
-msgstr ""
+msgstr "criteria/findability"
 
 #: ./criteria/make-the-codebase-findable.md:block 5 (header)
 msgid "Make the codebase findable"
-msgstr ""
+msgstr "代碼庫可查詢得到"
 
 #: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
 msgid ""
@@ -2666,6 +2946,8 @@ msgid ""
 "potential new collaborators will find it. Just publishing a codebase and "
 "hoping it is found does not work, instead proactiveness is needed."
 msgstr ""
+"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到"
+"它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必須主動積極。"
 
 #: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
 msgid ""
@@ -2675,47 +2957,55 @@ msgid ""
 "the codebase easier for people to refer, cite, disambiguate and discover "
 "through third party tools."
 msgstr ""
+"有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料"
+"，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄列表之"
+"中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用"
+"、辨別、發現代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr ""
+msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或"
+"組織單位品牌名稱或抬頭等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a short description that helps someone understand "
 "what the codebase is for or what it does."
-msgstr ""
+msgstr "代碼庫說明應該要簡短，幫助他人瞭解代碼庫的性質與作用。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr ""
+msgstr "維護人員應該將代碼庫提交至相關的軟體目錄上。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr ""
+msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理"
+"人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by codebase name."
-msgstr ""
+msgstr "在搜尋引擎查找代碼庫名稱時，應該能搜尋得到代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by describing the "
 "problem it solves in natural language."
-msgstr ""
+msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼"
+"庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a unique and persistent identifier where the entry "
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
-msgstr ""
+msgstr "代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../gloss"
+"ary.md#repository)、位置、網站等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -2723,135 +3013,141 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
+"代碼庫應該包含機器可讀的中介資料說明，例如採用[publiccode.yml](https://github"
+".com/publiccodeyml/publiccode.yml)格式的檔案。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否為代碼庫設定專用的網域名稱。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Regular presentations at conferences by the community are OPTIONAL."
-msgstr ""
+msgstr "可選擇是否在社群舉辦的會議中定期進行簡報。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check that the codebase name is descriptive and free of puns."
-msgstr ""
+msgstr "檢查代碼庫名稱是否描述說明其用途，且不包含雙關語。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of acronyms and abbreviations or that "
 "the acronyms or abbreviations in the name are more universally known than "
 "the longer forms."
-msgstr ""
+msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整"
+"名稱更熟為人知。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of organizational branding, unless that"
 " organization is of the codebase community itself."
-msgstr ""
+msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員"
+"）。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase repository has a short description of the codebase."
-msgstr ""
+msgstr "檢查代碼庫儲存庫是否包含代碼庫的簡短描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check for the codebase listing in relevant software catalogs."
-msgstr ""
+msgstr "檢查代碼庫有刊登在相關軟體型錄上。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check for a codebase website which describes the problem the codebase "
 "solves."
-msgstr ""
+msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by the codebase name."
-msgstr ""
+msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋"
+"結果的第一頁中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by using natural language, for instance, using the "
 "short description."
-msgstr ""
+msgstr "檢查以自然語言（例如簡短說明ㄢ來作搜尋時，有超過一個的常用主流搜尋引擎，都將"
+"代碼庫放在搜尋結果的第一頁中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for mention of the major "
 "contributors."
-msgstr ""
+msgstr "檢查永久唯一識別碼條目有提及主要貢獻者。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the repository location."
-msgstr ""
+msgstr "檢查永久唯一識別碼條目中有包含儲存庫位置。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the codebase website."
-msgstr ""
+msgstr "檢查永久唯一識別碼條目有列出代碼庫網站。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check for a machine-readable metadata description file."
-msgstr ""
+msgstr "檢查中介資料說明檔案是機器可讀的格式。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Contribute a description of the policy area or problem this codebase acts on"
 " or operates."
-msgstr ""
+msgstr "貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Test your problem description with peers outside of your context who aren't "
 "familiar with the codebase."
-msgstr ""
+msgstr "請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Present on how the codebase implements the [policy](../glossary.md#policy) "
 "at relevant conferences."
-msgstr ""
+msgstr "在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Search trademark databases to avoid confusion or infringement before "
 "deciding the name."
-msgstr ""
+msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as social media account descriptions."
-msgstr ""
+msgstr "使用簡短描述說明參照代碼庫的地方，例如社群媒體帳號說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Budget for content design and Search Engine Optimization skills in the team."
-msgstr ""
+msgstr "為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Make sure people involved in the project present at relevant conferences."
-msgstr ""
+msgstr "確保專案參與人員出席相關會議或作簡報介紹。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid ""
 "Search engine optimization, for instance adding a "
 "[sitemap](https://www.sitemaps.org/protocol.html)."
-msgstr ""
+msgstr "搜尋引擎最佳化，例如新增[網站地圖](https://www.sitemaps.org/protocol.html)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as the repository description."
-msgstr ""
+msgstr "在參照代碼庫的地方，都使用簡短描述，例如儲存庫的說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid "Suggest conferences to present at and present at them."
-msgstr ""
+msgstr "推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。"
 
 #: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
 msgid ""
@@ -2859,12 +3155,15 @@ msgid ""
 "Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
 "Wikidata community."
 msgstr ""
+"Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/"
+"Wikidata:Introduction)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
 msgid ""
 "[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
 "by the Free Software Foundation."
-msgstr ""
+msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
+"Main_Page)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
 msgid ""
@@ -2875,24 +3174,32 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
+"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
+"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
+"分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
+"對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 3 redirect_from:"
-msgstr ""
+msgstr "order: 3 redirect_from:"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
 #: list)
+#, fuzzy
 msgid "criteria/reusable-and-portable-codebases"
-msgstr ""
+msgstr "criteria/reusable-and-portable-codebases"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
 #: list)
+#, fuzzy
 msgid "criteria/create-reusable-and-portable-code"
-msgstr ""
+msgstr "criteria/create-reusable-and-portable-code"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
 msgid "Make the codebase reusable and portable"
-msgstr ""
+msgstr "使代碼庫可重複使用且具可攜性"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
 msgid ""
@@ -2901,6 +3208,9 @@ msgid ""
 "improve it and contribute those improvements back, leading to better "
 "quality, cheaper maintenance and higher reliability."
 msgstr ""
+"編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人"
+"員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，如"
+"此可提高品質、降低維護成本、增強可靠性。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
 msgid ""
@@ -2910,6 +3220,9 @@ msgid ""
 " developed and used by multiple parties are more likely to benefit from a "
 "self-sustaining community."
 msgstr ""
+"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代"
+"碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從能自我運作的社群"
+"中獲益。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
 msgid ""
@@ -2918,156 +3231,165 @@ msgid ""
 "[another context](../glossary.md#different-contexts) if its purpose is "
 "clearly documented."
 msgstr ""
+"以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄"
+"用途的模組，更容易在[另一種情境](../glossary.md#different-"
+"contexts)中重複利用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
 msgid ""
 "Source code which does not rely on the situation-specific infrastructure of "
 "any contributor, vendor or deployment can be tested by any other "
 "contributor."
-msgstr ""
+msgstr "如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都"
+"能測試該原始碼。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase MUST be developed to be reusable in different contexts."
-msgstr ""
+msgstr "代碼庫必須開發成能在不同情境中重複使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed software or services for execution and understanding."
-msgstr ""
+msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程"
+"式碼或服務。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be in use by multiple parties."
-msgstr ""
+msgstr "代碼庫應該有多方單位使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
-msgstr ""
+msgstr "發展路線圖應該有多方單位的需求影響。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The development of the codebase SHOULD be a collaboration between multiple "
 "parties."
-msgstr ""
+msgstr "代碼庫開發應該由多方單位合作。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Configuration SHOULD be used to make [source code](../glossary.md#source-"
 "code) adapt to context specific needs."
-msgstr ""
+msgstr "應該使用組態設定方式以將[程式碼](../glossary.md#source-code) "
+"調整成能適應各情境的特定需求。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be localizable."
-msgstr ""
+msgstr "代碼庫應該能夠在地化。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Source code and its documentation SHOULD NOT contain situation-specific "
 "information."
-msgstr ""
+msgstr "原始碼與其文件不應該包含特定情況專用的資訊。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr ""
+msgstr "代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The software SHOULD NOT require services or platforms available from only a "
 "single vendor."
-msgstr ""
+msgstr "軟體不應該要求只有單一供應商能提供的服務或平台。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "use the codebase and what that would entail."
-msgstr ""
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行"
+"。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed software or services."
-msgstr ""
+msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "If the codebase is in early development before a production-ready release, "
 "then check for evidence of ambition to obtain collaborators."
-msgstr ""
+msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願"
+"。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Or if the codebase is very mature and stable with very infrequent fixes, "
 "patches, or contributions:"
-msgstr ""
+msgstr "或是如果代碼庫非常成熟與穩定，鮮少需要修復或貢獻："
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the codebase is in use by multiple parties or in multiple "
 "contexts."
-msgstr ""
+msgstr "檢查是否有多方單位或是有在多種情境下正使用代碼庫。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid "Check for documented and budgeted commitments of collaboration."
-msgstr ""
+msgstr "檢查是否有文件記錄下合作的承諾以及承諾的預算。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid "Otherwise:"
-msgstr ""
+msgstr "若是沒有，則："
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid "Check that the codebase contributors are from multiple parties."
-msgstr ""
+msgstr "檢查代碼庫貢獻者是否來自多方單位。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr ""
+msgstr "檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the software can be deployed and run without services or "
 "platforms available from a single vendor."
-msgstr ""
+msgstr "檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid ""
 "Document your [policy](../glossary.md#policy) with enough clarity and detail"
 " that it can be understood outside of its original context."
-msgstr ""
+msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處"
+"於同個原始背景情境也能夠理解。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr ""
+msgstr "確保代碼庫有將貴組織單位列為已知用戶。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid "Identify other organizations for your teams to collaborate with."
-msgstr ""
+msgstr "列出貴團隊想要合作的其他組織。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
@@ -3075,38 +3397,40 @@ msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr ""
+msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式"
+"碼技術債，並讓代碼庫可以永續發展。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
 msgid "Make sure that your teams are collaborating with other teams."
-msgstr ""
+msgstr "確認您的團隊與其他團隊協作。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
 msgid "Source should be designed:"
-msgstr ""
+msgstr "原始碼應該設計成："
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
 #: list)
 msgid "for reuse by other users and organizations regardless of locale,"
-msgstr ""
+msgstr "能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
 #: list)
 msgid "to solve a general problem instead of a specific one,"
-msgstr ""
+msgstr "能解決通用性質問題，而非特定問題，"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
 #: list)
 msgid "in logically meaningful and isolated modules,"
-msgstr ""
+msgstr "以邏輯上具有意義且獨立的模組構成，"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
 #: list)
 msgid ""
 "so that someone in a similar organization facing a similar problem would be "
 "able to use (parts of) the solution."
-msgstr ""
+msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份"
+"）。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
 msgid ""
@@ -3115,13 +3439,17 @@ msgid ""
 "platforms or using proprietary components, make sure that collaborators can "
 "develop, use, test, and deploy without them."
 msgstr ""
+"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要"
+"將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者"
+"的情況下，就能進行開發、使用、測試、部署等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr ""
+msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
+"人與組織單位資料、代符與密碼等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
 #: list)
@@ -3130,6 +3458,8 @@ msgid ""
 "manual/technology/making-source-code-open-and-reusable) by the UK Government"
 " Digital Service."
 msgstr ""
+"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/"
+"service-manual/technology/making-source-code-open-and-reusable)》。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
 #: list)
@@ -3138,18 +3468,22 @@ msgid ""
 "Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
 " the World Wide Web Consortium."
 msgstr ""
+"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/"
+"questions/qa-i18n)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 13 redirect_from:"
-msgstr ""
+msgstr "order: 13 redirect_from:"
 
 #: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/open-licenses"
-msgstr ""
+msgstr "criteria/open-licenses"
 
 #: ./criteria/publish-with-an-open-license.md:block 5 (header)
 msgid "Publish with an open license"
-msgstr ""
+msgstr "發行採用開放授權"
 
 #: ./criteria/publish-with-an-open-license.md:block 6 (paragraph)
 msgid ""
@@ -3159,50 +3493,56 @@ msgid ""
 "[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
 "emerge around the codebase."
 msgstr ""
+"有了開放且熟為人知的授權，任何人都可以看到[原始碼](../glossary.md#source-"
+"code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼庫](../glossary."
+"md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。"
 
 #: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
 msgid ""
 "Clearly indicating the license for each file within a codebase facilitates "
 "correct reuse and attribution of parts of a codebase."
-msgstr ""
+msgstr "明確標示代碼庫中每一個檔案的授權，幫助使用者正確重複利用與引用代碼庫的內容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "All source code and documentation MUST be licensed such that it may be "
 "freely reusable, changeable and redistributable."
-msgstr ""
+msgstr "所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授"
+"權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Software source code MUST be licensed under an [OSI-approved or FSF "
 "Free/Libre license](https://spdx.org/licenses/)."
 msgstr ""
+"軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid "All source code MUST be published with a license file."
-msgstr ""
+msgstr "所有程式碼皆必須搭配授權條款檔案一併發行。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the codebase."
-msgstr ""
+msgstr "不得要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr ""
+msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Having multiple licenses for different types of source code and "
 "documentation is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否為不同類型的原始碼與文件採用多重授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the codebase is clearly licensed."
-msgstr ""
+msgstr "確認代碼庫有清楚給予授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
@@ -3211,41 +3551,50 @@ msgid ""
 "documentation [conforms to the Open "
 "Definition](https://opendefinition.org/licenses/)."
 msgstr ""
+"確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/"
+")，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/"
+"licenses/)。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the licenses used in the codebase are included as files."
-msgstr ""
+msgstr "確認代碼庫中有包含其採用的授權條款檔案。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
 "Confirm that contribution guidelines and "
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
-msgstr ""
+msgstr "確認貢獻指南中，以及[儲存庫](../glossary."
+"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
 "Check for machine-readable license checking in the codebase [continuous "
 "integration](../glossary.md#continuous-integration) tests."
 msgstr ""
+"在代碼庫[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
 
 #: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
 msgid ""
 "Develop [policy](../glossary.md#policy) that requires source code to be "
 "[open source](../glossary.md#open-source)."
 msgstr ""
+"制定要求原始碼必須採用[開放原始碼](../glossary.md#open-"
+"source)授權的[政策](../glossary.md#policy)。"
 
 #: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
 msgid ""
 "Develop policy that disincentivizes non-open source code and technology in "
 "procurement."
-msgstr ""
+msgstr "制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
 "Only work with open source vendors that deliver their source code by "
 "publishing it under an open source license."
-msgstr ""
+msgstr "只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
@@ -3255,28 +3604,32 @@ msgid ""
 "NOT freely reusable, changeable and redistributable and don't fulfill these "
 "requirements."
 msgstr ""
+"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作"
+"品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用"
+"、自由修改、自由再次散布等，因此未能符合規定。"
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid "Add a new `license` file to every new codebase created."
-msgstr ""
+msgstr "每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。"
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid ""
 "Add a copyright notice and a license header to every new source code file "
 "created."
-msgstr ""
+msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid ""
 "When source code is being reused by the codebase, make sure that it has a "
 "license that is compatible with the license or licenses of the codebase."
-msgstr ""
+msgstr "代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
 "[Open source definition](https://opensource.org/osd) by the Open Source "
 "Initiative, all open source licenses meet this definition."
-msgstr ""
+msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/"
+"osd)》，所有開放原始碼授權條款皆符合這套定義。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3284,6 +3637,8 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
+"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3291,31 +3646,38 @@ msgid ""
 "Software Foundation Europe for unambiguous, human-readable and machine-"
 "readable copyright and licensing information."
 msgstr ""
+"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
+")》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
 "[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
 " standardized, machine-readable abbreviations for most licenses."
 msgstr ""
+"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
+")提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
 
 #: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 7 redirect_from:"
-msgstr ""
+msgstr "order: 7 redirect_from:"
 
 #: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/require-review"
-msgstr ""
+msgstr "criteria/require-review"
 
 #: ./criteria/require-review-of-contributions.md:block 5 (header)
 msgid "Require review of contributions"
-msgstr ""
+msgstr "要求審查貢獻內容"
 
 #: ./criteria/require-review-of-contributions.md:block 6 (paragraph)
 msgid ""
 "Peer-review of contributions is essential for [source "
 "code](../glossary.md#source-code) quality, reducing security risks and "
 "operational risks."
-msgstr ""
+msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-"
+"code)品質的關鍵，降低安全性風險與營運風險。"
 
 #: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
 msgid ""
@@ -3326,6 +3688,10 @@ msgid ""
 "Knowing that all source code was reviewed discourages a culture of blaming "
 "individuals, and encourages a culture of focusing on solutions."
 msgstr ""
+"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始"
+"碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發現與修復潛在錯誤"
+"的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個"
+"人都專注在解決方案上。"
 
 #: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
 msgid ""
@@ -3333,139 +3699,143 @@ msgid ""
 "a guaranteed time for feedback or collaborative improvement, which increases"
 " both rate of delivery and contributor engagement."
 msgstr ""
+"快速審查的[政策](../glossary."
+"md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， "
+"進而提高貢獻者交付貢獻內容的頻率以及參與熱度。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "codebase MUST be reviewed by another contributor."
-msgstr ""
+msgstr "所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審"
+"查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews MUST include source, policy, tests and documentation."
-msgstr ""
+msgstr "審查必須包含原始碼、政策、測試與文件等。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Reviewers MUST provide feedback on all decisions to not accept a "
 "contribution."
-msgstr ""
+msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "The review process SHOULD confirm that a contribution conforms to the "
 "standards, architecture and decisions set out in the codebase in order to "
 "pass review."
-msgstr ""
+msgstr "審查流程應該確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Reviews SHOULD include running both the software and the tests of the "
 "codebase."
-msgstr ""
+msgstr "審查內容應該包含執行軟體與執行代碼庫測試。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Contributions SHOULD be reviewed by someone in a different context than the "
 "contributor."
-msgstr ""
+msgstr "貢獻內容應該由與貢獻者不同背景情境的人來審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr ""
+msgstr "版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
-msgstr ""
+msgstr "審查應該在兩個工作天內進行。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Performing reviews by multiple reviewers is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否由多位審查人員進行審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Confirm that every commit in the history has been reviewed by a different "
 "contributor."
-msgstr ""
+msgstr "確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
-msgstr ""
+msgstr "確認審查內容包含原始碼、政策、測試、文件等。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Confirm that rejected contributions were appropriately explained."
-msgstr ""
+msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Check if guidelines for reviewers include instructions to review for "
 "conformance to standards, architecture and codebase guidelines."
-msgstr ""
+msgstr "檢查審查人員指引有涵蓋是否遵循標準、架構、代碼庫指引等。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Check with reviewers if they run the software and tests during review."
-msgstr ""
+msgstr "檢查審查人員在審查時是否有執行程式與測試。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Check with reviewers if commits have been reviewed by a different "
 "contributor in a different context."
-msgstr ""
+msgstr "與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Check for use of branch protection in the [version "
 "control](../glossary.md#version-control) system."
-msgstr ""
+msgstr "檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Check the times between contribution submission and review."
-msgstr ""
+msgstr "檢查貢獻提交與審查之間的時間間隔。"
 
 #: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
 msgid ""
 "Institute a 'four eyes' policy where everything, not just source code, is "
 "reviewed."
-msgstr ""
+msgstr "制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。"
 
 #: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
 msgid ""
 "Use a version control system or methodology that enables review and "
 "feedback."
-msgstr ""
+msgstr "採用具有審查與意見回饋功能的版本控制系統或作業流程。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid "Make delivering great software a shared objective."
-msgstr ""
+msgstr "將交付妥善軟體作為共同目標。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid ""
 "Make sure writing and reviewing contributions to source, policy, "
 "documentation and tests are considered equally valuable."
-msgstr ""
+msgstr "確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid ""
 "Create a culture where all contributions are welcome and everyone is "
 "empowered to review them."
-msgstr ""
+msgstr "創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr ""
+msgstr "確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。"
 
 #: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
 msgid ""
 "Ask other contributors on the codebase to review your work, in your "
 "organization or outside of it."
-msgstr ""
+msgstr "請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。"
 
 #: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
 msgid ""
 "Try to respond to others' requests for review promptly, initially providing "
 "feedback about the concept of the change."
-msgstr ""
+msgstr "當他人請求您審查時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3473,6 +3843,8 @@ msgid ""
 "way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
 " Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way."
+"cloudapps.digital/manuals/code-review-guidelines.html#content)》。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3483,12 +3855,19 @@ msgid ""
 "[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
 "protected/)."
 msgstr ""
+"[GitHub](https://docs.github.com/en/repositories/"
+"configuring-branches-and-merges-in-your-repository/"
+"defining-the-mergeability-of-pull-requests/about-protected-branches) 與 "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/"
+"keeping-your-code-protected/) 平臺的分支保護說明。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
 "[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
 "gentle-art-of-patch-review/) by Sage Sharp."
 msgstr ""
+"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/"
+"the-gentle-art-of-patch-review/)》。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3496,25 +3875,31 @@ msgid ""
 "Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
 "mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
 msgstr ""
+"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/"
+"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id."
+"g43d857af8_0177)》。"
 
 #: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 15 redirect_from:"
-msgstr ""
+msgstr "order: 15 redirect_from:"
 
 #: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/style"
-msgstr ""
+msgstr "criteria/style"
 
 #: ./criteria/use-a-coherent-style.md:block 5 (header)
 msgid "Use a coherent style"
-msgstr ""
+msgstr "風格要前後一致"
 
 #: ./criteria/use-a-coherent-style.md:block 6 (paragraph)
 msgid ""
 "Following a consistent and coherent style enables contributors in different "
 "environments to work together. Unifying vocabularies reduces friction in "
 "communication between contributors."
-msgstr ""
+msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝"
+"通上的摩擦。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
@@ -3522,32 +3907,34 @@ msgid ""
 "guide, either the codebase community's own or an existing one referred to in"
 " the codebase."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指"
+"南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既有風格。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
-msgstr ""
+msgstr "貢獻內容應該通過自動化的風格測試。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
 "The style guide SHOULD include expectations for inline comments and "
 "documentation for non-trivial sections."
-msgstr ""
+msgstr "風格指南應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
 "Including expectations for [understandable English](use-plain-english.md) in"
 " the style guide is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指南之中。"
 
 #: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
 msgid ""
 "Confirm that contributions are in line with the style guides specified in "
 "the documentation."
-msgstr ""
+msgstr "確認貢獻內容有遵循文件中指定的風格指南。"
 
 #: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
 msgid "Check for the presence of automated tests on style."
-msgstr ""
+msgstr "檢查是否有自動化的風格測試。"
 
 #: ./criteria/use-a-coherent-style.md:block 12 (unordered list)
 msgid ""
@@ -3555,12 +3942,14 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
+"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄"
+"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
 
 #: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
 msgid ""
 "Include written language, source, test and policy standards in your "
 "organizational definition of quality."
-msgstr ""
+msgstr "將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。"
 
 #: ./criteria/use-a-coherent-style.md:block 16 (paragraph)
 msgid ""
@@ -3575,36 +3964,45 @@ msgid ""
 "documentation. Continually improve upon and expand this documentation with "
 "the aim of evolving this documentation into engineering guidelines."
 msgstr ""
+"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#r"
+"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
+"前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
+"以及機器不容易檢查的其他層面。指南應該包含貢獻的[原始碼](../glossary.md"
+"#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試"
+"、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
 
 #: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
 msgid "Additionally:"
-msgstr ""
+msgstr "此外："
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Use a linter."
-msgstr ""
+msgstr "使用程式碼品質分析工具 (linter)。"
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr ""
+msgstr "在代碼庫中加入程式碼品質分析工具的組態設定。"
 
 #: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
 msgid ""
 "[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
 "Wikipedia."
-msgstr ""
+msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/"
+"Programming_style)》條目。"
 
 #: ./criteria/use-continuous-integration.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 12 redirect_from:"
-msgstr ""
+msgstr "order: 12 redirect_from:"
 
 #: ./criteria/use-continuous-integration.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/continuous-integration"
-msgstr ""
+msgstr "criteria/continuous-integration"
 
 #: ./criteria/use-continuous-integration.md:block 5 (header)
 msgid "Use continuous integration"
-msgstr ""
+msgstr "使用持續整合"
 
 #: ./criteria/use-continuous-integration.md:block 6 (paragraph)
 msgid ""
@@ -3613,6 +4011,9 @@ msgid ""
 " merging and the smaller the contribution, the easier it is to resolve merge"
 " conflicts."
 msgstr ""
+"開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進"
+"行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易"
+"解決。"
 
 #: ./criteria/use-continuous-integration.md:block 7 (paragraph)
 msgid ""
@@ -3622,6 +4023,8 @@ msgid ""
 " The more focused the test, the easier it is to clearly identify and "
 "understand errors as they arise."
 msgstr ""
+"自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允"
+"許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。"
 
 #: ./criteria/use-continuous-integration.md:block 8 (paragraph)
 msgid ""
@@ -3630,154 +4033,161 @@ msgid ""
 "contributions. Continuous integration allows for an easier monitoring of the"
 " state of the [codebase](../glossary.md#codebase)."
 msgstr ""
+"以文件記錄代碼庫的[持續整合](../glossary.md#continuous-"
+"integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。"
+"透過持續整合可以更輕易地監督 [代碼庫](../glossary.md#codebase)狀態。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "All functionality in the [source code](../glossary.md#source-code) MUST have"
 " automated tests."
-msgstr ""
+msgstr "[原始碼](../glossary.md#source-code)中的所有功能都必須有自動化測試。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Contributions MUST pass all automated tests before they are admitted into "
 "the codebase."
-msgstr ""
+msgstr "所有貢獻內容都必須先通過自動化測試，才能上傳至代碼庫。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have guidelines explaining how to structure contributions."
-msgstr ""
+msgstr "代碼庫必須有說明貢獻內容結構的相關準則。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have active contributors who can review contributions."
-msgstr ""
+msgstr "代碼庫必須有能夠審查貢獻內容的活躍貢獻者。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Automated test results for contributions SHOULD be public."
-msgstr ""
+msgstr "應該公開貢獻的自動化測試結果。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr ""
+msgstr "代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr ""
+msgstr "應該監督原始碼測試與文件的涵蓋範圍。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否測試[政策](../glossary."
+"md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing the software by using examples in the documentation is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否使用文件範例來測試軟體。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid "Confirm that there are tests present."
-msgstr ""
+msgstr "確認有測試可用。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
 "Confirm that source code coverage tools check that coverage is at 100% of "
 "the source code."
-msgstr ""
+msgstr "確認原始碼覆蓋率工具能檢查到 100% 的原始碼。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
 "Confirm that contributions are only admitted into the codebase after all of "
 "the tests are passed."
-msgstr ""
+msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
 "Confirm that contribution guidelines explain how to structure contributions."
-msgstr ""
+msgstr "確認有貢獻準則說明貢獻內容的結構。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
 "Confirm that there are contributions from within the last three months."
-msgstr ""
+msgstr "確認最近三個月內有貢獻內容上傳。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid "Check that test results are viewable."
-msgstr ""
+msgstr "檢查是否可以查看測試結果。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid "Check if source code coverage data is published."
-msgstr ""
+msgstr "檢查是否已經公佈原始碼覆蓋率數據。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
 "Involve managers as well as developers and designers as early in the process"
 " as possible and keep them engaged throughout development of your policy."
-msgstr ""
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序"
+"。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
 "Make sure there are also automated tests set up for policy documentation."
-msgstr ""
+msgstr "確保政策文件也有設好自動化測試。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid "Fix policy documentation promptly if it fails a test."
-msgstr ""
+msgstr "如果政策文件未能通過測試，請立即修正。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
 "Make sure the source code reflects any changes to the policy (see [Maintain "
 "version control](maintain-version-control.md))."
-msgstr ""
+msgstr "確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-"
+"control.md)）。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
 "Make sure to test with real end users as quickly and often as possible."
-msgstr ""
+msgstr "確保能儘快且經常給真正的終端使用者進行測試。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
 "Plan the work to integrate small parts very often instead of large parts "
 "less frequently."
-msgstr ""
+msgstr "以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr ""
+msgstr "聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
 "After a large failure, encourage publication of incident reports and public "
 "discussion of what was learned."
-msgstr ""
+msgstr "發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
 "Help managers structure the work plan such that it can be integrated as "
 "small increments."
-msgstr ""
+msgstr "協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
 "Help contributors limit the scope of their contributions and feature "
 "requests to be as small as reasonable."
-msgstr ""
+msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
 "Help managers and policy makers test their contributions, for example by "
 "testing their contributions for broken links or style."
-msgstr ""
+msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式"
+"。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
@@ -3787,20 +4197,22 @@ msgid ""
 "of storage space and memory allocation failure are typical examples of "
 "difficult to create conditions."
 msgstr ""
+"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
+"來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
 "Tune the test code coverage tools to avoid false alarms resulting from "
 "inlining or other optimizations."
-msgstr ""
+msgstr "調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid "Deploy often."
-msgstr ""
+msgstr "經常部署。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid "Integrate your work at least once a day."
-msgstr ""
+msgstr "至少每天整合工作內容一次。"
 
 #: ./criteria/use-continuous-integration.md:block 20 (unordered list)
 msgid ""
@@ -3808,6 +4220,8 @@ msgid ""
 "integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
 " by Martin Fowler."
 msgstr ""
+"Martin Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/"
+"continuousIntegration.html)》。"
 
 #: ./criteria/use-continuous-integration.md:block 20 (unordered list)
 msgid ""
@@ -3815,6 +4229,8 @@ msgid ""
 "way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
 "Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/"
+"standards/continuous-delivery.html)》。"
 
 #: ./criteria/use-continuous-integration.md:block 20 (unordered list)
 msgid ""
@@ -3822,18 +4238,23 @@ msgid ""
 "regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
 "testing-your-service-regularly) by the UK Government Digital Service."
 msgstr ""
+"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/"
+"service-manual/technology/quality-assurance-testing-your-service-"
+"regularly)》。"
 
 #: ./criteria/use-open-standards.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 11 redirect_from:"
-msgstr ""
+msgstr "order: 11 redirect_from:"
 
 #: ./criteria/use-open-standards.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/open-standards"
-msgstr ""
+msgstr "criteria/open-standards"
 
 #: ./criteria/use-open-standards.md:block 5 (header)
 msgid "Use open standards"
-msgstr ""
+msgstr "採用開放標準"
 
 #: ./criteria/use-open-standards.md:block 6 (paragraph)
 msgid ""
@@ -3844,6 +4265,10 @@ msgid ""
 "unambiguous allow for independent development of either side of data "
 "exchange."
 msgstr ""
+"[開放標準](../glossary.md#open-"
+"standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的知"
+"識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明"
+"確，就可以獨立發展任何方向的資料交換。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -3851,85 +4276,90 @@ msgid ""
 "codebase MUST use an open standard that meets the [Open Source Initiative "
 "Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
+"代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需"
+"求規範](https://opensource.org/osr)的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any non-open standards used MUST be recorded clearly as such in the "
 "documentation."
-msgstr ""
+msgstr "如果有使用到任何的非開放標準，則必須在文件中清楚記錄。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr ""
+msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的"
+"連結。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr ""
+msgstr "代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "If no existing open standard is available, effort SHOULD be put into "
 "developing one."
-msgstr ""
+msgstr "如果還沒有已存在的開放標準可採用，則應該投入開發新標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Open standards that are machine testable SHOULD be preferred over open "
 "standards that are not."
-msgstr ""
+msgstr "採用開放標準時，應該優先選擇可經機器測試的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Non-open standards that are machine testable SHOULD be preferred over non-"
 "open standards that are not."
-msgstr ""
+msgstr "採用非開放標準時，應該優先選擇可經機器測試的非開放標準。"
 
 #: ./criteria/use-open-standards.md:block 10 (unordered list)
 msgid "Confirm that data exchange follows an OSI approved open standard."
-msgstr ""
+msgstr "確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 10 (unordered list)
 msgid ""
 "Confirm that any non-open standards used are clearly documented as such."
-msgstr ""
+msgstr "確認若有採用任何的非開放標準，皆有清楚記錄在文件中。"
 
 #: ./criteria/use-open-standards.md:block 10 (unordered list)
 msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr ""
+msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用"
+"任何標準時，則留下聲明。"
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
-msgstr ""
+msgstr "以政策要求盡可能在任何情況下使用開放標準。"
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Prohibit procurement of technology that does not use open standards."
-msgstr ""
+msgstr "禁止採購不採用開放標準的技術科技。"
 
 #: ./criteria/use-open-standards.md:block 14 (unordered list)
 msgid ""
 "Consider including open standard compliance assessment in [source "
 "code](../glossary.md#source-code) reviews."
-msgstr ""
+msgstr "考慮在 [原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。"
 
 #: ./criteria/use-open-standards.md:block 16 (unordered list)
 msgid ""
 "Add [continuous integration](../glossary.md#continuous-integration) tests "
 "for compliance with the standards."
-msgstr ""
+msgstr "將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。"
 
 #: ./criteria/use-open-standards.md:block 16 (unordered list)
 msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr ""
+msgstr "審查提交紀錄與其他[儲存庫](../glossary."
+"md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
 
 #: ./criteria/use-open-standards.md:block 18 (unordered list)
 msgid ""
@@ -3937,59 +4367,69 @@ msgid ""
 "standards-principles/open-standards-principles), "
 "[policy](../glossary.md#policy) paper of the UK Cabinet Office."
 msgstr ""
+"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/"
+"publications/open-standards-principles/open-standards-"
+"principles)》[政策](../glossary.md#policy)報告。"
 
 #: ./criteria/use-plain-english.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 10 redirect_from:"
-msgstr ""
+msgstr "order: 10 redirect_from:"
 
 #: ./criteria/use-plain-english.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/understandable-english-first"
-msgstr ""
+msgstr "criteria/understandable-english-first"
 
 #: ./criteria/use-plain-english.md:block 5 (header)
 msgid "Use plain English"
-msgstr ""
+msgstr "使用白話的英語"
 
 #: ./criteria/use-plain-english.md:block 6 (paragraph)
 msgid ""
 "English is the <i>de facto</i> language of collaboration in software "
 "development."
-msgstr ""
+msgstr "英文是軟體開發的 <i>慣用</i>協作語言。"
 
 #: ./criteria/use-plain-english.md:block 7 (paragraph)
 msgid ""
 "Public sector information needs to be accessible to all its constituents. "
 "Plain and simple language makes the [code](../glossary.md#code) and what it "
 "does easier to understand for a wider variety of people."
-msgstr ""
+msgstr "選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](.."
+"/glossary.md#code)與其功用。"
 
 #: ./criteria/use-plain-english.md:block 8 (paragraph)
 msgid ""
 "Translations further increase the possible reach of a "
 "[codebase](../glossary.md#codebase). Language that is easy to understand "
 "lowers the cost of creating and maintaining translations."
-msgstr ""
+msgstr "透過翻譯可以讓更多人認識[代碼庫](../glossary."
+"md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid "All codebase documentation MUST be in English."
-msgstr ""
+msgstr "代碼庫的所有文件都必須使用英語。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "All [source code](../glossary.md#source-code) MUST be in English, except "
 "where [policy](../glossary.md#policy) is machine interpreted as code."
 msgstr ""
+"所有[原始碼](../glossary.md#source-"
+"code)都必須使用英語編寫，其中[政策](../glossary."
+"md#policy)是由機器解讀當作程式碼的部分則除外。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "All bundled policy not available in English MUST have an accompanying "
 "summary in English."
-msgstr ""
+msgstr "任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "Any translation MUST be up to date with the English version and vice versa."
-msgstr ""
+msgstr "任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -3997,6 +4437,8 @@ msgid ""
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
 msgstr ""
+"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果"
+"有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4004,46 +4446,51 @@ msgid ""
 "recommended by the [Web Content Accessibility Guidelines "
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
+"根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否提供任何程式碼、文件、測試等的翻譯版。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
-msgstr ""
+msgstr "確認代碼庫文件有英語版本。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid ""
 "Confirm that source code is in English, or confirm any non-English is policy"
 " or terms with preceding explanations."
-msgstr ""
+msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等"
+"。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Confirm any non-English policy has an accompanying summary in English."
-msgstr ""
+msgstr "確認任何非英語政策都有隨附英語版摘要。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid ""
 "Confirm that translations and the English version have the same content."
-msgstr ""
+msgstr "確認翻譯版與英語版內容相同。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr ""
+msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業"
+"特定詞彙等。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
-msgstr ""
+msgstr "檢查文件的拼字、文法與易讀性等。"
 
 #: ./criteria/use-plain-english.md:block 14 (unordered list)
 msgid ""
 "Frequently test with other managers, developers and designers in the process"
 " if they understand what you are delivering and how you document it."
-msgstr ""
+msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交"
+"付的程式碼與其文件的內容。"
 
 #: ./criteria/use-plain-english.md:block 16 (unordered list)
 msgid ""
@@ -4052,24 +4499,29 @@ msgid ""
 "teams and stakeholders. Add any such terms to a glossary and link to it from"
 " the places they are being used."
 msgstr ""
+"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，"
+"或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，"
+"並且在使用這些詞彙的地方加上詞彙表連結。"
 
 #: ./criteria/use-plain-english.md:block 16 (unordered list)
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr ""
+msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其"
+"他人也同樣迷惘。"
 
 #: ./criteria/use-plain-english.md:block 18 (unordered list)
 msgid ""
 "Frequently test with policy makers and managers if they understand what you "
 "are delivering and how you document it."
-msgstr ""
+msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件"
+"的內容。"
 
 #: ./criteria/use-plain-english.md:block 18 (unordered list)
 msgid ""
 "Ask someone outside of your context if they understand the content (for "
 "example, a developer working on a different codebase)."
-msgstr ""
+msgstr "詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4077,6 +4529,9 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
 "readable and understandable."
 msgstr ""
+"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 "
+"之可讀性](https://www.w3.org/TR/WCAG21/"
+"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4084,25 +4539,30 @@ msgid ""
 "single-market/en/web-accessibility) by the European Commission, is an "
 "example of regulation requiring high accessibility."
 msgstr ""
+"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/"
+"digital-single-market/en/web-accessibility)》就是無障礙法規的例子。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
 "[Definition of plain "
 "language](https://www.plainlanguage.gov/about/definitions/) by United States"
 " General Services Administration."
-msgstr ""
+msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/"
+")》。"
 
 #: ./criteria/welcome-contributors.md:block 3 (paragraph)
+#, fuzzy
 msgid "order: 4 redirect_from:"
-msgstr ""
+msgstr "order: 4 redirect_from:"
 
 #: ./criteria/welcome-contributors.md:block 4 (unordered list)
+#, fuzzy
 msgid "criteria/open-to-contributions"
-msgstr ""
+msgstr "criteria/open-to-contributions"
 
 #: ./criteria/welcome-contributors.md:block 5 (header)
 msgid "Welcome contributors"
-msgstr ""
+msgstr "歡迎貢獻者"
 
 #: ./criteria/welcome-contributors.md:block 6 (paragraph)
 msgid ""
@@ -4114,88 +4574,94 @@ msgid ""
 " communities. Newcomers need to understand and trust the codebase "
 "community’s governance."
 msgstr ""
+"[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 歡迎任"
+"何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當中，若貢獻者有明"
+"確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新"
+"參與者需要瞭解並且相信代碼庫社群的治理。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST allow anyone to submit suggestions for changes to the "
 "codebase."
-msgstr ""
+msgstr "代碼庫必須允許任何人針對代碼庫提出修改建議。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr ""
+msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開"
+"發，例如以「`CONTRIBUTING`」檔案說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr ""
+msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
+"RNANCE`」檔案來說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The contribution guidelines SHOULD document who is expected to cover the "
 "costs of reviewing contributions."
-msgstr ""
+msgstr "貢獻指引應該說明由誰負責審查貢獻的成本。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr ""
+msgstr "代碼庫應該宣布投入其開發與維護工作的參與組織單位。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr ""
+msgstr "代碼庫應該要有可公開取得的發展路線圖。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD publish codebase activity statistics."
-msgstr ""
+msgstr "代碼庫應該公布代碼庫的活動統計數據。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr ""
+msgstr "可選擇是否為代碼庫加入貢獻者的行為準則。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Confirm that it is possible to submit suggestions for changes to the "
 "codebase."
-msgstr ""
+msgstr "確認可以提交修改建議給代碼庫。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Confirm there are contribution guidelines."
-msgstr ""
+msgstr "確認代碼庫有貢獻指引。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr ""
+msgstr "確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Check that contributing guidelines cover who is expected to cover the costs "
 "of reviewing contributions."
-msgstr ""
+msgstr "確認貢獻指引是否有說明由誰負責審查貢獻的成本。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for a list of involved organizations."
-msgstr ""
+msgstr "檢查是否有參與的組織單位名單。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for a roadmap."
-msgstr ""
+msgstr "檢查是否有發展路線圖。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for published activity statistics."
-msgstr ""
+msgstr "檢查是否有公布活動統計數據。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for a code of conduct."
-msgstr ""
+msgstr "檢查是否有行為準則。"
 
 #: ./criteria/welcome-contributors.md:block 12 (unordered list)
 msgid ""
@@ -4203,58 +4669,63 @@ msgid ""
 "[policy](../glossary.md#policy) experts, non-governmental organizations and "
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
+"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary."
+"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
 
 #: ./criteria/welcome-contributors.md:block 12 (unordered list)
 msgid ""
 "Consider adding contact details so that other policy makers considering "
 "collaboration can ask you for advice."
-msgstr ""
+msgstr "考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "Make sure that the documentation of the governance includes the current "
 "process for how to make changes to the governance."
-msgstr ""
+msgstr "確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "If the community has some consensus about how the governance should change, "
 "then include those ideas stated as ambitions in the documentation."
-msgstr ""
+msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中"
+"。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "If needed, make sure you have allocated budget for the contributions review "
 "process as agreed by the codebase community."
-msgstr ""
+msgstr "若有需要，確保如同代碼庫社群所同意的，編列貢獻審查流程的預算。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr ""
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與"
+"的時間長度等。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to stay "
 "part of the community for as long as possible."
-msgstr ""
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。"
 
 #: ./criteria/welcome-contributors.md:block 16 (unordered list)
 msgid "Respond promptly to requests."
-msgstr ""
+msgstr "快速回應請求。"
 
 #: ./criteria/welcome-contributors.md:block 16 (unordered list)
 msgid ""
 "Communicate clearly to contributors what they need to do make sure their "
 "contribution can be integrated."
-msgstr ""
+msgstr "清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式碼中。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr ""
+msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/"
+"building-community/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4262,6 +4733,9 @@ msgid ""
 "open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
 "source-project/) by Mike McQuaid."
 msgstr ""
+"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-o"
+"pen-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
+"project/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4269,96 +4743,103 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
+"開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
+"leadership-and-governance/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
 "[Building online communities](http://hintjens.com/blog:117) by Pieter "
 "Hintjens (long read!)."
-msgstr ""
+msgstr "Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。"
 
 #: ./docs/printing.md:block 1 (header)
 msgid "Printing"
-msgstr ""
+msgstr "印刷"
 
 #: ./docs/printing.md:block 3 (paragraph)
 msgid ""
 "The printed Standard for Public Code is printed by Reclameland. This guide "
 "tries to provide the relevant information to print it there or somewhere "
 "else."
-msgstr ""
+msgstr "公共程式標準由Reclameland負責印刷。本指南提供印刷相關資訊，方便在Reclameland"
+"或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
 "Details, mostly in order they are on the Reclameland page with the Dutch if "
 "necessary:"
-msgstr ""
+msgstr "印刷詳細資訊（依照Reclameland網頁上的順序，需要的地方有附上德文）："
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid ""
 "Form: Softcover book ([Reclameland product "
 "page](https://www.reclameland.nl/drukken/softcover-boeken))"
 msgstr ""
+"樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/"
+"softcover-boeken))"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Format: A4"
-msgstr ""
+msgstr "紙張尺寸：A4"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Portrait or landscape: Portrait (Staand)"
-msgstr ""
+msgstr "直橫向：直向（Staand）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing inside: 4/4 dual sided full color"
-msgstr ""
+msgstr "內頁印刷：正四反四（雙面彩色）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Inside material: 90 grams biotop"
-msgstr ""
+msgstr "內頁材質：Biotop 90克"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover: 350 grams cover"
-msgstr ""
+msgstr "封面：350克封面"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing cover: 4/0 one sided full cover"
-msgstr ""
+msgstr "封面印刷：正四（單面彩色）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover treatment: one sided matt foliated (Enke)"
-msgstr ""
+msgstr "封面材質：單面霧面立體字封面（Enke）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid ""
 "Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
 " multiple of 4"
-msgstr ""
+msgstr "頁數：書內頁數 + 4 + x，x 是 0-3頁，因此總頁數是4的倍數"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Individually sealed: no"
-msgstr ""
+msgstr "個別封裝：無"
 
 #: ./docs/printing.md:block 6 (paragraph)
 msgid ""
 "When these details are chosen, the cover and insides are uploaded and the "
 "order is placed payment can happen (payment ahead) after which printing "
 "starts."
-msgstr ""
+msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開"
+"始印刷。"
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
-msgstr ""
+msgstr "發行新版本的公共程式標準"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Review state of the 'develop' branch"
-msgstr ""
+msgstr "審查「develop」分支狀態"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Ensure all changes intended for release are merged"
-msgstr ""
+msgstr "確保該版本的內容都已經完成合併"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Invite a proofread of the current state of the branch"
-msgstr ""
+msgstr "請人校對目前的分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
@@ -4368,198 +4849,217 @@ msgid ""
 " truly the best expression of ideas, then follow the [Chicago Manual of "
 "Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
 msgstr ""
+"如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如"
+"果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達"
+"該句子的涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/"
+"Dash#En_dash_versus_em_dash)。"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create a release branch"
-msgstr ""
+msgstr "建立發佈分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
-msgstr ""
+msgstr "從 'develop'、`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "推動分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update the new release"
-msgstr ""
+msgstr "更新新版本"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
-msgstr ""
+msgstr "更新`_config.yml`、`README.md`與`publiccode.yml`的版本編號"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
-msgstr ""
+msgstr "使用`script/make-version-badge.sh`更新`assets/version-badge.svg`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update releaseDate in `publiccode.yml`"
-msgstr ""
+msgstr "更新`publiccode.yml`當中的發行日期"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
-msgstr ""
+msgstr "在[`AUTHORS.md`](../AUTHORS.md)加入新貢獻者資料"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
-msgstr ""
+msgstr "更新[`CHANGELOG.md`](../CHANGELOG.md)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Perform extra pass on diff to the 'main' branch"
-msgstr ""
+msgstr "與'main'分支進行額外比較"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "run `script/generate-review-template.sh` and commit updated `docs/review-"
 "template.html`"
 msgstr ""
+"執行 `script/generate-review-template.sh` 與更新提交紀錄`docs/review-template"
+".html`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "update `docs/standard-for-public-code.md` with the new text from the review "
 "template, updating any status changes as a result"
-msgstr ""
+msgstr "用審查範本的新文字來更新`docs/standard-for-public-code."
+"md`，更新所有的狀態變更"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Reread any section or paragraph to ensure wording changes still fit the "
 "whole and do not contain grammar or spelling errors"
-msgstr ""
+msgstr "重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼"
+"字錯誤"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
 " `script/ensure-font.sh`"
 msgstr ""
+"確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/"
+"ensure-font.sh`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
-msgstr ""
+msgstr "使用`script/pdf.sh rc1`檢視渲染的 `.pdf`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Ensure no link collisions exist"
-msgstr ""
+msgstr "確保沒有連結相衝的問題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Check the page breaks, possibly removing or adding page-break CSS, for "
 "example: `<p style=\"page-break-after: always;\"></p>`"
-msgstr ""
+msgstr "移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style=\"page-break-after: "
+"always;\"></p>`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "If needed, commit fixes and repeat extra pass"
-msgstr ""
+msgstr "若需要，進行修復並且重複進行額外傳輸"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push branch, open a pull request to the 'main' branch"
-msgstr ""
+msgstr "推動分支，對 「'main'」分支提出提取請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Request review from multiple reviewers, especially a proofreader"
-msgstr ""
+msgstr "要求多位審查人員（特別是校對人員）進行審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Reviewers will create issues for shortcomings found which would not prevent "
 "release"
-msgstr ""
+msgstr "審查人員若有發現不會影響發行的缺失，則會建立議題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "If needed for release, reviewers may create pull requests to resolve issues"
-msgstr ""
+msgstr "如果是發行所需，審查人員可以建立提取請求來解決問題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Re-request reviews if additional pull requests are merged into release "
 "branch"
-msgstr ""
+msgstr "若額外的提取請求合併至發行分支，請要求重新審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Run the to-archive-org.sh script"
-msgstr ""
+msgstr "執行「to-archive-org.sh」腳本"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Once reviews are complete, merge to 'main'"
-msgstr ""
+msgstr "審查完成後，合併至「'main'」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create GitHub release with the release notes and version number"
-msgstr ""
+msgstr "在 GItHub 上發行，並且附上發行說明與版本號碼"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Switch to the 'main' branch, `git pull` and `git status`"
-msgstr ""
+msgstr "切換至「'main'」分支、「`git pull`」與「`git status`」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
+#, fuzzy
 msgid "`git tag $MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "`git tag $MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
+#, fuzzy
 msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
-msgstr ""
+msgstr "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Trigger a rebuild of gh-pages"
-msgstr ""
+msgstr "觸發 gh-pages 的重建"
 
 #: ./docs/releasing.md:block 3 (ordered list)
+#, fuzzy
 msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
+#, fuzzy
 msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
-msgstr ""
+msgstr "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
+#, fuzzy
 msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Open a pull request from this branch to `main`"
-msgstr ""
+msgstr "從此分支向 「'main'」提出提取請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Approve and merge PR (containing empty commit)"
-msgstr ""
+msgstr "核准與合併 PR （包含空白的提交版本）"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update 'develop' with a merge from 'main'"
-msgstr ""
+msgstr "用「'main'」的內容合併並且更新「'develop'」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "[Send the files for print to the printer](printing.md)"
-msgstr ""
+msgstr "[將印刷檔案傳送至印刷廠](printing.md)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Cover file"
-msgstr ""
+msgstr "封面檔案"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Inside pages PDF"
-msgstr ""
+msgstr "內頁 PDF"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Ping [translation](https://github.com/publiccodenet/community-translations-"
 "standard) contributors"
 msgstr ""
+"標記[翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)貢獻者"
 
 #: ./docs/roadmap.md:block 1 (header)
 msgid "Roadmap"
-msgstr ""
+msgstr "發展路線圖"
 
 #: ./docs/roadmap.md:block 3 (paragraph)
 msgid "Last updated: 2023-03-08"
-msgstr ""
+msgstr "上次更新時間：2023-03-08"
 
 #: ./docs/roadmap.md:block 4 (paragraph)
 msgid ""
 "This document intends to shed light on the current development plans of the "
 "team. Plans change constantly as new information is absorbed by the team."
-msgstr ""
+msgstr "本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變"
+"動。"
 
 #: ./docs/roadmap.md:block 5 (paragraph)
 msgid ""
@@ -4567,113 +5067,118 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
+"代碼庫管理人員每月定期審查發展路線圖，這是[積壓修剪](https://about.publiccode"
+".net/activities/standard-maintenance/backlog-pruning.html)的一部份。"
 
 #: ./docs/roadmap.md:block 6 (header)
 msgid "Current work"
-msgstr ""
+msgstr "目前任務"
 
 #: ./docs/roadmap.md:block 7 (unordered list)
 msgid "As far as possible, make the standard Standard-compliant"
-msgstr ""
+msgstr "盡可能讓標準符合公共程式標準"
 
 #: ./docs/roadmap.md:block 8 (header)
 msgid "Near term"
-msgstr ""
+msgstr "近期"
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid "Separate executive summary"
-msgstr ""
+msgstr "分離執行摘要"
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid ""
 "Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
 " issue #208"
-msgstr ""
+msgstr "#208號議題：需要時，將「程式碼」清楚標示為「原始碼」或是「政策程式碼」"
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid "Possibly: add in the illustrations for each criterion"
-msgstr ""
+msgstr "潛在解決方案：為每個標準新增圖解"
 
 #: ./docs/roadmap.md:block 10 (header)
 msgid "Longer term"
-msgstr ""
+msgstr "長期"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Certification badges"
-msgstr ""
+msgstr "認證標章"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid ""
 "Add to README and index.md information (and eventually statistics) on "
 "adoption and use (issue #438)"
-msgstr ""
+msgstr "#438號議題：在採用與使用程式碼上，新增「README」與「index."
+"md」資訊（之後加入統計數據）"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Physical paper checklist"
-msgstr ""
+msgstr "實體檢查清單"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Becoming validated by multiple codebases"
-msgstr ""
+msgstr "取得多個代碼庫認證"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Release version 1.0.0 after a few codebases are compliant"
-msgstr ""
+msgstr "在幾個代碼庫符合標準後，推出 1.0.0 版"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Linkable requirements"
-msgstr ""
+msgstr "可連結需求規範"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "New cover art"
-msgstr ""
+msgstr "新封面設計"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Register for ISBN"
-msgstr ""
+msgstr "申請 ISBN 書號"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "List with an on-demand book printing service"
-msgstr ""
+msgstr "隨選書籍列印服務廠商清單"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "QR codes for external links in print version"
-msgstr ""
+msgstr "印刷版外部連結的 QR 二維碼"
 
 #: ./foreword.md:block 3 (paragraph)
+#, fuzzy
 msgid "redirect_from:"
-msgstr ""
+msgstr "redirect_from:"
 
 #: ./foreword.md:block 4 (unordered list)
 msgid "introduction"
-msgstr ""
+msgstr "前言"
 
 #: ./foreword.md:block 5 (header)
 msgid "Foreword"
-msgstr ""
+msgstr "序"
 
 #: ./foreword.md:block 6 (paragraph)
 msgid ""
 "The Standard for Public Code is a set of criteria that support public "
 "organizations in developing and maintaining software and policy together."
-msgstr ""
+msgstr "公共程式標準當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./foreword.md:block 7 (paragraph)
 msgid ""
 "Anyone developing public-purpose software or policy can use this standard to"
 " work towards higher quality public services that are more cost effective, "
 "with less risk and more control."
-msgstr ""
+msgstr "開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成"
+"本效益、風險更低且能夠掌控。"
 
 #: ./foreword.md:block 8 (paragraph)
 msgid ""
 "This foreword introduces the term public code and explains why this is "
 "important."
-msgstr ""
+msgstr "「序」介紹何謂「公共程式」以及其重要性。"
 
 #: ./foreword.md:block 9 (header)
 msgid "Definition of public code"
-msgstr ""
+msgstr "公共程式定義"
 
 #: ./foreword.md:block 10 (paragraph)
 msgid ""
@@ -4684,22 +5189,26 @@ msgid ""
 "distinct from regular software because it operates under fundamentally "
 "different circumstances and expectations."
 msgstr ""
+"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與預算法）與公"
+"共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體"
+"生產的安排，都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件"
+"與期待也不同。"
 
 #: ./foreword.md:block 11 (header)
 msgid "Reasons for public code"
-msgstr ""
+msgstr "使用公共程式的原因"
 
 #: ./foreword.md:block 12 (paragraph)
 msgid "There are many reasons for why public code is relevant now."
-msgstr ""
+msgstr "公共程式現在如此重要，背後有幾個原因。"
 
 #: ./foreword.md:block 13 (header)
 msgid "Software code == legal code"
-msgstr ""
+msgstr "軟體程式碼 == 政府法規"
 
 #: ./foreword.md:block 14 (paragraph)
 msgid "Software is public infrastructure."
-msgstr ""
+msgstr "軟體是公共基礎建設。"
 
 #: ./foreword.md:block 15 (paragraph)
 msgid ""
@@ -4708,6 +5217,8 @@ msgid ""
 "originator of new policy, for example where algorithms decide which "
 "districts need extra social services or policing."
 msgstr ""
+"在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用"
+"於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。"
 
 #: ./foreword.md:block 16 (paragraph)
 msgid ""
@@ -4719,51 +5230,55 @@ msgid ""
 "by machines. In other words, software code has increasingly started to equal"
 " legal code."
 msgstr ""
+"在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能"
+"執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共"
+"價值，設定社會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體"
+"程式越來越接近法規的地位。"
 
 #: ./foreword.md:block 17 (paragraph)
 msgid ""
 "Software should therefore be subject to the principles of democratic "
 "governance."
-msgstr ""
+msgstr "因此軟體也應該接受民主治理原則的約束。"
 
 #: ./foreword.md:block 18 (header)
 msgid "Traditional public software procurement"
-msgstr ""
+msgstr "傳統的公共軟體採購方式"
 
 #: ./foreword.md:block 19 (paragraph)
 msgid ""
 "Current public software production methods have not served public service "
 "delivery very well."
-msgstr ""
+msgstr "目前的公共軟體生產模式，在交付公共服務上的效率並不高。"
 
 #: ./foreword.md:block 20 (paragraph)
 msgid ""
 "In the last decade, public organizations that purchased complete software "
 "solutions have sometimes been surprised to discover that they:"
-msgstr ""
+msgstr "過去十年購買完整軟體解決方案的公共組織，都很訝異地發現："
 
 #: ./foreword.md:block 21 (unordered list)
 msgid ""
 "can’t change their software to reflect changing policy or take advantage of "
 "new technology"
-msgstr ""
+msgstr "無法修改軟體來反映政策的變動，或是利用新科技"
 
 #: ./foreword.md:block 21 (unordered list)
 msgid ""
 "don’t have access to their data as it's locked into proprietary systems"
-msgstr ""
+msgstr "資料都鎖在專有系統中，無法取得"
 
 #: ./foreword.md:block 21 (unordered list)
 msgid "are asked to pay ever increasing license fees"
-msgstr ""
+msgstr "授權費越來越貴而且還要定期繳納"
 
 #: ./foreword.md:block 22 (header)
 msgid "Technological sovereignty and democratic accountability"
-msgstr ""
+msgstr "技術主權與民主課責"
 
 #: ./foreword.md:block 23 (paragraph)
 msgid "Public institutions, civil servants and residents deserve better."
-msgstr ""
+msgstr "公共機關、公僕與市民都值得更好的。"
 
 #: ./foreword.md:block 24 (paragraph)
 msgid ""
@@ -4776,90 +5291,94 @@ msgid ""
 " Citizens and civil society actors need this software to be transparent and "
 "accountable."
 msgstr ""
+"我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將"
+"軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都"
+"需要技術主權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依"
+"法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。"
 
 #: ./foreword.md:block 25 (paragraph)
 msgid ""
 "The design of software as essential civic infrastructure should honor "
 "digital citizens’ rights."
-msgstr ""
+msgstr "設計為必要公民基礎建設的軟體，也應該尊重數位公民的權益。"
 
 #: ./foreword.md:block 26 (header)
 msgid "Designing truly public software"
-msgstr ""
+msgstr "設計真正屬乎民眾的軟體"
 
 #: ./foreword.md:block 27 (paragraph)
 msgid ""
 "Public code is at the core of modern public institutions, shapes the work of"
 " civil servants and affects the lives of almost all residents."
-msgstr ""
+msgstr "公共程式是現代公共基礎建設的核心，影響公僕的工作以及幾乎所有市民的生活。"
 
 #: ./foreword.md:block 28 (paragraph)
 msgid "Public software must therefore be:"
-msgstr ""
+msgstr "因此公共軟體必須："
 
 #: ./foreword.md:block 29 (unordered list)
 msgid "transparent"
-msgstr ""
+msgstr "透明"
 
 #: ./foreword.md:block 29 (unordered list)
 msgid "accountable"
-msgstr ""
+msgstr "負責任"
 
 #: ./foreword.md:block 29 (unordered list)
 msgid "understandable for its constituents"
-msgstr ""
+msgstr "讓選民能夠理解"
 
 #: ./foreword.md:block 30 (paragraph)
 msgid ""
 "It must reflect the values of the society it serves, for example by being "
 "inclusive and non-discriminatory."
-msgstr ""
+msgstr "反映其服務社會的價值觀，像是包容與不歧視。"
 
 #: ./foreword.md:block 31 (paragraph)
 msgid ""
 "Most proprietary software systems currently used by public organizations do "
 "not meet these requirements. Public code does."
-msgstr ""
+msgstr "公共組織目前使用的多數專有軟體系統都不符合這些要求，但是公共程式符合。"
 
 #: ./foreword.md:block 32 (header)
 msgid "Values of public code"
-msgstr ""
+msgstr "公共程式的價值"
 
 #: ./foreword.md:block 33 (paragraph)
 msgid "We consider public code to have these core values:"
-msgstr ""
+msgstr "我們認為公共程式具有以下核心價值："
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Inclusive"
-msgstr ""
+msgstr "包容"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Usable"
-msgstr ""
+msgstr "可用"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Open"
-msgstr ""
+msgstr "開放"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Legible"
-msgstr ""
+msgstr "清晰易讀"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accountable"
-msgstr ""
+msgstr "負責"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accessible"
-msgstr ""
+msgstr "容易取得"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Sustainable"
-msgstr ""
+msgstr "永續"
 
 #: ./foreword.md:block 35 (header)
 msgid "How public code works"
-msgstr ""
+msgstr "公共程式運作方式"
 
 #: ./foreword.md:block 36 (paragraph)
 msgid ""
@@ -4868,10 +5387,12 @@ msgid ""
 "to the software, so that its development and maintenance become truly "
 "collaborative."
 msgstr ""
+"公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程"
+"式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。"
 
 #: ./foreword.md:block 37 (paragraph)
 msgid "Being open unlocks many other things."
-msgstr ""
+msgstr "開放的精神能創造許多可能性。"
 
 #: ./foreword.md:block 38 (paragraph)
 msgid ""
@@ -4885,6 +5406,12 @@ msgid ""
 "in the future. The code will be easier to retool, repurpose or retire. This "
 "all results in lower risk public infrastructure."
 msgstr ""
+"公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且"
+"貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高"
+"。許多貢獻者會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多"
+"人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼"
+"與資料，在未來也更容易改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都"
+"讓公共基礎建設風險更低。"
 
 #: ./foreword.md:block 39 (paragraph)
 msgid ""
@@ -4892,18 +5419,20 @@ msgid ""
 "to how to customize the software so it works best in each local context, "
 "creating better user experiences for their end users (residents or "
 "citizens)."
-msgstr ""
+msgstr "集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情"
+"境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。"
 
 #: ./foreword.md:block 40 (header)
 msgid "Economics of public code"
-msgstr ""
+msgstr "公共程式的經濟"
 
 #: ./foreword.md:block 41 (paragraph)
 msgid ""
 "Public code offers a better economic model for public organizations as well "
 "as for commercial companies. It's an alternative to traditional software "
 "procurement which increases local control and economic opportunity."
-msgstr ""
+msgstr "公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助"
+"各地的公共組織更能控制程式，也有更好的經濟機會。"
 
 #: ./foreword.md:block 42 (paragraph)
 msgid ""
@@ -4916,23 +5445,29 @@ msgid ""
 "administrations can use their own software purchasing to stimulate "
 "innovation and competition in their local economy."
 msgstr ""
+"公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來"
+"開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始"
+"碼讓社會大眾更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在"
+"地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激"
+"當地經濟的創新與競爭。"
 
 #: ./foreword.md:block 43 (paragraph)
 msgid ""
 "This can be seen as investment leading to future economic growth. More "
 "vendors will be necessary due to growing technology demand."
-msgstr ""
+msgstr "這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。"
 
 #: ./foreword.md:block 44 (header)
 msgid "Procuring public code"
-msgstr ""
+msgstr "採購公共程式"
 
 #: ./foreword.md:block 45 (paragraph)
 msgid ""
 "Public code can be used and developed by permanent in-house development "
 "teams, contractors or outsourced suppliers. Vendors to public organizations "
 "can include public code in their bids for contracts."
-msgstr ""
+msgstr "公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可"
+"以包含公共程式。"
 
 #: ./foreword.md:block 46 (paragraph)
 msgid ""
@@ -4941,112 +5476,116 @@ msgid ""
 "innovative approach to adapting the public code to your context, you could "
 "describe the service or outcome in your contract."
 msgstr ""
+"若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用"
+"該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您"
+"的服務或成果。"
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
-msgstr ""
+msgstr "公共程式標準目標"
 
 #: ./foreword.md:block 48 (paragraph)
 msgid ""
 "This Standard supports developers, designers, managers and public policy "
 "makers to:"
-msgstr ""
+msgstr "公共程式標準支持開發人員、設計師、管理人員以及公共政策制定者："
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop high quality software and policy for better public service delivery"
-msgstr ""
+msgstr "開發優質軟體與政策，改善公共服務的交付"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop codebases that can be reused across contexts and collaboratively "
 "maintained"
-msgstr ""
+msgstr "開發能在各種情境下重複使用且共同維護的代碼庫"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "reduce technical debt and project failure rate"
-msgstr ""
+msgstr "減少技術債與專案失敗率"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "have more granular control over, and ability to make decisions about, their "
 "IT systems"
-msgstr ""
+msgstr "更能精細控制 IT 系統並且做出 IT 系統相關決策"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "improve vendor relationships with a better economic model"
-msgstr ""
+msgstr "更好的經濟模型改善與供應商的關係"
 
 #: ./foreword.md:block 50 (paragraph)
 msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
-msgstr ""
+msgstr "代碼庫潛在用戶依照公共程式標準測試代碼庫，結果認為代碼庫容易重複利用、維護且"
+"品質相當高。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
-msgstr ""
+msgstr "公共程式標準能有如此特性是因為："
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "setting out a common terminology for public code development"
-msgstr ""
+msgstr "訂定公共程式開發的通用術語"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "establishing measures to help develop high quality public code"
-msgstr ""
+msgstr "訂定措施協助優質公共程式的開發"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid ""
 "providing guidance on how to fulfill its criteria and operationalize "
 "compliance"
-msgstr ""
+msgstr "提出如何符合公共程式標準的指引並且協助他人遵循"
 
 #: ./foreword.md:block 53 (paragraph)
 msgid ""
 "The Standard for Public Code is meant to be time and technology independent."
-msgstr ""
+msgstr "公共程式標準原意是要不受時間與科技限制。"
 
 #: ./foreword.md:block 54 (header)
 msgid "Who this is for"
-msgstr ""
+msgstr "適用對象"
 
 #: ./foreword.md:block 55 (paragraph)
 msgid ""
 "The Standard for Public Code is for the people who create and reuse public "
 "code:"
-msgstr ""
+msgstr "公共程式標準適用於開發與重複使用公共程式的民眾："
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "public policy makers"
-msgstr ""
+msgstr "公共政策制定者"
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "business and project managers"
-msgstr ""
+msgstr "業務與專案經理"
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "developers and designers"
-msgstr ""
+msgstr "開發人員與設計師"
 
 #: ./foreword.md:block 57 (paragraph)
 msgid "These people work at:"
-msgstr ""
+msgstr "這些人的服務單位："
 
 #: ./foreword.md:block 58 (unordered list)
 msgid "institutions, organizations and administrations in the public sector"
-msgstr ""
+msgstr "公家機關的機構、組織與行政單位"
 
 #: ./foreword.md:block 58 (unordered list)
 msgid ""
 "consultancies and vendors of information technology and policy services to "
 "public organizations"
-msgstr ""
+msgstr "服務公家機關的資訊科技以及政策服務顧問公司與供應商"
 
 #: ./foreword.md:block 59 (paragraph)
 msgid ""
 "It is not aimed at public organizations' end users (residents or citizens), "
 "journalists or academics."
-msgstr ""
+msgstr "適用對象不包括公家機關的終端使用者（居民或市民）、記者或學者。"
 
 #: ./foreword.md:block 61 (unordered list)
 msgid ""
@@ -5054,10 +5593,13 @@ msgid ""
 "paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
 "Software.pdf) by the Free Software Foundation Europe."
 msgstr ""
+"歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮書](https:"
+"//download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) "
+"》。"
 
 #: ./foreword.md:block 62 (header)
 msgid "Videos on public code"
-msgstr ""
+msgstr "公共程式影片"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5065,6 +5607,8 @@ msgid ""
 "2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
 "the background behind the Foundation for Public Code."
 msgstr ""
+"[2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/"
+"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹公共程式基金會的背景。"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5072,16 +5616,19 @@ msgid ""
 "2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
 "procurement, law and more."
 msgstr ""
+"[ 2019 年 Nextcloud 大會的「公帑？公共程式！」專題討論](https://youtube.com/"
+"watch?v=QHFkD4xfd6c)。探討採購、法律等主題。"
 
 #: ./foreword.md:block 64 (header)
 msgid "Get involved"
-msgstr ""
+msgstr "加入我們的行列"
 
 #: ./foreword.md:block 65 (paragraph)
 msgid ""
 "This standard is a living document. [Read our contributor "
 "guide](/CONTRIBUTING.md) to learn how you can make it better."
-msgstr ""
+msgstr "此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING."
+"md)，瞭解您可以如何讓此標準變得更好。"
 
 #: ./foreword.md:block 66 (header)
 msgid "Contact"
@@ -5093,96 +5640,105 @@ msgid ""
 "can find us at [our website](https://publiccode.net/), email us at "
 "info@publiccode.net, or call us at +31 20 2 444 500."
 msgstr ""
+"若有疑問或想進一步瞭解公共程式基金會，請造訪[我們的官網](https://publiccode."
+"net/)、寄電子郵件到 info@publiccode.net，或是撥打我們的電話（+31 20 2 444 "
+"500）。"
 
 #: ./glossary.md:block 3 (header)
 msgid "Glossary"
-msgstr ""
+msgstr "詞彙表"
 
 #: ./glossary.md:block 4 (header)
 msgid "Code"
-msgstr ""
+msgstr "程式碼"
 
 #: ./glossary.md:block 5 (paragraph)
 msgid ""
 "Any explicitly described system of rules. This includes laws, policy and "
 "ordinances, as well as source code that is used to build software. Both of "
 "these are rules, some executed by humans and others by machines."
-msgstr ""
+msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是"
+"規則，前者由人類來執行，後者則是機器。"
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
-msgstr ""
+msgstr "代碼庫"
 
 #: ./glossary.md:block 7 (paragraph)
 msgid ""
 "Any discrete package of code (both source and policy), the tests and the "
 "documentation required to implement a piece of policy or software."
-msgstr ""
+msgstr "執行政策或軟體所需的任何離散程式碼套件（原始碼與政策程式碼）、測試與文件。"
 
 #: ./glossary.md:block 8 (paragraph)
 msgid "This can be, for example, a document or a version-control repository."
-msgstr ""
+msgstr "可以是文件或是版本控制的儲存庫。"
 
 #: ./glossary.md:block 9 (header)
 msgid "Continuous integration"
-msgstr ""
+msgstr "持續整合"
 
 #: ./glossary.md:block 10 (paragraph)
 msgid ""
 "In software engineering, continuous integration (CI) is the practice of "
 "merging all developers' working copies to a development branch of a codebase"
 " as frequently as reasonable."
-msgstr ""
+msgstr "軟體工程的持續整合 (CI) "
+"就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。"
 
 #: ./glossary.md:block 11 (header)
 msgid "Different contexts"
-msgstr ""
+msgstr "不同情境"
 
 #: ./glossary.md:block 12 (paragraph)
 msgid ""
 "Two contexts are different if they are different public organizations or "
 "different departments for which there is not one decision maker that could "
 "make collaboration happen naturally."
-msgstr ""
+msgstr "如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩"
+"個不同的情境。"
 
 #: ./glossary.md:block 13 (header)
 msgid "General public"
-msgstr ""
+msgstr "公眾"
 
 #: ./glossary.md:block 14 (paragraph)
 msgid ""
 "The public at large: end users of the code and the services based upon it."
-msgstr ""
+msgstr "一般民眾：程式碼以及以程式碼為基礎的服務的終端使用者。"
 
 #: ./glossary.md:block 15 (paragraph)
 msgid ""
 "For example, a city's residents are considered end users of a city's "
 "services and of all code that powers these services."
-msgstr ""
+msgstr "舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終"
+"端使用者。"
 
 #: ./glossary.md:block 16 (header)
 msgid "Open source"
-msgstr ""
+msgstr "開源"
 
 #: ./glossary.md:block 17 (paragraph)
 msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
-msgstr ""
+msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-"
+"annotated)》定義何謂「開源」。"
 
 #: ./glossary.md:block 18 (header)
 msgid "Open standard"
-msgstr ""
+msgstr "開放標準"
 
 #: ./glossary.md:block 19 (paragraph)
 msgid ""
 "An open standard is any standard that meets the Open Source Initiative's "
 "[Open Standard Requirements](https://opensource.org/osr)."
-msgstr ""
+msgstr "任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/"
+"osr)的標準就是開放標準。"
 
 #: ./glossary.md:block 20 (header)
 msgid "Policy"
-msgstr ""
+msgstr "政策"
 
 #: ./glossary.md:block 21 (paragraph)
 msgid ""
@@ -5192,34 +5748,37 @@ msgid ""
 "body within an organization. Policies can assist in both subjective and "
 "objective decision making."
 msgstr ""
+"政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協"
+"定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。"
 
 #: ./glossary.md:block 22 (paragraph)
 msgid ""
 "Public policy is the process by which governments translate their political "
 "vision into programs and actions to deliver outcomes."
-msgstr ""
+msgstr "公共政策是政府將其政治理念轉化成計畫與行動的流程，藉此取得成果。"
 
 #: ./glossary.md:block 23 (paragraph)
 msgid ""
 "At the national level, policy and legislation (the law) are usually "
 "separate. The distinction is often more blurred in local government."
-msgstr ""
+msgstr "在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一"
+"起。"
 
 #: ./glossary.md:block 24 (paragraph)
 msgid ""
 "In the Standard the word 'policy' refers to policy created and adopted by "
 "public organizations such as governments and municipalities."
-msgstr ""
+msgstr "公共程式標準當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
-msgstr ""
+msgstr "公共程式"
 
 #: ./glossary.md:block 26 (paragraph)
 msgid ""
 "Public code is open source software developed by public organizations, "
 "together with the policy and guidance needed for collaboration and reuse."
-msgstr ""
+msgstr "公共程式是由公家機關開發的開源軟體，當中包括協作與重複利用所需的政策與指引。"
 
 #: ./glossary.md:block 27 (paragraph)
 msgid ""

From abd081395d313482f087fad4b8313eb4da9eee3f Mon Sep 17 00:00:00 2001
From: Tommy JIang <baptist333@yahoo.com.tw>
Date: Tue, 8 Aug 2023 02:13:19 +0000
Subject: [PATCH 37/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 94.5% (967 of 1023 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 190 +++++++++++++++---------
 1 file changed, 117 insertions(+), 73 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 20c0421d..e4bbed31 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-08-06 17:44+0000\n"
+"PO-Revision-Date: 2023-08-09 06:44+0000\n"
 "Last-Translator: Tommy JIang <baptist333@yahoo.com.tw>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -21,15 +21,13 @@ msgid "SPDX-License-Identifier: CC0-1.0"
 msgstr "SPDX-License-Identifier: CC0-1.0"
 
 #: ./404.md:block 2 (header)
-#, fuzzy
 msgid ""
 "SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
-"publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2022-2023 公共程式基金會 [info@publiccode."
+"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./404.md:block 3 (header)
 msgid ""
@@ -43,7 +41,7 @@ msgstr ""
 
 #: ./404.md:block 4 (header)
 msgid "404 Not Found"
-msgstr "404找不到網頁"
+msgstr "404 找不到網頁"
 
 #: ./404.md:block 5 (paragraph)
 msgid "If you typed the web address, check it is correct."
@@ -64,15 +62,13 @@ msgstr ""
 "net)，讓我們能夠協助您，並且修正我們的錯誤。"
 
 #: ./AUTHORS.md:block 2 (header)
-#, fuzzy
 msgid ""
 "SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
-"publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2019-2023 公共程式基金會 [info@publiccode."
+"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./AUTHORS.md:block 3 (header)
 msgid "Authors"
@@ -228,7 +224,7 @@ msgstr "toc: false redirect_from: - license.html - LICENSE.html"
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
-msgstr "CC Zero v1.0 Universal授權"
+msgstr "創用 CC Zero v1.0 Universal授權"
 
 #: ./CC0-1.0.md:block 6 (paragraph)
 msgid ""
@@ -238,7 +234,7 @@ msgstr "此授權為法律合約，允許任何人任意使用本文件任何內
 
 #: ./CHANGELOG.md:block 3 (header)
 msgid "Version history"
-msgstr "版本紀錄"
+msgstr "版本歷史"
 
 #: ./CHANGELOG.md:block 5 (header)
 msgid "Version 0.7.0"
@@ -1194,8 +1190,8 @@ msgid ""
 "essentially means that the project, along with your contributions is in the "
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
-msgstr "本專案獲得CC Zero v1.0 Universal授權，基本上代表本專案與您的貢獻，都屬於公眾"
-"領域，任何人都可以任意使用。"
+msgstr "本專案獲得創用 CC Zero v1.0 Universal授權，基本上代表本專案與您的貢獻，都屬於"
+"公眾領域，任何人都可以任意使用。"
 
 #: ./CONTRIBUTING.md:block 14 (header)
 msgid "1. Make your changes"
@@ -1279,10 +1275,10 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
-"公共程式標準目標是[使用簡單英文](criteria/use-plain-english.md)，拼字採用美式"
-"英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們"
-"要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修"
-"正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
+"公共程式標準目標是[使用白話的英語](criteria/use-plain-english.md)，拼字採用美"
+"式英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我"
+"們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會"
+"修正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1384,7 +1380,7 @@ msgstr ""
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
-msgstr "版本"
+msgstr "出版"
 
 #: ./CONTRIBUTING.md:block 38 (paragraph)
 msgid ""
@@ -5784,13 +5780,14 @@ msgstr "公共程式是由公家機關開發的開源軟體，當中包括協作
 msgid ""
 "Public code is both computer source code (such as software and algorithms) "
 "and public policy executed in a public context, by humans or machines."
-msgstr ""
+msgstr "公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及"
+"公共政策。"
 
 #: ./glossary.md:block 28 (paragraph)
 msgid ""
 "Public code serves the public interest, is open, legible, accountable, "
 "accessible and sustainable."
-msgstr ""
+msgstr "滿足公共利益的公共程式，具有開放、易讀、負責、可用以及永續的特性。"
 
 #: ./glossary.md:block 29 (paragraph)
 msgid ""
@@ -5799,29 +5796,32 @@ msgid ""
 "development process openly, public code can provide a building block for "
 "others to:"
 msgstr ""
+"為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境"
+"中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以："
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "re-implement in their local context"
-msgstr ""
+msgstr "將該公共程式應用於他們的當地情境"
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "take as a starting point to continue development"
-msgstr ""
+msgstr "將該公共程式當成起點並接著繼續開發"
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "use as a basis for learning"
-msgstr ""
+msgstr "當成學習的基礎"
 
 #: ./glossary.md:block 31 (paragraph)
 msgid ""
 "To facilitate reuse, public code is either released into the public domain "
 "or licensed with an open license that permits others to view and reuse the "
 "work freely and to produce derivative works."
-msgstr ""
+msgstr "為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複"
+"利用其內容的開放授權，藉此推動衍生程式。"
 
 #: ./glossary.md:block 32 (header)
 msgid "Repository"
-msgstr ""
+msgstr "儲存庫"
 
 #: ./glossary.md:block 33 (paragraph)
 msgid ""
@@ -5829,21 +5829,22 @@ msgid ""
 "and metadata of a codebase. Repositories allow multiple contributors to work"
 " on the same set of files. Repositories are able to store multiple versions "
 "of sets of files."
-msgstr ""
+msgstr "儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者"
+"同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。"
 
 #: ./glossary.md:block 34 (header)
 msgid "Source Code"
-msgstr ""
+msgstr "原始碼"
 
 #: ./glossary.md:block 35 (paragraph)
 msgid ""
 "Human readable text of a computer program which can be translated into "
 "machine instructions."
-msgstr ""
+msgstr "人類可讀並且能夠翻譯成機器指令的電腦程式文字。"
 
 #: ./glossary.md:block 36 (header)
 msgid "Version control"
-msgstr ""
+msgstr "版本控制"
 
 #: ./glossary.md:block 37 (paragraph)
 msgid ""
@@ -5855,20 +5856,24 @@ msgid ""
 "different versions with each other and to see how content has changed over "
 "time."
 msgstr ""
+"版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修"
+"正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程"
+"式碼的演變。修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。"
 
 #: ./index.md:block 3 (header)
+#, fuzzy
 msgid "toc: false"
-msgstr ""
+msgstr "toc: false"
 
 #: ./index.md:block 4 (header)
 msgid "Guidance for government open source collaboration"
-msgstr ""
+msgstr "政府開源協作指引"
 
 #: ./index.md:block 5 (paragraph)
 msgid ""
 "The Standard for Public Code is a set of criteria that supports public "
 "organizations in developing and maintaining software and policy together."
-msgstr ""
+msgstr "公共程式標準當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./index.md:block 6 (paragraph)
 msgid ""
@@ -5881,6 +5886,11 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
+"公共程式標準指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區"
+"的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案。公共程式標準提"
+"供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過公共程式標"
+"準，合作建立可用、開放、易讀、負責且永續的代碼庫。公共程式標準適用於各政府層"
+"級的代碼庫，從超國家到市政府。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5888,12 +5898,14 @@ msgid ""
 "code)’ as open source software developed by public organizations, together "
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
+"公共程式標準將‘[公共程式](glossary.md#public-code)’定義為由公共組織所開發的開"
+"源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
 "The criteria of the Standard for Public Code are aligned with guidelines and"
 " best practices of open source software development."
-msgstr ""
+msgstr "公共程式標準當中的標準符合開源軟體開發的指引與最佳實務。"
 
 #: ./index.md:block 9 (paragraph)
 msgid ""
@@ -5901,18 +5913,20 @@ msgid ""
 " context and background can be found in the [foreword](foreword.md). {% "
 "endif%}{% endfor %}"
 msgstr ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} "
+"額外情境與背景資訊請參閱[序](foreword.md). {% endif%}{% endfor %}"
 
 #: ./index.md:block 10 (header)
 msgid "Contents"
-msgstr "內容"
+msgstr "目錄"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
-msgstr ""
+msgstr "[讀者指南：如何詮釋此標準](readers-guide.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Glossary](glossary.md)"
-msgstr ""
+msgstr "[詞彙表](glossary.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid ""
@@ -5920,39 +5934,44 @@ msgid ""
 " page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
 "\"index.md\" %}{% if page.title %}"
 msgstr ""
+"[標準](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for "
+"page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 11 (unordered list)
+#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
 msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Authors](AUTHORS.md)"
-msgstr ""
+msgstr "[作者群](AUTHORS.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Contributing guide](CONTRIBUTING.md)"
-msgstr ""
+msgstr "[貢獻指引](CONTRIBUTING.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
-msgstr ""
+msgstr "[行為準則](CODE_OF_CONDUCT.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Governance](GOVERNANCE.md)"
-msgstr ""
+msgstr "[治理](GOVERNANCE.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Version history](CHANGELOG.md)"
-msgstr ""
+msgstr "[版本歷史](CHANGELOG.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[License](license.html)"
-msgstr ""
+msgstr "[授權](license.html)"
 
 #: ./index.md:block 12 (header)
 msgid "Community calls"
-msgstr ""
+msgstr "社群會議"
 
 #: ./index.md:block 13 (paragraph)
 msgid ""
@@ -5963,10 +5982,15 @@ msgid ""
 "up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
 " to get a call invitation emailed to you."
 msgstr ""
+"我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。 "
+"[議程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-"
+"Code) 在會議前約一週的時間更新。您可以 [報名](https://odoo.publiccode.net/"
+"survey/start/"
+"594b9243-c7e5-4bc1-8714-35137c971842)，之後舉辦會議時會寄送邀情函給您。"
 
 #: ./index.md:block 14 (header)
 msgid "Other resources"
-msgstr ""
+msgstr "其他資源"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5974,6 +5998,8 @@ msgid ""
 "Standard](https://publiccodenet.github.io/community-translations-standard/) "
 "in other languages"
 msgstr ""
+"[公共程式標準社群其他語言](https://publiccodenet.github.io/"
+"community-translations-standard/) 非官方翻譯版"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5981,6 +6007,8 @@ msgid ""
 "assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
 "public sector open source codebases"
 msgstr ""
+"公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/"
+"assessment-eligibility/)"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5989,16 +6017,20 @@ msgid ""
 "template.html) used by Foundation for Public Code stewards for codebase "
 "review"
 msgstr ""
+"公共程式基金會管理人員審查代碼庫時使用的 "
+"[公共程式標準檢查清單](https://github.com/publiccodenet/standard/blob/"
+"develop/docs/review-template.html)"
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
-msgstr ""
+msgstr "讀者指南"
 
 #: ./readers-guide.md:block 4 (paragraph)
 msgid ""
 "The Standard describes a number of criteria. All criteria have consistent "
 "sections that make it clear how to create great public code."
-msgstr ""
+msgstr "公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的"
+"公共程式。"
 
 #: ./readers-guide.md:block 5 (paragraph)
 msgid ""
@@ -6006,106 +6038,109 @@ msgid ""
 "designers\" apply to anyone performing duties associated with these roles, "
 "regardless of their job title. It is common for individuals to have duties "
 "which span multiple roles."
-msgstr ""
+msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職"
+"責的人，不受職稱限制。很多人都承擔多個角色的職責。"
 
 #: ./readers-guide.md:block 6 (paragraph)
 msgid ""
 "Below is a brief explanation of each of these sections and how they are used"
 " within the criteria of the Standard."
-msgstr ""
+msgstr "以下是公共程式標準各章節的簡介，以及在標準當中的功用。"
 
 #: ./readers-guide.md:block 7 (header)
 msgid "Introduction"
-msgstr ""
+msgstr "前言"
 
 #: ./readers-guide.md:block 8 (paragraph)
 msgid ""
 "This section explains what the criterion aims to achieve and why it is "
 "important for a codebase's users and contributors."
-msgstr ""
+msgstr "本章節探討這些標準的目的，以及為什麼對代碼庫使用者與貢獻者很重要的原因。"
 
 #: ./readers-guide.md:block 10 (paragraph)
 msgid ""
 "This section lists what needs to be done in order to comply with the "
 "standard."
-msgstr ""
+msgstr "這章節解釋如何遵循公共程式標準。"
 
 #: ./readers-guide.md:block 11 (paragraph)
 msgid ""
 "The following keywords in this document are to be interpreted as described "
 "in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
-msgstr ""
+msgstr "本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/"
+"rfc2119) 來詮釋："
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST"
-msgstr ""
+msgstr "必須"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST NOT"
-msgstr ""
+msgstr "不得"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "REQUIRED"
-msgstr ""
+msgstr "被要求"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHALL"
-msgstr ""
+msgstr "應該"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHALL NOT"
-msgstr ""
+msgstr "不應"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHOULD"
-msgstr ""
+msgstr "應該"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHOULD NOT"
-msgstr ""
+msgstr "不應"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "RECOMMENDED"
-msgstr ""
+msgstr "建議"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MAY"
-msgstr ""
+msgstr "得"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "OPTIONAL"
-msgstr ""
+msgstr "可選擇"
 
 #: ./readers-guide.md:block 14 (paragraph)
 msgid ""
 "This section offers actions you can take to see if a contribution is "
 "compliant with the Standard. This is key if you want to operationalize the "
 "Standard."
-msgstr ""
+msgstr "本章節列出您可採取的行動，藉此了解貢獻內容是否遵循公共程式標準。如果您想要實"
+"施公共程式標準，這將會是關鍵。"
 
 #: ./readers-guide.md:block 15 (paragraph)
 msgid ""
 "We've tried to word it so that someone who is not intimately acquainted with"
 " the subject matter can still do a basic check for compliance."
-msgstr ""
+msgstr "我們的用字是要讓不熟悉此主題的讀者，看了之後也能夠進行基本的遵循檢測。"
 
 #: ./readers-guide.md:block 17 (paragraph)
 msgid ""
 "This section tries to specifically speak to policy makers by offering them "
 "concrete actions they can perform in their role."
-msgstr ""
+msgstr "本章節主要對象是政策制定者，列出他們的角色能採取的具體行動。"
 
 #: ./readers-guide.md:block 18 (paragraph)
 msgid ""
 "Public policy makers set the priorities and goals of projects and may be "
 "less technologically experienced."
-msgstr ""
+msgstr "公共政策制定者決定專案的優先順序與目標，在科技上的經驗可能沒那麼多。"
 
 #: ./readers-guide.md:block 20 (paragraph)
 msgid ""
 "This section tries to specifically speak to managers by offering concrete "
 "actions they can perform in their role."
-msgstr ""
+msgstr "本章節主要對象是管理人員，列出他們的角色能採取的具體行動。"
 
 #: ./readers-guide.md:block 21 (paragraph)
 msgid ""
@@ -6115,22 +6150,25 @@ msgid ""
 " to create the right culture, line up the right resources and provide the "
 "right structures to deliver great services."
 msgstr ""
+"管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們"
+"也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資"
+"源，提供正確的架構，才能夠帶來良好的服務。"
 
 #: ./readers-guide.md:block 23 (paragraph)
 msgid ""
 "This section tries to specifically speak to developers and designers by "
 "offering them concrete actions they can perform in their role."
-msgstr ""
+msgstr "本章節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。"
 
 #: ./readers-guide.md:block 24 (paragraph)
 msgid ""
 "Developers are usually more technically aligned and have more impact on the "
 "delivery of services than the previous groups."
-msgstr ""
+msgstr "開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務的交付的影響更大。"
 
 #: ./readers-guide.md:block 25 (header)
 msgid "Limitation of scope"
-msgstr ""
+msgstr "範圍限制"
 
 #: ./readers-guide.md:block 26 (paragraph)
 msgid ""
@@ -6138,7 +6176,8 @@ msgid ""
 "implementations of a codebase. This means the standard does not tell "
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
-msgstr ""
+msgstr "公共程式標準不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如"
+"何遵循他們組織的當地技術基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6149,10 +6188,15 @@ msgid ""
 "Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
 "synergize well with them."
 msgstr ""
+"公共程式標準有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動"
+"協作。因此公共程式標準目的並非是要取代品質標準（像是 ISO 25000 "
+"認證），或是以安全為準的標準（像是 [OpenSSF 最佳實務標章](https://github.com/"
+"coreinfrastructure/best-practices-badge)），而是要與他們協作。"
 
 #: ./readers-guide.md:block 28 (paragraph)
 msgid ""
 "And while the purpose includes enabling collaboration, it will not guarantee"
 " that a community will spring into existence. That still requires "
 "proactiveness and ambition beyond making the codebase collaboration ready."
-msgstr ""
+msgstr "公共程式標準的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立"
+"社群，除了代碼庫需要準備好進行協作以外，也需要主事者的積極與野心。"

From 5882944183977feeae38ada0a23e26d7d1206c9c Mon Sep 17 00:00:00 2001
From: Wilt <interpreter.wilt@gmail.com>
Date: Sat, 26 Aug 2023 01:03:04 +0000
Subject: [PATCH 38/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 95.9% (982 of 1023 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 198 ++++++++++++------------
 1 file changed, 98 insertions(+), 100 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index e4bbed31..d0a59847 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-08-09 06:44+0000\n"
-"Last-Translator: Tommy JIang <baptist333@yahoo.com.tw>\n"
+"PO-Revision-Date: 2023-08-27 11:44+0000\n"
+"Last-Translator: Wilt <interpreter.wilt@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -16,7 +16,6 @@ msgstr ""
 
 #
 #: ./404.md:block 1 (header)
-#, fuzzy
 msgid "SPDX-License-Identifier: CC0-1.0"
 msgstr "SPDX-License-Identifier: CC0-1.0"
 
@@ -26,8 +25,9 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2022-2023 公共程式基金會 [info@publiccode."
-"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
+"publiccode.net/AUTHORS"
 
 #: ./404.md:block 3 (header)
 msgid ""
@@ -35,9 +35,9 @@ msgid ""
 "title: Page not found\n"
 "toc: false"
 msgstr ""
-"版型：預設\n"
-"標題：找不到網頁\n"
-"目錄：否"
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
 
 #: ./404.md:block 4 (header)
 msgid "404 Not Found"
@@ -57,9 +57,8 @@ msgid ""
 "[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
 "able to help you out, as well as correct our mistake."
 msgstr ""
-"若網址正確或是您按下連結或按鈕，請寫信給 "
-"[公共程式基金會人員](mailto:info@publiccode."
-"net)，讓我們能夠協助您，並且修正我們的錯誤。"
+"若網址正確或是您按下連結或按鈕，請寫信給 [the Foundation for Public Code "
+"人員](mailto:info@publiccode.net)，讓我們能夠協助您，並且修正我們的錯誤。"
 
 #: ./AUTHORS.md:block 2 (header)
 msgid ""
@@ -67,8 +66,9 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2019-2023 公共程式基金會 [info@publiccode."
-"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
+"publiccode.net/AUTHORS"
 
 #: ./AUTHORS.md:block 3 (header)
 msgid "Authors"
@@ -76,16 +76,15 @@ msgstr "作者群"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
-msgstr "Alba Roza，[公共程式基金會](https://publiccode.net/)"
+msgstr "Alba Roza，[The Foundation for Public Code](https://publiccode.net/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Arnout Engelen"
 msgstr "Arnout Engelen"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Arnout Schuijff, The Foundation for Public Code"
-msgstr "Arnout Schuijff，公共程式基金會"
+msgstr "Arnout Schuijff，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
@@ -93,28 +92,25 @@ msgstr "唐鳳，[digitalminister.tw](https://digitalminister.tw/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Ben Cerveny, The Foundation for Public Code"
-msgstr "Ben Cerveny， 公共程式基金會"
+msgstr "Ben Cerveny，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Bert Spaan"
 msgstr "Bert Spaan"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Boris van Hoytema, The Foundation for Public Code"
-msgstr "Boris van Hoytema，公共程式基金會"
+msgstr "Boris van Hoytema，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Charlotte Heikendorf"
 msgstr "Charlotte Heikendorf"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Claus Mullie, The Foundation for Public Code"
-msgstr "Claus Mullie，公共程式基金會"
+msgstr "Claus Mullie，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "David Barberi"
 msgstr "David Barberi"
 
@@ -124,31 +120,29 @@ msgstr "Edo Plantinga，[Code For NL](https://codefor.nl/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Elena Findley-de Regt, The Foundation for Public Code"
-msgstr "Elena Findley-de Regt，公共程式基金會"
+msgstr "Elena Findley-de Regt，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Eric Herman, The Foundation for Public Code"
-msgstr "Eric Herman，公共程式基金會"
+msgstr "Eric Herman，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Felix Faassen, The Foundation for Public Code"
-msgstr "Felix Faassen，公共程式基金會"
+msgstr "Felix Faassen，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Floris Deerenberg"
 msgstr "Floris Deerenberg"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Jan Ainali, The Foundation for Public Code"
-msgstr "Jan Ainali，公共程式基金會"
+msgstr "Jan Ainali，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Johan Groenen, Code For NL"
-msgstr "Johan Groenen，荷蘭程式碼社群"
+msgstr "Johan Groenen，Code For NL"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Marcus Klaas de Vries"
 msgstr "Marcus Klaas de Vries"
 
@@ -166,12 +160,10 @@ msgstr ""
 "com/)，數位媒體與創意產業學院劇場與公民媒體系講師"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Matti Schneider"
 msgstr "Matti Schneider"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Mauko Quiroga"
 msgstr "Mauko Quiroga"
 
@@ -185,15 +177,13 @@ msgstr "Maurits van der Schee，阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Mirjam van Tiel, The Foundation for Public Code"
-msgstr "Mirjam van Tiel，公共程式基金會"
+msgstr "Mirjam van Tiel，The Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Ngô Ngọc Đức Huy"
 msgstr "Ngô Ngọc Đức Huy"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Paul Keller"
 msgstr "Paul Keller"
 
@@ -201,10 +191,11 @@ msgstr "Paul Keller"
 msgid ""
 "Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
 "(NIIS)](https://niis.org)"
-msgstr "Petteri Kivimäki， [北歐互通解決方案機構(NIIS)](https://niis.org)"
+msgstr ""
+"Petteri Kivimäki， [Nordic Institute for Interoperability Solutions "
+"(NIIS)](https://niis.org)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Sky Bristol"
 msgstr "Sky Bristol"
 
@@ -213,18 +204,16 @@ msgid "Tamas Erkelens, Gemeente Amsterdam"
 msgstr "Tamas Erkelens，阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
-#, fuzzy
 msgid "Timo Slinger"
 msgstr "Timo Slinger"
 
 #: ./CC0-1.0.md:block 3 (header)
-#, fuzzy
 msgid "toc: false redirect_from: - license.html - LICENSE.html"
 msgstr "toc: false redirect_from: - license.html - LICENSE.html"
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
-msgstr "創用 CC Zero v1.0 Universal授權"
+msgstr "創用 CC Zero v1.0 Universal 授權"
 
 #: ./CC0-1.0.md:block 6 (paragraph)
 msgid ""
@@ -276,11 +265,11 @@ msgstr "「簡介」轉變為「序」。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved contributing guidelines."
-msgstr "改善貢獻指南。"
+msgstr "已改善貢獻指南。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved documentation of scripts."
-msgstr "改善腳本註解。"
+msgstr "已改善腳本註解。"
 
 #: ./CHANGELOG.md:block 8 (header)
 msgid "Version 0.6.0"
@@ -296,7 +285,7 @@ msgstr "2023年4月20日：🔀第十四版新增可移植性與測試的規定
 msgid ""
 "New requirement in Create reusable and portable code about the development "
 "being a collaboration between multiple parties."
-msgstr "新增規定，針對多方合作的開發案，編寫可重複使用且可移植的程式碼。"
+msgstr "新增規定，針對多方合作的開發案來編寫可重複使用且可移植的程式碼。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -320,60 +309,61 @@ msgstr "區分兩個安全性規定，一個是有關提供辦法，另一個則
 msgid ""
 "Rephrased requirements to focus on the codebase rather than contributor "
 "behavior."
-msgstr "重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。"
+msgstr "已重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
-msgstr "移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。"
+msgstr "已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹"
+"。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added general What this does not do section in the introduction of the "
 "Standard."
-msgstr "在標準簡介中，新增「不具備以下作用」段落。"
+msgstr "在標準簡介中，已新增「不具備以下作用」段落。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for public policy makers about related policies and license "
 "compatibility."
-msgstr "新增有關相關政策與授權相容性的公共政策決策者指南。"
+msgstr "已新增有關相關政策與授權相容性的公共政策決策者指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for developers and designers about version controlling files."
-msgstr "新增有關版本控制檔案的開發人員與設計師指南。"
+msgstr "已新增有關版本控制檔案的開發人員與設計師指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Clarified guidance for developers and designers about prompt responses and "
 "search engine optimization."
-msgstr "釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。"
+msgstr "已釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added Further reading about accessibility."
-msgstr "新增「進一步閱讀無障礙」。"
+msgstr "已新增「進一步閱讀無障礙」。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Aligned criteria URLs with criteria names."
-msgstr "將各標準的連結與其名稱同步。"
+msgstr "已將各標準的連結與其名稱同步。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Improved navigation in the web version."
-msgstr "改善網頁版的導覽功能。"
+msgstr "已改善網頁版的導覽功能。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved tools in Further reading sections to the community implementation "
 "guide."
-msgstr "將「進一步閱讀」章節的工具移到社群實施指南。"
+msgstr "已將「進一步閱讀」章節的工具移到社群實施指南。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved compliance or certification process to "
 "[publiccode.net](https://publiccode.net)."
-msgstr "將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。"
+msgstr "已將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -384,19 +374,19 @@ msgstr "變更審查範本格式，讓範本在新版本推出後後更容易更
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Improved the text on the landing page and added links to related resources."
-msgstr "改善到達網頁文字，加入相關資源的連結。"
+msgstr "已改善到達網頁文字，加入相關資源的連結。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added spell checker automated test."
-msgstr "新增拼字檢查自動化測試。"
+msgstr "已新增拼字檢查自動化測試。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Made minor changes to text for clarity and consistency."
-msgstr "稍微調整文字，讓文字更明確與一致。"
+msgstr "已稍微調整文字，讓文字更明確與一致。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Moved SPDX headers to yaml header."
-msgstr "將SPDX標題換成yaml標題。"
+msgstr "將 SPDX 標頭換成 yaml 標頭。"
 
 #: ./CHANGELOG.md:block 11 (header)
 msgid "Version 0.5.0"
@@ -418,13 +408,14 @@ msgstr "調整編碼風格要求，專注在代碼庫上面，而非貢獻者行
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
-msgstr "變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。"
+msgstr "已變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement about testing the code by using examples to Use continuous"
 " integration from Document the code."
-msgstr "變更使用範例測試程式碼的規定，改為使用持續整合來測試。"
+msgstr "已變更使用範例測試程式碼的規定，改為使用「Document the "
+"code」的範例來持續整合測試。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
@@ -456,11 +447,11 @@ msgstr "文件成熟度端看該版本的代碼庫是否已經可以使用。"
 msgid ""
 "Document maturity no longer requires specific labels for codebases that are "
 "not ready to use."
-msgstr "文件成熟度再也不需要看尚未無法使用的代碼庫是否具有特定標籤。"
+msgstr "文件成熟度不再仰賴尚無法使用的代碼庫中的特定標籤。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Audit flow image now generated from an easier to translate format."
-msgstr "現在的審計流程圖格式更容易解讀。"
+msgstr "審計流程圖現在的由更容易轉譯的格式來生成。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Improved guidance on How to test."
@@ -468,7 +459,7 @@ msgstr "改善「測試方式」指南。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add publiccode.yml file."
-msgstr "新增publiccode.yml檔案。"
+msgstr "新增 publiccode.yml 檔案。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add review template."
@@ -476,19 +467,19 @@ msgstr "新增審查範本。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Consistently link glossary terms."
-msgstr "一貫連結詞彙。"
+msgstr "一致連結詞彙。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add practices and standards to follow in CONTRIBUTING."
-msgstr "新增「貢獻」的實務與標準。"
+msgstr "在「貢獻」中新增的實務與標準。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add Matti Schneider to Authors."
-msgstr "Matti Schneider加入作者群。"
+msgstr "加入 Matti Schneider 到作者群。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add remaining SPDX headers to files."
-msgstr "將剩餘SPDX標題加入檔案中。"
+msgstr "將剩餘 SPDX 標頭加入檔案中。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Made additional minor changes to text for clarity."
@@ -496,7 +487,7 @@ msgstr "稍微修改文字，讓文字更明確。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Some hyperlinks updated."
-msgstr "更新部分超連結。"
+msgstr "已更新部分超連結。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
@@ -504,7 +495,7 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
-"將範例移動到[社群實施指南](https://publiccodenet.github.io/"
+"已將範例移動到[社群實施指南](https://publiccodenet.github.io/"
 "community-implementation-guide-standard/)。"
 
 #: ./CHANGELOG.md:block 17 (header)
@@ -532,31 +523,33 @@ msgstr "「歡迎貢獻者」章節中有關發佈活動統計的新規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Removed redundant requirement about portable and reusable code."
-msgstr "移除有關可移植與可重複使用的程式碼的多餘規定。"
+msgstr "已移除有關可移植與可重複使用的程式碼的多餘規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expand open license definition to include both OSI and FSF approved "
 "licenses."
-msgstr "開放授權的定義中，加入OSI與FSF認證的授權。"
+msgstr "在開放授權的定義中，加入 OSI 與 FSF 認證的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr "重新編寫選擇性規定，加入「非必須」一詞，讓規定更明確。"
+msgstr "重新編寫「可以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定"
+"更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "表示公共程式標準在適用時應該符合自身規定，並且新增評估。"
+msgstr "已表明 The Standard for Public Code "
+"標準在適用時應該符合自身規定，且已新增評估。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
-msgstr "將SPDC license identifier加入檔案中。"
+msgstr "將 SPDC license identifier 加入檔案中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduced new Code of Conduct."
-msgstr "推出新行為守則。"
+msgstr "已推出新行為守則。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify distinction between source code and policy text."
@@ -585,7 +578,7 @@ msgstr "關於建制時期與執行階段相依性的額外指南。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
-msgstr "新增公共程式標準開發路徑圖。"
+msgstr "新增 The Standard for Public Code 開發路徑圖。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Update structure of Authors file."
@@ -597,7 +590,7 @@ msgstr "將唐鳳加入作者群。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added a list of criteria to the print edition."
-msgstr "在印刷版中新增標準清單。"
+msgstr "已新增標準清單到印刷版本中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
@@ -622,23 +615,23 @@ msgstr "「編寫可重複使用與可移植程式碼」章節有明確的本土
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
-msgstr "治理註解從「應該」變成「必須」。"
+msgstr "治理註解從「應該（Should）」變成「必須（Must）」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
-msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須有限」規定，改為必須紀錄貢"
-"獻的期望，專注在單一議題上。"
+msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必"
+"須紀錄貢獻的期望，專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
-msgstr "社群翻譯現在連結到頁尾中。"
+msgstr "社群翻譯現在已連結到頁尾中。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
-msgstr "還原「用Mermaid流程圖取代BPMN svg」。"
+msgstr "還原「用 Mermaid 流程圖取代 BPMN svg」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Many minor clarifications to language and sentences made more simple."
@@ -652,7 +645,7 @@ msgstr "0.2.3版"
 msgid ""
 "March 15th 2022: 📜 the ninth draft allows English summaries for policy "
 "lacking an official translation."
-msgstr "2022年3月15日：📜第九版在沒有官方翻譯的政策加入英文版摘要。"
+msgstr "2022年3月15日：📜第九版允許在沒有官方翻譯的政策中加入英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -996,7 +989,7 @@ msgstr "多方部署建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for license headers in files"
-msgstr "檔案授權標題建議"
+msgstr "檔案授權標頭建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for vulnerability reporting"
@@ -1020,7 +1013,7 @@ msgstr "2019年5月9日：🤔第二版修復基本的疏忽以及許多拼字
 msgid ""
 "Removed references to the Foundation for Public Code, we're going to have to"
 " change the name in becoming an association."
-msgstr "移除出現「公共程式基金會」的地方，我們必須改名才能成為協會。"
+msgstr "移除出現「The Foundation for Public Code」的地方，我們必須改名才能成為協會。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the introduction."
@@ -1056,7 +1049,8 @@ msgstr "14個標準、其規定以及實施方式。"
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
-msgstr "清楚明確的背景介紹、介紹本標準以及公共程式基金會會如何使用此標準。"
+msgstr "清楚明確的背景介紹、介紹本標準以及The Foundation for Public "
+"Code會如何使用此標準。"
 
 #: ./CHANGELOG.md:block 50 (paragraph)
 msgid ""
@@ -1329,8 +1323,9 @@ msgid ""
 "All contributions have to be reviewed by someone. The Foundation for Public "
 "Code has committed to make sure that maintainers are available to review "
 "contributions with an aim to provide feedback within two business days."
-msgstr "所有貢獻都必須接受審查。公共程式基金會承諾將確保有維護人員來審查貢獻，目標是"
-"在兩個工作日內提供意見回饋。"
+msgstr ""
+"所有貢獻都必須接受審查。The Foundation for Public "
+"Code承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
 
 #: ./CONTRIBUTING.md:block 30 (paragraph)
 msgid ""
@@ -1402,8 +1397,9 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2019-2022 公共程式基金會[info@publiccode."
-"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public "
+"Code[info@publiccode.net](mailto:info@publiccode.net), https://standard."
+"publiccode.net/AUTHORS"
 
 #: ./GOVERNANCE.md:block 3 (header)
 msgid "Governance"
@@ -1415,12 +1411,12 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"此標準是[公共程式基金會](https://publiccode.net/"
+"此標準是[The Foundation for Public Code](https://publiccode.net/"
 ")代碼庫管理的核心。我們依照本文件來判斷代碼庫是否已經準備好讓社群參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
-msgstr "本標準由公共程式基金會人員負責維護。"
+msgstr "本標準由The Foundation for Public Code人員負責維護。"
 
 #: ./GOVERNANCE.md:block 6 (paragraph)
 msgid ""
@@ -1542,8 +1538,9 @@ msgid ""
 "If there are any breaking changes in a new version of the Standard for "
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
-msgstr "若新版的公共程式標準有突破性的修改，公共程式基金會的代碼庫管理人員會幫助公共"
-"程式標準用戶彌補不同版之間的差異。"
+msgstr ""
+"若新版的公共程式標準有突破性的修改，The Foundation for Public "
+"Code的代碼庫管理人員會幫助公共程式標準用戶彌補不同版之間的差異。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1617,7 +1614,8 @@ msgid ""
 "The Foundation for Public Code is committed to maintaining and developing "
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
-msgstr "公共程式基金會致力於維護與開發公共程式標準，且品質也會符合該標準本身的品質。"
+msgstr "The Foundation for Public "
+"Code致力於維護與開發公共程式標準，且品質也會符合該標準本身的品質。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -3189,7 +3187,6 @@ msgstr "criteria/reusable-and-portable-codebases"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
 #: list)
-#, fuzzy
 msgid "criteria/create-reusable-and-portable-code"
 msgstr "criteria/create-reusable-and-portable-code"
 
@@ -5604,7 +5601,8 @@ msgid ""
 "the background behind the Foundation for Public Code."
 msgstr ""
 "[2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/"
-"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹公共程式基金會的背景。"
+"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹The Foundation for Public "
+"Code的背景。"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5636,9 +5634,9 @@ msgid ""
 "can find us at [our website](https://publiccode.net/), email us at "
 "info@publiccode.net, or call us at +31 20 2 444 500."
 msgstr ""
-"若有疑問或想進一步瞭解公共程式基金會，請造訪[我們的官網](https://publiccode."
-"net/)、寄電子郵件到 info@publiccode.net，或是撥打我們的電話（+31 20 2 444 "
-"500）。"
+"若有疑問或想進一步瞭解The Foundation for Public "
+"Code，請造訪[我們的官網](https://publiccode.net/)、寄電子郵件到 "
+"info@publiccode.net，或是撥打我們的電話（+31 20 2 444 500）。"
 
 #: ./glossary.md:block 3 (header)
 msgid "Glossary"
@@ -6017,7 +6015,7 @@ msgid ""
 "template.html) used by Foundation for Public Code stewards for codebase "
 "review"
 msgstr ""
-"公共程式基金會管理人員審查代碼庫時使用的 "
+"The Foundation for Public Code管理人員審查代碼庫時使用的 "
 "[公共程式標準檢查清單](https://github.com/publiccodenet/standard/blob/"
 "develop/docs/review-template.html)"
 

From d01c0141f6dda566f9ed62a7adbbfcd4a466fc1b Mon Sep 17 00:00:00 2001
From: Wilt <interpreter.wilt@gmail.com>
Date: Mon, 28 Aug 2023 08:20:03 +0000
Subject: [PATCH 39/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1023 of 1023 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 481 ++++++++++++------------
 1 file changed, 232 insertions(+), 249 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index d0a59847..0b97e01e 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-08-27 11:44+0000\n"
+"PO-Revision-Date: 2023-08-28 10:25+0000\n"
 "Last-Translator: Wilt <interpreter.wilt@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -213,7 +213,7 @@ msgstr "toc: false redirect_from: - license.html - LICENSE.html"
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
-msgstr "創用 CC Zero v1.0 Universal 授權"
+msgstr "Creative CC Zero v1.0 Universal 授權"
 
 #: ./CC0-1.0.md:block 6 (paragraph)
 msgid ""
@@ -227,7 +227,7 @@ msgstr "版本歷史"
 
 #: ./CHANGELOG.md:block 5 (header)
 msgid "Version 0.7.0"
-msgstr "0.7.0版"
+msgstr "0.7.0 版"
 
 #: ./CHANGELOG.md:block 6 (paragraph)
 msgid ""
@@ -253,7 +253,8 @@ msgstr "原本專注在貢獻內容是否符合標準，現在應該專注在貢
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr "許多「必須」的規定變更為「應該」的規定，讓代碼庫更容易找到。"
+msgstr "許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到"
+"。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
@@ -273,7 +274,7 @@ msgstr "已改善腳本註解。"
 
 #: ./CHANGELOG.md:block 8 (header)
 msgid "Version 0.6.0"
-msgstr "0.6.0版"
+msgstr "0.6.0 版"
 
 #: ./CHANGELOG.md:block 9 (paragraph)
 msgid ""
@@ -390,7 +391,7 @@ msgstr "將 SPDX 標頭換成 yaml 標頭。"
 
 #: ./CHANGELOG.md:block 11 (header)
 msgid "Version 0.5.0"
-msgstr "0.5.0版"
+msgstr "0.5.0 版"
 
 #: ./CHANGELOG.md:block 12 (paragraph)
 msgid ""
@@ -431,7 +432,7 @@ msgstr "調整可查找性的測試規定，減少對搜尋引擎演算法的依
 
 #: ./CHANGELOG.md:block 14 (header)
 msgid "Version 0.4.1"
-msgstr "0.4.1版"
+msgstr "0.4.1 版"
 
 #: ./CHANGELOG.md:block 15 (paragraph)
 msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
@@ -500,7 +501,7 @@ msgstr ""
 
 #: ./CHANGELOG.md:block 17 (header)
 msgid "Version 0.4.0"
-msgstr "0.4.0版"
+msgstr "0.4.0 版"
 
 #: ./CHANGELOG.md:block 18 (paragraph)
 msgid ""
@@ -533,7 +534,7 @@ msgstr "在開放授權的定義中，加入 OSI 與 FSF 認證的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr "重新編寫「可以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定"
+msgstr "重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定"
 "更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
@@ -560,7 +561,6 @@ msgid "Restructuring of requirements with bullet point lists."
 msgstr "將規定改為要點清單的格式。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
-#, fuzzy
 msgid "Acknowledge the importance of codebase modularity for reuse."
 msgstr "承認代碼庫成熟度在重複使用上的重要性。"
 
@@ -600,7 +600,7 @@ msgstr "釐清標準對政策制定者、管理者、開發人員與設計師的
 
 #: ./CHANGELOG.md:block 20 (header)
 msgid "Version 0.3.0"
-msgstr "0.3.0版"
+msgstr "0.3.0 版"
 
 #: ./CHANGELOG.md:block 21 (paragraph)
 msgid ""
@@ -639,7 +639,7 @@ msgstr "細微調整用詞，讓句子更簡單。"
 
 #: ./CHANGELOG.md:block 23 (header)
 msgid "Version 0.2.3"
-msgstr "0.2.3版"
+msgstr "0.2.3 版"
 
 #: ./CHANGELOG.md:block 24 (paragraph)
 msgid ""
@@ -659,7 +659,7 @@ msgstr "放寬「使用簡單英文」的標準，加入新的規定，允許沒
 msgid ""
 "Similarly, allow for English summaries for policies not available in English"
 " in Bundle policy and code."
-msgstr "同樣地，允許同捆政策與程式碼當中，沒有英文版的政策只需要英文版摘要。"
+msgstr "同樣地，允許同捆政策與程式碼當中沒有英文版的政策只提供英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -692,16 +692,16 @@ msgid ""
 "make [community translations](https://github.com/publiccodenet/community-"
 "translations-standard) easier."
 msgstr ""
-"變更拉取請求流程圖，從BPMN改用Mermaid，讓[社群翻譯](https://github.com/"
+"變更拉取請求流程圖，從 BPMN 改用 Mermaid，讓[社群翻譯](https://github.com/"
 "publiccodenet/community-translations-standard)更容易。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added Maurice Hendriks to AUTHORS."
-msgstr "將Maurice Hendriks加入作者群。"
+msgstr "將 Maurice Hendriks 加入作者群。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added OpenApi Specification to further reading."
-msgstr "將「OpenApi規格」加入「深入閱讀」。"
+msgstr "將「OpenApi 規格」加入「深入閱讀」。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Made the attributions in further reading sections clearer."
@@ -709,7 +709,7 @@ msgstr "將「深入閱讀」當中的歸因變得更明確。"
 
 #: ./CHANGELOG.md:block 26 (header)
 msgid "Version 0.2.2"
-msgstr "0.2.2版"
+msgstr "0.2.2 版"
 
 #: ./CHANGELOG.md:block 27 (paragraph)
 msgid ""
@@ -727,7 +727,7 @@ msgstr "標示當政策被詮釋為程式碼時，則不用遵守「僅限英文
 msgid ""
 "Add MAY requirement regarding committer email addresses in Maintain version "
 "control."
-msgstr "在「版本管控」中，新增關於提交者電子郵件的「得以」規定。"
+msgstr "在「版本管控」中，新增關於提交者電子郵件的「得以（May）」規定。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Policy Makers in Bundle policy and code."
@@ -743,7 +743,7 @@ msgstr "新增「不同脈絡」到詞彙表中。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
-msgstr "將Mauko Quiroga與Charlotte Heikendorf加入作者群。"
+msgstr "將 Mauko Quiroga 與 Charlotte Heikendorf 加入作者群。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Digital Public Goods approval badge."
@@ -769,7 +769,7 @@ msgstr "移動「語意化版本規格」引用的「深入閱讀」。"
 msgid ""
 "Clarify that publiccode.yml is one example of a machine-readable metadata "
 "description."
-msgstr "釐清publiccode.yml是描述機讀元資料的名稱之一。"
+msgstr "釐清 publiccode.yml 是描述機讀元資料的名稱之一。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
@@ -781,13 +781,13 @@ msgstr "新增印刷版的建立說明。"
 
 #: ./CHANGELOG.md:block 29 (header)
 msgid "Version 0.2.1"
-msgstr "0.2.1版"
+msgstr "0.2.1 版"
 
 #: ./CHANGELOG.md:block 30 (paragraph)
 msgid ""
 "March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
 "0.2.0."
-msgstr "2021年3月1日：🧽跟0.2.0版相較之下，第七版做了些微改善。"
+msgstr "2021年3月1日：🧽跟 0.2.0 版相較之下，第七版做了些微改善。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
@@ -822,7 +822,7 @@ msgstr "釐清詞彙表中「版本控制」的定義。"
 msgid ""
 "Add further reading encouraging contribution, SPDX, Git and reviewing "
 "contributions."
-msgstr "新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git以及審查貢獻。"
+msgstr "新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git 以及審查貢獻。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add links to videos about the concept of public code."
@@ -830,7 +830,7 @@ msgstr "新增有關公共程式概念的影片連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Update BPMN link."
-msgstr "更新BPMN連結。"
+msgstr "更新 BPMN 連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Reduce link duplication."
@@ -838,11 +838,11 @@ msgstr "減少重複連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
-msgstr "將Alba Roza與Ngô Ngọc Đức Huy加入作者群。"
+msgstr "將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。"
 
 #: ./CHANGELOG.md:block 32 (header)
 msgid "Version 0.2.0"
-msgstr "0.2.0版"
+msgstr "0.2.0 版"
 
 #: ./CHANGELOG.md:block 33 (paragraph)
 msgid ""
@@ -865,11 +865,11 @@ msgstr "將「注意代碼庫成熟度」標準改名為「註解代碼庫成熟
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
-msgstr "針對多方使用的代碼庫，將「必須」規定調整為「應該」規定。"
+msgstr "針對多方使用的代碼庫，將「必須（Must）」規定調整為「應該（Should）」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
-msgstr "針對著作權讓與，新增「不得」規定。"
+msgstr "針對著作權讓與，新增「不得（Must Not）」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
@@ -899,11 +899,11 @@ msgstr "將政策制定者、開發人員與設計師加入「深入閱讀」與
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add Felix Faassen and Arnout Engelen to authors."
-msgstr "將Felix Faassen與Arnout Engelen加入作者群。"
+msgstr "將 Felix Faassen 與 Arnout Engelen 加入作者群。"
 
 #: ./CHANGELOG.md:block 35 (header)
 msgid "Version 0.1.4"
-msgstr "0.1.4版"
+msgstr "0.1.4 版"
 
 #: ./CHANGELOG.md:block 36 (paragraph)
 msgid ""
@@ -913,11 +913,11 @@ msgstr "2019年11月27日：🧹第五版主要內容是額外的細部修復。
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Linked License.md file."
-msgstr "連結的License.md檔案。"
+msgstr "已連結 License.md 檔案。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
-msgstr "將Sky Bristol、Marcus Klaas de Vries與Jan Ainali加入作者群。"
+msgstr "將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Made punctuation more consistent, especially for bullet lists."
@@ -929,7 +929,7 @@ msgstr "細部調整文字，讓內容更明確。"
 
 #: ./CHANGELOG.md:block 38 (header)
 msgid "Version 0.1.3"
-msgstr "0.1.3版"
+msgstr "0.1.3 版"
 
 #: ./CHANGELOG.md:block 39 (paragraph)
 msgid ""
@@ -951,7 +951,7 @@ msgstr "改善樣式與一致性。"
 
 #: ./CHANGELOG.md:block 41 (header)
 msgid "Version 0.1.2"
-msgstr "0.1.2版"
+msgstr "0.1.2 版"
 
 #: ./CHANGELOG.md:block 42 (paragraph)
 msgid ""
@@ -965,7 +965,7 @@ msgstr "一群很棒的貢獻者，讓我們作者群加入許多新血。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "All links are now HTTPS."
-msgstr "所有連結開頭都是HTTPS。"
+msgstr "所有連結都是 HTTPS。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "General proofreading, wording clarifications, and smashed typos."
@@ -973,7 +973,7 @@ msgstr "一般校對、釐清用字與修改拼字錯誤。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Updated criteria:"
-msgstr "更新標準："
+msgstr "已更新標準："
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Requirement for reuse in different contexts"
@@ -993,7 +993,7 @@ msgstr "檔案授權標頭建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for vulnerability reporting"
-msgstr "脆弱性回報建議"
+msgstr "漏洞回報建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for explicit documentation of governance"
@@ -1001,7 +1001,7 @@ msgstr "明確治理註解建議"
 
 #: ./CHANGELOG.md:block 44 (header)
 msgid "Version 0.1.1"
-msgstr "0.1.1版"
+msgstr "0.1.1 版"
 
 #: ./CHANGELOG.md:block 45 (paragraph)
 msgid ""
@@ -1017,23 +1017,23 @@ msgstr "移除出現「The Foundation for Public Code」的地方，我們必須
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the introduction."
-msgstr "更新前言。"
+msgstr "已更新前言。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the glossary."
-msgstr "更新詞彙表。"
+msgstr "已更新詞彙表。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Added the code of conduct."
-msgstr "新增行為守則。"
+msgstr "已新增行為守則。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "We've recommended using the publiccode.yml standard for easier reuse."
-msgstr "我們建議使用publiccode.yml標準，方便重複使用。"
+msgstr "我們建議使用 publiccode.yml 標準，方便重複使用。"
 
 #: ./CHANGELOG.md:block 47 (header)
 msgid "Version 0.1.0"
-msgstr "0.1.0版"
+msgstr "0.1.0 版"
 
 #: ./CHANGELOG.md:block 48 (paragraph)
 msgid ""
@@ -1049,8 +1049,8 @@ msgstr "14個標準、其規定以及實施方式。"
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
-msgstr "清楚明確的背景介紹、介紹本標準以及The Foundation for Public "
-"Code會如何使用此標準。"
+msgstr "清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code "
+"會如何使用此標準。"
 
 #: ./CHANGELOG.md:block 50 (paragraph)
 msgid ""
@@ -1059,7 +1059,7 @@ msgid ""
 "Public Code! project](https://smartcities.publiccode.net/)."
 msgstr ""
 "第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於["
-"智慧城市？公共程式！專案](https://smartcities.publiccode.net/)。"
+"Smart Cities? Public Code! 專案](https://smartcities.publiccode.net/)。"
 
 #: ./CODE_OF_CONDUCT.md:block 1 (header)
 msgid "Code of Conduct"
@@ -1072,7 +1072,7 @@ msgid ""
 "expectations of all community members and all interactions regardless of "
 "communication channel."
 msgstr "社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基"
-"金會對所有社群成員以及互動（不管溝通管道）的期望。"
+"金會對所有社群成員以及互動的期望，不論透過何種溝通管道。"
 
 #: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
 msgid "Be here to collaborate."
@@ -1088,7 +1088,7 @@ msgstr "努力做出建設性的貢獻。"
 
 #: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
 msgid "To raise a concern, please email directors@publiccode.net."
-msgstr "若有問題，請寄送電子郵件到directors@publiccode.net。"
+msgstr "若有問題，請寄送電子郵件到 directors@publiccode.net。"
 
 #: ./CONTRIBUTING.md:block 1 (header)
 msgid "Contributing to this standard"
@@ -1114,7 +1114,7 @@ msgid ""
 "with GitHub, you can email use your feedback at "
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
-"我們歡迎每個人提出的議題與提取請求。如果您對GitHub不放心，"
+"我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，"
 "歡迎將意見用電子郵件傳送到 [info@publiccode.net](mailto:info@publiccode."
 "net)。"
 
@@ -1133,10 +1133,10 @@ msgid ""
 "Code](https://github.com/publiccodenet/standard/issues)."
 msgstr ""
 "[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以"
-"及發問，幫助推動本開發案。您可以到[GitHub的公共程式標準議題](https://github."
-"com/publiccodenet/standard/"
-"issues)頁面中，為此專案[在GitHub上建立議題](https://docs.github.com/en/"
-"issues/tracking-your-work-with-issues/creating-an-issue)。"
+"及發問，幫助推動本開發案。您可以到[GitHub 的The Standard for Public Code "
+"議題](https://github.com/publiccodenet/standard/issues)頁面中，為此專案[在 "
+"GitHub 上建立議題](https://docs.github.com/en/issues/"
+"tracking-your-work-with-issues/creating-an-issue)。"
 
 #: ./CONTRIBUTING.md:block 8 (paragraph)
 msgid ""
@@ -1157,13 +1157,13 @@ msgstr "不需要修改我們的程式碼或註解也能成為貢獻者！"
 
 #: ./CONTRIBUTING.md:block 10 (header)
 msgid "Documentation and code in pull requests"
-msgstr "提取請求中的註解與程式碼"
+msgstr "拉入請求中的註解與程式碼"
 
 #: ./CONTRIBUTING.md:block 11 (paragraph)
 msgid ""
 "If you want to add to the documentation or code of one of our projects you "
 "should make a pull request."
-msgstr "如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出提取請求。"
+msgstr "如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出拉入請求。"
 
 #: ./CONTRIBUTING.md:block 12 (paragraph)
 msgid ""
@@ -1173,10 +1173,10 @@ msgid ""
 "Skills](https://skills.github.com/) on working with GitHub and working with "
 "MarkDown, the syntax this project's documentation is in."
 msgstr ""
-"若您從未使用過GitHub，歡迎先[認識GitHub flow](https://docs.github.com/en/"
+"若您從未使用過 GitHub，歡迎先[認識 GitHub flow](https://docs.github.com/en/"
 "get-started/quickstart/github-flow)，或是參加[GitHub Skills](https://skills."
-"github.com/)的免費且優質的互動性課程，當中介紹如何使用GitHub以及MarkDown（本"
-"專案註解所使用的語法）。"
+"github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 "
+"MarkDown（本專案註解所使用的語法）。"
 
 #: ./CONTRIBUTING.md:block 13 (paragraph)
 msgid ""
@@ -1184,8 +1184,9 @@ msgid ""
 "essentially means that the project, along with your contributions is in the "
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
-msgstr "本專案獲得創用 CC Zero v1.0 Universal授權，基本上代表本專案與您的貢獻，都屬於"
-"公眾領域，任何人都可以任意使用。"
+msgstr ""
+"本專案獲得 Creative CC Zero v1.0 Universal "
+"授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。"
 
 #: ./CONTRIBUTING.md:block 14 (header)
 msgid "1. Make your changes"
@@ -1201,9 +1202,9 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
-"貢獻應該[遵守](docs/standard-for-public-code.html)公共程式標準當中列出的標準"
-"。審查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-"
-"code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-"
+"貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public "
+"Code 當中列出的標準。審查人員會確保貢獻符合[公共程式的價值](foreword.md"
+"#values-of-public-code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-"
 "follow)且與整體專案有連貫。"
 
 #: ./CONTRIBUTING.md:block 16 (paragraph)
@@ -1213,9 +1214,9 @@ msgid ""
 "you've forked this repository, please make sure to create a feature branch "
 "following the GitFlow model."
 msgstr ""
-"本專案使用[GitFlow分支與工作流程](https://nvie.com/posts/"
-"a-successful-git-branching-model/"
-")。當您複製了此存放庫，請務必依照GitFlow模型建立功能分支。"
+"本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/"
+"a-successful-git-branching-model/)。當您複製了此存放庫，請務必依照 GitFlow "
+"模型建立功能分支。"
 
 #: ./CONTRIBUTING.md:block 17 (paragraph)
 msgid ""
@@ -1241,7 +1242,7 @@ msgid ""
 "If you are adding code, make sure you've added and updated the relevant "
 "documentation and tests before you submit your pull request. Make sure to "
 "write tests that show the behavior of the newly added or changed code."
-msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出提取請求。請"
+msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請"
 "務必用文字描述新增或修改後的程式碼的作用。"
 
 #: ./CONTRIBUTING.md:block 19 (header)
@@ -1252,7 +1253,7 @@ msgstr "適用政策"
 msgid ""
 "Currently, the Standard for Public Code is not implementing any specific "
 "public policy."
-msgstr "公共程式標準目前沒有執行任何特定的公共政策。"
+msgstr "The Standard for Public Code 目前沒有執行任何特定的公共政策。"
 
 #: ./CONTRIBUTING.md:block 21 (header)
 msgid "Style"
@@ -1269,10 +1270,11 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
-"公共程式標準目標是[使用白話的英語](criteria/use-plain-english.md)，拼字採用美"
-"式英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我"
-"們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會"
-"修正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
+"The Standard for Public Code 目標是[使用白話的英語](criteria/use-plain-"
+"english.md)，拼字採用美式英文。文字基本上以每句一行為原則，沒有換行，讓「diff"
+"」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與"
+"排版。我們的審查流程會修正這一部分，也會另外再次檢查品質才[推出新版本](docs/"
+"releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1283,14 +1285,14 @@ msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr "這些是公共程式標準所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併"
-"。"
+msgstr "這些是 The Standard for Public Code "
+"所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
 "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
 " keywords"
-msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 「必要性」層級的關鍵字"
+msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 必要層級關鍵字"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
@@ -1300,7 +1302,7 @@ msgstr "[網頁無障礙性指導原則 2.1](https://www.w3.org/TR/WCAG21/#reada
 
 #: ./CONTRIBUTING.md:block 26 (header)
 msgid "2. Pull request"
-msgstr "2. 提取請求"
+msgstr "2. 拉入請求"
 
 #: ./CONTRIBUTING.md:block 27 (paragraph)
 msgid ""
@@ -1310,8 +1312,8 @@ msgid ""
 "issue where possible. In some cases a single set of changes may address "
 "multiple issues, in which case be sure to list all issue numbers fixed."
 msgstr ""
-"提出提取請求時，請附帶描述您想要解決的問題以及該提取請求能修復的議題編號。建"
-"議讓一個提取請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議"
+"提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建"
+"議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議"
 "題編號。"
 
 #: ./CONTRIBUTING.md:block 28 (header)
@@ -1324,8 +1326,8 @@ msgid ""
 "Code has committed to make sure that maintainers are available to review "
 "contributions with an aim to provide feedback within two business days."
 msgstr ""
-"所有貢獻都必須接受審查。The Foundation for Public "
-"Code承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
+"所有貢獻都必須接受審查。The Foundation for Public Code "
+"承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
 
 #: ./CONTRIBUTING.md:block 30 (paragraph)
 msgid ""
@@ -1335,7 +1337,7 @@ msgid ""
 "feedback. If this is the case the reviewing maintainer will help you improve"
 " your documentation and code."
 msgstr ""
-"維護人員可能可以立即合併您的貢獻。但是通常新提取請求需要改善，才能夠合併。其"
+"維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其"
 "他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人"
 "員，將負責協助改善您的註解與程式碼。"
 
@@ -1357,7 +1359,7 @@ msgstr "您的構思、註解與程式碼將成為本專案的一部份。您就
 msgid ""
 "In fact, feel free to open a pull request to add your name to the "
 "[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
-msgstr "歡迎您提出提取請求，將您的名字加入到[`作者`](AUTHORS."
+msgstr "歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS."
 "md)檔案中，您的名字可以永遠留在本專案中。"
 
 #: ./CONTRIBUTING.md:block 35 (header)
@@ -1370,8 +1372,9 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
-"公共程式標準雖然沒有官方翻譯，您可以幫助維護現有以及新增[公共程式標準社群翻譯"
-"](https://github.com/publiccodenet/community-translations-standard)。"
+"The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增["
+"The Standard for Public Code 社群翻譯](https://github.com/publiccodenet/"
+"community-translations-standard)。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
@@ -1389,7 +1392,7 @@ msgstr "建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/pr
 msgid ""
 "For more information on how to use and contribute to this project, please "
 "read the [`README`](README.md)."
-msgstr "若要進一步瞭解如何使用與貢獻本專案，請參閱 [`讀我`](README.md)。"
+msgstr "若要進一步瞭解如何使用與貢獻本專案，請參閱 [`README `](README.md)。"
 
 #: ./GOVERNANCE.md:block 2 (header)
 msgid ""
@@ -1416,7 +1419,7 @@ msgstr ""
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
-msgstr "本標準由The Foundation for Public Code人員負責維護。"
+msgstr "本標準由 The Foundation for Public Code 人員負責維護。"
 
 #: ./GOVERNANCE.md:block 6 (paragraph)
 msgid ""
@@ -1428,8 +1431,9 @@ msgstr "[我們歡迎任何人提供修改的建議或是一般意見回饋等
 msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
-msgstr "由於公共程式標準在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守公共程"
-"式標準中最嚴苛的標準。"
+msgstr ""
+"由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，"
+"我們也要求遵守 The Standard for Public Code 中最嚴苛的標準。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1437,13 +1441,13 @@ msgid ""
 " opportunity to work together to improve our methods and the Standard. We "
 "may not accept all changes, but we will explain our logic."
 msgstr ""
-"我們會努力儘速回覆所有提取請求。提取請求讓我們有機會一起合作，改善我們的方法"
-"與公共程式標準。我們可能不會接受貢獻者提出的所有修改，但我們會解釋背後的邏輯"
-"。"
+"我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，"
+"改善我們的方法與 The Standard for Public "
+"Code。我們可能不會接受貢獻者提出的所有修改，但我們會解釋背後的邏輯。"
 
 #: ./README.md:block 1 (header)
 msgid "Standard for Public Code"
-msgstr "公共程式標準"
+msgstr "The Standard for Public Code"
 
 #: ./README.md:block 3 (paragraph)
 msgid ""
@@ -1452,8 +1456,9 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"公共程式標準提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公"
-"共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供應商的指引。"
+"The Standard for Public Code 提供公共組織一個準備開源解決方案的模型，讓他們與"
+"其他地方相似的公共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供"
+"應商的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1499,11 +1504,12 @@ msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr "公共程式標準目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。"
+msgstr "The Standard for Public Code 目前為草稿階段。我們正在準備推出1."
+"0版，目前正在幾個代碼庫上測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將公共程式標準套用在您的代碼庫"
+msgstr "將 The Standard for Public Code 套用在您的代碼庫"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1514,10 +1520,10 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將公共程式標準套用在您的代碼庫，不需要任何猶豫，因為公共程式標準是開"
-"放性標準，任何人都可以免費使用。若要瞭解您代碼庫是否就緒，可以進行[資格自我評"
-"估](https://publiccodenet.github.io/assessment-"
-"eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
+"若您想要將 The Standard for Public Code 套用在您的代碼庫，不需要任何猶豫，"
+"因為 The Standard for Public Code 是開放性標準，任何人都可以免費使用。若要瞭"
+"解您代碼庫是否就緒，可以進行[資格自我評估](https://publiccodenet.github.io/"
+"assessment-eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
 
 #: ./README.md:block 9 (paragraph)
 msgid ""
@@ -1528,10 +1534,11 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
-"將公共程式標準套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不"
-"明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與您抱持同樣看法的民"
-"眾。如需靈感，請參閱[社群打造的實施指南](https://publiccodenet.github.io/"
-"community-implementation-guide-standard/)，當中包括範例與其他訣竅。"
+"將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。"
+"若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與"
+"您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指南](https://publiccode"
+"net.github.io/community-implementation-guide-standard/"
+")，當中包括範例與其他訣竅。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
@@ -1539,8 +1546,9 @@ msgid ""
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
 msgstr ""
-"若新版的公共程式標準有突破性的修改，The Foundation for Public "
-"Code的代碼庫管理人員會幫助公共程式標準用戶彌補不同版之間的差異。"
+"若新版的 The Standard for Public Code 有突破性的修改，The Foundation for "
+"Public Code 的代碼庫管理人員會幫助The Standard for Public Code "
+"使用者彌補不同版之間的差異。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1582,8 +1590,8 @@ msgid ""
 "[standard.publiccode.net](https://standard.publiccode.net/). See "
 "[`index.md`](index.md) for an overview of all content."
 msgstr ""
-"公共程式標準就在[standard.publiccode.net](https://standard.publiccode.net/"
-")。內容概覽請參閱[`index.md`](index.md)。"
+"The Standard for Public Code 就在[standard.publiccode.net](https://standard."
+"publiccode.net/)。內容概覽請參閱[`index.md`](index.md)。"
 
 #: ./README.md:block 16 (paragraph)
 msgid ""
@@ -1592,9 +1600,9 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
-"[![公共程式標準YouTube影片縮圖：兩隻手中間放著一本印刷版公共程式標準](https:/"
-"/img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/"
-"watch?v=QWt6vB-cipE)"
+"[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 "
+"The Standard for Public Code ](https://img.youtube.com/vi/QWt6vB-cipE/"
+"mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
 msgid ""
@@ -1602,8 +1610,8 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
-"[公共程式標準介紹影片](https://www.youtube.com/watch?v=QWt6vB-cipE) from "
-"Creative Commons Global Summit 2020 (4:12) on YouTube."
+"[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v"
+"=QWt6vB-cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube."
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
@@ -1614,8 +1622,9 @@ msgid ""
 "The Foundation for Public Code is committed to maintaining and developing "
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
-msgstr "The Foundation for Public "
-"Code致力於維護與開發公共程式標準，且品質也會符合該標準本身的品質。"
+msgstr ""
+"The Foundation for Public Code 致力於維護與開發 The Standard for Public Code "
+"，且品質也會符合該標準本身的品質。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -1677,7 +1686,7 @@ msgstr "測試"
 msgid ""
 "A variety of test scripts are included. The script `script/test-all.sh` "
 "wraps running of all local tests."
-msgstr "本標準包含許多測試腳本。`script/test-all.sh`腳本則會開始執行所有本機測試。"
+msgstr "本標準包含許多測試腳本。`script/test-all.sh` 腳本則會開始執行所有本機測試。"
 
 #: ./README.md:block 29 (paragraph)
 msgid ""
@@ -1689,7 +1698,7 @@ msgstr ""
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
-msgstr "生成公共程式標準PDF檔案"
+msgstr "生成 The Standard for Public Code PDF 檔案"
 
 #: ./README.md:block 31 (paragraph)
 msgid ""
@@ -1698,9 +1707,9 @@ msgid ""
 "[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
 "used to transform PDFs into `.epub`."
 msgstr ""
-"除了Jekyll以外，要生成PDF檔案也需要仰賴[Weasyprint](https://weasyprint.org/"
-")以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/"
-")可以將PDF轉換成`.epub`檔案。"
+"除了 Jekyll 以外，要生成 PDF 檔案也需要仰賴[Weasyprint](https://weasyprint."
+"org/)以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)"
+"可以將 PDF 轉換成`.epub`檔案。"
 
 #: ./README.md:block 32 (paragraph)
 msgid ""
@@ -1712,8 +1721,8 @@ msgstr "若要生成這些種類的檔案，則需要安裝類似下列的依附
 msgid ""
 "The file `standard-print.html` can be converted to a nice looking PDF, along"
 " with the other release files, using:"
-msgstr "使用以下腳本，可以將`standard-print.html` "
-"檔案以及其他的版本檔案轉換成美觀的PDF："
+msgstr "使用以下腳本，可以將 `standard-print.html` "
+"檔案以及其他的版本檔案轉換成美觀的 PDF："
 
 #: ./README.md:block 36 (header)
 msgid "License"
@@ -1730,12 +1739,11 @@ msgid ""
 "it. If you contribute you also grant these rights to others. You can read "
 "more about how to help in the [contributing guide](CONTRIBUTING.md)."
 msgstr ""
-"公共程式標準採用CC 0[授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任"
-"何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一"
-"步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
+"The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解"
+"與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權"
+"利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 2 redirect_from:"
 msgstr "order: 2 redirect_from:"
 
@@ -1780,25 +1788,26 @@ msgstr "規定"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "The codebase MUST include the policy that the source code is based on."
-msgstr "代碼庫「必須」包含做為原始碼基礎的政策。"
+msgstr "代碼庫「必須（Must）」包含做為原始碼基礎的政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr "若一個政策以原始碼為基礎，該原始碼「必須」包含在代碼庫內（用於詐騙偵測的原始"
-"碼除外）。"
+msgstr "若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵"
+"測的原始碼除外）。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr "政策格式「應該」可以機讀且明確。"
+msgstr "政策格式「應該（Should）」可以機讀且明確。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
-msgstr "[持續整合](../glossary.md#continuous-integration) "
-"測試「應該」驗證原始碼與政策是否有一致執行。"
+msgstr ""
+"[持續整合](../glossary.md#continuous-integration) "
+"測試「應該（Should）」驗證原始碼與政策是否有一致執行。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
 msgid "How to test"
@@ -1888,7 +1897,7 @@ msgstr ""
 "納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-lex."
 "europa.eu/eli/reg/2016/679/oj)或是 [歐盟無障礙指令](https://ec.europa.eu/"
 "digital-single-market/en/web-"
-"accessibility)這些法律義務，或是人權政策（像是公共組織對機會平等的承諾。"
+"accessibility)這些法律義務，或是人權政策，像是公共組織對機會平等的承諾。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
@@ -1963,7 +1972,6 @@ msgid ""
 msgstr "維基百科的[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。"
 
 #: ./criteria/code-in-the-open.md:block 3 (header)
-#, fuzzy
 msgid "order: 1"
 msgstr "order: 1"
 
@@ -2011,7 +2019,8 @@ msgstr "代碼庫「不允許」包含使用者、使用者機構或第三方的
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr "目前沒有使用的任何原始碼(像是新版本、提案或舊版本)都「應該」公佈。"
+msgstr "目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈"
+"。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
@@ -2119,7 +2128,6 @@ msgstr ""
 "blog.gov.uk/2014/01/27/how-we-use-github/)》。"
 
 #: ./criteria/document-codebase-maturity.md:block 3 (header)
-#, fuzzy
 msgid ""
 "order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
 "maturity"
@@ -2261,12 +2269,10 @@ msgstr ""
 "agile-delivery)》。"
 
 #: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 8 redirect_from:"
 msgstr "order: 8 redirect_from:"
 
 #: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/document-objectives"
 msgstr "criteria/document-objectives"
 
@@ -2357,12 +2363,10 @@ msgstr ""
 "RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
 
 #: ./criteria/document-the-code.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 9 redirect_from:"
 msgstr "order: 9 redirect_from:"
 
 #: ./criteria/document-the-code.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/documenting"
 msgstr "criteria/documenting"
 
@@ -2536,7 +2540,6 @@ msgid ""
 msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
 
 #: ./criteria/index.md:block 3 (header)
-#, fuzzy
 msgid "order: 0"
 msgstr "order: 0"
 
@@ -2545,12 +2548,10 @@ msgid "Criteria"
 msgstr "標準"
 
 #: ./criteria/index.md:block 5 (paragraph)
-#, fuzzy
 msgid "{% assign sorted = site.pages | sort:\"order\" %}"
 msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
 
 #: ./criteria/index.md:block 6 (paragraph)
-#, fuzzy
 msgid ""
 "{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
 "!= \"index.md\" %}{% if page.title %}"
@@ -2559,19 +2560,16 @@ msgstr ""
 "!= \"index.md\" %}{% if page.title %}"
 
 #: ./criteria/index.md:block 7 (ordered list)
-#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 msgstr ""
 "[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
 
 #: ./criteria/maintain-version-control.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 6 redirect_from:"
 msgstr "order: 6 redirect_from:"
 
 #: ./criteria/maintain-version-control.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/version-control-and-history"
 msgstr "criteria/version-control-and-history"
 
@@ -2592,7 +2590,7 @@ msgstr ""
 "[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md"
 "#source-code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓"
 "您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人"
-"員針對修改變動平行作業，幫助未來的開發人員瞭解修改的原因。"
+"員針對修改變動平行作業，並幫助未來的開發人員瞭解修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All files in the codebase MUST be version controlled."
@@ -2679,7 +2677,7 @@ msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
+msgstr "檢查代碼庫時，在可能的情況下檔案都是採用文字格式。"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid ""
@@ -2775,7 +2773,6 @@ msgstr ""
 "education.pdf)」列出了最常用的 git 指令。"
 
 #: ./criteria/make-contributing-easy.md:block 3 (header)
-#, fuzzy
 msgid "order: 5"
 msgstr "order: 5"
 
@@ -2817,8 +2814,8 @@ msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（如郵寄"
-"清單）。"
+msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄"
+"清單。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
@@ -2900,7 +2897,7 @@ msgstr "確保民眾可輕易找到合適的溝通管道來問維護人員與利
 msgid ""
 "Make sure that appropriate contact details are included in the metadata, for"
 " instance in the publiccode.yml file."
-msgstr "確保中介資料包含合適的聯絡資訊，例如在publiccode.yml檔案中。"
+msgstr "確保中介資料包含合適的聯絡資訊，例如在 publiccode.yml 檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 18 (unordered list)
 msgid ""
@@ -2921,12 +2918,10 @@ msgstr ""
 "2017/09/04/the-benefits-of-coding-in-the-open/)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 14 redirect_from:"
 msgstr "order: 14 redirect_from:"
 
 #: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/findability"
 msgstr "criteria/findability"
 
@@ -3064,8 +3059,8 @@ msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by using natural language, for instance, using the "
 "short description."
-msgstr "檢查以自然語言（例如簡短說明ㄢ來作搜尋時，有超過一個的常用主流搜尋引擎，都將"
-"代碼庫放在搜尋結果的第一頁中。"
+msgstr "檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
+"庫放在搜尋結果的第一頁中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3175,13 +3170,11 @@ msgstr ""
 "對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 3 redirect_from:"
 msgstr "order: 3 redirect_from:"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
 #: list)
-#, fuzzy
 msgid "criteria/reusable-and-portable-codebases"
 msgstr "criteria/reusable-and-portable-codebases"
 
@@ -3377,7 +3370,7 @@ msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr "確保代碼庫有將貴組織單位列為已知用戶。"
+msgstr "確保代碼庫有將貴組織單位列為已知使用者。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
@@ -3465,12 +3458,10 @@ msgstr ""
 "questions/qa-i18n)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 13 redirect_from:"
 msgstr "order: 13 redirect_from:"
 
 #: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/open-licenses"
 msgstr "criteria/open-licenses"
 
@@ -3630,7 +3621,7 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
-"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"紐西蘭 CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
 "videos/creative-commons-kiwi)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
@@ -3651,12 +3642,10 @@ msgstr ""
 ")提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
 
 #: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 7 redirect_from:"
 msgstr "order: 7 redirect_from:"
 
 #: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/require-review"
 msgstr "criteria/require-review"
 
@@ -3873,12 +3862,10 @@ msgstr ""
 "g43d857af8_0177)》。"
 
 #: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 15 redirect_from:"
 msgstr "order: 15 redirect_from:"
 
 #: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/style"
 msgstr "criteria/style"
 
@@ -3984,12 +3971,10 @@ msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/"
 "Programming_style)》條目。"
 
 #: ./criteria/use-continuous-integration.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 12 redirect_from:"
 msgstr "order: 12 redirect_from:"
 
 #: ./criteria/use-continuous-integration.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/continuous-integration"
 msgstr "criteria/continuous-integration"
 
@@ -4236,12 +4221,10 @@ msgstr ""
 "regularly)》。"
 
 #: ./criteria/use-open-standards.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 11 redirect_from:"
 msgstr "order: 11 redirect_from:"
 
 #: ./criteria/use-open-standards.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/open-standards"
 msgstr "criteria/open-standards"
 
@@ -4365,12 +4348,10 @@ msgstr ""
 "principles)》[政策](../glossary.md#policy)報告。"
 
 #: ./criteria/use-plain-english.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 10 redirect_from:"
 msgstr "order: 10 redirect_from:"
 
 #: ./criteria/use-plain-english.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/understandable-english-first"
 msgstr "criteria/understandable-english-first"
 
@@ -4544,12 +4525,10 @@ msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/abo
 ")》。"
 
 #: ./criteria/welcome-contributors.md:block 3 (paragraph)
-#, fuzzy
 msgid "order: 4 redirect_from:"
 msgstr "order: 4 redirect_from:"
 
 #: ./criteria/welcome-contributors.md:block 4 (unordered list)
-#, fuzzy
 msgid "criteria/open-to-contributions"
 msgstr "criteria/open-to-contributions"
 
@@ -4755,14 +4734,15 @@ msgid ""
 "The printed Standard for Public Code is printed by Reclameland. This guide "
 "tries to provide the relevant information to print it there or somewhere "
 "else."
-msgstr "公共程式標準由Reclameland負責印刷。本指南提供印刷相關資訊，方便在Reclameland"
-"或其他地方印刷。"
+msgstr ""
+"The Standard for Public Code 由 Reclameland "
+"負責印刷。本指南提供印刷相關資訊，方便在 Reclameland 或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
 "Details, mostly in order they are on the Reclameland page with the Dutch if "
 "necessary:"
-msgstr "印刷詳細資訊（依照Reclameland網頁上的順序，需要的地方有附上德文）："
+msgstr "印刷詳細資訊（依照 Reclameland 網頁上的順序，需要的地方有附上荷蘭語）："
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid ""
@@ -4782,7 +4762,7 @@ msgstr "直橫向：直向（Staand）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing inside: 4/4 dual sided full color"
-msgstr "內頁印刷：正四反四（雙面彩色）"
+msgstr "內頁印刷：正四反四，雙面全色印刷"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Inside material: 90 grams biotop"
@@ -4794,7 +4774,7 @@ msgstr "封面：350克封面"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing cover: 4/0 one sided full cover"
-msgstr "封面印刷：正四（單面彩色）"
+msgstr "封面印刷：正四（單面滿版印刷）"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover treatment: one sided matt foliated (Enke)"
@@ -4820,7 +4800,7 @@ msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
-msgstr "發行新版本的公共程式標準"
+msgstr "發行新版本的 The Standard for Public Code"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Review state of the 'develop' branch"
@@ -4832,7 +4812,7 @@ msgstr "確保該版本的內容都已經完成合併"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Invite a proofread of the current state of the branch"
-msgstr "請人校對目前的分支"
+msgstr "請人校對目前的分支狀態"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
@@ -4866,15 +4846,15 @@ msgstr "更新新版本"
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
-msgstr "更新`_config.yml`、`README.md`與`publiccode.yml`的版本編號"
+msgstr "更新 `_config.yml`、`README.md` 與 `publiccode.yml` 的版本編號"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
-msgstr "使用`script/make-version-badge.sh`更新`assets/version-badge.svg`"
+msgstr "使用 `script/make-version-badge.sh` 更新 `assets/version-badge.svg`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update releaseDate in `publiccode.yml`"
-msgstr "更新`publiccode.yml`當中的發行日期"
+msgstr "更新 `publiccode.yml` 當中的發行日期"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
@@ -4886,21 +4866,21 @@ msgstr "更新[`CHANGELOG.md`](../CHANGELOG.md)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Perform extra pass on diff to the 'main' branch"
-msgstr "與'main'分支進行額外比較"
+msgstr "在 diff 進行額外傳輸到 'main' 分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "run `script/generate-review-template.sh` and commit updated `docs/review-"
 "template.html`"
 msgstr ""
-"執行 `script/generate-review-template.sh` 與更新提交紀錄`docs/review-template"
-".html`"
+"執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-"
+"template.html`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "update `docs/standard-for-public-code.md` with the new text from the review "
 "template, updating any status changes as a result"
-msgstr "用審查範本的新文字來更新`docs/standard-for-public-code."
+msgstr "用審查範本的新文字來更新 `docs/standard-for-public-code."
 "md`，更新所有的狀態變更"
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4920,7 +4900,7 @@ msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
-msgstr "使用`script/pdf.sh rc1`檢視渲染的 `.pdf`"
+msgstr "使用 `script/pdf.sh rc1` 檢視渲染的 `.pdf`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Ensure no link collisions exist"
@@ -4939,7 +4919,7 @@ msgstr "若需要，進行修復並且重複進行額外傳輸"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push branch, open a pull request to the 'main' branch"
-msgstr "推動分支，對 「'main'」分支提出提取請求"
+msgstr "推動分支，對 「'main'」分支提出拉入請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Request review from multiple reviewers, especially a proofreader"
@@ -4954,13 +4934,13 @@ msgstr "審查人員若有發現不會影響發行的缺失，則會建立議題
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "If needed for release, reviewers may create pull requests to resolve issues"
-msgstr "如果是發行所需，審查人員可以建立提取請求來解決問題"
+msgstr "如果是發行所需，審查人員可以建立拉入請求來解決問題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Re-request reviews if additional pull requests are merged into release "
 "branch"
-msgstr "若額外的提取請求合併至發行分支，請要求重新審查"
+msgstr "若額外的拉入請求合併至發行分支，請要求重新審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Run the to-archive-org.sh script"
@@ -4979,12 +4959,10 @@ msgid "Switch to the 'main' branch, `git pull` and `git status`"
 msgstr "切換至「'main'」分支、「`git pull`」與「`git status`」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
-#, fuzzy
 msgid "`git tag $MAJOR.$MINOR.$PATCH`"
 msgstr "`git tag $MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
-#, fuzzy
 msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
 msgstr "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
 
@@ -4993,23 +4971,20 @@ msgid "Trigger a rebuild of gh-pages"
 msgstr "觸發 gh-pages 的重建"
 
 #: ./docs/releasing.md:block 3 (ordered list)
-#, fuzzy
 msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 msgstr "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
-#, fuzzy
 msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
 msgstr "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
-#, fuzzy
 msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 msgstr "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Open a pull request from this branch to `main`"
-msgstr "從此分支向 「'main'」提出提取請求"
+msgstr "從此分支向「'main'」提出拉入請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Approve and merge PR (containing empty commit)"
@@ -5060,8 +5035,9 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
-"代碼庫管理人員每月定期審查發展路線圖，這是[積壓修剪](https://about.publiccode"
-".net/activities/standard-maintenance/backlog-pruning.html)的一部份。"
+"代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會議](https://about."
+"publiccode.net/activities/standard-maintenance/backlog-pruning."
+"html)的一部份。"
 
 #: ./docs/roadmap.md:block 6 (header)
 msgid "Current work"
@@ -5069,7 +5045,7 @@ msgstr "目前任務"
 
 #: ./docs/roadmap.md:block 7 (unordered list)
 msgid "As far as possible, make the standard Standard-compliant"
-msgstr "盡可能讓標準符合公共程式標準"
+msgstr "盡可能讓標準符合 The Standard for Public Code"
 
 #: ./docs/roadmap.md:block 8 (header)
 msgid "Near term"
@@ -5087,7 +5063,7 @@ msgstr "#208號議題：需要時，將「程式碼」清楚標示為「原始
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid "Possibly: add in the illustrations for each criterion"
-msgstr "潛在解決方案：為每個標準新增圖解"
+msgstr "潛在解決方案：為每個標準新增圖示"
 
 #: ./docs/roadmap.md:block 10 (header)
 msgid "Longer term"
@@ -5101,8 +5077,8 @@ msgstr "認證標章"
 msgid ""
 "Add to README and index.md information (and eventually statistics) on "
 "adoption and use (issue #438)"
-msgstr "#438號議題：在採用與使用程式碼上，新增「README」與「index."
-"md」資訊（之後加入統計數據）"
+msgstr "新增「README」與「index."
+"md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Physical paper checklist"
@@ -5137,7 +5113,6 @@ msgid "QR codes for external links in print version"
 msgstr "印刷版外部連結的 QR 二維碼"
 
 #: ./foreword.md:block 3 (paragraph)
-#, fuzzy
 msgid "redirect_from:"
 msgstr "redirect_from:"
 
@@ -5153,7 +5128,8 @@ msgstr "序"
 msgid ""
 "The Standard for Public Code is a set of criteria that support public "
 "organizations in developing and maintaining software and policy together."
-msgstr "公共程式標準當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "The Standard for Public Code "
+"當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./foreword.md:block 7 (paragraph)
 msgid ""
@@ -5182,7 +5158,7 @@ msgid ""
 "distinct from regular software because it operates under fundamentally "
 "different circumstances and expectations."
 msgstr ""
-"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與預算法）與公"
+"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公"
 "共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體"
 "生產的安排，都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件"
 "與期待也不同。"
@@ -5475,13 +5451,14 @@ msgstr ""
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
-msgstr "公共程式標準目標"
+msgstr "The Standard for Public Code 目標"
 
 #: ./foreword.md:block 48 (paragraph)
 msgid ""
 "This Standard supports developers, designers, managers and public policy "
 "makers to:"
-msgstr "公共程式標準支持開發人員、設計師、管理人員以及公共政策制定者："
+msgstr "The Standard for Public Code "
+"支持開發人員、設計師、管理人員以及公共政策制定者："
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
@@ -5512,12 +5489,12 @@ msgstr "更好的經濟模型改善與供應商的關係"
 msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
-msgstr "代碼庫潛在用戶依照公共程式標準測試代碼庫，結果認為代碼庫容易重複利用、維護且"
-"品質相當高。"
+msgstr "代碼庫潛在使用者依照 The Standard for Public Code "
+"測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
-msgstr "公共程式標準能有如此特性是因為："
+msgstr "The Standard for Public Code 能有如此特性是因為："
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "setting out a common terminology for public code development"
@@ -5531,12 +5508,12 @@ msgstr "訂定措施協助優質公共程式的開發"
 msgid ""
 "providing guidance on how to fulfill its criteria and operationalize "
 "compliance"
-msgstr "提出如何符合公共程式標準的指引並且協助他人遵循"
+msgstr "提出如何符合 The Standard for Public Code 的指引並在施作中遵循"
 
 #: ./foreword.md:block 53 (paragraph)
 msgid ""
 "The Standard for Public Code is meant to be time and technology independent."
-msgstr "公共程式標準原意是要不受時間與科技限制。"
+msgstr "The Standard for Public Code 原意是要不受時間與科技限制。"
 
 #: ./foreword.md:block 54 (header)
 msgid "Who this is for"
@@ -5546,7 +5523,7 @@ msgstr "適用對象"
 msgid ""
 "The Standard for Public Code is for the people who create and reuse public "
 "code:"
-msgstr "公共程式標準適用於開發與重複使用公共程式的民眾："
+msgstr "The Standard for Public Code 適用於開發與重複使用公共程式的民眾："
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "public policy makers"
@@ -5601,8 +5578,8 @@ msgid ""
 "the background behind the Foundation for Public Code."
 msgstr ""
 "[2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/"
-"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹The Foundation for Public "
-"Code的背景。"
+"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹 The Foundation for Public Code "
+"的背景。"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5634,7 +5611,7 @@ msgid ""
 "can find us at [our website](https://publiccode.net/), email us at "
 "info@publiccode.net, or call us at +31 20 2 444 500."
 msgstr ""
-"若有疑問或想進一步瞭解The Foundation for Public "
+"若有疑問或想進一步瞭解 The Foundation for Public "
 "Code，請造訪[我們的官網](https://publiccode.net/)、寄電子郵件到 "
 "info@publiccode.net，或是撥打我們的電話（+31 20 2 444 500）。"
 
@@ -5644,7 +5621,7 @@ msgstr "詞彙表"
 
 #: ./glossary.md:block 4 (header)
 msgid "Code"
-msgstr "程式碼"
+msgstr "規則（Code）"
 
 #: ./glossary.md:block 5 (paragraph)
 msgid ""
@@ -5694,12 +5671,12 @@ msgstr "如果是有多家公家機關或部門，決策者不只一位，因而
 
 #: ./glossary.md:block 13 (header)
 msgid "General public"
-msgstr "公眾"
+msgstr "一般大眾"
 
 #: ./glossary.md:block 14 (paragraph)
 msgid ""
 "The public at large: end users of the code and the services based upon it."
-msgstr "一般民眾：程式碼以及以程式碼為基礎的服務的終端使用者。"
+msgstr "一般民眾：程式碼及以程式碼為基礎的服務的終端使用者。"
 
 #: ./glossary.md:block 15 (paragraph)
 msgid ""
@@ -5762,7 +5739,8 @@ msgstr "在國家層級，政策與立法（法律）通常是分開的，但地
 msgid ""
 "In the Standard the word 'policy' refers to policy created and adopted by "
 "public organizations such as governments and municipalities."
-msgstr "公共程式標準當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
+msgstr "The Standard for Public Code "
+"當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
@@ -5815,7 +5793,7 @@ msgid ""
 "or licensed with an open license that permits others to view and reuse the "
 "work freely and to produce derivative works."
 msgstr "為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複"
-"利用其內容的開放授權，藉此推動衍生程式。"
+"利用其內容的開放授權，藉此推動衍生工作。"
 
 #: ./glossary.md:block 32 (header)
 msgid "Repository"
@@ -5859,7 +5837,6 @@ msgstr ""
 "式碼的演變。修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。"
 
 #: ./index.md:block 3 (header)
-#, fuzzy
 msgid "toc: false"
 msgstr "toc: false"
 
@@ -5871,7 +5848,8 @@ msgstr "政府開源協作指引"
 msgid ""
 "The Standard for Public Code is a set of criteria that supports public "
 "organizations in developing and maintaining software and policy together."
-msgstr "公共程式標準當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "The Standard for Public Code "
+"當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./index.md:block 6 (paragraph)
 msgid ""
@@ -5884,11 +5862,12 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
-"公共程式標準指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區"
-"的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案。公共程式標準提"
-"供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過公共程式標"
-"準，合作建立可用、開放、易讀、負責且永續的代碼庫。公共程式標準適用於各政府層"
-"級的代碼庫，從超國家到市政府。"
+"The Standard for Public Code 指引正在建構自己開源解決方案的公共組織，方便他們"
+"未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案"
+"。The Standard for Public Code "
+"提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The "
+"Standard for Public Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The "
+"Standard for Public Code 適用於各政府層級的代碼庫，從超國家到市政府。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5896,14 +5875,14 @@ msgid ""
 "code)’ as open source software developed by public organizations, together "
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
-"公共程式標準將‘[公共程式](glossary.md#public-code)’定義為由公共組織所開發的開"
-"源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
+"The Standard for Public Code 將‘[公共程式](glossary.md#public-code)’定義為由"
+"公共組織所開發的開源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
 "The criteria of the Standard for Public Code are aligned with guidelines and"
 " best practices of open source software development."
-msgstr "公共程式標準當中的標準符合開源軟體開發的指引與最佳實務。"
+msgstr "The Standard for Public Code 當中的標準符合開源軟體開發的指引與最佳實務。"
 
 #: ./index.md:block 9 (paragraph)
 msgid ""
@@ -5937,7 +5916,6 @@ msgstr ""
 "\"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 11 (unordered list)
-#, fuzzy
 msgid ""
 "[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
 msgstr ""
@@ -5996,7 +5974,7 @@ msgid ""
 "Standard](https://publiccodenet.github.io/community-translations-standard/) "
 "in other languages"
 msgstr ""
-"[公共程式標準社群其他語言](https://publiccodenet.github.io/"
+"[The Standard for Public Code 社群其他語言](https://publiccodenet.github.io/"
 "community-translations-standard/) 非官方翻譯版"
 
 #: ./index.md:block 15 (unordered list)
@@ -6015,9 +5993,9 @@ msgid ""
 "template.html) used by Foundation for Public Code stewards for codebase "
 "review"
 msgstr ""
-"The Foundation for Public Code管理人員審查代碼庫時使用的 "
-"[公共程式標準檢查清單](https://github.com/publiccodenet/standard/blob/"
-"develop/docs/review-template.html)"
+"The Foundation for Public Code 管理人員審查代碼庫時使用的 [The Standard for "
+"Public Code 檢查清單](https://github.com/publiccodenet/standard/blob/develop/"
+"docs/review-template.html)"
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
@@ -6043,7 +6021,7 @@ msgstr "「政策制定者」、「管理人員」以及「開發人員與設計
 msgid ""
 "Below is a brief explanation of each of these sections and how they are used"
 " within the criteria of the Standard."
-msgstr "以下是公共程式標準各章節的簡介，以及在標準當中的功用。"
+msgstr "以下是 The Standard for Public Code 各章節的簡介，以及在標準當中的功用。"
 
 #: ./readers-guide.md:block 7 (header)
 msgid "Introduction"
@@ -6059,7 +6037,7 @@ msgstr "本章節探討這些標準的目的，以及為什麼對代碼庫使用
 msgid ""
 "This section lists what needs to be done in order to comply with the "
 "standard."
-msgstr "這章節解釋如何遵循公共程式標準。"
+msgstr "這章節解釋如何遵循 The Standard for Public Code 。"
 
 #: ./readers-guide.md:block 11 (paragraph)
 msgid ""
@@ -6113,8 +6091,9 @@ msgid ""
 "This section offers actions you can take to see if a contribution is "
 "compliant with the Standard. This is key if you want to operationalize the "
 "Standard."
-msgstr "本章節列出您可採取的行動，藉此了解貢獻內容是否遵循公共程式標準。如果您想要實"
-"施公共程式標準，這將會是關鍵。"
+msgstr ""
+"本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public "
+"Code 。如果您想要實施 The Standard for Public Code ，這將會是關鍵。"
 
 #: ./readers-guide.md:block 15 (paragraph)
 msgid ""
@@ -6162,7 +6141,7 @@ msgstr "本章節主要對象是開發人員與設計師，列出他們的角色
 msgid ""
 "Developers are usually more technically aligned and have more impact on the "
 "delivery of services than the previous groups."
-msgstr "開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務的交付的影響更大。"
+msgstr "開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務交付的影響更大。"
 
 #: ./readers-guide.md:block 25 (header)
 msgid "Limitation of scope"
@@ -6174,8 +6153,9 @@ msgid ""
 "implementations of a codebase. This means the standard does not tell "
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
-msgstr "公共程式標準不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如"
-"何遵循他們組織的當地技術基礎建設或法律框架。"
+msgstr ""
+"The Standard for Public Code 不是為了代碼庫的個別執行所撰寫。這代表該標準不是"
+"要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6186,8 +6166,9 @@ msgid ""
 "Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
 "synergize well with them."
 msgstr ""
-"公共程式標準有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動"
-"協作。因此公共程式標準目的並非是要取代品質標準（像是 ISO 25000 "
+"The Standard for Public Code "
+"有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。"
+"因此The Standard for Public Code 目的並非是要取代品質標準（像是 ISO 25000 "
 "認證），或是以安全為準的標準（像是 [OpenSSF 最佳實務標章](https://github.com/"
 "coreinfrastructure/best-practices-badge)），而是要與他們協作。"
 
@@ -6196,5 +6177,7 @@ msgid ""
 "And while the purpose includes enabling collaboration, it will not guarantee"
 " that a community will spring into existence. That still requires "
 "proactiveness and ambition beyond making the codebase collaboration ready."
-msgstr "公共程式標準的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立"
-"社群，除了代碼庫需要準備好進行協作以外，也需要主事者的積極與野心。"
+msgstr ""
+"The Standard for Public Code 的目的之一在於促進協作，但也無法保證能夠催生出一"
+"個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要協作者的積極推"
+"動與野心。"

From 62ed28346c3d8230bbae1c55f64be424bf540a1d Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Tue, 29 Aug 2023 11:19:17 +0800
Subject: [PATCH 40/71] update: en/messages.po by 0.7.1

---
 locales/en/LC_MESSAGES/messages.po | 507 +++++++++++++++--------------
 1 file changed, 263 insertions(+), 244 deletions(-)

diff --git a/locales/en/LC_MESSAGES/messages.po b/locales/en/LC_MESSAGES/messages.po
index 46615c34..9fad8d18 100644
--- a/locales/en/LC_MESSAGES/messages.po
+++ b/locales/en/LC_MESSAGES/messages.po
@@ -194,824 +194,885 @@ msgid ""
 msgstr ""
 
 #: ./CHANGELOG.md:block 3 (header)
-msgid "Version history"
+msgid ""
+"script/release-body.sh expects VERSION in the first second-level header"
+msgstr ""
+
+#: ./CHANGELOG.md:block 4 (header)
+msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
 msgstr ""
 
 #: ./CHANGELOG.md:block 5 (header)
+msgid "Version history"
+msgstr ""
+
+#: ./CHANGELOG.md:block 6 (header)
+msgid "Version 0.7.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (paragraph)
+msgid ""
+"July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
+"clarifies references to code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"The criterion \"Make the codebase reusable and portable\" was renamed from "
+"\"Create reusable and portable code\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Added a glossary entry for \"Source Code\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"References to \"code\" which only applied to \"source code\" now reference "
+"\"source code\" explicitly."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Clarification of \"running code\" as \"software\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Minor changes to clarify \"code\" vs \"codebase\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Simplify guidance to policy makers in Bundle policy and source code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"Clarify How to test sections of Make the codebase findable and Make the "
+"codebase reusable and portable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Add a criteria and requirements checklist to the release artifacts."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Increase automation of the release process."
+msgstr ""
+
+#: ./CHANGELOG.md:block 9 (header)
 msgid "Version 0.7.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 6 (paragraph)
+#: ./CHANGELOG.md:block 10 (paragraph)
 msgid ""
 "May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
 "review funding and clarifies review process requirement."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid ""
 "Add requirement to document who is expected to cover the cost of reviewing "
 "contributions."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid ""
 "Change the focus of contributions adhering to standards to focus on the "
 "review of contributions."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Review template now in HTML format."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Introduction converted to foreword."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Improved contributing guidelines."
 msgstr ""
 
-#: ./CHANGELOG.md:block 7 (unordered list)
+#: ./CHANGELOG.md:block 11 (unordered list)
 msgid "Improved documentation of scripts."
 msgstr ""
 
-#: ./CHANGELOG.md:block 8 (header)
+#: ./CHANGELOG.md:block 12 (header)
 msgid "Version 0.6.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 9 (paragraph)
+#: ./CHANGELOG.md:block 13 (paragraph)
 msgid ""
 "April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
 "portability and tests and an introduction to each criterion."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about the development "
 "being a collaboration between multiple parties."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about being dependent "
 "on a single vendor."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "New requirement in Use continuous integration about publishing results for "
 "automated tests."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Differentiating the two requirements about security to clearly be about "
 "providing a method and having documentation about it."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Rephrased requirements to focus on the codebase rather than contributor "
 "behavior."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Added general What this does not do section in the introduction of the "
 "Standard."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Added guidance for public policy makers about related policies and license "
 "compatibility."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Added guidance for developers and designers about version controlling files."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Clarified guidance for developers and designers about prompt responses and "
 "search engine optimization."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Added Further reading about accessibility."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Aligned criteria URLs with criteria names."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Improved navigation in the web version."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Moved tools in Further reading sections to the community implementation "
 "guide."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Moved compliance or certification process to "
 "[publiccode.net](https://publiccode.net)."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Change format of the review template to make it easier to update after a new"
 " release."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid ""
 "Improved the text on the landing page and added links to related resources."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Added spell checker automated test."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Made minor changes to text for clarity and consistency."
 msgstr ""
 
-#: ./CHANGELOG.md:block 10 (unordered list)
+#: ./CHANGELOG.md:block 14 (unordered list)
 msgid "Moved SPDX headers to yaml header."
 msgstr ""
 
-#: ./CHANGELOG.md:block 11 (header)
+#: ./CHANGELOG.md:block 15 (header)
 msgid "Version 0.5.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 12 (paragraph)
+#: ./CHANGELOG.md:block 16 (paragraph)
 msgid ""
 "January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
 "guidelines."
 msgstr ""
 
-#: ./CHANGELOG.md:block 13 (unordered list)
+#: ./CHANGELOG.md:block 17 (unordered list)
 msgid ""
 "Adjust the coding style requirement to focus on the codebase using a style "
 "guide rather than contributor behavior."
 msgstr ""
 
-#: ./CHANGELOG.md:block 13 (unordered list)
+#: ./CHANGELOG.md:block 17 (unordered list)
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
 msgstr ""
 
-#: ./CHANGELOG.md:block 13 (unordered list)
+#: ./CHANGELOG.md:block 17 (unordered list)
 msgid ""
 "Moved requirement about testing the code by using examples to Use continuous"
 " integration from Document the code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 13 (unordered list)
+#: ./CHANGELOG.md:block 17 (unordered list)
 msgid ""
 "Split requirement about machine testable standards to clarify that open is "
 "more important than testable."
 msgstr ""
 
-#: ./CHANGELOG.md:block 13 (unordered list)
+#: ./CHANGELOG.md:block 17 (unordered list)
 msgid ""
 "Adjust how to test findability requirements to be less reliant on search "
 "engine algorithms."
 msgstr ""
 
-#: ./CHANGELOG.md:block 14 (header)
+#: ./CHANGELOG.md:block 18 (header)
 msgid "Version 0.4.1"
 msgstr ""
 
-#: ./CHANGELOG.md:block 15 (paragraph)
+#: ./CHANGELOG.md:block 19 (paragraph)
 msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid ""
 "Document maturity focuses on whether or not versions of the codebase are "
 "ready to use."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid ""
 "Document maturity no longer requires specific labels for codebases that are "
 "not ready to use."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Audit flow image now generated from an easier to translate format."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Improved guidance on How to test."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Add publiccode.yml file."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Add review template."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Consistently link glossary terms."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Add practices and standards to follow in CONTRIBUTING."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Add Matti Schneider to Authors."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Add remaining SPDX headers to files."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Made additional minor changes to text for clarity."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid "Some hyperlinks updated."
 msgstr ""
 
-#: ./CHANGELOG.md:block 16 (unordered list)
+#: ./CHANGELOG.md:block 20 (unordered list)
 msgid ""
 "Moved examples to the [Community implementation "
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
 
-#: ./CHANGELOG.md:block 17 (header)
+#: ./CHANGELOG.md:block 21 (header)
 msgid "Version 0.4.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 18 (paragraph)
+#: ./CHANGELOG.md:block 22 (paragraph)
 msgid ""
 "September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Introduce new criterion: Make the codebase findable."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Improve How to test section for most criteria."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid ""
 "New requirement in Welcome contributors about publishing activity "
 "statistics."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Removed redundant requirement about portable and reusable code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid ""
 "Expand open license definition to include both OSI and FSF approved "
 "licenses."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Add SPDX license identifiers to files."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Introduced new Code of Conduct."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Clarify distinction between source code and policy text."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Restructuring of requirements with bullet point lists."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Acknowledge the importance of codebase modularity for reuse."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Move requirements related to Findability to the new criterion."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Clarify the role of non-open standards when used in a codebase."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Additional guidance about build-time and runtime dependencies."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Update structure of Authors file."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Add Audrey Tang to Authors."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid "Added a list of criteria to the print edition."
 msgstr ""
 
-#: ./CHANGELOG.md:block 19 (unordered list)
+#: ./CHANGELOG.md:block 23 (unordered list)
 msgid ""
 "Clarify what the standard means with policymakers, managers, developers and "
 "designers."
 msgstr ""
 
-#: ./CHANGELOG.md:block 20 (header)
+#: ./CHANGELOG.md:block 24 (header)
 msgid "Version 0.3.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 21 (paragraph)
+#: ./CHANGELOG.md:block 25 (paragraph)
 msgid ""
 "May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid ""
 "Requirement for localization made explicit in Create reusable and portable "
 "code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid "Community translations now linked in the footer."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
 msgstr ""
 
-#: ./CHANGELOG.md:block 22 (unordered list)
+#: ./CHANGELOG.md:block 26 (unordered list)
 msgid "Many minor clarifications to language and sentences made more simple."
 msgstr ""
 
-#: ./CHANGELOG.md:block 23 (header)
+#: ./CHANGELOG.md:block 27 (header)
 msgid "Version 0.2.3"
 msgstr ""
 
-#: ./CHANGELOG.md:block 24 (paragraph)
+#: ./CHANGELOG.md:block 28 (paragraph)
 msgid ""
 "March 15th 2022: 📜 the ninth draft allows English summaries for policy "
 "lacking an official translation."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Relax the criterion Use plain English by adding a new requirement allows "
 "bundled policy not available in English to have an accompanying summary in "
 "English instead of translating the full text."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Similarly, allow for English summaries for policies not available in English"
 " in Bundle policy and code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Clarify that term 'policy' includes processes which impact development and "
 "deployment in Bundle policy and code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Emphasize reusability also on parts of the solutions in Create reusable and "
 "portable code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Expand guidance to Developers and designers in Create reusable and portable "
 "code about deploying to proprietary platforms."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Add nuance to use of non-English terms in what management need to do in Use "
 "plain English."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid ""
 "Change the pull request process diagram to use Mermaid instead of BPMN to "
 "make [community translations](https://github.com/publiccodenet/community-"
 "translations-standard) easier."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid "Added Maurice Hendriks to AUTHORS."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid "Added OpenApi Specification to further reading."
 msgstr ""
 
-#: ./CHANGELOG.md:block 25 (unordered list)
+#: ./CHANGELOG.md:block 29 (unordered list)
 msgid "Made the attributions in further reading sections clearer."
 msgstr ""
 
-#: ./CHANGELOG.md:block 26 (header)
+#: ./CHANGELOG.md:block 30 (header)
 msgid "Version 0.2.2"
 msgstr ""
 
-#: ./CHANGELOG.md:block 27 (paragraph)
+#: ./CHANGELOG.md:block 31 (paragraph)
 msgid ""
 "November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
 " as code may not be in English."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid ""
 "Document exception to \"All code MUST be in English\" where policy is "
 "interpreted as code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid ""
 "Add MAY requirement regarding committer email addresses in Maintain version "
 "control."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Expand guidance to Policy Makers in Bundle policy and code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Expand guidance to Developers and designers in Use a coherent style."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add \"Different contexts\" to glossary."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add Digital Public Goods approval badge."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add Open Standards principles to further reading."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add Definition of plain language to further reading."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Move the Semantic Versioning Specification further reading reference."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid ""
 "Clarify that publiccode.yml is one example of a machine-readable metadata "
 "description."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
 msgstr ""
 
-#: ./CHANGELOG.md:block 28 (unordered list)
+#: ./CHANGELOG.md:block 32 (unordered list)
 msgid "Add instructions for creating a print version."
 msgstr ""
 
-#: ./CHANGELOG.md:block 29 (header)
+#: ./CHANGELOG.md:block 33 (header)
 msgid "Version 0.2.1"
 msgstr ""
 
-#: ./CHANGELOG.md:block 30 (paragraph)
+#: ./CHANGELOG.md:block 34 (paragraph)
 msgid ""
 "March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
 "0.2.0."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid ""
 "New SHOULD requirement on using a distributed version control system and why"
 " distributed is important."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid ""
 "Feedback requirements for rejected contributions are more strict than "
 "accepted ones."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid ""
 "Specify that copyright and license notices should also be machine-readable."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Advice on how to test that notices be machine-readable."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Clarify guidance for rolling releases."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Clear up definition of version control in glossary."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid ""
 "Add further reading encouraging contribution, SPDX, Git and reviewing "
 "contributions."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Add links to videos about the concept of public code."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Update BPMN link."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Reduce link duplication."
 msgstr ""
 
-#: ./CHANGELOG.md:block 31 (unordered list)
+#: ./CHANGELOG.md:block 35 (unordered list)
 msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
 msgstr ""
 
-#: ./CHANGELOG.md:block 32 (header)
+#: ./CHANGELOG.md:block 36 (header)
 msgid "Version 0.2.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 33 (paragraph)
+#: ./CHANGELOG.md:block 37 (paragraph)
 msgid ""
 "October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
 "and \"Welcome contributors\"."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Rename criterion \"Pay attention to codebase maturity\" to \"Document "
 "codebase maturity\"."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Glossary additions: continuous integration, policy, repository, and version "
 "control."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid "Replace references to 'cities' with 'public organizations'."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Clarify aspects of sensitive code by separating contributor and reviewer "
 "requirements into separate items."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid ""
 "Expand further reading, and guidance to policy makers, developers and "
 "designers."
 msgstr ""
 
-#: ./CHANGELOG.md:block 34 (unordered list)
+#: ./CHANGELOG.md:block 38 (unordered list)
 msgid "Add Felix Faassen and Arnout Engelen to authors."
 msgstr ""
 
-#: ./CHANGELOG.md:block 35 (header)
+#: ./CHANGELOG.md:block 39 (header)
 msgid "Version 0.1.4"
 msgstr ""
 
-#: ./CHANGELOG.md:block 36 (paragraph)
+#: ./CHANGELOG.md:block 40 (paragraph)
 msgid ""
 "November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
 "fixes."
 msgstr ""
 
-#: ./CHANGELOG.md:block 37 (unordered list)
+#: ./CHANGELOG.md:block 41 (unordered list)
 msgid "Linked License.md file."
 msgstr ""
 
-#: ./CHANGELOG.md:block 37 (unordered list)
+#: ./CHANGELOG.md:block 41 (unordered list)
 msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
 msgstr ""
 
-#: ./CHANGELOG.md:block 37 (unordered list)
+#: ./CHANGELOG.md:block 41 (unordered list)
 msgid "Made punctuation more consistent, especially for bullet lists."
 msgstr ""
 
-#: ./CHANGELOG.md:block 37 (unordered list)
+#: ./CHANGELOG.md:block 41 (unordered list)
 msgid "Made some minor changes to text for clarity."
 msgstr ""
 
-#: ./CHANGELOG.md:block 38 (header)
+#: ./CHANGELOG.md:block 42 (header)
 msgid "Version 0.1.3"
 msgstr ""
 
-#: ./CHANGELOG.md:block 39 (paragraph)
+#: ./CHANGELOG.md:block 43 (paragraph)
 msgid ""
 "October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
 " the autumn cleaning"
 msgstr ""
 
-#: ./CHANGELOG.md:block 40 (unordered list)
+#: ./CHANGELOG.md:block 44 (unordered list)
 msgid "Renamed continuous delivery to continuous integration."
 msgstr ""
 
-#: ./CHANGELOG.md:block 40 (unordered list)
+#: ./CHANGELOG.md:block 44 (unordered list)
 msgid "Referencing accessibility guidelines in the language standard."
 msgstr ""
 
-#: ./CHANGELOG.md:block 40 (unordered list)
+#: ./CHANGELOG.md:block 44 (unordered list)
 msgid "A bunch of style and consistency fixes."
 msgstr ""
 
-#: ./CHANGELOG.md:block 41 (header)
+#: ./CHANGELOG.md:block 45 (header)
 msgid "Version 0.1.2"
 msgstr ""
 
-#: ./CHANGELOG.md:block 42 (paragraph)
+#: ./CHANGELOG.md:block 46 (paragraph)
 msgid ""
 "August 22th 2019: 🌠 the third draft focuses on better text and takes "
 "community input"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "With some great new contributors comes a fresh author list."
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "All links are now HTTPS."
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "General proofreading, wording clarifications, and smashed typos."
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Updated criteria:"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Requirement for reuse in different contexts"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Recommendation for explicit versioning"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Recommendation for multi party development"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Recommendation for license headers in files"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Recommendation for vulnerability reporting"
 msgstr ""
 
-#: ./CHANGELOG.md:block 43 (unordered list)
+#: ./CHANGELOG.md:block 47 (unordered list)
 msgid "Recommendation for explicit documentation of governance"
 msgstr ""
 
-#: ./CHANGELOG.md:block 44 (header)
+#: ./CHANGELOG.md:block 48 (header)
 msgid "Version 0.1.1"
 msgstr ""
 
-#: ./CHANGELOG.md:block 45 (paragraph)
+#: ./CHANGELOG.md:block 49 (paragraph)
 msgid ""
 "May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
 "lot of typos"
 msgstr ""
 
-#: ./CHANGELOG.md:block 46 (unordered list)
+#: ./CHANGELOG.md:block 50 (unordered list)
 msgid ""
 "Removed references to the Foundation for Public Code, we're going to have to"
 " change the name in becoming an association."
 msgstr ""
 
-#: ./CHANGELOG.md:block 46 (unordered list)
+#: ./CHANGELOG.md:block 50 (unordered list)
 msgid "Updated the introduction."
 msgstr ""
 
-#: ./CHANGELOG.md:block 46 (unordered list)
+#: ./CHANGELOG.md:block 50 (unordered list)
 msgid "Updated the glossary."
 msgstr ""
 
-#: ./CHANGELOG.md:block 46 (unordered list)
+#: ./CHANGELOG.md:block 50 (unordered list)
 msgid "Added the code of conduct."
 msgstr ""
 
-#: ./CHANGELOG.md:block 46 (unordered list)
+#: ./CHANGELOG.md:block 50 (unordered list)
 msgid "We've recommended using the publiccode.yml standard for easier reuse."
 msgstr ""
 
-#: ./CHANGELOG.md:block 47 (header)
+#: ./CHANGELOG.md:block 51 (header)
 msgid "Version 0.1.0"
 msgstr ""
 
-#: ./CHANGELOG.md:block 48 (paragraph)
+#: ./CHANGELOG.md:block 52 (paragraph)
 msgid ""
 "April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
 "snazzy new ideas in it"
 msgstr ""
 
-#: ./CHANGELOG.md:block 49 (unordered list)
+#: ./CHANGELOG.md:block 53 (unordered list)
 msgid "14 criteria with their requirements and how to operationalize them."
 msgstr ""
 
-#: ./CHANGELOG.md:block 49 (unordered list)
+#: ./CHANGELOG.md:block 53 (unordered list)
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
 msgstr ""
 
-#: ./CHANGELOG.md:block 50 (paragraph)
+#: ./CHANGELOG.md:block 54 (paragraph)
 msgid ""
 "This first version was produced together with the Amsterdam University of "
 "Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
@@ -1353,9 +1414,11 @@ msgstr ""
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
-"![version 0.7.0](assets/version-badge.svg) [![License: "
+"![version 0.7.1](assets/version-badge.svg) [![License: "
 "CC0-1.0](https://img.shields.io/badge/License-"
-"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/) "
+"[![Standard commitment](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
 msgstr ""
 
 #: ./README.md:block 5 (paragraph)
@@ -1389,11 +1452,14 @@ msgstr ""
 #: ./README.md:block 8 (paragraph)
 msgid ""
 "If you want to apply the Standard for Public Code to your codebase, just go "
-"ahead, it's an open standard and free for anyone to use. To see how ready "
-"your codebase is, you can do a quick [eligibility self "
-"assessment](https://publiccodenet.github.io/assessment-eligibility) that "
-"will give you a rough idea of how much work you may need to do to meet all "
-"criteria."
+"ahead, it's an open standard and free for anyone to use. If you wish to "
+"advertise the codebase community's aspiration to meet the criteria of the "
+"Standard for Public Code, link the documentation of this commitment from the"
+" [standard-for-public-code-commitment badge](assets/standard-for-public-"
+"code-commitment.svg). To see how ready your codebase is, you can do a quick "
+"[eligibility self assessment](https://publiccodenet.github.io/assessment-"
+"eligibility) that will give you a rough idea of how much work you may need "
+"to do to meet all criteria."
 msgstr ""
 
 #: ./README.md:block 9 (paragraph)
@@ -4370,24 +4436,15 @@ msgid "Update the new release"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid ""
-"Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Update releaseDate in `publiccode.yml`"
+msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
+msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
+msgid "Update [`roadmap.md`](roadmap.md)"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4402,8 +4459,8 @@ msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
-"update `docs/standard-for-public-code.md` with the new text from the review "
-"template, updating any status changes as a result"
+"update `docs/standard-for-public-code.html` with the new text from the "
+"review template, updating any status changes as a result"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4437,7 +4494,9 @@ msgid "If needed, commit fixes and repeat extra pass"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid "Push branch, open a pull request to the 'main' branch"
+msgid ""
+"Push branch, compare with 'main' branch, i.e.: "
+"`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4465,20 +4524,12 @@ msgstr ""
 msgid "Run the to-archive-org.sh script"
 msgstr ""
 
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Once reviews are complete, merge to 'main'"
-msgstr ""
-
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create GitHub release with the release notes and version number"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid "Switch to the 'main' branch, `git pull` and `git status`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "`git tag $MAJOR.$MINOR.$PATCH`"
+msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4486,31 +4537,7 @@ msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
-msgid "Trigger a rebuild of gh-pages"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Open a pull request from this branch to `main`"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Approve and merge PR (containing empty commit)"
-msgstr ""
-
-#: ./docs/releasing.md:block 3 (ordered list)
-msgid "Update 'develop' with a merge from 'main'"
+msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
 msgstr ""
 
 #: ./docs/releasing.md:block 3 (ordered list)
@@ -4560,18 +4587,20 @@ msgstr ""
 msgid "As far as possible, make the standard Standard-compliant"
 msgstr ""
 
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "Certification badges"
+msgstr ""
+
 #: ./docs/roadmap.md:block 8 (header)
 msgid "Near term"
 msgstr ""
 
 #: ./docs/roadmap.md:block 9 (unordered list)
-msgid "Separate executive summary"
+msgid "Separate executive summary (issue #302)"
 msgstr ""
 
 #: ./docs/roadmap.md:block 9 (unordered list)
-msgid ""
-"Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
-" issue #208"
+msgid "Physical paper checklist"
 msgstr ""
 
 #: ./docs/roadmap.md:block 9 (unordered list)
@@ -4582,20 +4611,12 @@ msgstr ""
 msgid "Longer term"
 msgstr ""
 
-#: ./docs/roadmap.md:block 11 (unordered list)
-msgid "Certification badges"
-msgstr ""
-
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid ""
 "Add to README and index.md information (and eventually statistics) on "
 "adoption and use (issue #438)"
 msgstr ""
 
-#: ./docs/roadmap.md:block 11 (unordered list)
-msgid "Physical paper checklist"
-msgstr ""
-
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Becoming validated by multiple codebases"
 msgstr ""
@@ -5409,10 +5430,8 @@ msgstr ""
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
-"[Standard criteria "
-"checklist](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
-"template.html) used by Foundation for Public Code stewards for codebase "
-"review"
+"[Standard criteria checklist](/docs/review-template.html) used by Foundation"
+" for Public Code stewards for codebase review"
 msgstr ""
 
 #: ./readers-guide.md:block 3 (header)

From b74b732a523babf3382570d2a73dbe2ee96f951a Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Tue, 29 Aug 2023 11:53:36 +0800
Subject: [PATCH 41/71] update: zh/messages.po by 0.7.1

---
 locales/zh_Hant/LC_MESSAGES/messages.po | 1180 ++++++++++-------------
 1 file changed, 507 insertions(+), 673 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 0b97e01e..c24ed681 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -5,8 +5,7 @@ msgstr ""
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
 "PO-Revision-Date: 2023-08-28 10:25+0000\n"
 "Last-Translator: Wilt <interpreter.wilt@gmail.com>\n"
-"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
-"standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
+"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -26,8 +25,8 @@ msgid ""
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
 "SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
-"publiccode.net/AUTHORS"
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
 
 #: ./404.md:block 3 (header)
 msgid ""
@@ -67,8 +66,8 @@ msgid ""
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
 "SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), https://standard."
-"publiccode.net/AUTHORS"
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
 
 #: ./AUTHORS.md:block 3 (header)
 msgid "Authors"
@@ -156,8 +155,8 @@ msgid ""
 "(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
 "Creative Industries, Lectorate of Play & Civic Media"
 msgstr ""
-"Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas."
-"com/)，數位媒體與創意產業學院劇場與公民媒體系講師"
+"Martijn de Waal，[阿姆斯特丹應用科技大學 "
+"(AUAS)](https://www.amsterdamuas.com/)，數位媒體與創意產業學院劇場與公民媒體系講師"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Matti Schneider"
@@ -253,8 +252,7 @@ msgstr "原本專注在貢獻內容是否符合標準，現在應該專注在貢
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr "許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到"
-"。"
+msgstr "許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
@@ -316,8 +314,7 @@ msgstr "已重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。
 msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
-msgstr "已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹"
-"。"
+msgstr "已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -415,8 +412,7 @@ msgstr "已變更代碼庫名稱規定，用一般英文更容易搜尋到代碼
 msgid ""
 "Moved requirement about testing the code by using examples to Use continuous"
 " integration from Document the code."
-msgstr "已變更使用範例測試程式碼的規定，改為使用「Document the "
-"code」的範例來持續整合測試。"
+msgstr "已變更使用範例測試程式碼的規定，改為使用「Document the code」的範例來持續整合測試。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
@@ -496,8 +492,8 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
-"已將範例移動到[社群實施指南](https://publiccodenet.github.io/"
-"community-implementation-guide-standard/)。"
+"已將範例移動到[社群實施指南](https://publiccodenet.github.io/community-implementation-"
+"guide-standard/)。"
 
 #: ./CHANGELOG.md:block 17 (header)
 msgid "Version 0.4.0"
@@ -534,15 +530,13 @@ msgstr "在開放授權的定義中，加入 OSI 與 FSF 認證的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr "重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定"
-"更明確。"
+msgstr "重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "已表明 The Standard for Public Code "
-"標準在適用時應該符合自身規定，且已新增評估。"
+msgstr "已表明 The Standard for Public Code 標準在適用時應該符合自身規定，且已新增評估。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
@@ -622,8 +616,7 @@ msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
-msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必"
-"須紀錄貢獻的期望，專注在單一議題上。"
+msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必須紀錄貢獻的期望，專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
@@ -652,8 +645,7 @@ msgid ""
 "Relax the criterion Use plain English by adding a new requirement allows "
 "bundled policy not available in English to have an accompanying summary in "
 "English instead of translating the full text."
-msgstr "放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入"
-"英文版摘要，不用翻譯全文。"
+msgstr "放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入英文版摘要，不用翻譯全文。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -677,8 +669,7 @@ msgstr "強調「編寫可重複使用與移植的程式碼」解決方案部分
 msgid ""
 "Expand guidance to Developers and designers in Create reusable and portable "
 "code about deploying to proprietary platforms."
-msgstr "將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到"
-"不同專屬平台的內容。"
+msgstr "將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到不同專屬平台的內容。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -692,8 +683,9 @@ msgid ""
 "make [community translations](https://github.com/publiccodenet/community-"
 "translations-standard) easier."
 msgstr ""
-"變更拉取請求流程圖，從 BPMN 改用 Mermaid，讓[社群翻譯](https://github.com/"
-"publiccodenet/community-translations-standard)更容易。"
+"變更拉取請求流程圖，從 BPMN 改用 "
+"Mermaid，讓[社群翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)更容易。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added Maurice Hendriks to AUTHORS."
@@ -1049,8 +1041,7 @@ msgstr "14個標準、其規定以及實施方式。"
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
-msgstr "清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code "
-"會如何使用此標準。"
+msgstr "清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code 會如何使用此標準。"
 
 #: ./CHANGELOG.md:block 50 (paragraph)
 msgid ""
@@ -1058,8 +1049,8 @@ msgid ""
 "Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
 "Public Code! project](https://smartcities.publiccode.net/)."
 msgstr ""
-"第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於["
-"Smart Cities? Public Code! 專案](https://smartcities.publiccode.net/)。"
+"第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於[Smart Cities? Public Code! "
+"專案](https://smartcities.publiccode.net/)。"
 
 #: ./CODE_OF_CONDUCT.md:block 1 (header)
 msgid "Code of Conduct"
@@ -1071,8 +1062,7 @@ msgid ""
 "behavioral codes yet some individuals are not. This document expresses "
 "expectations of all community members and all interactions regardless of "
 "communication channel."
-msgstr "社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基"
-"金會對所有社群成員以及互動的期望，不論透過何種溝通管道。"
+msgstr "社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基金會對所有社群成員以及互動的期望，不論透過何種溝通管道。"
 
 #: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
 msgid "Be here to collaborate."
@@ -1105,8 +1095,7 @@ msgid ""
 "possible. Thus we appreciate your input, enjoy feedback and welcome "
 "improvements to this project and are very open to collaboration."
 msgstr ""
-"我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因"
-"此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。"
+"我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。"
 
 #: ./CONTRIBUTING.md:block 5 (paragraph)
 msgid ""
@@ -1114,9 +1103,8 @@ msgid ""
 "with GitHub, you can email use your feedback at "
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
-"我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，"
-"歡迎將意見用電子郵件傳送到 [info@publiccode.net](mailto:info@publiccode."
-"net)。"
+"我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，歡迎將意見用電子郵件傳送到 "
+"[info@publiccode.net](mailto:info@publiccode.net)。"
 
 #: ./CONTRIBUTING.md:block 6 (header)
 msgid "Problems, suggestions and questions in issues"
@@ -1132,11 +1120,11 @@ msgid ""
 "Issues for the Standard for Public "
 "Code](https://github.com/publiccodenet/standard/issues)."
 msgstr ""
-"[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以"
-"及發問，幫助推動本開發案。您可以到[GitHub 的The Standard for Public Code "
-"議題](https://github.com/publiccodenet/standard/issues)頁面中，為此專案[在 "
-"GitHub 上建立議題](https://docs.github.com/en/issues/"
-"tracking-your-work-with-issues/creating-an-issue)。"
+"[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以及發問，幫助推動本開發案。您可以到[GitHub "
+"的The Standard for Public Code "
+"議題](https://github.com/publiccodenet/standard/issues)頁面中，為此專案[在 GitHub "
+"上建立議題](https://docs.github.com/en/issues/tracking-your-work-with-"
+"issues/creating-an-issue)。"
 
 #: ./CONTRIBUTING.md:block 8 (paragraph)
 msgid ""
@@ -1145,9 +1133,7 @@ msgid ""
 " and send an email to "
 "[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
 msgstr ""
-"或者加入[郵寄清單](https://lists.publiccode.net/mailman/postorius/lists/"
-"standard.lists.publiccode.net/)並且傳送電子郵件到[standard@lists.publiccode."
-"net](mailto:standard@lists.publiccode.net)。"
+"或者加入[郵寄清單](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)並且傳送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。"
 
 #: ./CONTRIBUTING.md:block 9 (paragraph)
 msgid ""
@@ -1173,9 +1159,9 @@ msgid ""
 "Skills](https://skills.github.com/) on working with GitHub and working with "
 "MarkDown, the syntax this project's documentation is in."
 msgstr ""
-"若您從未使用過 GitHub，歡迎先[認識 GitHub flow](https://docs.github.com/en/"
-"get-started/quickstart/github-flow)，或是參加[GitHub Skills](https://skills."
-"github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 "
+"若您從未使用過 GitHub，歡迎先[認識 GitHub flow](https://docs.github.com/en/get-"
+"started/quickstart/github-flow)，或是參加[GitHub "
+"Skills](https://skills.github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 "
 "MarkDown（本專案註解所使用的語法）。"
 
 #: ./CONTRIBUTING.md:block 13 (paragraph)
@@ -1185,8 +1171,7 @@ msgid ""
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
 msgstr ""
-"本專案獲得 Creative CC Zero v1.0 Universal "
-"授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。"
+"本專案獲得 Creative CC Zero v1.0 Universal 授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。"
 
 #: ./CONTRIBUTING.md:block 14 (header)
 msgid "1. Make your changes"
@@ -1202,10 +1187,9 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
-"貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public "
-"Code 當中列出的標準。審查人員會確保貢獻符合[公共程式的價值](foreword.md"
-"#values-of-public-code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-"
-"follow)且與整體專案有連貫。"
+"貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public Code "
+"當中列出的標準。審查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-"
+"code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-follow)且與整體專案有連貫。"
 
 #: ./CONTRIBUTING.md:block 16 (paragraph)
 msgid ""
@@ -1214,9 +1198,8 @@ msgid ""
 "you've forked this repository, please make sure to create a feature branch "
 "following the GitFlow model."
 msgstr ""
-"本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/"
-"a-successful-git-branching-model/)。當您複製了此存放庫，請務必依照 GitFlow "
-"模型建立功能分支。"
+"本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-"
+"model/)。當您複製了此存放庫，請務必依照 GitFlow 模型建立功能分支。"
 
 #: ./CONTRIBUTING.md:block 17 (paragraph)
 msgid ""
@@ -1230,20 +1213,16 @@ msgid ""
 "commit message, this will enable everyone to be informed of your choices in "
 "the future."
 msgstr ""
-"將您變更內容加入到提交版本[並且附上說明](https://robots.thoughtbot.com/5"
-"-useful-tips-for-a-better-commit-message)。如果需要不只一種變更，將相關變更分"
-"類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不"
-"同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格式。像是「svg」格式就"
-"勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選"
-"擇。"
+"將您變更內容加入到提交版本[並且附上說明](https://robots.thoughtbot.com/5-useful-tips-for-a-"
+"better-commit-"
+"message)。如果需要不只一種變更，將相關變更分類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格式。像是「svg」格式就勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選擇。"
 
 #: ./CONTRIBUTING.md:block 18 (paragraph)
 msgid ""
 "If you are adding code, make sure you've added and updated the relevant "
 "documentation and tests before you submit your pull request. Make sure to "
 "write tests that show the behavior of the newly added or changed code."
-msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請"
-"務必用文字描述新增或修改後的程式碼的作用。"
+msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請務必用文字描述新增或修改後的程式碼的作用。"
 
 #: ./CONTRIBUTING.md:block 19 (header)
 msgid "Applicable policy"
@@ -1271,10 +1250,7 @@ msgid ""
 "release](docs/releasing.md)."
 msgstr ""
 "The Standard for Public Code 目標是[使用白話的英語](criteria/use-plain-"
-"english.md)，拼字採用美式英文。文字基本上以每句一行為原則，沒有換行，讓「diff"
-"」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與"
-"排版。我們的審查流程會修正這一部分，也會另外再次檢查品質才[推出新版本](docs/"
-"releasing.md)。"
+"english.md)，拼字採用美式英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1285,8 +1261,7 @@ msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr "這些是 The Standard for Public Code "
-"所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。"
+msgstr "這些是 The Standard for Public Code 所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
@@ -1312,9 +1287,7 @@ msgid ""
 "issue where possible. In some cases a single set of changes may address "
 "multiple issues, in which case be sure to list all issue numbers fixed."
 msgstr ""
-"提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建"
-"議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議"
-"題編號。"
+"提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議題編號。"
 
 #: ./CONTRIBUTING.md:block 28 (header)
 msgid "3. Improve"
@@ -1326,8 +1299,7 @@ msgid ""
 "Code has committed to make sure that maintainers are available to review "
 "contributions with an aim to provide feedback within two business days."
 msgstr ""
-"所有貢獻都必須接受審查。The Foundation for Public Code "
-"承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
+"所有貢獻都必須接受審查。The Foundation for Public Code 承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
 
 #: ./CONTRIBUTING.md:block 30 (paragraph)
 msgid ""
@@ -1337,9 +1309,7 @@ msgid ""
 "feedback. If this is the case the reviewing maintainer will help you improve"
 " your documentation and code."
 msgstr ""
-"維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其"
-"他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人"
-"員，將負責協助改善您的註解與程式碼。"
+"維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人員，將負責協助改善您的註解與程式碼。"
 
 #: ./CONTRIBUTING.md:block 31 (paragraph)
 msgid "If your documentation and code have passed human review, it is merged."
@@ -1359,8 +1329,7 @@ msgstr "您的構思、註解與程式碼將成為本專案的一部份。您就
 msgid ""
 "In fact, feel free to open a pull request to add your name to the "
 "[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
-msgstr "歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS."
-"md)檔案中，您的名字可以永遠留在本專案中。"
+msgstr "歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS.md)檔案中，您的名字可以永遠留在本專案中。"
 
 #: ./CONTRIBUTING.md:block 35 (header)
 msgid "Translations in other languages"
@@ -1372,9 +1341,9 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
-"The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增["
-"The Standard for Public Code 社群翻譯](https://github.com/publiccodenet/"
-"community-translations-standard)。"
+"The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增[The Standard for Public "
+"Code 社群翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
@@ -1385,8 +1354,7 @@ msgid ""
 "We have dedicated documentation for creating [new "
 "releases](/docs/releasing.md) and [ordering printed "
 "standards](/docs/printing.md)."
-msgstr "建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing."
-"md)有專用註解。"
+msgstr "建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing.md)有專用註解。"
 
 #: ./CONTRIBUTING.md:block 39 (paragraph)
 msgid ""
@@ -1401,8 +1369,8 @@ msgid ""
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
 "SPDX-FileCopyrightText: 2019-2022 The Foundation for Public "
-"Code[info@publiccode.net](mailto:info@publiccode.net), https://standard."
-"publiccode.net/AUTHORS"
+"Code[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
 
 #: ./GOVERNANCE.md:block 3 (header)
 msgid "Governance"
@@ -1414,8 +1382,8 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"此標準是[The Foundation for Public Code](https://publiccode.net/"
-")代碼庫管理的核心。我們依照本文件來判斷代碼庫是否已經準備好讓社群參與開發。"
+"此標準是[The Foundation for Public "
+"Code](https://publiccode.net/)代碼庫管理的核心。我們依照本文件來判斷代碼庫是否已經準備好讓社群參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
@@ -1432,8 +1400,8 @@ msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
 msgstr ""
-"由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，"
-"我們也要求遵守 The Standard for Public Code 中最嚴苛的標準。"
+"由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守 The Standard for"
+" Public Code 中最嚴苛的標準。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1441,8 +1409,7 @@ msgid ""
 " opportunity to work together to improve our methods and the Standard. We "
 "may not accept all changes, but we will explain our logic."
 msgstr ""
-"我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，"
-"改善我們的方法與 The Standard for Public "
+"我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，改善我們的方法與 The Standard for Public "
 "Code。我們可能不會接受貢獻者提出的所有修改，但我們會解釋背後的邏輯。"
 
 #: ./README.md:block 1 (header)
@@ -1456,9 +1423,8 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"The Standard for Public Code 提供公共組織一個準備開源解決方案的模型，讓他們與"
-"其他地方相似的公共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供"
-"應商的指引。"
+"The Standard for Public Code "
+"提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供應商的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1466,9 +1432,9 @@ msgid ""
 "CC0-1.0](https://img.shields.io/badge/License-"
 "CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
 msgstr ""
-"![0.7.0版](assets/version-badge.svg) [![授權：CC0-1.0](https://img.shields."
-"io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/"
-"publicdomain/zero/1.0/)"
+"![0.7.0版](assets/version-badge.svg) "
+"[![授權：CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
 
 #: ./README.md:block 5 (paragraph)
 msgid ""
@@ -1486,26 +1452,26 @@ msgid ""
 "develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
 "check/standard.publiccode.net-develop-url-check-look.json)"
 msgstr ""
-"[![頁面-建造-部署](https://github.com/publiccodenet/standard/actions/"
-"workflows/pages/pages-build-deployment/badge.svg)](https://github.com/"
-"publiccodenet/standard/actions/workflows/pages/pages-build-deployment) "
-"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test."
-"yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/"
-"test.yml) [![標準主徽章](https://publiccodenet.github.io/"
-"publiccodenet-url-check/badges/standard.publiccode.net."
-"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
-"publiccode.net-url-check-look.json) [![標準開發徽章](https://publiccodenet."
-"github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop."
-"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
-"publiccode.net-develop-url-check-look.json)"
+"[![頁面-建造-"
+"部署](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-"
+"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-deployment) "
+"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
+" [![標準主徽章](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
+"url-check/standard.publiccode.net-url-check-look.json) "
+"[![標準開發徽章](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net-"
+"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
+"check/standard.publiccode.net-develop-url-check-look.json)"
 
 #: ./README.md:block 6 (paragraph)
 msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr "The Standard for Public Code 目前為草稿階段。我們正在準備推出1."
-"0版，目前正在幾個代碼庫上測試。"
+msgstr "The Standard for Public Code 目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
@@ -1520,10 +1486,10 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將 The Standard for Public Code 套用在您的代碼庫，不需要任何猶豫，"
-"因為 The Standard for Public Code 是開放性標準，任何人都可以免費使用。若要瞭"
-"解您代碼庫是否就緒，可以進行[資格自我評估](https://publiccodenet.github.io/"
-"assessment-eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
+"若您想要將 The Standard for Public Code 套用在您的代碼庫，不需要任何猶豫，因為 The Standard for "
+"Public Code "
+"是開放性標準，任何人都可以免費使用。若要瞭解您代碼庫是否就緒，可以進行[資格自我評估](https://publiccodenet.github.io/assessment-"
+"eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
 
 #: ./README.md:block 9 (paragraph)
 msgid ""
@@ -1534,11 +1500,9 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
-"將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。"
-"若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與"
-"您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指南](https://publiccode"
-"net.github.io/community-implementation-guide-standard/"
-")，當中包括範例與其他訣竅。"
+"將 The Standard for Public Code "
+"套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指南](https://publiccodenet.github.io/community-"
+"implementation-guide-standard/)，當中包括範例與其他訣竅。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
@@ -1546,9 +1510,8 @@ msgid ""
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
 msgstr ""
-"若新版的 The Standard for Public Code 有突破性的修改，The Foundation for "
-"Public Code 的代碼庫管理人員會幫助The Standard for Public Code "
-"使用者彌補不同版之間的差異。"
+"若新版的 The Standard for Public Code 有突破性的修改，The Foundation for Public Code "
+"的代碼庫管理人員會幫助The Standard for Public Code 使用者彌補不同版之間的差異。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1558,10 +1521,8 @@ msgid ""
 "[assessment](https://about.publiccode.net/activities/codebase-"
 "stewardship/lifecycle-diagram.html#assessment)."
 msgstr ""
-"若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與"
-"我們聯繫：[info@publiccode.net](mailto:info@publiccode."
-"net)，並開始正式[評估](https://about.publiccode.net/activities/"
-"codebase-stewardship/lifecycle-diagram.html#assessment)。"
+"若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與我們聯繫：[info@publiccode.net](mailto:info@publiccode.net)，並開始正式[評估](https://about.publiccode.net/activities/codebase-"
+"stewardship/lifecycle-diagram.html#assessment)。"
 
 #: ./README.md:block 12 (header)
 msgid "Request for contributions"
@@ -1573,16 +1534,15 @@ msgid ""
 "legible, accountable, accessible and sustainable. This means we need a new "
 "way of designing, developing and procuring both the source code and policy "
 "documentation."
-msgstr "我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特"
-"性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。"
+msgstr ""
+"我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。"
 
 #: ./README.md:block 14 (paragraph)
 msgid ""
 "This standard sets a quality level for codebases that meets the needs of "
 "public organizations, institutions and administrations as well as other "
 "critical infrastructural services."
-msgstr "本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需"
-"求。"
+msgstr "本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需求。"
 
 #: ./README.md:block 15 (paragraph)
 msgid ""
@@ -1590,8 +1550,8 @@ msgid ""
 "[standard.publiccode.net](https://standard.publiccode.net/). See "
 "[`index.md`](index.md) for an overview of all content."
 msgstr ""
-"The Standard for Public Code 就在[standard.publiccode.net](https://standard."
-"publiccode.net/)。內容概覽請參閱[`index.md`](index.md)。"
+"The Standard for Public Code "
+"就在[standard.publiccode.net](https://standard.publiccode.net/)。內容概覽請參閱[`index.md`](index.md)。"
 
 #: ./README.md:block 16 (paragraph)
 msgid ""
@@ -1600,9 +1560,9 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
-"[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 "
-"The Standard for Public Code ](https://img.youtube.com/vi/QWt6vB-cipE/"
-"mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+"[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 The Standard for "
+"Public Code ](https://img.youtube.com/vi/QWt6vB-"
+"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
 msgid ""
@@ -1610,8 +1570,8 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
-"[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v"
-"=QWt6vB-cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube."
+"[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v=QWt6vB-"
+"cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube."
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
@@ -1635,18 +1595,14 @@ msgid ""
 " described how we govern the standard in the [governance "
 "statement](GOVERNANCE.md)."
 msgstr ""
-"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及"
-"協助開發。😊若要開始，請先參閱我們的[貢獻者指南](CONTRIBUTING.md)。由於這是相"
-"當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE."
-"md)提到我們管理該標準的方式。"
+"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及協助開發。😊若要開始，請先參閱我們的[貢獻者指南](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE.md)提到我們管理該標準的方式。"
 
 #: ./README.md:block 21 (paragraph)
 msgid ""
 "Please note that this project is released with a [code of "
 "conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
 "abide by its terms. Please be lovely to all other community members."
-msgstr "請注意，本專案有其[行為準則](CODE_OF_CONDUCT."
-"md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。"
+msgstr "請注意，本專案有其[行為準則](CODE_OF_CONDUCT.md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。"
 
 #: ./README.md:block 22 (header)
 msgid "Preview, build and deploy"
@@ -1659,24 +1615,22 @@ msgid ""
 "with [GitHub pages](https://pages.github.com) and "
 "[Jekyll](https://jekyllrb.com/)."
 msgstr ""
-"存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode."
-"net/)的靜態網站，使用的是[GitHub pages](https://pages.github."
-"com)與[Jekyll](https://jekyllrb.com/)。"
+"存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode.net/)的靜態網站，使用的是[GitHub"
+" pages](https://pages.github.com)與[Jekyll](https://jekyllrb.com/)。"
 
 #: ./README.md:block 24 (paragraph)
 msgid ""
 "The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
 "means you will need ruby and ruby-bundler installed, for example:"
 msgstr ""
-"當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構"
-"，換句話說您需要安裝ruby與ruby-bundler，像是："
+"當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構，換句話說您需要安裝ruby與ruby-bundler，像是："
 
 #: ./README.md:block 26 (paragraph)
 msgid ""
 "If `ruby` and `bundle` are installed, one can run `bundle install` after "
 "which the site can be rendered with the `script/serve.sh` script."
-msgstr "如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` "
-"腳本來渲染網站。"
+msgstr ""
+"如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` 腳本來渲染網站。"
 
 #: ./README.md:block 27 (header)
 msgid "Testing"
@@ -1693,8 +1647,7 @@ msgid ""
 "See the scripts in the "
 "[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
 msgstr ""
-"所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/"
-"script)檔案夾。"
+"所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/script)檔案夾。"
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
@@ -1707,9 +1660,9 @@ msgid ""
 "[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
 "used to transform PDFs into `.epub`."
 msgstr ""
-"除了 Jekyll 以外，要生成 PDF 檔案也需要仰賴[Weasyprint](https://weasyprint."
-"org/)以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)"
-"可以將 PDF 轉換成`.epub`檔案。"
+"除了 Jekyll 以外，要生成 PDF "
+"檔案也需要仰賴[Weasyprint](https://weasyprint.org/)以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)可以將"
+" PDF 轉換成`.epub`檔案。"
 
 #: ./README.md:block 32 (paragraph)
 msgid ""
@@ -1721,8 +1674,7 @@ msgstr "若要生成這些種類的檔案，則需要安裝類似下列的依附
 msgid ""
 "The file `standard-print.html` can be converted to a nice looking PDF, along"
 " with the other release files, using:"
-msgstr "使用以下腳本，可以將 `standard-print.html` "
-"檔案以及其他的版本檔案轉換成美觀的 PDF："
+msgstr "使用以下腳本，可以將 `standard-print.html` 檔案以及其他的版本檔案轉換成美觀的 PDF："
 
 #: ./README.md:block 36 (header)
 msgid "License"
@@ -1739,9 +1691,8 @@ msgid ""
 "it. If you contribute you also grant these rights to others. You can read "
 "more about how to help in the [contributing guide](CONTRIBUTING.md)."
 msgstr ""
-"The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解"
-"與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權"
-"利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
+"The Standard for Public Code 採用 CC 0 "
+"[授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
 msgid "order: 2 redirect_from:"
@@ -1762,9 +1713,8 @@ msgid ""
 "anyone to implement the codebase in their local context or contribute to the"
 " further development of the [codebase](../glossary.md#codebase)."
 msgstr ""
-"使用[原始碼](../glossary.md#source-code)以及[政策](../glossary.md#policy)註解"
-"，提供基石給想在當地脈絡使用代碼庫的人或是想要對[代碼庫](../glossary."
-"md#codebase)進一步發展有所貢獻的人。"
+"使用[原始碼](../glossary.md#source-"
+"code)以及[政策](../glossary.md#policy)註解，提供基石給想在當地脈絡使用代碼庫的人或是想要對[代碼庫](../glossary.md#codebase)進一步發展有所貢獻的人。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
 msgid ""
@@ -1779,8 +1729,7 @@ msgid ""
 "organization needs to understand what process changes it must choose to make"
 " or how to contribute additional configurability to the existing solution in"
 " order to adapt it to the new context."
-msgstr "組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在"
-"現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。"
+msgstr "組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
 msgid "Requirements"
@@ -1794,8 +1743,7 @@ msgstr "代碼庫「必須（Must）」包含做為原始碼基礎的政策。"
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr "若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵"
-"測的原始碼除外）。"
+msgstr "若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵測的原始碼除外）。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
@@ -1806,8 +1754,7 @@ msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
 msgstr ""
-"[持續整合](../glossary.md#continuous-integration) "
-"測試「應該（Should）」驗證原始碼與政策是否有一致執行。"
+"[持續整合](../glossary.md#continuous-integration) 測試「應該（Should）」驗證原始碼與政策是否有一致執行。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
 msgid "How to test"
@@ -1854,9 +1801,7 @@ msgid ""
 "which impact the development or the deployment context of the codebase for "
 "your organization."
 msgstr ""
-"提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有"
-"英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標準，以及影響貴機構代碼"
-"庫開發或部署脈絡的組織流程。"
+"提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標準，以及影響貴機構代碼庫開發或部署脈絡的組織流程。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -1867,23 +1812,20 @@ msgid ""
 "Document policy in formats that are unambiguous and machine-readable, such "
 "as those published by the [Object Management "
 "Group](https://www.omg.org/spec/)."
-msgstr "用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/"
-")發佈的格式）來紀錄政策。"
+msgstr "用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/)發佈的格式）來紀錄政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Track policy with [the same version control](maintain-version-control.md) "
 "and documentation used to track source code."
-msgstr "利用[相同的版本控制l](maintain-version-control."
-"md)以及用來追蹤原始碼的註解，來追蹤政策。"
+msgstr "利用[相同的版本控制l](maintain-version-control.md)以及用來追蹤原始碼的註解，來追蹤政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Check in regularly to understand how the source code in the codebase has "
 "changed and whether it still matches the [intentions of the "
 "policy](document-codebase-objectives.md)."
-msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-"
-"codebase-objectives.md)。"
+msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-codebase-objectives.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1894,10 +1836,9 @@ msgid ""
 "accessibility), or human rights policies, like a public organization's "
 "commitment to equal opportunity."
 msgstr ""
-"納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-lex."
-"europa.eu/eli/reg/2016/679/oj)或是 [歐盟無障礙指令](https://ec.europa.eu/"
-"digital-single-market/en/web-"
-"accessibility)這些法律義務，或是人權政策，像是公共組織對機會平等的承諾。"
+"納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-"
+"lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟無障礙指令](https://ec.europa.eu/digital-"
+"single-market/en/web-accessibility)這些法律義務，或是人權政策，像是公共組織對機會平等的承諾。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
@@ -1945,16 +1886,14 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
 " on Wikipedia."
 msgstr ""
-"維基百科的[商業流程模型與標記法](https://en.wikipedia.org/wiki/"
-"Business_Process_Model_and_Notation)。"
+"維基百科的[商業流程模型與標記法](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
-"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/"
-"view-bpmn-quick-guide/)。"
+"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
@@ -1962,8 +1901,7 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
 "Wikipedia."
 msgstr ""
-"維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/"
-"Decision_Model_and_Notation)。"
+"維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
@@ -1984,30 +1922,27 @@ msgid ""
 "Coding in the open improves transparency, increases [source "
 "code](../glossary.md#source-code) quality, makes the source code easier to "
 "audit, and enables collaboration."
-msgstr "開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-"
-"code)品質、讓原始碼更容易稽查，並且讓協作更容易。"
+msgstr ""
+"開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽查，並且讓協作更容易。"
 
 #: ./criteria/code-in-the-open.md:block 6 (paragraph)
 msgid ""
 "Together, this creates more opportunities for citizens to understand how "
 "software and [policy](../glossary.md#policy) impact their interactions with "
 "a public organization."
-msgstr "這讓市民更能夠瞭解軟體與[政策](../glossary."
-"md#policy)如何影響他們與公共組織的互動。"
+msgstr "這讓市民更能夠瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公共組織的互動。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any policy in use (unless used for fraud detection) MUST"
 " be published and publicly accessible."
-msgstr "任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用"
-"。"
+msgstr "任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用"
-"。"
+msgstr "任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
@@ -2019,16 +1954,14 @@ msgstr "代碼庫「不允許」包含使用者、使用者機構或第三方的
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr "目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈"
-"。"
+msgstr "目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "Documenting which source code or policy underpins any specific interaction "
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
-msgstr "可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-"
-"public)與任何組織互動的原始碼或政策。"
+msgstr "可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-public)與任何組織互動的原始碼或政策。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
@@ -2036,8 +1969,7 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr "確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須"
-"任何形式的驗證或認證也可以看到。"
+msgstr "確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須任何形式的驗證或認證也可以看到。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
@@ -2071,8 +2003,8 @@ msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr "審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者"
-"名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
+msgstr ""
+"審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 16 (unordered list)
 msgid ""
@@ -2085,8 +2017,8 @@ msgid ""
 "[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
 " by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/"
-"12/coding-in-the-open/)》。"
+"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/12/coding-in-the-"
+"open/)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -2095,9 +2027,8 @@ msgid ""
 "guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
 "Service."
 msgstr ""
-"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/"
-"government/publications/open-source-guidance/when-code-should-be-open-or-"
-"closed)》。"
+"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/government/publications/open-"
+"source-guidance/when-code-should-be-open-or-closed)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -2106,9 +2037,8 @@ msgid ""
 "guidance/security-considerations-when-coding-in-the-open) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/"
-"government/publications/open-source-guidance/security-considerations-when-"
-"coding-in-the-open)》。"
+"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/government/publications/open-"
+"source-guidance/security-considerations-when-coding-in-the-open)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
@@ -2116,16 +2046,16 @@ msgid ""
 "manual/technology/deploying-software-regularly) by the UK Government Digital"
 " Service."
 msgstr ""
-"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/"
-"technology/deploying-software-regularly)》。"
+"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/technology/deploying-"
+"software-regularly)》。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""
 "[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
 "use-github/) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[政府數位服務團如何使用 GitHub](https://gdstechnology."
-"blog.gov.uk/2014/01/27/how-we-use-github/)》。"
+"英國政府數位服務團《[政府數位服務團如何使用 "
+"GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/)》。"
 
 #: ./criteria/document-codebase-maturity.md:block 3 (header)
 msgid ""
@@ -2147,9 +2077,7 @@ msgid ""
 "codebase has evolved is key to understanding the codebase and how to "
 "contribute to it."
 msgstr ""
-"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或"
-"為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解代碼庫的演變，才"
-"能真正認識該代碼庫並且做出貢獻。"
+"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解代碼庫的演變，才能真正認識該代碼庫並且做出貢獻。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The codebase MUST be versioned."
@@ -2165,8 +2093,7 @@ msgstr "代碼庫必須明確標示是否有已經準備好使用的版本。"
 msgid ""
 "Codebase versions that are ready to use MUST only depend on versions of "
 "other codebases that are also ready to use."
-msgstr "準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本"
-"。"
+msgstr "準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
@@ -2191,15 +2118,13 @@ msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
 msgid ""
 "Confirm that it is obvious to policy makers, managers, developers and "
 "designers whether the codebase has versions that are ready to use."
-msgstr "確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使"
-"用的版本。"
+msgstr "確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that ready to use versions of the codebase do not depend on any "
 "versions of other codebases that are not ready to use."
-msgstr "確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何"
-"版本。"
+msgstr "確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
@@ -2216,8 +2141,8 @@ msgid ""
 " code](../glossary.md#source-code) developed needs to be tested and improved"
 " before it can be put into service."
 msgstr ""
-"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 "
-"[程式碼](../glossary.md#source-code) 都必須先經過測試與改善，才能夠投入服務。"
+"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [程式碼](../glossary.md#source-code) "
+"都必須先經過測試與改善，才能夠投入服務。"
 
 #: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
 msgid ""
@@ -2230,8 +2155,7 @@ msgid ""
 "Make sure that services only rely on versions of codebases of equal or "
 "greater maturity than the service. For example, don't use a beta version of "
 "a codebase in a production service."
-msgstr "要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，"
-"正式上線的服務不要使用 beta 公測版代碼庫。"
+msgstr "要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。"
 
 #: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
 msgid ""
@@ -2257,16 +2181,15 @@ msgid ""
 "advice/build-and-improve-services/service-design-and-delivery-process) by "
 "the Australian Digital Transformation Agency."
 msgstr ""
-"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/"
-"build-and-improve-services/service-design-and-delivery-process)》。"
+"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/build-and-"
+"improve-services/service-design-and-delivery-process)》。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
 "delivery) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/"
-"agile-delivery)》。"
+"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/agile-delivery)》。"
 
 #: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
 msgid "order: 8 redirect_from:"
@@ -2288,31 +2211,26 @@ msgid ""
 "provide an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
 msgstr ""
-"清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害"
-"關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷目前或未來是否會"
-"對此代碼庫（或其模組之一）有興趣。"
+"清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷目前或未來是否會對此代碼庫（或其模組之一）有興趣。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST contain documentation of its objectives, like a mission "
 "and goal statement, that is understandable by developers and designers so "
 "that they can use or contribute to the codebase."
-msgstr "代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要"
-"能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
+msgstr "代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr "代碼庫文件應該清楚描述[政策](../glossary."
-"md#policy)目標與代碼庫目標之前的關聯。"
+msgstr "代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-"
-"public)看的代碼庫目標。"
+msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
@@ -2338,8 +2256,8 @@ msgid ""
 "supporting policy documents added to meet the [Bundle policy and source "
 "code](bundle-policy-and-source-code.md) criterion."
 msgstr ""
-"確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼"
-"要合捆](bundle-policy-and-source-code.md)的標準。"
+"確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼要合捆](bundle-policy-and-source-"
+"code.md)的標準。"
 
 #: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
 msgid ""
@@ -2359,8 +2277,8 @@ msgid ""
 "objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
 " by Marek Hajduczenia."
 msgstr ""
-"Marek Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/"
-"RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
+"Marek "
+"Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
 
 #: ./criteria/document-the-code.md:block 3 (paragraph)
 msgid "order: 9 redirect_from:"
@@ -2381,9 +2299,8 @@ msgid ""
 "essential for people to start using the [codebase](../glossary.md#codebase) "
 "and contributing to it more quickly."
 msgstr ""
-"詳細記錄的[程式碼](../glossary.md#source-code)幫助民眾瞭解該原始碼的作用與使"
-"用方式。記錄文件是幫助民眾開始使用[代碼庫](../glossary."
-"md#codebase)並且更快做出貢獻的關鍵。"
+"詳細記錄的[程式碼](../glossary.md#source-"
+"code)幫助民眾瞭解該原始碼的作用與使用方式。記錄文件是幫助民眾開始使用[代碼庫](../glossary.md#codebase)並且更快做出貢獻的關鍵。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2391,8 +2308,7 @@ msgid ""
 " well as source code, MUST be described in language clearly understandable "
 "for those that understand the purpose of the codebase."
 msgstr ""
-"代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的"
-"用語描述，讓懂代碼庫目的用途的人也能夠理解。"
+"代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2412,16 +2328,14 @@ msgid ""
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
 msgstr ""
-"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-"
-"public)和記者等廣泛的利害關係人都能清楚明白。"
+"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也"
-"應該包含測試資料集。"
+msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2434,8 +2348,7 @@ msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架"
-"構圖表示。"
+msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2454,8 +2367,7 @@ msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以"
-"清楚明白。"
+msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
@@ -2495,8 +2407,7 @@ msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated correctly, and links and images are "
 "tested."
-msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與"
-"圖片等。"
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與圖片等。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid ""
@@ -2514,8 +2425,7 @@ msgid ""
 " and source code are documented. For example, is the current documentation "
 "sufficient to persuade a manager at another public organization to use this "
 "codebase?"
-msgstr "嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的"
-"文件是否足以說服另一個公共組織的管理人員使用本代碼庫？"
+msgstr "嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的文件是否足以說服另一個公共組織的管理人員使用本代碼庫？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -2587,10 +2497,8 @@ msgid ""
 "changes in parallel and helps future developers to understand the reasons "
 "for changes."
 msgstr ""
-"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md"
-"#source-code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓"
-"您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人"
-"員針對修改變動平行作業，並幫助未來的開發人員瞭解修改的原因。"
+"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md#source-"
+"code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人員針對修改變動平行作業，並幫助未來的開發人員瞭解修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All files in the codebase MUST be version controlled."
@@ -2634,8 +2542,7 @@ msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內"
-"容有疑問時，可以與之前的貢獻者聯絡。"
+msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
@@ -2654,8 +2561,7 @@ msgid ""
 "Review the commit history, confirming that where possible all commit "
 "messages include the discussion about the change was or where to find it "
 "(with a URL)."
-msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方"
-"，包含變動內容以及連結位置（提供網址）。"
+msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid "Check if the version control system is distributed."
@@ -2684,8 +2590,7 @@ msgid ""
 "If a new version of the codebase is created because of a "
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
-msgstr "如果因為[政策](../glossary."
-"md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
+msgstr "如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid "what the policy change is,"
@@ -2699,16 +2604,14 @@ msgstr "代碼庫如何因應而改變。"
 msgid ""
 "For example, adding a new category of applicant to a codebase that manages "
 "granting permits would be considered a policy change."
-msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政"
-"策變動。"
+msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。"
 
 #: ./criteria/maintain-version-control.md:block 15 (unordered list)
 msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保"
-"改善代碼庫不會有公關風險。"
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
@@ -2744,8 +2647,8 @@ msgid ""
 "Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
 "Fogel."
 msgstr ""
-"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc"
-".html#vc-vocabulary)》。"
+"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc.html#vc-"
+"vocabulary)》。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2753,16 +2656,15 @@ msgid ""
 "manual/technology/maintaining-version-control-in-coding) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-manual/"
-"technology/maintaining-version-control-in-coding)》。"
+"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding)》。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
 "[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
 "use GitHub or refresh your skills."
 msgstr ""
-"GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 "
-"GitHub，或是重溫您的技巧。"
+"GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2786,16 +2688,14 @@ msgid ""
 " able to fix problems, add features, and address security issues of the "
 "shared [codebase](../glossary.md#codebase)."
 msgstr ""
-"若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫]("
-"../glossary.md#codebase)修復問題與新增功能。"
+"若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫](../glossary.md#codebase)修復問題與新增功能。"
 
 #: ./criteria/make-contributing-easy.md:block 6 (paragraph)
 msgid ""
 "A shared digital infrastructure makes it easier to make collaborative "
 "contributions. The less effort it takes to make contributions that are "
 "accepted by the codebase, the more likely users are to become contributors."
-msgstr "共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者"
-"越可能成為貢獻者。"
+msgstr "共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者越可能成為貢獻者。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
@@ -2807,15 +2707,13 @@ msgstr "代碼庫必須有個可以公開接受任何人建議的議題追蹤器
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在"
-"「`README`」檔案中。"
+msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄"
-"清單。"
+msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄清單。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
@@ -2858,8 +2756,7 @@ msgstr "確認有說明如何私下通報安全性問題。"
 msgid ""
 "Track [policy](../glossary.md#policy) issues in the codebase, so that a "
 "relevant external policy expert can volunteer help."
-msgstr "追蹤代碼庫中的[政策](../glossary."
-"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
+msgstr "追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
 
 #: ./criteria/make-contributing-easy.md:block 14 (unordered list)
 msgid ""
@@ -2871,8 +2768,7 @@ msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久"
-"貢獻。"
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
@@ -2890,8 +2786,7 @@ msgstr "告知管理人員您支持其他貢獻者時所需的時間與資源。
 msgid ""
 "Make sure that appropriate communication channels for asking maintainers and"
 " stakeholders questions are easy to locate, for instance in the README."
-msgstr "確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`"
-"」文件當中。"
+msgstr "確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`」文件當中。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
@@ -2905,17 +2800,16 @@ msgid ""
 "project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
 "to-your-open-source-project-1ebf) by Joel Hans."
 msgstr ""
-"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/"
-"joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-"
-"project-1ebf)》。"
+"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/joelhans/how-to-inspire-"
+"exceptional-contributions-to-your-open-source-project-1ebf)》。"
 
 #: ./criteria/make-contributing-easy.md:block 18 (unordered list)
 msgid ""
 "[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
 "benefits-of-coding-in-the-open/) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/"
-"2017/09/04/the-benefits-of-coding-in-the-open/)》。"
+"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/2017/09/04/the-benefits-"
+"of-coding-in-the-open/)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
 msgid "order: 14 redirect_from:"
@@ -2935,8 +2829,7 @@ msgid ""
 "potential new collaborators will find it. Just publishing a codebase and "
 "hoping it is found does not work, instead proactiveness is needed."
 msgstr ""
-"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到"
-"它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必須主動積極。"
+"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必須主動積極。"
 
 #: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
 msgid ""
@@ -2946,17 +2839,14 @@ msgid ""
 "the codebase easier for people to refer, cite, disambiguate and discover "
 "through third party tools."
 msgstr ""
-"有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料"
-"，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄列表之"
-"中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用"
-"、辨別、發現代碼庫。"
+"有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF "
+"自由軟體基金會的軟體目錄列表之中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或"
-"組織單位品牌名稱或抬頭等。"
+msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -2973,8 +2863,7 @@ msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理"
-"人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
+msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -2985,16 +2874,15 @@ msgstr "在搜尋引擎查找代碼庫名稱時，應該能搜尋得到代碼庫
 msgid ""
 "The codebase SHOULD be findable using a search engine by describing the "
 "problem it solves in natural language."
-msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼"
-"庫。"
+msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a unique and persistent identifier where the entry "
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
-msgstr "代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../gloss"
-"ary.md#repository)、位置、網站等。"
+msgstr ""
+"代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -3002,8 +2890,7 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
-"代碼庫應該包含機器可讀的中介資料說明，例如採用[publiccode.yml](https://github"
-".com/publiccodeyml/publiccode.yml)格式的檔案。"
+"代碼庫應該包含機器可讀的中介資料說明，例如採用[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
@@ -3022,15 +2909,13 @@ msgid ""
 "Check that the codebase name is free of acronyms and abbreviations or that "
 "the acronyms or abbreviations in the name are more universally known than "
 "the longer forms."
-msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整"
-"名稱更熟為人知。"
+msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整名稱更熟為人知。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of organizational branding, unless that"
 " organization is of the codebase community itself."
-msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員"
-"）。"
+msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員）。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3051,16 +2936,14 @@ msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by the codebase name."
-msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋"
-"結果的第一頁中。"
+msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by using natural language, for instance, using the "
 "short description."
-msgstr "檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼"
-"庫放在搜尋結果的第一頁中。"
+msgstr "檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3144,15 +3027,14 @@ msgid ""
 "Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
 "Wikidata community."
 msgstr ""
-"Wikidata 維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/"
-"Wikidata:Introduction)》。"
+"Wikidata "
+"維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
 msgid ""
 "[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
 "by the Free Software Foundation."
-msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/"
-"Main_Page)》。"
+msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。"
 
 #: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
 msgid ""
@@ -3163,11 +3045,8 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
-"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
-"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
-"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
-"分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其"
-"對應的特性要怎麼處理。"
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-"
+"principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
 msgid "order: 3 redirect_from:"
@@ -3194,9 +3073,7 @@ msgid ""
 "improve it and contribute those improvements back, leading to better "
 "quality, cheaper maintenance and higher reliability."
 msgstr ""
-"編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人"
-"員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，如"
-"此可提高品質、降低維護成本、增強可靠性。"
+"編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
 msgid ""
@@ -3206,9 +3083,7 @@ msgid ""
 " developed and used by multiple parties are more likely to benefit from a "
 "self-sustaining community."
 msgstr ""
-"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代"
-"碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從能自我運作的社群"
-"中獲益。"
+"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從能自我運作的社群中獲益。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
 msgid ""
@@ -3217,8 +3092,7 @@ msgid ""
 "[another context](../glossary.md#different-contexts) if its purpose is "
 "clearly documented."
 msgstr ""
-"以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄"
-"用途的模組，更容易在[另一種情境](../glossary.md#different-"
+"以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情境](../glossary.md#different-"
 "contexts)中重複利用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
@@ -3226,8 +3100,7 @@ msgid ""
 "Source code which does not rely on the situation-specific infrastructure of "
 "any contributor, vendor or deployment can be tested by any other "
 "contributor."
-msgstr "如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都"
-"能測試該原始碼。"
+msgstr "如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都能測試該原始碼。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3239,8 +3112,7 @@ msgstr "代碼庫必須開發成能在不同情境中重複使用。"
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed software or services for execution and understanding."
-msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程"
-"式碼或服務。"
+msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程式碼或服務。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3264,8 +3136,7 @@ msgstr "代碼庫開發應該由多方單位合作。"
 msgid ""
 "Configuration SHOULD be used to make [source code](../glossary.md#source-"
 "code) adapt to context specific needs."
-msgstr "應該使用組態設定方式以將[程式碼](../glossary.md#source-code) "
-"調整成能適應各情境的特定需求。"
+msgstr "應該使用組態設定方式以將[程式碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3298,8 +3169,7 @@ msgstr "軟體不應該要求只有單一供應商能提供的服務或平台。
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "use the codebase and what that would entail."
-msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行"
-"。"
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3313,8 +3183,7 @@ msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式
 msgid ""
 "If the codebase is in early development before a production-ready release, "
 "then check for evidence of ambition to obtain collaborators."
-msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願"
-"。"
+msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3364,8 +3233,7 @@ msgstr "檢查軟體是否可以在不使用單一供應商服務或平台的情
 msgid ""
 "Document your [policy](../glossary.md#policy) with enough clarity and detail"
 " that it can be understood outside of its original context."
-msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處"
-"於同個原始背景情境也能夠理解。"
+msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
@@ -3383,8 +3251,7 @@ msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式"
-"碼技術債，並讓代碼庫可以永續發展。"
+msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
@@ -3415,8 +3282,7 @@ msgstr "以邏輯上具有意義且獨立的模組構成，"
 msgid ""
 "so that someone in a similar organization facing a similar problem would be "
 "able to use (parts of) the solution."
-msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份"
-"）。"
+msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
 msgid ""
@@ -3425,17 +3291,14 @@ msgid ""
 "platforms or using proprietary components, make sure that collaborators can "
 "develop, use, test, and deploy without them."
 msgstr ""
-"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要"
-"將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者"
-"的情況下，就能進行開發、使用、測試、部署等。"
+"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行開發、使用、測試、部署等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
-"人與組織單位資料、代符與密碼等。"
+msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
 #: list)
@@ -3444,8 +3307,8 @@ msgid ""
 "manual/technology/making-source-code-open-and-reusable) by the UK Government"
 " Digital Service."
 msgstr ""
-"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/"
-"service-manual/technology/making-source-code-open-and-reusable)》。"
+"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable)》。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
 #: list)
@@ -3454,8 +3317,7 @@ msgid ""
 "Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
 " the World Wide Web Consortium."
 msgstr ""
-"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/"
-"questions/qa-i18n)》。"
+"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/questions/qa-i18n)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
 msgid "order: 13 redirect_from:"
@@ -3478,8 +3340,7 @@ msgid ""
 "emerge around the codebase."
 msgstr ""
 "有了開放且熟為人知的授權，任何人都可以看到[原始碼](../glossary.md#source-"
-"code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼庫](../glossary."
-"md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。"
+"code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼庫](../glossary.md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。"
 
 #: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
 msgid ""
@@ -3491,8 +3352,7 @@ msgstr "明確標示代碼庫中每一個檔案的授權，幫助使用者正確
 msgid ""
 "All source code and documentation MUST be licensed such that it may be "
 "freely reusable, changeable and redistributable."
-msgstr "所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授"
-"權條款。"
+msgstr "所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
@@ -3536,9 +3396,7 @@ msgid ""
 "Definition](https://opendefinition.org/licenses/)."
 msgstr ""
 "確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF "
-"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/"
-")，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/"
-"licenses/)。"
+"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/)，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/licenses/)。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the licenses used in the codebase are included as files."
@@ -3549,16 +3407,14 @@ msgid ""
 "Confirm that contribution guidelines and "
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
-msgstr "確認貢獻指南中，以及[儲存庫](../glossary."
-"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
+msgstr "確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
 "Check for machine-readable license checking in the codebase [continuous "
 "integration](../glossary.md#continuous-integration) tests."
 msgstr ""
-"在代碼庫[持續整合](../glossary.md#continuous-"
-"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
+"在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
 
 #: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
 msgid ""
@@ -3588,9 +3444,7 @@ msgid ""
 "NOT freely reusable, changeable and redistributable and don't fulfill these "
 "requirements."
 msgstr ""
-"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作"
-"品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用"
-"、自由修改、自由再次散布等，因此未能符合規定。"
+"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。"
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid "Add a new `license` file to every new codebase created."
@@ -3612,8 +3466,8 @@ msgstr "代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫
 msgid ""
 "[Open source definition](https://opensource.org/osd) by the Open Source "
 "Initiative, all open source licenses meet this definition."
-msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/"
-"osd)》，所有開放原始碼授權條款皆符合這套定義。"
+msgstr ""
+"開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3621,8 +3475,9 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
-"紐西蘭 CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
-"videos/creative-commons-kiwi)》。"
+"紐西蘭 CC "
+"Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/videos/creative-"
+"commons-kiwi)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3630,16 +3485,16 @@ msgid ""
 "Software Foundation Europe for unambiguous, human-readable and machine-"
 "readable copyright and licensing information."
 msgstr ""
-"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
-")》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
+"歐洲自由軟體基金會所發表的《[REUSE "
+"倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
 "[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
 " standardized, machine-readable abbreviations for most licenses."
 msgstr ""
-"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
-")提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
+"Linux 基金會所發表的 [SPDX "
+"授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
 
 #: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
 msgid "order: 7 redirect_from:"
@@ -3658,8 +3513,7 @@ msgid ""
 "Peer-review of contributions is essential for [source "
 "code](../glossary.md#source-code) quality, reducing security risks and "
 "operational risks."
-msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-"
-"code)品質的關鍵，降低安全性風險與營運風險。"
+msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-code)品質的關鍵，降低安全性風險與營運風險。"
 
 #: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
 msgid ""
@@ -3670,10 +3524,7 @@ msgid ""
 "Knowing that all source code was reviewed discourages a culture of blaming "
 "individuals, and encourages a culture of focusing on solutions."
 msgstr ""
-"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始"
-"碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發現與修復潛在錯誤"
-"的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個"
-"人都專注在解決方案上。"
+"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發現與修復潛在錯誤的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。"
 
 #: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
 msgid ""
@@ -3681,16 +3532,14 @@ msgid ""
 "a guaranteed time for feedback or collaborative improvement, which increases"
 " both rate of delivery and contributor engagement."
 msgstr ""
-"快速審查的[政策](../glossary."
-"md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， "
+"快速審查的[政策](../glossary.md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， "
 "進而提高貢獻者交付貢獻內容的頻率以及參與熱度。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "codebase MUST be reviewed by another contributor."
-msgstr "所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審"
-"查。"
+msgstr "所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews MUST include source, policy, tests and documentation."
@@ -3825,8 +3674,8 @@ msgid ""
 "way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
 " Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way."
-"cloudapps.digital/manuals/code-review-guidelines.html#content)》。"
+"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way.cloudapps.digital/manuals/code-"
+"review-guidelines.html#content)》。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3837,19 +3686,19 @@ msgid ""
 "[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
 "protected/)."
 msgstr ""
-"[GitHub](https://docs.github.com/en/repositories/"
-"configuring-branches-and-merges-in-your-repository/"
-"defining-the-mergeability-of-pull-requests/about-protected-branches) 與 "
-"[GitLab](https://about.gitlab.com/blog/2014/11/26/"
-"keeping-your-code-protected/) 平臺的分支保護說明。"
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) 與 "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/) 平臺的分支保護說明。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
 "[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
 "gentle-art-of-patch-review/) by Sage Sharp."
 msgstr ""
-"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/"
-"the-gentle-art-of-patch-review/)》。"
+"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/the-gentle-"
+"art-of-patch-review/)》。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3857,9 +3706,8 @@ msgid ""
 "Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
 "mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
 msgstr ""
-"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/"
-"1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id."
-"g43d857af8_0177)》。"
+"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)》。"
 
 #: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
 msgid "order: 15 redirect_from:"
@@ -3878,8 +3726,7 @@ msgid ""
 "Following a consistent and coherent style enables contributors in different "
 "environments to work together. Unifying vocabularies reduces friction in "
 "communication between contributors."
-msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝"
-"通上的摩擦。"
+msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝通上的摩擦。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
@@ -3887,8 +3734,7 @@ msgid ""
 "guide, either the codebase community's own or an existing one referred to in"
 " the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指"
-"南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既有風格。"
+"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既有風格。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
@@ -3922,8 +3768,7 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
-"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄"
-"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
+"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
 
 #: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
 msgid ""
@@ -3944,12 +3789,8 @@ msgid ""
 "documentation. Continually improve upon and expand this documentation with "
 "the aim of evolving this documentation into engineering guidelines."
 msgstr ""
-"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#r"
-"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
-"前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
-"以及機器不容易檢查的其他層面。指南應該包含貢獻的[原始碼](../glossary.md"
-"#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試"
-"、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
+"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查的其他層面。指南應該包含貢獻的[原始碼](../glossary.md#source-"
+"code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
 
 #: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
 msgid "Additionally:"
@@ -3967,8 +3808,7 @@ msgstr "在代碼庫中加入程式碼品質分析工具的組態設定。"
 msgid ""
 "[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
 "Wikipedia."
-msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/"
-"Programming_style)》條目。"
+msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。"
 
 #: ./criteria/use-continuous-integration.md:block 3 (paragraph)
 msgid "order: 12 redirect_from:"
@@ -3989,9 +3829,7 @@ msgid ""
 " merging and the smaller the contribution, the easier it is to resolve merge"
 " conflicts."
 msgstr ""
-"開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進"
-"行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易"
-"解決。"
+"開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易解決。"
 
 #: ./criteria/use-continuous-integration.md:block 7 (paragraph)
 msgid ""
@@ -4001,8 +3839,7 @@ msgid ""
 " The more focused the test, the easier it is to clearly identify and "
 "understand errors as they arise."
 msgstr ""
-"自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允"
-"許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。"
+"自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。"
 
 #: ./criteria/use-continuous-integration.md:block 8 (paragraph)
 msgid ""
@@ -4012,8 +3849,8 @@ msgid ""
 " state of the [codebase](../glossary.md#codebase)."
 msgstr ""
 "以文件記錄代碼庫的[持續整合](../glossary.md#continuous-"
-"integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。"
-"透過持續整合可以更輕易地監督 [代碼庫](../glossary.md#codebase)狀態。"
+"integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。透過持續整合可以更輕易地監督 "
+"[代碼庫](../glossary.md#codebase)狀態。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
@@ -4055,8 +3892,7 @@ msgstr "應該監督原始碼測試與文件的涵蓋範圍。"
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr "可選擇是否測試[政策](../glossary."
-"md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
+msgstr "可選擇是否測試[政策](../glossary.md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
@@ -4106,8 +3942,7 @@ msgstr "檢查是否已經公佈原始碼覆蓋率數據。"
 msgid ""
 "Involve managers as well as developers and designers as early in the process"
 " as possible and keep them engaged throughout development of your policy."
-msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序"
-"。"
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
@@ -4122,8 +3957,7 @@ msgstr "如果政策文件未能通過測試，請立即修正。"
 msgid ""
 "Make sure the source code reflects any changes to the policy (see [Maintain "
 "version control](maintain-version-control.md))."
-msgstr "確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-"
-"control.md)）。"
+msgstr "確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-control.md)）。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
@@ -4164,8 +3998,7 @@ msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡
 msgid ""
 "Help managers and policy makers test their contributions, for example by "
 "testing their contributions for broken links or style."
-msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式"
-"。"
+msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
@@ -4175,8 +4008,7 @@ msgid ""
 "of storage space and memory allocation failure are typical examples of "
 "difficult to create conditions."
 msgstr ""
-"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
-"來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
+"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
@@ -4198,8 +4030,8 @@ msgid ""
 "integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
 " by Martin Fowler."
 msgstr ""
-"Martin Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/"
-"continuousIntegration.html)》。"
+"Martin "
+"Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/continuousIntegration.html)》。"
 
 #: ./criteria/use-continuous-integration.md:block 20 (unordered list)
 msgid ""
@@ -4207,8 +4039,8 @@ msgid ""
 "way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
 "Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/"
-"standards/continuous-delivery.html)》。"
+"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/standards/continuous-"
+"delivery.html)》。"
 
 #: ./criteria/use-continuous-integration.md:block 20 (unordered list)
 msgid ""
@@ -4216,9 +4048,8 @@ msgid ""
 "regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
 "testing-your-service-regularly) by the UK Government Digital Service."
 msgstr ""
-"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/"
-"service-manual/technology/quality-assurance-testing-your-service-"
-"regularly)》。"
+"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/service-"
+"manual/technology/quality-assurance-testing-your-service-regularly)》。"
 
 #: ./criteria/use-open-standards.md:block 3 (paragraph)
 msgid "order: 11 redirect_from:"
@@ -4242,9 +4073,7 @@ msgid ""
 "exchange."
 msgstr ""
 "[開放標準](../glossary.md#open-"
-"standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的知"
-"識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明"
-"確，就可以獨立發展任何方向的資料交換。"
+"standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的知識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明確，就可以獨立發展任何方向的資料交換。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4252,8 +4081,7 @@ msgid ""
 "codebase MUST use an open standard that meets the [Open Source Initiative "
 "Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
-"代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需"
-"求規範](https://opensource.org/osr)的開放標準。"
+"代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4265,8 +4093,7 @@ msgstr "如果有使用到任何的非開放標準，則必須在文件中清楚
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的"
-"連結。"
+msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4306,8 +4133,7 @@ msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用"
-"任何標準時，則留下聲明。"
+msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。"
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
@@ -4334,8 +4160,7 @@ msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr "審查提交紀錄與其他[儲存庫](../glossary."
-"md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
+msgstr "審查提交紀錄與其他[儲存庫](../glossary.md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
 
 #: ./criteria/use-open-standards.md:block 18 (unordered list)
 msgid ""
@@ -4343,8 +4168,8 @@ msgid ""
 "standards-principles/open-standards-principles), "
 "[policy](../glossary.md#policy) paper of the UK Cabinet Office."
 msgstr ""
-"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/"
-"publications/open-standards-principles/open-standards-"
+"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-"
 "principles)》[政策](../glossary.md#policy)報告。"
 
 #: ./criteria/use-plain-english.md:block 3 (paragraph)
@@ -4370,16 +4195,14 @@ msgid ""
 "Public sector information needs to be accessible to all its constituents. "
 "Plain and simple language makes the [code](../glossary.md#code) and what it "
 "does easier to understand for a wider variety of people."
-msgstr "選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](.."
-"/glossary.md#code)與其功用。"
+msgstr "選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。"
 
 #: ./criteria/use-plain-english.md:block 8 (paragraph)
 msgid ""
 "Translations further increase the possible reach of a "
 "[codebase](../glossary.md#codebase). Language that is easy to understand "
 "lowers the cost of creating and maintaining translations."
-msgstr "透過翻譯可以讓更多人認識[代碼庫](../glossary."
-"md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。"
+msgstr "透過翻譯可以讓更多人認識[代碼庫](../glossary.md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid "All codebase documentation MUST be in English."
@@ -4391,8 +4214,7 @@ msgid ""
 "where [policy](../glossary.md#policy) is machine interpreted as code."
 msgstr ""
 "所有[原始碼](../glossary.md#source-"
-"code)都必須使用英語編寫，其中[政策](../glossary."
-"md#policy)是由機器解讀當作程式碼的部分則除外。"
+"code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀當作程式碼的部分則除外。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4411,8 +4233,7 @@ msgid ""
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
 msgstr ""
-"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果"
-"有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
+"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4420,8 +4241,8 @@ msgid ""
 "recommended by the [Web Content Accessibility Guidelines "
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
-"根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/"
-"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
+"根據《[網頁內容近用性無障礙指南 "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4436,8 +4257,7 @@ msgstr "確認代碼庫文件有英語版本。"
 msgid ""
 "Confirm that source code is in English, or confirm any non-English is policy"
 " or terms with preceding explanations."
-msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等"
-"。"
+msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Confirm any non-English policy has an accompanying summary in English."
@@ -4452,8 +4272,7 @@ msgstr "確認翻譯版與英語版內容相同。"
 msgid ""
 "Check that no unexplained acronyms, abbreviations, puns or legal/non-"
 "English/domain specific terms are in the documentation."
-msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業"
-"特定詞彙等。"
+msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Check the spelling, grammar and readability of the documentation."
@@ -4463,8 +4282,7 @@ msgstr "檢查文件的拼字、文法與易讀性等。"
 msgid ""
 "Frequently test with other managers, developers and designers in the process"
 " if they understand what you are delivering and how you document it."
-msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交"
-"付的程式碼與其文件的內容。"
+msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。"
 
 #: ./criteria/use-plain-english.md:block 16 (unordered list)
 msgid ""
@@ -4473,23 +4291,19 @@ msgid ""
 "teams and stakeholders. Add any such terms to a glossary and link to it from"
 " the places they are being used."
 msgstr ""
-"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，"
-"或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，"
-"並且在使用這些詞彙的地方加上詞彙表連結。"
+"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在使用這些詞彙的地方加上詞彙表連結。"
 
 #: ./criteria/use-plain-english.md:block 16 (unordered list)
 msgid ""
 "Be critical of documentation and descriptions in proposals and changes. If "
 "you don't understand something, others will probably also struggle with it."
-msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其"
-"他人也同樣迷惘。"
+msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。"
 
 #: ./criteria/use-plain-english.md:block 18 (unordered list)
 msgid ""
 "Frequently test with policy makers and managers if they understand what you "
 "are delivering and how you document it."
-msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件"
-"的內容。"
+msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。"
 
 #: ./criteria/use-plain-english.md:block 18 (unordered list)
 msgid ""
@@ -4504,8 +4318,7 @@ msgid ""
 "readable and understandable."
 msgstr ""
 "根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 "
-"之可讀性](https://www.w3.org/TR/WCAG21/"
-"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
+"之可讀性](https://www.w3.org/TR/WCAG21/#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4513,16 +4326,15 @@ msgid ""
 "single-market/en/web-accessibility) by the European Commission, is an "
 "example of regulation requiring high accessibility."
 msgstr ""
-"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/"
-"digital-single-market/en/web-accessibility)》就是無障礙法規的例子。"
+"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/digital-single-market/en/web-"
+"accessibility)》就是無障礙法規的例子。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
 "[Definition of plain "
 "language](https://www.plainlanguage.gov/about/definitions/) by United States"
 " General Services Administration."
-msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/"
-")》。"
+msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/)》。"
 
 #: ./criteria/welcome-contributors.md:block 3 (paragraph)
 msgid "order: 4 redirect_from:"
@@ -4546,10 +4358,8 @@ msgid ""
 " communities. Newcomers need to understand and trust the codebase "
 "community’s governance."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 歡迎任"
-"何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當中，若貢獻者有明"
-"確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新"
-"參與者需要瞭解並且相信代碼庫社群的治理。"
+"[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 "
+"歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當中，若貢獻者有明確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並且相信代碼庫社群的治理。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
@@ -4562,15 +4372,13 @@ msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開"
-"發，例如以「`CONTRIBUTING`」檔案說明。"
+msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
-"RNANCE`」檔案來說明。"
+msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
@@ -4641,8 +4449,7 @@ msgid ""
 "[policy](../glossary.md#policy) experts, non-governmental organizations and "
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
-"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary."
-"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
+"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
 
 #: ./criteria/welcome-contributors.md:block 12 (unordered list)
 msgid ""
@@ -4660,8 +4467,7 @@ msgstr "確保治理架構文件內容中，有包含目前如何改變治理狀
 msgid ""
 "If the community has some consensus about how the governance should change, "
 "then include those ideas stated as ambitions in the documentation."
-msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中"
-"。"
+msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
@@ -4673,8 +4479,7 @@ msgstr "若有需要，確保如同代碼庫社群所同意的，編列貢獻審
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與"
-"的時間長度等。"
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
@@ -4696,8 +4501,7 @@ msgstr "清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/"
-"building-community/)》。"
+msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4705,8 +4509,8 @@ msgid ""
 "open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
 "source-project/) by Mike McQuaid."
 msgstr ""
-"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-o"
-"pen-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
+"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-"
+"source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
 "project/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
@@ -4716,8 +4520,8 @@ msgid ""
 " projects, by Open Source Guides."
 msgstr ""
 "開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-"
-"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
-"leadership-and-governance/)》。"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/leadership-and-"
+"governance/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4735,8 +4539,8 @@ msgid ""
 "tries to provide the relevant information to print it there or somewhere "
 "else."
 msgstr ""
-"The Standard for Public Code 由 Reclameland "
-"負責印刷。本指南提供印刷相關資訊，方便在 Reclameland 或其他地方印刷。"
+"The Standard for Public Code 由 Reclameland 負責印刷。本指南提供印刷相關資訊，方便在 Reclameland "
+"或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
@@ -4749,8 +4553,8 @@ msgid ""
 "Form: Softcover book ([Reclameland product "
 "page](https://www.reclameland.nl/drukken/softcover-boeken))"
 msgstr ""
-"樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/"
-"softcover-boeken))"
+"樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/softcover-"
+"boeken))"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Format: A4"
@@ -4795,8 +4599,7 @@ msgid ""
 "When these details are chosen, the cover and insides are uploaded and the "
 "order is placed payment can happen (payment ahead) after which printing "
 "starts."
-msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開"
-"始印刷。"
+msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。"
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
@@ -4822,10 +4625,7 @@ msgid ""
 " truly the best expression of ideas, then follow the [Chicago Manual of "
 "Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
 msgstr ""
-"如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如"
-"果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達"
-"該句子的涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/"
-"Dash#En_dash_versus_em_dash)。"
+"如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達該句子的涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)。"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create a release branch"
@@ -4873,30 +4673,27 @@ msgid ""
 "run `script/generate-review-template.sh` and commit updated `docs/review-"
 "template.html`"
 msgstr ""
-"執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-"
-"template.html`"
+"執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-template.html`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "update `docs/standard-for-public-code.md` with the new text from the review "
 "template, updating any status changes as a result"
-msgstr "用審查範本的新文字來更新 `docs/standard-for-public-code."
-"md`，更新所有的狀態變更"
+msgstr "用審查範本的新文字來更新 `docs/standard-for-public-code.md`，更新所有的狀態變更"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Reread any section or paragraph to ensure wording changes still fit the "
 "whole and do not contain grammar or spelling errors"
-msgstr "重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼"
-"字錯誤"
+msgstr "重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼字錯誤"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
 " `script/ensure-font.sh`"
 msgstr ""
-"確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/"
-"ensure-font.sh`"
+"確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/ensure-"
+"font.sh`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
@@ -4910,8 +4707,7 @@ msgstr "確保沒有連結相衝的問題"
 msgid ""
 "Check the page breaks, possibly removing or adding page-break CSS, for "
 "example: `<p style=\"page-break-after: always;\"></p>`"
-msgstr "移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style=\"page-break-after: "
-"always;\"></p>`"
+msgstr "移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style=\"page-break-after: always;\"></p>`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "If needed, commit fixes and repeat extra pass"
@@ -5011,8 +4807,7 @@ msgid ""
 "Ping [translation](https://github.com/publiccodenet/community-translations-"
 "standard) contributors"
 msgstr ""
-"標記[翻譯](https://github.com/publiccodenet/community-translations-"
-"standard)貢獻者"
+"標記[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者"
 
 #: ./docs/roadmap.md:block 1 (header)
 msgid "Roadmap"
@@ -5026,8 +4821,7 @@ msgstr "上次更新時間：2023-03-08"
 msgid ""
 "This document intends to shed light on the current development plans of the "
 "team. Plans change constantly as new information is absorbed by the team."
-msgstr "本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變"
-"動。"
+msgstr "本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變動。"
 
 #: ./docs/roadmap.md:block 5 (paragraph)
 msgid ""
@@ -5035,9 +4829,8 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
-"代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會議](https://about."
-"publiccode.net/activities/standard-maintenance/backlog-pruning."
-"html)的一部份。"
+"代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會議](https://about.publiccode.net/activities/standard-"
+"maintenance/backlog-pruning.html)的一部份。"
 
 #: ./docs/roadmap.md:block 6 (header)
 msgid "Current work"
@@ -5077,8 +4870,7 @@ msgstr "認證標章"
 msgid ""
 "Add to README and index.md information (and eventually statistics) on "
 "adoption and use (issue #438)"
-msgstr "新增「README」與「index."
-"md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上"
+msgstr "新增「README」與「index.md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Physical paper checklist"
@@ -5128,16 +4920,14 @@ msgstr "序"
 msgid ""
 "The Standard for Public Code is a set of criteria that support public "
 "organizations in developing and maintaining software and policy together."
-msgstr "The Standard for Public Code "
-"當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./foreword.md:block 7 (paragraph)
 msgid ""
 "Anyone developing public-purpose software or policy can use this standard to"
 " work towards higher quality public services that are more cost effective, "
 "with less risk and more control."
-msgstr "開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成"
-"本效益、風險更低且能夠掌控。"
+msgstr "開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成本效益、風險更低且能夠掌控。"
 
 #: ./foreword.md:block 8 (paragraph)
 msgid ""
@@ -5158,10 +4948,7 @@ msgid ""
 "distinct from regular software because it operates under fundamentally "
 "different circumstances and expectations."
 msgstr ""
-"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公"
-"共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體"
-"生產的安排，都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件"
-"與期待也不同。"
+"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體生產的安排，都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件與期待也不同。"
 
 #: ./foreword.md:block 11 (header)
 msgid "Reasons for public code"
@@ -5186,8 +4973,7 @@ msgid ""
 "originator of new policy, for example where algorithms decide which "
 "districts need extra social services or policing."
 msgstr ""
-"在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用"
-"於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。"
+"在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。"
 
 #: ./foreword.md:block 16 (paragraph)
 msgid ""
@@ -5199,10 +4985,7 @@ msgid ""
 "by machines. In other words, software code has increasingly started to equal"
 " legal code."
 msgstr ""
-"在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能"
-"執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共"
-"價值，設定社會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體"
-"程式越來越接近法規的地位。"
+"在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共價值，設定社會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體程式越來越接近法規的地位。"
 
 #: ./foreword.md:block 17 (paragraph)
 msgid ""
@@ -5260,10 +5043,7 @@ msgid ""
 " Citizens and civil society actors need this software to be transparent and "
 "accountable."
 msgstr ""
-"我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將"
-"軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都"
-"需要技術主權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依"
-"法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。"
+"我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都需要技術主權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。"
 
 #: ./foreword.md:block 25 (paragraph)
 msgid ""
@@ -5356,8 +5136,7 @@ msgid ""
 "to the software, so that its development and maintenance become truly "
 "collaborative."
 msgstr ""
-"公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程"
-"式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。"
+"公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。"
 
 #: ./foreword.md:block 37 (paragraph)
 msgid "Being open unlocks many other things."
@@ -5375,12 +5154,7 @@ msgid ""
 "in the future. The code will be easier to retool, repurpose or retire. This "
 "all results in lower risk public infrastructure."
 msgstr ""
-"公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且"
-"貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高"
-"。許多貢獻者會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多"
-"人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼"
-"與資料，在未來也更容易改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都"
-"讓公共基礎建設風險更低。"
+"公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高。許多貢獻者會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼與資料，在未來也更容易改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都讓公共基礎建設風險更低。"
 
 #: ./foreword.md:block 39 (paragraph)
 msgid ""
@@ -5388,8 +5162,7 @@ msgid ""
 "to how to customize the software so it works best in each local context, "
 "creating better user experiences for their end users (residents or "
 "citizens)."
-msgstr "集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情"
-"境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。"
+msgstr "集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。"
 
 #: ./foreword.md:block 40 (header)
 msgid "Economics of public code"
@@ -5400,8 +5173,7 @@ msgid ""
 "Public code offers a better economic model for public organizations as well "
 "as for commercial companies. It's an alternative to traditional software "
 "procurement which increases local control and economic opportunity."
-msgstr "公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助"
-"各地的公共組織更能控制程式，也有更好的經濟機會。"
+msgstr "公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助各地的公共組織更能控制程式，也有更好的經濟機會。"
 
 #: ./foreword.md:block 42 (paragraph)
 msgid ""
@@ -5414,11 +5186,7 @@ msgid ""
 "administrations can use their own software purchasing to stimulate "
 "innovation and competition in their local economy."
 msgstr ""
-"公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來"
-"開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始"
-"碼讓社會大眾更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在"
-"地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激"
-"當地經濟的創新與競爭。"
+"公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始碼讓社會大眾更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激當地經濟的創新與競爭。"
 
 #: ./foreword.md:block 43 (paragraph)
 msgid ""
@@ -5435,8 +5203,7 @@ msgid ""
 "Public code can be used and developed by permanent in-house development "
 "teams, contractors or outsourced suppliers. Vendors to public organizations "
 "can include public code in their bids for contracts."
-msgstr "公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可"
-"以包含公共程式。"
+msgstr "公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可以包含公共程式。"
 
 #: ./foreword.md:block 46 (paragraph)
 msgid ""
@@ -5445,9 +5212,7 @@ msgid ""
 "innovative approach to adapting the public code to your context, you could "
 "describe the service or outcome in your contract."
 msgstr ""
-"若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用"
-"該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您"
-"的服務或成果。"
+"若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您的服務或成果。"
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
@@ -5457,8 +5222,7 @@ msgstr "The Standard for Public Code 目標"
 msgid ""
 "This Standard supports developers, designers, managers and public policy "
 "makers to:"
-msgstr "The Standard for Public Code "
-"支持開發人員、設計師、管理人員以及公共政策制定者："
+msgstr "The Standard for Public Code 支持開發人員、設計師、管理人員以及公共政策制定者："
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
@@ -5489,8 +5253,7 @@ msgstr "更好的經濟模型改善與供應商的關係"
 msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
-msgstr "代碼庫潛在使用者依照 The Standard for Public Code "
-"測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。"
+msgstr "代碼庫潛在使用者依照 The Standard for Public Code 測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
@@ -5563,9 +5326,8 @@ msgid ""
 "paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
 "Software.pdf) by the Free Software Foundation Europe."
 msgstr ""
-"歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮書](https:"
-"//download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) "
-"》。"
+"歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮書](https://download.fsfe.org/campaigns/pmpc/PMPC-"
+"Modernising-with-Free-Software.pdf) 》。"
 
 #: ./foreword.md:block 62 (header)
 msgid "Videos on public code"
@@ -5577,9 +5339,9 @@ msgid ""
 "2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
 "the background behind the Foundation for Public Code."
 msgstr ""
-"[2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/"
-"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹 The Foundation for Public Code "
-"的背景。"
+"[2019 年 Decidim Fest "
+"的「程式合作是城市的未來」](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny "
+"介紹 The Foundation for Public Code 的背景。"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5587,8 +5349,8 @@ msgid ""
 "2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
 "procurement, law and more."
 msgstr ""
-"[ 2019 年 Nextcloud 大會的「公帑？公共程式！」專題討論](https://youtube.com/"
-"watch?v=QHFkD4xfd6c)。探討採購、法律等主題。"
+"[ 2019 年 Nextcloud "
+"大會的「公帑？公共程式！」專題討論](https://youtube.com/watch?v=QHFkD4xfd6c)。探討採購、法律等主題。"
 
 #: ./foreword.md:block 64 (header)
 msgid "Get involved"
@@ -5598,8 +5360,7 @@ msgstr "加入我們的行列"
 msgid ""
 "This standard is a living document. [Read our contributor "
 "guide](/CONTRIBUTING.md) to learn how you can make it better."
-msgstr "此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING."
-"md)，瞭解您可以如何讓此標準變得更好。"
+msgstr "此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING.md)，瞭解您可以如何讓此標準變得更好。"
 
 #: ./foreword.md:block 66 (header)
 msgid "Contact"
@@ -5628,8 +5389,7 @@ msgid ""
 "Any explicitly described system of rules. This includes laws, policy and "
 "ordinances, as well as source code that is used to build software. Both of "
 "these are rules, some executed by humans and others by machines."
-msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是"
-"規則，前者由人類來執行，後者則是機器。"
+msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是規則，前者由人類來執行，後者則是機器。"
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
@@ -5654,8 +5414,7 @@ msgid ""
 "In software engineering, continuous integration (CI) is the practice of "
 "merging all developers' working copies to a development branch of a codebase"
 " as frequently as reasonable."
-msgstr "軟體工程的持續整合 (CI) "
-"就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。"
+msgstr "軟體工程的持續整合 (CI) 就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。"
 
 #: ./glossary.md:block 11 (header)
 msgid "Different contexts"
@@ -5666,8 +5425,7 @@ msgid ""
 "Two contexts are different if they are different public organizations or "
 "different departments for which there is not one decision maker that could "
 "make collaboration happen naturally."
-msgstr "如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩"
-"個不同的情境。"
+msgstr "如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩個不同的情境。"
 
 #: ./glossary.md:block 13 (header)
 msgid "General public"
@@ -5682,8 +5440,7 @@ msgstr "一般民眾：程式碼及以程式碼為基礎的服務的終端使用
 msgid ""
 "For example, a city's residents are considered end users of a city's "
 "services and of all code that powers these services."
-msgstr "舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終"
-"端使用者。"
+msgstr "舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終端使用者。"
 
 #: ./glossary.md:block 16 (header)
 msgid "Open source"
@@ -5693,8 +5450,8 @@ msgstr "開源"
 msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
-msgstr "開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-"
-"annotated)》定義何謂「開源」。"
+msgstr ""
+"開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》定義何謂「開源」。"
 
 #: ./glossary.md:block 18 (header)
 msgid "Open standard"
@@ -5704,8 +5461,7 @@ msgstr "開放標準"
 msgid ""
 "An open standard is any standard that meets the Open Source Initiative's "
 "[Open Standard Requirements](https://opensource.org/osr)."
-msgstr "任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/"
-"osr)的標準就是開放標準。"
+msgstr "任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/osr)的標準就是開放標準。"
 
 #: ./glossary.md:block 20 (header)
 msgid "Policy"
@@ -5719,8 +5475,7 @@ msgid ""
 "body within an organization. Policies can assist in both subjective and "
 "objective decision making."
 msgstr ""
-"政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協"
-"定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。"
+"政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。"
 
 #: ./glossary.md:block 22 (paragraph)
 msgid ""
@@ -5732,15 +5487,13 @@ msgstr "公共政策是政府將其政治理念轉化成計畫與行動的流程
 msgid ""
 "At the national level, policy and legislation (the law) are usually "
 "separate. The distinction is often more blurred in local government."
-msgstr "在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一"
-"起。"
+msgstr "在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一起。"
 
 #: ./glossary.md:block 24 (paragraph)
 msgid ""
 "In the Standard the word 'policy' refers to policy created and adopted by "
 "public organizations such as governments and municipalities."
-msgstr "The Standard for Public Code "
-"當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
+msgstr "The Standard for Public Code 當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
@@ -5756,8 +5509,7 @@ msgstr "公共程式是由公家機關開發的開源軟體，當中包括協作
 msgid ""
 "Public code is both computer source code (such as software and algorithms) "
 "and public policy executed in a public context, by humans or machines."
-msgstr "公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及"
-"公共政策。"
+msgstr "公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及公共政策。"
 
 #: ./glossary.md:block 28 (paragraph)
 msgid ""
@@ -5772,8 +5524,7 @@ msgid ""
 "development process openly, public code can provide a building block for "
 "others to:"
 msgstr ""
-"為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境"
-"中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以："
+"為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以："
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "re-implement in their local context"
@@ -5792,8 +5543,7 @@ msgid ""
 "To facilitate reuse, public code is either released into the public domain "
 "or licensed with an open license that permits others to view and reuse the "
 "work freely and to produce derivative works."
-msgstr "為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複"
-"利用其內容的開放授權，藉此推動衍生工作。"
+msgstr "為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複利用其內容的開放授權，藉此推動衍生工作。"
 
 #: ./glossary.md:block 32 (header)
 msgid "Repository"
@@ -5805,8 +5555,7 @@ msgid ""
 "and metadata of a codebase. Repositories allow multiple contributors to work"
 " on the same set of files. Repositories are able to store multiple versions "
 "of sets of files."
-msgstr "儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者"
-"同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。"
+msgstr "儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。"
 
 #: ./glossary.md:block 34 (header)
 msgid "Source Code"
@@ -5832,9 +5581,7 @@ msgid ""
 "different versions with each other and to see how content has changed over "
 "time."
 msgstr ""
-"版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修"
-"正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程"
-"式碼的演變。修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。"
+"版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程式碼的演變。修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。"
 
 #: ./index.md:block 3 (header)
 msgid "toc: false"
@@ -5848,8 +5595,7 @@ msgstr "政府開源協作指引"
 msgid ""
 "The Standard for Public Code is a set of criteria that supports public "
 "organizations in developing and maintaining software and policy together."
-msgstr "The Standard for Public Code "
-"當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。"
 
 #: ./index.md:block 6 (paragraph)
 msgid ""
@@ -5862,12 +5608,11 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
-"The Standard for Public Code 指引正在建構自己開源解決方案的公共組織，方便他們"
-"未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案"
-"。The Standard for Public Code "
-"提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The "
-"Standard for Public Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The "
-"Standard for Public Code 適用於各政府層級的代碼庫，從超國家到市政府。"
+"The Standard for Public Code "
+"指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案。The Standard "
+"for Public Code 提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The Standard for Public "
+"Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The Standard for Public Code "
+"適用於各政府層級的代碼庫，從超國家到市政府。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5875,8 +5620,8 @@ msgid ""
 "code)’ as open source software developed by public organizations, together "
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
-"The Standard for Public Code 將‘[公共程式](glossary.md#public-code)’定義為由"
-"公共組織所開發的開源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
+"The Standard for Public Code 將‘[公共程式](glossary.md#public-"
+"code)’定義為由公共組織所開發的開源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
@@ -5911,8 +5656,8 @@ msgid ""
 " page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
 "\"index.md\" %}{% if page.title %}"
 msgstr ""
-"[標準](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for "
-"page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"[標準](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for page "
+"in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
 "\"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 11 (unordered list)
@@ -5960,9 +5705,8 @@ msgid ""
 msgstr ""
 "我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。 "
 "[議程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-"
-"Code) 在會議前約一週的時間更新。您可以 [報名](https://odoo.publiccode.net/"
-"survey/start/"
-"594b9243-c7e5-4bc1-8714-35137c971842)，之後舉辦會議時會寄送邀情函給您。"
+"Code) 在會議前約一週的時間更新。您可以 "
+"[報名](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)，之後舉辦會議時會寄送邀情函給您。"
 
 #: ./index.md:block 14 (header)
 msgid "Other resources"
@@ -5974,8 +5718,9 @@ msgid ""
 "Standard](https://publiccodenet.github.io/community-translations-standard/) "
 "in other languages"
 msgstr ""
-"[The Standard for Public Code 社群其他語言](https://publiccodenet.github.io/"
-"community-translations-standard/) 非官方翻譯版"
+"[The Standard for Public Code "
+"社群其他語言](https://publiccodenet.github.io/community-translations-standard/) "
+"非官方翻譯版"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5983,8 +5728,8 @@ msgid ""
 "assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
 "public sector open source codebases"
 msgstr ""
-"公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/"
-"assessment-eligibility/)"
+"公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/assessment-"
+"eligibility/)"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5993,9 +5738,9 @@ msgid ""
 "template.html) used by Foundation for Public Code stewards for codebase "
 "review"
 msgstr ""
-"The Foundation for Public Code 管理人員審查代碼庫時使用的 [The Standard for "
-"Public Code 檢查清單](https://github.com/publiccodenet/standard/blob/develop/"
-"docs/review-template.html)"
+"The Foundation for Public Code 管理人員審查代碼庫時使用的 [The Standard for Public Code "
+"檢查清單](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
+"template.html)"
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
@@ -6005,8 +5750,7 @@ msgstr "讀者指南"
 msgid ""
 "The Standard describes a number of criteria. All criteria have consistent "
 "sections that make it clear how to create great public code."
-msgstr "公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的"
-"公共程式。"
+msgstr "公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的公共程式。"
 
 #: ./readers-guide.md:block 5 (paragraph)
 msgid ""
@@ -6014,8 +5758,7 @@ msgid ""
 "designers\" apply to anyone performing duties associated with these roles, "
 "regardless of their job title. It is common for individuals to have duties "
 "which span multiple roles."
-msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職"
-"責的人，不受職稱限制。很多人都承擔多個角色的職責。"
+msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職責的人，不受職稱限制。很多人都承擔多個角色的職責。"
 
 #: ./readers-guide.md:block 6 (paragraph)
 msgid ""
@@ -6043,8 +5786,8 @@ msgstr "這章節解釋如何遵循 The Standard for Public Code 。"
 msgid ""
 "The following keywords in this document are to be interpreted as described "
 "in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
-msgstr "本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/"
-"rfc2119) 來詮釋："
+msgstr ""
+"本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) 來詮釋："
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST"
@@ -6092,8 +5835,8 @@ msgid ""
 "compliant with the Standard. This is key if you want to operationalize the "
 "Standard."
 msgstr ""
-"本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public "
-"Code 。如果您想要實施 The Standard for Public Code ，這將會是關鍵。"
+"本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public Code 。如果您想要實施 The Standard"
+" for Public Code ，這將會是關鍵。"
 
 #: ./readers-guide.md:block 15 (paragraph)
 msgid ""
@@ -6127,9 +5870,7 @@ msgid ""
 " to create the right culture, line up the right resources and provide the "
 "right structures to deliver great services."
 msgstr ""
-"管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們"
-"也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資"
-"源，提供正確的架構，才能夠帶來良好的服務。"
+"管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源，提供正確的架構，才能夠帶來良好的服務。"
 
 #: ./readers-guide.md:block 23 (paragraph)
 msgid ""
@@ -6154,8 +5895,8 @@ msgid ""
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
 msgstr ""
-"The Standard for Public Code 不是為了代碼庫的個別執行所撰寫。這代表該標準不是"
-"要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框架。"
+"The Standard for Public Code "
+"不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6166,11 +5907,10 @@ msgid ""
 "Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
 "synergize well with them."
 msgstr ""
-"The Standard for Public Code "
-"有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。"
-"因此The Standard for Public Code 目的並非是要取代品質標準（像是 ISO 25000 "
-"認證），或是以安全為準的標準（像是 [OpenSSF 最佳實務標章](https://github.com/"
-"coreinfrastructure/best-practices-badge)），而是要與他們協作。"
+"The Standard for Public Code 有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。因此The "
+"Standard for Public Code 目的並非是要取代品質標準（像是 ISO 25000 認證），或是以安全為準的標準（像是 "
+"[OpenSSF 最佳實務標章](https://github.com/coreinfrastructure/best-practices-"
+"badge)），而是要與他們協作。"
 
 #: ./readers-guide.md:block 28 (paragraph)
 msgid ""
@@ -6178,6 +5918,100 @@ msgid ""
 " that a community will spring into existence. That still requires "
 "proactiveness and ambition beyond making the codebase collaboration ready."
 msgstr ""
-"The Standard for Public Code 的目的之一在於促進協作，但也無法保證能夠催生出一"
-"個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要協作者的積極推"
-"動與野心。"
+"The Standard for Public Code "
+"的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要協作者的積極推動與野心。"
+
+msgid ""
+"script/release-body.sh expects VERSION in the first second-level header"
+msgstr ""
+
+msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
+msgstr ""
+
+msgid "Version 0.7.1"
+msgstr ""
+
+msgid ""
+"July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
+"clarifies references to code."
+msgstr ""
+
+msgid ""
+"The criterion \"Make the codebase reusable and portable\" was renamed from "
+"\"Create reusable and portable code\"."
+msgstr ""
+
+msgid "Added a glossary entry for \"Source Code\"."
+msgstr ""
+
+msgid ""
+"References to \"code\" which only applied to \"source code\" now reference "
+"\"source code\" explicitly."
+msgstr ""
+
+msgid "Clarification of \"running code\" as \"software\"."
+msgstr ""
+
+msgid "Minor changes to clarify \"code\" vs \"codebase\"."
+msgstr ""
+
+msgid "Simplify guidance to policy makers in Bundle policy and source code."
+msgstr ""
+
+msgid ""
+"Clarify How to test sections of Make the codebase findable and Make the "
+"codebase reusable and portable."
+msgstr ""
+
+msgid "Add a criteria and requirements checklist to the release artifacts."
+msgstr ""
+
+msgid "Increase automation of the release process."
+msgstr ""
+
+msgid ""
+"![version 0.7.1](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/) "
+"[![Standard commitment](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
+msgstr ""
+
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. If you wish to "
+"advertise the codebase community's aspiration to meet the criteria of the "
+"Standard for Public Code, link the documentation of this commitment from the"
+" [standard-for-public-code-commitment badge](assets/standard-for-public-"
+"code-commitment.svg). To see how ready your codebase is, you can do a quick "
+"[eligibility self assessment](https://publiccodenet.github.io/assessment-"
+"eligibility) that will give you a rough idea of how much work you may need "
+"to do to meet all criteria."
+msgstr ""
+
+msgid "Update [`roadmap.md`](roadmap.md)"
+msgstr ""
+
+msgid ""
+"update `docs/standard-for-public-code.html` with the new text from the "
+"review template, updating any status changes as a result"
+msgstr ""
+
+msgid ""
+"Push branch, compare with 'main' branch, i.e.: "
+"`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+msgid "Separate executive summary (issue #302)"
+msgstr ""
+
+msgid ""
+"[Standard criteria checklist](/docs/review-template.html) used by Foundation"
+" for Public Code stewards for codebase review"
+msgstr ""

From 21f15659ab4e098e42a4f161dff6f1fbf662c265 Mon Sep 17 00:00:00 2001
From: Toomore <toomore@ocf.tw>
Date: Tue, 29 Aug 2023 08:13:56 +0000
Subject: [PATCH 42/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1048 of 1048 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 59 ++++++++++++++++---------
 1 file changed, 37 insertions(+), 22 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index c24ed681..9b5dd769 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,9 +3,10 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-08-28 10:25+0000\n"
-"Last-Translator: Wilt <interpreter.wilt@gmail.com>\n"
-"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
+"PO-Revision-Date: 2023-08-30 02:17+0000\n"
+"Last-Translator: Toomore <toomore@ocf.tw>\n"
+"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
+"standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -5923,51 +5924,51 @@ msgstr ""
 
 msgid ""
 "script/release-body.sh expects VERSION in the first second-level header"
-msgstr ""
+msgstr "script/release-body.sh 預期 VERSION 參數在首位第二階層的標頭"
 
 msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
-msgstr ""
+msgstr "script/update-changelog-date.sh 預期 DATE-OF-RELEASE 參數與一個冒號 \":\""
 
 msgid "Version 0.7.1"
-msgstr ""
+msgstr "Version 0.7.1"
 
 msgid ""
 "July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
 "clarifies references to code."
-msgstr ""
+msgstr "2023/07/31: 💄 第十六個草案版本變更準則名稱與釐清參照的程式碼。"
 
 msgid ""
 "The criterion \"Make the codebase reusable and portable\" was renamed from "
 "\"Create reusable and portable code\"."
-msgstr ""
+msgstr "準則從 \"編寫可重複使用與移植的程式碼\" 更名為 \"使代碼庫可重複使用與移植\"。"
 
 msgid "Added a glossary entry for \"Source Code\"."
-msgstr ""
+msgstr "新增詞彙為 \"原始碼\"。"
 
 msgid ""
 "References to \"code\" which only applied to \"source code\" now reference "
 "\"source code\" explicitly."
-msgstr ""
+msgstr "對於只適用於 \"原始碼\" 的 \"程式碼\"，現在明確的引用 \"原始碼\"。"
 
 msgid "Clarification of \"running code\" as \"software\"."
-msgstr ""
+msgstr "釐清 \"運作的程式碼\" 為 \"軟體\"。"
 
 msgid "Minor changes to clarify \"code\" vs \"codebase\"."
-msgstr ""
+msgstr "微調文字使其清楚呈現 \"程式碼\" 與 \"代碼庫\"。"
 
 msgid "Simplify guidance to policy makers in Bundle policy and source code."
-msgstr ""
+msgstr "簡易的引導參考給政策制定者在同捆政策與原始碼。"
 
 msgid ""
 "Clarify How to test sections of Make the codebase findable and Make the "
 "codebase reusable and portable."
-msgstr ""
+msgstr "解釋使代碼庫可被發現與使代碼庫可重複使用與移植在如何測試章節中。"
 
 msgid "Add a criteria and requirements checklist to the release artifacts."
-msgstr ""
+msgstr "新增發行成果前，判定標準與必要需求項目的確認清單。"
 
 msgid "Increase automation of the release process."
-msgstr ""
+msgstr "提高發行程序的自動化。"
 
 msgid ""
 "![version 0.7.1](assets/version-badge.svg) [![License: "
@@ -5976,6 +5977,10 @@ msgid ""
 "[![Standard commitment](assets/standard-for-public-code-"
 "commitment.svg)](#help-improve-this-standard)"
 msgstr ""
+"![version 0.7.1](assets/version-badge.svg) [![License: CC0-1.0](https://img."
+"shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/"
+"publicdomain/zero/1.0/) [![標準承諾](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
 
 msgid ""
 "If you want to apply the Standard for Public Code to your codebase, just go "
@@ -5988,30 +5993,40 @@ msgid ""
 "eligibility) that will give you a rough idea of how much work you may need "
 "to do to meet all criteria."
 msgstr ""
+"如果您想要採用公共程式標準於您的代碼庫中，請隨意使用，它是一個開放標準與免費"
+"給任何人使用。如果您希望推廣代碼庫社群期望達成公共程式標準的資格，請使用 "
+"[公共程式標準徽章](assets/standard-for-public-code-commitment.svg) 連結到此份"
+"承諾文件。了解您的代碼庫準備的如何，您可以透過[快速自我檢測](https://publicco"
+"denet.github.io/assessment-"
+"eligibility)粗略的瞭解您還需要準備多少才能符合所有的資格。"
 
 msgid "Update [`roadmap.md`](roadmap.md)"
-msgstr ""
+msgstr "更新 [`roadmap.md`](roadmap.md)"
 
 msgid ""
 "update `docs/standard-for-public-code.html` with the new text from the "
 "review template, updating any status changes as a result"
-msgstr ""
+msgstr "使用審查範本的新文字更新 `docs/standard-for-public-code."
+"html`，根據結果更新任何狀態"
 
 msgid ""
 "Push branch, compare with 'main' branch, i.e.: "
 "`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
 msgstr ""
+"推送分支，與 `main` 分支比較，如：`https://github.com/publiccodenet/standard/"
+"compare/main...release-$MAJOR.$MINOR.$PATCH`"
 
 msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
 
 msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
-msgstr ""
+msgstr "移除本地端的標籤（tag）：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
 
 msgid "Separate executive summary (issue #302)"
-msgstr ""
+msgstr "分離執行摘要 (issue #302)"
 
 msgid ""
 "[Standard criteria checklist](/docs/review-template.html) used by Foundation"
 " for Public Code stewards for codebase review"
-msgstr ""
+msgstr "[標準資格檢查清單](/docs/review-template.html) "
+"由公共程式基金會管理人員用於代碼庫審查"

From f9c3b586784113815b37b1159b164bcd8ecbc5d1 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Wed, 30 Aug 2023 05:59:09 +0000
Subject: [PATCH 43/71] update translate

---
 .gitignore                                    |   2 +-
 404.md                                        |   9 +-
 AUTHORS.md                                    |  43 +-
 CC0-1.0.md                                    |   4 +-
 CHANGELOG.md                                  | 479 +++++++++---------
 CODE_OF_CONDUCT.md                            |  13 +-
 CONTRIBUTING.md                               | 121 +++--
 GOVERNANCE.md                                 |  18 +-
 README.md                                     | 125 ++---
 _config.yml                                   |   4 +-
 criteria/bundle-policy-and-source-code.md     |  73 +--
 criteria/code-in-the-open.md                  |  61 ++-
 criteria/document-codebase-maturity.md        |  59 +--
 criteria/document-codebase-objectives.md      |  41 +-
 criteria/document-the-code.md                 |  66 +--
 criteria/index.md                             |   7 +-
 criteria/maintain-version-control.md          |  82 +--
 criteria/make-contributing-easy.md            |  59 +--
 criteria/make-the-codebase-findable.md        |  96 ++--
 ...make-the-codebase-reusable-and-portable.md | 100 ++--
 criteria/publish-with-an-open-license.md      |  69 +--
 criteria/require-review-of-contributions.md   |  88 ++--
 criteria/use-a-coherent-style.md              |  51 +-
 criteria/use-continuous-integration.md        |  97 ++--
 criteria/use-open-standards.md                |  53 +-
 criteria/use-plain-english.md                 |  68 +--
 criteria/welcome-contributors.md              |  80 +--
 docker.sh                                     |   5 +-
 docker/apache-data/000-default.conf           |  34 ++
 docs/printing.md                              |  30 +-
 docs/releasing.md                             |  77 +--
 docs/roadmap.md                               |  43 +-
 foreword.md                                   | 204 ++++----
 glossary.md                                   |  86 ++--
 index.md                                      |  65 +--
 origin_source/404.md                          |  15 +
 origin_source/AUTHORS.md                      |  37 ++
 origin_source/CC0-1.0.md                      |  19 +
 origin_source/CHANGELOG.md                    | 247 +++++++++
 origin_source/CODE_OF_CONDUCT.md              |  15 +
 origin_source/CONTRIBUTING.md                 | 103 ++++
 origin_source/GOVERNANCE.md                   |  18 +
 origin_source/README.md                       | 107 ++++
 .../criteria/bundle-policy-and-source-code.md |  56 ++
 origin_source/criteria/code-in-the-open.md    |  47 ++
 .../criteria/document-codebase-maturity.md    |  50 ++
 .../criteria/document-codebase-objectives.md  |  40 ++
 origin_source/criteria/document-the-code.md   |  53 ++
 origin_source/criteria/index.md               |  12 +
 .../criteria/maintain-version-control.md      |  60 +++
 .../criteria/make-contributing-easy.md        |  48 ++
 .../criteria/make-the-codebase-findable.md    |  70 +++
 ...make-the-codebase-reusable-and-portable.md |  76 +++
 .../criteria/publish-with-an-open-license.md  |  54 ++
 .../require-review-of-contributions.md        |  63 +++
 .../criteria/use-a-coherent-style.md          |  47 ++
 .../criteria/use-continuous-integration.md    |  70 +++
 origin_source/criteria/use-open-standards.md  |  46 ++
 origin_source/criteria/use-plain-english.md   |  56 ++
 .../criteria/welcome-contributors.md          |  62 +++
 origin_source/docs/printing.md                |  22 +
 origin_source/docs/releasing.md               |  39 ++
 origin_source/docs/roadmap.md                 |  33 ++
 origin_source/foreword.md                     | 177 +++++++
 origin_source/glossary.md                     |  86 ++++
 origin_source/index.md                        |  46 ++
 origin_source/readers-guide.md                |  72 +++
 python/po2md.py                               | 102 ++++
 python/update_po.py                           |  34 ++
 readers-guide.md                              |  84 ++-
 70 files changed, 3419 insertions(+), 1259 deletions(-)
 create mode 100644 docker/apache-data/000-default.conf
 create mode 100644 origin_source/404.md
 create mode 100644 origin_source/AUTHORS.md
 create mode 100644 origin_source/CC0-1.0.md
 create mode 100644 origin_source/CHANGELOG.md
 create mode 100644 origin_source/CODE_OF_CONDUCT.md
 create mode 100644 origin_source/CONTRIBUTING.md
 create mode 100644 origin_source/GOVERNANCE.md
 create mode 100644 origin_source/README.md
 create mode 100644 origin_source/criteria/bundle-policy-and-source-code.md
 create mode 100644 origin_source/criteria/code-in-the-open.md
 create mode 100644 origin_source/criteria/document-codebase-maturity.md
 create mode 100644 origin_source/criteria/document-codebase-objectives.md
 create mode 100644 origin_source/criteria/document-the-code.md
 create mode 100644 origin_source/criteria/index.md
 create mode 100644 origin_source/criteria/maintain-version-control.md
 create mode 100644 origin_source/criteria/make-contributing-easy.md
 create mode 100644 origin_source/criteria/make-the-codebase-findable.md
 create mode 100644 origin_source/criteria/make-the-codebase-reusable-and-portable.md
 create mode 100644 origin_source/criteria/publish-with-an-open-license.md
 create mode 100644 origin_source/criteria/require-review-of-contributions.md
 create mode 100644 origin_source/criteria/use-a-coherent-style.md
 create mode 100644 origin_source/criteria/use-continuous-integration.md
 create mode 100644 origin_source/criteria/use-open-standards.md
 create mode 100644 origin_source/criteria/use-plain-english.md
 create mode 100644 origin_source/criteria/welcome-contributors.md
 create mode 100644 origin_source/docs/printing.md
 create mode 100644 origin_source/docs/releasing.md
 create mode 100644 origin_source/docs/roadmap.md
 create mode 100644 origin_source/foreword.md
 create mode 100644 origin_source/glossary.md
 create mode 100644 origin_source/index.md
 create mode 100644 origin_source/readers-guide.md
 create mode 100644 python/po2md.py
 create mode 100644 python/update_po.py

diff --git a/.gitignore b/.gitignore
index a205baba..309a1bf3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,4 +12,4 @@ urls.txt
 release.body
 *.orig
 node_modules/
-package-lock.json
+package-lock.json
\ No newline at end of file
diff --git a/404.md b/404.md
index 7a4a22bd..44827764 100644
--- a/404.md
+++ b/404.md
@@ -6,10 +6,11 @@ title: Page not found
 toc: false
 ---
 
-# 404 Not Found
+# 404 找不到網頁
 
-If you typed the web address, check it is correct.
+如果您手動輸入網址，請確認網址是否正確。
 
-If you pasted the web address, check you copied the entire address.
+如果您複製貼上此網址，請確認是否有複製到完整的網址。
 
-If the web address is correct or you followed a link or button, email the [Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be able to help you out, as well as correct our mistake.
+若網址正確或是您按下連結或按鈕，請寫信給 [the Foundation for Public Code 人
+員](mailto:info@publiccode.net)，讓我們能夠協助您，並且修正我們的錯誤。
diff --git a/AUTHORS.md b/AUTHORS.md
index ef7f3f3a..17f1e782 100644
--- a/AUTHORS.md
+++ b/AUTHORS.md
@@ -2,36 +2,39 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
-# Authors
 
-* Alba Roza, [The Foundation for Public Code](https://publiccode.net/)
+# 作者群
+
+* Alba Roza，[The Foundation for Public Code](https://publiccode.net/)
 * Arnout Engelen
-* Arnout Schuijff, The Foundation for Public Code
-* Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)
-* Ben Cerveny, The Foundation for Public Code
+* Arnout Schuijff，The Foundation for Public Code
+* 唐鳳，[digitalminister.tw](https://digitalminister.tw/)
+* Ben Cerveny，The Foundation for Public Code
 * Bert Spaan
-* Boris van Hoytema, The Foundation for Public Code
+* Boris van Hoytema，The Foundation for Public Code
 * Charlotte Heikendorf
-* Claus Mullie, The Foundation for Public Code
+* Claus Mullie，The Foundation for Public Code
 * David Barberi
-* Edo Plantinga, [Code For NL](https://codefor.nl/)
-* Elena Findley-de Regt, The Foundation for Public Code
-* Eric Herman, The Foundation for Public Code
-* Felix Faassen, The Foundation for Public Code
+* Edo Plantinga，[Code For NL](https://codefor.nl/)
+* Elena Findley-de Regt，The Foundation for Public Code
+* Eric Herman，The Foundation for Public Code
+* Felix Faassen，The Foundation for Public Code
 * Floris Deerenberg
-* Jan Ainali, The Foundation for Public Code
-* Johan Groenen, Code For NL
+* Jan Ainali，The Foundation for Public Code
+* Johan Groenen，Code For NL
 * Marcus Klaas de Vries
-* Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)
-* Martijn de Waal, [Amsterdam University of Applied Sciences (AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and Creative Industries, Lectorate of Play & Civic Media
+* Mark van der Net，[阿姆斯特丹市政府](https://www.amsterdam.nl/en/)
+* Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas.com/)，數位媒體與創意產業學院劇
+場與公民媒體系講師
 * Matti Schneider
 * Mauko Quiroga
-* Maurice Hendriks, Gemeente Amsterdam
-* Maurits van der Schee, Gemeente Amsterdam
-* Mirjam van Tiel, The Foundation for Public Code
+* Maurice Hendriks， 阿姆斯特丹市政府
+* Maurits van der Schee，阿姆斯特丹市政府
+* Mirjam van Tiel，The Foundation for Public Code
 * Ngô Ngọc Đức Huy
 * Paul Keller
-* Petteri Kivimäki, [Nordic Institute for Interoperability Solutions (NIIS)](https://niis.org)
+* Petteri Kivimäki， [Nordic Institute for Interoperability Solutions
+(NIIS)](https://niis.org)
 * Sky Bristol
-* Tamas Erkelens, Gemeente Amsterdam
+* Tamas Erkelens，阿姆斯特丹市政府
 * Timo Slinger
diff --git a/CC0-1.0.md b/CC0-1.0.md
index 7cadbfc4..26de1d12 100644
--- a/CC0-1.0.md
+++ b/CC0-1.0.md
@@ -7,12 +7,12 @@ redirect_from:
     - LICENSE.html
 ---
 
-# Creative Commons Zero v1.0 Universal
+# Creative CC Zero v1.0 Universal 授權
 
 <!-- TODO FIXME: move styling to the proper place, not inline html -->
 <style>.highlight { flex: 2 2 80%; max-width: 100%; } </style>
 
-This license is the legal contract that allows anyone to do anything they like with the content in this entire document.
+此授權為法律合約，允許任何人任意使用本文件任何內容。
 
 ```text
 {% include_relative LICENSE %}
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8464dc27..dcebd58d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,244 +4,247 @@
 # script/release-body.sh expects VERSION in the first second-level header
 # script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon
 ---
-# Version history
+# 版本歷史
 
 ## Version 0.7.1
 
-July 31st 2023: 💄 The sixteenth draft change the name of a criterion and clarifies references to code.
-
-* The criterion "Make the codebase reusable and portable" was renamed from "Create reusable and portable code".
-* Added a glossary entry for "Source Code".
-* References to "code" which only applied to "source code" now reference "source code" explicitly.
-* Clarification of "running code" as "software".
-* Minor changes to clarify "code" vs "codebase".
-* Simplify guidance to policy makers in Bundle policy and source code.
-* Clarify How to test sections of Make the codebase findable and Make the codebase reusable and portable.
-* Add a criteria and requirements checklist to the release artifacts.
-* Increase automation of the release process.
-
-## Version 0.7.0
-
-May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting review funding and clarifies review process requirement.
-
-* Add requirement to document who is expected to cover the cost of reviewing contributions.
-* Add requirement to have a short description of the codebase.
-* Change the focus of contributions adhering to standards to focus on the review of contributions.
-* Relaxed MUST requirements to SHOULD in Make the codebase findable.
-* Review template now in HTML format.
-* Introduction converted to foreword.
-* Improved contributing guidelines.
-* Improved documentation of scripts.
-
-## Version 0.6.0
-
-April 20th 2023: 🔀 the fourteenth draft adds new requirements for portability and tests and an introduction to each criterion.
-
-* New requirement in Create reusable and portable code about the development being a collaboration between multiple parties.
-* New requirement in Create reusable and portable code about being dependent on a single vendor.
-* New requirement in Use continuous integration about publishing results for automated tests.
-* Differentiating the two requirements about security to clearly be about providing a method and having documentation about it.
-* Rephrased requirements to focus on the codebase rather than contributor behavior.
-* Removed the sections Why this is important and What this does not do and replaced with an introduction in each criterion.
-* Added general What this does not do section in the introduction of the Standard.
-* Added guidance for public policy makers about related policies and license compatibility.
-* Added guidance for developers and designers about version controlling files.
-* Clarified guidance for developers and designers about prompt responses and search engine optimization.
-* Added Further reading about accessibility.
-* Aligned criteria URLs with criteria names.
-* Improved navigation in the web version.
-* Moved tools in Further reading sections to the community implementation guide.
-* Moved compliance or certification process to [publiccode.net](https://publiccode.net).
-* Change format of the review template to make it easier to update after a new release.
-* Improved the text on the landing page and added links to related resources.
-* Added spell checker automated test.
-* Made minor changes to text for clarity and consistency.
-* Moved SPDX headers to yaml header.
-
-## Version 0.5.0
-
-January 25th 2023: 🎨 the thirteenth draft focuses on documenting style guidelines.
-
-* Adjust the coding style requirement to focus on the codebase using a style guide rather than contributor behavior.
-* Moved requirement for codebase names to Make the codebase findable from Use plain English.
-* Moved requirement about testing the code by using examples to Use continuous integration from Document the code.
-* Split requirement about machine testable standards to clarify that open is more important than testable.
-* Adjust how to test findability requirements to be less reliant on search engine algorithms.
-* Made minor changes to text for clarity and consistency.
-
-## Version 0.4.1
-
-December 5th 2022: 📝 the twelfth draft clarifies document maturity.
-
-* Document maturity focuses on whether or not versions of the codebase are ready to use.
-* Document maturity no longer requires specific labels for codebases that are not ready to use.
-* Audit flow image now generated from an easier to translate format.
-* Improved guidance on How to test.
-* Add publiccode.yml file.
-* Add review template.
-* Consistently link glossary terms.
-* Add practices and standards to follow in CONTRIBUTING.
-* Add Matti Schneider to Authors.
-* Add remaining SPDX headers to files.
-* Made additional minor changes to text for clarity.
-* Some hyperlinks updated.
-* Moved examples to the [Community implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/).
-
-## Version 0.4.0
-
-September 7th 2022: 🔭 the eleventh draft adds a new findability criterion.
-
-* Introduce new criterion: Make the codebase findable.
-* Improve How to test section for most criteria.
-* New requirement in Welcome contributors about publishing activity statistics.
-* Removed redundant requirement about portable and reusable code.
-* Expand open license definition to include both OSI and FSF approved licenses.
-* Rephrase MAY requirements to use the keyword OPTIONAL for clarity.
-* Expressed intent that the Standard for Public Code should meet its own requirements where applicable and added assessment.
-* Add SPDX license identifiers to files.
-* Introduced new Code of Conduct.
-* Clarify distinction between source code and policy text.
-* Restructuring of requirements with bullet point lists.
-* Acknowledge the importance of codebase modularity for reuse.
-* Move requirements related to Findability to the new criterion.
-* Clarify the role of non-open standards when used in a codebase.
-* Additional guidance about build-time and runtime dependencies.
-* Added roadmap for the development of the Standard for Public Code.
-* Update structure of Authors file.
-* Add Audrey Tang to Authors.
-* Added a list of criteria to the print edition.
-* Clarify what the standard means with policymakers, managers, developers and designers.
-* Made additional minor changes to text for clarity.
-* Some hyperlinks updated.
-
-## Version 0.3.0
-
-May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization.
-
-* Requirement for localization made explicit in Create reusable and portable code.
-* Documentation of governance changed from a SHOULD to a MUST.
-* Replace the very subjective (and hard to test) "contributions MUST be small" with requirement to document expectation in contributing guidelines and focus on a single issue.
-* Community translations now linked in the footer.
-* Revert "Replace BPMN svg with Mermaid flowchart".
-* Many minor clarifications to language and sentences made more simple.
-* Some hyperlinks updated.
-
-## Version 0.2.3
-
-March 15th 2022: 📜 the ninth draft allows English summaries for policy lacking an official translation.
-
-* Relax the criterion Use plain English by adding a new requirement allows bundled policy not available in English to have an accompanying summary in English instead of translating the full text.
-* Similarly, allow for English summaries for policies not available in English in Bundle policy and code.
-* Clarify that term 'policy' includes processes which impact development and deployment in Bundle policy and code.
-* Emphasize reusability also on parts of the solutions in Create reusable and portable code.
-* Expand guidance to Developers and designers in Create reusable and portable code about deploying to proprietary platforms.
-* Add nuance to use of non-English terms in what management need to do in Use plain English.
-* Change the pull request process diagram to use Mermaid instead of BPMN to make [community translations](https://github.com/publiccodenet/community-translations-standard) easier.
-* Added Maurice Hendriks to AUTHORS.
-* Added OpenApi Specification to further reading.
-* Made the attributions in further reading sections clearer.
-* Made additional minor changes to text for clarity.
-
-## Version 0.2.2
-
-November 29th 2021: 🏛 the eighth draft recognizes that policy which executes as code may not be in English.
-
-* Document exception to "All code MUST be in English" where policy is interpreted as code.
-* Add MAY requirement regarding committer email addresses in Maintain version control.
-* Expand guidance to Policy Makers in Bundle policy and code.
-* Expand guidance to Developers and designers in Use a coherent style.
-* Add "Different contexts" to glossary.
-* Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS.
-* Add Digital Public Goods approval badge.
-* Added "next" and "previous" links to criteria pages of web version.
-* Add Open Standards principles to further reading.
-* Add Definition of plain language to further reading.
-* Move the Semantic Versioning Specification further reading reference.
-* Clarify that publiccode.yml is one example of a machine-readable metadata description.
-* Changed "your codebase" and "your organization" to be less possessive.
-* Made additional minor changes to text for clarity.
-* Add instructions for creating a print version.
-
-## Version 0.2.1
-
-March 1st 2021: 🧽 the seventh draft has minor cleaning up after version 0.2.0.
-
-* New SHOULD requirement on using a distributed version control system and why distributed is important.
-* Feedback requirements for rejected contributions are more strict than accepted ones.
-* Specify that copyright and license notices should also be machine-readable.
-* Advice on how to test that notices be machine-readable.
-* Clarify guidance for rolling releases.
-* Clear up definition of version control in glossary.
-* Add further reading encouraging contribution, SPDX, Git and reviewing contributions.
-* Add links to videos about the concept of public code.
-* Update BPMN link.
-* Reduce link duplication.
-* Add Alba Roza and Ngô Ngọc Đức Huy to authors.
-* Made additional minor changes to text for clarity.
-
-## Version 0.2.0
-
-October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity.
-
-* Split "Welcome contributions" criterion into "Make contributing easy" and "Welcome contributors".
-* Rename criterion "Pay attention to codebase maturity" to "Document codebase maturity".
-* Changed MUST to SHOULD for requirement of codebase in use by multiple parties.
-* Add MUST NOT requirement regarding copyright assignment.
-* Clarify role of configuration in reusable code requirement.
-* Glossary additions: continuous integration, policy, repository, and version control.
-* Replace references to 'cities' with 'public organizations'.
-* Clarify aspects of sensitive code by separating contributor and reviewer requirements into separate items.
-* Expand further reading, and guidance to policy makers, developers and designers.
-* Add Felix Faassen and Arnout Engelen to authors.
-* Made additional minor changes to text for clarity.
-
-## Version 0.1.4
-
-November 27th 2019: 🧹 the fifth draft consists mostly of additional minor fixes.
-
-* Linked License.md file.
-* Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors.
-* Made punctuation more consistent, especially for bullet lists.
-* Made some minor changes to text for clarity.
-
-## Version 0.1.3
-
-October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for the autumn cleaning
-
-* Renamed continuous delivery to continuous integration.
-* Referencing accessibility guidelines in the language standard.
-* A bunch of style and consistency fixes.
-
-## Version 0.1.2
-
-August 22th 2019: 🌠 the third draft focuses on better text and takes community input
-
-* With some great new contributors comes a fresh author list.
-* All links are now HTTPS.
-* General proofreading, wording clarifications, and smashed typos.
-* Updated criteria:
-  * Requirement for reuse in different contexts
-  * Recommendation for explicit versioning
-  * Recommendation for multi party development
-  * Recommendation for license headers in files
-  * Recommendation for vulnerability reporting
-  * Recommendation for explicit documentation of governance
-
-## Version 0.1.1
-
-May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a lot of typos
-
-* Removed references to the Foundation for Public Code, we're going to have to change the name in becoming an association.
-* Updated the introduction.
-* Updated the glossary.
-* Added the code of conduct.
-* We've recommended using the publiccode.yml standard for easier reuse.
-
-## Version 0.1.0
-
-April 16th 2019: 🎉 the first draft is ready, it is all brand new and has snazzy new ideas in it
-
-* 14 criteria with their requirements and how to operationalize them.
-* An introduction with a high level background, what this standard is, and how the Foundation for Public Code will use it.
-
-This first version was produced together with the Amsterdam University of Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? Public Code! project](https://smartcities.publiccode.net/).
+2023/07/31: 💄 第十六個草案版本變更準則名稱與釐清參照的程式碼。
+
+* 準則從 "編寫可重複使用與移植的程式碼" 更名為 "使代碼庫可重複使用與移植"。
+* 新增詞彙為 "原始碼"。
+* 對於只適用於 "原始碼" 的 "程式碼"，現在明確的引用 "原始碼"。
+* 釐清 "運作的程式碼" 為 "軟體"。
+* 微調文字使其清楚呈現 "程式碼" 與 "代碼庫"。
+* 簡易的引導參考給政策制定者在同捆政策與原始碼。
+* 解釋使代碼庫可被發現與使代碼庫可重複使用與移植在如何測試章節中。
+* 新增發行成果前，判定標準與必要需求項目的確認清單。
+* 提高發行程序的自動化。
+
+## 0.7.0 版
+
+2023年5月31日：📑第十五版新增募資審查紀錄新規定，並且釐清審查流程規定。
+
+* 新增規定，紀錄由誰負擔審核貢獻內容費用。
+* 新增規定，代碼庫必須要有簡短說明。
+* 原本專注在貢獻內容是否符合標準，現在應該專注在貢獻內容審查。
+* 許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到。
+* 審查HTML格式的範本。
+* 「簡介」轉變為「序」。
+* 已改善貢獻指南。
+* 已改善腳本註解。
+
+## 0.6.0 版
+
+2023年4月20日：🔀第十四版新增可移植性與測試的規定，並且介紹每個標準。
+
+* 新增規定，針對多方合作的開發案來編寫可重複使用且可移植的程式碼。
+* 新增規定，針對依賴單一供應商編寫可重複使用且可移植的程式碼。
+* 新增規定，公布自動化測試結果時，必須使用持續整合。
+* 區分兩個安全性規定，一個是有關提供辦法，另一個則是有關安全性的註解。
+* 已重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。
+* 已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。
+* 在標準簡介中，已新增「不具備以下作用」段落。
+* 已新增有關相關政策與授權相容性的公共政策決策者指南。
+* 已新增有關版本控制檔案的開發人員與設計師指南。
+* 已釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。
+* 已新增「進一步閱讀無障礙」。
+* 已將各標準的連結與其名稱同步。
+* 已改善網頁版的導覽功能。
+* 已將「進一步閱讀」章節的工具移到社群實施指南。
+* 已將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。
+* 變更審查範本格式，讓範本在新版本推出後後更容易更新。
+* 已改善到達網頁文字，加入相關資源的連結。
+* 已新增拼字檢查自動化測試。
+* 已稍微調整文字，讓文字更明確與一致。
+* 將 SPDX 標頭換成 yaml 標頭。
+
+## 0.5.0 版
+
+2023年1月25日：🎨第十三版焦點在於紀錄風格指南。
+
+* 調整編碼風格要求，專注在代碼庫上面，而非貢獻者行為。
+* 已變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。
+* 已變更使用範例測試程式碼的規定，改為使用「Document the code」的範例來持續整合測試。
+* 調整機讀標準規定，強調程式碼的開放性比可測試性更重要。
+* 調整可查找性的測試規定，減少對搜尋引擎演算法的依賴。
+* 已稍微調整文字，讓文字更明確與一致。
+
+## 0.4.1 版
+
+2022年12月5日：📝第十二版闡明文件成熟度。
+
+* 文件成熟度端看該版本的代碼庫是否已經可以使用。
+* 文件成熟度不再仰賴尚無法使用的代碼庫中的特定標籤。
+* 審計流程圖現在的由更容易轉譯的格式來生成。
+* 改善「測試方式」指南。
+* 新增 publiccode.yml 檔案。
+* 新增審查範本。
+* 一致連結詞彙。
+* 在「貢獻」中新增的實務與標準。
+* 加入 Matti Schneider 到作者群。
+* 將剩餘 SPDX 標頭加入檔案中。
+* 稍微修改文字，讓文字更明確。
+* 已更新部分超連結。
+* 已將範例移動到[社群實施指
+南](https://publiccodenet.github.io/community-implementation-guide-standard/)。
+
+## 0.4.0 版
+
+2022年9月7日：🔭第十一版新增全新的可查找性標準。
+
+* 推出新標準：使代碼庫變得容易查找。
+* 改善多數標準的「測試方式」章節。
+* 「歡迎貢獻者」章節中有關發佈活動統計的新規定。
+* 已移除有關可移植與可重複使用的程式碼的多餘規定。
+* 在開放授權的定義中，加入 OSI 與 FSF 認證的授權。
+* 重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定更明確。
+* 已表明 The Standard for Public Code 標準在適用時應該符合自身規定，且已新增評估。
+* 將 SPDC license identifier 加入檔案中。
+* 已推出新行為守則。
+* 解釋原始碼與政策內文的差異。
+* 將規定改為要點清單的格式。
+* 承認代碼庫成熟度在重複使用上的重要性。
+* 將可查找性相關規定移動到新標準。
+* 釐清非開放性標準在代碼庫中的角色。
+* 關於建制時期與執行階段相依性的額外指南。
+* 新增 The Standard for Public Code 開發路徑圖。
+* 更新作者檔案結構。
+* 將唐鳳加入作者群。
+* 已新增標準清單到印刷版本中。
+* 釐清標準對政策制定者、管理者、開發人員與設計師的意義。
+* 稍微修改文字，讓文字更明確。
+* 已更新部分超連結。
+
+## 0.3.0 版
+
+2022年5月23日：🗎第十版加強註解與本土化。
+
+* 「編寫可重複使用與可移植程式碼」章節有明確的本土化規定。
+* 治理註解從「應該（Should）」變成「必須（Must）」。
+* 在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必須紀錄貢獻的期望，專注在單一議題上。
+* 社群翻譯現在已連結到頁尾中。
+* 還原「用 Mermaid 流程圖取代 BPMN svg」。
+* 細微調整用詞，讓句子更簡單。
+* 已更新部分超連結。
+
+## 0.2.3 版
+
+2022年3月15日：📜第九版允許在沒有官方翻譯的政策中加入英文版摘要。
+
+* 放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入英文版摘要，不用翻譯全文。
+* 同樣地，允許同捆政策與程式碼當中沒有英文版的政策只提供英文版摘要。
+* 釐清「政策」包括能影響同捆政策與程式碼開發與部署的流程。
+* 強調「編寫可重複使用與移植的程式碼」解決方案部分內容的可重複使用性。
+* 將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到不同專屬平台的內容。
+* 在「使用簡單英文」中，加入管理人員需要使用的非英文詞彙。
+* 變更拉取請求流程圖，從 BPMN 改用 Mermaid，讓[社群翻
+譯](https://github.com/publiccodenet/community-translations-standard)更容易。
+* 將 Maurice Hendriks 加入作者群。
+* 將「OpenApi 規格」加入「深入閱讀」。
+* 將「深入閱讀」當中的歸因變得更明確。
+* 稍微修改文字，讓文字更明確。
+
+## 0.2.2 版
+
+2021年11月29日：🏛第八版承認當作程式碼來執行的政策，不一定是英文。
+
+* 標示當政策被詮釋為程式碼時，則不用遵守「僅限英文程式碼」的規則。
+* 在「版本管控」中，新增關於提交者電子郵件的「得以（May）」規定。
+* 將政策制定者加入「同捆政策與程式碼」指南。
+* 將開發人員與設計師加入「風格一致」指南。
+* 新增「不同脈絡」到詞彙表中。
+* 將 Mauko Quiroga 與 Charlotte Heikendorf 加入作者群。
+* 新增「數位公共財」認證標章。
+* 加入網頁版「標準」頁面的「上一頁」與「下一頁」連結。
+* 將「開放標準原則」加入「深入閱讀」。
+* 將「簡單語言定義」加入「深入閱讀」。
+* 移動「語意化版本規格」引用的「深入閱讀」。
+* 釐清 publiccode.yml 是描述機讀元資料的名稱之一。
+* 將「您的代碼庫」與「貴組織」改為較不具有所有格的寫法。
+* 稍微修改文字，讓文字更明確。
+* 新增印刷版的建立說明。
+
+## 0.2.1 版
+
+2021年3月1日：🧽跟 0.2.0 版相較之下，第七版做了些微改善。
+
+* 針對使用分散版本控制系統制定新的「應該」規定，並解釋分散的重要性。
+* 針對被拒絕的貢獻的回饋，比被接受的貢獻的回饋規定更嚴苛。
+* 明確指出著作權與授權聲明也應該要可機讀。
+* 聲明是否為可機讀的測試方式建議。
+* 釐清滾動發行的指南。
+* 釐清詞彙表中「版本控制」的定義。
+* 新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git 以及審查貢獻。
+* 新增有關公共程式概念的影片連結。
+* 更新 BPMN 連結。
+* 減少重複連結。
+* 將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。
+* 稍微修改文字，讓文字更明確。
+
+## 0.2.0 版
+
+2020年10月26日：🎊第六版分拆一項規定並且釐清內容。
+
+* 將「歡迎貢獻」標準分拆為「讓貢獻更容易」以及「歡迎貢獻者」。
+* 將「注意代碼庫成熟度」標準改名為「註解代碼庫成熟度」。
+* 針對多方使用的代碼庫，將「必須（Must）」規定調整為「應該（Should）」規定。
+* 針對著作權讓與，新增「不得（Must Not）」規定。
+* 在可重複使用程式碼規定中，釐清組態的角色。
+* 新增詞彙：持續整合、政策、儲存庫與版本控制。
+* 將「城市」都替換成「公共組織」。
+* 將貢獻者與審查規定分開，藉此釐清程式碼敏感的地方。
+* 將政策制定者、開發人員與設計師加入「深入閱讀」與指南中。
+* 將 Felix Faassen 與 Arnout Engelen 加入作者群。
+* 稍微修改文字，讓文字更明確。
+
+## 0.1.4 版
+
+2019年11月27日：🧹第五版主要內容是額外的細部修復。
+
+* 已連結 License.md 檔案。
+* 將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。
+* 讓標點符號更連貫，特別是項目符號列表。
+* 細部調整文字，讓內容更明確。
+
+## 0.1.3 版
+
+2019年10月8日：🍂第四版僅針對秋季的清理修復小問題
+
+* 將「持續交付」改名為「持續整合」。
+* 在語言標準中引述無障礙指導原則。
+* 改善樣式與一致性。
+
+## 0.1.2 版
+
+2019年8月22日：🌠第三版專注在提升文字品質，並且傾聽社群的意見
+
+* 一群很棒的貢獻者，讓我們作者群加入許多新血。
+* 所有連結都是 HTTPS。
+* 一般校對、釐清用字與修改拼字錯誤。
+* 已更新標準：
+   * 在不同脈絡下重複使用的規定
+   * 明確版本控制建議
+   * 多方部署建議
+   * 檔案授權標頭建議
+   * 漏洞回報建議
+   * 明確治理註解建議
+
+## 0.1.1 版
+
+2019年5月9日：🤔第二版修復基本的疏忽以及許多拼字錯誤
+
+* 移除出現「The Foundation for Public Code」的地方，我們必須改名才能成為協會。
+* 已更新前言。
+* 已更新詞彙表。
+* 已新增行為守則。
+* 我們建議使用 publiccode.yml 標準，方便重複使用。
+
+## 0.1.0 版
+
+2019年4月16日：🎉初版已經就緒，內容全新且有許多有趣的全新構想
+
+* 14個標準、其規定以及實施方式。
+* 清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code 會如何使用此標準。
+
+第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於[Smart Cities? Public Code! 專
+案](https://smartcities.publiccode.net/)。
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index b63243fd..c85c357a 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,15 +1,14 @@
-# Code of Conduct
+# 行為守則
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-Many community members are from civic or professional environments with behavioral codes yet some individuals are not.
-This document expresses expectations of all community members and all interactions regardless of communication channel.
+社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基金會對所有社群成員以及互動的期望，不論透過何種溝通管道。
 
-Be here to collaborate.
+到這裡來是為了協作。
 
-Be considerate, respectful, and patient.
+對彼此體貼、尊重以及有耐心。
 
-Strive to be as constructive as possible.
+努力做出建設性的貢獻。
 
-To raise a concern, please email directors@publiccode.net.
+若有問題，請寄送電子郵件到 directors@publiccode.net。
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 07c6fbab..5acbd508 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,103 +1,98 @@
-# Contributing to this standard
+# 貢獻給此標準
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-🙇‍♀️ Thank you for contributing!
+🙇‍♀️ 感謝您的貢獻！
 
-We understand that a standard like this can only be set in collaboration with as many public technologists, policy makers and interested folk as possible.
-Thus we appreciate your input, enjoy feedback and welcome improvements to this project and are very open to collaboration.
+我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。
 
-We love issues and pull requests from everyone.
-If you're not comfortable with GitHub, you can email use your feedback at <info@publiccode.net>.
+我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，歡迎將意見用電子郵件傳送到
+[info@publiccode.net](mailto:info@publiccode.net)。
 
-## Problems, suggestions and questions in issues
+## 問題、建議與議題中的問題
 
-A high-level overview of the development that we already have sketched out can be seen in the [roadmap](/docs/roadmap.md).
-Please help development by reporting problems, suggesting changes and asking questions.
-To do this, you can [create a GitHub issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue) for this project in the [GitHub Issues for the Standard for Public Code](https://github.com/publiccodenet/standard/issues).
+[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以及發問，幫助推動本開發案。您可以到[GitHub 的The
+Standard for Public Code 議題](https://github.com/publiccodenet/standard/issues)頁面
+中，為此專案[在 GitHub 上建立議
+題](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue)。
 
-Or, sign up to the [mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) and send an email to
-[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net).
+或者加入[郵寄清
+單](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)
+並且傳送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。
 
-You don't need to change any of our code or documentation to be a contributor!
+不需要修改我們的程式碼或註解也能成為貢獻者！
 
-## Documentation and code in pull requests
+## 拉入請求中的註解與程式碼
 
-If you want to add to the documentation or code of one of our projects you should make a pull request.
+如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出拉入請求。
 
-If you never used GitHub, get up to speed with [Understanding the GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) or follow one of the great free interactive courses in [GitHub Skills](https://skills.github.com/) on working with GitHub and working with MarkDown, the syntax this project's documentation is in.
+若您從未使用過 GitHub，歡迎先[認識 GitHub
+flow](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加[GitHub
+Skills](https://skills.github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 MarkDown（本專案註解
+所使用的語法）。
 
-This project is licensed Creative Commons Zero v1.0 Universal, which essentially means that the project, along with your contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it.
+本專案獲得 Creative CC Zero v1.0 Universal 授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。
 
-### 1. Make your changes
+### 1. 作出變更
 
-Contributions should [follow](docs/standard-for-public-code.html) the requirements set out in the criteria of the Standard for Public code itself.
-Reviewers will also be ensuring that contributions are aligned with the [values of public code](foreword.md#values-of-public-code).
-Furthermore, they will review that the contribution conforms to the [standards](#standards-to-follow) and remains coherent with the overall work.
+貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public Code 當中列出的標準。審
+查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否符合[標
+準](#standards-to-follow)且與整體專案有連貫。
 
-This project uses the [GitFlow branching model and workflow](https://nvie.com/posts/a-successful-git-branching-model/).
-When you've forked this repository, please make sure to create a feature branch following the GitFlow model.
+本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-model/)。當
+您複製了此存放庫，請務必依照 GitFlow 模型建立功能分支。
 
-Add your changes in commits [with a message that explains them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message).
-If more than one type of change is needed, group logically related changes into separate commits.
-For example, white-space fixes could be a separate commit from text content changes.
-When adding new files, select file formats that are easily viewed in a `diff`, for instance, `.svg` is preferable to a binary image.
-Document choices or decisions you make in the commit message, this will enable everyone to be informed of your choices in the future.
+將您變更內容加入到提交版本[並且附上說
+明](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)。如果需要不
+只一種變更，將相關變更分類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格
+式。像是「svg」格式就勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選擇。
 
-If you are adding code, make sure you've added and updated the relevant documentation and tests before you submit your pull request.
-Make sure to write tests that show the behavior of the newly added or changed code.
+如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請務必用文字描述新增或修改後的程式碼的作用。
 
-#### Applicable policy
+#### 適用政策
 
-Currently, the Standard for Public Code is not implementing any specific public policy.
+The Standard for Public Code 目前沒有執行任何特定的公共政策。
 
-#### Style
+#### 風格
 
-The Standard for Public Code aims to [use plain English](criteria/use-plain-english.md) and we have chosen American English for spelling.
-Text content should typically follow one line per sentence, with no line-wrap, in order to make `diff` output easier to view.
-However, we want to emphasize that it is more important that you make your contribution than worry about spelling and typography.
-We will help you get it right in our review process and we also have a separate quality check before [making a new release](docs/releasing.md).
+The Standard for Public Code 目標是[使用白話的英語](criteria/use-plain-english.md)，拼字採用美式英文。
+文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修正這一部分，
+也會另外再次檢查品質才[推出新版本](docs/releasing.md)。
 
-#### Standards to follow
+#### 遵守的標準
 
-These are the standards that the Standard for Public Code uses.
-Please make sure that your contributions are aligned with them so that they can be merged more easily.
+這些是 The Standard for Public Code 所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。
 
-* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level keywords
-* [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability
+* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 必要層級關鍵字
+* [網頁無障礙性指導原則 2.1](https://www.w3.org/TR/WCAG21/#readable) - 可讀性
 
-### 2. Pull request
+### 2. 拉入請求
 
-When submitting the pull request, please accompany it with a description of the problem you are trying to solve and the issue number that this pull request fixes.
-It is preferred for each pull request to address a single issue where possible.
-In some cases a single set of changes may address multiple issues, in which case be sure to list all issue numbers fixed.
+提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議題編號。
 
-### 3. Improve
+### 3. 改善
 
-All contributions have to be reviewed by someone.
-The Foundation for Public Code has committed to make sure that maintainers are available to review contributions with an aim to provide feedback within two business days.
+所有貢獻都必須接受審查。The Foundation for Public Code 承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。
 
-It could be that your contribution can be merged immediately by a maintainer.
-However, usually, a new pull request needs some improvements before it can be merged.
-Other contributors (or helper robots) might have feedback.
-If this is the case the reviewing maintainer will help you improve your documentation and code.
+維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人員，將負責協
+助改善您的註解與程式碼。
 
-If your documentation and code have passed human review, it is merged.
+若您的註解與程式碼通過人工審查，就會被合併。
 
-### 4. Celebrate
+### 4. 慶祝
 
-Your ideas, documentation and code have become an integral part of this project.
-You are the open source hero we need!
+您的構思、註解與程式碼將成為本專案的一部份。您就是我們所需要的開源英雄！
 
-In fact, feel free to open a pull request to add your name to the [`AUTHORS`](AUTHORS.md) file and get eternal attribution.
+歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS.md)檔案中，您的名字可以永遠留在本專案中。
 
-## Translations in other languages
+## 其他語言的翻譯
 
-While the Standard does not have any official translations, you can help maintain existing and add new [community translations of the Standard](https://github.com/publiccodenet/community-translations-standard).
+The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增[The Standard for Public Code 社
+群翻譯](https://github.com/publiccodenet/community-translations-standard)。
 
-## Releases
+## 出版
 
-We have dedicated documentation for creating [new releases](/docs/releasing.md) and [ordering printed standards](/docs/printing.md).
+建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing.md)有專用註解。
 
-For more information on how to use and contribute to this project, please read the [`README`](README.md).
+若要進一步瞭解如何使用與貢獻本專案，請參閱 [`README `](README.md)。
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 3a0cfd12..ff1548f8 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -2,17 +2,17 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
-# Governance
+# 治理
 
-This standard lies at the core of the codebase stewardship provided by the [Foundation for Public Code](https://publiccode.net/).
-We decide if a codebase is ready for community co-development based on this document.
+此標準是[The Foundation for Public Code](https://publiccode.net/)代碼庫管理的核心。我們依照本文件來判斷代碼
+庫是否已經準備好讓社群參與開發。
 
-The standard is maintained by Foundation for Public Code staff.
+本標準由 The Foundation for Public Code 人員負責維護。
 
-[We welcome contributions, such as suggestions for changes or general feedback, from anyone.](/CONTRIBUTING.md)
+[我們歡迎任何人提供修改的建議或是一般意見回饋等貢獻。](/CONTRIBUTING.md)
 
-Because of the important role that the Standard for Public Code has in our core process we require the highest standards from the Standard.
+由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守 The Standard for
+Public Code 中最嚴苛的標準。
 
-We will try to respond promptly to all pull requests.
-The pull request is an opportunity to work together to improve our methods and the Standard.
-We may not accept all changes, but we will explain our logic.
+我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，改善我們的方法與 The Standard for Public Code。我們可能不會接受貢獻者提出
+的所有修改，但我們會解釋背後的邏輯。
diff --git a/README.md b/README.md
index b90f5e3c..3773e268 100644
--- a/README.md
+++ b/README.md
@@ -1,107 +1,114 @@
-# Standard for Public Code
+# The Standard for Public Code
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-The Standard for Public Code gives public organizations a model for preparing open source solutions to enable collaborations with similar public organizations in other places.
-It includes guidance for policy makers, city administrators, developers and vendors.
+The Standard for Public Code 提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公共組織合作。該標準包含給政策制定者、城市管
+理者、開發人員與供應商的指引。
 
-![version 0.7.1](assets/version-badge.svg)
-[![License: CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
-[![Standard commitment](assets/standard-for-public-code-commitment.svg)](#help-improve-this-standard)
+![version 0.7.1](assets/version-badge.svg) [![License:
+CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
+[![標準承
+諾](assets/standard-for-public-code-commitment.svg)](#help-improve-this-standard)
 
-[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
-[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)
-[![standard main badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
-[![standard develop badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
+[![頁面-建造-部
+署](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
+[![測
+試](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)
+[![標準主徽
+章](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
+[![標準開發徽
+章](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
 
-The Standard for Public Code is in a draft format.
-We are preparing it for a version 1.0 release.
-Currently, we are testing it on a small number of codebases.
+The Standard for Public Code 目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。
 
-## Applying the Standard for Public Code to your codebase
+## 將 The Standard for Public Code 套用在您的代碼庫
 
-If you want to apply the Standard for Public Code to your codebase, just go ahead, it's an open standard and free for anyone to use.
-If you wish to advertise the codebase community's aspiration to meet the criteria of the Standard for Public Code, link the documentation of this commitment from the [standard-for-public-code-commitment badge](assets/standard-for-public-code-commitment.svg).
-To see how ready your codebase is, you can do a quick [eligibility self assessment](https://publiccodenet.github.io/assessment-eligibility) that will give you a rough idea of how much work you may need to do to meet all criteria.
+如果您想要採用公共程式標準於您的代碼庫中，請隨意使用，它是一個開放標準與免費給任何人使用。如果您希望推廣代碼庫社群期望達成公共程式標準的資格，請使用 [公共程式標準
+徽章](assets/standard-for-public-code-commitment.svg) 連結到此份承諾文件。了解您的代碼庫準備的如何，您可以透過
+[快速自我檢測](https://publiccodenet.github.io/assessment-eligibility)粗略的瞭解您還需要準備多少才能符合
+所有的資格。
 
-The standard *should* be mostly self-explanatory in how to apply it to your codebase.
-If anything in the standard is unclear, we encourage you to open an issue here so that we can help you and anyone else who feels the same as you.
-For inspiration, look at the [community built implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/) which contains examples and other tips.
+將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能
+夠協助您以及其他與您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指
+南](https://publiccodenet.github.io/community-implementation-guide-standard/)，當中包括
+範例與其他訣竅。
 
-If there are any breaking changes in a new version of the Standard for Public Code, the codebase stewards at the Foundation for Public Code will help any implementers of the standard understand how the gaps can be closed.
+若新版的 The Standard for Public Code 有突破性的修改，The Foundation for Public Code 的代碼庫管理人員會
+幫助The Standard for Public Code 使用者彌補不同版之間的差異。
 
-If you want to commit your codebase to become fully compliant to the standard for future certification, please contact us at <info@publiccode.net> to initiate a formal [assessment](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment).
+若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與我們聯繫：
+[info@publiccode.net](mailto:info@publiccode.net)，並開始正式[評
+估](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment)。
 
-## Request for contributions
+## 徵求貢獻
 
-We believe public policy and software should be inclusive, usable, open, legible, accountable, accessible and sustainable.
-This means we need a new way of designing, developing and procuring both the source code and policy documentation.
+我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。
 
-This standard sets a quality level for codebases that meets the needs of public organizations, institutions and administrations as well as other critical infrastructural services.
+本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需求。
 
-The standard lives at [standard.publiccode.net](https://standard.publiccode.net/).
-See [`index.md`](index.md) for an overview of all content.
+The Standard for Public Code 就在
+[standard.publiccode.net](https://standard.publiccode.net/)。內容概覽請參閱
+[`index.md`](index.md)。
 
-[![Thumbnail for the video on the Standard for Public Code: a printed version lying on a table between two hands](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)
+[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 The Standard for Public
+Code ](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?
+v=QWt6vB-cipE)
 
-[A video introduction to Standard for Public Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube.
+[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v=QWt6vB-cipE)
+from Creative Commons Global Summit 2020 (4:12) on YouTube.
 
-## Help improve this standard
+## 幫忙改善本標準
 
-The Foundation for Public Code is committed to maintaining and developing the Standard for Public Code at a level of quality that meets the standard itself.
+The Foundation for Public Code 致力於維護與開發 The Standard for Public Code ，且品質也會符合該標準本身
+的品質。
 
-We are looking for people like you to [contribute](CONTRIBUTING.md) to this project by suggesting improvements and helping develop it. 😊
-Get started by reading our [contributors guide](CONTRIBUTING.md).
-Since it is such a core document we will accept contributions when they add significant value.
-We've described how we govern the standard in the [governance statement](GOVERNANCE.md).
+我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及協助開發。😊若要開始，請先參閱我們的[貢獻者指
+南](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE.md)提到我們管理該標準的
+方式。
 
-Please note that this project is released with a [code of conduct](CODE_OF_CONDUCT.md).
-By participating in this project you agree to abide by its terms.
-Please be lovely to all other community members.
+請注意，本專案有其[行為準則](CODE_OF_CONDUCT.md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。
 
-## Preview, build and deploy
+## 預覽、建造與部署
 
-The repository builds to a static site deployed at [standard.publiccode.net](https://standard.publiccode.net/).
-It is built with [GitHub pages](https://pages.github.com) and [Jekyll](https://jekyllrb.com/).
+存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode.net/)的靜態網站，使用的是
+[GitHub pages](https://pages.github.com)與[Jekyll](https://jekyllrb.com/)。
 
-The content is made to be built with [Jekyll](http://jekyllrb.com/), which means you will need ruby and ruby-bundler installed, for example:
+當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構，換句話說您需要安裝ruby與ruby-bundler，像是：
 
 ```bash
 sudo apt-get install -y ruby ruby-bundler
 ```
 
-If `ruby` and `bundle` are installed, one can run `bundle install` after which the site can be rendered with the `script/serve.sh` script.
+如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` 腳本來渲染網站。
 
-### Testing
+### 測試
 
-A variety of test scripts are included.
-The script `script/test-all.sh` wraps running of all local tests.
+本標準包含許多測試腳本。`script/test-all.sh` 腳本則會開始執行所有本機測試。
 
-See the scripts in the [script](https://github.com/publiccodenet/standard/tree/main/script) folder.
+所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/script)檔案夾。
 
-### Generating a PDF of the Standard for Public Code
+### 生成 The Standard for Public Code PDF 檔案
 
-In addition to Jekyll, generating PDFs relies upon [Weasyprint](https://weasyprint.org/) and [QPDF](https://github.com/qpdf/qpdf).
-[Pandoc](https://pandoc.org/) can be used to transform PDFs into `.epub`.
+除了 Jekyll 以外，要生成 PDF 檔案也需要仰賴[Weasyprint](https://weasyprint.org/)以及
+[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)可以將 PDF 轉換成
+`.epub`檔案。
 
-To generate these kinds of files, the dependencies should be installed, for example:
+若要生成這些種類的檔案，則需要安裝類似下列的依附元件：
 
 ```bash
 sudo apt-get install -y pandoc qpdf weasyprint
 ```
 
-The file `standard-print.html` can be converted to a nice looking PDF, along with the other release files, using:
+使用以下腳本，可以將 `standard-print.html` 檔案以及其他的版本檔案轉換成美觀的 PDF：
 
 ```bash
 script/pdf.sh
 ```
 
-## License
+## 授權
 
-© [The authors and contributors](AUTHORS.md)
+© [作者與貢獻者](AUTHORS.md)
 
-The standard is [licensed](LICENSE) under CC 0, which also applies to all illustrations and the documentation.
-This means anyone can do anything with it.
-If you contribute you also grant these rights to others.
-You can read more about how to help in the [contributing guide](CONTRIBUTING.md).
+The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任何人都可以任意使用這些
+內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。
diff --git a/_config.yml b/_config.yml
index ff2d05ed..125f94bd 100644
--- a/_config.yml
+++ b/_config.yml
@@ -7,7 +7,9 @@ plugins:
   - jekyll-redirect-from
   - jekyll-sitemap
 
-remote_theme: publiccodenet/jekyll-theme
+repository: publiccodenet/jekyll-theme
+
+remote_theme: Lin-Chia-Cheng/publiccodenet.jekyll-theme
 include:
   - "README.md"
   - "CONTRIBUTING.md"
diff --git a/criteria/bundle-policy-and-source-code.md b/criteria/bundle-policy-and-source-code.md
index 39334f54..902a49bd 100644
--- a/criteria/bundle-policy-and-source-code.md
+++ b/criteria/bundle-policy-and-source-code.md
@@ -5,52 +5,57 @@ order: 2
 redirect_from:
   - criteria/bundle-policy-and-code
 ---
-# Bundle policy and source code
+# 同捆政策與原始碼
 
-Access to both [source code](../glossary.md#source-code) and [policy](../glossary.md#policy) documentation provides building blocks for anyone to implement the codebase in their local context or contribute to the further development of the [codebase](../glossary.md#codebase).
+使用[原始碼](../glossary.md#source-code)以及[政策](../glossary.md#policy)註解，提供基石給想在當地脈絡使用代碼
+庫的人或是想要對[代碼庫](../glossary.md#codebase)進一步發展有所貢獻的人。
 
-Understanding the domain and policies within that domain is fundamental to understanding what problems a codebase is trying to solve and how it sets out to solve them.
+瞭解網域與其政策，才能瞭解代碼庫想要解決的問題以及解決方式。
 
-To be able to evaluate whether to implement a codebase in a new context, an organization needs to understand what process changes it must choose to make or how to contribute additional configurability to the existing solution in order to adapt it to the new context.
+組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。
 
-## Requirements
+## 規定
 
-* The codebase MUST include the policy that the source code is based on.
-* If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection.
-* Policy SHOULD be provided in machine readable and unambiguous formats.
-* [Continuous integration](../glossary.md#continuous-integration) tests SHOULD validate that the source code and the policy are executed coherently.
+* 代碼庫「必須（Must）」包含做為原始碼基礎的政策。
+* 若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵測的原始碼除外）。
+* 政策格式「應該（Should）」可以機讀且明確。
+* [持續整合](../glossary.md#continuous-integration) 測試「應該（Should）」驗證原始碼與政策是否有一致執行。
 
-## How to test
+## 測試方式
 
-* Confirm with a civil servant that all policy that the source code is based on is included.
-* Confirm with a civil servant that all source code that the policy is based on is included.
-* Check if policy can be interpreted by a machine.
-* Check the continuous integration tests for coherent execution of source code and policy pass.
+* 與公務人員確認有收錄做為原始碼基礎的完整政策。
+* 與公務人員確認有收錄做為政策基礎的完成原始碼。
+* 確認政策是否可由機器判讀。
+* 透過持續整合測試，確認原始碼與政策的一致執行。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Collaborate with developers and designers to make sure there is no mismatch between policy code and source code.
-* Provide the relevant policy texts for inclusion in the [repository](../glossary.md#repository); if the text is not available in English, also provide an English summary. Be sure to include standards that your organization has chosen to adhere to and any organizational processes which impact the development or the deployment context of the codebase for your organization.
-* Provide references and links to texts which support the policies.
-* Document policy in formats that are unambiguous and machine-readable, such as those published by the [Object Management Group](https://www.omg.org/spec/).
-* Track policy with [the same version control](maintain-version-control.md) and documentation used to track source code.
-* Check in regularly to understand how the source code in the codebase has changed and whether it still matches the [intentions of the policy](document-codebase-objectives.md).
-* Include relevant policies which impact the community, codebase, and development, including legal obligations like the [General Data Protection Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-accessibility), or human rights policies, like a public organization's commitment to equal opportunity.
+* 與開發人員及設計師合作，確認政策程式碼與原始碼沒有錯配。
+* 提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標
+準，以及影響貴機構代碼庫開發或部署脈絡的組織流程。
+* 引用支持政策的文字並附上連結。
+* 用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/)發佈的格式）來紀錄政策。
+* 利用[相同的版本控制l](maintain-version-control.md)以及用來追蹤原始碼的註解，來追蹤政策。
+* 定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-codebase-objectives.md)。
+* 納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是
+[歐盟無障礙指令](https://ec.europa.eu/digital-single-market/en/web-accessibility)這些法律義
+務，或是人權政策，像是公共組織對機會平等的承諾。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Keep policy makers, developers and designers involved and connected throughout the whole development process.
-* Make sure policy makers, developers and designers are working to the same objectives.
+* 在整個開發流程中，讓政策制定者、開發人員與設計師全程參與。
+* 確保政策制定者、開發人員與設計師有同樣的目標。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Become familiar with and be able to use the process modelling notation that the policy makers in your organization use.
-* Work together with policy makers to make sure there is no mismatch between policy code and source code.
-* Give feedback on how to make policy documentation more clear.
+* 熟悉並且學會使用貴機構的政策制定者所使用的流程模型標記法。
+* 與政策制定者合作，確保政策程式碼與原始碼沒有錯配。
+* 針對如何讓政策註解更明確提供意見回饋。
 
-## Further reading
+## 延伸閱讀
 
-* [Business Process Model and Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation) on Wikipedia.
-* [BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by Trisotech.
-* [Decision Model and Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on Wikipedia.
-* [Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on Wikipedia.
+* 維基百科的[商業流程模型與標記
+法](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)。
+* Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。
+* 維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)。
+* 維基百科的[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。
diff --git a/criteria/code-in-the-open.md b/criteria/code-in-the-open.md
index b325ab2b..05277ff2 100644
--- a/criteria/code-in-the-open.md
+++ b/criteria/code-in-the-open.md
@@ -3,45 +3,50 @@
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 order: 1
 ---
-# Code in the open
+# 以開放精神編寫原始碼
 
-Coding in the open improves transparency, increases [source code](../glossary.md#source-code) quality, makes the source code easier to audit, and enables collaboration.
+開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽查，並且讓協作更容易。
 
-Together, this creates more opportunities for citizens to understand how software and [policy](../glossary.md#policy) impact their interactions with a public organization.
+這讓市民更能夠瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公共組織的互動。
 
-## Requirements
+## 規定
 
-* All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.
-* All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.
-* The codebase MUST NOT contain sensitive information regarding users, their organization or third parties.
-* Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.
-* Documenting which source code or policy underpins any specific interaction the [general public](../glossary.md#general-public) may have with an organization is OPTIONAL.
+* 任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。
+* 任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。
+* 代碼庫「不允許」包含使用者、使用者機構或第三方的敏感資料。
+* 目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈。
+* 可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-public)與任何組織互動的原始碼或政策。
 
-## How to test
+## 測試方式
 
-* Confirm that the source for each version currently in use is published on the internet where it can be seen from outside the original contributing organization and without the need for any form of authentication or authorization.
-* Confirm that the [codebase](../glossary.md#codebase) files and commit history do not include sensitive information.
-* Check for the publication of source code not currently in use.
+* 確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須任何形式的驗證或認證也可以看到。
+* 確認[代碼庫](../glossary.md#codebase)檔案與提交紀錄不包含敏感性資訊。
+* 檢查現在沒有使用的原始碼是否有公開。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Develop policies in the open.
-* Prioritize open and transparent policies.
+* 以開放精神制定政策。
+* 以公開透明的政策為優先。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Develop a culture that embraces openness, learning and feedback.
-* Collaborate with external vendors and freelancers by working in the open.
+* 孕育擁抱開放、重視學習、歡迎意見回饋的文化。
+* 與外部供應商和自由工作者以開放精神的方式協作。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* As a reviewer, for each commit, verify that content does not include sensitive information such as configurations, usernames or passwords, public keys or other real credentials used in production systems.
-* Clearly split data and source code, in order to meet the requirement about sensitive information above.
+* 審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。
+* 為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。
 
-## Further reading
+## 延伸閱讀
 
-* [Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/) by the UK Government Digital Service.
-* [When code should be open or closed](https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed) by the UK Government Digital Service.
-* [Security considerations when coding in the open](https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open) by the UK Government Digital Service.
-* [Deploying software regularly](https://www.gov.uk/service-manual/technology/deploying-software-regularly) by the UK Government Digital Service.
-* [How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/) by the UK Government Digital Service.
+* 英國政府數位服務團《[以開放精神編寫原始
+碼](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)》。
+* 英國政府數位服務團《[程式碼應該開放或封閉的時
+機](https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed)》。
+* 英國政府數位服務團《[以開放精神編寫原始碼的資安考
+量](https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open)》。
+* 英國政府數位服務團《[定期部署軟
+體](https://www.gov.uk/service-manual/technology/deploying-software-regularly)》。
+* 英國政府數位服務團《[政府數位服務團如何使用
+GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/)》。
diff --git a/criteria/document-codebase-maturity.md b/criteria/document-codebase-maturity.md
index bb7a4692..201369a9 100644
--- a/criteria/document-codebase-maturity.md
+++ b/criteria/document-codebase-maturity.md
@@ -6,45 +6,46 @@ redirect_from:
     - criteria/advertise-maturity
     - criteria/document-maturity
 ---
-# Document codebase maturity
+# 記錄代碼庫成熟度
 
-Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps others decide whether to use and contribute to it.
-A codebase version's maturity includes the maturity of its dependencies.
-Understanding how a codebase has evolved is key to understanding the codebase and how to contribute to it.
+清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解
+代碼庫的演變，才能真正認識該代碼庫並且做出貢獻。
 
-## Requirements
+## 規定
 
-* The codebase MUST be versioned.
-* The codebase MUST prominently document whether or not there are versions of the codebase that are ready to use.
-* Codebase versions that are ready to use MUST only depend on versions of other codebases that are also ready to use.
-* The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`.
-* The method for assigning version identifiers SHOULD be documented.
-* It is OPTIONAL to use semantic versioning.
+* 代碼庫必須註明版本編號。
+* 代碼庫必須明確標示是否有已經準備好使用的版本。
+* 準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本。
+* 代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
+* 應該有文件記錄分配版本識別碼的方式。
+* 可選擇是否使用語意化版本控制。
 
-## How to test
+## 測試方式
 
-* Confirm that the codebase has a strategy for versioning which is documented.
-* Confirm that it is obvious to policy makers, managers, developers and designers whether the codebase has versions that are ready to use.
-* Confirm that ready to use versions of the codebase do not depend on any versions of other codebases that are not ready to use.
-* Check that the versioning scheme of the codebase is documented and followed.
-* Check that there is a log of changes.
+* 確認代碼庫有版本編號策略，且有文件記載該策略。
+* 確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使用的版本。
+* 確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何版本。
+* 確認有記錄並遵守代碼庫的版本控制方式。
+* 確認是否有版本的變動紀錄。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* When developing [policy](../glossary.md#policy), understand that any [source code](../glossary.md#source-code) developed needs to be tested and improved before it can be put into service.
-* Consider versioning policy changes, especially when they trigger new versions of the source code.
+* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [程式碼](../glossary.md#source-code) 都必須先
+經過測試與改善，才能夠投入服務。
+* 考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Make sure that services only rely on versions of codebases of equal or greater maturity than the service. For example, don't use a beta version of a codebase in a production service.
+* 要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Make sure that the codebase versioning approach is followed for all releases.
+* 確認所有發行都遵守代碼庫版本控制方式。
 
-## Further reading
+## 延伸閱讀
 
-* [Semantic Versioning Specification](https://semver.org/) used by many codebases to label versions.
-* [Software release life cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)
-* [Service Design and Delivery Process](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process) by the Australian Digital Transformation Agency.
-* [Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-delivery) by the UK Government Digital Service.
+* 許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。
+* [軟體發行生命週期](https://en.wikipedia.org/wiki/Software_release_life_cycle)
+* 澳洲數位轉型局《[服務設計與交付流
+程](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process)》。
+* 英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/agile-delivery)》。
diff --git a/criteria/document-codebase-objectives.md b/criteria/document-codebase-objectives.md
index d54d30eb..7375b456 100644
--- a/criteria/document-codebase-objectives.md
+++ b/criteria/document-codebase-objectives.md
@@ -5,36 +5,37 @@ order: 8
 redirect_from:
   - criteria/document-objectives
 ---
-# Document codebase objectives
+# 記錄代碼庫目標
 
-Clearly documenting [codebase](../glossary.md#codebase) objectives communicates the purpose of the codebase.
-It helps stakeholders and contributors scope the development of the codebase.
-The objectives also provide an easy way for people to decide whether this codebase, or one of its modules, is interesting for them now or in the future.
+清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷
+目前或未來是否會對此代碼庫（或其模組之一）有興趣。
 
-## Requirements
+## 規定
 
-* The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.
-* Codebase documentation SHOULD clearly describe the connections between [policy](../glossary.md#policy) objectives and codebase objectives.
-* Documenting the objectives of the codebase for the [general public](../glossary.md#general-public) is OPTIONAL.
+* 代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
+* 代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
+* 可選擇是否以文件記錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。
 
-## How to test
+## 測試方式
 
-* Confirm that the codebase documentation includes the codebase objectives, mission or goal.
-* Check for descriptions of connections between policy objectives and codebase objectives.
+* 確認代碼庫文件有包含代碼庫目標，或主旨、使命等。
+* 查看政策目標與代碼庫目標之間關聯的描述。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Add the policy objectives to the codebase documentation, for example in the `README`.
-* Make sure that all your codebase objectives have links or references to supporting policy documents added to meet the [Bundle policy and source code](bundle-policy-and-source-code.md) criterion.
+* 將政策目標加入代碼庫文件中，例如「`README`」文件當中。
+* 確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼要合捆](bundle-policy-and-source-code.md)的標
+準。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Add the organizational and business objectives to the codebase documentation, for example in the `README`.
+* 將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Add the technology and design objectives to the codebase documentation, for example in the `README`.
+* 將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。
 
-## Further reading
+## 延伸閱讀
 
-* [How to write project objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf) by Marek Hajduczenia.
+* Marek Hajduczenia《[如何撰寫專案目
+標](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)》。
diff --git a/criteria/document-the-code.md b/criteria/document-the-code.md
index 228fb250..1d89b78f 100644
--- a/criteria/document-the-code.md
+++ b/criteria/document-the-code.md
@@ -5,49 +5,49 @@ order: 9
 redirect_from:
   - criteria/documenting
 ---
-# Document the code
+# 記錄程式碼
 
-Well documented [source code](../glossary.md#source-code) helps people to understand what the source code does and how to use it.
-Documentation is essential for people to start using the [codebase](../glossary.md#codebase) and contributing to it more quickly.
+詳細記錄的[程式碼](../glossary.md#source-code)幫助民眾瞭解該原始碼的作用與使用方式。記錄文件是幫助民眾開始使用[代碼
+庫](../glossary.md#codebase)並且更快做出貢獻的關鍵。
 
-## Requirements
+## 規定
 
-* All of the functionality of the codebase, [policy](../glossary.md#policy) as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase.
-* The documentation of the codebase MUST contain a description of how to install and run the software.
-* The documentation of the codebase MUST contain examples demonstrating the key functionality.
-* The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the [general public](../glossary.md#general-public) and journalists.
-* The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.
-* The documentation of the codebase SHOULD contain examples for all functionality.
-* The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.
-* There SHOULD be [continuous integration](../glossary.md#continuous-integration) tests for the quality of the documentation.
-* Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.
+* 代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。
+* 代碼庫文件必須說明如何安裝與執行軟體。
+* 代碼庫文件必須為關鍵功能舉出範例。
+* 代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
+* 代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。
+* 代碼庫文件應該包含所有功能的範例。
+* 程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
+* 應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。
+* 可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。
 
-## How to test
+## 測試方式
 
-* Confirm that other stakeholders, professionals from other public organizations and the general public find the documentation clear and understandable.
-* Confirm that the documentation describes how to install and run the source code.
-* Confirm that the documentation includes examples of the key functionality.
-* Check with members of the general public and journalists if they can understand the high level description.
-* Check that the instructions for how to install and run a standalone version of the source code result in a running system.
-* Check that all functionality documented contains an example.
-* Check that the documentation includes a high level architectural diagram or similar.
-* Check that the documentation quality is part of integration testing, for example documentation is generated correctly, and links and images are tested.
+* 確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。
+* 確認文件有說明如何安裝與執行原始碼。
+* 確認文件有包含主要功能的範例。
+* 向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。
+* 檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。
+* 檢查文件中列舉的所有功能都包含範例。
+* 檢查文件中是否包含高層架構圖，或類似的組件關係圖表。
+* 確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與圖片等。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Check in regularly to understand how the non-policy code in the codebase has changed.
-* Give feedback on how to make non-policy documentation more clear.
+* 定期檢查代碼庫中非政策程式碼的變動。
+* 針對如何讓非政策文字更清楚提供意見。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Try to use the codebase, so your feedback can improve how clearly the policy and source code are documented. For example, is the current documentation sufficient to persuade a manager at another public organization to use this codebase?
-* Make sure you understand both the policy and source code as well as the documentation.
+* 嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的文件是否足以說服另一個公共組織的管理人員使用本代碼庫？
+* 確保您同時瞭解政策、原始碼以及文件內容。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Check in regularly to understand how the non-source code in the codebase has changed.
-* Give feedback on how to make non-source documentation more clear.
+* 定期查看代碼庫中非原始碼部分的變動情況。
+* 針對如何讓非原始碼文件更清楚易懂提供意見回饋。
 
-## Further reading
+## 延伸閱讀
 
-* [Documentation guide](https://www.writethedocs.org/guide/) by Write the Docs.
+* Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。
diff --git a/criteria/index.md b/criteria/index.md
index 7bd1c002..b31f6f67 100644
--- a/criteria/index.md
+++ b/criteria/index.md
@@ -3,10 +3,11 @@
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 order: 0
 ---
-# Criteria
+# 標準
 
 {% assign sorted = site.pages | sort:"order" %}
 
-{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
+{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name !=
+"index.md" %}{% if page.title %}
 
-1. [{{page.title}}]({{page.url}}){% endif%}    {% endif%}  {% endif%}{% endfor %}
+1. [{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}
diff --git a/criteria/maintain-version-control.md b/criteria/maintain-version-control.md
index 5014df02..af6ae7e1 100644
--- a/criteria/maintain-version-control.md
+++ b/criteria/maintain-version-control.md
@@ -5,56 +5,60 @@ order: 6
 redirect_from:
   - criteria/version-control-and-history
 ---
-# Maintain version control
+# 維護版本控制
 
-[Version control](../glossary.md#version-control) means keeping track of changes to the [source code](../glossary.md#source-code) and other files of the [codebase](../glossary.md#codebase) over time.
-This allows you to maintain structured documentation of the history of the codebase.
-This is essential for collaboration at scale, as it enables developers to work on changes in parallel and helps future developers to understand the reasons for changes.
+[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md#source-code)以及其他[代碼
+庫](../glossary.md#codebase)檔案歷來的變動。這能讓您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人員針對修改
+變動平行作業，並幫助未來的開發人員瞭解修改的原因。
 
-## Requirements
+## 規定
 
-* All files in the codebase MUST be version controlled.
-* All decisions MUST be documented in commit messages.
-* Every commit message MUST link to discussions and issues wherever possible.
-* The codebase SHOULD be maintained in a distributed version control system.
-* Contribution guidelines SHOULD require contributors to group relevant changes in commits.
-* Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.
-* Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system.
-* It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.
+* 代碼庫中的所有檔案皆必須有版本控制。
+* 所有決定皆必須記錄成提交訊息。
+* 每份提交訊息皆必須盡可能附上討論與議題連結。
+* 代碼庫應該以分散式版本控制系統作維護。
+* 貢獻準則應該要求貢獻者將相關的修改變動提交內容作群組分類。
+* 維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。
+* 貢獻準則應該鼓勵採用方便版本控制系統檢視檔案修改內容的檔案格式。
+* 貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
 
-## How to test
+## 測試方式
 
-* Confirm that the codebase is kept in version control using software such as Git.
-* Review the commit history, confirming that all commit messages explain why the change was made.
-* Review the commit history, confirming that where possible all commit messages include the discussion about the change was or where to find it (with a URL).
-* Check if the version control system is distributed.
-* Review the commit history, check if grouping of relevant changes in accordance with the contributing guidelines.
-* Check that it is possible to access a specific version of the codebase, for example through a revision tag or a textual label.
-* Check that the file formats used in the codebase are text formats where possible.
+* 確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。
+* 審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。
+* 審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。
+* 檢查版本控制系統是否為分散式。
+* 審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。
+* 檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。
+* 檢查代碼庫時，在可能的情況下檔案都是採用文字格式。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* If a new version of the codebase is created because of a [policy](../glossary.md#policy) change, make sure it's clear in the documentation:
-  * what the policy change is,
-  * how it's changed the codebase.
+* 如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
+   * 政策改變的地方，
+   * 代碼庫如何因應而改變。
 
-For example, adding a new category of applicant to a codebase that manages granting permits would be considered a policy change.
+舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Support policy makers, developers and designers to be clear about what improvements they're making to the codebase. Making improvements isn't a public relations risk.
+* 支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Make sure that all files required to understand the code, build and deploy are in the version control system.
-* Write clear commit messages so that it is easy to understand why the commit was made.
-* Mark different versions so that it is easy to access a specific version, for example using revision tags or textual labels.
-* Write clear commit messages so that versions can be usefully compared.
-* Work with policy makers to describe how the source code was updated after a policy change.
+* 確認版本控制系統具有瞭解程式碼、組建與部署所需的所有檔案。
+* 提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。
+* 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。
+* 提交內容的訊息要寫清楚，方便之後比較各版本。
+* 在政策改變以後與政策制定者合作，說明原始碼更新的內容。
 
-## Further reading
+## 延伸閱讀
 
-* [Producing OSS: Version Control Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl Fogel.
-* [Maintaining version control in coding](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding) by the UK Government Digital Service.
-* [GitHub Skills](https://skills.github.com/) by GitHub for learning how to use GitHub or refresh your skills.
-* [Git Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) by GitHub, a list with the most common used git commands.
+* Karl Fogel《[製作開放原始碼軟體：版本控制字
+彙](https://producingoss.com/en/vc.html#vc-vocabulary)》。
+* 英國政府數位服務團《[維護程式碼的版本控
+制](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding)》。
+* GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
+* GitHub 提供的「[Git 密技
+表](https://education.github.com/git-cheat-sheet-education.pdf)」列出了最常用的 git 指
+令。
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
index 049491e5..d58263e7 100644
--- a/criteria/make-contributing-easy.md
+++ b/criteria/make-contributing-easy.md
@@ -3,46 +3,47 @@
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 order: 5
 ---
-# Make contributing easy
+# 貢獻要容易
 
-To develop better, more reliable and feature rich software, users need to be able to fix problems, add features, and address security issues of the shared [codebase](../glossary.md#codebase).
+若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫](../glossary.md#codebase)修復問題與新增功能。
 
-A shared digital infrastructure makes it easier to make collaborative contributions.
-The less effort it takes to make contributions that are accepted by the codebase, the more likely users are to become contributors.
+共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者越可能成為貢獻者。
 
-## Requirements
+## 規定
 
-* The codebase MUST have a public issue tracker that accepts suggestions from anyone.
-* The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file.
-* The codebase MUST have communication channels for users and developers, for example email lists.
-* There MUST be a way to report security issues for responsible disclosure over a closed channel.
-* The documentation MUST include instructions for how to report potentially security sensitive issues.
+* 代碼庫必須有個可以公開接受任何人建議的議題追蹤器。
+* 文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。
+* 代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄清單。
+* 必須有辦法透過封閉的管道通報安全性問題。
+* 文件必須說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。
 
-## How to test
+## 測試方式
 
-* Confirm that there is a public issue tracker.
-* Confirm that the codebase contains links to the public issue tracker and submitted codebase changes.
-* Confirm that it is possible to participate in a discussion with other users and developers about the software using channels described in the codebase.
-* Confirm that there is a closed channel for reporting security issues.
-* Confirm that there are instructions for privately reporting security issues.
+* 確認有公開的議題追蹤器。
+* 確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。
+* 確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。
+* 確認有封閉的管道通報安全性問題。
+* 確認有說明如何私下通報安全性問題。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Track [policy](../glossary.md#policy) issues in the codebase, so that a relevant external policy expert can volunteer help.
+* 追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Track management issues in the codebase, so that external managers with relevant experience can volunteer help.
-* Support your experienced policy makers, developers and designers to keep contributing to the codebase for as long as possible.
+* 追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。
+* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Just like for [reviews](require-review-of-contributions.md), make sure to respond to requests promptly.
-* Keep your managers informed of the time and resources you require to support other contributors.
-* Make sure that appropriate communication channels for asking maintainers and stakeholders questions are easy to locate, for instance in the README.
-* Make sure that appropriate contact details are included in the metadata, for instance in the publiccode.yml file.
+* 跟[審查](require-review-of-contributions.md)一樣，務必迅速回應請求。
+* 告知管理人員您支持其他貢獻者時所需的時間與資源。
+* 確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`」文件當中。
+* 確保中介資料包含合適的聯絡資訊，例如在 publiccode.yml 檔案中。
 
-## Further reading
+## 延伸閱讀
 
-* [How to inspire exceptional contributions to your open-source project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf) by Joel Hans.
-* [The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/) by the UK Government Digital Service.
+* Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢
+獻](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf)》。
+* 英國政府數位服務團《[以開放精神編寫原始碼的好
+處](https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/)》。
diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index ca2f1ce1..44a8cb3f 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -6,65 +6,69 @@ redirect_from:
   - criteria/findability
 ---
 
-# Make the codebase findable
+# 代碼庫可查詢得到
 
-The more findable a [codebase](../glossary.md#codebase) is, the more potential new collaborators will find it.
-Just publishing a codebase and hoping it is found does not work, instead proactiveness is needed.
+一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必
+須主動積極。
 
-A metadata description file increases discoverability.
-Well-written metadata containing a unique and persistent identifier, such as a Wikidata item or FSF software directory listing (thus being part of the semantic web), makes the codebase easier for people to refer, cite, disambiguate and discover through third party tools.
+有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄列
+表之中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。
 
-## Requirements
+## 規定
 
-* The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.
-* The codebase SHOULD have a short description that helps someone understand what the codebase is for or what it does.
-* Maintainers SHOULD submit the codebase to relevant software catalogs.
-* The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).
-* The codebase SHOULD be findable using a search engine by codebase name.
-* The codebase SHOULD be findable using a search engine by describing the problem it solves in natural language.
-* The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, [repository](../glossary.md#repository) location and website.
-* The codebase SHOULD include a machine-readable metadata description, for example in a [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file.
-* A dedicated domain name for the codebase is OPTIONAL.
-* Regular presentations at conferences by the community are OPTIONAL.
+* 代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
+* 代碼庫說明應該要簡短，幫助他人瞭解代碼庫的性質與作用。
+* 維護人員應該將代碼庫提交至相關的軟體目錄上。
+* 代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。
+* 在搜尋引擎查找代碼庫名稱時，應該能搜尋得到代碼庫。
+* 在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼庫。
+* 代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
+* 代碼庫應該包含機器可讀的中介資料說明，例如採用
+[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。
+* 可選擇是否為代碼庫設定專用的網域名稱。
+* 可選擇是否在社群舉辦的會議中定期進行簡報。
 
-## How to test
+## 測試方式
 
-* Check that the codebase name is descriptive and free of puns.
-* Check that the codebase name is free of acronyms and abbreviations or that the acronyms or abbreviations in the name are more universally known than the longer forms.
-* Check that the codebase name is free of organizational branding, unless that organization is of the codebase community itself.
-* Check that the codebase repository has a short description of the codebase.
-* Check for the codebase listing in relevant software catalogs.
-* Check for a codebase website which describes the problem the codebase solves.
-* Check that the codebase appears in the results on more than one major search engine when searching by the codebase name.
-* Check that the codebase appears in the results on more than one major search engine when searching by using natural language, for instance, using the short description.
-* Check unique and persistent identifier entries for mention of the major contributors.
-* Check unique and persistent identifier entries for the repository location.
-* Check unique and persistent identifier entries for the codebase website.
-* Check for a machine-readable metadata description file.
+* 檢查代碼庫名稱是否描述說明其用途，且不包含雙關語。
+* 檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整名稱更熟為人知。
+* 檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員）。
+* 檢查代碼庫儲存庫是否包含代碼庫的簡短描述。
+* 檢查代碼庫有刊登在相關軟體型錄上。
+* 檢查代碼庫的網站有描述代碼庫能夠解決的問題。
+* 檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 檢查永久唯一識別碼條目有提及主要貢獻者。
+* 檢查永久唯一識別碼條目中有包含儲存庫位置。
+* 檢查永久唯一識別碼條目有列出代碼庫網站。
+* 檢查中介資料說明檔案是機器可讀的格式。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Contribute a description of the policy area or problem this codebase acts on or operates.
-* Test your problem description with peers outside of your context who aren't familiar with the codebase.
-* Present on how the codebase implements the [policy](../glossary.md#policy) at relevant conferences.
+* 貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。
+* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
+* 在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Search trademark databases to avoid confusion or infringement before deciding the name.
-* Use the short description wherever the codebase is referenced, for instance, as social media account descriptions.
-* Budget for content design and Search Engine Optimization skills in the team.
-* Make sure people involved in the project present at relevant conferences.
+* 在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。
+* 使用簡短描述說明參照代碼庫的地方，例如社群媒體帳號說明。
+* 為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。
+* 確保專案參與人員出席相關會議或作簡報介紹。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Search engine optimization, for instance adding a [sitemap](https://www.sitemaps.org/protocol.html).
-* Use the short description wherever the codebase is referenced, for instance, as the repository description.
-* Test your problem description with peers outside of your context who aren't familiar with the codebase.
-* Suggest conferences to present at and present at them.
+* 搜尋引擎最佳化，例如新增[網站地圖](https://www.sitemaps.org/protocol.html)。
+* 在參照代碼庫的地方，都使用簡短描述，例如儲存庫的說明。
+* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
+* 推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
 
-* [Introduction to Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the Wikidata community.
-* [FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) by the Free Software Foundation.
-* The [FAIR Guiding Principles for scientific data management and stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR International Support and Coordination Office provide a nice list of attributes that make (meta)data more machine actionable (and hence more findable). Some of these apply directly to codebases, while others may provoke exploration into what the codebase equivalent would be.
+* Wikidata 維基數據社群《[維基數據簡
+介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
+* FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
+* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原
+則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
+機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。
diff --git a/criteria/make-the-codebase-reusable-and-portable.md b/criteria/make-the-codebase-reusable-and-portable.md
index 5437394c..153ceda9 100644
--- a/criteria/make-the-codebase-reusable-and-portable.md
+++ b/criteria/make-the-codebase-reusable-and-portable.md
@@ -6,71 +6,73 @@ redirect_from:
   - criteria/reusable-and-portable-codebases
   - criteria/create-reusable-and-portable-code
 ---
-# Make the codebase reusable and portable
+# 使代碼庫可重複使用且具可攜性
 
-Creating reusable and portable [code](../glossary.md#code) enables policy makers, developers and designers to reuse what has been developed, test it, improve it and contribute those improvements back, leading to better quality, cheaper maintenance and higher reliability.
+編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回
+代碼庫中，如此可提高品質、降低維護成本、增強可靠性。
 
-Thoughtfully and purposefully designing a [codebase](../glossary.md#codebase) for reusability allows for the mission, vision and scope of the codebase to be shared by multiple parties.
-Codebases developed and used by multiple parties are more likely to benefit from a self-sustaining community.
+以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從
+能自我運作的社群中獲益。
 
-Organizing a codebase such that it is composed of well documented modules improves reusability and maintainability.
-A module is easier to reuse in [another context](../glossary.md#different-contexts) if its purpose is clearly documented.
+以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
+境](../glossary.md#different-contexts)中重複利用。
 
-Source code which does not rely on the situation-specific infrastructure of any contributor, vendor or deployment can be tested by any other contributor.
+如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都能測試該原始碼。
 
-## Requirements
+## 規定
 
-* The codebase MUST be developed to be reusable in different contexts.
-* The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding.
-* The codebase SHOULD be in use by multiple parties.
-* The roadmap SHOULD be influenced by the needs of multiple parties.
-* The development of the codebase SHOULD be a collaboration between multiple parties.
-* Configuration SHOULD be used to make [source code](../glossary.md#source-code) adapt to context specific needs.
-* The codebase SHOULD be localizable.
-* Source code and its documentation SHOULD NOT contain situation-specific information.
-* Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.
-* The software SHOULD NOT require services or platforms available from only a single vendor.
+* 代碼庫必須開發成能在不同情境中重複使用。
+* 執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程式碼或服務。
+* 代碼庫應該有多方單位使用。
+* 發展路線圖應該有多方單位的需求影響。
+* 代碼庫開發應該由多方單位合作。
+* 應該使用組態設定方式以將[程式碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。
+* 代碼庫應該能夠在地化。
+* 原始碼與其文件不應該包含特定情況專用的資訊。
+* 代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。
+* 軟體不應該要求只有單一供應商能提供的服務或平台。
 
-## How to test
+## 測試方式
 
-* Confirm with someone in a similar role at another organization if they can use the codebase and what that would entail.
-* Confirm that the codebase can run without using any proprietary or non open-licensed software or services.
-* If the codebase is in early development before a production-ready release, then check for evidence of ambition to obtain collaborators.
-   * Or if the codebase is very mature and stable with very infrequent fixes, patches, or contributions:
-     * Check that the codebase is in use by multiple parties or in multiple contexts.
-     * Check for documented and budgeted commitments of collaboration.
-   * Otherwise:
-     * Check that the codebase is in use by multiple parties or in multiple contexts.
-     * Check that the codebase contributors are from multiple parties.
-* Check that the codebase files and commit history do not include situation-specific data.
-* Check that the software can be deployed and run without services or platforms available from a single vendor.
+* 與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行。
+* 確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。
+* 若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願。
+   * 或是如果代碼庫非常成熟與穩定，鮮少需要修復或貢獻：
+      * 檢查是否有多方單位或是有在多種情境下正使用代碼庫。
+      * 檢查是否有文件記錄下合作的承諾以及承諾的預算。
+   * 若是沒有，則：
+      * 檢查是否有多方單位或是有在多種情境下正使用代碼庫。
+      * 檢查代碼庫貢獻者是否來自多方單位。
+* 檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。
+* 檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Document your [policy](../glossary.md#policy) with enough clarity and detail that it can be understood outside of its original context.
-* Make sure your organization is listed as a known user by the codebase.
-* Identify other organizations for your teams to collaborate with.
+* 為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。
+* 確保代碼庫有將貴組織單位列為已知使用者。
+* 列出貴團隊想要合作的其他組織。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Make sure that stakeholders and business owners understand that reusability is an explicit codebase goal as this reduces technical debt and provides sustainability for the codebase.
-* Make sure that your teams are collaborating with other teams.
+* 確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。
+* 確認您的團隊與其他團隊協作。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-Source should be designed:
+原始碼應該設計成：
 
-* for reuse by other users and organizations regardless of locale,
-* to solve a general problem instead of a specific one,
-* in logically meaningful and isolated modules,
-* so that someone in a similar organization facing a similar problem would be able to use (parts of) the solution.
+* 能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，
+* 能解決通用性質問題，而非特定問題，
+* 以邏輯上具有意義且獨立的模組構成，
+* 如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。
 
-Make sure that the codebase documentation describes the build-time and runtime dependencies.
-If your context requires deploying to proprietary platforms or using proprietary components, make sure that collaborators can develop, use, test, and deploy without them.
+確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就
+能進行開發、使用、測試、部署等。
 
-For each commit, reviewers verify that content does not include situation-specific data such as hostnames, personal and organizational data, or tokens and passwords.
+在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。
 
-## Further reading
+## 延伸閱讀
 
-* [Making source code open and reusable](https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable) by the UK Government Digital Service.
-* [Localization vs. Internationalization](https://www.w3.org/International/questions/qa-i18n) by the World Wide Web Consortium.
+* 英國政府數位服務團《[讓原始碼開放且可重複利
+用](https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable)》。
+* W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/questions/qa-i18n)》。
diff --git a/criteria/publish-with-an-open-license.md b/criteria/publish-with-an-open-license.md
index 1b674dcb..6e4e8cfc 100644
--- a/criteria/publish-with-an-open-license.md
+++ b/criteria/publish-with-an-open-license.md
@@ -5,50 +5,57 @@ order: 13
 redirect_from:
   - criteria/open-licenses
 ---
-# Publish with an open license
+# 發行採用開放授權
 
-An open and well known license makes it possible for anyone to see the [source code](../glossary.md#source-code) in order to understand how it works, to use it freely and to contribute to the [codebase](../glossary.md#codebase).
-This enables a vendor ecosystem to emerge around the codebase.
+有了開放且熟為人知的授權，任何人都可以看到[原始碼](../glossary.md#source-code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼
+庫](../glossary.md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。
 
-Clearly indicating the license for each file within a codebase facilitates correct reuse and attribution of parts of a codebase.
+明確標示代碼庫中每一個檔案的授權，幫助使用者正確重複利用與引用代碼庫的內容。
 
-## Requirements
+## 規定
 
-* All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.
-* Software source code MUST be licensed under an [OSI-approved or FSF Free/Libre license](https://spdx.org/licenses/).
-* All source code MUST be published with a license file.
-* Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.
-* All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.
-* Having multiple licenses for different types of source code and documentation is OPTIONAL.
+* 所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。
+* 軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
+款](https://spdx.org/licenses/)。
+* 所有程式碼皆必須搭配授權條款檔案一併發行。
+* 不得要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。
+* 代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。
+* 可選擇是否為不同類型的原始碼與文件採用多重授權條款。
 
-## How to test
+## 測試方式
 
-* Confirm that the codebase is clearly licensed.
-* Confirm that the license for the source code is on the [OSI-approved or FSF Free/Libre license list](https://spdx.org/licenses/) and the license for documentation [conforms to the Open Definition](https://opendefinition.org/licenses/).
-* Confirm that the licenses used in the codebase are included as files.
-* Confirm that contribution guidelines and [repository](../glossary.md#repository) configuration do not require transfer of copyright.
-* Check for machine-readable license checking in the codebase [continuous integration](../glossary.md#continuous-integration) tests.
+* 確認代碼庫有清楚給予授權條款。
+* 確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清
+單](https://spdx.org/licenses/)，以及文件的授權條款有[符合「開放定
+義」](https://opendefinition.org/licenses/)。
+* 確認代碼庫中有包含其採用的授權條款檔案。
+* 確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
+* 在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Develop [policy](../glossary.md#policy) that requires source code to be [open source](../glossary.md#open-source).
-* Develop policy that disincentivizes non-open source code and technology in procurement.
+* 制定要求原始碼必須採用[開放原始碼](../glossary.md#open-source)授權的[政策](../glossary.md#policy)。
+* 制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Only work with open source vendors that deliver their source code by publishing it under an open source license.
-* Beware that even though [Creative Commons licenses](https://creativecommons.org/licenses/) are great for documentation, licenses that stipulate Non-Commercial or No Derivatives are NOT freely reusable, changeable and redistributable and don't fulfill these requirements.
+* 只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。
+* 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」
+的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Add a new `license` file to every new codebase created.
-* Add a copyright notice and a license header to every new source code file created.
-* When source code is being reused by the codebase, make sure that it has a license that is compatible with the license or licenses of the codebase.
+* 每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。
+* 每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。
+* 代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
 
-* [Open source definition](https://opensource.org/osd) by the Open Source Initiative, all open source licenses meet this definition.
-* [Animated video introduction to Creative Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by Creative Commons Aotearoa New Zealand.
-* [REUSE Initiative specification](https://reuse.software/spec/) by Free Software Foundation Europe for unambiguous, human-readable and machine-readable copyright and licensing information.
-* [SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with standardized, machine-readable abbreviations for most licenses.
+* 開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
+* 紐西蘭 CC Aotearoa《[創用CC介紹動畫影
+片](https://creativecommons.org/about/videos/creative-commons-kiwi)》。
+* 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授
+權資訊。
+* Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示
+法。
diff --git a/criteria/require-review-of-contributions.md b/criteria/require-review-of-contributions.md
index fca4fc5c..441dc1b5 100644
--- a/criteria/require-review-of-contributions.md
+++ b/criteria/require-review-of-contributions.md
@@ -5,59 +5,65 @@ order: 7
 redirect_from:
   - criteria/require-review
 ---
-# Require review of contributions
+# 要求審查貢獻內容
 
-Peer-review of contributions is essential for [source code](../glossary.md#source-code) quality, reducing security risks and operational risks.
+同儕審查貢獻是[原始碼](../glossary.md#source-code)品質的關鍵，降低安全性風險與營運風險。
 
-Requiring thorough review of contributions encourages a culture of making sure every contribution is of high quality, completeness and value.
-Source code review increases the chance of discovering and fixing potential bugs or mistakes before they are added to the [codebase](../glossary.md#codebase).
-Knowing that all source code was reviewed discourages a culture of blaming individuals, and encourages a culture of focusing on solutions.
+要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發
+現與修復潛在錯誤的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。
 
-A [policy](../glossary.md#policy) of prompt reviews assures contributors of a guaranteed time for feedback or collaborative improvement, which increases both rate of delivery and contributor engagement.
+快速審查的[政策](../glossary.md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， 進而提高貢獻者交付貢獻內容的頻率以及參與熱
+度。
 
-## Requirements
+## 規定
 
-* All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.
-* Reviews MUST include source, policy, tests and documentation.
-* Reviewers MUST provide feedback on all decisions to not accept a contribution.
-* The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review.
-* Reviews SHOULD include running both the software and the tests of the codebase.
-* Contributions SHOULD be reviewed by someone in a different context than the contributor.
-* Version control systems SHOULD NOT accept non-reviewed contributions in release versions.
-* Reviews SHOULD happen within two business days.
-* Performing reviews by multiple reviewers is OPTIONAL.
+* 所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。
+* 審查必須包含原始碼、政策、測試與文件等。
+* 如果不接受貢獻內容，審查人員必須提供意見回饋。
+* 審查流程應該確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。
+* 審查內容應該包含執行軟體與執行代碼庫測試。
+* 貢獻內容應該由與貢獻者不同背景情境的人來審查。
+* 版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。
+* 審查應該在兩個工作天內進行。
+* 可選擇是否由多位審查人員進行審查。
 
-## How to test
+## 測試方式
 
-* Confirm that every commit in the history has been reviewed by a different contributor.
-* Confirm that reviews include source, policy, tests and documentation.
-* Confirm that rejected contributions were appropriately explained.
-* Check if guidelines for reviewers include instructions to review for conformance to standards, architecture and codebase guidelines.
-* Check with reviewers if they run the software and tests during review.
-* Check with reviewers if commits have been reviewed by a different contributor in a different context.
-* Check for use of branch protection in the [version control](../glossary.md#version-control) system.
-* Check the times between contribution submission and review.
+* 確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。
+* 確認審查內容包含原始碼、政策、測試、文件等。
+* 針對未被採用的貢獻內容，確認有適當解釋原因。
+* 檢查審查人員指引有涵蓋是否遵循標準、架構、代碼庫指引等。
+* 檢查審查人員在審查時是否有執行程式與測試。
+* 與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。
+* 檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。
+* 檢查貢獻提交與審查之間的時間間隔。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Institute a 'four eyes' policy where everything, not just source code, is reviewed.
-* Use a version control system or methodology that enables review and feedback.
+* 制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。
+* 採用具有審查與意見回饋功能的版本控制系統或作業流程。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Make delivering great software a shared objective.
-* Make sure writing and reviewing contributions to source, policy, documentation and tests are considered equally valuable.
-* Create a culture where all contributions are welcome and everyone is empowered to review them.
-* Make sure no contributor is ever alone in contributing to a codebase.
+* 將交付妥善軟體作為共同目標。
+* 確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。
+* 創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。
+* 確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Ask other contributors on the codebase to review your work, in your organization or outside of it.
-* Try to respond to others' requests for review promptly, initially providing feedback about the concept of the change.
+* 請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。
+* 當他人請求您審查時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。
 
-## Further reading
+## 延伸閱讀
 
-* [How to review code the GDS way](https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK Government Digital Service.
-* Branch protection on [GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) and [GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-protected/).
-* [The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/) by Sage Sharp.
-* [Measuring Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla.
+* 英國政府數位服務團《[英國政府數位服務團程式碼審查程
+序](https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content)》。
+* [GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)
+與
+[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-protected/) 平
+臺的分支保護說明。
+* Sage Sharp《[程式修補審查的和善藝
+術](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/)》。
+* Mozilla《[參與度評測成
+果](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)》。
diff --git a/criteria/use-a-coherent-style.md b/criteria/use-a-coherent-style.md
index 6199ef02..87fb4d46 100644
--- a/criteria/use-a-coherent-style.md
+++ b/criteria/use-a-coherent-style.md
@@ -5,43 +5,44 @@ order: 15
 redirect_from:
   - criteria/style
 ---
-# Use a coherent style
+# 風格要前後一致
 
-Following a consistent and coherent style enables contributors in different environments to work together.
-Unifying vocabularies reduces friction in communication between contributors.
+採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝通上的摩擦。
 
-## Requirements
+## 規定
 
-* The [codebase](../glossary.md#codebase) MUST use a coding or writing style guide, either the codebase community's own or an existing one referred to in the codebase.
-* Contributions SHOULD pass automated tests on style.
-* The style guide SHOULD include expectations for inline comments and documentation for non-trivial sections.
-* Including expectations for [understandable English](use-plain-english.md) in the style guide is OPTIONAL.
+* [代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既
+有風格。
+* 貢獻內容應該通過自動化的風格測試。
+* 風格指南應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。
+* 可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指南之中。
 
-## How to test
+## 測試方式
 
-* Confirm that contributions are in line with the style guides specified in the documentation.
-* Check for the presence of automated tests on style.
+* 確認貢獻內容有遵循文件中指定的風格指南。
+* 檢查是否有自動化的風格測試。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Create, follow and continually improve on a style guide for [policy](../glossary.md#policy) and documentation as well as document this in the codebase, for example in the `CONTRIBUTING` or `README`.
+* 為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或
+「`README`」檔案。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Include written language, source, test and policy standards in your organizational definition of quality.
+* 將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-If the codebase does not already have engineering guidelines or other contributor guidance, start by adding documentation to the [repository](../glossary.md#repository) describing whatever is being done now, for example in the `CONTRIBUTING` or `README`.
-An important purpose of the file is to communicate design preferences, naming conventions, and other aspects machines can't easily check.
-Guidance should include what would be expected from [source code](../glossary.md#source-code) contributions in order for them to be merged by the maintainers, including source, tests and documentation.
-Continually improve upon and expand this documentation with the aim of evolving this documentation into engineering guidelines.
+如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是
+「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
+的其他層面。指南應該包含貢獻的[原始碼](../glossary.md#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、
+文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。
 
-Additionally:
+此外：
 
-* Use a linter.
-* Add linter configurations to the codebase.
+* 使用程式碼品質分析工具 (linter)。
+* 在代碼庫中加入程式碼品質分析工具的組態設定。
 
-## Further reading
+## 延伸閱讀
 
-* [Programming style](https://en.wikipedia.org/wiki/Programming_style) on Wikipedia.
+* 維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。
diff --git a/criteria/use-continuous-integration.md b/criteria/use-continuous-integration.md
index d19b4789..7f2c3d0b 100644
--- a/criteria/use-continuous-integration.md
+++ b/criteria/use-continuous-integration.md
@@ -5,66 +5,67 @@ order: 12
 redirect_from:
   - criteria/continuous-integration
 ---
-# Use continuous integration
+# 使用持續整合
 
-Asynchronous collaboration is enabled by developers merging their work to a shared branch frequently, verified by automated tests.
-The more frequent the merging and the smaller the contribution, the easier it is to resolve merge conflicts.
+開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易解決。
 
-Automated testing of all functionality provides confidence that contributions are working as intended and have not introduced errors, and allows reviewers to focus on the structure and approach of the contribution.
-The more focused the test, the easier it is to clearly identify and understand errors as they arise.
+自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。
 
-Documenting a codebase's [continuous integration](../glossary.md#continuous-integration) workflow helps contributors understand the expectations of contributions.
-Continuous integration allows for an easier monitoring of the state of the [codebase](../glossary.md#codebase).
+以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。透過持續整合
+可以更輕易地監督 [代碼庫](../glossary.md#codebase)狀態。
 
-## Requirements
+## 規定
 
-* All functionality in the [source code](../glossary.md#source-code) MUST have automated tests.
-* Contributions MUST pass all automated tests before they are admitted into the codebase.
-* The codebase MUST have guidelines explaining how to structure contributions.
-* The codebase MUST have active contributors who can review contributions.
-* Automated test results for contributions SHOULD be public.
-* The codebase guidelines SHOULD state that each contribution should focus on a single issue.
-* Source code test and documentation coverage SHOULD be monitored.
-* Testing [policy](../glossary.md#policy) and documentation for consistency with the source and vice versa is OPTIONAL.
-* Testing policy and documentation for style and broken links is OPTIONAL.
-* Testing the software by using examples in the documentation is OPTIONAL.
+* [原始碼](../glossary.md#source-code)中的所有功能都必須有自動化測試。
+* 所有貢獻內容都必須先通過自動化測試，才能上傳至代碼庫。
+* 代碼庫必須有說明貢獻內容結構的相關準則。
+* 代碼庫必須有能夠審查貢獻內容的活躍貢獻者。
+* 應該公開貢獻的自動化測試結果。
+* 代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。
+* 應該監督原始碼測試與文件的涵蓋範圍。
+* 可選擇是否測試[政策](../glossary.md#policy)和文件，與原始碼間有無一致性，或是反之亦然。
+* 可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。
+* 可選擇是否使用文件範例來測試軟體。
 
-## How to test
+## 測試方式
 
-* Confirm that there are tests present.
-* Confirm that source code coverage tools check that coverage is at 100% of the source code.
-* Confirm that contributions are only admitted into the codebase after all of the tests are passed.
-* Confirm that contribution guidelines explain how to structure contributions.
-* Confirm that there are contributions from within the last three months.
-* Check that test results are viewable.
-* Check if source code coverage data is published.
+* 確認有測試可用。
+* 確認原始碼覆蓋率工具能檢查到 100% 的原始碼。
+* 確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。
+* 確認有貢獻準則說明貢獻內容的結構。
+* 確認最近三個月內有貢獻內容上傳。
+* 檢查是否可以查看測試結果。
+* 檢查是否已經公佈原始碼覆蓋率數據。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Involve managers as well as developers and designers as early in the process as possible and keep them engaged throughout development of your policy.
-* Make sure there are also automated tests set up for policy documentation.
-* Fix policy documentation promptly if it fails a test.
-* Make sure the source code reflects any changes to the policy (see [Maintain version control](maintain-version-control.md)).
+* 儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。
+* 確保政策文件也有設好自動化測試。
+* 如果政策文件未能通過測試，請立即修正。
+* 確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-control.md)）。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Make sure to test with real end users as quickly and often as possible.
-* Plan the work to integrate small parts very often instead of large parts less frequently.
-* Procure consultancy services that deliver incrementally aligned with the plan.
-* After a large failure, encourage publication of incident reports and public discussion of what was learned.
+* 確保能儘快且經常給真正的終端使用者進行測試。
+* 以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。
+* 聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。
+* 發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Help managers structure the work plan such that it can be integrated as small increments.
-* Help contributors limit the scope of their contributions and feature requests to be as small as reasonable.
-* Help managers and policy makers test their contributions, for example by testing their contributions for broken links or style.
-* Structure source code written to handle conditions which are difficult to create in a test environment in such a way that the conditions can be simulated during testing. Forms of resource exhaustion such as running out of storage space and memory allocation failure are typical examples of difficult to create conditions.
-* Tune the test code coverage tools to avoid false alarms resulting from inlining or other optimizations.
-* Deploy often.
-* Integrate your work at least once a day.
+* 協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。
+* 協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。
+* 協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。
+* 編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。
+* 調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。
+* 經常部署。
+* 至少每天整合工作內容一次。
 
-## Further reading
+## 延伸閱讀
 
-* [What is continuous integration](https://www.martinfowler.com/articles/continuousIntegration.html) by Martin Fowler.
-* [Use continuous delivery](https://gds-way.cloudapps.digital/standards/continuous-delivery.html) by the UK Government Digital Service.
-* [Quality assurance: testing your service regularly](https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly) by the UK Government Digital Service.
+* Martin Fowler《[什麼是持續整
+合](https://www.martinfowler.com/articles/continuousIntegration.html)》。
+* 英國政府數位服務團《[使用持續交
+付](https://gds-way.cloudapps.digital/standards/continuous-delivery.html)》。
+* 英國政府數位服務團《[品質保證：定期測試您的服
+務](https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly)》。
diff --git a/criteria/use-open-standards.md b/criteria/use-open-standards.md
index 13d26b8b..5fbf8f6a 100644
--- a/criteria/use-open-standards.md
+++ b/criteria/use-open-standards.md
@@ -5,42 +5,43 @@ order: 11
 redirect_from:
   - criteria/open-standards
 ---
-# Use open standards
+# 採用開放標準
 
-[Open standards](../glossary.md#open-standard) guarantee access to the knowledge required to use and contribute to the [codebase](../glossary.md#codebase).
-They enable interoperability between systems and reduce the risk of vendor lock-in.
-Open standards which are unambiguous allow for independent development of either side of data exchange.
+[開放標準](../glossary.md#open-standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的
+知識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明確，就可以獨立發展任何方向的資料交換。
 
-## Requirements
+## 規定
 
-* For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the [Open Source Initiative Open Standard Requirements](https://opensource.org/osr).
-* Any non-open standards used MUST be recorded clearly as such in the documentation.
-* Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.
-* Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.
-* If no existing open standard is available, effort SHOULD be put into developing one.
-* Open standards that are machine testable SHOULD be preferred over open standards that are not.
-* Non-open standards that are machine testable SHOULD be preferred over non-open standards that are not.
+* 代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。
+* 如果有使用到任何的非開放標準，則必須在文件中清楚記錄。
+* 代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。
+* 代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。
+* 如果還沒有已存在的開放標準可採用，則應該投入開發新標準。
+* 採用開放標準時，應該優先選擇可經機器測試的開放標準。
+* 採用非開放標準時，應該優先選擇可經機器測試的非開放標準。
 
-## How to test
+## 測試方式
 
-* Confirm that data exchange follows an OSI approved open standard.
-* Confirm that any non-open standards used are clearly documented as such.
-* Confirm that documentation includes a list of the standards followed within the codebase, each with a working link, or a statement that no standards were chosen.
+* 確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。
+* 確認若有採用任何的非開放標準，皆有清楚記錄在文件中。
+* 確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Mandate use of open standards everywhere possible.
-* Prohibit procurement of technology that does not use open standards.
+* 以政策要求盡可能在任何情況下使用開放標準。
+* 禁止採購不採用開放標準的技術科技。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Consider including open standard compliance assessment in [source code](../glossary.md#source-code) reviews.
+* 考慮在 [原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Add [continuous integration](../glossary.md#continuous-integration) tests for compliance with the standards.
-* Review the commits and other [repository](../glossary.md#repository) resources for references to standards and cross-check those with the standards listed.
+* 將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。
+* 審查提交紀錄與其他[儲存庫](../glossary.md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。
 
-## Further reading
+## 延伸閱讀
 
-* [Open Standards principles](https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles), [policy](../glossary.md#policy) paper of the UK Cabinet Office.
+* 英國內閣辦公室發表的《[開放標準原
+則](https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles)》
+[政策](../glossary.md#policy)報告。
diff --git a/criteria/use-plain-english.md b/criteria/use-plain-english.md
index a5aee480..acc38fb3 100644
--- a/criteria/use-plain-english.md
+++ b/criteria/use-plain-english.md
@@ -5,52 +5,56 @@ order: 10
 redirect_from:
   - criteria/understandable-english-first
 ---
-# Use plain English
+# 使用白話的英語
 
-English is the <i>de facto</i> language of collaboration in software development.
+英文是軟體開發的 <i>慣用</i>協作語言。
 
-Public sector information needs to be accessible to all its constituents.
-Plain and simple language makes the [code](../glossary.md#code) and what it does easier to understand for a wider variety of people.
+選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。
 
-Translations further increase the possible reach of a [codebase](../glossary.md#codebase).
-Language that is easy to understand lowers the cost of creating and maintaining translations.
+透過翻譯可以讓更多人認識[代碼庫](../glossary.md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。
 
-## Requirements
+## 規定
 
-* All codebase documentation MUST be in English.
-* All [source code](../glossary.md#source-code) MUST be in English, except where [policy](../glossary.md#policy) is machine interpreted as code.
-* All bundled policy not available in English MUST have an accompanying summary in English.
-* Any translation MUST be up to date with the English version and vice versa.
-* There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.
-* Documentation SHOULD aim for a lower secondary education reading level, as recommended by the [Web Content Accessibility Guidelines 2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable).
-* Providing a translation of any code, documentation or tests is OPTIONAL.
+* 代碼庫的所有文件都必須使用英語。
+* 所有[原始碼](../glossary.md#source-code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀
+當作程式碼的部分則除外。
+* 任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。
+* 任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。
+* 代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
+* 根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/?
+showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。
+* 可選擇是否提供任何程式碼、文件、測試等的翻譯版。
 
-## How to test
+## 測試方式
 
-* Confirm that codebase documentation is available in English.
-* Confirm that source code is in English, or confirm any non-English is policy or terms with preceding explanations.
-* Confirm any non-English policy has an accompanying summary in English.
-* Confirm that translations and the English version have the same content.
-* Check that no unexplained acronyms, abbreviations, puns or legal/non-English/domain specific terms are in the documentation.
-* Check the spelling, grammar and readability of the documentation.
+* 確認代碼庫文件有英語版本。
+* 確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。
+* 確認任何非英語政策都有隨附英語版摘要。
+* 確認翻譯版與英語版內容相同。
+* 確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。
+* 檢查文件的拼字、文法與易讀性等。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Frequently test with other managers, developers and designers in the process if they understand what you are delivering and how you document it.
+* 在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Try to limit the use of acronyms, abbreviations, puns or legal/non-English/domain specific terms in internal communications in and between teams and stakeholders. Add any such terms to a glossary and link to it from the places they are being used.
-* Be critical of documentation and descriptions in proposals and changes. If you don't understand something, others will probably also struggle with it.
+* 在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在
+使用這些詞彙的地方加上詞彙表連結。
+* 以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-* Frequently test with policy makers and managers if they understand what you are delivering and how you document it.
-* Ask someone outside of your context if they understand the content (for example, a developer working on a different codebase).
+* 經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
+* 詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
 
-* Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content readable and understandable.
-* The[European Union accessibility directive](https://ec.europa.eu/digital-single-market/en/web-accessibility) by the European Commission, is an example of regulation requiring high accessibility.
-* [Definition of plain language](https://www.plainlanguage.gov/about/definitions/) by United States General Services Administration.
+* 根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 之可讀
+性](https://www.w3.org/TR/WCAG21/#readable)》內文，撰寫的文字內容要更容易閱讀與理解。
+* 歐盟委員會的《[歐盟無障礙環境命
+令](https://ec.europa.eu/digital-single-market/en/web-accessibility)》就是無障礙法規的例
+子。
+* 美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/)》。
diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index d8b8ce89..938e70d4 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -5,58 +5,58 @@ order: 4
 redirect_from:
   - criteria/open-to-contributions
 ---
-# Welcome contributors
+# 歡迎貢獻者
 
-The atmosphere in a [codebase](../glossary.md#codebase) community helps users decide to use one codebase over another.
-Welcoming anyone as a contributor enables the community to grow and sustain itself over time.
-A community where contributors have clear ways to influence codebase and community goals and progress is less likely to split and end up in diverging communities.
-Newcomers need to understand and trust the codebase community’s governance.
+[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當
+中，若貢獻者有明確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並且相信代碼庫社群的治理。
 
-## Requirements
+## 規定
 
-* The codebase MUST allow anyone to submit suggestions for changes to the codebase.
-* The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file.
-* The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file.
-* The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.
-* The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.
-* The codebase SHOULD have a publicly available roadmap.
-* The codebase SHOULD publish codebase activity statistics.
-* Including a code of conduct for contributors in the codebase is OPTIONAL.
+* 代碼庫必須允許任何人針對代碼庫提出修改建議。
+* 代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
+* 代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
+* 貢獻指引應該說明由誰負責審查貢獻的成本。
+* 代碼庫應該宣布投入其開發與維護工作的參與組織單位。
+* 代碼庫應該要有可公開取得的發展路線圖。
+* 代碼庫應該公布代碼庫的活動統計數據。
+* 可選擇是否為代碼庫加入貢獻者的行為準則。
 
-## How to test
+## 測試方式
 
-* Confirm that it is possible to submit suggestions for changes to the codebase.
-* Confirm there are contribution guidelines.
-* Confirm that the codebase governance is clearly explained, including how to influence codebase governance.
-* Check that contributing guidelines cover who is expected to cover the costs of reviewing contributions.
-* Check for a list of involved organizations.
-* Check for a roadmap.
-* Check for published activity statistics.
-* Check for a code of conduct.
+* 確認可以提交修改建議給代碼庫。
+* 確認代碼庫有貢獻指引。
+* 確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。
+* 確認貢獻指引是否有說明由誰負責審查貢獻的成本。
+* 檢查是否有參與的組織單位名單。
+* 檢查是否有發展路線圖。
+* 檢查是否有公布活動統計數據。
+* 檢查是否有行為準則。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-* Add a list to the codebase of any other resources that [policy](../glossary.md#policy) experts, non-governmental organizations and academics would find useful for understanding or reusing your policy.
-* Consider adding contact details so that other policy makers considering collaboration can ask you for advice.
+* 為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。
+* 考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-* Make sure that the documentation of the governance includes the current process for how to make changes to the governance.
-* If the community has some consensus about how the governance should change, then include those ideas stated as ambitions in the documentation.
-* If needed, make sure you have allocated budget for the contributions review process as agreed by the codebase community.
-* Make sure the documentation explains how each organization is involved in the codebase, what resources it has available for it and for how long.
-* Support your experienced policy makers, developers and designers to stay part of the community for as long as possible.
+* 確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。
+* 如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。
+* 若有需要，確保如同代碼庫社群所同意的，編列貢獻審查流程的預算。
+* 確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。
+* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
 
 <p style="page-break-after: always;"></p>
 ## Developers and designers: what you need to do
 
-* Respond promptly to requests.
-* Keep your managers informed of the time and resources you require to support other contributors.
-* Communicate clearly to contributors what they need to do make sure their contribution can be integrated.
+* 快速回應請求。
+* 告知管理人員您支持其他貢獻者時所需的時間與資源。
+* 清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式碼中。
 
-## Further reading
+## 延伸閱讀
 
-* [Building welcoming communities](https://opensource.guide/building-community/) by Open Source Guides.
-* [The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/) by Mike McQuaid.
-* [Leadership and governance](https://opensource.guide/leadership-and-governance/) for growing [open source](../glossary.md#open-source) community projects, by Open Source Guides.
-* [Building online communities](http://hintjens.com/blog:117) by Pieter Hintjens (long read!).
+* 開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
+* Mike McQuaid《[開放原始碼貢獻者瓶
+頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
+* 開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治
+理](https://opensource.guide/leadership-and-governance/)》。
+* Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。
diff --git a/docker.sh b/docker.sh
index 08acd8f3..b5f3ab98 100644
--- a/docker.sh
+++ b/docker.sh
@@ -1,6 +1,9 @@
 #!/bin/bash
+
+path=`pwd`
 docker run -d \
-    -v ./:/var/www/html \
+    -v ${path}:/var/www/html \
+    -v ${path}/docker/apache-data:/etc/apache2/sites-available \
     -p 8090:80 \
     --name=standard \
     steps/standard
diff --git a/docker/apache-data/000-default.conf b/docker/apache-data/000-default.conf
new file mode 100644
index 00000000..72b4196e
--- /dev/null
+++ b/docker/apache-data/000-default.conf
@@ -0,0 +1,34 @@
+<VirtualHost *:80>
+	# The ServerName directive sets the request scheme, hostname and port that
+	# the server uses to identify itself. This is used when creating
+	# redirection URLs. In the context of virtual hosts, the ServerName
+	# specifies what hostname must appear in the request's Host: header to
+	# match this virtual host. For the default virtual host (this file) this
+	# value is not decisive as it is used as a last resort host regardless.
+	# However, you must set it for any further virtual host explicitly.
+	#ServerName www.example.com
+
+	ServerAdmin webmaster@localhost
+	DocumentRoot /var/www/html/_site
+    <Directory /var/www/html/_site>
+        AllowOverride All
+    </Directory>
+
+	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
+	# error, crit, alert, emerg.
+	# It is also possible to configure the loglevel for particular
+	# modules, e.g.
+	#LogLevel info ssl:warn
+
+	ErrorLog ${APACHE_LOG_DIR}/error.log
+	CustomLog ${APACHE_LOG_DIR}/access.log combined
+
+	# For most configuration files from conf-available/, which are
+	# enabled or disabled at a global level, it is possible to
+	# include a line for only one particular virtual host. For example the
+	# following line enables the CGI configuration for this host only
+	# after it has been globally disabled with "a2disconf".
+	#Include conf-available/serve-cgi-bin.conf
+</VirtualHost>
+
+# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
diff --git a/docs/printing.md b/docs/printing.md
index 7994c3b2..24cbcb46 100644
--- a/docs/printing.md
+++ b/docs/printing.md
@@ -1,22 +1,22 @@
-# Printing
+# 印刷
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-The printed Standard for Public Code is printed by Reclameland.
-This guide tries to provide the relevant information to print it there or somewhere else.
+The Standard for Public Code 由 Reclameland 負責印刷。本指南提供印刷相關資訊，方便在 Reclameland 或其他地方印
+刷。
 
-Details, mostly in order they are on the Reclameland page with the Dutch if necessary:
+印刷詳細資訊（依照 Reclameland 網頁上的順序，需要的地方有附上荷蘭語）：
 
-* Form: Softcover book ([Reclameland product page](https://www.reclameland.nl/drukken/softcover-boeken))
-* Format: A4
-* Portrait or landscape: Portrait (Staand)
-* Printing inside: 4/4 dual sided full color
-* Inside material: 90 grams biotop
-* Cover: 350 grams cover
-* Printing cover: 4/0 one sided full cover
-* Cover treatment: one sided matt foliated (Enke)
-* Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a multiple of 4
-* Individually sealed: no
+* 樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/softcover-boeken))
+* 紙張尺寸：A4
+* 直橫向：直向（Staand）
+* 內頁印刷：正四反四，雙面全色印刷
+* 內頁材質：Biotop 90克
+* 封面：350克封面
+* 封面印刷：正四（單面滿版印刷）
+* 封面材質：單面霧面立體字封面（Enke）
+* 頁數：書內頁數 + 4 + x，x 是 0-3頁，因此總頁數是4的倍數
+* 個別封裝：無
 
-When these details are chosen, the cover and insides are uploaded and the order is placed payment can happen (payment ahead) after which printing starts.
+一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。
diff --git a/docs/releasing.md b/docs/releasing.md
index caada9f9..d9d44ade 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -1,39 +1,46 @@
-# Releasing a new version of the Standard for public code
+# 發行新版本的 The Standard for Public Code
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-1. Review state of the 'develop' branch
-    - Ensure all changes intended for release are merged
-    - Invite a proofread of the current state of the branch
-        - If new dashes are introduced, check if the language can be simplified to remove them in favor of more simple sentences. If a complex sentence is needed, see if the dash can be replaced with other punctuation. If a dash is truly the best expression of ideas, then follow the [Chicago Manual of Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash).
-2. Create a release branch
-    - From 'develop', `git switch -c "release-$MAJOR.$MINOR.$PATCH"`
-    - Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`
-3. Update the new release
-    - [ ] Update [`AUTHORS.md`](../AUTHORS.md) with new contributors
-    - [ ] Update [`CHANGELOG.md`](../CHANGELOG.md)
-    - [ ] Update [`roadmap.md`](roadmap.md)
-    - [ ] Perform extra pass on diff to the 'main' branch
-        - run `script/generate-review-template.sh` and commit updated `docs/review-template.html`
-        - update `docs/standard-for-public-code.html` with the new text from the review template, updating any status changes as a result
-        - Reread any section or paragraph to ensure wording changes still fit the whole and do not contain grammar or spelling errors
-        - Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see: `script/ensure-font.sh`
-        - Check the rendered `.pdf` using `script/pdf.sh rc1`
-          - Ensure no link collisions exist
-          - Check the page breaks, possibly removing or adding page-break CSS, for example: `<p style="page-break-after: always;"></p>`
-        - If needed, commit fixes and repeat extra pass
-    - [ ] Push branch, compare with 'main' branch, i.e.: `https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`
-        - Request review from multiple reviewers, especially a proofreader
-        - Reviewers will create issues for shortcomings found which would not prevent release
-        - If needed for release, reviewers may create pull requests to resolve issues
-        - Re-request reviews if additional pull requests are merged into release branch
-    - [ ] Run the to-archive-org.sh script
-4. Create GitHub release with the release notes and version number
-    - [ ] `git tag trigger-$MAJOR.$MINOR.$PATCH`
-    - [ ] `git push --tags` (see: `../.github/workflows/release-on-tag.yml`)
-    - [ ] delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`
-5. [Send the files for print to the printer](printing.md)
-    - [ ] Cover file
-    - [ ] Inside pages PDF
-6. Ping [translation](https://github.com/publiccodenet/community-translations-standard) contributors
+1. 審查「develop」分支狀態
+   - 確保該版本的內容都已經完成合併
+   - 請人校對目前的分支狀態
+      - 如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達該句子的
+涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)。
+
+1. 建立發佈分支
+   - 從 'develop'、`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
+   - 推動分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`
+
+1. 更新新版本
+   - [ ] 在[`AUTHORS.md`](../AUTHORS.md)加入新貢獻者資料
+   - [ ] 更新[`CHANGELOG.md`](../CHANGELOG.md)
+   - [ ] 更新 [`roadmap.md`](roadmap.md)
+   - [ ] 在 diff 進行額外傳輸到 'main' 分支
+      - 執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-template.html`
+      - 使用審查範本的新文字更新 `docs/standard-for-public-code.html`，根據結果更新任何狀態
+      - 重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼字錯誤
+      - 確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/ensure-font.sh`
+      - 使用 `script/pdf.sh rc1` 檢視渲染的 `.pdf`
+         - 確保沒有連結相衝的問題
+         - 移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style="page-break-after: always;"></p>`
+      - 若需要，進行修復並且重複進行額外傳輸
+   - [ ] 推送分支，與 `main` 分支比較，如：
+`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`
+      - 要求多位審查人員（特別是校對人員）進行審查
+      - 審查人員若有發現不會影響發行的缺失，則會建立議題
+      - 如果是發行所需，審查人員可以建立拉入請求來解決問題
+      - 若額外的拉入請求合併至發行分支，請要求重新審查
+   - [ ] 執行「to-archive-org.sh」腳本
+
+1. 在 GItHub 上發行，並且附上發行說明與版本號碼
+   - [ ] `git tag trigger-$MAJOR.$MINOR.$PATCH`
+   - [ ] `git push --tags` (see: `../.github/workflows/release-on-tag.yml`)
+   - [ ] 移除本地端的標籤（tag）：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`
+
+1. [將印刷檔案傳送至印刷廠](printing.md)
+   - [ ] 封面檔案
+   - [ ] 內頁 PDF
+
+1. 標記[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 40e5f47d..873dacae 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -1,33 +1,34 @@
-# Roadmap
+# 發展路線圖
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-Last updated: 2023-03-08
+上次更新時間：2023-03-08
 
-This document intends to shed light on the current development plans of the team.
-Plans change constantly as new information is absorbed by the team.
+本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變動。
 
-Codebase stewards review the roadmap monthly as part of our [backlog pruning session](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html).
+代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會
+議](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
+的一部份。
 
-## Current work
+## 目前任務
 
-* As far as possible, make the standard Standard-compliant
-* Certification badges
+* 盡可能讓標準符合 The Standard for Public Code
+* 認證標章
 
-## Near term
+## 近期
 
-* Separate executive summary (issue #302)
-* Physical paper checklist
-* Possibly: add in the illustrations for each criterion
+* 分離執行摘要 (issue #302)
+* 實體檢查清單
+* 潛在解決方案：為每個標準新增圖示
 
-## Longer term
+## 長期
 
-* Add to README and index.md information (and eventually statistics) on adoption and use (issue #438)
-* Becoming validated by multiple codebases
-* Release version 1.0.0 after a few codebases are compliant
-* Linkable requirements
-* New cover art
-* Register for ISBN
-* List with an on-demand book printing service
-* QR codes for external links in print version
+* 新增「README」與「index.md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上
+* 取得多個代碼庫認證
+* 在幾個代碼庫符合標準後，推出 1.0.0 版
+* 可連結需求規範
+* 新封面設計
+* 申請 ISBN 書號
+* 隨選書籍列印服務廠商清單
+* 印刷版外部連結的 QR 二維碼
diff --git a/foreword.md b/foreword.md
index 069f2207..d234a136 100644
--- a/foreword.md
+++ b/foreword.md
@@ -4,174 +4,160 @@
 redirect_from:
   - introduction
 ---
-# Foreword
+# 序
 
-The Standard for Public Code is a set of criteria that support public organizations in developing and maintaining software and policy together.
+The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。
 
-Anyone developing public-purpose software or policy can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control.
+開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成本效益、風險更低且能夠掌控。
 
-This foreword introduces the term public code and explains why this is important.
+「序」介紹何謂「公共程式」以及其重要性。
 
-## Definition of public code
+## 公共程式定義
 
-Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
-It encompasses the software built to operate with and as public infrastructure, along with the arrangements for its production.
-Public code is explicitly distinct from regular software because it operates under fundamentally different circumstances and expectations.
+公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體生產的安排，
+都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件與期待也不同。
 
-## Reasons for public code
+## 使用公共程式的原因
 
-There are many reasons for why public code is relevant now.
+公共程式現在如此重要，背後有幾個原因。
 
-### Software code == legal code
+### 軟體程式碼 == 政府法規
 
-Software is public infrastructure.
+軟體是公共基礎建設。
 
-In the 21st century, software can be considered vital public infrastructure.
-It is increasingly not just the expression of existing policy but the originator of new policy, for example where algorithms decide which districts need extra social services or policing.
+在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。
 
-Software mechanics, algorithms and data collection have become key elements in the execution of public policies.
-Computer code now executes policies that have been codified in legal code through democratic procedures.
-Both forms of code set conditions for society to function according to democratically set public values, the latter executed by humans, the former by machines.
-In other words, software code has increasingly started to equal legal code.
+在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共價值，設定社
+會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體程式越來越接近法規的地位。
 
-Software should therefore be subject to the principles of democratic governance.
+因此軟體也應該接受民主治理原則的約束。
 
-### Traditional public software procurement
+### 傳統的公共軟體採購方式
 
-Current public software production methods have not served public service delivery very well.
+目前的公共軟體生產模式，在交付公共服務上的效率並不高。
 
-In the last decade, public organizations that purchased complete software solutions have sometimes been surprised to discover that they:
+過去十年購買完整軟體解決方案的公共組織，都很訝異地發現：
 
-* can’t change their software to reflect changing policy or take advantage of new technology
-* don’t have access to their data as it's locked into proprietary systems
-* are asked to pay ever increasing license fees
+* 無法修改軟體來反映政策的變動，或是利用新科技
+* 資料都鎖在專有系統中，無法取得
+* 授權費越來越貴而且還要定期繳納
 
-### Technological sovereignty and democratic accountability
+### 技術主權與民主課責
 
-Public institutions, civil servants and residents deserve better.
+公共機關、公僕與市民都值得更好的。
 
-We believe the software that runs our society can no longer be a black box, controlled by outside companies that keep the underlying logic on which their software operates hidden in proprietary codebases.
-Instead, governments and the people they serve need technological sovereignty.
-This allows them to set and control the functioning of public software, just like they are able to set and control policy that is legally formulated in laws.
-Citizens and civil society actors need this software to be transparent and accountable.
+我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都需要技術主
+權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。
 
-The design of software as essential civic infrastructure should honor digital citizens’ rights.
+設計為必要公民基礎建設的軟體，也應該尊重數位公民的權益。
 
-### Designing truly public software
+### 設計真正屬乎民眾的軟體
 
-Public code is at the core of modern public institutions, shapes the work of civil servants and affects the lives of almost all residents.
+公共程式是現代公共基礎建設的核心，影響公僕的工作以及幾乎所有市民的生活。
 
-Public software must therefore be:
+因此公共軟體必須：
 
-* transparent
-* accountable
-* understandable for its constituents
+* 透明
+* 負責任
+* 讓選民能夠理解
 
-It must reflect the values of the society it serves, for example by being inclusive and non-discriminatory.
+反映其服務社會的價值觀，像是包容與不歧視。
 
-Most proprietary software systems currently used by public organizations do not meet these requirements.
-Public code does.
+公共組織目前使用的多數專有軟體系統都不符合這些要求，但是公共程式符合。
 
-### Values of public code
+### 公共程式的價值
 
-We consider public code to have these core values:
+我們認為公共程式具有以下核心價值：
 
-* Inclusive
-* Usable
-* Open
-* Legible
-* Accountable
-* Accessible
-* Sustainable
+* 包容
+* 可用
+* 開放
+* 清晰易讀
+* 負責
+* 容易取得
+* 永續
 
-## How public code works
+## 公共程式運作方式
 
-Public code is open source software meant for fulfilling the essential role of public organizations.
-Through use, other administrations contribute back to the software, so that its development and maintenance become truly collaborative.
+公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。
 
-Being open unlocks many other things.
+開放的精神能創造許多可能性。
 
-Local responsibility and democratic accountability are ensured when a public organization implements and maintains their own public code.
-By being open and with a broader contributor base, the software is more secure as it benefits from many eyes spotting potential flaws.
-Many contributors share the maintenance work to keep it functional and modern, which reduces future technical debt.
-The shared workload is more sustainable now and in the future.
-Its openness makes both the code and its data more easily adaptable in the future.
-The code will be easier to retool, repurpose or retire.
-This all results in lower risk public infrastructure.
+公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高。許多貢獻者
+會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼與資料，在未來也更容易
+改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都讓公共基礎建設風險更低。
 
-This pooling of resources lets public administrations give extra attention to how to customize the software so it works best in each local context, creating better user experiences for their end users (residents or citizens).
+集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。
 
-### Economics of public code
+### 公共程式的經濟
 
-Public code offers a better economic model for public organizations as well as for commercial companies.
-It's an alternative to traditional software procurement which increases local control and economic opportunity.
+公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助各地的公共組織更能控制程式，也有更好的經濟機會。
 
-Designed from the start to be open, adaptable and with data portability, it can be developed by in-house staff or trusted vendors.
-Because the code is open, the public administration can change vendors if they need to.
-Open code increases opportunities for public learning and scrutiny, allowing the public administration to procure smaller contracts.
-Smaller procurements are easier for local small and medium enterprises to bid upon.
-Public administrations can use their own software purchasing to stimulate innovation and competition in their local economy.
+公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始碼讓社會大眾
+更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激當地經濟的創新與競
+爭。
 
-This can be seen as investment leading to future economic growth.
-More vendors will be necessary due to growing technology demand.
+這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。
 
-### Procuring public code
+### 採購公共程式
 
-Public code can be used and developed by permanent in-house development teams, contractors or outsourced suppliers.
-Vendors to public organizations can include public code in their bids for contracts.
+公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可以包含公共程式。
 
-To use existing public code, you need to specify in your budget and project design that your new solution will use that codebase.
-To encourage an innovative approach to adapting the public code to your context, you could describe the service or outcome in your contract.
+若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您的服務或成
+果。
 
-## The goals for the Standard for Public Code
+## The Standard for Public Code 目標
 
-This Standard supports developers, designers, managers and public policy makers to:
+The Standard for Public Code 支持開發人員、設計師、管理人員以及公共政策制定者：
 
-* develop high quality software and policy for better public service delivery
-* develop codebases that can be reused across contexts and collaboratively maintained
-* reduce technical debt and project failure rate
-* have more granular control over, and ability to make decisions about, their IT systems
-* improve vendor relationships with a better economic model
+* 開發優質軟體與政策，改善公共服務的交付
+* 開發能在各種情境下重複使用且共同維護的代碼庫
+* 減少技術債與專案失敗率
+* 更能精細控制 IT 系統並且做出 IT 系統相關決策
+* 更好的經濟模型改善與供應商的關係
 
-Potential users of codebases tested against the Standard for Public Code can expect them to be highly reusable, easily maintainable and of high quality.
+代碼庫潛在使用者依照 The Standard for Public Code 測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。
 
-The Standard for Public Code does this by:
+The Standard for Public Code 能有如此特性是因為：
 
-* setting out a common terminology for public code development
-* establishing measures to help develop high quality public code
-* providing guidance on how to fulfill its criteria and operationalize compliance
+* 訂定公共程式開發的通用術語
+* 訂定措施協助優質公共程式的開發
+* 提出如何符合 The Standard for Public Code 的指引並在施作中遵循
 
-The Standard for Public Code is meant to be time and technology independent.
+The Standard for Public Code 原意是要不受時間與科技限制。
 
-### Who this is for
+### 適用對象
 
-The Standard for Public Code is for the people who create and reuse public code:
+The Standard for Public Code 適用於開發與重複使用公共程式的民眾：
 
-* public policy makers
-* business and project managers
-* developers and designers
+* 公共政策制定者
+* 業務與專案經理
+* 開發人員與設計師
 
-These people work at:
+這些人的服務單位：
 
-* institutions, organizations and administrations in the public sector
-* consultancies and vendors of information technology and policy services to public organizations
+* 公家機關的機構、組織與行政單位
+* 服務公家機關的資訊科技以及政策服務顧問公司與供應商
 
-It is not aimed at public organizations' end users (residents or citizens), journalists or academics.
+適用對象不包括公家機關的終端使用者（居民或市民）、記者或學者。
 
-## Further reading
+## 延伸閱讀
 
-* ["Modernising Public Infrastructure with Free Software" white paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) by the Free Software Foundation Europe.
+* 歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮
+書](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) 》。
 
-### Videos on public code
+### 公共程式影片
 
-* [Collaborative Code is the Future of Cities @ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on the background behind the Foundation for Public Code.
-* [Public Money? Public Code! - Panel @ Nextcloud Conference 2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like procurement, law and more.
+* [2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/watch?
+v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹 The Foundation for Public Code 的背景。
+* [ 2019 年 Nextcloud 大會的「公帑？公共程式！」專題討論](https://youtube.com/watch?v=QHFkD4xfd6c)。探
+討採購、法律等主題。
 
-## Get involved
+## 加入我們的行列
 
-This standard is a living document.
-[Read our contributor guide](/CONTRIBUTING.md) to learn how you can make it better.
+此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING.md)，瞭解您可以如何讓此標準變得更好。
 
-## Contact
+## 聯絡方式
 
-For questions and more information about the Foundation for Public Code you can find us at [our website](https://publiccode.net/), email us at info@publiccode.net, or call us at +31 20 2 444 500.
+若有疑問或想進一步瞭解 The Foundation for Public Code，請造訪[我們的官網](https://publiccode.net/)、寄電子
+郵件到 info@publiccode.net，或是撥打我們的電話（+31 20 2 444 500）。
diff --git a/glossary.md b/glossary.md
index 4cb3464e..26bf1e9f 100644
--- a/glossary.md
+++ b/glossary.md
@@ -2,85 +2,75 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
-# Glossary
+# 詞彙表
 
-## Code
+## 規則（Code）
 
-Any explicitly described system of rules.
-This includes laws, policy and ordinances, as well as source code that is used to build software.
-Both of these are rules, some executed by humans and others by machines.
+任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是規則，前者由人類來執行，後者則是機器。
 
-## Codebase
+## 代碼庫
 
-Any discrete package of code (both source and policy), the tests and the documentation required to implement a piece of policy or software.
+執行政策或軟體所需的任何離散程式碼套件（原始碼與政策程式碼）、測試與文件。
 
-This can be, for example, a document or a version-control repository.
+可以是文件或是版本控制的儲存庫。
 
-## Continuous integration
+## 持續整合
 
-In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a development branch of a codebase as frequently as reasonable.
+軟體工程的持續整合 (CI) 就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。
 
-## Different contexts
+## 不同情境
 
-Two contexts are different if they are different public organizations or different departments for which there is not one decision maker that could make collaboration happen naturally.
+如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩個不同的情境。
 
-## General public
+## 一般大眾
 
-The public at large: end users of the code and the services based upon it.
+一般民眾：程式碼及以程式碼為基礎的服務的終端使用者。
 
-For example, a city's residents are considered end users of a city's services and of all code that powers these services.
+舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終端使用者。
 
-## Open source
+## 開源
 
-Open source is defined by the Open Source Initiative in their [Open Source Definition](https://opensource.org/osd-annotated).
+開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》定義何謂「開源」。
 
-## Open standard
+## 開放標準
 
-An open standard is any standard that meets the Open Source Initiative's [Open Standard Requirements](https://opensource.org/osr).
+任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/osr)的標準就是開放標準。
 
-## Policy
+## 政策
 
-A policy is a deliberate system of principles to guide decisions and achieve rational outcomes.
-A policy is a statement of intent, and is implemented as a procedure or protocol.
-Policies are generally adopted by a governance body within an organization.
-Policies can assist in both subjective and objective decision making.
+政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。
 
-Public policy is the process by which governments translate their political vision into programs and actions to deliver outcomes.
+公共政策是政府將其政治理念轉化成計畫與行動的流程，藉此取得成果。
 
-At the national level, policy and legislation (the law) are usually separate.
-The distinction is often more blurred in local government.
+在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一起。
 
-In the Standard the word 'policy' refers to policy created and adopted by public organizations such as governments and municipalities.
+The Standard for Public Code 當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。
 
-## Public code
+## 公共程式
 
-Public code is open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+公共程式是由公家機關開發的開源軟體，當中包括協作與重複利用所需的政策與指引。
 
-Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及公共政策。
 
-Public code serves the public interest, is open, legible, accountable, accessible and sustainable.
+滿足公共利益的公共程式，具有開放、易讀、負責、可用以及永續的特性。
 
-By developing public code independently from but still implementable in the local context for which it was developed, as well as documenting the development process openly, public code can provide a building block for others to:
+為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以：
 
-* re-implement in their local context
-* take as a starting point to continue development
-* use as a basis for learning
+* 將該公共程式應用於他們的當地情境
+* 將該公共程式當成起點並接著繼續開發
+* 當成學習的基礎
 
-To facilitate reuse, public code is either released into the public domain or licensed with an open license that permits others to view and reuse the work freely and to produce derivative works.
+為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複利用其內容的開放授權，藉此推動衍生工作。
 
-## Repository
+## 儲存庫
 
-A repository is a storage location used by version control tools for files and metadata of a codebase.
-Repositories allow multiple contributors to work on the same set of files.
-Repositories are able to store multiple versions of sets of files.
+儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。
 
-## Source Code
+## 原始碼
 
-Human readable text of a computer program which can be translated into machine instructions.
+人類可讀並且能夠翻譯成機器指令的電腦程式文字。
 
-## Version control
+## 版本控制
 
-Version control is the management of changes to source code and the files associated with it.
-Changes are usually identified by a code, termed the *revision number* (or similar).
-Each revision is associated with the time it was made and the person making the change, thus making it easier to retrace the evolution of the code.
-Revision control systems can be used to compare different versions with each other and to see how content has changed over time.
+版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程式碼的演變。
+修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。
diff --git a/index.md b/index.md
index 1700ac9e..1d3ef901 100644
--- a/index.md
+++ b/index.md
@@ -3,44 +3,49 @@
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 toc: false
 ---
-# Guidance for government open source collaboration
+# 政府開源協作指引
 
-The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together.
+The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。
 
-The Standard for Public Code provides guidance to public organizations building their own open source solutions to enable successful future collaboration and reuse by similar organizations in the public sector in other places.
-It includes advice for policy makers, government managers, developers and vendors.
-The Standard for Public Code supports the collaborative creation of codebases that are usable, open, legible, accountable, accessible and sustainable.
-It is meant to be applicable to codebases for all levels of government, from supranational to municipal.
+The Standard for Public Code 指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利
+用前述開源解決方案。The Standard for Public Code 提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The
+Standard for Public Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The Standard for Public Code 適用於
+各政府層級的代碼庫，從超國家到市政府。
 
-The Standard for Public Code defines ‘[public code](glossary.md#public-code)’ as open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+The Standard for Public Code 將‘[公共程式](glossary.md#public-code)’定義為由公共組織所開發的開源軟體，並且
+遵照相關政策與指引，方便協作與重複利用。
 
-The criteria of the Standard for Public Code are aligned with guidelines and best practices of open source software development.
+The Standard for Public Code 當中的標準符合開源軟體開發的指引與最佳實務。
 
-{% for page in site.pages %}{% if page.name == "foreword.md" %}
-Additional context and background can be found in the [foreword](foreword.md).
-{% endif%}{% endfor %}
+{% for page in site.pages %}{% if page.name == "foreword.md" %} 額外情境與背景資訊請參閱
+[序](foreword.md). {% endif%}{% endfor %}
 
-## Contents
+## 目錄
 
-* [Readers guide: how to interpret this standard](readers-guide.md)
-* [Glossary](glossary.md)
-* [Criteria](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
-  * [{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}
-* [Authors](AUTHORS.md)
-* [Contributing guide](CONTRIBUTING.md)
-* [Code of conduct](CODE_OF_CONDUCT.md)
-* [Governance](GOVERNANCE.md)
-* [Version history](CHANGELOG.md)
-* [License](license.html)
+* [讀者指南：如何詮釋此標準](readers-guide.md)
+* [詞彙表](glossary.md)
+* [標準](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in
+sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{%
+if page.title %}
+   * [{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}
+* [作者群](AUTHORS.md)
+* [貢獻指引](CONTRIBUTING.md)
+* [行為準則](CODE_OF_CONDUCT.md)
+* [治理](GOVERNANCE.md)
+* [版本歷史](CHANGELOG.md)
+* [授權](license.html)
 
-## Community calls
+## 社群會議
 
-We usually have a community call on the first Thursday of the month at 15:00 (CET/CEST).
-[The agenda](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code) is updated roughly a week before the call.
-It is possible to [sign up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842) to get a call invitation emailed to you.
+我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。 [議
+程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code) 在會議
+前約一週的時間更新。您可以 [報
+名](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)，
+之後舉辦會議時會寄送邀情函給您。
 
-## Other resources
+## 其他資源
 
-* Unofficial [community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/) in other languages
-* [Standard compliance self assessment](https://publiccodenet.github.io/assessment-eligibility/) for public sector open source codebases
-* [Standard criteria checklist](/docs/review-template.html) used by Foundation for Public Code stewards for codebase review
+* [The Standard for Public Code 社群其他語
+言](https://publiccodenet.github.io/community-translations-standard/) 非官方翻譯版
+* 公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)
+* [標準資格檢查清單](/docs/review-template.html) 由公共程式基金會管理人員用於代碼庫審查
diff --git a/origin_source/404.md b/origin_source/404.md
new file mode 100644
index 00000000..7a4a22bd
--- /dev/null
+++ b/origin_source/404.md
@@ -0,0 +1,15 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+layout: default
+title: Page not found
+toc: false
+---
+
+# 404 Not Found
+
+If you typed the web address, check it is correct.
+
+If you pasted the web address, check you copied the entire address.
+
+If the web address is correct or you followed a link or button, email the [Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be able to help you out, as well as correct our mistake.
diff --git a/origin_source/AUTHORS.md b/origin_source/AUTHORS.md
new file mode 100644
index 00000000..ef7f3f3a
--- /dev/null
+++ b/origin_source/AUTHORS.md
@@ -0,0 +1,37 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+---
+# Authors
+
+* Alba Roza, [The Foundation for Public Code](https://publiccode.net/)
+* Arnout Engelen
+* Arnout Schuijff, The Foundation for Public Code
+* Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)
+* Ben Cerveny, The Foundation for Public Code
+* Bert Spaan
+* Boris van Hoytema, The Foundation for Public Code
+* Charlotte Heikendorf
+* Claus Mullie, The Foundation for Public Code
+* David Barberi
+* Edo Plantinga, [Code For NL](https://codefor.nl/)
+* Elena Findley-de Regt, The Foundation for Public Code
+* Eric Herman, The Foundation for Public Code
+* Felix Faassen, The Foundation for Public Code
+* Floris Deerenberg
+* Jan Ainali, The Foundation for Public Code
+* Johan Groenen, Code For NL
+* Marcus Klaas de Vries
+* Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)
+* Martijn de Waal, [Amsterdam University of Applied Sciences (AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and Creative Industries, Lectorate of Play & Civic Media
+* Matti Schneider
+* Mauko Quiroga
+* Maurice Hendriks, Gemeente Amsterdam
+* Maurits van der Schee, Gemeente Amsterdam
+* Mirjam van Tiel, The Foundation for Public Code
+* Ngô Ngọc Đức Huy
+* Paul Keller
+* Petteri Kivimäki, [Nordic Institute for Interoperability Solutions (NIIS)](https://niis.org)
+* Sky Bristol
+* Tamas Erkelens, Gemeente Amsterdam
+* Timo Slinger
diff --git a/origin_source/CC0-1.0.md b/origin_source/CC0-1.0.md
new file mode 100644
index 00000000..7cadbfc4
--- /dev/null
+++ b/origin_source/CC0-1.0.md
@@ -0,0 +1,19 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+toc: false
+redirect_from:
+    - license.html
+    - LICENSE.html
+---
+
+# Creative Commons Zero v1.0 Universal
+
+<!-- TODO FIXME: move styling to the proper place, not inline html -->
+<style>.highlight { flex: 2 2 80%; max-width: 100%; } </style>
+
+This license is the legal contract that allows anyone to do anything they like with the content in this entire document.
+
+```text
+{% include_relative LICENSE %}
+```
diff --git a/origin_source/CHANGELOG.md b/origin_source/CHANGELOG.md
new file mode 100644
index 00000000..8464dc27
--- /dev/null
+++ b/origin_source/CHANGELOG.md
@@ -0,0 +1,247 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+# script/release-body.sh expects VERSION in the first second-level header
+# script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon
+---
+# Version history
+
+## Version 0.7.1
+
+July 31st 2023: 💄 The sixteenth draft change the name of a criterion and clarifies references to code.
+
+* The criterion "Make the codebase reusable and portable" was renamed from "Create reusable and portable code".
+* Added a glossary entry for "Source Code".
+* References to "code" which only applied to "source code" now reference "source code" explicitly.
+* Clarification of "running code" as "software".
+* Minor changes to clarify "code" vs "codebase".
+* Simplify guidance to policy makers in Bundle policy and source code.
+* Clarify How to test sections of Make the codebase findable and Make the codebase reusable and portable.
+* Add a criteria and requirements checklist to the release artifacts.
+* Increase automation of the release process.
+
+## Version 0.7.0
+
+May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting review funding and clarifies review process requirement.
+
+* Add requirement to document who is expected to cover the cost of reviewing contributions.
+* Add requirement to have a short description of the codebase.
+* Change the focus of contributions adhering to standards to focus on the review of contributions.
+* Relaxed MUST requirements to SHOULD in Make the codebase findable.
+* Review template now in HTML format.
+* Introduction converted to foreword.
+* Improved contributing guidelines.
+* Improved documentation of scripts.
+
+## Version 0.6.0
+
+April 20th 2023: 🔀 the fourteenth draft adds new requirements for portability and tests and an introduction to each criterion.
+
+* New requirement in Create reusable and portable code about the development being a collaboration between multiple parties.
+* New requirement in Create reusable and portable code about being dependent on a single vendor.
+* New requirement in Use continuous integration about publishing results for automated tests.
+* Differentiating the two requirements about security to clearly be about providing a method and having documentation about it.
+* Rephrased requirements to focus on the codebase rather than contributor behavior.
+* Removed the sections Why this is important and What this does not do and replaced with an introduction in each criterion.
+* Added general What this does not do section in the introduction of the Standard.
+* Added guidance for public policy makers about related policies and license compatibility.
+* Added guidance for developers and designers about version controlling files.
+* Clarified guidance for developers and designers about prompt responses and search engine optimization.
+* Added Further reading about accessibility.
+* Aligned criteria URLs with criteria names.
+* Improved navigation in the web version.
+* Moved tools in Further reading sections to the community implementation guide.
+* Moved compliance or certification process to [publiccode.net](https://publiccode.net).
+* Change format of the review template to make it easier to update after a new release.
+* Improved the text on the landing page and added links to related resources.
+* Added spell checker automated test.
+* Made minor changes to text for clarity and consistency.
+* Moved SPDX headers to yaml header.
+
+## Version 0.5.0
+
+January 25th 2023: 🎨 the thirteenth draft focuses on documenting style guidelines.
+
+* Adjust the coding style requirement to focus on the codebase using a style guide rather than contributor behavior.
+* Moved requirement for codebase names to Make the codebase findable from Use plain English.
+* Moved requirement about testing the code by using examples to Use continuous integration from Document the code.
+* Split requirement about machine testable standards to clarify that open is more important than testable.
+* Adjust how to test findability requirements to be less reliant on search engine algorithms.
+* Made minor changes to text for clarity and consistency.
+
+## Version 0.4.1
+
+December 5th 2022: 📝 the twelfth draft clarifies document maturity.
+
+* Document maturity focuses on whether or not versions of the codebase are ready to use.
+* Document maturity no longer requires specific labels for codebases that are not ready to use.
+* Audit flow image now generated from an easier to translate format.
+* Improved guidance on How to test.
+* Add publiccode.yml file.
+* Add review template.
+* Consistently link glossary terms.
+* Add practices and standards to follow in CONTRIBUTING.
+* Add Matti Schneider to Authors.
+* Add remaining SPDX headers to files.
+* Made additional minor changes to text for clarity.
+* Some hyperlinks updated.
+* Moved examples to the [Community implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/).
+
+## Version 0.4.0
+
+September 7th 2022: 🔭 the eleventh draft adds a new findability criterion.
+
+* Introduce new criterion: Make the codebase findable.
+* Improve How to test section for most criteria.
+* New requirement in Welcome contributors about publishing activity statistics.
+* Removed redundant requirement about portable and reusable code.
+* Expand open license definition to include both OSI and FSF approved licenses.
+* Rephrase MAY requirements to use the keyword OPTIONAL for clarity.
+* Expressed intent that the Standard for Public Code should meet its own requirements where applicable and added assessment.
+* Add SPDX license identifiers to files.
+* Introduced new Code of Conduct.
+* Clarify distinction between source code and policy text.
+* Restructuring of requirements with bullet point lists.
+* Acknowledge the importance of codebase modularity for reuse.
+* Move requirements related to Findability to the new criterion.
+* Clarify the role of non-open standards when used in a codebase.
+* Additional guidance about build-time and runtime dependencies.
+* Added roadmap for the development of the Standard for Public Code.
+* Update structure of Authors file.
+* Add Audrey Tang to Authors.
+* Added a list of criteria to the print edition.
+* Clarify what the standard means with policymakers, managers, developers and designers.
+* Made additional minor changes to text for clarity.
+* Some hyperlinks updated.
+
+## Version 0.3.0
+
+May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization.
+
+* Requirement for localization made explicit in Create reusable and portable code.
+* Documentation of governance changed from a SHOULD to a MUST.
+* Replace the very subjective (and hard to test) "contributions MUST be small" with requirement to document expectation in contributing guidelines and focus on a single issue.
+* Community translations now linked in the footer.
+* Revert "Replace BPMN svg with Mermaid flowchart".
+* Many minor clarifications to language and sentences made more simple.
+* Some hyperlinks updated.
+
+## Version 0.2.3
+
+March 15th 2022: 📜 the ninth draft allows English summaries for policy lacking an official translation.
+
+* Relax the criterion Use plain English by adding a new requirement allows bundled policy not available in English to have an accompanying summary in English instead of translating the full text.
+* Similarly, allow for English summaries for policies not available in English in Bundle policy and code.
+* Clarify that term 'policy' includes processes which impact development and deployment in Bundle policy and code.
+* Emphasize reusability also on parts of the solutions in Create reusable and portable code.
+* Expand guidance to Developers and designers in Create reusable and portable code about deploying to proprietary platforms.
+* Add nuance to use of non-English terms in what management need to do in Use plain English.
+* Change the pull request process diagram to use Mermaid instead of BPMN to make [community translations](https://github.com/publiccodenet/community-translations-standard) easier.
+* Added Maurice Hendriks to AUTHORS.
+* Added OpenApi Specification to further reading.
+* Made the attributions in further reading sections clearer.
+* Made additional minor changes to text for clarity.
+
+## Version 0.2.2
+
+November 29th 2021: 🏛 the eighth draft recognizes that policy which executes as code may not be in English.
+
+* Document exception to "All code MUST be in English" where policy is interpreted as code.
+* Add MAY requirement regarding committer email addresses in Maintain version control.
+* Expand guidance to Policy Makers in Bundle policy and code.
+* Expand guidance to Developers and designers in Use a coherent style.
+* Add "Different contexts" to glossary.
+* Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS.
+* Add Digital Public Goods approval badge.
+* Added "next" and "previous" links to criteria pages of web version.
+* Add Open Standards principles to further reading.
+* Add Definition of plain language to further reading.
+* Move the Semantic Versioning Specification further reading reference.
+* Clarify that publiccode.yml is one example of a machine-readable metadata description.
+* Changed "your codebase" and "your organization" to be less possessive.
+* Made additional minor changes to text for clarity.
+* Add instructions for creating a print version.
+
+## Version 0.2.1
+
+March 1st 2021: 🧽 the seventh draft has minor cleaning up after version 0.2.0.
+
+* New SHOULD requirement on using a distributed version control system and why distributed is important.
+* Feedback requirements for rejected contributions are more strict than accepted ones.
+* Specify that copyright and license notices should also be machine-readable.
+* Advice on how to test that notices be machine-readable.
+* Clarify guidance for rolling releases.
+* Clear up definition of version control in glossary.
+* Add further reading encouraging contribution, SPDX, Git and reviewing contributions.
+* Add links to videos about the concept of public code.
+* Update BPMN link.
+* Reduce link duplication.
+* Add Alba Roza and Ngô Ngọc Đức Huy to authors.
+* Made additional minor changes to text for clarity.
+
+## Version 0.2.0
+
+October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity.
+
+* Split "Welcome contributions" criterion into "Make contributing easy" and "Welcome contributors".
+* Rename criterion "Pay attention to codebase maturity" to "Document codebase maturity".
+* Changed MUST to SHOULD for requirement of codebase in use by multiple parties.
+* Add MUST NOT requirement regarding copyright assignment.
+* Clarify role of configuration in reusable code requirement.
+* Glossary additions: continuous integration, policy, repository, and version control.
+* Replace references to 'cities' with 'public organizations'.
+* Clarify aspects of sensitive code by separating contributor and reviewer requirements into separate items.
+* Expand further reading, and guidance to policy makers, developers and designers.
+* Add Felix Faassen and Arnout Engelen to authors.
+* Made additional minor changes to text for clarity.
+
+## Version 0.1.4
+
+November 27th 2019: 🧹 the fifth draft consists mostly of additional minor fixes.
+
+* Linked License.md file.
+* Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors.
+* Made punctuation more consistent, especially for bullet lists.
+* Made some minor changes to text for clarity.
+
+## Version 0.1.3
+
+October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for the autumn cleaning
+
+* Renamed continuous delivery to continuous integration.
+* Referencing accessibility guidelines in the language standard.
+* A bunch of style and consistency fixes.
+
+## Version 0.1.2
+
+August 22th 2019: 🌠 the third draft focuses on better text and takes community input
+
+* With some great new contributors comes a fresh author list.
+* All links are now HTTPS.
+* General proofreading, wording clarifications, and smashed typos.
+* Updated criteria:
+  * Requirement for reuse in different contexts
+  * Recommendation for explicit versioning
+  * Recommendation for multi party development
+  * Recommendation for license headers in files
+  * Recommendation for vulnerability reporting
+  * Recommendation for explicit documentation of governance
+
+## Version 0.1.1
+
+May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a lot of typos
+
+* Removed references to the Foundation for Public Code, we're going to have to change the name in becoming an association.
+* Updated the introduction.
+* Updated the glossary.
+* Added the code of conduct.
+* We've recommended using the publiccode.yml standard for easier reuse.
+
+## Version 0.1.0
+
+April 16th 2019: 🎉 the first draft is ready, it is all brand new and has snazzy new ideas in it
+
+* 14 criteria with their requirements and how to operationalize them.
+* An introduction with a high level background, what this standard is, and how the Foundation for Public Code will use it.
+
+This first version was produced together with the Amsterdam University of Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? Public Code! project](https://smartcities.publiccode.net/).
diff --git a/origin_source/CODE_OF_CONDUCT.md b/origin_source/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..b63243fd
--- /dev/null
+++ b/origin_source/CODE_OF_CONDUCT.md
@@ -0,0 +1,15 @@
+# Code of Conduct
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+Many community members are from civic or professional environments with behavioral codes yet some individuals are not.
+This document expresses expectations of all community members and all interactions regardless of communication channel.
+
+Be here to collaborate.
+
+Be considerate, respectful, and patient.
+
+Strive to be as constructive as possible.
+
+To raise a concern, please email directors@publiccode.net.
diff --git a/origin_source/CONTRIBUTING.md b/origin_source/CONTRIBUTING.md
new file mode 100644
index 00000000..07c6fbab
--- /dev/null
+++ b/origin_source/CONTRIBUTING.md
@@ -0,0 +1,103 @@
+# Contributing to this standard
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+🙇‍♀️ Thank you for contributing!
+
+We understand that a standard like this can only be set in collaboration with as many public technologists, policy makers and interested folk as possible.
+Thus we appreciate your input, enjoy feedback and welcome improvements to this project and are very open to collaboration.
+
+We love issues and pull requests from everyone.
+If you're not comfortable with GitHub, you can email use your feedback at <info@publiccode.net>.
+
+## Problems, suggestions and questions in issues
+
+A high-level overview of the development that we already have sketched out can be seen in the [roadmap](/docs/roadmap.md).
+Please help development by reporting problems, suggesting changes and asking questions.
+To do this, you can [create a GitHub issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue) for this project in the [GitHub Issues for the Standard for Public Code](https://github.com/publiccodenet/standard/issues).
+
+Or, sign up to the [mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) and send an email to
+[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net).
+
+You don't need to change any of our code or documentation to be a contributor!
+
+## Documentation and code in pull requests
+
+If you want to add to the documentation or code of one of our projects you should make a pull request.
+
+If you never used GitHub, get up to speed with [Understanding the GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) or follow one of the great free interactive courses in [GitHub Skills](https://skills.github.com/) on working with GitHub and working with MarkDown, the syntax this project's documentation is in.
+
+This project is licensed Creative Commons Zero v1.0 Universal, which essentially means that the project, along with your contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it.
+
+### 1. Make your changes
+
+Contributions should [follow](docs/standard-for-public-code.html) the requirements set out in the criteria of the Standard for Public code itself.
+Reviewers will also be ensuring that contributions are aligned with the [values of public code](foreword.md#values-of-public-code).
+Furthermore, they will review that the contribution conforms to the [standards](#standards-to-follow) and remains coherent with the overall work.
+
+This project uses the [GitFlow branching model and workflow](https://nvie.com/posts/a-successful-git-branching-model/).
+When you've forked this repository, please make sure to create a feature branch following the GitFlow model.
+
+Add your changes in commits [with a message that explains them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message).
+If more than one type of change is needed, group logically related changes into separate commits.
+For example, white-space fixes could be a separate commit from text content changes.
+When adding new files, select file formats that are easily viewed in a `diff`, for instance, `.svg` is preferable to a binary image.
+Document choices or decisions you make in the commit message, this will enable everyone to be informed of your choices in the future.
+
+If you are adding code, make sure you've added and updated the relevant documentation and tests before you submit your pull request.
+Make sure to write tests that show the behavior of the newly added or changed code.
+
+#### Applicable policy
+
+Currently, the Standard for Public Code is not implementing any specific public policy.
+
+#### Style
+
+The Standard for Public Code aims to [use plain English](criteria/use-plain-english.md) and we have chosen American English for spelling.
+Text content should typically follow one line per sentence, with no line-wrap, in order to make `diff` output easier to view.
+However, we want to emphasize that it is more important that you make your contribution than worry about spelling and typography.
+We will help you get it right in our review process and we also have a separate quality check before [making a new release](docs/releasing.md).
+
+#### Standards to follow
+
+These are the standards that the Standard for Public Code uses.
+Please make sure that your contributions are aligned with them so that they can be merged more easily.
+
+* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level keywords
+* [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability
+
+### 2. Pull request
+
+When submitting the pull request, please accompany it with a description of the problem you are trying to solve and the issue number that this pull request fixes.
+It is preferred for each pull request to address a single issue where possible.
+In some cases a single set of changes may address multiple issues, in which case be sure to list all issue numbers fixed.
+
+### 3. Improve
+
+All contributions have to be reviewed by someone.
+The Foundation for Public Code has committed to make sure that maintainers are available to review contributions with an aim to provide feedback within two business days.
+
+It could be that your contribution can be merged immediately by a maintainer.
+However, usually, a new pull request needs some improvements before it can be merged.
+Other contributors (or helper robots) might have feedback.
+If this is the case the reviewing maintainer will help you improve your documentation and code.
+
+If your documentation and code have passed human review, it is merged.
+
+### 4. Celebrate
+
+Your ideas, documentation and code have become an integral part of this project.
+You are the open source hero we need!
+
+In fact, feel free to open a pull request to add your name to the [`AUTHORS`](AUTHORS.md) file and get eternal attribution.
+
+## Translations in other languages
+
+While the Standard does not have any official translations, you can help maintain existing and add new [community translations of the Standard](https://github.com/publiccodenet/community-translations-standard).
+
+## Releases
+
+We have dedicated documentation for creating [new releases](/docs/releasing.md) and [ordering printed standards](/docs/printing.md).
+
+For more information on how to use and contribute to this project, please read the [`README`](README.md).
diff --git a/origin_source/GOVERNANCE.md b/origin_source/GOVERNANCE.md
new file mode 100644
index 00000000..3a0cfd12
--- /dev/null
+++ b/origin_source/GOVERNANCE.md
@@ -0,0 +1,18 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+---
+# Governance
+
+This standard lies at the core of the codebase stewardship provided by the [Foundation for Public Code](https://publiccode.net/).
+We decide if a codebase is ready for community co-development based on this document.
+
+The standard is maintained by Foundation for Public Code staff.
+
+[We welcome contributions, such as suggestions for changes or general feedback, from anyone.](/CONTRIBUTING.md)
+
+Because of the important role that the Standard for Public Code has in our core process we require the highest standards from the Standard.
+
+We will try to respond promptly to all pull requests.
+The pull request is an opportunity to work together to improve our methods and the Standard.
+We may not accept all changes, but we will explain our logic.
diff --git a/origin_source/README.md b/origin_source/README.md
new file mode 100644
index 00000000..b90f5e3c
--- /dev/null
+++ b/origin_source/README.md
@@ -0,0 +1,107 @@
+# Standard for Public Code
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+The Standard for Public Code gives public organizations a model for preparing open source solutions to enable collaborations with similar public organizations in other places.
+It includes guidance for policy makers, city administrators, developers and vendors.
+
+![version 0.7.1](assets/version-badge.svg)
+[![License: CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
+[![Standard commitment](assets/standard-for-public-code-commitment.svg)](#help-improve-this-standard)
+
+[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
+[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)
+[![standard main badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
+[![standard develop badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
+
+The Standard for Public Code is in a draft format.
+We are preparing it for a version 1.0 release.
+Currently, we are testing it on a small number of codebases.
+
+## Applying the Standard for Public Code to your codebase
+
+If you want to apply the Standard for Public Code to your codebase, just go ahead, it's an open standard and free for anyone to use.
+If you wish to advertise the codebase community's aspiration to meet the criteria of the Standard for Public Code, link the documentation of this commitment from the [standard-for-public-code-commitment badge](assets/standard-for-public-code-commitment.svg).
+To see how ready your codebase is, you can do a quick [eligibility self assessment](https://publiccodenet.github.io/assessment-eligibility) that will give you a rough idea of how much work you may need to do to meet all criteria.
+
+The standard *should* be mostly self-explanatory in how to apply it to your codebase.
+If anything in the standard is unclear, we encourage you to open an issue here so that we can help you and anyone else who feels the same as you.
+For inspiration, look at the [community built implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/) which contains examples and other tips.
+
+If there are any breaking changes in a new version of the Standard for Public Code, the codebase stewards at the Foundation for Public Code will help any implementers of the standard understand how the gaps can be closed.
+
+If you want to commit your codebase to become fully compliant to the standard for future certification, please contact us at <info@publiccode.net> to initiate a formal [assessment](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment).
+
+## Request for contributions
+
+We believe public policy and software should be inclusive, usable, open, legible, accountable, accessible and sustainable.
+This means we need a new way of designing, developing and procuring both the source code and policy documentation.
+
+This standard sets a quality level for codebases that meets the needs of public organizations, institutions and administrations as well as other critical infrastructural services.
+
+The standard lives at [standard.publiccode.net](https://standard.publiccode.net/).
+See [`index.md`](index.md) for an overview of all content.
+
+[![Thumbnail for the video on the Standard for Public Code: a printed version lying on a table between two hands](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)
+
+[A video introduction to Standard for Public Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube.
+
+## Help improve this standard
+
+The Foundation for Public Code is committed to maintaining and developing the Standard for Public Code at a level of quality that meets the standard itself.
+
+We are looking for people like you to [contribute](CONTRIBUTING.md) to this project by suggesting improvements and helping develop it. 😊
+Get started by reading our [contributors guide](CONTRIBUTING.md).
+Since it is such a core document we will accept contributions when they add significant value.
+We've described how we govern the standard in the [governance statement](GOVERNANCE.md).
+
+Please note that this project is released with a [code of conduct](CODE_OF_CONDUCT.md).
+By participating in this project you agree to abide by its terms.
+Please be lovely to all other community members.
+
+## Preview, build and deploy
+
+The repository builds to a static site deployed at [standard.publiccode.net](https://standard.publiccode.net/).
+It is built with [GitHub pages](https://pages.github.com) and [Jekyll](https://jekyllrb.com/).
+
+The content is made to be built with [Jekyll](http://jekyllrb.com/), which means you will need ruby and ruby-bundler installed, for example:
+
+```bash
+sudo apt-get install -y ruby ruby-bundler
+```
+
+If `ruby` and `bundle` are installed, one can run `bundle install` after which the site can be rendered with the `script/serve.sh` script.
+
+### Testing
+
+A variety of test scripts are included.
+The script `script/test-all.sh` wraps running of all local tests.
+
+See the scripts in the [script](https://github.com/publiccodenet/standard/tree/main/script) folder.
+
+### Generating a PDF of the Standard for Public Code
+
+In addition to Jekyll, generating PDFs relies upon [Weasyprint](https://weasyprint.org/) and [QPDF](https://github.com/qpdf/qpdf).
+[Pandoc](https://pandoc.org/) can be used to transform PDFs into `.epub`.
+
+To generate these kinds of files, the dependencies should be installed, for example:
+
+```bash
+sudo apt-get install -y pandoc qpdf weasyprint
+```
+
+The file `standard-print.html` can be converted to a nice looking PDF, along with the other release files, using:
+
+```bash
+script/pdf.sh
+```
+
+## License
+
+© [The authors and contributors](AUTHORS.md)
+
+The standard is [licensed](LICENSE) under CC 0, which also applies to all illustrations and the documentation.
+This means anyone can do anything with it.
+If you contribute you also grant these rights to others.
+You can read more about how to help in the [contributing guide](CONTRIBUTING.md).
diff --git a/origin_source/criteria/bundle-policy-and-source-code.md b/origin_source/criteria/bundle-policy-and-source-code.md
new file mode 100644
index 00000000..39334f54
--- /dev/null
+++ b/origin_source/criteria/bundle-policy-and-source-code.md
@@ -0,0 +1,56 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 2
+redirect_from:
+  - criteria/bundle-policy-and-code
+---
+# Bundle policy and source code
+
+Access to both [source code](../glossary.md#source-code) and [policy](../glossary.md#policy) documentation provides building blocks for anyone to implement the codebase in their local context or contribute to the further development of the [codebase](../glossary.md#codebase).
+
+Understanding the domain and policies within that domain is fundamental to understanding what problems a codebase is trying to solve and how it sets out to solve them.
+
+To be able to evaluate whether to implement a codebase in a new context, an organization needs to understand what process changes it must choose to make or how to contribute additional configurability to the existing solution in order to adapt it to the new context.
+
+## Requirements
+
+* The codebase MUST include the policy that the source code is based on.
+* If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection.
+* Policy SHOULD be provided in machine readable and unambiguous formats.
+* [Continuous integration](../glossary.md#continuous-integration) tests SHOULD validate that the source code and the policy are executed coherently.
+
+## How to test
+
+* Confirm with a civil servant that all policy that the source code is based on is included.
+* Confirm with a civil servant that all source code that the policy is based on is included.
+* Check if policy can be interpreted by a machine.
+* Check the continuous integration tests for coherent execution of source code and policy pass.
+
+## Public policy makers: what you need to do
+
+* Collaborate with developers and designers to make sure there is no mismatch between policy code and source code.
+* Provide the relevant policy texts for inclusion in the [repository](../glossary.md#repository); if the text is not available in English, also provide an English summary. Be sure to include standards that your organization has chosen to adhere to and any organizational processes which impact the development or the deployment context of the codebase for your organization.
+* Provide references and links to texts which support the policies.
+* Document policy in formats that are unambiguous and machine-readable, such as those published by the [Object Management Group](https://www.omg.org/spec/).
+* Track policy with [the same version control](maintain-version-control.md) and documentation used to track source code.
+* Check in regularly to understand how the source code in the codebase has changed and whether it still matches the [intentions of the policy](document-codebase-objectives.md).
+* Include relevant policies which impact the community, codebase, and development, including legal obligations like the [General Data Protection Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-accessibility), or human rights policies, like a public organization's commitment to equal opportunity.
+
+## Managers: what you need to do
+
+* Keep policy makers, developers and designers involved and connected throughout the whole development process.
+* Make sure policy makers, developers and designers are working to the same objectives.
+
+## Developers and designers: what you need to do
+
+* Become familiar with and be able to use the process modelling notation that the policy makers in your organization use.
+* Work together with policy makers to make sure there is no mismatch between policy code and source code.
+* Give feedback on how to make policy documentation more clear.
+
+## Further reading
+
+* [Business Process Model and Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation) on Wikipedia.
+* [BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by Trisotech.
+* [Decision Model and Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on Wikipedia.
+* [Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on Wikipedia.
diff --git a/origin_source/criteria/code-in-the-open.md b/origin_source/criteria/code-in-the-open.md
new file mode 100644
index 00000000..b325ab2b
--- /dev/null
+++ b/origin_source/criteria/code-in-the-open.md
@@ -0,0 +1,47 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 1
+---
+# Code in the open
+
+Coding in the open improves transparency, increases [source code](../glossary.md#source-code) quality, makes the source code easier to audit, and enables collaboration.
+
+Together, this creates more opportunities for citizens to understand how software and [policy](../glossary.md#policy) impact their interactions with a public organization.
+
+## Requirements
+
+* All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.
+* All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.
+* The codebase MUST NOT contain sensitive information regarding users, their organization or third parties.
+* Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.
+* Documenting which source code or policy underpins any specific interaction the [general public](../glossary.md#general-public) may have with an organization is OPTIONAL.
+
+## How to test
+
+* Confirm that the source for each version currently in use is published on the internet where it can be seen from outside the original contributing organization and without the need for any form of authentication or authorization.
+* Confirm that the [codebase](../glossary.md#codebase) files and commit history do not include sensitive information.
+* Check for the publication of source code not currently in use.
+
+## Public policy makers: what you need to do
+
+* Develop policies in the open.
+* Prioritize open and transparent policies.
+
+## Managers: what you need to do
+
+* Develop a culture that embraces openness, learning and feedback.
+* Collaborate with external vendors and freelancers by working in the open.
+
+## Developers and designers: what you need to do
+
+* As a reviewer, for each commit, verify that content does not include sensitive information such as configurations, usernames or passwords, public keys or other real credentials used in production systems.
+* Clearly split data and source code, in order to meet the requirement about sensitive information above.
+
+## Further reading
+
+* [Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/) by the UK Government Digital Service.
+* [When code should be open or closed](https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed) by the UK Government Digital Service.
+* [Security considerations when coding in the open](https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open) by the UK Government Digital Service.
+* [Deploying software regularly](https://www.gov.uk/service-manual/technology/deploying-software-regularly) by the UK Government Digital Service.
+* [How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/) by the UK Government Digital Service.
diff --git a/origin_source/criteria/document-codebase-maturity.md b/origin_source/criteria/document-codebase-maturity.md
new file mode 100644
index 00000000..bb7a4692
--- /dev/null
+++ b/origin_source/criteria/document-codebase-maturity.md
@@ -0,0 +1,50 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 16
+redirect_from:
+    - criteria/advertise-maturity
+    - criteria/document-maturity
+---
+# Document codebase maturity
+
+Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps others decide whether to use and contribute to it.
+A codebase version's maturity includes the maturity of its dependencies.
+Understanding how a codebase has evolved is key to understanding the codebase and how to contribute to it.
+
+## Requirements
+
+* The codebase MUST be versioned.
+* The codebase MUST prominently document whether or not there are versions of the codebase that are ready to use.
+* Codebase versions that are ready to use MUST only depend on versions of other codebases that are also ready to use.
+* The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`.
+* The method for assigning version identifiers SHOULD be documented.
+* It is OPTIONAL to use semantic versioning.
+
+## How to test
+
+* Confirm that the codebase has a strategy for versioning which is documented.
+* Confirm that it is obvious to policy makers, managers, developers and designers whether the codebase has versions that are ready to use.
+* Confirm that ready to use versions of the codebase do not depend on any versions of other codebases that are not ready to use.
+* Check that the versioning scheme of the codebase is documented and followed.
+* Check that there is a log of changes.
+
+## Public policy makers: what you need to do
+
+* When developing [policy](../glossary.md#policy), understand that any [source code](../glossary.md#source-code) developed needs to be tested and improved before it can be put into service.
+* Consider versioning policy changes, especially when they trigger new versions of the source code.
+
+## Managers: what you need to do
+
+* Make sure that services only rely on versions of codebases of equal or greater maturity than the service. For example, don't use a beta version of a codebase in a production service.
+
+## Developers and designers: what you need to do
+
+* Make sure that the codebase versioning approach is followed for all releases.
+
+## Further reading
+
+* [Semantic Versioning Specification](https://semver.org/) used by many codebases to label versions.
+* [Software release life cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)
+* [Service Design and Delivery Process](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process) by the Australian Digital Transformation Agency.
+* [Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-delivery) by the UK Government Digital Service.
diff --git a/origin_source/criteria/document-codebase-objectives.md b/origin_source/criteria/document-codebase-objectives.md
new file mode 100644
index 00000000..d54d30eb
--- /dev/null
+++ b/origin_source/criteria/document-codebase-objectives.md
@@ -0,0 +1,40 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 8
+redirect_from:
+  - criteria/document-objectives
+---
+# Document codebase objectives
+
+Clearly documenting [codebase](../glossary.md#codebase) objectives communicates the purpose of the codebase.
+It helps stakeholders and contributors scope the development of the codebase.
+The objectives also provide an easy way for people to decide whether this codebase, or one of its modules, is interesting for them now or in the future.
+
+## Requirements
+
+* The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.
+* Codebase documentation SHOULD clearly describe the connections between [policy](../glossary.md#policy) objectives and codebase objectives.
+* Documenting the objectives of the codebase for the [general public](../glossary.md#general-public) is OPTIONAL.
+
+## How to test
+
+* Confirm that the codebase documentation includes the codebase objectives, mission or goal.
+* Check for descriptions of connections between policy objectives and codebase objectives.
+
+## Public policy makers: what you need to do
+
+* Add the policy objectives to the codebase documentation, for example in the `README`.
+* Make sure that all your codebase objectives have links or references to supporting policy documents added to meet the [Bundle policy and source code](bundle-policy-and-source-code.md) criterion.
+
+## Managers: what you need to do
+
+* Add the organizational and business objectives to the codebase documentation, for example in the `README`.
+
+## Developers and designers: what you need to do
+
+* Add the technology and design objectives to the codebase documentation, for example in the `README`.
+
+## Further reading
+
+* [How to write project objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf) by Marek Hajduczenia.
diff --git a/origin_source/criteria/document-the-code.md b/origin_source/criteria/document-the-code.md
new file mode 100644
index 00000000..228fb250
--- /dev/null
+++ b/origin_source/criteria/document-the-code.md
@@ -0,0 +1,53 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 9
+redirect_from:
+  - criteria/documenting
+---
+# Document the code
+
+Well documented [source code](../glossary.md#source-code) helps people to understand what the source code does and how to use it.
+Documentation is essential for people to start using the [codebase](../glossary.md#codebase) and contributing to it more quickly.
+
+## Requirements
+
+* All of the functionality of the codebase, [policy](../glossary.md#policy) as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase.
+* The documentation of the codebase MUST contain a description of how to install and run the software.
+* The documentation of the codebase MUST contain examples demonstrating the key functionality.
+* The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the [general public](../glossary.md#general-public) and journalists.
+* The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.
+* The documentation of the codebase SHOULD contain examples for all functionality.
+* The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.
+* There SHOULD be [continuous integration](../glossary.md#continuous-integration) tests for the quality of the documentation.
+* Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.
+
+## How to test
+
+* Confirm that other stakeholders, professionals from other public organizations and the general public find the documentation clear and understandable.
+* Confirm that the documentation describes how to install and run the source code.
+* Confirm that the documentation includes examples of the key functionality.
+* Check with members of the general public and journalists if they can understand the high level description.
+* Check that the instructions for how to install and run a standalone version of the source code result in a running system.
+* Check that all functionality documented contains an example.
+* Check that the documentation includes a high level architectural diagram or similar.
+* Check that the documentation quality is part of integration testing, for example documentation is generated correctly, and links and images are tested.
+
+## Public policy makers: what you need to do
+
+* Check in regularly to understand how the non-policy code in the codebase has changed.
+* Give feedback on how to make non-policy documentation more clear.
+
+## Managers: what you need to do
+
+* Try to use the codebase, so your feedback can improve how clearly the policy and source code are documented. For example, is the current documentation sufficient to persuade a manager at another public organization to use this codebase?
+* Make sure you understand both the policy and source code as well as the documentation.
+
+## Developers and designers: what you need to do
+
+* Check in regularly to understand how the non-source code in the codebase has changed.
+* Give feedback on how to make non-source documentation more clear.
+
+## Further reading
+
+* [Documentation guide](https://www.writethedocs.org/guide/) by Write the Docs.
diff --git a/origin_source/criteria/index.md b/origin_source/criteria/index.md
new file mode 100644
index 00000000..7bd1c002
--- /dev/null
+++ b/origin_source/criteria/index.md
@@ -0,0 +1,12 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 0
+---
+# Criteria
+
+{% assign sorted = site.pages | sort:"order" %}
+
+{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
+
+1. [{{page.title}}]({{page.url}}){% endif%}    {% endif%}  {% endif%}{% endfor %}
diff --git a/origin_source/criteria/maintain-version-control.md b/origin_source/criteria/maintain-version-control.md
new file mode 100644
index 00000000..5014df02
--- /dev/null
+++ b/origin_source/criteria/maintain-version-control.md
@@ -0,0 +1,60 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 6
+redirect_from:
+  - criteria/version-control-and-history
+---
+# Maintain version control
+
+[Version control](../glossary.md#version-control) means keeping track of changes to the [source code](../glossary.md#source-code) and other files of the [codebase](../glossary.md#codebase) over time.
+This allows you to maintain structured documentation of the history of the codebase.
+This is essential for collaboration at scale, as it enables developers to work on changes in parallel and helps future developers to understand the reasons for changes.
+
+## Requirements
+
+* All files in the codebase MUST be version controlled.
+* All decisions MUST be documented in commit messages.
+* Every commit message MUST link to discussions and issues wherever possible.
+* The codebase SHOULD be maintained in a distributed version control system.
+* Contribution guidelines SHOULD require contributors to group relevant changes in commits.
+* Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.
+* Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system.
+* It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.
+
+## How to test
+
+* Confirm that the codebase is kept in version control using software such as Git.
+* Review the commit history, confirming that all commit messages explain why the change was made.
+* Review the commit history, confirming that where possible all commit messages include the discussion about the change was or where to find it (with a URL).
+* Check if the version control system is distributed.
+* Review the commit history, check if grouping of relevant changes in accordance with the contributing guidelines.
+* Check that it is possible to access a specific version of the codebase, for example through a revision tag or a textual label.
+* Check that the file formats used in the codebase are text formats where possible.
+
+## Public policy makers: what you need to do
+
+* If a new version of the codebase is created because of a [policy](../glossary.md#policy) change, make sure it's clear in the documentation:
+  * what the policy change is,
+  * how it's changed the codebase.
+
+For example, adding a new category of applicant to a codebase that manages granting permits would be considered a policy change.
+
+## Managers: what you need to do
+
+* Support policy makers, developers and designers to be clear about what improvements they're making to the codebase. Making improvements isn't a public relations risk.
+
+## Developers and designers: what you need to do
+
+* Make sure that all files required to understand the code, build and deploy are in the version control system.
+* Write clear commit messages so that it is easy to understand why the commit was made.
+* Mark different versions so that it is easy to access a specific version, for example using revision tags or textual labels.
+* Write clear commit messages so that versions can be usefully compared.
+* Work with policy makers to describe how the source code was updated after a policy change.
+
+## Further reading
+
+* [Producing OSS: Version Control Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl Fogel.
+* [Maintaining version control in coding](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding) by the UK Government Digital Service.
+* [GitHub Skills](https://skills.github.com/) by GitHub for learning how to use GitHub or refresh your skills.
+* [Git Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) by GitHub, a list with the most common used git commands.
diff --git a/origin_source/criteria/make-contributing-easy.md b/origin_source/criteria/make-contributing-easy.md
new file mode 100644
index 00000000..049491e5
--- /dev/null
+++ b/origin_source/criteria/make-contributing-easy.md
@@ -0,0 +1,48 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 5
+---
+# Make contributing easy
+
+To develop better, more reliable and feature rich software, users need to be able to fix problems, add features, and address security issues of the shared [codebase](../glossary.md#codebase).
+
+A shared digital infrastructure makes it easier to make collaborative contributions.
+The less effort it takes to make contributions that are accepted by the codebase, the more likely users are to become contributors.
+
+## Requirements
+
+* The codebase MUST have a public issue tracker that accepts suggestions from anyone.
+* The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file.
+* The codebase MUST have communication channels for users and developers, for example email lists.
+* There MUST be a way to report security issues for responsible disclosure over a closed channel.
+* The documentation MUST include instructions for how to report potentially security sensitive issues.
+
+## How to test
+
+* Confirm that there is a public issue tracker.
+* Confirm that the codebase contains links to the public issue tracker and submitted codebase changes.
+* Confirm that it is possible to participate in a discussion with other users and developers about the software using channels described in the codebase.
+* Confirm that there is a closed channel for reporting security issues.
+* Confirm that there are instructions for privately reporting security issues.
+
+## Public policy makers: what you need to do
+
+* Track [policy](../glossary.md#policy) issues in the codebase, so that a relevant external policy expert can volunteer help.
+
+## Managers: what you need to do
+
+* Track management issues in the codebase, so that external managers with relevant experience can volunteer help.
+* Support your experienced policy makers, developers and designers to keep contributing to the codebase for as long as possible.
+
+## Developers and designers: what you need to do
+
+* Just like for [reviews](require-review-of-contributions.md), make sure to respond to requests promptly.
+* Keep your managers informed of the time and resources you require to support other contributors.
+* Make sure that appropriate communication channels for asking maintainers and stakeholders questions are easy to locate, for instance in the README.
+* Make sure that appropriate contact details are included in the metadata, for instance in the publiccode.yml file.
+
+## Further reading
+
+* [How to inspire exceptional contributions to your open-source project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf) by Joel Hans.
+* [The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/) by the UK Government Digital Service.
diff --git a/origin_source/criteria/make-the-codebase-findable.md b/origin_source/criteria/make-the-codebase-findable.md
new file mode 100644
index 00000000..ca2f1ce1
--- /dev/null
+++ b/origin_source/criteria/make-the-codebase-findable.md
@@ -0,0 +1,70 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 14
+redirect_from:
+  - criteria/findability
+---
+
+# Make the codebase findable
+
+The more findable a [codebase](../glossary.md#codebase) is, the more potential new collaborators will find it.
+Just publishing a codebase and hoping it is found does not work, instead proactiveness is needed.
+
+A metadata description file increases discoverability.
+Well-written metadata containing a unique and persistent identifier, such as a Wikidata item or FSF software directory listing (thus being part of the semantic web), makes the codebase easier for people to refer, cite, disambiguate and discover through third party tools.
+
+## Requirements
+
+* The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.
+* The codebase SHOULD have a short description that helps someone understand what the codebase is for or what it does.
+* Maintainers SHOULD submit the codebase to relevant software catalogs.
+* The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).
+* The codebase SHOULD be findable using a search engine by codebase name.
+* The codebase SHOULD be findable using a search engine by describing the problem it solves in natural language.
+* The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, [repository](../glossary.md#repository) location and website.
+* The codebase SHOULD include a machine-readable metadata description, for example in a [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file.
+* A dedicated domain name for the codebase is OPTIONAL.
+* Regular presentations at conferences by the community are OPTIONAL.
+
+## How to test
+
+* Check that the codebase name is descriptive and free of puns.
+* Check that the codebase name is free of acronyms and abbreviations or that the acronyms or abbreviations in the name are more universally known than the longer forms.
+* Check that the codebase name is free of organizational branding, unless that organization is of the codebase community itself.
+* Check that the codebase repository has a short description of the codebase.
+* Check for the codebase listing in relevant software catalogs.
+* Check for a codebase website which describes the problem the codebase solves.
+* Check that the codebase appears in the results on more than one major search engine when searching by the codebase name.
+* Check that the codebase appears in the results on more than one major search engine when searching by using natural language, for instance, using the short description.
+* Check unique and persistent identifier entries for mention of the major contributors.
+* Check unique and persistent identifier entries for the repository location.
+* Check unique and persistent identifier entries for the codebase website.
+* Check for a machine-readable metadata description file.
+
+## Public policy makers: what you need to do
+
+* Contribute a description of the policy area or problem this codebase acts on or operates.
+* Test your problem description with peers outside of your context who aren't familiar with the codebase.
+* Present on how the codebase implements the [policy](../glossary.md#policy) at relevant conferences.
+
+## Managers: what you need to do
+
+* Search trademark databases to avoid confusion or infringement before deciding the name.
+* Use the short description wherever the codebase is referenced, for instance, as social media account descriptions.
+* Budget for content design and Search Engine Optimization skills in the team.
+* Make sure people involved in the project present at relevant conferences.
+
+## Developers and designers: what you need to do
+
+* Search engine optimization, for instance adding a [sitemap](https://www.sitemaps.org/protocol.html).
+* Use the short description wherever the codebase is referenced, for instance, as the repository description.
+* Test your problem description with peers outside of your context who aren't familiar with the codebase.
+* Suggest conferences to present at and present at them.
+
+<p style="page-break-after: always;"></p>
+## Further reading
+
+* [Introduction to Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the Wikidata community.
+* [FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) by the Free Software Foundation.
+* The [FAIR Guiding Principles for scientific data management and stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR International Support and Coordination Office provide a nice list of attributes that make (meta)data more machine actionable (and hence more findable). Some of these apply directly to codebases, while others may provoke exploration into what the codebase equivalent would be.
diff --git a/origin_source/criteria/make-the-codebase-reusable-and-portable.md b/origin_source/criteria/make-the-codebase-reusable-and-portable.md
new file mode 100644
index 00000000..5437394c
--- /dev/null
+++ b/origin_source/criteria/make-the-codebase-reusable-and-portable.md
@@ -0,0 +1,76 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 3
+redirect_from:
+  - criteria/reusable-and-portable-codebases
+  - criteria/create-reusable-and-portable-code
+---
+# Make the codebase reusable and portable
+
+Creating reusable and portable [code](../glossary.md#code) enables policy makers, developers and designers to reuse what has been developed, test it, improve it and contribute those improvements back, leading to better quality, cheaper maintenance and higher reliability.
+
+Thoughtfully and purposefully designing a [codebase](../glossary.md#codebase) for reusability allows for the mission, vision and scope of the codebase to be shared by multiple parties.
+Codebases developed and used by multiple parties are more likely to benefit from a self-sustaining community.
+
+Organizing a codebase such that it is composed of well documented modules improves reusability and maintainability.
+A module is easier to reuse in [another context](../glossary.md#different-contexts) if its purpose is clearly documented.
+
+Source code which does not rely on the situation-specific infrastructure of any contributor, vendor or deployment can be tested by any other contributor.
+
+## Requirements
+
+* The codebase MUST be developed to be reusable in different contexts.
+* The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding.
+* The codebase SHOULD be in use by multiple parties.
+* The roadmap SHOULD be influenced by the needs of multiple parties.
+* The development of the codebase SHOULD be a collaboration between multiple parties.
+* Configuration SHOULD be used to make [source code](../glossary.md#source-code) adapt to context specific needs.
+* The codebase SHOULD be localizable.
+* Source code and its documentation SHOULD NOT contain situation-specific information.
+* Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.
+* The software SHOULD NOT require services or platforms available from only a single vendor.
+
+## How to test
+
+* Confirm with someone in a similar role at another organization if they can use the codebase and what that would entail.
+* Confirm that the codebase can run without using any proprietary or non open-licensed software or services.
+* If the codebase is in early development before a production-ready release, then check for evidence of ambition to obtain collaborators.
+   * Or if the codebase is very mature and stable with very infrequent fixes, patches, or contributions:
+     * Check that the codebase is in use by multiple parties or in multiple contexts.
+     * Check for documented and budgeted commitments of collaboration.
+   * Otherwise:
+     * Check that the codebase is in use by multiple parties or in multiple contexts.
+     * Check that the codebase contributors are from multiple parties.
+* Check that the codebase files and commit history do not include situation-specific data.
+* Check that the software can be deployed and run without services or platforms available from a single vendor.
+
+## Public policy makers: what you need to do
+
+* Document your [policy](../glossary.md#policy) with enough clarity and detail that it can be understood outside of its original context.
+* Make sure your organization is listed as a known user by the codebase.
+* Identify other organizations for your teams to collaborate with.
+
+## Managers: what you need to do
+
+* Make sure that stakeholders and business owners understand that reusability is an explicit codebase goal as this reduces technical debt and provides sustainability for the codebase.
+* Make sure that your teams are collaborating with other teams.
+
+## Developers and designers: what you need to do
+
+Source should be designed:
+
+* for reuse by other users and organizations regardless of locale,
+* to solve a general problem instead of a specific one,
+* in logically meaningful and isolated modules,
+* so that someone in a similar organization facing a similar problem would be able to use (parts of) the solution.
+
+Make sure that the codebase documentation describes the build-time and runtime dependencies.
+If your context requires deploying to proprietary platforms or using proprietary components, make sure that collaborators can develop, use, test, and deploy without them.
+
+For each commit, reviewers verify that content does not include situation-specific data such as hostnames, personal and organizational data, or tokens and passwords.
+
+## Further reading
+
+* [Making source code open and reusable](https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable) by the UK Government Digital Service.
+* [Localization vs. Internationalization](https://www.w3.org/International/questions/qa-i18n) by the World Wide Web Consortium.
diff --git a/origin_source/criteria/publish-with-an-open-license.md b/origin_source/criteria/publish-with-an-open-license.md
new file mode 100644
index 00000000..1b674dcb
--- /dev/null
+++ b/origin_source/criteria/publish-with-an-open-license.md
@@ -0,0 +1,54 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 13
+redirect_from:
+  - criteria/open-licenses
+---
+# Publish with an open license
+
+An open and well known license makes it possible for anyone to see the [source code](../glossary.md#source-code) in order to understand how it works, to use it freely and to contribute to the [codebase](../glossary.md#codebase).
+This enables a vendor ecosystem to emerge around the codebase.
+
+Clearly indicating the license for each file within a codebase facilitates correct reuse and attribution of parts of a codebase.
+
+## Requirements
+
+* All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.
+* Software source code MUST be licensed under an [OSI-approved or FSF Free/Libre license](https://spdx.org/licenses/).
+* All source code MUST be published with a license file.
+* Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.
+* All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.
+* Having multiple licenses for different types of source code and documentation is OPTIONAL.
+
+## How to test
+
+* Confirm that the codebase is clearly licensed.
+* Confirm that the license for the source code is on the [OSI-approved or FSF Free/Libre license list](https://spdx.org/licenses/) and the license for documentation [conforms to the Open Definition](https://opendefinition.org/licenses/).
+* Confirm that the licenses used in the codebase are included as files.
+* Confirm that contribution guidelines and [repository](../glossary.md#repository) configuration do not require transfer of copyright.
+* Check for machine-readable license checking in the codebase [continuous integration](../glossary.md#continuous-integration) tests.
+
+## Public policy makers: what you need to do
+
+* Develop [policy](../glossary.md#policy) that requires source code to be [open source](../glossary.md#open-source).
+* Develop policy that disincentivizes non-open source code and technology in procurement.
+
+## Managers: what you need to do
+
+* Only work with open source vendors that deliver their source code by publishing it under an open source license.
+* Beware that even though [Creative Commons licenses](https://creativecommons.org/licenses/) are great for documentation, licenses that stipulate Non-Commercial or No Derivatives are NOT freely reusable, changeable and redistributable and don't fulfill these requirements.
+
+## Developers and designers: what you need to do
+
+* Add a new `license` file to every new codebase created.
+* Add a copyright notice and a license header to every new source code file created.
+* When source code is being reused by the codebase, make sure that it has a license that is compatible with the license or licenses of the codebase.
+
+<p style="page-break-after: always;"></p>
+## Further reading
+
+* [Open source definition](https://opensource.org/osd) by the Open Source Initiative, all open source licenses meet this definition.
+* [Animated video introduction to Creative Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by Creative Commons Aotearoa New Zealand.
+* [REUSE Initiative specification](https://reuse.software/spec/) by Free Software Foundation Europe for unambiguous, human-readable and machine-readable copyright and licensing information.
+* [SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with standardized, machine-readable abbreviations for most licenses.
diff --git a/origin_source/criteria/require-review-of-contributions.md b/origin_source/criteria/require-review-of-contributions.md
new file mode 100644
index 00000000..fca4fc5c
--- /dev/null
+++ b/origin_source/criteria/require-review-of-contributions.md
@@ -0,0 +1,63 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 7
+redirect_from:
+  - criteria/require-review
+---
+# Require review of contributions
+
+Peer-review of contributions is essential for [source code](../glossary.md#source-code) quality, reducing security risks and operational risks.
+
+Requiring thorough review of contributions encourages a culture of making sure every contribution is of high quality, completeness and value.
+Source code review increases the chance of discovering and fixing potential bugs or mistakes before they are added to the [codebase](../glossary.md#codebase).
+Knowing that all source code was reviewed discourages a culture of blaming individuals, and encourages a culture of focusing on solutions.
+
+A [policy](../glossary.md#policy) of prompt reviews assures contributors of a guaranteed time for feedback or collaborative improvement, which increases both rate of delivery and contributor engagement.
+
+## Requirements
+
+* All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.
+* Reviews MUST include source, policy, tests and documentation.
+* Reviewers MUST provide feedback on all decisions to not accept a contribution.
+* The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review.
+* Reviews SHOULD include running both the software and the tests of the codebase.
+* Contributions SHOULD be reviewed by someone in a different context than the contributor.
+* Version control systems SHOULD NOT accept non-reviewed contributions in release versions.
+* Reviews SHOULD happen within two business days.
+* Performing reviews by multiple reviewers is OPTIONAL.
+
+## How to test
+
+* Confirm that every commit in the history has been reviewed by a different contributor.
+* Confirm that reviews include source, policy, tests and documentation.
+* Confirm that rejected contributions were appropriately explained.
+* Check if guidelines for reviewers include instructions to review for conformance to standards, architecture and codebase guidelines.
+* Check with reviewers if they run the software and tests during review.
+* Check with reviewers if commits have been reviewed by a different contributor in a different context.
+* Check for use of branch protection in the [version control](../glossary.md#version-control) system.
+* Check the times between contribution submission and review.
+
+## Public policy makers: what you need to do
+
+* Institute a 'four eyes' policy where everything, not just source code, is reviewed.
+* Use a version control system or methodology that enables review and feedback.
+
+## Managers: what you need to do
+
+* Make delivering great software a shared objective.
+* Make sure writing and reviewing contributions to source, policy, documentation and tests are considered equally valuable.
+* Create a culture where all contributions are welcome and everyone is empowered to review them.
+* Make sure no contributor is ever alone in contributing to a codebase.
+
+## Developers and designers: what you need to do
+
+* Ask other contributors on the codebase to review your work, in your organization or outside of it.
+* Try to respond to others' requests for review promptly, initially providing feedback about the concept of the change.
+
+## Further reading
+
+* [How to review code the GDS way](https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK Government Digital Service.
+* Branch protection on [GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) and [GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-protected/).
+* [The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/) by Sage Sharp.
+* [Measuring Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla.
diff --git a/origin_source/criteria/use-a-coherent-style.md b/origin_source/criteria/use-a-coherent-style.md
new file mode 100644
index 00000000..6199ef02
--- /dev/null
+++ b/origin_source/criteria/use-a-coherent-style.md
@@ -0,0 +1,47 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 15
+redirect_from:
+  - criteria/style
+---
+# Use a coherent style
+
+Following a consistent and coherent style enables contributors in different environments to work together.
+Unifying vocabularies reduces friction in communication between contributors.
+
+## Requirements
+
+* The [codebase](../glossary.md#codebase) MUST use a coding or writing style guide, either the codebase community's own or an existing one referred to in the codebase.
+* Contributions SHOULD pass automated tests on style.
+* The style guide SHOULD include expectations for inline comments and documentation for non-trivial sections.
+* Including expectations for [understandable English](use-plain-english.md) in the style guide is OPTIONAL.
+
+## How to test
+
+* Confirm that contributions are in line with the style guides specified in the documentation.
+* Check for the presence of automated tests on style.
+
+## Public policy makers: what you need to do
+
+* Create, follow and continually improve on a style guide for [policy](../glossary.md#policy) and documentation as well as document this in the codebase, for example in the `CONTRIBUTING` or `README`.
+
+## Managers: what you need to do
+
+* Include written language, source, test and policy standards in your organizational definition of quality.
+
+## Developers and designers: what you need to do
+
+If the codebase does not already have engineering guidelines or other contributor guidance, start by adding documentation to the [repository](../glossary.md#repository) describing whatever is being done now, for example in the `CONTRIBUTING` or `README`.
+An important purpose of the file is to communicate design preferences, naming conventions, and other aspects machines can't easily check.
+Guidance should include what would be expected from [source code](../glossary.md#source-code) contributions in order for them to be merged by the maintainers, including source, tests and documentation.
+Continually improve upon and expand this documentation with the aim of evolving this documentation into engineering guidelines.
+
+Additionally:
+
+* Use a linter.
+* Add linter configurations to the codebase.
+
+## Further reading
+
+* [Programming style](https://en.wikipedia.org/wiki/Programming_style) on Wikipedia.
diff --git a/origin_source/criteria/use-continuous-integration.md b/origin_source/criteria/use-continuous-integration.md
new file mode 100644
index 00000000..d19b4789
--- /dev/null
+++ b/origin_source/criteria/use-continuous-integration.md
@@ -0,0 +1,70 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 12
+redirect_from:
+  - criteria/continuous-integration
+---
+# Use continuous integration
+
+Asynchronous collaboration is enabled by developers merging their work to a shared branch frequently, verified by automated tests.
+The more frequent the merging and the smaller the contribution, the easier it is to resolve merge conflicts.
+
+Automated testing of all functionality provides confidence that contributions are working as intended and have not introduced errors, and allows reviewers to focus on the structure and approach of the contribution.
+The more focused the test, the easier it is to clearly identify and understand errors as they arise.
+
+Documenting a codebase's [continuous integration](../glossary.md#continuous-integration) workflow helps contributors understand the expectations of contributions.
+Continuous integration allows for an easier monitoring of the state of the [codebase](../glossary.md#codebase).
+
+## Requirements
+
+* All functionality in the [source code](../glossary.md#source-code) MUST have automated tests.
+* Contributions MUST pass all automated tests before they are admitted into the codebase.
+* The codebase MUST have guidelines explaining how to structure contributions.
+* The codebase MUST have active contributors who can review contributions.
+* Automated test results for contributions SHOULD be public.
+* The codebase guidelines SHOULD state that each contribution should focus on a single issue.
+* Source code test and documentation coverage SHOULD be monitored.
+* Testing [policy](../glossary.md#policy) and documentation for consistency with the source and vice versa is OPTIONAL.
+* Testing policy and documentation for style and broken links is OPTIONAL.
+* Testing the software by using examples in the documentation is OPTIONAL.
+
+## How to test
+
+* Confirm that there are tests present.
+* Confirm that source code coverage tools check that coverage is at 100% of the source code.
+* Confirm that contributions are only admitted into the codebase after all of the tests are passed.
+* Confirm that contribution guidelines explain how to structure contributions.
+* Confirm that there are contributions from within the last three months.
+* Check that test results are viewable.
+* Check if source code coverage data is published.
+
+## Public policy makers: what you need to do
+
+* Involve managers as well as developers and designers as early in the process as possible and keep them engaged throughout development of your policy.
+* Make sure there are also automated tests set up for policy documentation.
+* Fix policy documentation promptly if it fails a test.
+* Make sure the source code reflects any changes to the policy (see [Maintain version control](maintain-version-control.md)).
+
+## Managers: what you need to do
+
+* Make sure to test with real end users as quickly and often as possible.
+* Plan the work to integrate small parts very often instead of large parts less frequently.
+* Procure consultancy services that deliver incrementally aligned with the plan.
+* After a large failure, encourage publication of incident reports and public discussion of what was learned.
+
+## Developers and designers: what you need to do
+
+* Help managers structure the work plan such that it can be integrated as small increments.
+* Help contributors limit the scope of their contributions and feature requests to be as small as reasonable.
+* Help managers and policy makers test their contributions, for example by testing their contributions for broken links or style.
+* Structure source code written to handle conditions which are difficult to create in a test environment in such a way that the conditions can be simulated during testing. Forms of resource exhaustion such as running out of storage space and memory allocation failure are typical examples of difficult to create conditions.
+* Tune the test code coverage tools to avoid false alarms resulting from inlining or other optimizations.
+* Deploy often.
+* Integrate your work at least once a day.
+
+## Further reading
+
+* [What is continuous integration](https://www.martinfowler.com/articles/continuousIntegration.html) by Martin Fowler.
+* [Use continuous delivery](https://gds-way.cloudapps.digital/standards/continuous-delivery.html) by the UK Government Digital Service.
+* [Quality assurance: testing your service regularly](https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly) by the UK Government Digital Service.
diff --git a/origin_source/criteria/use-open-standards.md b/origin_source/criteria/use-open-standards.md
new file mode 100644
index 00000000..13d26b8b
--- /dev/null
+++ b/origin_source/criteria/use-open-standards.md
@@ -0,0 +1,46 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 11
+redirect_from:
+  - criteria/open-standards
+---
+# Use open standards
+
+[Open standards](../glossary.md#open-standard) guarantee access to the knowledge required to use and contribute to the [codebase](../glossary.md#codebase).
+They enable interoperability between systems and reduce the risk of vendor lock-in.
+Open standards which are unambiguous allow for independent development of either side of data exchange.
+
+## Requirements
+
+* For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the [Open Source Initiative Open Standard Requirements](https://opensource.org/osr).
+* Any non-open standards used MUST be recorded clearly as such in the documentation.
+* Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.
+* Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.
+* If no existing open standard is available, effort SHOULD be put into developing one.
+* Open standards that are machine testable SHOULD be preferred over open standards that are not.
+* Non-open standards that are machine testable SHOULD be preferred over non-open standards that are not.
+
+## How to test
+
+* Confirm that data exchange follows an OSI approved open standard.
+* Confirm that any non-open standards used are clearly documented as such.
+* Confirm that documentation includes a list of the standards followed within the codebase, each with a working link, or a statement that no standards were chosen.
+
+## Public policy makers: what you need to do
+
+* Mandate use of open standards everywhere possible.
+* Prohibit procurement of technology that does not use open standards.
+
+## Managers: what you need to do
+
+* Consider including open standard compliance assessment in [source code](../glossary.md#source-code) reviews.
+
+## Developers and designers: what you need to do
+
+* Add [continuous integration](../glossary.md#continuous-integration) tests for compliance with the standards.
+* Review the commits and other [repository](../glossary.md#repository) resources for references to standards and cross-check those with the standards listed.
+
+## Further reading
+
+* [Open Standards principles](https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles), [policy](../glossary.md#policy) paper of the UK Cabinet Office.
diff --git a/origin_source/criteria/use-plain-english.md b/origin_source/criteria/use-plain-english.md
new file mode 100644
index 00000000..a5aee480
--- /dev/null
+++ b/origin_source/criteria/use-plain-english.md
@@ -0,0 +1,56 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 10
+redirect_from:
+  - criteria/understandable-english-first
+---
+# Use plain English
+
+English is the <i>de facto</i> language of collaboration in software development.
+
+Public sector information needs to be accessible to all its constituents.
+Plain and simple language makes the [code](../glossary.md#code) and what it does easier to understand for a wider variety of people.
+
+Translations further increase the possible reach of a [codebase](../glossary.md#codebase).
+Language that is easy to understand lowers the cost of creating and maintaining translations.
+
+## Requirements
+
+* All codebase documentation MUST be in English.
+* All [source code](../glossary.md#source-code) MUST be in English, except where [policy](../glossary.md#policy) is machine interpreted as code.
+* All bundled policy not available in English MUST have an accompanying summary in English.
+* Any translation MUST be up to date with the English version and vice versa.
+* There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.
+* Documentation SHOULD aim for a lower secondary education reading level, as recommended by the [Web Content Accessibility Guidelines 2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable).
+* Providing a translation of any code, documentation or tests is OPTIONAL.
+
+## How to test
+
+* Confirm that codebase documentation is available in English.
+* Confirm that source code is in English, or confirm any non-English is policy or terms with preceding explanations.
+* Confirm any non-English policy has an accompanying summary in English.
+* Confirm that translations and the English version have the same content.
+* Check that no unexplained acronyms, abbreviations, puns or legal/non-English/domain specific terms are in the documentation.
+* Check the spelling, grammar and readability of the documentation.
+
+## Public policy makers: what you need to do
+
+* Frequently test with other managers, developers and designers in the process if they understand what you are delivering and how you document it.
+
+## Managers: what you need to do
+
+* Try to limit the use of acronyms, abbreviations, puns or legal/non-English/domain specific terms in internal communications in and between teams and stakeholders. Add any such terms to a glossary and link to it from the places they are being used.
+* Be critical of documentation and descriptions in proposals and changes. If you don't understand something, others will probably also struggle with it.
+
+## Developers and designers: what you need to do
+
+* Frequently test with policy makers and managers if they understand what you are delivering and how you document it.
+* Ask someone outside of your context if they understand the content (for example, a developer working on a different codebase).
+
+<p style="page-break-after: always;"></p>
+## Further reading
+
+* Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content readable and understandable.
+* The[European Union accessibility directive](https://ec.europa.eu/digital-single-market/en/web-accessibility) by the European Commission, is an example of regulation requiring high accessibility.
+* [Definition of plain language](https://www.plainlanguage.gov/about/definitions/) by United States General Services Administration.
diff --git a/origin_source/criteria/welcome-contributors.md b/origin_source/criteria/welcome-contributors.md
new file mode 100644
index 00000000..d8b8ce89
--- /dev/null
+++ b/origin_source/criteria/welcome-contributors.md
@@ -0,0 +1,62 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+order: 4
+redirect_from:
+  - criteria/open-to-contributions
+---
+# Welcome contributors
+
+The atmosphere in a [codebase](../glossary.md#codebase) community helps users decide to use one codebase over another.
+Welcoming anyone as a contributor enables the community to grow and sustain itself over time.
+A community where contributors have clear ways to influence codebase and community goals and progress is less likely to split and end up in diverging communities.
+Newcomers need to understand and trust the codebase community’s governance.
+
+## Requirements
+
+* The codebase MUST allow anyone to submit suggestions for changes to the codebase.
+* The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file.
+* The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file.
+* The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.
+* The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.
+* The codebase SHOULD have a publicly available roadmap.
+* The codebase SHOULD publish codebase activity statistics.
+* Including a code of conduct for contributors in the codebase is OPTIONAL.
+
+## How to test
+
+* Confirm that it is possible to submit suggestions for changes to the codebase.
+* Confirm there are contribution guidelines.
+* Confirm that the codebase governance is clearly explained, including how to influence codebase governance.
+* Check that contributing guidelines cover who is expected to cover the costs of reviewing contributions.
+* Check for a list of involved organizations.
+* Check for a roadmap.
+* Check for published activity statistics.
+* Check for a code of conduct.
+
+## Public policy makers: what you need to do
+
+* Add a list to the codebase of any other resources that [policy](../glossary.md#policy) experts, non-governmental organizations and academics would find useful for understanding or reusing your policy.
+* Consider adding contact details so that other policy makers considering collaboration can ask you for advice.
+
+## Managers: what you need to do
+
+* Make sure that the documentation of the governance includes the current process for how to make changes to the governance.
+* If the community has some consensus about how the governance should change, then include those ideas stated as ambitions in the documentation.
+* If needed, make sure you have allocated budget for the contributions review process as agreed by the codebase community.
+* Make sure the documentation explains how each organization is involved in the codebase, what resources it has available for it and for how long.
+* Support your experienced policy makers, developers and designers to stay part of the community for as long as possible.
+
+<p style="page-break-after: always;"></p>
+## Developers and designers: what you need to do
+
+* Respond promptly to requests.
+* Keep your managers informed of the time and resources you require to support other contributors.
+* Communicate clearly to contributors what they need to do make sure their contribution can be integrated.
+
+## Further reading
+
+* [Building welcoming communities](https://opensource.guide/building-community/) by Open Source Guides.
+* [The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/) by Mike McQuaid.
+* [Leadership and governance](https://opensource.guide/leadership-and-governance/) for growing [open source](../glossary.md#open-source) community projects, by Open Source Guides.
+* [Building online communities](http://hintjens.com/blog:117) by Pieter Hintjens (long read!).
diff --git a/origin_source/docs/printing.md b/origin_source/docs/printing.md
new file mode 100644
index 00000000..7994c3b2
--- /dev/null
+++ b/origin_source/docs/printing.md
@@ -0,0 +1,22 @@
+# Printing
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+The printed Standard for Public Code is printed by Reclameland.
+This guide tries to provide the relevant information to print it there or somewhere else.
+
+Details, mostly in order they are on the Reclameland page with the Dutch if necessary:
+
+* Form: Softcover book ([Reclameland product page](https://www.reclameland.nl/drukken/softcover-boeken))
+* Format: A4
+* Portrait or landscape: Portrait (Staand)
+* Printing inside: 4/4 dual sided full color
+* Inside material: 90 grams biotop
+* Cover: 350 grams cover
+* Printing cover: 4/0 one sided full cover
+* Cover treatment: one sided matt foliated (Enke)
+* Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a multiple of 4
+* Individually sealed: no
+
+When these details are chosen, the cover and insides are uploaded and the order is placed payment can happen (payment ahead) after which printing starts.
diff --git a/origin_source/docs/releasing.md b/origin_source/docs/releasing.md
new file mode 100644
index 00000000..caada9f9
--- /dev/null
+++ b/origin_source/docs/releasing.md
@@ -0,0 +1,39 @@
+# Releasing a new version of the Standard for public code
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+1. Review state of the 'develop' branch
+    - Ensure all changes intended for release are merged
+    - Invite a proofread of the current state of the branch
+        - If new dashes are introduced, check if the language can be simplified to remove them in favor of more simple sentences. If a complex sentence is needed, see if the dash can be replaced with other punctuation. If a dash is truly the best expression of ideas, then follow the [Chicago Manual of Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash).
+2. Create a release branch
+    - From 'develop', `git switch -c "release-$MAJOR.$MINOR.$PATCH"`
+    - Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`
+3. Update the new release
+    - [ ] Update [`AUTHORS.md`](../AUTHORS.md) with new contributors
+    - [ ] Update [`CHANGELOG.md`](../CHANGELOG.md)
+    - [ ] Update [`roadmap.md`](roadmap.md)
+    - [ ] Perform extra pass on diff to the 'main' branch
+        - run `script/generate-review-template.sh` and commit updated `docs/review-template.html`
+        - update `docs/standard-for-public-code.html` with the new text from the review template, updating any status changes as a result
+        - Reread any section or paragraph to ensure wording changes still fit the whole and do not contain grammar or spelling errors
+        - Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see: `script/ensure-font.sh`
+        - Check the rendered `.pdf` using `script/pdf.sh rc1`
+          - Ensure no link collisions exist
+          - Check the page breaks, possibly removing or adding page-break CSS, for example: `<p style="page-break-after: always;"></p>`
+        - If needed, commit fixes and repeat extra pass
+    - [ ] Push branch, compare with 'main' branch, i.e.: `https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`
+        - Request review from multiple reviewers, especially a proofreader
+        - Reviewers will create issues for shortcomings found which would not prevent release
+        - If needed for release, reviewers may create pull requests to resolve issues
+        - Re-request reviews if additional pull requests are merged into release branch
+    - [ ] Run the to-archive-org.sh script
+4. Create GitHub release with the release notes and version number
+    - [ ] `git tag trigger-$MAJOR.$MINOR.$PATCH`
+    - [ ] `git push --tags` (see: `../.github/workflows/release-on-tag.yml`)
+    - [ ] delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`
+5. [Send the files for print to the printer](printing.md)
+    - [ ] Cover file
+    - [ ] Inside pages PDF
+6. Ping [translation](https://github.com/publiccodenet/community-translations-standard) contributors
diff --git a/origin_source/docs/roadmap.md b/origin_source/docs/roadmap.md
new file mode 100644
index 00000000..40e5f47d
--- /dev/null
+++ b/origin_source/docs/roadmap.md
@@ -0,0 +1,33 @@
+# Roadmap
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+Last updated: 2023-03-08
+
+This document intends to shed light on the current development plans of the team.
+Plans change constantly as new information is absorbed by the team.
+
+Codebase stewards review the roadmap monthly as part of our [backlog pruning session](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html).
+
+## Current work
+
+* As far as possible, make the standard Standard-compliant
+* Certification badges
+
+## Near term
+
+* Separate executive summary (issue #302)
+* Physical paper checklist
+* Possibly: add in the illustrations for each criterion
+
+## Longer term
+
+* Add to README and index.md information (and eventually statistics) on adoption and use (issue #438)
+* Becoming validated by multiple codebases
+* Release version 1.0.0 after a few codebases are compliant
+* Linkable requirements
+* New cover art
+* Register for ISBN
+* List with an on-demand book printing service
+* QR codes for external links in print version
diff --git a/origin_source/foreword.md b/origin_source/foreword.md
new file mode 100644
index 00000000..069f2207
--- /dev/null
+++ b/origin_source/foreword.md
@@ -0,0 +1,177 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+redirect_from:
+  - introduction
+---
+# Foreword
+
+The Standard for Public Code is a set of criteria that support public organizations in developing and maintaining software and policy together.
+
+Anyone developing public-purpose software or policy can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control.
+
+This foreword introduces the term public code and explains why this is important.
+
+## Definition of public code
+
+Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+It encompasses the software built to operate with and as public infrastructure, along with the arrangements for its production.
+Public code is explicitly distinct from regular software because it operates under fundamentally different circumstances and expectations.
+
+## Reasons for public code
+
+There are many reasons for why public code is relevant now.
+
+### Software code == legal code
+
+Software is public infrastructure.
+
+In the 21st century, software can be considered vital public infrastructure.
+It is increasingly not just the expression of existing policy but the originator of new policy, for example where algorithms decide which districts need extra social services or policing.
+
+Software mechanics, algorithms and data collection have become key elements in the execution of public policies.
+Computer code now executes policies that have been codified in legal code through democratic procedures.
+Both forms of code set conditions for society to function according to democratically set public values, the latter executed by humans, the former by machines.
+In other words, software code has increasingly started to equal legal code.
+
+Software should therefore be subject to the principles of democratic governance.
+
+### Traditional public software procurement
+
+Current public software production methods have not served public service delivery very well.
+
+In the last decade, public organizations that purchased complete software solutions have sometimes been surprised to discover that they:
+
+* can’t change their software to reflect changing policy or take advantage of new technology
+* don’t have access to their data as it's locked into proprietary systems
+* are asked to pay ever increasing license fees
+
+### Technological sovereignty and democratic accountability
+
+Public institutions, civil servants and residents deserve better.
+
+We believe the software that runs our society can no longer be a black box, controlled by outside companies that keep the underlying logic on which their software operates hidden in proprietary codebases.
+Instead, governments and the people they serve need technological sovereignty.
+This allows them to set and control the functioning of public software, just like they are able to set and control policy that is legally formulated in laws.
+Citizens and civil society actors need this software to be transparent and accountable.
+
+The design of software as essential civic infrastructure should honor digital citizens’ rights.
+
+### Designing truly public software
+
+Public code is at the core of modern public institutions, shapes the work of civil servants and affects the lives of almost all residents.
+
+Public software must therefore be:
+
+* transparent
+* accountable
+* understandable for its constituents
+
+It must reflect the values of the society it serves, for example by being inclusive and non-discriminatory.
+
+Most proprietary software systems currently used by public organizations do not meet these requirements.
+Public code does.
+
+### Values of public code
+
+We consider public code to have these core values:
+
+* Inclusive
+* Usable
+* Open
+* Legible
+* Accountable
+* Accessible
+* Sustainable
+
+## How public code works
+
+Public code is open source software meant for fulfilling the essential role of public organizations.
+Through use, other administrations contribute back to the software, so that its development and maintenance become truly collaborative.
+
+Being open unlocks many other things.
+
+Local responsibility and democratic accountability are ensured when a public organization implements and maintains their own public code.
+By being open and with a broader contributor base, the software is more secure as it benefits from many eyes spotting potential flaws.
+Many contributors share the maintenance work to keep it functional and modern, which reduces future technical debt.
+The shared workload is more sustainable now and in the future.
+Its openness makes both the code and its data more easily adaptable in the future.
+The code will be easier to retool, repurpose or retire.
+This all results in lower risk public infrastructure.
+
+This pooling of resources lets public administrations give extra attention to how to customize the software so it works best in each local context, creating better user experiences for their end users (residents or citizens).
+
+### Economics of public code
+
+Public code offers a better economic model for public organizations as well as for commercial companies.
+It's an alternative to traditional software procurement which increases local control and economic opportunity.
+
+Designed from the start to be open, adaptable and with data portability, it can be developed by in-house staff or trusted vendors.
+Because the code is open, the public administration can change vendors if they need to.
+Open code increases opportunities for public learning and scrutiny, allowing the public administration to procure smaller contracts.
+Smaller procurements are easier for local small and medium enterprises to bid upon.
+Public administrations can use their own software purchasing to stimulate innovation and competition in their local economy.
+
+This can be seen as investment leading to future economic growth.
+More vendors will be necessary due to growing technology demand.
+
+### Procuring public code
+
+Public code can be used and developed by permanent in-house development teams, contractors or outsourced suppliers.
+Vendors to public organizations can include public code in their bids for contracts.
+
+To use existing public code, you need to specify in your budget and project design that your new solution will use that codebase.
+To encourage an innovative approach to adapting the public code to your context, you could describe the service or outcome in your contract.
+
+## The goals for the Standard for Public Code
+
+This Standard supports developers, designers, managers and public policy makers to:
+
+* develop high quality software and policy for better public service delivery
+* develop codebases that can be reused across contexts and collaboratively maintained
+* reduce technical debt and project failure rate
+* have more granular control over, and ability to make decisions about, their IT systems
+* improve vendor relationships with a better economic model
+
+Potential users of codebases tested against the Standard for Public Code can expect them to be highly reusable, easily maintainable and of high quality.
+
+The Standard for Public Code does this by:
+
+* setting out a common terminology for public code development
+* establishing measures to help develop high quality public code
+* providing guidance on how to fulfill its criteria and operationalize compliance
+
+The Standard for Public Code is meant to be time and technology independent.
+
+### Who this is for
+
+The Standard for Public Code is for the people who create and reuse public code:
+
+* public policy makers
+* business and project managers
+* developers and designers
+
+These people work at:
+
+* institutions, organizations and administrations in the public sector
+* consultancies and vendors of information technology and policy services to public organizations
+
+It is not aimed at public organizations' end users (residents or citizens), journalists or academics.
+
+## Further reading
+
+* ["Modernising Public Infrastructure with Free Software" white paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) by the Free Software Foundation Europe.
+
+### Videos on public code
+
+* [Collaborative Code is the Future of Cities @ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on the background behind the Foundation for Public Code.
+* [Public Money? Public Code! - Panel @ Nextcloud Conference 2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like procurement, law and more.
+
+## Get involved
+
+This standard is a living document.
+[Read our contributor guide](/CONTRIBUTING.md) to learn how you can make it better.
+
+## Contact
+
+For questions and more information about the Foundation for Public Code you can find us at [our website](https://publiccode.net/), email us at info@publiccode.net, or call us at +31 20 2 444 500.
diff --git a/origin_source/glossary.md b/origin_source/glossary.md
new file mode 100644
index 00000000..4cb3464e
--- /dev/null
+++ b/origin_source/glossary.md
@@ -0,0 +1,86 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+---
+# Glossary
+
+## Code
+
+Any explicitly described system of rules.
+This includes laws, policy and ordinances, as well as source code that is used to build software.
+Both of these are rules, some executed by humans and others by machines.
+
+## Codebase
+
+Any discrete package of code (both source and policy), the tests and the documentation required to implement a piece of policy or software.
+
+This can be, for example, a document or a version-control repository.
+
+## Continuous integration
+
+In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a development branch of a codebase as frequently as reasonable.
+
+## Different contexts
+
+Two contexts are different if they are different public organizations or different departments for which there is not one decision maker that could make collaboration happen naturally.
+
+## General public
+
+The public at large: end users of the code and the services based upon it.
+
+For example, a city's residents are considered end users of a city's services and of all code that powers these services.
+
+## Open source
+
+Open source is defined by the Open Source Initiative in their [Open Source Definition](https://opensource.org/osd-annotated).
+
+## Open standard
+
+An open standard is any standard that meets the Open Source Initiative's [Open Standard Requirements](https://opensource.org/osr).
+
+## Policy
+
+A policy is a deliberate system of principles to guide decisions and achieve rational outcomes.
+A policy is a statement of intent, and is implemented as a procedure or protocol.
+Policies are generally adopted by a governance body within an organization.
+Policies can assist in both subjective and objective decision making.
+
+Public policy is the process by which governments translate their political vision into programs and actions to deliver outcomes.
+
+At the national level, policy and legislation (the law) are usually separate.
+The distinction is often more blurred in local government.
+
+In the Standard the word 'policy' refers to policy created and adopted by public organizations such as governments and municipalities.
+
+## Public code
+
+Public code is open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+
+Public code is both computer source code (such as software and algorithms) and public policy executed in a public context, by humans or machines.
+
+Public code serves the public interest, is open, legible, accountable, accessible and sustainable.
+
+By developing public code independently from but still implementable in the local context for which it was developed, as well as documenting the development process openly, public code can provide a building block for others to:
+
+* re-implement in their local context
+* take as a starting point to continue development
+* use as a basis for learning
+
+To facilitate reuse, public code is either released into the public domain or licensed with an open license that permits others to view and reuse the work freely and to produce derivative works.
+
+## Repository
+
+A repository is a storage location used by version control tools for files and metadata of a codebase.
+Repositories allow multiple contributors to work on the same set of files.
+Repositories are able to store multiple versions of sets of files.
+
+## Source Code
+
+Human readable text of a computer program which can be translated into machine instructions.
+
+## Version control
+
+Version control is the management of changes to source code and the files associated with it.
+Changes are usually identified by a code, termed the *revision number* (or similar).
+Each revision is associated with the time it was made and the person making the change, thus making it easier to retrace the evolution of the code.
+Revision control systems can be used to compare different versions with each other and to see how content has changed over time.
diff --git a/origin_source/index.md b/origin_source/index.md
new file mode 100644
index 00000000..1700ac9e
--- /dev/null
+++ b/origin_source/index.md
@@ -0,0 +1,46 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+toc: false
+---
+# Guidance for government open source collaboration
+
+The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together.
+
+The Standard for Public Code provides guidance to public organizations building their own open source solutions to enable successful future collaboration and reuse by similar organizations in the public sector in other places.
+It includes advice for policy makers, government managers, developers and vendors.
+The Standard for Public Code supports the collaborative creation of codebases that are usable, open, legible, accountable, accessible and sustainable.
+It is meant to be applicable to codebases for all levels of government, from supranational to municipal.
+
+The Standard for Public Code defines ‘[public code](glossary.md#public-code)’ as open source software developed by public organizations, together with the policy and guidance needed for collaboration and reuse.
+
+The criteria of the Standard for Public Code are aligned with guidelines and best practices of open source software development.
+
+{% for page in site.pages %}{% if page.name == "foreword.md" %}
+Additional context and background can be found in the [foreword](foreword.md).
+{% endif%}{% endfor %}
+
+## Contents
+
+* [Readers guide: how to interpret this standard](readers-guide.md)
+* [Glossary](glossary.md)
+* [Criteria](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
+  * [{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}
+* [Authors](AUTHORS.md)
+* [Contributing guide](CONTRIBUTING.md)
+* [Code of conduct](CODE_OF_CONDUCT.md)
+* [Governance](GOVERNANCE.md)
+* [Version history](CHANGELOG.md)
+* [License](license.html)
+
+## Community calls
+
+We usually have a community call on the first Thursday of the month at 15:00 (CET/CEST).
+[The agenda](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code) is updated roughly a week before the call.
+It is possible to [sign up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842) to get a call invitation emailed to you.
+
+## Other resources
+
+* Unofficial [community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/) in other languages
+* [Standard compliance self assessment](https://publiccodenet.github.io/assessment-eligibility/) for public sector open source codebases
+* [Standard criteria checklist](/docs/review-template.html) used by Foundation for Public Code stewards for codebase review
diff --git a/origin_source/readers-guide.md b/origin_source/readers-guide.md
new file mode 100644
index 00000000..9a6208ab
--- /dev/null
+++ b/origin_source/readers-guide.md
@@ -0,0 +1,72 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+---
+# Readers guide
+
+The Standard describes a number of criteria.
+All criteria have consistent sections that make it clear how to create great public code.
+
+References to "policy makers", "managers", and "developers and designers" apply to anyone performing duties associated with these roles, regardless of their job title.
+It is common for individuals to have duties which span multiple roles.
+
+Below is a brief explanation of each of these sections and how they are used within the criteria of the Standard.
+
+## Introduction
+
+This section explains what the criterion aims to achieve and why it is important for a codebase's users and contributors.
+
+## Requirements
+
+This section lists what needs to be done in order to comply with the standard.
+
+The following keywords in this document are to be interpreted as described in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):
+
+* MUST
+* MUST NOT
+* REQUIRED
+* SHALL
+* SHALL NOT
+* SHOULD
+* SHOULD NOT
+* RECOMMENDED
+* MAY
+* OPTIONAL
+
+## How to test
+
+This section offers actions you can take to see if a contribution is compliant with the Standard.
+This is key if you want to operationalize the Standard.
+
+We've tried to word it so that someone who is not intimately acquainted with the subject matter can still do a basic check for compliance.
+
+## Public policy makers: what you need to do
+
+This section tries to specifically speak to policy makers by offering them concrete actions they can perform in their role.
+
+Public policy makers set the priorities and goals of projects and may be less technologically experienced.
+
+## Managers: what you need to do
+
+This section tries to specifically speak to managers by offering concrete actions they can perform in their role.
+
+Managers are responsible for on-time project delivery, stakeholder management and continued delivery of the service.
+For this they are wholly reliant on both policy makers as well as developers and designers.
+They need to create the right culture, line up the right resources and provide the right structures to deliver great services.
+
+## Developers and designers: what you need to do
+
+This section tries to specifically speak to developers and designers by offering them concrete actions they can perform in their role.
+
+Developers are usually more technically aligned and have more impact on the delivery of services than the previous groups.
+
+## Limitation of scope
+
+The Standard for Public Code is not meant to cover individual implementations of a codebase.
+This means the standard does not tell implementers how to comply with their organization's local technical infrastructure or legal framework.
+
+Also, while the Standard for Public Code refers to several standards and has considerable overlap with others, its purpose is to enable collaboration.
+Therefore, it does not aim to replace quality standards, like the ISO 25000 series, or those focusing on security, like the [OpenSSF Best Practices Badge](https://github.com/coreinfrastructure/best-practices-badge), but to synergize well with them.
+
+And while the purpose includes enabling collaboration, it will not guarantee that a community will spring into existence.
+That still requires proactiveness and ambition beyond making the codebase collaboration ready.
diff --git a/python/po2md.py b/python/po2md.py
new file mode 100644
index 00000000..05dbaed6
--- /dev/null
+++ b/python/po2md.py
@@ -0,0 +1,102 @@
+import os
+import shutil
+import subprocess
+
+PROJECT_FOLDER = "./"
+SOURCE_FOLDER = "./origin_source"
+
+def main():
+    root_path = "./"
+    source_path = "./origin_source"
+
+    # 1. get all md file
+    md_files = find_md_files(PROJECT_FOLDER)
+
+    # 2. filter origin file
+    md_files = [file for file in md_files if not file.startswith(SOURCE_FOLDER)]
+
+    # 3A. backup md file (複製一次)
+    # backup_md_files(md_files)
+
+    # 3B. restore md file (複製一次)
+    restore_md_files(md_files)
+
+    # 4. run po2md
+    for file in md_files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        do_po2md(source_file=full_target_path, target_file=file)
+
+    # 4. update md file
+    update_md_file(SOURCE_FOLDER)
+
+
+
+
+def find_md_files(folder_path) -> list:
+    md_files = []
+    for root, dirs, files in os.walk(folder_path):
+        md_files += [os.path.join(root, file) for file in files if file.endswith('.md')]
+    return md_files
+
+# 複製原始檔案
+def backup_md_files(files):
+    if not os.path.exists(SOURCE_FOLDER):
+        os.makedirs(SOURCE_FOLDER)
+
+    for file in files:
+        # 建立目標資料夾的完整路徑
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        if not os.path.exists(os.path.dirname(full_target_path)):
+            os.makedirs(os.path.dirname(full_target_path))
+
+        # 複製檔案到目標資料夾
+        shutil.copy2(file, full_target_path)
+
+# 還原原始檔案
+def restore_md_files(files):
+    for file in files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        shutil.copy2(full_target_path, file)
+
+
+def do_po2md(source_file, target_file):
+    locale_file = "locales/zh_Hant/LC_MESSAGES/messages.po"
+    cmd = f"po2md -p {locale_file} -s {target_file} {source_file}"
+    result = subprocess.run(cmd, shell=True, capture_output=True, text=True)
+    if result.returncode != 0:
+        print("錯誤訊息：")
+        print(result.stderr)
+        exit()
+
+def update_md_file(source_path):
+    source_marker = "---"
+    target_marker = "***"
+
+    source_files = find_md_files(source_path)
+    for file in source_files:
+        with open(file, 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(source_marker)
+        end_index = file_content.find(source_marker, start_index + len(source_marker))
+        copied_content = file_content[start_index:end_index + len(source_marker)]
+
+
+        with open(file[len(source_path) + 1:], 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(target_marker)
+        end_index = file_content.find(target_marker, start_index + len(target_marker))
+        if end_index == -1:
+            print(file)
+            continue
+
+        new_content = copied_content + file_content[end_index + len(target_marker):]
+
+        with open(file[len(source_path) + 1:], 'w') as outfile:
+            outfile.write(new_content)
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file
diff --git a/python/update_po.py b/python/update_po.py
new file mode 100644
index 00000000..b8df8924
--- /dev/null
+++ b/python/update_po.py
@@ -0,0 +1,34 @@
+import os
+import shutil
+import subprocess
+import polib
+
+
+def main():
+    locals_en = 'locales/en/LC_MESSAGES/messages.po'
+    locals_zh = 'locales/zh_Hant/LC_MESSAGES/messages.po'
+    en_po = polib.pofile(locals_en)
+    zh_po = polib.pofile(locals_zh)
+
+    zh_msgids = set(entry.msgid for entry in zh_po)
+
+    # 遍歷 en.po 中的每一個 entry
+    for entry in en_po:
+        # 如果 en.po 中的 msgid 不在 zh.po 中
+        if entry.msgid not in zh_msgids:
+            # 創建一個新的 POEntry 對象
+            new_entry = polib.POEntry(
+                msgid=entry.msgid,
+                msgstr='',  # 初始為空字符串
+            )
+            # 將新的 entry 添加到 zh.po 中
+            zh_po.append(new_entry)
+
+    # 儲存更新後的 zh.po 檔案
+    zh_po.save(locals_zh)
+
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file
diff --git a/readers-guide.md b/readers-guide.md
index 9a6208ab..1d2f7d7b 100644
--- a/readers-guide.md
+++ b/readers-guide.md
@@ -2,71 +2,69 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
-# Readers guide
+# 讀者指南
 
-The Standard describes a number of criteria.
-All criteria have consistent sections that make it clear how to create great public code.
+公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的公共程式。
 
-References to "policy makers", "managers", and "developers and designers" apply to anyone performing duties associated with these roles, regardless of their job title.
-It is common for individuals to have duties which span multiple roles.
+「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職責的人，不受職稱限制。很多人都承擔多個角色的職責。
 
-Below is a brief explanation of each of these sections and how they are used within the criteria of the Standard.
+以下是 The Standard for Public Code 各章節的簡介，以及在標準當中的功用。
 
-## Introduction
+## 前言
 
-This section explains what the criterion aims to achieve and why it is important for a codebase's users and contributors.
+本章節探討這些標準的目的，以及為什麼對代碼庫使用者與貢獻者很重要的原因。
 
-## Requirements
+## 規定
 
-This section lists what needs to be done in order to comply with the standard.
+這章節解釋如何遵循 The Standard for Public Code 。
 
-The following keywords in this document are to be interpreted as described in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):
+本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) 來詮釋：
 
-* MUST
-* MUST NOT
-* REQUIRED
-* SHALL
-* SHALL NOT
-* SHOULD
-* SHOULD NOT
-* RECOMMENDED
-* MAY
-* OPTIONAL
+* 必須
+* 不得
+* 被要求
+* 應該
+* 不應
+* 應該
+* 不應
+* 建議
+* 得
+* 可選擇
 
-## How to test
+## 測試方式
 
-This section offers actions you can take to see if a contribution is compliant with the Standard.
-This is key if you want to operationalize the Standard.
+本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public Code 。如果您想要實施 The Standard for
+Public Code ，這將會是關鍵。
 
-We've tried to word it so that someone who is not intimately acquainted with the subject matter can still do a basic check for compliance.
+我們的用字是要讓不熟悉此主題的讀者，看了之後也能夠進行基本的遵循檢測。
 
-## Public policy makers: what you need to do
+## 公共政策制定者：您的責任
 
-This section tries to specifically speak to policy makers by offering them concrete actions they can perform in their role.
+本章節主要對象是政策制定者，列出他們的角色能採取的具體行動。
 
-Public policy makers set the priorities and goals of projects and may be less technologically experienced.
+公共政策制定者決定專案的優先順序與目標，在科技上的經驗可能沒那麼多。
 
-## Managers: what you need to do
+## 管理人員：您的義務
 
-This section tries to specifically speak to managers by offering concrete actions they can perform in their role.
+本章節主要對象是管理人員，列出他們的角色能採取的具體行動。
 
-Managers are responsible for on-time project delivery, stakeholder management and continued delivery of the service.
-For this they are wholly reliant on both policy makers as well as developers and designers.
-They need to create the right culture, line up the right resources and provide the right structures to deliver great services.
+管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源，提供正確
+的架構，才能夠帶來良好的服務。
 
-## Developers and designers: what you need to do
+## 開發人員與設計師：您的責任
 
-This section tries to specifically speak to developers and designers by offering them concrete actions they can perform in their role.
+本章節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。
 
-Developers are usually more technically aligned and have more impact on the delivery of services than the previous groups.
+開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務交付的影響更大。
 
-## Limitation of scope
+## 範圍限制
 
-The Standard for Public Code is not meant to cover individual implementations of a codebase.
-This means the standard does not tell implementers how to comply with their organization's local technical infrastructure or legal framework.
+The Standard for Public Code 不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框
+架。
 
-Also, while the Standard for Public Code refers to several standards and has considerable overlap with others, its purpose is to enable collaboration.
-Therefore, it does not aim to replace quality standards, like the ISO 25000 series, or those focusing on security, like the [OpenSSF Best Practices Badge](https://github.com/coreinfrastructure/best-practices-badge), but to synergize well with them.
+The Standard for Public Code 有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。因此The Standard
+for Public Code 目的並非是要取代品質標準（像是 ISO 25000 認證），或是以安全為準的標準（像是 [OpenSSF 最佳實務標
+章](https://github.com/coreinfrastructure/best-practices-badge)），而是要與他們協作。
 
-And while the purpose includes enabling collaboration, it will not guarantee that a community will spring into existence.
-That still requires proactiveness and ambition beyond making the codebase collaboration ready.
+The Standard for Public Code 的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也
+需要協作者的積極推動與野心。

From 4f487ed3c46950d297217bff92061d8592b5a9b1 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Fri, 1 Sep 2023 07:18:22 +0000
Subject: [PATCH 44/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 28 ++++++++++++-------------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 9b5dd769..1a52cdbe 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-08-30 02:17+0000\n"
-"Last-Translator: Toomore <toomore@ocf.tw>\n"
+"PO-Revision-Date: 2023-09-01 13:05+0000\n"
+"Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -45,11 +45,11 @@ msgstr "404 找不到網頁"
 
 #: ./404.md:block 5 (paragraph)
 msgid "If you typed the web address, check it is correct."
-msgstr "如果您手動輸入網址，請確認網址是否正確。"
+msgstr "如果您是手動輸入網址，請確認網址是否正確。"
 
 #: ./404.md:block 6 (paragraph)
 msgid "If you pasted the web address, check you copied the entire address."
-msgstr "如果您複製貼上此網址，請確認是否有複製到完整的網址。"
+msgstr "如果您是複製貼上此網址，請確認是否有複製到完整的網址。"
 
 #: ./404.md:block 7 (paragraph)
 msgid ""
@@ -57,8 +57,8 @@ msgid ""
 "[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
 "able to help you out, as well as correct our mistake."
 msgstr ""
-"若網址正確或是您按下連結或按鈕，請寫信給 [the Foundation for Public Code "
-"人員](mailto:info@publiccode.net)，讓我們能夠協助您，並且修正我們的錯誤。"
+"若網址正確，或您是按下連結或按鈕，請寫信給 [Foundation for Public Code "
+"員工](mailto:info@publiccode.net)，讓我們協助您，並且修正我們的錯誤。"
 
 #: ./AUTHORS.md:block 2 (header)
 msgid ""
@@ -156,8 +156,8 @@ msgid ""
 "(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
 "Creative Industries, Lectorate of Play & Civic Media"
 msgstr ""
-"Martijn de Waal，[阿姆斯特丹應用科技大學 "
-"(AUAS)](https://www.amsterdamuas.com/)，數位媒體與創意產業學院劇場與公民媒體系講師"
+"Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas."
+"com/)，數位媒體與創意產業學院，戲劇與公民媒體系講師"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Matti Schneider"
@@ -191,9 +191,7 @@ msgstr "Paul Keller"
 msgid ""
 "Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
 "(NIIS)](https://niis.org)"
-msgstr ""
-"Petteri Kivimäki， [Nordic Institute for Interoperability Solutions "
-"(NIIS)](https://niis.org)"
+msgstr "Petteri Kivimäki， [北歐互通性解決方案機構 (NIIS)](https://niis.org)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Sky Bristol"
@@ -213,13 +211,13 @@ msgstr "toc: false redirect_from: - license.html - LICENSE.html"
 
 #: ./CC0-1.0.md:block 4 (header)
 msgid "Creative Commons Zero v1.0 Universal"
-msgstr "Creative CC Zero v1.0 Universal 授權"
+msgstr "創用 CC0 1.0 通用授權"
 
 #: ./CC0-1.0.md:block 6 (paragraph)
 msgid ""
 "This license is the legal contract that allows anyone to do anything they "
 "like with the content in this entire document."
-msgstr "此授權為法律合約，允許任何人任意使用本文件任何內容。"
+msgstr "此授權為法律契約，允許任何人任意使用本文件中的任何內容。"
 
 #: ./CHANGELOG.md:block 3 (header)
 msgid "Version history"
@@ -239,7 +237,7 @@ msgstr "2023年5月31日：📑第十五版新增募資審查紀錄新規定，
 msgid ""
 "Add requirement to document who is expected to cover the cost of reviewing "
 "contributions."
-msgstr "新增規定，紀錄由誰負擔審核貢獻內容費用。"
+msgstr "新增規定，紀錄應由誰負擔審核貢獻內容所需開銷費用。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
@@ -5641,7 +5639,7 @@ msgstr ""
 
 #: ./index.md:block 10 (header)
 msgid "Contents"
-msgstr "目錄"
+msgstr "目次"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"

From c92867aaea714f2c6ba2d6fc50fdde5a11f1a06a Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Mon, 4 Sep 2023 03:36:38 +0000
Subject: [PATCH 45/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 415 +++++++++++++-----------
 1 file changed, 221 insertions(+), 194 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 1a52cdbe..1723f298 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-01 13:05+0000\n"
+"PO-Revision-Date: 2023-09-04 09:27+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -25,9 +25,8 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), "
-"https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2022-2023 Foundation for Public Code [info@publiccode"
+".net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./404.md:block 3 (header)
 msgid ""
@@ -57,8 +56,8 @@ msgid ""
 "[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
 "able to help you out, as well as correct our mistake."
 msgstr ""
-"若網址正確，或您是按下連結或按鈕，請寫信給 [Foundation for Public Code "
-"員工](mailto:info@publiccode.net)，讓我們協助您，並且修正我們的錯誤。"
+"若網址正確，或您是按下連結或按鈕來的，請寫信給 [Foundation for Public Code "
+"員工](mailto:info@publiccode.net)，讓我們協助您，並同時修正我們的錯誤。"
 
 #: ./AUTHORS.md:block 2 (header)
 msgid ""
@@ -66,9 +65,8 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
-"[info@publiccode.net](mailto:info@publiccode.net), "
-"https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2019-2023 Foundation for Public Code [info@publiccode"
+".net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./AUTHORS.md:block 3 (header)
 msgid "Authors"
@@ -76,7 +74,7 @@ msgstr "作者群"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
-msgstr "Alba Roza，[The Foundation for Public Code](https://publiccode.net/)"
+msgstr "Alba Roza，[Foundation for Public Code](https://publiccode.net/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Arnout Engelen"
@@ -84,15 +82,15 @@ msgstr "Arnout Engelen"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Arnout Schuijff, The Foundation for Public Code"
-msgstr "Arnout Schuijff，The Foundation for Public Code"
+msgstr "Arnout Schuijff，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
-msgstr "唐鳳，[digitalminister.tw](https://digitalminister.tw/)"
+msgstr "唐鳳，[數位發展部](https://digitalminister.tw/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Ben Cerveny, The Foundation for Public Code"
-msgstr "Ben Cerveny，The Foundation for Public Code"
+msgstr "Ben Cerveny，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Bert Spaan"
@@ -100,7 +98,7 @@ msgstr "Bert Spaan"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Boris van Hoytema, The Foundation for Public Code"
-msgstr "Boris van Hoytema，The Foundation for Public Code"
+msgstr "Boris van Hoytema，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Charlotte Heikendorf"
@@ -108,7 +106,7 @@ msgstr "Charlotte Heikendorf"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Claus Mullie, The Foundation for Public Code"
-msgstr "Claus Mullie，The Foundation for Public Code"
+msgstr "Claus Mullie，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "David Barberi"
@@ -120,15 +118,15 @@ msgstr "Edo Plantinga，[Code For NL](https://codefor.nl/)"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Elena Findley-de Regt, The Foundation for Public Code"
-msgstr "Elena Findley-de Regt，The Foundation for Public Code"
+msgstr "Elena Findley-de Regt，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Eric Herman, The Foundation for Public Code"
-msgstr "Eric Herman，The Foundation for Public Code"
+msgstr "Eric Herman，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Felix Faassen, The Foundation for Public Code"
-msgstr "Felix Faassen，The Foundation for Public Code"
+msgstr "Felix Faassen，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Floris Deerenberg"
@@ -136,7 +134,7 @@ msgstr "Floris Deerenberg"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Jan Ainali, The Foundation for Public Code"
-msgstr "Jan Ainali，The Foundation for Public Code"
+msgstr "Jan Ainali，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Johan Groenen, Code For NL"
@@ -177,7 +175,7 @@ msgstr "Maurits van der Schee，阿姆斯特丹市政府"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Mirjam van Tiel, The Foundation for Public Code"
-msgstr "Mirjam van Tiel，The Foundation for Public Code"
+msgstr "Mirjam van Tiel，Foundation for Public Code"
 
 #: ./AUTHORS.md:block 4 (unordered list)
 msgid "Ngô Ngọc Đức Huy"
@@ -217,7 +215,7 @@ msgstr "創用 CC0 1.0 通用授權"
 msgid ""
 "This license is the legal contract that allows anyone to do anything they "
 "like with the content in this entire document."
-msgstr "此授權為法律契約，允許任何人任意使用本文件中的任何內容。"
+msgstr "此授權的法律契約允許任何人任意使用本文件中的任何內容。"
 
 #: ./CHANGELOG.md:block 3 (header)
 msgid "Version history"
@@ -231,13 +229,13 @@ msgstr "0.7.0 版"
 msgid ""
 "May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
 "review funding and clarifies review process requirement."
-msgstr "2023年5月31日：📑第十五版新增募資審查紀錄新規定，並且釐清審查流程規定。"
+msgstr "2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid ""
 "Add requirement to document who is expected to cover the cost of reviewing "
 "contributions."
-msgstr "新增規定，紀錄應由誰負擔審核貢獻內容所需開銷費用。"
+msgstr "新增規定，紀錄由誰負擔審核貢獻內容所需的開銷費用。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
@@ -247,27 +245,28 @@ msgstr "新增規定，代碼庫必須要有簡短說明。"
 msgid ""
 "Change the focus of contributions adhering to standards to focus on the "
 "review of contributions."
-msgstr "原本專注在貢獻內容是否符合標準，現在應該專注在貢獻內容審查。"
+msgstr "原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr "許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到。"
+msgstr "將〈代碼庫可查詢得到〉中許多「必須（Must）」等級的規定，調降為「應該（Should"
+"）」等級。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
-msgstr "審查HTML格式的範本。"
+msgstr "審查範本現在有 HTML 格式。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Introduction converted to foreword."
-msgstr "「簡介」轉變為「序」。"
+msgstr "「簡介」轉換為「序」。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved contributing guidelines."
-msgstr "已改善貢獻指南。"
+msgstr "改善貢獻指引。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved documentation of scripts."
-msgstr "已改善腳本註解。"
+msgstr "改善命令稿文件紀錄。"
 
 #: ./CHANGELOG.md:block 8 (header)
 msgid "Version 0.6.0"
@@ -277,109 +276,110 @@ msgstr "0.6.0 版"
 msgid ""
 "April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
 "portability and tests and an introduction to each criterion."
-msgstr "2023年4月20日：🔀第十四版新增可移植性與測試的規定，並且介紹每個標準。"
+msgstr "2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且介紹每個準則。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about the development "
 "being a collaboration between multiple parties."
-msgstr "新增規定，針對多方合作的開發案來編寫可重複使用且可移植的程式碼。"
+msgstr "新增規定，在〈編寫可重複使用且可移植的程式碼〉加入多方協作開發的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about being dependent "
 "on a single vendor."
-msgstr "新增規定，針對依賴單一供應商編寫可重複使用且可移植的程式碼。"
+msgstr "新增規定，在〈編寫可重複使用且可移植的程式碼〉中加入依賴單一供應商的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Use continuous integration about publishing results for "
 "automated tests."
-msgstr "新增規定，公布自動化測試結果時，必須使用持續整合。"
+msgstr "新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Differentiating the two requirements about security to clearly be about "
 "providing a method and having documentation about it."
-msgstr "區分兩個安全性規定，一個是有關提供辦法，另一個則是有關安全性的註解。"
+msgstr "對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Rephrased requirements to focus on the codebase rather than contributor "
 "behavior."
-msgstr "已重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。"
+msgstr "重新撰寫規定，將焦點放在代碼庫，而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
-msgstr "已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。"
+msgstr "移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加"
+"入介紹。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added general What this does not do section in the introduction of the "
 "Standard."
-msgstr "在標準簡介中，已新增「不具備以下作用」段落。"
+msgstr "在本《標準》簡介中，加入通用的「此措施辦不到的事」小節。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for public policy makers about related policies and license "
 "compatibility."
-msgstr "已新增有關相關政策與授權相容性的公共政策決策者指南。"
+msgstr "為政策制定者加入相關政策與授權相容性的指引。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added guidance for developers and designers about version controlling files."
-msgstr "已新增有關版本控制檔案的開發人員與設計師指南。"
+msgstr "為開發人員與設計師新增檔案要有版本控制的相關指引。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Clarified guidance for developers and designers about prompt responses and "
 "search engine optimization."
-msgstr "已釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。"
+msgstr "為開發人員與設計師釐清有關快速回應，以及搜尋引擎最佳化的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added Further reading about accessibility."
-msgstr "已新增「進一步閱讀無障礙」。"
+msgstr "新增可近用性無障礙環境的「延伸閱讀」內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Aligned criteria URLs with criteria names."
-msgstr "已將各標準的連結與其名稱同步。"
+msgstr "將各準則的連結與其名稱連動。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Improved navigation in the web version."
-msgstr "已改善網頁版的導覽功能。"
+msgstr "改善網頁版的導覽功能。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved tools in Further reading sections to the community implementation "
 "guide."
-msgstr "已將「進一步閱讀」章節的工具移到社群實施指南。"
+msgstr "已將「延伸閱讀」小節的工具移到社群實作指引。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Moved compliance or certification process to "
 "[publiccode.net](https://publiccode.net)."
-msgstr "已將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。"
+msgstr "將標準依循或認證相關流程移到 [publiccode.net](https://publiccode.net)。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Change format of the review template to make it easier to update after a new"
 " release."
-msgstr "變更審查範本格式，讓範本在新版本推出後後更容易更新。"
+msgstr "變更審查範本格式，讓範本在發行新版後更容易更新。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Improved the text on the landing page and added links to related resources."
-msgstr "已改善到達網頁文字，加入相關資源的連結。"
+msgstr "改善著陸引導頁文字，加入相關資源的連結。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Added spell checker automated test."
-msgstr "已新增拼字檢查自動化測試。"
+msgstr "新增拼字檢查自動化測試。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Made minor changes to text for clarity and consistency."
-msgstr "已稍微調整文字，讓文字更明確與一致。"
+msgstr "微調文字，讓內容更明確與一致。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid "Moved SPDX headers to yaml header."
@@ -393,37 +393,37 @@ msgstr "0.5.0 版"
 msgid ""
 "January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
 "guidelines."
-msgstr "2023年1月25日：🎨第十三版焦點在於紀錄風格指南。"
+msgstr "2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Adjust the coding style requirement to focus on the codebase using a style "
 "guide rather than contributor behavior."
-msgstr "調整編碼風格要求，專注在代碼庫上面，而非貢獻者行為。"
+msgstr "調整程式碼撰寫風格要求，專注於代碼庫上，而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
-msgstr "已變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。"
+msgstr "將代碼庫名稱規定，從〈使用白話的英文〉移動到〈代碼庫可查詢得到〉。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement about testing the code by using examples to Use continuous"
 " integration from Document the code."
-msgstr "已變更使用範例測試程式碼的規定，改為使用「Document the code」的範例來持續整合測試。"
+msgstr "將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Split requirement about machine testable standards to clarify that open is "
 "more important than testable."
-msgstr "調整機讀標準規定，強調程式碼的開放性比可測試性更重要。"
+msgstr "劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Adjust how to test findability requirements to be less reliant on search "
 "engine algorithms."
-msgstr "調整可查找性的測試規定，減少對搜尋引擎演算法的依賴。"
+msgstr "調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。"
 
 #: ./CHANGELOG.md:block 14 (header)
 msgid "Version 0.4.1"
@@ -431,27 +431,27 @@ msgstr "0.4.1 版"
 
 #: ./CHANGELOG.md:block 15 (paragraph)
 msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
-msgstr "2022年12月5日：📝第十二版闡明文件成熟度。"
+msgstr "2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
 "Document maturity focuses on whether or not versions of the codebase are "
 "ready to use."
-msgstr "文件成熟度端看該版本的代碼庫是否已經可以使用。"
+msgstr "寫下成熟度著重於代碼庫是否已經可供使用，更甚於版本編號。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
 "Document maturity no longer requires specific labels for codebases that are "
 "not ready to use."
-msgstr "文件成熟度不再仰賴尚無法使用的代碼庫中的特定標籤。"
+msgstr "寫下成熟度不再需要為尚未準備好可供使用的代碼庫加上特定標籤。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Audit flow image now generated from an easier to translate format."
-msgstr "審計流程圖現在的由更容易轉譯的格式來生成。"
+msgstr "稽核流程圖現在以更容易轉譯的格式生成。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Improved guidance on How to test."
-msgstr "改善「測試方式」指南。"
+msgstr "改善「測試方式」指引。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add publiccode.yml file."
@@ -463,15 +463,15 @@ msgstr "新增審查範本。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Consistently link glossary terms."
-msgstr "一致連結詞彙。"
+msgstr "一致性連動詞彙表。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add practices and standards to follow in CONTRIBUTING."
-msgstr "在「貢獻」中新增的實務與標準。"
+msgstr "在「CONTRIBUTING」中加入要遵循的實務與標準。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add Matti Schneider to Authors."
-msgstr "加入 Matti Schneider 到作者群。"
+msgstr "將 Matti Schneider 加入作者群。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add remaining SPDX headers to files."
@@ -483,7 +483,7 @@ msgstr "稍微修改文字，讓文字更明確。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Some hyperlinks updated."
-msgstr "已更新部分超連結。"
+msgstr "更新部分超連結。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
@@ -491,8 +491,8 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
-"已將範例移動到[社群實施指南](https://publiccodenet.github.io/community-implementation-"
-"guide-standard/)。"
+"將範例移動到[社群實作指引](https://publiccodenet.github.io/"
+"community-implementation-guide-standard/)。"
 
 #: ./CHANGELOG.md:block 17 (header)
 msgid "Version 0.4.0"
@@ -501,49 +501,51 @@ msgstr "0.4.0 版"
 #: ./CHANGELOG.md:block 18 (paragraph)
 msgid ""
 "September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
-msgstr "2022年9月7日：🔭第十一版新增全新的可查找性標準。"
+msgstr "2022年9月7日：🔭第十一版草稿新增可查找性準則。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduce new criterion: Make the codebase findable."
-msgstr "推出新標準：使代碼庫變得容易查找。"
+msgstr "導入新準則：代碼庫可查詢得到。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Improve How to test section for most criteria."
-msgstr "改善多數標準的「測試方式」章節。"
+msgstr "改善多數準則的「測試方式」小節。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "New requirement in Welcome contributors about publishing activity "
 "statistics."
-msgstr "「歡迎貢獻者」章節中有關發佈活動統計的新規定。"
+msgstr "在〈歡迎貢獻者〉中加入發布活動統計的新規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Removed redundant requirement about portable and reusable code."
-msgstr "已移除有關可移植與可重複使用的程式碼的多餘規定。"
+msgstr "移除可重複使用與移植的程式碼中多餘的規定。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expand open license definition to include both OSI and FSF approved "
 "licenses."
-msgstr "在開放授權的定義中，加入 OSI 與 FSF 認證的授權。"
+msgstr "在開放授權的定義中，納入 OSI 與 FSF 所批准的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr "重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定更明確。"
+msgstr "重新編寫「得以 (MAY)」等級的相關規定，加入使用「可選擇 "
+"(OPTIONAL)」這個關鍵字，讓規定更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "已表明 The Standard for Public Code 標準在適用時應該符合自身規定，且已新增評估。"
+msgstr "表明 Standard for Public Code "
+"應該盡可能符合其自身規定的立場，並且加入評估措施。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
-msgstr "將 SPDC license identifier 加入檔案中。"
+msgstr "將 SPDX 授權識別碼加入檔案中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduced new Code of Conduct."
-msgstr "已推出新行為守則。"
+msgstr "導入新的行為守則。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify distinction between source code and policy text."
@@ -551,31 +553,31 @@ msgstr "解釋原始碼與政策內文的差異。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Restructuring of requirements with bullet point lists."
-msgstr "將規定改為要點清單的格式。"
+msgstr "將規定重新調整為項目要點清單格式。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Acknowledge the importance of codebase modularity for reuse."
-msgstr "承認代碼庫成熟度在重複使用上的重要性。"
+msgstr "告知代碼庫成熟度對於重複使用時的重要性。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Move requirements related to Findability to the new criterion."
-msgstr "將可查找性相關規定移動到新標準。"
+msgstr "將可查找性相關規定移動到新準則中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify the role of non-open standards when used in a codebase."
-msgstr "釐清非開放性標準在代碼庫中的角色。"
+msgstr "釐清非開放標準在代碼庫中的角色。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Additional guidance about build-time and runtime dependencies."
-msgstr "關於建制時期與執行階段相依性的額外指南。"
+msgstr "加入建置時期與執行時期依賴項目的額外指引。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
-msgstr "新增 The Standard for Public Code 開發路徑圖。"
+msgstr "新增 Standard for Public Code 的發展路線圖。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Update structure of Authors file."
-msgstr "更新作者檔案結構。"
+msgstr "更新 Authors 檔案的結構。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add Audrey Tang to Authors."
@@ -583,13 +585,13 @@ msgstr "將唐鳳加入作者群。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added a list of criteria to the print edition."
-msgstr "已新增標準清單到印刷版本中。"
+msgstr "將準則列表加到印刷版本中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Clarify what the standard means with policymakers, managers, developers and "
 "designers."
-msgstr "釐清標準對政策制定者、管理者、開發人員與設計師的意義。"
+msgstr "釐清標準對於政策制定者、管理人員、開發人員與設計師等不同身分間的意義。"
 
 #: ./CHANGELOG.md:block 20 (header)
 msgid "Version 0.3.0"
@@ -598,32 +600,33 @@ msgstr "0.3.0 版"
 #: ./CHANGELOG.md:block 21 (paragraph)
 msgid ""
 "May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
-msgstr "2022年5月23日：🗎第十版加強註解與本土化。"
+msgstr "2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內容。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Requirement for localization made explicit in Create reusable and portable "
 "code."
-msgstr "「編寫可重複使用與可移植程式碼」章節有明確的本土化規定。"
+msgstr "在〈編寫可重複使用與移植的程式碼〉中定下明確的在地化規定。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
-msgstr "治理註解從「應該（Should）」變成「必須（Must）」。"
+msgstr "以文件記錄治理方式的規定，從「應該 (SHOULD)」等級調升為「必須 (MUST)」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
-msgstr "在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必須紀錄貢獻的期望，專注在單一議題上。"
+msgstr "在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容必須（MUST）小」的規定，改"
+"為必須紀錄貢獻所要完成的期望，並一次專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
-msgstr "社群翻譯現在已連結到頁尾中。"
+msgstr "社群翻譯連結現在已放到頁尾中。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
-msgstr "還原「用 Mermaid 流程圖取代 BPMN svg」。"
+msgstr "還原「用 Mermaid 流程圖取代業務流程 BPMN svg」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Many minor clarifications to language and sentences made more simple."
@@ -637,44 +640,47 @@ msgstr "0.2.3 版"
 msgid ""
 "March 15th 2022: 📜 the ninth draft allows English summaries for policy "
 "lacking an official translation."
-msgstr "2022年3月15日：📜第九版允許在沒有官方翻譯的政策中加入英文版摘要。"
+msgstr "2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策改為提供政策的英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Relax the criterion Use plain English by adding a new requirement allows "
 "bundled policy not available in English to have an accompanying summary in "
 "English instead of translating the full text."
-msgstr "放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入英文版摘要，不用翻譯全文。"
+msgstr "放寬「使用白話英文」的準則，加入新規定，允許合捆的政策內文如果沒有英文版，只"
+"需要加入英文版摘要，而不用翻譯全文。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Similarly, allow for English summaries for policies not available in English"
 " in Bundle policy and code."
-msgstr "同樣地，允許同捆政策與程式碼當中沒有英文版的政策只提供英文版摘要。"
+msgstr "同樣地，在〈政策與程式碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要"
+"。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Clarify that term 'policy' includes processes which impact development and "
 "deployment in Bundle policy and code."
-msgstr "釐清「政策」包括能影響同捆政策與程式碼開發與部署的流程。"
+msgstr "釐清〈政策與原始碼要合捆〉中，「政策」包含能影響開發與部署的流程。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Emphasize reusability also on parts of the solutions in Create reusable and "
 "portable code."
-msgstr "強調「編寫可重複使用與移植的程式碼」解決方案部分內容的可重複使用性。"
+msgstr "在〈編寫可重複使用與移植的程式碼〉中強調解決方案部分內容的可重複使用性。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Expand guidance to Developers and designers in Create reusable and portable "
 "code about deploying to proprietary platforms."
-msgstr "將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到不同專屬平台的內容。"
+msgstr "將〈編寫可重複使用與移植的程式碼〉當中的開發人員與設計師指引，加入部署到專有"
+"平台上的內容。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Add nuance to use of non-English terms in what management need to do in Use "
 "plain English."
-msgstr "在「使用簡單英文」中，加入管理人員需要使用的非英文詞彙。"
+msgstr "在〈使用白話的英文〉中，加入管理層在面對非英語詞彙時需要做的事的提點。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -682,9 +688,9 @@ msgid ""
 "make [community translations](https://github.com/publiccodenet/community-"
 "translations-standard) easier."
 msgstr ""
-"變更拉取請求流程圖，從 BPMN 改用 "
-"Mermaid，讓[社群翻譯](https://github.com/publiccodenet/community-translations-"
-"standard)更容易。"
+"變更拉取請求流程圖，從業務流程 BPMN 改用 "
+"Mermaid，來讓[社群翻譯](https://github.com/publiccodenet/community-"
+"translations-standard)更容易。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added Maurice Hendriks to AUTHORS."
@@ -692,11 +698,11 @@ msgstr "將 Maurice Hendriks 加入作者群。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Added OpenApi Specification to further reading."
-msgstr "將「OpenApi 規格」加入「深入閱讀」。"
+msgstr "將「OpenApi 規格」加入延伸閱讀。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid "Made the attributions in further reading sections clearer."
-msgstr "將「深入閱讀」當中的歸因變得更明確。"
+msgstr "將延伸閱讀小節的特性變得更明確。"
 
 #: ./CHANGELOG.md:block 26 (header)
 msgid "Version 0.2.2"
@@ -706,61 +712,62 @@ msgstr "0.2.2 版"
 msgid ""
 "November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
 " as code may not be in English."
-msgstr "2021年11月29日：🏛第八版承認當作程式碼來執行的政策，不一定是英文。"
+msgstr "2021年11月29日：🏛第八版草稿認知程式碼所執行的政策，不一定是英文。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Document exception to \"All code MUST be in English\" where policy is "
 "interpreted as code."
-msgstr "標示當政策被詮釋為程式碼時，則不用遵守「僅限英文程式碼」的規則。"
+msgstr "在「所有程式碼都必須以英文編寫」的規定中，雖然政策也視為一種 "
+"code，可以有例外。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Add MAY requirement regarding committer email addresses in Maintain version "
 "control."
-msgstr "在「版本管控」中，新增關於提交者電子郵件的「得以（May）」規定。"
+msgstr "在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以 (MAY)」規定。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Policy Makers in Bundle policy and code."
-msgstr "將政策制定者加入「同捆政策與程式碼」指南。"
+msgstr "將政策制定者加入〈政策與原始碼要合捆〉指引中。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Developers and designers in Use a coherent style."
-msgstr "將開發人員與設計師加入「風格一致」指南。"
+msgstr "將開發人員與設計師加入「風格要前後一致」指引中。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add \"Different contexts\" to glossary."
-msgstr "新增「不同脈絡」到詞彙表中。"
+msgstr "新增「不同情境」到詞彙表中。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
-msgstr "將 Mauko Quiroga 與 Charlotte Heikendorf 加入作者群。"
+msgstr "將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Digital Public Goods approval badge."
-msgstr "新增「數位公共財」認證標章。"
+msgstr "新增「數位公共財」核可徽章。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
-msgstr "加入網頁版「標準」頁面的「上一頁」與「下一頁」連結。"
+msgstr "為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Open Standards principles to further reading."
-msgstr "將「開放標準原則」加入「深入閱讀」。"
+msgstr "將「開放標準」原則加入延伸閱讀。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Definition of plain language to further reading."
-msgstr "將「簡單語言定義」加入「深入閱讀」。"
+msgstr "將「白話語言定義」加入延伸閱讀。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Move the Semantic Versioning Specification further reading reference."
-msgstr "移動「語意化版本規格」引用的「深入閱讀」。"
+msgstr "將「語意化版本控制規範」移動為延伸閱讀參考內容。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Clarify that publiccode.yml is one example of a machine-readable metadata "
 "description."
-msgstr "釐清 publiccode.yml 是描述機讀元資料的名稱之一。"
+msgstr "指出 publiccode.yml 是機器可讀中介資料說明的範例之一。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
@@ -768,7 +775,7 @@ msgstr "將「您的代碼庫」與「貴組織」改為較不具有所有格的
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add instructions for creating a print version."
-msgstr "新增印刷版的建立說明。"
+msgstr "新增印刷版的製作指示。"
 
 #: ./CHANGELOG.md:block 29 (header)
 msgid "Version 0.2.1"
@@ -778,32 +785,32 @@ msgstr "0.2.1 版"
 msgid ""
 "March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
 "0.2.0."
-msgstr "2021年3月1日：🧽跟 0.2.0 版相較之下，第七版做了些微改善。"
+msgstr "2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改善。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "New SHOULD requirement on using a distributed version control system and why"
 " distributed is important."
-msgstr "針對使用分散版本控制系統制定新的「應該」規定，並解釋分散的重要性。"
+msgstr "新增使用分散式版本控制系統的相關「應該 (SHOULD)」規定，並解釋分散式的重要性。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "Feedback requirements for rejected contributions are more strict than "
 "accepted ones."
-msgstr "針對被拒絕的貢獻的回饋，比被接受的貢獻的回饋規定更嚴苛。"
+msgstr "針對未被採用的貢獻需要給予回饋，規定要比被接受的貢獻更加嚴格。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
 "Specify that copyright and license notices should also be machine-readable."
-msgstr "明確指出著作權與授權聲明也應該要可機讀。"
+msgstr "明確指出著作權與授權聲明也應該要機器可讀。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Advice on how to test that notices be machine-readable."
-msgstr "聲明是否為可機讀的測試方式建議。"
+msgstr "聲明是否為機器可讀的測試方式建議。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Clarify guidance for rolling releases."
-msgstr "釐清滾動發行的指南。"
+msgstr "釐清滾動發行的指引。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Clear up definition of version control in glossary."
@@ -813,15 +820,15 @@ msgstr "釐清詞彙表中「版本控制」的定義。"
 msgid ""
 "Add further reading encouraging contribution, SPDX, Git and reviewing "
 "contributions."
-msgstr "新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git 以及審查貢獻。"
+msgstr "新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項目。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add links to videos about the concept of public code."
-msgstr "新增有關公共程式概念的影片連結。"
+msgstr "新增有關公共程式公開代碼概念的影片連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Update BPMN link."
-msgstr "更新 BPMN 連結。"
+msgstr "更新業務流程 BPMN 連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Reduce link duplication."
@@ -838,55 +845,55 @@ msgstr "0.2.0 版"
 #: ./CHANGELOG.md:block 33 (paragraph)
 msgid ""
 "October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
-msgstr "2020年10月26日：🎊第六版分拆一項規定並且釐清內容。"
+msgstr "2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
 "and \"Welcome contributors\"."
-msgstr "將「歡迎貢獻」標準分拆為「讓貢獻更容易」以及「歡迎貢獻者」。"
+msgstr "將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Rename criterion \"Pay attention to codebase maturity\" to \"Document "
 "codebase maturity\"."
-msgstr "將「注意代碼庫成熟度」標準改名為「註解代碼庫成熟度」。"
+msgstr "將〈注意代碼庫成熟度〉準則改名為〈記錄代碼庫成熟度〉。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
-msgstr "針對多方使用的代碼庫，將「必須（Must）」規定調整為「應該（Should）」規定。"
+msgstr "針對多方使用的代碼庫，將「必須 (MUST)」等級規定調降為「應該 (SHOULD)」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
-msgstr "針對著作權讓與，新增「不得（Must Not）」規定。"
+msgstr "針對著作權轉讓，新增「不得 (MUST NOT)」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
-msgstr "在可重複使用程式碼規定中，釐清組態的角色。"
+msgstr "在可重複使用程式碼的規定中，釐清組態設定的角色。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Glossary additions: continuous integration, policy, repository, and version "
 "control."
-msgstr "新增詞彙：持續整合、政策、儲存庫與版本控制。"
+msgstr "新增詞彙：持續整合、政策、儲存庫、版本控制等。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Replace references to 'cities' with 'public organizations'."
-msgstr "將「城市」都替換成「公共組織」。"
+msgstr "將「城市」替換成「公共組織」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Clarify aspects of sensitive code by separating contributor and reviewer "
 "requirements into separate items."
-msgstr "將貢獻者與審查規定分開，藉此釐清程式碼敏感的地方。"
+msgstr "將貢獻者與審查人員規定分開為不同項目，以釐清程式碼中較敏感性的層面。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Expand further reading, and guidance to policy makers, developers and "
 "designers."
-msgstr "將政策制定者、開發人員與設計師加入「深入閱讀」與指南中。"
+msgstr "將政策制定者、開發人員與設計師加入延伸閱讀與指引中。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add Felix Faassen and Arnout Engelen to authors."
@@ -900,11 +907,11 @@ msgstr "0.1.4 版"
 msgid ""
 "November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
 "fixes."
-msgstr "2019年11月27日：🧹第五版主要內容是額外的細部修復。"
+msgstr "2019年11月27日：🧹第五版草稿主要是一些細部修正。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Linked License.md file."
-msgstr "已連結 License.md 檔案。"
+msgstr "連結 License.md 檔案。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
@@ -912,7 +919,7 @@ msgstr "將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Made punctuation more consistent, especially for bullet lists."
-msgstr "讓標點符號更連貫，特別是項目符號列表。"
+msgstr "讓標點符號使用更一致，特別是項目符號列表。"
 
 #: ./CHANGELOG.md:block 37 (unordered list)
 msgid "Made some minor changes to text for clarity."
@@ -926,7 +933,7 @@ msgstr "0.1.3 版"
 msgid ""
 "October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
 " the autumn cleaning"
-msgstr "2019年10月8日：🍂第四版僅針對秋季的清理修復小問題"
+msgstr "2019年10月8日：🍂第四版草稿僅針對秋季所作的清理修正一些小地方"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "Renamed continuous delivery to continuous integration."
@@ -934,11 +941,11 @@ msgstr "將「持續交付」改名為「持續整合」。"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "Referencing accessibility guidelines in the language standard."
-msgstr "在語言標準中引述無障礙指導原則。"
+msgstr "在語言標準中引用無障礙指導原則。"
 
 #: ./CHANGELOG.md:block 40 (unordered list)
 msgid "A bunch of style and consistency fixes."
-msgstr "改善樣式與一致性。"
+msgstr "改善一些樣式，與一致性修正。"
 
 #: ./CHANGELOG.md:block 41 (header)
 msgid "Version 0.1.2"
@@ -948,11 +955,11 @@ msgstr "0.1.2 版"
 msgid ""
 "August 22th 2019: 🌠 the third draft focuses on better text and takes "
 "community input"
-msgstr "2019年8月22日：🌠第三版專注在提升文字品質，並且傾聽社群的意見"
+msgstr "2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "With some great new contributors comes a fresh author list."
-msgstr "一群很棒的貢獻者，讓我們作者群加入許多新血。"
+msgstr "好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "All links are now HTTPS."
@@ -960,35 +967,35 @@ msgstr "所有連結都是 HTTPS。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "General proofreading, wording clarifications, and smashed typos."
-msgstr "一般校對、釐清用字與修改拼字錯誤。"
+msgstr "一般校對、釐清用字淺詞、修正拼字錯誤等。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Updated criteria:"
-msgstr "已更新標準："
+msgstr "更新準則："
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Requirement for reuse in different contexts"
-msgstr "在不同脈絡下重複使用的規定"
+msgstr "在不同情境背景下重複使用的規定"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for explicit versioning"
-msgstr "明確版本控制建議"
+msgstr "明確的版本控制建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for multi party development"
-msgstr "多方部署建議"
+msgstr "多方部署的建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for license headers in files"
-msgstr "檔案授權標頭建議"
+msgstr "檔案授權標頭的建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for vulnerability reporting"
-msgstr "漏洞回報建議"
+msgstr "漏洞回報的建議"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "Recommendation for explicit documentation of governance"
-msgstr "明確治理註解建議"
+msgstr "明確以文件記錄治理方式的建議"
 
 #: ./CHANGELOG.md:block 44 (header)
 msgid "Version 0.1.1"
@@ -998,25 +1005,26 @@ msgstr "0.1.1 版"
 msgid ""
 "May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
 "lot of typos"
-msgstr "2019年5月9日：🤔第二版修復基本的疏忽以及許多拼字錯誤"
+msgstr "2019年5月9日：🤔第二版草稿修正一些基本的疏漏，以及許多拼字錯誤"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid ""
 "Removed references to the Foundation for Public Code, we're going to have to"
 " change the name in becoming an association."
-msgstr "移除出現「The Foundation for Public Code」的地方，我們必須改名才能成為協會。"
+msgstr "移除出現「Foundation for Public "
+"Code」的地方，我們之後可能必須改名才能成為協會。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the introduction."
-msgstr "已更新前言。"
+msgstr "更新簡介。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Updated the glossary."
-msgstr "已更新詞彙表。"
+msgstr "更新詞彙表。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "Added the code of conduct."
-msgstr "已新增行為守則。"
+msgstr "新增行為守則。"
 
 #: ./CHANGELOG.md:block 46 (unordered list)
 msgid "We've recommended using the publiccode.yml standard for easier reuse."
@@ -1030,17 +1038,18 @@ msgstr "0.1.0 版"
 msgid ""
 "April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
 "snazzy new ideas in it"
-msgstr "2019年4月16日：🎉初版已經就緒，內容全新且有許多有趣的全新構想"
+msgstr "2019年4月16日：🎉初版草稿已準備就緒，全新內容，而且有許多有趣的新穎理念"
 
 #: ./CHANGELOG.md:block 49 (unordered list)
 msgid "14 criteria with their requirements and how to operationalize them."
-msgstr "14個標準、其規定以及實施方式。"
+msgstr "14 項準則，有各自的規定，以及相關的實施方式。"
 
 #: ./CHANGELOG.md:block 49 (unordered list)
 msgid ""
 "An introduction with a high level background, what this standard is, and how"
 " the Foundation for Public Code will use it."
-msgstr "清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code 會如何使用此標準。"
+msgstr "精要的背景介紹，例如本標準是什麼，以及 Foundation for Public Code "
+"如何使用此標準。"
 
 #: ./CHANGELOG.md:block 50 (paragraph)
 msgid ""
@@ -1048,8 +1057,9 @@ msgid ""
 "Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
 "Public Code! project](https://smartcities.publiccode.net/)."
 msgstr ""
-"第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於[Smart Cities? Public Code! "
-"專案](https://smartcities.publiccode.net/)。"
+"最初的版本是由阿姆斯特丹應用科學大學、阿姆斯特丹市政府，以及本基金會合作撰寫"
+"，取自 [Smart Cities? Public Code! 專案](https://smartcities.publiccode.net/)"
+" 的部分內容。"
 
 #: ./CODE_OF_CONDUCT.md:block 1 (header)
 msgid "Code of Conduct"
@@ -1499,9 +1509,11 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
-"將 The Standard for Public Code "
-"套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指南](https://publiccodenet.github.io/community-"
-"implementation-guide-standard/)，當中包括範例與其他訣竅。"
+"將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。"
+"若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與"
+"您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指引](https://publiccode"
+"net.github.io/community-implementation-guide-standard/"
+")，當中包括範例與其他訣竅。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
@@ -1594,7 +1606,10 @@ msgid ""
 " described how we govern the standard in the [governance "
 "statement](GOVERNANCE.md)."
 msgstr ""
-"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及協助開發。😊若要開始，請先參閱我們的[貢獻者指南](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE.md)提到我們管理該標準的方式。"
+"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及"
+"協助開發。😊若要開始，請先參閱我們的[貢獻者指引](CONTRIBUTING.md)。由於這是相"
+"當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE."
+"md)提到我們管理該標準的方式。"
 
 #: ./README.md:block 21 (paragraph)
 msgid ""
@@ -1690,8 +1705,9 @@ msgid ""
 "it. If you contribute you also grant these rights to others. You can read "
 "more about how to help in the [contributing guide](CONTRIBUTING.md)."
 msgstr ""
-"The Standard for Public Code 採用 CC 0 "
-"[授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。"
+"The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解"
+"與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權"
+"利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
 msgid "order: 2 redirect_from:"
@@ -1746,7 +1762,7 @@ msgstr "若一個政策以原始碼為基礎，該原始碼「必須（Must）
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr "政策格式「應該（Should）」可以機讀且明確。"
+msgstr "政策格式「應該」機器可讀且明確。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
@@ -1811,7 +1827,8 @@ msgid ""
 "Document policy in formats that are unambiguous and machine-readable, such "
 "as those published by the [Object Management "
 "Group](https://www.omg.org/spec/)."
-msgstr "用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/)發佈的格式）來紀錄政策。"
+msgstr "用明確且機器可讀的格式（像是[對象管理組織](https://www.omg.org/spec/"
+")發佈的格式）來紀錄政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1892,7 +1909,8 @@ msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
-"Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。"
+"Trisotech的[BPMN快速指引](https://www.bpmnquickguide.com/"
+"view-bpmn-quick-guide/)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
@@ -2446,7 +2464,7 @@ msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
+msgstr "Write the Docs《[文件指引](https://www.writethedocs.org/guide/)》。"
 
 #: ./criteria/index.md:block 3 (header)
 msgid "order: 0"
@@ -2570,7 +2588,7 @@ msgstr "檢查版本控制系統是否為分散式。"
 msgid ""
 "Review the commit history, check if grouping of relevant changes in "
 "accordance with the contributing guidelines."
-msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。"
+msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
@@ -3406,7 +3424,8 @@ msgid ""
 "Confirm that contribution guidelines and "
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
-msgstr "確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
+msgstr "確認貢獻指引中，以及[儲存庫](../glossary."
+"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
@@ -3733,7 +3752,8 @@ msgid ""
 "guide, either the codebase community's own or an existing one referred to in"
 " the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既有風格。"
+"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指引、或文件寫作風格指"
+"引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用的既有風格。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
@@ -3743,19 +3763,19 @@ msgstr "貢獻內容應該通過自動化的風格測試。"
 msgid ""
 "The style guide SHOULD include expectations for inline comments and "
 "documentation for non-trivial sections."
-msgstr "風格指南應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。"
+msgstr "風格指引應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
 "Including expectations for [understandable English](use-plain-english.md) in"
 " the style guide is OPTIONAL."
-msgstr "可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指南之中。"
+msgstr "可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指引之中。"
 
 #: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
 msgid ""
 "Confirm that contributions are in line with the style guides specified in "
 "the documentation."
-msgstr "確認貢獻內容有遵循文件中指定的風格指南。"
+msgstr "確認貢獻內容有遵循文件中指定的風格指引。"
 
 #: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
 msgid "Check for the presence of automated tests on style."
@@ -3767,7 +3787,8 @@ msgid ""
 "[policy](../glossary.md#policy) and documentation as well as document this "
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
-"為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
+"為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄"
+"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
 
 #: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
 msgid ""
@@ -3788,8 +3809,12 @@ msgid ""
 "documentation. Continually improve upon and expand this documentation with "
 "the aim of evolving this documentation into engineering guidelines."
 msgstr ""
-"如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查的其他層面。指南應該包含貢獻的[原始碼](../glossary.md#source-"
-"code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。"
+"如果代碼庫還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md#r"
+"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
+"前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
+"以及機器不容易檢查的其他層面。指引應該包含貢獻的[原始碼](../glossary.md"
+"#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試"
+"、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
 
 #: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
 msgid "Additionally:"
@@ -4181,7 +4206,7 @@ msgstr "criteria/understandable-english-first"
 
 #: ./criteria/use-plain-english.md:block 5 (header)
 msgid "Use plain English"
-msgstr "使用白話的英語"
+msgstr "使用白話的英文"
 
 #: ./criteria/use-plain-english.md:block 6 (paragraph)
 msgid ""
@@ -4240,8 +4265,8 @@ msgid ""
 "recommended by the [Web Content Accessibility Guidelines "
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
-"根據《[網頁內容近用性無障礙指南 "
-"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
+"根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4316,8 +4341,9 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
 "readable and understandable."
 msgstr ""
-"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 "
-"之可讀性](https://www.w3.org/TR/WCAG21/#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
+"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1 與 3.1 "
+"之可讀性](https://www.w3.org/TR/WCAG21/"
+"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4500,7 +4526,8 @@ msgstr "清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式
 msgid ""
 "[Building welcoming communities](https://opensource.guide/building-"
 "community/) by Open Source Guides."
-msgstr "開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。"
+msgstr "開放原始碼指引所提供的《[營造友善的社群](https://opensource.guide/"
+"building-community/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4518,9 +4545,9 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
-"開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-"
-"source)社群專案所寫的《[領導與治理](https://opensource.guide/leadership-and-"
-"governance/)》。"
+"開放原始碼指引為成長中的[開放原始碼](../glossary.md#open-"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
+"leadership-and-governance/)》。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4538,8 +4565,8 @@ msgid ""
 "tries to provide the relevant information to print it there or somewhere "
 "else."
 msgstr ""
-"The Standard for Public Code 由 Reclameland 負責印刷。本指南提供印刷相關資訊，方便在 Reclameland "
-"或其他地方印刷。"
+"The Standard for Public Code 由 Reclameland "
+"負責印刷。本指引提供印刷相關資訊，方便在 Reclameland 或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
@@ -5643,7 +5670,7 @@ msgstr "目次"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
-msgstr "[讀者指南：如何詮釋此標準](readers-guide.md)"
+msgstr "[讀者指引：如何詮釋此標準](readers-guide.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Glossary](glossary.md)"
@@ -5743,7 +5770,7 @@ msgstr ""
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
-msgstr "讀者指南"
+msgstr "讀者指引"
 
 #: ./readers-guide.md:block 4 (paragraph)
 msgid ""

From e4885fef72bb868587430dd115b05a58f51a205f Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Mon, 4 Sep 2023 09:31:03 +0000
Subject: [PATCH 46/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 338 ++++++++++++++----------
 1 file changed, 193 insertions(+), 145 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 1723f298..c8a42de5 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-04 09:27+0000\n"
+"PO-Revision-Date: 2023-09-06 16:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -354,7 +354,7 @@ msgstr "改善網頁版的導覽功能。"
 msgid ""
 "Moved tools in Further reading sections to the community implementation "
 "guide."
-msgstr "已將「延伸閱讀」小節的工具移到社群實作指引。"
+msgstr "已將「延伸閱讀」小節的工具移到社群實踐指引。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -491,7 +491,7 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
-"將範例移動到[社群實作指引](https://publiccodenet.github.io/"
+"將範例移動到[社群實踐指引](https://publiccodenet.github.io/"
 "community-implementation-guide-standard/)。"
 
 #: ./CHANGELOG.md:block 17 (header)
@@ -824,7 +824,7 @@ msgstr "新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Add links to videos about the concept of public code."
-msgstr "新增有關公共程式公開代碼概念的影片連結。"
+msgstr "新增有關公共程式概念的影片連結。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid "Update BPMN link."
@@ -867,7 +867,7 @@ msgstr "針對多方使用的代碼庫，將「必須 (MUST)」等級規定調
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
-msgstr "針對著作權轉讓，新增「不得 (MUST NOT)」規定。"
+msgstr "針對著作權轉讓，新增「禁止 (MUST NOT)」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
@@ -1071,27 +1071,29 @@ msgid ""
 "behavioral codes yet some individuals are not. This document expresses "
 "expectations of all community members and all interactions regardless of "
 "communication channel."
-msgstr "社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基金會對所有社群成員以及互動的期望，不論透過何種溝通管道。"
+msgstr ""
+"社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達"
+"基金會對於所有社群成員，以及所有互動間的期望，不論透過何種溝通管道。"
 
 #: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
 msgid "Be here to collaborate."
-msgstr "到這裡來是為了協作。"
+msgstr "來到這裡來是為了協作。"
 
 #: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
 msgid "Be considerate, respectful, and patient."
-msgstr "對彼此體貼、尊重以及有耐心。"
+msgstr "請對彼此體貼、尊重，以及有耐心。"
 
 #: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
 msgid "Strive to be as constructive as possible."
-msgstr "努力做出建設性的貢獻。"
+msgstr "努力做出有建設性的行為。"
 
 #: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
 msgid "To raise a concern, please email directors@publiccode.net."
-msgstr "若有問題，請寄送電子郵件到 directors@publiccode.net。"
+msgstr "若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。"
 
 #: ./CONTRIBUTING.md:block 1 (header)
 msgid "Contributing to this standard"
-msgstr "貢獻給此標準"
+msgstr "貢獻此標準"
 
 #: ./CONTRIBUTING.md:block 3 (paragraph)
 msgid "🙇‍♀️ Thank you for contributing!"
@@ -1104,7 +1106,9 @@ msgid ""
 "possible. Thus we appreciate your input, enjoy feedback and welcome "
 "improvements to this project and are very open to collaboration."
 msgstr ""
-"我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。"
+"我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士"
+"協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專"
+"案的建議，我們非常開放任何合作的機會。"
 
 #: ./CONTRIBUTING.md:block 5 (paragraph)
 msgid ""
@@ -1112,12 +1116,13 @@ msgid ""
 "with GitHub, you can email use your feedback at "
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
-"我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，歡迎將意見用電子郵件傳送到 "
-"[info@publiccode.net](mailto:info@publiccode.net)。"
+"我們歡迎每個人提出的議題，以及拉入請求。如果您不大習慣 GitHub ，"
+"也歡迎將意見回饋用電子郵件計送到 [info@publiccode.net](mailto:info@publiccode"
+".net)。"
 
 #: ./CONTRIBUTING.md:block 6 (header)
 msgid "Problems, suggestions and questions in issues"
-msgstr "問題、建議與議題中的問題"
+msgstr "問題、建議與議題等"
 
 #: ./CONTRIBUTING.md:block 7 (paragraph)
 msgid ""
@@ -1129,11 +1134,11 @@ msgid ""
 "Issues for the Standard for Public "
 "Code](https://github.com/publiccodenet/standard/issues)."
 msgstr ""
-"[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以及發問，幫助推動本開發案。您可以到[GitHub "
-"的The Standard for Public Code "
-"議題](https://github.com/publiccodenet/standard/issues)頁面中，為此專案[在 GitHub "
-"上建立議題](https://docs.github.com/en/issues/tracking-your-work-with-"
-"issues/creating-an-issue)。"
+"[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議"
+"修改，以及發問等，來協助發展。您可以到 [Standard for Public Code 的 GitHub "
+"Issue](https://github.com/publiccodenet/standard/issues) 頁面中，為本專案["
+"提出 GitHub 議題](https://docs.github.com/en/issues/"
+"tracking-your-work-with-issues/creating-an-issue)。"
 
 #: ./CONTRIBUTING.md:block 8 (paragraph)
 msgid ""
@@ -1142,23 +1147,25 @@ msgid ""
 " and send an email to "
 "[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
 msgstr ""
-"或者加入[郵寄清單](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)並且傳送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。"
+"或者，註冊加入[郵遞論壇清單](https://lists.publiccode.net/mailman/postorius/"
+"lists/standard.lists.publiccode.net/)，並寄送電子郵件到[standard@lists."
+"publiccode.net](mailto:standard@lists.publiccode.net)。"
 
 #: ./CONTRIBUTING.md:block 9 (paragraph)
 msgid ""
 "You don't need to change any of our code or documentation to be a "
 "contributor!"
-msgstr "不需要修改我們的程式碼或註解也能成為貢獻者！"
+msgstr "您不一定要修改我們的程式碼或文件，也能成為貢獻者！"
 
 #: ./CONTRIBUTING.md:block 10 (header)
 msgid "Documentation and code in pull requests"
-msgstr "拉入請求中的註解與程式碼"
+msgstr "為文件記錄與程式碼提出拉入請求"
 
 #: ./CONTRIBUTING.md:block 11 (paragraph)
 msgid ""
 "If you want to add to the documentation or code of one of our projects you "
 "should make a pull request."
-msgstr "如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出拉入請求。"
+msgstr "如果您想要在我們的專案中，為文件紀錄或程式碼加入新內容，您應該提出拉入請求。"
 
 #: ./CONTRIBUTING.md:block 12 (paragraph)
 msgid ""
@@ -1168,10 +1175,11 @@ msgid ""
 "Skills](https://skills.github.com/) on working with GitHub and working with "
 "MarkDown, the syntax this project's documentation is in."
 msgstr ""
-"若您從未使用過 GitHub，歡迎先[認識 GitHub flow](https://docs.github.com/en/get-"
-"started/quickstart/github-flow)，或是參加[GitHub "
-"Skills](https://skills.github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 "
-"MarkDown（本專案註解所使用的語法）。"
+"若您從未使用過 GitHub，歡迎先[認識 GitHub 作業流程](https://docs.github.com/"
+"en/get-started/quickstart/github-flow)，或是參加 [GitHub "
+"Skills](https://skills.github.com/) 免費且優質的互動式課程，"
+"當中會介紹該如何使用 GitHub 以及 MarkDown 語法。MarkDown "
+"是本專案文件所採用的撰寫語法。"
 
 #: ./CONTRIBUTING.md:block 13 (paragraph)
 msgid ""
@@ -1180,11 +1188,13 @@ msgid ""
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
 msgstr ""
-"本專案獲得 Creative CC Zero v1.0 Universal 授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。"
+"本專案採用創用CC 0 1.0 通用，公眾領域貢獻宣告給予授權；這本質上代表本專案，以"
+"及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可"
+"以任意使用。"
 
 #: ./CONTRIBUTING.md:block 14 (header)
 msgid "1. Make your changes"
-msgstr "1. 作出變更"
+msgstr "1. 作出您的修改"
 
 #: ./CONTRIBUTING.md:block 15 (paragraph)
 msgid ""
@@ -1196,9 +1206,10 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
-"貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public Code "
-"當中列出的標準。審查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-"
-"code)。此外，他們也會審查貢獻是否符合[標準](#standards-to-follow)且與整體專案有連貫。"
+"貢獻內容應該[遵守](docs/standard-for-public-code.html) Standard for Public "
+"Code 自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值]"
+"(foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標準"
+"](#standards-to-follow)，且與整體作品有所連貫。"
 
 #: ./CONTRIBUTING.md:block 16 (paragraph)
 msgid ""
@@ -1207,8 +1218,9 @@ msgid ""
 "you've forked this repository, please make sure to create a feature branch "
 "following the GitFlow model."
 msgstr ""
-"本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-"
-"model/)。當您複製了此存放庫，請務必依照 GitFlow 模型建立功能分支。"
+"本專案使用 [GitFlow 分支與工作流程](https://nvie.com/posts/"
+"a-successful-git-branching-model/)。當您對此儲存庫作分支以後，請務必依照 "
+"GitFlow 模型建立新功能分支。"
 
 #: ./CONTRIBUTING.md:block 17 (paragraph)
 msgid ""
@@ -1222,16 +1234,20 @@ msgid ""
 "commit message, this will enable everyone to be informed of your choices in "
 "the future."
 msgstr ""
-"將您變更內容加入到提交版本[並且附上說明](https://robots.thoughtbot.com/5-useful-tips-for-a-"
-"better-commit-"
-"message)。如果需要不只一種變更，將相關變更分類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格式。像是「svg」格式就勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選擇。"
+"將您所作的變更內容加入送交版次，[並附上內容說明](https://robots.thoughtbot."
+"com/5-useful-tips-for-a-better-commit-message)。如果需要作出多種類型的變更，"
+"請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如，修正空白，"
+"以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用容易以「`"
+"diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，"
+"請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉擇。"
 
 #: ./CONTRIBUTING.md:block 18 (paragraph)
 msgid ""
 "If you are adding code, make sure you've added and updated the relevant "
 "documentation and tests before you submit your pull request. Make sure to "
 "write tests that show the behavior of the newly added or changed code."
-msgstr "如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請務必用文字描述新增或修改後的程式碼的作用。"
+msgstr "如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的"
+"拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。"
 
 #: ./CONTRIBUTING.md:block 19 (header)
 msgid "Applicable policy"
@@ -1241,7 +1257,7 @@ msgstr "適用政策"
 msgid ""
 "Currently, the Standard for Public Code is not implementing any specific "
 "public policy."
-msgstr "The Standard for Public Code 目前沒有執行任何特定的公共政策。"
+msgstr "就目前而言，Standard for Public Code 並非在執行任何特定的公共政策。"
 
 #: ./CONTRIBUTING.md:block 21 (header)
 msgid "Style"
@@ -1258,8 +1274,11 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
-"The Standard for Public Code 目標是[使用白話的英語](criteria/use-plain-"
-"english.md)，拼字採用美式英文。文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修正這一部分，也會另外再次檢查品質才[推出新版本](docs/releasing.md)。"
+"Standard for Public Code 目標[使用白話的英語](criteria/use-plain-english.md)"
+"，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有繞圖換行，來讓「`di"
+"ff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而"
+"不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才["
+"推出新發行版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1270,19 +1289,21 @@ msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr "這些是 The Standard for Public Code 所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。"
+msgstr "這些是 Standard for Public Code "
+"所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
 "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
 " keywords"
-msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 必要層級關鍵字"
+msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 要求等級關鍵字"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
 "[Web Content Accessibility Guidelines "
 "2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
-msgstr "[網頁無障礙性指導原則 2.1](https://www.w3.org/TR/WCAG21/#readable) - 可讀性"
+msgstr "[網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/#readable) - "
+"易讀性"
 
 #: ./CONTRIBUTING.md:block 26 (header)
 msgid "2. Pull request"
@@ -1296,7 +1317,9 @@ msgid ""
 "issue where possible. In some cases a single set of changes may address "
 "multiple issues, in which case be sure to list all issue numbers fixed."
 msgstr ""
-"提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議題編號。"
+"當您提出拉入請求時，請隨附描述您想要解決的問題，以及該拉入請求所能修正的議題"
+"編號。以一個拉入請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列"
+"出所有能一併修正的議題編號。"
 
 #: ./CONTRIBUTING.md:block 28 (header)
 msgid "3. Improve"
@@ -1308,7 +1331,8 @@ msgid ""
 "Code has committed to make sure that maintainers are available to review "
 "contributions with an aim to provide feedback within two business days."
 msgstr ""
-"所有貢獻都必須接受審查。The Foundation for Public Code 承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。"
+"所有貢獻都必須接受審查。Foundation for Public Code "
+"致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。"
 
 #: ./CONTRIBUTING.md:block 30 (paragraph)
 msgid ""
@@ -1318,11 +1342,13 @@ msgid ""
 "feedback. If this is the case the reviewing maintainer will help you improve"
 " your documentation and code."
 msgstr ""
-"維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人員，將負責協助改善您的註解與程式碼。"
+"維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉入請求通常需要再"
+"經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若"
+"是如此，負責審查您貢獻內容的維護人員，將協助您改善文件與程式碼。"
 
 #: ./CONTRIBUTING.md:block 31 (paragraph)
 msgid "If your documentation and code have passed human review, it is merged."
-msgstr "若您的註解與程式碼通過人工審查，就會被合併。"
+msgstr "一旦您的文件與程式碼通過人工審查，就會合併。"
 
 #: ./CONTRIBUTING.md:block 32 (header)
 msgid "4. Celebrate"
@@ -1332,17 +1358,18 @@ msgstr "4. 慶祝"
 msgid ""
 "Your ideas, documentation and code have become an integral part of this "
 "project. You are the open source hero we need!"
-msgstr "您的構思、註解與程式碼將成為本專案的一部份。您就是我們所需要的開源英雄！"
+msgstr "您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開源英雄！"
 
 #: ./CONTRIBUTING.md:block 34 (paragraph)
 msgid ""
 "In fact, feel free to open a pull request to add your name to the "
 "[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
-msgstr "歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS.md)檔案中，您的名字可以永遠留在本專案中。"
+msgstr "誠摯歡迎您提出拉入請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) "
+"檔案中，讓您所做的貢獻能銘記在本專案中。"
 
 #: ./CONTRIBUTING.md:block 35 (header)
 msgid "Translations in other languages"
-msgstr "其他語言的翻譯"
+msgstr "翻譯成其他語言"
 
 #: ./CONTRIBUTING.md:block 36 (paragraph)
 msgid ""
@@ -1350,26 +1377,27 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
-"The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增[The Standard for Public "
-"Code 社群翻譯](https://github.com/publiccodenet/community-translations-"
-"standard)。"
+"雖然 Standard for Public Code "
+"沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](https://github."
+"com/publiccodenet/community-translations-standard)，或是新增翻譯。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
-msgstr "出版"
+msgstr "發行版本"
 
 #: ./CONTRIBUTING.md:block 38 (paragraph)
 msgid ""
 "We have dedicated documentation for creating [new "
 "releases](/docs/releasing.md) and [ordering printed "
 "standards](/docs/printing.md)."
-msgstr "建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing.md)有專用註解。"
+msgstr "我們有提供[發行新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing."
+"md)的專用詳細文件。"
 
 #: ./CONTRIBUTING.md:block 39 (paragraph)
 msgid ""
 "For more information on how to use and contribute to this project, please "
 "read the [`README`](README.md)."
-msgstr "若要進一步瞭解如何使用與貢獻本專案，請參閱 [`README `](README.md)。"
+msgstr "若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 [`README `](README.md)。"
 
 #: ./GOVERNANCE.md:block 2 (header)
 msgid ""
@@ -1391,26 +1419,28 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"此標準是[The Foundation for Public "
-"Code](https://publiccode.net/)代碼庫管理的核心。我們依照本文件來判斷代碼庫是否已經準備好讓社群參與開發。"
+"此標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管"
+"理領域作監督時的核心。我們依照這份文件來判斷，某個代碼庫是否已經準備好讓社群"
+"共同參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
-msgstr "本標準由 The Foundation for Public Code 人員負責維護。"
+msgstr "這份標準由 Foundation for Public Code 職員負責維護。"
 
 #: ./GOVERNANCE.md:block 6 (paragraph)
 msgid ""
 "[We welcome contributions, such as suggestions for changes or general "
 "feedback, from anyone.](/CONTRIBUTING.md)"
-msgstr "[我們歡迎任何人提供修改的建議或是一般意見回饋等貢獻。](/CONTRIBUTING.md)"
+msgstr "[我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。](/CONTRIBUTIN"
+"G.md)"
 
 #: ./GOVERNANCE.md:block 7 (paragraph)
 msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
 msgstr ""
-"由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守 The Standard for"
-" Public Code 中最嚴苛的標準。"
+"由於 Standard for Public Code 在我們的核心流程中，扮演至關重要的角色，"
+"所以我們會以 Standard for Public Code 中的最高標準作要求。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1418,12 +1448,13 @@ msgid ""
 " opportunity to work together to improve our methods and the Standard. We "
 "may not accept all changes, but we will explain our logic."
 msgstr ""
-"我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，改善我們的方法與 The Standard for Public "
-"Code。我們可能不會接受貢獻者提出的所有修改，但我們會解釋背後的邏輯。"
+"我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方"
+"法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯"
+"。"
 
 #: ./README.md:block 1 (header)
 msgid "Standard for Public Code"
-msgstr "The Standard for Public Code"
+msgstr "Standard for Public Code"
 
 #: ./README.md:block 3 (paragraph)
 msgid ""
@@ -1432,8 +1463,9 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"The Standard for Public Code "
-"提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公共組織合作。該標準包含給政策制定者、城市管理者、開發人員與供應商的指引。"
+"Standard for Public Code 提供公共組織一套準備開源解決方案的模型，讓他們能與其"
+"他地方相似的公共組織協作。該標準包含給政策制定者、市行政官、開發人員與供應商"
+"的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1461,30 +1493,30 @@ msgid ""
 "develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
 "check/standard.publiccode.net-develop-url-check-look.json)"
 msgstr ""
-"[![頁面-建造-"
-"部署](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
-"build-"
-"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
-"build-deployment) "
-"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
-" [![標準主徽章](https://publiccodenet.github.io/publiccodenet-url-"
-"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
-"url-check/standard.publiccode.net-url-check-look.json) "
-"[![標準開發徽章](https://publiccodenet.github.io/publiccodenet-url-"
-"check/badges/standard.publiccode.net-"
-"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
-"check/standard.publiccode.net-develop-url-check-look.json)"
+"[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/"
+"workflows/pages/pages-build-deployment/badge.svg)](https://github.com/"
+"publiccodenet/standard/actions/workflows/pages/pages-build-deployment) "
+"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test."
+"yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/"
+"test.yml) [![standard main badge](https://publiccodenet.github.io/"
+"publiccodenet-url-check/badges/standard.publiccode.net."
+"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
+"publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/"
+"standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/"
+"publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)"
 
 #: ./README.md:block 6 (paragraph)
 msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr "The Standard for Public Code 目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。"
+msgstr "Standard for Public Code 目前為草稿階段。我們正在準備發行 1.0 "
+"版，目前仍在幾個代碼庫中作測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將 The Standard for Public Code 套用在您的代碼庫"
+msgstr "將 Standard for Public Code 套用到您的代碼庫"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1495,10 +1527,10 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將 The Standard for Public Code 套用在您的代碼庫，不需要任何猶豫，因為 The Standard for "
-"Public Code "
-"是開放性標準，任何人都可以免費使用。若要瞭解您代碼庫是否就緒，可以進行[資格自我評估](https://publiccodenet.github.io/assessment-"
-"eligibility)，幫助您瞭解若要滿足所有標準所需的行動。"
+"若您想要將 Standard for Public Code 套用到您的代碼庫，就請放心去做，因為它是"
+"人人都能自由採用的開放標準。若要瞭解您代碼庫所達成的程度，可以做[自我資格評估"
+"](https://publiccodenet.github.io/assessment-"
+"eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 #: ./README.md:block 9 (paragraph)
 msgid ""
@@ -1509,11 +1541,10 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
-"將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。"
-"若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能夠協助您以及其他與"
-"您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指引](https://publiccode"
-"net.github.io/community-implementation-guide-standard/"
-")，當中包括範例與其他訣竅。"
+"本標準 *應該* 足以自我解釋要如何套用到您的代碼庫中。若標準中有任何不明確的地"
+"方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如"
+"果需要一點靈感啟發，請參閱[社群製作的實踐指引](https://publiccodenet.github."
+"io/community-implementation-guide-standard/)，其中包括範例與其他提示。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
@@ -1521,8 +1552,9 @@ msgid ""
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
 msgstr ""
-"若新版的 The Standard for Public Code 有突破性的修改，The Foundation for Public Code "
-"的代碼庫管理人員會幫助The Standard for Public Code 使用者彌補不同版之間的差異。"
+"若新版的 Standard for Public Code 有任何導致過去作法不再適用的改動，則 "
+"Foundation for Public Code "
+"的代碼庫管事同仁，會協助標準的實踐者理解該如何銜接之間的落差。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1532,8 +1564,10 @@ msgid ""
 "[assessment](https://about.publiccode.net/activities/codebase-"
 "stewardship/lifecycle-diagram.html#assessment)."
 msgstr ""
-"若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與我們聯繫：[info@publiccode.net](mailto:info@publiccode.net)，並開始正式[評估](https://about.publiccode.net/activities/codebase-"
-"stewardship/lifecycle-diagram.html#assessment)。"
+"若您致力讓您的代碼庫完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：["
+"info@publiccode.net](mailto:info@publiccode."
+"net)，以展開正式[評估](https://about.publiccode.net/activities/"
+"codebase-stewardship/lifecycle-diagram.html#assessment)。"
 
 #: ./README.md:block 12 (header)
 msgid "Request for contributions"
@@ -1546,14 +1580,17 @@ msgid ""
 "way of designing, developing and procuring both the source code and policy "
 "documentation."
 msgstr ""
-"我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。"
+"我們相信公共政策與公共軟體，應該具備包容、好用、開放、易懂、可責、近用、永續"
+"等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政"
+"策文件。"
 
 #: ./README.md:block 14 (paragraph)
 msgid ""
 "This standard sets a quality level for codebases that meets the needs of "
 "public organizations, institutions and administrations as well as other "
 "critical infrastructural services."
-msgstr "本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需求。"
+msgstr "本標準為代碼庫設立品質檢核水準，使其能滿足公共組織、機構、行政機關，以及其他"
+"重大基礎設施服務的需求。"
 
 #: ./README.md:block 15 (paragraph)
 msgid ""
@@ -1561,8 +1598,8 @@ msgid ""
 "[standard.publiccode.net](https://standard.publiccode.net/). See "
 "[`index.md`](index.md) for an overview of all content."
 msgstr ""
-"The Standard for Public Code "
-"就在[standard.publiccode.net](https://standard.publiccode.net/)。內容概覽請參閱[`index.md`](index.md)。"
+"本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。"
+"請參閱 [`index.md`](index.md) 查看整體內容概覽。"
 
 #: ./README.md:block 16 (paragraph)
 msgid ""
@@ -1571,9 +1608,9 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
-"[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 The Standard for "
-"Public Code ](https://img.youtube.com/vi/QWt6vB-"
-"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+"[![Standard for Public Code "
+"的影片縮圖：兩隻手中間放著本標準的印刷本](https://img.youtube.com/vi/"
+"QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
 msgid ""
@@ -1581,12 +1618,12 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
-"[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v=QWt6vB-"
-"cipE) from Creative Commons Global Summit 2020 (4:12) on YouTube."
+"[Standard for Public Code 的影片介紹](https://www.youtube.com/watch?v=QWt6vB-"
+"cipE)，出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。"
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
-msgstr "幫忙改善本標準"
+msgstr "幫忙改善這份標準"
 
 #: ./README.md:block 19 (paragraph)
 msgid ""
@@ -1594,8 +1631,8 @@ msgid ""
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
 msgstr ""
-"The Foundation for Public Code 致力於維護與開發 The Standard for Public Code "
-"，且品質也會符合該標準本身的品質。"
+"Foundation for Public Code 致力於維護與開發 Standard for Public "
+"Code，且使其同時符合該標準自身的品質水準。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -1606,21 +1643,23 @@ msgid ""
 " described how we govern the standard in the [governance "
 "statement](GOVERNANCE.md)."
 msgstr ""
-"我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及"
-"協助開發。😊若要開始，請先參閱我們的[貢獻者指引](CONTRIBUTING.md)。由於這是相"
-"當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE."
-"md)提到我們管理該標準的方式。"
+"我們正在尋找像您這樣的人，能對此專案做出[貢獻](CONTRIBUTING.md)，像是建議改善"
+"方向，以及協助開發等。😊若要開始，請先參閱我們的[貢獻者指引](CONTRIBUTING.md)"
+"。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。[治理方式聲明](GOVE"
+"RNANCE.md)中有說明管理該標準的方式。"
 
 #: ./README.md:block 21 (paragraph)
 msgid ""
 "Please note that this project is released with a [code of "
 "conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
 "abide by its terms. Please be lovely to all other community members."
-msgstr "請注意，本專案有其[行為準則](CODE_OF_CONDUCT.md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。"
+msgstr ""
+"請注意，本專案配合[行為守則](CODE_OF_CONDUCT."
+"md)一同發行。如果要參加本專案，代表您同意遵守守則。請善待社群的所有其他成員。"
 
 #: ./README.md:block 22 (header)
 msgid "Preview, build and deploy"
-msgstr "預覽、建造與部署"
+msgstr "預覽、建置、部署"
 
 #: ./README.md:block 23 (paragraph)
 msgid ""
@@ -1629,22 +1668,25 @@ msgid ""
 "with [GitHub pages](https://pages.github.com) and "
 "[Jekyll](https://jekyllrb.com/)."
 msgstr ""
-"存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode.net/)的靜態網站，使用的是[GitHub"
-" pages](https://pages.github.com)與[Jekyll](https://jekyllrb.com/)。"
+"儲存庫會建置一個靜態網站，並部署至 [standard.publiccode.net](https://standard"
+".publiccode.net/)。網站採用 [GitHub 頁面](https://pages.github.com) 與 "
+"[Jekyll](https://jekyllrb.com/) 技術。"
 
 #: ./README.md:block 24 (paragraph)
 msgid ""
 "The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
 "means you will need ruby and ruby-bundler installed, for example:"
 msgstr ""
-"當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構，換句話說您需要安裝ruby與ruby-bundler，像是："
+"網站內容透過 [Jekyll](http://jekyllrb.com/) 技術建置。這代表您需要有安裝 "
+"ruby 與 ruby-bundler，例如："
 
 #: ./README.md:block 26 (paragraph)
 msgid ""
 "If `ruby` and `bundle` are installed, one can run `bundle install` after "
 "which the site can be rendered with the `script/serve.sh` script."
 msgstr ""
-"如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` 腳本來渲染網站。"
+"一旦安裝好 `ruby` 與 `bundle` 後，就可以執行 `bundle install`，接著再利用 `"
+"script/serve.sh` 命令稿轉譯呈現出網站成果。"
 
 #: ./README.md:block 27 (header)
 msgid "Testing"
@@ -1654,18 +1696,20 @@ msgstr "測試"
 msgid ""
 "A variety of test scripts are included. The script `script/test-all.sh` "
 "wraps running of all local tests."
-msgstr "本標準包含許多測試腳本。`script/test-all.sh` 腳本則會開始執行所有本機測試。"
+msgstr "本專案內含許多測試命令稿。其中 `script/test-all.sh` "
+"命令稿則統包執行所有本機測試。"
 
 #: ./README.md:block 29 (paragraph)
 msgid ""
 "See the scripts in the "
 "[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
 msgstr ""
-"所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/script)檔案夾。"
+"請前往 [script](https://github.com/publiccodenet/standard/tree/main/script) "
+"資料夾查看命令稿。"
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
-msgstr "生成 The Standard for Public Code PDF 檔案"
+msgstr "生成 Standard for Public Code 的 PDF 檔案"
 
 #: ./README.md:block 31 (paragraph)
 msgid ""
@@ -1674,21 +1718,22 @@ msgid ""
 "[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
 "used to transform PDFs into `.epub`."
 msgstr ""
-"除了 Jekyll 以外，要生成 PDF "
-"檔案也需要仰賴[Weasyprint](https://weasyprint.org/)以及[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)可以將"
-" PDF 轉換成`.epub`檔案。"
+"除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 "
+"[Weasyprint](https://weasyprint.org/) 和 [QPDF](https://github.com/qpdf/"
+"qpdf)。[Pandoc](https://pandoc.org/) 則可將 PDF 檔轉換成 `.epub` 檔。"
 
 #: ./README.md:block 32 (paragraph)
 msgid ""
 "To generate these kinds of files, the dependencies should be installed, for "
 "example:"
-msgstr "若要生成這些種類的檔案，則需要安裝類似下列的依附元件："
+msgstr "若要生成這類檔案，則應該要安裝依賴的軟體項目，例如："
 
 #: ./README.md:block 34 (paragraph)
 msgid ""
 "The file `standard-print.html` can be converted to a nice looking PDF, along"
 " with the other release files, using:"
-msgstr "使用以下腳本，可以將 `standard-print.html` 檔案以及其他的版本檔案轉換成美觀的 PDF："
+msgstr "使用以下命令稿，可以將 `standard-print.html` 檔案轉換成美觀的 PDF "
+"檔，同時包括其他發行用的檔案："
 
 #: ./README.md:block 36 (header)
 msgid "License"
@@ -1705,9 +1750,10 @@ msgid ""
 "it. If you contribute you also grant these rights to others. You can read "
 "more about how to help in the [contributing guide](CONTRIBUTING.md)."
 msgstr ""
-"The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解"
-"與註解。換句話說，任何人都可以任意使用這些內容。如果您是貢獻者，您也將這些權"
-"利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。"
+"本標準採用 CC0 "
+"公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任"
+"何人都能任意使用這些內容。如果您是貢獻者，代表您也將這些權利賦予他人。若要進"
+"一步瞭解如何協助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
 msgid "order: 2 redirect_from:"
@@ -1719,7 +1765,7 @@ msgstr "criteria/bundle-policy-and-code"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
 msgid "Bundle policy and source code"
-msgstr "同捆政策與原始碼"
+msgstr "政策與原始碼要合捆"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
 msgid ""
@@ -1748,7 +1794,7 @@ msgstr "組織要能夠評估是否在新脈絡中執行代碼庫時，必須先
 
 #: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
 msgid "Requirements"
-msgstr "規定"
+msgstr "需求規定"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "The codebase MUST include the policy that the source code is based on."
@@ -1965,7 +2011,7 @@ msgstr "任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外
 msgid ""
 "The codebase MUST NOT contain sensitive information regarding users, their "
 "organization or third parties."
-msgstr "代碼庫「不允許」包含使用者、使用者機構或第三方的敏感資料。"
+msgstr "代碼庫「禁止」包含使用者、使用者機構或第三方的敏感資料。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
@@ -3387,7 +3433,7 @@ msgstr "所有程式碼皆必須搭配授權條款檔案一併發行。"
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the codebase."
-msgstr "不得要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
+msgstr "禁止要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
@@ -4123,7 +4169,7 @@ msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr "代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。"
+msgstr "代碼庫採用的任何非開放標準，皆禁止妨礙代碼庫的協作與重複使用。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4766,7 +4812,7 @@ msgstr "若額外的拉入請求合併至發行分支，請要求重新審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Run the to-archive-org.sh script"
-msgstr "執行「to-archive-org.sh」腳本"
+msgstr "執行「to-archive-org.sh」命令稿"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Once reviews are complete, merge to 'main'"
@@ -5408,14 +5454,15 @@ msgstr "詞彙表"
 
 #: ./glossary.md:block 4 (header)
 msgid "Code"
-msgstr "規則（Code）"
+msgstr "規則或代碼 (Code)"
 
 #: ./glossary.md:block 5 (paragraph)
 msgid ""
 "Any explicitly described system of rules. This includes laws, policy and "
 "ordinances, as well as source code that is used to build software. Both of "
 "these are rules, some executed by humans and others by machines."
-msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是規則，前者由人類來執行，後者則是機器。"
+msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始代碼。兩者都"
+"是規則，前者由人類來執行，後者則是機器。"
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
@@ -5813,7 +5860,8 @@ msgid ""
 "The following keywords in this document are to be interpreted as described "
 "in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
 msgstr ""
-"本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) 來詮釋："
+"本文件的下列關鍵字，請以 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119)"
+" 中的描述作為詮釋："
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST"
@@ -5821,19 +5869,19 @@ msgstr "必須"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST NOT"
-msgstr "不得"
+msgstr "禁止"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "REQUIRED"
-msgstr "被要求"
+msgstr "要求"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHALL"
-msgstr "應該"
+msgstr "應當"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHALL NOT"
-msgstr "不應"
+msgstr "不得"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHOULD"
@@ -5841,7 +5889,7 @@ msgstr "應該"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "SHOULD NOT"
-msgstr "不應"
+msgstr "不該"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "RECOMMENDED"
@@ -5849,7 +5897,7 @@ msgstr "建議"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MAY"
-msgstr "得"
+msgstr "得以"
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "OPTIONAL"

From 13e089026cf429b4009a5185a2355144b9c8b71f Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Thu, 7 Sep 2023 03:26:54 +0000
Subject: [PATCH 47/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 123 ++++++++++++++----------
 1 file changed, 71 insertions(+), 52 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index c8a42de5..fac3631c 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-06 16:44+0000\n"
+"PO-Revision-Date: 2023-09-08 16:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -771,7 +771,7 @@ msgstr "指出 publiccode.yml 是機器可讀中介資料說明的範例之一
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
-msgstr "將「您的代碼庫」與「貴組織」改為較不具有所有格的寫法。"
+msgstr "將「您的代碼庫」與「您的組織單位」改為較不具有所有格的寫法。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add instructions for creating a print version."
@@ -1774,15 +1774,17 @@ msgid ""
 "anyone to implement the codebase in their local context or contribute to the"
 " further development of the [codebase](../glossary.md#codebase)."
 msgstr ""
-"使用[原始碼](../glossary.md#source-"
-"code)以及[政策](../glossary.md#policy)註解，提供基石給想在當地脈絡使用代碼庫的人或是想要對[代碼庫](../glossary.md#codebase)進一步發展有所貢獻的人。"
+"對於想根據所在情境實作代碼庫的人，或是想更進一步貢獻[代碼庫](../glossary."
+"md#codebase)開發的人來說，能同時取用[原始碼](../glossary.md#source-"
+"code)與[政策](../glossary.md#policy)文件兩者，可作為建置成品時的基礎組件。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
 msgid ""
 "Understanding the domain and policies within that domain is fundamental to "
 "understanding what problems a codebase is trying to solve and how it sets "
 "out to solve them."
-msgstr "瞭解網域與其政策，才能瞭解代碼庫想要解決的問題以及解決方式。"
+msgstr "瞭解作用範疇與該範疇的政策是基本原則，才能瞭解代碼庫試圖想解決的問題是什麼，"
+"以及該如何解決這些問題的作法。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
 msgid ""
@@ -1790,7 +1792,8 @@ msgid ""
 "organization needs to understand what process changes it must choose to make"
 " or how to contribute additional configurability to the existing solution in"
 " order to adapt it to the new context."
-msgstr "組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。"
+msgstr "為了評估是否需要在新的情境中實作代碼庫，組織單位需要瞭解必須做出改變的程序有"
+"哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
 msgid "Requirements"
@@ -1798,24 +1801,25 @@ msgstr "需求規定"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "The codebase MUST include the policy that the source code is based on."
-msgstr "代碼庫「必須（Must）」包含做為原始碼基礎的政策。"
+msgstr "代碼庫「必須」包含原始碼所根據的政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr "若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵測的原始碼除外）。"
+msgstr "如果政策基於原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始"
+"碼則可除外。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
-msgstr "政策格式「應該」機器可讀且明確。"
+msgstr "政策「應該」採用機器可讀且明確的格式。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
 " validate that the source code and the policy are executed coherently."
-msgstr ""
-"[持續整合](../glossary.md#continuous-integration) 測試「應該（Should）」驗證原始碼與政策是否有一致執行。"
+msgstr "[持續整合](../glossary.md#continuous-"
+"integration)測試「應該」驗證原始碼與政策是否有一致執行。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
 msgid "How to test"
@@ -1825,33 +1829,33 @@ msgstr "測試方式"
 msgid ""
 "Confirm with a civil servant that all policy that the source code is based "
 "on is included."
-msgstr "與公務人員確認有收錄做為原始碼基礎的完整政策。"
+msgstr "與公務人員確認原始碼所根據的所有政策內容都有收錄在內。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr "與公務人員確認有收錄做為政策基礎的完成原始碼。"
+msgstr "與公務人員確認根據政策而來的所有原始碼都有收錄在內。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
-msgstr "確認政策是否可由機器判讀。"
+msgstr "確認政策內容是否能在機器上解讀。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid ""
 "Check the continuous integration tests for coherent execution of source code"
 " and policy pass."
-msgstr "透過持續整合測試，確認原始碼與政策的一致執行。"
+msgstr "確認原始碼與政策間的執行一致性能通過持續整合測試。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
 msgid "Public policy makers: what you need to do"
-msgstr "公共政策制定者：您的責任"
+msgstr "公共政策制定者：需要的工作"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Collaborate with developers and designers to make sure there is no mismatch "
 "between policy code and source code."
-msgstr "與開發人員及設計師合作，確認政策程式碼與原始碼沒有錯配。"
+msgstr "與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1862,32 +1866,36 @@ msgid ""
 "which impact the development or the deployment context of the codebase for "
 "your organization."
 msgstr ""
-"提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標準，以及影響貴機構代碼庫開發或部署脈絡的組織流程。"
+"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
+"文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
+"，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid "Provide references and links to texts which support the policies."
-msgstr "引用支持政策的文字並附上連結。"
+msgstr "請提供政策相關參考資料與連結。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Document policy in formats that are unambiguous and machine-readable, such "
 "as those published by the [Object Management "
 "Group](https://www.omg.org/spec/)."
-msgstr "用明確且機器可讀的格式（像是[對象管理組織](https://www.omg.org/spec/"
-")發佈的格式）來紀錄政策。"
+msgstr "政策內容請使用明確且機器可讀的格式，像是[物件管理群體](https://www.omg.org/"
+"spec/)所發表的格式。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Track policy with [the same version control](maintain-version-control.md) "
 "and documentation used to track source code."
-msgstr "利用[相同的版本控制l](maintain-version-control.md)以及用來追蹤原始碼的註解，來追蹤政策。"
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](maintain-version-control."
+"md)與文件。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
 "Check in regularly to understand how the source code in the codebase has "
 "changed and whether it still matches the [intentions of the "
 "policy](document-codebase-objectives.md)."
-msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-codebase-objectives.md)。"
+msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否仍然符合[政策意圖](document-"
+"codebase-objectives.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1898,45 +1906,46 @@ msgid ""
 "accessibility), or human rights policies, like a public organization's "
 "commitment to equal opportunity."
 msgstr ""
-"納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-"
-"lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟無障礙指令](https://ec.europa.eu/digital-"
-"single-market/en/web-accessibility)這些法律義務，或是人權政策，像是公共組織對機會平等的承諾。"
+"納入會影響社會群體、代碼庫與開發目標的相關政策，包含[一般資料保護規則](https"
+"://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟網頁無障礙命令](https://ec"
+".europa.eu/digital-single-market/en/web-accessibility)等此類法律義務，或者是"
+"人權政策，例如公共組織對機會平等的承諾等。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
-msgstr "管理人員：您的義務"
+msgstr "管理人員：需要的工作"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
 msgid ""
 "Keep policy makers, developers and designers involved and connected "
 "throughout the whole development process."
-msgstr "在整個開發流程中，讓政策制定者、開發人員與設計師全程參與。"
+msgstr "讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
 msgid ""
 "Make sure policy makers, developers and designers are working to the same "
 "objectives."
-msgstr "確保政策制定者、開發人員與設計師有同樣的目標。"
+msgstr "確保政策制定者、開發人員與設計師朝相同目標努力。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
 msgid "Developers and designers: what you need to do"
-msgstr "開發人員與設計師：您的責任"
+msgstr "開發人員與設計師：需要的工作"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid ""
 "Become familiar with and be able to use the process modelling notation that "
 "the policy makers in your organization use."
-msgstr "熟悉並且學會使用貴機構的政策制定者所使用的流程模型標記法。"
+msgstr "熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid ""
 "Work together with policy makers to make sure there is no mismatch between "
 "policy code and source code."
-msgstr "與政策制定者合作，確保政策程式碼與原始碼沒有錯配。"
+msgstr "與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
 msgid "Give feedback on how to make policy documentation more clear."
-msgstr "針對如何讓政策註解更明確提供意見回饋。"
+msgstr "針對如何讓政策文字更清楚提供意見。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
 msgid "Further reading"
@@ -1948,14 +1957,15 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
 " on Wikipedia."
 msgstr ""
-"維基百科的[商業流程模型與標記法](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)。"
+"維基百科上的 [BPMN 業務流程模型與標記法](https://en.wikipedia.org/wiki/"
+"Business_Process_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
 "[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
 " Trisotech."
 msgstr ""
-"Trisotech的[BPMN快速指引](https://www.bpmnquickguide.com/"
+"Trisotech 提供的 [BPMN 快速指南](https://www.bpmnquickguide.com/"
 "view-bpmn-quick-guide/)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
@@ -1964,13 +1974,14 @@ msgid ""
 "Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
 "Wikipedia."
 msgstr ""
-"維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)。"
+"維基百科上的 [DMN 決策模型與標記法](https://en.wikipedia.org/wiki/"
+"Decision_Model_and_Notation)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
 msgid ""
 "[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
 "Wikipedia."
-msgstr "維基百科的[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。"
+msgstr "維基百科上的[ CMMN 案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。"
 
 #: ./criteria/code-in-the-open.md:block 3 (header)
 msgid "order: 1"
@@ -1978,7 +1989,7 @@ msgstr "order: 1"
 
 #: ./criteria/code-in-the-open.md:block 4 (header)
 msgid "Code in the open"
-msgstr "以開放精神編寫原始碼"
+msgstr "原始碼要開放"
 
 #: ./criteria/code-in-the-open.md:block 5 (paragraph)
 msgid ""
@@ -1986,45 +1997,51 @@ msgid ""
 "code](../glossary.md#source-code) quality, makes the source code easier to "
 "audit, and enables collaboration."
 msgstr ""
-"開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽查，並且讓協作更容易。"
+"以開放精神編寫原始碼，能改善資訊透明、提高[原始碼](../glossary.md#source-"
+"code)品質、讓原始碼更容易稽核，也能促進互相協作。"
 
 #: ./criteria/code-in-the-open.md:block 6 (paragraph)
 msgid ""
 "Together, this creates more opportunities for citizens to understand how "
 "software and [policy](../glossary.md#policy) impact their interactions with "
 "a public organization."
-msgstr "這讓市民更能夠瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公共組織的互動。"
+msgstr "這些加在一起，讓公民更有機會瞭解軟體與[政策](../glossary."
+"md#policy)如何影響他們與公共組織的互動。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any policy in use (unless used for fraud detection) MUST"
 " be published and publicly accessible."
-msgstr "任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。"
+msgstr "任何使用中政策的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
+"眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。"
+msgstr "任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
+"眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST NOT contain sensitive information regarding users, their "
 "organization or third parties."
-msgstr "代碼庫「禁止」包含使用者、使用者機構或第三方的敏感資料。"
+msgstr "代碼庫「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "Any source code not currently in use (such as new versions, proposals or "
 "older versions) SHOULD be published."
-msgstr "目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈。"
+msgstr "目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "Documenting which source code or policy underpins any specific interaction "
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
-msgstr "可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-public)與任何組織互動的原始碼或政策。"
+msgstr ""
+"可選擇是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間"
+"可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
@@ -2032,21 +2049,23 @@ msgid ""
 "the internet where it can be seen from outside the original contributing "
 "organization and without the need for any form of authentication or "
 "authorization."
-msgstr "確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須任何形式的驗證或認證也可以看到。"
+msgstr "確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形"
+"式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
 "Confirm that the [codebase](../glossary.md#codebase) files and commit "
 "history do not include sensitive information."
-msgstr "確認[代碼庫](../glossary.md#codebase)檔案與提交紀錄不包含敏感性資訊。"
+msgstr "確認[代碼庫](../glossary."
+"md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid "Check for the publication of source code not currently in use."
-msgstr "檢查現在沒有使用的原始碼是否有公開。"
+msgstr "檢查目前非使用中的原始碼是否有公開。"
 
 #: ./criteria/code-in-the-open.md:block 12 (unordered list)
 msgid "Develop policies in the open."
-msgstr "以開放精神制定政策。"
+msgstr "制定合乎開放精神的政策。"
 
 #: ./criteria/code-in-the-open.md:block 12 (unordered list)
 msgid "Prioritize open and transparent policies."
@@ -2066,14 +2085,14 @@ msgid ""
 "As a reviewer, for each commit, verify that content does not include "
 "sensitive information such as configurations, usernames or passwords, public"
 " keys or other real credentials used in production systems."
-msgstr ""
-"審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
+msgstr "審查人員在檢核每次的送交版次紀錄時，要確實核對內容沒有包含組態設定、使用者名"
+"稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 16 (unordered list)
 msgid ""
 "Clearly split data and source code, in order to meet the requirement about "
 "sensitive information above."
-msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。"
+msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與原始碼。"
 
 #: ./criteria/code-in-the-open.md:block 18 (unordered list)
 msgid ""

From 5e6824d8ae8966b45b18c5d3103f93d53c4f5cc0 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Sat, 9 Sep 2023 13:05:10 +0000
Subject: [PATCH 48/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 697 ++++++++++++++----------
 1 file changed, 395 insertions(+), 302 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index fac3631c..9989187c 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-08 16:44+0000\n"
+"PO-Revision-Date: 2023-09-10 00:15+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -235,7 +235,7 @@ msgstr "2023年5月31日：📑第十五版新增紀錄募資審查的新規定
 msgid ""
 "Add requirement to document who is expected to cover the cost of reviewing "
 "contributions."
-msgstr "新增規定，紀錄由誰負擔審核貢獻內容所需的開銷費用。"
+msgstr "新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
@@ -282,13 +282,13 @@ msgstr "2023年4月20日：🔀第十四版草稿新增可移植性與測試的
 msgid ""
 "New requirement in Create reusable and portable code about the development "
 "being a collaboration between multiple parties."
-msgstr "新增規定，在〈編寫可重複使用且可移植的程式碼〉加入多方協作開發的內容。"
+msgstr "新增規定，在〈程式碼要可重複使用且可攜〉加入多方協作開發的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "New requirement in Create reusable and portable code about being dependent "
 "on a single vendor."
-msgstr "新增規定，在〈編寫可重複使用且可移植的程式碼〉中加入依賴單一供應商的內容。"
+msgstr "新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -606,7 +606,7 @@ msgstr "2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內
 msgid ""
 "Requirement for localization made explicit in Create reusable and portable "
 "code."
-msgstr "在〈編寫可重複使用與移植的程式碼〉中定下明確的在地化規定。"
+msgstr "在〈程式碼要可重複使用且可攜〉中定下明確的在地化規定。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
@@ -618,7 +618,7 @@ msgid ""
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
 msgstr "在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容必須（MUST）小」的規定，改"
-"為必須紀錄貢獻所要完成的期望，並一次專注在單一議題上。"
+"為必須紀錄貢獻所要完成的期待，並一次專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
@@ -667,14 +667,14 @@ msgstr "釐清〈政策與原始碼要合捆〉中，「政策」包含能影響
 msgid ""
 "Emphasize reusability also on parts of the solutions in Create reusable and "
 "portable code."
-msgstr "在〈編寫可重複使用與移植的程式碼〉中強調解決方案部分內容的可重複使用性。"
+msgstr "在〈程式碼要可重複使用且可攜〉中強調解決方案部分內容的可重複使用性。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Expand guidance to Developers and designers in Create reusable and portable "
 "code about deploying to proprietary platforms."
-msgstr "將〈編寫可重複使用與移植的程式碼〉當中的開發人員與設計師指引，加入部署到專有"
-"平台上的內容。"
+msgstr "將〈程式碼要可重複使用且可攜〉當中的開發人員與設計師指引，加入部署到專有平台"
+"上的內容。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
@@ -761,7 +761,7 @@ msgstr "將「白話語言定義」加入延伸閱讀。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Move the Semantic Versioning Specification further reading reference."
-msgstr "將「語意化版本控制規範」移動為延伸閱讀參考內容。"
+msgstr "將「語意化版本編號規範」移動為延伸閱讀參考內容。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
@@ -1147,7 +1147,7 @@ msgid ""
 " and send an email to "
 "[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
 msgstr ""
-"或者，註冊加入[郵遞論壇清單](https://lists.publiccode.net/mailman/postorius/"
+"或者，註冊加入[郵遞論壇列表](https://lists.publiccode.net/mailman/postorius/"
 "lists/standard.lists.publiccode.net/)，並寄送電子郵件到[standard@lists."
 "publiccode.net](mailto:standard@lists.publiccode.net)。"
 
@@ -1275,10 +1275,10 @@ msgid ""
 "release](docs/releasing.md)."
 msgstr ""
 "Standard for Public Code 目標[使用白話的英語](criteria/use-plain-english.md)"
-"，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有繞圖換行，來讓「`di"
-"ff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而"
-"不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才["
-"推出新發行版本](docs/releasing.md)。"
+"，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`"
+"diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，"
+"而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質"
+"才[推出新發行版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -2159,37 +2159,40 @@ msgid ""
 "codebase has evolved is key to understanding the codebase and how to "
 "contribute to it."
 msgstr ""
-"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解代碼庫的演變，才能真正認識該代碼庫並且做出貢獻。"
+"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用，"
+"或為該代碼庫做出貢獻。代碼庫版本的成熟度，包含其依賴項目的成熟度。瞭解代碼庫"
+"演進到什麼程度，是理解該代碼庫並知道如何做出貢獻的關鍵。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The codebase MUST be versioned."
-msgstr "代碼庫必須註明版本編號。"
+msgstr "代碼庫「必須」註明版本編號。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase MUST prominently document whether or not there are versions of "
 "the codebase that are ready to use."
-msgstr "代碼庫必須明確標示是否有已經準備好使用的版本。"
+msgstr "代碼庫「必須」明確以文件記錄，是否有已經準備好可供使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "Codebase versions that are ready to use MUST only depend on versions of "
 "other codebases that are also ready to use."
-msgstr "準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本。"
+msgstr "準備好可供使用的代碼庫版本，「必須」只能依賴其他也已經準備好可供使用的代碼庫"
+"版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr "代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
+msgstr "代碼庫「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The method for assigning version identifiers SHOULD be documented."
-msgstr "應該有文件記錄分配版本識別碼的方式。"
+msgstr "「應該」要以文件記錄分配版本識別碼的方法。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "It is OPTIONAL to use semantic versioning."
-msgstr "可選擇是否使用語意化版本控制。"
+msgstr "「可選擇」是否使用語意化版本控制編號。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
@@ -2200,18 +2203,20 @@ msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
 msgid ""
 "Confirm that it is obvious to policy makers, managers, developers and "
 "designers whether the codebase has versions that are ready to use."
-msgstr "確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使用的版本。"
+msgstr "確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道代碼庫是否有準備好"
+"可供使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that ready to use versions of the codebase do not depend on any "
 "versions of other codebases that are not ready to use."
-msgstr "確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何版本。"
+msgstr "確認準備好可供使用的代碼庫版本，並不依賴任何尚未準備好可供使用的其他代碼庫的"
+"版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Check that the versioning scheme of the codebase is documented and followed."
-msgstr "確認有記錄並遵守代碼庫的版本控制方式。"
+msgstr "確認有文件記錄代碼庫的版本編號方法，並且確實遵守。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid "Check that there is a log of changes."
@@ -2223,8 +2228,8 @@ msgid ""
 " code](../glossary.md#source-code) developed needs to be tested and improved"
 " before it can be put into service."
 msgstr ""
-"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [程式碼](../glossary.md#source-code) "
-"都必須先經過測試與改善，才能夠投入服務。"
+"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 "
+"[原始碼](../glossary.md#source-code) 都必須先經過測試與改善，才能夠投入服務。"
 
 #: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
 msgid ""
@@ -2237,19 +2242,20 @@ msgid ""
 "Make sure that services only rely on versions of codebases of equal or "
 "greater maturity than the service. For example, don't use a beta version of "
 "a codebase in a production service."
-msgstr "要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。"
+msgstr "要確認服務依賴的代碼庫版本成熟度，等同或高於該服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 公測版代碼庫。"
 
 #: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
 msgid ""
 "Make sure that the codebase versioning approach is followed for all "
 "releases."
-msgstr "確認所有發行都遵守代碼庫版本控制方式。"
+msgstr "確認所有發行版，都有遵守代碼庫的版本控制編號作法。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Semantic Versioning Specification](https://semver.org/) used by many "
 "codebases to label versions."
-msgstr "許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。"
+msgstr "許多代碼庫使用「[語意化版本編號規範](https://semver.org/)」來標示版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
@@ -2283,7 +2289,7 @@ msgstr "criteria/document-objectives"
 
 #: ./criteria/document-codebase-objectives.md:block 5 (header)
 msgid "Document codebase objectives"
-msgstr "記錄代碼庫目標"
+msgstr "代碼庫要有目標文件"
 
 #: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
 msgid ""
@@ -2293,26 +2299,31 @@ msgid ""
 "provide an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
 msgstr ""
-"清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷目前或未來是否會對此代碼庫（或其模組之一）有興趣。"
+"以文件清楚記錄[代碼庫](../glossary.md#codebase)目標，來傳達代碼庫的用途目標。"
+"這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能方便人們判斷，是"
+"否在當下或未來，會對此代碼庫或其模組感興趣。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST contain documentation of its objectives, like a mission "
 "and goal statement, that is understandable by developers and designers so "
 "that they can use or contribute to the codebase."
-msgstr "代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
+msgstr "代碼庫「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師"
+"需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr "代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。"
+msgstr "代碼庫文件「應該」清楚描述[政策](../glossary."
+"md#policy)目標與代碼庫目標之前的關聯。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr "可選擇是否以文件記錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。"
+msgstr "「可選擇」是否以文件記錄給[一般民眾](../glossary.md#general-"
+"public)看的代碼庫目標。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
@@ -2338,8 +2349,8 @@ msgid ""
 "supporting policy documents added to meet the [Bundle policy and source "
 "code](bundle-policy-and-source-code.md) criterion."
 msgstr ""
-"確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼要合捆](bundle-policy-and-source-"
-"code.md)的標準。"
+"確保所有代碼庫目標，有連結或引用為了符合[政策與原始碼要合捆](bundle-policy-"
+"and-source-code.md)準則而加入的支持政策文件。"
 
 #: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
 msgid ""
@@ -2372,7 +2383,7 @@ msgstr "criteria/documenting"
 
 #: ./criteria/document-the-code.md:block 5 (header)
 msgid "Document the code"
-msgstr "記錄程式碼"
+msgstr "程式碼要有文件"
 
 #: ./criteria/document-the-code.md:block 6 (paragraph)
 msgid ""
@@ -2381,8 +2392,9 @@ msgid ""
 "essential for people to start using the [codebase](../glossary.md#codebase) "
 "and contributing to it more quickly."
 msgstr ""
-"詳細記錄的[程式碼](../glossary.md#source-"
-"code)幫助民眾瞭解該原始碼的作用與使用方式。記錄文件是幫助民眾開始使用[代碼庫](../glossary.md#codebase)並且更快做出貢獻的關鍵。"
+"文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作"
+"用與使用方式。文件紀錄是幫助人們快速上手[代碼庫](../glossary."
+"md#codebase)的使用並做出貢獻的關鍵。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2390,19 +2402,20 @@ msgid ""
 " well as source code, MUST be described in language clearly understandable "
 "for those that understand the purpose of the codebase."
 msgstr ""
-"代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。"
+"代碼庫的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚瞭"
+"解的用語描述，讓懂代碼庫目的用途的人也能夠理解。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain a description of how to "
 "install and run the software."
-msgstr "代碼庫文件必須說明如何安裝與執行軟體。"
+msgstr "代碼庫文件「必須」說明如何安裝與執行軟體。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr "代碼庫文件必須為關鍵功能舉出範例。"
+msgstr "代碼庫文件「必須」為關鍵功能舉出範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2410,39 +2423,43 @@ msgid ""
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
 msgstr ""
-"代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。"
+"代碼庫文件「應該」包含精要的說明，讓[一般民眾](../glossary.md#general-"
+"public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr "代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。"
+msgstr "代碼庫文件「應該」有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要"
+"，也應該包含測試資料集。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr "代碼庫文件應該包含所有功能的範例。"
+msgstr "代碼庫文件「應該」包含所有功能的範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr "程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。"
+msgstr "程式碼文件「應該」描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高"
+"層架構圖表示。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "There SHOULD be [continuous integration](../glossary.md#continuous-"
 "integration) tests for the quality of the documentation."
-msgstr "應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。"
+msgstr "「應該」要有針對文件品質的[持續整合](../glossary.md#continuous-"
+"integration)測試。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr "可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
+msgstr "「可選擇」是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
@@ -2489,17 +2506,18 @@ msgid ""
 "Check that the documentation quality is part of integration testing, for "
 "example documentation is generated correctly, and links and images are "
 "tested."
-msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與圖片等。"
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件是否正確，並檢查連結與"
+"圖片等。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed."
-msgstr "定期檢查代碼庫中非政策程式碼的變動。"
+msgstr "定期查看代碼庫中非政策程式碼的變動情況。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
-msgstr "針對如何讓非政策文字更清楚提供意見。"
+msgstr "針對如何讓非政策文件更清楚易懂提供意見回饋。"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -2507,7 +2525,8 @@ msgid ""
 " and source code are documented. For example, is the current documentation "
 "sufficient to persuade a manager at another public organization to use this "
 "codebase?"
-msgstr "嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的文件是否足以說服另一個公共組織的管理人員使用本代碼庫？"
+msgstr "嘗試使用代碼庫，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來"
+"說，目前的文件是否足以說服另一個公共組織的管理人員使用這個代碼庫？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -2529,7 +2548,7 @@ msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
 msgid ""
 "[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
 "Docs."
-msgstr "Write the Docs《[文件指引](https://www.writethedocs.org/guide/)》。"
+msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
 
 #: ./criteria/index.md:block 3 (header)
 msgid "order: 0"
@@ -2537,7 +2556,7 @@ msgstr "order: 0"
 
 #: ./criteria/index.md:block 4 (header)
 msgid "Criteria"
-msgstr "標準"
+msgstr "準則"
 
 #: ./criteria/index.md:block 5 (paragraph)
 msgid "{% assign sorted = site.pages | sort:\"order\" %}"
@@ -2579,52 +2598,57 @@ msgid ""
 "changes in parallel and helps future developers to understand the reasons "
 "for changes."
 msgstr ""
-"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md#source-"
-"code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人員針對修改變動平行作業，並幫助未來的開發人員瞭解修改的原因。"
+"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md"
+"#source-code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓"
+"您為代碼庫維護有條理的變動歷史文件。這是大規模協作能運作的要素，使開發人員得"
+"以針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All files in the codebase MUST be version controlled."
-msgstr "代碼庫中的所有檔案皆必須有版本控制。"
+msgstr "代碼庫中的所有檔案皆「必須」有版本控制。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All decisions MUST be documented in commit messages."
-msgstr "所有決定皆必須記錄成提交訊息。"
+msgstr "所有決定皆「必須」記錄成送交版次訊息。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Every commit message MUST link to discussions and issues wherever possible."
-msgstr "每份提交訊息皆必須盡可能附上討論與議題連結。"
+msgstr "每份送交版次訊息皆「必須」盡可能附上討論與議題連結。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "The codebase SHOULD be maintained in a distributed version control system."
-msgstr "代碼庫應該以分散式版本控制系統作維護。"
+msgstr "代碼庫「應該」以分散式版本控制系統作維護。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Contribution guidelines SHOULD require contributors to group relevant "
 "changes in commits."
-msgstr "貢獻準則應該要求貢獻者將相關的修改變動提交內容作群組分類。"
+msgstr "貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Maintainers SHOULD mark released versions of the codebase, for example using"
 " revision tags or textual labels."
-msgstr "維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。"
+msgstr "維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本"
+"。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "Contribution guidelines SHOULD encourage file formats where the changes "
 "within the files can be easily viewed and understood in the version control "
 "system."
-msgstr "貢獻準則應該鼓勵採用方便版本控制系統檢視檔案修改內容的檔案格式。"
+msgstr "貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更"
+"動的檔案格式。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr "貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。"
+msgstr "貢獻者「可選擇」是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對"
+"其內容有疑問時，可以與之前的貢獻者聯絡。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
@@ -2636,14 +2660,15 @@ msgstr "確認代碼庫維持在版本控制狀態中，像是使用 Git 之類
 msgid ""
 "Review the commit history, confirming that all commit messages explain why "
 "the change was made."
-msgstr "審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。"
+msgstr "審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Review the commit history, confirming that where possible all commit "
 "messages include the discussion about the change was or where to find it "
 "(with a URL)."
-msgstr "審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。"
+msgstr "審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的"
+"地方，包含變動內容以及連結位置（提供網址）。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid "Check if the version control system is distributed."
@@ -2653,7 +2678,7 @@ msgstr "檢查版本控制系統是否為分散式。"
 msgid ""
 "Review the commit history, check if grouping of relevant changes in "
 "accordance with the contributing guidelines."
-msgstr "審查提交內容歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。"
+msgstr "審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
@@ -2665,7 +2690,7 @@ msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr "檢查代碼庫時，在可能的情況下檔案都是採用文字格式。"
+msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid ""
@@ -2699,13 +2724,13 @@ msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達
 msgid ""
 "Make sure that all files required to understand the code, build and deploy "
 "are in the version control system."
-msgstr "確認版本控制系統具有瞭解程式碼、組建與部署所需的所有檔案。"
+msgstr "確認版本控制系統中，有瞭解程式碼、建置與部署所需的所有檔案。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Write clear commit messages so that it is easy to understand why the commit "
 "was made."
-msgstr "提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。"
+msgstr "送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
@@ -2715,7 +2740,7 @@ msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."
-msgstr "提交內容的訊息要寫清楚，方便之後比較各版本。"
+msgstr "送交版次訊息要寫清楚，方便之後比較各版本。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
@@ -2746,7 +2771,8 @@ msgid ""
 "[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
 "use GitHub or refresh your skills."
 msgstr ""
-"GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。"
+"GitHub 提供的「[GitHub 技能](https://skills.github.com/)」，可學習如何使用 "
+"GitHub，或是重溫您的技巧。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2770,44 +2796,48 @@ msgid ""
 " able to fix problems, add features, and address security issues of the "
 "shared [codebase](../glossary.md#codebase)."
 msgstr ""
-"若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫](../glossary.md#codebase)修復問題與新增功能。"
+"若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[代碼庫](../glo"
+"ssary.md#codebase)修正問題、新增功能，以及提出安全性議題等。"
 
 #: ./criteria/make-contributing-easy.md:block 6 (paragraph)
 msgid ""
 "A shared digital infrastructure makes it easier to make collaborative "
 "contributions. The less effort it takes to make contributions that are "
 "accepted by the codebase, the more likely users are to become contributors."
-msgstr "共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者越可能成為貢獻者。"
+msgstr "共享的數位基礎建設讓協作貢獻更容易。使用者讓代碼庫接受貢獻時所需付出的心力越"
+"少，則使用者越可能成為貢獻者。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have a public issue tracker that accepts suggestions from "
 "anyone."
-msgstr "代碼庫必須有個可以公開接受任何人建議的議題追蹤器。"
+msgstr "代碼庫「必須」有個可以公開接受任何人建議的議題追蹤器。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。"
+msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記"
+"錄在「`README`」檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr "代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄清單。"
+msgstr "代碼庫「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵"
+"遞論壇）。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "There MUST be a way to report security issues for responsible disclosure "
 "over a closed channel."
-msgstr "必須有辦法透過封閉的管道通報安全性問題。"
+msgstr "「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The documentation MUST include instructions for how to report potentially "
 "security sensitive issues."
-msgstr "文件必須說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。"
+msgstr "文件「必須」說明，該如何通報潛在的安全性與敏感性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid "Confirm that there is a public issue tracker."
@@ -2856,25 +2886,26 @@ msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使
 msgid ""
 "Just like for [reviews](require-review-of-contributions.md), make sure to "
 "respond to requests promptly."
-msgstr "跟[審查](require-review-of-contributions.md)一樣，務必迅速回應請求。"
+msgstr "與[審查](require-review-of-contributions.md)流程相同，務必迅速回應請求。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Keep your managers informed of the time and resources you require to support"
 " other contributors."
-msgstr "告知管理人員您支持其他貢獻者時所需的時間與資源。"
+msgstr "告知管理人員，您在支援其他貢獻者時所需的時間與資源。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Make sure that appropriate communication channels for asking maintainers and"
 " stakeholders questions are easy to locate, for instance in the README."
-msgstr "確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`」文件當中。"
+msgstr "確保人們可輕鬆找到合適的溝通管道，來詢問維護人員與利害關係人問題，例如寫在「`"
+"README`」文件當中。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
 "Make sure that appropriate contact details are included in the metadata, for"
 " instance in the publiccode.yml file."
-msgstr "確保中介資料包含合適的聯絡資訊，例如在 publiccode.yml 檔案中。"
+msgstr "確保中介資料包含合適的聯絡資訊，例如寫在 publiccode.yml 檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 18 (unordered list)
 msgid ""
@@ -2911,7 +2942,8 @@ msgid ""
 "potential new collaborators will find it. Just publishing a codebase and "
 "hoping it is found does not work, instead proactiveness is needed."
 msgstr ""
-"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必須主動積極。"
+"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到"
+"它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，更需要主動積極。"
 
 #: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
 msgid ""
@@ -2928,35 +2960,38 @@ msgstr ""
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。"
+msgstr "代碼庫名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語"
+"，或組織單位品牌名稱或抬頭等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a short description that helps someone understand "
 "what the codebase is for or what it does."
-msgstr "代碼庫說明應該要簡短，幫助他人瞭解代碼庫的性質與作用。"
+msgstr "代碼庫說明「應該」要簡短，幫助他人瞭解代碼庫的目的與作用。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr "維護人員應該將代碼庫提交至相關的軟體目錄上。"
+msgstr "維護人員「應該」將代碼庫提交至相關的軟體目錄上。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr "代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
+msgstr "代碼庫「應該」要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、"
+"管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by codebase name."
-msgstr "在搜尋引擎查找代碼庫名稱時，應該能搜尋得到代碼庫。"
+msgstr "在搜尋引擎查找代碼庫名稱時，「應該」能搜尋得到代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by describing the "
 "problem it solves in natural language."
-msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼庫。"
+msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，「應該」能搜尋得到"
+"代碼庫。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -2964,7 +2999,8 @@ msgid ""
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
 msgstr ""
-"代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。"
+"代碼庫「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../g"
+"lossary.md#repository)、位置、網站等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -2972,15 +3008,16 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
-"代碼庫應該包含機器可讀的中介資料說明，例如採用[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。"
+"代碼庫「應該」包含機器可讀的中介資料說明，例如採用[publiccode."
+"yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr "可選擇是否為代碼庫設定專用的網域名稱。"
+msgstr "「可選擇」是否為代碼庫設置專用的網域名稱。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Regular presentations at conferences by the community are OPTIONAL."
-msgstr "可選擇是否在社群舉辦的會議中定期進行簡報。"
+msgstr "「可選擇」是否在社群舉辦的會議中定期進行簡報。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check that the codebase name is descriptive and free of puns."
@@ -2991,13 +3028,15 @@ msgid ""
 "Check that the codebase name is free of acronyms and abbreviations or that "
 "the acronyms or abbreviations in the name are more universally known than "
 "the longer forms."
-msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整名稱更熟為人知。"
+msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完"
+"整名稱更熟為人知。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of organizational branding, unless that"
 " organization is of the codebase community itself."
-msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員）。"
+msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是代碼庫社群成"
+"員。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3018,14 +3057,16 @@ msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by the codebase name."
-msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。"
+msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將代碼庫列在搜"
+"尋結果中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by using natural language, for instance, using the "
 "short description."
-msgstr "檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。"
+msgstr "檢查以自然語言來作搜尋，例如使用代碼庫的簡短描述時，有超過一個的常用主流搜尋"
+"引擎，都將代碼庫放在搜尋結果中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3051,19 +3092,19 @@ msgstr "檢查中介資料說明檔案是機器可讀的格式。"
 msgid ""
 "Contribute a description of the policy area or problem this codebase acts on"
 " or operates."
-msgstr "貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。"
+msgstr "貢獻一段說明此代碼庫作用的政策領域，或處理的問題的描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Test your problem description with peers outside of your context who aren't "
 "familiar with the codebase."
-msgstr "請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。"
+msgstr "請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Present on how the codebase implements the [policy](../glossary.md#policy) "
 "at relevant conferences."
-msgstr "在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。"
+msgstr "在相關會議上作簡報，介紹代碼庫如何執行[政策](../glossary.md#policy)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
@@ -3075,7 +3116,7 @@ msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as social media account descriptions."
-msgstr "使用簡短描述說明參照代碼庫的地方，例如社群媒體帳號說明。"
+msgstr "在引用到代碼庫的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
@@ -3085,19 +3126,19 @@ msgstr "為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Make sure people involved in the project present at relevant conferences."
-msgstr "確保專案參與人員出席相關會議或作簡報介紹。"
+msgstr "確保專案參與人員出席相關會議，或作簡報介紹。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid ""
 "Search engine optimization, for instance adding a "
 "[sitemap](https://www.sitemaps.org/protocol.html)."
-msgstr "搜尋引擎最佳化，例如新增[網站地圖](https://www.sitemaps.org/protocol.html)。"
+msgstr "搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol.html)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as the repository description."
-msgstr "在參照代碼庫的地方，都使用簡短描述，例如儲存庫的說明。"
+msgstr "在引用到代碼庫的地方，都使用簡短描述，例如放到儲存庫中的說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid "Suggest conferences to present at and present at them."
@@ -3146,7 +3187,7 @@ msgstr "criteria/create-reusable-and-portable-code"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
 msgid "Make the codebase reusable and portable"
-msgstr "使代碼庫可重複使用且具可攜性"
+msgstr "代碼庫要可重複使用且可移植"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
 msgid ""
@@ -3155,7 +3196,9 @@ msgid ""
 "improve it and contribute those improvements back, leading to better "
 "quality, cheaper maintenance and higher reliability."
 msgstr ""
-"編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。"
+"編寫可重複使用且可移植的[程式碼](../glossary.md#code)，讓政策制定者、開發人員"
+"與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，"
+"如此可提高品質、降低維護成本、增強可靠性。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
 msgid ""
@@ -3165,7 +3208,9 @@ msgid ""
 " developed and used by multiple parties are more likely to benefit from a "
 "self-sustaining community."
 msgstr ""
-"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從能自我運作的社群中獲益。"
+"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方共享代"
+"碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫，更可以從能自我運作的社"
+"群中獲益。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
 msgid ""
@@ -3174,7 +3219,8 @@ msgid ""
 "[another context](../glossary.md#different-contexts) if its purpose is "
 "clearly documented."
 msgstr ""
-"以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情境](../glossary.md#different-"
+"以文件記錄周全的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄"
+"用途的模組，更容易在[另一種情境](../glossary.md#different-"
 "contexts)中重複利用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
@@ -3182,69 +3228,72 @@ msgid ""
 "Source code which does not rely on the situation-specific infrastructure of "
 "any contributor, vendor or deployment can be tested by any other "
 "contributor."
-msgstr "如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都能測試該原始碼。"
+msgstr "原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢"
+"獻者都能測試該原始碼。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase MUST be developed to be reusable in different contexts."
-msgstr "代碼庫必須開發成能在不同情境中重複使用。"
+msgstr "代碼庫「必須」開發成能在不同情境中重複使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed software or services for execution and understanding."
-msgstr "執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程式碼或服務。"
+msgstr "代碼庫「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，"
+"以供執行與瞭解。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be in use by multiple parties."
-msgstr "代碼庫應該有多方單位使用。"
+msgstr "代碼庫「應該」有多方單位使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
-msgstr "發展路線圖應該有多方單位的需求影響。"
+msgstr "發展路線圖「應該」有多方單位的需求影響。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The development of the codebase SHOULD be a collaboration between multiple "
 "parties."
-msgstr "代碼庫開發應該由多方單位合作。"
+msgstr "代碼庫開發「應該」由多方單位協作。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Configuration SHOULD be used to make [source code](../glossary.md#source-"
 "code) adapt to context specific needs."
-msgstr "應該使用組態設定方式以將[程式碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。"
+msgstr "「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code) "
+"調整成能適應各情境的特定需求。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be localizable."
-msgstr "代碼庫應該能夠在地化。"
+msgstr "代碼庫「應該」能夠在地化。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Source code and its documentation SHOULD NOT contain situation-specific "
 "information."
-msgstr "原始碼與其文件不應該包含特定情況專用的資訊。"
+msgstr "原始碼與其文件「不應該」包含特定情況專用的資訊。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr "代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。"
+msgstr "代碼庫模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The software SHOULD NOT require services or platforms available from only a "
 "single vendor."
-msgstr "軟體不應該要求只有單一供應商能提供的服務或平台。"
+msgstr "軟體「不應該」要求僅有單一供應商能提供的服務或平台。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3258,33 +3307,34 @@ msgstr "與另一組織單位角色與您相似的人確認，看他們是否能
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed software or services."
-msgstr "確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。"
+msgstr "確認代碼庫不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "If the codebase is in early development before a production-ready release, "
 "then check for evidence of ambition to obtain collaborators."
-msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願。"
+msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意"
+"圖跡象。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Or if the codebase is very mature and stable with very infrequent fixes, "
 "patches, or contributions:"
-msgstr "或是如果代碼庫非常成熟與穩定，鮮少需要修復或貢獻："
+msgstr "或是如果代碼庫非常成熟與穩定，鮮少需要修正、改善或貢獻："
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the codebase is in use by multiple parties or in multiple "
 "contexts."
-msgstr "檢查是否有多方單位或是有在多種情境下正使用代碼庫。"
+msgstr "檢查是否有多方單位，或是有在多種情境下正使用代碼庫。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid "Check for documented and budgeted commitments of collaboration."
-msgstr "檢查是否有文件記錄下合作的承諾以及承諾的預算。"
+msgstr "檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3301,7 +3351,7 @@ msgstr "檢查代碼庫貢獻者是否來自多方單位。"
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr "檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。"
+msgstr "檢查代碼庫檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3325,7 +3375,7 @@ msgstr "確保代碼庫有將貴組織單位列為已知使用者。"
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid "Identify other organizations for your teams to collaborate with."
-msgstr "列出貴團隊想要合作的其他組織。"
+msgstr "找出貴團隊想要協作的其他組織單位。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
@@ -3338,7 +3388,7 @@ msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
 msgid "Make sure that your teams are collaborating with other teams."
-msgstr "確認您的團隊與其他團隊協作。"
+msgstr "確認您的團隊與其他團隊能相互協作。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
 msgid "Source should be designed:"
@@ -3373,14 +3423,17 @@ msgid ""
 "platforms or using proprietary components, make sure that collaborators can "
 "develop, use, test, and deploy without them."
 msgstr ""
-"確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行開發、使用、測試、部署等。"
+"確保代碼庫文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要"
+"部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況"
+"下，就能進行開發、使用、測試、部署等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
 msgid ""
 "For each commit, reviewers verify that content does not include situation-"
 "specific data such as hostnames, personal and organizational data, or tokens"
 " and passwords."
-msgstr "在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。"
+msgstr "在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
+"人與組織單位資料、代符與密碼等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
 #: list)
@@ -3421,50 +3474,54 @@ msgid ""
 "[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
 "emerge around the codebase."
 msgstr ""
-"有了開放且熟為人知的授權，任何人都可以看到[原始碼](../glossary.md#source-"
-"code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼庫](../glossary.md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。"
+"採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-"
+"code)，使其能瞭解運作方式、自由使用，並且能為[代碼庫](../glossary."
+"md#codebase)做出貢獻。這也能促進供應商建立出以代碼庫為中心的生態系。"
 
 #: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
 msgid ""
 "Clearly indicating the license for each file within a codebase facilitates "
 "correct reuse and attribution of parts of a codebase."
-msgstr "明確標示代碼庫中每一個檔案的授權，幫助使用者正確重複利用與引用代碼庫的內容。"
+msgstr "明確指出代碼庫中每一個檔案的授權，讓使用者能正確重複利用代碼庫的部分內容，並"
+"表彰作者名稱。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "All source code and documentation MUST be licensed such that it may be "
 "freely reusable, changeable and redistributable."
-msgstr "所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。"
+msgstr "所有原始碼與文件，皆「必須」採用使其得以自由重複使用、自由修改、自由再次散布"
+"的授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Software source code MUST be licensed under an [OSI-approved or FSF "
 "Free/Libre license](https://spdx.org/licenses/)."
 msgstr ""
-"軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"軟體原始碼「必須」採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
 "自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid "All source code MUST be published with a license file."
-msgstr "所有程式碼皆必須搭配授權條款檔案一併發行。"
+msgstr "所有原始碼皆「必須」搭配授權條款檔案一併發行。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the codebase."
-msgstr "禁止要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
+msgstr "「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr "代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。"
+msgstr "代碼庫中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容"
+"。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "Having multiple licenses for different types of source code and "
 "documentation is OPTIONAL."
-msgstr "可選擇是否為不同類型的原始碼與文件採用多重授權條款。"
+msgstr "「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the codebase is clearly licensed."
@@ -3511,13 +3568,13 @@ msgstr ""
 msgid ""
 "Develop policy that disincentivizes non-open source code and technology in "
 "procurement."
-msgstr "制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。"
+msgstr "制定抑制採購非開放原始碼授權程式碼，與非開放科技的政策。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
 "Only work with open source vendors that deliver their source code by "
 "publishing it under an open source license."
-msgstr "只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。"
+msgstr "只與能採用開放原始碼授權，交付與發行其原始碼的開放原始碼軟體供應商合作。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
@@ -3543,7 +3600,7 @@ msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授
 msgid ""
 "When source code is being reused by the codebase, make sure that it has a "
 "license that is compatible with the license or licenses of the codebase."
-msgstr "代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。"
+msgstr "當代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3558,9 +3615,8 @@ msgid ""
 "Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
 "Creative Commons Aotearoa New Zealand."
 msgstr ""
-"紐西蘭 CC "
-"Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/videos/creative-"
-"commons-kiwi)》。"
+"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)》。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3596,7 +3652,8 @@ msgid ""
 "Peer-review of contributions is essential for [source "
 "code](../glossary.md#source-code) quality, reducing security risks and "
 "operational risks."
-msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-code)品質的關鍵，降低安全性風險與營運風險。"
+msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-"
+"code)提升品質的關鍵，也能降低安全性風險與營運風險。"
 
 #: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
 msgid ""
@@ -3607,7 +3664,10 @@ msgid ""
 "Knowing that all source code was reviewed discourages a culture of blaming "
 "individuals, and encourages a culture of focusing on solutions."
 msgstr ""
-"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發現與修復潛在錯誤的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。"
+"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始"
+"碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，就發現與修正潛在臭"
+"蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反"
+"倒是鼓勵每個人都專注在解決方案上。"
 
 #: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
 msgid ""
@@ -3615,63 +3675,64 @@ msgid ""
 "a guaranteed time for feedback or collaborative improvement, which increases"
 " both rate of delivery and contributor engagement."
 msgstr ""
-"快速審查的[政策](../glossary.md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， "
-"進而提高貢獻者交付貢獻內容的頻率以及參與熱度。"
+"快速審查[政策](../glossary.md#policy)在於向貢獻者保證，必定在一段時間內提供意"
+"見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參與的熱度。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "codebase MUST be reviewed by another contributor."
-msgstr "所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。"
+msgstr "所有被接受或是送交給代碼庫正式發行版本中的貢獻內容，都「必須」經過另一位貢獻"
+"者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews MUST include source, policy, tests and documentation."
-msgstr "審查必須包含原始碼、政策、測試與文件等。"
+msgstr "審查「必須」包含原始碼、政策、測試、文件等。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Reviewers MUST provide feedback on all decisions to not accept a "
 "contribution."
-msgstr "如果不接受貢獻內容，審查人員必須提供意見回饋。"
+msgstr "如果不接受貢獻內容，審查人員「必須」提供意見回饋。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "The review process SHOULD confirm that a contribution conforms to the "
 "standards, architecture and decisions set out in the codebase in order to "
 "pass review."
-msgstr "審查流程應該確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。"
+msgstr "審查流程「應該」確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Reviews SHOULD include running both the software and the tests of the "
 "codebase."
-msgstr "審查內容應該包含執行軟體與執行代碼庫測試。"
+msgstr "審查內容「應該」包含執行軟體與執行代碼庫測試。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Contributions SHOULD be reviewed by someone in a different context than the "
 "contributor."
-msgstr "貢獻內容應該由與貢獻者不同背景情境的人來審查。"
+msgstr "貢獻內容「應該」由與貢獻者不同背景情境的人來審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr "版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
+msgstr "版本控制系統「不應該」在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
-msgstr "審查應該在兩個工作天內進行。"
+msgstr "審查「應該」在兩個工作天內進行。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Performing reviews by multiple reviewers is OPTIONAL."
-msgstr "可選擇是否由多位審查人員進行審查。"
+msgstr "「可選擇」是否由多位審查人員進行審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Confirm that every commit in the history has been reviewed by a different "
 "contributor."
-msgstr "確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。"
+msgstr "確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Confirm that reviews include source, policy, tests and documentation."
@@ -3685,17 +3746,17 @@ msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
 msgid ""
 "Check if guidelines for reviewers include instructions to review for "
 "conformance to standards, architecture and codebase guidelines."
-msgstr "檢查審查人員指引有涵蓋是否遵循標準、架構、代碼庫指引等。"
+msgstr "檢查審查人員指引中，有包含是否遵循標準、架構、代碼庫指引等指示。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Check with reviewers if they run the software and tests during review."
-msgstr "檢查審查人員在審查時是否有執行程式與測試。"
+msgstr "檢查審查人員在審查時是否有執行軟體與測試。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
 "Check with reviewers if commits have been reviewed by a different "
 "contributor in a different context."
-msgstr "與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。"
+msgstr "與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid ""
@@ -3711,7 +3772,7 @@ msgstr "檢查貢獻提交與審查之間的時間間隔。"
 msgid ""
 "Institute a 'four eyes' policy where everything, not just source code, is "
 "reviewed."
-msgstr "制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。"
+msgstr "制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。"
 
 #: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
 msgid ""
@@ -3749,7 +3810,7 @@ msgstr "請代碼庫的其他貢獻者，審查您在貴組織單位內外的工
 msgid ""
 "Try to respond to others' requests for review promptly, initially providing "
 "feedback about the concept of the change."
-msgstr "當他人請求您審查時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。"
+msgstr "當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。"
 
 #: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
 msgid ""
@@ -3809,7 +3870,8 @@ msgid ""
 "Following a consistent and coherent style enables contributors in different "
 "environments to work together. Unifying vocabularies reduces friction in "
 "communication between contributors."
-msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝通上的摩擦。"
+msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠一同合作。用詞統一能減少貢獻者之間"
+"在溝通上的摩擦。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
@@ -3817,24 +3879,26 @@ msgid ""
 "guide, either the codebase community's own or an existing one referred to in"
 " the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指引、或文件寫作風格指"
-"引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用的既有風格。"
+"[代碼庫](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作風"
+"格指引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用的既有風格。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
-msgstr "貢獻內容應該通過自動化的風格測試。"
+msgstr "貢獻內容「應該」通過自動化的風格測試。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
 "The style guide SHOULD include expectations for inline comments and "
 "documentation for non-trivial sections."
-msgstr "風格指引應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。"
+msgstr "風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與寫下說明文件的期"
+"待。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
 "Including expectations for [understandable English](use-plain-english.md) in"
 " the style guide is OPTIONAL."
-msgstr "可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指引之中。"
+msgstr "「可選擇」是否將[可理解的白話英語](use-plain-english."
+"md)期望加入風格指引之中。"
 
 #: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
 msgid ""
@@ -3878,8 +3942,8 @@ msgstr ""
 "epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
 "前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
 "以及機器不容易檢查的其他層面。指引應該包含貢獻的[原始碼](../glossary.md"
-"#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試"
-"、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
+"#source-code)預期該符合哪些要求，才會被維護人員合併至代碼庫中，包括原始碼、測"
+"試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
 
 #: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
 msgid "Additionally:"
@@ -3887,11 +3951,11 @@ msgstr "此外："
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Use a linter."
-msgstr "使用程式碼品質分析工具 (linter)。"
+msgstr "使用程式碼品質梳理工具 (linter)。"
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入程式碼品質分析工具的組態設定。"
+msgstr "在代碼庫中加入程式碼品質梳理工具的組態設定。"
 
 #: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
 msgid ""
@@ -3918,7 +3982,8 @@ msgid ""
 " merging and the smaller the contribution, the easier it is to resolve merge"
 " conflicts."
 msgstr ""
-"開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易解決。"
+"透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同"
+"步協作。合併的頻率越頻繁，貢獻的規模越小，在合併時所發生的衝突就越容易解決。"
 
 #: ./criteria/use-continuous-integration.md:block 7 (paragraph)
 msgid ""
@@ -3928,7 +3993,8 @@ msgid ""
 " The more focused the test, the easier it is to clearly identify and "
 "understand errors as they arise."
 msgstr ""
-"自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。"
+"自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓"
+"審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。"
 
 #: ./criteria/use-continuous-integration.md:block 8 (paragraph)
 msgid ""
@@ -3937,61 +4003,62 @@ msgid ""
 "contributions. Continuous integration allows for an easier monitoring of the"
 " state of the [codebase](../glossary.md#codebase)."
 msgstr ""
-"以文件記錄代碼庫的[持續整合](../glossary.md#continuous-"
-"integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。透過持續整合可以更輕易地監督 "
-"[代碼庫](../glossary.md#codebase)狀態。"
+"以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，"
+"能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監督[代碼庫](../glossary."
+"md#codebase)狀態變得更為簡單。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "All functionality in the [source code](../glossary.md#source-code) MUST have"
 " automated tests."
-msgstr "[原始碼](../glossary.md#source-code)中的所有功能都必須有自動化測試。"
+msgstr "[原始碼](../glossary.md#source-code)中的所有功能，都「必須」有自動化測試。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Contributions MUST pass all automated tests before they are admitted into "
 "the codebase."
-msgstr "所有貢獻內容都必須先通過自動化測試，才能上傳至代碼庫。"
+msgstr "所有貢獻內容都「必須」先通過自動化測試，才能上傳至代碼庫。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have guidelines explaining how to structure contributions."
-msgstr "代碼庫必須有說明貢獻內容結構的相關準則。"
+msgstr "代碼庫「必須」有解說如何撰寫貢獻內容結構的相關指引。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have active contributors who can review contributions."
-msgstr "代碼庫必須有能夠審查貢獻內容的活躍貢獻者。"
+msgstr "代碼庫「必須」有能夠審查貢獻內容的活躍貢獻者。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Automated test results for contributions SHOULD be public."
-msgstr "應該公開貢獻的自動化測試結果。"
+msgstr "「應該」公開貢獻內容的自動化測試結果。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr "代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。"
+msgstr "代碼庫指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr "應該監督原始碼測試與文件的涵蓋範圍。"
+msgstr "「應該」監督原始碼測試與文件的涵蓋範圍。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing [policy](../glossary.md#policy) and documentation for consistency "
 "with the source and vice versa is OPTIONAL."
-msgstr "可選擇是否測試[政策](../glossary.md#policy)和文件，與原始碼間有無一致性，或是反之亦然。"
+msgstr "「可選擇」是否測試[政策](../glossary."
+"md#policy)和文件，與原始碼之間有無一致性，或是反之亦然。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing policy and documentation for style and broken links is OPTIONAL."
-msgstr "可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。"
+msgstr "「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "Testing the software by using examples in the documentation is OPTIONAL."
-msgstr "可選擇是否使用文件範例來測試軟體。"
+msgstr "「可選擇」是否使用文件中的範例來測試軟體。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid "Confirm that there are tests present."
@@ -4012,7 +4079,7 @@ msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
 "Confirm that contribution guidelines explain how to structure contributions."
-msgstr "確認有貢獻準則說明貢獻內容的結構。"
+msgstr "確認有貢獻指引解說如何撰寫貢獻內容的結構。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
@@ -4025,7 +4092,7 @@ msgstr "檢查是否可以查看測試結果。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid "Check if source code coverage data is published."
-msgstr "檢查是否已經公佈原始碼覆蓋率數據。"
+msgstr "檢查是否有公布原始碼覆蓋率數據。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
@@ -4040,13 +4107,14 @@ msgstr "確保政策文件也有設好自動化測試。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid "Fix policy documentation promptly if it fails a test."
-msgstr "如果政策文件未能通過測試，請立即修正。"
+msgstr "如果政策文件未能通過測試，請快速修正。"
 
 #: ./criteria/use-continuous-integration.md:block 14 (unordered list)
 msgid ""
 "Make sure the source code reflects any changes to the policy (see [Maintain "
 "version control](maintain-version-control.md))."
-msgstr "確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-control.md)）。"
+msgstr "確保原始碼能反映出政策的任何變動（請參閱〈[維護版本控制](maintain-version-"
+"control.md)〉）。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
@@ -4075,7 +4143,7 @@ msgstr "發生重大失誤後，鼓勵公開事故報告，以及公開討論事
 msgid ""
 "Help managers structure the work plan such that it can be integrated as "
 "small increments."
-msgstr "協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。"
+msgstr "協助管理人員擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
@@ -4097,7 +4165,8 @@ msgid ""
 "of storage space and memory allocation failure are typical examples of "
 "difficult to create conditions."
 msgstr ""
-"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。"
+"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
+"來。例如硬碟空間不足、記憶體分配失敗等資源耗盡情況，都是難以創造的典型案例。"
 
 #: ./criteria/use-continuous-integration.md:block 18 (unordered list)
 msgid ""
@@ -4162,7 +4231,9 @@ msgid ""
 "exchange."
 msgstr ""
 "[開放標準](../glossary.md#open-"
-"standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的知識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明確，就可以獨立發展任何方向的資料交換。"
+"standard)保證可以取得使用與貢獻[代碼庫](../glossary.md#codebase)所需的知識。"
+"不僅能為不同的系統之間建立互通性，更降低廠商套牢的可能性。開放標準如果明確，"
+"不同方就可以各自獨立開發作資料交換。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4170,43 +4241,45 @@ msgid ""
 "codebase MUST use an open standard that meets the [Open Source Initiative "
 "Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
-"代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。"
+"代碼庫如要促進資料交換的特性，就「必須」採用符合[OSI "
+"開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any non-open standards used MUST be recorded clearly as such in the "
 "documentation."
-msgstr "如果有使用到任何的非開放標準，則必須在文件中清楚記錄。"
+msgstr "如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr "代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。"
+msgstr "代碼庫選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標"
+"準的連結。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr "代碼庫採用的任何非開放標準，皆禁止妨礙代碼庫的協作與重複使用。"
+msgstr "代碼庫選擇採用的任何非開放標準，皆「禁止」妨礙代碼庫的協作與重複使用。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "If no existing open standard is available, effort SHOULD be put into "
 "developing one."
-msgstr "如果還沒有已存在的開放標準可採用，則應該投入開發新標準。"
+msgstr "如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Open standards that are machine testable SHOULD be preferred over open "
 "standards that are not."
-msgstr "採用開放標準時，應該優先選擇可經機器測試的開放標準。"
+msgstr "採用開放標準時，「應該」優先選擇可經機器測試的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Non-open standards that are machine testable SHOULD be preferred over non-"
 "open standards that are not."
-msgstr "採用非開放標準時，應該優先選擇可經機器測試的非開放標準。"
+msgstr "採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。"
 
 #: ./criteria/use-open-standards.md:block 10 (unordered list)
 msgid "Confirm that data exchange follows an OSI approved open standard."
@@ -4226,7 +4299,7 @@ msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
-msgstr "以政策要求盡可能在任何情況下使用開放標準。"
+msgstr "以政策要求盡可能在任何情況下採用開放標準。"
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Prohibit procurement of technology that does not use open standards."
@@ -4249,7 +4322,8 @@ msgid ""
 "Review the commits and other [repository](../glossary.md#repository) "
 "resources for references to standards and cross-check those with the "
 "standards listed."
-msgstr "審查提交紀錄與其他[儲存庫](../glossary.md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
+msgstr "審查送交版次與[儲存庫](../glossary."
+"md#repository)其他資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
 
 #: ./criteria/use-open-standards.md:block 18 (unordered list)
 msgid ""
@@ -4271,31 +4345,33 @@ msgstr "criteria/understandable-english-first"
 
 #: ./criteria/use-plain-english.md:block 5 (header)
 msgid "Use plain English"
-msgstr "使用白話的英文"
+msgstr "使用白話的英語"
 
 #: ./criteria/use-plain-english.md:block 6 (paragraph)
 msgid ""
 "English is the <i>de facto</i> language of collaboration in software "
 "development."
-msgstr "英文是軟體開發的 <i>慣用</i>協作語言。"
+msgstr "英語是軟體開發領域中的<i>實際</i>協作語言。"
 
 #: ./criteria/use-plain-english.md:block 7 (paragraph)
 msgid ""
 "Public sector information needs to be accessible to all its constituents. "
 "Plain and simple language makes the [code](../glossary.md#code) and what it "
 "does easier to understand for a wider variety of people."
-msgstr "選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。"
+msgstr "公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，讓更多人能瞭解[程式碼]("
+"../glossary.md#code)與其功用。"
 
 #: ./criteria/use-plain-english.md:block 8 (paragraph)
 msgid ""
 "Translations further increase the possible reach of a "
 "[codebase](../glossary.md#codebase). Language that is easy to understand "
 "lowers the cost of creating and maintaining translations."
-msgstr "透過翻譯可以讓更多人認識[代碼庫](../glossary.md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。"
+msgstr "翻譯可以讓更多人有機會認識[代碼庫](../glossary."
+"md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid "All codebase documentation MUST be in English."
-msgstr "代碼庫的所有文件都必須使用英語。"
+msgstr "代碼庫的所有文件都「必須」使用英語。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4309,12 +4385,12 @@ msgstr ""
 msgid ""
 "All bundled policy not available in English MUST have an accompanying "
 "summary in English."
-msgstr "任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。"
+msgstr "任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "Any translation MUST be up to date with the English version and vice versa."
-msgstr "任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。"
+msgstr "任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4322,7 +4398,8 @@ msgid ""
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
 msgstr ""
-"代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
+"代碼庫中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；"
+"如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4336,7 +4413,7 @@ msgstr ""
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
 "Providing a translation of any code, documentation or tests is OPTIONAL."
-msgstr "可選擇是否提供任何程式碼、文件、測試等的翻譯版。"
+msgstr "「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
@@ -4406,9 +4483,9 @@ msgid ""
 "Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
 "readable and understandable."
 msgstr ""
-"根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1 與 3.1 "
+"符合 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1、3.1 "
 "之可讀性](https://www.w3.org/TR/WCAG21/"
-"#readable)》內文，撰寫的文字內容要更容易閱讀與理解。"
+"#readable)》要求，撰寫的文字內容要容易閱讀與理解。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4416,8 +4493,9 @@ msgid ""
 "single-market/en/web-accessibility) by the European Commission, is an "
 "example of regulation requiring high accessibility."
 msgstr ""
-"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/digital-single-market/en/web-"
-"accessibility)》就是無障礙法規的例子。"
+"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/"
+"digital-single-market/en/web-"
+"accessibility)》，是高度要求無障礙環境的法規範例。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4448,52 +4526,56 @@ msgid ""
 " communities. Newcomers need to understand and trust the codebase "
 "community’s governance."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 "
-"歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當中，若貢獻者有明確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並且相信代碼庫社群的治理。"
+"[代碼庫](../glossary.md#codebase)的社群氛圍會影響使用者選擇所要使用的代碼庫。"
+"歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。若貢獻者有明確的"
+"方法可以影響代碼庫、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新"
+"參與者需要瞭解並信任代碼庫社群的治理方式。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST allow anyone to submit suggestions for changes to the "
 "codebase."
-msgstr "代碼庫必須允許任何人針對代碼庫提出修改建議。"
+msgstr "代碼庫必須「允許」任何人對代碼庫提出修改建議。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr "代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。"
+msgstr "代碼庫「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發"
+"，例如以「`CONTRIBUTING`」檔案說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr "代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。"
+msgstr "代碼庫「必須」以文件記錄代碼庫、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
+"RNANCE`」檔案來說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The contribution guidelines SHOULD document who is expected to cover the "
 "costs of reviewing contributions."
-msgstr "貢獻指引應該說明由誰負責審查貢獻的成本。"
+msgstr "貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr "代碼庫應該宣布投入其開發與維護工作的參與組織單位。"
+msgstr "代碼庫「應該」宣布投入其開發與維護工作的參與組織單位。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr "代碼庫應該要有可公開取得的發展路線圖。"
+msgstr "代碼庫「應該」要有可公開取得的發展路線圖。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD publish codebase activity statistics."
-msgstr "代碼庫應該公布代碼庫的活動統計數據。"
+msgstr "代碼庫「應該」公布代碼庫的活動統計數據。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr "可選擇是否為代碼庫加入貢獻者的行為準則。"
+msgstr "「可選擇」是否為代碼庫加入貢獻者的行為守則。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
@@ -4509,13 +4591,13 @@ msgstr "確認代碼庫有貢獻指引。"
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr "確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。"
+msgstr "確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理的方法。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Check that contributing guidelines cover who is expected to cover the costs "
 "of reviewing contributions."
-msgstr "確認貢獻指引是否有說明由誰負責審查貢獻的成本。"
+msgstr "確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for a list of involved organizations."
@@ -4531,7 +4613,7 @@ msgstr "檢查是否有公布活動統計數據。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Check for a code of conduct."
-msgstr "檢查是否有行為準則。"
+msgstr "檢查是否有行為守則。"
 
 #: ./criteria/welcome-contributors.md:block 12 (unordered list)
 msgid ""
@@ -4563,7 +4645,7 @@ msgstr "如果社群對於治理架構應該如何改變有共識，則應該將
 msgid ""
 "If needed, make sure you have allocated budget for the contributions review "
 "process as agreed by the codebase community."
-msgstr "若有需要，確保如同代碼庫社群所同意的，編列貢獻審查流程的預算。"
+msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且通過代碼庫社群同意。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
@@ -4585,7 +4667,7 @@ msgstr "快速回應請求。"
 msgid ""
 "Communicate clearly to contributors what they need to do make sure their "
 "contribution can be integrated."
-msgstr "清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式碼中。"
+msgstr "清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到代碼庫中。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4610,7 +4692,7 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
-"開放原始碼指引為成長中的[開放原始碼](../glossary.md#open-"
+"《開放原始碼指引》針對推動[開放原始碼](../glossary.md#open-"
 "source)社群專案所寫的《[領導與治理](https://opensource.guide/"
 "leadership-and-governance/)》。"
 
@@ -4630,22 +4712,22 @@ msgid ""
 "tries to provide the relevant information to print it there or somewhere "
 "else."
 msgstr ""
-"The Standard for Public Code 由 Reclameland "
-"負責印刷。本指引提供印刷相關資訊，方便在 Reclameland 或其他地方印刷。"
+"Standard for Public Code 是由 Reclameland "
+"負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
 "Details, mostly in order they are on the Reclameland page with the Dutch if "
 "necessary:"
-msgstr "印刷詳細資訊（依照 Reclameland 網頁上的順序，需要的地方有附上荷蘭語）："
+msgstr "印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）："
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid ""
 "Form: Softcover book ([Reclameland product "
 "page](https://www.reclameland.nl/drukken/softcover-boeken))"
 msgstr ""
-"樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/softcover-"
-"boeken))"
+"樣式：平裝書 ([Reclameland 產品頁面](https://www.reclameland.nl/drukken/"
+"softcover-boeken))"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Format: A4"
@@ -4653,7 +4735,7 @@ msgstr "紙張尺寸：A4"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Portrait or landscape: Portrait (Staand)"
-msgstr "直橫向：直向（Staand）"
+msgstr "直向或橫向：直向 (Staand)"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing inside: 4/4 dual sided full color"
@@ -4665,21 +4747,21 @@ msgstr "內頁材質：Biotop 90克"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover: 350 grams cover"
-msgstr "封面：350克封面"
+msgstr "封面：350 克封面"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing cover: 4/0 one sided full cover"
-msgstr "封面印刷：正四（單面滿版印刷）"
+msgstr "封面印刷：正四反空，單面滿版印刷"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover treatment: one sided matt foliated (Enke)"
-msgstr "封面材質：單面霧面立體字封面（Enke）"
+msgstr "封面處理：單面霧面層剝處理 (Enke)"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid ""
 "Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
 " multiple of 4"
-msgstr "頁數：書內頁數 + 4 + x，x 是 0-3頁，因此總頁數是4的倍數"
+msgstr "頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Individually sealed: no"
@@ -4694,19 +4776,19 @@ msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
-msgstr "發行新版本的 The Standard for Public Code"
+msgstr "發行新版本的 Standard for Public Code"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Review state of the 'develop' branch"
-msgstr "審查「develop」分支狀態"
+msgstr "審查「develop」分支的狀態"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Ensure all changes intended for release are merged"
-msgstr "確保該版本的內容都已經完成合併"
+msgstr "確認預計收入該次發行版的所有變更都已完成合併"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Invite a proofread of the current state of the branch"
-msgstr "請人校對目前的分支狀態"
+msgstr "邀請校對該分支目前的狀態"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
@@ -4716,28 +4798,31 @@ msgid ""
 " truly the best expression of ideas, then follow the [Chicago Manual of "
 "Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
 msgstr ""
-"如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達該句子的涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)。"
+"如果有引入新的破折號，檢查是否能簡化文字並且移除破折號，例如改用較簡易的句子"
+"。如果需要用到複雜的句子，檢查是否能用其他標點符號來取代破折號。如果破折號最"
+"適合用來表達該句子的涵義，則請遵守《[芝加哥格式手冊](https://en.wikipedia."
+"org/wiki/Dash#En_dash_versus_em_dash)》的規範。"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create a release branch"
-msgstr "建立發佈分支"
+msgstr "建立發行用分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
-msgstr "從 'develop'、`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr "從「develop」分支下指令，`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
-msgstr "推動分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+msgstr "推送分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update the new release"
-msgstr "更新新版本"
+msgstr "更新本次新發行"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
-msgstr "更新 `_config.yml`、`README.md` 與 `publiccode.yml` 的版本編號"
+msgstr "更新 `_config.yml`、`README.md` 與 `publiccode.yml` 中的版本編號"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
@@ -4745,105 +4830,110 @@ msgstr "使用 `script/make-version-badge.sh` 更新 `assets/version-badge.svg`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update releaseDate in `publiccode.yml`"
-msgstr "更新 `publiccode.yml` 當中的發行日期"
+msgstr "更新 `publiccode.yml` 當中的 releaseDate 日期"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
-msgstr "在[`AUTHORS.md`](../AUTHORS.md)加入新貢獻者資料"
+msgstr "在 [`AUTHORS.md`](../AUTHORS.md) 中加入新貢獻者的資料"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
-msgstr "更新[`CHANGELOG.md`](../CHANGELOG.md)"
+msgstr "更新 [`CHANGELOG.md`](../CHANGELOG.md)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Perform extra pass on diff to the 'main' branch"
-msgstr "在 diff 進行額外傳輸到 'main' 分支"
+msgstr "透過 diff 進行額外傳輸到「main」分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "run `script/generate-review-template.sh` and commit updated `docs/review-"
 "template.html`"
 msgstr ""
-"執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-template.html`"
+"執行 `script/generate-review-template.sh` 並送交更新後的 `docs/review-"
+"template.html` 版次記錄"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "update `docs/standard-for-public-code.md` with the new text from the review "
 "template, updating any status changes as a result"
-msgstr "用審查範本的新文字來更新 `docs/standard-for-public-code.md`，更新所有的狀態變更"
+msgstr "用審查範本中的新文字來更新 `docs/standard-for-public-code."
+"md`，根據成果更新所有的狀態變更"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Reread any section or paragraph to ensure wording changes still fit the "
 "whole and do not contain grammar or spelling errors"
-msgstr "重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼字錯誤"
+msgstr "重新檢查用字有變更的任何小節或段落，確保變更的字詞適合該整體內容，並且沒有文"
+"法或拼字錯誤"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
 " `script/ensure-font.sh`"
 msgstr ""
-"確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/ensure-"
-"font.sh`"
+"確認有安裝[字型](https://brand.publiccode.net/typography/)，請參見：`script/"
+"ensure-font.sh`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
-msgstr "使用 `script/pdf.sh rc1` 檢視渲染的 `.pdf`"
+msgstr "使用 `script/pdf.sh rc1` 檢查轉譯出的 `.pdf` 檔"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Ensure no link collisions exist"
-msgstr "確保沒有連結相衝的問題"
+msgstr "確認沒有連結相衝的問題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Check the page breaks, possibly removing or adding page-break CSS, for "
 "example: `<p style=\"page-break-after: always;\"></p>`"
-msgstr "移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style=\"page-break-after: always;\"></p>`"
+msgstr ""
+"檢查文字分頁之處，可能需要移除或新增 CSS 分頁語法，像是：`<p style=\"page-"
+"break-after: always;\"></p>`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "If needed, commit fixes and repeat extra pass"
-msgstr "若需要，進行修復並且重複進行額外傳輸"
+msgstr "如果有需要，送交修正版次，並重複進行額外傳輸"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push branch, open a pull request to the 'main' branch"
-msgstr "推動分支，對 「'main'」分支提出拉入請求"
+msgstr "推送分支，對 「main」分支提出拉取請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Request review from multiple reviewers, especially a proofreader"
-msgstr "要求多位審查人員（特別是校對人員）進行審查"
+msgstr "請多位審查人員（特別是校對人員）進行審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Reviewers will create issues for shortcomings found which would not prevent "
 "release"
-msgstr "審查人員若有發現不會影響發行的缺失，則會建立議題"
+msgstr "審查人員若發現不會阻礙發行的缺失，則會建立議題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "If needed for release, reviewers may create pull requests to resolve issues"
-msgstr "如果是發行所需，審查人員可以建立拉入請求來解決問題"
+msgstr "如果是發行所需處理的缺失，審查人員可以提交拉取請求來解決問題"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid ""
 "Re-request reviews if additional pull requests are merged into release "
 "branch"
-msgstr "若額外的拉入請求合併至發行分支，請要求重新審查"
+msgstr "若有額外的拉取請求合併至發行分支，則再次請求審查"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Run the to-archive-org.sh script"
-msgstr "執行「to-archive-org.sh」命令稿"
+msgstr "執行 to-archive-org.sh 命令稿"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Once reviews are complete, merge to 'main'"
-msgstr "審查完成後，合併至「'main'」"
+msgstr "當審查完成後，合併回「main」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Create GitHub release with the release notes and version number"
-msgstr "在 GItHub 上發行，並且附上發行說明與版本號碼"
+msgstr "在 GItHub 上發行，附上發行備註與版本編號"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Switch to the 'main' branch, `git pull` and `git status`"
-msgstr "切換至「'main'」分支、「`git pull`」與「`git status`」"
+msgstr "切換至「main」分支，`git pull` 然後 `git status`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "`git tag $MAJOR.$MINOR.$PATCH`"
@@ -4851,11 +4941,11 @@ msgstr "`git tag $MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
-msgstr "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
+msgstr "`git push --tags`（請參見：`../.github/workflows/release-on-tag.yml`）"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Trigger a rebuild of gh-pages"
-msgstr "觸發 gh-pages 的重建"
+msgstr "觸發 gh-pages 重建"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
@@ -4871,19 +4961,19 @@ msgstr "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Open a pull request from this branch to `main`"
-msgstr "從此分支向「'main'」提出拉入請求"
+msgstr "從此分支向「main」提出拉取請求"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Approve and merge PR (containing empty commit)"
-msgstr "核准與合併 PR （包含空白的提交版本）"
+msgstr "批准與合併 PR （包含空白的送交版次）"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Update 'develop' with a merge from 'main'"
-msgstr "用「'main'」的內容合併並且更新「'develop'」"
+msgstr "將「develop」透過合併更新「main」"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "[Send the files for print to the printer](printing.md)"
-msgstr "[將印刷檔案傳送至印刷廠](printing.md)"
+msgstr "[將檔案傳送給印刷廠商印刷](printing.md)"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Cover file"
@@ -4898,7 +4988,8 @@ msgid ""
 "Ping [translation](https://github.com/publiccodenet/community-translations-"
 "standard) contributors"
 msgstr ""
-"標記[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者"
+"通知[翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)貢獻者"
 
 #: ./docs/roadmap.md:block 1 (header)
 msgid "Roadmap"
@@ -5194,7 +5285,7 @@ msgstr "包容"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Usable"
-msgstr "可用"
+msgstr "好用"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Open"
@@ -5202,15 +5293,15 @@ msgstr "開放"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Legible"
-msgstr "清晰易讀"
+msgstr "易懂"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accountable"
-msgstr "負責"
+msgstr "可責"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accessible"
-msgstr "容易取得"
+msgstr "近用"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Sustainable"
@@ -5287,7 +5378,7 @@ msgstr "這可視為對未來經濟成長的投資。隨著科技需求成長，
 
 #: ./foreword.md:block 44 (header)
 msgid "Procuring public code"
-msgstr "採購公共程式"
+msgstr "育成公共程式"
 
 #: ./foreword.md:block 45 (paragraph)
 msgid ""
@@ -5307,24 +5398,24 @@ msgstr ""
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
-msgstr "The Standard for Public Code 目標"
+msgstr "Standard for Public Code 目標"
 
 #: ./foreword.md:block 48 (paragraph)
 msgid ""
 "This Standard supports developers, designers, managers and public policy "
 "makers to:"
-msgstr "The Standard for Public Code 支持開發人員、設計師、管理人員以及公共政策制定者："
+msgstr "本標準支持開發人員、設計師、管理人員、公共政策制定者："
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop high quality software and policy for better public service delivery"
-msgstr "開發優質軟體與政策，改善公共服務的交付"
+msgstr "開發高品質軟體與政策，來改善公共服務的交付"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop codebases that can be reused across contexts and collaboratively "
 "maintained"
-msgstr "開發能在各種情境下重複使用且共同維護的代碼庫"
+msgstr "開發能在各種情境下重複使用，且以協作方式維護的代碼庫"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "reduce technical debt and project failure rate"
@@ -5334,40 +5425,42 @@ msgstr "減少技術債與專案失敗率"
 msgid ""
 "have more granular control over, and ability to make decisions about, their "
 "IT systems"
-msgstr "更能精細控制 IT 系統並且做出 IT 系統相關決策"
+msgstr "更能精細控制 IT 系統粒度，並做出系統相關決策"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "improve vendor relationships with a better economic model"
-msgstr "更好的經濟模型改善與供應商的關係"
+msgstr "以更好的經濟模型改善供應商關係"
 
 #: ./foreword.md:block 50 (paragraph)
 msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
-msgstr "代碼庫潛在使用者依照 The Standard for Public Code 測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。"
+msgstr ""
+"如果有潛在使用者想採用經 Standard for Public Code "
+"測試過的代碼庫，可以預期這些代碼庫有方便重複利用、容易維護、品質高的特性。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
-msgstr "The Standard for Public Code 能有如此特性是因為："
+msgstr "Standard for Public Code 能有此成效是因為："
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "setting out a common terminology for public code development"
-msgstr "訂定公共程式開發的通用術語"
+msgstr "為公共程式開發訂立通用術語"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "establishing measures to help develop high quality public code"
-msgstr "訂定措施協助優質公共程式的開發"
+msgstr "訂定措施協助高品質公共程式的開發"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid ""
 "providing guidance on how to fulfill its criteria and operationalize "
 "compliance"
-msgstr "提出如何符合 The Standard for Public Code 的指引並在施作中遵循"
+msgstr "提出如何符合其準則，並實作遵循的指引"
 
 #: ./foreword.md:block 53 (paragraph)
 msgid ""
 "The Standard for Public Code is meant to be time and technology independent."
-msgstr "The Standard for Public Code 原意是要不受時間與科技限制。"
+msgstr "Standard for Public Code 本意是要跨越時間與科技，不受其限制。"
 
 #: ./foreword.md:block 54 (header)
 msgid "Who this is for"
@@ -6032,7 +6125,7 @@ msgstr "2023/07/31: 💄 第十六個草案版本變更準則名稱與釐清參
 msgid ""
 "The criterion \"Make the codebase reusable and portable\" was renamed from "
 "\"Create reusable and portable code\"."
-msgstr "準則從 \"編寫可重複使用與移植的程式碼\" 更名為 \"使代碼庫可重複使用與移植\"。"
+msgstr "〈程式碼要可重複使用且可攜〉準則改名為〈代碼庫要可重複使用且可移植〉。"
 
 msgid "Added a glossary entry for \"Source Code\"."
 msgstr "新增詞彙為 \"原始碼\"。"

From e6e16ca36f39f6756b44a374bd25d5c9728010fd Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Wed, 13 Sep 2023 10:11:59 +0800
Subject: [PATCH 49/71] add python: po2md

---
 python/po2md.py     | 102 ++++++++++++++++++++++++++++++++++++++++++++
 python/update_po.py |  34 +++++++++++++++
 2 files changed, 136 insertions(+)
 create mode 100644 python/po2md.py
 create mode 100644 python/update_po.py

diff --git a/python/po2md.py b/python/po2md.py
new file mode 100644
index 00000000..039d5145
--- /dev/null
+++ b/python/po2md.py
@@ -0,0 +1,102 @@
+import os
+import shutil
+import subprocess
+
+PROJECT_FOLDER = "./"
+SOURCE_FOLDER = "./origin_source"
+
+def main():
+    root_path = "./"
+    source_path = "./origin_source"
+
+    # 1. get all md file
+    md_files = find_md_files(PROJECT_FOLDER)
+
+    # 2. filter origin file
+    md_files = [file for file in md_files if not file.startswith(SOURCE_FOLDER)]
+
+    # 3A. backup md file (複製一次)
+    backup_md_files(md_files)
+
+    # 3B. restore md file
+    # restore_md_files(md_files)
+
+    # 4. run po2md
+    for file in md_files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        do_po2md(source_file=full_target_path, target_file=file)
+
+    # 4. update md file
+    update_md_file(SOURCE_FOLDER)
+
+
+
+
+def find_md_files(folder_path) -> list:
+    md_files = []
+    for root, dirs, files in os.walk(folder_path):
+        md_files += [os.path.join(root, file) for file in files if file.endswith('.md')]
+    return md_files
+
+# 複製原始檔案
+def backup_md_files(files):
+    if not os.path.exists(SOURCE_FOLDER):
+        os.makedirs(SOURCE_FOLDER)
+
+    for file in files:
+        # 建立目標資料夾的完整路徑
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        if not os.path.exists(os.path.dirname(full_target_path)):
+            os.makedirs(os.path.dirname(full_target_path))
+
+        # 複製檔案到目標資料夾
+        shutil.copy2(file, full_target_path)
+
+# 還原原始檔案
+def restore_md_files(files):
+    for file in files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        shutil.copy2(full_target_path, file)
+
+
+def do_po2md(source_file, target_file):
+    locale_file = "locales/zh_Hant/LC_MESSAGES/messages.po"
+    cmd = f"po2md -p {locale_file} -s {target_file} {source_file}"
+    result = subprocess.run(cmd, shell=True, capture_output=True, text=True)
+    if result.returncode != 0:
+        print("錯誤訊息：")
+        print(result.stderr)
+        exit()
+
+def update_md_file(source_path):
+    source_marker = "---"
+    target_marker = "***"
+
+    source_files = find_md_files(source_path)
+    for file in source_files:
+        with open(file, 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(source_marker)
+        end_index = file_content.find(source_marker, start_index + len(source_marker))
+        copied_content = file_content[start_index:end_index + len(source_marker)]
+
+
+        with open(file[len(source_path) + 1:], 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(target_marker)
+        end_index = file_content.find(target_marker, start_index + len(target_marker))
+        if end_index == -1:
+            print(file)
+            continue
+
+        new_content = copied_content + file_content[end_index + len(target_marker):]
+
+        with open(file[len(source_path) + 1:], 'w') as outfile:
+            outfile.write(new_content)
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file
diff --git a/python/update_po.py b/python/update_po.py
new file mode 100644
index 00000000..b8df8924
--- /dev/null
+++ b/python/update_po.py
@@ -0,0 +1,34 @@
+import os
+import shutil
+import subprocess
+import polib
+
+
+def main():
+    locals_en = 'locales/en/LC_MESSAGES/messages.po'
+    locals_zh = 'locales/zh_Hant/LC_MESSAGES/messages.po'
+    en_po = polib.pofile(locals_en)
+    zh_po = polib.pofile(locals_zh)
+
+    zh_msgids = set(entry.msgid for entry in zh_po)
+
+    # 遍歷 en.po 中的每一個 entry
+    for entry in en_po:
+        # 如果 en.po 中的 msgid 不在 zh.po 中
+        if entry.msgid not in zh_msgids:
+            # 創建一個新的 POEntry 對象
+            new_entry = polib.POEntry(
+                msgid=entry.msgid,
+                msgstr='',  # 初始為空字符串
+            )
+            # 將新的 entry 添加到 zh.po 中
+            zh_po.append(new_entry)
+
+    # 儲存更新後的 zh.po 檔案
+    zh_po.save(locals_zh)
+
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file

From f72d4684d34c102bc8b62343bfe59984ecd8137a Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Tue, 12 Sep 2023 15:51:32 +0000
Subject: [PATCH 50/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 653 +++++++++++++-----------
 1 file changed, 361 insertions(+), 292 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 9989187c..b593ecba 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-10 00:15+0000\n"
+"PO-Revision-Date: 2023-09-13 02:12+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -215,7 +215,7 @@ msgstr "創用 CC0 1.0 通用授權"
 msgid ""
 "This license is the legal contract that allows anyone to do anything they "
 "like with the content in this entire document."
-msgstr "此授權的法律契約允許任何人任意使用本文件中的任何內容。"
+msgstr "此授權的法律契約，允許任何人任意使用本文件中的任何內容。"
 
 #: ./CHANGELOG.md:block 3 (header)
 msgid "Version history"
@@ -249,8 +249,7 @@ msgstr "原先專注在貢獻內容是否遵循標準，現在則改為注重貢
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr "將〈代碼庫可查詢得到〉中許多「必須（Must）」等級的規定，調降為「應該（Should"
-"）」等級。"
+msgstr "將〈代碼庫可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
@@ -258,7 +257,7 @@ msgstr "審查範本現在有 HTML 格式。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Introduction converted to foreword."
-msgstr "「簡介」轉換為「序」。"
+msgstr "「前言」轉換為「序文」。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Improved contributing guidelines."
@@ -276,7 +275,8 @@ msgstr "0.6.0 版"
 msgid ""
 "April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
 "portability and tests and an introduction to each criterion."
-msgstr "2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且介紹每個準則。"
+msgstr "2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且每個準則都有一段前"
+"言。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -313,13 +313,13 @@ msgid ""
 "Removed the sections Why this is important and What this does not do and "
 "replaced with an introduction in each criterion."
 msgstr "移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加"
-"入介紹。"
+"入前言。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
 "Added general What this does not do section in the introduction of the "
 "Standard."
-msgstr "在本《標準》簡介中，加入通用的「此措施辦不到的事」小節。"
+msgstr "在本標準前言中，加入通用的「此措施辦不到的事」小節。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -479,7 +479,7 @@ msgstr "將剩餘 SPDX 標頭加入檔案中。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Made additional minor changes to text for clarity."
-msgstr "稍微修改文字，讓文字更明確。"
+msgstr "再稍微修改些文字，讓文字更明確。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Some hyperlinks updated."
@@ -491,8 +491,8 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/)."
 msgstr ""
-"將範例移動到[社群實踐指引](https://publiccodenet.github.io/"
-"community-implementation-guide-standard/)。"
+"將範例移動到《[社群實踐指引](https://publiccodenet.github.io/"
+"community-implementation-guide-standard/)》。"
 
 #: ./CHANGELOG.md:block 17 (header)
 msgid "Version 0.4.0"
@@ -525,19 +525,18 @@ msgstr "移除可重複使用與移植的程式碼中多餘的規定。"
 msgid ""
 "Expand open license definition to include both OSI and FSF approved "
 "licenses."
-msgstr "在開放授權的定義中，納入 OSI 與 FSF 所批准的授權。"
+msgstr "在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
-msgstr "重新編寫「得以 (MAY)」等級的相關規定，加入使用「可選擇 "
-"(OPTIONAL)」這個關鍵字，讓規定更明確。"
+msgstr "重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "表明 Standard for Public Code "
-"應該盡可能符合其自身規定的立場，並且加入評估措施。"
+msgstr "表明《Standard for Public "
+"Code》應該盡可能符合其自身規定的立場，並加入評估措施。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
@@ -573,7 +572,7 @@ msgstr "加入建置時期與執行時期依賴項目的額外指引。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
-msgstr "新增 Standard for Public Code 的發展路線圖。"
+msgstr "新增《Standard for Public Code》的發展路線圖。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Update structure of Authors file."
@@ -610,15 +609,15 @@ msgstr "在〈程式碼要可重複使用且可攜〉中定下明確的在地化
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Documentation of governance changed from a SHOULD to a MUST."
-msgstr "以文件記錄治理方式的規定，從「應該 (SHOULD)」等級調升為「必須 (MUST)」。"
+msgstr "以文件記錄治理方式的規定，從「應該」等級調升為「必須」。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid ""
 "Replace the very subjective (and hard to test) \"contributions MUST be "
 "small\" with requirement to document expectation in contributing guidelines "
 "and focus on a single issue."
-msgstr "在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容必須（MUST）小」的規定，改"
-"為必須紀錄貢獻所要完成的期待，並一次專注在單一議題上。"
+msgstr "在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容『必須』小」的規定，改為必"
+"須紀錄貢獻所要完成的期待，並一次專注在單一議題上。"
 
 #: ./CHANGELOG.md:block 22 (unordered list)
 msgid "Community translations now linked in the footer."
@@ -640,21 +639,21 @@ msgstr "0.2.3 版"
 msgid ""
 "March 15th 2022: 📜 the ninth draft allows English summaries for policy "
 "lacking an official translation."
-msgstr "2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策改為提供政策的英文版摘要。"
+msgstr "2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策，改為提供政策的英文版摘要。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Relax the criterion Use plain English by adding a new requirement allows "
 "bundled policy not available in English to have an accompanying summary in "
 "English instead of translating the full text."
-msgstr "放寬「使用白話英文」的準則，加入新規定，允許合捆的政策內文如果沒有英文版，只"
+msgstr "放寬〈使用白話的英文〉準則，加入新規定，允許合捆的政策內文如果沒有英文版，只"
 "需要加入英文版摘要，而不用翻譯全文。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
 msgid ""
 "Similarly, allow for English summaries for policies not available in English"
 " in Bundle policy and code."
-msgstr "同樣地，在〈政策與程式碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要"
+msgstr "同樣地，在〈政策與原始碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要"
 "。"
 
 #: ./CHANGELOG.md:block 25 (unordered list)
@@ -718,14 +717,14 @@ msgstr "2021年11月29日：🏛第八版草稿認知程式碼所執行的政策
 msgid ""
 "Document exception to \"All code MUST be in English\" where policy is "
 "interpreted as code."
-msgstr "在「所有程式碼都必須以英文編寫」的規定中，雖然政策也視為一種 "
-"code，可以有例外。"
+msgstr "在「所有程式碼都必須使用英語編寫」規定中，雖然政策也算是一種程式 "
+"(code)，但可以保有例外。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid ""
 "Add MAY requirement regarding committer email addresses in Maintain version "
 "control."
-msgstr "在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以 (MAY)」規定。"
+msgstr "在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以」規定。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Expand guidance to Policy Makers in Bundle policy and code."
@@ -791,7 +790,7 @@ msgstr "2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改
 msgid ""
 "New SHOULD requirement on using a distributed version control system and why"
 " distributed is important."
-msgstr "新增使用分散式版本控制系統的相關「應該 (SHOULD)」規定，並解釋分散式的重要性。"
+msgstr "新增使用分散式版本控制系統的相關「應該」規定，並解釋分散式的重要性。"
 
 #: ./CHANGELOG.md:block 31 (unordered list)
 msgid ""
@@ -863,11 +862,11 @@ msgstr "將〈注意代碼庫成熟度〉準則改名為〈記錄代碼庫成熟
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
-msgstr "針對多方使用的代碼庫，將「必須 (MUST)」等級規定調降為「應該 (SHOULD)」。"
+msgstr "針對多方使用的代碼庫，將「必須」等級規定調降為「應該」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
-msgstr "針對著作權轉讓，新增「禁止 (MUST NOT)」規定。"
+msgstr "針對著作權轉讓，新增「禁止」規定。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Clarify role of configuration in reusable code requirement."
@@ -881,7 +880,7 @@ msgstr "新增詞彙：持續整合、政策、儲存庫、版本控制等。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Replace references to 'cities' with 'public organizations'."
-msgstr "將「城市」替換成「公共組織」。"
+msgstr "將「城市」替換成「公家機關」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
@@ -1073,7 +1072,7 @@ msgid ""
 "communication channel."
 msgstr ""
 "社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達"
-"基金會對於所有社群成員，以及所有互動間的期望，不論透過何種溝通管道。"
+"基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。"
 
 #: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
 msgid "Be here to collaborate."
@@ -1108,7 +1107,7 @@ msgid ""
 msgstr ""
 "我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士"
 "協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專"
-"案的建議，我們非常開放任何合作的機會。"
+"案的建議。我們非常開放任何合作的機會。"
 
 #: ./CONTRIBUTING.md:block 5 (paragraph)
 msgid ""
@@ -1116,7 +1115,7 @@ msgid ""
 "with GitHub, you can email use your feedback at "
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
-"我們歡迎每個人提出的議題，以及拉入請求。如果您不大習慣 GitHub ，"
+"我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，"
 "也歡迎將意見回饋用電子郵件計送到 [info@publiccode.net](mailto:info@publiccode"
 ".net)。"
 
@@ -1159,13 +1158,13 @@ msgstr "您不一定要修改我們的程式碼或文件，也能成為貢獻者
 
 #: ./CONTRIBUTING.md:block 10 (header)
 msgid "Documentation and code in pull requests"
-msgstr "為文件記錄與程式碼提出拉入請求"
+msgstr "為文件與程式碼提出拉取請求"
 
 #: ./CONTRIBUTING.md:block 11 (paragraph)
 msgid ""
 "If you want to add to the documentation or code of one of our projects you "
 "should make a pull request."
-msgstr "如果您想要在我們的專案中，為文件紀錄或程式碼加入新內容，您應該提出拉入請求。"
+msgstr "如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求。"
 
 #: ./CONTRIBUTING.md:block 12 (paragraph)
 msgid ""
@@ -1188,7 +1187,7 @@ msgid ""
 "public domain in whatever jurisdiction possible, and everyone can do "
 "whatever they want with it."
 msgstr ""
-"本專案採用創用CC 0 1.0 通用，公眾領域貢獻宣告給予授權；這本質上代表本專案，以"
+"本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以"
 "及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可"
 "以任意使用。"
 
@@ -1206,8 +1205,8 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
-"貢獻內容應該[遵守](docs/standard-for-public-code.html) Standard for Public "
-"Code 自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值]"
+"貢獻內容應該[遵守](docs/standard-for-public-code.html)《Standard for Public C"
+"ode》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值]"
 "(foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標準"
 "](#standards-to-follow)，且與整體作品有所連貫。"
 
@@ -1257,7 +1256,7 @@ msgstr "適用政策"
 msgid ""
 "Currently, the Standard for Public Code is not implementing any specific "
 "public policy."
-msgstr "就目前而言，Standard for Public Code 並非在執行任何特定的公共政策。"
+msgstr "就目前而言，《Standard for Public Code》並非在執行任何特定的公共政策。"
 
 #: ./CONTRIBUTING.md:block 21 (header)
 msgid "Style"
@@ -1274,11 +1273,11 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
-"Standard for Public Code 目標[使用白話的英語](criteria/use-plain-english.md)"
-"，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`"
-"diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，"
-"而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質"
-"才[推出新發行版本](docs/releasing.md)。"
+"《Standard for Public Code》目標[使用白話的英語](criteria/use-plain-english.m"
+"d)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓"
+"「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容"
+"上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查"
+"品質才[推出新發行版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1289,8 +1288,8 @@ msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr "這些是 Standard for Public Code "
-"所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。"
+msgstr "這些是《Standard for Public "
+"Code》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
@@ -1307,7 +1306,7 @@ msgstr "[網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/
 
 #: ./CONTRIBUTING.md:block 26 (header)
 msgid "2. Pull request"
-msgstr "2. 拉入請求"
+msgstr "2. 拉取請求"
 
 #: ./CONTRIBUTING.md:block 27 (paragraph)
 msgid ""
@@ -1317,8 +1316,8 @@ msgid ""
 "issue where possible. In some cases a single set of changes may address "
 "multiple issues, in which case be sure to list all issue numbers fixed."
 msgstr ""
-"當您提出拉入請求時，請隨附描述您想要解決的問題，以及該拉入請求所能修正的議題"
-"編號。以一個拉入請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列"
+"當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題"
+"編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列"
 "出所有能一併修正的議題編號。"
 
 #: ./CONTRIBUTING.md:block 28 (header)
@@ -1342,7 +1341,7 @@ msgid ""
 "feedback. If this is the case the reviewing maintainer will help you improve"
 " your documentation and code."
 msgstr ""
-"維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉入請求通常需要再"
+"維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再"
 "經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若"
 "是如此，負責審查您貢獻內容的維護人員，將協助您改善文件與程式碼。"
 
@@ -1364,7 +1363,7 @@ msgstr "您的構想、文件與程式碼，已成為本專案的一部份。您
 msgid ""
 "In fact, feel free to open a pull request to add your name to the "
 "[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
-msgstr "誠摯歡迎您提出拉入請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) "
+msgstr "誠摯歡迎您提出拉取請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) "
 "檔案中，讓您所做的貢獻能銘記在本專案中。"
 
 #: ./CONTRIBUTING.md:block 35 (header)
@@ -1377,9 +1376,9 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
-"雖然 Standard for Public Code "
-"沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](https://github."
-"com/publiccodenet/community-translations-standard)，或是新增翻譯。"
+"《Standard for Public Code》沒有官方版本的翻譯，您仍可以協助本標準維護已有的["
+"社群翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)，或是新增翻譯。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
 msgid "Releases"
@@ -1390,8 +1389,8 @@ msgid ""
 "We have dedicated documentation for creating [new "
 "releases](/docs/releasing.md) and [ordering printed "
 "standards](/docs/printing.md)."
-msgstr "我們有提供[發行新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing."
-"md)的專用詳細文件。"
+msgstr "我們有提供[發行新版本](/docs/releasing.md)，與[訂購印刷版標準](/docs/printing"
+".md)的專用詳細文件。"
 
 #: ./CONTRIBUTING.md:block 39 (paragraph)
 msgid ""
@@ -1405,9 +1404,8 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net), "
 "https://standard.publiccode.net/AUTHORS"
 msgstr ""
-"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public "
-"Code[info@publiccode.net](mailto:info@publiccode.net), "
-"https://standard.publiccode.net/AUTHORS"
+"SPDX-FileCopyrightText: 2019-2022 Foundation for Public Code[info@publiccode."
+"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
 
 #: ./GOVERNANCE.md:block 3 (header)
 msgid "Governance"
@@ -1419,7 +1417,7 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"此標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管"
+"本標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管"
 "理領域作監督時的核心。我們依照這份文件來判斷，某個代碼庫是否已經準備好讓社群"
 "共同參與開發。"
 
@@ -1439,8 +1437,9 @@ msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
 msgstr ""
-"由於 Standard for Public Code 在我們的核心流程中，扮演至關重要的角色，"
-"所以我們會以 Standard for Public Code 中的最高標準作要求。"
+"由於《Standard for Public "
+"Code》在我們的核心流程中，扮演至關重要的角色，所以我們會以《Standard for "
+"Public Code》的最高標準作要求。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1463,9 +1462,9 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"Standard for Public Code 提供公共組織一套準備開源解決方案的模型，讓他們能與其"
-"他地方相似的公共組織協作。該標準包含給政策制定者、市行政官、開發人員與供應商"
-"的指引。"
+"《Standard for Public Code》提供公家機關一套準備開源解決方案的模型，讓他們能"
+"與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供"
+"應商的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1511,12 +1510,12 @@ msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr "Standard for Public Code 目前為草稿階段。我們正在準備發行 1.0 "
+msgstr "《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 "
 "版，目前仍在幾個代碼庫中作測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將 Standard for Public Code 套用到您的代碼庫"
+msgstr "將《Standard for Public Code》套用您的代碼庫"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1527,7 +1526,7 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將 Standard for Public Code 套用到您的代碼庫，就請放心去做，因為它是"
+"若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是"
 "人人都能自由採用的開放標準。若要瞭解您代碼庫所達成的程度，可以做[自我資格評估"
 "](https://publiccodenet.github.io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
@@ -1543,8 +1542,8 @@ msgid ""
 msgstr ""
 "本標準 *應該* 足以自我解釋要如何套用到您的代碼庫中。若標準中有任何不明確的地"
 "方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如"
-"果需要一點靈感啟發，請參閱[社群製作的實踐指引](https://publiccodenet.github."
-"io/community-implementation-guide-standard/)，其中包括範例與其他提示。"
+"果需要一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet."
+"github.io/community-implementation-guide-standard/)，其中包括範例與其他提示。"
 
 #: ./README.md:block 10 (paragraph)
 msgid ""
@@ -1552,9 +1551,9 @@ msgid ""
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
 msgstr ""
-"若新版的 Standard for Public Code 有任何導致過去作法不再適用的改動，則 "
+"若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 "
 "Foundation for Public Code "
-"的代碼庫管事同仁，會協助標準的實踐者理解該如何銜接之間的落差。"
+"的代碼庫管事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1580,7 +1579,7 @@ msgid ""
 "way of designing, developing and procuring both the source code and policy "
 "documentation."
 msgstr ""
-"我們相信公共政策與公共軟體，應該具備包容、好用、開放、易懂、可責、近用、永續"
+"我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續"
 "等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政"
 "策文件。"
 
@@ -1589,8 +1588,8 @@ msgid ""
 "This standard sets a quality level for codebases that meets the needs of "
 "public organizations, institutions and administrations as well as other "
 "critical infrastructural services."
-msgstr "本標準為代碼庫設立品質檢核水準，使其能滿足公共組織、機構、行政機關，以及其他"
-"重大基礎設施服務的需求。"
+msgstr "本標準為代碼庫設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及"
+"其他重大基礎設施服務的需求。"
 
 #: ./README.md:block 15 (paragraph)
 msgid ""
@@ -1608,8 +1607,8 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
-"[![Standard for Public Code "
-"的影片縮圖：兩隻手中間放著本標準的印刷本](https://img.youtube.com/vi/"
+"[![《Standard for Public "
+"Code》的影片縮圖：兩隻手中間放著本標準的印刷本](https://img.youtube.com/vi/"
 "QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
@@ -1618,8 +1617,9 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
-"[Standard for Public Code 的影片介紹](https://www.youtube.com/watch?v=QWt6vB-"
-"cipE)，出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。"
+"[《Standard for Public Code》的影片介紹](https://www.youtube.com/watch?v"
+"=QWt6vB-cipE)，出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube "
+"上。"
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
@@ -1631,8 +1631,8 @@ msgid ""
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
 msgstr ""
-"Foundation for Public Code 致力於維護與開發 Standard for Public "
-"Code，且使其同時符合該標準自身的品質水準。"
+"Foundation for Public Code 致力於維護與開發《Standard for Public "
+"Code》，且使其同時符合該標準自身的品質水準。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -1709,7 +1709,7 @@ msgstr ""
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
-msgstr "生成 Standard for Public Code 的 PDF 檔案"
+msgstr "生成《Standard for Public Code》的 PDF 檔案"
 
 #: ./README.md:block 31 (paragraph)
 msgid ""
@@ -1807,7 +1807,7 @@ msgstr "代碼庫「必須」包含原始碼所根據的政策。"
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr "如果政策基於原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始"
+msgstr "如果政策根據原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始"
 "碼則可除外。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
@@ -1835,7 +1835,7 @@ msgstr "與公務人員確認原始碼所根據的所有政策內容都有收錄
 msgid ""
 "Confirm with a civil servant that all source code that the policy is based "
 "on is included."
-msgstr "與公務人員確認根據政策而來的所有原始碼都有收錄在內。"
+msgstr "與公務人員確認政策所根據的所有原始碼都有收錄在內。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
 msgid "Check if policy can be interpreted by a machine."
@@ -1868,7 +1868,7 @@ msgid ""
 msgstr ""
 "提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
 "文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
-"，以及影響貴組織單位代碼庫開發或部署情境的任何組織流程。"
+"，以及影響貴組織單位代碼庫開發或部署情境的任何組織單位流程。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -1886,7 +1886,7 @@ msgstr "政策內容請使用明確且機器可讀的格式，像是[物件管
 msgid ""
 "Track policy with [the same version control](maintain-version-control.md) "
 "and documentation used to track source code."
-msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](maintain-version-control."
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制系統](maintain-version-control."
 "md)與文件。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
@@ -1906,10 +1906,10 @@ msgid ""
 "accessibility), or human rights policies, like a public organization's "
 "commitment to equal opportunity."
 msgstr ""
-"納入會影響社會群體、代碼庫與開發目標的相關政策，包含[一般資料保護規則](https"
-"://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟網頁無障礙命令](https://ec"
-".europa.eu/digital-single-market/en/web-accessibility)等此類法律義務，或者是"
-"人權政策，例如公共組織對機會平等的承諾等。"
+"納入會影響社會群體、代碼庫與開發目標的相關政策，包含 [GDPR "
+"一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 "
+"[歐盟網頁無障礙命令](https://ec.europa.eu/digital-single-market/en/web-access"
+"ibility)等此類法律義務，或者是人權政策，例如公家機關對機會平等的承諾等。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
@@ -2006,21 +2006,21 @@ msgid ""
 "software and [policy](../glossary.md#policy) impact their interactions with "
 "a public organization."
 msgstr "這些加在一起，讓公民更有機會瞭解軟體與[政策](../glossary."
-"md#policy)如何影響他們與公共組織的互動。"
+"md#policy)如何影響他們與公家機關的互動。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any policy in use (unless used for fraud detection) MUST"
 " be published and publicly accessible."
-msgstr "任何使用中政策的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
-"眾取用。"
+msgstr "任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能"
+"供民眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
 "All source code for any software in use (unless used for fraud detection) "
 "MUST be published and publicly accessible."
-msgstr "任何使用中軟體的所有原始碼都必須要公開（用於偵測詐欺的原始碼除外），且能供民"
-"眾取用。"
+msgstr "任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能"
+"供民眾取用。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
@@ -2040,8 +2040,8 @@ msgid ""
 "the [general public](../glossary.md#general-public) may have with an "
 "organization is OPTIONAL."
 msgstr ""
-"可選擇是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間"
-"可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
+"「可選擇」是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位"
+"之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
 msgid ""
@@ -2322,7 +2322,7 @@ msgstr "代碼庫文件「應該」清楚描述[政策](../glossary."
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
-msgstr "「可選擇」是否以文件記錄給[一般民眾](../glossary.md#general-"
+msgstr "「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-"
 "public)看的代碼庫目標。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
@@ -2423,7 +2423,7 @@ msgid ""
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
 msgstr ""
-"代碼庫文件「應該」包含精要的說明，讓[一般民眾](../glossary.md#general-"
+"代碼庫文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-"
 "public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
@@ -2466,7 +2466,8 @@ msgid ""
 "Confirm that other stakeholders, professionals from other public "
 "organizations and the general public find the documentation clear and "
 "understandable."
-msgstr "確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。"
+msgstr "確認文件內容能讓其他利害關係人、其他公家機關的專業人士，以及一般大眾，都可以"
+"清楚明白。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
@@ -2483,7 +2484,7 @@ msgstr "確認文件有包含主要功能的範例。"
 msgid ""
 "Check with members of the general public and journalists if they can "
 "understand the high level description."
-msgstr "向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
+msgstr "向一般大眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
@@ -2526,7 +2527,7 @@ msgid ""
 "sufficient to persuade a manager at another public organization to use this "
 "codebase?"
 msgstr "嘗試使用代碼庫，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來"
-"說，目前的文件是否足以說服另一個公共組織的管理人員使用這個代碼庫？"
+"說，目前的文件是否足以說服另一個公家機關的管理人員使用這個代碼庫？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -3951,11 +3952,11 @@ msgstr "此外："
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Use a linter."
-msgstr "使用程式碼品質梳理工具 (linter)。"
+msgstr "使用 linter 程式碼品質梳理工具。"
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入程式碼品質梳理工具的組態設定。"
+msgstr "在代碼庫中加入 linter 梳理工具的組態設定。"
 
 #: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
 msgid ""
@@ -4358,8 +4359,8 @@ msgid ""
 "Public sector information needs to be accessible to all its constituents. "
 "Plain and simple language makes the [code](../glossary.md#code) and what it "
 "does easier to understand for a wider variety of people."
-msgstr "公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，讓更多人能瞭解[程式碼]("
-"../glossary.md#code)與其功用。"
+msgstr "公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解[程式碼"
+"](../glossary.md#code)與其功用。"
 
 #: ./criteria/use-plain-english.md:block 8 (paragraph)
 msgid ""
@@ -4712,7 +4713,7 @@ msgid ""
 "tries to provide the relevant information to print it there or somewhere "
 "else."
 msgstr ""
-"Standard for Public Code 是由 Reclameland "
+"《Standard for Public Code》是由 Reclameland "
 "負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
@@ -4776,7 +4777,7 @@ msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
-msgstr "發行新版本的 Standard for Public Code"
+msgstr "發行新版本的《Standard for Public Code》"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Review state of the 'develop' branch"
@@ -5003,7 +5004,7 @@ msgstr "上次更新時間：2023-03-08"
 msgid ""
 "This document intends to shed light on the current development plans of the "
 "team. Plans change constantly as new information is absorbed by the team."
-msgstr "本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變動。"
+msgstr "本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。"
 
 #: ./docs/roadmap.md:block 5 (paragraph)
 msgid ""
@@ -5011,8 +5012,9 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
-"代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會議](https://about.publiccode.net/activities/standard-"
-"maintenance/backlog-pruning.html)的一部份。"
+"代碼庫管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://ab"
+"out.publiccode.net/activities/standard-maintenance/backlog-pruning."
+"html)環節的一部份。"
 
 #: ./docs/roadmap.md:block 6 (header)
 msgid "Current work"
@@ -5020,7 +5022,7 @@ msgstr "目前任務"
 
 #: ./docs/roadmap.md:block 7 (unordered list)
 msgid "As far as possible, make the standard Standard-compliant"
-msgstr "盡可能讓標準符合 The Standard for Public Code"
+msgstr "盡可能讓標準遵循自我標準"
 
 #: ./docs/roadmap.md:block 8 (header)
 msgid "Near term"
@@ -5034,11 +5036,11 @@ msgstr "分離執行摘要"
 msgid ""
 "Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
 " issue #208"
-msgstr "#208號議題：需要時，將「程式碼」清楚標示為「原始碼」或是「政策程式碼」"
+msgstr "#208號議題：將代碼或規則之「code」清楚區分為「原始碼」或是「政策法規」"
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid "Possibly: add in the illustrations for each criterion"
-msgstr "潛在解決方案：為每個標準新增圖示"
+msgstr "可能性：為每個準則新增解說插圖"
 
 #: ./docs/roadmap.md:block 10 (header)
 msgid "Longer term"
@@ -5052,23 +5054,23 @@ msgstr "認證標章"
 msgid ""
 "Add to README and index.md information (and eventually statistics) on "
 "adoption and use (issue #438)"
-msgstr "新增「README」與「index.md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上"
+msgstr "為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Physical paper checklist"
-msgstr "實體檢查清單"
+msgstr "實體紙張檢查清單"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Becoming validated by multiple codebases"
-msgstr "取得多個代碼庫認證"
+msgstr "通過多個代碼庫驗證"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Release version 1.0.0 after a few codebases are compliant"
-msgstr "在幾個代碼庫符合標準後，推出 1.0.0 版"
+msgstr "在幾個代碼庫遵循標準後，發行 1.0.0 版"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Linkable requirements"
-msgstr "可連結需求規範"
+msgstr "可連結的需求規範"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "New cover art"
@@ -5076,15 +5078,15 @@ msgstr "新封面設計"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Register for ISBN"
-msgstr "申請 ISBN 書號"
+msgstr "註冊申請 ISBN 書號"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "List with an on-demand book printing service"
-msgstr "隨選書籍列印服務廠商清單"
+msgstr "隨選書籍列印服務名單"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "QR codes for external links in print version"
-msgstr "印刷版外部連結的 QR 二維碼"
+msgstr "印刷版外部連結的 QR 二維圖碼"
 
 #: ./foreword.md:block 3 (paragraph)
 msgid "redirect_from:"
@@ -5096,26 +5098,28 @@ msgstr "前言"
 
 #: ./foreword.md:block 5 (header)
 msgid "Foreword"
-msgstr "序"
+msgstr "序文"
 
 #: ./foreword.md:block 6 (paragraph)
 msgid ""
 "The Standard for Public Code is a set of criteria that support public "
 "organizations in developing and maintaining software and policy together."
-msgstr "The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "《Standard for Public "
+"Code》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。"
 
 #: ./foreword.md:block 7 (paragraph)
 msgid ""
 "Anyone developing public-purpose software or policy can use this standard to"
 " work towards higher quality public services that are more cost effective, "
 "with less risk and more control."
-msgstr "開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成本效益、風險更低且能夠掌控。"
+msgstr "任何想開發具有公眾用途的軟體或政策的人，可以利用此標準來提升公共服務品質，使"
+"其更具成本效益、風險更低，還能對系統更有掌控權。"
 
 #: ./foreword.md:block 8 (paragraph)
 msgid ""
 "This foreword introduces the term public code and explains why this is "
 "important."
-msgstr "「序」介紹何謂「公共程式」以及其重要性。"
+msgstr "本序文在介紹何謂「公共程式」以及解說其重要性。"
 
 #: ./foreword.md:block 9 (header)
 msgid "Definition of public code"
@@ -5130,11 +5134,14 @@ msgid ""
 "distinct from regular software because it operates under fundamentally "
 "different circumstances and expectations."
 msgstr ""
-"公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體生產的安排，都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件與期待也不同。"
+"公共程式，英文為 Public Code，是指人類或機器在公共情境下，所執行的電腦原始碼"
+"（像是軟體與演算法）與公共政策。公共程式的範疇，涵蓋搭配公共基礎建設一同作業"
+"的軟體、作為公共基礎建設運作而建置的軟體，以及產生公共程式的過程安排等。公共"
+"程式與一般軟體有明顯區別，因為其作業的環境與期待全然不同。"
 
 #: ./foreword.md:block 11 (header)
 msgid "Reasons for public code"
-msgstr "使用公共程式的原因"
+msgstr "採用公共程式的原因"
 
 #: ./foreword.md:block 12 (paragraph)
 msgid "There are many reasons for why public code is relevant now."
@@ -5142,7 +5149,7 @@ msgstr "公共程式現在如此重要，背後有幾個原因。"
 
 #: ./foreword.md:block 13 (header)
 msgid "Software code == legal code"
-msgstr "軟體程式碼 == 政府法規"
+msgstr "軟體程式碼 == 法律條文"
 
 #: ./foreword.md:block 14 (paragraph)
 msgid "Software is public infrastructure."
@@ -5155,7 +5162,9 @@ msgid ""
 "originator of new policy, for example where algorithms decide which "
 "districts need extra social services or policing."
 msgstr ""
-"在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。"
+"在 21 世紀，軟體可被視為重要的公共基礎建設。軟體越來越常被用於實現既有政策，"
+"甚至成為新政策的制定來源。舉例來說，演算法可以決定哪些地區需要額外的社會服務"
+"或警力等。"
 
 #: ./foreword.md:block 16 (paragraph)
 msgid ""
@@ -5167,7 +5176,10 @@ msgid ""
 "by machines. In other words, software code has increasingly started to equal"
 " legal code."
 msgstr ""
-"在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共價值，設定社會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體程式越來越接近法規的地位。"
+"在公共政策的執行上，軟體運作機制、演算法與資料蒐集等，已成為關鍵要素。今日的"
+"電腦程式碼，正執行著透過民主程序制定的法規政策。程式碼與政策這兩種形式的程式"
+"，都根據民主程序而確立的公共價值，設立出社會的運作環境；前者由機器執行，後者"
+"則是由人類執行。換句話說，軟體程式碼，已經越來越實質趨近於法律條文的地位。"
 
 #: ./foreword.md:block 17 (paragraph)
 msgid ""
@@ -5177,42 +5189,42 @@ msgstr "因此軟體也應該接受民主治理原則的約束。"
 
 #: ./foreword.md:block 18 (header)
 msgid "Traditional public software procurement"
-msgstr "傳統的公共軟體採購方式"
+msgstr "傳統的公共軟體採購"
 
 #: ./foreword.md:block 19 (paragraph)
 msgid ""
 "Current public software production methods have not served public service "
 "delivery very well."
-msgstr "目前的公共軟體生產模式，在交付公共服務上的效率並不高。"
+msgstr "目前公共軟體的生產模式，在交付公共服務上的效率並不高。"
 
 #: ./foreword.md:block 20 (paragraph)
 msgid ""
 "In the last decade, public organizations that purchased complete software "
 "solutions have sometimes been surprised to discover that they:"
-msgstr "過去十年購買完整軟體解決方案的公共組織，都很訝異地發現："
+msgstr "過去近十年來，購置完整軟體解決方案的公家機關，有時甚至會很訝異地發現："
 
 #: ./foreword.md:block 21 (unordered list)
 msgid ""
 "can’t change their software to reflect changing policy or take advantage of "
 "new technology"
-msgstr "無法修改軟體來反映政策的變動，或是利用新科技"
+msgstr "他們無法修改軟體來反映政策的變動，或是改變軟體來利用新科技"
 
 #: ./foreword.md:block 21 (unordered list)
 msgid ""
 "don’t have access to their data as it's locked into proprietary systems"
-msgstr "資料都鎖在專有系統中，無法取得"
+msgstr "他們的資料都套牢在專有系統中，無法取用"
 
 #: ./foreword.md:block 21 (unordered list)
 msgid "are asked to pay ever increasing license fees"
-msgstr "授權費越來越貴而且還要定期繳納"
+msgstr "他們所需繳交的授權費變得越來越貴"
 
 #: ./foreword.md:block 22 (header)
 msgid "Technological sovereignty and democratic accountability"
-msgstr "技術主權與民主課責"
+msgstr "技術自主權與民主課責"
 
 #: ./foreword.md:block 23 (paragraph)
 msgid "Public institutions, civil servants and residents deserve better."
-msgstr "公共機關、公僕與市民都值得更好的。"
+msgstr "公家機關、公務員與居民都值得更好的。"
 
 #: ./foreword.md:block 24 (paragraph)
 msgid ""
@@ -5225,23 +5237,27 @@ msgid ""
 " Citizens and civil society actors need this software to be transparent and "
 "accountable."
 msgstr ""
-"我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都需要技術主權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。"
+"我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有代碼庫之"
+"下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主"
+"權。技術自主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整"
+"政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。"
 
 #: ./foreword.md:block 25 (paragraph)
 msgid ""
 "The design of software as essential civic infrastructure should honor "
 "digital citizens’ rights."
-msgstr "設計為必要公民基礎建設的軟體，也應該尊重數位公民的權益。"
+msgstr "作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。"
 
 #: ./foreword.md:block 26 (header)
 msgid "Designing truly public software"
-msgstr "設計真正屬乎民眾的軟體"
+msgstr "設計真正的公共軟體"
 
 #: ./foreword.md:block 27 (paragraph)
 msgid ""
 "Public code is at the core of modern public institutions, shapes the work of"
 " civil servants and affects the lives of almost all residents."
-msgstr "公共程式是現代公共基礎建設的核心，影響公僕的工作以及幾乎所有市民的生活。"
+msgstr "公共程式是現代公家機構的核心，型塑了公務員的工作樣態，並且影響了幾乎所有居民"
+"的生活。"
 
 #: ./foreword.md:block 28 (paragraph)
 msgid "Public software must therefore be:"
@@ -5253,7 +5269,7 @@ msgstr "透明"
 
 #: ./foreword.md:block 29 (unordered list)
 msgid "accountable"
-msgstr "負責任"
+msgstr "可課責"
 
 #: ./foreword.md:block 29 (unordered list)
 msgid "understandable for its constituents"
@@ -5263,13 +5279,13 @@ msgstr "讓選民能夠理解"
 msgid ""
 "It must reflect the values of the society it serves, for example by being "
 "inclusive and non-discriminatory."
-msgstr "反映其服務社會的價值觀，像是包容與不歧視。"
+msgstr "必須能反映其所服務的社會價值觀，像是涵容與不歧視。"
 
 #: ./foreword.md:block 31 (paragraph)
 msgid ""
 "Most proprietary software systems currently used by public organizations do "
 "not meet these requirements. Public code does."
-msgstr "公共組織目前使用的多數專有軟體系統都不符合這些要求，但是公共程式符合。"
+msgstr "目前公家機關使用的大多數專有軟體系統，都不符合這些要求；而公共程式能夠做到。"
 
 #: ./foreword.md:block 32 (header)
 msgid "Values of public code"
@@ -5277,11 +5293,11 @@ msgstr "公共程式的價值"
 
 #: ./foreword.md:block 33 (paragraph)
 msgid "We consider public code to have these core values:"
-msgstr "我們認為公共程式具有以下核心價值："
+msgstr "我們認為公共程式應具有下列核心價值："
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Inclusive"
-msgstr "包容"
+msgstr "涵容"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Usable"
@@ -5297,7 +5313,7 @@ msgstr "易懂"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accountable"
-msgstr "可責"
+msgstr "課責"
 
 #: ./foreword.md:block 34 (unordered list)
 msgid "Accessible"
@@ -5318,11 +5334,13 @@ msgid ""
 "to the software, so that its development and maintenance become truly "
 "collaborative."
 msgstr ""
-"公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。"
+"公共程式是旨在協助公家機關，履行其必要職責時所採用的開源軟體。透過使用，其他"
+"行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成"
+"果。"
 
 #: ./foreword.md:block 37 (paragraph)
 msgid "Being open unlocks many other things."
-msgstr "開放的精神能創造許多可能性。"
+msgstr "開放的精神能開創許多可能性。"
 
 #: ./foreword.md:block 38 (paragraph)
 msgid ""
@@ -5336,7 +5354,13 @@ msgid ""
 "in the future. The code will be easier to retool, repurpose or retire. This "
 "all results in lower risk public infrastructure."
 msgstr ""
-"公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高。許多貢獻者會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼與資料，在未來也更容易改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都讓公共基礎建設風險更低。"
+"公家機關在執行與維護其自身的公共程式時，就是在確保能為地方負責，並履行民主課"
+"責。開放且貢獻者眾多的軟體，得利於有許多人在看，更容易發現潛在缺陷，因此安全"
+"性會更高。許多貢獻者會分攤維護工作，讓公共程式能持續運作與更新，減少未來技術"
+"債的可能。因為能有多人分攤維護工作，使得現在與未來都會更加永續。而公共程式的"
+"開放性，代表其程式碼與資料，在未來也更容易改寫與調整。程式碼也更容易重新利用"
+"、重新調整目標，或甚至淘汰。這一切特性都讓公共基礎建設可能遭遇的風險降到更低"
+"。"
 
 #: ./foreword.md:block 39 (paragraph)
 msgid ""
@@ -5344,18 +5368,21 @@ msgid ""
 "to how to customize the software so it works best in each local context, "
 "creating better user experiences for their end users (residents or "
 "citizens)."
-msgstr "集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。"
+msgstr ""
+"這種將資源集中的作法，能讓公共行政單位可以有額外心力關注如何客製化軟體，來使"
+"軟體最適合當地情境的需求，為終端使用者（居民或市民）創造更佳的使用體驗。"
 
 #: ./foreword.md:block 40 (header)
 msgid "Economics of public code"
-msgstr "公共程式的經濟"
+msgstr "公共程式的經濟效應"
 
 #: ./foreword.md:block 41 (paragraph)
 msgid ""
 "Public code offers a better economic model for public organizations as well "
 "as for commercial companies. It's an alternative to traditional software "
 "procurement which increases local control and economic opportunity."
-msgstr "公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助各地的公共組織更能控制程式，也有更好的經濟機會。"
+msgstr "公共程式為公家機關以及商業公司，提供更好的經濟模型。公共程式作為替代傳統軟體"
+"採購的方案，更能提升當地的掌控權並促進經濟機會。"
 
 #: ./foreword.md:block 42 (paragraph)
 msgid ""
@@ -5368,7 +5395,11 @@ msgid ""
 "administrations can use their own software purchasing to stimulate "
 "innovation and competition in their local economy."
 msgstr ""
-"公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始碼讓社會大眾更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激當地經濟的創新與競爭。"
+"公共程式從設計之初，就是要開放、適應力強、資料可攜，能夠由內部員工或信任的供"
+"應商來開發。由於原始碼開放，公共行政單位在有需要時可以更換供應商。開放原始碼"
+"讓社會大眾更有機會瞭解與監督公共程式，使公共行政單位得以採購小規模的合約，而"
+"地方性的中小企業就更容易參與這些小型採購案的競標。如此一來，公共行政單位就可"
+"以透過他們所需的軟體採購案，刺激當地經濟的創新與競爭。"
 
 #: ./foreword.md:block 43 (paragraph)
 msgid ""
@@ -5378,14 +5409,15 @@ msgstr "這可視為對未來經濟成長的投資。隨著科技需求成長，
 
 #: ./foreword.md:block 44 (header)
 msgid "Procuring public code"
-msgstr "育成公共程式"
+msgstr "購置公共程式"
 
 #: ./foreword.md:block 45 (paragraph)
 msgid ""
 "Public code can be used and developed by permanent in-house development "
 "teams, contractors or outsourced suppliers. Vendors to public organizations "
 "can include public code in their bids for contracts."
-msgstr "公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可以包含公共程式。"
+msgstr "公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在"
+"投標時可以在標案中納入公共程式。"
 
 #: ./foreword.md:block 46 (paragraph)
 msgid ""
@@ -5394,28 +5426,30 @@ msgid ""
 "innovative approach to adapting the public code to your context, you could "
 "describe the service or outcome in your contract."
 msgstr ""
-"若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您的服務或成果。"
+"若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將"
+"會使用該代碼庫。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中"
+"描述說明服務內容或預期成果。"
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
-msgstr "Standard for Public Code 目標"
+msgstr "《Standard for Public Code》目標"
 
 #: ./foreword.md:block 48 (paragraph)
 msgid ""
 "This Standard supports developers, designers, managers and public policy "
 "makers to:"
-msgstr "本標準支持開發人員、設計師、管理人員、公共政策制定者："
+msgstr "本標準在於支持開發人員、設計師、管理人員、公共政策制定者："
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop high quality software and policy for better public service delivery"
-msgstr "開發高品質軟體與政策，來改善公共服務的交付"
+msgstr "開發出高品質的軟體與政策，來改善公共服務的交付"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid ""
 "develop codebases that can be reused across contexts and collaboratively "
 "maintained"
-msgstr "開發能在各種情境下重複使用，且以協作方式維護的代碼庫"
+msgstr "開發出能在各種情境下重複使用，且以協作方式維護的代碼庫"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "reduce technical debt and project failure rate"
@@ -5425,7 +5459,7 @@ msgstr "減少技術債與專案失敗率"
 msgid ""
 "have more granular control over, and ability to make decisions about, their "
 "IT systems"
-msgstr "更能精細控制 IT 系統粒度，並做出系統相關決策"
+msgstr "更能精細控制其 IT 系統粒度，並做出系統相關決策"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "improve vendor relationships with a better economic model"
@@ -5436,12 +5470,12 @@ msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
 msgstr ""
-"如果有潛在使用者想採用經 Standard for Public Code "
-"測試過的代碼庫，可以預期這些代碼庫有方便重複利用、容易維護、品質高的特性。"
+"如果有潛在使用者想採用經由《Standard for Public Code》測試過的代碼庫，便可以"
+"預期這些代碼庫具有方便重複利用、容易維護、高品質的特性。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
-msgstr "Standard for Public Code 能有此成效是因為："
+msgstr "《Standard for Public Code》能有此效果是基於："
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "setting out a common terminology for public code development"
@@ -5449,18 +5483,18 @@ msgstr "為公共程式開發訂立通用術語"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "establishing measures to help develop high quality public code"
-msgstr "訂定措施協助高品質公共程式的開發"
+msgstr "制定措施協助高品質公共程式的開發"
 
 #: ./foreword.md:block 52 (unordered list)
 msgid ""
 "providing guidance on how to fulfill its criteria and operationalize "
 "compliance"
-msgstr "提出如何符合其準則，並實作遵循的指引"
+msgstr "提出該如何符合準則並實作遵循的指引"
 
 #: ./foreword.md:block 53 (paragraph)
 msgid ""
 "The Standard for Public Code is meant to be time and technology independent."
-msgstr "Standard for Public Code 本意是要跨越時間與科技，不受其限制。"
+msgstr "《Standard for Public Code》設計精神就是要跨越時間與科技，不受其限制。"
 
 #: ./foreword.md:block 54 (header)
 msgid "Who this is for"
@@ -5470,7 +5504,7 @@ msgstr "適用對象"
 msgid ""
 "The Standard for Public Code is for the people who create and reuse public "
 "code:"
-msgstr "The Standard for Public Code 適用於開發與重複使用公共程式的民眾："
+msgstr "《Standard for Public Code》適用於開發與重複使用公共程式的人："
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "public policy makers"
@@ -5486,23 +5520,23 @@ msgstr "開發人員與設計師"
 
 #: ./foreword.md:block 57 (paragraph)
 msgid "These people work at:"
-msgstr "這些人的服務單位："
+msgstr "在以下單位服務的人："
 
 #: ./foreword.md:block 58 (unordered list)
 msgid "institutions, organizations and administrations in the public sector"
-msgstr "公家機關的機構、組織與行政單位"
+msgstr "社會機構、公家機關的組織與行政單位"
 
 #: ./foreword.md:block 58 (unordered list)
 msgid ""
 "consultancies and vendors of information technology and policy services to "
 "public organizations"
-msgstr "服務公家機關的資訊科技以及政策服務顧問公司與供應商"
+msgstr "公家機關在資訊科技與政策服務上的顧問與供應商"
 
 #: ./foreword.md:block 59 (paragraph)
 msgid ""
 "It is not aimed at public organizations' end users (residents or citizens), "
 "journalists or academics."
-msgstr "適用對象不包括公家機關的終端使用者（居民或市民）、記者或學者。"
+msgstr "適用對象不含公家機關的終端使用者（居民或市民）、記者或學者等。"
 
 #: ./foreword.md:block 61 (unordered list)
 msgid ""
@@ -5510,12 +5544,13 @@ msgid ""
 "paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
 "Software.pdf) by the Free Software Foundation Europe."
 msgstr ""
-"歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮書](https://download.fsfe.org/campaigns/pmpc/PMPC-"
-"Modernising-with-Free-Software.pdf) 》。"
+"歐洲自由軟體基金會所發表的[《透過自由軟體實現公共基礎設施現代化》白皮書](http"
+"s://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf)"
+" 》。"
 
 #: ./foreword.md:block 62 (header)
 msgid "Videos on public code"
-msgstr "公共程式影片"
+msgstr "探討公共程式的影片"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5523,9 +5558,9 @@ msgid ""
 "2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
 "the background behind the Foundation for Public Code."
 msgstr ""
-"[2019 年 Decidim Fest "
-"的「程式合作是城市的未來」](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny "
-"介紹 The Foundation for Public Code 的背景。"
+"[〈程式協作是城市的未來〉@ DecidimFest 2019](https://www.youtube.com/"
+"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny，講述 Foundation for Public Code "
+"的背景。"
 
 #: ./foreword.md:block 63 (unordered list)
 msgid ""
@@ -5533,18 +5568,19 @@ msgid ""
 "2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
 "procurement, law and more."
 msgstr ""
-"[ 2019 年 Nextcloud "
-"大會的「公帑？公共程式！」專題討論](https://youtube.com/watch?v=QHFkD4xfd6c)。探討採購、法律等主題。"
+"[ 〈用公共的納稅錢？做公共的程式吧！〉專題討論 @ Nextcloud 大會 "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c)。討論採購、法律等主題。"
 
 #: ./foreword.md:block 64 (header)
 msgid "Get involved"
-msgstr "加入我們的行列"
+msgstr "參與我們"
 
 #: ./foreword.md:block 65 (paragraph)
 msgid ""
 "This standard is a living document. [Read our contributor "
 "guide](/CONTRIBUTING.md) to learn how you can make it better."
-msgstr "此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING.md)，瞭解您可以如何讓此標準變得更好。"
+msgstr "本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING."
+"md)，瞭解您可以怎麼做來讓本標準變得更好。"
 
 #: ./foreword.md:block 66 (header)
 msgid "Contact"
@@ -5556,9 +5592,9 @@ msgid ""
 "can find us at [our website](https://publiccode.net/), email us at "
 "info@publiccode.net, or call us at +31 20 2 444 500."
 msgstr ""
-"若有疑問或想進一步瞭解 The Foundation for Public "
-"Code，請造訪[我們的官網](https://publiccode.net/)、寄電子郵件到 "
-"info@publiccode.net，或是撥打我們的電話（+31 20 2 444 500）。"
+"若有疑問，或想進一步瞭解 Foundation for Public "
+"Code，請造訪[我們的網站](https://publiccode.net/)，或是寄電子郵件到 "
+"info@publiccode.net，或撥打我們的電話 +31 20 2 444 500。"
 
 #: ./glossary.md:block 3 (header)
 msgid "Glossary"
@@ -5566,15 +5602,17 @@ msgstr "詞彙表"
 
 #: ./glossary.md:block 4 (header)
 msgid "Code"
-msgstr "規則或代碼 (Code)"
+msgstr "程式或程式碼 (Code)"
 
 #: ./glossary.md:block 5 (paragraph)
 msgid ""
 "Any explicitly described system of rules. This includes laws, policy and "
 "ordinances, as well as source code that is used to build software. Both of "
 "these are rules, some executed by humans and others by machines."
-msgstr "任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始代碼。兩者都"
-"是規則，前者由人類來執行，後者則是機器。"
+msgstr ""
+"任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以"
+"及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是"
+"由機器執行。"
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
@@ -5584,11 +5622,12 @@ msgstr "代碼庫"
 msgid ""
 "Any discrete package of code (both source and policy), the tests and the "
 "documentation required to implement a piece of policy or software."
-msgstr "執行政策或軟體所需的任何離散程式碼套件（原始碼與政策程式碼）、測試與文件。"
+msgstr "執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件的"
+"整套統合包。"
 
 #: ./glossary.md:block 8 (paragraph)
 msgid "This can be, for example, a document or a version-control repository."
-msgstr "可以是文件或是版本控制的儲存庫。"
+msgstr "例如，這可以是文件，或是版本控制的儲存庫。"
 
 #: ./glossary.md:block 9 (header)
 msgid "Continuous integration"
@@ -5599,7 +5638,8 @@ msgid ""
 "In software engineering, continuous integration (CI) is the practice of "
 "merging all developers' working copies to a development branch of a codebase"
 " as frequently as reasonable."
-msgstr "軟體工程的持續整合 (CI) 就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。"
+msgstr "在軟體工程中，持續整合 (CI) "
+"是盡可能頻繁地將所有開發人員工作中的副本，合併回代碼庫開發中分支的實務作法。"
 
 #: ./glossary.md:block 11 (header)
 msgid "Different contexts"
@@ -5610,7 +5650,8 @@ msgid ""
 "Two contexts are different if they are different public organizations or "
 "different departments for which there is not one decision maker that could "
 "make collaboration happen naturally."
-msgstr "如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩個不同的情境。"
+msgstr "只要是不同的公家機關或不同的部門，無法透過同一個決策單位讓協作自然發生，那就"
+"算是兩個不同的情境。"
 
 #: ./glossary.md:block 13 (header)
 msgid "General public"
@@ -5619,24 +5660,27 @@ msgstr "一般大眾"
 #: ./glossary.md:block 14 (paragraph)
 msgid ""
 "The public at large: end users of the code and the services based upon it."
-msgstr "一般民眾：程式碼及以程式碼為基礎的服務的終端使用者。"
+msgstr "整體民眾：程式碼與其所建立的服務的終端使用者。"
 
 #: ./glossary.md:block 15 (paragraph)
 msgid ""
 "For example, a city's residents are considered end users of a city's "
 "services and of all code that powers these services."
-msgstr "舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終端使用者。"
+msgstr "舉例而言，城市的居民視為該城市的服務，以及驅動這些服務運作的程式碼的終端使用"
+"者。"
 
 #: ./glossary.md:block 16 (header)
 msgid "Open source"
-msgstr "開源"
+msgstr "開源或開放原始碼"
 
 #: ./glossary.md:block 17 (paragraph)
 msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
 msgstr ""
-"開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》定義何謂「開源」。"
+"所謂「開源」，是根據 OSI "
+"開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-"
+"annotated)》而來。"
 
 #: ./glossary.md:block 18 (header)
 msgid "Open standard"
@@ -5646,7 +5690,8 @@ msgstr "開放標準"
 msgid ""
 "An open standard is any standard that meets the Open Source Initiative's "
 "[Open Standard Requirements](https://opensource.org/osr)."
-msgstr "任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/osr)的標準就是開放標準。"
+msgstr "任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/"
+"osr)》的標準就是開放標準。"
 
 #: ./glossary.md:block 20 (header)
 msgid "Policy"
@@ -5660,25 +5705,29 @@ msgid ""
 "body within an organization. Policies can assist in both subjective and "
 "objective decision making."
 msgstr ""
-"政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。"
+"政策是一套謹慎設計的原則體系，用來引導決策並達成合理的成果。政策是一種意圖的"
+"聲明，並以程序或協定來執行。政策通常是由組織單位內的理事機構採用執行。政策能"
+"協助做出主觀與客觀的決策。"
 
 #: ./glossary.md:block 22 (paragraph)
 msgid ""
 "Public policy is the process by which governments translate their political "
 "vision into programs and actions to deliver outcomes."
-msgstr "公共政策是政府將其政治理念轉化成計畫與行動的流程，藉此取得成果。"
+msgstr "公共政策是政府將其政治願景，轉化成計畫與行動來取得成果的程序。"
 
 #: ./glossary.md:block 23 (paragraph)
 msgid ""
 "At the national level, policy and legislation (the law) are usually "
 "separate. The distinction is often more blurred in local government."
-msgstr "在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一起。"
+msgstr "在國家層級，政策與立法（法律）通常是分開的；而在地方政府中，這兩者之間的區別"
+"通常比較模糊。"
 
 #: ./glossary.md:block 24 (paragraph)
 msgid ""
 "In the Standard the word 'policy' refers to policy created and adopted by "
 "public organizations such as governments and municipalities."
-msgstr "The Standard for Public Code 當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。"
+msgstr "在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的"
+"政策。"
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
@@ -5688,19 +5737,21 @@ msgstr "公共程式"
 msgid ""
 "Public code is open source software developed by public organizations, "
 "together with the policy and guidance needed for collaboration and reuse."
-msgstr "公共程式是由公家機關開發的開源軟體，當中包括協作與重複利用所需的政策與指引。"
+msgstr "公共程式，是由公家機關所開發的開源軟體，同時包含協作與重複利用所需的政策與指"
+"引。"
 
 #: ./glossary.md:block 27 (paragraph)
 msgid ""
 "Public code is both computer source code (such as software and algorithms) "
 "and public policy executed in a public context, by humans or machines."
-msgstr "公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及公共政策。"
+msgstr "公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以"
+"及公共政策兩者。"
 
 #: ./glossary.md:block 28 (paragraph)
 msgid ""
 "Public code serves the public interest, is open, legible, accountable, "
 "accessible and sustainable."
-msgstr "滿足公共利益的公共程式，具有開放、易讀、負責、可用以及永續的特性。"
+msgstr "服務公眾利益的公共程式，具有開放、易懂、課責、近用、永續等特性。"
 
 #: ./glossary.md:block 29 (paragraph)
 msgid ""
@@ -5709,26 +5760,28 @@ msgid ""
 "development process openly, public code can provide a building block for "
 "others to:"
 msgstr ""
-"為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以："
+"透過獨立於當地情境，但仍可在當地情境下實作的方式，還有公開以文件記錄開發程序"
+"等作法，來開發公共程式。如此，公共程式能作為基礎組件提供給他人，使其得以："
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "re-implement in their local context"
-msgstr "將該公共程式應用於他們的當地情境"
+msgstr "根據其當地情境重新實作"
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "take as a starting point to continue development"
-msgstr "將該公共程式當成起點並接著繼續開發"
+msgstr "作為起點並繼續開發"
 
 #: ./glossary.md:block 30 (unordered list)
 msgid "use as a basis for learning"
-msgstr "當成學習的基礎"
+msgstr "當作學習時的基礎"
 
 #: ./glossary.md:block 31 (paragraph)
 msgid ""
 "To facilitate reuse, public code is either released into the public domain "
 "or licensed with an open license that permits others to view and reuse the "
 "work freely and to produce derivative works."
-msgstr "為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複利用其內容的開放授權，藉此推動衍生工作。"
+msgstr "為了促進重複利用，公共程式通常放到公眾領域發行，或者採取允許他人能自由檢視、"
+"重複利用其成果，甚至產出衍生作品的開放授權。"
 
 #: ./glossary.md:block 32 (header)
 msgid "Repository"
@@ -5740,7 +5793,9 @@ msgid ""
 "and metadata of a codebase. Repositories allow multiple contributors to work"
 " on the same set of files. Repositories are able to store multiple versions "
 "of sets of files."
-msgstr "儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。"
+msgstr ""
+"儲存庫是版本控制工具，用於存放檔案與代碼庫中介資料的儲存位置。儲存庫允許多位"
+"貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。"
 
 #: ./glossary.md:block 34 (header)
 msgid "Source Code"
@@ -5750,7 +5805,7 @@ msgstr "原始碼"
 msgid ""
 "Human readable text of a computer program which can be translated into "
 "machine instructions."
-msgstr "人類可讀並且能夠翻譯成機器指令的電腦程式文字。"
+msgstr "人類可讀，並且能夠翻譯成機器指令的電腦程式文字。"
 
 #: ./glossary.md:block 36 (header)
 msgid "Version control"
@@ -5766,7 +5821,10 @@ msgid ""
 "different versions with each other and to see how content has changed over "
 "time."
 msgstr ""
-"版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程式碼的演變。修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。"
+"版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱"
+"為「*修訂編號*」（或「版次」等類似名稱）的代號作識別。每次修訂都會標示其改動"
+"時間以及作者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異"
+"，以及查看內容隨著時間的變動。"
 
 #: ./index.md:block 3 (header)
 msgid "toc: false"
@@ -5780,7 +5838,8 @@ msgstr "政府開源協作指引"
 msgid ""
 "The Standard for Public Code is a set of criteria that supports public "
 "organizations in developing and maintaining software and policy together."
-msgstr "The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。"
+msgstr "《Standard for Public "
+"Code》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。"
 
 #: ./index.md:block 6 (paragraph)
 msgid ""
@@ -5793,11 +5852,12 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
-"The Standard for Public Code "
-"指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利用前述開源解決方案。The Standard "
-"for Public Code 提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The Standard for Public "
-"Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The Standard for Public Code "
-"適用於各政府層級的代碼庫，從超國家到市政府。"
+"《Standard for Public Code》為那些在建構自身開源解決方案的公家機關提供指引，"
+"以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果"
+"。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《"
+"Standard for Public Code》支持公家機關透過協作方式，創造出好用、開放、易懂、"
+"課責、近用、永續的代碼庫。這份標準從設計之初，就是要用於各種不同政府層級的代"
+"碼庫，小從市政府，大到超國家組織都行。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5805,14 +5865,14 @@ msgid ""
 "code)’ as open source software developed by public organizations, together "
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
-"The Standard for Public Code 將‘[公共程式](glossary.md#public-"
-"code)’定義為由公共組織所開發的開源軟體，並且遵照相關政策與指引，方便協作與重複利用。"
+"《Standard for Public Code》將「[公共程式](glossary.md#public-code)」定義為："
+"由公家機關所開發的開源軟體，同時包含協作與重複使用所需的政策與指引。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
 "The criteria of the Standard for Public Code are aligned with guidelines and"
 " best practices of open source software development."
-msgstr "The Standard for Public Code 當中的標準符合開源軟體開發的指引與最佳實務。"
+msgstr "《Standard for Public Code》當中的準則，符合開源軟體開發的指引與最佳實務。"
 
 #: ./index.md:block 9 (paragraph)
 msgid ""
@@ -5821,7 +5881,7 @@ msgid ""
 "endif%}{% endfor %}"
 msgstr ""
 "{% for page in site.pages %}{% if page.name == \"foreword.md\" %} "
-"額外情境與背景資訊請參閱[序](foreword.md). {% endif%}{% endfor %}"
+"其他情境與背景資訊請參閱[序文](foreword.md). {% endif%}{% endfor %}"
 
 #: ./index.md:block 10 (header)
 msgid "Contents"
@@ -5841,8 +5901,8 @@ msgid ""
 " page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
 "\"index.md\" %}{% if page.title %}"
 msgstr ""
-"[標準](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for page "
-"in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"[準則](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for "
+"page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
 "\"index.md\" %}{% if page.title %}"
 
 #: ./index.md:block 11 (unordered list)
@@ -5861,11 +5921,11 @@ msgstr "[貢獻指引](CONTRIBUTING.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
-msgstr "[行為準則](CODE_OF_CONDUCT.md)"
+msgstr "[行為守則](CODE_OF_CONDUCT.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Governance](GOVERNANCE.md)"
-msgstr "[治理](GOVERNANCE.md)"
+msgstr "[治理方式](GOVERNANCE.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Version history](CHANGELOG.md)"
@@ -5888,10 +5948,11 @@ msgid ""
 "up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
 " to get a call invitation emailed to you."
 msgstr ""
-"我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。 "
-"[議程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-"
-"Code) 在會議前約一週的時間更新。您可以 "
-"[報名](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)，之後舉辦會議時會寄送邀情函給您。"
+"我們通常在每月第一個週四的 15:00 (CET/CEST) "
+"舉辦社群會議。[議程](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code) 在會議前約一週的時間更新。您可以[註冊](https://odoo"
+".publiccode.net/survey/start/"
+"594b9243-c7e5-4bc1-8714-35137c971842)報名，會再寄送會議通話邀請函給您。"
 
 #: ./index.md:block 14 (header)
 msgid "Other resources"
@@ -5903,9 +5964,8 @@ msgid ""
 "Standard](https://publiccodenet.github.io/community-translations-standard/) "
 "in other languages"
 msgstr ""
-"[The Standard for Public Code "
-"社群其他語言](https://publiccodenet.github.io/community-translations-standard/) "
-"非官方翻譯版"
+"本標準非官方的其他語言[社群翻譯](https://publiccodenet.github.io/"
+"community-translations-standard/)"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5913,8 +5973,8 @@ msgid ""
 "assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
 "public sector open source codebases"
 msgstr ""
-"公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/assessment-"
-"eligibility/)"
+"公部門開源代碼庫的〈[標準遵循自我評估](https://publiccodenet.github.io/"
+"assessment-eligibility/)〉"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5923,9 +5983,9 @@ msgid ""
 "template.html) used by Foundation for Public Code stewards for codebase "
 "review"
 msgstr ""
-"The Foundation for Public Code 管理人員審查代碼庫時使用的 [The Standard for Public Code "
-"檢查清單](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
-"template.html)"
+"Foundation for Public Code "
+"管事人員審查代碼庫時所使用的〈[本標準準則檢查清單](https://github.com/"
+"publiccodenet/standard/blob/develop/docs/review-template.html)〉"
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
@@ -5935,7 +5995,8 @@ msgstr "讀者指引"
 msgid ""
 "The Standard describes a number of criteria. All criteria have consistent "
 "sections that make it clear how to create great public code."
-msgstr "公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的公共程式。"
+msgstr "本標準描述說明許多準則。所有準則各小節結構維持一致，來讓讀者清楚明白如何開發"
+"良好的公共程式。"
 
 #: ./readers-guide.md:block 5 (paragraph)
 msgid ""
@@ -5943,13 +6004,14 @@ msgid ""
 "designers\" apply to anyone performing duties associated with these roles, "
 "regardless of their job title. It is common for individuals to have duties "
 "which span multiple roles."
-msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職責的人，不受職稱限制。很多人都承擔多個角色的職責。"
+msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」的稱呼，係指任何履行這些"
+"角色職責的人，不受其職稱限制。常見同時承擔多個角色職責的人。"
 
 #: ./readers-guide.md:block 6 (paragraph)
 msgid ""
 "Below is a brief explanation of each of these sections and how they are used"
 " within the criteria of the Standard."
-msgstr "以下是 The Standard for Public Code 各章節的簡介，以及在標準當中的功用。"
+msgstr "以下是各小節的簡要介紹，以及在本標準準則中的作用。"
 
 #: ./readers-guide.md:block 7 (header)
 msgid "Introduction"
@@ -5959,21 +6021,22 @@ msgstr "前言"
 msgid ""
 "This section explains what the criterion aims to achieve and why it is "
 "important for a codebase's users and contributors."
-msgstr "本章節探討這些標準的目的，以及為什麼對代碼庫使用者與貢獻者很重要的原因。"
+msgstr "本小節說明這些準則想達成的目的，以及為何會對代碼庫使用者與貢獻者來說這麼重要"
+"的原因。"
 
 #: ./readers-guide.md:block 10 (paragraph)
 msgid ""
 "This section lists what needs to be done in order to comply with the "
 "standard."
-msgstr "這章節解釋如何遵循 The Standard for Public Code 。"
+msgstr "這個小節列出如果要遵循本標準，需要完成哪些事項。"
 
 #: ./readers-guide.md:block 11 (paragraph)
 msgid ""
 "The following keywords in this document are to be interpreted as described "
 "in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
 msgstr ""
-"本文件的下列關鍵字，請以 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119)"
-" 中的描述作為詮釋："
+"本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/"
+"rfc2119)》的描述作詮釋："
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST"
@@ -6020,33 +6083,33 @@ msgid ""
 "This section offers actions you can take to see if a contribution is "
 "compliant with the Standard. This is key if you want to operationalize the "
 "Standard."
-msgstr ""
-"本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public Code 。如果您想要實施 The Standard"
-" for Public Code ，這將會是關鍵。"
+msgstr "本小節提供您可採取的行動，來確認貢獻內容是否遵循本標準。如果您想要務實操作本"
+"標準，這部分很關鍵。"
 
 #: ./readers-guide.md:block 15 (paragraph)
 msgid ""
 "We've tried to word it so that someone who is not intimately acquainted with"
 " the subject matter can still do a basic check for compliance."
-msgstr "我們的用字是要讓不熟悉此主題的讀者，看了之後也能夠進行基本的遵循檢測。"
+msgstr "我們已嘗試調整用字，讓即使是不熟悉這類主題內容的讀者，看完之後也能夠進行基本"
+"的遵循檢查。"
 
 #: ./readers-guide.md:block 17 (paragraph)
 msgid ""
 "This section tries to specifically speak to policy makers by offering them "
 "concrete actions they can perform in their role."
-msgstr "本章節主要對象是政策制定者，列出他們的角色能採取的具體行動。"
+msgstr "本小節主要對象是政策制定者，列出他們的角色所能採取的具體行動。"
 
 #: ./readers-guide.md:block 18 (paragraph)
 msgid ""
 "Public policy makers set the priorities and goals of projects and may be "
 "less technologically experienced."
-msgstr "公共政策制定者決定專案的優先順序與目標，在科技上的經驗可能沒那麼多。"
+msgstr "公共政策制定者設定專案的優先順序與目標，而在科技上的經驗可能沒那麼多。"
 
 #: ./readers-guide.md:block 20 (paragraph)
 msgid ""
 "This section tries to specifically speak to managers by offering concrete "
 "actions they can perform in their role."
-msgstr "本章節主要對象是管理人員，列出他們的角色能採取的具體行動。"
+msgstr "本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。"
 
 #: ./readers-guide.md:block 21 (paragraph)
 msgid ""
@@ -6056,23 +6119,25 @@ msgid ""
 " to create the right culture, line up the right resources and provide the "
 "right structures to deliver great services."
 msgstr ""
-"管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源，提供正確的架構，才能夠帶來良好的服務。"
+"管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他"
+"們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的"
+"資源、提供正確的架構等，才能交付優良的服務。"
 
 #: ./readers-guide.md:block 23 (paragraph)
 msgid ""
 "This section tries to specifically speak to developers and designers by "
 "offering them concrete actions they can perform in their role."
-msgstr "本章節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。"
+msgstr "本小節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。"
 
 #: ./readers-guide.md:block 24 (paragraph)
 msgid ""
 "Developers are usually more technically aligned and have more impact on the "
 "delivery of services than the previous groups."
-msgstr "開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務交付的影響更大。"
+msgstr "開發人員通常對技術比較在行，與其他角色類別相比，對服務交付的影響更大。"
 
 #: ./readers-guide.md:block 25 (header)
 msgid "Limitation of scope"
-msgstr "範圍限制"
+msgstr "作用範圍限制"
 
 #: ./readers-guide.md:block 26 (paragraph)
 msgid ""
@@ -6081,8 +6146,8 @@ msgid ""
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
 msgstr ""
-"The Standard for Public Code "
-"不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框架。"
+"《Standard for Public Code》不是為了涵蓋代碼庫的個別實作而撰寫。這代表本標準"
+"不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6093,10 +6158,11 @@ msgid ""
 "Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
 "synergize well with them."
 msgstr ""
-"The Standard for Public Code 有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。因此The "
-"Standard for Public Code 目的並非是要取代品質標準（像是 ISO 25000 認證），或是以安全為準的標準（像是 "
-"[OpenSSF 最佳實務標章](https://github.com/coreinfrastructure/best-practices-"
-"badge)），而是要與他們協作。"
+"此外，雖然《Standard for Public Code》有引用一些標準，並且與其他標準有滿多重"
+"疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，"
+"像是 ISO 25000 認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF "
+"最佳實務標章](https://github.com/coreinfrastructure/best-practices-"
+"badge)等，而是希望能與它們能良好協同搭配。"
 
 #: ./readers-guide.md:block 28 (paragraph)
 msgid ""
@@ -6104,23 +6170,24 @@ msgid ""
 " that a community will spring into existence. That still requires "
 "proactiveness and ambition beyond making the codebase collaboration ready."
 msgstr ""
-"The Standard for Public Code "
-"的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要協作者的積極推動與野心。"
+"《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群"
+"。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要積極主動，以及做到超"
+"越協作以外的企圖心。"
 
 msgid ""
 "script/release-body.sh expects VERSION in the first second-level header"
-msgstr "script/release-body.sh 預期 VERSION 參數在首位第二階層的標頭"
+msgstr "script/release-body.sh 預期 VERSION 放在第一個第二層的標頭中"
 
 msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
-msgstr "script/update-changelog-date.sh 預期 DATE-OF-RELEASE 參數與一個冒號 \":\""
+msgstr "script/update-changelog-date.sh 預期 DATE-OF-RELEASE 與一個冒號「:」"
 
 msgid "Version 0.7.1"
-msgstr "Version 0.7.1"
+msgstr "0.7.1 版"
 
 msgid ""
 "July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
 "clarifies references to code."
-msgstr "2023/07/31: 💄 第十六個草案版本變更準則名稱與釐清參照的程式碼。"
+msgstr "2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。"
 
 msgid ""
 "The criterion \"Make the codebase reusable and portable\" was renamed from "
@@ -6128,32 +6195,32 @@ msgid ""
 msgstr "〈程式碼要可重複使用且可攜〉準則改名為〈代碼庫要可重複使用且可移植〉。"
 
 msgid "Added a glossary entry for \"Source Code\"."
-msgstr "新增詞彙為 \"原始碼\"。"
+msgstr "新增詞彙條目「原始碼」。"
 
 msgid ""
 "References to \"code\" which only applied to \"source code\" now reference "
 "\"source code\" explicitly."
-msgstr "對於只適用於 \"原始碼\" 的 \"程式碼\"，現在明確的引用 \"原始碼\"。"
+msgstr "對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。"
 
 msgid "Clarification of \"running code\" as \"software\"."
-msgstr "釐清 \"運作的程式碼\" 為 \"軟體\"。"
+msgstr "將「運作的程式碼」釐清稱為「軟體」。"
 
 msgid "Minor changes to clarify \"code\" vs \"codebase\"."
-msgstr "微調文字使其清楚呈現 \"程式碼\" 與 \"代碼庫\"。"
+msgstr "細微修改以清楚區分「程式碼」與「代碼庫」。"
 
 msgid "Simplify guidance to policy makers in Bundle policy and source code."
-msgstr "簡易的引導參考給政策制定者在同捆政策與原始碼。"
+msgstr "簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。"
 
 msgid ""
 "Clarify How to test sections of Make the codebase findable and Make the "
 "codebase reusable and portable."
-msgstr "解釋使代碼庫可被發現與使代碼庫可重複使用與移植在如何測試章節中。"
+msgstr "釐清〈代碼庫可查詢得到〉與〈代碼庫要可重複使用且可移植〉的「測試方式」小節。"
 
 msgid "Add a criteria and requirements checklist to the release artifacts."
-msgstr "新增發行成果前，判定標準與必要需求項目的確認清單。"
+msgstr "在發行成品前的要求中，加入準則與需求規定檢查清單。"
 
 msgid "Increase automation of the release process."
-msgstr "提高發行程序的自動化。"
+msgstr "提升發行流程的自動化程度。"
 
 msgid ""
 "![version 0.7.1](assets/version-badge.svg) [![License: "
@@ -6178,12 +6245,13 @@ msgid ""
 "eligibility) that will give you a rough idea of how much work you may need "
 "to do to meet all criteria."
 msgstr ""
-"如果您想要採用公共程式標準於您的代碼庫中，請隨意使用，它是一個開放標準與免費"
-"給任何人使用。如果您希望推廣代碼庫社群期望達成公共程式標準的資格，請使用 "
-"[公共程式標準徽章](assets/standard-for-public-code-commitment.svg) 連結到此份"
-"承諾文件。了解您的代碼庫準備的如何，您可以透過[快速自我檢測](https://publicco"
-"denet.github.io/assessment-"
-"eligibility)粗略的瞭解您還需要準備多少才能符合所有的資格。"
+"若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是"
+"人人都能自由採用的開放標準。如果您希望宣傳代碼庫社群達成《Standard for "
+"Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment "
+"徽章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要"
+"瞭解您代碼庫所達成的程度，可以做[自我資格評估](https://publiccodenet.github."
+"io/assessment-"
+"eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 msgid "Update [`roadmap.md`](roadmap.md)"
 msgstr "更新 [`roadmap.md`](roadmap.md)"
@@ -6191,21 +6259,21 @@ msgstr "更新 [`roadmap.md`](roadmap.md)"
 msgid ""
 "update `docs/standard-for-public-code.html` with the new text from the "
 "review template, updating any status changes as a result"
-msgstr "使用審查範本的新文字更新 `docs/standard-for-public-code."
-"html`，根據結果更新任何狀態"
+msgstr "使用審查範本中的新文字來更新 `docs/standard-for-public-code."
+"html`，會將任何狀態變更作為結果更新"
 
 msgid ""
 "Push branch, compare with 'main' branch, i.e.: "
 "`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
 msgstr ""
-"推送分支，與 `main` 分支比較，如：`https://github.com/publiccodenet/standard/"
-"compare/main...release-$MAJOR.$MINOR.$PATCH`"
+"推送分支，與「main」分支比較，範例：`https://github.com/publiccodenet/"
+"standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
 
 msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
 msgstr "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
 
 msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
-msgstr "移除本地端的標籤（tag）：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr "移除本地端的 tag 標記：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
 
 msgid "Separate executive summary (issue #302)"
 msgstr "分離執行摘要 (issue #302)"
@@ -6213,5 +6281,6 @@ msgstr "分離執行摘要 (issue #302)"
 msgid ""
 "[Standard criteria checklist](/docs/review-template.html) used by Foundation"
 " for Public Code stewards for codebase review"
-msgstr "[標準資格檢查清單](/docs/review-template.html) "
-"由公共程式基金會管理人員用於代碼庫審查"
+msgstr ""
+"Foundation for Public Code 管事人員用於代碼庫審查的〈[標準準則檢查清單](/"
+"docs/review-template.html)〉"

From f50ade8afbb5047a18b8f30bb3a30da412796a7c Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Wed, 13 Sep 2023 10:35:07 +0800
Subject: [PATCH 51/71] update translate

---
 404.md                                        |   8 +-
 AUTHORS.md                                    |  29 +-
 CC0-1.0.md                                    |   4 +-
 CHANGELOG.md                                  | 326 +++++++++---------
 CODE_OF_CONDUCT.md                            |  10 +-
 CONTRIBUTING.md                               | 104 +++---
 GOVERNANCE.md                                 |  16 +-
 README.md                                     | 106 +++---
 criteria/bundle-policy-and-source-code.md     |  76 ++--
 criteria/code-in-the-open.md                  |  37 +-
 criteria/document-codebase-maturity.md        |  38 +-
 criteria/document-codebase-objectives.md      |  24 +-
 criteria/document-the-code.md                 |  45 +--
 criteria/index.md                             |   2 +-
 criteria/maintain-version-control.md          |  45 +--
 criteria/make-contributing-easy.md            |  31 +-
 criteria/make-the-codebase-findable.md        |  56 +--
 ...make-the-codebase-reusable-and-portable.md |  67 ++--
 criteria/publish-with-an-open-license.md      |  37 +-
 criteria/require-review-of-contributions.md   |  49 +--
 criteria/use-a-coherent-style.md              |  37 +-
 criteria/use-continuous-integration.md        |  49 +--
 criteria/use-open-standards.md                |  32 +-
 criteria/use-plain-english.md                 |  35 +-
 criteria/welcome-contributors.md              |  43 +--
 docs/printing.md                              |  18 +-
 docs/releasing.md                             |  66 ++--
 docs/roadmap.md                               |  28 +-
 foreword.md                                   | 151 ++++----
 glossary.md                                   |  57 +--
 index.md                                      |  46 +--
 readers-guide.md                              |  69 ++--
 32 files changed, 884 insertions(+), 857 deletions(-)

diff --git a/404.md b/404.md
index 44827764..7641cbba 100644
--- a/404.md
+++ b/404.md
@@ -8,9 +8,9 @@ toc: false
 
 # 404 找不到網頁
 
-如果您手動輸入網址，請確認網址是否正確。
+如果您是手動輸入網址，請確認網址是否正確。
 
-如果您複製貼上此網址，請確認是否有複製到完整的網址。
+如果您是複製貼上此網址，請確認是否有複製到完整的網址。
 
-若網址正確或是您按下連結或按鈕，請寫信給 [the Foundation for Public Code 人
-員](mailto:info@publiccode.net)，讓我們能夠協助您，並且修正我們的錯誤。
+若網址正確，或您是按下連結或按鈕來的，請寫信給 [Foundation for Public Code 員
+工](mailto:info@publiccode.net)，讓我們協助您，並同時修正我們的錯誤。
diff --git a/AUTHORS.md b/AUTHORS.md
index 17f1e782..f4042c02 100644
--- a/AUTHORS.md
+++ b/AUTHORS.md
@@ -5,36 +5,35 @@
 
 # 作者群
 
-* Alba Roza，[The Foundation for Public Code](https://publiccode.net/)
+* Alba Roza，[Foundation for Public Code](https://publiccode.net/)
 * Arnout Engelen
-* Arnout Schuijff，The Foundation for Public Code
-* 唐鳳，[digitalminister.tw](https://digitalminister.tw/)
-* Ben Cerveny，The Foundation for Public Code
+* Arnout Schuijff，Foundation for Public Code
+* 唐鳳，[數位發展部](https://digitalminister.tw/)
+* Ben Cerveny，Foundation for Public Code
 * Bert Spaan
-* Boris van Hoytema，The Foundation for Public Code
+* Boris van Hoytema，Foundation for Public Code
 * Charlotte Heikendorf
-* Claus Mullie，The Foundation for Public Code
+* Claus Mullie，Foundation for Public Code
 * David Barberi
 * Edo Plantinga，[Code For NL](https://codefor.nl/)
-* Elena Findley-de Regt，The Foundation for Public Code
-* Eric Herman，The Foundation for Public Code
-* Felix Faassen，The Foundation for Public Code
+* Elena Findley-de Regt，Foundation for Public Code
+* Eric Herman，Foundation for Public Code
+* Felix Faassen，Foundation for Public Code
 * Floris Deerenberg
-* Jan Ainali，The Foundation for Public Code
+* Jan Ainali，Foundation for Public Code
 * Johan Groenen，Code For NL
 * Marcus Klaas de Vries
 * Mark van der Net，[阿姆斯特丹市政府](https://www.amsterdam.nl/en/)
-* Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas.com/)，數位媒體與創意產業學院劇
-場與公民媒體系講師
+* Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas.com/)，數位媒體與創意產業學院，
+戲劇與公民媒體系講師
 * Matti Schneider
 * Mauko Quiroga
 * Maurice Hendriks， 阿姆斯特丹市政府
 * Maurits van der Schee，阿姆斯特丹市政府
-* Mirjam van Tiel，The Foundation for Public Code
+* Mirjam van Tiel，Foundation for Public Code
 * Ngô Ngọc Đức Huy
 * Paul Keller
-* Petteri Kivimäki， [Nordic Institute for Interoperability Solutions
-(NIIS)](https://niis.org)
+* Petteri Kivimäki， [北歐互通性解決方案機構 (NIIS)](https://niis.org)
 * Sky Bristol
 * Tamas Erkelens，阿姆斯特丹市政府
 * Timo Slinger
diff --git a/CC0-1.0.md b/CC0-1.0.md
index 26de1d12..4029e1ad 100644
--- a/CC0-1.0.md
+++ b/CC0-1.0.md
@@ -7,12 +7,12 @@ redirect_from:
     - LICENSE.html
 ---
 
-# Creative CC Zero v1.0 Universal 授權
+# 創用 CC0 1.0 通用授權
 
 <!-- TODO FIXME: move styling to the proper place, not inline html -->
 <style>.highlight { flex: 2 2 80%; max-width: 100%; } </style>
 
-此授權為法律合約，允許任何人任意使用本文件任何內容。
+此授權的法律契約，允許任何人任意使用本文件中的任何內容。
 
 ```text
 {% include_relative LICENSE %}
diff --git a/CHANGELOG.md b/CHANGELOG.md
index dcebd58d..21bcdd82 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,245 +6,245 @@
 ---
 # 版本歷史
 
-## Version 0.7.1
+## 0.7.1 版
 
-2023/07/31: 💄 第十六個草案版本變更準則名稱與釐清參照的程式碼。
+2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。
 
-* 準則從 "編寫可重複使用與移植的程式碼" 更名為 "使代碼庫可重複使用與移植"。
-* 新增詞彙為 "原始碼"。
-* 對於只適用於 "原始碼" 的 "程式碼"，現在明確的引用 "原始碼"。
-* 釐清 "運作的程式碼" 為 "軟體"。
-* 微調文字使其清楚呈現 "程式碼" 與 "代碼庫"。
-* 簡易的引導參考給政策制定者在同捆政策與原始碼。
-* 解釋使代碼庫可被發現與使代碼庫可重複使用與移植在如何測試章節中。
-* 新增發行成果前，判定標準與必要需求項目的確認清單。
-* 提高發行程序的自動化。
+* 〈程式碼要可重複使用且可攜〉準則改名為〈代碼庫要可重複使用且可移植〉。
+* 新增詞彙條目「原始碼」。
+* 對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。
+* 將「運作的程式碼」釐清稱為「軟體」。
+* 細微修改以清楚區分「程式碼」與「代碼庫」。
+* 簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。
+* 釐清〈代碼庫可查詢得到〉與〈代碼庫要可重複使用且可移植〉的「測試方式」小節。
+* 在發行成品前的要求中，加入準則與需求規定檢查清單。
+* 提升發行流程的自動化程度。
 
 ## 0.7.0 版
 
-2023年5月31日：📑第十五版新增募資審查紀錄新規定，並且釐清審查流程規定。
+2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。
 
-* 新增規定，紀錄由誰負擔審核貢獻內容費用。
+* 新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。
 * 新增規定，代碼庫必須要有簡短說明。
-* 原本專注在貢獻內容是否符合標準，現在應該專注在貢獻內容審查。
-* 許多「必須（Must）」的規定變更為「應該（Should）」的規定，讓代碼庫更容易找到。
-* 審查HTML格式的範本。
-* 「簡介」轉變為「序」。
-* 已改善貢獻指南。
-* 已改善腳本註解。
+* 原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。
+* 將〈代碼庫可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。
+* 審查範本現在有 HTML 格式。
+* 「前言」轉換為「序文」。
+* 改善貢獻指引。
+* 改善命令稿文件紀錄。
 
 ## 0.6.0 版
 
-2023年4月20日：🔀第十四版新增可移植性與測試的規定，並且介紹每個標準。
-
-* 新增規定，針對多方合作的開發案來編寫可重複使用且可移植的程式碼。
-* 新增規定，針對依賴單一供應商編寫可重複使用且可移植的程式碼。
-* 新增規定，公布自動化測試結果時，必須使用持續整合。
-* 區分兩個安全性規定，一個是有關提供辦法，另一個則是有關安全性的註解。
-* 已重新撰寫規定，將焦點放在代碼庫而非貢獻者行為。
-* 已移除「為什麼這非常重要」以及「不具備以下作用」兩個段落，加入每個標準的介紹。
-* 在標準簡介中，已新增「不具備以下作用」段落。
-* 已新增有關相關政策與授權相容性的公共政策決策者指南。
-* 已新增有關版本控制檔案的開發人員與設計師指南。
-* 已釐清開發人員與設計師指南當中，有關迅速回覆與搜尋引擎優化的內容。
-* 已新增「進一步閱讀無障礙」。
-* 已將各標準的連結與其名稱同步。
-* 已改善網頁版的導覽功能。
-* 已將「進一步閱讀」章節的工具移到社群實施指南。
-* 已將「遵循或認證」流程移到[publiccode.net](https://publiccode.net)。
-* 變更審查範本格式，讓範本在新版本推出後後更容易更新。
-* 已改善到達網頁文字，加入相關資源的連結。
-* 已新增拼字檢查自動化測試。
-* 已稍微調整文字，讓文字更明確與一致。
+2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且每個準則都有一段前言。
+
+* 新增規定，在〈程式碼要可重複使用且可攜〉加入多方協作開發的內容。
+* 新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。
+* 新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。
+* 對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。
+* 重新撰寫規定，將焦點放在代碼庫，而非貢獻者行為。
+* 移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加入前言。
+* 在本標準前言中，加入通用的「此措施辦不到的事」小節。
+* 為政策制定者加入相關政策與授權相容性的指引。
+* 為開發人員與設計師新增檔案要有版本控制的相關指引。
+* 為開發人員與設計師釐清有關快速回應，以及搜尋引擎最佳化的內容。
+* 新增可近用性無障礙環境的「延伸閱讀」內容。
+* 將各準則的連結與其名稱連動。
+* 改善網頁版的導覽功能。
+* 已將「延伸閱讀」小節的工具移到社群實踐指引。
+* 將標準依循或認證相關流程移到 [publiccode.net](https://publiccode.net)。
+* 變更審查範本格式，讓範本在發行新版後更容易更新。
+* 改善著陸引導頁文字，加入相關資源的連結。
+* 新增拼字檢查自動化測試。
+* 微調文字，讓內容更明確與一致。
 * 將 SPDX 標頭換成 yaml 標頭。
 
 ## 0.5.0 版
 
-2023年1月25日：🎨第十三版焦點在於紀錄風格指南。
+2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。
 
-* 調整編碼風格要求，專注在代碼庫上面，而非貢獻者行為。
-* 已變更代碼庫名稱規定，用一般英文更容易搜尋到代碼庫。
-* 已變更使用範例測試程式碼的規定，改為使用「Document the code」的範例來持續整合測試。
-* 調整機讀標準規定，強調程式碼的開放性比可測試性更重要。
-* 調整可查找性的測試規定，減少對搜尋引擎演算法的依賴。
-* 已稍微調整文字，讓文字更明確與一致。
+* 調整程式碼撰寫風格要求，專注於代碼庫上，而非貢獻者行為。
+* 將代碼庫名稱規定，從〈使用白話的英文〉移動到〈代碼庫可查詢得到〉。
+* 將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。
+* 劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。
+* 調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。
+* 微調文字，讓內容更明確與一致。
 
 ## 0.4.1 版
 
-2022年12月5日：📝第十二版闡明文件成熟度。
+2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。
 
-* 文件成熟度端看該版本的代碼庫是否已經可以使用。
-* 文件成熟度不再仰賴尚無法使用的代碼庫中的特定標籤。
-* 審計流程圖現在的由更容易轉譯的格式來生成。
-* 改善「測試方式」指南。
+* 寫下成熟度著重於代碼庫是否已經可供使用，更甚於版本編號。
+* 寫下成熟度不再需要為尚未準備好可供使用的代碼庫加上特定標籤。
+* 稽核流程圖現在以更容易轉譯的格式生成。
+* 改善「測試方式」指引。
 * 新增 publiccode.yml 檔案。
 * 新增審查範本。
-* 一致連結詞彙。
-* 在「貢獻」中新增的實務與標準。
-* 加入 Matti Schneider 到作者群。
+* 一致性連動詞彙表。
+* 在「CONTRIBUTING」中加入要遵循的實務與標準。
+* 將 Matti Schneider 加入作者群。
 * 將剩餘 SPDX 標頭加入檔案中。
-* 稍微修改文字，讓文字更明確。
-* 已更新部分超連結。
-* 已將範例移動到[社群實施指
-南](https://publiccodenet.github.io/community-implementation-guide-standard/)。
+* 再稍微修改些文字，讓文字更明確。
+* 更新部分超連結。
+* 將範例移動到《[社群實踐指
+引](https://publiccodenet.github.io/community-implementation-guide-standard/)》。
 
 ## 0.4.0 版
 
-2022年9月7日：🔭第十一版新增全新的可查找性標準。
-
-* 推出新標準：使代碼庫變得容易查找。
-* 改善多數標準的「測試方式」章節。
-* 「歡迎貢獻者」章節中有關發佈活動統計的新規定。
-* 已移除有關可移植與可重複使用的程式碼的多餘規定。
-* 在開放授權的定義中，加入 OSI 與 FSF 認證的授權。
-* 重新編寫「得以（May）」的相關規定，加入「選擇性（Optional）」一關鍵字，讓規定更明確。
-* 已表明 The Standard for Public Code 標準在適用時應該符合自身規定，且已新增評估。
-* 將 SPDC license identifier 加入檔案中。
-* 已推出新行為守則。
+2022年9月7日：🔭第十一版草稿新增可查找性準則。
+
+* 導入新準則：代碼庫可查詢得到。
+* 改善多數準則的「測試方式」小節。
+* 在〈歡迎貢獻者〉中加入發布活動統計的新規定。
+* 移除可重複使用與移植的程式碼中多餘的規定。
+* 在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。
+* 重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。
+* 表明《Standard for Public Code》應該盡可能符合其自身規定的立場，並加入評估措施。
+* 將 SPDX 授權識別碼加入檔案中。
+* 導入新的行為守則。
 * 解釋原始碼與政策內文的差異。
-* 將規定改為要點清單的格式。
-* 承認代碼庫成熟度在重複使用上的重要性。
-* 將可查找性相關規定移動到新標準。
-* 釐清非開放性標準在代碼庫中的角色。
-* 關於建制時期與執行階段相依性的額外指南。
-* 新增 The Standard for Public Code 開發路徑圖。
-* 更新作者檔案結構。
+* 將規定重新調整為項目要點清單格式。
+* 告知代碼庫成熟度對於重複使用時的重要性。
+* 將可查找性相關規定移動到新準則中。
+* 釐清非開放標準在代碼庫中的角色。
+* 加入建置時期與執行時期依賴項目的額外指引。
+* 新增《Standard for Public Code》的發展路線圖。
+* 更新 Authors 檔案的結構。
 * 將唐鳳加入作者群。
-* 已新增標準清單到印刷版本中。
-* 釐清標準對政策制定者、管理者、開發人員與設計師的意義。
-* 稍微修改文字，讓文字更明確。
-* 已更新部分超連結。
+* 將準則列表加到印刷版本中。
+* 釐清標準對於政策制定者、管理人員、開發人員與設計師等不同身分間的意義。
+* 再稍微修改些文字，讓文字更明確。
+* 更新部分超連結。
 
 ## 0.3.0 版
 
-2022年5月23日：🗎第十版加強註解與本土化。
+2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內容。
 
-* 「編寫可重複使用與可移植程式碼」章節有明確的本土化規定。
-* 治理註解從「應該（Should）」變成「必須（Must）」。
-* 在貢獻指南中，將非常主觀且難以驗證的「貢獻內容必須（Must）有限」規定，改為必須紀錄貢獻的期望，專注在單一議題上。
-* 社群翻譯現在已連結到頁尾中。
-* 還原「用 Mermaid 流程圖取代 BPMN svg」。
+* 在〈程式碼要可重複使用且可攜〉中定下明確的在地化規定。
+* 以文件記錄治理方式的規定，從「應該」等級調升為「必須」。
+* 在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容『必須』小」的規定，改為必須紀錄貢獻所要完成的期待，並一次專注在單一議題上。
+* 社群翻譯連結現在已放到頁尾中。
+* 還原「用 Mermaid 流程圖取代業務流程 BPMN svg」。
 * 細微調整用詞，讓句子更簡單。
-* 已更新部分超連結。
+* 更新部分超連結。
 
 ## 0.2.3 版
 
-2022年3月15日：📜第九版允許在沒有官方翻譯的政策中加入英文版摘要。
+2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策，改為提供政策的英文版摘要。
 
-* 放寬「使用簡單英文」的標準，加入新的規定，允許沒有英文版的同捆政策只需要加入英文版摘要，不用翻譯全文。
-* 同樣地，允許同捆政策與程式碼當中沒有英文版的政策只提供英文版摘要。
-* 釐清「政策」包括能影響同捆政策與程式碼開發與部署的流程。
-* 強調「編寫可重複使用與移植的程式碼」解決方案部分內容的可重複使用性。
-* 將「編寫可重複使用與移植的程式碼」當中的開發人員與設計師指南，加入關於部署到不同專屬平台的內容。
-* 在「使用簡單英文」中，加入管理人員需要使用的非英文詞彙。
-* 變更拉取請求流程圖，從 BPMN 改用 Mermaid，讓[社群翻
+* 放寬〈使用白話的英文〉準則，加入新規定，允許合捆的政策內文如果沒有英文版，只需要加入英文版摘要，而不用翻譯全文。
+* 同樣地，在〈政策與原始碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要。
+* 釐清〈政策與原始碼要合捆〉中，「政策」包含能影響開發與部署的流程。
+* 在〈程式碼要可重複使用且可攜〉中強調解決方案部分內容的可重複使用性。
+* 將〈程式碼要可重複使用且可攜〉當中的開發人員與設計師指引，加入部署到專有平台上的內容。
+* 在〈使用白話的英文〉中，加入管理層在面對非英語詞彙時需要做的事的提點。
+* 變更拉取請求流程圖，從業務流程 BPMN 改用 Mermaid，來讓[社群翻
 譯](https://github.com/publiccodenet/community-translations-standard)更容易。
 * 將 Maurice Hendriks 加入作者群。
-* 將「OpenApi 規格」加入「深入閱讀」。
-* 將「深入閱讀」當中的歸因變得更明確。
-* 稍微修改文字，讓文字更明確。
+* 將「OpenApi 規格」加入延伸閱讀。
+* 將延伸閱讀小節的特性變得更明確。
+* 再稍微修改些文字，讓文字更明確。
 
 ## 0.2.2 版
 
-2021年11月29日：🏛第八版承認當作程式碼來執行的政策，不一定是英文。
-
-* 標示當政策被詮釋為程式碼時，則不用遵守「僅限英文程式碼」的規則。
-* 在「版本管控」中，新增關於提交者電子郵件的「得以（May）」規定。
-* 將政策制定者加入「同捆政策與程式碼」指南。
-* 將開發人員與設計師加入「風格一致」指南。
-* 新增「不同脈絡」到詞彙表中。
-* 將 Mauko Quiroga 與 Charlotte Heikendorf 加入作者群。
-* 新增「數位公共財」認證標章。
-* 加入網頁版「標準」頁面的「上一頁」與「下一頁」連結。
-* 將「開放標準原則」加入「深入閱讀」。
-* 將「簡單語言定義」加入「深入閱讀」。
-* 移動「語意化版本規格」引用的「深入閱讀」。
-* 釐清 publiccode.yml 是描述機讀元資料的名稱之一。
-* 將「您的代碼庫」與「貴組織」改為較不具有所有格的寫法。
-* 稍微修改文字，讓文字更明確。
-* 新增印刷版的建立說明。
+2021年11月29日：🏛第八版草稿認知程式碼所執行的政策，不一定是英文。
+
+* 在「所有程式碼都必須使用英語編寫」規定中，雖然政策也算是一種程式 (code)，但可以保有例外。
+* 在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以」規定。
+* 將政策制定者加入〈政策與原始碼要合捆〉指引中。
+* 將開發人員與設計師加入「風格要前後一致」指引中。
+* 新增「不同情境」到詞彙表中。
+* 將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。
+* 新增「數位公共財」核可徽章。
+* 為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。
+* 將「開放標準」原則加入延伸閱讀。
+* 將「白話語言定義」加入延伸閱讀。
+* 將「語意化版本編號規範」移動為延伸閱讀參考內容。
+* 指出 publiccode.yml 是機器可讀中介資料說明的範例之一。
+* 將「您的代碼庫」與「您的組織單位」改為較不具有所有格的寫法。
+* 再稍微修改些文字，讓文字更明確。
+* 新增印刷版的製作指示。
 
 ## 0.2.1 版
 
-2021年3月1日：🧽跟 0.2.0 版相較之下，第七版做了些微改善。
+2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改善。
 
-* 針對使用分散版本控制系統制定新的「應該」規定，並解釋分散的重要性。
-* 針對被拒絕的貢獻的回饋，比被接受的貢獻的回饋規定更嚴苛。
-* 明確指出著作權與授權聲明也應該要可機讀。
-* 聲明是否為可機讀的測試方式建議。
-* 釐清滾動發行的指南。
+* 新增使用分散式版本控制系統的相關「應該」規定，並解釋分散式的重要性。
+* 針對未被採用的貢獻需要給予回饋，規定要比被接受的貢獻更加嚴格。
+* 明確指出著作權與授權聲明也應該要機器可讀。
+* 聲明是否為機器可讀的測試方式建議。
+* 釐清滾動發行的指引。
 * 釐清詞彙表中「版本控制」的定義。
-* 新增「深入閱讀」，鼓勵提交貢獻、SPDX、Git 以及審查貢獻。
+* 新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項目。
 * 新增有關公共程式概念的影片連結。
-* 更新 BPMN 連結。
+* 更新業務流程 BPMN 連結。
 * 減少重複連結。
 * 將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。
-* 稍微修改文字，讓文字更明確。
+* 再稍微修改些文字，讓文字更明確。
 
 ## 0.2.0 版
 
-2020年10月26日：🎊第六版分拆一項規定並且釐清內容。
-
-* 將「歡迎貢獻」標準分拆為「讓貢獻更容易」以及「歡迎貢獻者」。
-* 將「注意代碼庫成熟度」標準改名為「註解代碼庫成熟度」。
-* 針對多方使用的代碼庫，將「必須（Must）」規定調整為「應該（Should）」規定。
-* 針對著作權讓與，新增「不得（Must Not）」規定。
-* 在可重複使用程式碼規定中，釐清組態的角色。
-* 新增詞彙：持續整合、政策、儲存庫與版本控制。
-* 將「城市」都替換成「公共組織」。
-* 將貢獻者與審查規定分開，藉此釐清程式碼敏感的地方。
-* 將政策制定者、開發人員與設計師加入「深入閱讀」與指南中。
+2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。
+
+* 將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。
+* 將〈注意代碼庫成熟度〉準則改名為〈記錄代碼庫成熟度〉。
+* 針對多方使用的代碼庫，將「必須」等級規定調降為「應該」。
+* 針對著作權轉讓，新增「禁止」規定。
+* 在可重複使用程式碼的規定中，釐清組態設定的角色。
+* 新增詞彙：持續整合、政策、儲存庫、版本控制等。
+* 將「城市」替換成「公家機關」。
+* 將貢獻者與審查人員規定分開為不同項目，以釐清程式碼中較敏感性的層面。
+* 將政策制定者、開發人員與設計師加入延伸閱讀與指引中。
 * 將 Felix Faassen 與 Arnout Engelen 加入作者群。
-* 稍微修改文字，讓文字更明確。
+* 再稍微修改些文字，讓文字更明確。
 
 ## 0.1.4 版
 
-2019年11月27日：🧹第五版主要內容是額外的細部修復。
+2019年11月27日：🧹第五版草稿主要是一些細部修正。
 
-* 已連結 License.md 檔案。
+* 連結 License.md 檔案。
 * 將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。
-* 讓標點符號更連貫，特別是項目符號列表。
+* 讓標點符號使用更一致，特別是項目符號列表。
 * 細部調整文字，讓內容更明確。
 
 ## 0.1.3 版
 
-2019年10月8日：🍂第四版僅針對秋季的清理修復小問題
+2019年10月8日：🍂第四版草稿僅針對秋季所作的清理修正一些小地方
 
 * 將「持續交付」改名為「持續整合」。
-* 在語言標準中引述無障礙指導原則。
-* 改善樣式與一致性。
+* 在語言標準中引用無障礙指導原則。
+* 改善一些樣式，與一致性修正。
 
 ## 0.1.2 版
 
-2019年8月22日：🌠第三版專注在提升文字品質，並且傾聽社群的意見
+2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見
 
-* 一群很棒的貢獻者，讓我們作者群加入許多新血。
+* 好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。
 * 所有連結都是 HTTPS。
-* 一般校對、釐清用字與修改拼字錯誤。
-* 已更新標準：
-   * 在不同脈絡下重複使用的規定
-   * 明確版本控制建議
-   * 多方部署建議
-   * 檔案授權標頭建議
-   * 漏洞回報建議
-   * 明確治理註解建議
+* 一般校對、釐清用字淺詞、修正拼字錯誤等。
+* 更新準則：
+   * 在不同情境背景下重複使用的規定
+   * 明確的版本控制建議
+   * 多方部署的建議
+   * 檔案授權標頭的建議
+   * 漏洞回報的建議
+   * 明確以文件記錄治理方式的建議
 
 ## 0.1.1 版
 
-2019年5月9日：🤔第二版修復基本的疏忽以及許多拼字錯誤
+2019年5月9日：🤔第二版草稿修正一些基本的疏漏，以及許多拼字錯誤
 
-* 移除出現「The Foundation for Public Code」的地方，我們必須改名才能成為協會。
-* 已更新前言。
-* 已更新詞彙表。
-* 已新增行為守則。
+* 移除出現「Foundation for Public Code」的地方，我們之後可能必須改名才能成為協會。
+* 更新簡介。
+* 更新詞彙表。
+* 新增行為守則。
 * 我們建議使用 publiccode.yml 標準，方便重複使用。
 
 ## 0.1.0 版
 
-2019年4月16日：🎉初版已經就緒，內容全新且有許多有趣的全新構想
+2019年4月16日：🎉初版草稿已準備就緒，全新內容，而且有許多有趣的新穎理念
 
-* 14個標準、其規定以及實施方式。
-* 清楚明確的背景介紹、介紹本標準以及 The Foundation for Public Code 會如何使用此標準。
+* 14 項準則，有各自的規定，以及相關的實施方式。
+* 精要的背景介紹，例如本標準是什麼，以及 Foundation for Public Code 如何使用此標準。
 
-第一版是本基金會與阿姆斯特丹應用科學大學以及阿姆斯特丹市政府合作推出，隸屬於[Smart Cities? Public Code! 專
-案](https://smartcities.publiccode.net/)。
+最初的版本是由阿姆斯特丹應用科學大學、阿姆斯特丹市政府，以及本基金會合作撰寫，取自 [Smart Cities? Public Code! 專
+案](https://smartcities.publiccode.net/) 的部分內容。
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index c85c357a..bd491188 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -3,12 +3,12 @@
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-社群很多成員來自具有行為守則的公民或專業背景，但有些人並非如此。本文件表達基金會對所有社群成員以及互動的期望，不論透過何種溝通管道。
+社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。
 
-到這裡來是為了協作。
+來到這裡來是為了協作。
 
-對彼此體貼、尊重以及有耐心。
+請對彼此體貼、尊重，以及有耐心。
 
-努力做出建設性的貢獻。
+努力做出有建設性的行為。
 
-若有問題，請寄送電子郵件到 directors@publiccode.net。
+若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5acbd508..9e6f82cb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,98 +1,102 @@
-# 貢獻給此標準
+# 貢獻此標準
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
 🙇‍♀️ 感謝您的貢獻！
 
-我們理解這樣的標準只能盡可能與公共技術人與、政策制定者與有興趣的人士協作，因此相當感謝您的意見、回饋以及改善此專案的建議，並且對協作抱持開放的態度。
+我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專案的建議。我
+們非常開放任何合作的機會。
 
-我們歡迎每個人提出的議題與拉入請求。如果您對 GitHub 不放心，歡迎將意見用電子郵件傳送到
+我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件計送到
 [info@publiccode.net](mailto:info@publiccode.net)。
 
-## 問題、建議與議題中的問題
+## 問題、建議與議題等
 
-[路徑圖](/docs/roadmap.md)詳盡介紹我們勾勒的開發案。歡迎通報問題、建議變動以及發問，幫助推動本開發案。您可以到[GitHub 的The
-Standard for Public Code 議題](https://github.com/publiccodenet/standard/issues)頁面
-中，為此專案[在 GitHub 上建立議
+[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 [Standard for
+Public Code 的 GitHub Issue](https://github.com/publiccodenet/standard/issues) 頁面
+中，為本專案[提出 GitHub 議
 題](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue)。
 
-或者加入[郵寄清
-單](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)
-並且傳送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。
+或者，註冊加入[郵遞論壇列
+表](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)，
+並寄送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。
 
-不需要修改我們的程式碼或註解也能成為貢獻者！
+您不一定要修改我們的程式碼或文件，也能成為貢獻者！
 
-## 拉入請求中的註解與程式碼
+## 為文件與程式碼提出拉取請求
 
-如果您想要在我們的專案中，為註解或程式碼加添內容，您應該提出拉入請求。
+如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求。
 
-若您從未使用過 GitHub，歡迎先[認識 GitHub
-flow](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加[GitHub
-Skills](https://skills.github.com/)的免費且優質的互動性課程，當中介紹如何使用 GitHub 以及 MarkDown（本專案註解
-所使用的語法）。
+若您從未使用過 GitHub，歡迎先[認識 GitHub 作業流
+程](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加 [GitHub
+Skills](https://skills.github.com/) 免費且優質的互動式課程，當中會介紹該如何使用 GitHub 以及 MarkDown 語法。
+MarkDown 是本專案文件所採用的撰寫語法。
 
-本專案獲得 Creative CC Zero v1.0 Universal 授權，基本上代表本專案與您的貢獻，都屬於公眾領域，任何人都可以任意使用。
+本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可以
+任意使用。
 
-### 1. 作出變更
+### 1. 作出您的修改
 
-貢獻應該[遵守](docs/standard-for-public-code.html)The Standard for Public Code 當中列出的標準。審
-查人員會確保貢獻符合[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否符合[標
-準](#standards-to-follow)且與整體專案有連貫。
+貢獻內容應該[遵守](docs/standard-for-public-code.html)《Standard for Public Code》自身所列出的準則規
+定。審查人員同時也會確保貢獻內容，符合[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標
+準](#standards-to-follow)，且與整體作品有所連貫。
 
-本專案使用[GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-model/)。當
-您複製了此存放庫，請務必依照 GitFlow 模型建立功能分支。
+本專案使用 [GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-model/)。
+當您對此儲存庫作分支以後，請務必依照 GitFlow 模型建立新功能分支。
 
-將您變更內容加入到提交版本[並且附上說
-明](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)。如果需要不
-只一種變更，將相關變更分類在一起，並且放在另一個提交版本。例如修正留白跟文字內容變動，可以放在兩個不同的提交版本中。新增檔案時，選擇容易在「diff」中檢視的格
-式。像是「svg」格式就勝過二元影像。在提交版本訊息中，註解您的選擇與決策，未來每個人都會知道您的選擇。
+將您所作的變更內容加入送交版次，[並附上內容說
+明](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)。如果需要作
+出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如，修正空白，以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
+容易以「`diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉
+擇。
 
-如果您新增程式碼，請確保您有新增與更新相關註解與文字，之後在提出拉入請求。請務必用文字描述新增或修改後的程式碼的作用。
+如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。
 
 #### 適用政策
 
-The Standard for Public Code 目前沒有執行任何特定的公共政策。
+就目前而言，《Standard for Public Code》並非在執行任何特定的公共政策。
 
 #### 風格
 
-The Standard for Public Code 目標是[使用白話的英語](criteria/use-plain-english.md)，拼字採用美式英文。
-文字基本上以每句一行為原則，沒有換行，讓「diff」輸出更容易檢視。但我們要強調更重要的是您可以專注在貢獻上，而不是擔心拼字與排版。我們的審查流程會修正這一部分，
-也會另外再次檢查品質才[推出新版本](docs/releasing.md)。
+《Standard for Public Code》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內
+容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審
+查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
 
 #### 遵守的標準
 
-這些是 The Standard for Public Code 所遵循的標準。請確保您的貢獻也遵循這些標準，才會更容易合併。
+這些是《Standard for Public Code》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。
 
-* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 必要層級關鍵字
-* [網頁無障礙性指導原則 2.1](https://www.w3.org/TR/WCAG21/#readable) - 可讀性
+* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 要求等級關鍵字
+* [網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/#readable) - 易讀性
 
-### 2. 拉入請求
+### 2. 拉取請求
 
-提出拉入請求時，請附帶描述您想要解決的問題以及該拉入請求能修復的議題編號。建議讓一個拉入請求解決一個議題。若一組變動能解決多項議題，請列出所有能解決的議題編號。
+當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列出所有能一併
+修正的議題編號。
 
 ### 3. 改善
 
-所有貢獻都必須接受審查。The Foundation for Public Code 承諾將確保有維護人員來審查貢獻，目標是在兩個工作日內提供意見回饋。
+所有貢獻都必須接受審查。Foundation for Public Code 致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。
 
-維護人員可能可以立即合併您的貢獻。但是通常新拉入請求需要改善，才能夠合併。其他貢獻者（或是輔助機器人）也可能有意見回饋。若是如此，負責審查您貢獻的維護人員，將負責協
-助改善您的註解與程式碼。
+維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若是如此，負責
+審查您貢獻內容的維護人員，將協助您改善文件與程式碼。
 
-若您的註解與程式碼通過人工審查，就會被合併。
+一旦您的文件與程式碼通過人工審查，就會合併。
 
 ### 4. 慶祝
 
-您的構思、註解與程式碼將成為本專案的一部份。您就是我們所需要的開源英雄！
+您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開源英雄！
 
-歡迎您提出拉入請求，將您的名字加入到[`AUTHORS `](AUTHORS.md)檔案中，您的名字可以永遠留在本專案中。
+誠摯歡迎您提出拉取請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) 檔案中，讓您所做的貢獻能銘記在本專案中。
 
-## 其他語言的翻譯
+## 翻譯成其他語言
 
-The Standard for Public Code 雖然沒有官方翻譯，您可以幫助維護現有以及新增[The Standard for Public Code 社
-群翻譯](https://github.com/publiccodenet/community-translations-standard)。
+《Standard for Public Code》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻
+譯](https://github.com/publiccodenet/community-translations-standard)，或是新增翻譯。
 
-## 出版
+## 發行版本
 
-建立[新版本](/docs/releasing.md)與[訂購印刷版標準](/docs/printing.md)有專用註解。
+我們有提供[發行新版本](/docs/releasing.md)，與[訂購印刷版標準](/docs/printing.md)的專用詳細文件。
 
-若要進一步瞭解如何使用與貢獻本專案，請參閱 [`README `](README.md)。
+若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 [`README `](README.md)。
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index ff1548f8..98c7a43d 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -2,17 +2,17 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
+
 # 治理
 
-此標準是[The Foundation for Public Code](https://publiccode.net/)代碼庫管理的核心。我們依照本文件來判斷代碼
-庫是否已經準備好讓社群參與開發。
+本標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管理領域作監督時的核心。我們依照這
+份文件來判斷，某個代碼庫是否已經準備好讓社群共同參與開發。
 
-本標準由 The Foundation for Public Code 人員負責維護。
+這份標準由 Foundation for Public Code 職員負責維護。
 
-[我們歡迎任何人提供修改的建議或是一般意見回饋等貢獻。](/CONTRIBUTING.md)
+[我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。](/CONTRIBUTING.md)
 
-由於 The Standard for Public Code 在我們的核心流程中，扮演舉足輕重的角色，我們也要求遵守 The Standard for
-Public Code 中最嚴苛的標準。
+由於《Standard for Public Code》在我們的核心流程中，扮演至關重要的角色，所以我們會以《Standard for Public Code》的最
+高標準作要求。
 
-我們會努力儘速回覆所有拉入請求。拉入請求讓我們有機會一起合作，改善我們的方法與 The Standard for Public Code。我們可能不會接受貢獻者提出
-的所有修改，但我們會解釋背後的邏輯。
+我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯。
diff --git a/README.md b/README.md
index 3773e268..9c8b7849 100644
--- a/README.md
+++ b/README.md
@@ -1,106 +1,106 @@
-# The Standard for Public Code
+# Standard for Public Code
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-The Standard for Public Code 提供公共組織一個準備開源解決方案的模型，讓他們與其他地方相似的公共組織合作。該標準包含給政策制定者、城市管
-理者、開發人員與供應商的指引。
+《Standard for Public Code》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、
+開發人員與供應商的指引。
 
 ![version 0.7.1](assets/version-badge.svg) [![License:
 CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
 [![標準承
 諾](assets/standard-for-public-code-commitment.svg)](#help-improve-this-standard)
 
-[![頁面-建造-部
-署](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
+[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
 [![測
 試](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)
-[![標準主徽
-章](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
-[![標準開發徽
-章](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
+[![standard main
+badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
+[![standard develop
+badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
 
-The Standard for Public Code 目前為草稿階段。我們正在準備推出1.0版，目前正在幾個代碼庫上測試。
+《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個代碼庫中作測試。
 
-## 將 The Standard for Public Code 套用在您的代碼庫
+## 將《Standard for Public Code》套用您的代碼庫
 
-如果您想要採用公共程式標準於您的代碼庫中，請隨意使用，它是一個開放標準與免費給任何人使用。如果您希望推廣代碼庫社群期望達成公共程式標準的資格，請使用 [公共程式標準
-徽章](assets/standard-for-public-code-commitment.svg) 連結到此份承諾文件。了解您的代碼庫準備的如何，您可以透過
-[快速自我檢測](https://publiccodenet.github.io/assessment-eligibility)粗略的瞭解您還需要準備多少才能符合
-所有的資格。
+若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳代碼庫社群達成
+《Standard for Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment 徽
+章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您代碼庫所達成的程度，可以做[自我
+資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有準
+則，還需要下多少功夫。
 
-將 The Standard for Public Code 套用在您的代碼庫上時，「應該」不用額外說明。若該標準中有任何不明確的地方，鼓勵您在此創建議題，讓我們能
-夠協助您以及其他與您抱持同樣看法的民眾。如需靈感，請參閱[社群打造的實施指
-南](https://publiccodenet.github.io/community-implementation-guide-standard/)，當中包括
-範例與其他訣竅。
+本標準 *應該* 足以自我解釋要如何套用到您的代碼庫中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要一
+點靈感啟發，請參閱[社群製作的《實踐指
+引》](https://publiccodenet.github.io/community-implementation-guide-standard/)，其中包
+括範例與其他提示。
 
-若新版的 The Standard for Public Code 有突破性的修改，The Foundation for Public Code 的代碼庫管理人員會
-幫助The Standard for Public Code 使用者彌補不同版之間的差異。
+若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的代碼庫管事
+人員，會協助標準的實踐者理解該如何銜接之間的落差。
 
-若您想提交您的代碼庫，讓代碼庫能完全遵循此標準並且在未來能取得認證，請寫信與我們聯繫：
-[info@publiccode.net](mailto:info@publiccode.net)，並開始正式[評
+若您致力讓您的代碼庫完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
+[info@publiccode.net](mailto:info@publiccode.net)，以展開正式[評
 估](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment)。
 
 ## 徵求貢獻
 
-我們相信公共政策與軟體應該具有包容、可用、開放、易讀、負責、易懂以及永續的特性。這代表我們需要以新的方式來設計、開發與採購原始碼以及政策註解。
+我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政策文件。
 
-本標準設定代碼庫品質水準，滿足公共組織、機構行政機關以及其他基礎設施服務的需求。
+本標準為代碼庫設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及其他重大基礎設施服務的需求。
 
-The Standard for Public Code 就在
-[standard.publiccode.net](https://standard.publiccode.net/)。內容概覽請參閱
-[`index.md`](index.md)。
+本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。請參閱
+[`index.md`](index.md) 查看整體內容概覽。
 
-[![The Standard for Public Code YouTube 影片縮圖：兩隻手中間放著一本印刷版 The Standard for Public
-Code ](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?
+[![《Standard for Public Code》的影片縮圖：兩隻手中間放著本標準的印刷
+本](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?
 v=QWt6vB-cipE)
 
-[The Standard for Public Code 介紹影片](https://www.youtube.com/watch?v=QWt6vB-cipE)
-from Creative Commons Global Summit 2020 (4:12) on YouTube.
+[《Standard for Public Code》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，出自
+Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。
 
-## 幫忙改善本標準
+## 幫忙改善這份標準
 
-The Foundation for Public Code 致力於維護與開發 The Standard for Public Code ，且品質也會符合該標準本身
-的品質。
+Foundation for Public Code 致力於維護與開發《Standard for Public Code》，且使其同時符合該標準自身的品質水準。
 
-我們在找像您這樣的人對此專案提出[貢獻](CONTRIBUTING.md)，像是建議改善方向以及協助開發。😊若要開始，請先參閱我們的[貢獻者指
-南](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來非常大的價值的貢獻。[治理聲明](GOVERNANCE.md)提到我們管理該標準的
+我們正在尋找像您這樣的人，能對此專案做出[貢獻](CONTRIBUTING.md)，像是建議改善方向，以及協助開發等。😊若要開始，請先參閱我們的[貢獻者指
+引](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。[治理方式聲明](GOVERNANCE.md)中有說明管理該標準的
 方式。
 
-請注意，本專案有其[行為準則](CODE_OF_CONDUCT.md)。參加本專案代表您同意遵守該準則。請善待社群所有成員。
+請注意，本專案配合[行為守則](CODE_OF_CONDUCT.md)一同發行。如果要參加本專案，代表您同意遵守守則。請善待社群的所有其他成員。
 
-## 預覽、建造與部署
+## 預覽、建置、部署
 
-存放庫會上傳到部署於[standard.publiccode.net](https://standard.publiccode.net/)的靜態網站，使用的是
-[GitHub pages](https://pages.github.com)與[Jekyll](https://jekyllrb.com/)。
+儲存庫會建置一個靜態網站，並部署至 [standard.publiccode.net](https://standard.publiccode.net/)。網站採
+用 [GitHub 頁面](https://pages.github.com) 與 [Jekyll](https://jekyllrb.com/) 技術。
 
-當中內容格式就是要使用[Jekyll](http://jekyllrb.com/)來建構，換句話說您需要安裝ruby與ruby-bundler，像是：
+網站內容透過 [Jekyll](http://jekyllrb.com/) 技術建置。這代表您需要有安裝 ruby 與 ruby-bundler，例如：
 
 ```bash
 sudo apt-get install -y ruby ruby-bundler
 ```
 
-如果安裝了`ruby`與`bundle`，就可以執行`bundle install`，用 `script/serve.sh` 腳本來渲染網站。
+一旦安裝好 `ruby` 與 `bundle` 後，就可以執行 `bundle install`，接著再利用 `script/serve.sh` 命令稿轉譯呈現出網
+站成果。
 
 ### 測試
 
-本標準包含許多測試腳本。`script/test-all.sh` 腳本則會開始執行所有本機測試。
+本專案內含許多測試命令稿。其中 `script/test-all.sh` 命令稿則統包執行所有本機測試。
 
-所有腳本都在[腳本](https://github.com/publiccodenet/standard/tree/main/script)檔案夾。
+請前往 [script](https://github.com/publiccodenet/standard/tree/main/script) 資料夾查看命令
+稿。
 
-### 生成 The Standard for Public Code PDF 檔案
+### 生成《Standard for Public Code》的 PDF 檔案
 
-除了 Jekyll 以外，要生成 PDF 檔案也需要仰賴[Weasyprint](https://weasyprint.org/)以及
-[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/)可以將 PDF 轉換成
-`.epub`檔案。
+除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 [Weasyprint](https://weasyprint.org/) 和
+[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/) 則可將 PDF 檔轉換成
+`.epub` 檔。
 
-若要生成這些種類的檔案，則需要安裝類似下列的依附元件：
+若要生成這類檔案，則應該要安裝依賴的軟體項目，例如：
 
 ```bash
 sudo apt-get install -y pandoc qpdf weasyprint
 ```
 
-使用以下腳本，可以將 `standard-print.html` 檔案以及其他的版本檔案轉換成美觀的 PDF：
+使用以下命令稿，可以將 `standard-print.html` 檔案轉換成美觀的 PDF 檔，同時包括其他發行用的檔案：
 
 ```bash
 script/pdf.sh
@@ -110,5 +110,5 @@ script/pdf.sh
 
 © [作者與貢獻者](AUTHORS.md)
 
-The Standard for Public Code 採用 CC 0 [授權](LICENSE)，該授權也涵蓋所有圖解與註解。換句話說，任何人都可以任意使用這些
-內容。如果您是貢獻者，您也將這些權利賦予他人。若要進一步瞭解如何幫助本專案，請參閱[貢獻指南](CONTRIBUTING.md)。
+本標準採用 CC0 公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
+這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。
diff --git a/criteria/bundle-policy-and-source-code.md b/criteria/bundle-policy-and-source-code.md
index 902a49bd..6569e102 100644
--- a/criteria/bundle-policy-and-source-code.md
+++ b/criteria/bundle-policy-and-source-code.md
@@ -5,57 +5,61 @@ order: 2
 redirect_from:
   - criteria/bundle-policy-and-code
 ---
-# 同捆政策與原始碼
 
-使用[原始碼](../glossary.md#source-code)以及[政策](../glossary.md#policy)註解，提供基石給想在當地脈絡使用代碼
-庫的人或是想要對[代碼庫](../glossary.md#codebase)進一步發展有所貢獻的人。
+# 政策與原始碼要合捆
 
-瞭解網域與其政策，才能瞭解代碼庫想要解決的問題以及解決方式。
+對於想根據所在情境實作代碼庫的人，或是想更進一步貢獻[代碼庫](../glossary.md#codebase)開發的人來說，能同時取用[原始
+碼](../glossary.md#source-code)與[政策](../glossary.md#policy)文件兩者，可作為建置成品時的基礎組件。
 
-組織要能夠評估是否在新脈絡中執行代碼庫時，必須先瞭解如何改變其流程或是如何在現有解決方案中提供額外的可配置性，才能在新脈絡中使用該代碼庫。
+瞭解作用範疇與該範疇的政策是基本原則，才能瞭解代碼庫試圖想解決的問題是什麼，以及該如何解決這些問題的作法。
 
-## 規定
+為了評估是否需要在新的情境中實作代碼庫，組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。
 
-* 代碼庫「必須（Must）」包含做為原始碼基礎的政策。
-* 若一個政策以原始碼為基礎，該原始碼「必須（Must）」包含在代碼庫內（用於詐騙偵測的原始碼除外）。
-* 政策格式「應該（Should）」可以機讀且明確。
-* [持續整合](../glossary.md#continuous-integration) 測試「應該（Should）」驗證原始碼與政策是否有一致執行。
+## 需求規定
+
+* 代碼庫「必須」包含原始碼所根據的政策。
+* 如果政策根據原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始碼則可除外。
+* 政策「應該」採用機器可讀且明確的格式。
+* [持續整合](../glossary.md#continuous-integration)測試「應該」驗證原始碼與政策是否有一致執行。
 
 ## 測試方式
 
-* 與公務人員確認有收錄做為原始碼基礎的完整政策。
-* 與公務人員確認有收錄做為政策基礎的完成原始碼。
-* 確認政策是否可由機器判讀。
-* 透過持續整合測試，確認原始碼與政策的一致執行。
+* 與公務人員確認原始碼所根據的所有政策內容都有收錄在內。
+* 與公務人員確認政策所根據的所有原始碼都有收錄在內。
+* 確認政策內容是否能在機器上解讀。
+* 確認原始碼與政策間的執行一致性能通過持續整合測試。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 與開發人員及設計師合作，確認政策程式碼與原始碼沒有錯配。
-* 提供相關政策內文，用來收錄在[存放庫](../glossary.md#repository)中；若內文沒有英文版本，則請提供英文摘要。請務必附上貴機構所遵循的標
-準，以及影響貴機構代碼庫開發或部署脈絡的組織流程。
-* 引用支持政策的文字並附上連結。
-* 用明確且可機讀的格式（像是[對象管理組織](https://www.omg.org/spec/)發佈的格式）來紀錄政策。
-* 利用[相同的版本控制l](maintain-version-control.md)以及用來追蹤原始碼的註解，來追蹤政策。
-* 定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否依舊符合[政策意圖](document-codebase-objectives.md)。
-* 納入影響社群、代碼庫與發展的政策，包括[一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是
-[歐盟無障礙指令](https://ec.europa.eu/digital-single-market/en/web-accessibility)這些法律義
-務，或是人權政策，像是公共組織對機會平等的承諾。
+* 與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。
+* 提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單
+位所選擇遵守的各項標準，以及影響貴組織單位代碼庫開發或部署情境的任何組織單位流程。
+* 請提供政策相關參考資料與連結。
+* 政策內容請使用明確且機器可讀的格式，像是[物件管理群體](https://www.omg.org/spec/)所發表的格式。
+* 追蹤政策時，請使用與追蹤原始碼[相同的版本控制系統](maintain-version-control.md)與文件。
+* 定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否仍然符合[政策意圖](document-codebase-objectives.md)。
+* 納入會影響社會群體、代碼庫與開發目標的相關政策，包含 [GDPR 一般資料保護規
+則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟網頁無障礙命
+令](https://ec.europa.eu/digital-single-market/en/web-accessibility)等此類法律義務，或者是人權政
+策，例如公家機關對機會平等的承諾等。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
-* 在整個開發流程中，讓政策制定者、開發人員與設計師全程參與。
-* 確保政策制定者、開發人員與設計師有同樣的目標。
+* 讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。
+* 確保政策制定者、開發人員與設計師朝相同目標努力。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 熟悉並且學會使用貴機構的政策制定者所使用的流程模型標記法。
-* 與政策制定者合作，確保政策程式碼與原始碼沒有錯配。
-* 針對如何讓政策註解更明確提供意見回饋。
+* 熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。
+* 與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。
+* 針對如何讓政策文字更清楚提供意見。
 
 ## 延伸閱讀
 
-* 維基百科的[商業流程模型與標記
+* 維基百科上的 [BPMN 業務流程模型與標記
 法](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)。
-* Trisotech的[BPMN快速指南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。
-* 維基百科的[決策模型與標記法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)。
-* 維基百科的[案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。
+* Trisotech 提供的 [BPMN 快速指
+南](https://www.bpmnquickguide.com/view-bpmn-quick-guide/)。
+* 維基百科上的 [DMN 決策模型與標記
+法](https://en.wikipedia.org/wiki/Decision_Model_and_Notation)。
+* 維基百科上的[ CMMN 案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。
diff --git a/criteria/code-in-the-open.md b/criteria/code-in-the-open.md
index 05277ff2..bac381e3 100644
--- a/criteria/code-in-the-open.md
+++ b/criteria/code-in-the-open.md
@@ -3,40 +3,41 @@
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 order: 1
 ---
-# 以開放精神編寫原始碼
+# 原始碼要開放
 
-開放的編碼能夠提高透明度、改善[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽查，並且讓協作更容易。
+以開放精神編寫原始碼，能改善資訊透明、提高[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽核，也能促進互相協作。
 
-這讓市民更能夠瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公共組織的互動。
+這些加在一起，讓公民更有機會瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公家機關的互動。
 
-## 規定
+## 需求規定
 
-* 任何使用中政策的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。
-* 任何使用中軟體的原始碼（用於偵測詐欺的原始碼除外）都必須公開，且能供民眾取用。
-* 代碼庫「不允許」包含使用者、使用者機構或第三方的敏感資料。
-* 目前沒有使用的任何原始碼（像是新版本、提案或舊版本）都「應該（Should）」公佈。
-* 可選擇是否要紀錄支撐[社會大眾](../glossary.md#general-public)與任何組織互動的原始碼或政策。
+* 任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
+* 任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
+* 代碼庫「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。
+* 目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。
+* 「可選擇」是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或
+支持的政策。
 
 ## 測試方式
 
-* 確認目前使用的所有版本的原始碼，都有公佈在網路上，且非原始貢獻組織的民眾無須任何形式的驗證或認證也可以看到。
-* 確認[代碼庫](../glossary.md#codebase)檔案與提交紀錄不包含敏感性資訊。
-* 檢查現在沒有使用的原始碼是否有公開。
+* 確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。
+* 確認[代碼庫](../glossary.md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。
+* 檢查目前非使用中的原始碼是否有公開。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 以開放精神制定政策。
+* 制定合乎開放精神的政策。
 * 以公開透明的政策為優先。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 孕育擁抱開放、重視學習、歡迎意見回饋的文化。
 * 與外部供應商和自由工作者以開放精神的方式協作。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 審查人員在檢核每次的程式碼提交紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。
-* 為符合上述敏感性資訊的相關規定，請明確分開資料與程式碼。
+* 審查人員在檢核每次的送交版次紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。
+* 為符合上述敏感性資訊的相關規定，請明確分開資料與原始碼。
 
 ## 延伸閱讀
 
diff --git a/criteria/document-codebase-maturity.md b/criteria/document-codebase-maturity.md
index 201369a9..47a84058 100644
--- a/criteria/document-codebase-maturity.md
+++ b/criteria/document-codebase-maturity.md
@@ -8,43 +8,43 @@ redirect_from:
 ---
 # 記錄代碼庫成熟度
 
-清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用或為該代碼庫做出貢獻。代碼庫成熟度包括其依附元件的成熟度。瞭解
-代碼庫的演變，才能真正認識該代碼庫並且做出貢獻。
+清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用，或為該代碼庫做出貢獻。代碼庫版本的成熟度，包含其依賴項目的成
+熟度。瞭解代碼庫演進到什麼程度，是理解該代碼庫並知道如何做出貢獻的關鍵。
 
-## 規定
+## 需求規定
 
-* 代碼庫必須註明版本編號。
-* 代碼庫必須明確標示是否有已經準備好使用的版本。
-* 準備好可供使用的代碼庫版本，必須只能依賴其他也已經準備好可供使用的代碼庫版本。
-* 代碼庫應該包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
-* 應該有文件記錄分配版本識別碼的方式。
-* 可選擇是否使用語意化版本控制。
+* 代碼庫「必須」註明版本編號。
+* 代碼庫「必須」明確以文件記錄，是否有已經準備好可供使用的版本。
+* 準備好可供使用的代碼庫版本，「必須」只能依賴其他也已經準備好可供使用的代碼庫版本。
+* 代碼庫「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
+* 「應該」要以文件記錄分配版本識別碼的方法。
+* 「可選擇」是否使用語意化版本控制編號。
 
 ## 測試方式
 
 * 確認代碼庫有版本編號策略，且有文件記載該策略。
-* 確認政策制定者、管理人員、開發人員與設計師都相當清楚代碼庫是否有準備好可供使用的版本。
-* 確認準備好可供使用的代碼庫版本，並不依賴尚未準備好可供使用的其他代碼庫的任何版本。
-* 確認有記錄並遵守代碼庫的版本控制方式。
+* 確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道代碼庫是否有準備好可供使用的版本。
+* 確認準備好可供使用的代碼庫版本，並不依賴任何尚未準備好可供使用的其他代碼庫的版本。
+* 確認有文件記錄代碼庫的版本編號方法，並且確實遵守。
 * 確認是否有版本的變動紀錄。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [程式碼](../glossary.md#source-code) 都必須先
+* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [原始碼](../glossary.md#source-code) 都必須先
 經過測試與改善，才能夠投入服務。
 * 考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
-* 要確認服務依賴的代碼庫成熟度等同或高於服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。
+* 要確認服務依賴的代碼庫版本成熟度，等同或高於該服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 確認所有發行都遵守代碼庫版本控制方式。
+* 確認所有發行版，都有遵守代碼庫的版本控制編號作法。
 
 ## 延伸閱讀
 
-* 許多代碼庫使用「[語意化版本控制規範](https://semver.org/)」來標示版本。
+* 許多代碼庫使用「[語意化版本編號規範](https://semver.org/)」來標示版本。
 * [軟體發行生命週期](https://en.wikipedia.org/wiki/Software_release_life_cycle)
 * 澳洲數位轉型局《[服務設計與交付流
 程](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process)》。
diff --git a/criteria/document-codebase-objectives.md b/criteria/document-codebase-objectives.md
index 7375b456..c52cd031 100644
--- a/criteria/document-codebase-objectives.md
+++ b/criteria/document-codebase-objectives.md
@@ -5,33 +5,33 @@ order: 8
 redirect_from:
   - criteria/document-objectives
 ---
-# 記錄代碼庫目標
 
-清楚記錄[代碼庫](../glossary.md#codebase)目標能傳達代碼庫的目的。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能幫助民眾判斷
-目前或未來是否會對此代碼庫（或其模組之一）有興趣。
+# 代碼庫要有目標文件
 
-## 規定
+以文件清楚記錄[代碼庫](../glossary.md#codebase)目標，來傳達代碼庫的用途目標。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能
+方便人們判斷，是否在當下或未來，會對此代碼庫或其模組感興趣。
 
-* 代碼庫必須包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
-* 代碼庫文件應該清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
-* 可選擇是否以文件記錄給[一般民眾](../glossary.md#general-public)看的代碼庫目標。
+## 需求規定
+
+* 代碼庫「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
+* 代碼庫文件「應該」清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
+* 「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-public)看的代碼庫目標。
 
 ## 測試方式
 
 * 確認代碼庫文件有包含代碼庫目標，或主旨、使命等。
 * 查看政策目標與代碼庫目標之間關聯的描述。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 將政策目標加入代碼庫文件中，例如「`README`」文件當中。
-* 確保所有代碼庫目標都有相關支持政策文件的連結或參考資料，才能符合[政策與原始碼要合捆](bundle-policy-and-source-code.md)的標
-準。
+* 確保所有代碼庫目標，有連結或引用為了符合[政策與原始碼要合捆](bundle-policy-and-source-code.md)準則而加入的支持政策文件。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。
 
diff --git a/criteria/document-the-code.md b/criteria/document-the-code.md
index 1d89b78f..d68052ad 100644
--- a/criteria/document-the-code.md
+++ b/criteria/document-the-code.md
@@ -5,45 +5,46 @@ order: 9
 redirect_from:
   - criteria/documenting
 ---
-# 記錄程式碼
 
-詳細記錄的[程式碼](../glossary.md#source-code)幫助民眾瞭解該原始碼的作用與使用方式。記錄文件是幫助民眾開始使用[代碼
-庫](../glossary.md#codebase)並且更快做出貢獻的關鍵。
+# 程式碼要有文件
 
-## 規定
+文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作用與使用方式。文件紀錄是幫助人們快速上手[代碼
+庫](../glossary.md#codebase)的使用並做出貢獻的關鍵。
 
-* 代碼庫、[政策](../glossary.md#policy)與程式碼的所有功能，都必須以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。
-* 代碼庫文件必須說明如何安裝與執行軟體。
-* 代碼庫文件必須為關鍵功能舉出範例。
-* 代碼庫文件應該包含精要的說明，讓[一般民眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
-* 代碼庫文件應該有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。
-* 代碼庫文件應該包含所有功能的範例。
-* 程式碼文件應該描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
-* 應該要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。
-* 可選擇是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。
+## 需求規定
+
+* 代碼庫的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。
+* 代碼庫文件「必須」說明如何安裝與執行軟體。
+* 代碼庫文件「必須」為關鍵功能舉出範例。
+* 代碼庫文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
+* 代碼庫文件「應該」有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。
+* 代碼庫文件「應該」包含所有功能的範例。
+* 程式碼文件「應該」描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
+* 「應該」要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。
+* 「可選擇」是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。
 
 ## 測試方式
 
-* 確認文件內容能讓其他利害關係人、其他公共組織的專業人士，以及一般民眾，都可以清楚明白。
+* 確認文件內容能讓其他利害關係人、其他公家機關的專業人士，以及一般大眾，都可以清楚明白。
 * 確認文件有說明如何安裝與執行原始碼。
 * 確認文件有包含主要功能的範例。
-* 向一般民眾的成員以及記者確認，他們是否能明白文件當中的精要說明。
+* 向一般大眾的成員以及記者確認，他們是否能明白文件當中的精要說明。
 * 檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。
 * 檢查文件中列舉的所有功能都包含範例。
 * 檢查文件中是否包含高層架構圖，或類似的組件關係圖表。
-* 確認整合測試有包含到程式碼文件品質，例如確認生成的文件正確無誤，並檢查連結與圖片等。
+* 確認整合測試有包含到程式碼文件品質，例如確認生成的文件是否正確，並檢查連結與圖片等。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 定期檢查代碼庫中非政策程式碼的變動。
-* 針對如何讓非政策文字更清楚提供意見。
+* 定期查看代碼庫中非政策程式碼的變動情況。
+* 針對如何讓非政策文件更清楚易懂提供意見回饋。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
-* 嘗試使用代碼庫，讓您的意見回饋可以讓政策與原始碼文件更清楚。舉例來說，目前的文件是否足以說服另一個公共組織的管理人員使用本代碼庫？
+* 嘗試使用代碼庫，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，目前的文件是否足以說服另一個公家機關的管理人員使用這個代碼庫？
 * 確保您同時瞭解政策、原始碼以及文件內容。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 定期查看代碼庫中非原始碼部分的變動情況。
 * 針對如何讓非原始碼文件更清楚易懂提供意見回饋。
diff --git a/criteria/index.md b/criteria/index.md
index b31f6f67..d4dbee16 100644
--- a/criteria/index.md
+++ b/criteria/index.md
@@ -3,7 +3,7 @@
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 order: 0
 ---
-# 標準
+# 準則
 
 {% assign sorted = site.pages | sort:"order" %}
 
diff --git a/criteria/maintain-version-control.md b/criteria/maintain-version-control.md
index af6ae7e1..741e4cf9 100644
--- a/criteria/maintain-version-control.md
+++ b/criteria/maintain-version-control.md
@@ -5,34 +5,35 @@ order: 6
 redirect_from:
   - criteria/version-control-and-history
 ---
+
 # 維護版本控制
 
 [版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md#source-code)以及其他[代碼
-庫](../glossary.md#codebase)檔案歷來的變動。這能讓您維護代碼庫有條理的變動歷史文件。這是大規模協作能運作的要素，因為幫助開發人員針對修改
-變動平行作業，並幫助未來的開發人員瞭解修改的原因。
+庫](../glossary.md#codebase)檔案歷來的變動。這能讓您為代碼庫維護有條理的變動歷史文件。這是大規模協作能運作的要素，使開發人員得以針對修改
+變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。
 
-## 規定
+## 需求規定
 
-* 代碼庫中的所有檔案皆必須有版本控制。
-* 所有決定皆必須記錄成提交訊息。
-* 每份提交訊息皆必須盡可能附上討論與議題連結。
-* 代碼庫應該以分散式版本控制系統作維護。
-* 貢獻準則應該要求貢獻者將相關的修改變動提交內容作群組分類。
-* 維護人員應該使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。
-* 貢獻準則應該鼓勵採用方便版本控制系統檢視檔案修改內容的檔案格式。
-* 貢獻者可選擇是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
+* 代碼庫中的所有檔案皆「必須」有版本控制。
+* 所有決定皆「必須」記錄成送交版次訊息。
+* 每份送交版次訊息皆「必須」盡可能附上討論與議題連結。
+* 代碼庫「應該」以分散式版本控制系統作維護。
+* 貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。
+* 維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。
+* 貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。
+* 貢獻者「可選擇」是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
 
 ## 測試方式
 
 * 確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。
-* 審查提交內容歷史紀錄，確認所有的提交訊息皆有解釋之前程式碼修改變動的原因。
-* 審查提交內容歷史紀錄，確認所有提交訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。
+* 審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。
+* 審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。
 * 檢查版本控制系統是否為分散式。
-* 審查提交內容歷史紀錄，檢查是否有根據貢獻指南將相關的程式碼變動以群組分類。
+* 審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。
 * 檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。
-* 檢查代碼庫時，在可能的情況下檔案都是採用文字格式。
+* 檢查代碼庫在可能的情況下，檔案都是採用文字格式。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
    * 政策改變的地方，
@@ -40,16 +41,16 @@ redirect_from:
 
 舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 確認版本控制系統具有瞭解程式碼、組建與部署所需的所有檔案。
-* 提交內容的訊息要寫清楚，讓人一看就能瞭解提交修改的原因。
+* 確認版本控制系統中，有瞭解程式碼、建置與部署所需的所有檔案。
+* 送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。
 * 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。
-* 提交內容的訊息要寫清楚，方便之後比較各版本。
+* 送交版次訊息要寫清楚，方便之後比較各版本。
 * 在政策改變以後與政策制定者合作，說明原始碼更新的內容。
 
 ## 延伸閱讀
@@ -58,7 +59,7 @@ redirect_from:
 彙](https://producingoss.com/en/vc.html#vc-vocabulary)》。
 * 英國政府數位服務團《[維護程式碼的版本控
 制](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding)》。
-* GitHub 提供的「[GitHub技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
+* GitHub 提供的「[GitHub 技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
 * GitHub 提供的「[Git 密技
 表](https://education.github.com/git-cheat-sheet-education.pdf)」列出了最常用的 git 指
 令。
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
index d58263e7..1237ddf3 100644
--- a/criteria/make-contributing-easy.md
+++ b/criteria/make-contributing-easy.md
@@ -5,17 +5,18 @@ order: 5
 ---
 # 貢獻要容易
 
-若要開發變得更好、更可靠且功能更豐富的軟體，使用者必須要能夠為共享的[代碼庫](../glossary.md#codebase)修復問題與新增功能。
+若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[代碼庫](../glossary.md#codebase)修正問題、新增功能，以及提出安全性議題
+等。
 
-共享的數位基礎建設讓協作貢獻更容易。代碼庫能接受的貢獻需要的心力越少，使用者越可能成為貢獻者。
+共享的數位基礎建設讓協作貢獻更容易。使用者讓代碼庫接受貢獻時所需付出的心力越少，則使用者越可能成為貢獻者。
 
-## 規定
+## 需求規定
 
-* 代碼庫必須有個可以公開接受任何人建議的議題追蹤器。
-* 文件中必須同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。
-* 代碼庫必須要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表如，郵寄清單。
-* 必須有辦法透過封閉的管道通報安全性問題。
-* 文件必須說明，如何私下透過封閉的管道通報潛在的安全性與敏感性問題。
+* 代碼庫「必須」有個可以公開接受任何人建議的議題追蹤器。
+* 文件中「必須」同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。
+* 代碼庫「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。
+* 「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。
+* 文件「必須」說明，該如何通報潛在的安全性與敏感性問題。
 
 ## 測試方式
 
@@ -25,21 +26,21 @@ order: 5
 * 確認有封閉的管道通報安全性問題。
 * 確認有說明如何私下通報安全性問題。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。
 * 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 跟[審查](require-review-of-contributions.md)一樣，務必迅速回應請求。
-* 告知管理人員您支持其他貢獻者時所需的時間與資源。
-* 確保民眾可輕易找到合適的溝通管道來問維護人員與利害關係人問題，例如「`README`」文件當中。
-* 確保中介資料包含合適的聯絡資訊，例如在 publiccode.yml 檔案中。
+* 與[審查](require-review-of-contributions.md)流程相同，務必迅速回應請求。
+* 告知管理人員，您在支援其他貢獻者時所需的時間與資源。
+* 確保人們可輕鬆找到合適的溝通管道，來詢問維護人員與利害關係人問題，例如寫在「`README`」文件當中。
+* 確保中介資料包含合適的聯絡資訊，例如寫在 publiccode.yml 檔案中。
 
 ## 延伸閱讀
 
diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index 44a8cb3f..25665247 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -8,59 +8,59 @@ redirect_from:
 
 # 代碼庫可查詢得到
 
-一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，必
-須主動積極。
+一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，更
+需要主動積極。
 
 有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄列
 表之中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。
 
-## 規定
+## 需求規定
 
-* 代碼庫名稱應該要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
-* 代碼庫說明應該要簡短，幫助他人瞭解代碼庫的性質與作用。
-* 維護人員應該將代碼庫提交至相關的軟體目錄上。
-* 代碼庫應該要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。
-* 在搜尋引擎查找代碼庫名稱時，應該能搜尋得到代碼庫。
-* 在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，應該能搜尋得到代碼庫。
-* 代碼庫應該具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
-* 代碼庫應該包含機器可讀的中介資料說明，例如採用
+* 代碼庫名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
+* 代碼庫說明「應該」要簡短，幫助他人瞭解代碼庫的目的與作用。
+* 維護人員「應該」將代碼庫提交至相關的軟體目錄上。
+* 代碼庫「應該」要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。
+* 在搜尋引擎查找代碼庫名稱時，「應該」能搜尋得到代碼庫。
+* 在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，「應該」能搜尋得到代碼庫。
+* 代碼庫「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
+* 代碼庫「應該」包含機器可讀的中介資料說明，例如採用
 [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。
-* 可選擇是否為代碼庫設定專用的網域名稱。
-* 可選擇是否在社群舉辦的會議中定期進行簡報。
+* 「可選擇」是否為代碼庫設置專用的網域名稱。
+* 「可選擇」是否在社群舉辦的會議中定期進行簡報。
 
 ## 測試方式
 
 * 檢查代碼庫名稱是否描述說明其用途，且不包含雙關語。
-* 檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是首字母縮寫字或縮寫比完整名稱更熟為人知。
-* 檢查代碼庫是否不包含組織單位品牌名稱或抬頭等（除非組織單位也是代碼庫社群成員）。
+* 檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完整名稱更熟為人知。
+* 檢查代碼庫是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是代碼庫社群成員。
 * 檢查代碼庫儲存庫是否包含代碼庫的簡短描述。
 * 檢查代碼庫有刊登在相關軟體型錄上。
 * 檢查代碼庫的網站有描述代碼庫能夠解決的問題。
-* 檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
-* 檢查以自然語言（例如簡短說明來搜尋時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果的第一頁中。
+* 檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將代碼庫列在搜尋結果中。
+* 檢查以自然語言來作搜尋，例如使用代碼庫的簡短描述時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果中。
 * 檢查永久唯一識別碼條目有提及主要貢獻者。
 * 檢查永久唯一識別碼條目中有包含儲存庫位置。
 * 檢查永久唯一識別碼條目有列出代碼庫網站。
 * 檢查中介資料說明檔案是機器可讀的格式。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 貢獻一段說明此代碼庫作用的政策領域或處理的問題的描述。
-* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
-* 在相關會議上作簡報介紹代碼庫如何執行[政策](../glossary.md#policy)。
+* 貢獻一段說明此代碼庫作用的政策領域，或處理的問題的描述。
+* 請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。
+* 在相關會議上作簡報，介紹代碼庫如何執行[政策](../glossary.md#policy)。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。
-* 使用簡短描述說明參照代碼庫的地方，例如社群媒體帳號說明。
+* 在引用到代碼庫的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。
 * 為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。
-* 確保專案參與人員出席相關會議或作簡報介紹。
+* 確保專案參與人員出席相關會議，或作簡報介紹。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 搜尋引擎最佳化，例如新增[網站地圖](https://www.sitemaps.org/protocol.html)。
-* 在參照代碼庫的地方，都使用簡短描述，例如儲存庫的說明。
-* 請對代碼庫不熟悉且不同領域的同儕來測試您的問題描述。
+* 搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol.html)。
+* 在引用到代碼庫的地方，都使用簡短描述，例如放到儲存庫中的說明。
+* 請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。
 * 推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。
 
 <p style="page-break-after: always;"></p>
diff --git a/criteria/make-the-codebase-reusable-and-portable.md b/criteria/make-the-codebase-reusable-and-portable.md
index 153ceda9..38ce5210 100644
--- a/criteria/make-the-codebase-reusable-and-portable.md
+++ b/criteria/make-the-codebase-reusable-and-portable.md
@@ -6,58 +6,59 @@ redirect_from:
   - criteria/reusable-and-portable-codebases
   - criteria/create-reusable-and-portable-code
 ---
-# 使代碼庫可重複使用且具可攜性
 
-編寫可重複使用且具可攜性的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師能重複使用、測試與改善目前已開發的內容，並將改善貢獻回
-代碼庫中，如此可提高品質、降低維護成本、增強可靠性。
+# 代碼庫要可重複使用且可移植
 
-以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方分享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫更可以從
-能自我運作的社群中獲益。
+編寫可重複使用且可移植的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻
+回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。
 
-以文件記錄良好的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
+以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方共享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫，更可以
+從能自我運作的社群中獲益。
+
+以文件記錄周全的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
 境](../glossary.md#different-contexts)中重複利用。
 
-如果原始碼不依賴任何貢獻者、供應商或部署的特定情況專用基礎架構，任何貢獻者都能測試該原始碼。
+原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢獻者都能測試該原始碼。
 
-## 規定
+## 需求規定
 
-* 代碼庫必須開發成能在不同情境中重複使用。
-* 執行與瞭解代碼庫時，不得仰賴於任何採用保密、無法揭露、專有或非開放式授權的程式碼或服務。
-* 代碼庫應該有多方單位使用。
-* 發展路線圖應該有多方單位的需求影響。
-* 代碼庫開發應該由多方單位合作。
-* 應該使用組態設定方式以將[程式碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。
-* 代碼庫應該能夠在地化。
-* 原始碼與其文件不應該包含特定情況專用的資訊。
-* 代碼庫模組應該以使其能夠在其他情境中重複利用的模式撰寫文件。
-* 軟體不應該要求只有單一供應商能提供的服務或平台。
+* 代碼庫「必須」開發成能在不同情境中重複使用。
+* 代碼庫「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，以供執行與瞭解。
+* 代碼庫「應該」有多方單位使用。
+* 發展路線圖「應該」有多方單位的需求影響。
+* 代碼庫開發「應該」由多方單位協作。
+* 「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。
+* 代碼庫「應該」能夠在地化。
+* 原始碼與其文件「不應該」包含特定情況專用的資訊。
+* 代碼庫模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。
+* 軟體「不應該」要求僅有單一供應商能提供的服務或平台。
 
 ## 測試方式
 
 * 與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行。
-* 確認代碼庫不需要用到任何專有或非開放式授權的程式碼或服務，就能夠執行。
-* 若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作的意願。
-   * 或是如果代碼庫非常成熟與穩定，鮮少需要修復或貢獻：
-      * 檢查是否有多方單位或是有在多種情境下正使用代碼庫。
-      * 檢查是否有文件記錄下合作的承諾以及承諾的預算。
+* 確認代碼庫不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。
+* 若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意圖跡象。
+   * 或是如果代碼庫非常成熟與穩定，鮮少需要修正、改善或貢獻：
+      * 檢查是否有多方單位，或是有在多種情境下正使用代碼庫。
+      * 檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。
    * 若是沒有，則：
-      * 檢查是否有多方單位或是有在多種情境下正使用代碼庫。
+      * 檢查是否有多方單位，或是有在多種情境下正使用代碼庫。
       * 檢查代碼庫貢獻者是否來自多方單位。
-* 檢查代碼庫檔案與提交歷史紀錄中，不包含特定情況專用的資料。
+* 檢查代碼庫檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。
 * 檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。
 * 確保代碼庫有將貴組織單位列為已知使用者。
-* 列出貴團隊想要合作的其他組織。
+* 找出貴團隊想要協作的其他組織單位。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。
-* 確認您的團隊與其他團隊協作。
+* 確認您的團隊與其他團隊能相互協作。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 原始碼應該設計成：
 
@@ -66,10 +67,10 @@ redirect_from:
 * 以邏輯上具有意義且獨立的模組構成，
 * 如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。
 
-確保代碼庫文件中，有說明程式的組建時間與執行時期的依賴項目。如果您的情境需要將程式部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就
-能進行開發、使用、測試、部署等。
+確保代碼庫文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行
+開發、使用、測試、部署等。
 
-在每份提交內容中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。
+在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。
 
 ## 延伸閱讀
 
diff --git a/criteria/publish-with-an-open-license.md b/criteria/publish-with-an-open-license.md
index 6e4e8cfc..2021ceb1 100644
--- a/criteria/publish-with-an-open-license.md
+++ b/criteria/publish-with-an-open-license.md
@@ -5,22 +5,23 @@ order: 13
 redirect_from:
   - criteria/open-licenses
 ---
+
 # 發行採用開放授權
 
-有了開放且熟為人知的授權，任何人都可以看到[原始碼](../glossary.md#source-code)、認識其運作方式、任意使用原始碼，並且貢獻給[代碼
-庫](../glossary.md#codebase)。這也讓供應商能建立以代碼庫為中心的生態系。
+採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-code)，使其能瞭解運作方式、自由使用，並且能為[代碼
+庫](../glossary.md#codebase)做出貢獻。這也能促進供應商建立出以代碼庫為中心的生態系。
 
-明確標示代碼庫中每一個檔案的授權，幫助使用者正確重複利用與引用代碼庫的內容。
+明確指出代碼庫中每一個檔案的授權，讓使用者能正確重複利用代碼庫的部分內容，並表彰作者名稱。
 
-## 規定
+## 需求規定
 
-* 所有程式碼與文件，皆必須採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。
-* 軟體原始碼必須採用[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
+* 所有原始碼與文件，皆「必須」採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。
+* 軟體原始碼「必須」採用[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
 款](https://spdx.org/licenses/)。
-* 所有程式碼皆必須搭配授權條款檔案一併發行。
-* 不得要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。
-* 代碼庫中所有原始碼檔案，皆應該包含機器可讀的著作權聲明與授權條款標頭內容。
-* 可選擇是否為不同類型的原始碼與文件採用多重授權條款。
+* 所有原始碼皆「必須」搭配授權條款檔案一併發行。
+* 「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。
+* 代碼庫中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容。
+* 「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。
 
 ## 測試方式
 
@@ -29,31 +30,31 @@ redirect_from:
 單](https://spdx.org/licenses/)，以及文件的授權條款有[符合「開放定
 義」](https://opendefinition.org/licenses/)。
 * 確認代碼庫中有包含其採用的授權條款檔案。
-* 確認貢獻指南中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
+* 確認貢獻指引中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
 * 在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 制定要求原始碼必須採用[開放原始碼](../glossary.md#open-source)授權的[政策](../glossary.md#policy)。
-* 制定抑制採購非開放原始碼授權程式碼與非開放科技的政策。
+* 制定抑制採購非開放原始碼授權程式碼，與非開放科技的政策。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
-* 只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。
+* 只與能採用開放原始碼授權，交付與發行其原始碼的開放原始碼軟體供應商合作。
 * 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」
 的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。
 * 每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。
-* 代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。
+* 當代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
 
 * 開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
-* 紐西蘭 CC Aotearoa《[創用CC介紹動畫影
+* 紐西蘭CC Aotearoa《[創用CC介紹動畫影
 片](https://creativecommons.org/about/videos/creative-commons-kiwi)》。
 * 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授
 權資訊。
diff --git a/criteria/require-review-of-contributions.md b/criteria/require-review-of-contributions.md
index 441dc1b5..ec4d2e02 100644
--- a/criteria/require-review-of-contributions.md
+++ b/criteria/require-review-of-contributions.md
@@ -5,55 +5,56 @@ order: 7
 redirect_from:
   - criteria/require-review
 ---
+
 # 要求審查貢獻內容
 
-同儕審查貢獻是[原始碼](../glossary.md#source-code)品質的關鍵，降低安全性風險與營運風險。
+同儕審查貢獻是[原始碼](../glossary.md#source-code)提升品質的關鍵，也能降低安全性風險與營運風險。
 
-要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，發
-現與修復潛在錯誤的機率。得知所有原始碼都會被審查，就不會孕育出怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。
+要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，就
+發現與修正潛在臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。
 
-快速審查的[政策](../glossary.md#policy)，向貢獻者保證在一段時間內提供意見回饋或是合作改善， 進而提高貢獻者交付貢獻內容的頻率以及參與熱
-度。
+快速審查[政策](../glossary.md#policy)在於向貢獻者保證，必定在一段時間內提供意見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參
+與的熱度。
 
-## 規定
+## 需求規定
 
-* 所有被接受或是提交給代碼庫正式發行版本中的貢獻內容，都必須經過另一位貢獻者審查。
-* 審查必須包含原始碼、政策、測試與文件等。
-* 如果不接受貢獻內容，審查人員必須提供意見回饋。
-* 審查流程應該確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。
-* 審查內容應該包含執行軟體與執行代碼庫測試。
-* 貢獻內容應該由與貢獻者不同背景情境的人來審查。
-* 版本控制系統不應該在代碼庫的正式發行版本中，接受未經審查的貢獻內容。
-* 審查應該在兩個工作天內進行。
-* 可選擇是否由多位審查人員進行審查。
+* 所有被接受或是送交給代碼庫正式發行版本中的貢獻內容，都「必須」經過另一位貢獻者審查。
+* 審查「必須」包含原始碼、政策、測試、文件等。
+* 如果不接受貢獻內容，審查人員「必須」提供意見回饋。
+* 審查流程「應該」確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。
+* 審查內容「應該」包含執行軟體與執行代碼庫測試。
+* 貢獻內容「應該」由與貢獻者不同背景情境的人來審查。
+* 版本控制系統「不應該」在代碼庫的正式發行版本中，接受未經審查的貢獻內容。
+* 審查「應該」在兩個工作天內進行。
+* 「可選擇」是否由多位審查人員進行審查。
 
 ## 測試方式
 
-* 確認歷史紀錄中每個提交內容都有經過不同的貢獻者審查。
+* 確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。
 * 確認審查內容包含原始碼、政策、測試、文件等。
 * 針對未被採用的貢獻內容，確認有適當解釋原因。
-* 檢查審查人員指引有涵蓋是否遵循標準、架構、代碼庫指引等。
-* 檢查審查人員在審查時是否有執行程式與測試。
-* 與審查人員確認，提交的內容是否有經過不同情境背景的不同貢獻者審查。
+* 檢查審查人員指引中，有包含是否遵循標準、架構、代碼庫指引等指示。
+* 檢查審查人員在審查時是否有執行軟體與測試。
+* 與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。
 * 檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。
 * 檢查貢獻提交與審查之間的時間間隔。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 制定進行任何審查時，含程式碼與其他一切事物，都要恪遵「四眼原則」的政策。
+* 制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。
 * 採用具有審查與意見回饋功能的版本控制系統或作業流程。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 將交付妥善軟體作為共同目標。
 * 確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。
 * 創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。
 * 確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。
-* 當他人請求您審查時，請盡快回覆，並先給出程式碼需要修正之處背後的概念。
+* 當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。
 
 ## 延伸閱讀
 
diff --git a/criteria/use-a-coherent-style.md b/criteria/use-a-coherent-style.md
index 87fb4d46..97b7793b 100644
--- a/criteria/use-a-coherent-style.md
+++ b/criteria/use-a-coherent-style.md
@@ -5,43 +5,44 @@ order: 15
 redirect_from:
   - criteria/style
 ---
+
 # 風格要前後一致
 
-採用前後一致的風格，讓不同環境的貢獻者能夠合作。用詞統一能減少貢獻者之間在溝通上的摩擦。
+採用前後一致的風格，讓不同環境的貢獻者能夠一同合作。用詞統一能減少貢獻者之間在溝通上的摩擦。
 
-## 規定
+## 需求規定
 
-* [代碼庫](../glossary.md#codebase)必須遵守程式碼撰寫風格指南、或文件寫作風格指南，可以是代碼庫社群自身的風格指南，或是代碼庫有採用的既
-有風格。
-* 貢獻內容應該通過自動化的風格測試。
-* 風格指南應該描述對較複雜的程式碼區段，當中列內註解與說明文件的期望。
-* 可選擇是否將[可理解的白話英語](use-plain-english.md)小節加入風格指南之中。
+* [代碼庫](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作風格指引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用
+的既有風格。
+* 貢獻內容「應該」通過自動化的風格測試。
+* 風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與寫下說明文件的期待。
+* 「可選擇」是否將[可理解的白話英語](use-plain-english.md)期望加入風格指引之中。
 
 ## 測試方式
 
-* 確認貢獻內容有遵循文件中指定的風格指南。
+* 確認貢獻內容有遵循文件中指定的風格指引。
 * 檢查是否有自動化的風格測試。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 為[政策](../glossary.md#policy)與文件建立風格指南，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或
+* 為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或
 「`README`」檔案。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-如果代碼庫還沒有工程指南，或其他貢獻者指南，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是
-「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指南方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
-的其他層面。指南應該包含貢獻的[原始碼](../glossary.md#source-code)預期該符合哪些要求，才會被維護人員加入代碼庫中，包含原始碼、測試、
-文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指南演進。
+如果代碼庫還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是
+「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
+的其他層面。指引應該包含貢獻的[原始碼](../glossary.md#source-code)預期該符合哪些要求，才會被維護人員合併至代碼庫中，包括原始碼、測
+試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。
 
 此外：
 
-* 使用程式碼品質分析工具 (linter)。
-* 在代碼庫中加入程式碼品質分析工具的組態設定。
+* 使用 linter 程式碼品質梳理工具。
+* 在代碼庫中加入 linter 梳理工具的組態設定。
 
 ## 延伸閱讀
 
diff --git a/criteria/use-continuous-integration.md b/criteria/use-continuous-integration.md
index 7f2c3d0b..86140dbb 100644
--- a/criteria/use-continuous-integration.md
+++ b/criteria/use-continuous-integration.md
@@ -5,58 +5,59 @@ order: 12
 redirect_from:
   - criteria/continuous-integration
 ---
+
 # 使用持續整合
 
-開發人員頻繁地將其撰寫的程式碼合併至共享的分支，並且由自動化測試驗證，就能進行非同步協作。合併程式碼的頻率越頻繁且每次貢獻內容越少，合併上的衝突就越容易解決。
+透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同步協作。合併的頻率越頻繁，貢獻的規模越小，在合併時所發生的衝突就越容易解決。
 
-自動化測試所有功能，讓人更能相信貢獻內容發揮其功用且沒有造成任何錯誤，並且允許審查人員專注在貢獻的結構與方式。測試越集中，就越容易發現與瞭解出現的問題。
+自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。
 
-以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，能幫助貢獻者瞭解對貢獻內容的期待。透過持續整合
-可以更輕易地監督 [代碼庫](../glossary.md#codebase)狀態。
+以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監
+督[代碼庫](../glossary.md#codebase)狀態變得更為簡單。
 
-## 規定
+## 需求規定
 
-* [原始碼](../glossary.md#source-code)中的所有功能都必須有自動化測試。
-* 所有貢獻內容都必須先通過自動化測試，才能上傳至代碼庫。
-* 代碼庫必須有說明貢獻內容結構的相關準則。
-* 代碼庫必須有能夠審查貢獻內容的活躍貢獻者。
-* 應該公開貢獻的自動化測試結果。
-* 代碼庫準則應該規定每次做出貢獻時，都應只聚焦在單一議題上。
-* 應該監督原始碼測試與文件的涵蓋範圍。
-* 可選擇是否測試[政策](../glossary.md#policy)和文件，與原始碼間有無一致性，或是反之亦然。
-* 可選擇是否測試政策和文件所採用的樣式，以及連結有無失效。
-* 可選擇是否使用文件範例來測試軟體。
+* [原始碼](../glossary.md#source-code)中的所有功能，都「必須」有自動化測試。
+* 所有貢獻內容都「必須」先通過自動化測試，才能上傳至代碼庫。
+* 代碼庫「必須」有解說如何撰寫貢獻內容結構的相關指引。
+* 代碼庫「必須」有能夠審查貢獻內容的活躍貢獻者。
+* 「應該」公開貢獻內容的自動化測試結果。
+* 代碼庫指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。
+* 「應該」監督原始碼測試與文件的涵蓋範圍。
+* 「可選擇」是否測試[政策](../glossary.md#policy)和文件，與原始碼之間有無一致性，或是反之亦然。
+* 「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。
+* 「可選擇」是否使用文件中的範例來測試軟體。
 
 ## 測試方式
 
 * 確認有測試可用。
 * 確認原始碼覆蓋率工具能檢查到 100% 的原始碼。
 * 確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。
-* 確認有貢獻準則說明貢獻內容的結構。
+* 確認有貢獻指引解說如何撰寫貢獻內容的結構。
 * 確認最近三個月內有貢獻內容上傳。
 * 檢查是否可以查看測試結果。
-* 檢查是否已經公佈原始碼覆蓋率數據。
+* 檢查是否有公布原始碼覆蓋率數據。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。
 * 確保政策文件也有設好自動化測試。
-* 如果政策文件未能通過測試，請立即修正。
-* 確保原始碼能反映出政策的任何變動（請參閱[維護版本控制](maintain-version-control.md)）。
+* 如果政策文件未能通過測試，請快速修正。
+* 確保原始碼能反映出政策的任何變動（請參閱〈[維護版本控制](maintain-version-control.md)〉）。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 確保能儘快且經常給真正的終端使用者進行測試。
 * 以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。
 * 聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。
 * 發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-* 協助管理階層擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。
+* 協助管理人員擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。
 * 協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。
 * 協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。
-* 編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體配置失敗等資源耗盡情況，都是難以創造的典型案例。
+* 編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體分配失敗等資源耗盡情況，都是難以創造的典型案例。
 * 調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。
 * 經常部署。
 * 至少每天整合工作內容一次。
diff --git a/criteria/use-open-standards.md b/criteria/use-open-standards.md
index 5fbf8f6a..9a410303 100644
--- a/criteria/use-open-standards.md
+++ b/criteria/use-open-standards.md
@@ -5,20 +5,22 @@ order: 11
 redirect_from:
   - criteria/open-standards
 ---
+
 # 採用開放標準
 
-[開放標準](../glossary.md#open-standard)保證可以取得重複利用與貢獻[代碼庫](../glossary.md#codebase)所需的
-知識。不僅能為不同的系統之間建立互通性，也降低廠商套牢的可能性。開放標準如果明確，就可以獨立發展任何方向的資料交換。
+[開放標準](../glossary.md#open-standard)保證可以取得使用與貢獻[代碼庫](../glossary.md#codebase)所需的知
+識。不僅能為不同的系統之間建立互通性，更降低廠商套牢的可能性。開放標準如果明確，不同方就可以各自獨立開發作資料交換。
 
-## 規定
+## 需求規定
 
-* 代碼庫如要達成促進資料交換的特性，就必須採用符合[開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。
-* 如果有使用到任何的非開放標準，則必須在文件中清楚記錄。
-* 代碼庫採用的任何標準，皆必須在文件中清楚列出，並且只要有的話，就附上該標準的連結。
-* 代碼庫採用的任何非開放標準，皆不得妨礙代碼庫的協作與重複使用。
-* 如果還沒有已存在的開放標準可採用，則應該投入開發新標準。
-* 採用開放標準時，應該優先選擇可經機器測試的開放標準。
-* 採用非開放標準時，應該優先選擇可經機器測試的非開放標準。
+* 代碼庫如要促進資料交換的特性，就「必須」採用符合[OSI 開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標
+準。
+* 如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。
+* 代碼庫選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標準的連結。
+* 代碼庫選擇採用的任何非開放標準，皆「禁止」妨礙代碼庫的協作與重複使用。
+* 如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。
+* 採用開放標準時，「應該」優先選擇可經機器測試的開放標準。
+* 採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。
 
 ## 測試方式
 
@@ -26,19 +28,19 @@ redirect_from:
 * 確認若有採用任何的非開放標準，皆有清楚記錄在文件中。
 * 確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-* 以政策要求盡可能在任何情況下使用開放標準。
+* 以政策要求盡可能在任何情況下採用開放標準。
 * 禁止採購不採用開放標準的技術科技。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 考慮在 [原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。
-* 審查提交紀錄與其他[儲存庫](../glossary.md#repository)資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。
+* 審查送交版次與[儲存庫](../glossary.md#repository)其他資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。
 
 ## 延伸閱讀
 
diff --git a/criteria/use-plain-english.md b/criteria/use-plain-english.md
index acc38fb3..500dd19f 100644
--- a/criteria/use-plain-english.md
+++ b/criteria/use-plain-english.md
@@ -5,25 +5,26 @@ order: 10
 redirect_from:
   - criteria/understandable-english-first
 ---
+
 # 使用白話的英語
 
-英文是軟體開發的 <i>慣用</i>協作語言。
+英語是軟體開發領域中的<i>實際</i>協作語言。
 
-選民應該都能獲得當地公家機關資訊。簡單且白話的語言，讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。
+公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。
 
-透過翻譯可以讓更多人認識[代碼庫](../glossary.md#codebase)。代碼庫語言越是簡單明暸，翻譯與維護翻譯的成本就越低。
+翻譯可以讓更多人有機會認識[代碼庫](../glossary.md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。
 
-## 規定
+## 需求規定
 
-* 代碼庫的所有文件都必須使用英語。
+* 代碼庫的所有文件都「必須」使用英語。
 * 所有[原始碼](../glossary.md#source-code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀
 當作程式碼的部分則除外。
-* 任何合捆的政策如果沒有英語版本，則必須隨附英語版摘要。
-* 任何翻譯版本皆必須跟隨英語版本更新，以維持在最新狀態，反之亦然。
-* 代碼庫中不應該使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
-* 根據《[網頁內容近用性無障礙指南 2](https://www.w3.org/WAI/WCAG21/quickref/?
+* 任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。
+* 任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。
+* 代碼庫中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
+* 根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/?
 showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。
-* 可選擇是否提供任何程式碼、文件、測試等的翻譯版。
+* 「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。
 
 ## 測試方式
 
@@ -34,17 +35,17 @@ showtechniques=315#readable)》的建議，文件內容應該以國中識讀程
 * 確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。
 * 檢查文件的拼字、文法與易讀性等。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在
 使用這些詞彙的地方加上詞彙表連結。
 * 以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
 * 經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
 * 詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。
@@ -52,9 +53,9 @@ showtechniques=315#readable)》的建議，文件內容應該以國中識讀程
 <p style="page-break-after: always;"></p>
 ## Further reading
 
-* 根據 W3C 全球資訊網協會《[網頁內容近用性無障礙指南 2.1 與 3.1 之可讀
-性](https://www.w3.org/TR/WCAG21/#readable)》內文，撰寫的文字內容要更容易閱讀與理解。
+* 符合 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1、3.1 之可讀
+性](https://www.w3.org/TR/WCAG21/#readable)》要求，撰寫的文字內容要容易閱讀與理解。
 * 歐盟委員會的《[歐盟無障礙環境命
-令](https://ec.europa.eu/digital-single-market/en/web-accessibility)》就是無障礙法規的例
-子。
+令](https://ec.europa.eu/digital-single-market/en/web-accessibility)》，是高度要求無障礙環境
+的法規範例。
 * 美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/)》。
diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index 938e70d4..92967171 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -5,43 +5,44 @@ order: 4
 redirect_from:
   - criteria/open-to-contributions
 ---
+
 # 歡迎貢獻者
 
-[代碼庫](../glossary.md#codebase)社群氛圍幫助我們選擇要使用的代碼庫。 歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且自我運作。一個社群當
-中，若貢獻者有明確的方式來影響代碼庫、社群目標與進展，該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並且相信代碼庫社群的治理。
+[代碼庫](../glossary.md#codebase)的社群氛圍會影響使用者選擇所要使用的代碼庫。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。
+若貢獻者有明確的方法可以影響代碼庫、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並信任代碼庫社群的治理方式。
 
-## 規定
+## 需求規定
 
-* 代碼庫必須允許任何人針對代碼庫提出修改建議。
-* 代碼庫必須包含貢獻指引，說明歡迎貢獻者貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
-* 代碼庫必須以文件記錄代碼庫提交、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
-* 貢獻指引應該說明由誰負責審查貢獻的成本。
-* 代碼庫應該宣布投入其開發與維護工作的參與組織單位。
-* 代碼庫應該要有可公開取得的發展路線圖。
-* 代碼庫應該公布代碼庫的活動統計數據。
-* 可選擇是否為代碼庫加入貢獻者的行為準則。
+* 代碼庫必須「允許」任何人對代碼庫提出修改建議。
+* 代碼庫「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
+* 代碼庫「必須」以文件記錄代碼庫、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
+* 貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。
+* 代碼庫「應該」宣布投入其開發與維護工作的參與組織單位。
+* 代碼庫「應該」要有可公開取得的發展路線圖。
+* 代碼庫「應該」公布代碼庫的活動統計數據。
+* 「可選擇」是否為代碼庫加入貢獻者的行為守則。
 
 ## 測試方式
 
 * 確認可以提交修改建議給代碼庫。
 * 確認代碼庫有貢獻指引。
-* 確認代碼庫有清楚解釋治理架構，並包含如何對代碼庫治理施加影響。
-* 確認貢獻指引是否有說明由誰負責審查貢獻的成本。
+* 確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理的方法。
+* 確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。
 * 檢查是否有參與的組織單位名單。
 * 檢查是否有發展路線圖。
 * 檢查是否有公布活動統計數據。
-* 檢查是否有行為準則。
+* 檢查是否有行為守則。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
 * 為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。
 * 考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
 * 確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。
 * 如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。
-* 若有需要，確保如同代碼庫社群所同意的，編列貢獻審查流程的預算。
+* 若有需要，確認您有編列貢獻內容審查流程的預算，且通過代碼庫社群同意。
 * 確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。
 * 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
 
@@ -49,14 +50,14 @@ redirect_from:
 ## Developers and designers: what you need to do
 
 * 快速回應請求。
-* 告知管理人員您支持其他貢獻者時所需的時間與資源。
-* 清楚告知貢獻者他們該如何才能讓貢獻內容合併到程式碼中。
+* 告知管理人員，您在支援其他貢獻者時所需的時間與資源。
+* 清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到代碼庫中。
 
 ## 延伸閱讀
 
-* 開放原始碼指南所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
+* 開放原始碼指引所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
 * Mike McQuaid《[開放原始碼貢獻者瓶
 頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
-* 開放原始碼指南為成長中的[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治
+* 《開放原始碼指引》針對推動[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治
 理](https://opensource.guide/leadership-and-governance/)》。
 * Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。
diff --git a/docs/printing.md b/docs/printing.md
index 24cbcb46..f631e666 100644
--- a/docs/printing.md
+++ b/docs/printing.md
@@ -3,20 +3,20 @@
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-The Standard for Public Code 由 Reclameland 負責印刷。本指南提供印刷相關資訊，方便在 Reclameland 或其他地方印
-刷。
+《Standard for Public Code》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方
+印刷。
 
-印刷詳細資訊（依照 Reclameland 網頁上的順序，需要的地方有附上荷蘭語）：
+印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）：
 
-* 樣式：平裝書([Reclameland產品頁面](https://www.reclameland.nl/drukken/softcover-boeken))
+* 樣式：平裝書 ([Reclameland 產品頁面](https://www.reclameland.nl/drukken/softcover-boeken))
 * 紙張尺寸：A4
-* 直橫向：直向（Staand）
+* 直向或橫向：直向 (Staand)
 * 內頁印刷：正四反四，雙面全色印刷
 * 內頁材質：Biotop 90克
-* 封面：350克封面
-* 封面印刷：正四（單面滿版印刷）
-* 封面材質：單面霧面立體字封面（Enke）
-* 頁數：書內頁數 + 4 + x，x 是 0-3頁，因此總頁數是4的倍數
+* 封面：350 克封面
+* 封面印刷：正四反空，單面滿版印刷
+* 封面處理：單面霧面層剝處理 (Enke)
+* 頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數
 * 個別封裝：無
 
 一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。
diff --git a/docs/releasing.md b/docs/releasing.md
index d9d44ade..9a08a545 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -1,46 +1,48 @@
-# 發行新版本的 The Standard for Public Code
+# 發行新版本的《Standard for Public Code》
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-1. 審查「develop」分支狀態
-   - 確保該版本的內容都已經完成合併
-   - 請人校對目前的分支狀態
-      - 如果有另外加入破折號，檢查是否能簡化文字並且移除破折號，改用較簡易的句子。如果需要複雜的句子，檢查是否能用其他符號來取代破折號。如果破折號最適合用來表達該句子的
-涵義，請遵守[芝加哥格式手冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)。
+1. 審查「develop」分支的狀態
+   - 確認預計收入該次發行版的所有變更都已完成合併
+   - 邀請校對該分支目前的狀態
+      - 如果有引入新的破折號，檢查是否能簡化文字並且移除破折號，例如改用較簡易的句子。如果需要用到複雜的句子，檢查是否能用其他標點符號來取代破折號。如果破折號最適合用來
+表達該句子的涵義，則請遵守《[芝加哥格式手
+冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)》的規範。
 
-1. 建立發佈分支
-   - 從 'develop'、`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
-   - 推動分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`
+1. 建立發行用分支
+   - 從「develop」分支下指令，`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
+   - 推送分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`
 
-1. 更新新版本
-   - [ ] 在[`AUTHORS.md`](../AUTHORS.md)加入新貢獻者資料
-   - [ ] 更新[`CHANGELOG.md`](../CHANGELOG.md)
+1. 更新本次新發行
+   - [ ] 在 [`AUTHORS.md`](../AUTHORS.md) 中加入新貢獻者的資料
+   - [ ] 更新 [`CHANGELOG.md`](../CHANGELOG.md)
    - [ ] 更新 [`roadmap.md`](roadmap.md)
-   - [ ] 在 diff 進行額外傳輸到 'main' 分支
-      - 執行 `script/generate-review-template.sh` 與提交更新紀錄 `docs/review-template.html`
-      - 使用審查範本的新文字更新 `docs/standard-for-public-code.html`，根據結果更新任何狀態
-      - 重新檢查用字有變更的任何段落，確保變更的字詞適合該整體段落，並且沒有文法或拼字錯誤
-      - 確保安裝[字體](https://brand.publiccode.net/typography/)，請參閱：`script/ensure-font.sh`
-      - 使用 `script/pdf.sh rc1` 檢視渲染的 `.pdf`
-         - 確保沒有連結相衝的問題
-         - 移除或新增分頁符號 CSS 來檢查分頁符號，像是：`<p style="page-break-after: always;"></p>`
-      - 若需要，進行修復並且重複進行額外傳輸
-   - [ ] 推送分支，與 `main` 分支比較，如：
+   - [ ] 透過 diff 進行額外傳輸到「main」分支
+      - 執行 `script/generate-review-template.sh` 並送交更新後的 `docs/review-template.html` 版次記
+錄
+      - 使用審查範本中的新文字來更新 `docs/standard-for-public-code.html`，會將任何狀態變更作為結果更新
+      - 重新檢查用字有變更的任何小節或段落，確保變更的字詞適合該整體內容，並且沒有文法或拼字錯誤
+      - 確認有安裝[字型](https://brand.publiccode.net/typography/)，請參見：`script/ensure-font.sh`
+      - 使用 `script/pdf.sh rc1` 檢查轉譯出的 `.pdf` 檔
+         - 確認沒有連結相衝的問題
+         - 檢查文字分頁之處，可能需要移除或新增 CSS 分頁語法，像是：`<p style="page-break-after: always;"></p>`
+      - 如果有需要，送交修正版次，並重複進行額外傳輸
+   - [ ] 推送分支，與「main」分支比較，範例：
 `https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`
-      - 要求多位審查人員（特別是校對人員）進行審查
-      - 審查人員若有發現不會影響發行的缺失，則會建立議題
-      - 如果是發行所需，審查人員可以建立拉入請求來解決問題
-      - 若額外的拉入請求合併至發行分支，請要求重新審查
-   - [ ] 執行「to-archive-org.sh」腳本
+      - 請多位審查人員（特別是校對人員）進行審查
+      - 審查人員若發現不會阻礙發行的缺失，則會建立議題
+      - 如果是發行所需處理的缺失，審查人員可以提交拉取請求來解決問題
+      - 若有額外的拉取請求合併至發行分支，則再次請求審查
+   - [ ] 執行 to-archive-org.sh 命令稿
 
-1. 在 GItHub 上發行，並且附上發行說明與版本號碼
+1. 在 GItHub 上發行，附上發行備註與版本編號
    - [ ] `git tag trigger-$MAJOR.$MINOR.$PATCH`
-   - [ ] `git push --tags` (see: `../.github/workflows/release-on-tag.yml`)
-   - [ ] 移除本地端的標籤（tag）：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`
+   - [ ] `git push --tags`（請參見：`../.github/workflows/release-on-tag.yml`）
+   - [ ] 移除本地端的 tag 標記：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`
 
-1. [將印刷檔案傳送至印刷廠](printing.md)
+1. [將檔案傳送給印刷廠商印刷](printing.md)
    - [ ] 封面檔案
    - [ ] 內頁 PDF
 
-1. 標記[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者
+1. 通知[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 873dacae..3bd211cc 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -5,30 +5,30 @@
 
 上次更新時間：2023-03-08
 
-本文件旨在提供團隊目前開發計畫的資訊。隨著團隊吸收新資訊，這些計畫也會迅速變動。
+本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。
 
-代碼庫管理人員每月定期審查發展路線圖，這是[代辦事項梳理會
-議](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
-的一部份。
+代碼庫管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作
+業](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
+環節的一部份。
 
 ## 目前任務
 
-* 盡可能讓標準符合 The Standard for Public Code
+* 盡可能讓標準遵循自我標準
 * 認證標章
 
 ## 近期
 
 * 分離執行摘要 (issue #302)
-* 實體檢查清單
-* 潛在解決方案：為每個標準新增圖示
+* 實體紙張檢查清單
+* 可能性：為每個準則新增解說插圖
 
 ## 長期
 
-* 新增「README」與「index.md」資訊（並在之後加入統計數據）到採用與使用（議題#438號）上
-* 取得多個代碼庫認證
-* 在幾個代碼庫符合標準後，推出 1.0.0 版
-* 可連結需求規範
+* 為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）
+* 通過多個代碼庫驗證
+* 在幾個代碼庫遵循標準後，發行 1.0.0 版
+* 可連結的需求規範
 * 新封面設計
-* 申請 ISBN 書號
-* 隨選書籍列印服務廠商清單
-* 印刷版外部連結的 QR 二維碼
+* 註冊申請 ISBN 書號
+* 隨選書籍列印服務名單
+* 印刷版外部連結的 QR 二維圖碼
diff --git a/foreword.md b/foreword.md
index d234a136..bfaf3af0 100644
--- a/foreword.md
+++ b/foreword.md
@@ -4,160 +4,161 @@
 redirect_from:
   - introduction
 ---
-# 序
+# 序文
 
-The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。
+《Standard for Public Code》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。
 
-開發具有公共目的的軟體與政策，就可以使用此標準來提供優質公共服務，不僅更具成本效益、風險更低且能夠掌控。
+任何想開發具有公眾用途的軟體或政策的人，可以利用此標準來提升公共服務品質，使其更具成本效益、風險更低，還能對系統更有掌控權。
 
-「序」介紹何謂「公共程式」以及其重要性。
+本序文在介紹何謂「公共程式」以及解說其重要性。
 
 ## 公共程式定義
 
-公共程式是由人類或機器在公共情境下，執行的電腦原始碼（像是軟體與演算法）與公共政策。專為搭配公共基礎建設使用甚至是作為公共基礎建設所開發的軟體，以及軟體生產的安排，
-都屬於公共程式的範疇。公共程式與一般軟體明顯不同，因為執行的條件與期待也不同。
+公共程式，英文為 Public Code，是指人類或機器在公共情境下，所執行的電腦原始碼（像是軟體與演算法）與公共政策。公共程式的範疇，涵蓋搭配公共基礎建設一同作業
+的軟體、作為公共基礎建設運作而建置的軟體，以及產生公共程式的過程安排等。公共程式與一般軟體有明顯區別，因為其作業的環境與期待全然不同。
 
-## 使用公共程式的原因
+## 採用公共程式的原因
 
 公共程式現在如此重要，背後有幾個原因。
 
-### 軟體程式碼 == 政府法規
+### 軟體程式碼 == 法律條文
 
 軟體是公共基礎建設。
 
-在 21 世紀，軟體可被視為重要的公共基礎建設，因為能夠幫助傳遞現有政策，也能用於制定新政策。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力。
+在 21 世紀，軟體可被視為重要的公共基礎建設。軟體越來越常被用於實現既有政策，甚至成為新政策的制定來源。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力
+等。
 
-在公共政策的執行上，軟體技術、運算法與資料蒐集都成為關鍵要素。電腦程式現在能執行透過民主程序成為法規的政策。這兩種形式的程式，都根據民主程序所制定的公共價值，設定社
-會的運作環境。前者由人類執行，後者則是由電腦執行。換句話說，軟體程式越來越接近法規的地位。
+在公共政策的執行上，軟體運作機制、演算法與資料蒐集等，已成為關鍵要素。今日的電腦程式碼，正執行著透過民主程序制定的法規政策。程式碼與政策這兩種形式的程式，都根據民主
+程序而確立的公共價值，設立出社會的運作環境；前者由機器執行，後者則是由人類執行。換句話說，軟體程式碼，已經越來越實質趨近於法律條文的地位。
 
 因此軟體也應該接受民主治理原則的約束。
 
-### 傳統的公共軟體採購方式
+### 傳統的公共軟體採購
 
-目前的公共軟體生產模式，在交付公共服務上的效率並不高。
+目前公共軟體的生產模式，在交付公共服務上的效率並不高。
 
-過去十年購買完整軟體解決方案的公共組織，都很訝異地發現：
+過去近十年來，購置完整軟體解決方案的公家機關，有時甚至會很訝異地發現：
 
-* 無法修改軟體來反映政策的變動，或是利用新科技
-* 資料都鎖在專有系統中，無法取得
-* 授權費越來越貴而且還要定期繳納
+* 他們無法修改軟體來反映政策的變動，或是改變軟體來利用新科技
+* 他們的資料都套牢在專有系統中，無法取用
+* 他們所需繳交的授權費變得越來越貴
 
-### 技術主權與民主課責
+### 技術自主權與民主課責
 
-公共機關、公僕與市民都值得更好的。
+公家機關、公務員與居民都值得更好的。
 
-我們相信支持社會運作的軟體，再也不能只是個由外部企業控制的黑箱。這些企業也將軟體的底層邏輯藏在他們專屬的代碼庫中。反過來說，這些企業服務的政府與人民，都需要技術主
-權，讓他們能夠設定與控制公共軟體的運作，就如同他們能夠設定與掌控依法制定的政策一樣。市民與公民社會行動者，都需要透明且負責的軟體。
+我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有代碼庫之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主權。技術自主
+讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。
 
-設計為必要公民基礎建設的軟體，也應該尊重數位公民的權益。
+作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。
 
-### 設計真正屬乎民眾的軟體
+### 設計真正的公共軟體
 
-公共程式是現代公共基礎建設的核心，影響公僕的工作以及幾乎所有市民的生活。
+公共程式是現代公家機構的核心，型塑了公務員的工作樣態，並且影響了幾乎所有居民的生活。
 
 因此公共軟體必須：
 
 * 透明
-* 負責任
+* 可課責
 * 讓選民能夠理解
 
-反映其服務社會的價值觀，像是包容與不歧視。
+必須能反映其所服務的社會價值觀，像是涵容與不歧視。
 
-公共組織目前使用的多數專有軟體系統都不符合這些要求，但是公共程式符合。
+目前公家機關使用的大多數專有軟體系統，都不符合這些要求；而公共程式能夠做到。
 
 ### 公共程式的價值
 
-我們認為公共程式具有以下核心價值：
+我們認為公共程式應具有下列核心價值：
 
-* 包容
-* 可用
+* 涵容
+* 好用
 * 開放
-* 清晰易讀
-* 負責
-* 容易取得
+* 易懂
+* 課責
+* 近用
 * 永續
 
 ## 公共程式運作方式
 
-公共程式是開源軟體，旨在幫助公共組織履行其必要職責。其他行政機關在使用公共程式後，會提供意見反饋，因此公共程式的開發與維護可說是通力合作的成果。
+公共程式是旨在協助公家機關，履行其必要職責時所採用的開源軟體。透過使用，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成果。
 
-開放的精神能創造許多可能性。
+開放的精神能開創許多可能性。
 
-公共組織執行與維護自己的公共程式時，就是對地方負責，同時履行民主課責。開放且貢獻者眾多的軟體，在許多人幫忙監督是否具有潛在瑕疵的情況下，安全性會越來越高。許多貢獻者
-會分攤維護工作，保持公共程式的運作與更新，減少未來的技術債。由多人分攤維護工作，公共程式現在與未來都能更永續。公共程式的開放性，代表其程式碼與資料，在未來也更容易
-改編。程式碼也更容易改寫、重新利用或淘汰。這一切特性都讓公共基礎建設風險更低。
+公家機關在執行與維護其自身的公共程式時，就是在確保能為地方負責，並履行民主課責。開放且貢獻者眾多的軟體，得利於有許多人在看，更容易發現潛在缺陷，因此安全性會更高。許
+多貢獻者會分攤維護工作，讓公共程式能持續運作與更新，減少未來技術債的可能。因為能有多人分攤維護工作，使得現在與未來都會更加永續。而公共程式的開放性，代表其程式碼與
+資料，在未來也更容易改寫與調整。程式碼也更容易重新利用、重新調整目標，或甚至淘汰。這一切特性都讓公共基礎建設可能遭遇的風險降到更低。
 
-集中資源讓公共行政單位能夠額外注意如何客製化軟體，讓每套軟體都最能滿足各地情境的需求，為終端使用者（居民或市民）創造更好的使用者體驗。
+這種將資源集中的作法，能讓公共行政單位可以有額外心力關注如何客製化軟體，來使軟體最適合當地情境的需求，為終端使用者（居民或市民）創造更佳的使用體驗。
 
-### 公共程式的經濟
+### 公共程式的經濟效應
 
-公共程式對公共組織以及企業提供更好的經濟模型。公共程式取代傳統軟體採購，幫助各地的公共組織更能控制程式，也有更好的經濟機會。
+公共程式為公家機關以及商業公司，提供更好的經濟模型。公共程式作為替代傳統軟體採購的方案，更能提升當地的掌控權並促進經濟機會。
 
-公共程式的設計，就是開放、適應力強且資料可攜，能夠由內部員工或信賴的供應商來開發。由於其原始碼是開放性程式碼，公共行政單位需要時可以變更供應商。開放原始碼讓社會大眾
-更有機會瞭解與監督公共程式，讓公共行政單位能進行小規模的採購，在地的中小型企業才能夠參與這些採購案的招標。公共行政單位可以透過軟體採購來刺激當地經濟的創新與競
-爭。
+公共程式從設計之初，就是要開放、適應力強、資料可攜，能夠由內部員工或信任的供應商來開發。由於原始碼開放，公共行政單位在有需要時可以更換供應商。開放原始碼讓社會大眾更
+有機會瞭解與監督公共程式，使公共行政單位得以採購小規模的合約，而地方性的中小企業就更容易參與這些小型採購案的競標。如此一來，公共行政單位就可以透過他們所需的軟體採
+購案，刺激當地經濟的創新與競爭。
 
 這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。
 
-### 採購公共程式
+### 購置公共程式
 
-公共程式可由內部研發團隊、承包商或外包供應商開發。公共組織的供應商在投標時可以包含公共程式。
+公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在投標時可以在標案中納入公共程式。
 
-若要使用現有公共程式，您將需要在預算以及專案設計中，表明新的解決方案將會使用該代碼庫。為了鼓勵用創新方式將公共程式依據您的情境來調整，您可在合約中說明您的服務或成
-果。
+若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該代碼庫。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服務
+內容或預期成果。
 
-## The Standard for Public Code 目標
+## 《Standard for Public Code》目標
 
-The Standard for Public Code 支持開發人員、設計師、管理人員以及公共政策制定者：
+本標準在於支持開發人員、設計師、管理人員、公共政策制定者：
 
-* 開發優質軟體與政策，改善公共服務的交付
-* 開發能在各種情境下重複使用且共同維護的代碼庫
+* 開發出高品質的軟體與政策，來改善公共服務的交付
+* 開發出能在各種情境下重複使用，且以協作方式維護的代碼庫
 * 減少技術債與專案失敗率
-* 更能精細控制 IT 系統並且做出 IT 系統相關決策
-* 更好的經濟模型改善與供應商的關係
+* 更能精細控制其 IT 系統粒度，並做出系統相關決策
+* 以更好的經濟模型改善供應商關係
 
-代碼庫潛在使用者依照 The Standard for Public Code 測試代碼庫，結果認為代碼庫容易重複利用、維護且品質相當高。
+如果有潛在使用者想採用經由《Standard for Public Code》測試過的代碼庫，便可以預期這些代碼庫具有方便重複利用、容易維護、高品質的特性。
 
-The Standard for Public Code 能有如此特性是因為：
+《Standard for Public Code》能有此效果是基於：
 
-* 訂定公共程式開發的通用術語
-* 訂定措施協助優質公共程式的開發
-* 提出如何符合 The Standard for Public Code 的指引並在施作中遵循
+* 為公共程式開發訂立通用術語
+* 制定措施協助高品質公共程式的開發
+* 提出該如何符合準則並實作遵循的指引
 
-The Standard for Public Code 原意是要不受時間與科技限制。
+《Standard for Public Code》設計精神就是要跨越時間與科技，不受其限制。
 
 ### 適用對象
 
-The Standard for Public Code 適用於開發與重複使用公共程式的民眾：
+《Standard for Public Code》適用於開發與重複使用公共程式的人：
 
 * 公共政策制定者
 * 業務與專案經理
 * 開發人員與設計師
 
-這些人的服務單位：
+在以下單位服務的人：
 
-* 公家機關的機構、組織與行政單位
-* 服務公家機關的資訊科技以及政策服務顧問公司與供應商
+* 社會機構、公家機關的組織與行政單位
+* 公家機關在資訊科技與政策服務上的顧問與供應商
 
-適用對象不包括公家機關的終端使用者（居民或市民）、記者或學者。
+適用對象不含公家機關的終端使用者（居民或市民）、記者或學者等。
 
 ## 延伸閱讀
 
-* 歐洲自由軟體基金會所發表的《[「用免費軟體將公共基礎設施現代化」白皮
+* 歐洲自由軟體基金會所發表的[《透過自由軟體實現公共基礎設施現代化》白皮
 書](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf) 》。
 
-### 公共程式影片
+### 探討公共程式的影片
 
-* [2019 年 Decidim Fest 的「程式合作是城市的未來」](https://www.youtube.com/watch?
-v=cnJtnZ9Cx1o)。主講人 Ben Cerveny 介紹 The Foundation for Public Code 的背景。
-* [ 2019 年 Nextcloud 大會的「公帑？公共程式！」專題討論](https://youtube.com/watch?v=QHFkD4xfd6c)。探
-討採購、法律等主題。
+* [〈程式協作是城市的未來〉@ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)。主講
+人 Ben Cerveny，講述 Foundation for Public Code 的背景。
+* [ 〈用公共的納稅錢？做公共的程式吧！〉專題討論 @ Nextcloud 大會 2019](https://youtube.com/watch?
+v=QHFkD4xfd6c)。討論採購、法律等主題。
 
-## 加入我們的行列
+## 參與我們
 
-此標準是活文件。[請讀我們的貢獻者指引](/CONTRIBUTING.md)，瞭解您可以如何讓此標準變得更好。
+本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING.md)，瞭解您可以怎麼做來讓本標準變得更好。
 
 ## 聯絡方式
 
-若有疑問或想進一步瞭解 The Foundation for Public Code，請造訪[我們的官網](https://publiccode.net/)、寄電子
-郵件到 info@publiccode.net，或是撥打我們的電話（+31 20 2 444 500）。
+若有疑問，或想進一步瞭解 Foundation for Public Code，請造訪[我們的網站](https://publiccode.net/)，或是寄電子郵
+件到 info@publiccode.net，或撥打我們的電話 +31 20 2 444 500。
diff --git a/glossary.md b/glossary.md
index 26bf1e9f..4d035640 100644
--- a/glossary.md
+++ b/glossary.md
@@ -2,75 +2,78 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
+
 # 詞彙表
 
-## 規則（Code）
+## 程式或程式碼 (Code)
 
-任何明確的規則系統，包括法律、政策與條例，以及用來開發軟體的原始碼。兩者都是規則，前者由人類來執行，後者則是機器。
+任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是由機器執
+行。
 
 ## 代碼庫
 
-執行政策或軟體所需的任何離散程式碼套件（原始碼與政策程式碼）、測試與文件。
+執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件的整套統合包。
 
-可以是文件或是版本控制的儲存庫。
+例如，這可以是文件，或是版本控制的儲存庫。
 
 ## 持續整合
 
-軟體工程的持續整合 (CI) 就是盡可能頻繁地將所有開發人員的工作複本合併到代碼庫的開發分支。
+在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回代碼庫開發中分支的實務作法。
 
 ## 不同情境
 
-如果是有多家公家機關或部門，決策者不只一位，因而無法自然地進行協作，則算是兩個不同的情境。
+只要是不同的公家機關或不同的部門，無法透過同一個決策單位讓協作自然發生，那就算是兩個不同的情境。
 
 ## 一般大眾
 
-一般民眾：程式碼及以程式碼為基礎的服務的終端使用者。
+整體民眾：程式碼與其所建立的服務的終端使用者。
 
-舉例來說，一個城市的居民被視為該城市提供的服務（以及這些服務依據的法規）的終端使用者。
+舉例而言，城市的居民視為該城市的服務，以及驅動這些服務運作的程式碼的終端使用者。
 
-## 開源
+## 開源或開放原始碼
 
-開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》定義何謂「開源」。
+所謂「開源」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
 
 ## 開放標準
 
-任何符合開放原始碼促進會[開放標準需求規範](https://opensource.org/osr)的標準就是開放標準。
+任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/osr)》的標準就是開放標準。
 
 ## 政策
 
-政策就是引導決策與達成理性成果的一套原則系統。政策是意圖聲明，被當成程序或協定來執行。組織內通常是由治理單位來執行政策。政策能協助主觀與客觀的決策。
+政策是一套謹慎設計的原則體系，用來引導決策並達成合理的成果。政策是一種意圖的聲明，並以程序或協定來執行。政策通常是由組織單位內的理事機構採用執行。政策能協助做出主觀
+與客觀的決策。
 
-公共政策是政府將其政治理念轉化成計畫與行動的流程，藉此取得成果。
+公共政策是政府將其政治願景，轉化成計畫與行動來取得成果的程序。
 
-在國家層級，政策與立法（法律）通常是分開的，但地方政府比較容易將兩者混淆在一起。
+在國家層級，政策與立法（法律）通常是分開的；而在地方政府中，這兩者之間的區別通常比較模糊。
 
-The Standard for Public Code 當中，「政策」係指公共機關（像是政府與市政府）建立與採用的政策。
+在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的政策。
 
 ## 公共程式
 
-公共程式是由公家機關開發的開源軟體，當中包括協作與重複利用所需的政策與指引。
+公共程式，是由公家機關所開發的開源軟體，同時包含協作與重複利用所需的政策與指引。
 
-公共程式在公共情境下，由人類或機器所執行的電腦原始碼（像是軟體與演算法）以及公共政策。
+公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以及公共政策兩者。
 
-滿足公共利益的公共程式，具有開放、易讀、負責、可用以及永續的特性。
+服務公眾利益的公共程式，具有開放、易懂、課責、近用、永續等特性。
 
-為當地情境開發公共程式時，開發過程不受當地情境影響，開發完成依舊在該當地情境中使用，並且公開紀錄整個開發過程。如此的公共程式能夠提供基石讓別人可以：
+透過獨立於當地情境，但仍可在當地情境下實作的方式，還有公開以文件記錄開發程序等作法，來開發公共程式。如此，公共程式能作為基礎組件提供給他人，使其得以：
 
-* 將該公共程式應用於他們的當地情境
-* 將該公共程式當成起點並接著繼續開發
-* 當成學習的基礎
+* 根據其當地情境重新實作
+* 作為起點並繼續開發
+* 當作學習時的基礎
 
-為了方便重複利用，公共程式可以在公領域中發行，或者採取允許他人任意檢視與重複利用其內容的開放授權，藉此推動衍生工作。
+為了促進重複利用，公共程式通常放到公眾領域發行，或者採取允許他人能自由檢視、重複利用其成果，甚至產出衍生作品的開放授權。
 
 ## 儲存庫
 
-儲存庫是版本控制工具用來儲存代碼庫檔案與中介資料的地方。儲存庫允許多位貢獻者同時使用同一組檔案。儲存庫可以用儲存同一組檔案的多個版本。
+儲存庫是版本控制工具，用於存放檔案與代碼庫中介資料的儲存位置。儲存庫允許多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
 
 ## 原始碼
 
-人類可讀並且能夠翻譯成機器指令的電腦程式文字。
+人類可讀，並且能夠翻譯成機器指令的電腦程式文字。
 
 ## 版本控制
 
-版本控制是對於原始碼以及其相關檔案的變動的管理。這邊的變動通常是一個稱為「修正編號」（或類似名稱）的代碼。每次修正都會標示修正的時間以及作者，方便追溯程式碼的演變。
-修正控制系統可用於彼此比較不同的版本，瞭解內容長期下的變動。
+版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「*修訂編號*」（或「版次」等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作
+者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間的變動。
diff --git a/index.md b/index.md
index 1d3ef901..eadcea4e 100644
--- a/index.md
+++ b/index.md
@@ -5,47 +5,47 @@ toc: false
 ---
 # 政府開源協作指引
 
-The Standard for Public Code 當中的標準，支持公共組織合作開發與維護軟體及政策。
+《Standard for Public Code》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。
 
-The Standard for Public Code 指引正在建構自己開源解決方案的公共組織，方便他們未來能跟其他地區的類似公部門組織合作，並讓這些組織能重複利
-用前述開源解決方案。The Standard for Public Code 提供建議給政策制定者、政府管理人員、開發人員與供應商。不同人士可透過The
-Standard for Public Code ，合作建立可用、開放、易讀、負責且永續的代碼庫。The Standard for Public Code 適用於
-各政府層級的代碼庫，從超國家到市政府。
+《Standard for Public Code》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使
+用各自的成果。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《Standard for Public Code》支持公家機關透過協作方式，創造
+出好用、開放、易懂、課責、近用、永續的代碼庫。這份標準從設計之初，就是要用於各種不同政府層級的代碼庫，小從市政府，大到超國家組織都行。
 
-The Standard for Public Code 將‘[公共程式](glossary.md#public-code)’定義為由公共組織所開發的開源軟體，並且
-遵照相關政策與指引，方便協作與重複利用。
+《Standard for Public Code》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開源軟體，同時包含
+協作與重複使用所需的政策與指引。
 
-The Standard for Public Code 當中的標準符合開源軟體開發的指引與最佳實務。
+《Standard for Public Code》當中的準則，符合開源軟體開發的指引與最佳實務。
 
-{% for page in site.pages %}{% if page.name == "foreword.md" %} 額外情境與背景資訊請參閱
-[序](foreword.md). {% endif%}{% endfor %}
+{% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序
+文](foreword.md). {% endif%}{% endfor %}
 
-## 目錄
+## 目次
 
-* [讀者指南：如何詮釋此標準](readers-guide.md)
+* [讀者指引：如何詮釋此標準](readers-guide.md)
 * [詞彙表](glossary.md)
-* [標準](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in
+* [準則](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in
 sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{%
 if page.title %}
    * [{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}
 * [作者群](AUTHORS.md)
 * [貢獻指引](CONTRIBUTING.md)
-* [行為準則](CODE_OF_CONDUCT.md)
-* [治理](GOVERNANCE.md)
+* [行為守則](CODE_OF_CONDUCT.md)
+* [治理方式](GOVERNANCE.md)
 * [版本歷史](CHANGELOG.md)
 * [授權](license.html)
 
 ## 社群會議
 
-我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。 [議
+我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。[議
 程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code) 在會議
-前約一週的時間更新。您可以 [報
-名](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)，
-之後舉辦會議時會寄送邀情函給您。
+前約一週的時間更新。您可以[註
+冊](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)
+報名，會再寄送會議通話邀請函給您。
 
 ## 其他資源
 
-* [The Standard for Public Code 社群其他語
-言](https://publiccodenet.github.io/community-translations-standard/) 非官方翻譯版
-* 公部門開源代碼庫的 [標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)
-* [標準資格檢查清單](/docs/review-template.html) 由公共程式基金會管理人員用於代碼庫審查
+* 本標準非官方的其他語言[社群翻
+譯](https://publiccodenet.github.io/community-translations-standard/)
+* 公部門開源代碼庫的〈[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)〉
+* Foundation for Public Code 管事人員用於代碼庫審查的〈[標準準則檢查清
+單](/docs/review-template.html)〉
diff --git a/readers-guide.md b/readers-guide.md
index 1d2f7d7b..ae39504c 100644
--- a/readers-guide.md
+++ b/readers-guide.md
@@ -2,69 +2,70 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
-# 讀者指南
 
-公共標準程式包含許多標準。所有標準的段落都相當一致，讓讀者瞭解如何打造好用的公共程式。
+# 讀者指引
 
-「政策制定者」、「管理人員」以及「開發人員與設計師」，係指任何履行這些角色職責的人，不受職稱限制。很多人都承擔多個角色的職責。
+本標準描述說明許多準則。所有準則各小節結構維持一致，來讓讀者清楚明白如何開發良好的公共程式。
 
-以下是 The Standard for Public Code 各章節的簡介，以及在標準當中的功用。
+「政策制定者」、「管理人員」以及「開發人員與設計師」的稱呼，係指任何履行這些角色職責的人，不受其職稱限制。常見同時承擔多個角色職責的人。
+
+以下是各小節的簡要介紹，以及在本標準準則中的作用。
 
 ## 前言
 
-本章節探討這些標準的目的，以及為什麼對代碼庫使用者與貢獻者很重要的原因。
+本小節說明這些準則想達成的目的，以及為何會對代碼庫使用者與貢獻者來說這麼重要的原因。
 
-## 規定
+## 需求規定
 
-這章節解釋如何遵循 The Standard for Public Code 。
+這個小節列出如果要遵循本標準，需要完成哪些事項。
 
-本文件的下列關線字應該根據 [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) 來詮釋：
+本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/rfc2119)》的描述作詮釋：
 
 * 必須
+* 禁止
+* 要求
+* 應當
 * 不得
-* 被要求
-* 應該
-* 不應
 * 應該
-* 不應
+* 不該
 * 建議
-* 得
+* 得以
 * 可選擇
 
 ## 測試方式
 
-本章節列出您可採取的行動，藉此了解貢獻內容是否遵循 The Standard for Public Code 。如果您想要實施 The Standard for
-Public Code ，這將會是關鍵。
+本小節提供您可採取的行動，來確認貢獻內容是否遵循本標準。如果您想要務實操作本標準，這部分很關鍵。
 
-我們的用字是要讓不熟悉此主題的讀者，看了之後也能夠進行基本的遵循檢測。
+我們已嘗試調整用字，讓即使是不熟悉這類主題內容的讀者，看完之後也能夠進行基本的遵循檢查。
 
-## 公共政策制定者：您的責任
+## 公共政策制定者：需要的工作
 
-本章節主要對象是政策制定者，列出他們的角色能採取的具體行動。
+本小節主要對象是政策制定者，列出他們的角色所能採取的具體行動。
 
-公共政策制定者決定專案的優先順序與目標，在科技上的經驗可能沒那麼多。
+公共政策制定者設定專案的優先順序與目標，而在科技上的經驗可能沒那麼多。
 
-## 管理人員：您的義務
+## 管理人員：需要的工作
 
-本章節主要對象是管理人員，列出他們的角色能採取的具體行動。
+本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。
 
-管理人員負責監督專案的準時交付、利害關係人管理以及持續性的服務交付。因此他們也完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源，提供正確
-的架構，才能夠帶來良好的服務。
+管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源、提供正
+確的架構等，才能交付優良的服務。
 
-## 開發人員與設計師：您的責任
+## 開發人員與設計師：需要的工作
 
-本章節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。
+本小節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。
 
-開發人員通常比較熟悉相關技術，跟其他類別相較之下對服務交付的影響更大。
+開發人員通常對技術比較在行，與其他角色類別相比，對服務交付的影響更大。
 
-## 範圍限制
+## 作用範圍限制
 
-The Standard for Public Code 不是為了代碼庫的個別執行所撰寫。這代表該標準不是要告訴實施者該如何遵循他們組織的當地技術基礎建設或法律框
-架。
+《Standard for Public Code》不是為了涵蓋代碼庫的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法
+律框架。
 
-The Standard for Public Code 有參照幾個標準，並且與其他標準有許多重疊的部分，但其目的是要推動協作。因此The Standard
-for Public Code 目的並非是要取代品質標準（像是 ISO 25000 認證），或是以安全為準的標準（像是 [OpenSSF 最佳實務標
-章](https://github.com/coreinfrastructure/best-practices-badge)），而是要與他們協作。
+此外，雖然《Standard for Public Code》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代
+品質標準，像是 ISO 25000 認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF 最佳實務標
+章](https://github.com/coreinfrastructure/best-practices-badge)等，而是希望能與它們能良好協同搭
+配。
 
-The Standard for Public Code 的目的之一在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也
-需要協作者的積極推動與野心。
+《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要積極主
+動，以及做到超越協作以外的企圖心。

From 006c6ff9ec43ff3ffaa35b418778b168f2180e82 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Wed, 13 Sep 2023 15:39:21 +0000
Subject: [PATCH 52/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index b593ecba..0f4dc12f 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-13 02:12+0000\n"
+"PO-Revision-Date: 2023-09-14 15:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -405,7 +405,7 @@ msgstr "調整程式碼撰寫風格要求，專注於代碼庫上，而非貢獻
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
-msgstr "將代碼庫名稱規定，從〈使用白話的英文〉移動到〈代碼庫可查詢得到〉。"
+msgstr "將代碼庫名稱規定，從〈使用白話的英文〉移到〈代碼庫可查詢得到〉。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
@@ -1164,7 +1164,8 @@ msgstr "為文件與程式碼提出拉取請求"
 msgid ""
 "If you want to add to the documentation or code of one of our projects you "
 "should make a pull request."
-msgstr "如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求。"
+msgstr "如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull "
+"Request，亦可簡稱 PR)。"
 
 #: ./CONTRIBUTING.md:block 12 (paragraph)
 msgid ""
@@ -1235,7 +1236,7 @@ msgid ""
 msgstr ""
 "將您所作的變更內容加入送交版次，[並附上內容說明](https://robots.thoughtbot."
 "com/5-useful-tips-for-a-better-commit-message)。如果需要作出多種類型的變更，"
-"請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如，修正空白，"
+"請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、"
 "以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用容易以「`"
 "diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，"
 "請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉擇。"
@@ -1753,7 +1754,7 @@ msgstr ""
 "本標準採用 CC0 "
 "公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任"
 "何人都能任意使用這些內容。如果您是貢獻者，代表您也將這些權利賦予他人。若要進"
-"一步瞭解如何協助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。"
+"一步瞭解如何協助本專案，請參閱《[貢獻指引](CONTRIBUTING.md)》。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
 msgid "order: 2 redirect_from:"
@@ -5671,7 +5672,7 @@ msgstr "舉例而言，城市的居民視為該城市的服務，以及驅動這
 
 #: ./glossary.md:block 16 (header)
 msgid "Open source"
-msgstr "開源或開放原始碼"
+msgstr "開源或開放原始碼 (Open Source)"
 
 #: ./glossary.md:block 17 (paragraph)
 msgid ""
@@ -5881,7 +5882,7 @@ msgid ""
 "endif%}{% endfor %}"
 msgstr ""
 "{% for page in site.pages %}{% if page.name == \"foreword.md\" %} "
-"其他情境與背景資訊請參閱[序文](foreword.md). {% endif%}{% endfor %}"
+"其他情境與背景資訊請參閱[序文](foreword.md)。 {% endif%}{% endfor %}"
 
 #: ./index.md:block 10 (header)
 msgid "Contents"
@@ -5889,7 +5890,7 @@ msgstr "目次"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
-msgstr "[讀者指引：如何詮釋此標準](readers-guide.md)"
+msgstr "[讀者指引：如何解讀此標準](readers-guide.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Glossary](glossary.md)"

From b9f1d61e2fee7a981a0d0c87ea2e78a7c9f46e2b Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Fri, 15 Sep 2023 14:17:11 +0000
Subject: [PATCH 53/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 712 ++++++++++++------------
 1 file changed, 369 insertions(+), 343 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 0f4dc12f..844ebae6 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-14 15:44+0000\n"
+"PO-Revision-Date: 2023-09-15 15:51+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -239,7 +239,7 @@ msgstr "新增規定，記錄預期由何者負擔審核貢獻內容所需的開
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Add requirement to have a short description of the codebase."
-msgstr "新增規定，代碼庫必須要有簡短說明。"
+msgstr "新增規定，程式基底必須要有簡短說明。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid ""
@@ -249,7 +249,7 @@ msgstr "原先專注在貢獻內容是否遵循標準，現在則改為注重貢
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
-msgstr "將〈代碼庫可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。"
+msgstr "將〈程式基底可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。"
 
 #: ./CHANGELOG.md:block 7 (unordered list)
 msgid "Review template now in HTML format."
@@ -306,7 +306,7 @@ msgstr "對安全性區分出兩項規定，一是要有提供方法，另一個
 msgid ""
 "Rephrased requirements to focus on the codebase rather than contributor "
 "behavior."
-msgstr "重新撰寫規定，將焦點放在代碼庫，而非貢獻者行為。"
+msgstr "重新撰寫規定，將焦點放在程式基底，而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 10 (unordered list)
 msgid ""
@@ -399,13 +399,13 @@ msgstr "2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風
 msgid ""
 "Adjust the coding style requirement to focus on the codebase using a style "
 "guide rather than contributor behavior."
-msgstr "調整程式碼撰寫風格要求，專注於代碼庫上，而非貢獻者行為。"
+msgstr "調整程式碼撰寫風格要求，專注於程式基底上，而非貢獻者行為。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
 "Moved requirement for codebase names to Make the codebase findable from Use "
 "plain English."
-msgstr "將代碼庫名稱規定，從〈使用白話的英文〉移到〈代碼庫可查詢得到〉。"
+msgstr "將程式基底名稱規定，從〈使用白話的英文〉移到〈程式基底可查詢得到〉。"
 
 #: ./CHANGELOG.md:block 13 (unordered list)
 msgid ""
@@ -437,13 +437,13 @@ msgstr "2022年12月5日：📝第十二版草稿指出要以文件記錄成熟
 msgid ""
 "Document maturity focuses on whether or not versions of the codebase are "
 "ready to use."
-msgstr "寫下成熟度著重於代碼庫是否已經可供使用，更甚於版本編號。"
+msgstr "寫下成熟度著重於程式基底是否已經可供使用，更甚於版本編號。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid ""
 "Document maturity no longer requires specific labels for codebases that are "
 "not ready to use."
-msgstr "寫下成熟度不再需要為尚未準備好可供使用的代碼庫加上特定標籤。"
+msgstr "寫下成熟度不再需要為尚未準備好可供使用的程式基底加上特定標籤。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Audit flow image now generated from an easier to translate format."
@@ -505,7 +505,7 @@ msgstr "2022年9月7日：🔭第十一版草稿新增可查找性準則。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Introduce new criterion: Make the codebase findable."
-msgstr "導入新準則：代碼庫可查詢得到。"
+msgstr "導入新準則：程式基底可查詢得到。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Improve How to test section for most criteria."
@@ -556,7 +556,7 @@ msgstr "將規定重新調整為項目要點清單格式。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Acknowledge the importance of codebase modularity for reuse."
-msgstr "告知代碼庫成熟度對於重複使用時的重要性。"
+msgstr "告知程式基底成熟度對於重複使用時的重要性。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Move requirements related to Findability to the new criterion."
@@ -564,7 +564,7 @@ msgstr "將可查找性相關規定移動到新準則中。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Clarify the role of non-open standards when used in a codebase."
-msgstr "釐清非開放標準在代碼庫中的角色。"
+msgstr "釐清非開放標準在程式基底中的角色。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Additional guidance about build-time and runtime dependencies."
@@ -770,7 +770,7 @@ msgstr "指出 publiccode.yml 是機器可讀中介資料說明的範例之一
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
-msgstr "將「您的代碼庫」與「您的組織單位」改為較不具有所有格的寫法。"
+msgstr "將「您的程式基底」與「您的組織單位」改為較不具有所有格的寫法。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add instructions for creating a print version."
@@ -856,13 +856,13 @@ msgstr "將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎
 msgid ""
 "Rename criterion \"Pay attention to codebase maturity\" to \"Document "
 "codebase maturity\"."
-msgstr "將〈注意代碼庫成熟度〉準則改名為〈記錄代碼庫成熟度〉。"
+msgstr "將〈注意程式基底成熟度〉準則改名為〈記錄程式基底成熟度〉。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid ""
 "Changed MUST to SHOULD for requirement of codebase in use by multiple "
 "parties."
-msgstr "針對多方使用的代碼庫，將「必須」等級規定調降為「應該」。"
+msgstr "針對多方使用的程式基底，將「必須」等級規定調降為「應該」。"
 
 #: ./CHANGELOG.md:block 34 (unordered list)
 msgid "Add MUST NOT requirement regarding copyright assignment."
@@ -1133,8 +1133,8 @@ msgid ""
 "Issues for the Standard for Public "
 "Code](https://github.com/publiccodenet/standard/issues)."
 msgstr ""
-"[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議"
-"修改，以及發問等，來協助發展。您可以到 [Standard for Public Code 的 GitHub "
+"在[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建"
+"議修改，以及發問等，來協助發展。您可以到 [Standard for Public Code 的 GitHub "
 "Issue](https://github.com/publiccodenet/standard/issues) 頁面中，為本專案["
 "提出 GitHub 議題](https://docs.github.com/en/issues/"
 "tracking-your-work-with-issues/creating-an-issue)。"
@@ -1418,8 +1418,8 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"本標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管"
-"理領域作監督時的核心。我們依照這份文件來判斷，某個代碼庫是否已經準備好讓社群"
+"本標準是 [Foundation for Public Code](https://publiccode.net/) 在程式基底盡職"
+"管理作監督時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群"
 "共同參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
@@ -1512,11 +1512,11 @@ msgid ""
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
 msgstr "《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 "
-"版，目前仍在幾個代碼庫中作測試。"
+"版，目前仍在幾個程式基底中作測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將《Standard for Public Code》套用您的代碼庫"
+msgstr "將《Standard for Public Code》套用您的程式基底"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1527,9 +1527,9 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是"
-"人人都能自由採用的開放標準。若要瞭解您代碼庫所達成的程度，可以做[自我資格評估"
-"](https://publiccodenet.github.io/assessment-"
+"若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它"
+"是人人都能自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資格"
+"評估](https://publiccodenet.github.io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 #: ./README.md:block 9 (paragraph)
@@ -1541,9 +1541,9 @@ msgid ""
 "guide](https://publiccodenet.github.io/community-implementation-guide-"
 "standard/) which contains examples and other tips."
 msgstr ""
-"本標準 *應該* 足以自我解釋要如何套用到您的代碼庫中。若標準中有任何不明確的地"
-"方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如"
-"果需要一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet."
+"本標準 *應該* 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的"
+"地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。"
+"如果需要一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet."
 "github.io/community-implementation-guide-standard/)，其中包括範例與其他提示。"
 
 #: ./README.md:block 10 (paragraph)
@@ -1554,7 +1554,7 @@ msgid ""
 msgstr ""
 "若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 "
 "Foundation for Public Code "
-"的代碼庫管事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
+"的程式基底管事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1564,8 +1564,8 @@ msgid ""
 "[assessment](https://about.publiccode.net/activities/codebase-"
 "stewardship/lifecycle-diagram.html#assessment)."
 msgstr ""
-"若您致力讓您的代碼庫完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：["
-"info@publiccode.net](mailto:info@publiccode."
+"若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫"
+"：[info@publiccode.net](mailto:info@publiccode."
 "net)，以展開正式[評估](https://about.publiccode.net/activities/"
 "codebase-stewardship/lifecycle-diagram.html#assessment)。"
 
@@ -1589,8 +1589,8 @@ msgid ""
 "This standard sets a quality level for codebases that meets the needs of "
 "public organizations, institutions and administrations as well as other "
 "critical infrastructural services."
-msgstr "本標準為代碼庫設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及"
-"其他重大基礎設施服務的需求。"
+msgstr "本標準為程式基底設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以"
+"及其他重大基礎設施服務的需求。"
 
 #: ./README.md:block 15 (paragraph)
 msgid ""
@@ -1775,7 +1775,7 @@ msgid ""
 "anyone to implement the codebase in their local context or contribute to the"
 " further development of the [codebase](../glossary.md#codebase)."
 msgstr ""
-"對於想根據所在情境實作代碼庫的人，或是想更進一步貢獻[代碼庫](../glossary."
+"對於想根據所在情境實作程式基底的人，或是想更進一步貢獻[程式基底](../glossary."
 "md#codebase)開發的人來說，能同時取用[原始碼](../glossary.md#source-"
 "code)與[政策](../glossary.md#policy)文件兩者，可作為建置成品時的基礎組件。"
 
@@ -1784,8 +1784,8 @@ msgid ""
 "Understanding the domain and policies within that domain is fundamental to "
 "understanding what problems a codebase is trying to solve and how it sets "
 "out to solve them."
-msgstr "瞭解作用範疇與該範疇的政策是基本原則，才能瞭解代碼庫試圖想解決的問題是什麼，"
-"以及該如何解決這些問題的作法。"
+msgstr "瞭解作用範疇與該範疇的政策是基本原則，才能瞭解程式基底試圖想解決的問題是什麼"
+"，以及該如何解決這些問題的作法。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
 msgid ""
@@ -1793,8 +1793,9 @@ msgid ""
 "organization needs to understand what process changes it must choose to make"
 " or how to contribute additional configurability to the existing solution in"
 " order to adapt it to the new context."
-msgstr "為了評估是否需要在新的情境中實作代碼庫，組織單位需要瞭解必須做出改變的程序有"
-"哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。"
+msgstr ""
+"為了評估是否需要在新的情境中實作程式基底，組織單位需要瞭解必須做出改變的程序"
+"有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
 msgid "Requirements"
@@ -1802,14 +1803,14 @@ msgstr "需求規定"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "The codebase MUST include the policy that the source code is based on."
-msgstr "代碼庫「必須」包含原始碼所根據的政策。"
+msgstr "程式基底「必須」包含原始碼所根據的政策。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid ""
 "If a policy is based on source code, that source code MUST be included in "
 "the codebase, unless used for fraud detection."
-msgstr "如果政策根據原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始"
-"碼則可除外。"
+msgstr "如果政策根據原始碼而來，則該原始碼「必須」包含在程式基底中，用於偵測詐騙的原"
+"始碼則可除外。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
 msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
@@ -1869,7 +1870,7 @@ msgid ""
 msgstr ""
 "提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
 "文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
-"，以及影響貴組織單位代碼庫開發或部署情境的任何組織單位流程。"
+"，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid "Provide references and links to texts which support the policies."
@@ -1895,8 +1896,8 @@ msgid ""
 "Check in regularly to understand how the source code in the codebase has "
 "changed and whether it still matches the [intentions of the "
 "policy](document-codebase-objectives.md)."
-msgstr "定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否仍然符合[政策意圖](document-"
-"codebase-objectives.md)。"
+msgstr "定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合[政策意圖"
+"](document-codebase-objectives.md)。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
 msgid ""
@@ -1907,7 +1908,7 @@ msgid ""
 "accessibility), or human rights policies, like a public organization's "
 "commitment to equal opportunity."
 msgstr ""
-"納入會影響社會群體、代碼庫與開發目標的相關政策，包含 [GDPR "
+"納入會影響社會群體、程式基底與開發目標的相關政策，包含 [GDPR "
 "一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 "
 "[歐盟網頁無障礙命令](https://ec.europa.eu/digital-single-market/en/web-access"
 "ibility)等此類法律義務，或者是人權政策，例如公家機關對機會平等的承諾等。"
@@ -2006,7 +2007,7 @@ msgid ""
 "Together, this creates more opportunities for citizens to understand how "
 "software and [policy](../glossary.md#policy) impact their interactions with "
 "a public organization."
-msgstr "這些加在一起，讓公民更有機會瞭解軟體與[政策](../glossary."
+msgstr "這些合在一起，讓公民更有機會瞭解軟體與[政策](../glossary."
 "md#policy)如何影響他們與公家機關的互動。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
@@ -2027,7 +2028,7 @@ msgstr "任何使用中軟體的所有原始碼都「必須」要公開（用於
 msgid ""
 "The codebase MUST NOT contain sensitive information regarding users, their "
 "organization or third parties."
-msgstr "代碼庫「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。"
+msgstr "程式基底「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 8 (unordered list)
 msgid ""
@@ -2057,7 +2058,7 @@ msgstr "確認目前使用中的每個版本都有公布原始碼在網際網路
 msgid ""
 "Confirm that the [codebase](../glossary.md#codebase) files and commit "
 "history do not include sensitive information."
-msgstr "確認[代碼庫](../glossary."
+msgstr "確認[程式基底](../glossary."
 "md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。"
 
 #: ./criteria/code-in-the-open.md:block 10 (unordered list)
@@ -2150,7 +2151,7 @@ msgstr ""
 
 #: ./criteria/document-codebase-maturity.md:block 4 (header)
 msgid "Document codebase maturity"
-msgstr "記錄代碼庫成熟度"
+msgstr "記錄程式基底成熟度"
 
 #: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
 msgid ""
@@ -2160,32 +2161,32 @@ msgid ""
 "codebase has evolved is key to understanding the codebase and how to "
 "contribute to it."
 msgstr ""
-"清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用，"
-"或為該代碼庫做出貢獻。代碼庫版本的成熟度，包含其依賴項目的成熟度。瞭解代碼庫"
-"演進到什麼程度，是理解該代碼庫並知道如何做出貢獻的關鍵。"
+"清楚標示[程式基底](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用"
+"，或為該程式基底做出貢獻。程式基底版本的成熟度，包含其依賴項目的成熟度。瞭解"
+"程式基底演進到什麼程度，是理解該程式基底並知道如何做出貢獻的關鍵。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The codebase MUST be versioned."
-msgstr "代碼庫「必須」註明版本編號。"
+msgstr "程式基底「必須」註明版本編號。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase MUST prominently document whether or not there are versions of "
 "the codebase that are ready to use."
-msgstr "代碼庫「必須」明確以文件記錄，是否有已經準備好可供使用的版本。"
+msgstr "程式基底「必須」明確以文件記錄，是否有已經準備好可供使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "Codebase versions that are ready to use MUST only depend on versions of "
 "other codebases that are also ready to use."
-msgstr "準備好可供使用的代碼庫版本，「必須」只能依賴其他也已經準備好可供使用的代碼庫"
-"版本。"
+msgstr "準備好可供使用的程式基底版本，「必須」只能依賴其他也已經準備好可供使用的程式"
+"基底版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid ""
 "The codebase SHOULD contain a log of changes from version to version, for "
 "example in the `CHANGELOG`."
-msgstr "代碼庫「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
+msgstr "程式基底「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "The method for assigning version identifiers SHOULD be documented."
@@ -2193,31 +2194,31 @@ msgstr "「應該」要以文件記錄分配版本識別碼的方法。"
 
 #: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
 msgid "It is OPTIONAL to use semantic versioning."
-msgstr "「可選擇」是否使用語意化版本控制編號。"
+msgstr "「可選擇」是否採用語意化版本控制編號。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that the codebase has a strategy for versioning which is documented."
-msgstr "確認代碼庫有版本編號策略，且有文件記載該策略。"
+msgstr "確認程式基底有版本編號策略，且有文件記載該策略。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that it is obvious to policy makers, managers, developers and "
 "designers whether the codebase has versions that are ready to use."
-msgstr "確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道代碼庫是否有準備好"
-"可供使用的版本。"
+msgstr "確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道程式基底是否有準備"
+"好可供使用的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Confirm that ready to use versions of the codebase do not depend on any "
 "versions of other codebases that are not ready to use."
-msgstr "確認準備好可供使用的代碼庫版本，並不依賴任何尚未準備好可供使用的其他代碼庫的"
-"版本。"
+msgstr "確認準備好可供使用的程式基底版本，並不依賴任何尚未準備好可供使用的其他程式基"
+"底的版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid ""
 "Check that the versioning scheme of the codebase is documented and followed."
-msgstr "確認有文件記錄代碼庫的版本編號方法，並且確實遵守。"
+msgstr "確認有文件記錄程式基底的版本編號方法，並且確實遵守。"
 
 #: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
 msgid "Check that there is a log of changes."
@@ -2229,34 +2230,34 @@ msgid ""
 " code](../glossary.md#source-code) developed needs to be tested and improved"
 " before it can be put into service."
 msgstr ""
-"制定[政策](../glossary.md#policy)時，請記住任何開發出來的 "
-"[原始碼](../glossary.md#source-code) 都必須先經過測試與改善，才能夠投入服務。"
+"制定[政策](../glossary.md#policy)時，請記住任何開發出來的[原始碼](../glossary"
+".md#source-code)都必須先經過測試與改善，才能夠投入服務。"
 
 #: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
 msgid ""
 "Consider versioning policy changes, especially when they trigger new "
 "versions of the source code."
-msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。"
+msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發新版本原始碼開發的情況。"
 
 #: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
 msgid ""
 "Make sure that services only rely on versions of codebases of equal or "
 "greater maturity than the service. For example, don't use a beta version of "
 "a codebase in a production service."
-msgstr "要確認服務依賴的代碼庫版本成熟度，等同或高於該服務本身。舉例來說，"
-"正式上線的服務不要使用 beta 公測版代碼庫。"
+msgstr "要確認服務依賴的程式基底版本成熟度，等同或高於該服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 公測版程式基底。"
 
 #: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
 msgid ""
 "Make sure that the codebase versioning approach is followed for all "
 "releases."
-msgstr "確認所有發行版，都有遵守代碼庫的版本控制編號作法。"
+msgstr "確認所有發行版，都有遵守程式基底的版本控制編號作法。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
 "[Semantic Versioning Specification](https://semver.org/) used by many "
 "codebases to label versions."
-msgstr "許多代碼庫使用「[語意化版本編號規範](https://semver.org/)」來標示版本。"
+msgstr "許多程式基底使用「[語意化版本編號規範](https://semver.org/)」來標示版本。"
 
 #: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
 msgid ""
@@ -2290,7 +2291,7 @@ msgstr "criteria/document-objectives"
 
 #: ./criteria/document-codebase-objectives.md:block 5 (header)
 msgid "Document codebase objectives"
-msgstr "代碼庫要有目標文件"
+msgstr "程式基底要有目標文件"
 
 #: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
 msgid ""
@@ -2300,49 +2301,49 @@ msgid ""
 "provide an easy way for people to decide whether this codebase, or one of "
 "its modules, is interesting for them now or in the future."
 msgstr ""
-"以文件清楚記錄[代碼庫](../glossary.md#codebase)目標，來傳達代碼庫的用途目標。"
-"這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能方便人們判斷，是"
-"否在當下或未來，會對此代碼庫或其模組感興趣。"
+"以文件清楚記錄[程式基底](../glossary.md#codebase)目標，來傳達程式基底的用途目"
+"標。這能幫助利害關係人與貢獻者劃定程式基底的開發範圍。這些目標也能方便人們判"
+"斷，是否在當下或未來，會對此程式基底或其模組感興趣。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST contain documentation of its objectives, like a mission "
 "and goal statement, that is understandable by developers and designers so "
 "that they can use or contribute to the codebase."
-msgstr "代碼庫「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師"
-"需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。"
+msgstr "程式基底「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計"
+"師需要能夠瞭解這些，他們才知道可以怎樣使用程式基底或協助貢獻。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Codebase documentation SHOULD clearly describe the connections between "
 "[policy](../glossary.md#policy) objectives and codebase objectives."
-msgstr "代碼庫文件「應該」清楚描述[政策](../glossary."
-"md#policy)目標與代碼庫目標之前的關聯。"
+msgstr "程式基底文件「應該」清楚描述[政策](../glossary."
+"md#policy)目標與程式基底目標之間的關聯。"
 
 #: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
 msgid ""
 "Documenting the objectives of the codebase for the [general "
 "public](../glossary.md#general-public) is OPTIONAL."
 msgstr "「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-"
-"public)看的代碼庫目標。"
+"public)看的程式基底目標。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase documentation includes the codebase objectives, "
 "mission or goal."
-msgstr "確認代碼庫文件有包含代碼庫目標，或主旨、使命等。"
+msgstr "確認程式基底文件有包含程式基底目標，或主旨、使命等。"
 
 #: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
 msgid ""
 "Check for descriptions of connections between policy objectives and codebase"
 " objectives."
-msgstr "查看政策目標與代碼庫目標之間關聯的描述。"
+msgstr "查看政策目標與程式基底目標之間關聯的描述。"
 
 #: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
 msgid ""
 "Add the policy objectives to the codebase documentation, for example in the "
 "`README`."
-msgstr "將政策目標加入代碼庫文件中，例如「`README`」文件當中。"
+msgstr "將政策目標加入程式基底文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
 msgid ""
@@ -2350,20 +2351,20 @@ msgid ""
 "supporting policy documents added to meet the [Bundle policy and source "
 "code](bundle-policy-and-source-code.md) criterion."
 msgstr ""
-"確保所有代碼庫目標，有連結或引用為了符合[政策與原始碼要合捆](bundle-policy-"
-"and-source-code.md)準則而加入的支持政策文件。"
+"確保所有程式基底目標，有連結或引用為了符合〈[政策與原始碼要合捆](bundle-"
+"policy-and-source-code.md)〉準則而加入的支持政策文件。"
 
 #: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
 msgid ""
 "Add the organizational and business objectives to the codebase "
 "documentation, for example in the `README`."
-msgstr "將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。"
+msgstr "將單位目標、組織目標或業務目標加入程式基底文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
 msgid ""
 "Add the technology and design objectives to the codebase documentation, for "
 "example in the `README`."
-msgstr "將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。"
+msgstr "將技術與設計目標加入程式基底文件中，例如「`README`」文件當中。"
 
 #: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
 msgid ""
@@ -2394,8 +2395,8 @@ msgid ""
 "and contributing to it more quickly."
 msgstr ""
 "文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作"
-"用與使用方式。文件紀錄是幫助人們快速上手[代碼庫](../glossary."
-"md#codebase)的使用並做出貢獻的關鍵。"
+"用與使用方式。文件紀錄是幫助人們快速上手如何使用[程式基底](../glossary."
+"md#codebase)，並做出貢獻的關鍵。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2403,20 +2404,20 @@ msgid ""
 " well as source code, MUST be described in language clearly understandable "
 "for those that understand the purpose of the codebase."
 msgstr ""
-"代碼庫的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚瞭"
-"解的用語描述，讓懂代碼庫目的用途的人也能夠理解。"
+"程式基底的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚"
+"瞭解的用語描述，讓懂程式基底目的用途的人也能夠理解。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain a description of how to "
 "install and run the software."
-msgstr "代碼庫文件「必須」說明如何安裝與執行軟體。"
+msgstr "程式基底文件「必須」說明如何安裝與執行軟體。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase MUST contain examples demonstrating the "
 "key functionality."
-msgstr "代碼庫文件「必須」為關鍵功能舉出範例。"
+msgstr "程式基底文件「必須」為關鍵功能舉出範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2424,7 +2425,7 @@ msgid ""
 "that is clearly understandable for a wide audience of stakeholders, like the"
 " [general public](../glossary.md#general-public) and journalists."
 msgstr ""
-"代碼庫文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-"
+"程式基底文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-"
 "public)和記者等廣泛的利害關係人都能清楚明白。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
@@ -2432,22 +2433,22 @@ msgid ""
 "The documentation of the codebase SHOULD contain a section describing how to"
 " install and run a standalone version of the source code, including, if "
 "necessary, a test dataset."
-msgstr "代碼庫文件「應該」有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要"
-"，也應該包含測試資料集。"
+msgstr "程式基底文件「應該」有一部分用來說明，如何安裝與執行原始碼的單機版；如果有必"
+"要，也應該包含測試資料集。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation of the codebase SHOULD contain examples for all "
 "functionality."
-msgstr "代碼庫文件「應該」包含所有功能的範例。"
+msgstr "程式基底文件「應該」包含所有功能的範例。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
 "The documentation SHOULD describe the key components or modules of the "
 "codebase and their relationships, for example as a high level architectural "
 "diagram."
-msgstr "程式碼文件「應該」描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高"
-"層架構圖表示。"
+msgstr "程式碼文件「應該」描述程式基底的主要組件或模組，以及其彼此之間的關係，例如以"
+"高層架構圖表示。"
 
 #: ./criteria/document-the-code.md:block 8 (unordered list)
 msgid ""
@@ -2460,7 +2461,7 @@ msgstr "「應該」要有針對文件品質的[持續整合](../glossary.md#con
 msgid ""
 "Including examples that make users want to immediately start using the "
 "codebase in the documentation of the codebase is OPTIONAL."
-msgstr "「可選擇」是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。"
+msgstr "「可選擇」是否在程式基底文件中，包含讓使用者想要立即使用程式基底的範例。"
 
 #: ./criteria/document-the-code.md:block 10 (unordered list)
 msgid ""
@@ -2515,7 +2516,7 @@ msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成
 msgid ""
 "Check in regularly to understand how the non-policy code in the codebase has"
 " changed."
-msgstr "定期查看代碼庫中非政策程式碼的變動情況。"
+msgstr "定期查看程式基底中非政策程式碼的變動情況。"
 
 #: ./criteria/document-the-code.md:block 12 (unordered list)
 msgid "Give feedback on how to make non-policy documentation more clear."
@@ -2527,8 +2528,10 @@ msgid ""
 " and source code are documented. For example, is the current documentation "
 "sufficient to persuade a manager at another public organization to use this "
 "codebase?"
-msgstr "嘗試使用代碼庫，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來"
-"說，目前的文件是否足以說服另一個公家機關的管理人員使用這個代碼庫？"
+msgstr ""
+"嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例"
+"來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這個程式基底"
+"？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
 msgid ""
@@ -2540,7 +2543,7 @@ msgstr "確保您同時瞭解政策、原始碼以及文件內容。"
 msgid ""
 "Check in regularly to understand how the non-source code in the codebase has"
 " changed."
-msgstr "定期查看代碼庫中非原始碼部分的變動情況。"
+msgstr "定期查看程式基底中非原始碼部分的變動情況。"
 
 #: ./criteria/document-the-code.md:block 16 (unordered list)
 msgid "Give feedback on how to make non-source documentation more clear."
@@ -2600,14 +2603,14 @@ msgid ""
 "changes in parallel and helps future developers to understand the reasons "
 "for changes."
 msgstr ""
-"[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md"
-"#source-code)以及其他[代碼庫](../glossary.md#codebase)檔案歷來的變動。這能讓"
-"您為代碼庫維護有條理的變動歷史文件。這是大規模協作能運作的要素，使開發人員得"
-"以針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。"
+"[版本控制](../glossary.md#version-control)主要在追蹤[原始碼](../glossary.md"
+"#source-code)以及其他[程式基底](../glossary.md#codebase)檔案歷來的變動。這能"
+"讓您為程式基底維護有條理的變動歷史文件。這是大規模協作得以運作的要素，使開發"
+"人員可以針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All files in the codebase MUST be version controlled."
-msgstr "代碼庫中的所有檔案皆「必須」有版本控制。"
+msgstr "程式基底中的所有檔案皆「必須」有版本控制。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid "All decisions MUST be documented in commit messages."
@@ -2621,7 +2624,7 @@ msgstr "每份送交版次訊息皆「必須」盡可能附上討論與議題連
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
 "The codebase SHOULD be maintained in a distributed version control system."
-msgstr "代碼庫「應該」以分散式版本控制系統作維護。"
+msgstr "程式基底「應該」以分散式版本控制系統作維護。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
@@ -2633,8 +2636,8 @@ msgstr "貢獻守則「應該」要求貢獻者，將相關的修改變動以群
 msgid ""
 "Maintainers SHOULD mark released versions of the codebase, for example using"
 " revision tags or textual labels."
-msgstr "維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本"
-"。"
+msgstr "維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版"
+"本。"
 
 #: ./criteria/maintain-version-control.md:block 8 (unordered list)
 msgid ""
@@ -2656,7 +2659,7 @@ msgstr "貢獻者「可選擇」是否在提交內容中簽章，並附上電子
 msgid ""
 "Confirm that the codebase is kept in version control using software such as "
 "Git."
-msgstr "確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。"
+msgstr "確認程式基底維持在版本控制狀態中，像是使用 Git 之類的軟體。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
@@ -2686,20 +2689,21 @@ msgstr "審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相
 msgid ""
 "Check that it is possible to access a specific version of the codebase, for "
 "example through a revision tag or a textual label."
-msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。"
+msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來取用程式基底中的特定版本。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
 msgid ""
 "Check that the file formats used in the codebase are text formats where "
 "possible."
-msgstr "檢查代碼庫在可能的情況下，檔案都是採用文字格式。"
+msgstr "檢查程式基底在盡可能的情況下，檔案都是採用文字格式。"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid ""
 "If a new version of the codebase is created because of a "
 "[policy](../glossary.md#policy) change, make sure it's clear in the "
 "documentation:"
-msgstr "如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明："
+msgstr "如果因為[政策](../glossary."
+"md#policy)改變而在程式基底中有新的版本，則請確認有在文件中清楚說明："
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid "what the policy change is,"
@@ -2707,26 +2711,28 @@ msgstr "政策改變的地方，"
 
 #: ./criteria/maintain-version-control.md:block 12 (unordered list)
 msgid "how it's changed the codebase."
-msgstr "代碼庫如何因應而改變。"
+msgstr "程式基底如何因應而改變。"
 
 #: ./criteria/maintain-version-control.md:block 13 (paragraph)
 msgid ""
 "For example, adding a new category of applicant to a codebase that manages "
 "granting permits would be considered a policy change."
-msgstr "舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。"
+msgstr "舉例來說，為程式基底作權限管理時，如果要新增申請方類別來賦予取用權，應視為一"
+"種政策變動。"
 
 #: ./criteria/maintain-version-control.md:block 15 (unordered list)
 msgid ""
 "Support policy makers, developers and designers to be clear about what "
 "improvements they're making to the codebase. Making improvements isn't a "
 "public relations risk."
-msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。"
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對程式基底做出的改善。確"
+"保改善程式基底不會有公關風險。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
 "Make sure that all files required to understand the code, build and deploy "
 "are in the version control system."
-msgstr "確認版本控制系統中，有瞭解程式碼、建置與部署所需的所有檔案。"
+msgstr "確認版本控制系統中，有瞭解程式碼、建置與部署所需要用到的所有檔案。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid ""
@@ -2738,7 +2744,7 @@ msgstr "送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的
 msgid ""
 "Mark different versions so that it is easy to access a specific version, for"
 " example using revision tags or textual labels."
-msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。"
+msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。"
 
 #: ./criteria/maintain-version-control.md:block 17 (unordered list)
 msgid "Write clear commit messages so that versions can be usefully compared."
@@ -2782,7 +2788,7 @@ msgid ""
 "education.pdf) by GitHub, a list with the most common used git commands."
 msgstr ""
 "GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-"
-"education.pdf)」列出了最常用的 git 指令。"
+"education.pdf)」，列出了最常用的 git 命令。"
 
 #: ./criteria/make-contributing-easy.md:block 3 (header)
 msgid "order: 5"
@@ -2798,36 +2804,36 @@ msgid ""
 " able to fix problems, add features, and address security issues of the "
 "shared [codebase](../glossary.md#codebase)."
 msgstr ""
-"若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[代碼庫](../glo"
-"ssary.md#codebase)修正問題、新增功能，以及提出安全性議題等。"
+"若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[程式基底](../g"
+"lossary.md#codebase)修正問題、新增功能，以及提出安全性議題等。"
 
 #: ./criteria/make-contributing-easy.md:block 6 (paragraph)
 msgid ""
 "A shared digital infrastructure makes it easier to make collaborative "
 "contributions. The less effort it takes to make contributions that are "
 "accepted by the codebase, the more likely users are to become contributors."
-msgstr "共享的數位基礎建設讓協作貢獻更容易。使用者讓代碼庫接受貢獻時所需付出的心力越"
-"少，則使用者越可能成為貢獻者。"
+msgstr "共享的數位基礎建設讓協作貢獻更容易。使用者讓程式基底接受貢獻時所需付出的心力"
+"越少，則使用者越可能成為貢獻者。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have a public issue tracker that accepts suggestions from "
 "anyone."
-msgstr "代碼庫「必須」有個可以公開接受任何人建議的議題追蹤器。"
+msgstr "程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記"
-"錄在「`README`」檔案中。"
+msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及提交的程式基底變動的連結，例如"
+"記錄在「`README`」檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST have communication channels for users and developers, for "
 "example email lists."
-msgstr "代碼庫「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵"
-"遞論壇）。"
+msgstr "程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（"
+"郵遞論壇）。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
@@ -2849,13 +2855,13 @@ msgstr "確認有公開的議題追蹤器。"
 msgid ""
 "Confirm that the codebase contains links to the public issue tracker and "
 "submitted codebase changes."
-msgstr "確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。"
+msgstr "確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid ""
 "Confirm that it is possible to participate in a discussion with other users "
 "and developers about the software using channels described in the codebase."
-msgstr "確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
+msgstr "確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid "Confirm that there is a closed channel for reporting security issues."
@@ -2870,19 +2876,21 @@ msgstr "確認有說明如何私下通報安全性問題。"
 msgid ""
 "Track [policy](../glossary.md#policy) issues in the codebase, so that a "
 "relevant external policy expert can volunteer help."
-msgstr "追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
+msgstr "追蹤程式基底中的[政策](../glossary."
+"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
 
 #: ./criteria/make-contributing-easy.md:block 14 (unordered list)
 msgid ""
 "Track management issues in the codebase, so that external managers with "
 "relevant experience can volunteer help."
-msgstr "追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
+msgstr "追蹤程式基底中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
 
 #: ./criteria/make-contributing-easy.md:block 14 (unordered list)
 msgid ""
 "Support your experienced policy makers, developers and designers to keep "
 "contributing to the codebase for as long as possible."
-msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。"
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為程式基底持續做出長"
+"久貢獻。"
 
 #: ./criteria/make-contributing-easy.md:block 16 (unordered list)
 msgid ""
@@ -2936,7 +2944,7 @@ msgstr "criteria/findability"
 
 #: ./criteria/make-the-codebase-findable.md:block 5 (header)
 msgid "Make the codebase findable"
-msgstr "代碼庫可查詢得到"
+msgstr "程式基底可查詢得到"
 
 #: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
 msgid ""
@@ -2944,8 +2952,9 @@ msgid ""
 "potential new collaborators will find it. Just publishing a codebase and "
 "hoping it is found does not work, instead proactiveness is needed."
 msgstr ""
-"一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到"
-"它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，更需要主動積極。"
+"一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得"
+"到它。不能只是發表個程式基底，然後就盼望他人找得到這個程式基底，更需要主動積"
+"極。"
 
 #: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
 msgid ""
@@ -2955,45 +2964,47 @@ msgid ""
 "the codebase easier for people to refer, cite, disambiguate and discover "
 "through third party tools."
 msgstr ""
-"有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF "
-"自由軟體基金會的軟體目錄列表之中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。"
+"有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中"
+"介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄"
+"列表之中（使程式基底成為語意網路中的一部份），他人就能更容易透過第三方工具參"
+"考、引用、辨別、發現程式基底。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The name of the codebase SHOULD be descriptive and free from acronyms, "
 "abbreviations, puns or organizational branding."
-msgstr "代碼庫名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語"
-"，或組織單位品牌名稱或抬頭等。"
+msgstr "程式基底名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關"
+"語，或組織單位品牌名稱或抬頭等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a short description that helps someone understand "
 "what the codebase is for or what it does."
-msgstr "代碼庫說明「應該」要簡短，幫助他人瞭解代碼庫的目的與作用。"
+msgstr "程式基底說明「應該」要簡短，幫助他人瞭解程式基底的目的與作用。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
-msgstr "維護人員「應該」將代碼庫提交至相關的軟體目錄上。"
+msgstr "維護人員「應該」將程式基底提交至相關的軟體目錄上。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD have a website which describes the problem the codebase "
 "solves using the preferred jargon of different potential users of the "
 "codebase (including technologists, policy experts and managers)."
-msgstr "代碼庫「應該」要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、"
-"管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。"
+msgstr "程式基底「應該」要架設網站，內容中以程式基底各類潛在使用者（技術人員、政策專"
+"家、管理人員等）偏好的業內用語，描述程式基底所能解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by codebase name."
-msgstr "在搜尋引擎查找代碼庫名稱時，「應該」能搜尋得到代碼庫。"
+msgstr "在搜尋引擎查找程式基底名稱時，「應該」能搜尋得到程式基底。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
 "The codebase SHOULD be findable using a search engine by describing the "
 "problem it solves in natural language."
-msgstr "在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，「應該」能搜尋得到"
-"代碼庫。"
+msgstr "在使用搜尋引擎時，如果以自然語言描述程式基底所能解決的問題，「應該」能搜尋得"
+"到程式基底。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -3001,8 +3012,8 @@ msgid ""
 "mentions the major contributors, [repository](../glossary.md#repository) "
 "location and website."
 msgstr ""
-"代碼庫「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../g"
-"lossary.md#repository)、位置、網站等。"
+"程式基底「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](.."
+"/glossary.md#repository)、位置、網站等。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid ""
@@ -3010,12 +3021,12 @@ msgid ""
 "example in a "
 "[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
 msgstr ""
-"代碼庫「應該」包含機器可讀的中介資料說明，例如採用[publiccode."
+"程式基底「應該」包含機器可讀的中介資料說明，例如採用[publiccode."
 "yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "A dedicated domain name for the codebase is OPTIONAL."
-msgstr "「可選擇」是否為代碼庫設置專用的網域名稱。"
+msgstr "「可選擇」是否為程式基底設置專用的網域名稱。"
 
 #: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
 msgid "Regular presentations at conferences by the community are OPTIONAL."
@@ -3023,52 +3034,52 @@ msgstr "「可選擇」是否在社群舉辦的會議中定期進行簡報。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check that the codebase name is descriptive and free of puns."
-msgstr "檢查代碼庫名稱是否描述說明其用途，且不包含雙關語。"
+msgstr "檢查程式基底名稱是否描述說明其用途，且不包含雙關語。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of acronyms and abbreviations or that "
 "the acronyms or abbreviations in the name are more universally known than "
 "the longer forms."
-msgstr "檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完"
-"整名稱更熟為人知。"
+msgstr "檢查程式基底名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比"
+"完整名稱更熟為人知。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase name is free of organizational branding, unless that"
 " organization is of the codebase community itself."
-msgstr "檢查代碼庫是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是代碼庫社群成"
-"員。"
+msgstr "檢查程式基底是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是程式基底社"
+"群成員。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase repository has a short description of the codebase."
-msgstr "檢查代碼庫儲存庫是否包含代碼庫的簡短描述。"
+msgstr "檢查程式基底儲存庫是否包含程式基底的簡短描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check for the codebase listing in relevant software catalogs."
-msgstr "檢查代碼庫有刊登在相關軟體型錄上。"
+msgstr "檢查程式基底有刊登在相關軟體型錄上。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check for a codebase website which describes the problem the codebase "
 "solves."
-msgstr "檢查代碼庫的網站有描述代碼庫能夠解決的問題。"
+msgstr "檢查程式基底的網站有描述程式基底能夠解決的問題。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by the codebase name."
-msgstr "檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將代碼庫列在搜"
-"尋結果中。"
+msgstr "檢查以程式基底名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將程式基底列"
+"在搜尋結果中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check that the codebase appears in the results on more than one major search"
 " engine when searching by using natural language, for instance, using the "
 "short description."
-msgstr "檢查以自然語言來作搜尋，例如使用代碼庫的簡短描述時，有超過一個的常用主流搜尋"
-"引擎，都將代碼庫放在搜尋結果中。"
+msgstr "檢查以自然語言來作搜尋，例如使用程式基底的簡短描述時，有超過一個的常用主流搜"
+"尋引擎，都將程式基底放在搜尋結果中。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
@@ -3084,29 +3095,29 @@ msgstr "檢查永久唯一識別碼條目中有包含儲存庫位置。"
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid ""
 "Check unique and persistent identifier entries for the codebase website."
-msgstr "檢查永久唯一識別碼條目有列出代碼庫網站。"
+msgstr "檢查永久唯一識別碼條目有列出程式基底網站。"
 
 #: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
 msgid "Check for a machine-readable metadata description file."
-msgstr "檢查中介資料說明檔案是機器可讀的格式。"
+msgstr "檢查中介資料說明檔是機器可讀的格式。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Contribute a description of the policy area or problem this codebase acts on"
 " or operates."
-msgstr "貢獻一段說明此代碼庫作用的政策領域，或處理的問題的描述。"
+msgstr "貢獻一段說明此程式基底作用的政策領域，或所處理問題的描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Test your problem description with peers outside of your context who aren't "
 "familiar with the codebase."
-msgstr "請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。"
+msgstr "請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。"
 
 #: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
 msgid ""
 "Present on how the codebase implements the [policy](../glossary.md#policy) "
 "at relevant conferences."
-msgstr "在相關會議上作簡報，介紹代碼庫如何執行[政策](../glossary.md#policy)。"
+msgstr "在相關會議上作簡報，介紹程式基底如何執行[政策](../glossary.md#policy)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
@@ -3118,12 +3129,12 @@ msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as social media account descriptions."
-msgstr "在引用到代碼庫的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。"
+msgstr "在引用到程式基底的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
 "Budget for content design and Search Engine Optimization skills in the team."
-msgstr "為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。"
+msgstr "為團隊編列內容設計與實作 SEO 搜尋引擎最佳化技能的預算。"
 
 #: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
 msgid ""
@@ -3134,13 +3145,14 @@ msgstr "確保專案參與人員出席相關會議，或作簡報介紹。"
 msgid ""
 "Search engine optimization, for instance adding a "
 "[sitemap](https://www.sitemaps.org/protocol.html)."
-msgstr "搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol.html)。"
+msgstr "實作搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol."
+"html)。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid ""
 "Use the short description wherever the codebase is referenced, for instance,"
 " as the repository description."
-msgstr "在引用到代碼庫的地方，都使用簡短描述，例如放到儲存庫中的說明。"
+msgstr "在引用到程式基底的地方，都使用簡短描述，例如放到儲存庫中的說明。"
 
 #: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
 msgid "Suggest conferences to present at and present at them."
@@ -3170,8 +3182,11 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
-"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](https://www.go-fair.org/fair-"
-"principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。"
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
+"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
+"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
+"分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底"
+"與其對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
 msgid "order: 3 redirect_from:"
@@ -3189,7 +3204,7 @@ msgstr "criteria/create-reusable-and-portable-code"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
 msgid "Make the codebase reusable and portable"
-msgstr "代碼庫要可重複使用且可移植"
+msgstr "程式基底要可重複使用且可移植"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
 msgid ""
@@ -3199,8 +3214,8 @@ msgid ""
 "quality, cheaper maintenance and higher reliability."
 msgstr ""
 "編寫可重複使用且可移植的[程式碼](../glossary.md#code)，讓政策制定者、開發人員"
-"與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻回代碼庫中，"
-"如此可提高品質、降低維護成本、增強可靠性。"
+"與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻回程式基底中"
+"，如此可提高品質、降低維護成本、增強可靠性。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
 msgid ""
@@ -3210,9 +3225,9 @@ msgid ""
 " developed and used by multiple parties are more likely to benefit from a "
 "self-sustaining community."
 msgstr ""
-"以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方共享代"
-"碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫，更可以從能自我運作的社"
-"群中獲益。"
+"以重複利用為前提籌劃設計[程式基底](../glossary.md#codebase)，更容易與多方共享"
+"程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，更可以從能自我運"
+"作的社群中獲益。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
 msgid ""
@@ -3221,8 +3236,8 @@ msgid ""
 "[another context](../glossary.md#different-contexts) if its purpose is "
 "clearly documented."
 msgstr ""
-"以文件記錄周全的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄"
-"用途的模組，更容易在[另一種情境](../glossary.md#different-"
+"以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記"
+"錄用途的模組，更容易在[另一種情境](../glossary.md#different-"
 "contexts)中重複利用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
@@ -3236,20 +3251,20 @@ msgstr "原始碼不依賴任何貢獻者、供應商或部署底下的特定情
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase MUST be developed to be reusable in different contexts."
-msgstr "代碼庫「必須」開發成能在不同情境中重複使用。"
+msgstr "程式基底「必須」開發成能在不同情境中重複使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid ""
 "The codebase MUST be independent from any secret, undisclosed, proprietary "
 "or non-open licensed software or services for execution and understanding."
-msgstr "代碼庫「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，"
-"以供執行與瞭解。"
+msgstr "程式基底「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務"
+"，以供執行與瞭解。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be in use by multiple parties."
-msgstr "代碼庫「應該」有多方單位使用。"
+msgstr "程式基底「應該」有多方單位使用。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3261,7 +3276,7 @@ msgstr "發展路線圖「應該」有多方單位的需求影響。"
 msgid ""
 "The development of the codebase SHOULD be a collaboration between multiple "
 "parties."
-msgstr "代碼庫開發「應該」由多方單位協作。"
+msgstr "程式基底開發「應該」由多方單位協作。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3274,7 +3289,7 @@ msgstr "「應該」使用組態設定方式以將[原始碼](../glossary.md#sou
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
 msgid "The codebase SHOULD be localizable."
-msgstr "代碼庫「應該」能夠在地化。"
+msgstr "程式基底「應該」能夠在地化。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3288,7 +3303,7 @@ msgstr "原始碼與其文件「不應該」包含特定情況專用的資訊。
 msgid ""
 "Codebase modules SHOULD be documented in such a way as to enable reuse in "
 "codebases in other contexts."
-msgstr "代碼庫模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。"
+msgstr "程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3302,36 +3317,37 @@ msgstr "軟體「不應該」要求僅有單一供應商能提供的服務或平
 msgid ""
 "Confirm with someone in a similar role at another organization if they can "
 "use the codebase and what that would entail."
-msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行。"
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用程式基底，以及需要怎麼進"
+"行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Confirm that the codebase can run without using any proprietary or non open-"
 "licensed software or services."
-msgstr "確認代碼庫不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。"
+msgstr "確認程式基底不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "If the codebase is in early development before a production-ready release, "
 "then check for evidence of ambition to obtain collaborators."
-msgstr "若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意"
-"圖跡象。"
+msgstr "若程式基底處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的"
+"意圖跡象。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Or if the codebase is very mature and stable with very infrequent fixes, "
 "patches, or contributions:"
-msgstr "或是如果代碼庫非常成熟與穩定，鮮少需要修正、改善或貢獻："
+msgstr "或是如果程式基底非常成熟與穩定，鮮少需要修正、改善或貢獻："
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the codebase is in use by multiple parties or in multiple "
 "contexts."
-msgstr "檢查是否有多方單位，或是有在多種情境下正使用代碼庫。"
+msgstr "檢查是否有多方單位，或是有在多種情境下正使用程式基底。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3346,14 +3362,14 @@ msgstr "若是沒有，則："
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid "Check that the codebase contributors are from multiple parties."
-msgstr "檢查代碼庫貢獻者是否來自多方單位。"
+msgstr "檢查程式基底貢獻者是否來自多方單位。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
 msgid ""
 "Check that the codebase files and commit history do not include situation-"
 "specific data."
-msgstr "檢查代碼庫檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。"
+msgstr "檢查程式基底檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
 #: list)
@@ -3372,7 +3388,7 @@ msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
 msgid "Make sure your organization is listed as a known user by the codebase."
-msgstr "確保代碼庫有將貴組織單位列為已知使用者。"
+msgstr "確保程式基底有將貴組織單位列為已知使用者。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
 #: list)
@@ -3385,7 +3401,8 @@ msgid ""
 "Make sure that stakeholders and business owners understand that reusability "
 "is an explicit codebase goal as this reduces technical debt and provides "
 "sustainability for the codebase."
-msgstr "確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。"
+msgstr "確認利害關係人與業主能夠瞭解，程式基底是以重複利用為明確目標，因而得以減少程"
+"式碼技術債，並讓程式基底可以永續發展。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
 #: list)
@@ -3425,9 +3442,9 @@ msgid ""
 "platforms or using proprietary components, make sure that collaborators can "
 "develop, use, test, and deploy without them."
 msgstr ""
-"確保代碼庫文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要"
-"部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況"
-"下，就能進行開發、使用、測試、部署等。"
+"確保程式基底文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需"
+"要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情"
+"況下，就能進行開發、使用、測試、部署等。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
 msgid ""
@@ -3477,15 +3494,15 @@ msgid ""
 "emerge around the codebase."
 msgstr ""
 "採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-"
-"code)，使其能瞭解運作方式、自由使用，並且能為[代碼庫](../glossary."
-"md#codebase)做出貢獻。這也能促進供應商建立出以代碼庫為中心的生態系。"
+"code)，使其能瞭解運作方式、自由使用，並且能為[程式基底](../glossary."
+"md#codebase)做出貢獻。這也能促進供應商建立出以程式基底為中心的生態系。"
 
 #: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
 msgid ""
 "Clearly indicating the license for each file within a codebase facilitates "
 "correct reuse and attribution of parts of a codebase."
-msgstr "明確指出代碼庫中每一個檔案的授權，讓使用者能正確重複利用代碼庫的部分內容，並"
-"表彰作者名稱。"
+msgstr "明確指出程式基底中每一個檔案的授權，讓使用者能正確重複利用程式基底的部分內容"
+"，並表彰作者名稱。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
@@ -3510,14 +3527,14 @@ msgstr "所有原始碼皆「必須」搭配授權條款檔案一併發行。"
 msgid ""
 "Contributors MUST NOT be required to transfer copyright of their "
 "contributions to the codebase."
-msgstr "「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。"
+msgstr "「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給程式基底。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
 "All source code files in the codebase SHOULD include a copyright notice and "
 "a license header that are machine-readable."
-msgstr "代碼庫中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容"
-"。"
+msgstr "程式基底中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內"
+"容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
 msgid ""
@@ -3527,7 +3544,7 @@ msgstr "「可選擇」是否為不同類型的原始碼與文件採用多重授
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the codebase is clearly licensed."
-msgstr "確認代碼庫有清楚給予授權條款。"
+msgstr "確認程式基底有清楚給予授權條款。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
@@ -3541,7 +3558,7 @@ msgstr ""
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid "Confirm that the licenses used in the codebase are included as files."
-msgstr "確認代碼庫中有包含其採用的授權條款檔案。"
+msgstr "確認程式基底中有包含其採用的授權條款檔案。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
@@ -3549,14 +3566,15 @@ msgid ""
 "[repository](../glossary.md#repository) configuration do not require "
 "transfer of copyright."
 msgstr "確認貢獻指引中，以及[儲存庫](../glossary."
-"md#repository)的組態設定中，沒有求貢獻者轉讓著作權。"
+"md#repository)的組態設定中，沒有要求貢獻者轉讓著作權。"
 
 #: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
 msgid ""
 "Check for machine-readable license checking in the codebase [continuous "
 "integration](../glossary.md#continuous-integration) tests."
 msgstr ""
-"在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
+"在程式基底[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
 
 #: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
 msgid ""
@@ -3576,7 +3594,7 @@ msgstr "制定抑制採購非開放原始碼授權程式碼，與非開放科技
 msgid ""
 "Only work with open source vendors that deliver their source code by "
 "publishing it under an open source license."
-msgstr "只與能採用開放原始碼授權，交付與發行其原始碼的開放原始碼軟體供應商合作。"
+msgstr "只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
@@ -3590,7 +3608,7 @@ msgstr ""
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid "Add a new `license` file to every new codebase created."
-msgstr "每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。"
+msgstr "每當建立新的程式基底時，都要加入新的「`license`」授權條款檔案。"
 
 #: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
 msgid ""
@@ -3602,7 +3620,7 @@ msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授
 msgid ""
 "When source code is being reused by the codebase, make sure that it has a "
 "license that is compatible with the license or licenses of the codebase."
-msgstr "當代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。"
+msgstr "每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
@@ -3626,16 +3644,16 @@ msgid ""
 "Software Foundation Europe for unambiguous, human-readable and machine-"
 "readable copyright and licensing information."
 msgstr ""
-"歐洲自由軟體基金會所發表的《[REUSE "
-"倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
+"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
+")》，提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
 
 #: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
 msgid ""
 "[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
 " standardized, machine-readable abbreviations for most licenses."
 msgstr ""
-"Linux 基金會所發表的 [SPDX "
-"授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
+"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
+")，提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
 
 #: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
 msgid "order: 7 redirect_from:"
@@ -3667,9 +3685,9 @@ msgid ""
 "individuals, and encourages a culture of focusing on solutions."
 msgstr ""
 "要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始"
-"碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，就發現與修正潛在臭"
-"蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反"
-"倒是鼓勵每個人都專注在解決方案上。"
+"碼能提高在原始碼加入[程式基底](../glossary.md#codebase)之前，就發現與修正潛在"
+"臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，"
+"反倒是鼓勵每個人都專注在解決方案上。"
 
 #: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
 msgid ""
@@ -3684,8 +3702,8 @@ msgstr ""
 msgid ""
 "All contributions that are accepted or committed to release versions of the "
 "codebase MUST be reviewed by another contributor."
-msgstr "所有被接受或是送交給代碼庫正式發行版本中的貢獻內容，都「必須」經過另一位貢獻"
-"者審查。"
+msgstr "所有被接受或是送交給程式基底正式發行版本中的貢獻內容，都「必須」經過另一位貢"
+"獻者審查。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews MUST include source, policy, tests and documentation."
@@ -3702,13 +3720,14 @@ msgid ""
 "The review process SHOULD confirm that a contribution conforms to the "
 "standards, architecture and decisions set out in the codebase in order to "
 "pass review."
-msgstr "審查流程「應該」確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。"
+msgstr "審查流程「應該」確認貢獻內容遵循程式基底的標準、架構、決策安排等，以通過審查"
+"。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
 "Reviews SHOULD include running both the software and the tests of the "
 "codebase."
-msgstr "審查內容「應該」包含執行軟體與執行代碼庫測試。"
+msgstr "審查內容「應該」包含執行軟體與執行程式基底測試。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid ""
@@ -3720,7 +3739,7 @@ msgstr "貢獻內容「應該」由與貢獻者不同背景情境的人來審查
 msgid ""
 "Version control systems SHOULD NOT accept non-reviewed contributions in "
 "release versions."
-msgstr "版本控制系統「不應該」在代碼庫的正式發行版本中，接受未經審查的貢獻內容。"
+msgstr "版本控制系統「不應該」在程式基底的正式發行版本中，接受未經審查的貢獻內容。"
 
 #: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
 msgid "Reviews SHOULD happen within two business days."
@@ -3748,7 +3767,7 @@ msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
 msgid ""
 "Check if guidelines for reviewers include instructions to review for "
 "conformance to standards, architecture and codebase guidelines."
-msgstr "檢查審查人員指引中，有包含是否遵循標準、架構、代碼庫指引等指示。"
+msgstr "檢查審查人員指引中，有包含是否遵循標準、架構、程式基底指引等指示。"
 
 #: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
 msgid "Check with reviewers if they run the software and tests during review."
@@ -3780,7 +3799,7 @@ msgstr "制定進行任何審查時，含原始碼與其他一切事物，都要
 msgid ""
 "Use a version control system or methodology that enables review and "
 "feedback."
-msgstr "採用具有審查與意見回饋功能的版本控制系統或作業流程。"
+msgstr "採用具有審查與意見回饋功能的版本控制系統，或作業流程。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid "Make delivering great software a shared objective."
@@ -3790,7 +3809,7 @@ msgstr "將交付妥善軟體作為共同目標。"
 msgid ""
 "Make sure writing and reviewing contributions to source, policy, "
 "documentation and tests are considered equally valuable."
-msgstr "確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。"
+msgstr "確保如原始碼、政策、文件、測試等的貢獻內容撰寫與審查，皆受到同等重視。"
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid ""
@@ -3800,13 +3819,13 @@ msgstr "創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻
 
 #: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
 msgid "Make sure no contributor is ever alone in contributing to a codebase."
-msgstr "確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。"
+msgstr "確保貢獻者在貢獻內容給程式基底時，不是獨自一人埋頭苦幹。"
 
 #: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
 msgid ""
 "Ask other contributors on the codebase to review your work, in your "
 "organization or outside of it."
-msgstr "請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。"
+msgstr "請程式基底的其他貢獻者，審查您在貴組織單位內外的工作成果。"
 
 #: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
 msgid ""
@@ -3881,8 +3900,8 @@ msgid ""
 "guide, either the codebase community's own or an existing one referred to in"
 " the codebase."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作風"
-"格指引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用的既有風格。"
+"[程式基底](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作"
+"風格指引，可以是程式基底社群自身的風格指引，或是程式基底有採用的既有風格。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid "Contributions SHOULD pass automated tests on style."
@@ -3892,8 +3911,8 @@ msgstr "貢獻內容「應該」通過自動化的風格測試。"
 msgid ""
 "The style guide SHOULD include expectations for inline comments and "
 "documentation for non-trivial sections."
-msgstr "風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與寫下說明文件的期"
-"待。"
+msgstr "風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與為其寫下說明文件"
+"的期待。"
 
 #: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
 msgid ""
@@ -3919,7 +3938,7 @@ msgid ""
 "in the codebase, for example in the `CONTRIBUTING` or `README`."
 msgstr ""
 "為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄"
-"到代碼庫文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
+"到程式基底文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
 
 #: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
 msgid ""
@@ -3940,12 +3959,12 @@ msgid ""
 "documentation. Continually improve upon and expand this documentation with "
 "the aim of evolving this documentation into engineering guidelines."
 msgstr ""
-"如果代碼庫還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md#r"
-"epository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述目"
-"前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，"
-"以及機器不容易檢查的其他層面。指引應該包含貢獻的[原始碼](../glossary.md"
-"#source-code)預期該符合哪些要求，才會被維護人員合併至代碼庫中，包括原始碼、測"
-"試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
+"如果程式基底還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md"
+"#repository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述"
+"目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則"
+"，以及機器不容易檢查的其他層面。指引應該包含貢獻的[原始碼](../glossary.md"
+"#source-code)預期該符合哪些要求，才會被維護人員合併至程式基底中，包括原始碼、"
+"測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
 
 #: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
 msgid "Additionally:"
@@ -3957,13 +3976,14 @@ msgstr "使用 linter 程式碼品質梳理工具。"
 
 #: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
 msgid "Add linter configurations to the codebase."
-msgstr "在代碼庫中加入 linter 梳理工具的組態設定。"
+msgstr "在程式基底中加入 linter 梳理工具的組態設定。"
 
 #: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
 msgid ""
 "[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
 "Wikipedia."
-msgstr "維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。"
+msgstr "維基百科上的《[程式碼風格](https://en.wikipedia.org/wiki/"
+"Programming_style)》條目。"
 
 #: ./criteria/use-continuous-integration.md:block 3 (paragraph)
 msgid "order: 12 redirect_from:"
@@ -3985,7 +4005,7 @@ msgid ""
 " conflicts."
 msgstr ""
 "透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同"
-"步協作。合併的頻率越頻繁，貢獻的規模越小，在合併時所發生的衝突就越容易解決。"
+"步協作。合併的頻率越頻繁、貢獻的規模越小，在合併時所發生的衝突就越容易解決。"
 
 #: ./criteria/use-continuous-integration.md:block 7 (paragraph)
 msgid ""
@@ -4005,8 +4025,8 @@ msgid ""
 "contributions. Continuous integration allows for an easier monitoring of the"
 " state of the [codebase](../glossary.md#codebase)."
 msgstr ""
-"以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，"
-"能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監督[代碼庫](../glossary."
+"以文件記錄程式基底的[持續整合](../glossary.md#continuous-integration)工作流程"
+"，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監督[程式基底](../glossary."
 "md#codebase)狀態變得更為簡單。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
@@ -4019,17 +4039,17 @@ msgstr "[原始碼](../glossary.md#source-code)中的所有功能，都「必須
 msgid ""
 "Contributions MUST pass all automated tests before they are admitted into "
 "the codebase."
-msgstr "所有貢獻內容都「必須」先通過自動化測試，才能上傳至代碼庫。"
+msgstr "所有貢獻內容都「必須」先通過自動化測試，才能上傳至程式基底。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have guidelines explaining how to structure contributions."
-msgstr "代碼庫「必須」有解說如何撰寫貢獻內容結構的相關指引。"
+msgstr "程式基底「必須」有解說如何撰寫貢獻內容結構的相關指引。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
 "The codebase MUST have active contributors who can review contributions."
-msgstr "代碼庫「必須」有能夠審查貢獻內容的活躍貢獻者。"
+msgstr "程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Automated test results for contributions SHOULD be public."
@@ -4039,7 +4059,7 @@ msgstr "「應該」公開貢獻內容的自動化測試結果。"
 msgid ""
 "The codebase guidelines SHOULD state that each contribution should focus on "
 "a single issue."
-msgstr "代碼庫指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。"
+msgstr "程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
@@ -4076,7 +4096,7 @@ msgstr "確認原始碼覆蓋率工具能檢查到 100% 的原始碼。"
 msgid ""
 "Confirm that contributions are only admitted into the codebase after all of "
 "the tests are passed."
-msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。"
+msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至程式基底。"
 
 #: ./criteria/use-continuous-integration.md:block 12 (unordered list)
 msgid ""
@@ -4133,7 +4153,7 @@ msgstr "以頻繁整合少量部分內容的方式做專案規劃，而非久久
 msgid ""
 "Procure consultancy services that deliver incrementally aligned with the "
 "plan."
-msgstr "聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。"
+msgstr "聘請有能力處理漸進式交付，並跟得上規劃進度的顧問服務。"
 
 #: ./criteria/use-continuous-integration.md:block 16 (unordered list)
 msgid ""
@@ -4233,9 +4253,9 @@ msgid ""
 "exchange."
 msgstr ""
 "[開放標準](../glossary.md#open-"
-"standard)保證可以取得使用與貢獻[代碼庫](../glossary.md#codebase)所需的知識。"
-"不僅能為不同的系統之間建立互通性，更降低廠商套牢的可能性。開放標準如果明確，"
-"不同方就可以各自獨立開發作資料交換。"
+"standard)保證可以取得使用與貢獻[程式基底](../glossary.md#codebase)所需的知識"
+"。不僅能為不同的系統之間建立互通性，更能降低廠商套牢的可能性。開放標準如果明"
+"確，不同方就可以各自獨立開發作資料交換。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4243,8 +4263,9 @@ msgid ""
 "codebase MUST use an open standard that meets the [Open Source Initiative "
 "Open Standard Requirements](https://opensource.org/osr)."
 msgstr ""
-"代碼庫如要促進資料交換的特性，就「必須」採用符合[OSI "
-"開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標準。"
+"程式基底如要促進資料交換的特性，就「必須」採用符合 [OSI "
+"開放原始碼促進會其《開放標準需求規範](https://opensource.org/"
+"osr)》的開放標準。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4256,14 +4277,14 @@ msgstr "如果有使用到任何非開放標準，則「必須」在文件中清
 msgid ""
 "Any standard chosen for use within the codebase MUST be listed in the "
 "documentation with a link to where it is available."
-msgstr "代碼庫選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標"
-"準的連結。"
+msgstr "程式基底選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該"
+"標準的連結。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
 "Any non-open standards chosen for use within the codebase MUST NOT hinder "
 "collaboration and reuse."
-msgstr "代碼庫選擇採用的任何非開放標準，皆「禁止」妨礙代碼庫的協作與重複使用。"
+msgstr "程式基底選擇採用的任何非開放標準，皆「禁止」妨礙程式基底的協作與重複使用。"
 
 #: ./criteria/use-open-standards.md:block 8 (unordered list)
 msgid ""
@@ -4297,7 +4318,8 @@ msgid ""
 "Confirm that documentation includes a list of the standards followed within "
 "the codebase, each with a working link, or a statement that no standards "
 "were chosen."
-msgstr "確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。"
+msgstr "確認文件有清單列出程式基底所採用的標準，其中各標準有對應的有效連結；或沒有採"
+"用任何標準時，則留下聲明。"
 
 #: ./criteria/use-open-standards.md:block 12 (unordered list)
 msgid "Mandate use of open standards everywhere possible."
@@ -4311,7 +4333,7 @@ msgstr "禁止採購不採用開放標準的技術科技。"
 msgid ""
 "Consider including open standard compliance assessment in [source "
 "code](../glossary.md#source-code) reviews."
-msgstr "考慮在 [原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。"
+msgstr "考慮在[原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。"
 
 #: ./criteria/use-open-standards.md:block 16 (unordered list)
 msgid ""
@@ -4353,7 +4375,7 @@ msgstr "使用白話的英語"
 msgid ""
 "English is the <i>de facto</i> language of collaboration in software "
 "development."
-msgstr "英語是軟體開發領域中的<i>實際</i>協作語言。"
+msgstr "英語是軟體開發領域中的<i>實際</i> 協作語言。"
 
 #: ./criteria/use-plain-english.md:block 7 (paragraph)
 msgid ""
@@ -4368,12 +4390,12 @@ msgid ""
 "Translations further increase the possible reach of a "
 "[codebase](../glossary.md#codebase). Language that is easy to understand "
 "lowers the cost of creating and maintaining translations."
-msgstr "翻譯可以讓更多人有機會認識[代碼庫](../glossary."
+msgstr "翻譯可以讓更多人有機會認識[程式基底](../glossary."
 "md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid "All codebase documentation MUST be in English."
-msgstr "代碼庫的所有文件都「必須」使用英語。"
+msgstr "程式基底的所有文件都「必須」使用英語。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4400,8 +4422,9 @@ msgid ""
 " specific terms in the codebase without an explanation preceding it or a "
 "link to an explanation."
 msgstr ""
-"代碼庫中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；"
-"如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。"
+"程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙"
+"；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結"
+"。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4419,7 +4442,7 @@ msgstr "「可選擇」是否提供任何程式碼、文件、測試等的翻譯
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid "Confirm that codebase documentation is available in English."
-msgstr "確認代碼庫文件有英語版本。"
+msgstr "確認程式基底文件有英語版本。"
 
 #: ./criteria/use-plain-english.md:block 12 (unordered list)
 msgid ""
@@ -4477,7 +4500,7 @@ msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解
 msgid ""
 "Ask someone outside of your context if they understand the content (for "
 "example, a developer working on a different codebase)."
-msgstr "詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。"
+msgstr "詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。"
 
 #: ./criteria/use-plain-english.md:block 20 (unordered list)
 msgid ""
@@ -4528,31 +4551,31 @@ msgid ""
 " communities. Newcomers need to understand and trust the codebase "
 "community’s governance."
 msgstr ""
-"[代碼庫](../glossary.md#codebase)的社群氛圍會影響使用者選擇所要使用的代碼庫。"
-"歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。若貢獻者有明確的"
-"方法可以影響代碼庫、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新"
-"參與者需要瞭解並信任代碼庫社群的治理方式。"
+"[程式基底](../glossary.md#codebase)社群的氛圍，會影響使用者選擇所要使用的程式"
+"基底。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。若貢獻者有"
+"明確的方法可以影響程式基底、社群目標與進展，則該社群分裂成分歧的社群的機率也"
+"較低。新參與者需要瞭解並信任程式基底社群的治理方式。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST allow anyone to submit suggestions for changes to the "
 "codebase."
-msgstr "代碼庫必須「允許」任何人對代碼庫提出修改建議。"
+msgstr "程式基底必須「允許」任何人對程式基底提出修改建議。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST include contribution guidelines explaining what kinds of "
 "contributions are welcome and how contributors can get involved, for example"
 " in a `CONTRIBUTING` file."
-msgstr "代碼庫「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發"
-"，例如以「`CONTRIBUTING`」檔案說明。"
+msgstr "程式基底「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開"
+"發，例如以「`CONTRIBUTING`」檔案說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "The codebase MUST document the governance of the codebase, contributions and"
 " its community, for example in a `GOVERNANCE` file."
-msgstr "代碼庫「必須」以文件記錄代碼庫、貢獻內容與社群互動等的治理方式，例如以「`GOVE"
-"RNANCE`」檔案來說明。"
+msgstr "程式基底「必須」以文件記錄程式基底、貢獻內容與社群互動等的治理方式，例如以「`"
+"GOVERNANCE`」檔案來說明。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
@@ -4564,36 +4587,36 @@ msgstr "貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻
 msgid ""
 "The codebase SHOULD advertise the committed engagement of involved "
 "organizations in the development and maintenance."
-msgstr "代碼庫「應該」宣布投入其開發與維護工作的參與組織單位。"
+msgstr "程式基底「應該」宣布投入其開發與維護工作的參與組織單位。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD have a publicly available roadmap."
-msgstr "代碼庫「應該」要有可公開取得的發展路線圖。"
+msgstr "程式基底「應該」要有可公開取得的發展路線圖。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid "The codebase SHOULD publish codebase activity statistics."
-msgstr "代碼庫「應該」公布代碼庫的活動統計數據。"
+msgstr "程式基底「應該」公布程式基底的活動統計數據。"
 
 #: ./criteria/welcome-contributors.md:block 8 (unordered list)
 msgid ""
 "Including a code of conduct for contributors in the codebase is OPTIONAL."
-msgstr "「可選擇」是否為代碼庫加入貢獻者的行為守則。"
+msgstr "「可選擇」是否為程式基底加入貢獻者的行為守則。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Confirm that it is possible to submit suggestions for changes to the "
 "codebase."
-msgstr "確認可以提交修改建議給代碼庫。"
+msgstr "確認可以提交修改建議給程式基底。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid "Confirm there are contribution guidelines."
-msgstr "確認代碼庫有貢獻指引。"
+msgstr "確認程式基底有貢獻指引。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
 "Confirm that the codebase governance is clearly explained, including how to "
 "influence codebase governance."
-msgstr "確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理的方法。"
+msgstr "確認程式基底有清楚解釋治理架構，並包含如何影響程式基底治理的方法。"
 
 #: ./criteria/welcome-contributors.md:block 10 (unordered list)
 msgid ""
@@ -4623,7 +4646,8 @@ msgid ""
 "[policy](../glossary.md#policy) experts, non-governmental organizations and "
 "academics would find useful for understanding or reusing your policy."
 msgstr ""
-"為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
+"為程式基底加入其他資源的清單，而這些資源可幫助[政策](../glossary."
+"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
 
 #: ./criteria/welcome-contributors.md:block 12 (unordered list)
 msgid ""
@@ -4647,13 +4671,14 @@ msgstr "如果社群對於治理架構應該如何改變有共識，則應該將
 msgid ""
 "If needed, make sure you have allocated budget for the contributions review "
 "process as agreed by the codebase community."
-msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且通過代碼庫社群同意。"
+msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且通過程式基底社群同意。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
 "Make sure the documentation explains how each organization is involved in "
 "the codebase, what resources it has available for it and for how long."
-msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。"
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參"
+"與的時間長度等。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
@@ -4669,7 +4694,7 @@ msgstr "快速回應請求。"
 msgid ""
 "Communicate clearly to contributors what they need to do make sure their "
 "contribution can be integrated."
-msgstr "清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到代碼庫中。"
+msgstr "清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到程式基底中。"
 
 #: ./criteria/welcome-contributors.md:block 18 (unordered list)
 msgid ""
@@ -4694,7 +4719,7 @@ msgid ""
 "governance/) for growing [open source](../glossary.md#open-source) community"
 " projects, by Open Source Guides."
 msgstr ""
-"《開放原始碼指引》針對推動[開放原始碼](../glossary.md#open-"
+"開放原始碼指引針對推動[開放原始碼](../glossary.md#open-"
 "source)社群專案所寫的《[領導與治理](https://opensource.guide/"
 "leadership-and-governance/)》。"
 
@@ -4811,7 +4836,7 @@ msgstr "建立發行用分支"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
-msgstr "從「develop」分支下指令，`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr "從「develop」分支下命令，`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
@@ -5013,8 +5038,8 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
-"代碼庫管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://ab"
-"out.publiccode.net/activities/standard-maintenance/backlog-pruning."
+"程式基底管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://"
+"about.publiccode.net/activities/standard-maintenance/backlog-pruning."
 "html)環節的一部份。"
 
 #: ./docs/roadmap.md:block 6 (header)
@@ -5037,7 +5062,7 @@ msgstr "分離執行摘要"
 msgid ""
 "Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
 " issue #208"
-msgstr "#208號議題：將代碼或規則之「code」清楚區分為「原始碼」或是「政策法規」"
+msgstr "#208號議題：將程式碼或規則之「code」清楚區分為「原始碼」或是「政策法規」"
 
 #: ./docs/roadmap.md:block 9 (unordered list)
 msgid "Possibly: add in the illustrations for each criterion"
@@ -5063,11 +5088,11 @@ msgstr "實體紙張檢查清單"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Becoming validated by multiple codebases"
-msgstr "通過多個代碼庫驗證"
+msgstr "通過多個程式基底驗證"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Release version 1.0.0 after a few codebases are compliant"
-msgstr "在幾個代碼庫遵循標準後，發行 1.0.0 版"
+msgstr "在幾個程式基底遵循標準後，發行 1.0.0 版"
 
 #: ./docs/roadmap.md:block 11 (unordered list)
 msgid "Linkable requirements"
@@ -5238,10 +5263,10 @@ msgid ""
 " Citizens and civil society actors need this software to be transparent and "
 "accountable."
 msgstr ""
-"我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有代碼庫之"
-"下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主"
-"權。技術自主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整"
-"政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。"
+"我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有程式基底"
+"之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自"
+"主權。技術自主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調"
+"整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。"
 
 #: ./foreword.md:block 25 (paragraph)
 msgid ""
@@ -5428,8 +5453,8 @@ msgid ""
 "describe the service or outcome in your contract."
 msgstr ""
 "若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將"
-"會使用該代碼庫。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中"
-"描述說明服務內容或預期成果。"
+"會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約"
+"中描述說明服務內容或預期成果。"
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
@@ -5450,7 +5475,7 @@ msgstr "開發出高品質的軟體與政策，來改善公共服務的交付"
 msgid ""
 "develop codebases that can be reused across contexts and collaboratively "
 "maintained"
-msgstr "開發出能在各種情境下重複使用，且以協作方式維護的代碼庫"
+msgstr "開發出能在各種情境下重複使用，且以協作方式維護的程式基底"
 
 #: ./foreword.md:block 49 (unordered list)
 msgid "reduce technical debt and project failure rate"
@@ -5471,8 +5496,8 @@ msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
 msgstr ""
-"如果有潛在使用者想採用經由《Standard for Public Code》測試過的代碼庫，便可以"
-"預期這些代碼庫具有方便重複利用、容易維護、高品質的特性。"
+"如果有潛在使用者想採用經由《Standard for Public Code》測試過的程式基底，便可"
+"以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
@@ -5617,18 +5642,18 @@ msgstr ""
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
-msgstr "代碼庫"
+msgstr "程式基底"
 
 #: ./glossary.md:block 7 (paragraph)
 msgid ""
 "Any discrete package of code (both source and policy), the tests and the "
 "documentation required to implement a piece of policy or software."
-msgstr "執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件的"
-"整套統合包。"
+msgstr "執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件等"
+"的整套內容統合包。"
 
 #: ./glossary.md:block 8 (paragraph)
 msgid "This can be, for example, a document or a version-control repository."
-msgstr "例如，這可以是文件，或是版本控制的儲存庫。"
+msgstr "舉例來說，這可以是用文件，或是版本控制的儲存庫來存放。"
 
 #: ./glossary.md:block 9 (header)
 msgid "Continuous integration"
@@ -5639,8 +5664,8 @@ msgid ""
 "In software engineering, continuous integration (CI) is the practice of "
 "merging all developers' working copies to a development branch of a codebase"
 " as frequently as reasonable."
-msgstr "在軟體工程中，持續整合 (CI) "
-"是盡可能頻繁地將所有開發人員工作中的副本，合併回代碼庫開發中分支的實務作法。"
+msgstr "在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回"
+"程式基底開發中分支的實務作法。"
 
 #: ./glossary.md:block 11 (header)
 msgid "Different contexts"
@@ -5732,7 +5757,7 @@ msgstr "在本標準當中，「政策」一詞指的是公家機關，例如政
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
-msgstr "公共程式"
+msgstr "公共程式 (Public code)"
 
 #: ./glossary.md:block 26 (paragraph)
 msgid ""
@@ -5795,8 +5820,8 @@ msgid ""
 " on the same set of files. Repositories are able to store multiple versions "
 "of sets of files."
 msgstr ""
-"儲存庫是版本控制工具，用於存放檔案與代碼庫中介資料的儲存位置。儲存庫允許多位"
-"貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。"
+"儲存庫是版本控制工具，用於存放檔案與程式基底中介資料的儲存位置。儲存庫允許多"
+"位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。"
 
 #: ./glossary.md:block 34 (header)
 msgid "Source Code"
@@ -5823,9 +5848,9 @@ msgid ""
 "time."
 msgstr ""
 "版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱"
-"為「*修訂編號*」（或「版次」等類似名稱）的代號作識別。每次修訂都會標示其改動"
-"時間以及作者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異"
-"，以及查看內容隨著時間的變動。"
+"為「*修訂編號*」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間"
+"以及作者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以"
+"及查看內容隨著時間的變動。"
 
 #: ./index.md:block 3 (header)
 msgid "toc: false"
@@ -5857,8 +5882,8 @@ msgstr ""
 "以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果"
 "。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《"
 "Standard for Public Code》支持公家機關透過協作方式，創造出好用、開放、易懂、"
-"課責、近用、永續的代碼庫。這份標準從設計之初，就是要用於各種不同政府層級的代"
-"碼庫，小從市政府，大到超國家組織都行。"
+"課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的"
+"程式基底，小從市政府，大到超國家組織都行。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5951,8 +5976,8 @@ msgid ""
 msgstr ""
 "我們通常在每月第一個週四的 15:00 (CET/CEST) "
 "舉辦社群會議。[議程](https://write.publiccode.net/pads/Community-Call-"
-"Standard-for-Public-Code) 在會議前約一週的時間更新。您可以[註冊](https://odoo"
-".publiccode.net/survey/start/"
+"Standard-for-Public-Code)在會議前約一週的時間更新。您可以[註冊](https://odoo."
+"publiccode.net/survey/start/"
 "594b9243-c7e5-4bc1-8714-35137c971842)報名，會再寄送會議通話邀請函給您。"
 
 #: ./index.md:block 14 (header)
@@ -5974,8 +5999,8 @@ msgid ""
 "assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
 "public sector open source codebases"
 msgstr ""
-"公部門開源代碼庫的〈[標準遵循自我評估](https://publiccodenet.github.io/"
-"assessment-eligibility/)〉"
+"公部門開源程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/"
+"assessment-eligibility/)》"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""
@@ -5985,8 +6010,8 @@ msgid ""
 "review"
 msgstr ""
 "Foundation for Public Code "
-"管事人員審查代碼庫時所使用的〈[本標準準則檢查清單](https://github.com/"
-"publiccodenet/standard/blob/develop/docs/review-template.html)〉"
+"管事人員審查程式基底時所使用的《[本標準準則檢查清單](https://github.com/"
+"publiccodenet/standard/blob/develop/docs/review-template.html)》"
 
 #: ./readers-guide.md:block 3 (header)
 msgid "Readers guide"
@@ -6022,8 +6047,8 @@ msgstr "前言"
 msgid ""
 "This section explains what the criterion aims to achieve and why it is "
 "important for a codebase's users and contributors."
-msgstr "本小節說明這些準則想達成的目的，以及為何會對代碼庫使用者與貢獻者來說這麼重要"
-"的原因。"
+msgstr "本小節說明這些準則想達成的目的，以及為何會對程式基底使用者與貢獻者來說這麼重"
+"要的原因。"
 
 #: ./readers-guide.md:block 10 (paragraph)
 msgid ""
@@ -6147,8 +6172,8 @@ msgid ""
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
 msgstr ""
-"《Standard for Public Code》不是為了涵蓋代碼庫的個別實作而撰寫。這代表本標準"
-"不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
+"《Standard for Public Code》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標"
+"準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6172,8 +6197,8 @@ msgid ""
 "proactiveness and ambition beyond making the codebase collaboration ready."
 msgstr ""
 "《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群"
-"。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要積極主動，以及做到超"
-"越協作以外的企圖心。"
+"。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到"
+"超越協作以外的企圖心。"
 
 msgid ""
 "script/release-body.sh expects VERSION in the first second-level header"
@@ -6193,7 +6218,7 @@ msgstr "2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式
 msgid ""
 "The criterion \"Make the codebase reusable and portable\" was renamed from "
 "\"Create reusable and portable code\"."
-msgstr "〈程式碼要可重複使用且可攜〉準則改名為〈代碼庫要可重複使用且可移植〉。"
+msgstr "〈程式碼要可重複使用且可攜〉準則改名為〈程式基底要可重複使用且可移植〉。"
 
 msgid "Added a glossary entry for \"Source Code\"."
 msgstr "新增詞彙條目「原始碼」。"
@@ -6207,7 +6232,7 @@ msgid "Clarification of \"running code\" as \"software\"."
 msgstr "將「運作的程式碼」釐清稱為「軟體」。"
 
 msgid "Minor changes to clarify \"code\" vs \"codebase\"."
-msgstr "細微修改以清楚區分「程式碼」與「代碼庫」。"
+msgstr "細微修改以清楚區分「程式碼」與「程式基底」。"
 
 msgid "Simplify guidance to policy makers in Bundle policy and source code."
 msgstr "簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。"
@@ -6215,7 +6240,8 @@ msgstr "簡化給政策制定者在〈政策與原始碼要合捆〉中的指引
 msgid ""
 "Clarify How to test sections of Make the codebase findable and Make the "
 "codebase reusable and portable."
-msgstr "釐清〈代碼庫可查詢得到〉與〈代碼庫要可重複使用且可移植〉的「測試方式」小節。"
+msgstr "釐清〈程式基底可查詢得到〉與〈程式基底要可重複使用且可移植〉的「測試方式」小"
+"節。"
 
 msgid "Add a criteria and requirements checklist to the release artifacts."
 msgstr "在發行成品前的要求中，加入準則與需求規定檢查清單。"
@@ -6246,12 +6272,12 @@ msgid ""
 "eligibility) that will give you a rough idea of how much work you may need "
 "to do to meet all criteria."
 msgstr ""
-"若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是"
-"人人都能自由採用的開放標準。如果您希望宣傳代碼庫社群達成《Standard for "
+"若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它"
+"是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成《Standard for "
 "Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment "
 "徽章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要"
-"瞭解您代碼庫所達成的程度，可以做[自我資格評估](https://publiccodenet.github."
-"io/assessment-"
+"瞭解您程式基底所達成的程度，可以做[自我資格評估](https://publiccodenet.github"
+".io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 msgid "Update [`roadmap.md`](roadmap.md)"
@@ -6283,5 +6309,5 @@ msgid ""
 "[Standard criteria checklist](/docs/review-template.html) used by Foundation"
 " for Public Code stewards for codebase review"
 msgstr ""
-"Foundation for Public Code 管事人員用於代碼庫審查的〈[標準準則檢查清單](/"
+"Foundation for Public Code 管事人員用於程式基底審查的〈[標準準則檢查清單](/"
 "docs/review-template.html)〉"

From c1d8d7e312da1bb24693bbd27036815243d2d20a Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Sat, 16 Sep 2023 03:28:52 +0000
Subject: [PATCH 54/71] update translate

---
 CHANGELOG.md                                  | 32 ++++-----
 CONTRIBUTING.md                               | 10 +--
 GOVERNANCE.md                                 |  4 +-
 README.md                                     | 26 ++++----
 criteria/bundle-policy-and-source-code.md     | 16 ++---
 criteria/code-in-the-open.md                  |  6 +-
 criteria/document-codebase-maturity.md        | 36 +++++-----
 criteria/document-codebase-objectives.md      | 25 +++----
 criteria/document-the-code.md                 | 26 ++++----
 criteria/maintain-version-control.md          | 32 ++++-----
 criteria/make-contributing-easy.md            | 20 +++---
 criteria/make-the-codebase-findable.md        | 66 +++++++++----------
 ...make-the-codebase-reusable-and-portable.md | 46 ++++++-------
 criteria/publish-with-an-open-license.md      | 30 ++++-----
 criteria/require-review-of-contributions.md   | 22 +++----
 criteria/use-a-coherent-style.md              | 16 ++---
 criteria/use-continuous-integration.md        | 18 ++---
 criteria/use-open-standards.md                | 16 ++---
 criteria/use-plain-english.md                 | 12 ++--
 criteria/welcome-contributors.md              | 34 +++++-----
 docs/releasing.md                             |  2 +-
 docs/roadmap.md                               |  6 +-
 foreword.md                                   | 12 ++--
 glossary.md                                   | 18 ++---
 index.md                                      | 15 +++--
 readers-guide.md                              |  8 +--
 26 files changed, 278 insertions(+), 276 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 21bcdd82..b12cef83 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,13 +10,13 @@
 
 2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。
 
-* 〈程式碼要可重複使用且可攜〉準則改名為〈代碼庫要可重複使用且可移植〉。
+* 〈程式碼要可重複使用且可攜〉準則改名為〈程式基底要可重複使用且可移植〉。
 * 新增詞彙條目「原始碼」。
 * 對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。
 * 將「運作的程式碼」釐清稱為「軟體」。
-* 細微修改以清楚區分「程式碼」與「代碼庫」。
+* 細微修改以清楚區分「程式碼」與「程式基底」。
 * 簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。
-* 釐清〈代碼庫可查詢得到〉與〈代碼庫要可重複使用且可移植〉的「測試方式」小節。
+* 釐清〈程式基底可查詢得到〉與〈程式基底要可重複使用且可移植〉的「測試方式」小節。
 * 在發行成品前的要求中，加入準則與需求規定檢查清單。
 * 提升發行流程的自動化程度。
 
@@ -25,9 +25,9 @@
 2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。
 
 * 新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。
-* 新增規定，代碼庫必須要有簡短說明。
+* 新增規定，程式基底必須要有簡短說明。
 * 原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。
-* 將〈代碼庫可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。
+* 將〈程式基底可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。
 * 審查範本現在有 HTML 格式。
 * 「前言」轉換為「序文」。
 * 改善貢獻指引。
@@ -41,7 +41,7 @@
 * 新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。
 * 新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。
 * 對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。
-* 重新撰寫規定，將焦點放在代碼庫，而非貢獻者行為。
+* 重新撰寫規定，將焦點放在程式基底，而非貢獻者行為。
 * 移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加入前言。
 * 在本標準前言中，加入通用的「此措施辦不到的事」小節。
 * 為政策制定者加入相關政策與授權相容性的指引。
@@ -62,8 +62,8 @@
 
 2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。
 
-* 調整程式碼撰寫風格要求，專注於代碼庫上，而非貢獻者行為。
-* 將代碼庫名稱規定，從〈使用白話的英文〉移動到〈代碼庫可查詢得到〉。
+* 調整程式碼撰寫風格要求，專注於程式基底上，而非貢獻者行為。
+* 將程式基底名稱規定，從〈使用白話的英文〉移到〈程式基底可查詢得到〉。
 * 將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。
 * 劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。
 * 調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。
@@ -73,8 +73,8 @@
 
 2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。
 
-* 寫下成熟度著重於代碼庫是否已經可供使用，更甚於版本編號。
-* 寫下成熟度不再需要為尚未準備好可供使用的代碼庫加上特定標籤。
+* 寫下成熟度著重於程式基底是否已經可供使用，更甚於版本編號。
+* 寫下成熟度不再需要為尚未準備好可供使用的程式基底加上特定標籤。
 * 稽核流程圖現在以更容易轉譯的格式生成。
 * 改善「測試方式」指引。
 * 新增 publiccode.yml 檔案。
@@ -92,7 +92,7 @@
 
 2022年9月7日：🔭第十一版草稿新增可查找性準則。
 
-* 導入新準則：代碼庫可查詢得到。
+* 導入新準則：程式基底可查詢得到。
 * 改善多數準則的「測試方式」小節。
 * 在〈歡迎貢獻者〉中加入發布活動統計的新規定。
 * 移除可重複使用與移植的程式碼中多餘的規定。
@@ -103,9 +103,9 @@
 * 導入新的行為守則。
 * 解釋原始碼與政策內文的差異。
 * 將規定重新調整為項目要點清單格式。
-* 告知代碼庫成熟度對於重複使用時的重要性。
+* 告知程式基底成熟度對於重複使用時的重要性。
 * 將可查找性相關規定移動到新準則中。
-* 釐清非開放標準在代碼庫中的角色。
+* 釐清非開放標準在程式基底中的角色。
 * 加入建置時期與執行時期依賴項目的額外指引。
 * 新增《Standard for Public Code》的發展路線圖。
 * 更新 Authors 檔案的結構。
@@ -160,7 +160,7 @@
 * 將「白話語言定義」加入延伸閱讀。
 * 將「語意化版本編號規範」移動為延伸閱讀參考內容。
 * 指出 publiccode.yml 是機器可讀中介資料說明的範例之一。
-* 將「您的代碼庫」與「您的組織單位」改為較不具有所有格的寫法。
+* 將「您的程式基底」與「您的組織單位」改為較不具有所有格的寫法。
 * 再稍微修改些文字，讓文字更明確。
 * 新增印刷版的製作指示。
 
@@ -186,8 +186,8 @@
 2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。
 
 * 將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。
-* 將〈注意代碼庫成熟度〉準則改名為〈記錄代碼庫成熟度〉。
-* 針對多方使用的代碼庫，將「必須」等級規定調降為「應該」。
+* 將〈注意程式基底成熟度〉準則改名為〈記錄程式基底成熟度〉。
+* 針對多方使用的程式基底，將「必須」等級規定調降為「應該」。
 * 針對著作權轉讓，新增「禁止」規定。
 * 在可重複使用程式碼的規定中，釐清組態設定的角色。
 * 新增詞彙：持續整合、政策、儲存庫、版本控制等。
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9e6f82cb..2c273a09 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -13,9 +13,9 @@
 
 ## 問題、建議與議題等
 
-[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 [Standard for
-Public Code 的 GitHub Issue](https://github.com/publiccodenet/standard/issues) 頁面
-中，為本專案[提出 GitHub 議
+在[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 [Standard
+for Public Code 的 GitHub
+Issue](https://github.com/publiccodenet/standard/issues) 頁面中，為本專案[提出 GitHub 議
 題](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue)。
 
 或者，註冊加入[郵遞論壇列
@@ -26,7 +26,7 @@ Public Code 的 GitHub Issue](https://github.com/publiccodenet/standard/issues)
 
 ## 為文件與程式碼提出拉取請求
 
-如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求。
+如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull Request，亦可簡稱 PR)。
 
 若您從未使用過 GitHub，歡迎先[認識 GitHub 作業流
 程](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加 [GitHub
@@ -47,7 +47,7 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 將您所作的變更內容加入送交版次，[並附上內容說
 明](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)。如果需要作
-出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如，修正空白，以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
+出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
 容易以「`diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉
 擇。
 
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 98c7a43d..b7454b44 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -5,8 +5,8 @@
 
 # 治理
 
-本標準是 [Foundation for Public Code](https://publiccode.net/) 在代碼庫盡職管理領域作監督時的核心。我們依照這
-份文件來判斷，某個代碼庫是否已經準備好讓社群共同參與開發。
+本標準是 [Foundation for Public Code](https://publiccode.net/) 在程式基底盡職管理作監督時的核心。我們依照這份
+文件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。
 
 這份標準由 Foundation for Public Code 職員負責維護。
 
diff --git a/README.md b/README.md
index 9c8b7849..46343166 100644
--- a/README.md
+++ b/README.md
@@ -19,25 +19,25 @@ badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.p
 [![standard develop
 badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
 
-《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個代碼庫中作測試。
+《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。
 
-## 將《Standard for Public Code》套用您的代碼庫
+## 將《Standard for Public Code》套用您的程式基底
 
-若您想要將《Standard for Public Code》套用您的代碼庫，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳代碼庫社群達成
+若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成
 《Standard for Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment 徽
-章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您代碼庫所達成的程度，可以做[自我
-資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有準
-則，還需要下多少功夫。
+章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度，可以做[自
+我資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有
+準則，還需要下多少功夫。
 
-本標準 *應該* 足以自我解釋要如何套用到您的代碼庫中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要一
-點靈感啟發，請參閱[社群製作的《實踐指
+本標準 *應該* 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要
+一點靈感啟發，請參閱[社群製作的《實踐指
 引》](https://publiccodenet.github.io/community-implementation-guide-standard/)，其中包
 括範例與其他提示。
 
-若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的代碼庫管事
-人員，會協助標準的實踐者理解該如何銜接之間的落差。
+若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的程式基底管
+事人員，會協助標準的實踐者理解該如何銜接之間的落差。
 
-若您致力讓您的代碼庫完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
+若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
 [info@publiccode.net](mailto:info@publiccode.net)，以展開正式[評
 估](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment)。
 
@@ -45,7 +45,7 @@ badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.p
 
 我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政策文件。
 
-本標準為代碼庫設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及其他重大基礎設施服務的需求。
+本標準為程式基底設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及其他重大基礎設施服務的需求。
 
 本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。請參閱
 [`index.md`](index.md) 查看整體內容概覽。
@@ -111,4 +111,4 @@ script/pdf.sh
 © [作者與貢獻者](AUTHORS.md)
 
 本標準採用 CC0 公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
-這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱[貢獻指引](CONTRIBUTING.md)。
+這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱《[貢獻指引](CONTRIBUTING.md)》。
diff --git a/criteria/bundle-policy-and-source-code.md b/criteria/bundle-policy-and-source-code.md
index 6569e102..ce98486b 100644
--- a/criteria/bundle-policy-and-source-code.md
+++ b/criteria/bundle-policy-and-source-code.md
@@ -8,17 +8,17 @@ redirect_from:
 
 # 政策與原始碼要合捆
 
-對於想根據所在情境實作代碼庫的人，或是想更進一步貢獻[代碼庫](../glossary.md#codebase)開發的人來說，能同時取用[原始
+對於想根據所在情境實作程式基底的人，或是想更進一步貢獻[程式基底](../glossary.md#codebase)開發的人來說，能同時取用[原始
 碼](../glossary.md#source-code)與[政策](../glossary.md#policy)文件兩者，可作為建置成品時的基礎組件。
 
-瞭解作用範疇與該範疇的政策是基本原則，才能瞭解代碼庫試圖想解決的問題是什麼，以及該如何解決這些問題的作法。
+瞭解作用範疇與該範疇的政策是基本原則，才能瞭解程式基底試圖想解決的問題是什麼，以及該如何解決這些問題的作法。
 
-為了評估是否需要在新的情境中實作代碼庫，組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。
+為了評估是否需要在新的情境中實作程式基底，組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。
 
 ## 需求規定
 
-* 代碼庫「必須」包含原始碼所根據的政策。
-* 如果政策根據原始碼而來，則該原始碼「必須」包含在代碼庫中，用於偵測詐騙的原始碼則可除外。
+* 程式基底「必須」包含原始碼所根據的政策。
+* 如果政策根據原始碼而來，則該原始碼「必須」包含在程式基底中，用於偵測詐騙的原始碼則可除外。
 * 政策「應該」採用機器可讀且明確的格式。
 * [持續整合](../glossary.md#continuous-integration)測試「應該」驗證原始碼與政策是否有一致執行。
 
@@ -33,12 +33,12 @@ redirect_from:
 
 * 與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。
 * 提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單
-位所選擇遵守的各項標準，以及影響貴組織單位代碼庫開發或部署情境的任何組織單位流程。
+位所選擇遵守的各項標準，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。
 * 請提供政策相關參考資料與連結。
 * 政策內容請使用明確且機器可讀的格式，像是[物件管理群體](https://www.omg.org/spec/)所發表的格式。
 * 追蹤政策時，請使用與追蹤原始碼[相同的版本控制系統](maintain-version-control.md)與文件。
-* 定期檢查，瞭解代碼庫中的原始碼如何變動，以及是否仍然符合[政策意圖](document-codebase-objectives.md)。
-* 納入會影響社會群體、代碼庫與開發目標的相關政策，包含 [GDPR 一般資料保護規
+* 定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合[政策意圖](document-codebase-objectives.md)。
+* 納入會影響社會群體、程式基底與開發目標的相關政策，包含 [GDPR 一般資料保護規
 則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟網頁無障礙命
 令](https://ec.europa.eu/digital-single-market/en/web-accessibility)等此類法律義務，或者是人權政
 策，例如公家機關對機會平等的承諾等。
diff --git a/criteria/code-in-the-open.md b/criteria/code-in-the-open.md
index bac381e3..86f48c44 100644
--- a/criteria/code-in-the-open.md
+++ b/criteria/code-in-the-open.md
@@ -7,13 +7,13 @@ order: 1
 
 以開放精神編寫原始碼，能改善資訊透明、提高[原始碼](../glossary.md#source-code)品質、讓原始碼更容易稽核，也能促進互相協作。
 
-這些加在一起，讓公民更有機會瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公家機關的互動。
+這些合在一起，讓公民更有機會瞭解軟體與[政策](../glossary.md#policy)如何影響他們與公家機關的互動。
 
 ## 需求規定
 
 * 任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
 * 任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。
-* 代碼庫「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。
+* 程式基底「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。
 * 目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。
 * 「可選擇」是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或
 支持的政策。
@@ -21,7 +21,7 @@ order: 1
 ## 測試方式
 
 * 確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。
-* 確認[代碼庫](../glossary.md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。
+* 確認[程式基底](../glossary.md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。
 * 檢查目前非使用中的原始碼是否有公開。
 
 ## 公共政策制定者：需要的工作
diff --git a/criteria/document-codebase-maturity.md b/criteria/document-codebase-maturity.md
index 47a84058..c1f04d75 100644
--- a/criteria/document-codebase-maturity.md
+++ b/criteria/document-codebase-maturity.md
@@ -6,45 +6,45 @@ redirect_from:
     - criteria/advertise-maturity
     - criteria/document-maturity
 ---
-# 記錄代碼庫成熟度
+# 記錄程式基底成熟度
 
-清楚標示[代碼庫](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用，或為該代碼庫做出貢獻。代碼庫版本的成熟度，包含其依賴項目的成
-熟度。瞭解代碼庫演進到什麼程度，是理解該代碼庫並知道如何做出貢獻的關鍵。
+清楚標示[程式基底](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用，或為該程式基底做出貢獻。程式基底版本的成熟度，包含其依賴項
+目的成熟度。瞭解程式基底演進到什麼程度，是理解該程式基底並知道如何做出貢獻的關鍵。
 
 ## 需求規定
 
-* 代碼庫「必須」註明版本編號。
-* 代碼庫「必須」明確以文件記錄，是否有已經準備好可供使用的版本。
-* 準備好可供使用的代碼庫版本，「必須」只能依賴其他也已經準備好可供使用的代碼庫版本。
-* 代碼庫「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
+* 程式基底「必須」註明版本編號。
+* 程式基底「必須」明確以文件記錄，是否有已經準備好可供使用的版本。
+* 準備好可供使用的程式基底版本，「必須」只能依賴其他也已經準備好可供使用的程式基底版本。
+* 程式基底「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。
 * 「應該」要以文件記錄分配版本識別碼的方法。
-* 「可選擇」是否使用語意化版本控制編號。
+* 「可選擇」是否採用語意化版本控制編號。
 
 ## 測試方式
 
-* 確認代碼庫有版本編號策略，且有文件記載該策略。
-* 確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道代碼庫是否有準備好可供使用的版本。
-* 確認準備好可供使用的代碼庫版本，並不依賴任何尚未準備好可供使用的其他代碼庫的版本。
-* 確認有文件記錄代碼庫的版本編號方法，並且確實遵守。
+* 確認程式基底有版本編號策略，且有文件記載該策略。
+* 確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道程式基底是否有準備好可供使用的版本。
+* 確認準備好可供使用的程式基底版本，並不依賴任何尚未準備好可供使用的其他程式基底的版本。
+* 確認有文件記錄程式基底的版本編號方法，並且確實遵守。
 * 確認是否有版本的變動紀錄。
 
 ## 公共政策制定者：需要的工作
 
-* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的 [原始碼](../glossary.md#source-code) 都必須先
-經過測試與改善，才能夠投入服務。
-* 考慮將政策的變動註明版本編號，尤其是因而觸發開發新版本原始碼的情況。
+* 制定[政策](../glossary.md#policy)時，請記住任何開發出來的[原始碼](../glossary.md#source-code)都必須先經過
+測試與改善，才能夠投入服務。
+* 考慮將政策的變動註明版本編號，尤其是因而觸發新版本原始碼開發的情況。
 
 ## 管理人員：需要的工作
 
-* 要確認服務依賴的代碼庫版本成熟度，等同或高於該服務本身。舉例來說，正式上線的服務不要使用 beta 公測版代碼庫。
+* 要確認服務依賴的程式基底版本成熟度，等同或高於該服務本身。舉例來說，正式上線的服務不要使用 beta 公測版程式基底。
 
 ## 開發人員與設計師：需要的工作
 
-* 確認所有發行版，都有遵守代碼庫的版本控制編號作法。
+* 確認所有發行版，都有遵守程式基底的版本控制編號作法。
 
 ## 延伸閱讀
 
-* 許多代碼庫使用「[語意化版本編號規範](https://semver.org/)」來標示版本。
+* 許多程式基底使用「[語意化版本編號規範](https://semver.org/)」來標示版本。
 * [軟體發行生命週期](https://en.wikipedia.org/wiki/Software_release_life_cycle)
 * 澳洲數位轉型局《[服務設計與交付流
 程](https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process)》。
diff --git a/criteria/document-codebase-objectives.md b/criteria/document-codebase-objectives.md
index c52cd031..c1d0aca0 100644
--- a/criteria/document-codebase-objectives.md
+++ b/criteria/document-codebase-objectives.md
@@ -6,34 +6,35 @@ redirect_from:
   - criteria/document-objectives
 ---
 
-# 代碼庫要有目標文件
+# 程式基底要有目標文件
 
-以文件清楚記錄[代碼庫](../glossary.md#codebase)目標，來傳達代碼庫的用途目標。這能幫助利害關係人與貢獻者劃定代碼庫的開發範圍。這些目標也能
-方便人們判斷，是否在當下或未來，會對此代碼庫或其模組感興趣。
+以文件清楚記錄[程式基底](../glossary.md#codebase)目標，來傳達程式基底的用途目標。這能幫助利害關係人與貢獻者劃定程式基底的開發範圍。這些目
+標也能方便人們判斷，是否在當下或未來，會對此程式基底或其模組感興趣。
 
 ## 需求規定
 
-* 代碼庫「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用代碼庫或協助貢獻。
-* 代碼庫文件「應該」清楚描述[政策](../glossary.md#policy)目標與代碼庫目標之前的關聯。
-* 「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-public)看的代碼庫目標。
+* 程式基底「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用程式基底或協助貢獻。
+* 程式基底文件「應該」清楚描述[政策](../glossary.md#policy)目標與程式基底目標之間的關聯。
+* 「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-public)看的程式基底目標。
 
 ## 測試方式
 
-* 確認代碼庫文件有包含代碼庫目標，或主旨、使命等。
-* 查看政策目標與代碼庫目標之間關聯的描述。
+* 確認程式基底文件有包含程式基底目標，或主旨、使命等。
+* 查看政策目標與程式基底目標之間關聯的描述。
 
 ## 公共政策制定者：需要的工作
 
-* 將政策目標加入代碼庫文件中，例如「`README`」文件當中。
-* 確保所有代碼庫目標，有連結或引用為了符合[政策與原始碼要合捆](bundle-policy-and-source-code.md)準則而加入的支持政策文件。
+* 將政策目標加入程式基底文件中，例如「`README`」文件當中。
+* 確保所有程式基底目標，有連結或引用為了符合〈[政策與原始碼要合捆](bundle-policy-and-source-code.md)〉準則而加入的支持政策文
+件。
 
 ## 管理人員：需要的工作
 
-* 將單位目標、組織目標或業務目標加入代碼庫文件中，例如「`README`」文件當中。
+* 將單位目標、組織目標或業務目標加入程式基底文件中，例如「`README`」文件當中。
 
 ## 開發人員與設計師：需要的工作
 
-* 將技術與設計目標加入代碼庫文件中，例如「`README`」文件當中。
+* 將技術與設計目標加入程式基底文件中，例如「`README`」文件當中。
 
 ## 延伸閱讀
 
diff --git a/criteria/document-the-code.md b/criteria/document-the-code.md
index d68052ad..37c0cc2b 100644
--- a/criteria/document-the-code.md
+++ b/criteria/document-the-code.md
@@ -8,20 +8,20 @@ redirect_from:
 
 # 程式碼要有文件
 
-文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作用與使用方式。文件紀錄是幫助人們快速上手[代碼
-庫](../glossary.md#codebase)的使用並做出貢獻的關鍵。
+文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作用與使用方式。文件紀錄是幫助人們快速上手如何使用[程式基
+底](../glossary.md#codebase)，並做出貢獻的關鍵。
 
 ## 需求規定
 
-* 代碼庫的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚瞭解的用語描述，讓懂代碼庫目的用途的人也能夠理解。
-* 代碼庫文件「必須」說明如何安裝與執行軟體。
-* 代碼庫文件「必須」為關鍵功能舉出範例。
-* 代碼庫文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
-* 代碼庫文件「應該」有一部分用來說明，如何安裝與執行單機版的原始碼；如果有必要，也應該包含測試資料集。
-* 代碼庫文件「應該」包含所有功能的範例。
-* 程式碼文件「應該」描述代碼庫的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
+* 程式基底的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚瞭解的用語描述，讓懂程式基底目的用途的人也能夠理解。
+* 程式基底文件「必須」說明如何安裝與執行軟體。
+* 程式基底文件「必須」為關鍵功能舉出範例。
+* 程式基底文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-public)和記者等廣泛的利害關係人都能清楚明白。
+* 程式基底文件「應該」有一部分用來說明，如何安裝與執行原始碼的單機版；如果有必要，也應該包含測試資料集。
+* 程式基底文件「應該」包含所有功能的範例。
+* 程式碼文件「應該」描述程式基底的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。
 * 「應該」要有針對文件品質的[持續整合](../glossary.md#continuous-integration)測試。
-* 「可選擇」是否在代碼庫文件中，包含讓使用者想要立即使用代碼庫的範例。
+* 「可選擇」是否在程式基底文件中，包含讓使用者想要立即使用程式基底的範例。
 
 ## 測試方式
 
@@ -36,17 +36,17 @@ redirect_from:
 
 ## 公共政策制定者：需要的工作
 
-* 定期查看代碼庫中非政策程式碼的變動情況。
+* 定期查看程式基底中非政策程式碼的變動情況。
 * 針對如何讓非政策文件更清楚易懂提供意見回饋。
 
 ## 管理人員：需要的工作
 
-* 嘗試使用代碼庫，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，目前的文件是否足以說服另一個公家機關的管理人員使用這個代碼庫？
+* 嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這個程式基底？
 * 確保您同時瞭解政策、原始碼以及文件內容。
 
 ## 開發人員與設計師：需要的工作
 
-* 定期查看代碼庫中非原始碼部分的變動情況。
+* 定期查看程式基底中非原始碼部分的變動情況。
 * 針對如何讓非原始碼文件更清楚易懂提供意見回饋。
 
 ## 延伸閱讀
diff --git a/criteria/maintain-version-control.md b/criteria/maintain-version-control.md
index 741e4cf9..5e89f08f 100644
--- a/criteria/maintain-version-control.md
+++ b/criteria/maintain-version-control.md
@@ -8,48 +8,48 @@ redirect_from:
 
 # 維護版本控制
 
-[版本控制](../glossary.md#version-control)代表追蹤[原始碼](../glossary.md#source-code)以及其他[代碼
-庫](../glossary.md#codebase)檔案歷來的變動。這能讓您為代碼庫維護有條理的變動歷史文件。這是大規模協作能運作的要素，使開發人員得以針對修改
-變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。
+[版本控制](../glossary.md#version-control)主要在追蹤[原始碼](../glossary.md#source-code)以及其他[程
+式基底](../glossary.md#codebase)檔案歷來的變動。這能讓您為程式基底維護有條理的變動歷史文件。這是大規模協作得以運作的要素，使開發人員可以
+針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。
 
 ## 需求規定
 
-* 代碼庫中的所有檔案皆「必須」有版本控制。
+* 程式基底中的所有檔案皆「必須」有版本控制。
 * 所有決定皆「必須」記錄成送交版次訊息。
 * 每份送交版次訊息皆「必須」盡可能附上討論與議題連結。
-* 代碼庫「應該」以分散式版本控制系統作維護。
+* 程式基底「應該」以分散式版本控制系統作維護。
 * 貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。
-* 維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示代碼庫正式發行的版本。
+* 維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版本。
 * 貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。
 * 貢獻者「可選擇」是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
 
 ## 測試方式
 
-* 確認代碼庫維持在版本控制狀態中，像是使用 Git 之類的軟體。
+* 確認程式基底維持在版本控制狀態中，像是使用 Git 之類的軟體。
 * 審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。
 * 審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。
 * 檢查版本控制系統是否為分散式。
 * 審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。
-* 檢查是否可能透過像是修訂版次標記，或文字標籤，來存取代碼庫中的特定版本。
-* 檢查代碼庫在可能的情況下，檔案都是採用文字格式。
+* 檢查是否可能透過像是修訂版次標記，或文字標籤，來取用程式基底中的特定版本。
+* 檢查程式基底在盡可能的情況下，檔案都是採用文字格式。
 
 ## 公共政策制定者：需要的工作
 
-* 如果因為[政策](../glossary.md#policy)改變而在代碼庫中有新的版本，則請確認有在文件中清楚說明：
+* 如果因為[政策](../glossary.md#policy)改變而在程式基底中有新的版本，則請確認有在文件中清楚說明：
    * 政策改變的地方，
-   * 代碼庫如何因應而改變。
+   * 程式基底如何因應而改變。
 
-舉例來說，在做權限管理賦予取用權的代碼庫中，如果要新增申請方類別，就會視為政策變動。
+舉例來說，為程式基底作權限管理時，如果要新增申請方類別來賦予取用權，應視為一種政策變動。
 
 ## 管理人員：需要的工作
 
-* 支持政策制定者、開發人員與設計師，使其能清楚表達他們對代碼庫做出的改善。確保改善代碼庫不會有公關風險。
+* 支持政策制定者、開發人員與設計師，使其能清楚表達他們對程式基底做出的改善。確保改善程式基底不會有公關風險。
 
 ## 開發人員與設計師：需要的工作
 
-* 確認版本控制系統中，有瞭解程式碼、建置與部署所需的所有檔案。
+* 確認版本控制系統中，有瞭解程式碼、建置與部署所需要用到的所有檔案。
 * 送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。
-* 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便存取特定版本。
+* 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。
 * 送交版次訊息要寫清楚，方便之後比較各版本。
 * 在政策改變以後與政策制定者合作，說明原始碼更新的內容。
 
@@ -61,5 +61,5 @@ redirect_from:
 制](https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding)》。
 * GitHub 提供的「[GitHub 技能](https://skills.github.com/)」，可學習如何使用 GitHub，或是重溫您的技巧。
 * GitHub 提供的「[Git 密技
-表](https://education.github.com/git-cheat-sheet-education.pdf)」列出了最常用的 git 指
+表](https://education.github.com/git-cheat-sheet-education.pdf)」，列出了最常用的 git 命
 令。
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
index 1237ddf3..b00506aa 100644
--- a/criteria/make-contributing-easy.md
+++ b/criteria/make-contributing-easy.md
@@ -5,35 +5,35 @@ order: 5
 ---
 # 貢獻要容易
 
-若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[代碼庫](../glossary.md#codebase)修正問題、新增功能，以及提出安全性議題
+若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[程式基底](../glossary.md#codebase)修正問題、新增功能，以及提出安全性議題
 等。
 
-共享的數位基礎建設讓協作貢獻更容易。使用者讓代碼庫接受貢獻時所需付出的心力越少，則使用者越可能成為貢獻者。
+共享的數位基礎建設讓協作貢獻更容易。使用者讓程式基底接受貢獻時所需付出的心力越少，則使用者越可能成為貢獻者。
 
 ## 需求規定
 
-* 代碼庫「必須」有個可以公開接受任何人建議的議題追蹤器。
-* 文件中「必須」同時有公開的議題追蹤器連結，以及提交的代碼庫變動的連結，例如記錄在「`README`」檔案中。
-* 代碼庫「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。
+* 程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。
+* 文件中「必須」同時有公開的議題追蹤器連結，以及提交的程式基底變動的連結，例如記錄在「`README`」檔案中。
+* 程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。
 * 「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。
 * 文件「必須」說明，該如何通報潛在的安全性與敏感性問題。
 
 ## 測試方式
 
 * 確認有公開的議題追蹤器。
-* 確認代碼庫有公開的議題追蹤器連結，以及已提交的代碼庫變動的連結。
-* 確認可以使用代碼庫中提到的管道，與其他使用者以及開發人員一同討論該軟體。
+* 確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。
+* 確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。
 * 確認有封閉的管道通報安全性問題。
 * 確認有說明如何私下通報安全性問題。
 
 ## 公共政策制定者：需要的工作
 
-* 追蹤代碼庫中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。
+* 追蹤程式基底中的[政策](../glossary.md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。
 
 ## 管理人員：需要的工作
 
-* 追蹤代碼庫中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。
-* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為代碼庫持續做出長久貢獻。
+* 追蹤程式基底中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。
+* 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為程式基底持續做出長久貢獻。
 
 ## 開發人員與設計師：需要的工作
 
diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index 25665247..34680574 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -6,61 +6,61 @@ redirect_from:
   - criteria/findability
 ---
 
-# 代碼庫可查詢得到
+# 程式基底可查詢得到
 
-一旦[代碼庫](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個代碼庫，然後就盼望他人找得到這個代碼庫，更
-需要主動積極。
+一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個程式基底，然後就盼望他人找得到這個程式基
+底，更需要主動積極。
 
-有中介資料說明檔案會讓代碼庫更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄列
-表之中（使代碼庫成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現代碼庫。
+有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體
+目錄列表之中（使程式基底成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現程式基底。
 
 ## 需求規定
 
-* 代碼庫名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
-* 代碼庫說明「應該」要簡短，幫助他人瞭解代碼庫的目的與作用。
-* 維護人員「應該」將代碼庫提交至相關的軟體目錄上。
-* 代碼庫「應該」要架設網站，內容中以代碼庫各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述代碼庫所能解決的問題。
-* 在搜尋引擎查找代碼庫名稱時，「應該」能搜尋得到代碼庫。
-* 在使用搜尋引擎時，如果以自然語言描述代碼庫所能解決的問題，「應該」能搜尋得到代碼庫。
-* 代碼庫「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
-* 代碼庫「應該」包含機器可讀的中介資料說明，例如採用
+* 程式基底名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。
+* 程式基底說明「應該」要簡短，幫助他人瞭解程式基底的目的與作用。
+* 維護人員「應該」將程式基底提交至相關的軟體目錄上。
+* 程式基底「應該」要架設網站，內容中以程式基底各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述程式基底所能解決的問題。
+* 在搜尋引擎查找程式基底名稱時，「應該」能搜尋得到程式基底。
+* 在使用搜尋引擎時，如果以自然語言描述程式基底所能解決的問題，「應該」能搜尋得到程式基底。
+* 程式基底「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](../glossary.md#repository)、位置、網站等。
+* 程式基底「應該」包含機器可讀的中介資料說明，例如採用
 [publiccode.yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。
-* 「可選擇」是否為代碼庫設置專用的網域名稱。
+* 「可選擇」是否為程式基底設置專用的網域名稱。
 * 「可選擇」是否在社群舉辦的會議中定期進行簡報。
 
 ## 測試方式
 
-* 檢查代碼庫名稱是否描述說明其用途，且不包含雙關語。
-* 檢查代碼庫名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完整名稱更熟為人知。
-* 檢查代碼庫是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是代碼庫社群成員。
-* 檢查代碼庫儲存庫是否包含代碼庫的簡短描述。
-* 檢查代碼庫有刊登在相關軟體型錄上。
-* 檢查代碼庫的網站有描述代碼庫能夠解決的問題。
-* 檢查以代碼庫名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將代碼庫列在搜尋結果中。
-* 檢查以自然語言來作搜尋，例如使用代碼庫的簡短描述時，有超過一個的常用主流搜尋引擎，都將代碼庫放在搜尋結果中。
+* 檢查程式基底名稱是否描述說明其用途，且不包含雙關語。
+* 檢查程式基底名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完整名稱更熟為人知。
+* 檢查程式基底是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是程式基底社群成員。
+* 檢查程式基底儲存庫是否包含程式基底的簡短描述。
+* 檢查程式基底有刊登在相關軟體型錄上。
+* 檢查程式基底的網站有描述程式基底能夠解決的問題。
+* 檢查以程式基底名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將程式基底列在搜尋結果中。
+* 檢查以自然語言來作搜尋，例如使用程式基底的簡短描述時，有超過一個的常用主流搜尋引擎，都將程式基底放在搜尋結果中。
 * 檢查永久唯一識別碼條目有提及主要貢獻者。
 * 檢查永久唯一識別碼條目中有包含儲存庫位置。
-* 檢查永久唯一識別碼條目有列出代碼庫網站。
-* 檢查中介資料說明檔案是機器可讀的格式。
+* 檢查永久唯一識別碼條目有列出程式基底網站。
+* 檢查中介資料說明檔是機器可讀的格式。
 
 ## 公共政策制定者：需要的工作
 
-* 貢獻一段說明此代碼庫作用的政策領域，或處理的問題的描述。
-* 請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。
-* 在相關會議上作簡報，介紹代碼庫如何執行[政策](../glossary.md#policy)。
+* 貢獻一段說明此程式基底作用的政策領域，或所處理問題的描述。
+* 請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。
+* 在相關會議上作簡報，介紹程式基底如何執行[政策](../glossary.md#policy)。
 
 ## 管理人員：需要的工作
 
 * 在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。
-* 在引用到代碼庫的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。
-* 為團隊編列內容設計與 SEO 搜尋引擎最佳化技能的預算。
+* 在引用到程式基底的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。
+* 為團隊編列內容設計與實作 SEO 搜尋引擎最佳化技能的預算。
 * 確保專案參與人員出席相關會議，或作簡報介紹。
 
 ## 開發人員與設計師：需要的工作
 
-* 搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol.html)。
-* 在引用到代碼庫的地方，都使用簡短描述，例如放到儲存庫中的說明。
-* 請那些對代碼庫不熟悉且不同領域背景的同事，來測試您的問題描述。
+* 實作搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol.html)。
+* 在引用到程式基底的地方，都使用簡短描述，例如放到儲存庫中的說明。
+* 請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。
 * 推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。
 
 <p style="page-break-after: always;"></p>
@@ -71,4 +71,4 @@ redirect_from:
 * FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
 * GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原
 則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
-機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到代碼庫上，而其他無法直接套用的，我們還需要再研究代碼庫與其對應的特性要怎麼處理。
+機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。
diff --git a/criteria/make-the-codebase-reusable-and-portable.md b/criteria/make-the-codebase-reusable-and-portable.md
index 38ce5210..ffe750ed 100644
--- a/criteria/make-the-codebase-reusable-and-portable.md
+++ b/criteria/make-the-codebase-reusable-and-portable.md
@@ -7,55 +7,55 @@ redirect_from:
   - criteria/create-reusable-and-portable-code
 ---
 
-# 代碼庫要可重複使用且可移植
+# 程式基底要可重複使用且可移植
 
 編寫可重複使用且可移植的[程式碼](../glossary.md#code)，讓政策制定者、開發人員與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻
-回代碼庫中，如此可提高品質、降低維護成本、增強可靠性。
+回程式基底中，如此可提高品質、降低維護成本、增強可靠性。
 
-以重複利用為前提籌劃設計[代碼庫](../glossary.md#codebase)，更容易與多方共享代碼庫的目標使命、願景與範圍等。多方開發與使用的代碼庫，更可以
-從能自我運作的社群中獲益。
+以重複利用為前提籌劃設計[程式基底](../glossary.md#codebase)，更容易與多方共享程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，
+更可以從能自我運作的社群中獲益。
 
-以文件記錄周全的模組構成代碼庫，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
+以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
 境](../glossary.md#different-contexts)中重複利用。
 
 原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢獻者都能測試該原始碼。
 
 ## 需求規定
 
-* 代碼庫「必須」開發成能在不同情境中重複使用。
-* 代碼庫「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，以供執行與瞭解。
-* 代碼庫「應該」有多方單位使用。
+* 程式基底「必須」開發成能在不同情境中重複使用。
+* 程式基底「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，以供執行與瞭解。
+* 程式基底「應該」有多方單位使用。
 * 發展路線圖「應該」有多方單位的需求影響。
-* 代碼庫開發「應該」由多方單位協作。
+* 程式基底開發「應該」由多方單位協作。
 * 「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。
-* 代碼庫「應該」能夠在地化。
+* 程式基底「應該」能夠在地化。
 * 原始碼與其文件「不應該」包含特定情況專用的資訊。
-* 代碼庫模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。
+* 程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。
 * 軟體「不應該」要求僅有單一供應商能提供的服務或平台。
 
 ## 測試方式
 
-* 與另一組織單位角色與您相似的人確認，看他們是否能利用代碼庫，以及需要怎麼進行。
-* 確認代碼庫不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。
-* 若代碼庫處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意圖跡象。
-   * 或是如果代碼庫非常成熟與穩定，鮮少需要修正、改善或貢獻：
-      * 檢查是否有多方單位，或是有在多種情境下正使用代碼庫。
+* 與另一組織單位角色與您相似的人確認，看他們是否能利用程式基底，以及需要怎麼進行。
+* 確認程式基底不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。
+* 若程式基底處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意圖跡象。
+   * 或是如果程式基底非常成熟與穩定，鮮少需要修正、改善或貢獻：
+      * 檢查是否有多方單位，或是有在多種情境下正使用程式基底。
       * 檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。
    * 若是沒有，則：
-      * 檢查是否有多方單位，或是有在多種情境下正使用代碼庫。
-      * 檢查代碼庫貢獻者是否來自多方單位。
-* 檢查代碼庫檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。
+      * 檢查是否有多方單位，或是有在多種情境下正使用程式基底。
+      * 檢查程式基底貢獻者是否來自多方單位。
+* 檢查程式基底檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。
 * 檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。
 
 ## 公共政策制定者：需要的工作
 
 * 為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。
-* 確保代碼庫有將貴組織單位列為已知使用者。
+* 確保程式基底有將貴組織單位列為已知使用者。
 * 找出貴團隊想要協作的其他組織單位。
 
 ## 管理人員：需要的工作
 
-* 確認利害關係人與業主能夠瞭解，代碼庫是以重複利用為明確目標，因而得以減少程式碼技術債，並讓代碼庫可以永續發展。
+* 確認利害關係人與業主能夠瞭解，程式基底是以重複利用為明確目標，因而得以減少程式碼技術債，並讓程式基底可以永續發展。
 * 確認您的團隊與其他團隊能相互協作。
 
 ## 開發人員與設計師：需要的工作
@@ -67,8 +67,8 @@ redirect_from:
 * 以邏輯上具有意義且獨立的模組構成，
 * 如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。
 
-確保代碼庫文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進行
-開發、使用、測試、部署等。
+確保程式基底文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進
+行開發、使用、測試、部署等。
 
 在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。
 
diff --git a/criteria/publish-with-an-open-license.md b/criteria/publish-with-an-open-license.md
index 2021ceb1..36a0e6ea 100644
--- a/criteria/publish-with-an-open-license.md
+++ b/criteria/publish-with-an-open-license.md
@@ -8,10 +8,10 @@ redirect_from:
 
 # 發行採用開放授權
 
-採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-code)，使其能瞭解運作方式、自由使用，並且能為[代碼
-庫](../glossary.md#codebase)做出貢獻。這也能促進供應商建立出以代碼庫為中心的生態系。
+採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-code)，使其能瞭解運作方式、自由使用，並且能為[程式基
+底](../glossary.md#codebase)做出貢獻。這也能促進供應商建立出以程式基底為中心的生態系。
 
-明確指出代碼庫中每一個檔案的授權，讓使用者能正確重複利用代碼庫的部分內容，並表彰作者名稱。
+明確指出程式基底中每一個檔案的授權，讓使用者能正確重複利用程式基底的部分內容，並表彰作者名稱。
 
 ## 需求規定
 
@@ -19,19 +19,19 @@ redirect_from:
 * 軟體原始碼「必須」採用[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
 款](https://spdx.org/licenses/)。
 * 所有原始碼皆「必須」搭配授權條款檔案一併發行。
-* 「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給代碼庫。
-* 代碼庫中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容。
+* 「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給程式基底。
+* 程式基底中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容。
 * 「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。
 
 ## 測試方式
 
-* 確認代碼庫有清楚給予授權條款。
+* 確認程式基底有清楚給予授權條款。
 * 確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清
 單](https://spdx.org/licenses/)，以及文件的授權條款有[符合「開放定
 義」](https://opendefinition.org/licenses/)。
-* 確認代碼庫中有包含其採用的授權條款檔案。
-* 確認貢獻指引中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有求貢獻者轉讓著作權。
-* 在代碼庫[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。
+* 確認程式基底中有包含其採用的授權條款檔案。
+* 確認貢獻指引中，以及[儲存庫](../glossary.md#repository)的組態設定中，沒有要求貢獻者轉讓著作權。
+* 在程式基底[持續整合](../glossary.md#continuous-integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。
 
 ## 公共政策制定者：需要的工作
 
@@ -40,15 +40,15 @@ redirect_from:
 
 ## 管理人員：需要的工作
 
-* 只與能採用開放原始碼授權，交付與發行其原始碼的開放原始碼軟體供應商合作。
+* 只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。
 * 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」
 的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
 
 ## 開發人員與設計師：需要的工作
 
-* 每當建立新的代碼庫時，都要加入新的「`license`」授權條款檔案。
+* 每當建立新的程式基底時，都要加入新的「`license`」授權條款檔案。
 * 每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。
-* 當代碼庫重複利用原始碼時，確認原始碼的授權與代碼庫的授權相容。
+* 每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
@@ -56,7 +56,7 @@ redirect_from:
 * 開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
 * 紐西蘭CC Aotearoa《[創用CC介紹動畫影
 片](https://creativecommons.org/about/videos/creative-commons-kiwi)》。
-* 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》提供規範明確、人類可讀以及機器可讀的著作權與授
-權資訊。
-* Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/)提供經標準化、且機器可讀的大多數授權條款縮寫表示
+* 歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/)》，提供規範明確、人類可讀以及機器可讀的著作權與
+授權資訊。
+* Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/)，提供經標準化、且機器可讀的大多數授權條款縮寫表示
 法。
diff --git a/criteria/require-review-of-contributions.md b/criteria/require-review-of-contributions.md
index ec4d2e02..905b5df2 100644
--- a/criteria/require-review-of-contributions.md
+++ b/criteria/require-review-of-contributions.md
@@ -10,21 +10,21 @@ redirect_from:
 
 同儕審查貢獻是[原始碼](../glossary.md#source-code)提升品質的關鍵，也能降低安全性風險與營運風險。
 
-要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[代碼庫](../glossary.md#codebase)之前，就
-發現與修正潛在臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。
+要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入[程式基底](../glossary.md#codebase)之前，
+就發現與修正潛在臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。
 
 快速審查[政策](../glossary.md#policy)在於向貢獻者保證，必定在一段時間內提供意見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參
 與的熱度。
 
 ## 需求規定
 
-* 所有被接受或是送交給代碼庫正式發行版本中的貢獻內容，都「必須」經過另一位貢獻者審查。
+* 所有被接受或是送交給程式基底正式發行版本中的貢獻內容，都「必須」經過另一位貢獻者審查。
 * 審查「必須」包含原始碼、政策、測試、文件等。
 * 如果不接受貢獻內容，審查人員「必須」提供意見回饋。
-* 審查流程「應該」確認貢獻內容遵循代碼庫的標準、架構、決策安排等，以通過審查。
-* 審查內容「應該」包含執行軟體與執行代碼庫測試。
+* 審查流程「應該」確認貢獻內容遵循程式基底的標準、架構、決策安排等，以通過審查。
+* 審查內容「應該」包含執行軟體與執行程式基底測試。
 * 貢獻內容「應該」由與貢獻者不同背景情境的人來審查。
-* 版本控制系統「不應該」在代碼庫的正式發行版本中，接受未經審查的貢獻內容。
+* 版本控制系統「不應該」在程式基底的正式發行版本中，接受未經審查的貢獻內容。
 * 審查「應該」在兩個工作天內進行。
 * 「可選擇」是否由多位審查人員進行審查。
 
@@ -33,7 +33,7 @@ redirect_from:
 * 確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。
 * 確認審查內容包含原始碼、政策、測試、文件等。
 * 針對未被採用的貢獻內容，確認有適當解釋原因。
-* 檢查審查人員指引中，有包含是否遵循標準、架構、代碼庫指引等指示。
+* 檢查審查人員指引中，有包含是否遵循標準、架構、程式基底指引等指示。
 * 檢查審查人員在審查時是否有執行軟體與測試。
 * 與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。
 * 檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。
@@ -42,18 +42,18 @@ redirect_from:
 ## 公共政策制定者：需要的工作
 
 * 制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。
-* 採用具有審查與意見回饋功能的版本控制系統或作業流程。
+* 採用具有審查與意見回饋功能的版本控制系統，或作業流程。
 
 ## 管理人員：需要的工作
 
 * 將交付妥善軟體作為共同目標。
-* 確保如原始碼、政策、文件、測試等的撰寫與審查貢獻，皆受到同等重視。
+* 確保如原始碼、政策、文件、測試等的貢獻內容撰寫與審查，皆受到同等重視。
 * 創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。
-* 確保貢獻者在貢獻內容給代碼庫時，不是獨自一人埋頭苦幹。
+* 確保貢獻者在貢獻內容給程式基底時，不是獨自一人埋頭苦幹。
 
 ## 開發人員與設計師：需要的工作
 
-* 請代碼庫的其他貢獻者，審查您在貴組織單位內外的工作成果。
+* 請程式基底的其他貢獻者，審查您在貴組織單位內外的工作成果。
 * 當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。
 
 ## 延伸閱讀
diff --git a/criteria/use-a-coherent-style.md b/criteria/use-a-coherent-style.md
index 97b7793b..a12e7e07 100644
--- a/criteria/use-a-coherent-style.md
+++ b/criteria/use-a-coherent-style.md
@@ -12,10 +12,10 @@ redirect_from:
 
 ## 需求規定
 
-* [代碼庫](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作風格指引，可以是代碼庫社群自身的風格指引，或是代碼庫有採用
-的既有風格。
+* [程式基底](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作風格指引，可以是程式基底社群自身的風格指引，或是程式基底
+有採用的既有風格。
 * 貢獻內容「應該」通過自動化的風格測試。
-* 風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與寫下說明文件的期待。
+* 風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與為其寫下說明文件的期待。
 * 「可選擇」是否將[可理解的白話英語](use-plain-english.md)期望加入風格指引之中。
 
 ## 測試方式
@@ -25,7 +25,7 @@ redirect_from:
 
 ## 公共政策制定者：需要的工作
 
-* 為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄到代碼庫文件中，像是「`CONTRIBUTING`」或
+* 為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄到程式基底文件中，像是「`CONTRIBUTING`」或
 「`README`」檔案。
 
 ## 管理人員：需要的工作
@@ -34,16 +34,16 @@ redirect_from:
 
 ## 開發人員與設計師：需要的工作
 
-如果代碼庫還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是
+如果程式基底還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md#repository)中加入相關文件，像是
 「`CONTRIBUTING`」或「`README`」檔案，並描述目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
-的其他層面。指引應該包含貢獻的[原始碼](../glossary.md#source-code)預期該符合哪些要求，才會被維護人員合併至代碼庫中，包括原始碼、測
+的其他層面。指引應該包含貢獻的[原始碼](../glossary.md#source-code)預期該符合哪些要求，才會被維護人員合併至程式基底中，包括原始碼、測
 試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。
 
 此外：
 
 * 使用 linter 程式碼品質梳理工具。
-* 在代碼庫中加入 linter 梳理工具的組態設定。
+* 在程式基底中加入 linter 梳理工具的組態設定。
 
 ## 延伸閱讀
 
-* 維基百科上的《[代碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。
+* 維基百科上的《[程式碼風格](https://en.wikipedia.org/wiki/Programming_style)》條目。
diff --git a/criteria/use-continuous-integration.md b/criteria/use-continuous-integration.md
index 86140dbb..5a855522 100644
--- a/criteria/use-continuous-integration.md
+++ b/criteria/use-continuous-integration.md
@@ -8,21 +8,21 @@ redirect_from:
 
 # 使用持續整合
 
-透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同步協作。合併的頻率越頻繁，貢獻的規模越小，在合併時所發生的衝突就越容易解決。
+透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同步協作。合併的頻率越頻繁、貢獻的規模越小，在合併時所發生的衝突就越容易解決。
 
 自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。
 
-以文件記錄代碼庫的[持續整合](../glossary.md#continuous-integration)工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監
-督[代碼庫](../glossary.md#codebase)狀態變得更為簡單。
+以文件記錄程式基底的[持續整合](../glossary.md#continuous-integration)工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓
+監督[程式基底](../glossary.md#codebase)狀態變得更為簡單。
 
 ## 需求規定
 
 * [原始碼](../glossary.md#source-code)中的所有功能，都「必須」有自動化測試。
-* 所有貢獻內容都「必須」先通過自動化測試，才能上傳至代碼庫。
-* 代碼庫「必須」有解說如何撰寫貢獻內容結構的相關指引。
-* 代碼庫「必須」有能夠審查貢獻內容的活躍貢獻者。
+* 所有貢獻內容都「必須」先通過自動化測試，才能上傳至程式基底。
+* 程式基底「必須」有解說如何撰寫貢獻內容結構的相關指引。
+* 程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。
 * 「應該」公開貢獻內容的自動化測試結果。
-* 代碼庫指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。
+* 程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。
 * 「應該」監督原始碼測試與文件的涵蓋範圍。
 * 「可選擇」是否測試[政策](../glossary.md#policy)和文件，與原始碼之間有無一致性，或是反之亦然。
 * 「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。
@@ -32,7 +32,7 @@ redirect_from:
 
 * 確認有測試可用。
 * 確認原始碼覆蓋率工具能檢查到 100% 的原始碼。
-* 確認貢獻內容只有在通過所有測試後，才會認可上傳至代碼庫。
+* 確認貢獻內容只有在通過所有測試後，才會認可上傳至程式基底。
 * 確認有貢獻指引解說如何撰寫貢獻內容的結構。
 * 確認最近三個月內有貢獻內容上傳。
 * 檢查是否可以查看測試結果。
@@ -49,7 +49,7 @@ redirect_from:
 
 * 確保能儘快且經常給真正的終端使用者進行測試。
 * 以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。
-* 聘請有能力處理漸進式交付並跟上規劃進度的顧問服務。
+* 聘請有能力處理漸進式交付，並跟得上規劃進度的顧問服務。
 * 發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。
 
 ## 開發人員與設計師：需要的工作
diff --git a/criteria/use-open-standards.md b/criteria/use-open-standards.md
index 9a410303..d8cae67b 100644
--- a/criteria/use-open-standards.md
+++ b/criteria/use-open-standards.md
@@ -8,16 +8,16 @@ redirect_from:
 
 # 採用開放標準
 
-[開放標準](../glossary.md#open-standard)保證可以取得使用與貢獻[代碼庫](../glossary.md#codebase)所需的知
-識。不僅能為不同的系統之間建立互通性，更降低廠商套牢的可能性。開放標準如果明確，不同方就可以各自獨立開發作資料交換。
+[開放標準](../glossary.md#open-standard)保證可以取得使用與貢獻[程式基底](../glossary.md#codebase)所需的知
+識。不僅能為不同的系統之間建立互通性，更能降低廠商套牢的可能性。開放標準如果明確，不同方就可以各自獨立開發作資料交換。
 
 ## 需求規定
 
-* 代碼庫如要促進資料交換的特性，就「必須」採用符合[OSI 開放原始碼促進會其開放標準需求規範](https://opensource.org/osr)的開放標
-準。
+* 程式基底如要促進資料交換的特性，就「必須」採用符合 [OSI 開放原始碼促進會其《開放標準需求規範](https://opensource.org/osr)》的
+開放標準。
 * 如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。
-* 代碼庫選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標準的連結。
-* 代碼庫選擇採用的任何非開放標準，皆「禁止」妨礙代碼庫的協作與重複使用。
+* 程式基底選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標準的連結。
+* 程式基底選擇採用的任何非開放標準，皆「禁止」妨礙程式基底的協作與重複使用。
 * 如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。
 * 採用開放標準時，「應該」優先選擇可經機器測試的開放標準。
 * 採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。
@@ -26,7 +26,7 @@ redirect_from:
 
 * 確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。
 * 確認若有採用任何的非開放標準，皆有清楚記錄在文件中。
-* 確認文件有清單列出代碼庫所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
+* 確認文件有清單列出程式基底所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。
 
 ## 公共政策制定者：需要的工作
 
@@ -35,7 +35,7 @@ redirect_from:
 
 ## 管理人員：需要的工作
 
-* 考慮在 [原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。
+* 考慮在[原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。
 
 ## 開發人員與設計師：需要的工作
 
diff --git a/criteria/use-plain-english.md b/criteria/use-plain-english.md
index 500dd19f..0666f51f 100644
--- a/criteria/use-plain-english.md
+++ b/criteria/use-plain-english.md
@@ -8,27 +8,27 @@ redirect_from:
 
 # 使用白話的英語
 
-英語是軟體開發領域中的<i>實際</i>協作語言。
+英語是軟體開發領域中的<i>實際</i> 協作語言。
 
 公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解[程式碼](../glossary.md#code)與其功用。
 
-翻譯可以讓更多人有機會認識[代碼庫](../glossary.md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。
+翻譯可以讓更多人有機會認識[程式基底](../glossary.md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。
 
 ## 需求規定
 
-* 代碼庫的所有文件都「必須」使用英語。
+* 程式基底的所有文件都「必須」使用英語。
 * 所有[原始碼](../glossary.md#source-code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀
 當作程式碼的部分則除外。
 * 任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。
 * 任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。
-* 代碼庫中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
+* 程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
 * 根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/?
 showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。
 * 「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。
 
 ## 測試方式
 
-* 確認代碼庫文件有英語版本。
+* 確認程式基底文件有英語版本。
 * 確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。
 * 確認任何非英語政策都有隨附英語版摘要。
 * 確認翻譯版與英語版內容相同。
@@ -48,7 +48,7 @@ showtechniques=315#readable)》的建議，文件內容應該以國中識讀程
 ## 開發人員與設計師：需要的工作
 
 * 經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。
-* 詢問身處不同背景情境的人（像是另一個代碼庫的開發人員）是否能瞭解內容。
+* 詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。
 
 <p style="page-break-after: always;"></p>
 ## Further reading
diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index 92967171..83de6e1b 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -8,25 +8,25 @@ redirect_from:
 
 # 歡迎貢獻者
 
-[代碼庫](../glossary.md#codebase)的社群氛圍會影響使用者選擇所要使用的代碼庫。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。
-若貢獻者有明確的方法可以影響代碼庫、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並信任代碼庫社群的治理方式。
+[程式基底](../glossary.md#codebase)社群的氛圍，會影響使用者選擇所要使用的程式基底。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我
+運作。若貢獻者有明確的方法可以影響程式基底、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並信任程式基底社群的治理方式。
 
 ## 需求規定
 
-* 代碼庫必須「允許」任何人對代碼庫提出修改建議。
-* 代碼庫「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
-* 代碼庫「必須」以文件記錄代碼庫、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
+* 程式基底必須「允許」任何人對程式基底提出修改建議。
+* 程式基底「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發，例如以「`CONTRIBUTING`」檔案說明。
+* 程式基底「必須」以文件記錄程式基底、貢獻內容與社群互動等的治理方式，例如以「`GOVERNANCE`」檔案來說明。
 * 貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。
-* 代碼庫「應該」宣布投入其開發與維護工作的參與組織單位。
-* 代碼庫「應該」要有可公開取得的發展路線圖。
-* 代碼庫「應該」公布代碼庫的活動統計數據。
-* 「可選擇」是否為代碼庫加入貢獻者的行為守則。
+* 程式基底「應該」宣布投入其開發與維護工作的參與組織單位。
+* 程式基底「應該」要有可公開取得的發展路線圖。
+* 程式基底「應該」公布程式基底的活動統計數據。
+* 「可選擇」是否為程式基底加入貢獻者的行為守則。
 
 ## 測試方式
 
-* 確認可以提交修改建議給代碼庫。
-* 確認代碼庫有貢獻指引。
-* 確認代碼庫有清楚解釋治理架構，並包含如何影響代碼庫治理的方法。
+* 確認可以提交修改建議給程式基底。
+* 確認程式基底有貢獻指引。
+* 確認程式基底有清楚解釋治理架構，並包含如何影響程式基底治理的方法。
 * 確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。
 * 檢查是否有參與的組織單位名單。
 * 檢查是否有發展路線圖。
@@ -35,15 +35,15 @@ redirect_from:
 
 ## 公共政策制定者：需要的工作
 
-* 為代碼庫加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。
+* 為程式基底加入其他資源的清單，而這些資源可幫助[政策](../glossary.md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。
 * 考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。
 
 ## 管理人員：需要的工作
 
 * 確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。
 * 如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。
-* 若有需要，確認您有編列貢獻內容審查流程的預算，且通過代碼庫社群同意。
-* 確認文件有解釋每個參與組織單位所投入的內容，例如提供代碼庫哪些資源，以及參與的時間長度等。
+* 若有需要，確認您有編列貢獻內容審查流程的預算，且通過程式基底社群同意。
+* 確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參與的時間長度等。
 * 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
 
 <p style="page-break-after: always;"></p>
@@ -51,13 +51,13 @@ redirect_from:
 
 * 快速回應請求。
 * 告知管理人員，您在支援其他貢獻者時所需的時間與資源。
-* 清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到代碼庫中。
+* 清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到程式基底中。
 
 ## 延伸閱讀
 
 * 開放原始碼指引所提供的《[營造友善的社群](https://opensource.guide/building-community/)》。
 * Mike McQuaid《[開放原始碼貢獻者瓶
 頸](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/)》。
-* 《開放原始碼指引》針對推動[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治
+* 開放原始碼指引針對推動[開放原始碼](../glossary.md#open-source)社群專案所寫的《[領導與治
 理](https://opensource.guide/leadership-and-governance/)》。
 * Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。
diff --git a/docs/releasing.md b/docs/releasing.md
index 9a08a545..2d915574 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -11,7 +11,7 @@
 冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)》的規範。
 
 1. 建立發行用分支
-   - 從「develop」分支下指令，`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
+   - 從「develop」分支下命令，`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
    - 推送分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`
 
 1. 更新本次新發行
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 3bd211cc..3468d5f9 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -7,7 +7,7 @@
 
 本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。
 
-代碼庫管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作
+程式基底管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作
 業](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
 環節的一部份。
 
@@ -25,8 +25,8 @@
 ## 長期
 
 * 為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）
-* 通過多個代碼庫驗證
-* 在幾個代碼庫遵循標準後，發行 1.0.0 版
+* 通過多個程式基底驗證
+* 在幾個程式基底遵循標準後，發行 1.0.0 版
 * 可連結的需求規範
 * 新封面設計
 * 註冊申請 ISBN 書號
diff --git a/foreword.md b/foreword.md
index bfaf3af0..7091b008 100644
--- a/foreword.md
+++ b/foreword.md
@@ -47,8 +47,8 @@ redirect_from:
 
 公家機關、公務員與居民都值得更好的。
 
-我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有代碼庫之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主權。技術自主
-讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。
+我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有程式基底之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主權。技術自
+主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。
 
 作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。
 
@@ -104,20 +104,20 @@ redirect_from:
 
 公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在投標時可以在標案中納入公共程式。
 
-若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該代碼庫。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服務
-內容或預期成果。
+若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服
+務內容或預期成果。
 
 ## 《Standard for Public Code》目標
 
 本標準在於支持開發人員、設計師、管理人員、公共政策制定者：
 
 * 開發出高品質的軟體與政策，來改善公共服務的交付
-* 開發出能在各種情境下重複使用，且以協作方式維護的代碼庫
+* 開發出能在各種情境下重複使用，且以協作方式維護的程式基底
 * 減少技術債與專案失敗率
 * 更能精細控制其 IT 系統粒度，並做出系統相關決策
 * 以更好的經濟模型改善供應商關係
 
-如果有潛在使用者想採用經由《Standard for Public Code》測試過的代碼庫，便可以預期這些代碼庫具有方便重複利用、容易維護、高品質的特性。
+如果有潛在使用者想採用經由《Standard for Public Code》測試過的程式基底，便可以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。
 
 《Standard for Public Code》能有此效果是基於：
 
diff --git a/glossary.md b/glossary.md
index 4d035640..91d1497d 100644
--- a/glossary.md
+++ b/glossary.md
@@ -10,15 +10,15 @@
 任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是由機器執
 行。
 
-## 代碼庫
+## 程式基底
 
-執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件的整套統合包。
+執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件等的整套內容統合包。
 
-例如，這可以是文件，或是版本控制的儲存庫。
+舉例來說，這可以是用文件，或是版本控制的儲存庫來存放。
 
 ## 持續整合
 
-在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回代碼庫開發中分支的實務作法。
+在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回程式基底開發中分支的實務作法。
 
 ## 不同情境
 
@@ -30,7 +30,7 @@
 
 舉例而言，城市的居民視為該城市的服務，以及驅動這些服務運作的程式碼的終端使用者。
 
-## 開源或開放原始碼
+## 開源或開放原始碼 (Open Source)
 
 所謂「開源」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
 
@@ -49,7 +49,7 @@
 
 在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的政策。
 
-## 公共程式
+## 公共程式 (Public code)
 
 公共程式，是由公家機關所開發的開源軟體，同時包含協作與重複利用所需的政策與指引。
 
@@ -67,7 +67,7 @@
 
 ## 儲存庫
 
-儲存庫是版本控制工具，用於存放檔案與代碼庫中介資料的儲存位置。儲存庫允許多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
+儲存庫是版本控制工具，用於存放檔案與程式基底中介資料的儲存位置。儲存庫允許多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
 
 ## 原始碼
 
@@ -75,5 +75,5 @@
 
 ## 版本控制
 
-版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「*修訂編號*」（或「版次」等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作
-者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間的變動。
+版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「*修訂編號*」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作者，
+方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間的變動。
diff --git a/index.md b/index.md
index eadcea4e..2ef439b2 100644
--- a/index.md
+++ b/index.md
@@ -9,7 +9,7 @@ toc: false
 
 《Standard for Public Code》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使
 用各自的成果。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《Standard for Public Code》支持公家機關透過協作方式，創造
-出好用、開放、易懂、課責、近用、永續的代碼庫。這份標準從設計之初，就是要用於各種不同政府層級的代碼庫，小從市政府，大到超國家組織都行。
+出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。
 
 《Standard for Public Code》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開源軟體，同時包含
 協作與重複使用所需的政策與指引。
@@ -17,11 +17,11 @@ toc: false
 《Standard for Public Code》當中的準則，符合開源軟體開發的指引與最佳實務。
 
 {% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序
-文](foreword.md). {% endif%}{% endfor %}
+文](foreword.md)。 {% endif%}{% endfor %}
 
 ## 目次
 
-* [讀者指引：如何詮釋此標準](readers-guide.md)
+* [讀者指引：如何解讀此標準](readers-guide.md)
 * [詞彙表](glossary.md)
 * [準則](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in
 sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{%
@@ -37,8 +37,8 @@ if page.title %}
 ## 社群會議
 
 我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。[議
-程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code) 在會議
-前約一週的時間更新。您可以[註
+程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code)在會議前
+約一週的時間更新。您可以[註
 冊](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)
 報名，會再寄送會議通話邀請函給您。
 
@@ -46,6 +46,7 @@ if page.title %}
 
 * 本標準非官方的其他語言[社群翻
 譯](https://publiccodenet.github.io/community-translations-standard/)
-* 公部門開源代碼庫的〈[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)〉
-* Foundation for Public Code 管事人員用於代碼庫審查的〈[標準準則檢查清
+* 公部門開源程式基底的《[標準遵循自我評
+估](https://publiccodenet.github.io/assessment-eligibility/)》
+* Foundation for Public Code 管事人員用於程式基底審查的〈[標準準則檢查清
 單](/docs/review-template.html)〉
diff --git a/readers-guide.md b/readers-guide.md
index ae39504c..9e0bbf61 100644
--- a/readers-guide.md
+++ b/readers-guide.md
@@ -13,7 +13,7 @@
 
 ## 前言
 
-本小節說明這些準則想達成的目的，以及為何會對代碼庫使用者與貢獻者來說這麼重要的原因。
+本小節說明這些準則想達成的目的，以及為何會對程式基底使用者與貢獻者來說這麼重要的原因。
 
 ## 需求規定
 
@@ -59,13 +59,13 @@
 
 ## 作用範圍限制
 
-《Standard for Public Code》不是為了涵蓋代碼庫的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法
-律框架。
+《Standard for Public Code》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或
+法律框架。
 
 此外，雖然《Standard for Public Code》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代
 品質標準，像是 ISO 25000 認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF 最佳實務標
 章](https://github.com/coreinfrastructure/best-practices-badge)等，而是希望能與它們能良好協同搭
 配。
 
-《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了代碼庫需要準備好進行協作以外，也需要積極主
+《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主
 動，以及做到超越協作以外的企圖心。

From 944a00f540f43a2cb3296865a1bb55dc9cf4ef84 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Fri, 15 Sep 2023 15:54:28 +0000
Subject: [PATCH 55/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 83 +++++++++++++------------
 1 file changed, 42 insertions(+), 41 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 844ebae6..511cfdaf 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-15 15:51+0000\n"
+"PO-Revision-Date: 2023-09-16 03:32+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -463,7 +463,7 @@ msgstr "新增審查範本。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Consistently link glossary terms."
-msgstr "一致性連動詞彙表。"
+msgstr "一致性連結詞彙表。"
 
 #: ./CHANGELOG.md:block 16 (unordered list)
 msgid "Add practices and standards to follow in CONTRIBUTING."
@@ -535,7 +535,7 @@ msgstr "重新編寫「得以」等級的相關規定，加入使用「可選擇
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "表明《Standard for Public "
+msgstr "表達《Standard for Public "
 "Code》應該盡可能符合其自身規定的立場，並加入評估措施。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
@@ -744,7 +744,7 @@ msgstr "將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Add Digital Public Goods approval badge."
-msgstr "新增「數位公共財」核可徽章。"
+msgstr "新增「數位公共財」認可標章。"
 
 #: ./CHANGELOG.md:block 28 (unordered list)
 msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
@@ -958,7 +958,7 @@ msgstr "2019年8月22日：🌠第三版草稿專注在提升文字品質，並
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "With some great new contributors comes a fresh author list."
-msgstr "好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。"
+msgstr "有好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。"
 
 #: ./CHANGELOG.md:block 43 (unordered list)
 msgid "All links are now HTTPS."
@@ -1410,7 +1410,7 @@ msgstr ""
 
 #: ./GOVERNANCE.md:block 3 (header)
 msgid "Governance"
-msgstr "治理"
+msgstr "治理方式"
 
 #: ./GOVERNANCE.md:block 4 (paragraph)
 msgid ""
@@ -1418,9 +1418,9 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"本標準是 [Foundation for Public Code](https://publiccode.net/) 在程式基底盡職"
-"管理作監督時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群"
-"共同參與開發。"
+"本標準是 [Foundation for Public Code](https://publiccode.net/) 在監督程式基底"
+"盡職管理時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共"
+"同參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
@@ -1516,7 +1516,7 @@ msgstr "《Standard for Public Code》目前為草稿階段。我們正在準備
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將《Standard for Public Code》套用您的程式基底"
+msgstr "將《Standard for Public Code》套用到您的程式基底"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1527,9 +1527,9 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它"
-"是人人都能自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資格"
-"評估](https://publiccodenet.github.io/assessment-"
+"若您想要將《Standard for Public Code》套用到您的程式基底，就請放心去做，因為"
+"它是人人都能自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資"
+"格評估](https://publiccodenet.github.io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 #: ./README.md:block 9 (paragraph)
@@ -1754,7 +1754,7 @@ msgstr ""
 "本標準採用 CC0 "
 "公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任"
 "何人都能任意使用這些內容。如果您是貢獻者，代表您也將這些權利賦予他人。若要進"
-"一步瞭解如何協助本專案，請參閱《[貢獻指引](CONTRIBUTING.md)》。"
+"一步瞭解如何協助本專案，請參閱〈[貢獻指引](CONTRIBUTING.md)〉。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
 msgid "order: 2 redirect_from:"
@@ -1888,7 +1888,7 @@ msgstr "政策內容請使用明確且機器可讀的格式，像是[物件管
 msgid ""
 "Track policy with [the same version control](maintain-version-control.md) "
 "and documentation used to track source code."
-msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制系統](maintain-version-control."
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](maintain-version-control."
 "md)與文件。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
@@ -1909,9 +1909,10 @@ msgid ""
 "commitment to equal opportunity."
 msgstr ""
 "納入會影響社會群體、程式基底與開發目標的相關政策，包含 [GDPR "
-"一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 "
-"[歐盟網頁無障礙命令](https://ec.europa.eu/digital-single-market/en/web-access"
-"ibility)等此類法律義務，或者是人權政策，例如公家機關對機會平等的承諾等。"
+"一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/"
+"oj)或是[歐盟網頁無障礙命令](https://ec.europa.eu/digital-single-market/en/"
+"web-accessibility)等此類法律義務，或者是人權政策，例如公家機關對機會平等的承"
+"諾等。"
 
 #: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
 msgid "Managers: what you need to do"
@@ -3182,11 +3183,11 @@ msgid ""
 "findable). Some of these apply directly to codebases, while others may "
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
-"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原則](ht"
-"tps://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特"
-"性會讓資料（或中介資料）更容易讓機器採取行動（也因此更容易被找到）。其中的部"
-"分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底"
-"與其對應的特性要怎麼處理。"
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR "
+"科學資料管理與盡職監督指導原則](https://www.go-fair.org/fair-principles/)》，"
+"提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行"
+"動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直"
+"接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
 msgid "order: 3 redirect_from:"
@@ -4766,7 +4767,7 @@ msgstr "直向或橫向：直向 (Staand)"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing inside: 4/4 dual sided full color"
-msgstr "內頁印刷：正四反四，雙面全色印刷"
+msgstr "內頁印刷：正四反四 4/4，雙面全色印刷"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Inside material: 90 grams biotop"
@@ -4778,7 +4779,7 @@ msgstr "封面：350 克封面"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Printing cover: 4/0 one sided full cover"
-msgstr "封面印刷：正四反空，單面滿版印刷"
+msgstr "封面印刷：正四反空 4/0，單面滿版印刷"
 
 #: ./docs/printing.md:block 5 (unordered list)
 msgid "Cover treatment: one sided matt foliated (Enke)"
@@ -5584,7 +5585,7 @@ msgid ""
 "2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
 "the background behind the Foundation for Public Code."
 msgstr ""
-"[〈程式協作是城市的未來〉@ DecidimFest 2019](https://www.youtube.com/"
+"[「程式協作是城市的未來」@ DecidimFest 2019](https://www.youtube.com/"
 "watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny，講述 Foundation for Public Code "
 "的背景。"
 
@@ -5594,7 +5595,7 @@ msgid ""
 "2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
 "procurement, law and more."
 msgstr ""
-"[ 〈用公共的納稅錢？做公共的程式吧！〉專題討論 @ Nextcloud 大會 "
+"[ 「用公共的納稅錢？做公共的程式吧！」專題討論 @ Nextcloud 大會 "
 "2019](https://youtube.com/watch?v=QHFkD4xfd6c)。討論採購、法律等主題。"
 
 #: ./foreword.md:block 64 (header)
@@ -5605,7 +5606,7 @@ msgstr "參與我們"
 msgid ""
 "This standard is a living document. [Read our contributor "
 "guide](/CONTRIBUTING.md) to learn how you can make it better."
-msgstr "本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING."
+msgstr "本標準是持續成長的文件。[請讀我們的《貢獻者指引》](/CONTRIBUTING."
 "md)，瞭解您可以怎麼做來讓本標準變得更好。"
 
 #: ./foreword.md:block 66 (header)
@@ -5648,12 +5649,12 @@ msgstr "程式基底"
 msgid ""
 "Any discrete package of code (both source and policy), the tests and the "
 "documentation required to implement a piece of policy or software."
-msgstr "執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件等"
-"的整套內容統合包。"
+msgstr "任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、"
+"測試與文件等的整套內容。"
 
 #: ./glossary.md:block 8 (paragraph)
 msgid "This can be, for example, a document or a version-control repository."
-msgstr "舉例來說，這可以是用文件，或是版本控制的儲存庫來存放。"
+msgstr "舉例而言，這個具體形式可以是文件，或是版本控制的儲存庫。"
 
 #: ./glossary.md:block 9 (header)
 msgid "Continuous integration"
@@ -5692,8 +5693,8 @@ msgstr "整體民眾：程式碼與其所建立的服務的終端使用者。"
 msgid ""
 "For example, a city's residents are considered end users of a city's "
 "services and of all code that powers these services."
-msgstr "舉例而言，城市的居民視為該城市的服務，以及驅動這些服務運作的程式碼的終端使用"
-"者。"
+msgstr "舉例而言，城市的居民即視為該城市的服務、以及驅動這些服務運作的程式碼的終端使"
+"用者。"
 
 #: ./glossary.md:block 16 (header)
 msgid "Open source"
@@ -5704,7 +5705,7 @@ msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
 msgstr ""
-"所謂「開源」，是根據 OSI "
+"所謂「開源」或「開放原始碼」，是根據 OSI "
 "開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-"
 "annotated)》而來。"
 
@@ -5717,7 +5718,7 @@ msgid ""
 "An open standard is any standard that meets the Open Source Initiative's "
 "[Open Standard Requirements](https://opensource.org/osr)."
 msgstr "任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/"
-"osr)》的標準就是開放標準。"
+"osr)》的標準，就是開放標準。"
 
 #: ./glossary.md:block 20 (header)
 msgid "Policy"
@@ -5820,7 +5821,7 @@ msgid ""
 " on the same set of files. Repositories are able to store multiple versions "
 "of sets of files."
 msgstr ""
-"儲存庫是版本控制工具，用於存放檔案與程式基底中介資料的儲存位置。儲存庫允許多"
+"儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多"
 "位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。"
 
 #: ./glossary.md:block 34 (header)
@@ -5850,7 +5851,7 @@ msgstr ""
 "版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱"
 "為「*修訂編號*」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間"
 "以及作者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以"
-"及查看內容隨著時間的變動。"
+"及查看內容隨著時間經歷的變動。"
 
 #: ./index.md:block 3 (header)
 msgid "toc: false"
@@ -6062,7 +6063,7 @@ msgid ""
 "in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
 msgstr ""
 "本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/"
-"rfc2119)》的描述作詮釋："
+"rfc2119)》的描述作解釋："
 
 #: ./readers-guide.md:block 12 (unordered list)
 msgid "MUST"
@@ -6147,7 +6148,7 @@ msgid ""
 msgstr ""
 "管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他"
 "們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的"
-"資源、提供正確的架構等，才能交付優良的服務。"
+"資源、提供適當的架構等，才能交付優良的服務。"
 
 #: ./readers-guide.md:block 23 (paragraph)
 msgid ""
@@ -6309,5 +6310,5 @@ msgid ""
 "[Standard criteria checklist](/docs/review-template.html) used by Foundation"
 " for Public Code stewards for codebase review"
 msgstr ""
-"Foundation for Public Code 管事人員用於程式基底審查的〈[標準準則檢查清單](/"
-"docs/review-template.html)〉"
+"Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清單](/"
+"docs/review-template.html)》"

From 23c6d25ad41fcdba05b5eb34839d823c29695d3d Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Sat, 16 Sep 2023 03:38:57 +0000
Subject: [PATCH 56/71] update translate

---
 CHANGELOG.md                              |  8 ++++----
 GOVERNANCE.md                             |  6 +++---
 README.md                                 |  4 ++--
 criteria/bundle-policy-and-source-code.md |  4 ++--
 criteria/make-the-codebase-findable.md    |  2 +-
 docs/printing.md                          |  4 ++--
 foreword.md                               |  6 +++---
 glossary.md                               | 15 ++++++++-------
 index.md                                  |  4 ++--
 readers-guide.md                          |  6 +++---
 10 files changed, 30 insertions(+), 29 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index b12cef83..1ec82c27 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -79,7 +79,7 @@
 * 改善「測試方式」指引。
 * 新增 publiccode.yml 檔案。
 * 新增審查範本。
-* 一致性連動詞彙表。
+* 一致性連結詞彙表。
 * 在「CONTRIBUTING」中加入要遵循的實務與標準。
 * 將 Matti Schneider 加入作者群。
 * 將剩餘 SPDX 標頭加入檔案中。
@@ -98,7 +98,7 @@
 * 移除可重複使用與移植的程式碼中多餘的規定。
 * 在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。
 * 重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。
-* 表明《Standard for Public Code》應該盡可能符合其自身規定的立場，並加入評估措施。
+* 表達《Standard for Public Code》應該盡可能符合其自身規定的立場，並加入評估措施。
 * 將 SPDX 授權識別碼加入檔案中。
 * 導入新的行為守則。
 * 解釋原始碼與政策內文的差異。
@@ -154,7 +154,7 @@
 * 將開發人員與設計師加入「風格要前後一致」指引中。
 * 新增「不同情境」到詞彙表中。
 * 將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。
-* 新增「數位公共財」核可徽章。
+* 新增「數位公共財」認可標章。
 * 為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。
 * 將「開放標準」原則加入延伸閱讀。
 * 將「白話語言定義」加入延伸閱讀。
@@ -218,7 +218,7 @@
 
 2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見
 
-* 好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。
+* 有好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。
 * 所有連結都是 HTTPS。
 * 一般校對、釐清用字淺詞、修正拼字錯誤等。
 * 更新準則：
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index b7454b44..635d303b 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -3,10 +3,10 @@
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 ---
 
-# 治理
+# 治理方式
 
-本標準是 [Foundation for Public Code](https://publiccode.net/) 在程式基底盡職管理作監督時的核心。我們依照這份
-文件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。
+本標準是 [Foundation for Public Code](https://publiccode.net/) 在監督程式基底盡職管理時的核心。我們依照這份文
+件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。
 
 這份標準由 Foundation for Public Code 職員負責維護。
 
diff --git a/README.md b/README.md
index 46343166..539363d3 100644
--- a/README.md
+++ b/README.md
@@ -21,7 +21,7 @@ badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.p
 
 《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。
 
-## 將《Standard for Public Code》套用您的程式基底
+## 將《Standard for Public Code》套用到您的程式基底
 
 若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成
 《Standard for Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment 徽
@@ -111,4 +111,4 @@ script/pdf.sh
 © [作者與貢獻者](AUTHORS.md)
 
 本標準採用 CC0 公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
-這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱《[貢獻指引](CONTRIBUTING.md)》。
+這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱〈[貢獻指引](CONTRIBUTING.md)〉。
diff --git a/criteria/bundle-policy-and-source-code.md b/criteria/bundle-policy-and-source-code.md
index ce98486b..3b1d1c32 100644
--- a/criteria/bundle-policy-and-source-code.md
+++ b/criteria/bundle-policy-and-source-code.md
@@ -36,10 +36,10 @@ redirect_from:
 位所選擇遵守的各項標準，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。
 * 請提供政策相關參考資料與連結。
 * 政策內容請使用明確且機器可讀的格式，像是[物件管理群體](https://www.omg.org/spec/)所發表的格式。
-* 追蹤政策時，請使用與追蹤原始碼[相同的版本控制系統](maintain-version-control.md)與文件。
+* 追蹤政策時，請使用與追蹤原始碼[相同的版本控制](maintain-version-control.md)與文件。
 * 定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合[政策意圖](document-codebase-objectives.md)。
 * 納入會影響社會群體、程式基底與開發目標的相關政策，包含 [GDPR 一般資料保護規
-則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是 [歐盟網頁無障礙命
+則](https://eur-lex.europa.eu/eli/reg/2016/679/oj)或是[歐盟網頁無障礙命
 令](https://ec.europa.eu/digital-single-market/en/web-accessibility)等此類法律義務，或者是人權政
 策，例如公家機關對機會平等的承諾等。
 
diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index 34680574..a6da5cdb 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -69,6 +69,6 @@ redirect_from:
 * Wikidata 維基數據社群《[維基數據簡
 介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
 * FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
-* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR科學資料管理與盡職治理指導原
+* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR 科學資料管理與盡職監督指導原
 則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
 機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。
diff --git a/docs/printing.md b/docs/printing.md
index f631e666..5fb3d9f8 100644
--- a/docs/printing.md
+++ b/docs/printing.md
@@ -11,10 +11,10 @@
 * 樣式：平裝書 ([Reclameland 產品頁面](https://www.reclameland.nl/drukken/softcover-boeken))
 * 紙張尺寸：A4
 * 直向或橫向：直向 (Staand)
-* 內頁印刷：正四反四，雙面全色印刷
+* 內頁印刷：正四反四 4/4，雙面全色印刷
 * 內頁材質：Biotop 90克
 * 封面：350 克封面
-* 封面印刷：正四反空，單面滿版印刷
+* 封面印刷：正四反空 4/0，單面滿版印刷
 * 封面處理：單面霧面層剝處理 (Enke)
 * 頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數
 * 個別封裝：無
diff --git a/foreword.md b/foreword.md
index 7091b008..d4c3fe7c 100644
--- a/foreword.md
+++ b/foreword.md
@@ -149,14 +149,14 @@ redirect_from:
 
 ### 探討公共程式的影片
 
-* [〈程式協作是城市的未來〉@ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)。主講
+* [「程式協作是城市的未來」@ DecidimFest 2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)。主講
 人 Ben Cerveny，講述 Foundation for Public Code 的背景。
-* [ 〈用公共的納稅錢？做公共的程式吧！〉專題討論 @ Nextcloud 大會 2019](https://youtube.com/watch?
+* [ 「用公共的納稅錢？做公共的程式吧！」專題討論 @ Nextcloud 大會 2019](https://youtube.com/watch?
 v=QHFkD4xfd6c)。討論採購、法律等主題。
 
 ## 參與我們
 
-本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING.md)，瞭解您可以怎麼做來讓本標準變得更好。
+本標準是持續成長的文件。[請讀我們的《貢獻者指引》](/CONTRIBUTING.md)，瞭解您可以怎麼做來讓本標準變得更好。
 
 ## 聯絡方式
 
diff --git a/glossary.md b/glossary.md
index 91d1497d..7c636dd8 100644
--- a/glossary.md
+++ b/glossary.md
@@ -12,9 +12,9 @@
 
 ## 程式基底
 
-執行部分政策或軟體所需，任何獨立分離的程式（包含原始碼與政策）、測試與文件等的整套內容統合包。
+任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、測試與文件等的整套內容。
 
-舉例來說，這可以是用文件，或是版本控制的儲存庫來存放。
+舉例而言，這個具體形式可以是文件，或是版本控制的儲存庫。
 
 ## 持續整合
 
@@ -28,15 +28,16 @@
 
 整體民眾：程式碼與其所建立的服務的終端使用者。
 
-舉例而言，城市的居民視為該城市的服務，以及驅動這些服務運作的程式碼的終端使用者。
+舉例而言，城市的居民即視為該城市的服務、以及驅動這些服務運作的程式碼的終端使用者。
 
 ## 開源或開放原始碼 (Open Source)
 
-所謂「開源」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
+所謂「開源」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定
+義](https://opensource.org/osd-annotated)》而來。
 
 ## 開放標準
 
-任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/osr)》的標準就是開放標準。
+任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/osr)》的標準，就是開放標準。
 
 ## 政策
 
@@ -67,7 +68,7 @@
 
 ## 儲存庫
 
-儲存庫是版本控制工具，用於存放檔案與程式基底中介資料的儲存位置。儲存庫允許多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
+儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
 
 ## 原始碼
 
@@ -76,4 +77,4 @@
 ## 版本控制
 
 版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「*修訂編號*」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作者，
-方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間的變動。
+方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間經歷的變動。
diff --git a/index.md b/index.md
index 2ef439b2..3f16cd1a 100644
--- a/index.md
+++ b/index.md
@@ -48,5 +48,5 @@ if page.title %}
 譯](https://publiccodenet.github.io/community-translations-standard/)
 * 公部門開源程式基底的《[標準遵循自我評
 估](https://publiccodenet.github.io/assessment-eligibility/)》
-* Foundation for Public Code 管事人員用於程式基底審查的〈[標準準則檢查清
-單](/docs/review-template.html)〉
+* Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清
+單](/docs/review-template.html)》
diff --git a/readers-guide.md b/readers-guide.md
index 9e0bbf61..cef7591a 100644
--- a/readers-guide.md
+++ b/readers-guide.md
@@ -19,7 +19,7 @@
 
 這個小節列出如果要遵循本標準，需要完成哪些事項。
 
-本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/rfc2119)》的描述作詮釋：
+本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/rfc2119)》的描述作解釋：
 
 * 必須
 * 禁止
@@ -48,8 +48,8 @@
 
 本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。
 
-管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源、提供正
-確的架構等，才能交付優良的服務。
+管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源、提供適
+當的架構等，才能交付優良的服務。
 
 ## 開發人員與設計師：需要的工作
 

From 1394c12eeb99acb7bb3beed521356e3d6cc092e5 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Sat, 16 Sep 2023 12:42:31 +0800
Subject: [PATCH 57/71] custom tranlate

---
 index.md | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/index.md b/index.md
index 3f16cd1a..0030069c 100644
--- a/index.md
+++ b/index.md
@@ -36,17 +36,12 @@ if page.title %}
 
 ## 社群會議
 
-我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。[議
-程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code)在會議前
-約一週的時間更新。您可以[註
-冊](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)
+我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。[議程](https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code)在會議前
+約一週的時間更新。您可以[註冊](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)
 報名，會再寄送會議通話邀請函給您。
 
 ## 其他資源
 
-* 本標準非官方的其他語言[社群翻
-譯](https://publiccodenet.github.io/community-translations-standard/)
-* 公部門開源程式基底的《[標準遵循自我評
-估](https://publiccodenet.github.io/assessment-eligibility/)》
-* Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清
-單](/docs/review-template.html)》
+* 本標準非官方的其他語言[社群翻譯](https://publiccodenet.github.io/community-translations-standard/)
+* 公部門開源程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)》
+* Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清單](/docs/review-template.html)》

From 788c58619269db45ec545d019141088b958f7af3 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Sat, 16 Sep 2023 03:59:05 +0000
Subject: [PATCH 58/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 67 +++++++++++++------------
 1 file changed, 34 insertions(+), 33 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 511cfdaf..5adfa0eb 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-16 03:32+0000\n"
+"PO-Revision-Date: 2023-09-17 09:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -568,7 +568,7 @@ msgstr "釐清非開放標準在程式基底中的角色。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Additional guidance about build-time and runtime dependencies."
-msgstr "加入建置時期與執行時期依賴項目的額外指引。"
+msgstr "加入組建日期與執行時期依賴項目的額外指引。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
@@ -1418,9 +1418,9 @@ msgid ""
 "[Foundation for Public Code](https://publiccode.net/). We decide if a "
 "codebase is ready for community co-development based on this document."
 msgstr ""
-"本標準是 [Foundation for Public Code](https://publiccode.net/) 在監督程式基底"
-"盡職管理時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共"
-"同參與開發。"
+"本標準是 [Foundation for Public Code](https://publiccode.net/) 在為程式基底提"
+"供督導時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共同"
+"參與開發。"
 
 #: ./GOVERNANCE.md:block 5 (paragraph)
 msgid "The standard is maintained by Foundation for Public Code staff."
@@ -1554,7 +1554,7 @@ msgid ""
 msgstr ""
 "若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 "
 "Foundation for Public Code "
-"的程式基底管事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
+"的程式基底執事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -2531,7 +2531,7 @@ msgid ""
 "codebase?"
 msgstr ""
 "嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例"
-"來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這個程式基底"
+"來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這套程式基底"
 "？"
 
 #: ./criteria/document-the-code.md:block 14 (unordered list)
@@ -2653,7 +2653,7 @@ msgid ""
 "It is OPTIONAL for contributors to sign their commits and provide an email "
 "address, so that future contributors are able to contact past contributors "
 "with questions about their work."
-msgstr "貢獻者「可選擇」是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對"
+msgstr "貢獻者「可選擇」是否對送交內容作簽章，並附上電子郵件信箱，以便當未來貢獻者對"
 "其內容有疑問時，可以與之前的貢獻者聯絡。"
 
 #: ./criteria/maintain-version-control.md:block 10 (unordered list)
@@ -2755,7 +2755,7 @@ msgstr "送交版次訊息要寫清楚，方便之後比較各版本。"
 msgid ""
 "Work with policy makers to describe how the source code was updated after a "
 "policy change."
-msgstr "在政策改變以後與政策制定者合作，說明原始碼更新的內容。"
+msgstr "在政策改變以後，與政策制定者合作說明原始碼更新的部分。"
 
 #: ./criteria/maintain-version-control.md:block 19 (unordered list)
 msgid ""
@@ -2826,8 +2826,8 @@ msgstr "程式基底「必須」有個可以公開接受任何人建議的議題
 msgid ""
 "The documentation MUST link to both the public issue tracker and submitted "
 "codebase changes, for example in a `README` file."
-msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及提交的程式基底變動的連結，例如"
-"記錄在「`README`」檔案中。"
+msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及已提交的程式基底變動的連結，例"
+"如記錄在「`README`」檔案中。"
 
 #: ./criteria/make-contributing-easy.md:block 8 (unordered list)
 msgid ""
@@ -2866,7 +2866,7 @@ msgstr "確認可以使用程式基底中提到的管道，與其他使用者以
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid "Confirm that there is a closed channel for reporting security issues."
-msgstr "確認有封閉的管道通報安全性問題。"
+msgstr "確認有封閉的管道可通報安全性問題。"
 
 #: ./criteria/make-contributing-easy.md:block 10 (unordered list)
 msgid ""
@@ -2954,7 +2954,7 @@ msgid ""
 "hoping it is found does not work, instead proactiveness is needed."
 msgstr ""
 "一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得"
-"到它。不能只是發表個程式基底，然後就盼望他人找得到這個程式基底，更需要主動積"
+"到它。不能只是發表個程式基底，然後就盼望他人找得到這套程式基底，更需要主動積"
 "極。"
 
 #: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
@@ -3184,10 +3184,10 @@ msgid ""
 "provoke exploration into what the codebase equivalent would be."
 msgstr ""
 "GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR "
-"科學資料管理與盡職監督指導原則](https://www.go-fair.org/fair-principles/)》，"
-"提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行"
-"動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直"
-"接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。"
+"科學資料管理與監督指導原則](https://www.go-fair.org/fair-principles/)》，提供"
+"一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（"
+"也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套"
+"用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
 msgid "order: 3 redirect_from:"
@@ -3284,8 +3284,8 @@ msgstr "程式基底開發「應該」由多方單位協作。"
 msgid ""
 "Configuration SHOULD be used to make [source code](../glossary.md#source-"
 "code) adapt to context specific needs."
-msgstr "「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code) "
-"調整成能適應各情境的特定需求。"
+msgstr "「應該」使用組態設定方式以將[原始碼](../glossary.md#source-"
+"code)調整成能適應各情境的特定需求。"
 
 #: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
 #: list)
@@ -3595,7 +3595,7 @@ msgstr "制定抑制採購非開放原始碼授權程式碼，與非開放科技
 msgid ""
 "Only work with open source vendors that deliver their source code by "
 "publishing it under an open source license."
-msgstr "只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。"
+msgstr "只與能採用開放原始碼授權交付、與發行其原始碼的開放原始碼軟體供應商合作。"
 
 #: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
 msgid ""
@@ -4027,7 +4027,7 @@ msgid ""
 " state of the [codebase](../glossary.md#codebase)."
 msgstr ""
 "以文件記錄程式基底的[持續整合](../glossary.md#continuous-integration)工作流程"
-"，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監督[程式基底](../glossary."
+"，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監管[程式基底](../glossary."
 "md#codebase)狀態變得更為簡單。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
@@ -4064,7 +4064,7 @@ msgstr "程式基底指引「應該」指出，每次的貢獻內容都只應聚
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid "Source code test and documentation coverage SHOULD be monitored."
-msgstr "「應該」監督原始碼測試與文件的涵蓋範圍。"
+msgstr "「應該」監管原始碼測試與文件的涵蓋範圍。"
 
 #: ./criteria/use-continuous-integration.md:block 10 (unordered list)
 msgid ""
@@ -4404,7 +4404,8 @@ msgid ""
 "where [policy](../glossary.md#policy) is machine interpreted as code."
 msgstr ""
 "所有[原始碼](../glossary.md#source-"
-"code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀當作程式碼的部分則除外。"
+"code)都「必須」使用英語編寫，其中[政策](../glossary."
+"md#policy)是由機器解讀當作程式碼的部分則除外。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4434,7 +4435,7 @@ msgid ""
 "2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
 msgstr ""
 "根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/"
-"?showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。"
+"?showtechniques=315#readable)》的建議，文件內容「應該」以國中識讀程度為主。"
 
 #: ./criteria/use-plain-english.md:block 10 (unordered list)
 msgid ""
@@ -4672,7 +4673,7 @@ msgstr "如果社群對於治理架構應該如何改變有共識，則應該將
 msgid ""
 "If needed, make sure you have allocated budget for the contributions review "
 "process as agreed by the codebase community."
-msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且通過程式基底社群同意。"
+msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且經過程式基底社群同意。"
 
 #: ./criteria/welcome-contributors.md:block 14 (unordered list)
 msgid ""
@@ -5039,7 +5040,7 @@ msgid ""
 " session](https://about.publiccode.net/activities/standard-"
 "maintenance/backlog-pruning.html)."
 msgstr ""
-"程式基底管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://"
+"程式基底執事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://"
 "about.publiccode.net/activities/standard-maintenance/backlog-pruning."
 "html)環節的一部份。"
 
@@ -5139,7 +5140,7 @@ msgid ""
 "Anyone developing public-purpose software or policy can use this standard to"
 " work towards higher quality public services that are more cost effective, "
 "with less risk and more control."
-msgstr "任何想開發具有公眾用途的軟體或政策的人，可以利用此標準來提升公共服務品質，使"
+msgstr "任何想開發具有公眾用途的軟體或政策的人，可以利用本標準來提升公共服務品質，使"
 "其更具成本效益、風險更低，還能對系統更有掌控權。"
 
 #: ./foreword.md:block 8 (paragraph)
@@ -5606,7 +5607,7 @@ msgstr "參與我們"
 msgid ""
 "This standard is a living document. [Read our contributor "
 "guide](/CONTRIBUTING.md) to learn how you can make it better."
-msgstr "本標準是持續成長的文件。[請讀我們的《貢獻者指引》](/CONTRIBUTING."
+msgstr "本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING."
 "md)，瞭解您可以怎麼做來讓本標準變得更好。"
 
 #: ./foreword.md:block 66 (header)
@@ -5643,7 +5644,7 @@ msgstr ""
 
 #: ./glossary.md:block 6 (header)
 msgid "Codebase"
-msgstr "程式基底"
+msgstr "程式基底 (Codebase)"
 
 #: ./glossary.md:block 7 (paragraph)
 msgid ""
@@ -5826,7 +5827,7 @@ msgstr ""
 
 #: ./glossary.md:block 34 (header)
 msgid "Source Code"
-msgstr "原始碼"
+msgstr "原始碼 (Source Code)"
 
 #: ./glossary.md:block 35 (paragraph)
 msgid ""
@@ -5916,7 +5917,7 @@ msgstr "目次"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
-msgstr "[讀者指引：如何解讀此標準](readers-guide.md)"
+msgstr "[讀者指引：如何解讀本標準](readers-guide.md)"
 
 #: ./index.md:block 11 (unordered list)
 msgid "[Glossary](glossary.md)"
@@ -6011,7 +6012,7 @@ msgid ""
 "review"
 msgstr ""
 "Foundation for Public Code "
-"管事人員審查程式基底時所使用的《[本標準準則檢查清單](https://github.com/"
+"執事人員審查程式基底時所使用的《[本標準準則檢查清單](https://github.com/"
 "publiccodenet/standard/blob/develop/docs/review-template.html)》"
 
 #: ./readers-guide.md:block 3 (header)
@@ -6310,5 +6311,5 @@ msgid ""
 "[Standard criteria checklist](/docs/review-template.html) used by Foundation"
 " for Public Code stewards for codebase review"
 msgstr ""
-"Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清單](/"
+"Foundation for Public Code 執事人員用於程式基底審查的《[標準準則檢查清單](/"
 "docs/review-template.html)》"

From 297cdd2f5ff2c621d7e8a7948aa792f0d3a994ef Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Mon, 18 Sep 2023 15:23:46 +0000
Subject: [PATCH 59/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 153 +++++++++++-------------
 1 file changed, 70 insertions(+), 83 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 5adfa0eb..5fe9ad2f 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-17 09:44+0000\n"
+"PO-Revision-Date: 2023-09-19 15:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -535,8 +535,7 @@ msgstr "重新編寫「得以」等級的相關規定，加入使用「可選擇
 msgid ""
 "Expressed intent that the Standard for Public Code should meet its own "
 "requirements where applicable and added assessment."
-msgstr "表達《Standard for Public "
-"Code》應該盡可能符合其自身規定的立場，並加入評估措施。"
+msgstr "表達《公共程式標準》應該盡可能符合其自身規定的立場，並加入評估措施。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Add SPDX license identifiers to files."
@@ -572,7 +571,7 @@ msgstr "加入組建日期與執行時期依賴項目的額外指引。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Added roadmap for the development of the Standard for Public Code."
-msgstr "新增《Standard for Public Code》的發展路線圖。"
+msgstr "新增《公共程式標準》的發展路線圖。"
 
 #: ./CHANGELOG.md:block 19 (unordered list)
 msgid "Update structure of Authors file."
@@ -1206,10 +1205,10 @@ msgid ""
 "[standards](#standards-to-follow) and remains coherent with the overall "
 "work."
 msgstr ""
-"貢獻內容應該[遵守](docs/standard-for-public-code.html)《Standard for Public C"
-"ode》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值]"
-"(foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標準"
-"](#standards-to-follow)，且與整體作品有所連貫。"
+"貢獻內容應該[遵守](docs/standard-for-public-code.html)《公共程式標準》自身所"
+"列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值](foreword."
+"md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標準](#standards-"
+"to-follow)，且與整體作品有所連貫。"
 
 #: ./CONTRIBUTING.md:block 16 (paragraph)
 msgid ""
@@ -1257,7 +1256,7 @@ msgstr "適用政策"
 msgid ""
 "Currently, the Standard for Public Code is not implementing any specific "
 "public policy."
-msgstr "就目前而言，《Standard for Public Code》並非在執行任何特定的公共政策。"
+msgstr "就目前而言，《公共程式標準》並非在執行任何特定的公共政策。"
 
 #: ./CONTRIBUTING.md:block 21 (header)
 msgid "Style"
@@ -1274,11 +1273,11 @@ msgid ""
 "also have a separate quality check before [making a new "
 "release](docs/releasing.md)."
 msgstr ""
-"《Standard for Public Code》目標[使用白話的英語](criteria/use-plain-english.m"
-"d)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓"
-"「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容"
-"上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查"
-"品質才[推出新發行版本](docs/releasing.md)。"
+"《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採"
+"用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸"
+"出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔"
+"心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新"
+"發行版本](docs/releasing.md)。"
 
 #: ./CONTRIBUTING.md:block 23 (header)
 msgid "Standards to follow"
@@ -1289,8 +1288,8 @@ msgid ""
 "These are the standards that the Standard for Public Code uses. Please make "
 "sure that your contributions are aligned with them so that they can be "
 "merged more easily."
-msgstr "這些是《Standard for Public "
-"Code》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。"
+msgstr "這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更"
+"容易合併。"
 
 #: ./CONTRIBUTING.md:block 25 (unordered list)
 msgid ""
@@ -1377,8 +1376,8 @@ msgid ""
 "maintain existing and add new [community translations of the "
 "Standard](https://github.com/publiccodenet/community-translations-standard)."
 msgstr ""
-"《Standard for Public Code》沒有官方版本的翻譯，您仍可以協助本標準維護已有的["
-"社群翻譯](https://github.com/publiccodenet/community-translations-"
+"《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](ht"
+"tps://github.com/publiccodenet/community-translations-"
 "standard)，或是新增翻譯。"
 
 #: ./CONTRIBUTING.md:block 37 (header)
@@ -1437,10 +1436,8 @@ msgstr "[我們歡迎任何人貢獻，例如提供修改建議，或是給予
 msgid ""
 "Because of the important role that the Standard for Public Code has in our "
 "core process we require the highest standards from the Standard."
-msgstr ""
-"由於《Standard for Public "
-"Code》在我們的核心流程中，扮演至關重要的角色，所以我們會以《Standard for "
-"Public Code》的最高標準作要求。"
+msgstr "由於《公共程式標準》在我們的核心流程中，扮演至關重要的角色，所以我們會以《公"
+"共程式標準》的最高標準作要求。"
 
 #: ./GOVERNANCE.md:block 8 (paragraph)
 msgid ""
@@ -1454,7 +1451,7 @@ msgstr ""
 
 #: ./README.md:block 1 (header)
 msgid "Standard for Public Code"
-msgstr "Standard for Public Code"
+msgstr "公共程式標準"
 
 #: ./README.md:block 3 (paragraph)
 msgid ""
@@ -1463,9 +1460,8 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"《Standard for Public Code》提供公家機關一套準備開源解決方案的模型，讓他們能"
-"與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供"
-"應商的指引。"
+"《公共程式標準》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相"
+"似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -1511,12 +1507,12 @@ msgid ""
 "The Standard for Public Code is in a draft format. We are preparing it for a"
 " version 1.0 release. Currently, we are testing it on a small number of "
 "codebases."
-msgstr "《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 "
+msgstr "《公共程式標準》目前為草稿階段。我們正在準備發行 1.0 "
 "版，目前仍在幾個程式基底中作測試。"
 
 #: ./README.md:block 7 (header)
 msgid "Applying the Standard for Public Code to your codebase"
-msgstr "將《Standard for Public Code》套用到您的程式基底"
+msgstr "將《公共程式標準》套用到您的程式基底"
 
 #: ./README.md:block 8 (paragraph)
 msgid ""
@@ -1527,9 +1523,9 @@ msgid ""
 "will give you a rough idea of how much work you may need to do to meet all "
 "criteria."
 msgstr ""
-"若您想要將《Standard for Public Code》套用到您的程式基底，就請放心去做，因為"
-"它是人人都能自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資"
-"格評估](https://publiccodenet.github.io/assessment-"
+"若您想要將《公共程式標準》套用到您的程式基底，就請放心去做，因為它是人人都能"
+"自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資格評估](http"
+"s://publiccodenet.github.io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 #: ./README.md:block 9 (paragraph)
@@ -1552,9 +1548,8 @@ msgid ""
 "Public Code, the codebase stewards at the Foundation for Public Code will "
 "help any implementers of the standard understand how the gaps can be closed."
 msgstr ""
-"若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 "
-"Foundation for Public Code "
-"的程式基底執事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
+"若新版的《公共程式標準》有任何導致過去作法不再適用的改動，則 Foundation for "
+"Public Code 的程式基底執事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
 
 #: ./README.md:block 11 (paragraph)
 msgid ""
@@ -1608,9 +1603,9 @@ msgid ""
 "hands](https://img.youtube.com/vi/QWt6vB-"
 "cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
 msgstr ""
-"[![《Standard for Public "
-"Code》的影片縮圖：兩隻手中間放著本標準的印刷本](https://img.youtube.com/vi/"
-"QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+"[![《公共程式標準》的影片縮圖：兩隻手中間放著本標準的印刷本](https://img."
+"youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v"
+"=QWt6vB-cipE)"
 
 #: ./README.md:block 17 (paragraph)
 msgid ""
@@ -1618,9 +1613,8 @@ msgid ""
 "Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
 "Global Summit 2020 (4:12) on YouTube."
 msgstr ""
-"[《Standard for Public Code》的影片介紹](https://www.youtube.com/watch?v"
-"=QWt6vB-cipE)，出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube "
-"上。"
+"[《公共程式標準》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，"
+"出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。"
 
 #: ./README.md:block 18 (header)
 msgid "Help improve this standard"
@@ -1631,9 +1625,8 @@ msgid ""
 "The Foundation for Public Code is committed to maintaining and developing "
 "the Standard for Public Code at a level of quality that meets the standard "
 "itself."
-msgstr ""
-"Foundation for Public Code 致力於維護與開發《Standard for Public "
-"Code》，且使其同時符合該標準自身的品質水準。"
+msgstr "Foundation for Public Code "
+"致力於維護與開發《公共程式標準》，且使其同時符合該標準自身的品質水準。"
 
 #: ./README.md:block 20 (paragraph)
 msgid ""
@@ -1710,7 +1703,7 @@ msgstr ""
 
 #: ./README.md:block 30 (header)
 msgid "Generating a PDF of the Standard for Public Code"
-msgstr "生成《Standard for Public Code》的 PDF 檔案"
+msgstr "生成《公共程式標準》的 PDF 檔案"
 
 #: ./README.md:block 31 (paragraph)
 msgid ""
@@ -4740,9 +4733,8 @@ msgid ""
 "The printed Standard for Public Code is printed by Reclameland. This guide "
 "tries to provide the relevant information to print it there or somewhere "
 "else."
-msgstr ""
-"《Standard for Public Code》是由 Reclameland "
-"負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。"
+msgstr "《公共程式標準》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，"
+"方便您到 Reclameland 或其他地方印刷。"
 
 #: ./docs/printing.md:block 4 (paragraph)
 msgid ""
@@ -4805,7 +4797,7 @@ msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，
 
 #: ./docs/releasing.md:block 1 (header)
 msgid "Releasing a new version of the Standard for public code"
-msgstr "發行新版本的《Standard for Public Code》"
+msgstr "發行新版本的《公共程式標準》"
 
 #: ./docs/releasing.md:block 3 (ordered list)
 msgid "Review state of the 'develop' branch"
@@ -5132,8 +5124,7 @@ msgstr "序文"
 msgid ""
 "The Standard for Public Code is a set of criteria that support public "
 "organizations in developing and maintaining software and policy together."
-msgstr "《Standard for Public "
-"Code》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。"
+msgstr "《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。"
 
 #: ./foreword.md:block 7 (paragraph)
 msgid ""
@@ -5460,7 +5451,7 @@ msgstr ""
 
 #: ./foreword.md:block 47 (header)
 msgid "The goals for the Standard for Public Code"
-msgstr "《Standard for Public Code》目標"
+msgstr "《公共程式標準》目標"
 
 #: ./foreword.md:block 48 (paragraph)
 msgid ""
@@ -5497,13 +5488,12 @@ msgstr "以更好的經濟模型改善供應商關係"
 msgid ""
 "Potential users of codebases tested against the Standard for Public Code can"
 " expect them to be highly reusable, easily maintainable and of high quality."
-msgstr ""
-"如果有潛在使用者想採用經由《Standard for Public Code》測試過的程式基底，便可"
-"以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。"
+msgstr "如果有潛在使用者想採用經由《公共程式標準》測試過的程式基底，便可以預期這些程"
+"式基底具有方便重複利用、容易維護、高品質的特性。"
 
 #: ./foreword.md:block 51 (paragraph)
 msgid "The Standard for Public Code does this by:"
-msgstr "《Standard for Public Code》能有此效果是基於："
+msgstr "《公共程式標準》能有此效果是基於："
 
 #: ./foreword.md:block 52 (unordered list)
 msgid "setting out a common terminology for public code development"
@@ -5522,7 +5512,7 @@ msgstr "提出該如何符合準則並實作遵循的指引"
 #: ./foreword.md:block 53 (paragraph)
 msgid ""
 "The Standard for Public Code is meant to be time and technology independent."
-msgstr "《Standard for Public Code》設計精神就是要跨越時間與科技，不受其限制。"
+msgstr "《公共程式標準》設計精神就是要跨越時間與科技，不受其限制。"
 
 #: ./foreword.md:block 54 (header)
 msgid "Who this is for"
@@ -5532,7 +5522,7 @@ msgstr "適用對象"
 msgid ""
 "The Standard for Public Code is for the people who create and reuse public "
 "code:"
-msgstr "《Standard for Public Code》適用於開發與重複使用公共程式的人："
+msgstr "《公共程式標準》適用於開發與重複使用公共程式的人："
 
 #: ./foreword.md:block 56 (unordered list)
 msgid "public policy makers"
@@ -5866,8 +5856,7 @@ msgstr "政府開源協作指引"
 msgid ""
 "The Standard for Public Code is a set of criteria that supports public "
 "organizations in developing and maintaining software and policy together."
-msgstr "《Standard for Public "
-"Code》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。"
+msgstr "《公共程式標準》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。"
 
 #: ./index.md:block 6 (paragraph)
 msgid ""
@@ -5880,12 +5869,12 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
-"《Standard for Public Code》為那些在建構自身開源解決方案的公家機關提供指引，"
-"以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果"
-"。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《"
-"Standard for Public Code》支持公家機關透過協作方式，創造出好用、開放、易懂、"
-"課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的"
-"程式基底，小從市政府，大到超國家組織都行。"
+"《公共程式標準》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來"
+"能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵"
+"蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持"
+"公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這"
+"份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國"
+"家組織都行。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5893,14 +5882,14 @@ msgid ""
 "code)’ as open source software developed by public organizations, together "
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
-"《Standard for Public Code》將「[公共程式](glossary.md#public-code)」定義為："
-"由公家機關所開發的開源軟體，同時包含協作與重複使用所需的政策與指引。"
+"《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所"
+"開發的開源軟體，同時包含協作與重複使用所需的政策與指引。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
 "The criteria of the Standard for Public Code are aligned with guidelines and"
 " best practices of open source software development."
-msgstr "《Standard for Public Code》當中的準則，符合開源軟體開發的指引與最佳實務。"
+msgstr "《公共程式標準》當中的準則，符合開源軟體開發的指引與最佳實務。"
 
 #: ./index.md:block 9 (paragraph)
 msgid ""
@@ -6173,9 +6162,8 @@ msgid ""
 "implementations of a codebase. This means the standard does not tell "
 "implementers how to comply with their organization's local technical "
 "infrastructure or legal framework."
-msgstr ""
-"《Standard for Public Code》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標"
-"準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
+msgstr "《公共程式標準》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴"
+"實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
 
 #: ./readers-guide.md:block 27 (paragraph)
 msgid ""
@@ -6186,9 +6174,9 @@ msgid ""
 "Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
 "synergize well with them."
 msgstr ""
-"此外，雖然《Standard for Public Code》有引用一些標準，並且與其他標準有滿多重"
-"疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，"
-"像是 ISO 25000 認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF "
+"此外，雖然《公共程式標準》有引用一些標準，並且與其他標準有滿多重疊的部分，但"
+"本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，像是 ISO 25000 "
+"認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF "
 "最佳實務標章](https://github.com/coreinfrastructure/best-practices-"
 "badge)等，而是希望能與它們能良好協同搭配。"
 
@@ -6198,9 +6186,9 @@ msgid ""
 " that a community will spring into existence. That still requires "
 "proactiveness and ambition beyond making the codebase collaboration ready."
 msgstr ""
-"《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群"
-"。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到"
-"超越協作以外的企圖心。"
+"《公共程式標準》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社"
+"群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到超越協作以外"
+"的企圖心。"
 
 msgid ""
 "script/release-body.sh expects VERSION in the first second-level header"
@@ -6274,12 +6262,11 @@ msgid ""
 "eligibility) that will give you a rough idea of how much work you may need "
 "to do to meet all criteria."
 msgstr ""
-"若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它"
-"是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成《Standard for "
-"Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment "
-"徽章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要"
-"瞭解您程式基底所達成的程度，可以做[自我資格評估](https://publiccodenet.github"
-".io/assessment-"
+"若您想要將《公共程式標準》套用您的程式基底，就請放心去做，因為它是人人都能自"
+"由採用的開放標準。如果您希望宣傳程式基底社群達成《公共程式標準》準則要求時的"
+"熱誠，請使用 [standard-for-public-code-commitment 徽章](assets/standard-for-"
+"public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度"
+"，可以做[自我資格評估](https://publiccodenet.github.io/assessment-"
 "eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
 
 msgid "Update [`roadmap.md`](roadmap.md)"

From e9a2490e937f912db9c4ddab614143f76871cef8 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Mon, 2 Oct 2023 10:56:48 +0800
Subject: [PATCH 60/71] update translate

---
 CHANGELOG.md                                  |  6 ++--
 CONTRIBUTING.md                               | 15 ++++-----
 GOVERNANCE.md                                 |  6 ++--
 README.md                                     | 32 ++++++++-----------
 criteria/document-the-code.md                 |  2 +-
 criteria/maintain-version-control.md          |  4 +--
 criteria/make-contributing-easy.md            |  4 +--
 criteria/make-the-codebase-findable.md        |  4 +--
 ...make-the-codebase-reusable-and-portable.md |  2 +-
 criteria/publish-with-an-open-license.md      |  2 +-
 criteria/use-continuous-integration.md        |  4 +--
 criteria/use-plain-english.md                 |  6 ++--
 criteria/welcome-contributors.md              |  2 +-
 docs/printing.md                              |  3 +-
 docs/releasing.md                             |  2 +-
 docs/roadmap.md                               |  3 +-
 foreword.md                                   | 16 +++++-----
 glossary.md                                   |  4 +--
 index.md                                      | 17 +++++-----
 note.txt                                      |  7 ++++
 python/po2md.py                               |  6 ++--
 readers-guide.md                              | 11 +++----
 22 files changed, 76 insertions(+), 82 deletions(-)
 create mode 100644 note.txt

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1ec82c27..985d8bb3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -98,7 +98,7 @@
 * 移除可重複使用與移植的程式碼中多餘的規定。
 * 在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。
 * 重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。
-* 表達《Standard for Public Code》應該盡可能符合其自身規定的立場，並加入評估措施。
+* 表達《公共程式標準》應該盡可能符合其自身規定的立場，並加入評估措施。
 * 將 SPDX 授權識別碼加入檔案中。
 * 導入新的行為守則。
 * 解釋原始碼與政策內文的差異。
@@ -106,8 +106,8 @@
 * 告知程式基底成熟度對於重複使用時的重要性。
 * 將可查找性相關規定移動到新準則中。
 * 釐清非開放標準在程式基底中的角色。
-* 加入建置時期與執行時期依賴項目的額外指引。
-* 新增《Standard for Public Code》的發展路線圖。
+* 加入組建日期與執行時期依賴項目的額外指引。
+* 新增《公共程式標準》的發展路線圖。
 * 更新 Authors 檔案的結構。
 * 將唐鳳加入作者群。
 * 將準則列表加到印刷版本中。
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2c273a09..d30b2816 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -38,8 +38,8 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 ### 1. 作出您的修改
 
-貢獻內容應該[遵守](docs/standard-for-public-code.html)《Standard for Public Code》自身所列出的準則規
-定。審查人員同時也會確保貢獻內容，符合[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標
+貢獻內容應該[遵守](docs/standard-for-public-code.html)《公共程式標準》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合
+[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標
 準](#standards-to-follow)，且與整體作品有所連貫。
 
 本專案使用 [GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-model/)。
@@ -55,17 +55,15 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 #### 適用政策
 
-就目前而言，《Standard for Public Code》並非在執行任何特定的公共政策。
+就目前而言，《公共程式標準》並非在執行任何特定的公共政策。
 
 #### 風格
 
-《Standard for Public Code》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內
-容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審
-查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
+《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
 
 #### 遵守的標準
 
-這些是《Standard for Public Code》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。
+這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。
 
 * [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 要求等級關鍵字
 * [網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/#readable) - 易讀性
@@ -92,8 +90,7 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 ## 翻譯成其他語言
 
-《Standard for Public Code》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻
-譯](https://github.com/publiccodenet/community-translations-standard)，或是新增翻譯。
+《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](https://github.com/publiccodenet/community-translations-standard)，或是新增翻譯。
 
 ## 發行版本
 
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 635d303b..439a13fc 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -5,14 +5,12 @@
 
 # 治理方式
 
-本標準是 [Foundation for Public Code](https://publiccode.net/) 在監督程式基底盡職管理時的核心。我們依照這份文
-件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。
+本標準是 [Foundation for Public Code](https://publiccode.net/) 在為程式基底提供督導時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。
 
 這份標準由 Foundation for Public Code 職員負責維護。
 
 [我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。](/CONTRIBUTING.md)
 
-由於《Standard for Public Code》在我們的核心流程中，扮演至關重要的角色，所以我們會以《Standard for Public Code》的最
-高標準作要求。
+由於《公共程式標準》在我們的核心流程中，扮演至關重要的角色，所以我們會以《公共程式標準》的最高標準作要求。
 
 我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯。
diff --git a/README.md b/README.md
index 539363d3..faddd13f 100644
--- a/README.md
+++ b/README.md
@@ -1,10 +1,9 @@
-# Standard for Public Code
+# 公共程式標準
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-《Standard for Public Code》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、
-開發人員與供應商的指引。
+《公共程式標準》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。
 
 ![version 0.7.1](assets/version-badge.svg) [![License:
 CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
@@ -19,23 +18,20 @@ badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.p
 [![standard develop
 badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
 
-《Standard for Public Code》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。
+《公共程式標準》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。
 
-## 將《Standard for Public Code》套用到您的程式基底
+## 將《公共程式標準》套用到您的程式基底
 
-若您想要將《Standard for Public Code》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成
-《Standard for Public Code》準則要求時的熱誠，請使用 [standard-for-public-code-commitment 徽
-章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度，可以做[自
-我資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有
+若您想要將《公共程式標準》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成《公共程式標準》準則要求時的熱誠，請使
+用 [standard-for-public-code-commitment 徽章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度，可以做[自我資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有
 準則，還需要下多少功夫。
 
 本標準 *應該* 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要
-一點靈感啟發，請參閱[社群製作的《實踐指
-引》](https://publiccodenet.github.io/community-implementation-guide-standard/)，其中包
+一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet.github.io/community-implementation-guide-standard/)，其中包
 括範例與其他提示。
 
-若新版的《Standard for Public Code》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的程式基底管
-事人員，會協助標準的實踐者理解該如何銜接之間的落差。
+若新版的《公共程式標準》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的程式基底執事人員，會協助標準的實踐者理解該如何
+銜接之間的落差。
 
 若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
 [info@publiccode.net](mailto:info@publiccode.net)，以展開正式[評
@@ -50,16 +46,16 @@ badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.p
 本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。請參閱
 [`index.md`](index.md) 查看整體內容概覽。
 
-[![《Standard for Public Code》的影片縮圖：兩隻手中間放著本標準的印刷
+[![《公共程式標準》的影片縮圖：兩隻手中間放著本標準的印刷
 本](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?
 v=QWt6vB-cipE)
 
-[《Standard for Public Code》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，出自
-Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。
+[《公共程式標準》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，出自 Creative Commons
+Global Summit 2020 (4:12)，放在 YouTube 上。
 
 ## 幫忙改善這份標準
 
-Foundation for Public Code 致力於維護與開發《Standard for Public Code》，且使其同時符合該標準自身的品質水準。
+Foundation for Public Code 致力於維護與開發《公共程式標準》，且使其同時符合該標準自身的品質水準。
 
 我們正在尋找像您這樣的人，能對此專案做出[貢獻](CONTRIBUTING.md)，像是建議改善方向，以及協助開發等。😊若要開始，請先參閱我們的[貢獻者指
 引](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。[治理方式聲明](GOVERNANCE.md)中有說明管理該標準的
@@ -88,7 +84,7 @@ sudo apt-get install -y ruby ruby-bundler
 請前往 [script](https://github.com/publiccodenet/standard/tree/main/script) 資料夾查看命令
 稿。
 
-### 生成《Standard for Public Code》的 PDF 檔案
+### 生成《公共程式標準》的 PDF 檔案
 
 除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 [Weasyprint](https://weasyprint.org/) 和
 [QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/) 則可將 PDF 檔轉換成
diff --git a/criteria/document-the-code.md b/criteria/document-the-code.md
index 37c0cc2b..8247db71 100644
--- a/criteria/document-the-code.md
+++ b/criteria/document-the-code.md
@@ -41,7 +41,7 @@ redirect_from:
 
 ## 管理人員：需要的工作
 
-* 嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這個程式基底？
+* 嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這套程式基底？
 * 確保您同時瞭解政策、原始碼以及文件內容。
 
 ## 開發人員與設計師：需要的工作
diff --git a/criteria/maintain-version-control.md b/criteria/maintain-version-control.md
index 5e89f08f..bb9c58d2 100644
--- a/criteria/maintain-version-control.md
+++ b/criteria/maintain-version-control.md
@@ -21,7 +21,7 @@ redirect_from:
 * 貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。
 * 維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版本。
 * 貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。
-* 貢獻者「可選擇」是否在提交內容中簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
+* 貢獻者「可選擇」是否對送交內容作簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。
 
 ## 測試方式
 
@@ -51,7 +51,7 @@ redirect_from:
 * 送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。
 * 使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。
 * 送交版次訊息要寫清楚，方便之後比較各版本。
-* 在政策改變以後與政策制定者合作，說明原始碼更新的內容。
+* 在政策改變以後，與政策制定者合作說明原始碼更新的部分。
 
 ## 延伸閱讀
 
diff --git a/criteria/make-contributing-easy.md b/criteria/make-contributing-easy.md
index b00506aa..67597241 100644
--- a/criteria/make-contributing-easy.md
+++ b/criteria/make-contributing-easy.md
@@ -13,7 +13,7 @@ order: 5
 ## 需求規定
 
 * 程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。
-* 文件中「必須」同時有公開的議題追蹤器連結，以及提交的程式基底變動的連結，例如記錄在「`README`」檔案中。
+* 文件中「必須」同時有公開的議題追蹤器連結，以及已提交的程式基底變動的連結，例如記錄在「`README`」檔案中。
 * 程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。
 * 「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。
 * 文件「必須」說明，該如何通報潛在的安全性與敏感性問題。
@@ -23,7 +23,7 @@ order: 5
 * 確認有公開的議題追蹤器。
 * 確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。
 * 確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。
-* 確認有封閉的管道通報安全性問題。
+* 確認有封閉的管道可通報安全性問題。
 * 確認有說明如何私下通報安全性問題。
 
 ## 公共政策制定者：需要的工作
diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index a6da5cdb..51f03bb9 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -8,7 +8,7 @@ redirect_from:
 
 # 程式基底可查詢得到
 
-一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個程式基底，然後就盼望他人找得到這個程式基
+一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個程式基底，然後就盼望他人找得到這套程式基
 底，更需要主動積極。
 
 有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體
@@ -69,6 +69,6 @@ redirect_from:
 * Wikidata 維基數據社群《[維基數據簡
 介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
 * FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。
-* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR 科學資料管理與盡職監督指導原
+* GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR 科學資料管理與監督指導原
 則](https://www.go-fair.org/fair-principles/)》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
 機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。
diff --git a/criteria/make-the-codebase-reusable-and-portable.md b/criteria/make-the-codebase-reusable-and-portable.md
index ffe750ed..af6fca59 100644
--- a/criteria/make-the-codebase-reusable-and-portable.md
+++ b/criteria/make-the-codebase-reusable-and-portable.md
@@ -27,7 +27,7 @@ redirect_from:
 * 程式基底「應該」有多方單位使用。
 * 發展路線圖「應該」有多方單位的需求影響。
 * 程式基底開發「應該」由多方單位協作。
-* 「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code) 調整成能適應各情境的特定需求。
+* 「應該」使用組態設定方式以將[原始碼](../glossary.md#source-code)調整成能適應各情境的特定需求。
 * 程式基底「應該」能夠在地化。
 * 原始碼與其文件「不應該」包含特定情況專用的資訊。
 * 程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。
diff --git a/criteria/publish-with-an-open-license.md b/criteria/publish-with-an-open-license.md
index 36a0e6ea..2c8f1cf9 100644
--- a/criteria/publish-with-an-open-license.md
+++ b/criteria/publish-with-an-open-license.md
@@ -40,7 +40,7 @@ redirect_from:
 
 ## 管理人員：需要的工作
 
-* 只與能採用開放原始碼授權交付與發行其原始碼的開放原始碼軟體供應商合作。
+* 只與能採用開放原始碼授權交付、與發行其原始碼的開放原始碼軟體供應商合作。
 * 請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」
 的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。
 
diff --git a/criteria/use-continuous-integration.md b/criteria/use-continuous-integration.md
index 5a855522..9559693f 100644
--- a/criteria/use-continuous-integration.md
+++ b/criteria/use-continuous-integration.md
@@ -13,7 +13,7 @@ redirect_from:
 自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。
 
 以文件記錄程式基底的[持續整合](../glossary.md#continuous-integration)工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓
-監督[程式基底](../glossary.md#codebase)狀態變得更為簡單。
+監管[程式基底](../glossary.md#codebase)狀態變得更為簡單。
 
 ## 需求規定
 
@@ -23,7 +23,7 @@ redirect_from:
 * 程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。
 * 「應該」公開貢獻內容的自動化測試結果。
 * 程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。
-* 「應該」監督原始碼測試與文件的涵蓋範圍。
+* 「應該」監管原始碼測試與文件的涵蓋範圍。
 * 「可選擇」是否測試[政策](../glossary.md#policy)和文件，與原始碼之間有無一致性，或是反之亦然。
 * 「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。
 * 「可選擇」是否使用文件中的範例來測試軟體。
diff --git a/criteria/use-plain-english.md b/criteria/use-plain-english.md
index 0666f51f..a478fe36 100644
--- a/criteria/use-plain-english.md
+++ b/criteria/use-plain-english.md
@@ -17,13 +17,13 @@ redirect_from:
 ## 需求規定
 
 * 程式基底的所有文件都「必須」使用英語。
-* 所有[原始碼](../glossary.md#source-code)都必須使用英語編寫，其中[政策](../glossary.md#policy)是由機器解讀
-當作程式碼的部分則除外。
+* 所有[原始碼](../glossary.md#source-code)都「必須」使用英語編寫，其中[政策](../glossary.md#policy)是由機器
+解讀當作程式碼的部分則除外。
 * 任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。
 * 任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。
 * 程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。
 * 根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/?
-showtechniques=315#readable)》的建議，文件內容應該以國中識讀程度為主。
+showtechniques=315#readable)》的建議，文件內容「應該」以國中識讀程度為主。
 * 「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。
 
 ## 測試方式
diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index 83de6e1b..59fefa12 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -42,7 +42,7 @@ redirect_from:
 
 * 確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。
 * 如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。
-* 若有需要，確認您有編列貢獻內容審查流程的預算，且通過程式基底社群同意。
+* 若有需要，確認您有編列貢獻內容審查流程的預算，且經過程式基底社群同意。
 * 確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參與的時間長度等。
 * 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
 
diff --git a/docs/printing.md b/docs/printing.md
index 5fb3d9f8..abb13962 100644
--- a/docs/printing.md
+++ b/docs/printing.md
@@ -3,8 +3,7 @@
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-《Standard for Public Code》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方
-印刷。
+《公共程式標準》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。
 
 印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）：
 
diff --git a/docs/releasing.md b/docs/releasing.md
index 2d915574..0ab61c4e 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -1,4 +1,4 @@
-# 發行新版本的《Standard for Public Code》
+# 發行新版本的《公共程式標準》
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 3468d5f9..55f132de 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -7,8 +7,7 @@
 
 本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。
 
-程式基底管事人員每月會定期審查發展路線圖，這是我們[積累事項修整作
-業](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
+程式基底執事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
 環節的一部份。
 
 ## 目前任務
diff --git a/foreword.md b/foreword.md
index d4c3fe7c..952099a2 100644
--- a/foreword.md
+++ b/foreword.md
@@ -6,9 +6,9 @@ redirect_from:
 ---
 # 序文
 
-《Standard for Public Code》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。
+《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。
 
-任何想開發具有公眾用途的軟體或政策的人，可以利用此標準來提升公共服務品質，使其更具成本效益、風險更低，還能對系統更有掌控權。
+任何想開發具有公眾用途的軟體或政策的人，可以利用本標準來提升公共服務品質，使其更具成本效益、風險更低，還能對系統更有掌控權。
 
 本序文在介紹何謂「公共程式」以及解說其重要性。
 
@@ -107,7 +107,7 @@ redirect_from:
 若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服
 務內容或預期成果。
 
-## 《Standard for Public Code》目標
+## 《公共程式標準》目標
 
 本標準在於支持開發人員、設計師、管理人員、公共政策制定者：
 
@@ -117,19 +117,19 @@ redirect_from:
 * 更能精細控制其 IT 系統粒度，並做出系統相關決策
 * 以更好的經濟模型改善供應商關係
 
-如果有潛在使用者想採用經由《Standard for Public Code》測試過的程式基底，便可以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。
+如果有潛在使用者想採用經由《公共程式標準》測試過的程式基底，便可以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。
 
-《Standard for Public Code》能有此效果是基於：
+《公共程式標準》能有此效果是基於：
 
 * 為公共程式開發訂立通用術語
 * 制定措施協助高品質公共程式的開發
 * 提出該如何符合準則並實作遵循的指引
 
-《Standard for Public Code》設計精神就是要跨越時間與科技，不受其限制。
+《公共程式標準》設計精神就是要跨越時間與科技，不受其限制。
 
 ### 適用對象
 
-《Standard for Public Code》適用於開發與重複使用公共程式的人：
+《公共程式標準》適用於開發與重複使用公共程式的人：
 
 * 公共政策制定者
 * 業務與專案經理
@@ -156,7 +156,7 @@ v=QHFkD4xfd6c)。討論採購、法律等主題。
 
 ## 參與我們
 
-本標準是持續成長的文件。[請讀我們的《貢獻者指引》](/CONTRIBUTING.md)，瞭解您可以怎麼做來讓本標準變得更好。
+本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING.md)，瞭解您可以怎麼做來讓本標準變得更好。
 
 ## 聯絡方式
 
diff --git a/glossary.md b/glossary.md
index 7c636dd8..b20fa5a6 100644
--- a/glossary.md
+++ b/glossary.md
@@ -10,7 +10,7 @@
 任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是由機器執
 行。
 
-## 程式基底
+## 程式基底 (Codebase)
 
 任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、測試與文件等的整套內容。
 
@@ -70,7 +70,7 @@
 
 儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。
 
-## 原始碼
+## 原始碼 (Source Code)
 
 人類可讀，並且能夠翻譯成機器指令的電腦程式文字。
 
diff --git a/index.md b/index.md
index 0030069c..7b74709b 100644
--- a/index.md
+++ b/index.md
@@ -5,23 +5,22 @@ toc: false
 ---
 # 政府開源協作指引
 
-《Standard for Public Code》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。
+《公共程式標準》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。
 
-《Standard for Public Code》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使
-用各自的成果。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《Standard for Public Code》支持公家機關透過協作方式，創造
-出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。
+《公共程式標準》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵蓋寫給政策制
+定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是
+要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。
 
-《Standard for Public Code》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開源軟體，同時包含
-協作與重複使用所需的政策與指引。
+《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開源軟體，同時包含協作與重複使用所需的政策與指引。
 
-《Standard for Public Code》當中的準則，符合開源軟體開發的指引與最佳實務。
+《公共程式標準》當中的準則，符合開源軟體開發的指引與最佳實務。
 
 {% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序
 文](foreword.md)。 {% endif%}{% endfor %}
 
 ## 目次
 
-* [讀者指引：如何解讀此標準](readers-guide.md)
+* [讀者指引：如何解讀本標準](readers-guide.md)
 * [詞彙表](glossary.md)
 * [準則](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in
 sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{%
@@ -44,4 +43,4 @@ if page.title %}
 
 * 本標準非官方的其他語言[社群翻譯](https://publiccodenet.github.io/community-translations-standard/)
 * 公部門開源程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)》
-* Foundation for Public Code 管事人員用於程式基底審查的《[標準準則檢查清單](/docs/review-template.html)》
+* Foundation for Public Code 執事人員用於程式基底審查的《[標準準則檢查清單](/docs/review-template.html)》
diff --git a/note.txt b/note.txt
new file mode 100644
index 00000000..5b6150cb
--- /dev/null
+++ b/note.txt
@@ -0,0 +1,7 @@
+(use docker)
+1. 切換branch: i18n
+2. 更新翻譯: git pull
+3. 合併到: branch: ru8tp6
+4. 執行腳本: po2md.py(移除上一次的_site)
+5. 處理jekyll-theme
+6. 用github, git remote fetch
\ No newline at end of file
diff --git a/python/po2md.py b/python/po2md.py
index 039d5145..3cd0cd10 100644
--- a/python/po2md.py
+++ b/python/po2md.py
@@ -15,11 +15,11 @@ def main():
     # 2. filter origin file
     md_files = [file for file in md_files if not file.startswith(SOURCE_FOLDER)]
 
-    # 3A. backup md file (複製一次)
-    backup_md_files(md_files)
+    # 3A. backup md file (只有主程式更新的時候，才需要複製一次)
+    # backup_md_files(md_files)
 
     # 3B. restore md file
-    # restore_md_files(md_files)
+    restore_md_files(md_files)
 
     # 4. run po2md
     for file in md_files:
diff --git a/readers-guide.md b/readers-guide.md
index cef7591a..62c20c45 100644
--- a/readers-guide.md
+++ b/readers-guide.md
@@ -59,13 +59,12 @@
 
 ## 作用範圍限制
 
-《Standard for Public Code》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或
-法律框架。
+《公共程式標準》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。
 
-此外，雖然《Standard for Public Code》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代
-品質標準，像是 ISO 25000 認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF 最佳實務標
+此外，雖然《公共程式標準》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，像是 ISO 25000
+認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF 最佳實務標
 章](https://github.com/coreinfrastructure/best-practices-badge)等，而是希望能與它們能良好協同搭
 配。
 
-《Standard for Public Code》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主
-動，以及做到超越協作以外的企圖心。
+《公共程式標準》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到超越協作以外的企圖
+心。

From 0ddda2d18afb4fb185cd925c11c26da0e1fd1d19 Mon Sep 17 00:00:00 2001
From: Cheng-Chia Tseng <zerngjia@gmail.com>
Date: Tue, 3 Oct 2023 16:40:05 +0000
Subject: [PATCH 61/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 5fe9ad2f..cb88757d 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-09-19 15:44+0000\n"
+"PO-Revision-Date: 2023-10-04 16:44+0000\n"
 "Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -1115,7 +1115,7 @@ msgid ""
 "[info@publiccode.net](mailto:info@publiccode.net)."
 msgstr ""
 "我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，"
-"也歡迎將意見回饋用電子郵件計送到 [info@publiccode.net](mailto:info@publiccode"
+"也歡迎將意見回饋用電子郵件寄送到 [info@publiccode.net](mailto:info@publiccode"
 ".net)。"
 
 #: ./CONTRIBUTING.md:block 6 (header)
@@ -5749,7 +5749,7 @@ msgstr "在本標準當中，「政策」一詞指的是公家機關，例如政
 
 #: ./glossary.md:block 25 (header)
 msgid "Public code"
-msgstr "公共程式 (Public code)"
+msgstr "公共程式 (Public Code)"
 
 #: ./glossary.md:block 26 (paragraph)
 msgid ""

From 8d3a70c198c15493cbe2bb452d43ad2aa8ab2e98 Mon Sep 17 00:00:00 2001
From: Winnie <winnie@steps.com.tw>
Date: Thu, 2 Nov 2023 02:25:45 +0000
Subject: [PATCH 62/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 46 +++++++++++++------------
 1 file changed, 24 insertions(+), 22 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index cb88757d..5ae859fa 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,8 +3,8 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-10-04 16:44+0000\n"
-"Last-Translator: Cheng-Chia Tseng <zerngjia@gmail.com>\n"
+"PO-Revision-Date: 2023-11-02 02:30+0000\n"
+"Last-Translator: Winnie <winnie@steps.com.tw>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
 "Language: zh_Hant\n"
@@ -1357,7 +1357,8 @@ msgstr "4. 慶祝"
 msgid ""
 "Your ideas, documentation and code have become an integral part of this "
 "project. You are the open source hero we need!"
-msgstr "您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開源英雄！"
+msgstr "您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄"
+"！"
 
 #: ./CONTRIBUTING.md:block 34 (paragraph)
 msgid ""
@@ -1460,8 +1461,9 @@ msgid ""
 " organizations in other places. It includes guidance for policy makers, city"
 " administrators, developers and vendors."
 msgstr ""
-"《公共程式標準》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相"
-"似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。"
+"《公共程式標準》提供公家機關一套準備開放原始碼解決方案的模型，讓他們能與其他"
+"地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的"
+"指引。"
 
 #: ./README.md:block 4 (paragraph)
 msgid ""
@@ -5353,9 +5355,9 @@ msgid ""
 "to the software, so that its development and maintenance become truly "
 "collaborative."
 msgstr ""
-"公共程式是旨在協助公家機關，履行其必要職責時所採用的開源軟體。透過使用，其他"
-"行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成"
-"果。"
+"公共程式是旨在協助公家機關，履行其必要職責時所採用的開放原始碼軟體。透過使用"
+"，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協"
+"作的成果。"
 
 #: ./foreword.md:block 37 (paragraph)
 msgid "Being open unlocks many other things."
@@ -5696,7 +5698,7 @@ msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
 msgstr ""
-"所謂「開源」或「開放原始碼」，是根據 OSI "
+"所謂「開放原始碼」或「開放原始碼」，是根據 OSI "
 "開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-"
 "annotated)》而來。"
 
@@ -5755,8 +5757,8 @@ msgstr "公共程式 (Public Code)"
 msgid ""
 "Public code is open source software developed by public organizations, "
 "together with the policy and guidance needed for collaboration and reuse."
-msgstr "公共程式，是由公家機關所開發的開源軟體，同時包含協作與重複利用所需的政策與指"
-"引。"
+msgstr "公共程式，是由公家機關所開發的開放原始碼軟體，同時包含協作與重複利用所需的政"
+"策與指引。"
 
 #: ./glossary.md:block 27 (paragraph)
 msgid ""
@@ -5850,7 +5852,7 @@ msgstr "toc: false"
 
 #: ./index.md:block 4 (header)
 msgid "Guidance for government open source collaboration"
-msgstr "政府開源協作指引"
+msgstr "政府開放原始碼協作指引"
 
 #: ./index.md:block 5 (paragraph)
 msgid ""
@@ -5869,12 +5871,12 @@ msgid ""
 "accountable, accessible and sustainable. It is meant to be applicable to "
 "codebases for all levels of government, from supranational to municipal."
 msgstr ""
-"《公共程式標準》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來"
-"能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵"
-"蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持"
-"公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這"
-"份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國"
-"家組織都行。"
+"《公共程式標準》為那些在建構自身開放原始碼解決方案的公家機關提供指引，以便他"
+"們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份"
+"標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準"
+"》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基"
+"底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大"
+"到超國家組織都行。"
 
 #: ./index.md:block 7 (paragraph)
 msgid ""
@@ -5883,13 +5885,13 @@ msgid ""
 "with the policy and guidance needed for collaboration and reuse."
 msgstr ""
 "《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所"
-"開發的開源軟體，同時包含協作與重複使用所需的政策與指引。"
+"開發的開放原始碼軟體，同時包含協作與重複使用所需的政策與指引。"
 
 #: ./index.md:block 8 (paragraph)
 msgid ""
 "The criteria of the Standard for Public Code are aligned with guidelines and"
 " best practices of open source software development."
-msgstr "《公共程式標準》當中的準則，符合開源軟體開發的指引與最佳實務。"
+msgstr "《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。"
 
 #: ./index.md:block 9 (paragraph)
 msgid ""
@@ -5990,8 +5992,8 @@ msgid ""
 "assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
 "public sector open source codebases"
 msgstr ""
-"公部門開源程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/"
-"assessment-eligibility/)》"
+"公部門開放原始碼程式基底的《[標準遵循自我評估](https://publiccodenet.github."
+"io/assessment-eligibility/)》"
 
 #: ./index.md:block 15 (unordered list)
 msgid ""

From d61f0b8c1b04054c41b7d232e1ffe2199f799a23 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Fri, 3 Nov 2023 13:58:18 +0800
Subject: [PATCH 63/71] update translate

---
 CONTRIBUTING.md |  7 ++++---
 README.md       |  2 +-
 foreword.md     |  2 +-
 glossary.md     |  7 +++----
 index.md        | 12 +++++-------
 5 files changed, 14 insertions(+), 16 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d30b2816..fb7c7b5e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,7 +8,7 @@
 我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專案的建議。我
 們非常開放任何合作的機會。
 
-我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件計送到
+我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件寄送到
 [info@publiccode.net](mailto:info@publiccode.net)。
 
 ## 問題、建議與議題等
@@ -59,7 +59,8 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 #### 風格
 
-《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
+《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖
+換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
 
 #### 遵守的標準
 
@@ -84,7 +85,7 @@ MarkDown 是本專案文件所採用的撰寫語法。
 
 ### 4. 慶祝
 
-您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開源英雄！
+您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄！
 
 誠摯歡迎您提出拉取請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) 檔案中，讓您所做的貢獻能銘記在本專案中。
 
diff --git a/README.md b/README.md
index faddd13f..46f2ac2c 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
 
-《公共程式標準》提供公家機關一套準備開源解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。
+《公共程式標準》提供公家機關一套準備開放原始碼解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。
 
 ![version 0.7.1](assets/version-badge.svg) [![License:
 CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
diff --git a/foreword.md b/foreword.md
index 952099a2..af59044e 100644
--- a/foreword.md
+++ b/foreword.md
@@ -80,7 +80,7 @@ redirect_from:
 
 ## 公共程式運作方式
 
-公共程式是旨在協助公家機關，履行其必要職責時所採用的開源軟體。透過使用，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成果。
+公共程式是旨在協助公家機關，履行其必要職責時所採用的開放原始碼軟體。透過使用，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成果。
 
 開放的精神能開創許多可能性。
 
diff --git a/glossary.md b/glossary.md
index b20fa5a6..99186f9a 100644
--- a/glossary.md
+++ b/glossary.md
@@ -32,8 +32,7 @@
 
 ## 開源或開放原始碼 (Open Source)
 
-所謂「開源」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定
-義](https://opensource.org/osd-annotated)》而來。
+所謂「開放原始碼」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
 
 ## 開放標準
 
@@ -50,9 +49,9 @@
 
 在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的政策。
 
-## 公共程式 (Public code)
+## 公共程式 (Public Code)
 
-公共程式，是由公家機關所開發的開源軟體，同時包含協作與重複利用所需的政策與指引。
+公共程式，是由公家機關所開發的開放原始碼軟體，同時包含協作與重複利用所需的政策與指引。
 
 公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以及公共政策兩者。
 
diff --git a/index.md b/index.md
index 7b74709b..99e11cc6 100644
--- a/index.md
+++ b/index.md
@@ -3,17 +3,15 @@
 # SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
 toc: false
 ---
-# 政府開源協作指引
+# 政府開放原始碼協作指引
 
 《公共程式標準》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。
 
-《公共程式標準》為那些在建構自身開源解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵蓋寫給政策制
-定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是
-要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。
+《公共程式標準》為那些在建構自身開放原始碼解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。
 
-《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開源軟體，同時包含協作與重複使用所需的政策與指引。
+《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所開發的開放原始碼軟體，同時包含協作與重複使用所需的政策與指引。
 
-《公共程式標準》當中的準則，符合開源軟體開發的指引與最佳實務。
+《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。
 
 {% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序
 文](foreword.md)。 {% endif%}{% endfor %}
@@ -42,5 +40,5 @@ if page.title %}
 ## 其他資源
 
 * 本標準非官方的其他語言[社群翻譯](https://publiccodenet.github.io/community-translations-standard/)
-* 公部門開源程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)》
+* 公部門開放原始碼程式基底的《[標準遵循自我評估](https://publiccodenet.github.io/assessment-eligibility/)》
 * Foundation for Public Code 執事人員用於程式基底審查的《[標準準則檢查清單](/docs/review-template.html)》

From 9bdae550aa8934b7d3ba91d309256bda6eeda8b4 Mon Sep 17 00:00:00 2001
From: Winnie <winnie@steps.com.tw>
Date: Fri, 3 Nov 2023 06:05:59 +0000
Subject: [PATCH 64/71] Translated using Weblate (Chinese (Traditional))

Currently translated at 100.0% (1046 of 1046 strings)

Translation: Standard for Public code/Standard for Public code
Translate-URL: http://weblate.steps.tw/projects/standard-for-public-code/standard-for-public-code/zh_Hant/
---
 locales/zh_Hant/LC_MESSAGES/messages.po | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po
index 5ae859fa..ae369f9a 100644
--- a/locales/zh_Hant/LC_MESSAGES/messages.po
+++ b/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -3,7 +3,7 @@ msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-07-30 22:44+0800\n"
-"PO-Revision-Date: 2023-11-02 02:30+0000\n"
+"PO-Revision-Date: 2023-11-03 06:41+0000\n"
 "Last-Translator: Winnie <winnie@steps.com.tw>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
 "standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
@@ -5698,7 +5698,7 @@ msgid ""
 "Open source is defined by the Open Source Initiative in their [Open Source "
 "Definition](https://opensource.org/osd-annotated)."
 msgstr ""
-"所謂「開放原始碼」或「開放原始碼」，是根據 OSI "
+"所謂「開源」或「開放原始碼」，是根據 OSI "
 "開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-"
 "annotated)》而來。"
 

From 5140eb86b6246195854e52a1817a99bd7b8de296 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Fri, 3 Nov 2023 14:47:35 +0800
Subject: [PATCH 65/71] update translate

---
 CHANGELOG.md | 1 +
 foreword.md  | 1 +
 glossary.md  | 2 +-
 3 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 985d8bb3..71b80820 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,7 @@
 # script/release-body.sh expects VERSION in the first second-level header
 # script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon
 ---
+
 # 版本歷史
 
 ## 0.7.1 版
diff --git a/foreword.md b/foreword.md
index af59044e..19c3650c 100644
--- a/foreword.md
+++ b/foreword.md
@@ -4,6 +4,7 @@
 redirect_from:
   - introduction
 ---
+
 # 序文
 
 《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。
diff --git a/glossary.md b/glossary.md
index 99186f9a..40fe9366 100644
--- a/glossary.md
+++ b/glossary.md
@@ -32,7 +32,7 @@
 
 ## 開源或開放原始碼 (Open Source)
 
-所謂「開放原始碼」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
+所謂「開源」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-annotated)》而來。
 
 ## 開放標準
 

From 3d3dd654cd14dcc9e2a4172da84a0e6026d5312f Mon Sep 17 00:00:00 2001
From: Moda / L10n Project <147604016+moda-l10n@users.noreply.github.com>
Date: Wed, 8 Nov 2023 10:26:57 +0800
Subject: [PATCH 66/71] Update README.md

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index 3ac24864..d957cfc4 100644
--- a/README.md
+++ b/README.md
@@ -53,3 +53,7 @@ weasyprint http://localhost:4000/print.html standard.pdf
 © [The authors and contributors](AUTHORS.md)
 
 The standard is [licensed](LICENSE) under CC 0, which also applies to all illustrations and the documentation. This means anyone can do anything with it. If you contribute you also grant these rights to others. You can read more about how to help in the [contributing guide](CONTRIBUTING.md).
+
+## 軟體中文化
+
+本專案為數位部開放原始碼軟體中文化專案項目之一，其中文化與專案應用可參考 [Wiki](https://github.com/moda-gov-tw/publiccodenet.standard/wiki)。

From 83125414c3dde23eb9ca1c452d693867f42688ca Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Mon, 13 Nov 2023 15:42:30 +0800
Subject: [PATCH 67/71] =?UTF-8?q?=E6=9B=B4=E6=96=B0=E5=8E=9F=E5=A7=8Btempl?=
 =?UTF-8?q?ate?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 criteria/make-the-codebase-findable.md                 | 3 ++-
 criteria/publish-with-an-open-license.md               | 3 ++-
 criteria/use-plain-english.md                          | 3 ++-
 criteria/welcome-contributors.md                       | 3 ++-
 origin_source/criteria/make-the-codebase-findable.md   | 1 +
 origin_source/criteria/publish-with-an-open-license.md | 1 +
 origin_source/criteria/use-plain-english.md            | 1 +
 origin_source/criteria/welcome-contributors.md         | 1 +
 8 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/criteria/make-the-codebase-findable.md b/criteria/make-the-codebase-findable.md
index 51f03bb9..98ecc695 100644
--- a/criteria/make-the-codebase-findable.md
+++ b/criteria/make-the-codebase-findable.md
@@ -64,7 +64,8 @@ redirect_from:
 * 推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。
 
 <p style="page-break-after: always;"></p>
-## Further reading
+
+## 延伸閱讀
 
 * Wikidata 維基數據社群《[維基數據簡
 介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。
diff --git a/criteria/publish-with-an-open-license.md b/criteria/publish-with-an-open-license.md
index 2c8f1cf9..f001ce8e 100644
--- a/criteria/publish-with-an-open-license.md
+++ b/criteria/publish-with-an-open-license.md
@@ -51,7 +51,8 @@ redirect_from:
 * 每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。
 
 <p style="page-break-after: always;"></p>
-## Further reading
+
+## 延伸閱讀
 
 * 開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。
 * 紐西蘭CC Aotearoa《[創用CC介紹動畫影
diff --git a/criteria/use-plain-english.md b/criteria/use-plain-english.md
index a478fe36..c6123aab 100644
--- a/criteria/use-plain-english.md
+++ b/criteria/use-plain-english.md
@@ -51,7 +51,8 @@ showtechniques=315#readable)》的建議，文件內容「應該」以國中識
 * 詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。
 
 <p style="page-break-after: always;"></p>
-## Further reading
+
+## 延伸閱讀
 
 * 符合 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1、3.1 之可讀
 性](https://www.w3.org/TR/WCAG21/#readable)》要求，撰寫的文字內容要容易閱讀與理解。
diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index 59fefa12..4f2727de 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -47,7 +47,8 @@ redirect_from:
 * 支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。
 
 <p style="page-break-after: always;"></p>
-## Developers and designers: what you need to do
+
+## 開發人員與設計師：需要的工作
 
 * 快速回應請求。
 * 告知管理人員，您在支援其他貢獻者時所需的時間與資源。
diff --git a/origin_source/criteria/make-the-codebase-findable.md b/origin_source/criteria/make-the-codebase-findable.md
index ca2f1ce1..4a805102 100644
--- a/origin_source/criteria/make-the-codebase-findable.md
+++ b/origin_source/criteria/make-the-codebase-findable.md
@@ -63,6 +63,7 @@ Well-written metadata containing a unique and persistent identifier, such as a W
 * Suggest conferences to present at and present at them.
 
 <p style="page-break-after: always;"></p>
+
 ## Further reading
 
 * [Introduction to Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the Wikidata community.
diff --git a/origin_source/criteria/publish-with-an-open-license.md b/origin_source/criteria/publish-with-an-open-license.md
index 1b674dcb..dd6ac3fb 100644
--- a/origin_source/criteria/publish-with-an-open-license.md
+++ b/origin_source/criteria/publish-with-an-open-license.md
@@ -46,6 +46,7 @@ Clearly indicating the license for each file within a codebase facilitates corre
 * When source code is being reused by the codebase, make sure that it has a license that is compatible with the license or licenses of the codebase.
 
 <p style="page-break-after: always;"></p>
+
 ## Further reading
 
 * [Open source definition](https://opensource.org/osd) by the Open Source Initiative, all open source licenses meet this definition.
diff --git a/origin_source/criteria/use-plain-english.md b/origin_source/criteria/use-plain-english.md
index a5aee480..57ae80df 100644
--- a/origin_source/criteria/use-plain-english.md
+++ b/origin_source/criteria/use-plain-english.md
@@ -49,6 +49,7 @@ Language that is easy to understand lowers the cost of creating and maintaining
 * Ask someone outside of your context if they understand the content (for example, a developer working on a different codebase).
 
 <p style="page-break-after: always;"></p>
+
 ## Further reading
 
 * Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content readable and understandable.
diff --git a/origin_source/criteria/welcome-contributors.md b/origin_source/criteria/welcome-contributors.md
index d8b8ce89..a22cea20 100644
--- a/origin_source/criteria/welcome-contributors.md
+++ b/origin_source/criteria/welcome-contributors.md
@@ -48,6 +48,7 @@ Newcomers need to understand and trust the codebase community’s governance.
 * Support your experienced policy makers, developers and designers to stay part of the community for as long as possible.
 
 <p style="page-break-after: always;"></p>
+
 ## Developers and designers: what you need to do
 
 * Respond promptly to requests.

From e2930e881336e3c10e603dbf2ba7d6ae0ff86eaf Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Mon, 13 Nov 2023 15:56:43 +0800
Subject: [PATCH 68/71] =?UTF-8?q?=E6=9B=B4=E6=96=B0=E9=80=A3=E7=B5=90?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 index.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/index.md b/index.md
index 99e11cc6..16365e32 100644
--- a/index.md
+++ b/index.md
@@ -13,8 +13,7 @@ toc: false
 
 《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。
 
-{% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序
-文](foreword.md)。 {% endif%}{% endfor %}
+{% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序文](foreword.html)。 {% endif%}{% endfor %}
 
 ## 目次
 

From fb88aa9a687896a9319dfebb960090a64a17bf78 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Wed, 15 Nov 2023 11:07:12 +0800
Subject: [PATCH 69/71] =?UTF-8?q?=E6=9B=B4=E6=96=B0=E9=80=A3=E7=B5=90?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 criteria/make-the-codebase-reusable-and-portable.md | 3 +--
 index.md                                            | 2 +-
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/criteria/make-the-codebase-reusable-and-portable.md b/criteria/make-the-codebase-reusable-and-portable.md
index af6fca59..39a597a8 100644
--- a/criteria/make-the-codebase-reusable-and-portable.md
+++ b/criteria/make-the-codebase-reusable-and-portable.md
@@ -15,8 +15,7 @@ redirect_from:
 以重複利用為前提籌劃設計[程式基底](../glossary.md#codebase)，更容易與多方共享程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，
 更可以從能自我運作的社群中獲益。
 
-以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情
-境](../glossary.md#different-contexts)中重複利用。
+以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在[另一種情境](../glossary.md#different-contexts)中重複利用。
 
 原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢獻者都能測試該原始碼。
 
diff --git a/index.md b/index.md
index 16365e32..02cef7b7 100644
--- a/index.md
+++ b/index.md
@@ -13,7 +13,7 @@ toc: false
 
 《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。
 
-{% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序文](foreword.html)。 {% endif%}{% endfor %}
+{% for page in site.pages %}{% if page.name == "foreword.md" %} 其他情境與背景資訊請參閱[序文](foreword.md)。 {% endif%}{% endfor %}
 
 ## 目次
 

From 86a42cd55f27d42ba121e5d64a3e6e730404b893 Mon Sep 17 00:00:00 2001
From: ru8tp6 <ru8tp6@steps.com.tw>
Date: Tue, 21 Nov 2023 18:38:09 +0800
Subject: [PATCH 70/71] Add _site files

---
 _site/404.html                                |  238 +
 _site/AUTHORS.html                            |  274 +
 _site/CC0-1.0.html                            |  360 +
 _site/CHANGELOG.html                          |  534 ++
 _site/CODE_OF_CONDUCT.html                    |  252 +
 _site/CODE_OF_CONDUCT.md                      |   14 +
 _site/CONTRIBUTING.html                       |  358 +
 _site/CONTRIBUTING.md                         |  100 +
 _site/Dockerfile                              |   50 +
 _site/GOVERNANCE.html                         |  249 +
 _site/LICENSE                                 |  121 +
 _site/README.html                             |  356 +
 _site/README.md                               |  110 +
 _site/assets/cc-zero-badge.svg                |   12 +
 _site/assets/codebase.svg                     |  134 +
 _site/assets/collaboration.svg                |   37 +
 _site/assets/collaborative-development.svg    |   50 +
 _site/assets/dpg-badge.svg                    |   53 +
 _site/assets/eco-system.svg                   |   57 +
 _site/assets/github-markdown.css              |  695 ++
 _site/assets/hand-point.svg                   |    6 +
 _site/assets/hands-shake.svg                  |   15 +
 _site/assets/print.css                        |  274 +
 _site/assets/rouge-highlight.css              |  210 +
 .../standard-for-public-code-commitment.svg   |   25 +
 _site/assets/style.css                        |  873 +++
 _site/assets/unlock.svg                       |   36 +
 _site/assets/version-badge.svg                |   25 +
 _site/criteria/advertise-maturity.html        |   11 +
 _site/criteria/bundle-policy-and-code.html    |   11 +
 .../bundle-policy-and-source-code.html        |  501 ++
 _site/criteria/code-in-the-open.html          |  492 ++
 _site/criteria/continuous-integration.html    |   11 +
 .../create-reusable-and-portable-code.html    |   11 +
 .../criteria/document-codebase-maturity.html  |  483 ++
 .../document-codebase-objectives.html         |  478 ++
 _site/criteria/document-maturity.html         |   11 +
 _site/criteria/document-objectives.html       |   11 +
 _site/criteria/document-the-code.html         |  490 ++
 _site/criteria/documenting.html               |   11 +
 _site/criteria/findability.html               |   11 +
 _site/criteria/index.html                     |  473 ++
 _site/criteria/maintain-version-control.html  |  504 ++
 _site/criteria/make-contributing-easy.html    |  489 ++
 .../criteria/make-the-codebase-findable.html  |  511 ++
 ...ke-the-codebase-reusable-and-portable.html |  522 ++
 _site/criteria/open-licenses.html             |   11 +
 _site/criteria/open-standards.html            |   11 +
 _site/criteria/open-to-contributions.html     |   11 +
 .../publish-with-an-open-license.html         |  499 ++
 .../require-review-of-contributions.html      |  506 ++
 _site/criteria/require-review.html            |   11 +
 .../reusable-and-portable-codebases.html      |   11 +
 _site/criteria/style.html                     |   11 +
 .../understandable-english-first.html         |   11 +
 _site/criteria/use-a-coherent-style.html      |  485 ++
 .../criteria/use-continuous-integration.html  |  508 ++
 _site/criteria/use-open-standards.html        |  485 ++
 _site/criteria/use-plain-english.html         |  498 ++
 .../criteria/version-control-and-history.html |   11 +
 _site/criteria/welcome-contributors.html      |  500 ++
 _site/docker.sh                               |    9 +
 _site/docker/apache-data/000-default.conf     |   34 +
 _site/docs/checklist.html                     |  230 +
 _site/docs/printing.html                      |  261 +
 _site/docs/printing.md                        |   21 +
 _site/docs/releasing.html                     |  310 +
 _site/docs/releasing.md                       |   48 +
 _site/docs/review-template.html               | 1512 ++++
 _site/docs/roadmap.html                       |  281 +
 _site/docs/roadmap.md                         |   33 +
 _site/docs/standard-for-public-code.html      | 1514 ++++
 _site/foreword-print.html                     |  215 +
 _site/foreword.html                           |  443 ++
 _site/glossary.html                           |  327 +
 _site/index.html                              |  288 +
 _site/introduction.html                       |   11 +
 _site/jargon.txt                              |  190 +
 _site/license.html                            |   11 +
 _site/locales/en/LC_MESSAGES/messages.po      | 5602 +++++++++++++++
 _site/locales/zh_Hant/LC_MESSAGES/messages.po | 6304 +++++++++++++++++
 _site/package.json                            |    5 +
 _site/print-cover.html                        |  308 +
 _site/publiccode.yml                          |   74 +
 _site/python/po2md.py                         |  102 +
 _site/python/update_po.py                     |   34 +
 _site/readers-guide.html                      |  313 +
 _site/redirects.json                          |    1 +
 _site/robots.txt                              |    1 +
 _site/script/check-new-links.sh               |   61 +
 _site/script/ensure-font.sh                   |   29 +
 _site/script/find-missing-spdx.sh             |   26 +
 _site/script/generate-checklist.sh            |   94 +
 _site/script/generate-review-template.sh      |  119 +
 _site/script/make-version-badge.sh            |   61 +
 _site/script/missing-glossary-links.sh        |  101 +
 _site/script/pdf.sh                           |  160 +
 _site/script/release-body.sh                  |   36 +
 _site/script/serve.sh                         |   15 +
 _site/script/spell-check.sh                   |   44 +
 _site/script/test-all.sh                      |   20 +
 _site/script/test-markdown.sh                 |   13 +
 _site/script/test-with-link-check.sh          |   60 +
 _site/script/test-without-link-check.sh       |   33 +
 _site/script/to-archive-org.sh                |   84 +
 _site/script/update-changelog-date.sh         |   46 +
 _site/sitemap.xml                             |  117 +
 _site/standard-print.html                     | 2078 ++++++
 108 files changed, 35797 insertions(+)
 create mode 100644 _site/404.html
 create mode 100644 _site/AUTHORS.html
 create mode 100644 _site/CC0-1.0.html
 create mode 100644 _site/CHANGELOG.html
 create mode 100644 _site/CODE_OF_CONDUCT.html
 create mode 100644 _site/CODE_OF_CONDUCT.md
 create mode 100644 _site/CONTRIBUTING.html
 create mode 100644 _site/CONTRIBUTING.md
 create mode 100644 _site/Dockerfile
 create mode 100644 _site/GOVERNANCE.html
 create mode 100644 _site/LICENSE
 create mode 100644 _site/README.html
 create mode 100644 _site/README.md
 create mode 100644 _site/assets/cc-zero-badge.svg
 create mode 100644 _site/assets/codebase.svg
 create mode 100644 _site/assets/collaboration.svg
 create mode 100644 _site/assets/collaborative-development.svg
 create mode 100644 _site/assets/dpg-badge.svg
 create mode 100644 _site/assets/eco-system.svg
 create mode 100644 _site/assets/github-markdown.css
 create mode 100644 _site/assets/hand-point.svg
 create mode 100644 _site/assets/hands-shake.svg
 create mode 100644 _site/assets/print.css
 create mode 100644 _site/assets/rouge-highlight.css
 create mode 100644 _site/assets/standard-for-public-code-commitment.svg
 create mode 100644 _site/assets/style.css
 create mode 100644 _site/assets/unlock.svg
 create mode 100644 _site/assets/version-badge.svg
 create mode 100644 _site/criteria/advertise-maturity.html
 create mode 100644 _site/criteria/bundle-policy-and-code.html
 create mode 100644 _site/criteria/bundle-policy-and-source-code.html
 create mode 100644 _site/criteria/code-in-the-open.html
 create mode 100644 _site/criteria/continuous-integration.html
 create mode 100644 _site/criteria/create-reusable-and-portable-code.html
 create mode 100644 _site/criteria/document-codebase-maturity.html
 create mode 100644 _site/criteria/document-codebase-objectives.html
 create mode 100644 _site/criteria/document-maturity.html
 create mode 100644 _site/criteria/document-objectives.html
 create mode 100644 _site/criteria/document-the-code.html
 create mode 100644 _site/criteria/documenting.html
 create mode 100644 _site/criteria/findability.html
 create mode 100644 _site/criteria/index.html
 create mode 100644 _site/criteria/maintain-version-control.html
 create mode 100644 _site/criteria/make-contributing-easy.html
 create mode 100644 _site/criteria/make-the-codebase-findable.html
 create mode 100644 _site/criteria/make-the-codebase-reusable-and-portable.html
 create mode 100644 _site/criteria/open-licenses.html
 create mode 100644 _site/criteria/open-standards.html
 create mode 100644 _site/criteria/open-to-contributions.html
 create mode 100644 _site/criteria/publish-with-an-open-license.html
 create mode 100644 _site/criteria/require-review-of-contributions.html
 create mode 100644 _site/criteria/require-review.html
 create mode 100644 _site/criteria/reusable-and-portable-codebases.html
 create mode 100644 _site/criteria/style.html
 create mode 100644 _site/criteria/understandable-english-first.html
 create mode 100644 _site/criteria/use-a-coherent-style.html
 create mode 100644 _site/criteria/use-continuous-integration.html
 create mode 100644 _site/criteria/use-open-standards.html
 create mode 100644 _site/criteria/use-plain-english.html
 create mode 100644 _site/criteria/version-control-and-history.html
 create mode 100644 _site/criteria/welcome-contributors.html
 create mode 100644 _site/docker.sh
 create mode 100644 _site/docker/apache-data/000-default.conf
 create mode 100644 _site/docs/checklist.html
 create mode 100644 _site/docs/printing.html
 create mode 100644 _site/docs/printing.md
 create mode 100644 _site/docs/releasing.html
 create mode 100644 _site/docs/releasing.md
 create mode 100644 _site/docs/review-template.html
 create mode 100644 _site/docs/roadmap.html
 create mode 100644 _site/docs/roadmap.md
 create mode 100644 _site/docs/standard-for-public-code.html
 create mode 100644 _site/foreword-print.html
 create mode 100644 _site/foreword.html
 create mode 100644 _site/glossary.html
 create mode 100644 _site/index.html
 create mode 100644 _site/introduction.html
 create mode 100644 _site/jargon.txt
 create mode 100644 _site/license.html
 create mode 100644 _site/locales/en/LC_MESSAGES/messages.po
 create mode 100644 _site/locales/zh_Hant/LC_MESSAGES/messages.po
 create mode 100644 _site/package.json
 create mode 100644 _site/print-cover.html
 create mode 100644 _site/publiccode.yml
 create mode 100644 _site/python/po2md.py
 create mode 100644 _site/python/update_po.py
 create mode 100644 _site/readers-guide.html
 create mode 100644 _site/redirects.json
 create mode 100644 _site/robots.txt
 create mode 100755 _site/script/check-new-links.sh
 create mode 100755 _site/script/ensure-font.sh
 create mode 100755 _site/script/find-missing-spdx.sh
 create mode 100755 _site/script/generate-checklist.sh
 create mode 100755 _site/script/generate-review-template.sh
 create mode 100755 _site/script/make-version-badge.sh
 create mode 100755 _site/script/missing-glossary-links.sh
 create mode 100755 _site/script/pdf.sh
 create mode 100755 _site/script/release-body.sh
 create mode 100755 _site/script/serve.sh
 create mode 100755 _site/script/spell-check.sh
 create mode 100755 _site/script/test-all.sh
 create mode 100755 _site/script/test-markdown.sh
 create mode 100755 _site/script/test-with-link-check.sh
 create mode 100755 _site/script/test-without-link-check.sh
 create mode 100755 _site/script/to-archive-org.sh
 create mode 100755 _site/script/update-changelog-date.sh
 create mode 100644 _site/sitemap.xml
 create mode 100644 _site/standard-print.html

diff --git a/_site/404.html b/_site/404.html
new file mode 100644
index 00000000..ec3c3d96
--- /dev/null
+++ b/_site/404.html
@@ -0,0 +1,238 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>Page not found, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/404.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class=" ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/404.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `404.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="404-找不到網頁">404 找不到網頁</h1>
+
+<p>如果您是手動輸入網址，請確認網址是否正確。</p>
+
+<p>如果您是複製貼上此網址，請確認是否有複製到完整的網址。</p>
+
+<p>若網址正確，或您是按下連結或按鈕來的，請寫信給 <a href="mailto:info@publiccode.net">Foundation for Public Code 員
+工</a>，讓我們協助您，並同時修正我們的錯誤。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/AUTHORS.html b/_site/AUTHORS.html
new file mode 100644
index 00000000..fc407efa
--- /dev/null
+++ b/_site/AUTHORS.html
@@ -0,0 +1,274 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>作者群, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/AUTHORS.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/AUTHORS.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `AUTHORS.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="作者群">作者群</h1>
+
+<ul>
+  <li>Alba Roza，<a href="https://publiccode.net/">Foundation for Public Code</a></li>
+  <li>Arnout Engelen</li>
+  <li>Arnout Schuijff，Foundation for Public Code</li>
+  <li>唐鳳，<a href="https://digitalminister.tw/">數位發展部</a></li>
+  <li>Ben Cerveny，Foundation for Public Code</li>
+  <li>Bert Spaan</li>
+  <li>Boris van Hoytema，Foundation for Public Code</li>
+  <li>Charlotte Heikendorf</li>
+  <li>Claus Mullie，Foundation for Public Code</li>
+  <li>David Barberi</li>
+  <li>Edo Plantinga，<a href="https://codefor.nl/">Code For NL</a></li>
+  <li>Elena Findley-de Regt，Foundation for Public Code</li>
+  <li>Eric Herman，Foundation for Public Code</li>
+  <li>Felix Faassen，Foundation for Public Code</li>
+  <li>Floris Deerenberg</li>
+  <li>Jan Ainali，Foundation for Public Code</li>
+  <li>Johan Groenen，Code For NL</li>
+  <li>Marcus Klaas de Vries</li>
+  <li>Mark van der Net，<a href="https://www.amsterdam.nl/en/">阿姆斯特丹市政府</a></li>
+  <li>Martijn de Waal，<a href="https://www.amsterdamuas.com/">阿姆斯特丹應用科技大學 (AUAS)</a>，數位媒體與創意產業學院，
+戲劇與公民媒體系講師</li>
+  <li>Matti Schneider</li>
+  <li>Mauko Quiroga</li>
+  <li>Maurice Hendriks， 阿姆斯特丹市政府</li>
+  <li>Maurits van der Schee，阿姆斯特丹市政府</li>
+  <li>Mirjam van Tiel，Foundation for Public Code</li>
+  <li>Ngô Ngọc Đức Huy</li>
+  <li>Paul Keller</li>
+  <li>Petteri Kivimäki， <a href="https://niis.org">北歐互通性解決方案機構 (NIIS)</a></li>
+  <li>Sky Bristol</li>
+  <li>Tamas Erkelens，阿姆斯特丹市政府</li>
+  <li>Timo Slinger</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CC0-1.0.html b/_site/CC0-1.0.html
new file mode 100644
index 00000000..1f2996ef
--- /dev/null
+++ b/_site/CC0-1.0.html
@@ -0,0 +1,360 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>創用 CC0 1.0 通用授權, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CC0-1.0.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class=" ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/CC0-1.0.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `CC0-1.0.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="創用-cc0-10-通用授權">創用 CC0 1.0 通用授權</h1>
+
+<!-- TODO FIXME: move styling to the proper place, not inline html -->
+<style>.highlight { flex: 2 2 80%; max-width: 100%; } </style>
+
+<p>此授權的法律契約，允許任何人任意使用本文件中的任何內容。</p>
+
+<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
+
+</code></pre></div></div>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CHANGELOG.html b/_site/CHANGELOG.html
new file mode 100644
index 00000000..1c417af0
--- /dev/null
+++ b/_site/CHANGELOG.html
@@ -0,0 +1,534 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>版本歷史, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CHANGELOG.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#071-版">0.7.1 版</a></li>
+  <li><a href="#070-版">0.7.0 版</a></li>
+  <li><a href="#060-版">0.6.0 版</a></li>
+  <li><a href="#050-版">0.5.0 版</a></li>
+  <li><a href="#041-版">0.4.1 版</a></li>
+  <li><a href="#040-版">0.4.0 版</a></li>
+  <li><a href="#030-版">0.3.0 版</a></li>
+  <li><a href="#023-版">0.2.3 版</a></li>
+  <li><a href="#022-版">0.2.2 版</a></li>
+  <li><a href="#021-版">0.2.1 版</a></li>
+  <li><a href="#020-版">0.2.0 版</a></li>
+  <li><a href="#014-版">0.1.4 版</a></li>
+  <li><a href="#013-版">0.1.3 版</a></li>
+  <li><a href="#012-版">0.1.2 版</a></li>
+  <li><a href="#011-版">0.1.1 版</a></li>
+  <li><a href="#010-版">0.1.0 版</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/CHANGELOG.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `CHANGELOG.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="版本歷史">版本歷史</h1>
+
+<h2 id="071-版">0.7.1 版</h2>
+
+<p>2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。</p>
+
+<ul>
+  <li>〈程式碼要可重複使用且可攜〉準則改名為〈程式基底要可重複使用且可移植〉。</li>
+  <li>新增詞彙條目「原始碼」。</li>
+  <li>對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。</li>
+  <li>將「運作的程式碼」釐清稱為「軟體」。</li>
+  <li>細微修改以清楚區分「程式碼」與「程式基底」。</li>
+  <li>簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。</li>
+  <li>釐清〈程式基底可查詢得到〉與〈程式基底要可重複使用且可移植〉的「測試方式」小節。</li>
+  <li>在發行成品前的要求中，加入準則與需求規定檢查清單。</li>
+  <li>提升發行流程的自動化程度。</li>
+</ul>
+
+<h2 id="070-版">0.7.0 版</h2>
+
+<p>2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。</p>
+
+<ul>
+  <li>新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。</li>
+  <li>新增規定，程式基底必須要有簡短說明。</li>
+  <li>原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。</li>
+  <li>將〈程式基底可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。</li>
+  <li>審查範本現在有 HTML 格式。</li>
+  <li>「前言」轉換為「序文」。</li>
+  <li>改善貢獻指引。</li>
+  <li>改善命令稿文件紀錄。</li>
+</ul>
+
+<h2 id="060-版">0.6.0 版</h2>
+
+<p>2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且每個準則都有一段前言。</p>
+
+<ul>
+  <li>新增規定，在〈程式碼要可重複使用且可攜〉加入多方協作開發的內容。</li>
+  <li>新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。</li>
+  <li>新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。</li>
+  <li>對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。</li>
+  <li>重新撰寫規定，將焦點放在程式基底，而非貢獻者行為。</li>
+  <li>移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加入前言。</li>
+  <li>在本標準前言中，加入通用的「此措施辦不到的事」小節。</li>
+  <li>為政策制定者加入相關政策與授權相容性的指引。</li>
+  <li>為開發人員與設計師新增檔案要有版本控制的相關指引。</li>
+  <li>為開發人員與設計師釐清有關快速回應，以及搜尋引擎最佳化的內容。</li>
+  <li>新增可近用性無障礙環境的「延伸閱讀」內容。</li>
+  <li>將各準則的連結與其名稱連動。</li>
+  <li>改善網頁版的導覽功能。</li>
+  <li>已將「延伸閱讀」小節的工具移到社群實踐指引。</li>
+  <li>將標準依循或認證相關流程移到 <a href="https://publiccode.net">publiccode.net</a>。</li>
+  <li>變更審查範本格式，讓範本在發行新版後更容易更新。</li>
+  <li>改善著陸引導頁文字，加入相關資源的連結。</li>
+  <li>新增拼字檢查自動化測試。</li>
+  <li>微調文字，讓內容更明確與一致。</li>
+  <li>將 SPDX 標頭換成 yaml 標頭。</li>
+</ul>
+
+<h2 id="050-版">0.5.0 版</h2>
+
+<p>2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。</p>
+
+<ul>
+  <li>調整程式碼撰寫風格要求，專注於程式基底上，而非貢獻者行為。</li>
+  <li>將程式基底名稱規定，從〈使用白話的英文〉移到〈程式基底可查詢得到〉。</li>
+  <li>將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。</li>
+  <li>劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。</li>
+  <li>調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。</li>
+  <li>微調文字，讓內容更明確與一致。</li>
+</ul>
+
+<h2 id="041-版">0.4.1 版</h2>
+
+<p>2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。</p>
+
+<ul>
+  <li>寫下成熟度著重於程式基底是否已經可供使用，更甚於版本編號。</li>
+  <li>寫下成熟度不再需要為尚未準備好可供使用的程式基底加上特定標籤。</li>
+  <li>稽核流程圖現在以更容易轉譯的格式生成。</li>
+  <li>改善「測試方式」指引。</li>
+  <li>新增 publiccode.yml 檔案。</li>
+  <li>新增審查範本。</li>
+  <li>一致性連結詞彙表。</li>
+  <li>在「CONTRIBUTING」中加入要遵循的實務與標準。</li>
+  <li>將 Matti Schneider 加入作者群。</li>
+  <li>將剩餘 SPDX 標頭加入檔案中。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>更新部分超連結。</li>
+  <li>將範例移動到《<a href="https://publiccodenet.github.io/community-implementation-guide-standard/">社群實踐指
+引</a>》。</li>
+</ul>
+
+<h2 id="040-版">0.4.0 版</h2>
+
+<p>2022年9月7日：🔭第十一版草稿新增可查找性準則。</p>
+
+<ul>
+  <li>導入新準則：程式基底可查詢得到。</li>
+  <li>改善多數準則的「測試方式」小節。</li>
+  <li>在〈歡迎貢獻者〉中加入發布活動統計的新規定。</li>
+  <li>移除可重複使用與移植的程式碼中多餘的規定。</li>
+  <li>在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。</li>
+  <li>重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。</li>
+  <li>表達《公共程式標準》應該盡可能符合其自身規定的立場，並加入評估措施。</li>
+  <li>將 SPDX 授權識別碼加入檔案中。</li>
+  <li>導入新的行為守則。</li>
+  <li>解釋原始碼與政策內文的差異。</li>
+  <li>將規定重新調整為項目要點清單格式。</li>
+  <li>告知程式基底成熟度對於重複使用時的重要性。</li>
+  <li>將可查找性相關規定移動到新準則中。</li>
+  <li>釐清非開放標準在程式基底中的角色。</li>
+  <li>加入組建日期與執行時期依賴項目的額外指引。</li>
+  <li>新增《公共程式標準》的發展路線圖。</li>
+  <li>更新 Authors 檔案的結構。</li>
+  <li>將唐鳳加入作者群。</li>
+  <li>將準則列表加到印刷版本中。</li>
+  <li>釐清標準對於政策制定者、管理人員、開發人員與設計師等不同身分間的意義。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>更新部分超連結。</li>
+</ul>
+
+<h2 id="030-版">0.3.0 版</h2>
+
+<p>2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內容。</p>
+
+<ul>
+  <li>在〈程式碼要可重複使用且可攜〉中定下明確的在地化規定。</li>
+  <li>以文件記錄治理方式的規定，從「應該」等級調升為「必須」。</li>
+  <li>在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容『必須』小」的規定，改為必須紀錄貢獻所要完成的期待，並一次專注在單一議題上。</li>
+  <li>社群翻譯連結現在已放到頁尾中。</li>
+  <li>還原「用 Mermaid 流程圖取代業務流程 BPMN svg」。</li>
+  <li>細微調整用詞，讓句子更簡單。</li>
+  <li>更新部分超連結。</li>
+</ul>
+
+<h2 id="023-版">0.2.3 版</h2>
+
+<p>2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策，改為提供政策的英文版摘要。</p>
+
+<ul>
+  <li>放寬〈使用白話的英文〉準則，加入新規定，允許合捆的政策內文如果沒有英文版，只需要加入英文版摘要，而不用翻譯全文。</li>
+  <li>同樣地，在〈政策與原始碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要。</li>
+  <li>釐清〈政策與原始碼要合捆〉中，「政策」包含能影響開發與部署的流程。</li>
+  <li>在〈程式碼要可重複使用且可攜〉中強調解決方案部分內容的可重複使用性。</li>
+  <li>將〈程式碼要可重複使用且可攜〉當中的開發人員與設計師指引，加入部署到專有平台上的內容。</li>
+  <li>在〈使用白話的英文〉中，加入管理層在面對非英語詞彙時需要做的事的提點。</li>
+  <li>變更拉取請求流程圖，從業務流程 BPMN 改用 Mermaid，來讓<a href="https://github.com/publiccodenet/community-translations-standard">社群翻
+譯</a>更容易。</li>
+  <li>將 Maurice Hendriks 加入作者群。</li>
+  <li>將「OpenApi 規格」加入延伸閱讀。</li>
+  <li>將延伸閱讀小節的特性變得更明確。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="022-版">0.2.2 版</h2>
+
+<p>2021年11月29日：🏛第八版草稿認知程式碼所執行的政策，不一定是英文。</p>
+
+<ul>
+  <li>在「所有程式碼都必須使用英語編寫」規定中，雖然政策也算是一種程式 (code)，但可以保有例外。</li>
+  <li>在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以」規定。</li>
+  <li>將政策制定者加入〈政策與原始碼要合捆〉指引中。</li>
+  <li>將開發人員與設計師加入「風格要前後一致」指引中。</li>
+  <li>新增「不同情境」到詞彙表中。</li>
+  <li>將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。</li>
+  <li>新增「數位公共財」認可標章。</li>
+  <li>為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。</li>
+  <li>將「開放標準」原則加入延伸閱讀。</li>
+  <li>將「白話語言定義」加入延伸閱讀。</li>
+  <li>將「語意化版本編號規範」移動為延伸閱讀參考內容。</li>
+  <li>指出 publiccode.yml 是機器可讀中介資料說明的範例之一。</li>
+  <li>將「您的程式基底」與「您的組織單位」改為較不具有所有格的寫法。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>新增印刷版的製作指示。</li>
+</ul>
+
+<h2 id="021-版">0.2.1 版</h2>
+
+<p>2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改善。</p>
+
+<ul>
+  <li>新增使用分散式版本控制系統的相關「應該」規定，並解釋分散式的重要性。</li>
+  <li>針對未被採用的貢獻需要給予回饋，規定要比被接受的貢獻更加嚴格。</li>
+  <li>明確指出著作權與授權聲明也應該要機器可讀。</li>
+  <li>聲明是否為機器可讀的測試方式建議。</li>
+  <li>釐清滾動發行的指引。</li>
+  <li>釐清詞彙表中「版本控制」的定義。</li>
+  <li>新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項目。</li>
+  <li>新增有關公共程式概念的影片連結。</li>
+  <li>更新業務流程 BPMN 連結。</li>
+  <li>減少重複連結。</li>
+  <li>將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="020-版">0.2.0 版</h2>
+
+<p>2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。</p>
+
+<ul>
+  <li>將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。</li>
+  <li>將〈注意程式基底成熟度〉準則改名為〈記錄程式基底成熟度〉。</li>
+  <li>針對多方使用的程式基底，將「必須」等級規定調降為「應該」。</li>
+  <li>針對著作權轉讓，新增「禁止」規定。</li>
+  <li>在可重複使用程式碼的規定中，釐清組態設定的角色。</li>
+  <li>新增詞彙：持續整合、政策、儲存庫、版本控制等。</li>
+  <li>將「城市」替換成「公家機關」。</li>
+  <li>將貢獻者與審查人員規定分開為不同項目，以釐清程式碼中較敏感性的層面。</li>
+  <li>將政策制定者、開發人員與設計師加入延伸閱讀與指引中。</li>
+  <li>將 Felix Faassen 與 Arnout Engelen 加入作者群。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="014-版">0.1.4 版</h2>
+
+<p>2019年11月27日：🧹第五版草稿主要是一些細部修正。</p>
+
+<ul>
+  <li>連結 License.md 檔案。</li>
+  <li>將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。</li>
+  <li>讓標點符號使用更一致，特別是項目符號列表。</li>
+  <li>細部調整文字，讓內容更明確。</li>
+</ul>
+
+<h2 id="013-版">0.1.3 版</h2>
+
+<p>2019年10月8日：🍂第四版草稿僅針對秋季所作的清理修正一些小地方</p>
+
+<ul>
+  <li>將「持續交付」改名為「持續整合」。</li>
+  <li>在語言標準中引用無障礙指導原則。</li>
+  <li>改善一些樣式，與一致性修正。</li>
+</ul>
+
+<h2 id="012-版">0.1.2 版</h2>
+
+<p>2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見</p>
+
+<ul>
+  <li>有好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。</li>
+  <li>所有連結都是 HTTPS。</li>
+  <li>一般校對、釐清用字淺詞、修正拼字錯誤等。</li>
+  <li>更新準則：
+    <ul>
+      <li>在不同情境背景下重複使用的規定</li>
+      <li>明確的版本控制建議</li>
+      <li>多方部署的建議</li>
+      <li>檔案授權標頭的建議</li>
+      <li>漏洞回報的建議</li>
+      <li>明確以文件記錄治理方式的建議</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="011-版">0.1.1 版</h2>
+
+<p>2019年5月9日：🤔第二版草稿修正一些基本的疏漏，以及許多拼字錯誤</p>
+
+<ul>
+  <li>移除出現「Foundation for Public Code」的地方，我們之後可能必須改名才能成為協會。</li>
+  <li>更新簡介。</li>
+  <li>更新詞彙表。</li>
+  <li>新增行為守則。</li>
+  <li>我們建議使用 publiccode.yml 標準，方便重複使用。</li>
+</ul>
+
+<h2 id="010-版">0.1.0 版</h2>
+
+<p>2019年4月16日：🎉初版草稿已準備就緒，全新內容，而且有許多有趣的新穎理念</p>
+
+<ul>
+  <li>14 項準則，有各自的規定，以及相關的實施方式。</li>
+  <li>精要的背景介紹，例如本標準是什麼，以及 Foundation for Public Code 如何使用此標準。</li>
+</ul>
+
+<p>最初的版本是由阿姆斯特丹應用科學大學、阿姆斯特丹市政府，以及本基金會合作撰寫，取自 <a href="https://smartcities.publiccode.net/">Smart Cities? Public Code! 專
+案</a> 的部分內容。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CODE_OF_CONDUCT.html b/_site/CODE_OF_CONDUCT.html
new file mode 100644
index 00000000..05df32e9
--- /dev/null
+++ b/_site/CODE_OF_CONDUCT.html
@@ -0,0 +1,252 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>行為守則, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CODE_OF_CONDUCT.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/CODE_OF_CONDUCT.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `CODE_OF_CONDUCT.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="行為守則">行為守則</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。</p>
+
+<p>來到這裡來是為了協作。</p>
+
+<p>請對彼此體貼、尊重，以及有耐心。</p>
+
+<p>努力做出有建設性的行為。</p>
+
+<p>若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CODE_OF_CONDUCT.md b/_site/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..bd491188
--- /dev/null
+++ b/_site/CODE_OF_CONDUCT.md
@@ -0,0 +1,14 @@
+# 行為守則
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。
+
+來到這裡來是為了協作。
+
+請對彼此體貼、尊重，以及有耐心。
+
+努力做出有建設性的行為。
+
+若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。
diff --git a/_site/CONTRIBUTING.html b/_site/CONTRIBUTING.html
new file mode 100644
index 00000000..c2dae15c
--- /dev/null
+++ b/_site/CONTRIBUTING.html
@@ -0,0 +1,358 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>貢獻此標準, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/CONTRIBUTING.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#問題建議與議題等">問題、建議與議題等</a></li>
+  <li><a href="#為文件與程式碼提出拉取請求">為文件與程式碼提出拉取請求</a>
+    <ol>
+      <li><a href="#1-作出您的修改">1. 作出您的修改</a>
+        <ol>
+          <li><a href="#適用政策">適用政策</a></li>
+          <li><a href="#風格">風格</a></li>
+          <li><a href="#遵守的標準">遵守的標準</a></li>
+        </ol>
+      </li>
+      <li><a href="#2-拉取請求">2. 拉取請求</a></li>
+      <li><a href="#3-改善">3. 改善</a></li>
+      <li><a href="#4-慶祝">4. 慶祝</a></li>
+    </ol>
+  </li>
+  <li><a href="#翻譯成其他語言">翻譯成其他語言</a></li>
+  <li><a href="#發行版本">發行版本</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/CONTRIBUTING.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `CONTRIBUTING.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="貢獻此標準">貢獻此標準</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>🙇‍♀️ 感謝您的貢獻！</p>
+
+<p>我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專案的建議。我
+們非常開放任何合作的機會。</p>
+
+<p>我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件寄送到
+<a href="mailto:info@publiccode.net">info@publiccode.net</a>。</p>
+
+<h2 id="問題建議與議題等">問題、建議與議題等</h2>
+
+<p>在<a href="/docs/roadmap.html">發展路線圖</a>中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 <a href="https://github.com/publiccodenet/standard/issues">Standard
+for Public Code 的 GitHub
+Issue</a> 頁面中，為本專案<a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue">提出 GitHub 議
+題</a>。</p>
+
+<p>或者，註冊加入<a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">郵遞論壇列
+表</a>，
+並寄送電子郵件到<a href="mailto:standard@lists.publiccode.net">standard@lists.publiccode.net</a>。</p>
+
+<p>您不一定要修改我們的程式碼或文件，也能成為貢獻者！</p>
+
+<h2 id="為文件與程式碼提出拉取請求">為文件與程式碼提出拉取請求</h2>
+
+<p>如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull Request，亦可簡稱 PR)。</p>
+
+<p>若您從未使用過 GitHub，歡迎先<a href="https://docs.github.com/en/get-started/quickstart/github-flow">認識 GitHub 作業流
+程</a>，或是參加 <a href="https://skills.github.com/">GitHub
+Skills</a> 免費且優質的互動式課程，當中會介紹該如何使用 GitHub 以及 MarkDown 語法。
+MarkDown 是本專案文件所採用的撰寫語法。</p>
+
+<p>本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可以
+任意使用。</p>
+
+<h3 id="1-作出您的修改">1. 作出您的修改</h3>
+
+<p>貢獻內容應該<a href="/docs/standard-for-public-code.html">遵守</a>《公共程式標準》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合
+<a href="/foreword.html#values-of-public-code">公共程式的價值</a>。此外，他們也會審查貢獻是否遵循<a href="#standards-to-follow">標
+準</a>，且與整體作品有所連貫。</p>
+
+<p>本專案使用 <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow 分支與工作流程</a>。
+當您對此儲存庫作分支以後，請務必依照 GitFlow 模型建立新功能分支。</p>
+
+<p>將您所作的變更內容加入送交版次，<a href="https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message">並附上內容說
+明</a>。如果需要作
+出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
+容易以「<code class="language-plaintext highlighter-rouge">diff</code> 」檢視的檔案格式，如「<code class="language-plaintext highlighter-rouge">.svg</code> 」格式就勝過二進位影像。在送交版次訊息中，請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉
+擇。</p>
+
+<p>如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。</p>
+
+<h4 id="適用政策">適用政策</h4>
+
+<p>就目前而言，《公共程式標準》並非在執行任何特定的公共政策。</p>
+
+<h4 id="風格">風格</h4>
+
+<p>《公共程式標準》目標<a href="/criteria/use-plain-english.html">使用白話的英語</a>，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖
+換行，來讓「<code class="language-plaintext highlighter-rouge">diff</code>」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才<a href="/docs/releasing.html">推出新發行版本</a>。</p>
+
+<h4 id="遵守的標準">遵守的標準</h4>
+
+<p>這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。</p>
+
+<ul>
+  <li><a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a> - 要求等級關鍵字</li>
+  <li><a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容可近用無障礙指引 2.1</a> - 易讀性</li>
+</ul>
+
+<h3 id="2-拉取請求">2. 拉取請求</h3>
+
+<p>當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列出所有能一併
+修正的議題編號。</p>
+
+<h3 id="3-改善">3. 改善</h3>
+
+<p>所有貢獻都必須接受審查。Foundation for Public Code 致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。</p>
+
+<p>維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若是如此，負責
+審查您貢獻內容的維護人員，將協助您改善文件與程式碼。</p>
+
+<p>一旦您的文件與程式碼通過人工審查，就會合併。</p>
+
+<h3 id="4-慶祝">4. 慶祝</h3>
+
+<p>您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄！</p>
+
+<p>誠摯歡迎您提出拉取請求，將您的名字加到 <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS</code></a> 檔案中，讓您所做的貢獻能銘記在本專案中。</p>
+
+<h2 id="翻譯成其他語言">翻譯成其他語言</h2>
+
+<p>《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的<a href="https://github.com/publiccodenet/community-translations-standard">社群翻譯</a>，或是新增翻譯。</p>
+
+<h2 id="發行版本">發行版本</h2>
+
+<p>我們有提供<a href="/docs/releasing.html">發行新版本</a>，與<a href="/docs/printing.html">訂購印刷版標準</a>的專用詳細文件。</p>
+
+<p>若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 <a href="/README.html"><code class="language-plaintext highlighter-rouge">README </code></a>。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/CONTRIBUTING.md b/_site/CONTRIBUTING.md
new file mode 100644
index 00000000..fb7c7b5e
--- /dev/null
+++ b/_site/CONTRIBUTING.md
@@ -0,0 +1,100 @@
+# 貢獻此標準
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+🙇‍♀️ 感謝您的貢獻！
+
+我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專案的建議。我
+們非常開放任何合作的機會。
+
+我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件寄送到
+[info@publiccode.net](mailto:info@publiccode.net)。
+
+## 問題、建議與議題等
+
+在[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 [Standard
+for Public Code 的 GitHub
+Issue](https://github.com/publiccodenet/standard/issues) 頁面中，為本專案[提出 GitHub 議
+題](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue)。
+
+或者，註冊加入[郵遞論壇列
+表](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)，
+並寄送電子郵件到[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)。
+
+您不一定要修改我們的程式碼或文件，也能成為貢獻者！
+
+## 為文件與程式碼提出拉取請求
+
+如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull Request，亦可簡稱 PR)。
+
+若您從未使用過 GitHub，歡迎先[認識 GitHub 作業流
+程](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加 [GitHub
+Skills](https://skills.github.com/) 免費且優質的互動式課程，當中會介紹該如何使用 GitHub 以及 MarkDown 語法。
+MarkDown 是本專案文件所採用的撰寫語法。
+
+本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可以
+任意使用。
+
+### 1. 作出您的修改
+
+貢獻內容應該[遵守](docs/standard-for-public-code.html)《公共程式標準》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合
+[公共程式的價值](foreword.md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標
+準](#standards-to-follow)，且與整體作品有所連貫。
+
+本專案使用 [GitFlow 分支與工作流程](https://nvie.com/posts/a-successful-git-branching-model/)。
+當您對此儲存庫作分支以後，請務必依照 GitFlow 模型建立新功能分支。
+
+將您所作的變更內容加入送交版次，[並附上內容說
+明](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)。如果需要作
+出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
+容易以「`diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉
+擇。
+
+如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。
+
+#### 適用政策
+
+就目前而言，《公共程式標準》並非在執行任何特定的公共政策。
+
+#### 風格
+
+《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖
+換行，來讓「`diff`」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新發行版本](docs/releasing.md)。
+
+#### 遵守的標準
+
+這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。
+
+* [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 要求等級關鍵字
+* [網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/#readable) - 易讀性
+
+### 2. 拉取請求
+
+當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列出所有能一併
+修正的議題編號。
+
+### 3. 改善
+
+所有貢獻都必須接受審查。Foundation for Public Code 致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。
+
+維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若是如此，負責
+審查您貢獻內容的維護人員，將協助您改善文件與程式碼。
+
+一旦您的文件與程式碼通過人工審查，就會合併。
+
+### 4. 慶祝
+
+您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄！
+
+誠摯歡迎您提出拉取請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) 檔案中，讓您所做的貢獻能銘記在本專案中。
+
+## 翻譯成其他語言
+
+《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](https://github.com/publiccodenet/community-translations-standard)，或是新增翻譯。
+
+## 發行版本
+
+我們有提供[發行新版本](/docs/releasing.md)，與[訂購印刷版標準](/docs/printing.md)的專用詳細文件。
+
+若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 [`README `](README.md)。
diff --git a/_site/Dockerfile b/_site/Dockerfile
new file mode 100644
index 00000000..e4552ba3
--- /dev/null
+++ b/_site/Dockerfile
@@ -0,0 +1,50 @@
+# OS: Ubuntu 22.04
+
+FROM ubuntu:22.04
+
+WORKDIR /var/www/html
+
+ENV TZ="Asia/Taipei"
+
+ENV GIT_COMPLETION_URL="https://raw.githubusercontent.com/git/git/master/contrib/completion/git-completion.bash"
+
+RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone
+
+RUN apt-get update && apt-get upgrade -y \
+    && apt-get install -y software-properties-common ca-certificates lsb-release apt-transport-https \
+    && apt-get install -y zip unzip curl vim wget cron
+
+RUN add-apt-repository ppa:ondrej/php \
+    && apt-get update
+
+RUN apt-get install -y apache2 apache2-utils
+
+RUN apt-get install -y git curl autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm6 libgdbm-dev libdb-dev
+
+RUN curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash
+RUN echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
+RUN echo 'eval "$(rbenv init -)"' >> ~/.bashrc
+
+RUN ~/.rbenv/bin/rbenv init -
+RUN ~/.rbenv/bin/rbenv install 3.1.3
+RUN ~/.rbenv/bin/rbenv global 3.1.3
+
+RUN ~/.rbenv/shims/gem install bundler jekyll
+
+# 中文語系顯示
+RUN apt-get install -y locales language-pack-zh-hans
+RUN locale-gen zh_TW.UTF-8
+
+RUN apt-get -y autoremove \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
+RUN a2enmod rewrite && a2enmod proxy && a2enmod proxy_http
+
+# 中文語系顯示
+RUN echo "export LANG=zh_TW.UTF-8" >> /root/.bashrc
+RUN echo "export LC_ALL=zh_TW.UTF-8" >> /root/.bashrc
+RUN echo 'PS1="\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\u@\h:\W\$ "' >> /root/.bashrc
+
+CMD ["apache2ctl", "-D", "FOREGROUND"]
+EXPOSE 80
+
diff --git a/_site/GOVERNANCE.html b/_site/GOVERNANCE.html
new file mode 100644
index 00000000..f3b24b72
--- /dev/null
+++ b/_site/GOVERNANCE.html
@@ -0,0 +1,249 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>治理方式, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/GOVERNANCE.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/GOVERNANCE.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `GOVERNANCE.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="治理方式">治理方式</h1>
+
+<p>本標準是 <a href="https://publiccode.net/">Foundation for Public Code</a> 在為程式基底提供督導時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。</p>
+
+<p>這份標準由 Foundation for Public Code 職員負責維護。</p>
+
+<p><a href="/CONTRIBUTING.html">我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。</a></p>
+
+<p>由於《公共程式標準》在我們的核心流程中，扮演至關重要的角色，所以我們會以《公共程式標準》的最高標準作要求。</p>
+
+<p>我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/LICENSE b/_site/LICENSE
new file mode 100644
index 00000000..0e259d42
--- /dev/null
+++ b/_site/LICENSE
@@ -0,0 +1,121 @@
+Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
diff --git a/_site/README.html b/_site/README.html
new file mode 100644
index 00000000..5bcf83a4
--- /dev/null
+++ b/_site/README.html
@@ -0,0 +1,356 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>公共程式標準, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/README.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#將公共程式標準套用到您的程式基底">將《公共程式標準》套用到您的程式基底</a></li>
+  <li><a href="#徵求貢獻">徵求貢獻</a></li>
+  <li><a href="#幫忙改善這份標準">幫忙改善這份標準</a></li>
+  <li><a href="#預覽建置部署">預覽、建置、部署</a>
+    <ol>
+      <li><a href="#測試">測試</a></li>
+      <li><a href="#生成公共程式標準的-pdf-檔案">生成《公共程式標準》的 PDF 檔案</a></li>
+    </ol>
+  </li>
+  <li><a href="#授權">授權</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/README.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `README.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="公共程式標準">公共程式標準</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>《公共程式標準》提供公家機關一套準備開放原始碼解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。</p>
+
+<p><img src="/assets/version-badge.svg" alt="version 0.7.1" /> <a href="http://creativecommons.org/publicdomain/zero/1.0/"><img src="https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg" alt="License:
+CC0-1.0" /></a>
+<a href="#help-improve-this-standard"><img src="assets/standard-for-public-code-commitment.svg" alt="標準承
+諾" /></a></p>
+
+<p><a href="https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment"><img src="https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg" alt="pages-build-deployment" /></a>
+<a href="https://github.com/publiccodenet/standard/actions/workflows/test.yml"><img src="https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg" alt="測
+試" /></a>
+<a href="https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json"><img src="https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg" alt="standard main
+badge" /></a>
+<a href="https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json"><img src="https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg" alt="standard develop
+badge" /></a></p>
+
+<p>《公共程式標準》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。</p>
+
+<h2 id="將公共程式標準套用到您的程式基底">將《公共程式標準》套用到您的程式基底</h2>
+
+<p>若您想要將《公共程式標準》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成《公共程式標準》準則要求時的熱誠，請使
+用 <a href="/assets/standard-for-public-code-commitment.svg">standard-for-public-code-commitment 徽章</a>連結到這份承諾文件。若要瞭解您程式基底所達成的程度，可以做<a href="https://publiccodenet.github.io/assessment-eligibility">自我資格評估</a>；它能幫助您大略瞭解，如果想要滿足所有
+準則，還需要下多少功夫。</p>
+
+<p>本標準 <em>應該</em> 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要
+一點靈感啟發，請參閱<a href="https://publiccodenet.github.io/community-implementation-guide-standard/">社群製作的《實踐指引》</a>，其中包
+括範例與其他提示。</p>
+
+<p>若新版的《公共程式標準》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的程式基底執事人員，會協助標準的實踐者理解該如何
+銜接之間的落差。</p>
+
+<p>若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
+<a href="mailto:info@publiccode.net">info@publiccode.net</a>，以展開正式<a href="https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment">評
+估</a>。</p>
+
+<h2 id="徵求貢獻">徵求貢獻</h2>
+
+<p>我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政策文件。</p>
+
+<p>本標準為程式基底設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及其他重大基礎設施服務的需求。</p>
+
+<p>本標準放在線上：<a href="https://standard.publiccode.net/">standard.publiccode.net</a>。請參閱
+<a href="/"><code class="language-plaintext highlighter-rouge">index.md</code></a> 查看整體內容概覽。</p>
+
+<p><a href="https://www.youtube.com/watch?
+v=QWt6vB-cipE"><img src="https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg" alt="《公共程式標準》的影片縮圖：兩隻手中間放著本標準的印刷
+本" /></a></p>
+
+<p><a href="https://www.youtube.com/watch?v=QWt6vB-cipE">《公共程式標準》的影片介紹</a>，出自 Creative Commons
+Global Summit 2020 (4:12)，放在 YouTube 上。</p>
+
+<h2 id="幫忙改善這份標準">幫忙改善這份標準</h2>
+
+<p>Foundation for Public Code 致力於維護與開發《公共程式標準》，且使其同時符合該標準自身的品質水準。</p>
+
+<p>我們正在尋找像您這樣的人，能對此專案做出<a href="/CONTRIBUTING.html">貢獻</a>，像是建議改善方向，以及協助開發等。😊若要開始，請先參閱我們的<a href="CONTRIBUTING.md">貢獻者指
+引</a>。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。<a href="/GOVERNANCE.html">治理方式聲明</a>中有說明管理該標準的
+方式。</p>
+
+<p>請注意，本專案配合<a href="/CODE_OF_CONDUCT.html">行為守則</a>一同發行。如果要參加本專案，代表您同意遵守守則。請善待社群的所有其他成員。</p>
+
+<h2 id="預覽建置部署">預覽、建置、部署</h2>
+
+<p>儲存庫會建置一個靜態網站，並部署至 <a href="https://standard.publiccode.net/">standard.publiccode.net</a>。網站採
+用 <a href="https://pages.github.com">GitHub 頁面</a> 與 <a href="https://jekyllrb.com/">Jekyll</a> 技術。</p>
+
+<p>網站內容透過 <a href="http://jekyllrb.com/">Jekyll</a> 技術建置。這代表您需要有安裝 ruby 與 ruby-bundler，例如：</p>
+
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>apt-get <span class="nb">install</span> <span class="nt">-y</span> ruby ruby-bundler
+</code></pre></div></div>
+
+<p>一旦安裝好 <code class="language-plaintext highlighter-rouge">ruby</code> 與 <code class="language-plaintext highlighter-rouge">bundle</code> 後，就可以執行 <code class="language-plaintext highlighter-rouge">bundle install</code>，接著再利用 <code class="language-plaintext highlighter-rouge">script/serve.sh</code> 命令稿轉譯呈現出網
+站成果。</p>
+
+<h3 id="測試">測試</h3>
+
+<p>本專案內含許多測試命令稿。其中 <code class="language-plaintext highlighter-rouge">script/test-all.sh</code> 命令稿則統包執行所有本機測試。</p>
+
+<p>請前往 <a href="https://github.com/publiccodenet/standard/tree/main/script">script</a> 資料夾查看命令
+稿。</p>
+
+<h3 id="生成公共程式標準的-pdf-檔案">生成《公共程式標準》的 PDF 檔案</h3>
+
+<p>除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 <a href="https://weasyprint.org/">Weasyprint</a> 和
+<a href="https://github.com/qpdf/qpdf">QPDF</a>。<a href="https://pandoc.org/">Pandoc</a> 則可將 PDF 檔轉換成
+<code class="language-plaintext highlighter-rouge">.epub</code> 檔。</p>
+
+<p>若要生成這類檔案，則應該要安裝依賴的軟體項目，例如：</p>
+
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>apt-get <span class="nb">install</span> <span class="nt">-y</span> pandoc qpdf weasyprint
+</code></pre></div></div>
+
+<p>使用以下命令稿，可以將 <code class="language-plaintext highlighter-rouge">standard-print.html</code> 檔案轉換成美觀的 PDF 檔，同時包括其他發行用的檔案：</p>
+
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>script/pdf.sh
+</code></pre></div></div>
+
+<h2 id="授權">授權</h2>
+
+<p>© <a href="/AUTHORS.html">作者與貢獻者</a></p>
+
+<p>本標準採用 CC0 公眾領域貢獻宣告<a href="/LICENSE">給予授權</a>，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
+這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱〈<a href="/CONTRIBUTING.html">貢獻指引</a>〉。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/README.md b/_site/README.md
new file mode 100644
index 00000000..46f2ac2c
--- /dev/null
+++ b/_site/README.md
@@ -0,0 +1,110 @@
+# 公共程式標準
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+《公共程式標準》提供公家機關一套準備開放原始碼解決方案的模型，讓他們能與其他地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的指引。
+
+![version 0.7.1](assets/version-badge.svg) [![License:
+CC0-1.0](https://img.shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)
+[![標準承
+諾](assets/standard-for-public-code-commitment.svg)](#help-improve-this-standard)
+
+[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-build-deployment)
+[![測
+試](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)
+[![standard main
+badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-url-check-look.json)
+[![standard develop
+badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)
+
+《公共程式標準》目前為草稿階段。我們正在準備發行 1.0 版，目前仍在幾個程式基底中作測試。
+
+## 將《公共程式標準》套用到您的程式基底
+
+若您想要將《公共程式標準》套用您的程式基底，就請放心去做，因為它是人人都能自由採用的開放標準。如果您希望宣傳程式基底社群達成《公共程式標準》準則要求時的熱誠，請使
+用 [standard-for-public-code-commitment 徽章](assets/standard-for-public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度，可以做[自我資格評估](https://publiccodenet.github.io/assessment-eligibility)；它能幫助您大略瞭解，如果想要滿足所有
+準則，還需要下多少功夫。
+
+本標準 *應該* 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。如果需要
+一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet.github.io/community-implementation-guide-standard/)，其中包
+括範例與其他提示。
+
+若新版的《公共程式標準》有任何導致過去作法不再適用的改動，則 Foundation for Public Code 的程式基底執事人員，會協助標準的實踐者理解該如何
+銜接之間的落差。
+
+若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫：
+[info@publiccode.net](mailto:info@publiccode.net)，以展開正式[評
+估](https://about.publiccode.net/activities/codebase-stewardship/lifecycle-diagram.html#assessment)。
+
+## 徵求貢獻
+
+我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政策文件。
+
+本標準為程式基底設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以及其他重大基礎設施服務的需求。
+
+本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。請參閱
+[`index.md`](index.md) 查看整體內容概覽。
+
+[![《公共程式標準》的影片縮圖：兩隻手中間放著本標準的印刷
+本](https://img.youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?
+v=QWt6vB-cipE)
+
+[《公共程式標準》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，出自 Creative Commons
+Global Summit 2020 (4:12)，放在 YouTube 上。
+
+## 幫忙改善這份標準
+
+Foundation for Public Code 致力於維護與開發《公共程式標準》，且使其同時符合該標準自身的品質水準。
+
+我們正在尋找像您這樣的人，能對此專案做出[貢獻](CONTRIBUTING.md)，像是建議改善方向，以及協助開發等。😊若要開始，請先參閱我們的[貢獻者指
+引](CONTRIBUTING.md)。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。[治理方式聲明](GOVERNANCE.md)中有說明管理該標準的
+方式。
+
+請注意，本專案配合[行為守則](CODE_OF_CONDUCT.md)一同發行。如果要參加本專案，代表您同意遵守守則。請善待社群的所有其他成員。
+
+## 預覽、建置、部署
+
+儲存庫會建置一個靜態網站，並部署至 [standard.publiccode.net](https://standard.publiccode.net/)。網站採
+用 [GitHub 頁面](https://pages.github.com) 與 [Jekyll](https://jekyllrb.com/) 技術。
+
+網站內容透過 [Jekyll](http://jekyllrb.com/) 技術建置。這代表您需要有安裝 ruby 與 ruby-bundler，例如：
+
+```bash
+sudo apt-get install -y ruby ruby-bundler
+```
+
+一旦安裝好 `ruby` 與 `bundle` 後，就可以執行 `bundle install`，接著再利用 `script/serve.sh` 命令稿轉譯呈現出網
+站成果。
+
+### 測試
+
+本專案內含許多測試命令稿。其中 `script/test-all.sh` 命令稿則統包執行所有本機測試。
+
+請前往 [script](https://github.com/publiccodenet/standard/tree/main/script) 資料夾查看命令
+稿。
+
+### 生成《公共程式標準》的 PDF 檔案
+
+除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 [Weasyprint](https://weasyprint.org/) 和
+[QPDF](https://github.com/qpdf/qpdf)。[Pandoc](https://pandoc.org/) 則可將 PDF 檔轉換成
+`.epub` 檔。
+
+若要生成這類檔案，則應該要安裝依賴的軟體項目，例如：
+
+```bash
+sudo apt-get install -y pandoc qpdf weasyprint
+```
+
+使用以下命令稿，可以將 `standard-print.html` 檔案轉換成美觀的 PDF 檔，同時包括其他發行用的檔案：
+
+```bash
+script/pdf.sh
+```
+
+## 授權
+
+© [作者與貢獻者](AUTHORS.md)
+
+本標準採用 CC0 公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
+這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱〈[貢獻指引](CONTRIBUTING.md)〉。
diff --git a/_site/assets/cc-zero-badge.svg b/_site/assets/cc-zero-badge.svg
new file mode 100644
index 00000000..9a925204
--- /dev/null
+++ b/_site/assets/cc-zero-badge.svg
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1 Basic//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11-basic.dtd">
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="88" height="31" viewBox="0 0 88 31" baseProfile="basic" version="1.1">
+<g id="surface1">
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(66.666667%,69.803922%,67.058824%);fill-opacity:1;" d="M 2.300781 0.570313 L 85.429688 0.71875 C 86.589844 0.71875 87.628906 0.546875 87.628906 3.039063 L 87.527344 30.414063 L 0.203125 30.414063 L 0.203125 2.9375 C 0.203125 1.707031 0.324219 0.570313 2.300781 0.570313 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 86.351563 0.199219 L 1.648438 0.199219 C 0.738281 0.199219 0 0.9375 0 1.847656 L 0 30.628906 C 0 30.832031 0.167969 31 0.371094 31 L 87.628906 31 C 87.832031 31 88 30.832031 88 30.628906 L 88 1.847656 C 88 0.9375 87.261719 0.199219 86.351563 0.199219 Z M 1.648438 0.945313 L 86.351563 0.945313 C 86.851563 0.945313 87.253906 1.347656 87.253906 1.847656 C 87.253906 1.847656 87.253906 13.46875 87.253906 21.851563 L 26.515625 21.851563 C 24.296875 25.863281 20.023438 28.585938 15.117188 28.585938 C 10.207031 28.585938 5.933594 25.863281 3.714844 21.851563 L 0.746094 21.851563 C 0.746094 13.46875 0.746094 1.847656 0.746094 1.847656 C 0.746094 1.347656 1.148438 0.945313 1.648438 0.945313 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 46.753906 23.984375 L 50.832031 23.984375 L 50.832031 24.738281 L 48.230469 27.886719 L 50.90625 27.886719 L 50.90625 28.832031 L 46.679688 28.832031 L 46.679688 28.074219 L 49.28125 24.925781 L 46.753906 24.925781 L 46.753906 23.984375 M 51.8125 23.984375 L 55.183594 23.984375 L 55.183594 24.925781 L 53.0625 24.925781 L 53.0625 25.832031 L 55.058594 25.832031 L 55.058594 26.773438 L 53.0625 26.773438 L 53.0625 27.886719 L 55.253906 27.886719 L 55.253906 28.832031 L 51.8125 28.832031 L 51.8125 23.984375 M 58.132813 26.132813 C 58.394531 26.132813 58.582031 26.082031 58.695313 25.984375 C 58.808594 25.890625 58.867188 25.730469 58.867188 25.503906 C 58.867188 25.285156 58.808594 25.125 58.695313 25.03125 C 58.582031 24.9375 58.394531 24.890625 58.132813 24.890625 L 57.605469 24.890625 L 57.605469 26.132813 L 58.132813 26.132813 M 57.605469 26.996094 L 57.605469 28.832031 L 56.355469 28.832031 L 56.355469 23.984375 L 58.265625 23.984375 C 58.902344 23.984375 59.371094 24.089844 59.667969 24.304688 C 59.964844 24.519531 60.117188 24.855469 60.117188 25.320313 C 60.117188 25.640625 60.039063 25.902344 59.882813 26.109375 C 59.730469 26.316406 59.496094 26.464844 59.183594 26.5625 C 59.355469 26.601563 59.507813 26.691406 59.640625 26.832031 C 59.777344 26.964844 59.914063 27.175781 60.054688 27.453125 L 60.734375 28.832031 L 59.402344 28.832031 L 58.8125 27.625 C 58.691406 27.382813 58.570313 27.21875 58.445313 27.128906 C 58.324219 27.039063 58.164063 26.996094 57.960938 26.996094 L 57.605469 26.996094 M 63.6875 24.800781 C 63.304688 24.800781 63.011719 24.941406 62.800781 25.222656 C 62.589844 25.503906 62.484375 25.902344 62.484375 26.410156 C 62.484375 26.921875 62.589844 27.316406 62.800781 27.597656 C 63.011719 27.878906 63.304688 28.019531 63.6875 28.019531 C 64.070313 28.019531 64.367188 27.878906 64.578125 27.597656 C 64.785156 27.316406 64.890625 26.921875 64.890625 26.410156 C 64.890625 25.902344 64.785156 25.503906 64.578125 25.222656 C 64.367188 24.941406 64.070313 24.800781 63.6875 24.800781 M 63.6875 23.894531 C 64.464844 23.894531 65.078125 24.117188 65.519531 24.5625 C 65.960938 25.011719 66.179688 25.625 66.179688 26.410156 C 66.179688 27.195313 65.960938 27.808594 65.519531 28.253906 C 65.078125 28.703125 64.464844 28.925781 63.6875 28.925781 C 62.910156 28.925781 62.300781 28.703125 61.855469 28.253906 C 61.414063 27.808594 61.195313 27.195313 61.195313 26.410156 C 61.195313 25.625 61.414063 25.011719 61.855469 24.5625 C 62.300781 24.117188 62.910156 23.894531 63.6875 23.894531 "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 25.121094 14.578125 C 25.125 20.097656 20.648438 24.578125 15.125 24.582031 C 9.605469 24.585938 5.125 20.113281 5.121094 14.589844 C 5.121094 14.585938 5.121094 14.582031 5.121094 14.578125 C 5.117188 9.054688 9.59375 4.578125 15.113281 4.574219 C 20.636719 4.570313 25.117188 9.042969 25.121094 14.566406 C 25.121094 14.570313 25.121094 14.574219 25.121094 14.578125 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 23.25 6.433594 C 25.464844 8.652344 26.574219 11.367188 26.574219 14.578125 C 26.574219 17.789063 25.484375 20.476563 23.304688 22.636719 C 20.992188 24.910156 18.261719 26.046875 15.105469 26.046875 C 11.992188 26.046875 9.304688 24.921875 7.050781 22.664063 C 4.792969 20.410156 3.667969 17.714844 3.667969 14.578125 C 3.667969 11.441406 4.792969 8.726563 7.050781 6.433594 C 9.246094 4.214844 11.933594 3.109375 15.105469 3.109375 C 18.316406 3.109375 21.03125 4.214844 23.25 6.433594 Z M 8.542969 7.925781 C 6.667969 9.820313 5.730469 12.035156 5.730469 14.582031 C 5.730469 17.125 6.660156 19.324219 8.511719 21.175781 C 10.367188 23.03125 12.578125 23.960938 15.140625 23.960938 C 17.703125 23.960938 19.929688 23.023438 21.824219 21.148438 C 23.621094 19.410156 24.519531 17.21875 24.519531 14.582031 C 24.519531 11.960938 23.605469 9.738281 21.78125 7.910156 C 19.953125 6.085938 17.742188 5.171875 15.140625 5.171875 C 12.539063 5.171875 10.339844 6.089844 8.542969 7.925781 Z M 13.476563 13.460938 C 13.1875 12.835938 12.761719 12.523438 12.1875 12.523438 C 11.175781 12.523438 10.671875 13.207031 10.671875 14.566406 C 10.671875 15.925781 11.175781 16.605469 12.1875 16.605469 C 12.855469 16.605469 13.332031 16.277344 13.617188 15.613281 L 15.019531 16.359375 C 14.351563 17.542969 13.351563 18.136719 12.015625 18.136719 C 10.984375 18.136719 10.15625 17.824219 9.539063 17.191406 C 8.917969 16.558594 8.609375 15.6875 8.609375 14.578125 C 8.609375 13.488281 8.925781 12.621094 9.566406 11.980469 C 10.207031 11.335938 11.003906 11.015625 11.957031 11.015625 C 13.371094 11.015625 14.378906 11.574219 14.992188 12.6875 Z M 20.066406 13.460938 C 19.78125 12.835938 19.359375 12.523438 18.808594 12.523438 C 17.777344 12.523438 17.261719 13.207031 17.261719 14.566406 C 17.261719 15.925781 17.777344 16.605469 18.808594 16.605469 C 19.476563 16.605469 19.945313 16.277344 20.210938 15.613281 L 21.644531 16.359375 C 20.976563 17.542969 19.976563 18.136719 18.644531 18.136719 C 17.613281 18.136719 16.789063 17.824219 16.171875 17.191406 C 15.550781 16.558594 15.242188 15.6875 15.242188 14.578125 C 15.242188 13.488281 15.554688 12.621094 16.183594 11.980469 C 16.8125 11.335938 17.613281 11.015625 18.585938 11.015625 C 19.996094 11.015625 21.003906 11.574219 21.613281 12.6875 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 60.03125 10.878906 C 60.03125 15.128906 58.308594 18.578125 56.183594 18.578125 C 54.054688 18.578125 52.332031 15.128906 52.332031 10.878906 C 52.332031 6.625 54.054688 3.179688 56.183594 3.179688 C 58.308594 3.179688 60.03125 6.625 60.03125 10.878906 Z "/>
+<path style=" stroke:none;fill-rule:nonzero;fill:rgb(0%,0%,0%);fill-opacity:1;" d="M 56.429688 2.417969 C 51.582031 2.417969 50.359375 6.996094 50.359375 10.875 C 50.359375 14.757813 51.582031 19.332031 56.429688 19.332031 C 61.28125 19.332031 62.5 14.757813 62.5 10.875 C 62.5 6.996094 61.28125 2.417969 56.429688 2.417969 Z M 56.429688 5.609375 C 56.628906 5.609375 56.808594 5.636719 56.976563 5.679688 C 57.324219 5.980469 57.496094 6.394531 57.160156 6.976563 L 53.929688 12.914063 C 53.832031 12.160156 53.816406 11.425781 53.816406 10.875 C 53.816406 9.167969 53.9375 5.609375 56.429688 5.609375 Z M 58.847656 8.34375 C 59.019531 9.257813 59.042969 10.207031 59.042969 10.875 C 59.042969 12.585938 58.925781 16.144531 56.429688 16.144531 C 56.234375 16.144531 56.054688 16.125 55.886719 16.082031 C 55.851563 16.074219 55.824219 16.0625 55.792969 16.050781 C 55.742188 16.035156 55.6875 16.019531 55.640625 16 C 55.082031 15.765625 54.734375 15.335938 55.238281 14.582031 Z "/>
+</g>
+</svg>
diff --git a/_site/assets/codebase.svg b/_site/assets/codebase.svg
new file mode 100644
index 00000000..bdd5de50
--- /dev/null
+++ b/_site/assets/codebase.svg
@@ -0,0 +1,134 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>Public code codebase</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<g clip-path="url(#clip0)">
+<rect width="595" height="842" fill="#00BA8D"/>
+<path d="M275.383 549.165L275.383 602.307C275.383 608.457 272.553 614.265 267.71 618.056L233.53 644.809C228.299 648.903 225.243 655.177 225.243 661.82V661.82C225.243 667.785 220.407 672.621 214.442 672.621L-121 672.621" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M280.755 549.165L280.755 603.744C280.755 609.061 278.638 614.16 274.871 617.913L247.245 645.433C243.478 649.186 241.36 654.285 241.36 659.602L241.36 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M296.872 549.165L296.872 612.05L296.44 651.296L296.44 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M291.5 549.165L291.5 608.832C291.5 610.964 291.159 613.082 290.49 615.106L279.542 648.24C278.874 650.264 278.533 652.382 278.533 654.514L278.533 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M286.126 549.165L286.126 605.779C286.126 609.862 284.877 613.847 282.546 617.198L262.414 646.147C260.083 649.499 258.834 653.484 258.834 657.566L258.834 671.068C258.834 682.114 249.88 691.068 238.834 691.068L156.487 691.068C150.964 691.068 146.487 695.545 146.487 701.068L146.487 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M179.125 691.068L85.1144 691.068C79.6284 691.068 75.1812 695.516 75.1812 701.002V701.002C75.1812 706.488 70.7339 710.935 65.2479 710.935L-18.8297 710.935C-24.3157 710.935 -28.7629 715.382 -28.7629 720.868V720.868" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M325.523 549.165L325.523 602.307C325.523 608.457 328.352 614.265 333.195 618.056L367.989 645.29C372.832 649.081 375.662 654.889 375.662 661.039L375.662 844.324" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M320.15 549.165L320.151 603.739C320.151 609.057 322.268 614.156 326.035 617.908L353.661 645.429C357.428 649.182 359.546 654.281 359.546 659.598L359.546 850" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M304.034 549.165L304.467 844.321" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M309.406 549.165L309.406 610.226C309.406 611.44 309.517 612.651 309.736 613.844L319.36 666.172C321.106 675.663 329.38 682.554 339.03 682.554L533.75 682.554C544.795 682.554 553.75 691.509 553.75 702.554L553.75 720.159L553.75 844.324" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M314.779 549.165L314.779 605.78C314.779 609.862 316.028 613.847 318.359 617.198L336.103 642.714C339.842 648.09 345.975 651.296 352.523 651.296L723.324 651.296" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="121.655" cy="672.621" r="4.25709" fill="#FFF500"/>
+<circle cx="476.412" cy="682.554" r="4.25709" fill="#FFF500"/>
+<circle cx="571.488" cy="651.336" r="4.25709" fill="#FFF500"/>
+<circle cx="279.167" cy="654.174" r="4.25709" fill="#FFF500"/>
+<circle cx="459.384" cy="651.336" r="2.83806" fill="#FFF500"/>
+<circle cx="304" cy="639.274" r="3.54758" fill="#FFF500"/>
+<circle cx="296.195" cy="678.297" r="2.83806" fill="#FFF500"/>
+<circle cx="487.765" cy="651.336" r="2.83806" fill="#FFF500"/>
+<circle cx="551.621" cy="651.336" r="2.83806" fill="#FFF500"/>
+<path d="M380.411 0V237.001C380.411 243.005 377.713 248.692 373.063 252.49L356.557 265.972C351.907 269.77 349.209 275.457 349.209 281.462V317.154" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M387.345 0V241.521C387.345 247.45 384.714 253.073 380.163 256.873L363.903 270.449C359.352 274.249 356.721 279.873 356.721 285.802V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M374.633 0V241.521C374.633 247.45 372.002 253.073 367.451 256.873L351.191 270.449C346.64 274.249 344.009 279.873 344.009 285.802V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M394.856 0V246.3C394.856 252.322 392.142 258.024 387.468 261.822L371.043 275.168C366.369 278.966 363.655 284.668 363.655 290.69V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M368.855 0V246.3C368.855 252.322 366.141 258.024 361.467 261.822L345.041 275.168C340.367 278.966 337.653 284.668 337.653 290.69V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M402.368 0V250.835C402.368 256.857 399.654 262.558 394.981 266.356L378.553 279.706C373.88 283.504 371.166 289.206 371.166 295.228V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M363.655 0V250.835C363.655 256.857 360.941 262.558 356.268 266.356L339.84 279.706C335.166 283.504 332.453 289.206 332.453 295.228V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M409.302 0V255.78C409.302 261.707 406.672 267.329 402.123 271.129L385.857 284.716C381.307 288.516 378.678 294.138 378.678 300.066V326.762" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M356.721 0V255.78C356.721 261.707 354.092 267.329 349.542 271.129L333.276 284.716C328.727 288.516 326.097 294.138 326.097 300.066V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M416.813 0V260.419C416.813 266.428 414.111 272.119 409.454 275.917L392.971 289.362C388.314 293.16 385.611 298.851 385.611 304.86V331.019" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M351.521 0V260.419C351.521 266.428 348.818 272.119 344.162 275.917L327.678 289.362C323.021 293.16 320.319 298.851 320.319 304.86V316.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M226.17 0V155.161C226.17 158.539 227.026 161.862 228.658 164.821L254.884 212.367C256.516 215.325 257.372 218.649 257.372 222.027V317.154" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M219.236 0V164.999C219.236 168.315 220.061 171.579 221.635 174.497L247.461 222.356C249.036 225.274 249.86 228.538 249.86 231.854V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M231.948 0V164.999C231.948 168.315 232.773 171.579 234.347 174.497L260.173 222.356C261.748 225.274 262.572 228.538 262.572 231.854V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M211.725 0V175.847C211.725 179.24 212.588 182.578 214.234 185.546L240.417 232.764C242.063 235.732 242.927 239.07 242.927 242.463V316.433" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M237.726 0V175.847C237.726 179.24 238.59 182.578 240.235 185.546L266.419 232.764C268.065 235.732 268.928 239.07 268.928 242.463V316.433" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M204.213 0V185.911C204.213 189.304 205.077 192.642 206.722 195.609L232.907 242.838C234.552 245.806 235.415 249.143 235.415 252.536V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M242.926 0V185.911C242.926 189.304 243.79 192.642 245.435 195.609L271.62 242.838C273.265 245.806 274.128 249.143 274.128 252.536V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M197.28 0V196.644C197.28 199.958 198.104 203.221 199.677 206.139L225.506 254.021C227.08 256.939 227.904 260.202 227.904 263.516V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M249.86 0V196.644C249.86 199.958 250.684 203.221 252.258 206.139L278.087 254.021C279.66 256.939 280.484 260.202 280.484 263.516V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M189.768 0V207.151C189.768 210.533 190.626 213.861 192.262 216.822L218.476 264.277C220.112 267.238 220.97 270.565 220.97 273.948V330.634" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M255.061 0V207.151C255.061 210.533 255.918 213.861 257.554 216.822L283.769 264.277C285.404 267.238 286.262 270.565 286.262 273.948V316.434" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="403.332" cy="207.888" r="3.54758" fill="#FFF500"/>
+<circle cx="189.768" cy="211.436" r="4.25709" fill="#FFF500"/>
+<circle cx="219.568" cy="244.073" r="4.25709" fill="#FFF500"/>
+<circle cx="224.534" cy="203.631" r="2.12855" fill="#FFF500"/>
+<circle cx="197.573" cy="124.165" r="2.12855" fill="#FFF500"/>
+<circle cx="246.529" cy="221.369" r="4.25709" fill="#FFF500"/>
+<circle cx="257.172" cy="284.516" r="3.54758" fill="#FFF500"/>
+<circle cx="363.599" cy="305.801" r="3.54758" fill="#FFF500"/>
+<path d="M-121 493.823L27.0723 493.823C33.4516 493.823 39.4483 490.78 43.2146 485.631L87.2815 425.387C91.0478 420.239 97.0445 417.195 103.424 417.195L194.025 417.195" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 510.851L37.7624 510.851C44.0562 510.851 49.983 507.889 53.7602 502.854L98.1875 443.64C101.965 438.605 107.891 435.643 114.185 435.643L194.025 435.643" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 479.633L37.1175 479.633C43.434 479.633 49.3792 476.649 53.1538 471.584L97.2088 412.472C100.983 407.408 106.929 404.424 113.245 404.424L194.025 404.424" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 529.299L48.5065 529.299C54.892 529.299 60.8938 526.25 64.6592 521.092L108.624 460.877C112.389 455.72 118.391 452.671 124.777 452.671L194.025 452.671" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 465.442L47.7296 465.442C54.0633 465.442 60.0227 462.442 63.7951 457.354L108.619 396.902C112.391 391.815 118.35 388.815 124.684 388.815L194.025 388.815" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 547.746L58.514 547.746C64.899 547.746 70.9003 544.698 74.6658 539.541L118.639 479.324C122.405 474.167 128.406 471.118 134.791 471.118L194.025 471.118" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 452.671L56.9474 452.671C63.2844 452.671 69.2466 449.668 73.0185 444.576L117.787 384.139C121.559 379.047 127.521 376.043 133.858 376.043L194.025 376.043" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 564.775L69.2272 564.775C75.5198 564.775 81.4454 561.813 85.2228 556.78L129.672 497.56C133.449 492.527 139.375 489.566 145.667 489.566L194.025 489.566" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 435.643L69.2272 435.643C75.5198 435.643 81.4454 432.681 85.2228 427.648L129.672 368.428C133.449 363.395 139.375 360.434 145.667 360.434H194.025" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M-121 583.222L79.6379 583.222C86.0107 583.222 92.002 580.185 95.7692 575.045L139.945 514.771C143.712 509.631 149.703 506.594 156.076 506.594L193.309 506.594" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M208.216 346.244H156.488C150.192 346.244 144.265 349.208 140.488 354.244L95.0169 414.871C91.2398 419.907 85.312 422.871 79.0169 422.871L-32.0732 422.871C-44.1226 422.871 -55.7667 418.52 -64.8632 410.618L-85.6531 392.558C-97.8729 381.943 -90.3655 361.853 -74.1789 361.853V361.853C-57.8228 361.853 -50.41 382.297 -62.9651 392.78L-85.0885 411.252C-94.0797 418.759 -105.421 422.871 -117.134 422.871L-121 422.871" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="33.6746" cy="547.746" r="2.83806" fill="#FFF500"/>
+<circle cx="73.4075" cy="446.995" r="4.25709" fill="#FFF500"/>
+<circle cx="147.197" cy="435.643" r="4.25709" fill="#FFF500"/>
+<path d="M723.324 353.458L572.459 353.458C568.063 353.458 563.791 354.906 560.301 357.578L515.326 392.011C511.836 394.683 507.563 396.131 503.168 396.131L411.137 396.131" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 343.975L562.744 343.975C558.421 343.975 554.214 345.376 550.754 347.967L505.495 381.865C502.035 384.457 497.829 385.858 493.506 385.858L411.847 385.858" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 361.36L562.744 361.36C558.421 361.36 554.214 362.761 550.754 365.352L505.495 399.251C502.035 401.842 497.829 403.243 493.506 403.243L411.847 403.243" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 333.702L552.081 333.702C547.668 333.702 543.379 335.161 539.882 337.853L495.224 372.224C491.727 374.915 487.439 376.375 483.026 376.375L411.847 376.375" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 369.263L552.081 369.263C547.668 369.263 543.379 370.722 539.882 373.413L495.224 407.785C491.727 410.476 487.439 411.936 483.026 411.936L411.847 411.936" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 323.429L648.19 323.429C646.189 323.429 644.568 321.807 644.568 319.806V319.806C644.568 316.885 641.287 315.166 638.885 316.827L631.483 321.948C630.088 322.912 628.433 323.429 626.738 323.429L542.163 323.429C537.751 323.429 533.463 324.888 529.966 327.579L485.298 361.952C481.802 364.643 477.513 366.102 473.101 366.102L411.847 366.102" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M721.195 376.375L542.163 376.375C537.751 376.375 533.463 377.834 529.966 380.525L485.298 414.898C481.802 417.589 477.513 419.048 473.101 419.048L411.847 419.048" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 313.946L665.199 313.946C660.074 313.946 655.92 309.791 655.92 304.667V304.667C655.92 296.417 645.961 292.269 640.105 298.08L628.772 309.324C625.789 312.285 621.756 313.946 617.553 313.946L531.563 313.946C527.241 313.946 523.036 315.346 519.576 317.936L474.294 351.839C470.834 354.429 466.629 355.829 462.307 355.829L411.847 355.829" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M722.614 385.858L531.563 385.858C527.241 385.858 523.036 387.257 519.576 389.848L474.294 423.75C470.834 426.34 466.629 427.74 462.307 427.74L411.847 427.74" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M721.905 303.673L687.001 303.673C678.064 303.673 670.82 296.428 670.82 287.492V287.492C670.82 272.683 652.576 265.655 642.641 276.635L624.131 297.092C620.339 301.282 614.952 303.673 609.301 303.673L521.232 303.673C516.832 303.673 512.554 305.124 509.062 307.801L464.175 342.217C460.684 344.895 456.406 346.346 452.006 346.346L392.69 346.346" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M723.324 392.97L521.232 392.97C516.832 392.97 512.554 394.421 509.063 397.098L464.176 431.514C460.684 434.192 456.406 435.643 452.006 435.643L411.847 435.643" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<circle cx="571.488" cy="313.606" r="2.83806" fill="#FFF500"/>
+<path d="M79.0835 95.0751H152.873V201.503H79.0835V95.0751Z" fill="#5B57CA"/>
+<path d="M81.9215 97.9132H155.711V204.341H81.9215V97.9132Z" fill="#5B57CA"/>
+<path d="M84.7596 100.751H158.549V207.179H84.7596V100.751Z" fill="#5B57CA"/>
+<path d="M87.5977 103.589H161.387V210.017H87.5977V103.589Z" fill="#5B57CA"/>
+<path d="M90.4357 106.427H164.225V212.855H90.4357V106.427Z" fill="#5B57CA"/>
+<path d="M93.2738 109.265H167.063V215.693H93.2738V109.265Z" fill="#5B57CA"/>
+<path d="M130.352 181.098L130.352 181.098L129.675 181.011L129.796 181.683L129.796 181.683L129.796 181.683L129.797 181.684L129.798 181.69L129.802 181.718C129.806 181.744 129.813 181.785 129.82 181.838C129.835 181.946 129.855 182.106 129.873 182.311C129.91 182.722 129.941 183.313 129.917 184.023C129.87 185.447 129.605 187.332 128.739 189.211C127.877 191.082 126.415 192.955 123.955 194.366C121.489 195.78 117.991 196.745 113.033 196.745H112.948H112.864H112.779H112.695H112.61H112.524H112.439H112.353H112.268H112.182H112.096H112.01H111.923H111.837H111.75H111.663H111.576H111.489H111.402H111.314H111.226H111.139H111.051H110.962H110.874H110.786H110.697H110.608H110.52H110.431H110.341H110.252H110.163H110.073H109.983H109.893H109.803H109.713H109.623H109.533H109.442H109.351H109.261H109.17H109.079H108.988H108.896H108.805H108.713H108.622H108.53H108.438H108.346H108.254H108.162H108.07H107.977H107.885H107.792H107.699H107.606H107.513H107.42H107.327H107.234H107.141H107.047H106.954H106.86H106.766H106.673H106.579H106.485H106.391H106.297H106.202H106.108H106.014H105.919H105.825H105.73H105.636H105.541H105.446H105.351H105.256H105.161H105.066H104.971H104.876H104.78H104.685H104.59H104.494H104.399H104.303H104.207H104.112H104.016H103.92H103.824H103.728H103.633H103.537H103.441H103.345H103.248H103.152H103.056H102.96H102.864H102.768H102.671H102.575H102.479H102.382H102.286H102.189H102.093H101.996H101.9H101.803H101.707H101.61H101.514H101.417H101.32H101.224H101.127H101.031H100.934H100.837H100.741H100.644H100.547H100.451H100.354H100.257H100.161H100.064H99.9675H99.8709H99.7743H99.6777H99.5811H99.4845H99.3879H99.2914H99.1949H99.0983H99.0019H98.9054H98.8089H98.7125H98.6161H98.5197H98.4234H98.3271H98.2308H98.1345H98.0383H97.9421H97.846H97.7499H97.6538H97.5578H97.4618H97.3658H97.2699H97.1741H97.0783H96.9825H96.8868H96.7911H96.6955H96.6H96.5045H96.409H96.3137H96.2183H96.1231H96.0279H95.9327H95.8377H95.7427H95.6477H95.5529H95.4581H95.3633H95.2687H95.1741H95.0796H94.9852H94.8908H94.7966H94.7024H94.6083H94.5143H94.4203H94.3265H94.2327H94.1391H94.0455H93.952H93.8586H93.7653H93.6721H93.579H93.486H93.3931H93.3003H93.2076H93.115H93.0225H92.9302H92.8379H92.7457H92.6537H92.5617H92.4699H92.3782H92.2866H92.1951H92.1038H92.0125H91.9214H91.8304H91.7396H91.6488H91.5582H91.4678H91.3774H91.2872H91.1971H91.1071H91.0173H90.9277H90.8381H90.7487H90.6595H90.5703H90.4814H90.3925H90.3039H90.2153H90.127H90.0387H89.9506H89.8627H89.7749H89.6873H89.5999H89.5126H89.4254H89.3385H89.2516H89.165H89.0785H88.9922H88.9061H88.8201H88.7343H88.6486H88.5632H88.4779H88.3928H88.3079H88.2231H88.1385H88.0542H87.9699H87.8859H87.8021H87.7185H87.635H87.5517H87.4687H87.3858H87.3031H87.2206H87.1383H87.0562H86.9743H86.8926H86.8111H86.7298H86.6488H86.5679H86.4872H86.4067H86.3265H86.2465H86.1666H86.087H86.0076H85.9285H85.8495H85.7708H85.6923H85.614H85.5359H85.4581H85.3805H85.3031H85.2259H85.149H85.0723H84.9958H84.9196H84.8436H84.7679H84.6924H84.6171H84.5421H84.4673H84.3928H84.3185H84.2444H84.1706H84.0971H84.0238H83.9508H83.878H83.8055H83.7332H83.6612H83.5894H83.5179H83.4467H83.3757H83.305H83.2346H83.1644H83.0945H83.0249H82.9555H82.8865H82.8177H82.7491H82.6809H82.6129H82.5452H82.4778H82.4107H82.3438H82.2773H82.211H82.145H82.0793H82.0139H81.9488H81.884H81.8194H81.7552H81.6913H81.6277H81.5643H81.5013H81.4386H81.3762H81.3141H81.2523H81.1908H81.1296H81.0687H81.0081H80.9479H80.888H80.8284H80.7691H80.7101H80.6514H80.5931H80.5351H80.4774H80.42H80.363H80.3063H80.25H80.1939H80.1382H80.0828H80.0278H79.9731H79.9188H79.8647H79.8111H79.7577H79.7047H79.6521H79.5998H79.5479H79.4963H79.445H79.3941H79.3436H79.2934H79.2436H79.1941H79.145H79.0962H79.0479H78.9998H78.9522H78.9049H78.8579H78.8114H78.7652H78.7194H78.6739H78.6289H78.5842H78.5399H78.4959H78.4524H78.4092H78.3664H78.324H78.282H78.2403H78.1991H78.1582H78.1177H78.0776H78.038H77.9987H77.9598H77.9213H77.8832H77.8455H77.8082H77.7713H77.7348H77.6987H77.663H77.6277H77.5929H77.5584H77.5244H77.4908H77.4576H77.4248H77.3924H77.3604H77.3289H77.2978H77.2671H77.2368H77.207H77.1776H77.1486H77.12H77.0919H77.0642H77.037H77.0101H76.9838H76.9578H76.9323H76.9072H76.8826H76.8584H76.8347H76.8114H76.7886H76.7662H76.7454V91.318H149.535V91.3349V91.3719V91.4101V91.4495V91.4901V91.5319V91.575V91.6192V91.6647V91.7113V91.7591V91.8082V91.8584V91.9098V91.9623V92.0161V92.071V92.127V92.1842V92.2426V92.3021V92.3628V92.4246V92.4875V92.5516V92.6167V92.683V92.7504V92.819V92.8886V92.9593V93.0312V93.1041V93.1781V93.2532V93.3294V93.4066V93.4849V93.5643V93.6447V93.7262V93.8088V93.8924V93.977V94.0627V94.1494V94.2371V94.3259V94.4156V94.5064V94.5982V94.691V94.7848V94.8796V94.9754V95.0722V95.17V95.2687V95.3684V95.4691V95.5708V95.6734V95.7769V95.8815V95.9869V96.0933V96.2007V96.3089V96.4181V96.5283V96.6393V96.7513V96.8641V96.9779V97.0926V97.2082V97.3246V97.442V97.5602V97.6793V97.7993V97.9201V98.0418V98.1644V98.2878V98.4121V98.5372V98.6632V98.79V98.9177V99.0461V99.1754V99.3055V99.4364V99.5681V99.7007V99.834V99.9681V100.103V100.239V100.375V100.513V100.651V100.789V100.929V101.069V101.21V101.352V101.495V101.638V101.782V101.927V102.072V102.219V102.366V102.513V102.662V102.811V102.961V103.111V103.262V103.414V103.567V103.72V103.874V104.028V104.183V104.339V104.496V104.653V104.811V104.969V105.128V105.288V105.449V105.61V105.771V105.933V106.096V106.26V106.424V106.588V106.753V106.919V107.086V107.253V107.42V107.588V107.757V107.926V108.096V108.266V108.437V108.609V108.78V108.953V109.126V109.299V109.474V109.648V109.823V109.999V110.175V110.351V110.528V110.706V110.884V111.062V111.241V111.421V111.601V111.781V111.962V112.143V112.325V112.507V112.69V112.873V113.056V113.24V113.424V113.609V113.794V113.979V114.165V114.352V114.538V114.725V114.913V115.101V115.289V115.477V115.666V115.856V116.045V116.235V116.425V116.616V116.807V116.998V117.19V117.382V117.574V117.767V117.96V118.153V118.347V118.54V118.735V118.929V119.124V119.319V119.514V119.709V119.905V120.101V120.297V120.494V120.69V120.887V121.085V121.282V121.48V121.678V121.876V122.074V122.273V122.471V122.67V122.869V123.069V123.268V123.468V123.668V123.868V124.068V124.268V124.469V124.67V124.87V125.071V125.272V125.474V125.675V125.876V126.078V126.28V126.482V126.684V126.886V127.088V127.29V127.492V127.695V127.897V128.1V128.302V128.505V128.708V128.911V129.113V129.316V129.519V129.722V129.925V130.128V130.331V130.535V130.738V130.941V131.144V131.347V131.55V131.753V131.956V132.16V132.363V132.566V132.769V132.972V133.175V133.378V133.58V133.783V133.986V134.189V134.391V134.594V134.796V134.999V135.201V135.403V135.605V135.807V136.009V136.211V136.413V136.615V136.816V137.017V137.219V137.42V137.621V137.821V138.022V138.223V138.423V138.623V138.823V139.023V139.223V139.422V139.621V139.82V140.019V140.218V140.417V140.615V140.813V141.011V141.209V141.406V141.603V141.8V141.997V142.193V142.39V142.586V142.781V142.977V143.172V143.367V143.561V143.756V143.95V144.144V144.337V144.53V144.723V144.916V145.108V145.3V145.492V145.683V145.874V146.065V146.255V146.445V146.634V146.824V147.013V147.201V147.389V147.577V147.764V147.952V148.138V148.324V148.51V148.696V148.881V149.065V149.25V149.434V149.617V149.8V149.982V150.165V150.346V150.527V150.708V150.889V151.068V151.248V151.427V151.605V151.783V151.961V152.138V152.314V152.49V152.666V152.841V153.015V153.189V153.363V153.536V153.708V153.88V154.051V154.222V154.392V154.562V154.731V154.9V155.068V155.236V155.402V155.569V155.735V155.9V156.064V156.228V156.392V156.554V156.717V156.878V157.039V157.199V157.359V157.518V157.677V157.834V157.991V158.148V158.304V158.459V158.613V158.767V158.92V159.073V159.225V159.376V159.526V159.676V159.825V159.973V160.121V160.268V160.414V160.559V160.704V160.848V160.991V161.134V161.276V161.417V161.557V161.697V161.835V161.973V162.11V162.247V162.382V162.517V162.651V162.785V162.917V163.049V163.18V163.31V163.439V163.567V163.695V163.822V163.948V164.073V164.197V164.32V164.443V164.564V164.685V164.805V164.924V165.042V165.159V165.276V165.391V165.506V165.62V165.732V165.844V165.955V166.065V166.174V166.283V166.39V166.496V166.602V166.706V166.81V166.912V167.014V167.114V167.214C149.535 171.34 148.334 174.233 146.571 176.273C144.801 178.32 142.428 179.549 140.018 180.271C137.609 180.993 135.19 181.201 133.367 181.227C132.457 181.24 131.699 181.207 131.171 181.172C130.906 181.154 130.7 181.135 130.56 181.121C130.49 181.114 130.437 181.108 130.402 181.104L130.363 181.1L130.354 181.099L130.352 181.098L130.352 181.098Z" stroke="#FFF500"/>
+<path d="M76.2454 90.818L76.7454 90.818L76.7454 91.318L76.2454 91.318L76.2454 90.818ZM49.2838 90.818L49.2838 91.318L49.2838 90.818ZM49.2838 37.3948C34.6694 37.3948 22.8222 49.2421 22.8222 63.8564L21.8222 63.8564C21.8222 48.6898 34.1171 36.3948 49.2838 36.3948L49.2838 37.3948ZM75.7454 63.8564C75.7454 49.2421 63.8981 37.3948 49.2838 37.3948L49.2838 36.3948C64.4504 36.3948 76.7454 48.6898 76.7454 63.8564L75.7454 63.8564ZM75.7454 90.818L75.7454 63.8564L76.7454 63.8564L76.7454 90.818L75.7454 90.818ZM49.2838 90.318L76.2454 90.318L76.2454 91.318L49.2838 91.318L49.2838 90.318ZM22.8222 63.8564C22.8222 78.4708 34.6694 90.318 49.2838 90.318L49.2838 91.318C34.1171 91.318 21.8222 79.023 21.8222 63.8564L22.8222 63.8564Z" fill="#FFF500"/>
+<rect x="36.1882" y="60.7751" width="6.16265" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<rect x="46.2025" y="60.7751" width="6.16265" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<rect x="56.2168" y="60.7751" width="6.16266" height="6.16265" rx="3.08133" fill="#FFF500"/>
+<line x1="113.64" y1="115.442" x2="113.64" y2="172.622" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="0.5" y1="-0.5" x2="52.0137" y2="-0.5" transform="matrix(-0.999819 -0.0190427 0 -1 140.102 144.322)" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="125.578" y1="155.048" x2="103.207" y2="132.677" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="124.866" y1="132.677" x2="102.495" y2="155.048" stroke="#FFF500" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M115.269 215.693V329.925V329.925C115.269 346.285 134.981 354.555 146.653 343.091L149.184 340.606C152.913 336.943 157.93 334.891 163.157 334.891H218.149" stroke="#FFF500"/>
+<circle cx="115.269" cy="216.402" r="4.96661" fill="#FFF500"/>
+<circle cx="304.71" cy="414.357" r="252.588" fill="#FFF500" fill-opacity="0.1"/>
+<circle cx="304.71" cy="414.357" r="201.502" fill="#FFF500" fill-opacity="0.1"/>
+<circle cx="301.872" cy="421.452" r="146.16" fill="#FFF500"/>
+<rect x="480.97" y="121.396" width="94.7708" height="61.0451" fill="#5B57CA"/>
+<rect x="480.97" y="121.396" width="30.8005" height="16.6487" fill="#FF0F00"/>
+<path d="M490.921 125.36L486.499 129.799L490.921 134.238" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M501.845 125.36L506.267 129.799L501.845 134.238" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="0.5" y1="-0.5" x2="9.41277" y2="-0.5" transform="matrix(-0.498561 0.866854 -0.865192 -0.50144 498.415 125.36)" stroke="black" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="417" y="77" width="94.7708" height="61.0452" stroke="#FFF500"/>
+<path d="M511.771 92.0631L511.271 92.0631L511.271 92.5631L511.771 92.5631L511.771 92.0631ZM526.776 62.4369C534.785 62.4369 541.281 68.9552 541.281 77L542.281 77C542.281 68.4066 535.341 61.4369 526.776 61.4369L526.776 62.4369ZM512.271 77C512.271 68.9552 518.767 62.4369 526.776 62.4369L526.776 61.4369C518.211 61.4369 511.271 68.4066 511.271 77L512.271 77ZM512.271 92.0631L512.271 77L511.271 77L511.271 92.0631L512.271 92.0631ZM526.776 91.5631L511.771 91.5631L511.771 92.5631L526.776 92.5631L526.776 91.5631ZM541.281 77C541.281 85.0448 534.785 91.5631 526.776 91.5631L526.776 92.5631C535.341 92.5631 542.281 85.5935 542.281 77L541.281 77Z" fill="#5B57CA"/>
+<rect width="3.4298" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 534.064 75.2785)" fill="#5B57CA"/>
+<rect width="3.42979" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 528.491 75.2785)" fill="#5B57CA"/>
+<rect width="3.42981" height="3.44299" rx="1.7149" transform="matrix(-1 0 0 1 523.098 75.4144)" fill="#5B57CA"/>
+<path d="M291.339 580.795L161.653 519.09C156.069 516.433 154.397 509.279 158.225 504.422C164.225 496.809 174.203 493.533 183.548 496.107L277.795 522.075C285.614 524.229 293.973 523.126 300.966 519.015L414.444 452.313C419.354 449.426 416.389 441.888 410.828 443.121L370.7 452.013C363.596 453.587 356.342 454.381 349.065 454.381L290.213 454.381C282.723 454.381 276.238 449.177 274.618 441.864C272.756 433.462 277.885 425.095 286.218 422.942L335.318 410.258C351.699 406.026 367.402 399.506 381.963 390.889L424.413 365.769C441.932 355.403 462.196 350.629 482.5 352.087L609.463 361.201L609.463 497.377L524.106 497.377C515.98 497.377 507.938 499.028 500.468 502.229L316.047 581.279C308.124 584.675 299.123 584.498 291.339 580.795Z" fill="#5B57CA"/>
+<path d="M572.907 354.791C572.907 352.03 575.145 349.791 577.907 349.791H723.324V539.193L577.116 515.783C574.691 515.394 572.907 513.302 572.907 510.845V354.791Z" fill="#5F5AE0"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="595" height="842" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/collaboration.svg b/_site/assets/collaboration.svg
new file mode 100644
index 00000000..deec655b
--- /dev/null
+++ b/_site/assets/collaboration.svg
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+    <rdf:RDF>
+       <cc:Work rdf:about="">
+          <dc:format>image/svg+xml</dc:format>
+            <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+            <dc:title>Collaboration on public code</dc:title>
+            <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+       </cc:Work>
+       <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+            <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+            <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+            <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+       </cc:License>
+    </rdf:RDF>
+</metadata>
+<g clip-path="url(#clip0)">
+<rect width="595" height="842" fill="#56CCF2"/>
+<path d="M353.189 555.208L596 582L596 468.549L375.081 490.445C346.189 493.309 317.545 483.002 297.102 462.386L280.734 445.879C274.147 439.236 262.932 441.355 259.222 449.943C254.345 461.237 243.221 468.549 230.92 468.549L188.2 468.549C185.843 468.549 183.559 469.369 181.739 470.867L180.733 471.695C176.705 475.011 175.332 480.578 177.356 485.386C178.721 488.63 178.035 492.374 175.609 494.923L172.819 497.854C168.788 502.089 168.074 508.491 171.072 513.511C172.851 516.49 172.917 520.189 171.243 523.229L170.434 524.699C167.735 529.602 168.162 535.631 171.525 540.105C173.964 543.351 174.9 547.484 174.097 551.464L173.976 552.066C172.729 558.246 176.606 564.302 182.74 565.758L236.333 578.475C246.015 580.773 256.162 580.129 265.476 576.627L307.025 561.003C321.744 555.469 337.559 553.484 353.189 555.208Z" fill="#FFB7B7"/>
+<path d="M415.414 384.398L425.148 146L307.616 146L333.953 380.337C336.452 402.571 329.684 424.852 315.241 441.94L306.017 452.853C300.035 459.93 302.585 470.774 311.093 474.445C322.902 479.54 330.549 491.168 330.549 504.029L330.549 552.818C330.549 555.176 331.37 557.461 332.87 559.282L333.692 560.28C337.011 564.306 342.577 565.679 347.386 563.657C350.63 562.293 354.374 562.978 356.925 565.403L359.852 568.187C364.089 572.215 370.49 572.929 375.511 569.933C378.49 568.156 382.189 568.09 385.229 569.762L386.701 570.571C391.603 573.267 397.631 572.841 402.105 569.482C405.351 567.044 409.483 566.109 413.463 566.911L413.986 567.016C420.179 568.264 426.228 564.313 427.574 558.141L440.85 497.278C442.906 487.854 442.192 478.036 438.794 469.008L421.741 423.707C417.019 411.161 414.867 397.793 415.414 384.398Z" fill="#683838"/>
+<path d="M242.649 292.789L1.15043e-05 266L-4.95358e-09 379.451L220.785 357.556C249.666 354.691 278.299 364.999 298.729 385.613L315.084 402.116C321.669 408.76 332.883 406.642 336.59 398.054C341.464 386.763 352.584 379.451 364.882 379.451L411.81 379.451C414.167 379.451 416.452 378.631 418.272 377.132L419.274 376.306C423.301 372.989 424.674 367.423 422.651 362.614C421.286 359.37 421.972 355.626 424.397 353.076L427.184 350.147C431.213 345.911 431.927 339.509 428.931 334.489C427.152 331.51 427.087 327.811 428.76 324.771L429.569 323.3C432.266 318.397 431.839 312.369 428.479 307.895C426.04 304.649 425.105 300.516 425.907 296.537L426.018 295.983C427.266 289.795 423.344 283.744 417.186 282.356L359.216 269.29C349.694 267.144 339.752 267.832 330.616 271.269L288.836 286.988C274.111 292.528 258.287 294.515 242.649 292.789Z" fill="#FF7F80"/>
+<path d="M181.287 458.539L182.792 688L284.685 688L262.513 458.648C260.537 438.205 265.946 417.73 277.761 400.93L285.809 389.487C291.066 382.013 288.126 371.595 279.738 367.971C267.424 362.652 259.451 350.522 259.451 337.109L259.451 296.204C259.451 293.847 258.632 291.563 257.134 289.744L256.304 288.735C252.989 284.707 247.422 283.334 242.614 285.358C239.37 286.724 235.626 286.038 233.077 283.611L230.146 280.82C225.911 276.789 219.509 276.075 214.489 279.073C211.51 280.853 207.811 280.918 204.771 279.245L203.301 278.435C198.398 275.736 192.368 276.163 187.895 279.526C184.649 281.966 180.515 282.902 176.535 282.099L175.933 281.978C169.754 280.731 163.698 284.607 162.243 290.741L149.922 342.676C147.379 353.396 148.447 364.656 152.962 374.706L172.508 418.22C178.206 430.903 181.195 444.635 181.287 458.539Z" fill="#391F1F"/>
+<path d="M264.628 576.801L295.184 565.306C315.528 557.653 329 538.192 329 516.455C329 502.693 323.565 489.488 313.876 479.713L280.345 445.883C273.76 439.239 262.545 441.357 258.837 449.946C253.963 461.237 242.841 468.549 230.543 468.549L182.193 468.549C179.835 468.549 177.551 469.369 175.731 470.868L174.728 471.694C170.701 475.011 169.328 480.577 171.351 485.386C172.715 488.63 172.03 492.374 169.604 494.924L166.817 497.853C162.787 502.089 162.073 508.491 165.07 513.511C166.849 516.49 166.914 520.189 165.241 523.229L164.432 524.7C161.734 529.603 162.161 535.631 165.522 540.105C167.961 543.351 168.897 547.484 168.094 551.464L167.986 552.002C166.737 558.192 170.674 564.242 176.839 565.608L236.388 578.805C245.797 580.89 255.608 580.193 264.628 576.801Z" fill="#FFB7B7"/>
+<path d="M298.622 149.215C296.448 148.813 294.797 147.031 294.561 144.833L279 0L443 6.24721e-06L432.741 168.358C432.558 171.356 429.792 173.517 426.839 172.97L298.622 149.215Z" fill="black"/>
+<path d="M596 454L596 593L467.549 581.356C464.973 581.123 463 578.963 463 576.377L463 472.679C463 470.123 464.928 467.978 467.47 467.707L596 454Z" fill="#FF776E"/>
+<path d="M279.923 650C282.508 650 284.667 651.971 284.902 654.546L299 809L178 809C175.239 809 173 806.761 173 804L173 655C173 652.239 175.239 650 178 650L279.923 650Z" fill="white"/>
+<path d="M287.025 682C289.6 682 291.754 683.956 292.001 686.52L307 842L178 842C175.239 842 173 839.761 173 837L173 687C173 684.239 175.239 682 178 682L287.025 682Z" fill="#0000FF"/>
+<path d="M122 266C124.761 266 127 268.239 127 271L127 376C127 378.761 124.761 381 122 381L79 381L79 266L122 266Z" fill="#9F9F9F"/>
+<path d="M93 256C95.7614 256 98 258.239 98 261L98 386C98 388.761 95.7614 391 93 391L1.72836e-06 391L7.62939e-06 256L93 256Z" fill="#C4C4C4"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="595" height="842" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/collaborative-development.svg b/_site/assets/collaborative-development.svg
new file mode 100644
index 00000000..61961e20
--- /dev/null
+++ b/_site/assets/collaborative-development.svg
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>collaborative public code development</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="white"/>
+<rect width="595" height="842" fill="#FDBBAB"/>
+<rect x="132" y="324" width="200" height="150" fill="black"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M463 364C463 344.67 447.33 329 428 329C408.67 329 393 344.67 393 364L393 398C393 398.552 393.448 399 394 399L428 399C447.33 399 463 383.33 463 364Z" fill="black"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 444 360)" stroke="white"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 431 360)" stroke="white"/>
+<rect x="-0.5" y="0.5" width="7" height="7" rx="3.5" transform="matrix(-1 0 0 1 418 360)" stroke="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M262 289C262 269.67 277.67 254 297 254C316.33 254 332 269.67 332 289L332 323C332 323.552 331.552 324 331 324L297 324C277.67 324 262 308.33 262 289Z" fill="#5B57CA"/>
+<rect x="280.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="293.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="306.5" y="285.5" width="7" height="7" rx="3.5" stroke="white"/>
+<rect x="232" y="399" width="200" height="150" fill="#5B57CA"/>
+<rect x="232" y="399" width="100" height="75" fill="#FF0F00"/>
+<path d="M264.316 423L250 437.316L264.316 451.632" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M299.684 423L314 437.316L299.684 451.632" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<line x1="288.945" y1="424.366" x2="273.945" y2="450.347" stroke="black" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="343" y="419" width="78" height="2" rx="1" fill="black"/>
+<rect x="343" y="430.721" width="21" height="2" rx="1" fill="black"/>
+<rect x="388" y="442.442" width="21" height="2" rx="1" fill="black"/>
+<rect x="371" y="430.721" width="50" height="2" rx="1" fill="black"/>
+<rect width="21" height="2" rx="1" transform="matrix(-1 0 0 1 421 455.14)" fill="black"/>
+<rect width="50" height="2" rx="1" transform="matrix(-1 0 0 1 393 455.14)" fill="black"/>
+<rect x="343" y="442.442" width="39" height="2" rx="1" fill="black"/>
+<rect x="414" y="442.442" width="7" height="2" rx="1" fill="black"/>
+<rect x="143" y="419" width="78" height="2" rx="1" fill="white"/>
+<rect x="143" y="430.721" width="21" height="2" rx="1" fill="white"/>
+<rect x="188" y="442.442" width="21" height="2" rx="1" fill="white"/>
+<rect x="171" y="430.721" width="50" height="2" rx="1" fill="white"/>
+<rect width="21" height="2" rx="1" transform="matrix(-1 0 0 1 221 455.14)" fill="white"/>
+<rect width="50" height="2" rx="1" transform="matrix(-1 0 0 1 193 455.14)" fill="white"/>
+<rect x="143" y="442.442" width="39" height="2" rx="1" fill="white"/>
+<rect x="214" y="442.442" width="7" height="2" rx="1" fill="white"/>
+</svg>
diff --git a/_site/assets/dpg-badge.svg b/_site/assets/dpg-badge.svg
new file mode 100644
index 00000000..96e97b1d
--- /dev/null
+++ b/_site/assets/dpg-badge.svg
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 25.2.3, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 92.19 46.47" style="enable-background:new 0 0 92.19 46.47;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#2C269A;}
+	.st1{fill:#82DBE1;}
+	.st2{fill:none;stroke:#FFFFFF;stroke-miterlimit:10;}
+</style>
+<g>
+	<g>
+		<g>
+			<g>
+				<g>
+					<path class="st0" d="M73.52,44.58H8.51L1.24,30.55l0.16-0.34L14.71,1.89l64.95,0l7.25,14.07L73.52,44.58z M9.42,43.08h63.14
+						l12.68-27.08l-6.49-12.6H15.67L2.91,30.52L9.42,43.08z"/>
+				</g>
+			</g>
+		</g>
+	</g>
+	<g>
+		<g>
+			<g>
+				<g>
+					<path class="st1" d="M73.52,44.58H8.51L1.24,30.55l0.16-0.34L14.71,1.89l64.95,0l7.25,14.07L73.52,44.58z M9.42,43.08h63.14
+						l12.68-27.08l-6.49-12.6H15.67L2.91,30.52L9.42,43.08z"/>
+				</g>
+			</g>
+		</g>
+	</g>
+	<polygon class="st1" points="14.71,1.89 78.75,1.89 85.24,15.99 72.56,43.08 9.42,43.08 2.91,30.52 	"/>
+	<g>
+		<g>
+			<path class="st0" d="M18.05,15.4h4.11c4.14,0,7.52,3.36,7.52,7.52s-3.38,7.52-7.52,7.52h-4.11V15.4z M22.14,28.84
+				c3.34,0,5.94-2.53,5.94-5.92S25.48,17,22.14,17h-2.51v11.83H22.14z"/>
+			<path class="st0" d="M42.33,19.58c0,2.33-1.86,4.16-4.19,4.16h-3.79v6.7h-1.6V15.4h5.39C40.47,15.4,42.33,17.28,42.33,19.58z
+				 M40.73,19.61c0-1.6-1.23-2.66-2.73-2.66h-3.64v5.27h3.64C39.5,22.22,40.73,21.26,40.73,19.61z"/>
+			<path class="st0" d="M59.51,22.47v0.45c0,4.26-3.46,7.72-7.72,7.72c-4.29,0-7.72-3.46-7.72-7.72c0-4.26,3.44-7.72,7.72-7.72
+				c2.88,0,5.39,1.58,6.69,3.91l-1.38,0.78c-1.03-1.86-3.03-3.08-5.31-3.08c-3.39,0-6.12,2.71-6.12,6.12s2.73,6.12,6.12,6.12
+				c3.03,0,5.54-2.16,6.02-5.07h-6.04v-1.5H59.51z"/>
+		</g>
+	</g>
+	<g>
+		<g>
+			<rect x="67.42" y="11.04" class="st0" width="19.92" height="19.92"/>
+			
+				<rect x="67.38" y="10.96" transform="matrix(0.866 0.5 -0.5 0.866 20.8201 -35.8665)" class="st0" width="19.92" height="19.92"/>
+			<rect x="67.38" y="10.96" transform="matrix(0.866 -0.5 0.5 0.866 -0.0975 41.4714)" class="st0" width="19.92" height="19.92"/>
+		</g>
+		<polyline class="st2" points="72.34,21.15 76.12,24.93 83.48,17.57 		"/>
+	</g>
+</g>
+</svg>
diff --git a/_site/assets/eco-system.svg b/_site/assets/eco-system.svg
new file mode 100644
index 00000000..02706113
--- /dev/null
+++ b/_site/assets/eco-system.svg
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>ecosystem around public code development</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="#FDBBAB"/>
+<g transform="scale(1.4) translate(0 75)">
+    <circle cx="352.5" cy="88.5" r="22.5" fill="#FFF500"/>
+    <path d="M324 117L323 117L323 118L324 118L324 117ZM352.5 61C367.688 61 380 73.3122 380 88.5L382 88.5C382 72.2076 368.792 59 352.5 59L352.5 61ZM325 88.5C325 73.3122 337.312 61 352.5 61L352.5 59C336.208 59 323 72.2076 323 88.5L325 88.5ZM325 117L325 88.5L323 88.5L323 117L325 117ZM352.5 116L324 116L324 118L352.5 118L352.5 116ZM380 88.5C380 103.688 367.688 116 352.5 116L352.5 118C368.792 118 382 104.792 382 88.5L380 88.5Z" fill="#5B57CA"/>
+    <path d="M344.364 86.3492C344.05 85.8955 343.427 85.7829 342.973 86.0977C342.519 86.4126 342.406 87.0356 342.721 87.4894L344.364 86.3492ZM350.855 97.4571L350.033 98.0272C350.227 98.307 350.551 98.4688 350.891 98.4565C351.231 98.4442 351.542 98.2595 351.715 97.9665L350.855 97.4571ZM362.318 80.0522C362.599 79.5769 362.442 78.9636 361.966 78.6823C361.491 78.401 360.878 78.5582 360.597 79.0335L362.318 80.0522ZM342.721 87.4894L350.033 98.0272L351.676 96.8871L344.364 86.3492L342.721 87.4894ZM351.715 97.9665L362.318 80.0522L360.597 79.0335L349.994 96.9478L351.715 97.9665Z" fill="#5B57CA"/>
+    <path d="M160.915 108.133L163.003 120.061C163.276 121.623 162.24 123.113 160.681 123.402C159.422 123.635 158.159 123.011 157.579 121.87L152.417 111.721C149.754 106.485 143.713 103.922 138.097 105.644L132.207 107.45C127.792 108.804 123.034 106.861 120.829 102.804L114.609 91.3608L147.998 95.7539C154.546 96.6154 159.776 101.628 160.915 108.133Z" fill="#0D06C1"/>
+    <path d="M172.397 108.556L176.264 129.116C176.605 130.927 175.409 132.669 173.598 133.003C172.133 133.273 170.667 132.536 170.009 131.2L162.92 116.788C157.62 106.015 145.304 100.657 133.809 104.125L129.021 105.57C122.644 107.494 116.204 102.763 116.133 96.1031L116.023 85.8799L150.764 88.9444C161.555 89.8963 170.395 97.9104 172.397 108.556Z" fill="#241ED3"/>
+    <path d="M173.559 102.552L187.461 124.065C188.586 125.806 188.037 128.133 186.253 129.186C184.77 130.062 182.878 129.781 181.712 128.514L166.482 111.948C158.659 103.44 146.644 100.182 135.595 103.573L129.123 105.559C122.733 107.52 116.254 102.78 116.189 96.096L116.101 86.9952L151.969 89.7161C160.777 90.3843 168.765 95.1336 173.559 102.552Z" fill="#403ADD"/>
+    <path d="M217 301.057C195.471 301.057 174.608 293.592 157.965 279.934C141.323 266.276 129.931 247.27 125.731 226.155C121.531 205.039 124.782 183.12 134.931 164.133C145.08 145.146 161.498 130.265 181.389 122.027C201.279 113.788 223.411 112.7 244.013 118.95C264.615 125.2 282.413 138.399 294.374 156.3C306.335 174.201 311.719 195.696 309.609 217.121C307.499 238.547 298.025 258.578 282.801 273.801L217 208L217 301.057Z" fill="#FF6666"/>
+    <path d="M217 150.614C227.073 150.614 236.969 153.265 245.693 158.302C254.417 163.339 261.661 170.583 266.698 179.307C271.735 188.031 274.386 197.927 274.386 208C274.386 218.073 271.735 227.969 266.698 236.693C261.661 245.417 254.417 252.661 245.693 257.698C236.969 262.735 227.073 265.386 217 265.386C206.927 265.386 197.031 262.735 188.307 257.698C179.583 252.661 172.339 245.417 167.302 236.693L217 208L217 150.614Z" fill="#FFF500"/>
+    <path d="M217 228C213.044 228 209.178 226.827 205.889 224.629C202.6 222.432 200.036 219.308 198.522 215.654C197.009 211.999 196.613 207.978 197.384 204.098C198.156 200.219 200.061 196.655 202.858 193.858C205.655 191.061 209.219 189.156 213.098 188.384C216.978 187.613 220.999 188.009 224.654 189.522C228.308 191.036 231.432 193.6 233.629 196.889C235.827 200.178 237 204.044 237 208L217 208L217 228Z" fill="#5B57CA"/>
+    <path d="M240.846 338.808L230.88 313.476C230.014 311.274 231.091 308.786 233.289 307.91C235.313 307.104 237.62 307.94 238.658 309.855L243.653 319.073C250.138 331.041 263.45 337.635 276.9 335.542L294.731 332.766L282.229 358.794L266.76 357.758C255.184 356.984 245.093 349.604 240.846 338.808Z" fill="#0D06C1"/>
+    <path d="M230.062 348.809L201.522 322.841C199.553 321.05 199.76 317.894 201.946 316.375C203.314 315.425 205.118 315.386 206.526 316.278L216.409 322.538C230.056 331.181 245.837 335.858 261.99 336.047L284.449 336.308L278.525 364.883L242.767 355.671C238.037 354.452 233.675 352.097 230.062 348.809Z" fill="#241ED3"/>
+    <path d="M228.222 356.834L182.375 335.491C180.456 334.598 179.457 332.455 180.004 330.411C180.637 328.051 183.083 326.672 185.429 327.352L215.834 336.17C226.445 339.248 237.431 340.845 248.479 340.917L275.724 341.094L276.818 363.72L237.641 359.46C234.379 359.106 231.197 358.218 228.222 356.834Z" fill="#403ADD"/>
+    <path d="M224.679 364.935L183.047 349.069C180.573 348.127 179.213 345.466 179.898 342.909C180.62 340.215 183.352 338.581 186.067 339.22L225.434 348.48C230.065 349.57 234.89 349.542 239.508 348.4L267.282 341.529C270.542 340.722 270.804 336.189 267.658 335.013L263.649 333.514C259.35 331.906 254.817 331.01 250.23 330.86L234.755 330.356C231.524 330.251 229.001 327.528 229.142 324.299C229.266 321.48 231.398 319.158 234.196 318.794L271.356 313.967C282.595 312.507 294 312.968 305.084 315.331L363.332 327.746C372.469 329.694 379 337.764 379 347.106C379 358.039 370.138 366.901 359.205 366.901L305 366.901L235.362 366.901C231.711 366.901 228.091 366.235 224.679 364.935Z" fill="#5B57CA"/>
+    <circle cx="98.5" cy="205.5" r="7.5" fill="#FFF500"/>
+    <circle cx="335.5" cy="205.5" r="7.5" fill="#FFF500"/>
+    <ellipse cx="217.5" cy="208" rx="118.5" ry="119" stroke="#5B57CA" stroke-width="2"/>
+    <path fill-rule="evenodd" clip-rule="evenodd" d="M36 333C36 313.67 51.67 298 71 298C90.33 298 106 313.67 106 333L106 367C106 367.552 105.552 368 105 368L71 368C51.67 368 36 352.33 36 333Z" fill="#5B57CA"/>
+    <rect x="54.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <rect x="67.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <rect x="80.5" y="329.5" width="7" height="7" rx="3.5" stroke="white"/>
+    <circle cx="216.5" cy="88.5" r="13.5" fill="#FFF500"/>
+    <path d="M199.737 42L189 52.5L199.737 63" stroke="#FFF500" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+    <path d="M234.263 42L245 52.5L234.263 63" stroke="#FFF500" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
+    <circle cx="216.5" cy="52.5" r="7.5" fill="#FFF500"/>
+    <ellipse cx="217" cy="207.5" rx="30" ry="29.5" stroke="#5B57CA" stroke-width="2"/>
+    <circle cx="99" cy="206" r="44" stroke="#5B57CA" stroke-width="2"/>
+    <circle cx="217" cy="208" r="6" fill="#FF6666"/>
+    <circle cx="216" cy="327" r="12" fill="#FFF500"/>
+    <path d="M345 345.996C344.448 345.996 344 346.444 344 346.996C344 347.549 344.448 347.996 345 347.996V345.996ZM368.993 347.996C369.545 347.996 369.993 347.549 369.993 346.996C369.993 346.444 369.545 345.996 368.993 345.996V347.996ZM345 347.996L368.993 347.996V345.996L345 345.996V347.996Z" fill="#F55C5C"/>
+    <path d="M357.996 335C357.996 334.448 357.549 334 356.996 334C356.444 334 355.996 334.448 355.996 335H357.996ZM355.996 358.993C355.996 359.545 356.444 359.993 356.996 359.993C357.549 359.993 357.996 359.545 357.996 358.993H355.996ZM355.996 335V358.993H357.996V335H355.996Z" fill="#F55C5C"/>
+    <path d="M99.1344 161.009C98.5871 160.935 98.0833 161.318 98.0091 161.866C97.9349 162.413 98.3184 162.917 98.8656 162.991L99.1344 161.009ZM216.866 178.991C217.413 179.065 217.917 178.682 217.991 178.134C218.065 177.587 217.682 177.083 217.134 177.009L216.866 178.991ZM98.8656 162.991L216.866 178.991L217.134 177.009L99.1344 161.009L98.8656 162.991Z" fill="#5B57CA"/>
+    <path d="M212.886 236.007C213.434 235.943 213.93 236.337 213.993 236.886C214.057 237.434 213.663 237.93 213.114 237.993L212.886 236.007ZM100.114 250.993C99.5656 251.057 99.0697 250.663 99.0065 250.114C98.9434 249.566 99.337 249.07 99.8857 249.007L100.114 250.993ZM213.114 237.993L100.114 250.993L99.8857 249.007L212.886 236.007L213.114 237.993Z" fill="#5B57CA"/>
+    <circle cx="128.5" cy="205.5" r="11.5" fill="#FFF500"/>
+    <path d="M174.899 97.1398L196.049 118.96C197.809 120.776 197.408 123.76 195.23 125.046C193.909 125.827 192.253 125.762 190.997 124.88L170.387 110.422C162.846 105.131 153.292 103.598 144.474 106.265L129.864 110.683C125.582 111.977 124.97 117.787 128.888 119.946L148.457 130.731C151.409 132.358 152.263 136.207 150.275 138.929C148.954 140.739 146.68 141.586 144.496 141.081L110.523 133.224C95.3408 129.346 81.4885 121.438 70.4298 110.337L46.4595 86.2757C37.6089 77.3914 39.5035 62.5471 50.3018 56.1705C56.9223 52.261 65.236 52.6747 71.4357 57.2221L91.2365 71.7455C99.0407 77.4698 108.114 81.2212 117.682 82.6796L159.1 88.9928C165.115 89.9096 170.664 92.7712 174.899 97.1398Z" fill="#5B57CA"/>
+    <path d="M61.2287 62C61.2287 61.4477 60.781 61 60.2287 61C59.6764 61 59.2287 61.4477 59.2287 62L61.2287 62ZM59.2287 82.4574C59.2287 83.0097 59.6764 83.4574 60.2287 83.4574C60.781 83.4574 61.2287 83.0097 61.2287 82.4574L59.2287 82.4574ZM59.2287 62L59.2287 82.4574L61.2287 82.4574L61.2287 62L59.2287 62Z" fill="#F55C5C"/>
+    <path d="M70.4574 73.2288C71.0097 73.2288 71.4574 72.781 71.4574 72.2288C71.4574 71.6765 71.0097 71.2288 70.4574 71.2288L70.4574 73.2288ZM50 71.2288C49.4477 71.2288 49 71.6765 49 72.2288C49 72.781 49.4477 73.2288 50 73.2288L50 71.2288ZM70.4574 71.2288L50 71.2288L50 73.2288L70.4574 73.2288L70.4574 71.2288Z" fill="#F55C5C"/>
+</g>
+</svg>
diff --git a/_site/assets/github-markdown.css b/_site/assets/github-markdown.css
new file mode 100644
index 00000000..bc9c3901
--- /dev/null
+++ b/_site/assets/github-markdown.css
@@ -0,0 +1,695 @@
+@font-face {
+  font-family: octicons-link;
+  src: url(data:font/woff;charset=utf-8;base64,d09GRgABAAAAAAZwABAAAAAACFQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABEU0lHAAAGaAAAAAgAAAAIAAAAAUdTVUIAAAZcAAAACgAAAAoAAQAAT1MvMgAAAyQAAABJAAAAYFYEU3RjbWFwAAADcAAAAEUAAACAAJThvmN2dCAAAATkAAAABAAAAAQAAAAAZnBnbQAAA7gAAACyAAABCUM+8IhnYXNwAAAGTAAAABAAAAAQABoAI2dseWYAAAFsAAABPAAAAZwcEq9taGVhZAAAAsgAAAA0AAAANgh4a91oaGVhAAADCAAAABoAAAAkCA8DRGhtdHgAAAL8AAAADAAAAAwGAACfbG9jYQAAAsAAAAAIAAAACABiATBtYXhwAAACqAAAABgAAAAgAA8ASm5hbWUAAAToAAABQgAAAlXu73sOcG9zdAAABiwAAAAeAAAAME3QpOBwcmVwAAAEbAAAAHYAAAB/aFGpk3jaTY6xa8JAGMW/O62BDi0tJLYQincXEypYIiGJjSgHniQ6umTsUEyLm5BV6NDBP8Tpts6F0v+k/0an2i+itHDw3v2+9+DBKTzsJNnWJNTgHEy4BgG3EMI9DCEDOGEXzDADU5hBKMIgNPZqoD3SilVaXZCER3/I7AtxEJLtzzuZfI+VVkprxTlXShWKb3TBecG11rwoNlmmn1P2WYcJczl32etSpKnziC7lQyWe1smVPy/Lt7Kc+0vWY/gAgIIEqAN9we0pwKXreiMasxvabDQMM4riO+qxM2ogwDGOZTXxwxDiycQIcoYFBLj5K3EIaSctAq2kTYiw+ymhce7vwM9jSqO8JyVd5RH9gyTt2+J/yUmYlIR0s04n6+7Vm1ozezUeLEaUjhaDSuXHwVRgvLJn1tQ7xiuVv/ocTRF42mNgZGBgYGbwZOBiAAFGJBIMAAizAFoAAABiAGIAznjaY2BkYGAA4in8zwXi+W2+MjCzMIDApSwvXzC97Z4Ig8N/BxYGZgcgl52BCSQKAA3jCV8CAABfAAAAAAQAAEB42mNgZGBg4f3vACQZQABIMjKgAmYAKEgBXgAAeNpjYGY6wTiBgZWBg2kmUxoDA4MPhGZMYzBi1AHygVLYQUCaawqDA4PChxhmh/8ODDEsvAwHgMKMIDnGL0x7gJQCAwMAJd4MFwAAAHjaY2BgYGaA4DAGRgYQkAHyGMF8NgYrIM3JIAGVYYDT+AEjAwuDFpBmA9KMDEwMCh9i/v8H8sH0/4dQc1iAmAkALaUKLgAAAHjaTY9LDsIgEIbtgqHUPpDi3gPoBVyRTmTddOmqTXThEXqrob2gQ1FjwpDvfwCBdmdXC5AVKFu3e5MfNFJ29KTQT48Ob9/lqYwOGZxeUelN2U2R6+cArgtCJpauW7UQBqnFkUsjAY/kOU1cP+DAgvxwn1chZDwUbd6CFimGXwzwF6tPbFIcjEl+vvmM/byA48e6tWrKArm4ZJlCbdsrxksL1AwWn/yBSJKpYbq8AXaaTb8AAHja28jAwOC00ZrBeQNDQOWO//sdBBgYGRiYWYAEELEwMTE4uzo5Zzo5b2BxdnFOcALxNjA6b2ByTswC8jYwg0VlNuoCTWAMqNzMzsoK1rEhNqByEyerg5PMJlYuVueETKcd/89uBpnpvIEVomeHLoMsAAe1Id4AAAAAAAB42oWQT07CQBTGv0JBhagk7HQzKxca2sJCE1hDt4QF+9JOS0nbaaYDCQfwCJ7Au3AHj+LO13FMmm6cl7785vven0kBjHCBhfpYuNa5Ph1c0e2Xu3jEvWG7UdPDLZ4N92nOm+EBXuAbHmIMSRMs+4aUEd4Nd3CHD8NdvOLTsA2GL8M9PODbcL+hD7C1xoaHeLJSEao0FEW14ckxC+TU8TxvsY6X0eLPmRhry2WVioLpkrbp84LLQPGI7c6sOiUzpWIWS5GzlSgUzzLBSikOPFTOXqly7rqx0Z1Q5BAIoZBSFihQYQOOBEdkCOgXTOHA07HAGjGWiIjaPZNW13/+lm6S9FT7rLHFJ6fQbkATOG1j2OFMucKJJsxIVfQORl+9Jyda6Sl1dUYhSCm1dyClfoeDve4qMYdLEbfqHf3O/AdDumsjAAB42mNgYoAAZQYjBmyAGYQZmdhL8zLdDEydARfoAqIAAAABAAMABwAKABMAB///AA8AAQAAAAAAAAAAAAAAAAABAAAAAA==) format('woff');
+}
+
+.markdown-body {
+  -ms-text-size-adjust: 100%;
+  -webkit-text-size-adjust: 100%;
+  line-height: 1.5;
+  color: #24292e;
+  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";
+  font-size: 16px;
+  line-height: 1.5;
+  word-wrap: break-word;
+}
+
+.markdown-body .pl-c {
+  color: #6a737d;
+}
+
+.markdown-body .pl-c1,
+.markdown-body .pl-s .pl-v {
+  color: #005cc5;
+}
+
+.markdown-body .pl-e,
+.markdown-body .pl-en {
+  color: #6f42c1;
+}
+
+.markdown-body .pl-smi,
+.markdown-body .pl-s .pl-s1 {
+  color: #24292e;
+}
+
+.markdown-body .pl-ent {
+  color: #22863a;
+}
+
+.markdown-body .pl-k {
+  color: #d73a49;
+}
+
+.markdown-body .pl-s,
+.markdown-body .pl-pds,
+.markdown-body .pl-s .pl-pse .pl-s1,
+.markdown-body .pl-sr,
+.markdown-body .pl-sr .pl-cce,
+.markdown-body .pl-sr .pl-sre,
+.markdown-body .pl-sr .pl-sra {
+  color: #032f62;
+}
+
+.markdown-body .pl-v,
+.markdown-body .pl-smw {
+  color: #e36209;
+}
+
+.markdown-body .pl-bu {
+  color: #b31d28;
+}
+
+.markdown-body .pl-ii {
+  color: #fafbfc;
+  background-color: #b31d28;
+}
+
+.markdown-body .pl-c2 {
+  color: #fafbfc;
+  background-color: #d73a49;
+}
+
+.markdown-body .pl-c2::before {
+  content: "^M";
+}
+
+.markdown-body .pl-sr .pl-cce {
+  font-weight: bold;
+  color: #22863a;
+}
+
+.markdown-body .pl-ml {
+  color: #735c0f;
+}
+
+.markdown-body .pl-mh,
+.markdown-body .pl-mh .pl-en,
+.markdown-body .pl-ms {
+  font-weight: bold;
+  color: #005cc5;
+}
+
+.markdown-body .pl-mi {
+  font-style: italic;
+  color: #24292e;
+}
+
+.markdown-body .pl-mb {
+  font-weight: bold;
+  color: #24292e;
+}
+
+.markdown-body .pl-md {
+  color: #b31d28;
+  background-color: #ffeef0;
+}
+
+.markdown-body .pl-mi1 {
+  color: #22863a;
+  background-color: #f0fff4;
+}
+
+.markdown-body .pl-mc {
+  color: #e36209;
+  background-color: #ffebda;
+}
+
+.markdown-body .pl-mi2 {
+  color: #f6f8fa;
+  background-color: #005cc5;
+}
+
+.markdown-body .pl-mdr {
+  font-weight: bold;
+  color: #6f42c1;
+}
+
+.markdown-body .pl-ba {
+  color: #586069;
+}
+
+.markdown-body .pl-sg {
+  color: #959da5;
+}
+
+.markdown-body .pl-corl {
+  text-decoration: underline;
+  color: #032f62;
+}
+
+.markdown-body .octicon {
+  display: inline-block;
+  vertical-align: text-top;
+  fill: currentColor;
+}
+
+.markdown-body a {
+  background-color: transparent;
+}
+
+.markdown-body a:active,
+.markdown-body a:hover {
+  outline-width: 0;
+}
+
+.markdown-body strong {
+  font-weight: inherit;
+}
+
+.markdown-body strong {
+  font-weight: bolder;
+}
+
+.markdown-body h1 {
+  font-size: 2em;
+  margin: 0.67em 0;
+}
+
+.markdown-body img {
+  border-style: none;
+}
+
+.markdown-body code,
+.markdown-body kbd,
+.markdown-body pre {
+  font-family: monospace, monospace;
+  font-size: 1em;
+}
+
+.markdown-body hr {
+  box-sizing: content-box;
+  height: 0;
+  overflow: visible;
+}
+
+.markdown-body input {
+  font: inherit;
+  margin: 0;
+}
+
+.markdown-body input {
+  overflow: visible;
+}
+
+.markdown-body [type="checkbox"] {
+  box-sizing: border-box;
+  padding: 0;
+}
+
+.markdown-body * {
+  box-sizing: border-box;
+}
+
+.markdown-body input {
+  font-family: inherit;
+  font-size: inherit;
+  line-height: inherit;
+}
+
+.markdown-body a {
+  color: #0366d6;
+  text-decoration: none;
+}
+
+.markdown-body a:hover {
+  text-decoration: underline;
+}
+
+.markdown-body strong {
+  font-weight: 600;
+}
+
+.markdown-body hr {
+  height: 0;
+  margin: 15px 0;
+  overflow: hidden;
+  background: transparent;
+  border: 0;
+  border-bottom: 1px solid #dfe2e5;
+}
+
+.markdown-body hr::before {
+  display: table;
+  content: "";
+}
+
+.markdown-body hr::after {
+  display: table;
+  clear: both;
+  content: "";
+}
+
+.markdown-body table {
+  border-spacing: 0;
+  border-collapse: collapse;
+}
+
+.markdown-body td,
+.markdown-body th {
+  padding: 0;
+}
+
+.markdown-body h1,
+.markdown-body h2,
+.markdown-body h3,
+.markdown-body h4,
+.markdown-body h5,
+.markdown-body h6 {
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body h1 {
+  font-size: 32px;
+  font-weight: 600;
+}
+
+.markdown-body h2 {
+  font-size: 24px;
+  font-weight: 600;
+}
+
+.markdown-body h3 {
+  font-size: 20px;
+  font-weight: 600;
+}
+
+.markdown-body h4 {
+  font-size: 16px;
+  font-weight: 600;
+}
+
+.markdown-body h5 {
+  font-size: 14px;
+  font-weight: 600;
+}
+
+.markdown-body h6 {
+  font-size: 12px;
+  font-weight: 600;
+}
+
+.markdown-body p {
+  margin-top: 0;
+  margin-bottom: 10px;
+}
+
+.markdown-body blockquote {
+  margin: 0;
+}
+
+.markdown-body ul,
+.markdown-body ol {
+  padding-left: 0;
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body ol ol,
+.markdown-body ul ol {
+  list-style-type: lower-roman;
+}
+
+.markdown-body ul ul ol,
+.markdown-body ul ol ol,
+.markdown-body ol ul ol,
+.markdown-body ol ol ol {
+  list-style-type: lower-alpha;
+}
+
+.markdown-body dd {
+  margin-left: 0;
+}
+
+.markdown-body code {
+  font-family: "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  font-size: 12px;
+}
+
+.markdown-body pre {
+  margin-top: 0;
+  margin-bottom: 0;
+  font-family: "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  font-size: 12px;
+}
+
+.markdown-body .octicon {
+  vertical-align: text-bottom;
+}
+
+.markdown-body .pl-0 {
+  padding-left: 0 !important;
+}
+
+.markdown-body .pl-1 {
+  padding-left: 4px !important;
+}
+
+.markdown-body .pl-2 {
+  padding-left: 8px !important;
+}
+
+.markdown-body .pl-3 {
+  padding-left: 16px !important;
+}
+
+.markdown-body .pl-4 {
+  padding-left: 24px !important;
+}
+
+.markdown-body .pl-5 {
+  padding-left: 32px !important;
+}
+
+.markdown-body .pl-6 {
+  padding-left: 40px !important;
+}
+
+.markdown-body::before {
+  display: table;
+  content: "";
+}
+
+.markdown-body::after {
+  display: table;
+  clear: both;
+  content: "";
+}
+
+.markdown-body>*:first-child {
+  margin-top: 0 !important;
+}
+
+.markdown-body>*:last-child {
+  margin-bottom: 0 !important;
+}
+
+.markdown-body a:not([href]) {
+  color: inherit;
+  text-decoration: none;
+}
+
+.markdown-body .anchor {
+  float: left;
+  padding-right: 4px;
+  margin-left: -20px;
+  line-height: 1;
+}
+
+.markdown-body .anchor:focus {
+  outline: none;
+}
+
+.markdown-body p,
+.markdown-body blockquote,
+.markdown-body ul,
+.markdown-body ol,
+.markdown-body dl,
+.markdown-body table,
+.markdown-body pre {
+  margin-top: 0;
+  margin-bottom: 16px;
+}
+
+.markdown-body hr {
+  height: 0.25em;
+  padding: 0;
+  margin: 24px 0;
+  background-color: #e1e4e8;
+  border: 0;
+}
+
+.markdown-body blockquote {
+  padding: 0 1em;
+  color: #6a737d;
+  border-left: 0.25em solid #dfe2e5;
+}
+
+.markdown-body blockquote>:first-child {
+  margin-top: 0;
+}
+
+.markdown-body blockquote>:last-child {
+  margin-bottom: 0;
+}
+
+.markdown-body kbd {
+  display: inline-block;
+  padding: 3px 5px;
+  font-size: 11px;
+  line-height: 10px;
+  color: #444d56;
+  vertical-align: middle;
+  background-color: #fafbfc;
+  border: solid 1px #c6cbd1;
+  border-bottom-color: #959da5;
+  border-radius: 3px;
+  box-shadow: inset 0 -1px 0 #959da5;
+}
+
+.markdown-body h1,
+.markdown-body h2,
+.markdown-body h3,
+.markdown-body h4,
+.markdown-body h5,
+.markdown-body h6 {
+  margin-top: 24px;
+  margin-bottom: 16px;
+  font-weight: 600;
+  line-height: 1.25;
+}
+
+.markdown-body h1 .octicon-link,
+.markdown-body h2 .octicon-link,
+.markdown-body h3 .octicon-link,
+.markdown-body h4 .octicon-link,
+.markdown-body h5 .octicon-link,
+.markdown-body h6 .octicon-link {
+  color: #1b1f23;
+  vertical-align: middle;
+  visibility: hidden;
+}
+
+.markdown-body h1:hover .anchor,
+.markdown-body h2:hover .anchor,
+.markdown-body h3:hover .anchor,
+.markdown-body h4:hover .anchor,
+.markdown-body h5:hover .anchor,
+.markdown-body h6:hover .anchor {
+  text-decoration: none;
+}
+
+.markdown-body h1:hover .anchor .octicon-link,
+.markdown-body h2:hover .anchor .octicon-link,
+.markdown-body h3:hover .anchor .octicon-link,
+.markdown-body h4:hover .anchor .octicon-link,
+.markdown-body h5:hover .anchor .octicon-link,
+.markdown-body h6:hover .anchor .octicon-link {
+  visibility: visible;
+}
+
+.markdown-body h1 {
+  padding-bottom: 0.3em;
+  font-size: 2em;
+  border-bottom: 1px solid #eaecef;
+}
+
+.markdown-body h2 {
+  padding-bottom: 0.3em;
+  font-size: 1.5em;
+  border-bottom: 1px solid #eaecef;
+}
+
+.markdown-body h3 {
+  font-size: 1.25em;
+}
+
+.markdown-body h4 {
+  font-size: 1em;
+}
+
+.markdown-body h5 {
+  font-size: 0.875em;
+}
+
+.markdown-body h6 {
+  font-size: 0.85em;
+  color: #6a737d;
+}
+
+.markdown-body ul,
+.markdown-body ol {
+  padding-left: 2em;
+}
+
+.markdown-body ul ul,
+.markdown-body ul ol,
+.markdown-body ol ol,
+.markdown-body ol ul {
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+.markdown-body li {
+  word-wrap: break-all;
+}
+
+.markdown-body li>p {
+  margin-top: 16px;
+}
+
+.markdown-body li+li {
+  margin-top: 0.25em;
+}
+
+.markdown-body dl {
+  padding: 0;
+}
+
+.markdown-body dl dt {
+  padding: 0;
+  margin-top: 16px;
+  font-size: 1em;
+  font-style: italic;
+  font-weight: 600;
+}
+
+.markdown-body dl dd {
+  padding: 0 16px;
+  margin-bottom: 16px;
+}
+
+.markdown-body table {
+  display: block;
+  width: 100%;
+  overflow: auto;
+}
+
+.markdown-body table th {
+  font-weight: 600;
+}
+
+.markdown-body table th,
+.markdown-body table td {
+  padding: 6px 13px;
+  border: 1px solid #dfe2e5;
+}
+
+.markdown-body table tr {
+  background-color: #fff;
+  border-top: 1px solid #c6cbd1;
+}
+
+.markdown-body table tr:nth-child(2n) {
+  background-color: #f6f8fa;
+}
+
+.markdown-body img {
+  max-width: 100%;
+  box-sizing: content-box;
+  /* background-color: #fff; */
+}
+
+.markdown-body img[align=right] {
+  padding-left: 20px;
+}
+
+.markdown-body img[align=left] {
+  padding-right: 20px;
+}
+
+.markdown-body code {
+  padding: 0.2em 0.4em;
+  margin: 0;
+  font-size: 85%;
+  background-color: rgba(27,31,35,0.05);
+  border-radius: 3px;
+}
+
+.markdown-body pre {
+  word-wrap: normal;
+}
+
+.markdown-body pre>code {
+  padding: 0;
+  margin: 0;
+  font-size: 100%;
+  word-break: normal;
+  white-space: pre;
+  background: transparent;
+  border: 0;
+}
+
+.markdown-body .highlight {
+  margin-bottom: 16px;
+}
+
+.markdown-body .highlight pre {
+  margin-bottom: 0;
+  word-break: normal;
+}
+
+.markdown-body .highlight pre,
+.markdown-body pre {
+  padding: 16px;
+  overflow: auto;
+  font-size: 85%;
+  line-height: 1.45;
+  background-color: #f6f8fa;
+  border-radius: 3px;
+}
+
+.markdown-body pre code {
+  display: inline;
+  max-width: auto;
+  padding: 0;
+  margin: 0;
+  overflow: visible;
+  line-height: inherit;
+  word-wrap: normal;
+  background-color: transparent;
+  border: 0;
+}
+
+.markdown-body .full-commit .btn-outline:not(:disabled):hover {
+  color: #005cc5;
+  border-color: #005cc5;
+}
+
+.markdown-body kbd {
+  display: inline-block;
+  padding: 3px 5px;
+  font: 11px "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace;
+  line-height: 10px;
+  color: #444d56;
+  vertical-align: middle;
+  background-color: #fafbfc;
+  border: solid 1px #d1d5da;
+  border-bottom-color: #c6cbd1;
+  border-radius: 3px;
+  box-shadow: inset 0 -1px 0 #c6cbd1;
+}
+
+.markdown-body :checked+.radio-label {
+  position: relative;
+  z-index: 1;
+  border-color: #0366d6;
+}
+
+.markdown-body .task-list-item {
+  list-style-type: none;
+}
+
+.markdown-body .task-list-item+.task-list-item {
+  margin-top: 3px;
+}
+
+.markdown-body .task-list-item input {
+  margin: 0 0.2em 0.25em -1.6em;
+  vertical-align: middle;
+}
+
+.markdown-body hr {
+  border-bottom-color: #eee;
+}
diff --git a/_site/assets/hand-point.svg b/_site/assets/hand-point.svg
new file mode 100644
index 00000000..beaa6645
--- /dev/null
+++ b/_site/assets/hand-point.svg
@@ -0,0 +1,6 @@
+<svg width="506" height="182" viewBox="0 0 506 182" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M130.914 32.0168L168.738 140.874C171.006 147.4 177.438 151.533 184.316 150.884L240.857 145.549L240.857 87.8457C240.857 81.303 235.553 75.999 229.01 75.999C221.486 75.999 215.868 82.9216 217.417 90.2844L221.022 107.42C221.708 110.683 219.218 113.75 215.884 113.75C213.398 113.75 211.253 112.006 210.745 109.573L204.97 81.8926C203.525 74.9685 209.529 68.7741 216.495 70.0019L250.519 75.999L292.941 10.7653L146.027 10.7653C135.021 10.7653 127.301 21.6203 130.914 32.0168Z" fill="#FF7F80"/>
+<path d="M223.392 69.9115C223.731 67.0178 220.962 64.7437 218.19 65.6393L211.779 67.7102C211.189 67.9007 210.563 67.9515 209.951 67.8588L193.515 65.3701C189.822 64.8109 187.446 69.1684 189.915 71.97L198.888 82.1492C202.841 86.634 204.31 92.7889 202.807 98.5754L199.437 111.555C198.69 114.434 201.515 116.95 204.288 115.875V115.875C208.53 114.23 213.234 114.23 217.477 115.875L217.983 116.071C220.756 117.146 223.671 114.871 223.303 111.921L220.869 92.4222C220.829 92.1031 220.828 91.7803 220.865 91.4609L223.392 69.9115Z" fill="#FF6666"/>
+<path d="M188.255 9.00011L16.4893 9.00001C7.54843 9 0.456482 16.5346 0.997192 25.4591C1.44373 32.8295 7.02103 38.8649 14.3333 39.8905L216.269 68.2159C228.915 69.9897 236.682 82.9993 232.244 94.9731L215.638 139.776C213.167 146.442 213.568 153.833 216.747 160.192C222.487 171.677 235.825 177.161 247.983 173.035L356.527 136.207C370.397 131.501 385.206 130.251 399.669 132.566L510 150.224V9.00011L414.161 9L188.255 9.00011Z" fill="#FF9999"/>
+<path d="M505.802 5.61211C505.802 2.85069 503.564 0.612122 500.802 0.612122H419.506C416.745 0.612122 414.506 2.8507 414.506 5.61212V145.853C414.506 148.024 415.908 149.948 417.975 150.613L499.272 176.755C502.499 177.792 505.802 175.385 505.802 171.995V5.61211Z" fill="#0000FF"/>
+</svg>
diff --git a/_site/assets/hands-shake.svg b/_site/assets/hands-shake.svg
new file mode 100644
index 00000000..b855bb40
--- /dev/null
+++ b/_site/assets/hands-shake.svg
@@ -0,0 +1,15 @@
+<svg width="614" height="200" viewBox="0 0 614 200" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0)">
+<path d="M352.33 50.0618C345.872 47.4623 342.742 40.1193 345.339 33.6607V33.6607C347.936 27.2021 355.276 24.0736 361.733 26.6731L365.027 27.9991C372.864 31.1539 375.443 40.9751 370.166 47.5713V47.5713C366.692 51.9139 360.783 53.4648 355.624 51.3878L352.33 50.0618Z" fill="#FF6666"/>
+<path d="M380.89 21.3972C389.463 21.3972 396.414 28.3475 396.414 36.9212L396.414 79.6875C396.414 89.6091 388.371 97.6522 378.449 97.6522V97.6522C367.718 97.6522 359.38 88.3053 360.601 77.6437L365.466 35.155C366.364 27.3159 372.999 21.3972 380.89 21.3972V21.3972Z" fill="#FF7F80"/>
+<path d="M279.17 186.353L299.773 196.535C306.307 199.764 314.08 199.183 320.062 195.019L409.334 132.868C414.766 129.087 418.154 123.015 418.521 116.407L421.998 53.7794C422.45 45.6246 416.695 38.435 408.639 37.0912C400.246 35.6913 392.224 41.0973 390.37 49.4017L376.69 110.687L320.556 140.832C314.251 144.218 306.618 143.977 300.54 140.201L286.909 131.734L279.17 186.353Z" fill="#FF9999"/>
+<path d="M257.369 3.54956L202.356 31.0729C194.07 35.2185 192.537 46.3952 199.401 52.6171C202.725 55.6301 207.354 56.7442 211.685 55.5737L252.327 44.5905C263.423 41.5918 275.257 45.1966 282.795 53.8721L308.541 83.4994C314.681 90.5654 308.614 101.441 299.375 99.9281L219.125 86.7861C210.896 85.4384 202.945 90.4106 200.553 98.4001C198.106 106.573 202.258 115.268 210.151 118.503L375.56 186.298C399.691 196.188 425.684 200.716 451.739 199.568L614.778 192.385L614.778 48.5263L474.211 79.919C461.125 82.8415 447.437 81.2964 435.332 75.5302L283.693 3.29448C275.348 -0.680748 265.636 -0.586645 257.369 3.54956Z" fill="#683838"/>
+<path d="M169.603 130.572L279.523 186.065L313.136 174.209L264.509 123.189C258.74 117.136 262.508 107.094 270.835 106.329L371.87 97.045C379.95 96.3026 386.434 90.0536 387.476 82.0061C388.622 73.1547 382.86 64.8819 374.162 62.89L174.826 17.2398C165.283 15.0542 155.576 13.6511 145.804 13.0446L-2.40968 3.84655L-2.4097 162.306L126.446 126.345C140.857 122.323 156.249 123.83 169.603 130.572Z" fill="#FF9999"/>
+<path d="M219.135 86.8177L337.414 106.433C337.85 106.506 338.242 106.738 338.514 107.086C358.547 132.707 331.609 168.284 301.515 155.95L209.749 118.339C202.084 115.197 198.052 106.753 200.428 98.8164L200.548 98.4145C202.941 90.4209 210.904 85.4527 219.135 86.8177Z" fill="#683838"/>
+</g>
+<defs>
+<clipPath id="clip0">
+<rect width="614" height="200" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/_site/assets/print.css b/_site/assets/print.css
new file mode 100644
index 00000000..7d0eead1
--- /dev/null
+++ b/_site/assets/print.css
@@ -0,0 +1,274 @@
+/* SPDX-License-Identifier: CC0-1.0 */
+/* SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS */
+html, .markdown-body {
+  font-family: Mulish;
+  font-size: 11pt;
+}
+
+.markdown-body h1, .markdown-body h2, .markdown-body h3 {
+  font-weight: normal;
+  position: relative;
+}
+.markdown-body h1 {
+  margin-top: 0;
+  font-size: 1.5cm;
+  border-bottom: none;
+}
+.markdown-body h2 {
+  font-size: 1.5em;
+}
+.markdown-body h3 {
+  font-size: 1em;
+  font-weight: bold;
+}
+.markdown-body h4 {
+  font-size: 1em;
+  font-style: italic;
+}
+.markdown-body h4 {
+  font-weight: bold;
+  font-weight: normal;
+}
+
+article>p, article>ul, article>ol {
+  position: relative;
+  max-width: 27rem;
+}
+
+article {
+  clear: both;
+}
+
+a:link {
+  color: inherit;
+  text-decoration: none;
+}
+
+a:link:before {
+  color: grey;
+  page-break-inside: avoid;
+  margin-left: .25em;
+  break-inside: avoid;
+  display: block;
+  right: 0;
+  width: 6cm;
+  margin-right: -7cm;
+  padding: 0.25rem;
+  line-height: 1.25;
+  text-align: left;
+  float: right;
+  clear: both;
+  word-break: normal;
+  text-decoration: none;
+}
+a[href^="http"]:link {
+  color: black;
+  text-decoration: none;
+  word-wrap: normal;
+}
+a[href^="http"]:before {
+  content: "" attr(href) "";
+  font-size: .75em;
+}
+a[href^="#"] {
+  color: black;
+  text-decoration: none;
+}
+a[href^="#"]:after {
+  content: "" target-counter(attr(href), page);
+  color: black;
+  background-color: whitesmoke;
+  display: inline;
+  width: 0.8cm;
+  padding: 0.2cm;
+  text-align: right;
+}
+
+img {
+  max-width: 155% !important;
+}
+
+ol, ul {
+  margin-bottom: 2em;
+}
+
+li, p {
+  clear: both;
+}
+
+/* Headings */
+
+.markdown-body [id$="public-policy-makers-what-you-need-to-do"]:before,
+.markdown-body [id$="managers-what-you-need-to-do"]:before,
+.markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+  display: block;
+  position: absolute;
+  content: 'A';
+  text-align: center;
+  width: 1cm;
+  height: 1cm;
+  background-color: black;
+  border: 1px solid black;
+  color: white;
+  display: inline-block;
+  margin-left: -1.2cm;
+  box-sizing: border-box;
+  padding: 0.12cm;
+  font-size: 0.5cm;
+  font-weight: 900;
+}
+.markdown-body [id$="public-policy-makers-what-you-need-to-do"]:before {
+  background-color: #00EFB5;
+  border-color: #00EFB5;
+  content: 'P';
+}
+.markdown-body [id$="managers-what-you-need-to-do"]:before {
+  background-color: #FF6D1C;
+  border-color: #FF6D1C;
+  content: 'M';
+}
+.markdown-body [id$="developers-and-designers-what-you-need-to-do"]:before {
+  background-color: #8626FF;
+  border-color: #8626FF;
+  content: 'D';
+}
+
+/* First page */
+
+h1.title {
+  font-size: 5em;
+  font-weight: 700;
+  margin-bottom: 1cm;
+}
+
+ul.first-page-audiences {
+  max-width: none;
+  list-style: none;
+  font-size: 1.25em;
+  padding-left: 0;
+}
+.first-page-audiences li, .first-page-audiences lh {
+  display: block;
+  margin-bottom: .5cm;
+}
+.first-page-audiences lh {
+  margin-bottom: 1cm;
+}
+.first-page-audiences li {
+  padding-left: 1.2cm;
+}
+.first-page-audiences li::before {
+  margin-top: -.15cm;
+}
+#section-first-page>img {
+  width: 100%;
+}
+
+/* Print specific */
+
+@media print {
+  /* html { page-break-before: left } */
+  @page {
+    /* A4 with a 3mm bleed on every side */
+    size: 21.6cm 30.3cm;
+    margin: 2cm 0;
+    orphans:4;
+    widows:4;
+  }
+  @page :left {
+    margin-right: 1cm;
+    @top-left {
+      background: whitesmoke;
+      font-size: 75%;
+      height: 1cm;
+      width: 1.23cm;
+      text-align: center;
+      padding-left: 0.5cm;
+    }
+  }
+  @page :right {
+    margin-left: 1cm;
+    @top-right {
+      background: whitesmoke;
+      font-size: 75%;
+      height: 1cm;
+      width: 1.23cm;
+      text-align: center;
+      padding-right: 0.5cm;
+    }
+  }
+  figure {
+    page: image;
+  }
+  figure>img {
+    width: 100%;
+    height: 100%;
+  }
+  @page image {
+    margin-top: 0 !important;
+    margin-left: -1.5cm !important;
+    margin-right: -1.5cm !important;
+    margin-bottom: 0 !important;
+    padding: 0 0 0 0 !important;
+  }
+
+  article {
+    margin: 0 2cm;
+    break-before: left;
+  }
+  article:first-of-type {
+    break-before: avoid;
+  }
+  h1, h2, h3, h4 {
+    page-break-after: avoid;
+  }
+  img {
+    page-break-inside: avoid;
+  }
+  #table-of-contents {
+    line-height: 0.9;
+  }
+  a.table-of-contents[href^="http"]:after {
+  content: "" attr(href) "";
+  font-size: .75em;
+}
+  a.table-of-contents:link:after {
+  color: grey;
+  page-break-inside: avoid;
+  margin-left: .25em;
+  break-inside: avoid;
+  display: block;
+  right: 0;
+  width: 0.8cm;
+  margin-right: -7cm;
+  padding: 0.25rem;
+  line-height: 1.25;
+  text-align: right;
+  float: right;
+  clear: both;
+  word-break: normal;
+  text-decoration: none;
+}
+
+  #section-first-page>img {
+    width: 21.6cm;
+    margin: 1cm 0 1cm -3.21cm; /* This value for the left margin was done by eye */
+  }
+}
+
+@media screen {
+  body {
+    background-color: whitesmoke;
+    margin: 0; padding: 0;
+  }
+  article {
+    display: block;
+    background-color: white;
+    padding: 1cm;
+    min-height: 29.7cm;
+    max-width: 50em;
+    max-width: 21cm;
+    box-sizing: border-box;
+    margin: 2cm 0;
+  }
+}
diff --git a/_site/assets/rouge-highlight.css b/_site/assets/rouge-highlight.css
new file mode 100644
index 00000000..f1877f20
--- /dev/null
+++ b/_site/assets/rouge-highlight.css
@@ -0,0 +1,210 @@
+
+.highlight table td { padding: 5px; }
+.highlight table pre { margin: 0; }
+.highlight .cm {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .cp {
+  color: #797676;
+  font-weight: bold;
+}
+.highlight .c1 {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .cs {
+  color: #797676;
+  font-weight: bold;
+  font-style: italic;
+}
+.highlight .c, .highlight .cd {
+  color: #777772;
+  font-style: italic;
+}
+.highlight .err {
+  color: #a61717;
+  background-color: #e3d2d2;
+}
+.highlight .gd {
+  color: #000000;
+  background-color: #ffdddd;
+}
+.highlight .ge {
+  color: #000000;
+  font-style: italic;
+}
+.highlight .gr {
+  color: #aa0000;
+}
+.highlight .gh {
+  color: #797676;
+}
+.highlight .gi {
+  color: #000000;
+  background-color: #ddffdd;
+}
+.highlight .go {
+  color: #888888;
+}
+.highlight .gp {
+  color: #555555;
+}
+.highlight .gs {
+  font-weight: bold;
+}
+.highlight .gu {
+  color: #aaaaaa;
+}
+.highlight .gt {
+  color: #aa0000;
+}
+.highlight .kc {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kd {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kn {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kp {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kr {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .kt {
+  color: #445588;
+  font-weight: bold;
+}
+.highlight .k, .highlight .kv {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .mf {
+  color: #009999;
+}
+.highlight .mh {
+  color: #009999;
+}
+.highlight .il {
+  color: #009999;
+}
+.highlight .mi {
+  color: #009999;
+}
+.highlight .mo {
+  color: #009999;
+}
+.highlight .m, .highlight .mb, .highlight .mx {
+  color: #009999;
+}
+.highlight .sb {
+  color: #d14;
+}
+.highlight .sc {
+  color: #d14;
+}
+.highlight .sd {
+  color: #d14;
+}
+.highlight .s2 {
+  color: #d14;
+}
+.highlight .se {
+  color: #d14;
+}
+.highlight .sh {
+  color: #d14;
+}
+.highlight .si {
+  color: #d14;
+}
+.highlight .sx {
+  color: #d14;
+}
+.highlight .sr {
+  color: #009926;
+}
+.highlight .s1 {
+  color: #d14;
+}
+.highlight .ss {
+  color: #990073;
+}
+.highlight .s {
+  color: #d14;
+}
+.highlight .na {
+  color: #008080;
+}
+.highlight .bp {
+  color: #797676;
+}
+.highlight .nb {
+  color: #0086B3;
+}
+.highlight .nc {
+  color: #445588;
+  font-weight: bold;
+}
+.highlight .no {
+  color: #008080;
+}
+.highlight .nd {
+  color: #3c5d5d;
+  font-weight: bold;
+}
+.highlight .ni {
+  color: #800080;
+}
+.highlight .ne {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nf {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nl {
+  color: #990000;
+  font-weight: bold;
+}
+.highlight .nn {
+  color: #555555;
+}
+.highlight .nt {
+  color: #000080;
+}
+.highlight .vc {
+  color: #008080;
+}
+.highlight .vg {
+  color: #008080;
+}
+.highlight .vi {
+  color: #008080;
+}
+.highlight .nv {
+  color: #008080;
+}
+.highlight .ow {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .o {
+  color: #000000;
+  font-weight: bold;
+}
+.highlight .w {
+  color: #bbbbbb;
+}
+.highlight {
+  background-color: #f8f8f8;
+}
diff --git a/_site/assets/standard-for-public-code-commitment.svg b/_site/assets/standard-for-public-code-commitment.svg
new file mode 100644
index 00000000..34b1faa2
--- /dev/null
+++ b/_site/assets/standard-for-public-code-commitment.svg
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net> -->
+<!-- standard-for-public-code-commitment.svg -->
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="226" height="20" role="img" aria-label="Standard for Public Code: commitment">
+  <title>Standard for Public Code: commitment</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="226" height="20" rx="3" fill="#fff"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="147" height="20" fill="#555"/>
+    <rect x="147" width="79" height="20" fill="#97ca00"/>
+    <rect width="226" height="20" fill="url(#s)"/>
+  </g>
+  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+    <text aria-hidden="true" x="745" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="1370">Standard for Public Code</text>
+    <text x="745" y="140" transform="scale(.1)" fill="#fff" textLength="1370">Standard for Public Code</text>
+    <text aria-hidden="true" x="1855" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="690">commitment</text>
+    <text x="1855" y="140" transform="scale(.1)" fill="#fff" textLength="690">commitment</text>
+  </g>
+</svg>
diff --git a/_site/assets/style.css b/_site/assets/style.css
new file mode 100644
index 00000000..9470766b
--- /dev/null
+++ b/_site/assets/style.css
@@ -0,0 +1,873 @@
+@import url("github-markdown.css");
+@import url("rouge-highlight.css");
+@import url('https://fonts.googleapis.com/css?family=Muli:400,400i,700');
+
+
+/*
+ * HTML and Body elements
+*/
+
+body, html {
+  font-family: 'Muli', sans-serif;
+  margin: 0;
+}
+
+@media screen {
+  body {
+    background: whitesmoke;
+  }
+}
+
+@media print {
+  html {
+    font-size: 12pt;
+  }
+
+  @page {
+    /* A4 with, for printing presses add a (3mm to each side) bleed here */
+    size: 21cm 29.7cm;
+    margin: 2cm 1cm;
+    orphans:4;
+    widows:4;
+    @bottom-center {
+      background: whitesmoke;
+      font-size: 75%;
+      content: counter(page);
+      margin-top: 0.25cm;
+      height: 1cm;
+      width: 1cm;
+      text-align: center;
+    }
+  }
+}
+
+/*
+ * General elements and ground rules
+*/
+
+hr {
+  border: none;
+  border-bottom: 1px solid lightgrey;
+}
+
+@media screen {
+  p, h1, h2, h3, h4, h5, ul, pre, blockquote, .highlight {
+    max-width: 35em;
+    max-width: calc(30rem + 5em);
+  }
+}
+@media print {
+  p, ul {
+    max-width: 12cm;
+    max-width: 60vw;
+    box-sizing: border-box;
+  }
+}
+
+h1, h2, h3, h4, h5 {
+  page-break-after: avoid;
+}
+img, code {
+  break-inside: avoid;
+  page-break-inside: avoid;
+  overflow: wrap;
+}
+
+@media print {
+  ul, ol {
+    page-break-inside: avoid;
+  }
+  ul li, ol li {
+    margin: .5em 0;
+  }
+}
+
+/*
+ * Links
+*/
+
+a:link, a:visited {
+  text-decoration: underline;
+  color: black;
+}
+a:link {
+  text-decoration-color: blue;
+}
+a:visited {
+  text-decoration-color: purple;
+}
+a:link[href^='#'], a:visited[href^='#'] {
+  text-decoration-color: darkgrey;
+}
+a:hover {
+  background: whitesmoke;
+}
+
+@media print {
+  a:link, a:visited {
+    text-decoration: none !important;
+  }
+  a:link:after, a:visited:after {
+    color: grey;
+    border-left: 2px solid whitesmoke;
+    page-break-inside: avoid;
+    break-inside: avoid;
+    display: block;
+    right: 0;
+    width: 6cm;
+    width: 30vw;
+    margin-right: -7cm;
+    margin-right: -30vw;
+    padding: 0 0 0.25em .25em;
+    margin-bottom: .25em;
+    line-height: 1.25;
+    text-align: left;
+    float: right;
+    clear: both;
+    text-decoration: none;
+    font-weight: normal;
+  }
+  /* Add `[href^="http"]` for limiting to external sites */
+  a[href^="http"]:link {
+    color: black;
+    text-decoration: underline;
+  }
+  a[href^="http"]:after {
+    content: "" attr(href) "";
+    font-size: .75rem;
+  }
+  a[href^="/"]:after {
+    /* content: "" attr(href) "";
+    font-size: .75rem; */
+    display: none;
+  }
+  a[href^="#"]:after {
+    content: "" target-counter(attr(href), page);
+    color: black;
+    background-color: whitesmoke;
+    width: 1cm;
+    padding: 0.2cm;
+    text-align: right;
+  }
+}
+
+/*
+Buttons
+*/
+
+button, input {
+  font-family: inherit;
+  font-size: inherit;
+  margin-bottom: 0.5em;
+  padding: 0.5em;
+  display: inline-block;
+  background: none;
+  border: 1px solid lightgrey;
+  border-radius: 2px;
+  white-space: nowrap;
+}
+input:focus, button:focus {
+  border: 1px solid black;
+  background: whitesmoke;
+}
+button:hover {
+  background: whitesmoke;
+}
+button svg {
+  vertical-align: -2px;
+}
+
+/*
+ * general layout
+*/
+
+body>hr {
+  margin: 0;
+}
+
+@media screen {
+  body>nav.theme-nav, body>header, body>footer {
+    padding: 1em;
+  }
+  body>header, body>footer#site-footer {
+    background-color: white;
+  }
+  body>*:not(hr) {
+    box-sizing: border-box;
+    max-width: 80em;
+    margin: auto;
+  }
+  body.with-site-nav>*:not(hr) {
+    max-width: 100em;
+  }
+}
+
+@media screen and (min-width:68em) {
+  body>nav.theme-nav, body>header, body>footer {
+    padding: 2em 4em;
+  }
+}
+
+/*
+ * Foundation Navigation
+*/
+
+@media screen {
+  nav.theme-nav {
+    display: flex;
+    flex-direction: row;
+    align-items: center;
+    flex-wrap: wrap;
+    padding-bottom: 1rem;
+    background: none;
+  }
+}
+@media screen and (min-width:400px) {
+  nav.theme-nav {
+    padding: 1rem;
+  }
+}
+@media screen and (min-width:64em) {
+  nav.theme-nav {
+    padding: 1rem 4em;
+  }
+}
+@media print {
+  nav.theme-nav {
+    display: block;
+  }
+  nav.theme-nav ul {
+    display: none;
+  }
+}
+
+nav.theme-nav ul {
+  list-style: none;
+  margin: 0 0 12px;
+  padding-inline-start: 0px;
+  max-width: none;
+}
+nav.theme-nav ul li {
+  padding: 5px 0;
+  display: inline-block;
+}
+
+nav.theme-nav a:link, header a:visited {
+  font-weight: normal;
+  border-bottom: none;
+}
+@media screen {
+  nav.theme-nav a:link, header a:visited {
+    padding: 1rem;
+  }
+}
+@media print {
+  nav.theme-nav a:link:after, header a:visited:after {
+    display: none;
+  }
+}
+
+nav.theme-nav a.logo-mark {
+  display: flex;
+  flex-direction: row;
+  align-items: center;
+  flex: 1;
+  text-decoration: none;
+  margin-right: 40px;
+}
+
+@media screen and (max-width:640px) {
+  nav.theme-nav {
+    align-items: flex-start;
+  }
+  nav.theme-nav a.logo-mark {
+    margin-right: 0px;
+  }
+  nav.theme-nav ul  {
+    margin: 16px 15px 16px 0;
+  }
+  nav.theme-nav ul li  {
+    display:block;
+  }
+}
+
+@media screen and (min-width:520px) {
+  nav.theme-nav a.logo-mark {
+    font-size: 2em;
+  }
+}
+@media screen and (min-width:400px) and (max-width:520px) {
+  nav.theme-nav a.logo-mark {
+    font-size: 1.5em;
+  }
+}
+
+@media screen and (max-width:440px) {
+  nav.theme-nav {
+    flex-direction: column;
+  }
+  nav.theme-nav {
+    align-items: flex-start;
+  }
+}
+
+
+nav.theme-nav a.logo-mark>img {
+  height: 2em;
+  margin-right: 0.5em;
+}
+nav.theme-nav a.logo-mark>p {
+  font-weight: bold;
+  margin: 0;
+}
+
+@media print {
+  nav.theme-nav+hr {
+    display: none;
+  }
+  nav.theme-nav a.logo-mark {
+    font-size: 1.5em;
+  }
+  nav.theme-nav a.logo-mark>img {
+    margin-right: 0.9rem;
+  }
+}
+
+/*
+ * Site header
+*/
+
+@media screen {
+  header .site-title {
+    padding: 1em 1rem;
+    font-size: 1.5em;
+  }
+}
+@media screen and (min-width:400px) {
+  header .site-title {
+    font-size: 2em;
+    padding: 1.5em 2rem;
+  }
+}
+@media screen and (min-width:700px) {
+  header .site-title.home {
+    font-size: 4em;
+  }
+}
+
+header .site-title a {
+  text-decoration: none;
+}
+header .site-title a:hover {
+  text-decoration: underline;
+}
+
+@media print {
+  header .site-title a:after {
+    display: none;
+  }
+  header .site-title {
+    font-size: 1.5em;
+    margin-left: 3.5rem;
+  }
+  header+hr {
+    margin: 2em 0;
+  }
+}
+
+/*
+ * Site navigation
+*/
+
+input#show-site-nav {
+  display: none;
+}
+input#show-site-nav ~ label:before {
+  content: 'Open '
+}
+input#show-site-nav:checked ~ label:before {
+  content: 'Close '
+}
+
+nav#site-nav {
+  padding: 1rem;
+}
+nav#site-nav>ul {
+  display: none;
+}
+label[for=show-site-nav] {
+  display: block;
+}
+nav#site-nav a.active {
+  font-weight: bold;
+}
+
+input#show-site-nav ~ label {
+  margin: 1em;
+  padding: 1rem;
+  text-decoration: none;
+  border: 1px solid grey;
+  border-radius: 2px;
+  display: block;
+}
+input#show-site-nav ~ label:hover, input#show-site-nav:checked ~ label {
+  background: lightgrey;
+}
+input#show-site-nav:checked ~ ul {
+  display: block;
+}
+
+@media print {
+  nav#site-nav, input#show-site-nav {
+    display: none !important;
+    /* Hide navigation from all print */
+  }
+}
+
+/*
+ * Main content
+*/
+
+@media screen {
+  main {
+    display: flex;
+    flex-direction: row;
+    flex-wrap: wrap;
+    background: white;
+  }
+  main>* {
+    padding: 2rem;
+    box-sizing: border-box;
+    max-width: 100%;
+    order: 2;
+  }
+  main>*>* {
+    max-width: 100%;
+  }
+  main #theme-breadcrumbs {
+    flex-basis: 100%;
+    order: 0;
+  }
+  main .theme-prev-next {
+    flex-basis: 100%;
+    order: 0;
+  }
+  main .theme-prev-next-prev {
+    float:left;
+    margin-right: 5px;
+  }
+  main .theme-prev-next-next {
+    float:right;
+    margin-left: 5px;
+  }
+  main>h1 {
+    flex-basis: 100%;
+    margin: 0;
+    order: 1;
+  }
+  main .content {
+    flex: 2 2 60%;
+  }
+  main .page-information {
+    flex: 1 1 33%;
+    order: 3;
+  }
+}
+
+@media screen and (min-width:68em) {
+  main {
+    padding: 4em;
+  }
+  main>h1 {
+    font-size: 3em;
+    margin-bottom: .25em;
+  }
+}
+
+@media print {
+  main {
+    display: block !important;
+    page-break-after: always;
+  }
+  main+hr {
+    display: none;
+  }
+  main>h1 {
+    padding: 1em 3.5rem;
+    font-size: 3em;
+  }
+  main .page-information {
+    page-break-after: always;
+  }
+}
+
+/*
+ * Content
+ */
+
+#bpmn-canvas {
+  height: 50vh;
+  border: 1px solid lightgrey;
+  border-radius: 2px;
+  max-width: 50em;
+  max-height: 50vw;
+  margin-bottom: 1em;
+  page-break-inside: avoid;
+}
+#bpmn-canvas .bjs-powered-by {
+  display: none;
+}
+
+main .content>article>:first-child:not(h1):not(h2):not(ol):not(ul) {
+  font-size: 1.15em;
+}
+
+/*
+ * Markdown content
+ */
+
+@media print {
+  .markdown-body {
+    font-family: "Muli"
+  }
+
+  .markdown-body h1, .markdown-body h2, .markdown-body h3 {
+    font-weight: normal;
+    position: relative;
+  }
+  .markdown-body h1 {
+    font-size: 1.5cm;
+    border-bottom: none;
+  }
+  .markdown-body h2 {
+    font-size: 1.5em;
+  }
+  .markdown-body h3 {
+    font-size: 1em;
+    font-weight: bold;
+  }
+  .markdown-body h4 {
+    font-size: 1em;
+    font-weight: normal;
+  }
+  .markdown-body h4 {
+    font-weight: bold;
+  }
+}
+
+/*
+ * Page information section
+ */
+
+ @media screen {
+  main section.page-information {
+    flex: 1 2 300px;
+    box-sizing: border-box;
+    display: flex;
+    flex-direction: column;
+  }
+}
+
+/*
+ * Table of contents
+*/
+
+/*
+ * Navigation lists
+*/
+
+@media screen {
+  nav#site-nav>ul:before {
+    color: lightgrey;
+    text-align: center;
+    font-size: 1em;
+    line-height: 2;
+    display: block;
+    border-bottom: 1px solid;
+  }
+  ol.table-of-contents, nav#site-nav>ul {
+    list-style: none;
+    flex: 1 1 auto;
+    overflow: hidden;
+    margin: 0 0;
+    padding: 0;
+    box-sizing: border-box;
+  }
+
+  ol.table-of-contents li, nav#site-nav>ul li {
+    margin: .5em 0;
+  }
+  ol.table-of-contents>li, nav#site-nav>ul>li {
+    font-size: 1.15rem;
+    padding-bottom: 0.5em;
+  }
+  ol.table-of-contents>li ol, nav#site-nav>ul>li ul {
+    padding-left: 1em;
+    list-style: none;
+  }
+  ol.table-of-contents>li>ol>li, nav#site-nav>ul>li>ul>li {
+    font-size: 1rem;
+  }
+}
+
+@media print {
+  nav#site-nav>ul:before {
+    font-size: 1.5em;
+    font-weight: bold;
+    padding-left: 0;
+  }
+}
+
+/*
+ * Breadcrumbs
+ */
+
+#theme-breadcrumbs {
+  padding-top: 0;
+  padding-bottom: 0;
+  background-color: white;
+}
+
+#theme-breadcrumbs ul {
+  padding: 0;
+  margin: 0;
+  list-style: none;
+  line-height: 2em;
+}
+#theme-breadcrumbs li {
+  display: inline-block;
+  margin: -1.15em 0;
+  max-width: 100%;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+  overflow: hidden;
+}
+
+#theme-breadcrumbs li::after {
+  content: '›';
+  display: inline-block;
+  opacity: 0.3;
+  font-size: 1em;
+  padding: .5em;
+  line-height: 0;
+}
+
+@media print {
+  #theme-breadcrumbs {
+    display: none;
+  }
+}
+
+/*
+ * Edit links
+*/
+
+main .edit-links {
+  padding-left: 0;
+}
+main .edit-links li {
+  list-style-type: none;
+}
+main .edit-links li a {
+  margin-bottom: 0.5em;
+  padding: 0.5em;
+  text-decoration: none;
+  border-radius: 2px;
+  display: inline-block;
+  border: 1px solid lightgrey;
+}
+main .edit-links li a:link {
+  border-bottom: 1px solid blue;
+}
+main .edit-links li a:visited {
+  border-bottom: 1px solid purple;
+}
+main .edit-links a svg {
+  vertical-align: -2px;
+}
+@media print {
+  h3#page-edit-links, main .edit-links {
+    display: none;
+  }
+}
+
+/*
+ * Metadata display
+ */
+
+.metadata tbody {
+  width: 100%;
+}
+.metadata tr {
+  margin: .25em 0 0 0;
+}
+.metadata .expired {
+  color: red;
+}
+.metadata td, .metadata th {
+  padding: 0, 0.5em, 0.5em, 0;
+  text-align: left;
+  vertical-align: top;
+}
+
+/*
+ * Footer
+ */
+
+@media screen {
+  .footer-trio {
+    width: 100%;
+    display: flex;
+    flex-direction: row;
+    justify-content: space-between;
+  }
+  .footer-trio section {
+    background: white;
+    width: calc(33.33% - 15px);
+    max-width: none;
+    padding: 30px;
+    box-sizing: border-box;
+    display: flex;
+    flex-direction: column;
+    justify-content: space-between;
+  }
+  .footer-trio h2 {
+    margin: 0px;
+  }
+  .footer-links {
+    text-align: right;
+  }
+  .footer-trio section a {
+    font-weight: 700;
+    text-decoration: none;
+    display: inline-block;
+    clear: both;
+    float: right;
+    margin-top: 15px;
+  }
+  .footer-trio section a:after {
+    content: '>';
+    padding-left: 8px;
+  }
+
+  .footer-duo {
+    width: 100%;
+    margin: 50px 0px;
+    display: flex;
+    flex-direction: row;
+    justify-content: space-between;
+  }
+  .footer-contact {
+    width: calc(33.33% - 15px);
+    max-width: none;
+    padding-left: 30px;
+    box-sizing: border-box;
+  }
+  .footer-contact dl {
+    width: 100%;
+    display: flex;
+    flex-flow: row;
+    flex-wrap: wrap;
+    overflow: visible;
+  }
+  .footer-contact dt {
+    font-weight: 700;
+    flex: 0 0 100px;
+  }
+  .footer-contact dd {
+    margin-left: auto;
+    text-align: left;
+    flex: 0 0 calc(100% - 100px);
+    display: block;
+    padding-bottom: 1em;
+  }
+  .footer-contact dd a {
+  }
+  .footer-contact dd address {
+    font-style: normal;
+  }
+
+  .footer-notes {
+    width: calc(66.67% - 7.5px);
+    max-width: none;
+    padding-left: 30px;
+    box-sizing: border-box;
+  }
+  .footer-note-cluster {
+    margin-top: 30px;
+  }
+  .footer-last-updated::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve' aria-hidden='true'%3e%3cpath fill-rule='evenodd' fill='black' d='M1.5 8a6.5 6.5 0 1113 0 6.5 6.5 0 01-13 0zM8 0a8 8 0 100 16A8 8 0 008 0zm.5 4.75a.75.75 0 00-1.5 0v3.5a.75.75 0 00.471.696l2.5 1a.75.75 0 00.557-1.392L8.5 7.742V4.75z'%3e%3c/path%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+  .footer-copyright::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve' aria-hidden='true'%3e%3cpath fill='black' d='M1.5,8c0-1.7,0.7-3.4,1.9-4.6C4.6,2.2,6.3,1.5,8,1.5s3.4,0.7,4.6,1.9c1.2,1.2,1.9,2.9,1.9,4.6s-0.7,3.4-1.9,4.6 S9.7,14.5,8,14.5s-3.4-0.7-4.6-1.9C2.2,11.4,1.5,9.7,1.5,8z M8,0C5.9,0,3.8,0.8,2.3,2.3C0.8,3.8,0,5.9,0,8c0,2.1,0.8,4.2,2.3,5.7 C3.8,15.2,5.9,16,8,16c2.1,0,4.2-0.8,5.7-2.3C15.2,12.2,16,10.1,16,8c0-2.1-0.8-4.2-2.3-5.7C12.2,0.8,10.1,0,8,0z'/%3e%3cpath fill='black' class='st0' d='M8,5.8c-1.2,0-2.2,1-2.2,2.2s1,2.2,2.2,2.2c0.6,0,1.1-0.2,1.5-0.6c0.3-0.3,0.8-0.3,1.1,0c0.3,0.3,0.3,0.8,0,1.1 c-0.7,0.6-1.6,1-2.6,1c-2.1,0-3.7-1.7-3.7-3.8c0-2.1,1.6-3.8,3.7-3.8c1,0,1.9,0.4,2.6,1c0.3,0.3,0.3,0.8,0,1.1 c-0.3,0.3-0.8,0.3-1.1,0C9.1,6,8.5,5.8,8,5.8z'/%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+  .footer-license::before {
+    content:'';
+    background-image: url("data:image/svg+xml;charset=UTF-8,%3csvg version='1.1' xmlns='http://www.w3.org/2000/svg' xmlns:xlink='http://www.w3.org/1999/xlink' x='0px' y='0px' width='16px' height='16px' viewBox='0 0 16 16' style='overflow:visible;enable-background:new 0 0 16 16;' xml:space='preserve'  aria-hidden='true'%3e%3cpath fill-rule='evenodd' fill='black' d='M8.75.75a.75.75 0 00-1.5 0V2h-.984c-.305 0-.604.08-.869.23l-1.288.737A.25.25 0 013.984 3H1.75a.75.75 0 000 1.5h.428L.066 9.192a.75.75 0 00.154.838l.53-.53-.53.53v.001l.002.002.002.002.006.006.016.015.045.04a3.514 3.514 0 00.686.45A4.492 4.492 0 003 11c.88 0 1.556-.22 2.023-.454a3.515 3.515 0 00.686-.45l.045-.04.016-.015.006-.006.002-.002.001-.002L5.25 9.5l.53.53a.75.75 0 00.154-.838L3.822 4.5h.162c.305 0 .604-.08.869-.23l1.289-.737a.25.25 0 01.124-.033h.984V13h-2.5a.75.75 0 000 1.5h6.5a.75.75 0 000-1.5h-2.5V3.5h.984a.25.25 0 01.124.033l1.29.736c.264.152.563.231.868.231h.162l-2.112 4.692a.75.75 0 00.154.838l.53-.53-.53.53v.001l.002.002.002.002.006.006.016.015.045.04a3.517 3.517 0 00.686.45A4.492 4.492 0 0013 11c.88 0 1.556-.22 2.023-.454a3.512 3.512 0 00.686-.45l.045-.04.01-.01.006-.005.006-.006.002-.002.001-.002-.529-.531.53.53a.75.75 0 00.154-.838L13.823 4.5h.427a.75.75 0 000-1.5h-2.234a.25.25 0 01-.124-.033l-1.29-.736A1.75 1.75 0 009.735 2H8.75V.75zM1.695 9.227c.285.135.718.273 1.305.273s1.02-.138 1.305-.273L3 6.327l-1.305 2.9zm10 0c.285.135.718.273 1.305.273s1.02-.138 1.305-.273L13 6.327l-1.305 2.9z'%3e%3c/path%3e%3c/svg%3e");
+    background-repeat: no-repeat;
+    width: 16px;
+    height: 16px;
+    position: relative;
+    margin-right: 8px;
+    display: inline-block;
+    transform: translateY(3px);
+  }
+
+  #search-repository>button {
+    border-bottom-color: blue;
+  }
+
+  @media screen and (max-width: 1000px) {
+    .footer-contact dl {
+      flex-flow: column;
+    }
+    .footer-contact dt {
+      flex: 0 0 auto;
+    }
+    .footer-contact dd {
+      margin-left: 0;
+      flex: 0 0 auto;
+    }
+  }
+
+  @media screen and (max-width: 800px) {
+    .footer-trio {
+      flex-direction: column;
+    }
+    .footer-trio section {
+      width: 100%;
+      margin-bottom: 20px;
+    }
+    .footer-duo {
+      flex-direction: column;
+    }
+    .footer-duo section {
+      width: 100%;
+    }
+  }
+}
+@media print {
+  footer {
+    page-break-after: always;
+  }
+  #search-repository {
+    display: none;
+  }
+}
diff --git a/_site/assets/unlock.svg b/_site/assets/unlock.svg
new file mode 100644
index 00000000..6510b4d6
--- /dev/null
+++ b/_site/assets/unlock.svg
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg width="595" height="842" viewBox="0 0 595 842" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<metadata id="metadata5">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+          <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+          <dc:title>Unlock public code</dc:title>
+          <cc:license rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/" />
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/publicdomain/zero/1.0/">
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#Distribution" />
+          <cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks" />
+     </cc:License>
+  </rdf:RDF>
+</metadata>
+<rect width="595" height="842" fill="white"/>
+<rect width="595" height="842" fill="#5B57CA"/>
+<rect x="268" y="405" width="200" height="150" fill="#FFF500"/>
+<rect x="128" y="315" width="200" height="150" fill="#FF776E"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M232.377 392.651C232.275 392.199 232.499 391.74 232.9 391.509C236.453 389.461 238.844 385.624 238.844 381.228C238.844 374.679 233.535 369.37 226.986 369.37C220.437 369.37 215.128 374.679 215.128 381.228C215.128 385.778 217.69 389.729 221.45 391.718C221.872 391.941 222.114 392.413 222.009 392.879L216.218 418.489C216.077 419.114 216.552 419.709 217.194 419.709H237.243C237.885 419.709 238.36 419.114 238.219 418.489L232.377 392.651Z" fill="black"/>
+<rect x="386" y="460" width="22" height="36" rx="11" stroke="#FF6666" stroke-width="7" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="337" y="493" width="12" height="6" fill="#D95047"/>
+<rect x="333" y="493" width="13" height="6" fill="#F55C5C"/>
+<rect x="337" y="481" width="12" height="6" fill="#D95047"/>
+<rect x="333" y="481" width="13" height="6" fill="#F55C5C"/>
+<rect x="339" y="487" width="13" height="6" fill="#D95047"/>
+<rect x="337" y="487" width="12" height="6" fill="#F55C5C"/>
+<line x1="383.5" y1="478.5" x2="331.5" y2="478.5" stroke="#FF6666" stroke-width="7" stroke-linecap="round" stroke-linejoin="round"/>
+<rect x="268" y="405" width="60" height="60" fill="#0000FF"/>
+<path d="M301 428.483H308.241C312.526 428.483 316 431.956 316 436.241V436.241C316 440.526 312.526 444 308.241 444H288.637C283.867 444 280 440.133 280 435.363V435.363C280 431.337 282.782 427.845 286.706 426.944L293 425.5" stroke="white" stroke-width="5"/>
+<path d="M297.5 418.875V411M302.375 420L307.625 414.75M292.625 420L287.375 414.75" stroke="#FFF500" stroke-width="3"/>
+<line x1="308" y1="435.5" x2="328" y2="435.5" stroke="white" stroke-width="5"/>
+<line x1="268" y1="435.5" x2="288" y2="435.5" stroke="white" stroke-width="5"/>
+</svg>
diff --git a/_site/assets/version-badge.svg b/_site/assets/version-badge.svg
new file mode 100644
index 00000000..26d99837
--- /dev/null
+++ b/_site/assets/version-badge.svg
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net> -->
+<!-- version-badge.svg 0.7.1 yellow -->
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="90" height="20" role="img" aria-label="version: 0.7.1">
+  <title>version: 0.7.1</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="90" height="20" rx="3" fill="#fff"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="51" height="20" fill="#555"/>
+    <rect x="51" width="39" height="20" fill="#dfb317"/>
+    <rect width="90" height="20" fill="url(#s)"/>
+  </g>
+  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+    <text aria-hidden="true" x="265" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="410">version</text>
+    <text x="265" y="140" transform="scale(.1)" fill="#fff" textLength="410">version</text>
+    <text aria-hidden="true" x="695" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="290">0.7.1</text>
+    <text x="695" y="140" transform="scale(.1)" fill="#fff" textLength="290">0.7.1</text>
+  </g>
+</svg>
diff --git a/_site/criteria/advertise-maturity.html b/_site/criteria/advertise-maturity.html
new file mode 100644
index 00000000..f159d99e
--- /dev/null
+++ b/_site/criteria/advertise-maturity.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/document-codebase-maturity.html">
+  <script>location="/criteria/document-codebase-maturity.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/document-codebase-maturity.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/document-codebase-maturity.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/bundle-policy-and-code.html b/_site/criteria/bundle-policy-and-code.html
new file mode 100644
index 00000000..1ce82743
--- /dev/null
+++ b/_site/criteria/bundle-policy-and-code.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/bundle-policy-and-source-code.html">
+  <script>location="/criteria/bundle-policy-and-source-code.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/bundle-policy-and-source-code.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/bundle-policy-and-source-code.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/bundle-policy-and-source-code.html b/_site/criteria/bundle-policy-and-source-code.html
new file mode 100644
index 00000000..59d1c23c
--- /dev/null
+++ b/_site/criteria/bundle-policy-and-source-code.html
@@ -0,0 +1,501 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>政策與原始碼要合捆, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/bundle-policy-and-source-code.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/code-in-the-open.html"
+		     >&#8592; 原始碼要開放</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/make-the-codebase-reusable-and-portable.html"
+		     >程式基底要可重複使用且可移植 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/bundle-policy-and-source-code.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/bundle-policy-and-source-code.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="政策與原始碼要合捆">政策與原始碼要合捆</h1>
+
+<p>對於想根據所在情境實作程式基底的人，或是想更進一步貢獻<a href="/glossary.html#codebase">程式基底</a>開發的人來說，能同時取用<a href="../glossary.md#source-code">原始
+碼</a>與<a href="/glossary.html#policy">政策</a>文件兩者，可作為建置成品時的基礎組件。</p>
+
+<p>瞭解作用範疇與該範疇的政策是基本原則，才能瞭解程式基底試圖想解決的問題是什麼，以及該如何解決這些問題的作法。</p>
+
+<p>為了評估是否需要在新的情境中實作程式基底，組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」包含原始碼所根據的政策。</li>
+  <li>如果政策根據原始碼而來，則該原始碼「必須」包含在程式基底中，用於偵測詐騙的原始碼則可除外。</li>
+  <li>政策「應該」採用機器可讀且明確的格式。</li>
+  <li><a href="/glossary.html#continuous-integration">持續整合</a>測試「應該」驗證原始碼與政策是否有一致執行。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與公務人員確認原始碼所根據的所有政策內容都有收錄在內。</li>
+  <li>與公務人員確認政策所根據的所有原始碼都有收錄在內。</li>
+  <li>確認政策內容是否能在機器上解讀。</li>
+  <li>確認原始碼與政策間的執行一致性能通過持續整合測試。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>提供相關政策內文，以便收錄於<a href="/glossary.html#repository">儲存庫</a>中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單
+位所選擇遵守的各項標準，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。</li>
+  <li>請提供政策相關參考資料與連結。</li>
+  <li>政策內容請使用明確且機器可讀的格式，像是<a href="https://www.omg.org/spec/">物件管理群體</a>所發表的格式。</li>
+  <li>追蹤政策時，請使用與追蹤原始碼<a href="/criteria/maintain-version-control.html">相同的版本控制</a>與文件。</li>
+  <li>定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合<a href="/criteria/document-codebase-objectives.html">政策意圖</a>。</li>
+  <li>納入會影響社會群體、程式基底與開發目標的相關政策，包含 <a href="https://eur-lex.europa.eu/eli/reg/2016/679/oj">GDPR 一般資料保護規
+則</a>或是<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟網頁無障礙命
+令</a>等此類法律義務，或者是人權政
+策，例如公家機關對機會平等的承諾等。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。</li>
+  <li>確保政策制定者、開發人員與設計師朝相同目標努力。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。</li>
+  <li>與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>針對如何讓政策文字更清楚提供意見。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>維基百科上的 <a href="https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation">BPMN 業務流程模型與標記
+法</a>。</li>
+  <li>Trisotech 提供的 <a href="https://www.bpmnquickguide.com/view-bpmn-quick-guide/">BPMN 快速指
+南</a>。</li>
+  <li>維基百科上的 <a href="https://en.wikipedia.org/wiki/Decision_Model_and_Notation">DMN 決策模型與標記
+法</a>。</li>
+  <li>維基百科上的<a href="https://en.wikipedia.org/wiki/CMMN"> CMMN 案例管理模型標記法</a>。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/code-in-the-open.html b/_site/criteria/code-in-the-open.html
new file mode 100644
index 00000000..2ed413eb
--- /dev/null
+++ b/_site/criteria/code-in-the-open.html
@@ -0,0 +1,492 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>原始碼要開放, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/code-in-the-open.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/"
+		     >&#8592; 準則</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/bundle-policy-and-source-code.html"
+		     >政策與原始碼要合捆 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/code-in-the-open.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/code-in-the-open.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="原始碼要開放">原始碼要開放</h1>
+
+<p>以開放精神編寫原始碼，能改善資訊透明、提高<a href="/glossary.html#source-code">原始碼</a>品質、讓原始碼更容易稽核，也能促進互相協作。</p>
+
+<p>這些合在一起，讓公民更有機會瞭解軟體與<a href="/glossary.html#policy">政策</a>如何影響他們與公家機關的互動。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>程式基底「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。</li>
+  <li>目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。</li>
+  <li>「可選擇」是否要以文件記錄<a href="/glossary.html#general-public">一般大眾</a>與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或
+支持的政策。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。</li>
+  <li>確認<a href="/glossary.html#codebase">程式基底</a>檔案與送交版次歷史紀錄，不包含敏感性資訊。</li>
+  <li>檢查目前非使用中的原始碼是否有公開。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定合乎開放精神的政策。</li>
+  <li>以公開透明的政策為優先。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>孕育擁抱開放、重視學習、歡迎意見回饋的文化。</li>
+  <li>與外部供應商和自由工作者以開放精神的方式協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>審查人員在檢核每次的送交版次紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。</li>
+  <li>為符合上述敏感性資訊的相關規定，請明確分開資料與原始碼。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">以開放精神編寫原始
+碼</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed">程式碼應該開放或封閉的時
+機</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open">以開放精神編寫原始碼的資安考
+量</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/deploying-software-regularly">定期部署軟
+體</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">政府數位服務團如何使用
+GitHub</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/continuous-integration.html b/_site/criteria/continuous-integration.html
new file mode 100644
index 00000000..1136b0be
--- /dev/null
+++ b/_site/criteria/continuous-integration.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/use-continuous-integration.html">
+  <script>location="/criteria/use-continuous-integration.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/use-continuous-integration.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/use-continuous-integration.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/create-reusable-and-portable-code.html b/_site/criteria/create-reusable-and-portable-code.html
new file mode 100644
index 00000000..3220819c
--- /dev/null
+++ b/_site/criteria/create-reusable-and-portable-code.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/make-the-codebase-reusable-and-portable.html">
+  <script>location="/criteria/make-the-codebase-reusable-and-portable.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/make-the-codebase-reusable-and-portable.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/make-the-codebase-reusable-and-portable.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/document-codebase-maturity.html b/_site/criteria/document-codebase-maturity.html
new file mode 100644
index 00000000..f98de071
--- /dev/null
+++ b/_site/criteria/document-codebase-maturity.html
@@ -0,0 +1,483 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>記錄程式基底成熟度, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/document-codebase-maturity.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/use-a-coherent-style.html"
+		     >&#8592; 風格要前後一致</a></span>
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/document-codebase-maturity.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/document-codebase-maturity.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="記錄程式基底成熟度">記錄程式基底成熟度</h1>
+
+<p>清楚標示<a href="/glossary.html#codebase">程式基底</a>的成熟度，有助於他人決定是否要使用，或為該程式基底做出貢獻。程式基底版本的成熟度，包含其依賴項
+目的成熟度。瞭解程式基底演進到什麼程度，是理解該程式基底並知道如何做出貢獻的關鍵。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」註明版本編號。</li>
+  <li>程式基底「必須」明確以文件記錄，是否有已經準備好可供使用的版本。</li>
+  <li>準備好可供使用的程式基底版本，「必須」只能依賴其他也已經準備好可供使用的程式基底版本。</li>
+  <li>程式基底「應該」包含每次版本的變動紀錄，像是以「<code class="language-plaintext highlighter-rouge">CHANGELOG</code>」日誌格式檔記錄。</li>
+  <li>「應該」要以文件記錄分配版本識別碼的方法。</li>
+  <li>「可選擇」是否採用語意化版本控制編號。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底有版本編號策略，且有文件記載該策略。</li>
+  <li>確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道程式基底是否有準備好可供使用的版本。</li>
+  <li>確認準備好可供使用的程式基底版本，並不依賴任何尚未準備好可供使用的其他程式基底的版本。</li>
+  <li>確認有文件記錄程式基底的版本編號方法，並且確實遵守。</li>
+  <li>確認是否有版本的變動紀錄。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定<a href="/glossary.html#policy">政策</a>時，請記住任何開發出來的<a href="/glossary.html#source-code">原始碼</a>都必須先經過
+測試與改善，才能夠投入服務。</li>
+  <li>考慮將政策的變動註明版本編號，尤其是因而觸發新版本原始碼開發的情況。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>要確認服務依賴的程式基底版本成熟度，等同或高於該服務本身。舉例來說，正式上線的服務不要使用 beta 公測版程式基底。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>確認所有發行版，都有遵守程式基底的版本控制編號作法。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>許多程式基底使用「<a href="https://semver.org/">語意化版本編號規範</a>」來標示版本。</li>
+  <li><a href="https://en.wikipedia.org/wiki/Software_release_life_cycle">軟體發行生命週期</a></li>
+  <li>澳洲數位轉型局《<a href="https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process">服務設計與交付流
+程</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/agile-delivery">敏捷交付服務手冊</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/document-codebase-objectives.html b/_site/criteria/document-codebase-objectives.html
new file mode 100644
index 00000000..7e0c09eb
--- /dev/null
+++ b/_site/criteria/document-codebase-objectives.html
@@ -0,0 +1,478 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式基底要有目標文件, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/document-codebase-objectives.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/require-review-of-contributions.html"
+		     >&#8592; 要求審查貢獻內容</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/document-the-code.html"
+		     >程式碼要有文件 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/document-codebase-objectives.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/document-codebase-objectives.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式基底要有目標文件">程式基底要有目標文件</h1>
+
+<p>以文件清楚記錄<a href="/glossary.html#codebase">程式基底</a>目標，來傳達程式基底的用途目標。這能幫助利害關係人與貢獻者劃定程式基底的開發範圍。這些目
+標也能方便人們判斷，是否在當下或未來，會對此程式基底或其模組感興趣。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用程式基底或協助貢獻。</li>
+  <li>程式基底文件「應該」清楚描述<a href="/glossary.html#policy">政策</a>目標與程式基底目標之間的關聯。</li>
+  <li>「可選擇」是否以文件記錄給<a href="/glossary.html#general-public">一般大眾</a>看的程式基底目標。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底文件有包含程式基底目標，或主旨、使命等。</li>
+  <li>查看政策目標與程式基底目標之間關聯的描述。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>將政策目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>確保所有程式基底目標，有連結或引用為了符合〈<a href="/criteria/bundle-policy-and-source-code.html">政策與原始碼要合捆</a>〉準則而加入的支持政策文
+件。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將單位目標、組織目標或業務目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將技術與設計目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Marek Hajduczenia《<a href="http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf">如何撰寫專案目
+標</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/document-maturity.html b/_site/criteria/document-maturity.html
new file mode 100644
index 00000000..f159d99e
--- /dev/null
+++ b/_site/criteria/document-maturity.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/document-codebase-maturity.html">
+  <script>location="/criteria/document-codebase-maturity.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/document-codebase-maturity.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/document-codebase-maturity.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/document-objectives.html b/_site/criteria/document-objectives.html
new file mode 100644
index 00000000..f8c50e56
--- /dev/null
+++ b/_site/criteria/document-objectives.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/document-codebase-objectives.html">
+  <script>location="/criteria/document-codebase-objectives.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/document-codebase-objectives.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/document-codebase-objectives.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/document-the-code.html b/_site/criteria/document-the-code.html
new file mode 100644
index 00000000..2ea9a10e
--- /dev/null
+++ b/_site/criteria/document-the-code.html
@@ -0,0 +1,490 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式碼要有文件, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/document-the-code.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/document-codebase-objectives.html"
+		     >&#8592; 程式基底要有目標文件</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/use-plain-english.html"
+		     >使用白話的英語 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/document-the-code.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/document-the-code.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式碼要有文件">程式碼要有文件</h1>
+
+<p>文件記錄周全的<a href="/glossary.html#source-code">原始碼</a>能幫助人們瞭解該原始碼的作用與使用方式。文件紀錄是幫助人們快速上手如何使用<a href="../glossary.md#codebase">程式基
+底</a>，並做出貢獻的關鍵。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底的所有功能、<a href="/glossary.html#policy">政策</a>及原始碼，都「必須」以可清楚瞭解的用語描述，讓懂程式基底目的用途的人也能夠理解。</li>
+  <li>程式基底文件「必須」說明如何安裝與執行軟體。</li>
+  <li>程式基底文件「必須」為關鍵功能舉出範例。</li>
+  <li>程式基底文件「應該」包含精要的說明，讓<a href="/glossary.html#general-public">一般大眾</a>和記者等廣泛的利害關係人都能清楚明白。</li>
+  <li>程式基底文件「應該」有一部分用來說明，如何安裝與執行原始碼的單機版；如果有必要，也應該包含測試資料集。</li>
+  <li>程式基底文件「應該」包含所有功能的範例。</li>
+  <li>程式碼文件「應該」描述程式基底的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。</li>
+  <li>「應該」要有針對文件品質的<a href="/glossary.html#continuous-integration">持續整合</a>測試。</li>
+  <li>「可選擇」是否在程式基底文件中，包含讓使用者想要立即使用程式基底的範例。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認文件內容能讓其他利害關係人、其他公家機關的專業人士，以及一般大眾，都可以清楚明白。</li>
+  <li>確認文件有說明如何安裝與執行原始碼。</li>
+  <li>確認文件有包含主要功能的範例。</li>
+  <li>向一般大眾的成員以及記者確認，他們是否能明白文件當中的精要說明。</li>
+  <li>檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。</li>
+  <li>檢查文件中列舉的所有功能都包含範例。</li>
+  <li>檢查文件中是否包含高層架構圖，或類似的組件關係圖表。</li>
+  <li>確認整合測試有包含到程式碼文件品質，例如確認生成的文件是否正確，並檢查連結與圖片等。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>定期查看程式基底中非政策程式碼的變動情況。</li>
+  <li>針對如何讓非政策文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這套程式基底？</li>
+  <li>確保您同時瞭解政策、原始碼以及文件內容。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>定期查看程式基底中非原始碼部分的變動情況。</li>
+  <li>針對如何讓非原始碼文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Write the Docs《<a href="https://www.writethedocs.org/guide/">文件指南</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/documenting.html b/_site/criteria/documenting.html
new file mode 100644
index 00000000..e513d32e
--- /dev/null
+++ b/_site/criteria/documenting.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/document-the-code.html">
+  <script>location="/criteria/document-the-code.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/document-the-code.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/document-the-code.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/findability.html b/_site/criteria/findability.html
new file mode 100644
index 00000000..2390e655
--- /dev/null
+++ b/_site/criteria/findability.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/make-the-codebase-findable.html">
+  <script>location="/criteria/make-the-codebase-findable.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/make-the-codebase-findable.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/make-the-codebase-findable.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/index.html b/_site/criteria/index.html
new file mode 100644
index 00000000..4126b85c
--- /dev/null
+++ b/_site/criteria/index.html
@@ -0,0 +1,473 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>準則, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/code-in-the-open.html"
+		     >原始碼要開放 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/index.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/index.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="準則">準則</h1>
+
+<ol>
+  <li>
+    <p><a href="/criteria/code-in-the-open.html">原始碼要開放</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/bundle-policy-and-source-code.html">政策與原始碼要合捆</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/make-the-codebase-reusable-and-portable.html">程式基底要可重複使用且可移植</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/welcome-contributors.html">歡迎貢獻者</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/make-contributing-easy.html">貢獻要容易</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/maintain-version-control.html">維護版本控制</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/require-review-of-contributions.html">要求審查貢獻內容</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-codebase-objectives.html">程式基底要有目標文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-the-code.html">程式碼要有文件</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/use-plain-english.html">使用白話的英語</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/use-open-standards.html">採用開放標準</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/use-continuous-integration.html">使用持續整合</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/publish-with-an-open-license.html">發行採用開放授權</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/make-the-codebase-findable.html">程式基底可查詢得到</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/use-a-coherent-style.html">風格要前後一致</a></p>
+  </li>
+  <li>
+    <p><a href="/criteria/document-codebase-maturity.html">記錄程式基底成熟度</a></p>
+  </li>
+</ol>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/maintain-version-control.html b/_site/criteria/maintain-version-control.html
new file mode 100644
index 00000000..06a52b03
--- /dev/null
+++ b/_site/criteria/maintain-version-control.html
@@ -0,0 +1,504 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>維護版本控制, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/maintain-version-control.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/make-contributing-easy.html"
+		     >&#8592; 貢獻要容易</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/require-review-of-contributions.html"
+		     >要求審查貢獻內容 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/maintain-version-control.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/maintain-version-control.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="維護版本控制">維護版本控制</h1>
+
+<p><a href="/glossary.html#version-control">版本控制</a>主要在追蹤<a href="/glossary.html#source-code">原始碼</a>以及其他<a href="../glossary.md#codebase">程
+式基底</a>檔案歷來的變動。這能讓您為程式基底維護有條理的變動歷史文件。這是大規模協作得以運作的要素，使開發人員可以
+針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底中的所有檔案皆「必須」有版本控制。</li>
+  <li>所有決定皆「必須」記錄成送交版次訊息。</li>
+  <li>每份送交版次訊息皆「必須」盡可能附上討論與議題連結。</li>
+  <li>程式基底「應該」以分散式版本控制系統作維護。</li>
+  <li>貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。</li>
+  <li>維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版本。</li>
+  <li>貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。</li>
+  <li>貢獻者「可選擇」是否對送交內容作簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底維持在版本控制狀態中，像是使用 Git 之類的軟體。</li>
+  <li>審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。</li>
+  <li>審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。</li>
+  <li>檢查版本控制系統是否為分散式。</li>
+  <li>審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。</li>
+  <li>檢查是否可能透過像是修訂版次標記，或文字標籤，來取用程式基底中的特定版本。</li>
+  <li>檢查程式基底在盡可能的情況下，檔案都是採用文字格式。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>如果因為<a href="/glossary.html#policy">政策</a>改變而在程式基底中有新的版本，則請確認有在文件中清楚說明：
+    <ul>
+      <li>政策改變的地方，</li>
+      <li>程式基底如何因應而改變。</li>
+    </ul>
+  </li>
+</ul>
+
+<p>舉例來說，為程式基底作權限管理時，如果要新增申請方類別來賦予取用權，應視為一種政策變動。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>支持政策制定者、開發人員與設計師，使其能清楚表達他們對程式基底做出的改善。確保改善程式基底不會有公關風險。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>確認版本控制系統中，有瞭解程式碼、建置與部署所需要用到的所有檔案。</li>
+  <li>送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。</li>
+  <li>使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。</li>
+  <li>送交版次訊息要寫清楚，方便之後比較各版本。</li>
+  <li>在政策改變以後，與政策制定者合作說明原始碼更新的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Karl Fogel《<a href="https://producingoss.com/en/vc.html#vc-vocabulary">製作開放原始碼軟體：版本控制字
+彙</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding">維護程式碼的版本控
+制</a>》。</li>
+  <li>GitHub 提供的「<a href="https://skills.github.com/">GitHub 技能</a>」，可學習如何使用 GitHub，或是重溫您的技巧。</li>
+  <li>GitHub 提供的「<a href="https://education.github.com/git-cheat-sheet-education.pdf">Git 密技
+表</a>」，列出了最常用的 git 命
+令。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/make-contributing-easy.html b/_site/criteria/make-contributing-easy.html
new file mode 100644
index 00000000..2663c498
--- /dev/null
+++ b/_site/criteria/make-contributing-easy.html
@@ -0,0 +1,489 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>貢獻要容易, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/make-contributing-easy.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/welcome-contributors.html"
+		     >&#8592; 歡迎貢獻者</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/maintain-version-control.html"
+		     >維護版本控制 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/make-contributing-easy.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/make-contributing-easy.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="貢獻要容易">貢獻要容易</h1>
+
+<p>若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的<a href="/glossary.html#codebase">程式基底</a>修正問題、新增功能，以及提出安全性議題
+等。</p>
+
+<p>共享的數位基礎建設讓協作貢獻更容易。使用者讓程式基底接受貢獻時所需付出的心力越少，則使用者越可能成為貢獻者。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。</li>
+  <li>文件中「必須」同時有公開的議題追蹤器連結，以及已提交的程式基底變動的連結，例如記錄在「<code class="language-plaintext highlighter-rouge">README</code>」檔案中。</li>
+  <li>程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。</li>
+  <li>「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。</li>
+  <li>文件「必須」說明，該如何通報潛在的安全性與敏感性問題。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有公開的議題追蹤器。</li>
+  <li>確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。</li>
+  <li>確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。</li>
+  <li>確認有封閉的管道可通報安全性問題。</li>
+  <li>確認有說明如何私下通報安全性問題。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>追蹤程式基底中的<a href="/glossary.html#policy">政策</a>問題，讓相關的外部政策專家如果自願也能夠協助。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>追蹤程式基底中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為程式基底持續做出長久貢獻。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>與<a href="/criteria/require-review-of-contributions.html">審查</a>流程相同，務必迅速回應請求。</li>
+  <li>告知管理人員，您在支援其他貢獻者時所需的時間與資源。</li>
+  <li>確保人們可輕鬆找到合適的溝通管道，來詢問維護人員與利害關係人問題，例如寫在「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>確保中介資料包含合適的聯絡資訊，例如寫在 publiccode.yml 檔案中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Joel Hans《<a href="https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf">如何引發他人為您的開放原始碼專案做出優秀貢
+獻</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">以開放精神編寫原始碼的好
+處</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/make-the-codebase-findable.html b/_site/criteria/make-the-codebase-findable.html
new file mode 100644
index 00000000..0222502c
--- /dev/null
+++ b/_site/criteria/make-the-codebase-findable.html
@@ -0,0 +1,511 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式基底可查詢得到, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/make-the-codebase-findable.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/publish-with-an-open-license.html"
+		     >&#8592; 發行採用開放授權</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/use-a-coherent-style.html"
+		     >風格要前後一致 &#8594;</a></span>
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/make-the-codebase-findable.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/make-the-codebase-findable.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式基底可查詢得到">程式基底可查詢得到</h1>
+
+<p>一旦<a href="/glossary.html#codebase">程式基底</a>越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個程式基底，然後就盼望他人找得到這套程式基
+底，更需要主動積極。</p>
+
+<p>有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體
+目錄列表之中（使程式基底成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現程式基底。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。</li>
+  <li>程式基底說明「應該」要簡短，幫助他人瞭解程式基底的目的與作用。</li>
+  <li>維護人員「應該」將程式基底提交至相關的軟體目錄上。</li>
+  <li>程式基底「應該」要架設網站，內容中以程式基底各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述程式基底所能解決的問題。</li>
+  <li>在搜尋引擎查找程式基底名稱時，「應該」能搜尋得到程式基底。</li>
+  <li>在使用搜尋引擎時，如果以自然語言描述程式基底所能解決的問題，「應該」能搜尋得到程式基底。</li>
+  <li>程式基底「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、<a href="/glossary.html#repository">儲存庫</a>、位置、網站等。</li>
+  <li>程式基底「應該」包含機器可讀的中介資料說明，例如採用
+<a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a>格式的檔案。</li>
+  <li>「可選擇」是否為程式基底設置專用的網域名稱。</li>
+  <li>「可選擇」是否在社群舉辦的會議中定期進行簡報。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>檢查程式基底名稱是否描述說明其用途，且不包含雙關語。</li>
+  <li>檢查程式基底名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完整名稱更熟為人知。</li>
+  <li>檢查程式基底是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是程式基底社群成員。</li>
+  <li>檢查程式基底儲存庫是否包含程式基底的簡短描述。</li>
+  <li>檢查程式基底有刊登在相關軟體型錄上。</li>
+  <li>檢查程式基底的網站有描述程式基底能夠解決的問題。</li>
+  <li>檢查以程式基底名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將程式基底列在搜尋結果中。</li>
+  <li>檢查以自然語言來作搜尋，例如使用程式基底的簡短描述時，有超過一個的常用主流搜尋引擎，都將程式基底放在搜尋結果中。</li>
+  <li>檢查永久唯一識別碼條目有提及主要貢獻者。</li>
+  <li>檢查永久唯一識別碼條目中有包含儲存庫位置。</li>
+  <li>檢查永久唯一識別碼條目有列出程式基底網站。</li>
+  <li>檢查中介資料說明檔是機器可讀的格式。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>貢獻一段說明此程式基底作用的政策領域，或所處理問題的描述。</li>
+  <li>請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。</li>
+  <li>在相關會議上作簡報，介紹程式基底如何執行<a href="/glossary.html#policy">政策</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。</li>
+  <li>在引用到程式基底的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。</li>
+  <li>為團隊編列內容設計與實作 SEO 搜尋引擎最佳化技能的預算。</li>
+  <li>確保專案參與人員出席相關會議，或作簡報介紹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>實作搜尋引擎最佳化，例如加入<a href="https://www.sitemaps.org/protocol.html">網站地圖</a>。</li>
+  <li>在引用到程式基底的地方，都使用簡短描述，例如放到儲存庫中的說明。</li>
+  <li>請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。</li>
+  <li>推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Wikidata 維基數據社群《<a href="https://www.wikidata.org/wiki/Wikidata:Introduction">維基數據簡
+介</a>》。</li>
+  <li>FSF 自由軟體基金會《<a href="https://directory.fsf.org/wiki/Main_Page">FSF 軟體目錄列表</a>》。</li>
+  <li>GO FAIR 國際支援與合作辦公室所撰寫的《<a href="https://www.go-fair.org/fair-principles/">FAIR 科學資料管理與監督指導原
+則</a>》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
+機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/make-the-codebase-reusable-and-portable.html b/_site/criteria/make-the-codebase-reusable-and-portable.html
new file mode 100644
index 00000000..fc6c3c4d
--- /dev/null
+++ b/_site/criteria/make-the-codebase-reusable-and-portable.html
@@ -0,0 +1,522 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>程式基底要可重複使用且可移植, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/make-the-codebase-reusable-and-portable.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/bundle-policy-and-source-code.html"
+		     >&#8592; 政策與原始碼要合捆</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/welcome-contributors.html"
+		     >歡迎貢獻者 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/make-the-codebase-reusable-and-portable.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/make-the-codebase-reusable-and-portable.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="程式基底要可重複使用且可移植">程式基底要可重複使用且可移植</h1>
+
+<p>編寫可重複使用且可移植的<a href="/glossary.html#code">程式碼</a>，讓政策制定者、開發人員與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻
+回程式基底中，如此可提高品質、降低維護成本、增強可靠性。</p>
+
+<p>以重複利用為前提籌劃設計<a href="/glossary.html#codebase">程式基底</a>，更容易與多方共享程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，
+更可以從能自我運作的社群中獲益。</p>
+
+<p>以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在<a href="/glossary.html#different-contexts">另一種情境</a>中重複利用。</p>
+
+<p>原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢獻者都能測試該原始碼。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」開發成能在不同情境中重複使用。</li>
+  <li>程式基底「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，以供執行與瞭解。</li>
+  <li>程式基底「應該」有多方單位使用。</li>
+  <li>發展路線圖「應該」有多方單位的需求影響。</li>
+  <li>程式基底開發「應該」由多方單位協作。</li>
+  <li>「應該」使用組態設定方式以將<a href="/glossary.html#source-code">原始碼</a>調整成能適應各情境的特定需求。</li>
+  <li>程式基底「應該」能夠在地化。</li>
+  <li>原始碼與其文件「不應該」包含特定情況專用的資訊。</li>
+  <li>程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。</li>
+  <li>軟體「不應該」要求僅有單一供應商能提供的服務或平台。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與另一組織單位角色與您相似的人確認，看他們是否能利用程式基底，以及需要怎麼進行。</li>
+  <li>確認程式基底不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。</li>
+  <li>若程式基底處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意圖跡象。
+    <ul>
+      <li>或是如果程式基底非常成熟與穩定，鮮少需要修正、改善或貢獻：
+        <ul>
+          <li>檢查是否有多方單位，或是有在多種情境下正使用程式基底。</li>
+          <li>檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。</li>
+        </ul>
+      </li>
+      <li>若是沒有，則：
+        <ul>
+          <li>檢查是否有多方單位，或是有在多種情境下正使用程式基底。</li>
+          <li>檢查程式基底貢獻者是否來自多方單位。</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>檢查程式基底檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。</li>
+  <li>檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為您的<a href="/glossary.html#policy">政策</a>撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。</li>
+  <li>確保程式基底有將貴組織單位列為已知使用者。</li>
+  <li>找出貴團隊想要協作的其他組織單位。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確認利害關係人與業主能夠瞭解，程式基底是以重複利用為明確目標，因而得以減少程式碼技術債，並讓程式基底可以永續發展。</li>
+  <li>確認您的團隊與其他團隊能相互協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>原始碼應該設計成：</p>
+
+<ul>
+  <li>能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，</li>
+  <li>能解決通用性質問題，而非特定問題，</li>
+  <li>以邏輯上具有意義且獨立的模組構成，</li>
+  <li>如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。</li>
+</ul>
+
+<p>確保程式基底文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進
+行開發、使用、測試、部署等。</p>
+
+<p>在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable">讓原始碼開放且可重複利
+用</a>》。</li>
+  <li>W3C 全球資訊網協會《<a href="https://www.w3.org/International/questions/qa-i18n">在地化與國際化</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/open-licenses.html b/_site/criteria/open-licenses.html
new file mode 100644
index 00000000..08dd1f7c
--- /dev/null
+++ b/_site/criteria/open-licenses.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/publish-with-an-open-license.html">
+  <script>location="/criteria/publish-with-an-open-license.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/publish-with-an-open-license.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/publish-with-an-open-license.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/open-standards.html b/_site/criteria/open-standards.html
new file mode 100644
index 00000000..bede9515
--- /dev/null
+++ b/_site/criteria/open-standards.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/use-open-standards.html">
+  <script>location="/criteria/use-open-standards.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/use-open-standards.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/use-open-standards.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/open-to-contributions.html b/_site/criteria/open-to-contributions.html
new file mode 100644
index 00000000..b349ab45
--- /dev/null
+++ b/_site/criteria/open-to-contributions.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/welcome-contributors.html">
+  <script>location="/criteria/welcome-contributors.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/welcome-contributors.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/welcome-contributors.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/publish-with-an-open-license.html b/_site/criteria/publish-with-an-open-license.html
new file mode 100644
index 00000000..96e37471
--- /dev/null
+++ b/_site/criteria/publish-with-an-open-license.html
@@ -0,0 +1,499 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>發行採用開放授權, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/publish-with-an-open-license.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/use-continuous-integration.html"
+		     >&#8592; 使用持續整合</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/make-the-codebase-findable.html"
+		     >程式基底可查詢得到 &#8594;</a></span>
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/publish-with-an-open-license.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/publish-with-an-open-license.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="發行採用開放授權">發行採用開放授權</h1>
+
+<p>採用開放且為人熟知的授權，讓任何人都可以查看<a href="/glossary.html#source-code">原始碼</a>，使其能瞭解運作方式、自由使用，並且能為<a href="../glossary.md#codebase">程式基
+底</a>做出貢獻。這也能促進供應商建立出以程式基底為中心的生態系。</p>
+
+<p>明確指出程式基底中每一個檔案的授權，讓使用者能正確重複利用程式基底的部分內容，並表彰作者名稱。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>所有原始碼與文件，皆「必須」採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。</li>
+  <li>軟體原始碼「必須」採用<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
+款</a>。</li>
+  <li>所有原始碼皆「必須」搭配授權條款檔案一併發行。</li>
+  <li>「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給程式基底。</li>
+  <li>程式基底中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容。</li>
+  <li>「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底有清楚給予授權條款。</li>
+  <li>確認原始碼的授權條款有列於<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清
+單</a>，以及文件的授權條款有<a href="https://opendefinition.org/licenses/">符合「開放定
+義」</a>。</li>
+  <li>確認程式基底中有包含其採用的授權條款檔案。</li>
+  <li>確認貢獻指引中，以及<a href="/glossary.html#repository">儲存庫</a>的組態設定中，沒有要求貢獻者轉讓著作權。</li>
+  <li>在程式基底<a href="/glossary.html#continuous-integration">持續整合</a>測試中，確認是否有檢查授權內容為機器可讀的檢查項目。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定要求原始碼必須採用<a href="/glossary.html#open-source">開放原始碼</a>授權的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>制定抑制採購非開放原始碼授權程式碼，與非開放科技的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>只與能採用開放原始碼授權交付、與發行其原始碼的開放原始碼軟體供應商合作。</li>
+  <li>請注意，雖然<a href="https://creativecommons.org/licenses/">創用CC授權</a>適合用於文件作品，但其中指明「非商業性」或「禁止改作」
+的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>每當建立新的程式基底時，都要加入新的「<code class="language-plaintext highlighter-rouge">license</code>」授權條款檔案。</li>
+  <li>每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。</li>
+  <li>每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼促進會所發表的《<a href="https://opensource.org/osd">開放原始碼定義</a>》，所有開放原始碼授權條款皆符合這套定義。</li>
+  <li>紐西蘭CC Aotearoa《<a href="https://creativecommons.org/about/videos/creative-commons-kiwi">創用CC介紹動畫影
+片</a>》。</li>
+  <li>歐洲自由軟體基金會所發表的《<a href="https://reuse.software/spec/">REUSE 倡議規範</a>》，提供規範明確、人類可讀以及機器可讀的著作權與
+授權資訊。</li>
+  <li>Linux 基金會所發表的 <a href="https://spdx.org/licenses/">SPDX 授權條款清單</a>，提供經標準化、且機器可讀的大多數授權條款縮寫表示
+法。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/require-review-of-contributions.html b/_site/criteria/require-review-of-contributions.html
new file mode 100644
index 00000000..d95b2ffd
--- /dev/null
+++ b/_site/criteria/require-review-of-contributions.html
@@ -0,0 +1,506 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>要求審查貢獻內容, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/require-review-of-contributions.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/maintain-version-control.html"
+		     >&#8592; 維護版本控制</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/document-codebase-objectives.html"
+		     >程式基底要有目標文件 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/require-review-of-contributions.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/require-review-of-contributions.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="要求審查貢獻內容">要求審查貢獻內容</h1>
+
+<p>同儕審查貢獻是<a href="/glossary.html#source-code">原始碼</a>提升品質的關鍵，也能降低安全性風險與營運風險。</p>
+
+<p>要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入<a href="/glossary.html#codebase">程式基底</a>之前，
+就發現與修正潛在臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。</p>
+
+<p>快速審查<a href="/glossary.html#policy">政策</a>在於向貢獻者保證，必定在一段時間內提供意見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參
+與的熱度。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>所有被接受或是送交給程式基底正式發行版本中的貢獻內容，都「必須」經過另一位貢獻者審查。</li>
+  <li>審查「必須」包含原始碼、政策、測試、文件等。</li>
+  <li>如果不接受貢獻內容，審查人員「必須」提供意見回饋。</li>
+  <li>審查流程「應該」確認貢獻內容遵循程式基底的標準、架構、決策安排等，以通過審查。</li>
+  <li>審查內容「應該」包含執行軟體與執行程式基底測試。</li>
+  <li>貢獻內容「應該」由與貢獻者不同背景情境的人來審查。</li>
+  <li>版本控制系統「不應該」在程式基底的正式發行版本中，接受未經審查的貢獻內容。</li>
+  <li>審查「應該」在兩個工作天內進行。</li>
+  <li>「可選擇」是否由多位審查人員進行審查。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。</li>
+  <li>確認審查內容包含原始碼、政策、測試、文件等。</li>
+  <li>針對未被採用的貢獻內容，確認有適當解釋原因。</li>
+  <li>檢查審查人員指引中，有包含是否遵循標準、架構、程式基底指引等指示。</li>
+  <li>檢查審查人員在審查時是否有執行軟體與測試。</li>
+  <li>與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。</li>
+  <li>檢查<a href="/glossary.html#version-control">版本控制</a>系統中是否有採用分支保護。</li>
+  <li>檢查貢獻提交與審查之間的時間間隔。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。</li>
+  <li>採用具有審查與意見回饋功能的版本控制系統，或作業流程。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將交付妥善軟體作為共同目標。</li>
+  <li>確保如原始碼、政策、文件、測試等的貢獻內容撰寫與審查，皆受到同等重視。</li>
+  <li>創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。</li>
+  <li>確保貢獻者在貢獻內容給程式基底時，不是獨自一人埋頭苦幹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>請程式基底的其他貢獻者，審查您在貴組織單位內外的工作成果。</li>
+  <li>當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content">英國政府數位服務團程式碼審查程
+序</a>》。</li>
+  <li><a href="https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches">GitHub</a>
+與
+<a href="https://about.gitlab.com/blog/2014/11/26/keeping-your-code-protected/">GitLab</a> 平
+臺的分支保護說明。</li>
+  <li>Sage Sharp《<a href="https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/">程式修補審查的和善藝
+術</a>》。</li>
+  <li>Mozilla《<a href="https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177">參與度評測成
+果</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/require-review.html b/_site/criteria/require-review.html
new file mode 100644
index 00000000..76cde276
--- /dev/null
+++ b/_site/criteria/require-review.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/require-review-of-contributions.html">
+  <script>location="/criteria/require-review-of-contributions.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/require-review-of-contributions.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/require-review-of-contributions.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/reusable-and-portable-codebases.html b/_site/criteria/reusable-and-portable-codebases.html
new file mode 100644
index 00000000..3220819c
--- /dev/null
+++ b/_site/criteria/reusable-and-portable-codebases.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/make-the-codebase-reusable-and-portable.html">
+  <script>location="/criteria/make-the-codebase-reusable-and-portable.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/make-the-codebase-reusable-and-portable.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/make-the-codebase-reusable-and-portable.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/style.html b/_site/criteria/style.html
new file mode 100644
index 00000000..c2e6dc13
--- /dev/null
+++ b/_site/criteria/style.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/use-a-coherent-style.html">
+  <script>location="/criteria/use-a-coherent-style.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/use-a-coherent-style.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/use-a-coherent-style.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/understandable-english-first.html b/_site/criteria/understandable-english-first.html
new file mode 100644
index 00000000..b3d31cef
--- /dev/null
+++ b/_site/criteria/understandable-english-first.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/use-plain-english.html">
+  <script>location="/criteria/use-plain-english.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/use-plain-english.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/use-plain-english.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/use-a-coherent-style.html b/_site/criteria/use-a-coherent-style.html
new file mode 100644
index 00000000..371e6a56
--- /dev/null
+++ b/_site/criteria/use-a-coherent-style.html
@@ -0,0 +1,485 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>風格要前後一致, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/use-a-coherent-style.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/make-the-codebase-findable.html"
+		     >&#8592; 程式基底可查詢得到</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/document-codebase-maturity.html"
+		     >記錄程式基底成熟度 &#8594;</a></span>
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/use-a-coherent-style.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/use-a-coherent-style.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="風格要前後一致">風格要前後一致</h1>
+
+<p>採用前後一致的風格，讓不同環境的貢獻者能夠一同合作。用詞統一能減少貢獻者之間在溝通上的摩擦。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">程式基底</a>「必須」遵守程式碼撰寫風格指引、或文件寫作風格指引，可以是程式基底社群自身的風格指引，或是程式基底
+有採用的既有風格。</li>
+  <li>貢獻內容「應該」通過自動化的風格測試。</li>
+  <li>風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與為其寫下說明文件的期待。</li>
+  <li>「可選擇」是否將<a href="/criteria/use-plain-english.html">可理解的白話英語</a>期望加入風格指引之中。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認貢獻內容有遵循文件中指定的風格指引。</li>
+  <li>檢查是否有自動化的風格測試。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為<a href="/glossary.html#policy">政策</a>與文件建立風格指引，遵守並且持續改善，同時記錄到程式基底文件中，像是「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或
+「<code class="language-plaintext highlighter-rouge">README</code>」檔案。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>如果程式基底還沒有工程指引，或其他貢獻者指引，則請先在<a href="/glossary.html#repository">儲存庫</a>中加入相關文件，像是
+「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「<code class="language-plaintext highlighter-rouge">README</code>」檔案，並描述目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
+的其他層面。指引應該包含貢獻的<a href="/glossary.html#source-code">原始碼</a>預期該符合哪些要求，才會被維護人員合併至程式基底中，包括原始碼、測
+試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。</p>
+
+<p>此外：</p>
+
+<ul>
+  <li>使用 linter 程式碼品質梳理工具。</li>
+  <li>在程式基底中加入 linter 梳理工具的組態設定。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>維基百科上的《<a href="https://en.wikipedia.org/wiki/Programming_style">程式碼風格</a>》條目。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/use-continuous-integration.html b/_site/criteria/use-continuous-integration.html
new file mode 100644
index 00000000..1a59591e
--- /dev/null
+++ b/_site/criteria/use-continuous-integration.html
@@ -0,0 +1,508 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>使用持續整合, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/use-continuous-integration.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/use-open-standards.html"
+		     >&#8592; 採用開放標準</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/publish-with-an-open-license.html"
+		     >發行採用開放授權 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/use-continuous-integration.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/use-continuous-integration.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="使用持續整合">使用持續整合</h1>
+
+<p>透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同步協作。合併的頻率越頻繁、貢獻的規模越小，在合併時所發生的衝突就越容易解決。</p>
+
+<p>自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。</p>
+
+<p>以文件記錄程式基底的<a href="/glossary.html#continuous-integration">持續整合</a>工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓
+監管<a href="/glossary.html#codebase">程式基底</a>狀態變得更為簡單。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li><a href="/glossary.html#source-code">原始碼</a>中的所有功能，都「必須」有自動化測試。</li>
+  <li>所有貢獻內容都「必須」先通過自動化測試，才能上傳至程式基底。</li>
+  <li>程式基底「必須」有解說如何撰寫貢獻內容結構的相關指引。</li>
+  <li>程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。</li>
+  <li>「應該」公開貢獻內容的自動化測試結果。</li>
+  <li>程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。</li>
+  <li>「應該」監管原始碼測試與文件的涵蓋範圍。</li>
+  <li>「可選擇」是否測試<a href="/glossary.html#policy">政策</a>和文件，與原始碼之間有無一致性，或是反之亦然。</li>
+  <li>「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。</li>
+  <li>「可選擇」是否使用文件中的範例來測試軟體。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有測試可用。</li>
+  <li>確認原始碼覆蓋率工具能檢查到 100% 的原始碼。</li>
+  <li>確認貢獻內容只有在通過所有測試後，才會認可上傳至程式基底。</li>
+  <li>確認有貢獻指引解說如何撰寫貢獻內容的結構。</li>
+  <li>確認最近三個月內有貢獻內容上傳。</li>
+  <li>檢查是否可以查看測試結果。</li>
+  <li>檢查是否有公布原始碼覆蓋率數據。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。</li>
+  <li>確保政策文件也有設好自動化測試。</li>
+  <li>如果政策文件未能通過測試，請快速修正。</li>
+  <li>確保原始碼能反映出政策的任何變動（請參閱〈<a href="/criteria/maintain-version-control.html">維護版本控制</a>〉）。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保能儘快且經常給真正的終端使用者進行測試。</li>
+  <li>以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。</li>
+  <li>聘請有能力處理漸進式交付，並跟得上規劃進度的顧問服務。</li>
+  <li>發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>協助管理人員擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。</li>
+  <li>協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。</li>
+  <li>協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。</li>
+  <li>編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體分配失敗等資源耗盡情況，都是難以創造的典型案例。</li>
+  <li>調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。</li>
+  <li>經常部署。</li>
+  <li>至少每天整合工作內容一次。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Martin Fowler《<a href="https://www.martinfowler.com/articles/continuousIntegration.html">什麼是持續整
+合</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/standards/continuous-delivery.html">使用持續交
+付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly">品質保證：定期測試您的服
+務</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/use-open-standards.html b/_site/criteria/use-open-standards.html
new file mode 100644
index 00000000..306397cb
--- /dev/null
+++ b/_site/criteria/use-open-standards.html
@@ -0,0 +1,485 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>採用開放標準, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/use-open-standards.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/use-plain-english.html"
+		     >&#8592; 使用白話的英語</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/use-continuous-integration.html"
+		     >使用持續整合 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/use-open-standards.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/use-open-standards.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="採用開放標準">採用開放標準</h1>
+
+<p><a href="/glossary.html#open-standard">開放標準</a>保證可以取得使用與貢獻<a href="/glossary.html#codebase">程式基底</a>所需的知
+識。不僅能為不同的系統之間建立互通性，更能降低廠商套牢的可能性。開放標準如果明確，不同方就可以各自獨立開發作資料交換。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底如要促進資料交換的特性，就「必須」採用符合 <a href="https://opensource.org/osr">OSI 開放原始碼促進會其《開放標準需求規範</a>》的
+開放標準。</li>
+  <li>如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。</li>
+  <li>程式基底選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標準的連結。</li>
+  <li>程式基底選擇採用的任何非開放標準，皆「禁止」妨礙程式基底的協作與重複使用。</li>
+  <li>如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。</li>
+  <li>採用開放標準時，「應該」優先選擇可經機器測試的開放標準。</li>
+  <li>採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。</li>
+  <li>確認若有採用任何的非開放標準，皆有清楚記錄在文件中。</li>
+  <li>確認文件有清單列出程式基底所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>以政策要求盡可能在任何情況下採用開放標準。</li>
+  <li>禁止採購不採用開放標準的技術科技。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>考慮在<a href="/glossary.html#source-code">原始碼</a>審查中納入開放標準依循評估。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將是否依循標準加入<a href="/glossary.html#continuous-integration">持續整合</a>測試中。</li>
+  <li>審查送交版次與<a href="/glossary.html#repository">儲存庫</a>其他資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國內閣辦公室發表的《<a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">開放標準原
+則</a>》
+<a href="/glossary.html#policy">政策</a>報告。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/use-plain-english.html b/_site/criteria/use-plain-english.html
new file mode 100644
index 00000000..974187db
--- /dev/null
+++ b/_site/criteria/use-plain-english.html
@@ -0,0 +1,498 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>使用白話的英語, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/use-plain-english.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/document-the-code.html"
+		     >&#8592; 程式碼要有文件</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/use-open-standards.html"
+		     >採用開放標準 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/use-plain-english.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/use-plain-english.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="使用白話的英語">使用白話的英語</h1>
+
+<p>英語是軟體開發領域中的<i>實際</i> 協作語言。</p>
+
+<p>公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解<a href="/glossary.html#code">程式碼</a>與其功用。</p>
+
+<p>翻譯可以讓更多人有機會認識<a href="/glossary.html#codebase">程式基底</a>。用語越是簡單明暸，製作與維護翻譯的成本就越低。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底的所有文件都「必須」使用英語。</li>
+  <li>所有<a href="/glossary.html#source-code">原始碼</a>都「必須」使用英語編寫，其中<a href="/glossary.html#policy">政策</a>是由機器
+解讀當作程式碼的部分則除外。</li>
+  <li>任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。</li>
+  <li>任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。</li>
+  <li>程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。</li>
+  <li>根據《<a href="https://www.w3.org/WAI/WCAG21/quickref/?
+showtechniques=315#readable">網頁內容近用性無障礙指引 2</a>》的建議，文件內容「應該」以國中識讀程度為主。</li>
+  <li>「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底文件有英語版本。</li>
+  <li>確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。</li>
+  <li>確認任何非英語政策都有隨附英語版摘要。</li>
+  <li>確認翻譯版與英語版內容相同。</li>
+  <li>確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。</li>
+  <li>檢查文件的拼字、文法與易讀性等。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在
+使用這些詞彙的地方加上詞彙表連結。</li>
+  <li>以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+  <li>詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>符合 W3C 全球資訊網協會《<a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容近用性無障礙指引 2.1、3.1 之可讀
+性</a>》要求，撰寫的文字內容要容易閱讀與理解。</li>
+  <li>歐盟委員會的《<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟無障礙環境命
+令</a>》，是高度要求無障礙環境
+的法規範例。</li>
+  <li>美國總務署《<a href="https://www.plainlanguage.gov/about/definitions/">白話語言定義</a>》。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/criteria/version-control-and-history.html b/_site/criteria/version-control-and-history.html
new file mode 100644
index 00000000..ae7034c1
--- /dev/null
+++ b/_site/criteria/version-control-and-history.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/criteria/maintain-version-control.html">
+  <script>location="/criteria/maintain-version-control.html"</script>
+  <meta http-equiv="refresh" content="0; url=/criteria/maintain-version-control.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/criteria/maintain-version-control.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/criteria/welcome-contributors.html b/_site/criteria/welcome-contributors.html
new file mode 100644
index 00000000..770b71f9
--- /dev/null
+++ b/_site/criteria/welcome-contributors.html
@@ -0,0 +1,500 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>歡迎貢獻者, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/criteria/welcome-contributors.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+      <span id="span-prev-next" class="theme-prev-next">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span id="span-prev" class="theme-prev-next-prev"><a
+		     href="/criteria/make-the-codebase-reusable-and-portable.html"
+		     >&#8592; 程式基底要可重複使用且可移植</a></span>
+
+
+
+
+
+
+
+
+<span id="span-next" class="theme-prev-next-next"><a
+		     href="/criteria/make-contributing-easy.html"
+		     >貢獻要容易 &#8594;</a></span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><!-- span-prev-next -->
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#延伸閱讀">延伸閱讀</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/criteria/welcome-contributors.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `criteria/welcome-contributors.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="歡迎貢獻者">歡迎貢獻者</h1>
+
+<p><a href="/glossary.html#codebase">程式基底</a>社群的氛圍，會影響使用者選擇所要使用的程式基底。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我
+運作。若貢獻者有明確的方法可以影響程式基底、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並信任程式基底社群的治理方式。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底必須「允許」任何人對程式基底提出修改建議。</li>
+  <li>程式基底「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發，例如以「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」檔案說明。</li>
+  <li>程式基底「必須」以文件記錄程式基底、貢獻內容與社群互動等的治理方式，例如以「<code class="language-plaintext highlighter-rouge">GOVERNANCE</code>」檔案來說明。</li>
+  <li>貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。</li>
+  <li>程式基底「應該」宣布投入其開發與維護工作的參與組織單位。</li>
+  <li>程式基底「應該」要有可公開取得的發展路線圖。</li>
+  <li>程式基底「應該」公布程式基底的活動統計數據。</li>
+  <li>「可選擇」是否為程式基底加入貢獻者的行為守則。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認可以提交修改建議給程式基底。</li>
+  <li>確認程式基底有貢獻指引。</li>
+  <li>確認程式基底有清楚解釋治理架構，並包含如何影響程式基底治理的方法。</li>
+  <li>確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。</li>
+  <li>檢查是否有參與的組織單位名單。</li>
+  <li>檢查是否有發展路線圖。</li>
+  <li>檢查是否有公布活動統計數據。</li>
+  <li>檢查是否有行為守則。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為程式基底加入其他資源的清單，而這些資源可幫助<a href="/glossary.html#policy">政策</a>專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。</li>
+  <li>考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。</li>
+  <li>如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。</li>
+  <li>若有需要，確認您有編列貢獻內容審查流程的預算，且經過程式基底社群同意。</li>
+  <li>確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參與的時間長度等。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>告知管理人員，您在支援其他貢獻者時所需的時間與資源。</li>
+  <li>清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到程式基底中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼指引所提供的《<a href="https://opensource.guide/building-community/">營造友善的社群</a>》。</li>
+  <li>Mike McQuaid《<a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/">開放原始碼貢獻者瓶
+頸</a>》。</li>
+  <li>開放原始碼指引針對推動<a href="/glossary.html#open-source">開放原始碼</a>社群專案所寫的《<a href="https://opensource.guide/leadership-and-governance/">領導與治
+理</a>》。</li>
+  <li>Pieter Hintjens《<a href="http://hintjens.com/blog:117">打造網路社群</a>》(長篇文章！)。</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docker.sh b/_site/docker.sh
new file mode 100644
index 00000000..b5f3ab98
--- /dev/null
+++ b/_site/docker.sh
@@ -0,0 +1,9 @@
+#!/bin/bash
+
+path=`pwd`
+docker run -d \
+    -v ${path}:/var/www/html \
+    -v ${path}/docker/apache-data:/etc/apache2/sites-available \
+    -p 8090:80 \
+    --name=standard \
+    steps/standard
diff --git a/_site/docker/apache-data/000-default.conf b/_site/docker/apache-data/000-default.conf
new file mode 100644
index 00000000..72b4196e
--- /dev/null
+++ b/_site/docker/apache-data/000-default.conf
@@ -0,0 +1,34 @@
+<VirtualHost *:80>
+	# The ServerName directive sets the request scheme, hostname and port that
+	# the server uses to identify itself. This is used when creating
+	# redirection URLs. In the context of virtual hosts, the ServerName
+	# specifies what hostname must appear in the request's Host: header to
+	# match this virtual host. For the default virtual host (this file) this
+	# value is not decisive as it is used as a last resort host regardless.
+	# However, you must set it for any further virtual host explicitly.
+	#ServerName www.example.com
+
+	ServerAdmin webmaster@localhost
+	DocumentRoot /var/www/html/_site
+    <Directory /var/www/html/_site>
+        AllowOverride All
+    </Directory>
+
+	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
+	# error, crit, alert, emerg.
+	# It is also possible to configure the loglevel for particular
+	# modules, e.g.
+	#LogLevel info ssl:warn
+
+	ErrorLog ${APACHE_LOG_DIR}/error.log
+	CustomLog ${APACHE_LOG_DIR}/access.log combined
+
+	# For most configuration files from conf-available/, which are
+	# enabled or disabled at a global level, it is possible to
+	# include a line for only one particular virtual host. For example the
+	# following line enables the CGI configuration for this host only
+	# after it has been globally disabled with "a2disconf".
+	#Include conf-available/serve-cgi-bin.conf
+</VirtualHost>
+
+# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
diff --git a/_site/docs/checklist.html b/_site/docs/checklist.html
new file mode 100644
index 00000000..5bc1b865
--- /dev/null
+++ b/_site/docs/checklist.html
@@ -0,0 +1,230 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2023 by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<head>
+<meta charset="UTF-8">
+<title>Standard for Public Code Checklist</title>
+<style>
+html, body {
+font-family: Mulish;
+font-size: 8.5pt;
+}
+h1, h2 {
+font-weight: normal;
+position: relative;
+}
+h1 {
+margin-top: 0;
+font-size: 0.5cm;
+border-bottom: none;
+}
+h2 {
+font-size: 1.0em;
+}
+ul {
+list-style-type: "\2610";
+}
+@media print {
+  @page {
+    size: 14.8cm 21.0cm;
+    margin: 0.5cm 0.2cm;
+  }
+}
+</style>
+</head>
+<body>
+<h1>Standard for Public Code version <span class="standard-version">0.7.1</span> checklist</h1>
+
+<h2>&#9744; Code in the open</h2>
+
+<ul id="code-in-the-open">
+<li>All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible. </li>
+<li>All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible. </li>
+<li>The codebase MUST NOT contain sensitive information regarding users, their organization or third parties. </li>
+<li>Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published. </li>
+<li>Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Bundle policy and source code</h2>
+
+<ul id="bundle-policy-and-source-code">
+<li>The codebase MUST include the policy that the source code is based on. </li>
+<li>If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection. </li>
+<li>Policy SHOULD be provided in machine readable and unambiguous formats. </li>
+<li>Continuous integration tests SHOULD validate that the source code and the policy are executed coherently. </li>
+</ul>
+
+<h2>&#9744; Make the codebase reusable and portable</h2>
+
+<ul id="make-the-codebase-reusable-and-portable">
+<li>The codebase MUST be developed to be reusable in different contexts. </li>
+<li>The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding. </li>
+<li>The codebase SHOULD be in use by multiple parties. </li>
+<li>The roadmap SHOULD be influenced by the needs of multiple parties. </li>
+<li>The development of the codebase SHOULD be a collaboration between multiple parties. </li>
+<li>Configuration SHOULD be used to make source code adapt to context specific needs. </li>
+<li>The codebase SHOULD be localizable. </li>
+<li>Source code and its documentation SHOULD NOT contain situation-specific information. </li>
+<li>Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts. </li>
+<li>The software SHOULD NOT require services or platforms available from only a single vendor. </li>
+</ul>
+
+<h2>&#9744; Welcome contributors</h2>
+
+<ul id="welcome-contributors">
+<li>The codebase MUST allow anyone to submit suggestions for changes to the codebase. </li>
+<li>The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file. </li>
+<li>The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file. </li>
+<li>The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions. </li>
+<li>The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance. </li>
+<li>The codebase SHOULD have a publicly available roadmap. </li>
+<li>The codebase SHOULD publish codebase activity statistics. </li>
+<li>Including a code of conduct for contributors in the codebase is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Make contributing easy</h2>
+
+<ul id="make-contributing-easy">
+<li>The codebase MUST have a public issue tracker that accepts suggestions from anyone. </li>
+<li>The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file. </li>
+<li>The codebase MUST have communication channels for users and developers, for example email lists. </li>
+<li>There MUST be a way to report security issues for responsible disclosure over a closed channel. </li>
+<li>The documentation MUST include instructions for how to report potentially security sensitive issues. </li>
+</ul>
+
+<h2>&#9744; Maintain version control</h2>
+
+<ul id="maintain-version-control">
+<li>All files in the codebase MUST be version controlled. </li>
+<li>All decisions MUST be documented in commit messages. </li>
+<li>Every commit message MUST link to discussions and issues wherever possible. </li>
+<li>The codebase SHOULD be maintained in a distributed version control system. </li>
+<li>Contribution guidelines SHOULD require contributors to group relevant changes in commits. </li>
+<li>Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels. </li>
+<li>Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system. </li>
+<li>It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work. </li>
+</ul>
+
+<h2>&#9744; Require review of contributions</h2>
+
+<ul id="require-review-of-contributions">
+<li>All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor. </li>
+<li>Reviews MUST include source, policy, tests and documentation. </li>
+<li>Reviewers MUST provide feedback on all decisions to not accept a contribution. </li>
+<li>The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review. </li>
+<li>Reviews SHOULD include running both the software and the tests of the codebase. </li>
+<li>Contributions SHOULD be reviewed by someone in a different context than the contributor. </li>
+<li>Version control systems SHOULD NOT accept non-reviewed contributions in release versions. </li>
+<li>Reviews SHOULD happen within two business days. </li>
+<li>Performing reviews by multiple reviewers is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Document codebase objectives</h2>
+
+<ul id="document-codebase-objectives">
+<li>The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase. </li>
+<li>Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives. </li>
+<li>Documenting the objectives of the codebase for the general public is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Document the code</h2>
+
+<ul id="document-the-code">
+<li>All of the functionality of the codebase, policy as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase. </li>
+<li>The documentation of the codebase MUST contain a description of how to install and run the software. </li>
+<li>The documentation of the codebase MUST contain examples demonstrating the key functionality. </li>
+<li>The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists. </li>
+<li>The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset. </li>
+<li>The documentation of the codebase SHOULD contain examples for all functionality. </li>
+<li>The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram. </li>
+<li>There SHOULD be continuous integration tests for the quality of the documentation. </li>
+<li>Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Use plain English</h2>
+
+<ul id="use-plain-english">
+<li>All codebase documentation MUST be in English. </li>
+<li>All source code MUST be in English, except where policy is machine interpreted as code. </li>
+<li>All bundled policy not available in English MUST have an accompanying summary in English. </li>
+<li>Any translation MUST be up to date with the English version and vice versa. </li>
+<li>There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation. </li>
+<li>Documentation SHOULD aim for a lower secondary education reading level, as recommended by the Web Content Accessibility Guidelines 2. </li>
+<li>Providing a translation of any code, documentation or tests is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Use open standards</h2>
+
+<ul id="use-open-standards">
+<li>For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the Open Source Initiative Open Standard Requirements. </li>
+<li>Any non-open standards used MUST be recorded clearly as such in the documentation. </li>
+<li>Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available. </li>
+<li>Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse. </li>
+<li>If no existing open standard is available, effort SHOULD be put into developing one. </li>
+<li>Open standards that are machine testable SHOULD be preferred over open standards that are not. </li>
+<li>Non-open standards that are machine testable SHOULD be preferred over non-open standards that are not. </li>
+</ul>
+
+<h2>&#9744; Use continuous integration</h2>
+
+<ul id="use-continuous-integration">
+<li>All functionality in the source code MUST have automated tests. </li>
+<li>Contributions MUST pass all automated tests before they are admitted into the codebase. </li>
+<li>The codebase MUST have guidelines explaining how to structure contributions. </li>
+<li>The codebase MUST have active contributors who can review contributions. </li>
+<li>Automated test results for contributions SHOULD be public. </li>
+<li>The codebase guidelines SHOULD state that each contribution should focus on a single issue. </li>
+<li>Source code test and documentation coverage SHOULD be monitored. </li>
+<li>Testing policy and documentation for consistency with the source and vice versa is OPTIONAL. </li>
+<li>Testing policy and documentation for style and broken links is OPTIONAL. </li>
+<li>Testing the software by using examples in the documentation is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Publish with an open license</h2>
+
+<ul id="publish-with-an-open-license">
+<li>All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable. </li>
+<li>Software source code MUST be licensed under an OSI-approved or FSF Free/Libre license. </li>
+<li>All source code MUST be published with a license file. </li>
+<li>Contributors MUST NOT be required to transfer copyright of their contributions to the codebase. </li>
+<li>All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable. </li>
+<li>Having multiple licenses for different types of source code and documentation is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Make the codebase findable</h2>
+
+<ul id="make-the-codebase-findable">
+<li>The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding. </li>
+<li>The codebase SHOULD have a short description that helps someone understand what the codebase is for or what it does. </li>
+<li>Maintainers SHOULD submit the codebase to relevant software catalogs. </li>
+<li>The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers). </li>
+<li>The codebase SHOULD be findable using a search engine by codebase name. </li>
+<li>The codebase SHOULD be findable using a search engine by describing the problem it solves in natural language. </li>
+<li>The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website. </li>
+<li>The codebase SHOULD include a machine-readable metadata description, for example in a publiccode.yml file. </li>
+<li>A dedicated domain name for the codebase is OPTIONAL. </li>
+<li>Regular presentations at conferences by the community are OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Use a coherent style</h2>
+
+<ul id="use-a-coherent-style">
+<li>The codebase MUST use a coding or writing style guide, either the codebase community's own or an existing one referred to in the codebase. </li>
+<li>Contributions SHOULD pass automated tests on style. </li>
+<li>The style guide SHOULD include expectations for inline comments and documentation for non-trivial sections. </li>
+<li>Including expectations for understandable English in the style guide is OPTIONAL. </li>
+</ul>
+
+<h2>&#9744; Document codebase maturity</h2>
+
+<ul id="document-codebase-maturity">
+<li>The codebase MUST be versioned. </li>
+<li>The codebase MUST prominently document whether or not there are versions of the codebase that are ready to use. </li>
+<li>Codebase versions that are ready to use MUST only depend on versions of other codebases that are also ready to use. </li>
+<li>The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`. </li>
+<li>The method for assigning version identifiers SHOULD be documented. </li>
+<li>It is OPTIONAL to use semantic versioning. </li>
+</ul>
+</body>
+</html>
diff --git a/_site/docs/printing.html b/_site/docs/printing.html
new file mode 100644
index 00000000..9333f311
--- /dev/null
+++ b/_site/docs/printing.html
@@ -0,0 +1,261 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>印刷, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/printing.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/docs/printing.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `docs/printing.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="印刷">印刷</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>《公共程式標準》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。</p>
+
+<p>印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）：</p>
+
+<ul>
+  <li>樣式：平裝書 (<a href="https://www.reclameland.nl/drukken/softcover-boeken">Reclameland 產品頁面</a>)</li>
+  <li>紙張尺寸：A4</li>
+  <li>直向或橫向：直向 (Staand)</li>
+  <li>內頁印刷：正四反四 4/4，雙面全色印刷</li>
+  <li>內頁材質：Biotop 90克</li>
+  <li>封面：350 克封面</li>
+  <li>封面印刷：正四反空 4/0，單面滿版印刷</li>
+  <li>封面處理：單面霧面層剝處理 (Enke)</li>
+  <li>頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數</li>
+  <li>個別封裝：無</li>
+</ul>
+
+<p>一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/printing.md b/_site/docs/printing.md
new file mode 100644
index 00000000..abb13962
--- /dev/null
+++ b/_site/docs/printing.md
@@ -0,0 +1,21 @@
+# 印刷
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+《公共程式標準》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，方便您到 Reclameland 或其他地方印刷。
+
+印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）：
+
+* 樣式：平裝書 ([Reclameland 產品頁面](https://www.reclameland.nl/drukken/softcover-boeken))
+* 紙張尺寸：A4
+* 直向或橫向：直向 (Staand)
+* 內頁印刷：正四反四 4/4，雙面全色印刷
+* 內頁材質：Biotop 90克
+* 封面：350 克封面
+* 封面印刷：正四反空 4/0，單面滿版印刷
+* 封面處理：單面霧面層剝處理 (Enke)
+* 頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數
+* 個別封裝：無
+
+一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。
diff --git a/_site/docs/releasing.html b/_site/docs/releasing.html
new file mode 100644
index 00000000..1c4a1227
--- /dev/null
+++ b/_site/docs/releasing.html
@@ -0,0 +1,310 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>發行新版本的《公共程式標準》, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/releasing.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/docs/releasing.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `docs/releasing.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="發行新版本的公共程式標準">發行新版本的《公共程式標準》</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<ol>
+  <li>審查「develop」分支的狀態
+    <ul>
+      <li>確認預計收入該次發行版的所有變更都已完成合併</li>
+      <li>邀請校對該分支目前的狀態
+        <ul>
+          <li>如果有引入新的破折號，檢查是否能簡化文字並且移除破折號，例如改用較簡易的句子。如果需要用到複雜的句子，檢查是否能用其他標點符號來取代破折號。如果破折號最適合用來
+表達該句子的涵義，則請遵守《<a href="https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash">芝加哥格式手
+冊</a>》的規範。</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>建立發行用分支
+    <ul>
+      <li>從「develop」分支下命令，<code class="language-plaintext highlighter-rouge">git switch -c "release-$MAJOR.$MINOR.$PATCH"</code></li>
+      <li>推送分支，<code class="language-plaintext highlighter-rouge">git push -u origin release-$MAJOR.$MINOR.$PATCH</code></li>
+    </ul>
+  </li>
+  <li>更新本次新發行
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />在 <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS.md</code></a> 中加入新貢獻者的資料</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />更新 <a href="/CHANGELOG.html"><code class="language-plaintext highlighter-rouge">CHANGELOG.md</code></a></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />更新 <a href="/docs/roadmap.html"><code class="language-plaintext highlighter-rouge">roadmap.md</code></a></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />透過 diff 進行額外傳輸到「main」分支
+        <ul>
+          <li>執行 <code class="language-plaintext highlighter-rouge">script/generate-review-template.sh</code> 並送交更新後的 <code class="language-plaintext highlighter-rouge">docs/review-template.html</code> 版次記
+錄</li>
+          <li>使用審查範本中的新文字來更新 <code class="language-plaintext highlighter-rouge">docs/standard-for-public-code.html</code>，會將任何狀態變更作為結果更新</li>
+          <li>重新檢查用字有變更的任何小節或段落，確保變更的字詞適合該整體內容，並且沒有文法或拼字錯誤</li>
+          <li>確認有安裝<a href="https://brand.publiccode.net/typography/">字型</a>，請參見：<code class="language-plaintext highlighter-rouge">script/ensure-font.sh</code></li>
+          <li>使用 <code class="language-plaintext highlighter-rouge">script/pdf.sh rc1</code> 檢查轉譯出的 <code class="language-plaintext highlighter-rouge">.pdf</code> 檔
+            <ul>
+              <li>確認沒有連結相衝的問題</li>
+              <li>檢查文字分頁之處，可能需要移除或新增 CSS 分頁語法，像是：<code class="language-plaintext highlighter-rouge">&lt;p style="page-break-after: always;"&gt;&lt;/p&gt;</code></li>
+            </ul>
+          </li>
+          <li>如果有需要，送交修正版次，並重複進行額外傳輸</li>
+        </ul>
+      </li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />推送分支，與「main」分支比較，範例：
+<code class="language-plaintext highlighter-rouge">https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH</code>
+        <ul>
+          <li>請多位審查人員（特別是校對人員）進行審查</li>
+          <li>審查人員若發現不會阻礙發行的缺失，則會建立議題</li>
+          <li>如果是發行所需處理的缺失，審查人員可以提交拉取請求來解決問題</li>
+          <li>若有額外的拉取請求合併至發行分支，則再次請求審查</li>
+        </ul>
+      </li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />執行 to-archive-org.sh 命令稿</li>
+    </ul>
+  </li>
+  <li>在 GItHub 上發行，附上發行備註與版本編號
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git tag trigger-$MAJOR.$MINOR.$PATCH</code></li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" /><code class="language-plaintext highlighter-rouge">git push --tags</code>（請參見：<code class="language-plaintext highlighter-rouge">../.github/workflows/release-on-tag.yml</code>）</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />移除本地端的 tag 標記：<code class="language-plaintext highlighter-rouge">git tag -d trigger-$MAJOR.$MINOR.$PATCH</code></li>
+    </ul>
+  </li>
+  <li><a href="/docs/printing.html">將檔案傳送給印刷廠商印刷</a>
+    <ul class="task-list">
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />封面檔案</li>
+      <li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />內頁 PDF</li>
+    </ul>
+  </li>
+  <li>通知<a href="https://github.com/publiccodenet/community-translations-standard">翻譯</a>貢獻者</li>
+</ol>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/releasing.md b/_site/docs/releasing.md
new file mode 100644
index 00000000..0ab61c4e
--- /dev/null
+++ b/_site/docs/releasing.md
@@ -0,0 +1,48 @@
+# 發行新版本的《公共程式標準》
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+1. 審查「develop」分支的狀態
+   - 確認預計收入該次發行版的所有變更都已完成合併
+   - 邀請校對該分支目前的狀態
+      - 如果有引入新的破折號，檢查是否能簡化文字並且移除破折號，例如改用較簡易的句子。如果需要用到複雜的句子，檢查是否能用其他標點符號來取代破折號。如果破折號最適合用來
+表達該句子的涵義，則請遵守《[芝加哥格式手
+冊](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)》的規範。
+
+1. 建立發行用分支
+   - 從「develop」分支下命令，`git switch -c "release-$MAJOR.$MINOR.$PATCH"`
+   - 推送分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`
+
+1. 更新本次新發行
+   - [ ] 在 [`AUTHORS.md`](../AUTHORS.md) 中加入新貢獻者的資料
+   - [ ] 更新 [`CHANGELOG.md`](../CHANGELOG.md)
+   - [ ] 更新 [`roadmap.md`](roadmap.md)
+   - [ ] 透過 diff 進行額外傳輸到「main」分支
+      - 執行 `script/generate-review-template.sh` 並送交更新後的 `docs/review-template.html` 版次記
+錄
+      - 使用審查範本中的新文字來更新 `docs/standard-for-public-code.html`，會將任何狀態變更作為結果更新
+      - 重新檢查用字有變更的任何小節或段落，確保變更的字詞適合該整體內容，並且沒有文法或拼字錯誤
+      - 確認有安裝[字型](https://brand.publiccode.net/typography/)，請參見：`script/ensure-font.sh`
+      - 使用 `script/pdf.sh rc1` 檢查轉譯出的 `.pdf` 檔
+         - 確認沒有連結相衝的問題
+         - 檢查文字分頁之處，可能需要移除或新增 CSS 分頁語法，像是：`<p style="page-break-after: always;"></p>`
+      - 如果有需要，送交修正版次，並重複進行額外傳輸
+   - [ ] 推送分支，與「main」分支比較，範例：
+`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`
+      - 請多位審查人員（特別是校對人員）進行審查
+      - 審查人員若發現不會阻礙發行的缺失，則會建立議題
+      - 如果是發行所需處理的缺失，審查人員可以提交拉取請求來解決問題
+      - 若有額外的拉取請求合併至發行分支，則再次請求審查
+   - [ ] 執行 to-archive-org.sh 命令稿
+
+1. 在 GItHub 上發行，附上發行備註與版本編號
+   - [ ] `git tag trigger-$MAJOR.$MINOR.$PATCH`
+   - [ ] `git push --tags`（請參見：`../.github/workflows/release-on-tag.yml`）
+   - [ ] 移除本地端的 tag 標記：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`
+
+1. [將檔案傳送給印刷廠商印刷](printing.md)
+   - [ ] 封面檔案
+   - [ ] 內頁 PDF
+
+1. 通知[翻譯](https://github.com/publiccodenet/community-translations-standard)貢獻者
diff --git a/_site/docs/review-template.html b/_site/docs/review-template.html
new file mode 100644
index 00000000..7818ee68
--- /dev/null
+++ b/_site/docs/review-template.html
@@ -0,0 +1,1512 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-2023 by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<head>
+<meta charset="UTF-8">
+<title>________ and the Standard for Public Code</title>
+<style>
+html, body {
+font-family: Mulish;
+font-size: 11pt;
+}
+h1, h2 {
+font-weight: normal;
+position: relative;
+}
+h1 {
+margin-top: 0;
+font-size: 1.5cm;
+border-bottom: none;
+}
+h2 {
+font-size: 1.5em;
+}
+@media print {
+a {
+color: #111;
+text-decoration: none;
+}
+th {
+font-weight: 600;
+}
+td {
+padding: 6px 13px;
+border: 1px solid #dfe2e5;
+}
+tr {
+background-color: #fff;
+border-top: 1px solid #c6cbd1;
+}
+tr:nth-child(2n) {
+background-color: #f6f8fa;
+}
+}
+</style>
+</head>
+<body>
+<h1>________ and the Standard for Public Code version <span class="standard-version">0.7.1</span></h1>
+
+Link to commitment to meet the Standard for Public Code:
+
+<h2><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="code-in-the-open" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST NOT contain sensitive information regarding users, their organization or third parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/bundle-policy-and-source-code.html">Bundle policy and source code</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="bundle-policy-and-source-code" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST include the policy that the source code is based on.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Policy SHOULD be provided in machine readable and unambiguous formats.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/make-the-codebase-reusable-and-portable.html">Make the codebase reusable and portable</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="make-the-codebase-reusable-and-portable" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST be developed to be reusable in different contexts.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD be in use by multiple parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The roadmap SHOULD be influenced by the needs of multiple parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The development of the codebase SHOULD be a collaboration between multiple parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Configuration SHOULD be used to make source code adapt to context specific needs.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD be localizable.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Source code and its documentation SHOULD NOT contain situation-specific information.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The software SHOULD NOT require services or platforms available from only a single vendor.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/welcome-contributors.html">Welcome contributors</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="welcome-contributors" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST allow anyone to submit suggestions for changes to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD have a publicly available roadmap.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD publish codebase activity statistics.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Including a code of conduct for contributors in the codebase is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="make-contributing-easy" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST have a public issue tracker that accepts suggestions from anyone.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST have communication channels for users and developers, for example email lists.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+There MUST be a way to report security issues for responsible disclosure over a closed channel.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation MUST include instructions for how to report potentially security sensitive issues.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/maintain-version-control.html">Maintain version control</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="maintain-version-control" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All files in the codebase MUST be version controlled.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All decisions MUST be documented in commit messages.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Every commit message MUST link to discussions and issues wherever possible.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD be maintained in a distributed version control system.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contribution guidelines SHOULD require contributors to group relevant changes in commits.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/require-review-of-contributions.html">Require review of contributions</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="require-review-of-contributions" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Reviews MUST include source, policy, tests and documentation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Reviewers MUST provide feedback on all decisions to not accept a contribution.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Reviews SHOULD include running both the software and the tests of the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contributions SHOULD be reviewed by someone in a different context than the contributor.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Version control systems SHOULD NOT accept non-reviewed contributions in release versions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Reviews SHOULD happen within two business days.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Performing reviews by multiple reviewers is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-codebase-objectives.html">Document codebase objectives</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="document-codebase-objectives" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Documenting the objectives of the codebase for the general public is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-the-code.html">Document the code</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="document-the-code" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All of the functionality of the codebase, policy as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation of the codebase MUST contain a description of how to install and run the software.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation of the codebase MUST contain examples demonstrating the key functionality.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation of the codebase SHOULD contain examples for all functionality.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+There SHOULD be continuous integration tests for the quality of the documentation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-plain-english.html">Use plain English</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="use-plain-english" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All codebase documentation MUST be in English.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All source code MUST be in English, except where policy is machine interpreted as code.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All bundled policy not available in English MUST have an accompanying summary in English.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Any translation MUST be up to date with the English version and vice versa.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Providing a translation of any code, documentation or tests is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-open-standards.html">Use open standards</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="use-open-standards" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Any non-open standards used MUST be recorded clearly as such in the documentation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+If no existing open standard is available, effort SHOULD be put into developing one.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Open standards that are machine testable SHOULD be preferred over open standards that are not.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Non-open standards that are machine testable SHOULD be preferred over non-open standards that are not.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-continuous-integration.html">Use continuous integration</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="use-continuous-integration" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All functionality in the source code MUST have automated tests.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contributions MUST pass all automated tests before they are admitted into the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST have guidelines explaining how to structure contributions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST have active contributors who can review contributions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Automated test results for contributions SHOULD be public.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase guidelines SHOULD state that each contribution should focus on a single issue.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Source code test and documentation coverage SHOULD be monitored.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Testing policy and documentation for consistency with the source and vice versa is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Testing policy and documentation for style and broken links is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Testing the software by using examples in the documentation is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/publish-with-an-open-license.html">Publish with an open license</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="publish-with-an-open-license" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All source code MUST be published with a license file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Having multiple licenses for different types of source code and documentation is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/make-the-codebase-findable.html">Make the codebase findable</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="make-the-codebase-findable" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD have a short description that helps someone understand what the codebase is for or what it does.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Maintainers SHOULD submit the codebase to relevant software catalogs.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD be findable using a search engine by codebase name.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD be findable using a search engine by describing the problem it solves in natural language.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+A dedicated domain name for the codebase is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Regular presentations at conferences by the community are OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-a-coherent-style.html">Use a coherent style</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="use-a-coherent-style" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST use a coding or writing style guide, either the codebase community's own or an existing one referred to in the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Contributions SHOULD pass automated tests on style.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The style guide SHOULD include expectations for inline comments and documentation for non-trivial sections.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Including expectations for <a href="https://standard.publiccode.net/criteria/use-plain-english.html">understandable English</a> in the style guide is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-codebase-maturity.html">Document codebase maturity</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="document-codebase-maturity" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST be versioned.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase MUST prominently document whether or not there are versions of the codebase that are ready to use.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Codebase versions that are ready to use MUST only depend on versions of other codebases that are also ready to use.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The method for assigning version identifiers SHOULD be documented.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+It is OPTIONAL to use semantic versioning.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+</body>
+</html>
diff --git a/_site/docs/roadmap.html b/_site/docs/roadmap.html
new file mode 100644
index 00000000..34d6f4cb
--- /dev/null
+++ b/_site/docs/roadmap.html
@@ -0,0 +1,281 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>發展路線圖, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/docs/roadmap.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#目前任務">目前任務</a></li>
+  <li><a href="#近期">近期</a></li>
+  <li><a href="#長期">長期</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/docs/roadmap.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `docs/roadmap.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="發展路線圖">發展路線圖</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>上次更新時間：2023-03-08</p>
+
+<p>本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。</p>
+
+<p>程式基底執事人員每月會定期審查發展路線圖，這是我們<a href="https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html">積累事項修整作業</a>
+環節的一部份。</p>
+
+<h2 id="目前任務">目前任務</h2>
+
+<ul>
+  <li>盡可能讓標準遵循自我標準</li>
+  <li>認證標章</li>
+</ul>
+
+<h2 id="近期">近期</h2>
+
+<ul>
+  <li>分離執行摘要 (issue #302)</li>
+  <li>實體紙張檢查清單</li>
+  <li>可能性：為每個準則新增解說插圖</li>
+</ul>
+
+<h2 id="長期">長期</h2>
+
+<ul>
+  <li>為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）</li>
+  <li>通過多個程式基底驗證</li>
+  <li>在幾個程式基底遵循標準後，發行 1.0.0 版</li>
+  <li>可連結的需求規範</li>
+  <li>新封面設計</li>
+  <li>註冊申請 ISBN 書號</li>
+  <li>隨選書籍列印服務名單</li>
+  <li>印刷版外部連結的 QR 二維圖碼</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/docs/roadmap.md b/_site/docs/roadmap.md
new file mode 100644
index 00000000..55f132de
--- /dev/null
+++ b/_site/docs/roadmap.md
@@ -0,0 +1,33 @@
+# 發展路線圖
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+上次更新時間：2023-03-08
+
+本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。
+
+程式基底執事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://about.publiccode.net/activities/standard-maintenance/backlog-pruning.html)
+環節的一部份。
+
+## 目前任務
+
+* 盡可能讓標準遵循自我標準
+* 認證標章
+
+## 近期
+
+* 分離執行摘要 (issue #302)
+* 實體紙張檢查清單
+* 可能性：為每個準則新增解說插圖
+
+## 長期
+
+* 為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）
+* 通過多個程式基底驗證
+* 在幾個程式基底遵循標準後，發行 1.0.0 版
+* 可連結的需求規範
+* 新封面設計
+* 註冊申請 ISBN 書號
+* 隨選書籍列印服務名單
+* 印刷版外部連結的 QR 二維圖碼
diff --git a/_site/docs/standard-for-public-code.html b/_site/docs/standard-for-public-code.html
new file mode 100644
index 00000000..5e68f7b0
--- /dev/null
+++ b/_site/docs/standard-for-public-code.html
@@ -0,0 +1,1514 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-2023 by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<head>
+<meta charset="UTF-8">
+<title>The Standard for Public Code's compliance to the criteria and requirements of the Standard for Public Code version 0.7.1</title>
+<style>
+html, body {
+font-family: Mulish;
+font-size: 11pt;
+}
+h1, h2 {
+font-weight: normal;
+position: relative;
+}
+h1 {
+margin-top: 0;
+font-size: 1.5cm;
+border-bottom: none;
+}
+h2 {
+font-size: 1.5em;
+}
+@media print {
+a {
+color: #111;
+text-decoration: none;
+}
+th {
+font-weight: 600;
+}
+td {
+padding: 6px 13px;
+border: 1px solid #dfe2e5;
+}
+tr {
+background-color: #fff;
+border-top: 1px solid #c6cbd1;
+}
+tr:nth-child(2n) {
+background-color: #f6f8fa;
+}
+}
+</style>
+</head>
+<body>
+<h1>The Standard for Public Code's compliance to the criteria and requirements of the Standard for Public Code version 0.7.1</h1>
+
+The Standard for Public Code is not a codebase created in the context of a policy mandate, thus some criteria do not apply directly.
+
+Link to commitment to meet the Standard for Public Code: [CONTRIBUTING.md](../CONTRIBUTING.md#1-make-your-changes)
+
+<h2><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="code-in-the-open" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+N/A
+</td>
+<td>
+All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/">GitHub repository, no official policy at this time</a>
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/">GitHub repository, not software</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST NOT contain sensitive information regarding users, their organization or third parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/releases">GitHub releases</a>
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/bundle-policy-and-source-code.html">Bundle policy and source code</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="bundle-policy-and-source-code" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+N/A
+</td>
+<td>
+The codebase MUST include the policy that the source code is based on.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Policy SHOULD be provided in machine readable and unambiguous formats.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/create-reusable-and-portable-code.html">Create reusable and portable code</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="create-reusable-and-portable-code" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST be developed to be reusable in different contexts.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD be in use by multiple parties.
+</td>
+<td>
+<a href="https://github.com/Amsterdam/signals/blob/master/docs/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship">Signalen</a>, <a href="https://github.com/open-zaak/open-zaak/blob/main/CONTRIBUTING.md#under-foundation-for-public-code-incubating-codebase-stewardship">OpenZaak</a>, <a href="https://github.com/Algoritmeregister/standard#standard-for-public-code-compliance">Algoritmeregister</a>, <a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#1-make-your-changes">Standard for Public Code</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The roadmap SHOULD be influenced by the needs of multiple parties.
+</td>
+<td>
+Community calls influenced initial roadmap
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+The development of the codebase SHOULD be a collaboration between multiple parties.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Configuration SHOULD be used to make source code adapt to context specific needs.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD be localizable.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Source code and its documentation SHOULD NOT contain situation-specific information.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The software SHOULD NOT require services or platforms available from only a single vendor.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/welcome-contributors.html">Welcome contributors</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="welcome-contributors" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST allow anyone to submit suggestions for changes to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md">CONTRIBUTING</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/GOVERNANCE.md">GOVERNANCE</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.
+</td>
+<td>
+In <a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md">CONTRIBUTING</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD have a publicly available roadmap.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/docs/roadmap.md">Roadmap</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD publish codebase activity statistics.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/pulse">GitHub Pulse</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Including a code of conduct for contributors in the codebase is OPTIONAL.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/CODE_OF_CONDUCT.md">CODE OF CONDUCT</a>
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="make-contributing-easy" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST have a public issue tracker that accepts suggestions from anyone.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/issues">GitHub Issues</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file.
+</td>
+<td>
+Via GitHub
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST have communication channels for users and developers, for example email lists.
+</td>
+<td>
+<a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">Mailing list</a>
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+There MUST be a way to report security issues for responsible disclosure over a closed channel.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation MUST include instructions for how to report potentially security sensitive issues.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/maintain-version-control.html">Maintain version control</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="maintain-version-control" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All files in the codebase MUST be version controlled.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+All decisions MUST be documented in commit messages.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Every commit message MUST link to discussions and issues wherever possible.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD be maintained in a distributed version control system.
+</td>
+<td>
+git
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contribution guidelines SHOULD require contributors to group relevant changes in commits.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.
+</td>
+<td>
+GitHub releases
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/require-review-of-contributions.html">Require review of contributions</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="require-review-of-contributions" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Reviews MUST include source, policy, tests and documentation.
+</td>
+<td>
+policy does not apply
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Reviewers MUST provide feedback on all decisions to not accept a contribution.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Reviews SHOULD include running both the software and the tests of the codebase.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/actions">GitHub Actions</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contributions SHOULD be reviewed by someone in a different context than the contributor.
+</td>
+<td>
+Usually in the same context, rarely get reviews from other contexts, currently no other contexts regularly available
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Version control systems SHOULD NOT accept non-reviewed contributions in release versions.
+</td>
+<td>
+the `main` branch is "protected"
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Reviews SHOULD happen within two business days.
+</td>
+<td>
+very few exceptions
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Performing reviews by multiple reviewers is OPTIONAL.
+</td>
+<td>
+for larger contributions
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-codebase-objectives.html">Document codebase objectives</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="document-codebase-objectives" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Documenting the objectives of the codebase for the general public is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-the-code.html">Document the code</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="document-the-code" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All of the functionality of the codebase, policy as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation of the codebase MUST contain a description of how to install and run the software.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation of the codebase MUST contain examples demonstrating the key functionality.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation of the codebase SHOULD contain examples for all functionality.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+There SHOULD be continuous integration tests for the quality of the documentation.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/actions">GitHub Actions</a>
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.
+</td>
+<td>
+We're not linking to examples
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-plain-english.html">Use plain English</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="use-plain-english" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All codebase documentation MUST be in English.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+All source code MUST be in English, except where policy is machine interpreted as code.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+All bundled policy not available in English MUST have an accompanying summary in English.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Any translation MUST be up to date with the English version and vice versa.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+</td>
+<td>
+Providing a translation of any code, documentation or tests is OPTIONAL.
+</td>
+<td>
+We have <a href="https://publiccodenet.github.io/community-translations-standard/">Community translations</a>
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-open-standards.html">Use open standards</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="use-open-standards" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+N/A
+</td>
+<td>
+For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Any non-open standards used MUST be recorded clearly as such in the documentation.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/CONTRIBUTING.md#standards-to-follow">CONTRIBUTING</a>
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+If no existing open standard is available, effort SHOULD be put into developing one.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Open standards that are machine testable SHOULD be preferred over open standards that are not.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Non-open standards that are machine testable SHOULD be preferred over non-open standards that are not.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-continuous-integration.html">Use continuous integration</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="use-continuous-integration" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All functionality in the source code MUST have automated tests.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contributions MUST pass all automated tests before they are admitted into the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST have guidelines explaining how to structure contributions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST have active contributors who can review contributions.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Automated test results for contributions SHOULD be public.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase guidelines SHOULD state that each contribution should focus on a single issue.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Source code test and documentation coverage SHOULD be monitored.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Testing policy and documentation for consistency with the source and vice versa is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Testing policy and documentation for style and broken links is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+Testing the software by using examples in the documentation is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/publish-with-an-open-license.html">Publish with an open license</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="publish-with-an-open-license" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/LICENSE">CC 0</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Software source code MUST be licensed under an <a href="https://spdx.org/licenses/">OSI-approved or FSF Free/Libre license</a>.
+</td>
+<td>
+CC 0
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+All source code MUST be published with a license file.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contributors MUST NOT be required to transfer copyright of their contributions to the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+All source code files in the codebase SHOULD include a copyright notice and a license header that are machine-readable.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Having multiple licenses for different types of source code and documentation is OPTIONAL.
+</td>
+<td>
+CC 0
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/make-the-codebase-findable.html">Make the codebase findable</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="make-the-codebase-findable" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The name of the codebase SHOULD be descriptive and free from acronyms, abbreviations, puns or organizational branding.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD have a short description that helps someone understand what the codebase is for or what it does.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Maintainers SHOULD submit the codebase to relevant software catalogs.
+</td>
+<td>
+In the <a href="https://digitalpublicgoods.net/registry/standard-for-public-code.html">DPG registry</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD have a website which describes the problem the codebase solves using the preferred jargon of different potential users of the codebase (including technologists, policy experts and managers).
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD be findable using a search engine by codebase name.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD be findable using a search engine by describing the problem it solves in natural language.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD have a unique and persistent identifier where the entry mentions the major contributors, repository location and website.
+</td>
+<td>
+<a href="https://www.wikidata.org/wiki/Q68006929">Q68006929</a> on Wikidata
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD include a machine-readable metadata description, for example in a <a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a> file.
+</td>
+<td>
+<a href="../publiccode.yml">publiccode.yml</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+A dedicated domain name for the codebase is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Regular presentations at conferences by the community are OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/use-a-coherent-style.html">Use a coherent style</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="use-a-coherent-style" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST use a coding or writing style guide, either the codebase community's own or an existing one referred to in the codebase.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Contributions SHOULD pass automated tests on style.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+N/A
+</td>
+<td>
+The style guide SHOULD include expectations for inline comments and documentation for non-trivial sections.
+</td>
+<td>
+maybe some of the Jekyll could apply
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Including expectations for <a href="https://standard.publiccode.net/criteria/use-plain-english.html">understandable English</a> in the style guide is OPTIONAL.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+
+<h2><a href="https://standard.publiccode.net/criteria/document-codebase-maturity.html">Document codebase maturity</a></h2>
+
+&#9745;<!-- &#9745; --> criterion met.
+
+<table id="document-codebase-maturity" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST be versioned.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase MUST prominently document whether or not there are versions of the codebase that are ready to use.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+Codebase versions that are ready to use MUST only depend on versions of other codebases that are also ready to use.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The codebase SHOULD contain a log of changes from version to version, for example in the `CHANGELOG`.
+</td>
+<td>
+<a href="https://github.com/publiccodenet/standard/blob/develop/CHANGELOG.md">CHANGELOG</a>
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+The method for assigning version identifiers SHOULD be documented.
+</td>
+<td>
+
+</td>
+</tr>
+
+<tr>
+<td>
+Ok
+</td>
+<td>
+It is OPTIONAL to use semantic versioning.
+</td>
+<td>
+
+</td>
+</tr>
+
+</table>
+</body>
+</html>
diff --git a/_site/foreword-print.html b/_site/foreword-print.html
new file mode 100644
index 00000000..2f2c00c9
--- /dev/null
+++ b/_site/foreword-print.html
@@ -0,0 +1,215 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <link rel="stylesheet" href="assets/github-markdown.css">
+  <link rel="stylesheet" href="assets/print.css">
+  <title>Standard for Public Code</title>
+  <style>
+  /* Print specific */
+
+    @media print {
+      @page :left {
+        @top-left {
+          content: counter(page, lower-roman);
+        }
+      }
+      @page :right {
+        @top-right {
+          content: counter(page, lower-roman);
+        }
+      }
+    }
+
+  </style>
+</head>
+<body class="markdown-body">
+
+  <article id="section-foreword">
+
+    <h1 id="序文">序文</h1>
+
+<p>《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。</p>
+
+<p>任何想開發具有公眾用途的軟體或政策的人，可以利用本標準來提升公共服務品質，使其更具成本效益、風險更低，還能對系統更有掌控權。</p>
+
+<p>本序文在介紹何謂「公共程式」以及解說其重要性。</p>
+
+<h2 id="公共程式定義">公共程式定義</h2>
+
+<p>公共程式，英文為 Public Code，是指人類或機器在公共情境下，所執行的電腦原始碼（像是軟體與演算法）與公共政策。公共程式的範疇，涵蓋搭配公共基礎建設一同作業
+的軟體、作為公共基礎建設運作而建置的軟體，以及產生公共程式的過程安排等。公共程式與一般軟體有明顯區別，因為其作業的環境與期待全然不同。</p>
+
+<h2 id="採用公共程式的原因">採用公共程式的原因</h2>
+
+<p>公共程式現在如此重要，背後有幾個原因。</p>
+
+<h3 id="軟體程式碼--法律條文">軟體程式碼 == 法律條文</h3>
+
+<p>軟體是公共基礎建設。</p>
+
+<p>在 21 世紀，軟體可被視為重要的公共基礎建設。軟體越來越常被用於實現既有政策，甚至成為新政策的制定來源。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力
+等。</p>
+
+<p>在公共政策的執行上，軟體運作機制、演算法與資料蒐集等，已成為關鍵要素。今日的電腦程式碼，正執行著透過民主程序制定的法規政策。程式碼與政策這兩種形式的程式，都根據民主
+程序而確立的公共價值，設立出社會的運作環境；前者由機器執行，後者則是由人類執行。換句話說，軟體程式碼，已經越來越實質趨近於法律條文的地位。</p>
+
+<p>因此軟體也應該接受民主治理原則的約束。</p>
+
+<h3 id="傳統的公共軟體採購">傳統的公共軟體採購</h3>
+
+<p>目前公共軟體的生產模式，在交付公共服務上的效率並不高。</p>
+
+<p>過去近十年來，購置完整軟體解決方案的公家機關，有時甚至會很訝異地發現：</p>
+
+<ul>
+  <li>他們無法修改軟體來反映政策的變動，或是改變軟體來利用新科技</li>
+  <li>他們的資料都套牢在專有系統中，無法取用</li>
+  <li>他們所需繳交的授權費變得越來越貴</li>
+</ul>
+
+<h3 id="技術自主權與民主課責">技術自主權與民主課責</h3>
+
+<p>公家機關、公務員與居民都值得更好的。</p>
+
+<p>我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有程式基底之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主權。技術自
+主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。</p>
+
+<p>作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。</p>
+
+<h3 id="設計真正的公共軟體">設計真正的公共軟體</h3>
+
+<p>公共程式是現代公家機構的核心，型塑了公務員的工作樣態，並且影響了幾乎所有居民的生活。</p>
+
+<p>因此公共軟體必須：</p>
+
+<ul>
+  <li>透明</li>
+  <li>可課責</li>
+  <li>讓選民能夠理解</li>
+</ul>
+
+<p>必須能反映其所服務的社會價值觀，像是涵容與不歧視。</p>
+
+<p>目前公家機關使用的大多數專有軟體系統，都不符合這些要求；而公共程式能夠做到。</p>
+
+<h3 id="公共程式的價值">公共程式的價值</h3>
+
+<p>我們認為公共程式應具有下列核心價值：</p>
+
+<ul>
+  <li>涵容</li>
+  <li>好用</li>
+  <li>開放</li>
+  <li>易懂</li>
+  <li>課責</li>
+  <li>近用</li>
+  <li>永續</li>
+</ul>
+
+<h2 id="公共程式運作方式">公共程式運作方式</h2>
+
+<p>公共程式是旨在協助公家機關，履行其必要職責時所採用的開放原始碼軟體。透過使用，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成果。</p>
+
+<p>開放的精神能開創許多可能性。</p>
+
+<p>公家機關在執行與維護其自身的公共程式時，就是在確保能為地方負責，並履行民主課責。開放且貢獻者眾多的軟體，得利於有許多人在看，更容易發現潛在缺陷，因此安全性會更高。許
+多貢獻者會分攤維護工作，讓公共程式能持續運作與更新，減少未來技術債的可能。因為能有多人分攤維護工作，使得現在與未來都會更加永續。而公共程式的開放性，代表其程式碼與
+資料，在未來也更容易改寫與調整。程式碼也更容易重新利用、重新調整目標，或甚至淘汰。這一切特性都讓公共基礎建設可能遭遇的風險降到更低。</p>
+
+<p>這種將資源集中的作法，能讓公共行政單位可以有額外心力關注如何客製化軟體，來使軟體最適合當地情境的需求，為終端使用者（居民或市民）創造更佳的使用體驗。</p>
+
+<h3 id="公共程式的經濟效應">公共程式的經濟效應</h3>
+
+<p>公共程式為公家機關以及商業公司，提供更好的經濟模型。公共程式作為替代傳統軟體採購的方案，更能提升當地的掌控權並促進經濟機會。</p>
+
+<p>公共程式從設計之初，就是要開放、適應力強、資料可攜，能夠由內部員工或信任的供應商來開發。由於原始碼開放，公共行政單位在有需要時可以更換供應商。開放原始碼讓社會大眾更
+有機會瞭解與監督公共程式，使公共行政單位得以採購小規模的合約，而地方性的中小企業就更容易參與這些小型採購案的競標。如此一來，公共行政單位就可以透過他們所需的軟體採
+購案，刺激當地經濟的創新與競爭。</p>
+
+<p>這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。</p>
+
+<h3 id="購置公共程式">購置公共程式</h3>
+
+<p>公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在投標時可以在標案中納入公共程式。</p>
+
+<p>若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服
+務內容或預期成果。</p>
+
+<h2 id="公共程式標準目標">《公共程式標準》目標</h2>
+
+<p>本標準在於支持開發人員、設計師、管理人員、公共政策制定者：</p>
+
+<ul>
+  <li>開發出高品質的軟體與政策，來改善公共服務的交付</li>
+  <li>開發出能在各種情境下重複使用，且以協作方式維護的程式基底</li>
+  <li>減少技術債與專案失敗率</li>
+  <li>更能精細控制其 IT 系統粒度，並做出系統相關決策</li>
+  <li>以更好的經濟模型改善供應商關係</li>
+</ul>
+
+<p>如果有潛在使用者想採用經由《公共程式標準》測試過的程式基底，便可以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。</p>
+
+<p>《公共程式標準》能有此效果是基於：</p>
+
+<ul>
+  <li>為公共程式開發訂立通用術語</li>
+  <li>制定措施協助高品質公共程式的開發</li>
+  <li>提出該如何符合準則並實作遵循的指引</li>
+</ul>
+
+<p>《公共程式標準》設計精神就是要跨越時間與科技，不受其限制。</p>
+
+<h3 id="適用對象">適用對象</h3>
+
+<p>《公共程式標準》適用於開發與重複使用公共程式的人：</p>
+
+<ul>
+  <li>公共政策制定者</li>
+  <li>業務與專案經理</li>
+  <li>開發人員與設計師</li>
+</ul>
+
+<p>在以下單位服務的人：</p>
+
+<ul>
+  <li>社會機構、公家機關的組織與行政單位</li>
+  <li>公家機關在資訊科技與政策服務上的顧問與供應商</li>
+</ul>
+
+<p>適用對象不含公家機關的終端使用者（居民或市民）、記者或學者等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>歐洲自由軟體基金會所發表的<a href="https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf">《透過自由軟體實現公共基礎設施現代化》白皮
+書</a> 》。</li>
+</ul>
+
+<h3 id="探討公共程式的影片">探討公共程式的影片</h3>
+
+<ul>
+  <li><a href="https://www.youtube.com/watch?v=cnJtnZ9Cx1o">「程式協作是城市的未來」@ DecidimFest 2019</a>。主講
+人 Ben Cerveny，講述 Foundation for Public Code 的背景。</li>
+  <li><a href="https://youtube.com/watch?
+v=QHFkD4xfd6c"> 「用公共的納稅錢？做公共的程式吧！」專題討論 @ Nextcloud 大會 2019</a>。討論採購、法律等主題。</li>
+</ul>
+
+<h2 id="參與我們">參與我們</h2>
+
+<p>本標準是持續成長的文件。<a href="/CONTRIBUTING.html">請讀我們的〈貢獻者指引〉</a>，瞭解您可以怎麼做來讓本標準變得更好。</p>
+
+<h2 id="聯絡方式">聯絡方式</h2>
+
+<p>若有疑問，或想進一步瞭解 Foundation for Public Code，請造訪<a href="https://publiccode.net/">我們的網站</a>，或是寄電子郵
+件到 info@publiccode.net，或撥打我們的電話 +31 20 2 444 500。</p>
+
+
+  </article>
+
+</body>
+</html>
diff --git a/_site/foreword.html b/_site/foreword.html
new file mode 100644
index 00000000..21facae7
--- /dev/null
+++ b/_site/foreword.html
@@ -0,0 +1,443 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>序文, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/foreword.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#公共程式定義">公共程式定義</a></li>
+  <li><a href="#採用公共程式的原因">採用公共程式的原因</a>
+    <ol>
+      <li><a href="#軟體程式碼--法律條文">軟體程式碼 == 法律條文</a></li>
+      <li><a href="#傳統的公共軟體採購">傳統的公共軟體採購</a></li>
+      <li><a href="#技術自主權與民主課責">技術自主權與民主課責</a></li>
+      <li><a href="#設計真正的公共軟體">設計真正的公共軟體</a></li>
+      <li><a href="#公共程式的價值">公共程式的價值</a></li>
+    </ol>
+  </li>
+  <li><a href="#公共程式運作方式">公共程式運作方式</a>
+    <ol>
+      <li><a href="#公共程式的經濟效應">公共程式的經濟效應</a></li>
+      <li><a href="#購置公共程式">購置公共程式</a></li>
+    </ol>
+  </li>
+  <li><a href="#公共程式標準目標">《公共程式標準》目標</a>
+    <ol>
+      <li><a href="#適用對象">適用對象</a></li>
+    </ol>
+  </li>
+  <li><a href="#延伸閱讀">延伸閱讀</a>
+    <ol>
+      <li><a href="#探討公共程式的影片">探討公共程式的影片</a></li>
+    </ol>
+  </li>
+  <li><a href="#參與我們">參與我們</a></li>
+  <li><a href="#聯絡方式">聯絡方式</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/foreword.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `foreword.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="序文">序文</h1>
+
+<p>《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。</p>
+
+<p>任何想開發具有公眾用途的軟體或政策的人，可以利用本標準來提升公共服務品質，使其更具成本效益、風險更低，還能對系統更有掌控權。</p>
+
+<p>本序文在介紹何謂「公共程式」以及解說其重要性。</p>
+
+<h2 id="公共程式定義">公共程式定義</h2>
+
+<p>公共程式，英文為 Public Code，是指人類或機器在公共情境下，所執行的電腦原始碼（像是軟體與演算法）與公共政策。公共程式的範疇，涵蓋搭配公共基礎建設一同作業
+的軟體、作為公共基礎建設運作而建置的軟體，以及產生公共程式的過程安排等。公共程式與一般軟體有明顯區別，因為其作業的環境與期待全然不同。</p>
+
+<h2 id="採用公共程式的原因">採用公共程式的原因</h2>
+
+<p>公共程式現在如此重要，背後有幾個原因。</p>
+
+<h3 id="軟體程式碼--法律條文">軟體程式碼 == 法律條文</h3>
+
+<p>軟體是公共基礎建設。</p>
+
+<p>在 21 世紀，軟體可被視為重要的公共基礎建設。軟體越來越常被用於實現既有政策，甚至成為新政策的制定來源。舉例來說，演算法可以決定哪些地區需要額外的社會服務或警力
+等。</p>
+
+<p>在公共政策的執行上，軟體運作機制、演算法與資料蒐集等，已成為關鍵要素。今日的電腦程式碼，正執行著透過民主程序制定的法規政策。程式碼與政策這兩種形式的程式，都根據民主
+程序而確立的公共價值，設立出社會的運作環境；前者由機器執行，後者則是由人類執行。換句話說，軟體程式碼，已經越來越實質趨近於法律條文的地位。</p>
+
+<p>因此軟體也應該接受民主治理原則的約束。</p>
+
+<h3 id="傳統的公共軟體採購">傳統的公共軟體採購</h3>
+
+<p>目前公共軟體的生產模式，在交付公共服務上的效率並不高。</p>
+
+<p>過去近十年來，購置完整軟體解決方案的公家機關，有時甚至會很訝異地發現：</p>
+
+<ul>
+  <li>他們無法修改軟體來反映政策的變動，或是改變軟體來利用新科技</li>
+  <li>他們的資料都套牢在專有系統中，無法取用</li>
+  <li>他們所需繳交的授權費變得越來越貴</li>
+</ul>
+
+<h3 id="技術自主權與民主課責">技術自主權與民主課責</h3>
+
+<p>公家機關、公務員與居民都值得更好的。</p>
+
+<p>我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有程式基底之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自主權。技術自
+主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。</p>
+
+<p>作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。</p>
+
+<h3 id="設計真正的公共軟體">設計真正的公共軟體</h3>
+
+<p>公共程式是現代公家機構的核心，型塑了公務員的工作樣態，並且影響了幾乎所有居民的生活。</p>
+
+<p>因此公共軟體必須：</p>
+
+<ul>
+  <li>透明</li>
+  <li>可課責</li>
+  <li>讓選民能夠理解</li>
+</ul>
+
+<p>必須能反映其所服務的社會價值觀，像是涵容與不歧視。</p>
+
+<p>目前公家機關使用的大多數專有軟體系統，都不符合這些要求；而公共程式能夠做到。</p>
+
+<h3 id="公共程式的價值">公共程式的價值</h3>
+
+<p>我們認為公共程式應具有下列核心價值：</p>
+
+<ul>
+  <li>涵容</li>
+  <li>好用</li>
+  <li>開放</li>
+  <li>易懂</li>
+  <li>課責</li>
+  <li>近用</li>
+  <li>永續</li>
+</ul>
+
+<h2 id="公共程式運作方式">公共程式運作方式</h2>
+
+<p>公共程式是旨在協助公家機關，履行其必要職責時所採用的開放原始碼軟體。透過使用，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協作的成果。</p>
+
+<p>開放的精神能開創許多可能性。</p>
+
+<p>公家機關在執行與維護其自身的公共程式時，就是在確保能為地方負責，並履行民主課責。開放且貢獻者眾多的軟體，得利於有許多人在看，更容易發現潛在缺陷，因此安全性會更高。許
+多貢獻者會分攤維護工作，讓公共程式能持續運作與更新，減少未來技術債的可能。因為能有多人分攤維護工作，使得現在與未來都會更加永續。而公共程式的開放性，代表其程式碼與
+資料，在未來也更容易改寫與調整。程式碼也更容易重新利用、重新調整目標，或甚至淘汰。這一切特性都讓公共基礎建設可能遭遇的風險降到更低。</p>
+
+<p>這種將資源集中的作法，能讓公共行政單位可以有額外心力關注如何客製化軟體，來使軟體最適合當地情境的需求，為終端使用者（居民或市民）創造更佳的使用體驗。</p>
+
+<h3 id="公共程式的經濟效應">公共程式的經濟效應</h3>
+
+<p>公共程式為公家機關以及商業公司，提供更好的經濟模型。公共程式作為替代傳統軟體採購的方案，更能提升當地的掌控權並促進經濟機會。</p>
+
+<p>公共程式從設計之初，就是要開放、適應力強、資料可攜，能夠由內部員工或信任的供應商來開發。由於原始碼開放，公共行政單位在有需要時可以更換供應商。開放原始碼讓社會大眾更
+有機會瞭解與監督公共程式，使公共行政單位得以採購小規模的合約，而地方性的中小企業就更容易參與這些小型採購案的競標。如此一來，公共行政單位就可以透過他們所需的軟體採
+購案，刺激當地經濟的創新與競爭。</p>
+
+<p>這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。</p>
+
+<h3 id="購置公共程式">購置公共程式</h3>
+
+<p>公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在投標時可以在標案中納入公共程式。</p>
+
+<p>若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約中描述說明服
+務內容或預期成果。</p>
+
+<h2 id="公共程式標準目標">《公共程式標準》目標</h2>
+
+<p>本標準在於支持開發人員、設計師、管理人員、公共政策制定者：</p>
+
+<ul>
+  <li>開發出高品質的軟體與政策，來改善公共服務的交付</li>
+  <li>開發出能在各種情境下重複使用，且以協作方式維護的程式基底</li>
+  <li>減少技術債與專案失敗率</li>
+  <li>更能精細控制其 IT 系統粒度，並做出系統相關決策</li>
+  <li>以更好的經濟模型改善供應商關係</li>
+</ul>
+
+<p>如果有潛在使用者想採用經由《公共程式標準》測試過的程式基底，便可以預期這些程式基底具有方便重複利用、容易維護、高品質的特性。</p>
+
+<p>《公共程式標準》能有此效果是基於：</p>
+
+<ul>
+  <li>為公共程式開發訂立通用術語</li>
+  <li>制定措施協助高品質公共程式的開發</li>
+  <li>提出該如何符合準則並實作遵循的指引</li>
+</ul>
+
+<p>《公共程式標準》設計精神就是要跨越時間與科技，不受其限制。</p>
+
+<h3 id="適用對象">適用對象</h3>
+
+<p>《公共程式標準》適用於開發與重複使用公共程式的人：</p>
+
+<ul>
+  <li>公共政策制定者</li>
+  <li>業務與專案經理</li>
+  <li>開發人員與設計師</li>
+</ul>
+
+<p>在以下單位服務的人：</p>
+
+<ul>
+  <li>社會機構、公家機關的組織與行政單位</li>
+  <li>公家機關在資訊科技與政策服務上的顧問與供應商</li>
+</ul>
+
+<p>適用對象不含公家機關的終端使用者（居民或市民）、記者或學者等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>歐洲自由軟體基金會所發表的<a href="https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf">《透過自由軟體實現公共基礎設施現代化》白皮
+書</a> 》。</li>
+</ul>
+
+<h3 id="探討公共程式的影片">探討公共程式的影片</h3>
+
+<ul>
+  <li><a href="https://www.youtube.com/watch?v=cnJtnZ9Cx1o">「程式協作是城市的未來」@ DecidimFest 2019</a>。主講
+人 Ben Cerveny，講述 Foundation for Public Code 的背景。</li>
+  <li><a href="https://youtube.com/watch?
+v=QHFkD4xfd6c"> 「用公共的納稅錢？做公共的程式吧！」專題討論 @ Nextcloud 大會 2019</a>。討論採購、法律等主題。</li>
+</ul>
+
+<h2 id="參與我們">參與我們</h2>
+
+<p>本標準是持續成長的文件。<a href="/CONTRIBUTING.html">請讀我們的〈貢獻者指引〉</a>，瞭解您可以怎麼做來讓本標準變得更好。</p>
+
+<h2 id="聯絡方式">聯絡方式</h2>
+
+<p>若有疑問，或想進一步瞭解 Foundation for Public Code，請造訪<a href="https://publiccode.net/">我們的網站</a>，或是寄電子郵
+件到 info@publiccode.net，或撥打我們的電話 +31 20 2 444 500。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/glossary.html b/_site/glossary.html
new file mode 100644
index 00000000..1dd179a1
--- /dev/null
+++ b/_site/glossary.html
@@ -0,0 +1,327 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>詞彙表, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/glossary.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#程式或程式碼-code">程式或程式碼 (Code)</a></li>
+  <li><a href="#程式基底-codebase">程式基底 (Codebase)</a></li>
+  <li><a href="#持續整合">持續整合</a></li>
+  <li><a href="#不同情境">不同情境</a></li>
+  <li><a href="#一般大眾">一般大眾</a></li>
+  <li><a href="#開源或開放原始碼-open-source">開源或開放原始碼 (Open Source)</a></li>
+  <li><a href="#開放標準">開放標準</a></li>
+  <li><a href="#政策">政策</a></li>
+  <li><a href="#公共程式-public-code">公共程式 (Public Code)</a></li>
+  <li><a href="#儲存庫">儲存庫</a></li>
+  <li><a href="#原始碼-source-code">原始碼 (Source Code)</a></li>
+  <li><a href="#版本控制">版本控制</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/glossary.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `glossary.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="詞彙表">詞彙表</h1>
+
+<h2 id="程式或程式碼-code">程式或程式碼 (Code)</h2>
+
+<p>任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是由機器執
+行。</p>
+
+<h2 id="程式基底-codebase">程式基底 (Codebase)</h2>
+
+<p>任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、測試與文件等的整套內容。</p>
+
+<p>舉例而言，這個具體形式可以是文件，或是版本控制的儲存庫。</p>
+
+<h2 id="持續整合">持續整合</h2>
+
+<p>在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回程式基底開發中分支的實務作法。</p>
+
+<h2 id="不同情境">不同情境</h2>
+
+<p>只要是不同的公家機關或不同的部門，無法透過同一個決策單位讓協作自然發生，那就算是兩個不同的情境。</p>
+
+<h2 id="一般大眾">一般大眾</h2>
+
+<p>整體民眾：程式碼與其所建立的服務的終端使用者。</p>
+
+<p>舉例而言，城市的居民即視為該城市的服務、以及驅動這些服務運作的程式碼的終端使用者。</p>
+
+<h2 id="開源或開放原始碼-open-source">開源或開放原始碼 (Open Source)</h2>
+
+<p>所謂「開源」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《<a href="https://opensource.org/osd-annotated">開放原始碼定義</a>》而來。</p>
+
+<h2 id="開放標準">開放標準</h2>
+
+<p>任何符合 OSI 開放原始碼促進會《<a href="https://opensource.org/osr">開放標準需求規範</a>》的標準，就是開放標準。</p>
+
+<h2 id="政策">政策</h2>
+
+<p>政策是一套謹慎設計的原則體系，用來引導決策並達成合理的成果。政策是一種意圖的聲明，並以程序或協定來執行。政策通常是由組織單位內的理事機構採用執行。政策能協助做出主觀
+與客觀的決策。</p>
+
+<p>公共政策是政府將其政治願景，轉化成計畫與行動來取得成果的程序。</p>
+
+<p>在國家層級，政策與立法（法律）通常是分開的；而在地方政府中，這兩者之間的區別通常比較模糊。</p>
+
+<p>在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的政策。</p>
+
+<h2 id="公共程式-public-code">公共程式 (Public Code)</h2>
+
+<p>公共程式，是由公家機關所開發的開放原始碼軟體，同時包含協作與重複利用所需的政策與指引。</p>
+
+<p>公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以及公共政策兩者。</p>
+
+<p>服務公眾利益的公共程式，具有開放、易懂、課責、近用、永續等特性。</p>
+
+<p>透過獨立於當地情境，但仍可在當地情境下實作的方式，還有公開以文件記錄開發程序等作法，來開發公共程式。如此，公共程式能作為基礎組件提供給他人，使其得以：</p>
+
+<ul>
+  <li>根據其當地情境重新實作</li>
+  <li>作為起點並繼續開發</li>
+  <li>當作學習時的基礎</li>
+</ul>
+
+<p>為了促進重複利用，公共程式通常放到公眾領域發行，或者採取允許他人能自由檢視、重複利用其成果，甚至產出衍生作品的開放授權。</p>
+
+<h2 id="儲存庫">儲存庫</h2>
+
+<p>儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。</p>
+
+<h2 id="原始碼-source-code">原始碼 (Source Code)</h2>
+
+<p>人類可讀，並且能夠翻譯成機器指令的電腦程式文字。</p>
+
+<h2 id="版本控制">版本控制</h2>
+
+<p>版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「<em>修訂編號</em>」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作者，
+方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間經歷的變動。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/index.html b/_site/index.html
new file mode 100644
index 00000000..d1423ff9
--- /dev/null
+++ b/_site/index.html
@@ -0,0 +1,288 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>政府開放原始碼協作指引, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class=" ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title  home ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/index.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `index.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="政府開放原始碼協作指引">政府開放原始碼協作指引</h1>
+
+<p>《公共程式標準》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。</p>
+
+<p>《公共程式標準》為那些在建構自身開放原始碼解決方案的公家機關提供指引，以便他們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大到超國家組織都行。</p>
+
+<p>《公共程式標準》將「<a href="/glossary.html#public-code">公共程式</a>」定義為：由公家機關所開發的開放原始碼軟體，同時包含協作與重複使用所需的政策與指引。</p>
+
+<p>《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。</p>
+
+<p>其他情境與背景資訊請參閱<a href="/foreword.html">序文</a>。</p>
+
+<h2 id="目次">目次</h2>
+
+<ul>
+  <li><a href="/readers-guide.html">讀者指引：如何解讀本標準</a></li>
+  <li><a href="/glossary.html">詞彙表</a></li>
+  <li><a href="criteria/">準則</a>
+    <ul>
+      <li><a href="/criteria/code-in-the-open.html">原始碼要開放</a></li>
+      <li><a href="/criteria/bundle-policy-and-source-code.html">政策與原始碼要合捆</a></li>
+      <li><a href="/criteria/make-the-codebase-reusable-and-portable.html">程式基底要可重複使用且可移植</a></li>
+      <li><a href="/criteria/welcome-contributors.html">歡迎貢獻者</a></li>
+      <li><a href="/criteria/make-contributing-easy.html">貢獻要容易</a></li>
+      <li><a href="/criteria/maintain-version-control.html">維護版本控制</a></li>
+      <li><a href="/criteria/require-review-of-contributions.html">要求審查貢獻內容</a></li>
+      <li><a href="/criteria/document-codebase-objectives.html">程式基底要有目標文件</a></li>
+      <li><a href="/criteria/document-the-code.html">程式碼要有文件</a></li>
+      <li><a href="/criteria/use-plain-english.html">使用白話的英語</a></li>
+      <li><a href="/criteria/use-open-standards.html">採用開放標準</a></li>
+      <li><a href="/criteria/use-continuous-integration.html">使用持續整合</a></li>
+      <li><a href="/criteria/publish-with-an-open-license.html">發行採用開放授權</a></li>
+      <li><a href="/criteria/make-the-codebase-findable.html">程式基底可查詢得到</a></li>
+      <li><a href="/criteria/use-a-coherent-style.html">風格要前後一致</a></li>
+      <li><a href="/criteria/document-codebase-maturity.html">記錄程式基底成熟度</a></li>
+    </ul>
+  </li>
+  <li><a href="/AUTHORS.html">作者群</a></li>
+  <li><a href="/CONTRIBUTING.html">貢獻指引</a></li>
+  <li><a href="/CODE_OF_CONDUCT.html">行為守則</a></li>
+  <li><a href="/GOVERNANCE.html">治理方式</a></li>
+  <li><a href="/CHANGELOG.html">版本歷史</a></li>
+  <li><a href="license.html">授權</a></li>
+</ul>
+
+<h2 id="社群會議">社群會議</h2>
+
+<p>我們通常在每月第一個週四的 15:00 (CET/CEST) 舉辦社群會議。<a href="https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code">議程</a>在會議前
+約一週的時間更新。您可以<a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">註冊</a>
+報名，會再寄送會議通話邀請函給您。</p>
+
+<h2 id="其他資源">其他資源</h2>
+
+<ul>
+  <li>本標準非官方的其他語言<a href="https://publiccodenet.github.io/community-translations-standard/">社群翻譯</a></li>
+  <li>公部門開放原始碼程式基底的《<a href="https://publiccodenet.github.io/assessment-eligibility/">標準遵循自我評估</a>》</li>
+  <li>Foundation for Public Code 執事人員用於程式基底審查的《<a href="/docs/review-template.html">標準準則檢查清單</a>》</li>
+</ul>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/introduction.html b/_site/introduction.html
new file mode 100644
index 00000000..4ac2bfdb
--- /dev/null
+++ b/_site/introduction.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/foreword.html">
+  <script>location="/foreword.html"</script>
+  <meta http-equiv="refresh" content="0; url=/foreword.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/foreword.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/jargon.txt b/_site/jargon.txt
new file mode 100644
index 00000000..ad01f5e7
--- /dev/null
+++ b/_site/jargon.txt
@@ -0,0 +1,190 @@
+personal_ws-1.1 en 30 utf-8
+st
+nd
+rd
+th
+Ainali
+Algoritmeregister
+Aotearoa
+Arial
+Arnout
+AUAS
+authorsFile
+availableLanguages
+Barberi
+biotop
+bmpn
+BPMN
+bundler
+Camunda
+Cerveny
+CEST
+CET
+CHANGELOG
+changelog
+cibuild
+CMMN
+codebase
+codebase's
+codebases
+configurability
+cron
+dataset
+de
+DecidimFest
+Deerenberg
+deps
+der
+developmentStatus
+digitalminister
+dir
+discoverability
+discoverable
+disincentivizes
+DMN
+DPG
+Edo
+endfor
+endif
+Engelen
+english
+Enke
+epub
+Erkelens
+Faassen
+facto
+FileCopyrightText
+findability
+findable
+Findley
+Floris
+Fogel
+foliated
+fontconfig
+fontname
+GDS
+Gemeente
+Gemfile
+genericName
+gh
+GitFlow
+GitLab
+Groenen
+Hajduczenia
+Heikendorf
+Hendriks
+Hintjens
+hostnames
+Hoytema
+html
+HTTPS
+Huy
+IETF
+implementers
+inlining
+io
+jekyll
+Johan
+Kivimäki
+Klaas
+landingURL
+Lectorate
+libre
+linkable
+linter
+linters
+localisationReady
+localisedName
+localizable
+longDescription
+mainCopyrightOwner
+Marek
+MarkDown
+markdownify
+Markdownlint
+Martijn
+Matti
+Mauko
+Maurits
+McQuaid
+md
+Mirjam
+modularity
+Mullie
+Nextcloud
+Ngô
+Ngọc
+NIIS
+nl
+ok
+OpenApi
+OpenSSF
+OpenZaak
+operationalize
+OSI
+OSS
+pandoc
+pdf
+PDFs
+Petteri
+Pieter
+Plantinga
+proactiveness
+procurements
+provincie
+publiccode
+publiccodenet
+publiccodeYmlVersion
+QPDF
+Quiroga
+README
+Reclameland
+redistributable
+Regt
+releaseDate
+repoOwner
+repurpose
+reusability
+roadmap
+Roza
+ruleset
+runtime
+Sanderson
+Schee
+Schuijff
+shortDescription
+Signalen
+Slinger
+softwareType
+softwareVersion
+Spaan
+spdx
+Staand
+sudo
+svg
+synergize
+Tamas
+Theo
+Tiel
+Timo
+toc
+Trisotech
+Tsvg
+tw
+txt
+ubuntu
+ức
+Upgoer
+url
+URL
+URLs
+usedBy
+venv
+Vries
+Waal
+weasyprint
+whitepaper
+Wikidata
+yaml
+yml
+Zuid
diff --git a/_site/license.html b/_site/license.html
new file mode 100644
index 00000000..1a40f449
--- /dev/null
+++ b/_site/license.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="/CC0-1.0.html">
+  <script>location="/CC0-1.0.html"</script>
+  <meta http-equiv="refresh" content="0; url=/CC0-1.0.html">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="/CC0-1.0.html">Click here if you are not redirected.</a>
+</html>
diff --git a/_site/locales/en/LC_MESSAGES/messages.po b/_site/locales/en/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..9fad8d18
--- /dev/null
+++ b/_site/locales/en/LC_MESSAGES/messages.po
@@ -0,0 +1,5602 @@
+#
+msgid ""
+msgstr ""
+
+#: ./404.md:block 1 (header)
+msgid "SPDX-License-Identifier: CC0-1.0"
+msgstr ""
+
+#: ./404.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./404.md:block 3 (header)
+msgid ""
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
+msgstr ""
+
+#: ./404.md:block 4 (header)
+msgid "404 Not Found"
+msgstr ""
+
+#: ./404.md:block 5 (paragraph)
+msgid "If you typed the web address, check it is correct."
+msgstr ""
+
+#: ./404.md:block 6 (paragraph)
+msgid "If you pasted the web address, check you copied the entire address."
+msgstr ""
+
+#: ./404.md:block 7 (paragraph)
+msgid ""
+"If the web address is correct or you followed a link or button, email the "
+"[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
+"able to help you out, as well as correct our mistake."
+msgstr ""
+
+#: ./AUTHORS.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./AUTHORS.md:block 3 (header)
+msgid "Authors"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Engelen"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Schuijff, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ben Cerveny, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Bert Spaan"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Boris van Hoytema, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Charlotte Heikendorf"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Claus Mullie, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "David Barberi"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Edo Plantinga, [Code For NL](https://codefor.nl/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Elena Findley-de Regt, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Eric Herman, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Felix Faassen, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Floris Deerenberg"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Jan Ainali, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Johan Groenen, Code For NL"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Marcus Klaas de Vries"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Martijn de Waal, [Amsterdam University of Applied Sciences "
+"(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
+"Creative Industries, Lectorate of Play & Civic Media"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Matti Schneider"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mauko Quiroga"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurice Hendriks, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurits van der Schee, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mirjam van Tiel, The Foundation for Public Code"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ngô Ngọc Đức Huy"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Paul Keller"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
+"(NIIS)](https://niis.org)"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Sky Bristol"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Tamas Erkelens, Gemeente Amsterdam"
+msgstr ""
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Timo Slinger"
+msgstr ""
+
+#: ./CC0-1.0.md:block 3 (header)
+msgid "toc: false redirect_from: - license.html - LICENSE.html"
+msgstr ""
+
+#: ./CC0-1.0.md:block 4 (header)
+msgid "Creative Commons Zero v1.0 Universal"
+msgstr ""
+
+#: ./CC0-1.0.md:block 6 (paragraph)
+msgid ""
+"This license is the legal contract that allows anyone to do anything they "
+"like with the content in this entire document."
+msgstr ""
+
+#: ./CHANGELOG.md:block 3 (header)
+msgid ""
+"script/release-body.sh expects VERSION in the first second-level header"
+msgstr ""
+
+#: ./CHANGELOG.md:block 4 (header)
+msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
+msgstr ""
+
+#: ./CHANGELOG.md:block 5 (header)
+msgid "Version history"
+msgstr ""
+
+#: ./CHANGELOG.md:block 6 (header)
+msgid "Version 0.7.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 7 (paragraph)
+msgid ""
+"July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
+"clarifies references to code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"The criterion \"Make the codebase reusable and portable\" was renamed from "
+"\"Create reusable and portable code\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Added a glossary entry for \"Source Code\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"References to \"code\" which only applied to \"source code\" now reference "
+"\"source code\" explicitly."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Clarification of \"running code\" as \"software\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Minor changes to clarify \"code\" vs \"codebase\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Simplify guidance to policy makers in Bundle policy and source code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid ""
+"Clarify How to test sections of Make the codebase findable and Make the "
+"codebase reusable and portable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Add a criteria and requirements checklist to the release artifacts."
+msgstr ""
+
+#: ./CHANGELOG.md:block 8 (unordered list)
+msgid "Increase automation of the release process."
+msgstr ""
+
+#: ./CHANGELOG.md:block 9 (header)
+msgid "Version 0.7.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 10 (paragraph)
+msgid ""
+"May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
+"review funding and clarifies review process requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid ""
+"Add requirement to document who is expected to cover the cost of reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Add requirement to have a short description of the codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid ""
+"Change the focus of contributions adhering to standards to focus on the "
+"review of contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Review template now in HTML format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Introduction converted to foreword."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Improved contributing guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 11 (unordered list)
+msgid "Improved documentation of scripts."
+msgstr ""
+
+#: ./CHANGELOG.md:block 12 (header)
+msgid "Version 0.6.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 13 (paragraph)
+msgid ""
+"April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
+"portability and tests and an introduction to each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about the development "
+"being a collaboration between multiple parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about being dependent "
+"on a single vendor."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"New requirement in Use continuous integration about publishing results for "
+"automated tests."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Differentiating the two requirements about security to clearly be about "
+"providing a method and having documentation about it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Rephrased requirements to focus on the codebase rather than contributor "
+"behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Removed the sections Why this is important and What this does not do and "
+"replaced with an introduction in each criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Added general What this does not do section in the introduction of the "
+"Standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Added guidance for public policy makers about related policies and license "
+"compatibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Added guidance for developers and designers about version controlling files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Clarified guidance for developers and designers about prompt responses and "
+"search engine optimization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Added Further reading about accessibility."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Aligned criteria URLs with criteria names."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Improved navigation in the web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Moved tools in Further reading sections to the community implementation "
+"guide."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Moved compliance or certification process to "
+"[publiccode.net](https://publiccode.net)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Change format of the review template to make it easier to update after a new"
+" release."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid ""
+"Improved the text on the landing page and added links to related resources."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Added spell checker automated test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Made minor changes to text for clarity and consistency."
+msgstr ""
+
+#: ./CHANGELOG.md:block 14 (unordered list)
+msgid "Moved SPDX headers to yaml header."
+msgstr ""
+
+#: ./CHANGELOG.md:block 15 (header)
+msgid "Version 0.5.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 16 (paragraph)
+msgid ""
+"January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
+"guidelines."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (unordered list)
+msgid ""
+"Adjust the coding style requirement to focus on the codebase using a style "
+"guide rather than contributor behavior."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (unordered list)
+msgid ""
+"Moved requirement for codebase names to Make the codebase findable from Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (unordered list)
+msgid ""
+"Moved requirement about testing the code by using examples to Use continuous"
+" integration from Document the code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (unordered list)
+msgid ""
+"Split requirement about machine testable standards to clarify that open is "
+"more important than testable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 17 (unordered list)
+msgid ""
+"Adjust how to test findability requirements to be less reliant on search "
+"engine algorithms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 18 (header)
+msgid "Version 0.4.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 19 (paragraph)
+msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid ""
+"Document maturity focuses on whether or not versions of the codebase are "
+"ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid ""
+"Document maturity no longer requires specific labels for codebases that are "
+"not ready to use."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Audit flow image now generated from an easier to translate format."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Improved guidance on How to test."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Add publiccode.yml file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Add review template."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Consistently link glossary terms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Add practices and standards to follow in CONTRIBUTING."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Add Matti Schneider to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Add remaining SPDX headers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Made additional minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid "Some hyperlinks updated."
+msgstr ""
+
+#: ./CHANGELOG.md:block 20 (unordered list)
+msgid ""
+"Moved examples to the [Community implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/)."
+msgstr ""
+
+#: ./CHANGELOG.md:block 21 (header)
+msgid "Version 0.4.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 22 (paragraph)
+msgid ""
+"September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Introduce new criterion: Make the codebase findable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Improve How to test section for most criteria."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid ""
+"New requirement in Welcome contributors about publishing activity "
+"statistics."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Removed redundant requirement about portable and reusable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid ""
+"Expand open license definition to include both OSI and FSF approved "
+"licenses."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid ""
+"Expressed intent that the Standard for Public Code should meet its own "
+"requirements where applicable and added assessment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Add SPDX license identifiers to files."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Introduced new Code of Conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Clarify distinction between source code and policy text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Restructuring of requirements with bullet point lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Acknowledge the importance of codebase modularity for reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Move requirements related to Findability to the new criterion."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Clarify the role of non-open standards when used in a codebase."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Additional guidance about build-time and runtime dependencies."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Added roadmap for the development of the Standard for Public Code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Update structure of Authors file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Add Audrey Tang to Authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid "Added a list of criteria to the print edition."
+msgstr ""
+
+#: ./CHANGELOG.md:block 23 (unordered list)
+msgid ""
+"Clarify what the standard means with policymakers, managers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 24 (header)
+msgid "Version 0.3.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 25 (paragraph)
+msgid ""
+"May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid ""
+"Requirement for localization made explicit in Create reusable and portable "
+"code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid "Documentation of governance changed from a SHOULD to a MUST."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid ""
+"Replace the very subjective (and hard to test) \"contributions MUST be "
+"small\" with requirement to document expectation in contributing guidelines "
+"and focus on a single issue."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid "Community translations now linked in the footer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 26 (unordered list)
+msgid "Many minor clarifications to language and sentences made more simple."
+msgstr ""
+
+#: ./CHANGELOG.md:block 27 (header)
+msgid "Version 0.2.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 28 (paragraph)
+msgid ""
+"March 15th 2022: 📜 the ninth draft allows English summaries for policy "
+"lacking an official translation."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Relax the criterion Use plain English by adding a new requirement allows "
+"bundled policy not available in English to have an accompanying summary in "
+"English instead of translating the full text."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Similarly, allow for English summaries for policies not available in English"
+" in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Clarify that term 'policy' includes processes which impact development and "
+"deployment in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Emphasize reusability also on parts of the solutions in Create reusable and "
+"portable code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Expand guidance to Developers and designers in Create reusable and portable "
+"code about deploying to proprietary platforms."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Add nuance to use of non-English terms in what management need to do in Use "
+"plain English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid ""
+"Change the pull request process diagram to use Mermaid instead of BPMN to "
+"make [community translations](https://github.com/publiccodenet/community-"
+"translations-standard) easier."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid "Added Maurice Hendriks to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid "Added OpenApi Specification to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 29 (unordered list)
+msgid "Made the attributions in further reading sections clearer."
+msgstr ""
+
+#: ./CHANGELOG.md:block 30 (header)
+msgid "Version 0.2.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 31 (paragraph)
+msgid ""
+"November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
+" as code may not be in English."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid ""
+"Document exception to \"All code MUST be in English\" where policy is "
+"interpreted as code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid ""
+"Add MAY requirement regarding committer email addresses in Maintain version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Expand guidance to Policy Makers in Bundle policy and code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Expand guidance to Developers and designers in Use a coherent style."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add \"Different contexts\" to glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add Digital Public Goods approval badge."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add Open Standards principles to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add Definition of plain language to further reading."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Move the Semantic Versioning Specification further reading reference."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid ""
+"Clarify that publiccode.yml is one example of a machine-readable metadata "
+"description."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
+msgstr ""
+
+#: ./CHANGELOG.md:block 32 (unordered list)
+msgid "Add instructions for creating a print version."
+msgstr ""
+
+#: ./CHANGELOG.md:block 33 (header)
+msgid "Version 0.2.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 34 (paragraph)
+msgid ""
+"March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
+"0.2.0."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid ""
+"New SHOULD requirement on using a distributed version control system and why"
+" distributed is important."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid ""
+"Feedback requirements for rejected contributions are more strict than "
+"accepted ones."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid ""
+"Specify that copyright and license notices should also be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Advice on how to test that notices be machine-readable."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Clarify guidance for rolling releases."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Clear up definition of version control in glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid ""
+"Add further reading encouraging contribution, SPDX, Git and reviewing "
+"contributions."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Add links to videos about the concept of public code."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Update BPMN link."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Reduce link duplication."
+msgstr ""
+
+#: ./CHANGELOG.md:block 35 (unordered list)
+msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 36 (header)
+msgid "Version 0.2.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 37 (paragraph)
+msgid ""
+"October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
+"and \"Welcome contributors\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Rename criterion \"Pay attention to codebase maturity\" to \"Document "
+"codebase maturity\"."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Changed MUST to SHOULD for requirement of codebase in use by multiple "
+"parties."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid "Add MUST NOT requirement regarding copyright assignment."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid "Clarify role of configuration in reusable code requirement."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Glossary additions: continuous integration, policy, repository, and version "
+"control."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid "Replace references to 'cities' with 'public organizations'."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Clarify aspects of sensitive code by separating contributor and reviewer "
+"requirements into separate items."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid ""
+"Expand further reading, and guidance to policy makers, developers and "
+"designers."
+msgstr ""
+
+#: ./CHANGELOG.md:block 38 (unordered list)
+msgid "Add Felix Faassen and Arnout Engelen to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 39 (header)
+msgid "Version 0.1.4"
+msgstr ""
+
+#: ./CHANGELOG.md:block 40 (paragraph)
+msgid ""
+"November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
+"fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (unordered list)
+msgid "Linked License.md file."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (unordered list)
+msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (unordered list)
+msgid "Made punctuation more consistent, especially for bullet lists."
+msgstr ""
+
+#: ./CHANGELOG.md:block 41 (unordered list)
+msgid "Made some minor changes to text for clarity."
+msgstr ""
+
+#: ./CHANGELOG.md:block 42 (header)
+msgid "Version 0.1.3"
+msgstr ""
+
+#: ./CHANGELOG.md:block 43 (paragraph)
+msgid ""
+"October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
+" the autumn cleaning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 44 (unordered list)
+msgid "Renamed continuous delivery to continuous integration."
+msgstr ""
+
+#: ./CHANGELOG.md:block 44 (unordered list)
+msgid "Referencing accessibility guidelines in the language standard."
+msgstr ""
+
+#: ./CHANGELOG.md:block 44 (unordered list)
+msgid "A bunch of style and consistency fixes."
+msgstr ""
+
+#: ./CHANGELOG.md:block 45 (header)
+msgid "Version 0.1.2"
+msgstr ""
+
+#: ./CHANGELOG.md:block 46 (paragraph)
+msgid ""
+"August 22th 2019: 🌠 the third draft focuses on better text and takes "
+"community input"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "With some great new contributors comes a fresh author list."
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "All links are now HTTPS."
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "General proofreading, wording clarifications, and smashed typos."
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Updated criteria:"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Requirement for reuse in different contexts"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Recommendation for explicit versioning"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Recommendation for multi party development"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Recommendation for license headers in files"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Recommendation for vulnerability reporting"
+msgstr ""
+
+#: ./CHANGELOG.md:block 47 (unordered list)
+msgid "Recommendation for explicit documentation of governance"
+msgstr ""
+
+#: ./CHANGELOG.md:block 48 (header)
+msgid "Version 0.1.1"
+msgstr ""
+
+#: ./CHANGELOG.md:block 49 (paragraph)
+msgid ""
+"May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
+"lot of typos"
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (unordered list)
+msgid ""
+"Removed references to the Foundation for Public Code, we're going to have to"
+" change the name in becoming an association."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (unordered list)
+msgid "Updated the introduction."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (unordered list)
+msgid "Updated the glossary."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (unordered list)
+msgid "Added the code of conduct."
+msgstr ""
+
+#: ./CHANGELOG.md:block 50 (unordered list)
+msgid "We've recommended using the publiccode.yml standard for easier reuse."
+msgstr ""
+
+#: ./CHANGELOG.md:block 51 (header)
+msgid "Version 0.1.0"
+msgstr ""
+
+#: ./CHANGELOG.md:block 52 (paragraph)
+msgid ""
+"April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
+"snazzy new ideas in it"
+msgstr ""
+
+#: ./CHANGELOG.md:block 53 (unordered list)
+msgid "14 criteria with their requirements and how to operationalize them."
+msgstr ""
+
+#: ./CHANGELOG.md:block 53 (unordered list)
+msgid ""
+"An introduction with a high level background, what this standard is, and how"
+" the Foundation for Public Code will use it."
+msgstr ""
+
+#: ./CHANGELOG.md:block 54 (paragraph)
+msgid ""
+"This first version was produced together with the Amsterdam University of "
+"Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
+"Public Code! project](https://smartcities.publiccode.net/)."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 1 (header)
+msgid "Code of Conduct"
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 3 (paragraph)
+msgid ""
+"Many community members are from civic or professional environments with "
+"behavioral codes yet some individuals are not. This document expresses "
+"expectations of all community members and all interactions regardless of "
+"communication channel."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
+msgid "Be here to collaborate."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
+msgid "Be considerate, respectful, and patient."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
+msgid "Strive to be as constructive as possible."
+msgstr ""
+
+#: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
+msgid "To raise a concern, please email directors@publiccode.net."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 1 (header)
+msgid "Contributing to this standard"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 3 (paragraph)
+msgid "🙇‍♀️ Thank you for contributing!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 4 (paragraph)
+msgid ""
+"We understand that a standard like this can only be set in collaboration "
+"with as many public technologists, policy makers and interested folk as "
+"possible. Thus we appreciate your input, enjoy feedback and welcome "
+"improvements to this project and are very open to collaboration."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 5 (paragraph)
+msgid ""
+"We love issues and pull requests from everyone. If you're not comfortable "
+"with GitHub, you can email use your feedback at "
+"[info@publiccode.net](mailto:info@publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 6 (header)
+msgid "Problems, suggestions and questions in issues"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 7 (paragraph)
+msgid ""
+"A high-level overview of the development that we already have sketched out "
+"can be seen in the [roadmap](/docs/roadmap.md). Please help development by "
+"reporting problems, suggesting changes and asking questions. To do this, you"
+" can [create a GitHub issue](https://docs.github.com/en/issues/tracking-"
+"your-work-with-issues/creating-an-issue) for this project in the [GitHub "
+"Issues for the Standard for Public "
+"Code](https://github.com/publiccodenet/standard/issues)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 8 (paragraph)
+msgid ""
+"Or, sign up to the [mailing "
+"list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)"
+" and send an email to "
+"[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 9 (paragraph)
+msgid ""
+"You don't need to change any of our code or documentation to be a "
+"contributor!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 10 (header)
+msgid "Documentation and code in pull requests"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 11 (paragraph)
+msgid ""
+"If you want to add to the documentation or code of one of our projects you "
+"should make a pull request."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 12 (paragraph)
+msgid ""
+"If you never used GitHub, get up to speed with [Understanding the GitHub "
+"flow](https://docs.github.com/en/get-started/quickstart/github-flow) or "
+"follow one of the great free interactive courses in [GitHub "
+"Skills](https://skills.github.com/) on working with GitHub and working with "
+"MarkDown, the syntax this project's documentation is in."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 13 (paragraph)
+msgid ""
+"This project is licensed Creative Commons Zero v1.0 Universal, which "
+"essentially means that the project, along with your contributions is in the "
+"public domain in whatever jurisdiction possible, and everyone can do "
+"whatever they want with it."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 14 (header)
+msgid "1. Make your changes"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 15 (paragraph)
+msgid ""
+"Contributions should [follow](docs/standard-for-public-code.html) the "
+"requirements set out in the criteria of the Standard for Public code itself."
+" Reviewers will also be ensuring that contributions are aligned with the "
+"[values of public code](foreword.md#values-of-public-code). Furthermore, "
+"they will review that the contribution conforms to the "
+"[standards](#standards-to-follow) and remains coherent with the overall "
+"work."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 16 (paragraph)
+msgid ""
+"This project uses the [GitFlow branching model and "
+"workflow](https://nvie.com/posts/a-successful-git-branching-model/). When "
+"you've forked this repository, please make sure to create a feature branch "
+"following the GitFlow model."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 17 (paragraph)
+msgid ""
+"Add your changes in commits [with a message that explains "
+"them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-"
+"message). If more than one type of change is needed, group logically related"
+" changes into separate commits. For example, white-space fixes could be a "
+"separate commit from text content changes. When adding new files, select "
+"file formats that are easily viewed in a `diff`, for instance, `.svg` is "
+"preferable to a binary image. Document choices or decisions you make in the "
+"commit message, this will enable everyone to be informed of your choices in "
+"the future."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 18 (paragraph)
+msgid ""
+"If you are adding code, make sure you've added and updated the relevant "
+"documentation and tests before you submit your pull request. Make sure to "
+"write tests that show the behavior of the newly added or changed code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 19 (header)
+msgid "Applicable policy"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 20 (paragraph)
+msgid ""
+"Currently, the Standard for Public Code is not implementing any specific "
+"public policy."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 21 (header)
+msgid "Style"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 22 (paragraph)
+msgid ""
+"The Standard for Public Code aims to [use plain English](criteria/use-plain-"
+"english.md) and we have chosen American English for spelling. Text content "
+"should typically follow one line per sentence, with no line-wrap, in order "
+"to make `diff` output easier to view. However, we want to emphasize that it "
+"is more important that you make your contribution than worry about spelling "
+"and typography. We will help you get it right in our review process and we "
+"also have a separate quality check before [making a new "
+"release](docs/releasing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 23 (header)
+msgid "Standards to follow"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 24 (paragraph)
+msgid ""
+"These are the standards that the Standard for Public Code uses. Please make "
+"sure that your contributions are aligned with them so that they can be "
+"merged more easily."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
+" keywords"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[Web Content Accessibility Guidelines "
+"2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 26 (header)
+msgid "2. Pull request"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 27 (paragraph)
+msgid ""
+"When submitting the pull request, please accompany it with a description of "
+"the problem you are trying to solve and the issue number that this pull "
+"request fixes. It is preferred for each pull request to address a single "
+"issue where possible. In some cases a single set of changes may address "
+"multiple issues, in which case be sure to list all issue numbers fixed."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 28 (header)
+msgid "3. Improve"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 29 (paragraph)
+msgid ""
+"All contributions have to be reviewed by someone. The Foundation for Public "
+"Code has committed to make sure that maintainers are available to review "
+"contributions with an aim to provide feedback within two business days."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 30 (paragraph)
+msgid ""
+"It could be that your contribution can be merged immediately by a "
+"maintainer. However, usually, a new pull request needs some improvements "
+"before it can be merged. Other contributors (or helper robots) might have "
+"feedback. If this is the case the reviewing maintainer will help you improve"
+" your documentation and code."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 31 (paragraph)
+msgid "If your documentation and code have passed human review, it is merged."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 32 (header)
+msgid "4. Celebrate"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 33 (paragraph)
+msgid ""
+"Your ideas, documentation and code have become an integral part of this "
+"project. You are the open source hero we need!"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 34 (paragraph)
+msgid ""
+"In fact, feel free to open a pull request to add your name to the "
+"[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 35 (header)
+msgid "Translations in other languages"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 36 (paragraph)
+msgid ""
+"While the Standard does not have any official translations, you can help "
+"maintain existing and add new [community translations of the "
+"Standard](https://github.com/publiccodenet/community-translations-standard)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 37 (header)
+msgid "Releases"
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 38 (paragraph)
+msgid ""
+"We have dedicated documentation for creating [new "
+"releases](/docs/releasing.md) and [ordering printed "
+"standards](/docs/printing.md)."
+msgstr ""
+
+#: ./CONTRIBUTING.md:block 39 (paragraph)
+msgid ""
+"For more information on how to use and contribute to this project, please "
+"read the [`README`](README.md)."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 3 (header)
+msgid "Governance"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 4 (paragraph)
+msgid ""
+"This standard lies at the core of the codebase stewardship provided by the "
+"[Foundation for Public Code](https://publiccode.net/). We decide if a "
+"codebase is ready for community co-development based on this document."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 5 (paragraph)
+msgid "The standard is maintained by Foundation for Public Code staff."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 6 (paragraph)
+msgid ""
+"[We welcome contributions, such as suggestions for changes or general "
+"feedback, from anyone.](/CONTRIBUTING.md)"
+msgstr ""
+
+#: ./GOVERNANCE.md:block 7 (paragraph)
+msgid ""
+"Because of the important role that the Standard for Public Code has in our "
+"core process we require the highest standards from the Standard."
+msgstr ""
+
+#: ./GOVERNANCE.md:block 8 (paragraph)
+msgid ""
+"We will try to respond promptly to all pull requests. The pull request is an"
+" opportunity to work together to improve our methods and the Standard. We "
+"may not accept all changes, but we will explain our logic."
+msgstr ""
+
+#: ./README.md:block 1 (header)
+msgid "Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 3 (paragraph)
+msgid ""
+"The Standard for Public Code gives public organizations a model for "
+"preparing open source solutions to enable collaborations with similar public"
+" organizations in other places. It includes guidance for policy makers, city"
+" administrators, developers and vendors."
+msgstr ""
+
+#: ./README.md:block 4 (paragraph)
+msgid ""
+"![version 0.7.1](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/) "
+"[![Standard commitment](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
+msgstr ""
+
+#: ./README.md:block 5 (paragraph)
+msgid ""
+"[![pages-build-"
+"deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-"
+"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-deployment) "
+"[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
+" [![standard main badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
+"url-check/standard.publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net-"
+"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
+"check/standard.publiccode.net-develop-url-check-look.json)"
+msgstr ""
+
+#: ./README.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is in a draft format. We are preparing it for a"
+" version 1.0 release. Currently, we are testing it on a small number of "
+"codebases."
+msgstr ""
+
+#: ./README.md:block 7 (header)
+msgid "Applying the Standard for Public Code to your codebase"
+msgstr ""
+
+#: ./README.md:block 8 (paragraph)
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. If you wish to "
+"advertise the codebase community's aspiration to meet the criteria of the "
+"Standard for Public Code, link the documentation of this commitment from the"
+" [standard-for-public-code-commitment badge](assets/standard-for-public-"
+"code-commitment.svg). To see how ready your codebase is, you can do a quick "
+"[eligibility self assessment](https://publiccodenet.github.io/assessment-"
+"eligibility) that will give you a rough idea of how much work you may need "
+"to do to meet all criteria."
+msgstr ""
+
+#: ./README.md:block 9 (paragraph)
+msgid ""
+"The standard *should* be mostly self-explanatory in how to apply it to your "
+"codebase. If anything in the standard is unclear, we encourage you to open "
+"an issue here so that we can help you and anyone else who feels the same as "
+"you. For inspiration, look at the [community built implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/) which contains examples and other tips."
+msgstr ""
+
+#: ./README.md:block 10 (paragraph)
+msgid ""
+"If there are any breaking changes in a new version of the Standard for "
+"Public Code, the codebase stewards at the Foundation for Public Code will "
+"help any implementers of the standard understand how the gaps can be closed."
+msgstr ""
+
+#: ./README.md:block 11 (paragraph)
+msgid ""
+"If you want to commit your codebase to become fully compliant to the "
+"standard for future certification, please contact us at "
+"[info@publiccode.net](mailto:info@publiccode.net) to initiate a formal "
+"[assessment](https://about.publiccode.net/activities/codebase-"
+"stewardship/lifecycle-diagram.html#assessment)."
+msgstr ""
+
+#: ./README.md:block 12 (header)
+msgid "Request for contributions"
+msgstr ""
+
+#: ./README.md:block 13 (paragraph)
+msgid ""
+"We believe public policy and software should be inclusive, usable, open, "
+"legible, accountable, accessible and sustainable. This means we need a new "
+"way of designing, developing and procuring both the source code and policy "
+"documentation."
+msgstr ""
+
+#: ./README.md:block 14 (paragraph)
+msgid ""
+"This standard sets a quality level for codebases that meets the needs of "
+"public organizations, institutions and administrations as well as other "
+"critical infrastructural services."
+msgstr ""
+
+#: ./README.md:block 15 (paragraph)
+msgid ""
+"The standard lives at "
+"[standard.publiccode.net](https://standard.publiccode.net/). See "
+"[`index.md`](index.md) for an overview of all content."
+msgstr ""
+
+#: ./README.md:block 16 (paragraph)
+msgid ""
+"[![Thumbnail for the video on the Standard for Public Code: a printed "
+"version lying on a table between two "
+"hands](https://img.youtube.com/vi/QWt6vB-"
+"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+msgstr ""
+
+#: ./README.md:block 17 (paragraph)
+msgid ""
+"[A video introduction to Standard for Public "
+"Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
+"Global Summit 2020 (4:12) on YouTube."
+msgstr ""
+
+#: ./README.md:block 18 (header)
+msgid "Help improve this standard"
+msgstr ""
+
+#: ./README.md:block 19 (paragraph)
+msgid ""
+"The Foundation for Public Code is committed to maintaining and developing "
+"the Standard for Public Code at a level of quality that meets the standard "
+"itself."
+msgstr ""
+
+#: ./README.md:block 20 (paragraph)
+msgid ""
+"We are looking for people like you to [contribute](CONTRIBUTING.md) to this "
+"project by suggesting improvements and helping develop it. 😊 Get started by "
+"reading our [contributors guide](CONTRIBUTING.md). Since it is such a core "
+"document we will accept contributions when they add significant value. We've"
+" described how we govern the standard in the [governance "
+"statement](GOVERNANCE.md)."
+msgstr ""
+
+#: ./README.md:block 21 (paragraph)
+msgid ""
+"Please note that this project is released with a [code of "
+"conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
+"abide by its terms. Please be lovely to all other community members."
+msgstr ""
+
+#: ./README.md:block 22 (header)
+msgid "Preview, build and deploy"
+msgstr ""
+
+#: ./README.md:block 23 (paragraph)
+msgid ""
+"The repository builds to a static site deployed at "
+"[standard.publiccode.net](https://standard.publiccode.net/). It is built "
+"with [GitHub pages](https://pages.github.com) and "
+"[Jekyll](https://jekyllrb.com/)."
+msgstr ""
+
+#: ./README.md:block 24 (paragraph)
+msgid ""
+"The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
+"means you will need ruby and ruby-bundler installed, for example:"
+msgstr ""
+
+#: ./README.md:block 26 (paragraph)
+msgid ""
+"If `ruby` and `bundle` are installed, one can run `bundle install` after "
+"which the site can be rendered with the `script/serve.sh` script."
+msgstr ""
+
+#: ./README.md:block 27 (header)
+msgid "Testing"
+msgstr ""
+
+#: ./README.md:block 28 (paragraph)
+msgid ""
+"A variety of test scripts are included. The script `script/test-all.sh` "
+"wraps running of all local tests."
+msgstr ""
+
+#: ./README.md:block 29 (paragraph)
+msgid ""
+"See the scripts in the "
+"[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
+msgstr ""
+
+#: ./README.md:block 30 (header)
+msgid "Generating a PDF of the Standard for Public Code"
+msgstr ""
+
+#: ./README.md:block 31 (paragraph)
+msgid ""
+"In addition to Jekyll, generating PDFs relies upon "
+"[Weasyprint](https://weasyprint.org/) and "
+"[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
+"used to transform PDFs into `.epub`."
+msgstr ""
+
+#: ./README.md:block 32 (paragraph)
+msgid ""
+"To generate these kinds of files, the dependencies should be installed, for "
+"example:"
+msgstr ""
+
+#: ./README.md:block 34 (paragraph)
+msgid ""
+"The file `standard-print.html` can be converted to a nice looking PDF, along"
+" with the other release files, using:"
+msgstr ""
+
+#: ./README.md:block 36 (header)
+msgid "License"
+msgstr ""
+
+#: ./README.md:block 37 (paragraph)
+msgid "© [The authors and contributors](AUTHORS.md)"
+msgstr ""
+
+#: ./README.md:block 38 (paragraph)
+msgid ""
+"The standard is [licensed](LICENSE) under CC 0, which also applies to all "
+"illustrations and the documentation. This means anyone can do anything with "
+"it. If you contribute you also grant these rights to others. You can read "
+"more about how to help in the [contributing guide](CONTRIBUTING.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
+msgid "order: 2 redirect_from:"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 4 (unordered list)
+msgid "criteria/bundle-policy-and-code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
+msgid "Bundle policy and source code"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
+msgid ""
+"Access to both [source code](../glossary.md#source-code) and "
+"[policy](../glossary.md#policy) documentation provides building blocks for "
+"anyone to implement the codebase in their local context or contribute to the"
+" further development of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
+msgid ""
+"Understanding the domain and policies within that domain is fundamental to "
+"understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
+msgid ""
+"To be able to evaluate whether to implement a codebase in a new context, an "
+"organization needs to understand what process changes it must choose to make"
+" or how to contribute additional configurability to the existing solution in"
+" order to adapt it to the new context."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
+msgid "Requirements"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "The codebase MUST include the policy that the source code is based on."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"If a policy is based on source code, that source code MUST be included in "
+"the codebase, unless used for fraud detection."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
+msgid "How to test"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
+msgid "Public policy makers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Collaborate with developers and designers to make sure there is no mismatch "
+"between policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable, such "
+"as those published by the [Object Management "
+"Group](https://www.omg.org/spec/)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Track policy with [the same version control](maintain-version-control.md) "
+"and documentation used to track source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Check in regularly to understand how the source code in the codebase has "
+"changed and whether it still matches the [intentions of the "
+"policy](document-codebase-objectives.md)."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development, including legal obligations like the [General Data Protection "
+"Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web "
+"Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-"
+"accessibility), or human rights policies, like a public organization's "
+"commitment to equal opportunity."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
+msgid "Managers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
+msgid "Developers and designers: what you need to do"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Work together with policy makers to make sure there is no mismatch between "
+"policy code and source code."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
+msgid "Further reading"
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
+" on Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 3 (header)
+msgid "order: 1"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 4 (header)
+msgid "Code in the open"
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 5 (paragraph)
+msgid ""
+"Coding in the open improves transparency, increases [source "
+"code](../glossary.md#source-code) quality, makes the source code easier to "
+"audit, and enables collaboration."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 6 (paragraph)
+msgid ""
+"Together, this creates more opportunities for citizens to understand how "
+"software and [policy](../glossary.md#policy) impact their interactions with "
+"a public organization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any policy in use (unless used for fraud detection) MUST"
+" be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST NOT contain sensitive information regarding users, their "
+"organization or third parties."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the [codebase](../glossary.md#codebase) files and commit "
+"history do not include sensitive information."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Develop policies in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"Clearly split data and source code, in order to meet the requirement about "
+"sensitive information above."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 3 (header)
+msgid ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 4 (header)
+msgid "Document codebase maturity"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
+msgid ""
+"Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps "
+"others decide whether to use and contribute to it. A codebase version's "
+"maturity includes the maturity of its dependencies. Understanding how a "
+"codebase has evolved is key to understanding the codebase and how to "
+"contribute to it."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The codebase MUST be versioned."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase MUST prominently document whether or not there are versions of "
+"the codebase that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"Codebase versions that are ready to use MUST only depend on versions of "
+"other codebases that are also ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The method for assigning version identifiers SHOULD be documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "It is OPTIONAL to use semantic versioning."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that it is obvious to policy makers, managers, developers and "
+"designers whether the codebase has versions that are ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that ready to use versions of the codebase do not depend on any "
+"versions of other codebases that are not ready to use."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Check that the versioning scheme of the codebase is documented and followed."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any [source"
+" code](../glossary.md#source-code) developed needs to be tested and improved"
+" before it can be put into service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
+msgid ""
+"Make sure that services only rely on versions of codebases of equal or "
+"greater maturity than the service. For example, don't use a beta version of "
+"a codebase in a production service."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that the codebase versioning approach is followed for all "
+"releases."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Software release life "
+"cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
+msgid "order: 8 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
+msgid "criteria/document-objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 5 (header)
+msgid "Document codebase objectives"
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
+msgid ""
+"Clearly documenting [codebase](../glossary.md#codebase) objectives "
+"communicates the purpose of the codebase. It helps stakeholders and "
+"contributors scope the development of the codebase. The objectives also "
+"provide an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST contain documentation of its objectives, like a mission "
+"and goal statement, that is understandable by developers and designers so "
+"that they can use or contribute to the codebase."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Make sure that all your codebase objectives have links or references to "
+"supporting policy documents added to meet the [Bundle policy and source "
+"code](bundle-policy-and-source-code.md) criterion."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr ""
+
+#: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 3 (paragraph)
+msgid "order: 9 redirect_from:"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 4 (unordered list)
+msgid "criteria/documenting"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 5 (header)
+msgid "Document the code"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 6 (paragraph)
+msgid ""
+"Well documented [source code](../glossary.md#source-code) helps people to "
+"understand what the source code does and how to use it. Documentation is "
+"essential for people to start using the [codebase](../glossary.md#codebase) "
+"and contributing to it more quickly."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"All of the functionality of the codebase, [policy](../glossary.md#policy) as"
+" well as source code, MUST be described in language clearly understandable "
+"for those that understand the purpose of the codebase."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the software."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated correctly, and links and images are "
+"tested."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Try to use the codebase, so your feedback can improve how clearly the policy"
+" and source code are documented. For example, is the current documentation "
+"sufficient to persuade a manager at another public organization to use this "
+"codebase?"
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr ""
+
+#: ./criteria/document-the-code.md:block 18 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr ""
+
+#: ./criteria/index.md:block 3 (header)
+msgid "order: 0"
+msgstr ""
+
+#: ./criteria/index.md:block 4 (header)
+msgid "Criteria"
+msgstr ""
+
+#: ./criteria/index.md:block 5 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr ""
+
+#: ./criteria/index.md:block 6 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./criteria/index.md:block 7 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 3 (paragraph)
+msgid "order: 6 redirect_from:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 4 (unordered list)
+msgid "criteria/version-control-and-history"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 5 (header)
+msgid "Maintain version control"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 6 (paragraph)
+msgid ""
+"[Version control](../glossary.md#version-control) means keeping track of "
+"changes to the [source code](../glossary.md#source-code) and other files of "
+"the [codebase](../glossary.md#codebase) over time. This allows you to "
+"maintain structured documentation of the history of the codebase. This is "
+"essential for collaboration at scale, as it enables developers to work on "
+"changes in parallel and helps future developers to understand the reasons "
+"for changes."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All files in the codebase MUST be version controlled."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD require contributors to group relevant "
+"changes in commits."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD encourage file formats where the changes "
+"within the files can be easily viewed and understood in the version control "
+"system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "what the policy change is,"
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "how it's changed the codebase."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 13 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 15 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Make sure that all files required to understand the code, build and deploy "
+"are in the version control system."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
+"use GitHub or refresh your skills."
+msgstr ""
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 3 (header)
+msgid "order: 5"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 4 (header)
+msgid "Make contributing easy"
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 5 (paragraph)
+msgid ""
+"To develop better, more reliable and feature rich software, users need to be"
+" able to fix problems, add features, and address security issues of the "
+"shared [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 6 (paragraph)
+msgid ""
+"A shared digital infrastructure makes it easier to make collaborative "
+"contributions. The less effort it takes to make contributions that are "
+"accepted by the codebase, the more likely users are to become contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have a public issue tracker that accepts suggestions from "
+"anyone."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"There MUST be a way to report security issues for responsible disclosure "
+"over a closed channel."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST include instructions for how to report potentially "
+"security sensitive issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a closed channel for reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 12 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Just like for [reviews](require-review-of-contributions.md), make sure to "
+"respond to requests promptly."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Keep your managers informed of the time and resources you require to support"
+" other contributors."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate communication channels for asking maintainers and"
+" stakeholders questions are easy to locate, for instance in the README."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate contact details are included in the metadata, for"
+" instance in the publiccode.yml file."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
+msgid "order: 14 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
+msgid "criteria/findability"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 5 (header)
+msgid "Make the codebase findable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
+msgid ""
+"The more findable a [codebase](../glossary.md#codebase) is, the more "
+"potential new collaborators will find it. Just publishing a codebase and "
+"hoping it is found does not work, instead proactiveness is needed."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
+msgid ""
+"A metadata description file increases discoverability. Well-written metadata"
+" containing a unique and persistent identifier, such as a Wikidata item or "
+"FSF software directory listing (thus being part of the semantic web), makes "
+"the codebase easier for people to refer, cite, disambiguate and discover "
+"through third party tools."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a short description that helps someone understand "
+"what the codebase is for or what it does."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by describing the "
+"problem it solves in natural language."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check that the codebase name is descriptive and free of puns."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of acronyms and abbreviations or that "
+"the acronyms or abbreviations in the name are more universally known than "
+"the longer forms."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of organizational branding, unless that"
+" organization is of the codebase community itself."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase repository has a short description of the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by the codebase name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by using natural language, for instance, using the "
+"short description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as social media account descriptions."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Make sure people involved in the project present at relevant conferences."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Search engine optimization, for instance adding a "
+"[sitemap](https://www.sitemaps.org/protocol.html)."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as the repository description."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Software Foundation."
+msgstr ""
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
+msgid "order: 3 redirect_from:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/reusable-and-portable-codebases"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/create-reusable-and-portable-code"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
+msgid "Make the codebase reusable and portable"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
+msgid ""
+"Creating reusable and portable [code](../glossary.md#code) enables policy "
+"makers, developers and designers to reuse what has been developed, test it, "
+"improve it and contribute those improvements back, leading to better "
+"quality, cheaper maintenance and higher reliability."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
+msgid ""
+"Thoughtfully and purposefully designing a "
+"[codebase](../glossary.md#codebase) for reusability allows for the mission, "
+"vision and scope of the codebase to be shared by multiple parties. Codebases"
+" developed and used by multiple parties are more likely to benefit from a "
+"self-sustaining community."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
+msgid ""
+"Organizing a codebase such that it is composed of well documented modules "
+"improves reusability and maintainability. A module is easier to reuse in "
+"[another context](../glossary.md#different-contexts) if its purpose is "
+"clearly documented."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
+msgid ""
+"Source code which does not rely on the situation-specific infrastructure of "
+"any contributor, vendor or deployment can be tested by any other "
+"contributor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase MUST be developed to be reusable in different contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed software or services for execution and understanding."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The development of the codebase SHOULD be a collaboration between multiple "
+"parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Configuration SHOULD be used to make [source code](../glossary.md#source-"
+"code) adapt to context specific needs."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be localizable."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Source code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The software SHOULD NOT require services or platforms available from only a "
+"single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"use the codebase and what that would entail."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed software or services."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"If the codebase is in early development before a production-ready release, "
+"then check for evidence of ambition to obtain collaborators."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Or if the codebase is very mature and stable with very infrequent fixes, "
+"patches, or contributions:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check for documented and budgeted commitments of collaboration."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Otherwise:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check that the codebase contributors are from multiple parties."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the software can be deployed and run without services or "
+"platforms available from a single vendor."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Identify other organizations for your teams to collaborate with."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid "Make sure that your teams are collaborating with other teams."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
+msgid "Source should be designed:"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "in logically meaningful and isolated modules,"
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
+msgid ""
+"Make sure that the codebase documentation describes the build-time and "
+"runtime dependencies. If your context requires deploying to proprietary "
+"platforms or using proprietary components, make sure that collaborators can "
+"develop, use, test, and deploy without them."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
+msgid "order: 13 redirect_from:"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
+msgid "criteria/open-licenses"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 5 (header)
+msgid "Publish with an open license"
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 6 (paragraph)
+msgid ""
+"An open and well known license makes it possible for anyone to see the "
+"[source code](../glossary.md#source-code) in order to understand how it "
+"works, to use it freely and to contribute to the "
+"[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
+"emerge around the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
+msgid ""
+"Clearly indicating the license for each file within a codebase facilitates "
+"correct reuse and attribution of parts of a codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code and documentation MUST be licensed such that it may be "
+"freely reusable, changeable and redistributable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid "All source code MUST be published with a license file."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Having multiple licenses for different types of source code and "
+"documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires source code to be "
+"[open source](../glossary.md#open-source)."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their source code by "
+"publishing it under an open source license."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"When source code is being reused by the codebase, make sure that it has a "
+"license that is compatible with the license or licenses of the codebase."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
+msgid "order: 7 redirect_from:"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
+msgid "criteria/require-review"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 5 (header)
+msgid "Require review of contributions"
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 6 (paragraph)
+msgid ""
+"Peer-review of contributions is essential for [source "
+"code](../glossary.md#source-code) quality, reducing security risks and "
+"operational risks."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
+msgid ""
+"Requiring thorough review of contributions encourages a culture of making "
+"sure every contribution is of high quality, completeness and value. Source "
+"code review increases the chance of discovering and fixing potential bugs or"
+" mistakes before they are added to the [codebase](../glossary.md#codebase). "
+"Knowing that all source code was reviewed discourages a culture of blaming "
+"individuals, and encourages a culture of focusing on solutions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
+msgid ""
+"A [policy](../glossary.md#policy) of prompt reviews assures contributors of "
+"a guaranteed time for feedback or collaborative improvement, which increases"
+" both rate of delivery and contributor engagement."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"codebase MUST be reviewed by another contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews MUST include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"The review process SHOULD confirm that a contribution conforms to the "
+"standards, architecture and decisions set out in the codebase in order to "
+"pass review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the software and the tests of the "
+"codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check if guidelines for reviewers include instructions to review for "
+"conformance to standards, architecture and codebase guidelines."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check with reviewers if they run the software and tests during review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just source code, is "
+"reviewed."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make delivering great software a shared objective."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Try to respond to others' requests for review promptly, initially providing "
+"feedback about the concept of the change."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/)."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
+msgid "order: 15 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
+msgid "criteria/style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 5 (header)
+msgid "Use a coherent style"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 6 (paragraph)
+msgid ""
+"Following a consistent and coherent style enables contributors in different "
+"environments to work together. Unifying vocabularies reduces friction in "
+"communication between contributors."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST use a coding or writing style "
+"guide, either the codebase community's own or an existing one referred to in"
+" the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The style guide SHOULD include expectations for inline comments and "
+"documentation for non-trivial sections."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"Including expectations for [understandable English](use-plain-english.md) in"
+" the style guide is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 12 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 16 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [source code](../glossary.md#source-code) contributions in "
+"order for them to be merged by the maintainers, including source, tests and "
+"documentation. Continually improve upon and expand this documentation with "
+"the aim of evolving this documentation into engineering guidelines."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
+msgid "Additionally:"
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Use a linter."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr ""
+
+#: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 3 (paragraph)
+msgid "order: 12 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 4 (unordered list)
+msgid "criteria/continuous-integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 5 (header)
+msgid "Use continuous integration"
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 6 (paragraph)
+msgid ""
+"Asynchronous collaboration is enabled by developers merging their work to a "
+"shared branch frequently, verified by automated tests. The more frequent the"
+" merging and the smaller the contribution, the easier it is to resolve merge"
+" conflicts."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 7 (paragraph)
+msgid ""
+"Automated testing of all functionality provides confidence that "
+"contributions are working as intended and have not introduced errors, and "
+"allows reviewers to focus on the structure and approach of the contribution."
+" The more focused the test, the easier it is to clearly identify and "
+"understand errors as they arise."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 8 (paragraph)
+msgid ""
+"Documenting a codebase's [continuous integration](../glossary.md#continuous-"
+"integration) workflow helps contributors understand the expectations of "
+"contributions. Continuous integration allows for an easier monitoring of the"
+" state of the [codebase](../glossary.md#codebase)."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"All functionality in the [source code](../glossary.md#source-code) MUST have"
+" automated tests."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the codebase."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have active contributors who can review contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Automated test results for contributions SHOULD be public."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing the software by using examples in the documentation is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code coverage tools check that coverage is at 100% of "
+"the source code."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check that test results are viewable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check if source code coverage data is published."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Involve managers as well as developers and designers as early in the process"
+" as possible and keep them engaged throughout development of your policy."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure the source code reflects any changes to the policy (see [Maintain "
+"version control](maintain-version-control.md))."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Plan the work to integrate small parts very often instead of large parts "
+"less frequently."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers structure the work plan such that it can be integrated as "
+"small increments."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Structure source code written to handle conditions which are difficult to "
+"create in a test environment in such a way that the conditions can be "
+"simulated during testing. Forms of resource exhaustion such as running out "
+"of storage space and memory allocation failure are typical examples of "
+"difficult to create conditions."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Deploy often."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 3 (paragraph)
+msgid "order: 11 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 4 (unordered list)
+msgid "criteria/open-standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 5 (header)
+msgid "Use open standards"
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 6 (paragraph)
+msgid ""
+"[Open standards](../glossary.md#open-standard) guarantee access to the "
+"knowledge required to use and contribute to the "
+"[codebase](../glossary.md#codebase). They enable interoperability between "
+"systems and reduce the risk of vendor lock-in. Open standards which are "
+"unambiguous allow for independent development of either side of data "
+"exchange."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"For features of the codebase that facilitate the exchange of data the "
+"codebase MUST use an open standard that meets the [Open Source Initiative "
+"Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Open standards that are machine testable SHOULD be preferred over open "
+"standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Non-open standards that are machine testable SHOULD be preferred over non-"
+"open standards that are not."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 14 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in [source "
+"code](../glossary.md#source-code) reviews."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr ""
+
+#: ./criteria/use-open-standards.md:block 18 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 3 (paragraph)
+msgid "order: 10 redirect_from:"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 4 (unordered list)
+msgid "criteria/understandable-english-first"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 5 (header)
+msgid "Use plain English"
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 6 (paragraph)
+msgid ""
+"English is the <i>de facto</i> language of collaboration in software "
+"development."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 7 (paragraph)
+msgid ""
+"Public sector information needs to be accessible to all its constituents. "
+"Plain and simple language makes the [code](../glossary.md#code) and what it "
+"does easier to understand for a wider variety of people."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 8 (paragraph)
+msgid ""
+"Translations further increase the possible reach of a "
+"[codebase](../glossary.md#codebase). Language that is easy to understand "
+"lowers the cost of creating and maintaining translations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid "All codebase documentation MUST be in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All [source code](../glossary.md#source-code) MUST be in English, except "
+"where [policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 14 (unordered list)
+msgid ""
+"Frequently test with other managers, developers and designers in the process"
+" if they understand what you are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Frequently test with policy makers and managers if they understand what you "
+"are delivering and how you document it."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
+"readable and understandable."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"The[European Union accessibility directive](https://ec.europa.eu/digital-"
+"single-market/en/web-accessibility) by the European Commission, is an "
+"example of regulation requiring high accessibility."
+msgstr ""
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 3 (paragraph)
+msgid "order: 4 redirect_from:"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 4 (unordered list)
+msgid "criteria/open-to-contributions"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 5 (header)
+msgid "Welcome contributors"
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 6 (paragraph)
+msgid ""
+"The atmosphere in a [codebase](../glossary.md#codebase) community helps "
+"users decide to use one codebase over another. Welcoming anyone as a "
+"contributor enables the community to grow and sustain itself over time. A "
+"community where contributors have clear ways to influence codebase and "
+"community goals and progress is less likely to split and end up in diverging"
+" communities. Newcomers need to understand and trust the codebase "
+"community’s governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST allow anyone to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The contribution guidelines SHOULD document who is expected to cover the "
+"costs of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Check that contributing guidelines cover who is expected to cover the costs "
+"of reviewing contributions."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a roadmap."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for published activity statistics."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a code of conduct."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If needed, make sure you have allocated budget for the contributions review "
+"process as agreed by the codebase community."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid "Respond promptly to requests."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid ""
+"Communicate clearly to contributors what they need to do make sure their "
+"contribution can be integrated."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr ""
+
+#: ./docs/printing.md:block 1 (header)
+msgid "Printing"
+msgstr ""
+
+#: ./docs/printing.md:block 3 (paragraph)
+msgid ""
+"The printed Standard for Public Code is printed by Reclameland. This guide "
+"tries to provide the relevant information to print it there or somewhere "
+"else."
+msgstr ""
+
+#: ./docs/printing.md:block 4 (paragraph)
+msgid ""
+"Details, mostly in order they are on the Reclameland page with the Dutch if "
+"necessary:"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Form: Softcover book ([Reclameland product "
+"page](https://www.reclameland.nl/drukken/softcover-boeken))"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Format: A4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Portrait or landscape: Portrait (Staand)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing inside: 4/4 dual sided full color"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Inside material: 90 grams biotop"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover: 350 grams cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing cover: 4/0 one sided full cover"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover treatment: one sided matt foliated (Enke)"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
+" multiple of 4"
+msgstr ""
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Individually sealed: no"
+msgstr ""
+
+#: ./docs/printing.md:block 6 (paragraph)
+msgid ""
+"When these details are chosen, the cover and insides are uploaded and the "
+"order is placed payment can happen (payment ahead) after which printing "
+"starts."
+msgstr ""
+
+#: ./docs/releasing.md:block 1 (header)
+msgid "Releasing a new version of the Standard for public code"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Review state of the 'develop' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure all changes intended for release are merged"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Invite a proofread of the current state of the branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If new dashes are introduced, check if the language can be simplified to "
+"remove them in favor of more simple sentences. If a complex sentence is "
+"needed, see if the dash can be replaced with other punctuation. If a dash is"
+" truly the best expression of ideas, then follow the [Chicago Manual of "
+"Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create a release branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update the new release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`roadmap.md`](roadmap.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Perform extra pass on diff to the 'main' branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"run `script/generate-review-template.sh` and commit updated `docs/review-"
+"template.html`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"update `docs/standard-for-public-code.html` with the new text from the "
+"review template, updating any status changes as a result"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reread any section or paragraph to ensure wording changes still fit the "
+"whole and do not contain grammar or spelling errors"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
+" `script/ensure-font.sh`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure no link collisions exist"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Check the page breaks, possibly removing or adding page-break CSS, for "
+"example: `<p style=\"page-break-after: always;\"></p>`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "If needed, commit fixes and repeat extra pass"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Push branch, compare with 'main' branch, i.e.: "
+"`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Request review from multiple reviewers, especially a proofreader"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reviewers will create issues for shortcomings found which would not prevent "
+"release"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If needed for release, reviewers may create pull requests to resolve issues"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Re-request reviews if additional pull requests are merged into release "
+"branch"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Run the to-archive-org.sh script"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create GitHub release with the release notes and version number"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "[Send the files for print to the printer](printing.md)"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Cover file"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Inside pages PDF"
+msgstr ""
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ping [translation](https://github.com/publiccodenet/community-translations-"
+"standard) contributors"
+msgstr ""
+
+#: ./docs/roadmap.md:block 1 (header)
+msgid "Roadmap"
+msgstr ""
+
+#: ./docs/roadmap.md:block 3 (paragraph)
+msgid "Last updated: 2023-03-08"
+msgstr ""
+
+#: ./docs/roadmap.md:block 4 (paragraph)
+msgid ""
+"This document intends to shed light on the current development plans of the "
+"team. Plans change constantly as new information is absorbed by the team."
+msgstr ""
+
+#: ./docs/roadmap.md:block 5 (paragraph)
+msgid ""
+"Codebase stewards review the roadmap monthly as part of our [backlog pruning"
+" session](https://about.publiccode.net/activities/standard-"
+"maintenance/backlog-pruning.html)."
+msgstr ""
+
+#: ./docs/roadmap.md:block 6 (header)
+msgid "Current work"
+msgstr ""
+
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "As far as possible, make the standard Standard-compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "Certification badges"
+msgstr ""
+
+#: ./docs/roadmap.md:block 8 (header)
+msgid "Near term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Separate executive summary (issue #302)"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Physical paper checklist"
+msgstr ""
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Possibly: add in the illustrations for each criterion"
+msgstr ""
+
+#: ./docs/roadmap.md:block 10 (header)
+msgid "Longer term"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid ""
+"Add to README and index.md information (and eventually statistics) on "
+"adoption and use (issue #438)"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Becoming validated by multiple codebases"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Release version 1.0.0 after a few codebases are compliant"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Linkable requirements"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "New cover art"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Register for ISBN"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "List with an on-demand book printing service"
+msgstr ""
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "QR codes for external links in print version"
+msgstr ""
+
+#: ./foreword.md:block 3 (paragraph)
+msgid "redirect_from:"
+msgstr ""
+
+#: ./foreword.md:block 4 (unordered list)
+msgid "introduction"
+msgstr ""
+
+#: ./foreword.md:block 5 (header)
+msgid "Foreword"
+msgstr ""
+
+#: ./foreword.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that support public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./foreword.md:block 7 (paragraph)
+msgid ""
+"Anyone developing public-purpose software or policy can use this standard to"
+" work towards higher quality public services that are more cost effective, "
+"with less risk and more control."
+msgstr ""
+
+#: ./foreword.md:block 8 (paragraph)
+msgid ""
+"This foreword introduces the term public code and explains why this is "
+"important."
+msgstr ""
+
+#: ./foreword.md:block 9 (header)
+msgid "Definition of public code"
+msgstr ""
+
+#: ./foreword.md:block 10 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines. It "
+"encompasses the software built to operate with and as public infrastructure,"
+" along with the arrangements for its production. Public code is explicitly "
+"distinct from regular software because it operates under fundamentally "
+"different circumstances and expectations."
+msgstr ""
+
+#: ./foreword.md:block 11 (header)
+msgid "Reasons for public code"
+msgstr ""
+
+#: ./foreword.md:block 12 (paragraph)
+msgid "There are many reasons for why public code is relevant now."
+msgstr ""
+
+#: ./foreword.md:block 13 (header)
+msgid "Software code == legal code"
+msgstr ""
+
+#: ./foreword.md:block 14 (paragraph)
+msgid "Software is public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 15 (paragraph)
+msgid ""
+"In the 21st century, software can be considered vital public infrastructure."
+" It is increasingly not just the expression of existing policy but the "
+"originator of new policy, for example where algorithms decide which "
+"districts need extra social services or policing."
+msgstr ""
+
+#: ./foreword.md:block 16 (paragraph)
+msgid ""
+"Software mechanics, algorithms and data collection have become key elements "
+"in the execution of public policies. Computer code now executes policies "
+"that have been codified in legal code through democratic procedures. Both "
+"forms of code set conditions for society to function according to "
+"democratically set public values, the latter executed by humans, the former "
+"by machines. In other words, software code has increasingly started to equal"
+" legal code."
+msgstr ""
+
+#: ./foreword.md:block 17 (paragraph)
+msgid ""
+"Software should therefore be subject to the principles of democratic "
+"governance."
+msgstr ""
+
+#: ./foreword.md:block 18 (header)
+msgid "Traditional public software procurement"
+msgstr ""
+
+#: ./foreword.md:block 19 (paragraph)
+msgid ""
+"Current public software production methods have not served public service "
+"delivery very well."
+msgstr ""
+
+#: ./foreword.md:block 20 (paragraph)
+msgid ""
+"In the last decade, public organizations that purchased complete software "
+"solutions have sometimes been surprised to discover that they:"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"can’t change their software to reflect changing policy or take advantage of "
+"new technology"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"don’t have access to their data as it's locked into proprietary systems"
+msgstr ""
+
+#: ./foreword.md:block 21 (unordered list)
+msgid "are asked to pay ever increasing license fees"
+msgstr ""
+
+#: ./foreword.md:block 22 (header)
+msgid "Technological sovereignty and democratic accountability"
+msgstr ""
+
+#: ./foreword.md:block 23 (paragraph)
+msgid "Public institutions, civil servants and residents deserve better."
+msgstr ""
+
+#: ./foreword.md:block 24 (paragraph)
+msgid ""
+"We believe the software that runs our society can no longer be a black box, "
+"controlled by outside companies that keep the underlying logic on which "
+"their software operates hidden in proprietary codebases. Instead, "
+"governments and the people they serve need technological sovereignty. This "
+"allows them to set and control the functioning of public software, just like"
+" they are able to set and control policy that is legally formulated in laws."
+" Citizens and civil society actors need this software to be transparent and "
+"accountable."
+msgstr ""
+
+#: ./foreword.md:block 25 (paragraph)
+msgid ""
+"The design of software as essential civic infrastructure should honor "
+"digital citizens’ rights."
+msgstr ""
+
+#: ./foreword.md:block 26 (header)
+msgid "Designing truly public software"
+msgstr ""
+
+#: ./foreword.md:block 27 (paragraph)
+msgid ""
+"Public code is at the core of modern public institutions, shapes the work of"
+" civil servants and affects the lives of almost all residents."
+msgstr ""
+
+#: ./foreword.md:block 28 (paragraph)
+msgid "Public software must therefore be:"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "transparent"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "accountable"
+msgstr ""
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "understandable for its constituents"
+msgstr ""
+
+#: ./foreword.md:block 30 (paragraph)
+msgid ""
+"It must reflect the values of the society it serves, for example by being "
+"inclusive and non-discriminatory."
+msgstr ""
+
+#: ./foreword.md:block 31 (paragraph)
+msgid ""
+"Most proprietary software systems currently used by public organizations do "
+"not meet these requirements. Public code does."
+msgstr ""
+
+#: ./foreword.md:block 32 (header)
+msgid "Values of public code"
+msgstr ""
+
+#: ./foreword.md:block 33 (paragraph)
+msgid "We consider public code to have these core values:"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Inclusive"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Usable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Open"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Legible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accountable"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accessible"
+msgstr ""
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Sustainable"
+msgstr ""
+
+#: ./foreword.md:block 35 (header)
+msgid "How public code works"
+msgstr ""
+
+#: ./foreword.md:block 36 (paragraph)
+msgid ""
+"Public code is open source software meant for fulfilling the essential role "
+"of public organizations. Through use, other administrations contribute back "
+"to the software, so that its development and maintenance become truly "
+"collaborative."
+msgstr ""
+
+#: ./foreword.md:block 37 (paragraph)
+msgid "Being open unlocks many other things."
+msgstr ""
+
+#: ./foreword.md:block 38 (paragraph)
+msgid ""
+"Local responsibility and democratic accountability are ensured when a public"
+" organization implements and maintains their own public code. By being open "
+"and with a broader contributor base, the software is more secure as it "
+"benefits from many eyes spotting potential flaws. Many contributors share "
+"the maintenance work to keep it functional and modern, which reduces future "
+"technical debt. The shared workload is more sustainable now and in the "
+"future. Its openness makes both the code and its data more easily adaptable "
+"in the future. The code will be easier to retool, repurpose or retire. This "
+"all results in lower risk public infrastructure."
+msgstr ""
+
+#: ./foreword.md:block 39 (paragraph)
+msgid ""
+"This pooling of resources lets public administrations give extra attention "
+"to how to customize the software so it works best in each local context, "
+"creating better user experiences for their end users (residents or "
+"citizens)."
+msgstr ""
+
+#: ./foreword.md:block 40 (header)
+msgid "Economics of public code"
+msgstr ""
+
+#: ./foreword.md:block 41 (paragraph)
+msgid ""
+"Public code offers a better economic model for public organizations as well "
+"as for commercial companies. It's an alternative to traditional software "
+"procurement which increases local control and economic opportunity."
+msgstr ""
+
+#: ./foreword.md:block 42 (paragraph)
+msgid ""
+"Designed from the start to be open, adaptable and with data portability, it "
+"can be developed by in-house staff or trusted vendors. Because the code is "
+"open, the public administration can change vendors if they need to. Open "
+"code increases opportunities for public learning and scrutiny, allowing the "
+"public administration to procure smaller contracts. Smaller procurements are"
+" easier for local small and medium enterprises to bid upon. Public "
+"administrations can use their own software purchasing to stimulate "
+"innovation and competition in their local economy."
+msgstr ""
+
+#: ./foreword.md:block 43 (paragraph)
+msgid ""
+"This can be seen as investment leading to future economic growth. More "
+"vendors will be necessary due to growing technology demand."
+msgstr ""
+
+#: ./foreword.md:block 44 (header)
+msgid "Procuring public code"
+msgstr ""
+
+#: ./foreword.md:block 45 (paragraph)
+msgid ""
+"Public code can be used and developed by permanent in-house development "
+"teams, contractors or outsourced suppliers. Vendors to public organizations "
+"can include public code in their bids for contracts."
+msgstr ""
+
+#: ./foreword.md:block 46 (paragraph)
+msgid ""
+"To use existing public code, you need to specify in your budget and project "
+"design that your new solution will use that codebase. To encourage an "
+"innovative approach to adapting the public code to your context, you could "
+"describe the service or outcome in your contract."
+msgstr ""
+
+#: ./foreword.md:block 47 (header)
+msgid "The goals for the Standard for Public Code"
+msgstr ""
+
+#: ./foreword.md:block 48 (paragraph)
+msgid ""
+"This Standard supports developers, designers, managers and public policy "
+"makers to:"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop high quality software and policy for better public service delivery"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop codebases that can be reused across contexts and collaboratively "
+"maintained"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "reduce technical debt and project failure rate"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"have more granular control over, and ability to make decisions about, their "
+"IT systems"
+msgstr ""
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "improve vendor relationships with a better economic model"
+msgstr ""
+
+#: ./foreword.md:block 50 (paragraph)
+msgid ""
+"Potential users of codebases tested against the Standard for Public Code can"
+" expect them to be highly reusable, easily maintainable and of high quality."
+msgstr ""
+
+#: ./foreword.md:block 51 (paragraph)
+msgid "The Standard for Public Code does this by:"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "setting out a common terminology for public code development"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "establishing measures to help develop high quality public code"
+msgstr ""
+
+#: ./foreword.md:block 52 (unordered list)
+msgid ""
+"providing guidance on how to fulfill its criteria and operationalize "
+"compliance"
+msgstr ""
+
+#: ./foreword.md:block 53 (paragraph)
+msgid ""
+"The Standard for Public Code is meant to be time and technology independent."
+msgstr ""
+
+#: ./foreword.md:block 54 (header)
+msgid "Who this is for"
+msgstr ""
+
+#: ./foreword.md:block 55 (paragraph)
+msgid ""
+"The Standard for Public Code is for the people who create and reuse public "
+"code:"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "public policy makers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "business and project managers"
+msgstr ""
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "developers and designers"
+msgstr ""
+
+#: ./foreword.md:block 57 (paragraph)
+msgid "These people work at:"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid "institutions, organizations and administrations in the public sector"
+msgstr ""
+
+#: ./foreword.md:block 58 (unordered list)
+msgid ""
+"consultancies and vendors of information technology and policy services to "
+"public organizations"
+msgstr ""
+
+#: ./foreword.md:block 59 (paragraph)
+msgid ""
+"It is not aimed at public organizations' end users (residents or citizens), "
+"journalists or academics."
+msgstr ""
+
+#: ./foreword.md:block 61 (unordered list)
+msgid ""
+"[\"Modernising Public Infrastructure with Free Software\" white "
+"paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
+"Software.pdf) by the Free Software Foundation Europe."
+msgstr ""
+
+#: ./foreword.md:block 62 (header)
+msgid "Videos on public code"
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Collaborative Code is the Future of Cities @ DecidimFest "
+"2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
+"the background behind the Foundation for Public Code."
+msgstr ""
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Public Money? Public Code! - Panel @ Nextcloud Conference "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
+"procurement, law and more."
+msgstr ""
+
+#: ./foreword.md:block 64 (header)
+msgid "Get involved"
+msgstr ""
+
+#: ./foreword.md:block 65 (paragraph)
+msgid ""
+"This standard is a living document. [Read our contributor "
+"guide](/CONTRIBUTING.md) to learn how you can make it better."
+msgstr ""
+
+#: ./foreword.md:block 66 (header)
+msgid "Contact"
+msgstr ""
+
+#: ./foreword.md:block 67 (paragraph)
+msgid ""
+"For questions and more information about the Foundation for Public Code you "
+"can find us at [our website](https://publiccode.net/), email us at "
+"info@publiccode.net, or call us at +31 20 2 444 500."
+msgstr ""
+
+#: ./glossary.md:block 3 (header)
+msgid "Glossary"
+msgstr ""
+
+#: ./glossary.md:block 4 (header)
+msgid "Code"
+msgstr ""
+
+#: ./glossary.md:block 5 (paragraph)
+msgid ""
+"Any explicitly described system of rules. This includes laws, policy and "
+"ordinances, as well as source code that is used to build software. Both of "
+"these are rules, some executed by humans and others by machines."
+msgstr ""
+
+#: ./glossary.md:block 6 (header)
+msgid "Codebase"
+msgstr ""
+
+#: ./glossary.md:block 7 (paragraph)
+msgid ""
+"Any discrete package of code (both source and policy), the tests and the "
+"documentation required to implement a piece of policy or software."
+msgstr ""
+
+#: ./glossary.md:block 8 (paragraph)
+msgid "This can be, for example, a document or a version-control repository."
+msgstr ""
+
+#: ./glossary.md:block 9 (header)
+msgid "Continuous integration"
+msgstr ""
+
+#: ./glossary.md:block 10 (paragraph)
+msgid ""
+"In software engineering, continuous integration (CI) is the practice of "
+"merging all developers' working copies to a development branch of a codebase"
+" as frequently as reasonable."
+msgstr ""
+
+#: ./glossary.md:block 11 (header)
+msgid "Different contexts"
+msgstr ""
+
+#: ./glossary.md:block 12 (paragraph)
+msgid ""
+"Two contexts are different if they are different public organizations or "
+"different departments for which there is not one decision maker that could "
+"make collaboration happen naturally."
+msgstr ""
+
+#: ./glossary.md:block 13 (header)
+msgid "General public"
+msgstr ""
+
+#: ./glossary.md:block 14 (paragraph)
+msgid ""
+"The public at large: end users of the code and the services based upon it."
+msgstr ""
+
+#: ./glossary.md:block 15 (paragraph)
+msgid ""
+"For example, a city's residents are considered end users of a city's "
+"services and of all code that powers these services."
+msgstr ""
+
+#: ./glossary.md:block 16 (header)
+msgid "Open source"
+msgstr ""
+
+#: ./glossary.md:block 17 (paragraph)
+msgid ""
+"Open source is defined by the Open Source Initiative in their [Open Source "
+"Definition](https://opensource.org/osd-annotated)."
+msgstr ""
+
+#: ./glossary.md:block 18 (header)
+msgid "Open standard"
+msgstr ""
+
+#: ./glossary.md:block 19 (paragraph)
+msgid ""
+"An open standard is any standard that meets the Open Source Initiative's "
+"[Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+
+#: ./glossary.md:block 20 (header)
+msgid "Policy"
+msgstr ""
+
+#: ./glossary.md:block 21 (paragraph)
+msgid ""
+"A policy is a deliberate system of principles to guide decisions and achieve"
+" rational outcomes. A policy is a statement of intent, and is implemented as"
+" a procedure or protocol. Policies are generally adopted by a governance "
+"body within an organization. Policies can assist in both subjective and "
+"objective decision making."
+msgstr ""
+
+#: ./glossary.md:block 22 (paragraph)
+msgid ""
+"Public policy is the process by which governments translate their political "
+"vision into programs and actions to deliver outcomes."
+msgstr ""
+
+#: ./glossary.md:block 23 (paragraph)
+msgid ""
+"At the national level, policy and legislation (the law) are usually "
+"separate. The distinction is often more blurred in local government."
+msgstr ""
+
+#: ./glossary.md:block 24 (paragraph)
+msgid ""
+"In the Standard the word 'policy' refers to policy created and adopted by "
+"public organizations such as governments and municipalities."
+msgstr ""
+
+#: ./glossary.md:block 25 (header)
+msgid "Public code"
+msgstr ""
+
+#: ./glossary.md:block 26 (paragraph)
+msgid ""
+"Public code is open source software developed by public organizations, "
+"together with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./glossary.md:block 27 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines."
+msgstr ""
+
+#: ./glossary.md:block 28 (paragraph)
+msgid ""
+"Public code serves the public interest, is open, legible, accountable, "
+"accessible and sustainable."
+msgstr ""
+
+#: ./glossary.md:block 29 (paragraph)
+msgid ""
+"By developing public code independently from but still implementable in the "
+"local context for which it was developed, as well as documenting the "
+"development process openly, public code can provide a building block for "
+"others to:"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "re-implement in their local context"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "take as a starting point to continue development"
+msgstr ""
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "use as a basis for learning"
+msgstr ""
+
+#: ./glossary.md:block 31 (paragraph)
+msgid ""
+"To facilitate reuse, public code is either released into the public domain "
+"or licensed with an open license that permits others to view and reuse the "
+"work freely and to produce derivative works."
+msgstr ""
+
+#: ./glossary.md:block 32 (header)
+msgid "Repository"
+msgstr ""
+
+#: ./glossary.md:block 33 (paragraph)
+msgid ""
+"A repository is a storage location used by version control tools for files "
+"and metadata of a codebase. Repositories allow multiple contributors to work"
+" on the same set of files. Repositories are able to store multiple versions "
+"of sets of files."
+msgstr ""
+
+#: ./glossary.md:block 34 (header)
+msgid "Source Code"
+msgstr ""
+
+#: ./glossary.md:block 35 (paragraph)
+msgid ""
+"Human readable text of a computer program which can be translated into "
+"machine instructions."
+msgstr ""
+
+#: ./glossary.md:block 36 (header)
+msgid "Version control"
+msgstr ""
+
+#: ./glossary.md:block 37 (paragraph)
+msgid ""
+"Version control is the management of changes to source code and the files "
+"associated with it. Changes are usually identified by a code, termed the "
+"*revision number* (or similar). Each revision is associated with the time it"
+" was made and the person making the change, thus making it easier to retrace"
+" the evolution of the code. Revision control systems can be used to compare "
+"different versions with each other and to see how content has changed over "
+"time."
+msgstr ""
+
+#: ./index.md:block 3 (header)
+msgid "toc: false"
+msgstr ""
+
+#: ./index.md:block 4 (header)
+msgid "Guidance for government open source collaboration"
+msgstr ""
+
+#: ./index.md:block 5 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that supports public "
+"organizations in developing and maintaining software and policy together."
+msgstr ""
+
+#: ./index.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code provides guidance to public organizations "
+"building their own open source solutions to enable successful future "
+"collaboration and reuse by similar organizations in the public sector in "
+"other places. It includes advice for policy makers, government managers, "
+"developers and vendors. The Standard for Public Code supports the "
+"collaborative creation of codebases that are usable, open, legible, "
+"accountable, accessible and sustainable. It is meant to be applicable to "
+"codebases for all levels of government, from supranational to municipal."
+msgstr ""
+
+#: ./index.md:block 7 (paragraph)
+msgid ""
+"The Standard for Public Code defines ‘[public code](glossary.md#public-"
+"code)’ as open source software developed by public organizations, together "
+"with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+
+#: ./index.md:block 8 (paragraph)
+msgid ""
+"The criteria of the Standard for Public Code are aligned with guidelines and"
+" best practices of open source software development."
+msgstr ""
+
+#: ./index.md:block 9 (paragraph)
+msgid ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} Additional"
+" context and background can be found in the [foreword](foreword.md). {% "
+"endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 10 (header)
+msgid "Contents"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Glossary](glossary.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[Criteria](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for"
+" page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Authors](AUTHORS.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Contributing guide](CONTRIBUTING.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Governance](GOVERNANCE.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Version history](CHANGELOG.md)"
+msgstr ""
+
+#: ./index.md:block 11 (unordered list)
+msgid "[License](license.html)"
+msgstr ""
+
+#: ./index.md:block 12 (header)
+msgid "Community calls"
+msgstr ""
+
+#: ./index.md:block 13 (paragraph)
+msgid ""
+"We usually have a community call on the first Thursday of the month at 15:00"
+" (CET/CEST). [The agenda](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code) is updated roughly a week before the call. It is "
+"possible to [sign "
+"up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
+" to get a call invitation emailed to you."
+msgstr ""
+
+#: ./index.md:block 14 (header)
+msgid "Other resources"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"Unofficial [community translations of the "
+"Standard](https://publiccodenet.github.io/community-translations-standard/) "
+"in other languages"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard compliance self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
+"public sector open source codebases"
+msgstr ""
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard criteria checklist](/docs/review-template.html) used by Foundation"
+" for Public Code stewards for codebase review"
+msgstr ""
+
+#: ./readers-guide.md:block 3 (header)
+msgid "Readers guide"
+msgstr ""
+
+#: ./readers-guide.md:block 4 (paragraph)
+msgid ""
+"The Standard describes a number of criteria. All criteria have consistent "
+"sections that make it clear how to create great public code."
+msgstr ""
+
+#: ./readers-guide.md:block 5 (paragraph)
+msgid ""
+"References to \"policy makers\", \"managers\", and \"developers and "
+"designers\" apply to anyone performing duties associated with these roles, "
+"regardless of their job title. It is common for individuals to have duties "
+"which span multiple roles."
+msgstr ""
+
+#: ./readers-guide.md:block 6 (paragraph)
+msgid ""
+"Below is a brief explanation of each of these sections and how they are used"
+" within the criteria of the Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 7 (header)
+msgid "Introduction"
+msgstr ""
+
+#: ./readers-guide.md:block 8 (paragraph)
+msgid ""
+"This section explains what the criterion aims to achieve and why it is "
+"important for a codebase's users and contributors."
+msgstr ""
+
+#: ./readers-guide.md:block 10 (paragraph)
+msgid ""
+"This section lists what needs to be done in order to comply with the "
+"standard."
+msgstr ""
+
+#: ./readers-guide.md:block 11 (paragraph)
+msgid ""
+"The following keywords in this document are to be interpreted as described "
+"in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "REQUIRED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD NOT"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "RECOMMENDED"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MAY"
+msgstr ""
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "OPTIONAL"
+msgstr ""
+
+#: ./readers-guide.md:block 14 (paragraph)
+msgid ""
+"This section offers actions you can take to see if a contribution is "
+"compliant with the Standard. This is key if you want to operationalize the "
+"Standard."
+msgstr ""
+
+#: ./readers-guide.md:block 15 (paragraph)
+msgid ""
+"We've tried to word it so that someone who is not intimately acquainted with"
+" the subject matter can still do a basic check for compliance."
+msgstr ""
+
+#: ./readers-guide.md:block 17 (paragraph)
+msgid ""
+"This section tries to specifically speak to policy makers by offering them "
+"concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 18 (paragraph)
+msgid ""
+"Public policy makers set the priorities and goals of projects and may be "
+"less technologically experienced."
+msgstr ""
+
+#: ./readers-guide.md:block 20 (paragraph)
+msgid ""
+"This section tries to specifically speak to managers by offering concrete "
+"actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 21 (paragraph)
+msgid ""
+"Managers are responsible for on-time project delivery, stakeholder "
+"management and continued delivery of the service. For this they are wholly "
+"reliant on both policy makers as well as developers and designers. They need"
+" to create the right culture, line up the right resources and provide the "
+"right structures to deliver great services."
+msgstr ""
+
+#: ./readers-guide.md:block 23 (paragraph)
+msgid ""
+"This section tries to specifically speak to developers and designers by "
+"offering them concrete actions they can perform in their role."
+msgstr ""
+
+#: ./readers-guide.md:block 24 (paragraph)
+msgid ""
+"Developers are usually more technically aligned and have more impact on the "
+"delivery of services than the previous groups."
+msgstr ""
+
+#: ./readers-guide.md:block 25 (header)
+msgid "Limitation of scope"
+msgstr ""
+
+#: ./readers-guide.md:block 26 (paragraph)
+msgid ""
+"The Standard for Public Code is not meant to cover individual "
+"implementations of a codebase. This means the standard does not tell "
+"implementers how to comply with their organization's local technical "
+"infrastructure or legal framework."
+msgstr ""
+
+#: ./readers-guide.md:block 27 (paragraph)
+msgid ""
+"Also, while the Standard for Public Code refers to several standards and has"
+" considerable overlap with others, its purpose is to enable collaboration. "
+"Therefore, it does not aim to replace quality standards, like the ISO 25000 "
+"series, or those focusing on security, like the [OpenSSF Best Practices "
+"Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
+"synergize well with them."
+msgstr ""
+
+#: ./readers-guide.md:block 28 (paragraph)
+msgid ""
+"And while the purpose includes enabling collaboration, it will not guarantee"
+" that a community will spring into existence. That still requires "
+"proactiveness and ambition beyond making the codebase collaboration ready."
+msgstr ""
diff --git a/_site/locales/zh_Hant/LC_MESSAGES/messages.po b/_site/locales/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..ae369f9a
--- /dev/null
+++ b/_site/locales/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,6304 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2023-07-30 22:44+0800\n"
+"PO-Revision-Date: 2023-11-03 06:41+0000\n"
+"Last-Translator: Winnie <winnie@steps.com.tw>\n"
+"Language-Team: Chinese (Traditional) <http://weblate.steps.tw/projects/"
+"standard-for-public-code/standard-for-public-code/zh_Hant/>\n"
+"Language: zh_Hant\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Generator: Weblate 4.18.2\n"
+
+#
+#: ./404.md:block 1 (header)
+msgid "SPDX-License-Identifier: CC0-1.0"
+msgstr "SPDX-License-Identifier: CC0-1.0"
+
+#: ./404.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+"SPDX-FileCopyrightText: 2022-2023 Foundation for Public Code [info@publiccode"
+".net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+
+#: ./404.md:block 3 (header)
+msgid ""
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
+msgstr ""
+"layout: default\n"
+"title: Page not found\n"
+"toc: false"
+
+#: ./404.md:block 4 (header)
+msgid "404 Not Found"
+msgstr "404 找不到網頁"
+
+#: ./404.md:block 5 (paragraph)
+msgid "If you typed the web address, check it is correct."
+msgstr "如果您是手動輸入網址，請確認網址是否正確。"
+
+#: ./404.md:block 6 (paragraph)
+msgid "If you pasted the web address, check you copied the entire address."
+msgstr "如果您是複製貼上此網址，請確認是否有複製到完整的網址。"
+
+#: ./404.md:block 7 (paragraph)
+msgid ""
+"If the web address is correct or you followed a link or button, email the "
+"[Foundation for Public Code staff](mailto:info@publiccode.net) so we'll be "
+"able to help you out, as well as correct our mistake."
+msgstr ""
+"若網址正確，或您是按下連結或按鈕來的，請寫信給 [Foundation for Public Code "
+"員工](mailto:info@publiccode.net)，讓我們協助您，並同時修正我們的錯誤。"
+
+#: ./AUTHORS.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+"SPDX-FileCopyrightText: 2019-2023 Foundation for Public Code [info@publiccode"
+".net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+
+#: ./AUTHORS.md:block 3 (header)
+msgid "Authors"
+msgstr "作者群"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Alba Roza, [The Foundation for Public Code](https://publiccode.net/)"
+msgstr "Alba Roza，[Foundation for Public Code](https://publiccode.net/)"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Engelen"
+msgstr "Arnout Engelen"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Arnout Schuijff, The Foundation for Public Code"
+msgstr "Arnout Schuijff，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Audrey Tang, [digitalminister.tw](https://digitalminister.tw/)"
+msgstr "唐鳳，[數位發展部](https://digitalminister.tw/)"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ben Cerveny, The Foundation for Public Code"
+msgstr "Ben Cerveny，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Bert Spaan"
+msgstr "Bert Spaan"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Boris van Hoytema, The Foundation for Public Code"
+msgstr "Boris van Hoytema，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Charlotte Heikendorf"
+msgstr "Charlotte Heikendorf"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Claus Mullie, The Foundation for Public Code"
+msgstr "Claus Mullie，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "David Barberi"
+msgstr "David Barberi"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Edo Plantinga, [Code For NL](https://codefor.nl/)"
+msgstr "Edo Plantinga，[Code For NL](https://codefor.nl/)"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Elena Findley-de Regt, The Foundation for Public Code"
+msgstr "Elena Findley-de Regt，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Eric Herman, The Foundation for Public Code"
+msgstr "Eric Herman，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Felix Faassen, The Foundation for Public Code"
+msgstr "Felix Faassen，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Floris Deerenberg"
+msgstr "Floris Deerenberg"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Jan Ainali, The Foundation for Public Code"
+msgstr "Jan Ainali，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Johan Groenen, Code For NL"
+msgstr "Johan Groenen，Code For NL"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Marcus Klaas de Vries"
+msgstr "Marcus Klaas de Vries"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mark van der Net, [Gemeente Amsterdam](https://www.amsterdam.nl/en/)"
+msgstr "Mark van der Net，[阿姆斯特丹市政府](https://www.amsterdam.nl/en/)"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Martijn de Waal, [Amsterdam University of Applied Sciences "
+"(AUAS)](https://www.amsterdamuas.com/), Faculty of Digital Media and "
+"Creative Industries, Lectorate of Play & Civic Media"
+msgstr ""
+"Martijn de Waal，[阿姆斯特丹應用科技大學 (AUAS)](https://www.amsterdamuas."
+"com/)，數位媒體與創意產業學院，戲劇與公民媒體系講師"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Matti Schneider"
+msgstr "Matti Schneider"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mauko Quiroga"
+msgstr "Mauko Quiroga"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurice Hendriks, Gemeente Amsterdam"
+msgstr "Maurice Hendriks， 阿姆斯特丹市政府"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Maurits van der Schee, Gemeente Amsterdam"
+msgstr "Maurits van der Schee，阿姆斯特丹市政府"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Mirjam van Tiel, The Foundation for Public Code"
+msgstr "Mirjam van Tiel，Foundation for Public Code"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Ngô Ngọc Đức Huy"
+msgstr "Ngô Ngọc Đức Huy"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Paul Keller"
+msgstr "Paul Keller"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid ""
+"Petteri Kivimäki, [Nordic Institute for Interoperability Solutions "
+"(NIIS)](https://niis.org)"
+msgstr "Petteri Kivimäki， [北歐互通性解決方案機構 (NIIS)](https://niis.org)"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Sky Bristol"
+msgstr "Sky Bristol"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Tamas Erkelens, Gemeente Amsterdam"
+msgstr "Tamas Erkelens，阿姆斯特丹市政府"
+
+#: ./AUTHORS.md:block 4 (unordered list)
+msgid "Timo Slinger"
+msgstr "Timo Slinger"
+
+#: ./CC0-1.0.md:block 3 (header)
+msgid "toc: false redirect_from: - license.html - LICENSE.html"
+msgstr "toc: false redirect_from: - license.html - LICENSE.html"
+
+#: ./CC0-1.0.md:block 4 (header)
+msgid "Creative Commons Zero v1.0 Universal"
+msgstr "創用 CC0 1.0 通用授權"
+
+#: ./CC0-1.0.md:block 6 (paragraph)
+msgid ""
+"This license is the legal contract that allows anyone to do anything they "
+"like with the content in this entire document."
+msgstr "此授權的法律契約，允許任何人任意使用本文件中的任何內容。"
+
+#: ./CHANGELOG.md:block 3 (header)
+msgid "Version history"
+msgstr "版本歷史"
+
+#: ./CHANGELOG.md:block 5 (header)
+msgid "Version 0.7.0"
+msgstr "0.7.0 版"
+
+#: ./CHANGELOG.md:block 6 (paragraph)
+msgid ""
+"May 31st 2023: 📑 the fifteenth draft adds new requirements for documenting "
+"review funding and clarifies review process requirement."
+msgstr "2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Add requirement to document who is expected to cover the cost of reviewing "
+"contributions."
+msgstr "新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Add requirement to have a short description of the codebase."
+msgstr "新增規定，程式基底必須要有簡短說明。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid ""
+"Change the focus of contributions adhering to standards to focus on the "
+"review of contributions."
+msgstr "原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Relaxed MUST requirements to SHOULD in Make the codebase findable."
+msgstr "將〈程式基底可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Review template now in HTML format."
+msgstr "審查範本現在有 HTML 格式。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Introduction converted to foreword."
+msgstr "「前言」轉換為「序文」。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved contributing guidelines."
+msgstr "改善貢獻指引。"
+
+#: ./CHANGELOG.md:block 7 (unordered list)
+msgid "Improved documentation of scripts."
+msgstr "改善命令稿文件紀錄。"
+
+#: ./CHANGELOG.md:block 8 (header)
+msgid "Version 0.6.0"
+msgstr "0.6.0 版"
+
+#: ./CHANGELOG.md:block 9 (paragraph)
+msgid ""
+"April 20th 2023: 🔀 the fourteenth draft adds new requirements for "
+"portability and tests and an introduction to each criterion."
+msgstr "2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且每個準則都有一段前"
+"言。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about the development "
+"being a collaboration between multiple parties."
+msgstr "新增規定，在〈程式碼要可重複使用且可攜〉加入多方協作開發的內容。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Create reusable and portable code about being dependent "
+"on a single vendor."
+msgstr "新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"New requirement in Use continuous integration about publishing results for "
+"automated tests."
+msgstr "新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Differentiating the two requirements about security to clearly be about "
+"providing a method and having documentation about it."
+msgstr "對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Rephrased requirements to focus on the codebase rather than contributor "
+"behavior."
+msgstr "重新撰寫規定，將焦點放在程式基底，而非貢獻者行為。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Removed the sections Why this is important and What this does not do and "
+"replaced with an introduction in each criterion."
+msgstr "移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加"
+"入前言。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added general What this does not do section in the introduction of the "
+"Standard."
+msgstr "在本標準前言中，加入通用的「此措施辦不到的事」小節。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for public policy makers about related policies and license "
+"compatibility."
+msgstr "為政策制定者加入相關政策與授權相容性的指引。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Added guidance for developers and designers about version controlling files."
+msgstr "為開發人員與設計師新增檔案要有版本控制的相關指引。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Clarified guidance for developers and designers about prompt responses and "
+"search engine optimization."
+msgstr "為開發人員與設計師釐清有關快速回應，以及搜尋引擎最佳化的內容。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added Further reading about accessibility."
+msgstr "新增可近用性無障礙環境的「延伸閱讀」內容。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Aligned criteria URLs with criteria names."
+msgstr "將各準則的連結與其名稱連動。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Improved navigation in the web version."
+msgstr "改善網頁版的導覽功能。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved tools in Further reading sections to the community implementation "
+"guide."
+msgstr "已將「延伸閱讀」小節的工具移到社群實踐指引。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Moved compliance or certification process to "
+"[publiccode.net](https://publiccode.net)."
+msgstr "將標準依循或認證相關流程移到 [publiccode.net](https://publiccode.net)。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Change format of the review template to make it easier to update after a new"
+" release."
+msgstr "變更審查範本格式，讓範本在發行新版後更容易更新。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid ""
+"Improved the text on the landing page and added links to related resources."
+msgstr "改善著陸引導頁文字，加入相關資源的連結。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Added spell checker automated test."
+msgstr "新增拼字檢查自動化測試。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Made minor changes to text for clarity and consistency."
+msgstr "微調文字，讓內容更明確與一致。"
+
+#: ./CHANGELOG.md:block 10 (unordered list)
+msgid "Moved SPDX headers to yaml header."
+msgstr "將 SPDX 標頭換成 yaml 標頭。"
+
+#: ./CHANGELOG.md:block 11 (header)
+msgid "Version 0.5.0"
+msgstr "0.5.0 版"
+
+#: ./CHANGELOG.md:block 12 (paragraph)
+msgid ""
+"January 25th 2023: 🎨 the thirteenth draft focuses on documenting style "
+"guidelines."
+msgstr "2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。"
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust the coding style requirement to focus on the codebase using a style "
+"guide rather than contributor behavior."
+msgstr "調整程式碼撰寫風格要求，專注於程式基底上，而非貢獻者行為。"
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement for codebase names to Make the codebase findable from Use "
+"plain English."
+msgstr "將程式基底名稱規定，從〈使用白話的英文〉移到〈程式基底可查詢得到〉。"
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Moved requirement about testing the code by using examples to Use continuous"
+" integration from Document the code."
+msgstr "將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。"
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Split requirement about machine testable standards to clarify that open is "
+"more important than testable."
+msgstr "劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。"
+
+#: ./CHANGELOG.md:block 13 (unordered list)
+msgid ""
+"Adjust how to test findability requirements to be less reliant on search "
+"engine algorithms."
+msgstr "調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。"
+
+#: ./CHANGELOG.md:block 14 (header)
+msgid "Version 0.4.1"
+msgstr "0.4.1 版"
+
+#: ./CHANGELOG.md:block 15 (paragraph)
+msgid "December 5th 2022: 📝 the twelfth draft clarifies document maturity."
+msgstr "2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity focuses on whether or not versions of the codebase are "
+"ready to use."
+msgstr "寫下成熟度著重於程式基底是否已經可供使用，更甚於版本編號。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Document maturity no longer requires specific labels for codebases that are "
+"not ready to use."
+msgstr "寫下成熟度不再需要為尚未準備好可供使用的程式基底加上特定標籤。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Audit flow image now generated from an easier to translate format."
+msgstr "稽核流程圖現在以更容易轉譯的格式生成。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Improved guidance on How to test."
+msgstr "改善「測試方式」指引。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add publiccode.yml file."
+msgstr "新增 publiccode.yml 檔案。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add review template."
+msgstr "新增審查範本。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Consistently link glossary terms."
+msgstr "一致性連結詞彙表。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add practices and standards to follow in CONTRIBUTING."
+msgstr "在「CONTRIBUTING」中加入要遵循的實務與標準。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add Matti Schneider to Authors."
+msgstr "將 Matti Schneider 加入作者群。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Add remaining SPDX headers to files."
+msgstr "將剩餘 SPDX 標頭加入檔案中。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Made additional minor changes to text for clarity."
+msgstr "再稍微修改些文字，讓文字更明確。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid "Some hyperlinks updated."
+msgstr "更新部分超連結。"
+
+#: ./CHANGELOG.md:block 16 (unordered list)
+msgid ""
+"Moved examples to the [Community implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/)."
+msgstr ""
+"將範例移動到《[社群實踐指引](https://publiccodenet.github.io/"
+"community-implementation-guide-standard/)》。"
+
+#: ./CHANGELOG.md:block 17 (header)
+msgid "Version 0.4.0"
+msgstr "0.4.0 版"
+
+#: ./CHANGELOG.md:block 18 (paragraph)
+msgid ""
+"September 7th 2022: 🔭 the eleventh draft adds a new findability criterion."
+msgstr "2022年9月7日：🔭第十一版草稿新增可查找性準則。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduce new criterion: Make the codebase findable."
+msgstr "導入新準則：程式基底可查詢得到。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Improve How to test section for most criteria."
+msgstr "改善多數準則的「測試方式」小節。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"New requirement in Welcome contributors about publishing activity "
+"statistics."
+msgstr "在〈歡迎貢獻者〉中加入發布活動統計的新規定。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Removed redundant requirement about portable and reusable code."
+msgstr "移除可重複使用與移植的程式碼中多餘的規定。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expand open license definition to include both OSI and FSF approved "
+"licenses."
+msgstr "在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Rephrase MAY requirements to use the keyword OPTIONAL for clarity."
+msgstr "重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Expressed intent that the Standard for Public Code should meet its own "
+"requirements where applicable and added assessment."
+msgstr "表達《公共程式標準》應該盡可能符合其自身規定的立場，並加入評估措施。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add SPDX license identifiers to files."
+msgstr "將 SPDX 授權識別碼加入檔案中。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Introduced new Code of Conduct."
+msgstr "導入新的行為守則。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify distinction between source code and policy text."
+msgstr "解釋原始碼與政策內文的差異。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Restructuring of requirements with bullet point lists."
+msgstr "將規定重新調整為項目要點清單格式。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Acknowledge the importance of codebase modularity for reuse."
+msgstr "告知程式基底成熟度對於重複使用時的重要性。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Move requirements related to Findability to the new criterion."
+msgstr "將可查找性相關規定移動到新準則中。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Clarify the role of non-open standards when used in a codebase."
+msgstr "釐清非開放標準在程式基底中的角色。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Additional guidance about build-time and runtime dependencies."
+msgstr "加入組建日期與執行時期依賴項目的額外指引。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added roadmap for the development of the Standard for Public Code."
+msgstr "新增《公共程式標準》的發展路線圖。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Update structure of Authors file."
+msgstr "更新 Authors 檔案的結構。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Add Audrey Tang to Authors."
+msgstr "將唐鳳加入作者群。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid "Added a list of criteria to the print edition."
+msgstr "將準則列表加到印刷版本中。"
+
+#: ./CHANGELOG.md:block 19 (unordered list)
+msgid ""
+"Clarify what the standard means with policymakers, managers, developers and "
+"designers."
+msgstr "釐清標準對於政策制定者、管理人員、開發人員與設計師等不同身分間的意義。"
+
+#: ./CHANGELOG.md:block 20 (header)
+msgid "Version 0.3.0"
+msgstr "0.3.0 版"
+
+#: ./CHANGELOG.md:block 21 (paragraph)
+msgid ""
+"May 23rd 2022: 🗎 the tenth draft strengthens documentation and localization."
+msgstr "2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內容。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Requirement for localization made explicit in Create reusable and portable "
+"code."
+msgstr "在〈程式碼要可重複使用且可攜〉中定下明確的在地化規定。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Documentation of governance changed from a SHOULD to a MUST."
+msgstr "以文件記錄治理方式的規定，從「應該」等級調升為「必須」。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid ""
+"Replace the very subjective (and hard to test) \"contributions MUST be "
+"small\" with requirement to document expectation in contributing guidelines "
+"and focus on a single issue."
+msgstr "在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容『必須』小」的規定，改為必"
+"須紀錄貢獻所要完成的期待，並一次專注在單一議題上。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Community translations now linked in the footer."
+msgstr "社群翻譯連結現在已放到頁尾中。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Revert \"Replace BPMN svg with Mermaid flowchart\"."
+msgstr "還原「用 Mermaid 流程圖取代業務流程 BPMN svg」。"
+
+#: ./CHANGELOG.md:block 22 (unordered list)
+msgid "Many minor clarifications to language and sentences made more simple."
+msgstr "細微調整用詞，讓句子更簡單。"
+
+#: ./CHANGELOG.md:block 23 (header)
+msgid "Version 0.2.3"
+msgstr "0.2.3 版"
+
+#: ./CHANGELOG.md:block 24 (paragraph)
+msgid ""
+"March 15th 2022: 📜 the ninth draft allows English summaries for policy "
+"lacking an official translation."
+msgstr "2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策，改為提供政策的英文版摘要。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Relax the criterion Use plain English by adding a new requirement allows "
+"bundled policy not available in English to have an accompanying summary in "
+"English instead of translating the full text."
+msgstr "放寬〈使用白話的英文〉準則，加入新規定，允許合捆的政策內文如果沒有英文版，只"
+"需要加入英文版摘要，而不用翻譯全文。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Similarly, allow for English summaries for policies not available in English"
+" in Bundle policy and code."
+msgstr "同樣地，在〈政策與原始碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要"
+"。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Clarify that term 'policy' includes processes which impact development and "
+"deployment in Bundle policy and code."
+msgstr "釐清〈政策與原始碼要合捆〉中，「政策」包含能影響開發與部署的流程。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Emphasize reusability also on parts of the solutions in Create reusable and "
+"portable code."
+msgstr "在〈程式碼要可重複使用且可攜〉中強調解決方案部分內容的可重複使用性。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Expand guidance to Developers and designers in Create reusable and portable "
+"code about deploying to proprietary platforms."
+msgstr "將〈程式碼要可重複使用且可攜〉當中的開發人員與設計師指引，加入部署到專有平台"
+"上的內容。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Add nuance to use of non-English terms in what management need to do in Use "
+"plain English."
+msgstr "在〈使用白話的英文〉中，加入管理層在面對非英語詞彙時需要做的事的提點。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid ""
+"Change the pull request process diagram to use Mermaid instead of BPMN to "
+"make [community translations](https://github.com/publiccodenet/community-"
+"translations-standard) easier."
+msgstr ""
+"變更拉取請求流程圖，從業務流程 BPMN 改用 "
+"Mermaid，來讓[社群翻譯](https://github.com/publiccodenet/community-"
+"translations-standard)更容易。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added Maurice Hendriks to AUTHORS."
+msgstr "將 Maurice Hendriks 加入作者群。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Added OpenApi Specification to further reading."
+msgstr "將「OpenApi 規格」加入延伸閱讀。"
+
+#: ./CHANGELOG.md:block 25 (unordered list)
+msgid "Made the attributions in further reading sections clearer."
+msgstr "將延伸閱讀小節的特性變得更明確。"
+
+#: ./CHANGELOG.md:block 26 (header)
+msgid "Version 0.2.2"
+msgstr "0.2.2 版"
+
+#: ./CHANGELOG.md:block 27 (paragraph)
+msgid ""
+"November 29th 2021: 🏛 the eighth draft recognizes that policy which executes"
+" as code may not be in English."
+msgstr "2021年11月29日：🏛第八版草稿認知程式碼所執行的政策，不一定是英文。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Document exception to \"All code MUST be in English\" where policy is "
+"interpreted as code."
+msgstr "在「所有程式碼都必須使用英語編寫」規定中，雖然政策也算是一種程式 "
+"(code)，但可以保有例外。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Add MAY requirement regarding committer email addresses in Maintain version "
+"control."
+msgstr "在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以」規定。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Policy Makers in Bundle policy and code."
+msgstr "將政策制定者加入〈政策與原始碼要合捆〉指引中。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Expand guidance to Developers and designers in Use a coherent style."
+msgstr "將開發人員與設計師加入「風格要前後一致」指引中。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add \"Different contexts\" to glossary."
+msgstr "新增「不同情境」到詞彙表中。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Mauko Quiroga and Charlotte Heikendorf to AUTHORS."
+msgstr "將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Digital Public Goods approval badge."
+msgstr "新增「數位公共財」認可標章。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Added \"next\" and \"previous\" links to criteria pages of web version."
+msgstr "為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Open Standards principles to further reading."
+msgstr "將「開放標準」原則加入延伸閱讀。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add Definition of plain language to further reading."
+msgstr "將「白話語言定義」加入延伸閱讀。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Move the Semantic Versioning Specification further reading reference."
+msgstr "將「語意化版本編號規範」移動為延伸閱讀參考內容。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid ""
+"Clarify that publiccode.yml is one example of a machine-readable metadata "
+"description."
+msgstr "指出 publiccode.yml 是機器可讀中介資料說明的範例之一。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Changed \"your codebase\" and \"your organization\" to be less possessive."
+msgstr "將「您的程式基底」與「您的組織單位」改為較不具有所有格的寫法。"
+
+#: ./CHANGELOG.md:block 28 (unordered list)
+msgid "Add instructions for creating a print version."
+msgstr "新增印刷版的製作指示。"
+
+#: ./CHANGELOG.md:block 29 (header)
+msgid "Version 0.2.1"
+msgstr "0.2.1 版"
+
+#: ./CHANGELOG.md:block 30 (paragraph)
+msgid ""
+"March 1st 2021: 🧽 the seventh draft has minor cleaning up after version "
+"0.2.0."
+msgstr "2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改善。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"New SHOULD requirement on using a distributed version control system and why"
+" distributed is important."
+msgstr "新增使用分散式版本控制系統的相關「應該」規定，並解釋分散式的重要性。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Feedback requirements for rejected contributions are more strict than "
+"accepted ones."
+msgstr "針對未被採用的貢獻需要給予回饋，規定要比被接受的貢獻更加嚴格。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Specify that copyright and license notices should also be machine-readable."
+msgstr "明確指出著作權與授權聲明也應該要機器可讀。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Advice on how to test that notices be machine-readable."
+msgstr "聲明是否為機器可讀的測試方式建議。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clarify guidance for rolling releases."
+msgstr "釐清滾動發行的指引。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Clear up definition of version control in glossary."
+msgstr "釐清詞彙表中「版本控制」的定義。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid ""
+"Add further reading encouraging contribution, SPDX, Git and reviewing "
+"contributions."
+msgstr "新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項目。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add links to videos about the concept of public code."
+msgstr "新增有關公共程式概念的影片連結。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Update BPMN link."
+msgstr "更新業務流程 BPMN 連結。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Reduce link duplication."
+msgstr "減少重複連結。"
+
+#: ./CHANGELOG.md:block 31 (unordered list)
+msgid "Add Alba Roza and Ngô Ngọc Đức Huy to authors."
+msgstr "將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。"
+
+#: ./CHANGELOG.md:block 32 (header)
+msgid "Version 0.2.0"
+msgstr "0.2.0 版"
+
+#: ./CHANGELOG.md:block 33 (paragraph)
+msgid ""
+"October 26th 2020: 🎊 the sixth draft splits a requirement and adds clarity."
+msgstr "2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Split \"Welcome contributions\" criterion into \"Make contributing easy\" "
+"and \"Welcome contributors\"."
+msgstr "將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Rename criterion \"Pay attention to codebase maturity\" to \"Document "
+"codebase maturity\"."
+msgstr "將〈注意程式基底成熟度〉準則改名為〈記錄程式基底成熟度〉。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Changed MUST to SHOULD for requirement of codebase in use by multiple "
+"parties."
+msgstr "針對多方使用的程式基底，將「必須」等級規定調降為「應該」。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add MUST NOT requirement regarding copyright assignment."
+msgstr "針對著作權轉讓，新增「禁止」規定。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Clarify role of configuration in reusable code requirement."
+msgstr "在可重複使用程式碼的規定中，釐清組態設定的角色。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Glossary additions: continuous integration, policy, repository, and version "
+"control."
+msgstr "新增詞彙：持續整合、政策、儲存庫、版本控制等。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Replace references to 'cities' with 'public organizations'."
+msgstr "將「城市」替換成「公家機關」。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Clarify aspects of sensitive code by separating contributor and reviewer "
+"requirements into separate items."
+msgstr "將貢獻者與審查人員規定分開為不同項目，以釐清程式碼中較敏感性的層面。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid ""
+"Expand further reading, and guidance to policy makers, developers and "
+"designers."
+msgstr "將政策制定者、開發人員與設計師加入延伸閱讀與指引中。"
+
+#: ./CHANGELOG.md:block 34 (unordered list)
+msgid "Add Felix Faassen and Arnout Engelen to authors."
+msgstr "將 Felix Faassen 與 Arnout Engelen 加入作者群。"
+
+#: ./CHANGELOG.md:block 35 (header)
+msgid "Version 0.1.4"
+msgstr "0.1.4 版"
+
+#: ./CHANGELOG.md:block 36 (paragraph)
+msgid ""
+"November 27th 2019: 🧹 the fifth draft consists mostly of additional minor "
+"fixes."
+msgstr "2019年11月27日：🧹第五版草稿主要是一些細部修正。"
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Linked License.md file."
+msgstr "連結 License.md 檔案。"
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Add Sky Bristol, Marcus Klaas de Vries, and Jan Ainali to authors."
+msgstr "將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。"
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made punctuation more consistent, especially for bullet lists."
+msgstr "讓標點符號使用更一致，特別是項目符號列表。"
+
+#: ./CHANGELOG.md:block 37 (unordered list)
+msgid "Made some minor changes to text for clarity."
+msgstr "細部調整文字，讓內容更明確。"
+
+#: ./CHANGELOG.md:block 38 (header)
+msgid "Version 0.1.3"
+msgstr "0.1.3 版"
+
+#: ./CHANGELOG.md:block 39 (paragraph)
+msgid ""
+"October 8th 2019: 🍂 the fourth draft only patches and fixes minor things for"
+" the autumn cleaning"
+msgstr "2019年10月8日：🍂第四版草稿僅針對秋季所作的清理修正一些小地方"
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Renamed continuous delivery to continuous integration."
+msgstr "將「持續交付」改名為「持續整合」。"
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "Referencing accessibility guidelines in the language standard."
+msgstr "在語言標準中引用無障礙指導原則。"
+
+#: ./CHANGELOG.md:block 40 (unordered list)
+msgid "A bunch of style and consistency fixes."
+msgstr "改善一些樣式，與一致性修正。"
+
+#: ./CHANGELOG.md:block 41 (header)
+msgid "Version 0.1.2"
+msgstr "0.1.2 版"
+
+#: ./CHANGELOG.md:block 42 (paragraph)
+msgid ""
+"August 22th 2019: 🌠 the third draft focuses on better text and takes "
+"community input"
+msgstr "2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "With some great new contributors comes a fresh author list."
+msgstr "有好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "All links are now HTTPS."
+msgstr "所有連結都是 HTTPS。"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "General proofreading, wording clarifications, and smashed typos."
+msgstr "一般校對、釐清用字淺詞、修正拼字錯誤等。"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Updated criteria:"
+msgstr "更新準則："
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Requirement for reuse in different contexts"
+msgstr "在不同情境背景下重複使用的規定"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit versioning"
+msgstr "明確的版本控制建議"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for multi party development"
+msgstr "多方部署的建議"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for license headers in files"
+msgstr "檔案授權標頭的建議"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for vulnerability reporting"
+msgstr "漏洞回報的建議"
+
+#: ./CHANGELOG.md:block 43 (unordered list)
+msgid "Recommendation for explicit documentation of governance"
+msgstr "明確以文件記錄治理方式的建議"
+
+#: ./CHANGELOG.md:block 44 (header)
+msgid "Version 0.1.1"
+msgstr "0.1.1 版"
+
+#: ./CHANGELOG.md:block 45 (paragraph)
+msgid ""
+"May 9th 2019: 🤔 the second draft fixes a few basic oversights and fixes a "
+"lot of typos"
+msgstr "2019年5月9日：🤔第二版草稿修正一些基本的疏漏，以及許多拼字錯誤"
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid ""
+"Removed references to the Foundation for Public Code, we're going to have to"
+" change the name in becoming an association."
+msgstr "移除出現「Foundation for Public "
+"Code」的地方，我們之後可能必須改名才能成為協會。"
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the introduction."
+msgstr "更新簡介。"
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Updated the glossary."
+msgstr "更新詞彙表。"
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "Added the code of conduct."
+msgstr "新增行為守則。"
+
+#: ./CHANGELOG.md:block 46 (unordered list)
+msgid "We've recommended using the publiccode.yml standard for easier reuse."
+msgstr "我們建議使用 publiccode.yml 標準，方便重複使用。"
+
+#: ./CHANGELOG.md:block 47 (header)
+msgid "Version 0.1.0"
+msgstr "0.1.0 版"
+
+#: ./CHANGELOG.md:block 48 (paragraph)
+msgid ""
+"April 16th 2019: 🎉 the first draft is ready, it is all brand new and has "
+"snazzy new ideas in it"
+msgstr "2019年4月16日：🎉初版草稿已準備就緒，全新內容，而且有許多有趣的新穎理念"
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid "14 criteria with their requirements and how to operationalize them."
+msgstr "14 項準則，有各自的規定，以及相關的實施方式。"
+
+#: ./CHANGELOG.md:block 49 (unordered list)
+msgid ""
+"An introduction with a high level background, what this standard is, and how"
+" the Foundation for Public Code will use it."
+msgstr "精要的背景介紹，例如本標準是什麼，以及 Foundation for Public Code "
+"如何使用此標準。"
+
+#: ./CHANGELOG.md:block 50 (paragraph)
+msgid ""
+"This first version was produced together with the Amsterdam University of "
+"Applied Sciences and the City of Amsterdam as a part of the [Smart Cities? "
+"Public Code! project](https://smartcities.publiccode.net/)."
+msgstr ""
+"最初的版本是由阿姆斯特丹應用科學大學、阿姆斯特丹市政府，以及本基金會合作撰寫"
+"，取自 [Smart Cities? Public Code! 專案](https://smartcities.publiccode.net/)"
+" 的部分內容。"
+
+#: ./CODE_OF_CONDUCT.md:block 1 (header)
+msgid "Code of Conduct"
+msgstr "行為守則"
+
+#: ./CODE_OF_CONDUCT.md:block 3 (paragraph)
+msgid ""
+"Many community members are from civic or professional environments with "
+"behavioral codes yet some individuals are not. This document expresses "
+"expectations of all community members and all interactions regardless of "
+"communication channel."
+msgstr ""
+"社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達"
+"基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。"
+
+#: ./CODE_OF_CONDUCT.md:block 4 (paragraph)
+msgid "Be here to collaborate."
+msgstr "來到這裡來是為了協作。"
+
+#: ./CODE_OF_CONDUCT.md:block 5 (paragraph)
+msgid "Be considerate, respectful, and patient."
+msgstr "請對彼此體貼、尊重，以及有耐心。"
+
+#: ./CODE_OF_CONDUCT.md:block 6 (paragraph)
+msgid "Strive to be as constructive as possible."
+msgstr "努力做出有建設性的行為。"
+
+#: ./CODE_OF_CONDUCT.md:block 7 (paragraph)
+msgid "To raise a concern, please email directors@publiccode.net."
+msgstr "若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。"
+
+#: ./CONTRIBUTING.md:block 1 (header)
+msgid "Contributing to this standard"
+msgstr "貢獻此標準"
+
+#: ./CONTRIBUTING.md:block 3 (paragraph)
+msgid "🙇‍♀️ Thank you for contributing!"
+msgstr "🙇‍♀️ 感謝您的貢獻！"
+
+#: ./CONTRIBUTING.md:block 4 (paragraph)
+msgid ""
+"We understand that a standard like this can only be set in collaboration "
+"with as many public technologists, policy makers and interested folk as "
+"possible. Thus we appreciate your input, enjoy feedback and welcome "
+"improvements to this project and are very open to collaboration."
+msgstr ""
+"我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士"
+"協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專"
+"案的建議。我們非常開放任何合作的機會。"
+
+#: ./CONTRIBUTING.md:block 5 (paragraph)
+msgid ""
+"We love issues and pull requests from everyone. If you're not comfortable "
+"with GitHub, you can email use your feedback at "
+"[info@publiccode.net](mailto:info@publiccode.net)."
+msgstr ""
+"我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，"
+"也歡迎將意見回饋用電子郵件寄送到 [info@publiccode.net](mailto:info@publiccode"
+".net)。"
+
+#: ./CONTRIBUTING.md:block 6 (header)
+msgid "Problems, suggestions and questions in issues"
+msgstr "問題、建議與議題等"
+
+#: ./CONTRIBUTING.md:block 7 (paragraph)
+msgid ""
+"A high-level overview of the development that we already have sketched out "
+"can be seen in the [roadmap](/docs/roadmap.md). Please help development by "
+"reporting problems, suggesting changes and asking questions. To do this, you"
+" can [create a GitHub issue](https://docs.github.com/en/issues/tracking-"
+"your-work-with-issues/creating-an-issue) for this project in the [GitHub "
+"Issues for the Standard for Public "
+"Code](https://github.com/publiccodenet/standard/issues)."
+msgstr ""
+"在[發展路線圖](/docs/roadmap.md)中可查看我們勾勒的精要概覽。歡迎回報問題、建"
+"議修改，以及發問等，來協助發展。您可以到 [Standard for Public Code 的 GitHub "
+"Issue](https://github.com/publiccodenet/standard/issues) 頁面中，為本專案["
+"提出 GitHub 議題](https://docs.github.com/en/issues/"
+"tracking-your-work-with-issues/creating-an-issue)。"
+
+#: ./CONTRIBUTING.md:block 8 (paragraph)
+msgid ""
+"Or, sign up to the [mailing "
+"list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)"
+" and send an email to "
+"[standard@lists.publiccode.net](mailto:standard@lists.publiccode.net)."
+msgstr ""
+"或者，註冊加入[郵遞論壇列表](https://lists.publiccode.net/mailman/postorius/"
+"lists/standard.lists.publiccode.net/)，並寄送電子郵件到[standard@lists."
+"publiccode.net](mailto:standard@lists.publiccode.net)。"
+
+#: ./CONTRIBUTING.md:block 9 (paragraph)
+msgid ""
+"You don't need to change any of our code or documentation to be a "
+"contributor!"
+msgstr "您不一定要修改我們的程式碼或文件，也能成為貢獻者！"
+
+#: ./CONTRIBUTING.md:block 10 (header)
+msgid "Documentation and code in pull requests"
+msgstr "為文件與程式碼提出拉取請求"
+
+#: ./CONTRIBUTING.md:block 11 (paragraph)
+msgid ""
+"If you want to add to the documentation or code of one of our projects you "
+"should make a pull request."
+msgstr "如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull "
+"Request，亦可簡稱 PR)。"
+
+#: ./CONTRIBUTING.md:block 12 (paragraph)
+msgid ""
+"If you never used GitHub, get up to speed with [Understanding the GitHub "
+"flow](https://docs.github.com/en/get-started/quickstart/github-flow) or "
+"follow one of the great free interactive courses in [GitHub "
+"Skills](https://skills.github.com/) on working with GitHub and working with "
+"MarkDown, the syntax this project's documentation is in."
+msgstr ""
+"若您從未使用過 GitHub，歡迎先[認識 GitHub 作業流程](https://docs.github.com/"
+"en/get-started/quickstart/github-flow)，或是參加 [GitHub "
+"Skills](https://skills.github.com/) 免費且優質的互動式課程，"
+"當中會介紹該如何使用 GitHub 以及 MarkDown 語法。MarkDown "
+"是本專案文件所採用的撰寫語法。"
+
+#: ./CONTRIBUTING.md:block 13 (paragraph)
+msgid ""
+"This project is licensed Creative Commons Zero v1.0 Universal, which "
+"essentially means that the project, along with your contributions is in the "
+"public domain in whatever jurisdiction possible, and everyone can do "
+"whatever they want with it."
+msgstr ""
+"本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以"
+"及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可"
+"以任意使用。"
+
+#: ./CONTRIBUTING.md:block 14 (header)
+msgid "1. Make your changes"
+msgstr "1. 作出您的修改"
+
+#: ./CONTRIBUTING.md:block 15 (paragraph)
+msgid ""
+"Contributions should [follow](docs/standard-for-public-code.html) the "
+"requirements set out in the criteria of the Standard for Public code itself."
+" Reviewers will also be ensuring that contributions are aligned with the "
+"[values of public code](foreword.md#values-of-public-code). Furthermore, "
+"they will review that the contribution conforms to the "
+"[standards](#standards-to-follow) and remains coherent with the overall "
+"work."
+msgstr ""
+"貢獻內容應該[遵守](docs/standard-for-public-code.html)《公共程式標準》自身所"
+"列出的準則規定。審查人員同時也會確保貢獻內容，符合[公共程式的價值](foreword."
+"md#values-of-public-code)。此外，他們也會審查貢獻是否遵循[標準](#standards-"
+"to-follow)，且與整體作品有所連貫。"
+
+#: ./CONTRIBUTING.md:block 16 (paragraph)
+msgid ""
+"This project uses the [GitFlow branching model and "
+"workflow](https://nvie.com/posts/a-successful-git-branching-model/). When "
+"you've forked this repository, please make sure to create a feature branch "
+"following the GitFlow model."
+msgstr ""
+"本專案使用 [GitFlow 分支與工作流程](https://nvie.com/posts/"
+"a-successful-git-branching-model/)。當您對此儲存庫作分支以後，請務必依照 "
+"GitFlow 模型建立新功能分支。"
+
+#: ./CONTRIBUTING.md:block 17 (paragraph)
+msgid ""
+"Add your changes in commits [with a message that explains "
+"them](https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-"
+"message). If more than one type of change is needed, group logically related"
+" changes into separate commits. For example, white-space fixes could be a "
+"separate commit from text content changes. When adding new files, select "
+"file formats that are easily viewed in a `diff`, for instance, `.svg` is "
+"preferable to a binary image. Document choices or decisions you make in the "
+"commit message, this will enable everyone to be informed of your choices in "
+"the future."
+msgstr ""
+"將您所作的變更內容加入送交版次，[並附上內容說明](https://robots.thoughtbot."
+"com/5-useful-tips-for-a-better-commit-message)。如果需要作出多種類型的變更，"
+"請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、"
+"以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用容易以「`"
+"diff` 」檢視的檔案格式，如「`.svg` 」格式就勝過二進位影像。在送交版次訊息中，"
+"請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉擇。"
+
+#: ./CONTRIBUTING.md:block 18 (paragraph)
+msgid ""
+"If you are adding code, make sure you've added and updated the relevant "
+"documentation and tests before you submit your pull request. Make sure to "
+"write tests that show the behavior of the newly added or changed code."
+msgstr "如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的"
+"拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。"
+
+#: ./CONTRIBUTING.md:block 19 (header)
+msgid "Applicable policy"
+msgstr "適用政策"
+
+#: ./CONTRIBUTING.md:block 20 (paragraph)
+msgid ""
+"Currently, the Standard for Public Code is not implementing any specific "
+"public policy."
+msgstr "就目前而言，《公共程式標準》並非在執行任何特定的公共政策。"
+
+#: ./CONTRIBUTING.md:block 21 (header)
+msgid "Style"
+msgstr "風格"
+
+#: ./CONTRIBUTING.md:block 22 (paragraph)
+msgid ""
+"The Standard for Public Code aims to [use plain English](criteria/use-plain-"
+"english.md) and we have chosen American English for spelling. Text content "
+"should typically follow one line per sentence, with no line-wrap, in order "
+"to make `diff` output easier to view. However, we want to emphasize that it "
+"is more important that you make your contribution than worry about spelling "
+"and typography. We will help you get it right in our review process and we "
+"also have a separate quality check before [making a new "
+"release](docs/releasing.md)."
+msgstr ""
+"《公共程式標準》目標[使用白話的英語](criteria/use-plain-english.md)，而拼字採"
+"用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖換行，來讓「`diff`」輸"
+"出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔"
+"心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才[推出新"
+"發行版本](docs/releasing.md)。"
+
+#: ./CONTRIBUTING.md:block 23 (header)
+msgid "Standards to follow"
+msgstr "遵守的標準"
+
+#: ./CONTRIBUTING.md:block 24 (paragraph)
+msgid ""
+"These are the standards that the Standard for Public Code uses. Please make "
+"sure that your contributions are aligned with them so that they can be "
+"merged more easily."
+msgstr "這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更"
+"容易合併。"
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - for requirement level"
+" keywords"
+msgstr "[IETF RFC 2119](https://tools.ietf.org/html/rfc2119) - 要求等級關鍵字"
+
+#: ./CONTRIBUTING.md:block 25 (unordered list)
+msgid ""
+"[Web Content Accessibility Guidelines "
+"2.1](https://www.w3.org/TR/WCAG21/#readable) - for readability"
+msgstr "[網頁內容可近用無障礙指引 2.1](https://www.w3.org/TR/WCAG21/#readable) - "
+"易讀性"
+
+#: ./CONTRIBUTING.md:block 26 (header)
+msgid "2. Pull request"
+msgstr "2. 拉取請求"
+
+#: ./CONTRIBUTING.md:block 27 (paragraph)
+msgid ""
+"When submitting the pull request, please accompany it with a description of "
+"the problem you are trying to solve and the issue number that this pull "
+"request fixes. It is preferred for each pull request to address a single "
+"issue where possible. In some cases a single set of changes may address "
+"multiple issues, in which case be sure to list all issue numbers fixed."
+msgstr ""
+"當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題"
+"編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列"
+"出所有能一併修正的議題編號。"
+
+#: ./CONTRIBUTING.md:block 28 (header)
+msgid "3. Improve"
+msgstr "3. 改善"
+
+#: ./CONTRIBUTING.md:block 29 (paragraph)
+msgid ""
+"All contributions have to be reviewed by someone. The Foundation for Public "
+"Code has committed to make sure that maintainers are available to review "
+"contributions with an aim to provide feedback within two business days."
+msgstr ""
+"所有貢獻都必須接受審查。Foundation for Public Code "
+"致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。"
+
+#: ./CONTRIBUTING.md:block 30 (paragraph)
+msgid ""
+"It could be that your contribution can be merged immediately by a "
+"maintainer. However, usually, a new pull request needs some improvements "
+"before it can be merged. Other contributors (or helper robots) might have "
+"feedback. If this is the case the reviewing maintainer will help you improve"
+" your documentation and code."
+msgstr ""
+"維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再"
+"經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若"
+"是如此，負責審查您貢獻內容的維護人員，將協助您改善文件與程式碼。"
+
+#: ./CONTRIBUTING.md:block 31 (paragraph)
+msgid "If your documentation and code have passed human review, it is merged."
+msgstr "一旦您的文件與程式碼通過人工審查，就會合併。"
+
+#: ./CONTRIBUTING.md:block 32 (header)
+msgid "4. Celebrate"
+msgstr "4. 慶祝"
+
+#: ./CONTRIBUTING.md:block 33 (paragraph)
+msgid ""
+"Your ideas, documentation and code have become an integral part of this "
+"project. You are the open source hero we need!"
+msgstr "您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄"
+"！"
+
+#: ./CONTRIBUTING.md:block 34 (paragraph)
+msgid ""
+"In fact, feel free to open a pull request to add your name to the "
+"[`AUTHORS`](AUTHORS.md) file and get eternal attribution."
+msgstr "誠摯歡迎您提出拉取請求，將您的名字加到 [`AUTHORS`](AUTHORS.md) "
+"檔案中，讓您所做的貢獻能銘記在本專案中。"
+
+#: ./CONTRIBUTING.md:block 35 (header)
+msgid "Translations in other languages"
+msgstr "翻譯成其他語言"
+
+#: ./CONTRIBUTING.md:block 36 (paragraph)
+msgid ""
+"While the Standard does not have any official translations, you can help "
+"maintain existing and add new [community translations of the "
+"Standard](https://github.com/publiccodenet/community-translations-standard)."
+msgstr ""
+"《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](ht"
+"tps://github.com/publiccodenet/community-translations-"
+"standard)，或是新增翻譯。"
+
+#: ./CONTRIBUTING.md:block 37 (header)
+msgid "Releases"
+msgstr "發行版本"
+
+#: ./CONTRIBUTING.md:block 38 (paragraph)
+msgid ""
+"We have dedicated documentation for creating [new "
+"releases](/docs/releasing.md) and [ordering printed "
+"standards](/docs/printing.md)."
+msgstr "我們有提供[發行新版本](/docs/releasing.md)，與[訂購印刷版標準](/docs/printing"
+".md)的專用詳細文件。"
+
+#: ./CONTRIBUTING.md:block 39 (paragraph)
+msgid ""
+"For more information on how to use and contribute to this project, please "
+"read the [`README`](README.md)."
+msgstr "若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 [`README `](README.md)。"
+
+#: ./GOVERNANCE.md:block 2 (header)
+msgid ""
+"SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code "
+"[info@publiccode.net](mailto:info@publiccode.net), "
+"https://standard.publiccode.net/AUTHORS"
+msgstr ""
+"SPDX-FileCopyrightText: 2019-2022 Foundation for Public Code[info@publiccode."
+"net](mailto:info@publiccode.net), https://standard.publiccode.net/AUTHORS"
+
+#: ./GOVERNANCE.md:block 3 (header)
+msgid "Governance"
+msgstr "治理方式"
+
+#: ./GOVERNANCE.md:block 4 (paragraph)
+msgid ""
+"This standard lies at the core of the codebase stewardship provided by the "
+"[Foundation for Public Code](https://publiccode.net/). We decide if a "
+"codebase is ready for community co-development based on this document."
+msgstr ""
+"本標準是 [Foundation for Public Code](https://publiccode.net/) 在為程式基底提"
+"供督導時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共同"
+"參與開發。"
+
+#: ./GOVERNANCE.md:block 5 (paragraph)
+msgid "The standard is maintained by Foundation for Public Code staff."
+msgstr "這份標準由 Foundation for Public Code 職員負責維護。"
+
+#: ./GOVERNANCE.md:block 6 (paragraph)
+msgid ""
+"[We welcome contributions, such as suggestions for changes or general "
+"feedback, from anyone.](/CONTRIBUTING.md)"
+msgstr "[我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。](/CONTRIBUTIN"
+"G.md)"
+
+#: ./GOVERNANCE.md:block 7 (paragraph)
+msgid ""
+"Because of the important role that the Standard for Public Code has in our "
+"core process we require the highest standards from the Standard."
+msgstr "由於《公共程式標準》在我們的核心流程中，扮演至關重要的角色，所以我們會以《公"
+"共程式標準》的最高標準作要求。"
+
+#: ./GOVERNANCE.md:block 8 (paragraph)
+msgid ""
+"We will try to respond promptly to all pull requests. The pull request is an"
+" opportunity to work together to improve our methods and the Standard. We "
+"may not accept all changes, but we will explain our logic."
+msgstr ""
+"我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方"
+"法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯"
+"。"
+
+#: ./README.md:block 1 (header)
+msgid "Standard for Public Code"
+msgstr "公共程式標準"
+
+#: ./README.md:block 3 (paragraph)
+msgid ""
+"The Standard for Public Code gives public organizations a model for "
+"preparing open source solutions to enable collaborations with similar public"
+" organizations in other places. It includes guidance for policy makers, city"
+" administrators, developers and vendors."
+msgstr ""
+"《公共程式標準》提供公家機關一套準備開放原始碼解決方案的模型，讓他們能與其他"
+"地方相似的公家機關協作。該標準包含給政策制定者、市行政官、開發人員與供應商的"
+"指引。"
+
+#: ./README.md:block 4 (paragraph)
+msgid ""
+"![version 0.7.0](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
+msgstr ""
+"![0.7.0版](assets/version-badge.svg) "
+"[![授權：CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/)"
+
+#: ./README.md:block 5 (paragraph)
+msgid ""
+"[![pages-build-"
+"deployment](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-"
+"deployment/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/pages/pages-"
+"build-deployment) "
+"[![Test](https://github.com/publiccodenet/standard/actions/workflows/test.yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/test.yml)"
+" [![standard main badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net.svg)](https://publiccodenet.github.io/publiccodenet-"
+"url-check/standard.publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-"
+"check/badges/standard.publiccode.net-"
+"develop.svg)](https://publiccodenet.github.io/publiccodenet-url-"
+"check/standard.publiccode.net-develop-url-check-look.json)"
+msgstr ""
+"[![pages-build-deployment](https://github.com/publiccodenet/standard/actions/"
+"workflows/pages/pages-build-deployment/badge.svg)](https://github.com/"
+"publiccodenet/standard/actions/workflows/pages/pages-build-deployment) "
+"[![測試](https://github.com/publiccodenet/standard/actions/workflows/test."
+"yml/badge.svg)](https://github.com/publiccodenet/standard/actions/workflows/"
+"test.yml) [![standard main badge](https://publiccodenet.github.io/"
+"publiccodenet-url-check/badges/standard.publiccode.net."
+"svg)](https://publiccodenet.github.io/publiccodenet-url-check/standard."
+"publiccode.net-url-check-look.json) [![standard develop "
+"badge](https://publiccodenet.github.io/publiccodenet-url-check/badges/"
+"standard.publiccode.net-develop.svg)](https://publiccodenet.github.io/"
+"publiccodenet-url-check/standard.publiccode.net-develop-url-check-look.json)"
+
+#: ./README.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is in a draft format. We are preparing it for a"
+" version 1.0 release. Currently, we are testing it on a small number of "
+"codebases."
+msgstr "《公共程式標準》目前為草稿階段。我們正在準備發行 1.0 "
+"版，目前仍在幾個程式基底中作測試。"
+
+#: ./README.md:block 7 (header)
+msgid "Applying the Standard for Public Code to your codebase"
+msgstr "將《公共程式標準》套用到您的程式基底"
+
+#: ./README.md:block 8 (paragraph)
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. To see how ready "
+"your codebase is, you can do a quick [eligibility self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility) that "
+"will give you a rough idea of how much work you may need to do to meet all "
+"criteria."
+msgstr ""
+"若您想要將《公共程式標準》套用到您的程式基底，就請放心去做，因為它是人人都能"
+"自由採用的開放標準。若要瞭解您程式基底所達成的程度，可以做[自我資格評估](http"
+"s://publiccodenet.github.io/assessment-"
+"eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
+
+#: ./README.md:block 9 (paragraph)
+msgid ""
+"The standard *should* be mostly self-explanatory in how to apply it to your "
+"codebase. If anything in the standard is unclear, we encourage you to open "
+"an issue here so that we can help you and anyone else who feels the same as "
+"you. For inspiration, look at the [community built implementation "
+"guide](https://publiccodenet.github.io/community-implementation-guide-"
+"standard/) which contains examples and other tips."
+msgstr ""
+"本標準 *應該* 足以自我解釋要如何套用到您的程式基底中。若標準中有任何不明確的"
+"地方，我們鼓勵您在此開立議題，來讓我們能協助您以及其他與您抱持同樣看法的人。"
+"如果需要一點靈感啟發，請參閱[社群製作的《實踐指引》](https://publiccodenet."
+"github.io/community-implementation-guide-standard/)，其中包括範例與其他提示。"
+
+#: ./README.md:block 10 (paragraph)
+msgid ""
+"If there are any breaking changes in a new version of the Standard for "
+"Public Code, the codebase stewards at the Foundation for Public Code will "
+"help any implementers of the standard understand how the gaps can be closed."
+msgstr ""
+"若新版的《公共程式標準》有任何導致過去作法不再適用的改動，則 Foundation for "
+"Public Code 的程式基底執事人員，會協助標準的實踐者理解該如何銜接之間的落差。"
+
+#: ./README.md:block 11 (paragraph)
+msgid ""
+"If you want to commit your codebase to become fully compliant to the "
+"standard for future certification, please contact us at "
+"[info@publiccode.net](mailto:info@publiccode.net) to initiate a formal "
+"[assessment](https://about.publiccode.net/activities/codebase-"
+"stewardship/lifecycle-diagram.html#assessment)."
+msgstr ""
+"若您致力讓您的程式基底完全遵循此標準，並想在未來能取得認證，請寫信與我們聯繫"
+"：[info@publiccode.net](mailto:info@publiccode."
+"net)，以展開正式[評估](https://about.publiccode.net/activities/"
+"codebase-stewardship/lifecycle-diagram.html#assessment)。"
+
+#: ./README.md:block 12 (header)
+msgid "Request for contributions"
+msgstr "徵求貢獻"
+
+#: ./README.md:block 13 (paragraph)
+msgid ""
+"We believe public policy and software should be inclusive, usable, open, "
+"legible, accountable, accessible and sustainable. This means we need a new "
+"way of designing, developing and procuring both the source code and policy "
+"documentation."
+msgstr ""
+"我們相信公共政策與公共軟體，應該具備涵容、好用、開放、易懂、課責、近用、永續"
+"等特質。這代表我們需要一種新的方式，來設計、開發，以及付出心力育成原始碼和政"
+"策文件。"
+
+#: ./README.md:block 14 (paragraph)
+msgid ""
+"This standard sets a quality level for codebases that meets the needs of "
+"public organizations, institutions and administrations as well as other "
+"critical infrastructural services."
+msgstr "本標準為程式基底設立品質檢核水準，使其能滿足公家機關、社會機構、行政單位，以"
+"及其他重大基礎設施服務的需求。"
+
+#: ./README.md:block 15 (paragraph)
+msgid ""
+"The standard lives at "
+"[standard.publiccode.net](https://standard.publiccode.net/). See "
+"[`index.md`](index.md) for an overview of all content."
+msgstr ""
+"本標準放在線上：[standard.publiccode.net](https://standard.publiccode.net/)。"
+"請參閱 [`index.md`](index.md) 查看整體內容概覽。"
+
+#: ./README.md:block 16 (paragraph)
+msgid ""
+"[![Thumbnail for the video on the Standard for Public Code: a printed "
+"version lying on a table between two "
+"hands](https://img.youtube.com/vi/QWt6vB-"
+"cipE/mqdefault.jpg)](https://www.youtube.com/watch?v=QWt6vB-cipE)"
+msgstr ""
+"[![《公共程式標準》的影片縮圖：兩隻手中間放著本標準的印刷本](https://img."
+"youtube.com/vi/QWt6vB-cipE/mqdefault.jpg)](https://www.youtube.com/watch?v"
+"=QWt6vB-cipE)"
+
+#: ./README.md:block 17 (paragraph)
+msgid ""
+"[A video introduction to Standard for Public "
+"Code](https://www.youtube.com/watch?v=QWt6vB-cipE) from Creative Commons "
+"Global Summit 2020 (4:12) on YouTube."
+msgstr ""
+"[《公共程式標準》的影片介紹](https://www.youtube.com/watch?v=QWt6vB-cipE)，"
+"出自 Creative Commons Global Summit 2020 (4:12)，放在 YouTube 上。"
+
+#: ./README.md:block 18 (header)
+msgid "Help improve this standard"
+msgstr "幫忙改善這份標準"
+
+#: ./README.md:block 19 (paragraph)
+msgid ""
+"The Foundation for Public Code is committed to maintaining and developing "
+"the Standard for Public Code at a level of quality that meets the standard "
+"itself."
+msgstr "Foundation for Public Code "
+"致力於維護與開發《公共程式標準》，且使其同時符合該標準自身的品質水準。"
+
+#: ./README.md:block 20 (paragraph)
+msgid ""
+"We are looking for people like you to [contribute](CONTRIBUTING.md) to this "
+"project by suggesting improvements and helping develop it. 😊 Get started by "
+"reading our [contributors guide](CONTRIBUTING.md). Since it is such a core "
+"document we will accept contributions when they add significant value. We've"
+" described how we govern the standard in the [governance "
+"statement](GOVERNANCE.md)."
+msgstr ""
+"我們正在尋找像您這樣的人，能對此專案做出[貢獻](CONTRIBUTING.md)，像是建議改善"
+"方向，以及協助開發等。😊若要開始，請先參閱我們的[貢獻者指引](CONTRIBUTING.md)"
+"。由於這是相當核心的文件，我們僅接受能帶來重大價值的貢獻。[治理方式聲明](GOVE"
+"RNANCE.md)中有說明管理該標準的方式。"
+
+#: ./README.md:block 21 (paragraph)
+msgid ""
+"Please note that this project is released with a [code of "
+"conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to "
+"abide by its terms. Please be lovely to all other community members."
+msgstr ""
+"請注意，本專案配合[行為守則](CODE_OF_CONDUCT."
+"md)一同發行。如果要參加本專案，代表您同意遵守守則。請善待社群的所有其他成員。"
+
+#: ./README.md:block 22 (header)
+msgid "Preview, build and deploy"
+msgstr "預覽、建置、部署"
+
+#: ./README.md:block 23 (paragraph)
+msgid ""
+"The repository builds to a static site deployed at "
+"[standard.publiccode.net](https://standard.publiccode.net/). It is built "
+"with [GitHub pages](https://pages.github.com) and "
+"[Jekyll](https://jekyllrb.com/)."
+msgstr ""
+"儲存庫會建置一個靜態網站，並部署至 [standard.publiccode.net](https://standard"
+".publiccode.net/)。網站採用 [GitHub 頁面](https://pages.github.com) 與 "
+"[Jekyll](https://jekyllrb.com/) 技術。"
+
+#: ./README.md:block 24 (paragraph)
+msgid ""
+"The content is made to be built with [Jekyll](http://jekyllrb.com/), which "
+"means you will need ruby and ruby-bundler installed, for example:"
+msgstr ""
+"網站內容透過 [Jekyll](http://jekyllrb.com/) 技術建置。這代表您需要有安裝 "
+"ruby 與 ruby-bundler，例如："
+
+#: ./README.md:block 26 (paragraph)
+msgid ""
+"If `ruby` and `bundle` are installed, one can run `bundle install` after "
+"which the site can be rendered with the `script/serve.sh` script."
+msgstr ""
+"一旦安裝好 `ruby` 與 `bundle` 後，就可以執行 `bundle install`，接著再利用 `"
+"script/serve.sh` 命令稿轉譯呈現出網站成果。"
+
+#: ./README.md:block 27 (header)
+msgid "Testing"
+msgstr "測試"
+
+#: ./README.md:block 28 (paragraph)
+msgid ""
+"A variety of test scripts are included. The script `script/test-all.sh` "
+"wraps running of all local tests."
+msgstr "本專案內含許多測試命令稿。其中 `script/test-all.sh` "
+"命令稿則統包執行所有本機測試。"
+
+#: ./README.md:block 29 (paragraph)
+msgid ""
+"See the scripts in the "
+"[script](https://github.com/publiccodenet/standard/tree/main/script) folder."
+msgstr ""
+"請前往 [script](https://github.com/publiccodenet/standard/tree/main/script) "
+"資料夾查看命令稿。"
+
+#: ./README.md:block 30 (header)
+msgid "Generating a PDF of the Standard for Public Code"
+msgstr "生成《公共程式標準》的 PDF 檔案"
+
+#: ./README.md:block 31 (paragraph)
+msgid ""
+"In addition to Jekyll, generating PDFs relies upon "
+"[Weasyprint](https://weasyprint.org/) and "
+"[QPDF](https://github.com/qpdf/qpdf). [Pandoc](https://pandoc.org/) can be "
+"used to transform PDFs into `.epub`."
+msgstr ""
+"除了先前提到的 Jekyll 以外，想生成 PDF 檔，還需要依賴 "
+"[Weasyprint](https://weasyprint.org/) 和 [QPDF](https://github.com/qpdf/"
+"qpdf)。[Pandoc](https://pandoc.org/) 則可將 PDF 檔轉換成 `.epub` 檔。"
+
+#: ./README.md:block 32 (paragraph)
+msgid ""
+"To generate these kinds of files, the dependencies should be installed, for "
+"example:"
+msgstr "若要生成這類檔案，則應該要安裝依賴的軟體項目，例如："
+
+#: ./README.md:block 34 (paragraph)
+msgid ""
+"The file `standard-print.html` can be converted to a nice looking PDF, along"
+" with the other release files, using:"
+msgstr "使用以下命令稿，可以將 `standard-print.html` 檔案轉換成美觀的 PDF "
+"檔，同時包括其他發行用的檔案："
+
+#: ./README.md:block 36 (header)
+msgid "License"
+msgstr "授權"
+
+#: ./README.md:block 37 (paragraph)
+msgid "© [The authors and contributors](AUTHORS.md)"
+msgstr "© [作者與貢獻者](AUTHORS.md)"
+
+#: ./README.md:block 38 (paragraph)
+msgid ""
+"The standard is [licensed](LICENSE) under CC 0, which also applies to all "
+"illustrations and the documentation. This means anyone can do anything with "
+"it. If you contribute you also grant these rights to others. You can read "
+"more about how to help in the [contributing guide](CONTRIBUTING.md)."
+msgstr ""
+"本標準採用 CC0 "
+"公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任"
+"何人都能任意使用這些內容。如果您是貢獻者，代表您也將這些權利賦予他人。若要進"
+"一步瞭解如何協助本專案，請參閱〈[貢獻指引](CONTRIBUTING.md)〉。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 3 (paragraph)
+msgid "order: 2 redirect_from:"
+msgstr "order: 2 redirect_from:"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 4 (unordered list)
+msgid "criteria/bundle-policy-and-code"
+msgstr "criteria/bundle-policy-and-code"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 5 (header)
+msgid "Bundle policy and source code"
+msgstr "政策與原始碼要合捆"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 6 (paragraph)
+msgid ""
+"Access to both [source code](../glossary.md#source-code) and "
+"[policy](../glossary.md#policy) documentation provides building blocks for "
+"anyone to implement the codebase in their local context or contribute to the"
+" further development of the [codebase](../glossary.md#codebase)."
+msgstr ""
+"對於想根據所在情境實作程式基底的人，或是想更進一步貢獻[程式基底](../glossary."
+"md#codebase)開發的人來說，能同時取用[原始碼](../glossary.md#source-"
+"code)與[政策](../glossary.md#policy)文件兩者，可作為建置成品時的基礎組件。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 7 (paragraph)
+msgid ""
+"Understanding the domain and policies within that domain is fundamental to "
+"understanding what problems a codebase is trying to solve and how it sets "
+"out to solve them."
+msgstr "瞭解作用範疇與該範疇的政策是基本原則，才能瞭解程式基底試圖想解決的問題是什麼"
+"，以及該如何解決這些問題的作法。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 8 (paragraph)
+msgid ""
+"To be able to evaluate whether to implement a codebase in a new context, an "
+"organization needs to understand what process changes it must choose to make"
+" or how to contribute additional configurability to the existing solution in"
+" order to adapt it to the new context."
+msgstr ""
+"為了評估是否需要在新的情境中實作程式基底，組織單位需要瞭解必須做出改變的程序"
+"有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 9 (header)
+msgid "Requirements"
+msgstr "需求規定"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "The codebase MUST include the policy that the source code is based on."
+msgstr "程式基底「必須」包含原始碼所根據的政策。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"If a policy is based on source code, that source code MUST be included in "
+"the codebase, unless used for fraud detection."
+msgstr "如果政策根據原始碼而來，則該原始碼「必須」包含在程式基底中，用於偵測詐騙的原"
+"始碼則可除外。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid "Policy SHOULD be provided in machine readable and unambiguous formats."
+msgstr "政策「應該」採用機器可讀且明確的格式。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 10 (unordered list)
+msgid ""
+"[Continuous integration](../glossary.md#continuous-integration) tests SHOULD"
+" validate that the source code and the policy are executed coherently."
+msgstr "[持續整合](../glossary.md#continuous-"
+"integration)測試「應該」驗證原始碼與政策是否有一致執行。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 11 (header)
+msgid "How to test"
+msgstr "測試方式"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all policy that the source code is based "
+"on is included."
+msgstr "與公務人員確認原始碼所根據的所有政策內容都有收錄在內。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Confirm with a civil servant that all source code that the policy is based "
+"on is included."
+msgstr "與公務人員確認政策所根據的所有原始碼都有收錄在內。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid "Check if policy can be interpreted by a machine."
+msgstr "確認政策內容是否能在機器上解讀。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 12 (unordered list)
+msgid ""
+"Check the continuous integration tests for coherent execution of source code"
+" and policy pass."
+msgstr "確認原始碼與政策間的執行一致性能通過持續整合測試。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 13 (header)
+msgid "Public policy makers: what you need to do"
+msgstr "公共政策制定者：需要的工作"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Collaborate with developers and designers to make sure there is no mismatch "
+"between policy code and source code."
+msgstr "與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Provide the relevant policy texts for inclusion in the "
+"[repository](../glossary.md#repository); if the text is not available in "
+"English, also provide an English summary. Be sure to include standards that "
+"your organization has chosen to adhere to and any organizational processes "
+"which impact the development or the deployment context of the codebase for "
+"your organization."
+msgstr ""
+"提供相關政策內文，以便收錄於[儲存庫](../glossary.md#repository)中；如果政策內"
+"文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單位所選擇遵守的各項標準"
+"，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid "Provide references and links to texts which support the policies."
+msgstr "請提供政策相關參考資料與連結。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Document policy in formats that are unambiguous and machine-readable, such "
+"as those published by the [Object Management "
+"Group](https://www.omg.org/spec/)."
+msgstr "政策內容請使用明確且機器可讀的格式，像是[物件管理群體](https://www.omg.org/"
+"spec/)所發表的格式。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Track policy with [the same version control](maintain-version-control.md) "
+"and documentation used to track source code."
+msgstr "追蹤政策時，請使用與追蹤原始碼[相同的版本控制](maintain-version-control."
+"md)與文件。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Check in regularly to understand how the source code in the codebase has "
+"changed and whether it still matches the [intentions of the "
+"policy](document-codebase-objectives.md)."
+msgstr "定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合[政策意圖"
+"](document-codebase-objectives.md)。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 14 (unordered list)
+msgid ""
+"Include relevant policies which impact the community, codebase, and "
+"development, including legal obligations like the [General Data Protection "
+"Regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj) or the [EU Web "
+"Accessibility Directive](https://ec.europa.eu/digital-single-market/en/web-"
+"accessibility), or human rights policies, like a public organization's "
+"commitment to equal opportunity."
+msgstr ""
+"納入會影響社會群體、程式基底與開發目標的相關政策，包含 [GDPR "
+"一般資料保護規則](https://eur-lex.europa.eu/eli/reg/2016/679/"
+"oj)或是[歐盟網頁無障礙命令](https://ec.europa.eu/digital-single-market/en/"
+"web-accessibility)等此類法律義務，或者是人權政策，例如公家機關對機會平等的承"
+"諾等。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 15 (header)
+msgid "Managers: what you need to do"
+msgstr "管理人員：需要的工作"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Keep policy makers, developers and designers involved and connected "
+"throughout the whole development process."
+msgstr "讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 16 (unordered list)
+msgid ""
+"Make sure policy makers, developers and designers are working to the same "
+"objectives."
+msgstr "確保政策制定者、開發人員與設計師朝相同目標努力。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 17 (header)
+msgid "Developers and designers: what you need to do"
+msgstr "開發人員與設計師：需要的工作"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Become familiar with and be able to use the process modelling notation that "
+"the policy makers in your organization use."
+msgstr "熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid ""
+"Work together with policy makers to make sure there is no mismatch between "
+"policy code and source code."
+msgstr "與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 18 (unordered list)
+msgid "Give feedback on how to make policy documentation more clear."
+msgstr "針對如何讓政策文字更清楚提供意見。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 19 (header)
+msgid "Further reading"
+msgstr "延伸閱讀"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Business Process Model and "
+"Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)"
+" on Wikipedia."
+msgstr ""
+"維基百科上的 [BPMN 業務流程模型與標記法](https://en.wikipedia.org/wiki/"
+"Business_Process_Model_and_Notation)。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[BPMN Quick Guide](https://www.bpmnquickguide.com/view-bpmn-quick-guide/) by"
+" Trisotech."
+msgstr ""
+"Trisotech 提供的 [BPMN 快速指南](https://www.bpmnquickguide.com/"
+"view-bpmn-quick-guide/)。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Decision Model and "
+"Notation](https://en.wikipedia.org/wiki/Decision_Model_and_Notation) on "
+"Wikipedia."
+msgstr ""
+"維基百科上的 [DMN 決策模型與標記法](https://en.wikipedia.org/wiki/"
+"Decision_Model_and_Notation)。"
+
+#: ./criteria/bundle-policy-and-source-code.md:block 20 (unordered list)
+msgid ""
+"[Case Management Model Notation](https://en.wikipedia.org/wiki/CMMN) on "
+"Wikipedia."
+msgstr "維基百科上的[ CMMN 案例管理模型標記法](https://en.wikipedia.org/wiki/CMMN)。"
+
+#: ./criteria/code-in-the-open.md:block 3 (header)
+msgid "order: 1"
+msgstr "order: 1"
+
+#: ./criteria/code-in-the-open.md:block 4 (header)
+msgid "Code in the open"
+msgstr "原始碼要開放"
+
+#: ./criteria/code-in-the-open.md:block 5 (paragraph)
+msgid ""
+"Coding in the open improves transparency, increases [source "
+"code](../glossary.md#source-code) quality, makes the source code easier to "
+"audit, and enables collaboration."
+msgstr ""
+"以開放精神編寫原始碼，能改善資訊透明、提高[原始碼](../glossary.md#source-"
+"code)品質、讓原始碼更容易稽核，也能促進互相協作。"
+
+#: ./criteria/code-in-the-open.md:block 6 (paragraph)
+msgid ""
+"Together, this creates more opportunities for citizens to understand how "
+"software and [policy](../glossary.md#policy) impact their interactions with "
+"a public organization."
+msgstr "這些合在一起，讓公民更有機會瞭解軟體與[政策](../glossary."
+"md#policy)如何影響他們與公家機關的互動。"
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any policy in use (unless used for fraud detection) MUST"
+" be published and publicly accessible."
+msgstr "任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能"
+"供民眾取用。"
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"All source code for any software in use (unless used for fraud detection) "
+"MUST be published and publicly accessible."
+msgstr "任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能"
+"供民眾取用。"
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST NOT contain sensitive information regarding users, their "
+"organization or third parties."
+msgstr "程式基底「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。"
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Any source code not currently in use (such as new versions, proposals or "
+"older versions) SHOULD be published."
+msgstr "目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。"
+
+#: ./criteria/code-in-the-open.md:block 8 (unordered list)
+msgid ""
+"Documenting which source code or policy underpins any specific interaction "
+"the [general public](../glossary.md#general-public) may have with an "
+"organization is OPTIONAL."
+msgstr ""
+"「可選擇」是否要以文件記錄[一般大眾](../glossary.md#general-public)與組織單位"
+"之間可能發生的任何特定互動，其背後所採用的原始碼或支持的政策。"
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the source for each version currently in use is published on "
+"the internet where it can be seen from outside the original contributing "
+"organization and without the need for any form of authentication or "
+"authorization."
+msgstr "確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形"
+"式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。"
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid ""
+"Confirm that the [codebase](../glossary.md#codebase) files and commit "
+"history do not include sensitive information."
+msgstr "確認[程式基底](../glossary."
+"md#codebase)檔案與送交版次歷史紀錄，不包含敏感性資訊。"
+
+#: ./criteria/code-in-the-open.md:block 10 (unordered list)
+msgid "Check for the publication of source code not currently in use."
+msgstr "檢查目前非使用中的原始碼是否有公開。"
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Develop policies in the open."
+msgstr "制定合乎開放精神的政策。"
+
+#: ./criteria/code-in-the-open.md:block 12 (unordered list)
+msgid "Prioritize open and transparent policies."
+msgstr "以公開透明的政策為優先。"
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid "Develop a culture that embraces openness, learning and feedback."
+msgstr "孕育擁抱開放、重視學習、歡迎意見回饋的文化。"
+
+#: ./criteria/code-in-the-open.md:block 14 (unordered list)
+msgid ""
+"Collaborate with external vendors and freelancers by working in the open."
+msgstr "與外部供應商和自由工作者以開放精神的方式協作。"
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"As a reviewer, for each commit, verify that content does not include "
+"sensitive information such as configurations, usernames or passwords, public"
+" keys or other real credentials used in production systems."
+msgstr "審查人員在檢核每次的送交版次紀錄時，要確實核對內容沒有包含組態設定、使用者名"
+"稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。"
+
+#: ./criteria/code-in-the-open.md:block 16 (unordered list)
+msgid ""
+"Clearly split data and source code, in order to meet the requirement about "
+"sensitive information above."
+msgstr "為符合上述敏感性資訊的相關規定，請明確分開資料與原始碼。"
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Coding in the open](https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/)"
+" by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼](https://gds.blog.gov.uk/2012/10/12/coding-in-the-"
+"open/)》。"
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[When code should be open or "
+"closed](https://www.gov.uk/government/publications/open-source-"
+"guidance/when-code-should-be-open-or-closed) by the UK Government Digital "
+"Service."
+msgstr ""
+"英國政府數位服務團《[程式碼應該開放或封閉的時機](https://www.gov.uk/government/publications/open-"
+"source-guidance/when-code-should-be-open-or-closed)》。"
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Security considerations when coding in the "
+"open](https://www.gov.uk/government/publications/open-source-"
+"guidance/security-considerations-when-coding-in-the-open) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的資安考量](https://www.gov.uk/government/publications/open-"
+"source-guidance/security-considerations-when-coding-in-the-open)》。"
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[Deploying software regularly](https://www.gov.uk/service-"
+"manual/technology/deploying-software-regularly) by the UK Government Digital"
+" Service."
+msgstr ""
+"英國政府數位服務團《[定期部署軟體](https://www.gov.uk/service-manual/technology/deploying-"
+"software-regularly)》。"
+
+#: ./criteria/code-in-the-open.md:block 18 (unordered list)
+msgid ""
+"[How GDS uses GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-"
+"use-github/) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[政府數位服務團如何使用 "
+"GitHub](https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/)》。"
+
+#: ./criteria/document-codebase-maturity.md:block 3 (header)
+msgid ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
+msgstr ""
+"order: 16 redirect_from: - criteria/advertise-maturity - criteria/document-"
+"maturity"
+
+#: ./criteria/document-codebase-maturity.md:block 4 (header)
+msgid "Document codebase maturity"
+msgstr "記錄程式基底成熟度"
+
+#: ./criteria/document-codebase-maturity.md:block 5 (paragraph)
+msgid ""
+"Clearly signalling a [codebase](../glossary.md#codebase)'s maturity helps "
+"others decide whether to use and contribute to it. A codebase version's "
+"maturity includes the maturity of its dependencies. Understanding how a "
+"codebase has evolved is key to understanding the codebase and how to "
+"contribute to it."
+msgstr ""
+"清楚標示[程式基底](../glossary.md#codebase)的成熟度，有助於他人決定是否要使用"
+"，或為該程式基底做出貢獻。程式基底版本的成熟度，包含其依賴項目的成熟度。瞭解"
+"程式基底演進到什麼程度，是理解該程式基底並知道如何做出貢獻的關鍵。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The codebase MUST be versioned."
+msgstr "程式基底「必須」註明版本編號。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase MUST prominently document whether or not there are versions of "
+"the codebase that are ready to use."
+msgstr "程式基底「必須」明確以文件記錄，是否有已經準備好可供使用的版本。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"Codebase versions that are ready to use MUST only depend on versions of "
+"other codebases that are also ready to use."
+msgstr "準備好可供使用的程式基底版本，「必須」只能依賴其他也已經準備好可供使用的程式"
+"基底版本。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid ""
+"The codebase SHOULD contain a log of changes from version to version, for "
+"example in the `CHANGELOG`."
+msgstr "程式基底「應該」包含每次版本的變動紀錄，像是以「`CHANGELOG`」日誌格式檔記錄。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "The method for assigning version identifiers SHOULD be documented."
+msgstr "「應該」要以文件記錄分配版本識別碼的方法。"
+
+#: ./criteria/document-codebase-maturity.md:block 7 (unordered list)
+msgid "It is OPTIONAL to use semantic versioning."
+msgstr "「可選擇」是否採用語意化版本控制編號。"
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that the codebase has a strategy for versioning which is documented."
+msgstr "確認程式基底有版本編號策略，且有文件記載該策略。"
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that it is obvious to policy makers, managers, developers and "
+"designers whether the codebase has versions that are ready to use."
+msgstr "確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道程式基底是否有準備"
+"好可供使用的版本。"
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Confirm that ready to use versions of the codebase do not depend on any "
+"versions of other codebases that are not ready to use."
+msgstr "確認準備好可供使用的程式基底版本，並不依賴任何尚未準備好可供使用的其他程式基"
+"底的版本。"
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid ""
+"Check that the versioning scheme of the codebase is documented and followed."
+msgstr "確認有文件記錄程式基底的版本編號方法，並且確實遵守。"
+
+#: ./criteria/document-codebase-maturity.md:block 9 (unordered list)
+msgid "Check that there is a log of changes."
+msgstr "確認是否有版本的變動紀錄。"
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"When developing [policy](../glossary.md#policy), understand that any [source"
+" code](../glossary.md#source-code) developed needs to be tested and improved"
+" before it can be put into service."
+msgstr ""
+"制定[政策](../glossary.md#policy)時，請記住任何開發出來的[原始碼](../glossary"
+".md#source-code)都必須先經過測試與改善，才能夠投入服務。"
+
+#: ./criteria/document-codebase-maturity.md:block 11 (unordered list)
+msgid ""
+"Consider versioning policy changes, especially when they trigger new "
+"versions of the source code."
+msgstr "考慮將政策的變動註明版本編號，尤其是因而觸發新版本原始碼開發的情況。"
+
+#: ./criteria/document-codebase-maturity.md:block 13 (unordered list)
+msgid ""
+"Make sure that services only rely on versions of codebases of equal or "
+"greater maturity than the service. For example, don't use a beta version of "
+"a codebase in a production service."
+msgstr "要確認服務依賴的程式基底版本成熟度，等同或高於該服務本身。舉例來說，"
+"正式上線的服務不要使用 beta 公測版程式基底。"
+
+#: ./criteria/document-codebase-maturity.md:block 15 (unordered list)
+msgid ""
+"Make sure that the codebase versioning approach is followed for all "
+"releases."
+msgstr "確認所有發行版，都有遵守程式基底的版本控制編號作法。"
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Semantic Versioning Specification](https://semver.org/) used by many "
+"codebases to label versions."
+msgstr "許多程式基底使用「[語意化版本編號規範](https://semver.org/)」來標示版本。"
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Software release life "
+"cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
+msgstr "[軟體發行生命週期](https://en.wikipedia.org/wiki/Software_release_life_cycle)"
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Design and Delivery Process](https://www.dta.gov.au/help-and-"
+"advice/build-and-improve-services/service-design-and-delivery-process) by "
+"the Australian Digital Transformation Agency."
+msgstr ""
+"澳洲數位轉型局《[服務設計與交付流程](https://www.dta.gov.au/help-and-advice/build-and-"
+"improve-services/service-design-and-delivery-process)》。"
+
+#: ./criteria/document-codebase-maturity.md:block 17 (unordered list)
+msgid ""
+"[Service Manual on Agile Delivery](https://www.gov.uk/service-manual/agile-"
+"delivery) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[敏捷交付服務手冊](https://www.gov.uk/service-manual/agile-delivery)》。"
+
+#: ./criteria/document-codebase-objectives.md:block 3 (paragraph)
+msgid "order: 8 redirect_from:"
+msgstr "order: 8 redirect_from:"
+
+#: ./criteria/document-codebase-objectives.md:block 4 (unordered list)
+msgid "criteria/document-objectives"
+msgstr "criteria/document-objectives"
+
+#: ./criteria/document-codebase-objectives.md:block 5 (header)
+msgid "Document codebase objectives"
+msgstr "程式基底要有目標文件"
+
+#: ./criteria/document-codebase-objectives.md:block 6 (paragraph)
+msgid ""
+"Clearly documenting [codebase](../glossary.md#codebase) objectives "
+"communicates the purpose of the codebase. It helps stakeholders and "
+"contributors scope the development of the codebase. The objectives also "
+"provide an easy way for people to decide whether this codebase, or one of "
+"its modules, is interesting for them now or in the future."
+msgstr ""
+"以文件清楚記錄[程式基底](../glossary.md#codebase)目標，來傳達程式基底的用途目"
+"標。這能幫助利害關係人與貢獻者劃定程式基底的開發範圍。這些目標也能方便人們判"
+"斷，是否在當下或未來，會對此程式基底或其模組感興趣。"
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST contain documentation of its objectives, like a mission "
+"and goal statement, that is understandable by developers and designers so "
+"that they can use or contribute to the codebase."
+msgstr "程式基底「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計"
+"師需要能夠瞭解這些，他們才知道可以怎樣使用程式基底或協助貢獻。"
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Codebase documentation SHOULD clearly describe the connections between "
+"[policy](../glossary.md#policy) objectives and codebase objectives."
+msgstr "程式基底文件「應該」清楚描述[政策](../glossary."
+"md#policy)目標與程式基底目標之間的關聯。"
+
+#: ./criteria/document-codebase-objectives.md:block 8 (unordered list)
+msgid ""
+"Documenting the objectives of the codebase for the [general "
+"public](../glossary.md#general-public) is OPTIONAL."
+msgstr "「可選擇」是否以文件記錄給[一般大眾](../glossary.md#general-"
+"public)看的程式基底目標。"
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase documentation includes the codebase objectives, "
+"mission or goal."
+msgstr "確認程式基底文件有包含程式基底目標，或主旨、使命等。"
+
+#: ./criteria/document-codebase-objectives.md:block 10 (unordered list)
+msgid ""
+"Check for descriptions of connections between policy objectives and codebase"
+" objectives."
+msgstr "查看政策目標與程式基底目標之間關聯的描述。"
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Add the policy objectives to the codebase documentation, for example in the "
+"`README`."
+msgstr "將政策目標加入程式基底文件中，例如「`README`」文件當中。"
+
+#: ./criteria/document-codebase-objectives.md:block 12 (unordered list)
+msgid ""
+"Make sure that all your codebase objectives have links or references to "
+"supporting policy documents added to meet the [Bundle policy and source "
+"code](bundle-policy-and-source-code.md) criterion."
+msgstr ""
+"確保所有程式基底目標，有連結或引用為了符合〈[政策與原始碼要合捆](bundle-"
+"policy-and-source-code.md)〉準則而加入的支持政策文件。"
+
+#: ./criteria/document-codebase-objectives.md:block 14 (unordered list)
+msgid ""
+"Add the organizational and business objectives to the codebase "
+"documentation, for example in the `README`."
+msgstr "將單位目標、組織目標或業務目標加入程式基底文件中，例如「`README`」文件當中。"
+
+#: ./criteria/document-codebase-objectives.md:block 16 (unordered list)
+msgid ""
+"Add the technology and design objectives to the codebase documentation, for "
+"example in the `README`."
+msgstr "將技術與設計目標加入程式基底文件中，例如「`README`」文件當中。"
+
+#: ./criteria/document-codebase-objectives.md:block 18 (unordered list)
+msgid ""
+"[How to write project "
+"objectives](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)"
+" by Marek Hajduczenia."
+msgstr ""
+"Marek "
+"Hajduczenia《[如何撰寫專案目標](http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf)》。"
+
+#: ./criteria/document-the-code.md:block 3 (paragraph)
+msgid "order: 9 redirect_from:"
+msgstr "order: 9 redirect_from:"
+
+#: ./criteria/document-the-code.md:block 4 (unordered list)
+msgid "criteria/documenting"
+msgstr "criteria/documenting"
+
+#: ./criteria/document-the-code.md:block 5 (header)
+msgid "Document the code"
+msgstr "程式碼要有文件"
+
+#: ./criteria/document-the-code.md:block 6 (paragraph)
+msgid ""
+"Well documented [source code](../glossary.md#source-code) helps people to "
+"understand what the source code does and how to use it. Documentation is "
+"essential for people to start using the [codebase](../glossary.md#codebase) "
+"and contributing to it more quickly."
+msgstr ""
+"文件記錄周全的[原始碼](../glossary.md#source-code)能幫助人們瞭解該原始碼的作"
+"用與使用方式。文件紀錄是幫助人們快速上手如何使用[程式基底](../glossary."
+"md#codebase)，並做出貢獻的關鍵。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"All of the functionality of the codebase, [policy](../glossary.md#policy) as"
+" well as source code, MUST be described in language clearly understandable "
+"for those that understand the purpose of the codebase."
+msgstr ""
+"程式基底的所有功能、[政策](../glossary.md#policy)及原始碼，都「必須」以可清楚"
+"瞭解的用語描述，讓懂程式基底目的用途的人也能夠理解。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain a description of how to "
+"install and run the software."
+msgstr "程式基底文件「必須」說明如何安裝與執行軟體。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase MUST contain examples demonstrating the "
+"key functionality."
+msgstr "程式基底文件「必須」為關鍵功能舉出範例。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a high level description "
+"that is clearly understandable for a wide audience of stakeholders, like the"
+" [general public](../glossary.md#general-public) and journalists."
+msgstr ""
+"程式基底文件「應該」包含精要的說明，讓[一般大眾](../glossary.md#general-"
+"public)和記者等廣泛的利害關係人都能清楚明白。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain a section describing how to"
+" install and run a standalone version of the source code, including, if "
+"necessary, a test dataset."
+msgstr "程式基底文件「應該」有一部分用來說明，如何安裝與執行原始碼的單機版；如果有必"
+"要，也應該包含測試資料集。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation of the codebase SHOULD contain examples for all "
+"functionality."
+msgstr "程式基底文件「應該」包含所有功能的範例。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"The documentation SHOULD describe the key components or modules of the "
+"codebase and their relationships, for example as a high level architectural "
+"diagram."
+msgstr "程式碼文件「應該」描述程式基底的主要組件或模組，以及其彼此之間的關係，例如以"
+"高層架構圖表示。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"There SHOULD be [continuous integration](../glossary.md#continuous-"
+"integration) tests for the quality of the documentation."
+msgstr "「應該」要有針對文件品質的[持續整合](../glossary.md#continuous-"
+"integration)測試。"
+
+#: ./criteria/document-the-code.md:block 8 (unordered list)
+msgid ""
+"Including examples that make users want to immediately start using the "
+"codebase in the documentation of the codebase is OPTIONAL."
+msgstr "「可選擇」是否在程式基底文件中，包含讓使用者想要立即使用程式基底的範例。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that other stakeholders, professionals from other public "
+"organizations and the general public find the documentation clear and "
+"understandable."
+msgstr "確認文件內容能讓其他利害關係人、其他公家機關的專業人士，以及一般大眾，都可以"
+"清楚明白。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation describes how to install and run the source "
+"code."
+msgstr "確認文件有說明如何安裝與執行原始碼。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Confirm that the documentation includes examples of the key functionality."
+msgstr "確認文件有包含主要功能的範例。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check with members of the general public and journalists if they can "
+"understand the high level description."
+msgstr "向一般大眾的成員以及記者確認，他們是否能明白文件當中的精要說明。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the instructions for how to install and run a standalone version "
+"of the source code result in a running system."
+msgstr "檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid "Check that all functionality documented contains an example."
+msgstr "檢查文件中列舉的所有功能都包含範例。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation includes a high level architectural diagram or "
+"similar."
+msgstr "檢查文件中是否包含高層架構圖，或類似的組件關係圖表。"
+
+#: ./criteria/document-the-code.md:block 10 (unordered list)
+msgid ""
+"Check that the documentation quality is part of integration testing, for "
+"example documentation is generated correctly, and links and images are "
+"tested."
+msgstr "確認整合測試有包含到程式碼文件品質，例如確認生成的文件是否正確，並檢查連結與"
+"圖片等。"
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-policy code in the codebase has"
+" changed."
+msgstr "定期查看程式基底中非政策程式碼的變動情況。"
+
+#: ./criteria/document-the-code.md:block 12 (unordered list)
+msgid "Give feedback on how to make non-policy documentation more clear."
+msgstr "針對如何讓非政策文件更清楚易懂提供意見回饋。"
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Try to use the codebase, so your feedback can improve how clearly the policy"
+" and source code are documented. For example, is the current documentation "
+"sufficient to persuade a manager at another public organization to use this "
+"codebase?"
+msgstr ""
+"嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例"
+"來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這套程式基底"
+"？"
+
+#: ./criteria/document-the-code.md:block 14 (unordered list)
+msgid ""
+"Make sure you understand both the policy and source code as well as the "
+"documentation."
+msgstr "確保您同時瞭解政策、原始碼以及文件內容。"
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid ""
+"Check in regularly to understand how the non-source code in the codebase has"
+" changed."
+msgstr "定期查看程式基底中非原始碼部分的變動情況。"
+
+#: ./criteria/document-the-code.md:block 16 (unordered list)
+msgid "Give feedback on how to make non-source documentation more clear."
+msgstr "針對如何讓非原始碼文件更清楚易懂提供意見回饋。"
+
+#: ./criteria/document-the-code.md:block 18 (unordered list)
+msgid ""
+"[Documentation guide](https://www.writethedocs.org/guide/) by Write the "
+"Docs."
+msgstr "Write the Docs《[文件指南](https://www.writethedocs.org/guide/)》。"
+
+#: ./criteria/index.md:block 3 (header)
+msgid "order: 0"
+msgstr "order: 0"
+
+#: ./criteria/index.md:block 4 (header)
+msgid "Criteria"
+msgstr "準則"
+
+#: ./criteria/index.md:block 5 (paragraph)
+msgid "{% assign sorted = site.pages | sort:\"order\" %}"
+msgstr "{% assign sorted = site.pages | sort:\"order\" %}"
+
+#: ./criteria/index.md:block 6 (paragraph)
+msgid ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+msgstr ""
+"{% for page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name "
+"!= \"index.md\" %}{% if page.title %}"
+
+#: ./criteria/index.md:block 7 (ordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%} {% endif%} {% endif%}{% endfor %}"
+
+#: ./criteria/maintain-version-control.md:block 3 (paragraph)
+msgid "order: 6 redirect_from:"
+msgstr "order: 6 redirect_from:"
+
+#: ./criteria/maintain-version-control.md:block 4 (unordered list)
+msgid "criteria/version-control-and-history"
+msgstr "criteria/version-control-and-history"
+
+#: ./criteria/maintain-version-control.md:block 5 (header)
+msgid "Maintain version control"
+msgstr "維護版本控制"
+
+#: ./criteria/maintain-version-control.md:block 6 (paragraph)
+msgid ""
+"[Version control](../glossary.md#version-control) means keeping track of "
+"changes to the [source code](../glossary.md#source-code) and other files of "
+"the [codebase](../glossary.md#codebase) over time. This allows you to "
+"maintain structured documentation of the history of the codebase. This is "
+"essential for collaboration at scale, as it enables developers to work on "
+"changes in parallel and helps future developers to understand the reasons "
+"for changes."
+msgstr ""
+"[版本控制](../glossary.md#version-control)主要在追蹤[原始碼](../glossary.md"
+"#source-code)以及其他[程式基底](../glossary.md#codebase)檔案歷來的變動。這能"
+"讓您為程式基底維護有條理的變動歷史文件。這是大規模協作得以運作的要素，使開發"
+"人員可以針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All files in the codebase MUST be version controlled."
+msgstr "程式基底中的所有檔案皆「必須」有版本控制。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid "All decisions MUST be documented in commit messages."
+msgstr "所有決定皆「必須」記錄成送交版次訊息。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Every commit message MUST link to discussions and issues wherever possible."
+msgstr "每份送交版次訊息皆「必須」盡可能附上討論與議題連結。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD be maintained in a distributed version control system."
+msgstr "程式基底「應該」以分散式版本控制系統作維護。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD require contributors to group relevant "
+"changes in commits."
+msgstr "貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Maintainers SHOULD mark released versions of the codebase, for example using"
+" revision tags or textual labels."
+msgstr "維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版"
+"本。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"Contribution guidelines SHOULD encourage file formats where the changes "
+"within the files can be easily viewed and understood in the version control "
+"system."
+msgstr "貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更"
+"動的檔案格式。"
+
+#: ./criteria/maintain-version-control.md:block 8 (unordered list)
+msgid ""
+"It is OPTIONAL for contributors to sign their commits and provide an email "
+"address, so that future contributors are able to contact past contributors "
+"with questions about their work."
+msgstr "貢獻者「可選擇」是否對送交內容作簽章，並附上電子郵件信箱，以便當未來貢獻者對"
+"其內容有疑問時，可以與之前的貢獻者聯絡。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase is kept in version control using software such as "
+"Git."
+msgstr "確認程式基底維持在版本控制狀態中，像是使用 Git 之類的軟體。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that all commit messages explain why "
+"the change was made."
+msgstr "審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, confirming that where possible all commit "
+"messages include the discussion about the change was or where to find it "
+"(with a URL)."
+msgstr "審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的"
+"地方，包含變動內容以及連結位置（提供網址）。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid "Check if the version control system is distributed."
+msgstr "檢查版本控制系統是否為分散式。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Review the commit history, check if grouping of relevant changes in "
+"accordance with the contributing guidelines."
+msgstr "審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that it is possible to access a specific version of the codebase, for "
+"example through a revision tag or a textual label."
+msgstr "檢查是否可能透過像是修訂版次標記，或文字標籤，來取用程式基底中的特定版本。"
+
+#: ./criteria/maintain-version-control.md:block 10 (unordered list)
+msgid ""
+"Check that the file formats used in the codebase are text formats where "
+"possible."
+msgstr "檢查程式基底在盡可能的情況下，檔案都是採用文字格式。"
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid ""
+"If a new version of the codebase is created because of a "
+"[policy](../glossary.md#policy) change, make sure it's clear in the "
+"documentation:"
+msgstr "如果因為[政策](../glossary."
+"md#policy)改變而在程式基底中有新的版本，則請確認有在文件中清楚說明："
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "what the policy change is,"
+msgstr "政策改變的地方，"
+
+#: ./criteria/maintain-version-control.md:block 12 (unordered list)
+msgid "how it's changed the codebase."
+msgstr "程式基底如何因應而改變。"
+
+#: ./criteria/maintain-version-control.md:block 13 (paragraph)
+msgid ""
+"For example, adding a new category of applicant to a codebase that manages "
+"granting permits would be considered a policy change."
+msgstr "舉例來說，為程式基底作權限管理時，如果要新增申請方類別來賦予取用權，應視為一"
+"種政策變動。"
+
+#: ./criteria/maintain-version-control.md:block 15 (unordered list)
+msgid ""
+"Support policy makers, developers and designers to be clear about what "
+"improvements they're making to the codebase. Making improvements isn't a "
+"public relations risk."
+msgstr "支持政策制定者、開發人員與設計師，使其能清楚表達他們對程式基底做出的改善。確"
+"保改善程式基底不會有公關風險。"
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Make sure that all files required to understand the code, build and deploy "
+"are in the version control system."
+msgstr "確認版本控制系統中，有瞭解程式碼、建置與部署所需要用到的所有檔案。"
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Write clear commit messages so that it is easy to understand why the commit "
+"was made."
+msgstr "送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。"
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Mark different versions so that it is easy to access a specific version, for"
+" example using revision tags or textual labels."
+msgstr "使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。"
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid "Write clear commit messages so that versions can be usefully compared."
+msgstr "送交版次訊息要寫清楚，方便之後比較各版本。"
+
+#: ./criteria/maintain-version-control.md:block 17 (unordered list)
+msgid ""
+"Work with policy makers to describe how the source code was updated after a "
+"policy change."
+msgstr "在政策改變以後，與政策制定者合作說明原始碼更新的部分。"
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Producing OSS: Version Control "
+"Vocabulary](https://producingoss.com/en/vc.html#vc-vocabulary) by Karl "
+"Fogel."
+msgstr ""
+"Karl Fogel《[製作開放原始碼軟體：版本控制字彙](https://producingoss.com/en/vc.html#vc-"
+"vocabulary)》。"
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Maintaining version control in coding](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[維護程式碼的版本控制](https://www.gov.uk/service-"
+"manual/technology/maintaining-version-control-in-coding)》。"
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[GitHub Skills](https://skills.github.com/) by GitHub for learning how to "
+"use GitHub or refresh your skills."
+msgstr ""
+"GitHub 提供的「[GitHub 技能](https://skills.github.com/)」，可學習如何使用 "
+"GitHub，或是重溫您的技巧。"
+
+#: ./criteria/maintain-version-control.md:block 19 (unordered list)
+msgid ""
+"[Git Cheat Sheet](https://education.github.com/git-cheat-sheet-"
+"education.pdf) by GitHub, a list with the most common used git commands."
+msgstr ""
+"GitHub 提供的「[Git 密技表](https://education.github.com/git-cheat-sheet-"
+"education.pdf)」，列出了最常用的 git 命令。"
+
+#: ./criteria/make-contributing-easy.md:block 3 (header)
+msgid "order: 5"
+msgstr "order: 5"
+
+#: ./criteria/make-contributing-easy.md:block 4 (header)
+msgid "Make contributing easy"
+msgstr "貢獻要容易"
+
+#: ./criteria/make-contributing-easy.md:block 5 (paragraph)
+msgid ""
+"To develop better, more reliable and feature rich software, users need to be"
+" able to fix problems, add features, and address security issues of the "
+"shared [codebase](../glossary.md#codebase)."
+msgstr ""
+"若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的[程式基底](../g"
+"lossary.md#codebase)修正問題、新增功能，以及提出安全性議題等。"
+
+#: ./criteria/make-contributing-easy.md:block 6 (paragraph)
+msgid ""
+"A shared digital infrastructure makes it easier to make collaborative "
+"contributions. The less effort it takes to make contributions that are "
+"accepted by the codebase, the more likely users are to become contributors."
+msgstr "共享的數位基礎建設讓協作貢獻更容易。使用者讓程式基底接受貢獻時所需付出的心力"
+"越少，則使用者越可能成為貢獻者。"
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have a public issue tracker that accepts suggestions from "
+"anyone."
+msgstr "程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。"
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST link to both the public issue tracker and submitted "
+"codebase changes, for example in a `README` file."
+msgstr "文件中「必須」同時有公開的議題追蹤器連結，以及已提交的程式基底變動的連結，例"
+"如記錄在「`README`」檔案中。"
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST have communication channels for users and developers, for "
+"example email lists."
+msgstr "程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（"
+"郵遞論壇）。"
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"There MUST be a way to report security issues for responsible disclosure "
+"over a closed channel."
+msgstr "「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。"
+
+#: ./criteria/make-contributing-easy.md:block 8 (unordered list)
+msgid ""
+"The documentation MUST include instructions for how to report potentially "
+"security sensitive issues."
+msgstr "文件「必須」說明，該如何通報潛在的安全性與敏感性問題。"
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a public issue tracker."
+msgstr "確認有公開的議題追蹤器。"
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase contains links to the public issue tracker and "
+"submitted codebase changes."
+msgstr "確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。"
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to participate in a discussion with other users "
+"and developers about the software using channels described in the codebase."
+msgstr "確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。"
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid "Confirm that there is a closed channel for reporting security issues."
+msgstr "確認有封閉的管道可通報安全性問題。"
+
+#: ./criteria/make-contributing-easy.md:block 10 (unordered list)
+msgid ""
+"Confirm that there are instructions for privately reporting security issues."
+msgstr "確認有說明如何私下通報安全性問題。"
+
+#: ./criteria/make-contributing-easy.md:block 12 (unordered list)
+msgid ""
+"Track [policy](../glossary.md#policy) issues in the codebase, so that a "
+"relevant external policy expert can volunteer help."
+msgstr "追蹤程式基底中的[政策](../glossary."
+"md#policy)問題，讓相關的外部政策專家如果自願也能夠協助。"
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Track management issues in the codebase, so that external managers with "
+"relevant experience can volunteer help."
+msgstr "追蹤程式基底中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。"
+
+#: ./criteria/make-contributing-easy.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to keep "
+"contributing to the codebase for as long as possible."
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為程式基底持續做出長"
+"久貢獻。"
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Just like for [reviews](require-review-of-contributions.md), make sure to "
+"respond to requests promptly."
+msgstr "與[審查](require-review-of-contributions.md)流程相同，務必迅速回應請求。"
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Keep your managers informed of the time and resources you require to support"
+" other contributors."
+msgstr "告知管理人員，您在支援其他貢獻者時所需的時間與資源。"
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate communication channels for asking maintainers and"
+" stakeholders questions are easy to locate, for instance in the README."
+msgstr "確保人們可輕鬆找到合適的溝通管道，來詢問維護人員與利害關係人問題，例如寫在「`"
+"README`」文件當中。"
+
+#: ./criteria/make-contributing-easy.md:block 16 (unordered list)
+msgid ""
+"Make sure that appropriate contact details are included in the metadata, for"
+" instance in the publiccode.yml file."
+msgstr "確保中介資料包含合適的聯絡資訊，例如寫在 publiccode.yml 檔案中。"
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[How to inspire exceptional contributions to your open-source "
+"project](https://dev.to/joelhans/how-to-inspire-exceptional-contributions-"
+"to-your-open-source-project-1ebf) by Joel Hans."
+msgstr ""
+"Joel Hans《[如何引發他人為您的開放原始碼專案做出優秀貢獻](https://dev.to/joelhans/how-to-inspire-"
+"exceptional-contributions-to-your-open-source-project-1ebf)》。"
+
+#: ./criteria/make-contributing-easy.md:block 18 (unordered list)
+msgid ""
+"[The benefits of coding in the open](https://gds.blog.gov.uk/2017/09/04/the-"
+"benefits-of-coding-in-the-open/) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[以開放精神編寫原始碼的好處](https://gds.blog.gov.uk/2017/09/04/the-benefits-"
+"of-coding-in-the-open/)》。"
+
+#: ./criteria/make-the-codebase-findable.md:block 3 (paragraph)
+msgid "order: 14 redirect_from:"
+msgstr "order: 14 redirect_from:"
+
+#: ./criteria/make-the-codebase-findable.md:block 4 (unordered list)
+msgid "criteria/findability"
+msgstr "criteria/findability"
+
+#: ./criteria/make-the-codebase-findable.md:block 5 (header)
+msgid "Make the codebase findable"
+msgstr "程式基底可查詢得到"
+
+#: ./criteria/make-the-codebase-findable.md:block 6 (paragraph)
+msgid ""
+"The more findable a [codebase](../glossary.md#codebase) is, the more "
+"potential new collaborators will find it. Just publishing a codebase and "
+"hoping it is found does not work, instead proactiveness is needed."
+msgstr ""
+"一旦[程式基底](../glossary.md#codebase)越容易被發現，更多的潛在協作者也就找得"
+"到它。不能只是發表個程式基底，然後就盼望他人找得到這套程式基底，更需要主動積"
+"極。"
+
+#: ./criteria/make-the-codebase-findable.md:block 7 (paragraph)
+msgid ""
+"A metadata description file increases discoverability. Well-written metadata"
+" containing a unique and persistent identifier, such as a Wikidata item or "
+"FSF software directory listing (thus being part of the semantic web), makes "
+"the codebase easier for people to refer, cite, disambiguate and discover "
+"through third party tools."
+msgstr ""
+"有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中"
+"介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體目錄"
+"列表之中（使程式基底成為語意網路中的一部份），他人就能更容易透過第三方工具參"
+"考、引用、辨別、發現程式基底。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The name of the codebase SHOULD be descriptive and free from acronyms, "
+"abbreviations, puns or organizational branding."
+msgstr "程式基底名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關"
+"語，或組織單位品牌名稱或抬頭等。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a short description that helps someone understand "
+"what the codebase is for or what it does."
+msgstr "程式基底說明「應該」要簡短，幫助他人瞭解程式基底的目的與作用。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Maintainers SHOULD submit the codebase to relevant software catalogs."
+msgstr "維護人員「應該」將程式基底提交至相關的軟體目錄上。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a website which describes the problem the codebase "
+"solves using the preferred jargon of different potential users of the "
+"codebase (including technologists, policy experts and managers)."
+msgstr "程式基底「應該」要架設網站，內容中以程式基底各類潛在使用者（技術人員、政策專"
+"家、管理人員等）偏好的業內用語，描述程式基底所能解決的問題。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by codebase name."
+msgstr "在搜尋引擎查找程式基底名稱時，「應該」能搜尋得到程式基底。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD be findable using a search engine by describing the "
+"problem it solves in natural language."
+msgstr "在使用搜尋引擎時，如果以自然語言描述程式基底所能解決的問題，「應該」能搜尋得"
+"到程式基底。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD have a unique and persistent identifier where the entry "
+"mentions the major contributors, [repository](../glossary.md#repository) "
+"location and website."
+msgstr ""
+"程式基底「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、[儲存庫](.."
+"/glossary.md#repository)、位置、網站等。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid ""
+"The codebase SHOULD include a machine-readable metadata description, for "
+"example in a "
+"[publiccode.yml](https://github.com/publiccodeyml/publiccode.yml) file."
+msgstr ""
+"程式基底「應該」包含機器可讀的中介資料說明，例如採用[publiccode."
+"yml](https://github.com/publiccodeyml/publiccode.yml)格式的檔案。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "A dedicated domain name for the codebase is OPTIONAL."
+msgstr "「可選擇」是否為程式基底設置專用的網域名稱。"
+
+#: ./criteria/make-the-codebase-findable.md:block 9 (unordered list)
+msgid "Regular presentations at conferences by the community are OPTIONAL."
+msgstr "「可選擇」是否在社群舉辦的會議中定期進行簡報。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check that the codebase name is descriptive and free of puns."
+msgstr "檢查程式基底名稱是否描述說明其用途，且不包含雙關語。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of acronyms and abbreviations or that "
+"the acronyms or abbreviations in the name are more universally known than "
+"the longer forms."
+msgstr "檢查程式基底名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比"
+"完整名稱更熟為人知。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase name is free of organizational branding, unless that"
+" organization is of the codebase community itself."
+msgstr "檢查程式基底是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是程式基底社"
+"群成員。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase repository has a short description of the codebase."
+msgstr "檢查程式基底儲存庫是否包含程式基底的簡短描述。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for the codebase listing in relevant software catalogs."
+msgstr "檢查程式基底有刊登在相關軟體型錄上。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check for a codebase website which describes the problem the codebase "
+"solves."
+msgstr "檢查程式基底的網站有描述程式基底能夠解決的問題。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by the codebase name."
+msgstr "檢查以程式基底名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將程式基底列"
+"在搜尋結果中。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check that the codebase appears in the results on more than one major search"
+" engine when searching by using natural language, for instance, using the "
+"short description."
+msgstr "檢查以自然語言來作搜尋，例如使用程式基底的簡短描述時，有超過一個的常用主流搜"
+"尋引擎，都將程式基底放在搜尋結果中。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for mention of the major "
+"contributors."
+msgstr "檢查永久唯一識別碼條目有提及主要貢獻者。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the repository location."
+msgstr "檢查永久唯一識別碼條目中有包含儲存庫位置。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid ""
+"Check unique and persistent identifier entries for the codebase website."
+msgstr "檢查永久唯一識別碼條目有列出程式基底網站。"
+
+#: ./criteria/make-the-codebase-findable.md:block 11 (unordered list)
+msgid "Check for a machine-readable metadata description file."
+msgstr "檢查中介資料說明檔是機器可讀的格式。"
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Contribute a description of the policy area or problem this codebase acts on"
+" or operates."
+msgstr "貢獻一段說明此程式基底作用的政策領域，或所處理問題的描述。"
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Test your problem description with peers outside of your context who aren't "
+"familiar with the codebase."
+msgstr "請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。"
+
+#: ./criteria/make-the-codebase-findable.md:block 13 (unordered list)
+msgid ""
+"Present on how the codebase implements the [policy](../glossary.md#policy) "
+"at relevant conferences."
+msgstr "在相關會議上作簡報，介紹程式基底如何執行[政策](../glossary.md#policy)。"
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Search trademark databases to avoid confusion or infringement before "
+"deciding the name."
+msgstr "在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。"
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as social media account descriptions."
+msgstr "在引用到程式基底的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。"
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Budget for content design and Search Engine Optimization skills in the team."
+msgstr "為團隊編列內容設計與實作 SEO 搜尋引擎最佳化技能的預算。"
+
+#: ./criteria/make-the-codebase-findable.md:block 15 (unordered list)
+msgid ""
+"Make sure people involved in the project present at relevant conferences."
+msgstr "確保專案參與人員出席相關會議，或作簡報介紹。"
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Search engine optimization, for instance adding a "
+"[sitemap](https://www.sitemaps.org/protocol.html)."
+msgstr "實作搜尋引擎最佳化，例如加入[網站地圖](https://www.sitemaps.org/protocol."
+"html)。"
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid ""
+"Use the short description wherever the codebase is referenced, for instance,"
+" as the repository description."
+msgstr "在引用到程式基底的地方，都使用簡短描述，例如放到儲存庫中的說明。"
+
+#: ./criteria/make-the-codebase-findable.md:block 17 (unordered list)
+msgid "Suggest conferences to present at and present at them."
+msgstr "推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。"
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[Introduction to "
+"Wikidata](https://www.wikidata.org/wiki/Wikidata:Introduction) by the "
+"Wikidata community."
+msgstr ""
+"Wikidata "
+"維基數據社群《[維基數據簡介](https://www.wikidata.org/wiki/Wikidata:Introduction)》。"
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"[FSF software directory listing](https://directory.fsf.org/wiki/Main_Page) "
+"by the Free Software Foundation."
+msgstr "FSF 自由軟體基金會《[FSF 軟體目錄列表](https://directory.fsf.org/wiki/Main_Page)》。"
+
+#: ./criteria/make-the-codebase-findable.md:block 19 (unordered list)
+msgid ""
+"The [FAIR Guiding Principles for scientific data management and "
+"stewardship](https://www.go-fair.org/fair-principles/) by the GO FAIR "
+"International Support and Coordination Office provide a nice list of "
+"attributes that make (meta)data more machine actionable (and hence more "
+"findable). Some of these apply directly to codebases, while others may "
+"provoke exploration into what the codebase equivalent would be."
+msgstr ""
+"GO FAIR 國際支援與合作辦公室所撰寫的《[FAIR "
+"科學資料管理與監督指導原則](https://www.go-fair.org/fair-principles/)》，提供"
+"一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓機器採取行動（"
+"也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套"
+"用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 3 (paragraph)
+msgid "order: 3 redirect_from:"
+msgstr "order: 3 redirect_from:"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/reusable-and-portable-codebases"
+msgstr "criteria/reusable-and-portable-codebases"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 4 (unordered
+#: list)
+msgid "criteria/create-reusable-and-portable-code"
+msgstr "criteria/create-reusable-and-portable-code"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 5 (header)
+msgid "Make the codebase reusable and portable"
+msgstr "程式基底要可重複使用且可移植"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 6 (paragraph)
+msgid ""
+"Creating reusable and portable [code](../glossary.md#code) enables policy "
+"makers, developers and designers to reuse what has been developed, test it, "
+"improve it and contribute those improvements back, leading to better "
+"quality, cheaper maintenance and higher reliability."
+msgstr ""
+"編寫可重複使用且可移植的[程式碼](../glossary.md#code)，讓政策制定者、開發人員"
+"與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻回程式基底中"
+"，如此可提高品質、降低維護成本、增強可靠性。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 7 (paragraph)
+msgid ""
+"Thoughtfully and purposefully designing a "
+"[codebase](../glossary.md#codebase) for reusability allows for the mission, "
+"vision and scope of the codebase to be shared by multiple parties. Codebases"
+" developed and used by multiple parties are more likely to benefit from a "
+"self-sustaining community."
+msgstr ""
+"以重複利用為前提籌劃設計[程式基底](../glossary.md#codebase)，更容易與多方共享"
+"程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，更可以從能自我運"
+"作的社群中獲益。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 8 (paragraph)
+msgid ""
+"Organizing a codebase such that it is composed of well documented modules "
+"improves reusability and maintainability. A module is easier to reuse in "
+"[another context](../glossary.md#different-contexts) if its purpose is "
+"clearly documented."
+msgstr ""
+"以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記"
+"錄用途的模組，更容易在[另一種情境](../glossary.md#different-"
+"contexts)中重複利用。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 9 (paragraph)
+msgid ""
+"Source code which does not rely on the situation-specific infrastructure of "
+"any contributor, vendor or deployment can be tested by any other "
+"contributor."
+msgstr "原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢"
+"獻者都能測試該原始碼。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase MUST be developed to be reusable in different contexts."
+msgstr "程式基底「必須」開發成能在不同情境中重複使用。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The codebase MUST be independent from any secret, undisclosed, proprietary "
+"or non-open licensed software or services for execution and understanding."
+msgstr "程式基底「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務"
+"，以供執行與瞭解。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be in use by multiple parties."
+msgstr "程式基底「應該」有多方單位使用。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The roadmap SHOULD be influenced by the needs of multiple parties."
+msgstr "發展路線圖「應該」有多方單位的需求影響。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The development of the codebase SHOULD be a collaboration between multiple "
+"parties."
+msgstr "程式基底開發「應該」由多方單位協作。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Configuration SHOULD be used to make [source code](../glossary.md#source-"
+"code) adapt to context specific needs."
+msgstr "「應該」使用組態設定方式以將[原始碼](../glossary.md#source-"
+"code)調整成能適應各情境的特定需求。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid "The codebase SHOULD be localizable."
+msgstr "程式基底「應該」能夠在地化。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Source code and its documentation SHOULD NOT contain situation-specific "
+"information."
+msgstr "原始碼與其文件「不應該」包含特定情況專用的資訊。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"Codebase modules SHOULD be documented in such a way as to enable reuse in "
+"codebases in other contexts."
+msgstr "程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 11 (unordered
+#: list)
+msgid ""
+"The software SHOULD NOT require services or platforms available from only a "
+"single vendor."
+msgstr "軟體「不應該」要求僅有單一供應商能提供的服務或平台。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm with someone in a similar role at another organization if they can "
+"use the codebase and what that would entail."
+msgstr "與另一組織單位角色與您相似的人確認，看他們是否能利用程式基底，以及需要怎麼進"
+"行。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Confirm that the codebase can run without using any proprietary or non open-"
+"licensed software or services."
+msgstr "確認程式基底不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"If the codebase is in early development before a production-ready release, "
+"then check for evidence of ambition to obtain collaborators."
+msgstr "若程式基底處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的"
+"意圖跡象。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Or if the codebase is very mature and stable with very infrequent fixes, "
+"patches, or contributions:"
+msgstr "或是如果程式基底非常成熟與穩定，鮮少需要修正、改善或貢獻："
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase is in use by multiple parties or in multiple "
+"contexts."
+msgstr "檢查是否有多方單位，或是有在多種情境下正使用程式基底。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check for documented and budgeted commitments of collaboration."
+msgstr "檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Otherwise:"
+msgstr "若是沒有，則："
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid "Check that the codebase contributors are from multiple parties."
+msgstr "檢查程式基底貢獻者是否來自多方單位。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the codebase files and commit history do not include situation-"
+"specific data."
+msgstr "檢查程式基底檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 13 (unordered
+#: list)
+msgid ""
+"Check that the software can be deployed and run without services or "
+"platforms available from a single vendor."
+msgstr "檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid ""
+"Document your [policy](../glossary.md#policy) with enough clarity and detail"
+" that it can be understood outside of its original context."
+msgstr "為您的[政策](../glossary.md#policy)撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Make sure your organization is listed as a known user by the codebase."
+msgstr "確保程式基底有將貴組織單位列為已知使用者。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 15 (unordered
+#: list)
+msgid "Identify other organizations for your teams to collaborate with."
+msgstr "找出貴團隊想要協作的其他組織單位。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid ""
+"Make sure that stakeholders and business owners understand that reusability "
+"is an explicit codebase goal as this reduces technical debt and provides "
+"sustainability for the codebase."
+msgstr "確認利害關係人與業主能夠瞭解，程式基底是以重複利用為明確目標，因而得以減少程"
+"式碼技術債，並讓程式基底可以永續發展。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 17 (unordered
+#: list)
+msgid "Make sure that your teams are collaborating with other teams."
+msgstr "確認您的團隊與其他團隊能相互協作。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 19 (paragraph)
+msgid "Source should be designed:"
+msgstr "原始碼應該設計成："
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "for reuse by other users and organizations regardless of locale,"
+msgstr "能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "to solve a general problem instead of a specific one,"
+msgstr "能解決通用性質問題，而非特定問題，"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid "in logically meaningful and isolated modules,"
+msgstr "以邏輯上具有意義且獨立的模組構成，"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 20 (unordered
+#: list)
+msgid ""
+"so that someone in a similar organization facing a similar problem would be "
+"able to use (parts of) the solution."
+msgstr "如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 21 (paragraph)
+msgid ""
+"Make sure that the codebase documentation describes the build-time and "
+"runtime dependencies. If your context requires deploying to proprietary "
+"platforms or using proprietary components, make sure that collaborators can "
+"develop, use, test, and deploy without them."
+msgstr ""
+"確保程式基底文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需"
+"要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情"
+"況下，就能進行開發、使用、測試、部署等。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 22 (paragraph)
+msgid ""
+"For each commit, reviewers verify that content does not include situation-"
+"specific data such as hostnames, personal and organizational data, or tokens"
+" and passwords."
+msgstr "在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個"
+"人與組織單位資料、代符與密碼等。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Making source code open and reusable](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable) by the UK Government"
+" Digital Service."
+msgstr ""
+"英國政府數位服務團《[讓原始碼開放且可重複利用](https://www.gov.uk/service-"
+"manual/technology/making-source-code-open-and-reusable)》。"
+
+#: ./criteria/make-the-codebase-reusable-and-portable.md:block 24 (unordered
+#: list)
+msgid ""
+"[Localization vs. "
+"Internationalization](https://www.w3.org/International/questions/qa-i18n) by"
+" the World Wide Web Consortium."
+msgstr ""
+"W3C 全球資訊網協會《[在地化與國際化](https://www.w3.org/International/questions/qa-i18n)》。"
+
+#: ./criteria/publish-with-an-open-license.md:block 3 (paragraph)
+msgid "order: 13 redirect_from:"
+msgstr "order: 13 redirect_from:"
+
+#: ./criteria/publish-with-an-open-license.md:block 4 (unordered list)
+msgid "criteria/open-licenses"
+msgstr "criteria/open-licenses"
+
+#: ./criteria/publish-with-an-open-license.md:block 5 (header)
+msgid "Publish with an open license"
+msgstr "發行採用開放授權"
+
+#: ./criteria/publish-with-an-open-license.md:block 6 (paragraph)
+msgid ""
+"An open and well known license makes it possible for anyone to see the "
+"[source code](../glossary.md#source-code) in order to understand how it "
+"works, to use it freely and to contribute to the "
+"[codebase](../glossary.md#codebase). This enables a vendor ecosystem to "
+"emerge around the codebase."
+msgstr ""
+"採用開放且為人熟知的授權，讓任何人都可以查看[原始碼](../glossary.md#source-"
+"code)，使其能瞭解運作方式、自由使用，並且能為[程式基底](../glossary."
+"md#codebase)做出貢獻。這也能促進供應商建立出以程式基底為中心的生態系。"
+
+#: ./criteria/publish-with-an-open-license.md:block 7 (paragraph)
+msgid ""
+"Clearly indicating the license for each file within a codebase facilitates "
+"correct reuse and attribution of parts of a codebase."
+msgstr "明確指出程式基底中每一個檔案的授權，讓使用者能正確重複利用程式基底的部分內容"
+"，並表彰作者名稱。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code and documentation MUST be licensed such that it may be "
+"freely reusable, changeable and redistributable."
+msgstr "所有原始碼與文件，皆「必須」採用使其得以自由重複使用、自由修改、自由再次散布"
+"的授權條款。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Software source code MUST be licensed under an [OSI-approved or FSF "
+"Free/Libre license](https://spdx.org/licenses/)."
+msgstr ""
+"軟體原始碼「必須」採用[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款](https://spdx.org/licenses/)。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid "All source code MUST be published with a license file."
+msgstr "所有原始碼皆「必須」搭配授權條款檔案一併發行。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Contributors MUST NOT be required to transfer copyright of their "
+"contributions to the codebase."
+msgstr "「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給程式基底。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"All source code files in the codebase SHOULD include a copyright notice and "
+"a license header that are machine-readable."
+msgstr "程式基底中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內"
+"容。"
+
+#: ./criteria/publish-with-an-open-license.md:block 9 (unordered list)
+msgid ""
+"Having multiple licenses for different types of source code and "
+"documentation is OPTIONAL."
+msgstr "「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。"
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the codebase is clearly licensed."
+msgstr "確認程式基底有清楚給予授權條款。"
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that the license for the source code is on the [OSI-approved or FSF "
+"Free/Libre license list](https://spdx.org/licenses/) and the license for "
+"documentation [conforms to the Open "
+"Definition](https://opendefinition.org/licenses/)."
+msgstr ""
+"確認原始碼的授權條款有列於[經 OSI 開放原始碼促進會所批准，或由 FSF "
+"自由軟體基金會所發表的自由授權條款清單](https://spdx.org/licenses/)，以及文件的授權條款有[符合「開放定義」](https://opendefinition.org/licenses/)。"
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid "Confirm that the licenses used in the codebase are included as files."
+msgstr "確認程式基底中有包含其採用的授權條款檔案。"
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Confirm that contribution guidelines and "
+"[repository](../glossary.md#repository) configuration do not require "
+"transfer of copyright."
+msgstr "確認貢獻指引中，以及[儲存庫](../glossary."
+"md#repository)的組態設定中，沒有要求貢獻者轉讓著作權。"
+
+#: ./criteria/publish-with-an-open-license.md:block 11 (unordered list)
+msgid ""
+"Check for machine-readable license checking in the codebase [continuous "
+"integration](../glossary.md#continuous-integration) tests."
+msgstr ""
+"在程式基底[持續整合](../glossary.md#continuous-"
+"integration)測試中，確認是否有檢查授權內容為機器可讀的檢查項目。"
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop [policy](../glossary.md#policy) that requires source code to be "
+"[open source](../glossary.md#open-source)."
+msgstr ""
+"制定要求原始碼必須採用[開放原始碼](../glossary.md#open-"
+"source)授權的[政策](../glossary.md#policy)。"
+
+#: ./criteria/publish-with-an-open-license.md:block 13 (unordered list)
+msgid ""
+"Develop policy that disincentivizes non-open source code and technology in "
+"procurement."
+msgstr "制定抑制採購非開放原始碼授權程式碼，與非開放科技的政策。"
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Only work with open source vendors that deliver their source code by "
+"publishing it under an open source license."
+msgstr "只與能採用開放原始碼授權交付、與發行其原始碼的開放原始碼軟體供應商合作。"
+
+#: ./criteria/publish-with-an-open-license.md:block 15 (unordered list)
+msgid ""
+"Beware that even though [Creative Commons "
+"licenses](https://creativecommons.org/licenses/) are great for "
+"documentation, licenses that stipulate Non-Commercial or No Derivatives are "
+"NOT freely reusable, changeable and redistributable and don't fulfill these "
+"requirements."
+msgstr ""
+"請注意，雖然[創用CC授權](https://creativecommons.org/licenses/)適合用於文件作品，但其中指明「非商業性」或「禁止改作」的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。"
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid "Add a new `license` file to every new codebase created."
+msgstr "每當建立新的程式基底時，都要加入新的「`license`」授權條款檔案。"
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"Add a copyright notice and a license header to every new source code file "
+"created."
+msgstr "每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。"
+
+#: ./criteria/publish-with-an-open-license.md:block 17 (unordered list)
+msgid ""
+"When source code is being reused by the codebase, make sure that it has a "
+"license that is compatible with the license or licenses of the codebase."
+msgstr "每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。"
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Open source definition](https://opensource.org/osd) by the Open Source "
+"Initiative, all open source licenses meet this definition."
+msgstr ""
+"開放原始碼促進會所發表的《[開放原始碼定義](https://opensource.org/osd)》，所有開放原始碼授權條款皆符合這套定義。"
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[Animated video introduction to Creative "
+"Commons](https://creativecommons.org/about/videos/creative-commons-kiwi) by "
+"Creative Commons Aotearoa New Zealand."
+msgstr ""
+"紐西蘭CC Aotearoa《[創用CC介紹動畫影片](https://creativecommons.org/about/"
+"videos/creative-commons-kiwi)》。"
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[REUSE Initiative specification](https://reuse.software/spec/) by Free "
+"Software Foundation Europe for unambiguous, human-readable and machine-"
+"readable copyright and licensing information."
+msgstr ""
+"歐洲自由軟體基金會所發表的《[REUSE 倡議規範](https://reuse.software/spec/"
+")》，提供規範明確、人類可讀以及機器可讀的著作權與授權資訊。"
+
+#: ./criteria/publish-with-an-open-license.md:block 19 (unordered list)
+msgid ""
+"[SPDX License List](https://spdx.org/licenses/) by the Linux Foundation with"
+" standardized, machine-readable abbreviations for most licenses."
+msgstr ""
+"Linux 基金會所發表的 [SPDX 授權條款清單](https://spdx.org/licenses/"
+")，提供經標準化、且機器可讀的大多數授權條款縮寫表示法。"
+
+#: ./criteria/require-review-of-contributions.md:block 3 (paragraph)
+msgid "order: 7 redirect_from:"
+msgstr "order: 7 redirect_from:"
+
+#: ./criteria/require-review-of-contributions.md:block 4 (unordered list)
+msgid "criteria/require-review"
+msgstr "criteria/require-review"
+
+#: ./criteria/require-review-of-contributions.md:block 5 (header)
+msgid "Require review of contributions"
+msgstr "要求審查貢獻內容"
+
+#: ./criteria/require-review-of-contributions.md:block 6 (paragraph)
+msgid ""
+"Peer-review of contributions is essential for [source "
+"code](../glossary.md#source-code) quality, reducing security risks and "
+"operational risks."
+msgstr "同儕審查貢獻是[原始碼](../glossary.md#source-"
+"code)提升品質的關鍵，也能降低安全性風險與營運風險。"
+
+#: ./criteria/require-review-of-contributions.md:block 7 (paragraph)
+msgid ""
+"Requiring thorough review of contributions encourages a culture of making "
+"sure every contribution is of high quality, completeness and value. Source "
+"code review increases the chance of discovering and fixing potential bugs or"
+" mistakes before they are added to the [codebase](../glossary.md#codebase). "
+"Knowing that all source code was reviewed discourages a culture of blaming "
+"individuals, and encourages a culture of focusing on solutions."
+msgstr ""
+"要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始"
+"碼能提高在原始碼加入[程式基底](../glossary.md#codebase)之前，就發現與修正潛在"
+"臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，"
+"反倒是鼓勵每個人都專注在解決方案上。"
+
+#: ./criteria/require-review-of-contributions.md:block 8 (paragraph)
+msgid ""
+"A [policy](../glossary.md#policy) of prompt reviews assures contributors of "
+"a guaranteed time for feedback or collaborative improvement, which increases"
+" both rate of delivery and contributor engagement."
+msgstr ""
+"快速審查[政策](../glossary.md#policy)在於向貢獻者保證，必定在一段時間內提供意"
+"見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參與的熱度。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"All contributions that are accepted or committed to release versions of the "
+"codebase MUST be reviewed by another contributor."
+msgstr "所有被接受或是送交給程式基底正式發行版本中的貢獻內容，都「必須」經過另一位貢"
+"獻者審查。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews MUST include source, policy, tests and documentation."
+msgstr "審查「必須」包含原始碼、政策、測試、文件等。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviewers MUST provide feedback on all decisions to not accept a "
+"contribution."
+msgstr "如果不接受貢獻內容，審查人員「必須」提供意見回饋。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"The review process SHOULD confirm that a contribution conforms to the "
+"standards, architecture and decisions set out in the codebase in order to "
+"pass review."
+msgstr "審查流程「應該」確認貢獻內容遵循程式基底的標準、架構、決策安排等，以通過審查"
+"。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Reviews SHOULD include running both the software and the tests of the "
+"codebase."
+msgstr "審查內容「應該」包含執行軟體與執行程式基底測試。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Contributions SHOULD be reviewed by someone in a different context than the "
+"contributor."
+msgstr "貢獻內容「應該」由與貢獻者不同背景情境的人來審查。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid ""
+"Version control systems SHOULD NOT accept non-reviewed contributions in "
+"release versions."
+msgstr "版本控制系統「不應該」在程式基底的正式發行版本中，接受未經審查的貢獻內容。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Reviews SHOULD happen within two business days."
+msgstr "審查「應該」在兩個工作天內進行。"
+
+#: ./criteria/require-review-of-contributions.md:block 10 (unordered list)
+msgid "Performing reviews by multiple reviewers is OPTIONAL."
+msgstr "「可選擇」是否由多位審查人員進行審查。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Confirm that every commit in the history has been reviewed by a different "
+"contributor."
+msgstr "確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that reviews include source, policy, tests and documentation."
+msgstr "確認審查內容包含原始碼、政策、測試、文件等。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Confirm that rejected contributions were appropriately explained."
+msgstr "針對未被採用的貢獻內容，確認有適當解釋原因。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check if guidelines for reviewers include instructions to review for "
+"conformance to standards, architecture and codebase guidelines."
+msgstr "檢查審查人員指引中，有包含是否遵循標準、架構、程式基底指引等指示。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check with reviewers if they run the software and tests during review."
+msgstr "檢查審查人員在審查時是否有執行軟體與測試。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check with reviewers if commits have been reviewed by a different "
+"contributor in a different context."
+msgstr "與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid ""
+"Check for use of branch protection in the [version "
+"control](../glossary.md#version-control) system."
+msgstr "檢查[版本控制](../glossary.md#version-control)系統中是否有採用分支保護。"
+
+#: ./criteria/require-review-of-contributions.md:block 12 (unordered list)
+msgid "Check the times between contribution submission and review."
+msgstr "檢查貢獻提交與審查之間的時間間隔。"
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Institute a 'four eyes' policy where everything, not just source code, is "
+"reviewed."
+msgstr "制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。"
+
+#: ./criteria/require-review-of-contributions.md:block 14 (unordered list)
+msgid ""
+"Use a version control system or methodology that enables review and "
+"feedback."
+msgstr "採用具有審查與意見回饋功能的版本控制系統，或作業流程。"
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make delivering great software a shared objective."
+msgstr "將交付妥善軟體作為共同目標。"
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Make sure writing and reviewing contributions to source, policy, "
+"documentation and tests are considered equally valuable."
+msgstr "確保如原始碼、政策、文件、測試等的貢獻內容撰寫與審查，皆受到同等重視。"
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid ""
+"Create a culture where all contributions are welcome and everyone is "
+"empowered to review them."
+msgstr "創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。"
+
+#: ./criteria/require-review-of-contributions.md:block 16 (unordered list)
+msgid "Make sure no contributor is ever alone in contributing to a codebase."
+msgstr "確保貢獻者在貢獻內容給程式基底時，不是獨自一人埋頭苦幹。"
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Ask other contributors on the codebase to review your work, in your "
+"organization or outside of it."
+msgstr "請程式基底的其他貢獻者，審查您在貴組織單位內外的工作成果。"
+
+#: ./criteria/require-review-of-contributions.md:block 18 (unordered list)
+msgid ""
+"Try to respond to others' requests for review promptly, initially providing "
+"feedback about the concept of the change."
+msgstr "當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。"
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[How to review code the GDS way](https://gds-"
+"way.cloudapps.digital/manuals/code-review-guidelines.html#content) by the UK"
+" Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[英國政府數位服務團程式碼審查程序](https://gds-way.cloudapps.digital/manuals/code-"
+"review-guidelines.html#content)》。"
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"Branch protection on "
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) and "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/)."
+msgstr ""
+"[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-"
+"merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-"
+"protected-branches) 與 "
+"[GitLab](https://about.gitlab.com/blog/2014/11/26/keeping-your-code-"
+"protected/) 平臺的分支保護說明。"
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[The Gentle Art of Patch Review](https://sage.thesharps.us/2014/09/01/the-"
+"gentle-art-of-patch-review/) by Sage Sharp."
+msgstr ""
+"Sage Sharp《[程式修補審查的和善藝術](https://sage.thesharps.us/2014/09/01/the-gentle-"
+"art-of-patch-review/)》。"
+
+#: ./criteria/require-review-of-contributions.md:block 20 (unordered list)
+msgid ""
+"[Measuring "
+"Engagement](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) by Mozilla."
+msgstr ""
+"Mozilla《[參與度評測成果](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-"
+"mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)》。"
+
+#: ./criteria/use-a-coherent-style.md:block 3 (paragraph)
+msgid "order: 15 redirect_from:"
+msgstr "order: 15 redirect_from:"
+
+#: ./criteria/use-a-coherent-style.md:block 4 (unordered list)
+msgid "criteria/style"
+msgstr "criteria/style"
+
+#: ./criteria/use-a-coherent-style.md:block 5 (header)
+msgid "Use a coherent style"
+msgstr "風格要前後一致"
+
+#: ./criteria/use-a-coherent-style.md:block 6 (paragraph)
+msgid ""
+"Following a consistent and coherent style enables contributors in different "
+"environments to work together. Unifying vocabularies reduces friction in "
+"communication between contributors."
+msgstr "採用前後一致的風格，讓不同環境的貢獻者能夠一同合作。用詞統一能減少貢獻者之間"
+"在溝通上的摩擦。"
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The [codebase](../glossary.md#codebase) MUST use a coding or writing style "
+"guide, either the codebase community's own or an existing one referred to in"
+" the codebase."
+msgstr ""
+"[程式基底](../glossary.md#codebase)「必須」遵守程式碼撰寫風格指引、或文件寫作"
+"風格指引，可以是程式基底社群自身的風格指引，或是程式基底有採用的既有風格。"
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid "Contributions SHOULD pass automated tests on style."
+msgstr "貢獻內容「應該」通過自動化的風格測試。"
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"The style guide SHOULD include expectations for inline comments and "
+"documentation for non-trivial sections."
+msgstr "風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與為其寫下說明文件"
+"的期待。"
+
+#: ./criteria/use-a-coherent-style.md:block 8 (unordered list)
+msgid ""
+"Including expectations for [understandable English](use-plain-english.md) in"
+" the style guide is OPTIONAL."
+msgstr "「可選擇」是否將[可理解的白話英語](use-plain-english."
+"md)期望加入風格指引之中。"
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid ""
+"Confirm that contributions are in line with the style guides specified in "
+"the documentation."
+msgstr "確認貢獻內容有遵循文件中指定的風格指引。"
+
+#: ./criteria/use-a-coherent-style.md:block 10 (unordered list)
+msgid "Check for the presence of automated tests on style."
+msgstr "檢查是否有自動化的風格測試。"
+
+#: ./criteria/use-a-coherent-style.md:block 12 (unordered list)
+msgid ""
+"Create, follow and continually improve on a style guide for "
+"[policy](../glossary.md#policy) and documentation as well as document this "
+"in the codebase, for example in the `CONTRIBUTING` or `README`."
+msgstr ""
+"為[政策](../glossary.md#policy)與文件建立風格指引，遵守並且持續改善，同時記錄"
+"到程式基底文件中，像是「`CONTRIBUTING`」或「`README`」檔案。"
+
+#: ./criteria/use-a-coherent-style.md:block 14 (unordered list)
+msgid ""
+"Include written language, source, test and policy standards in your "
+"organizational definition of quality."
+msgstr "將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。"
+
+#: ./criteria/use-a-coherent-style.md:block 16 (paragraph)
+msgid ""
+"If the codebase does not already have engineering guidelines or other "
+"contributor guidance, start by adding documentation to the "
+"[repository](../glossary.md#repository) describing whatever is being done "
+"now, for example in the `CONTRIBUTING` or `README`. An important purpose of "
+"the file is to communicate design preferences, naming conventions, and other"
+" aspects machines can't easily check. Guidance should include what would be "
+"expected from [source code](../glossary.md#source-code) contributions in "
+"order for them to be merged by the maintainers, including source, tests and "
+"documentation. Continually improve upon and expand this documentation with "
+"the aim of evolving this documentation into engineering guidelines."
+msgstr ""
+"如果程式基底還沒有工程指引，或其他貢獻者指引，則請先在[儲存庫](../glossary.md"
+"#repository)中加入相關文件，像是「`CONTRIBUTING`」或「`README`」檔案，並描述"
+"目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則"
+"，以及機器不容易檢查的其他層面。指引應該包含貢獻的[原始碼](../glossary.md"
+"#source-code)預期該符合哪些要求，才會被維護人員合併至程式基底中，包括原始碼、"
+"測試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。"
+
+#: ./criteria/use-a-coherent-style.md:block 17 (paragraph)
+msgid "Additionally:"
+msgstr "此外："
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Use a linter."
+msgstr "使用 linter 程式碼品質梳理工具。"
+
+#: ./criteria/use-a-coherent-style.md:block 18 (unordered list)
+msgid "Add linter configurations to the codebase."
+msgstr "在程式基底中加入 linter 梳理工具的組態設定。"
+
+#: ./criteria/use-a-coherent-style.md:block 20 (unordered list)
+msgid ""
+"[Programming style](https://en.wikipedia.org/wiki/Programming_style) on "
+"Wikipedia."
+msgstr "維基百科上的《[程式碼風格](https://en.wikipedia.org/wiki/"
+"Programming_style)》條目。"
+
+#: ./criteria/use-continuous-integration.md:block 3 (paragraph)
+msgid "order: 12 redirect_from:"
+msgstr "order: 12 redirect_from:"
+
+#: ./criteria/use-continuous-integration.md:block 4 (unordered list)
+msgid "criteria/continuous-integration"
+msgstr "criteria/continuous-integration"
+
+#: ./criteria/use-continuous-integration.md:block 5 (header)
+msgid "Use continuous integration"
+msgstr "使用持續整合"
+
+#: ./criteria/use-continuous-integration.md:block 6 (paragraph)
+msgid ""
+"Asynchronous collaboration is enabled by developers merging their work to a "
+"shared branch frequently, verified by automated tests. The more frequent the"
+" merging and the smaller the contribution, the easier it is to resolve merge"
+" conflicts."
+msgstr ""
+"透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同"
+"步協作。合併的頻率越頻繁、貢獻的規模越小，在合併時所發生的衝突就越容易解決。"
+
+#: ./criteria/use-continuous-integration.md:block 7 (paragraph)
+msgid ""
+"Automated testing of all functionality provides confidence that "
+"contributions are working as intended and have not introduced errors, and "
+"allows reviewers to focus on the structure and approach of the contribution."
+" The more focused the test, the easier it is to clearly identify and "
+"understand errors as they arise."
+msgstr ""
+"自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓"
+"審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。"
+
+#: ./criteria/use-continuous-integration.md:block 8 (paragraph)
+msgid ""
+"Documenting a codebase's [continuous integration](../glossary.md#continuous-"
+"integration) workflow helps contributors understand the expectations of "
+"contributions. Continuous integration allows for an easier monitoring of the"
+" state of the [codebase](../glossary.md#codebase)."
+msgstr ""
+"以文件記錄程式基底的[持續整合](../glossary.md#continuous-integration)工作流程"
+"，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓監管[程式基底](../glossary."
+"md#codebase)狀態變得更為簡單。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"All functionality in the [source code](../glossary.md#source-code) MUST have"
+" automated tests."
+msgstr "[原始碼](../glossary.md#source-code)中的所有功能，都「必須」有自動化測試。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Contributions MUST pass all automated tests before they are admitted into "
+"the codebase."
+msgstr "所有貢獻內容都「必須」先通過自動化測試，才能上傳至程式基底。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have guidelines explaining how to structure contributions."
+msgstr "程式基底「必須」有解說如何撰寫貢獻內容結構的相關指引。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase MUST have active contributors who can review contributions."
+msgstr "程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Automated test results for contributions SHOULD be public."
+msgstr "「應該」公開貢獻內容的自動化測試結果。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"The codebase guidelines SHOULD state that each contribution should focus on "
+"a single issue."
+msgstr "程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid "Source code test and documentation coverage SHOULD be monitored."
+msgstr "「應該」監管原始碼測試與文件的涵蓋範圍。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing [policy](../glossary.md#policy) and documentation for consistency "
+"with the source and vice versa is OPTIONAL."
+msgstr "「可選擇」是否測試[政策](../glossary."
+"md#policy)和文件，與原始碼之間有無一致性，或是反之亦然。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing policy and documentation for style and broken links is OPTIONAL."
+msgstr "「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。"
+
+#: ./criteria/use-continuous-integration.md:block 10 (unordered list)
+msgid ""
+"Testing the software by using examples in the documentation is OPTIONAL."
+msgstr "「可選擇」是否使用文件中的範例來測試軟體。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Confirm that there are tests present."
+msgstr "確認有測試可用。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code coverage tools check that coverage is at 100% of "
+"the source code."
+msgstr "確認原始碼覆蓋率工具能檢查到 100% 的原始碼。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contributions are only admitted into the codebase after all of "
+"the tests are passed."
+msgstr "確認貢獻內容只有在通過所有測試後，才會認可上傳至程式基底。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that contribution guidelines explain how to structure contributions."
+msgstr "確認有貢獻指引解說如何撰寫貢獻內容的結構。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid ""
+"Confirm that there are contributions from within the last three months."
+msgstr "確認最近三個月內有貢獻內容上傳。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check that test results are viewable."
+msgstr "檢查是否可以查看測試結果。"
+
+#: ./criteria/use-continuous-integration.md:block 12 (unordered list)
+msgid "Check if source code coverage data is published."
+msgstr "檢查是否有公布原始碼覆蓋率數據。"
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Involve managers as well as developers and designers as early in the process"
+" as possible and keep them engaged throughout development of your policy."
+msgstr "儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。"
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure there are also automated tests set up for policy documentation."
+msgstr "確保政策文件也有設好自動化測試。"
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid "Fix policy documentation promptly if it fails a test."
+msgstr "如果政策文件未能通過測試，請快速修正。"
+
+#: ./criteria/use-continuous-integration.md:block 14 (unordered list)
+msgid ""
+"Make sure the source code reflects any changes to the policy (see [Maintain "
+"version control](maintain-version-control.md))."
+msgstr "確保原始碼能反映出政策的任何變動（請參閱〈[維護版本控制](maintain-version-"
+"control.md)〉）。"
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Make sure to test with real end users as quickly and often as possible."
+msgstr "確保能儘快且經常給真正的終端使用者進行測試。"
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Plan the work to integrate small parts very often instead of large parts "
+"less frequently."
+msgstr "以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。"
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"Procure consultancy services that deliver incrementally aligned with the "
+"plan."
+msgstr "聘請有能力處理漸進式交付，並跟得上規劃進度的顧問服務。"
+
+#: ./criteria/use-continuous-integration.md:block 16 (unordered list)
+msgid ""
+"After a large failure, encourage publication of incident reports and public "
+"discussion of what was learned."
+msgstr "發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers structure the work plan such that it can be integrated as "
+"small increments."
+msgstr "協助管理人員擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help contributors limit the scope of their contributions and feature "
+"requests to be as small as reasonable."
+msgstr "協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Help managers and policy makers test their contributions, for example by "
+"testing their contributions for broken links or style."
+msgstr "協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Structure source code written to handle conditions which are difficult to "
+"create in a test environment in such a way that the conditions can be "
+"simulated during testing. Forms of resource exhaustion such as running out "
+"of storage space and memory allocation failure are typical examples of "
+"difficult to create conditions."
+msgstr ""
+"編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出"
+"來。例如硬碟空間不足、記憶體分配失敗等資源耗盡情況，都是難以創造的典型案例。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid ""
+"Tune the test code coverage tools to avoid false alarms resulting from "
+"inlining or other optimizations."
+msgstr "調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Deploy often."
+msgstr "經常部署。"
+
+#: ./criteria/use-continuous-integration.md:block 18 (unordered list)
+msgid "Integrate your work at least once a day."
+msgstr "至少每天整合工作內容一次。"
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[What is continuous "
+"integration](https://www.martinfowler.com/articles/continuousIntegration.html)"
+" by Martin Fowler."
+msgstr ""
+"Martin "
+"Fowler《[什麼是持續整合](https://www.martinfowler.com/articles/continuousIntegration.html)》。"
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Use continuous delivery](https://gds-"
+"way.cloudapps.digital/standards/continuous-delivery.html) by the UK "
+"Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[使用持續交付](https://gds-way.cloudapps.digital/standards/continuous-"
+"delivery.html)》。"
+
+#: ./criteria/use-continuous-integration.md:block 20 (unordered list)
+msgid ""
+"[Quality assurance: testing your service "
+"regularly](https://www.gov.uk/service-manual/technology/quality-assurance-"
+"testing-your-service-regularly) by the UK Government Digital Service."
+msgstr ""
+"英國政府數位服務團《[品質保證：定期測試您的服務](https://www.gov.uk/service-"
+"manual/technology/quality-assurance-testing-your-service-regularly)》。"
+
+#: ./criteria/use-open-standards.md:block 3 (paragraph)
+msgid "order: 11 redirect_from:"
+msgstr "order: 11 redirect_from:"
+
+#: ./criteria/use-open-standards.md:block 4 (unordered list)
+msgid "criteria/open-standards"
+msgstr "criteria/open-standards"
+
+#: ./criteria/use-open-standards.md:block 5 (header)
+msgid "Use open standards"
+msgstr "採用開放標準"
+
+#: ./criteria/use-open-standards.md:block 6 (paragraph)
+msgid ""
+"[Open standards](../glossary.md#open-standard) guarantee access to the "
+"knowledge required to use and contribute to the "
+"[codebase](../glossary.md#codebase). They enable interoperability between "
+"systems and reduce the risk of vendor lock-in. Open standards which are "
+"unambiguous allow for independent development of either side of data "
+"exchange."
+msgstr ""
+"[開放標準](../glossary.md#open-"
+"standard)保證可以取得使用與貢獻[程式基底](../glossary.md#codebase)所需的知識"
+"。不僅能為不同的系統之間建立互通性，更能降低廠商套牢的可能性。開放標準如果明"
+"確，不同方就可以各自獨立開發作資料交換。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"For features of the codebase that facilitate the exchange of data the "
+"codebase MUST use an open standard that meets the [Open Source Initiative "
+"Open Standard Requirements](https://opensource.org/osr)."
+msgstr ""
+"程式基底如要促進資料交換的特性，就「必須」採用符合 [OSI "
+"開放原始碼促進會其《開放標準需求規範](https://opensource.org/"
+"osr)》的開放標準。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards used MUST be recorded clearly as such in the "
+"documentation."
+msgstr "如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any standard chosen for use within the codebase MUST be listed in the "
+"documentation with a link to where it is available."
+msgstr "程式基底選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該"
+"標準的連結。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Any non-open standards chosen for use within the codebase MUST NOT hinder "
+"collaboration and reuse."
+msgstr "程式基底選擇採用的任何非開放標準，皆「禁止」妨礙程式基底的協作與重複使用。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"If no existing open standard is available, effort SHOULD be put into "
+"developing one."
+msgstr "如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Open standards that are machine testable SHOULD be preferred over open "
+"standards that are not."
+msgstr "採用開放標準時，「應該」優先選擇可經機器測試的開放標準。"
+
+#: ./criteria/use-open-standards.md:block 8 (unordered list)
+msgid ""
+"Non-open standards that are machine testable SHOULD be preferred over non-"
+"open standards that are not."
+msgstr "採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。"
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid "Confirm that data exchange follows an OSI approved open standard."
+msgstr "確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。"
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that any non-open standards used are clearly documented as such."
+msgstr "確認若有採用任何的非開放標準，皆有清楚記錄在文件中。"
+
+#: ./criteria/use-open-standards.md:block 10 (unordered list)
+msgid ""
+"Confirm that documentation includes a list of the standards followed within "
+"the codebase, each with a working link, or a statement that no standards "
+"were chosen."
+msgstr "確認文件有清單列出程式基底所採用的標準，其中各標準有對應的有效連結；或沒有採"
+"用任何標準時，則留下聲明。"
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Mandate use of open standards everywhere possible."
+msgstr "以政策要求盡可能在任何情況下採用開放標準。"
+
+#: ./criteria/use-open-standards.md:block 12 (unordered list)
+msgid "Prohibit procurement of technology that does not use open standards."
+msgstr "禁止採購不採用開放標準的技術科技。"
+
+#: ./criteria/use-open-standards.md:block 14 (unordered list)
+msgid ""
+"Consider including open standard compliance assessment in [source "
+"code](../glossary.md#source-code) reviews."
+msgstr "考慮在[原始碼](../glossary.md#source-code)審查中納入開放標準依循評估。"
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Add [continuous integration](../glossary.md#continuous-integration) tests "
+"for compliance with the standards."
+msgstr "將是否依循標準加入[持續整合](../glossary.md#continuous-integration)測試中。"
+
+#: ./criteria/use-open-standards.md:block 16 (unordered list)
+msgid ""
+"Review the commits and other [repository](../glossary.md#repository) "
+"resources for references to standards and cross-check those with the "
+"standards listed."
+msgstr "審查送交版次與[儲存庫](../glossary."
+"md#repository)其他資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。"
+
+#: ./criteria/use-open-standards.md:block 18 (unordered list)
+msgid ""
+"[Open Standards principles](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-principles), "
+"[policy](../glossary.md#policy) paper of the UK Cabinet Office."
+msgstr ""
+"英國內閣辦公室發表的《[開放標準原則](https://www.gov.uk/government/publications/open-"
+"standards-principles/open-standards-"
+"principles)》[政策](../glossary.md#policy)報告。"
+
+#: ./criteria/use-plain-english.md:block 3 (paragraph)
+msgid "order: 10 redirect_from:"
+msgstr "order: 10 redirect_from:"
+
+#: ./criteria/use-plain-english.md:block 4 (unordered list)
+msgid "criteria/understandable-english-first"
+msgstr "criteria/understandable-english-first"
+
+#: ./criteria/use-plain-english.md:block 5 (header)
+msgid "Use plain English"
+msgstr "使用白話的英語"
+
+#: ./criteria/use-plain-english.md:block 6 (paragraph)
+msgid ""
+"English is the <i>de facto</i> language of collaboration in software "
+"development."
+msgstr "英語是軟體開發領域中的<i>實際</i> 協作語言。"
+
+#: ./criteria/use-plain-english.md:block 7 (paragraph)
+msgid ""
+"Public sector information needs to be accessible to all its constituents. "
+"Plain and simple language makes the [code](../glossary.md#code) and what it "
+"does easier to understand for a wider variety of people."
+msgstr "公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解[程式碼"
+"](../glossary.md#code)與其功用。"
+
+#: ./criteria/use-plain-english.md:block 8 (paragraph)
+msgid ""
+"Translations further increase the possible reach of a "
+"[codebase](../glossary.md#codebase). Language that is easy to understand "
+"lowers the cost of creating and maintaining translations."
+msgstr "翻譯可以讓更多人有機會認識[程式基底](../glossary."
+"md#codebase)。用語越是簡單明暸，製作與維護翻譯的成本就越低。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid "All codebase documentation MUST be in English."
+msgstr "程式基底的所有文件都「必須」使用英語。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All [source code](../glossary.md#source-code) MUST be in English, except "
+"where [policy](../glossary.md#policy) is machine interpreted as code."
+msgstr ""
+"所有[原始碼](../glossary.md#source-"
+"code)都「必須」使用英語編寫，其中[政策](../glossary."
+"md#policy)是由機器解讀當作程式碼的部分則除外。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"All bundled policy not available in English MUST have an accompanying "
+"summary in English."
+msgstr "任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Any translation MUST be up to date with the English version and vice versa."
+msgstr "任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain"
+" specific terms in the codebase without an explanation preceding it or a "
+"link to an explanation."
+msgstr ""
+"程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙"
+"；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結"
+"。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Documentation SHOULD aim for a lower secondary education reading level, as "
+"recommended by the [Web Content Accessibility Guidelines "
+"2](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable)."
+msgstr ""
+"根據《[網頁內容近用性無障礙指引 2](https://www.w3.org/WAI/WCAG21/quickref/"
+"?showtechniques=315#readable)》的建議，文件內容「應該」以國中識讀程度為主。"
+
+#: ./criteria/use-plain-english.md:block 10 (unordered list)
+msgid ""
+"Providing a translation of any code, documentation or tests is OPTIONAL."
+msgstr "「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm that codebase documentation is available in English."
+msgstr "確認程式基底文件有英語版本。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that source code is in English, or confirm any non-English is policy"
+" or terms with preceding explanations."
+msgstr "確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Confirm any non-English policy has an accompanying summary in English."
+msgstr "確認任何非英語政策都有隨附英語版摘要。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Confirm that translations and the English version have the same content."
+msgstr "確認翻譯版與英語版內容相同。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid ""
+"Check that no unexplained acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms are in the documentation."
+msgstr "確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。"
+
+#: ./criteria/use-plain-english.md:block 12 (unordered list)
+msgid "Check the spelling, grammar and readability of the documentation."
+msgstr "檢查文件的拼字、文法與易讀性等。"
+
+#: ./criteria/use-plain-english.md:block 14 (unordered list)
+msgid ""
+"Frequently test with other managers, developers and designers in the process"
+" if they understand what you are delivering and how you document it."
+msgstr "在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。"
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Try to limit the use of acronyms, abbreviations, puns or legal/non-"
+"English/domain specific terms in internal communications in and between "
+"teams and stakeholders. Add any such terms to a glossary and link to it from"
+" the places they are being used."
+msgstr ""
+"在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在使用這些詞彙的地方加上詞彙表連結。"
+
+#: ./criteria/use-plain-english.md:block 16 (unordered list)
+msgid ""
+"Be critical of documentation and descriptions in proposals and changes. If "
+"you don't understand something, others will probably also struggle with it."
+msgstr "以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。"
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Frequently test with policy makers and managers if they understand what you "
+"are delivering and how you document it."
+msgstr "經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。"
+
+#: ./criteria/use-plain-english.md:block 18 (unordered list)
+msgid ""
+"Ask someone outside of your context if they understand the content (for "
+"example, a developer working on a different codebase)."
+msgstr "詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。"
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"Meeting the [Web Content Accessibility Guidelines 2.1, Guideline 3.1 "
+"Readable](https://www.w3.org/TR/WCAG21/#readable) by W3C makes text content "
+"readable and understandable."
+msgstr ""
+"符合 W3C 全球資訊網協會《[網頁內容近用性無障礙指引 2.1、3.1 "
+"之可讀性](https://www.w3.org/TR/WCAG21/"
+"#readable)》要求，撰寫的文字內容要容易閱讀與理解。"
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"The[European Union accessibility directive](https://ec.europa.eu/digital-"
+"single-market/en/web-accessibility) by the European Commission, is an "
+"example of regulation requiring high accessibility."
+msgstr ""
+"歐盟委員會的《[歐盟無障礙環境命令](https://ec.europa.eu/"
+"digital-single-market/en/web-"
+"accessibility)》，是高度要求無障礙環境的法規範例。"
+
+#: ./criteria/use-plain-english.md:block 20 (unordered list)
+msgid ""
+"[Definition of plain "
+"language](https://www.plainlanguage.gov/about/definitions/) by United States"
+" General Services Administration."
+msgstr "美國總務署《[白話語言定義](https://www.plainlanguage.gov/about/definitions/)》。"
+
+#: ./criteria/welcome-contributors.md:block 3 (paragraph)
+msgid "order: 4 redirect_from:"
+msgstr "order: 4 redirect_from:"
+
+#: ./criteria/welcome-contributors.md:block 4 (unordered list)
+msgid "criteria/open-to-contributions"
+msgstr "criteria/open-to-contributions"
+
+#: ./criteria/welcome-contributors.md:block 5 (header)
+msgid "Welcome contributors"
+msgstr "歡迎貢獻者"
+
+#: ./criteria/welcome-contributors.md:block 6 (paragraph)
+msgid ""
+"The atmosphere in a [codebase](../glossary.md#codebase) community helps "
+"users decide to use one codebase over another. Welcoming anyone as a "
+"contributor enables the community to grow and sustain itself over time. A "
+"community where contributors have clear ways to influence codebase and "
+"community goals and progress is less likely to split and end up in diverging"
+" communities. Newcomers need to understand and trust the codebase "
+"community’s governance."
+msgstr ""
+"[程式基底](../glossary.md#codebase)社群的氛圍，會影響使用者選擇所要使用的程式"
+"基底。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我運作。若貢獻者有"
+"明確的方法可以影響程式基底、社群目標與進展，則該社群分裂成分歧的社群的機率也"
+"較低。新參與者需要瞭解並信任程式基底社群的治理方式。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST allow anyone to submit suggestions for changes to the "
+"codebase."
+msgstr "程式基底必須「允許」任何人對程式基底提出修改建議。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST include contribution guidelines explaining what kinds of "
+"contributions are welcome and how contributors can get involved, for example"
+" in a `CONTRIBUTING` file."
+msgstr "程式基底「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開"
+"發，例如以「`CONTRIBUTING`」檔案說明。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase MUST document the governance of the codebase, contributions and"
+" its community, for example in a `GOVERNANCE` file."
+msgstr "程式基底「必須」以文件記錄程式基底、貢獻內容與社群互動等的治理方式，例如以「`"
+"GOVERNANCE`」檔案來說明。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The contribution guidelines SHOULD document who is expected to cover the "
+"costs of reviewing contributions."
+msgstr "貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"The codebase SHOULD advertise the committed engagement of involved "
+"organizations in the development and maintenance."
+msgstr "程式基底「應該」宣布投入其開發與維護工作的參與組織單位。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD have a publicly available roadmap."
+msgstr "程式基底「應該」要有可公開取得的發展路線圖。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid "The codebase SHOULD publish codebase activity statistics."
+msgstr "程式基底「應該」公布程式基底的活動統計數據。"
+
+#: ./criteria/welcome-contributors.md:block 8 (unordered list)
+msgid ""
+"Including a code of conduct for contributors in the codebase is OPTIONAL."
+msgstr "「可選擇」是否為程式基底加入貢獻者的行為守則。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that it is possible to submit suggestions for changes to the "
+"codebase."
+msgstr "確認可以提交修改建議給程式基底。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Confirm there are contribution guidelines."
+msgstr "確認程式基底有貢獻指引。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Confirm that the codebase governance is clearly explained, including how to "
+"influence codebase governance."
+msgstr "確認程式基底有清楚解釋治理架構，並包含如何影響程式基底治理的方法。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid ""
+"Check that contributing guidelines cover who is expected to cover the costs "
+"of reviewing contributions."
+msgstr "確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a list of involved organizations."
+msgstr "檢查是否有參與的組織單位名單。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a roadmap."
+msgstr "檢查是否有發展路線圖。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for published activity statistics."
+msgstr "檢查是否有公布活動統計數據。"
+
+#: ./criteria/welcome-contributors.md:block 10 (unordered list)
+msgid "Check for a code of conduct."
+msgstr "檢查是否有行為守則。"
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Add a list to the codebase of any other resources that "
+"[policy](../glossary.md#policy) experts, non-governmental organizations and "
+"academics would find useful for understanding or reusing your policy."
+msgstr ""
+"為程式基底加入其他資源的清單，而這些資源可幫助[政策](../glossary."
+"md#policy)專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。"
+
+#: ./criteria/welcome-contributors.md:block 12 (unordered list)
+msgid ""
+"Consider adding contact details so that other policy makers considering "
+"collaboration can ask you for advice."
+msgstr "考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。"
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure that the documentation of the governance includes the current "
+"process for how to make changes to the governance."
+msgstr "確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。"
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If the community has some consensus about how the governance should change, "
+"then include those ideas stated as ambitions in the documentation."
+msgstr "如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。"
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"If needed, make sure you have allocated budget for the contributions review "
+"process as agreed by the codebase community."
+msgstr "若有需要，確認您有編列貢獻內容審查流程的預算，且經過程式基底社群同意。"
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Make sure the documentation explains how each organization is involved in "
+"the codebase, what resources it has available for it and for how long."
+msgstr "確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參"
+"與的時間長度等。"
+
+#: ./criteria/welcome-contributors.md:block 14 (unordered list)
+msgid ""
+"Support your experienced policy makers, developers and designers to stay "
+"part of the community for as long as possible."
+msgstr "支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。"
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid "Respond promptly to requests."
+msgstr "快速回應請求。"
+
+#: ./criteria/welcome-contributors.md:block 16 (unordered list)
+msgid ""
+"Communicate clearly to contributors what they need to do make sure their "
+"contribution can be integrated."
+msgstr "清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到程式基底中。"
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building welcoming communities](https://opensource.guide/building-"
+"community/) by Open Source Guides."
+msgstr "開放原始碼指引所提供的《[營造友善的社群](https://opensource.guide/"
+"building-community/)》。"
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[The Open Source Contributor Funnel](https://mikemcquaid.com/2018/08/14/the-"
+"open-source-contributor-funnel-why-people-dont-contribute-to-your-open-"
+"source-project/) by Mike McQuaid."
+msgstr ""
+"Mike McQuaid《[開放原始碼貢獻者瓶頸](https://mikemcquaid.com/2018/08/14/the-open-"
+"source-contributor-funnel-why-people-dont-contribute-to-your-open-source-"
+"project/)》。"
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Leadership and governance](https://opensource.guide/leadership-and-"
+"governance/) for growing [open source](../glossary.md#open-source) community"
+" projects, by Open Source Guides."
+msgstr ""
+"開放原始碼指引針對推動[開放原始碼](../glossary.md#open-"
+"source)社群專案所寫的《[領導與治理](https://opensource.guide/"
+"leadership-and-governance/)》。"
+
+#: ./criteria/welcome-contributors.md:block 18 (unordered list)
+msgid ""
+"[Building online communities](http://hintjens.com/blog:117) by Pieter "
+"Hintjens (long read!)."
+msgstr "Pieter Hintjens《[打造網路社群](http://hintjens.com/blog:117)》(長篇文章！)。"
+
+#: ./docs/printing.md:block 1 (header)
+msgid "Printing"
+msgstr "印刷"
+
+#: ./docs/printing.md:block 3 (paragraph)
+msgid ""
+"The printed Standard for Public Code is printed by Reclameland. This guide "
+"tries to provide the relevant information to print it there or somewhere "
+"else."
+msgstr "《公共程式標準》是由 Reclameland 負責印刷。本指引試著提供印刷相關資訊，"
+"方便您到 Reclameland 或其他地方印刷。"
+
+#: ./docs/printing.md:block 4 (paragraph)
+msgid ""
+"Details, mostly in order they are on the Reclameland page with the Dutch if "
+"necessary:"
+msgstr "印刷詳細資訊（多數依照 Reclameland 網頁上的順序，依需要附上荷蘭語）："
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Form: Softcover book ([Reclameland product "
+"page](https://www.reclameland.nl/drukken/softcover-boeken))"
+msgstr ""
+"樣式：平裝書 ([Reclameland 產品頁面](https://www.reclameland.nl/drukken/"
+"softcover-boeken))"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Format: A4"
+msgstr "紙張尺寸：A4"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Portrait or landscape: Portrait (Staand)"
+msgstr "直向或橫向：直向 (Staand)"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing inside: 4/4 dual sided full color"
+msgstr "內頁印刷：正四反四 4/4，雙面全色印刷"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Inside material: 90 grams biotop"
+msgstr "內頁材質：Biotop 90克"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover: 350 grams cover"
+msgstr "封面：350 克封面"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Printing cover: 4/0 one sided full cover"
+msgstr "封面印刷：正四反空 4/0，單面滿版印刷"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Cover treatment: one sided matt foliated (Enke)"
+msgstr "封面處理：單面霧面層剝處理 (Enke)"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid ""
+"Pages: pages of the inside + 4 + x, where x is 0-3 so that the sum becomes a"
+" multiple of 4"
+msgstr "頁數：書內頁數 + 4 + x，x 是 0-3頁，讓總頁數是 4 的倍數"
+
+#: ./docs/printing.md:block 5 (unordered list)
+msgid "Individually sealed: no"
+msgstr "個別封裝：無"
+
+#: ./docs/printing.md:block 6 (paragraph)
+msgid ""
+"When these details are chosen, the cover and insides are uploaded and the "
+"order is placed payment can happen (payment ahead) after which printing "
+"starts."
+msgstr "一旦選定這些印刷的詳細資訊，封面與內頁就會上傳，並且下單與付費。付費後才會開始印刷。"
+
+#: ./docs/releasing.md:block 1 (header)
+msgid "Releasing a new version of the Standard for public code"
+msgstr "發行新版本的《公共程式標準》"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Review state of the 'develop' branch"
+msgstr "審查「develop」分支的狀態"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure all changes intended for release are merged"
+msgstr "確認預計收入該次發行版的所有變更都已完成合併"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Invite a proofread of the current state of the branch"
+msgstr "邀請校對該分支目前的狀態"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If new dashes are introduced, check if the language can be simplified to "
+"remove them in favor of more simple sentences. If a complex sentence is "
+"needed, see if the dash can be replaced with other punctuation. If a dash is"
+" truly the best expression of ideas, then follow the [Chicago Manual of "
+"Style](https://en.wikipedia.org/wiki/Dash#En_dash_versus_em_dash)."
+msgstr ""
+"如果有引入新的破折號，檢查是否能簡化文字並且移除破折號，例如改用較簡易的句子"
+"。如果需要用到複雜的句子，檢查是否能用其他標點符號來取代破折號。如果破折號最"
+"適合用來表達該句子的涵義，則請遵守《[芝加哥格式手冊](https://en.wikipedia."
+"org/wiki/Dash#En_dash_versus_em_dash)》的規範。"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create a release branch"
+msgstr "建立發行用分支"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "From 'develop', `git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+msgstr "從「develop」分支下命令，`git switch -c \"release-$MAJOR.$MINOR.$PATCH\"`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push the branch, `git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+msgstr "推送分支，`git push -u origin release-$MAJOR.$MINOR.$PATCH`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update the new release"
+msgstr "更新本次新發行"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Update version number in `_config.yml`, `README.md` and `publiccode.yml`"
+msgstr "更新 `_config.yml`、`README.md` 與 `publiccode.yml` 中的版本編號"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update `assets/version-badge.svg` with `script/make-version-badge.sh`"
+msgstr "使用 `script/make-version-badge.sh` 更新 `assets/version-badge.svg`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update releaseDate in `publiccode.yml`"
+msgstr "更新 `publiccode.yml` 當中的 releaseDate 日期"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`AUTHORS.md`](../AUTHORS.md) with new contributors"
+msgstr "在 [`AUTHORS.md`](../AUTHORS.md) 中加入新貢獻者的資料"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update [`CHANGELOG.md`](../CHANGELOG.md)"
+msgstr "更新 [`CHANGELOG.md`](../CHANGELOG.md)"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Perform extra pass on diff to the 'main' branch"
+msgstr "透過 diff 進行額外傳輸到「main」分支"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"run `script/generate-review-template.sh` and commit updated `docs/review-"
+"template.html`"
+msgstr ""
+"執行 `script/generate-review-template.sh` 並送交更新後的 `docs/review-"
+"template.html` 版次記錄"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"update `docs/standard-for-public-code.md` with the new text from the review "
+"template, updating any status changes as a result"
+msgstr "用審查範本中的新文字來更新 `docs/standard-for-public-code."
+"md`，根據成果更新所有的狀態變更"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reread any section or paragraph to ensure wording changes still fit the "
+"whole and do not contain grammar or spelling errors"
+msgstr "重新檢查用字有變更的任何小節或段落，確保變更的字詞適合該整體內容，並且沒有文"
+"法或拼字錯誤"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ensure [fonts](https://brand.publiccode.net/typography/) are installed, see:"
+" `script/ensure-font.sh`"
+msgstr ""
+"確認有安裝[字型](https://brand.publiccode.net/typography/)，請參見：`script/"
+"ensure-font.sh`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Check the rendered `.pdf` using `script/pdf.sh rc1`"
+msgstr "使用 `script/pdf.sh rc1` 檢查轉譯出的 `.pdf` 檔"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Ensure no link collisions exist"
+msgstr "確認沒有連結相衝的問題"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Check the page breaks, possibly removing or adding page-break CSS, for "
+"example: `<p style=\"page-break-after: always;\"></p>`"
+msgstr ""
+"檢查文字分頁之處，可能需要移除或新增 CSS 分頁語法，像是：`<p style=\"page-"
+"break-after: always;\"></p>`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "If needed, commit fixes and repeat extra pass"
+msgstr "如果有需要，送交修正版次，並重複進行額外傳輸"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Push branch, open a pull request to the 'main' branch"
+msgstr "推送分支，對 「main」分支提出拉取請求"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Request review from multiple reviewers, especially a proofreader"
+msgstr "請多位審查人員（特別是校對人員）進行審查"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Reviewers will create issues for shortcomings found which would not prevent "
+"release"
+msgstr "審查人員若發現不會阻礙發行的缺失，則會建立議題"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"If needed for release, reviewers may create pull requests to resolve issues"
+msgstr "如果是發行所需處理的缺失，審查人員可以提交拉取請求來解決問題"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Re-request reviews if additional pull requests are merged into release "
+"branch"
+msgstr "若有額外的拉取請求合併至發行分支，則再次請求審查"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Run the to-archive-org.sh script"
+msgstr "執行 to-archive-org.sh 命令稿"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Once reviews are complete, merge to 'main'"
+msgstr "當審查完成後，合併回「main」"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Create GitHub release with the release notes and version number"
+msgstr "在 GItHub 上發行，附上發行備註與版本編號"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Switch to the 'main' branch, `git pull` and `git status`"
+msgstr "切換至「main」分支，`git pull` 然後 `git status`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git tag $MAJOR.$MINOR.$PATCH`"
+msgstr "`git tag $MAJOR.$MINOR.$PATCH`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push --tags` (see: `../.github/workflows/release-on-tag.yml`)"
+msgstr "`git push --tags`（請參見：`../.github/workflows/release-on-tag.yml`）"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Trigger a rebuild of gh-pages"
+msgstr "觸發 gh-pages 重建"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr "`git switch -c rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
+msgstr "`git commit --allow-empty -m\"Rebuild GH Pages $MAJOR.$MINOR.$PATCH\"`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+msgstr "`git push -u origin rebuild-gh-pages-$MAJOR.$MINOR.$PATCH`"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Open a pull request from this branch to `main`"
+msgstr "從此分支向「main」提出拉取請求"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Approve and merge PR (containing empty commit)"
+msgstr "批准與合併 PR （包含空白的送交版次）"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Update 'develop' with a merge from 'main'"
+msgstr "將「develop」透過合併更新「main」"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "[Send the files for print to the printer](printing.md)"
+msgstr "[將檔案傳送給印刷廠商印刷](printing.md)"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Cover file"
+msgstr "封面檔案"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid "Inside pages PDF"
+msgstr "內頁 PDF"
+
+#: ./docs/releasing.md:block 3 (ordered list)
+msgid ""
+"Ping [translation](https://github.com/publiccodenet/community-translations-"
+"standard) contributors"
+msgstr ""
+"通知[翻譯](https://github.com/publiccodenet/community-translations-"
+"standard)貢獻者"
+
+#: ./docs/roadmap.md:block 1 (header)
+msgid "Roadmap"
+msgstr "發展路線圖"
+
+#: ./docs/roadmap.md:block 3 (paragraph)
+msgid "Last updated: 2023-03-08"
+msgstr "上次更新時間：2023-03-08"
+
+#: ./docs/roadmap.md:block 4 (paragraph)
+msgid ""
+"This document intends to shed light on the current development plans of the "
+"team. Plans change constantly as new information is absorbed by the team."
+msgstr "本文件旨在闡明團隊目前的開發計畫。隨著團隊吸收新資訊，這些計畫也會持續變動。"
+
+#: ./docs/roadmap.md:block 5 (paragraph)
+msgid ""
+"Codebase stewards review the roadmap monthly as part of our [backlog pruning"
+" session](https://about.publiccode.net/activities/standard-"
+"maintenance/backlog-pruning.html)."
+msgstr ""
+"程式基底執事人員每月會定期審查發展路線圖，這是我們[積累事項修整作業](https://"
+"about.publiccode.net/activities/standard-maintenance/backlog-pruning."
+"html)環節的一部份。"
+
+#: ./docs/roadmap.md:block 6 (header)
+msgid "Current work"
+msgstr "目前任務"
+
+#: ./docs/roadmap.md:block 7 (unordered list)
+msgid "As far as possible, make the standard Standard-compliant"
+msgstr "盡可能讓標準遵循自我標準"
+
+#: ./docs/roadmap.md:block 8 (header)
+msgid "Near term"
+msgstr "近期"
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Separate executive summary"
+msgstr "分離執行摘要"
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid ""
+"Clarify \"code\" as \"source code\" or \"policy code\" when specific to one,"
+" issue #208"
+msgstr "#208號議題：將程式碼或規則之「code」清楚區分為「原始碼」或是「政策法規」"
+
+#: ./docs/roadmap.md:block 9 (unordered list)
+msgid "Possibly: add in the illustrations for each criterion"
+msgstr "可能性：為每個準則新增解說插圖"
+
+#: ./docs/roadmap.md:block 10 (header)
+msgid "Longer term"
+msgstr "長期"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Certification badges"
+msgstr "認證標章"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid ""
+"Add to README and index.md information (and eventually statistics) on "
+"adoption and use (issue #438)"
+msgstr "為「README」與「index.md」加入採用與使用（之後會繼續統計）條目（議題#438號）"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Physical paper checklist"
+msgstr "實體紙張檢查清單"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Becoming validated by multiple codebases"
+msgstr "通過多個程式基底驗證"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Release version 1.0.0 after a few codebases are compliant"
+msgstr "在幾個程式基底遵循標準後，發行 1.0.0 版"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Linkable requirements"
+msgstr "可連結的需求規範"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "New cover art"
+msgstr "新封面設計"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "Register for ISBN"
+msgstr "註冊申請 ISBN 書號"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "List with an on-demand book printing service"
+msgstr "隨選書籍列印服務名單"
+
+#: ./docs/roadmap.md:block 11 (unordered list)
+msgid "QR codes for external links in print version"
+msgstr "印刷版外部連結的 QR 二維圖碼"
+
+#: ./foreword.md:block 3 (paragraph)
+msgid "redirect_from:"
+msgstr "redirect_from:"
+
+#: ./foreword.md:block 4 (unordered list)
+msgid "introduction"
+msgstr "前言"
+
+#: ./foreword.md:block 5 (header)
+msgid "Foreword"
+msgstr "序文"
+
+#: ./foreword.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that support public "
+"organizations in developing and maintaining software and policy together."
+msgstr "《公共程式標準》提供一套準則規範，支持公家機關一同開發與維護軟體及政策。"
+
+#: ./foreword.md:block 7 (paragraph)
+msgid ""
+"Anyone developing public-purpose software or policy can use this standard to"
+" work towards higher quality public services that are more cost effective, "
+"with less risk and more control."
+msgstr "任何想開發具有公眾用途的軟體或政策的人，可以利用本標準來提升公共服務品質，使"
+"其更具成本效益、風險更低，還能對系統更有掌控權。"
+
+#: ./foreword.md:block 8 (paragraph)
+msgid ""
+"This foreword introduces the term public code and explains why this is "
+"important."
+msgstr "本序文在介紹何謂「公共程式」以及解說其重要性。"
+
+#: ./foreword.md:block 9 (header)
+msgid "Definition of public code"
+msgstr "公共程式定義"
+
+#: ./foreword.md:block 10 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines. It "
+"encompasses the software built to operate with and as public infrastructure,"
+" along with the arrangements for its production. Public code is explicitly "
+"distinct from regular software because it operates under fundamentally "
+"different circumstances and expectations."
+msgstr ""
+"公共程式，英文為 Public Code，是指人類或機器在公共情境下，所執行的電腦原始碼"
+"（像是軟體與演算法）與公共政策。公共程式的範疇，涵蓋搭配公共基礎建設一同作業"
+"的軟體、作為公共基礎建設運作而建置的軟體，以及產生公共程式的過程安排等。公共"
+"程式與一般軟體有明顯區別，因為其作業的環境與期待全然不同。"
+
+#: ./foreword.md:block 11 (header)
+msgid "Reasons for public code"
+msgstr "採用公共程式的原因"
+
+#: ./foreword.md:block 12 (paragraph)
+msgid "There are many reasons for why public code is relevant now."
+msgstr "公共程式現在如此重要，背後有幾個原因。"
+
+#: ./foreword.md:block 13 (header)
+msgid "Software code == legal code"
+msgstr "軟體程式碼 == 法律條文"
+
+#: ./foreword.md:block 14 (paragraph)
+msgid "Software is public infrastructure."
+msgstr "軟體是公共基礎建設。"
+
+#: ./foreword.md:block 15 (paragraph)
+msgid ""
+"In the 21st century, software can be considered vital public infrastructure."
+" It is increasingly not just the expression of existing policy but the "
+"originator of new policy, for example where algorithms decide which "
+"districts need extra social services or policing."
+msgstr ""
+"在 21 世紀，軟體可被視為重要的公共基礎建設。軟體越來越常被用於實現既有政策，"
+"甚至成為新政策的制定來源。舉例來說，演算法可以決定哪些地區需要額外的社會服務"
+"或警力等。"
+
+#: ./foreword.md:block 16 (paragraph)
+msgid ""
+"Software mechanics, algorithms and data collection have become key elements "
+"in the execution of public policies. Computer code now executes policies "
+"that have been codified in legal code through democratic procedures. Both "
+"forms of code set conditions for society to function according to "
+"democratically set public values, the latter executed by humans, the former "
+"by machines. In other words, software code has increasingly started to equal"
+" legal code."
+msgstr ""
+"在公共政策的執行上，軟體運作機制、演算法與資料蒐集等，已成為關鍵要素。今日的"
+"電腦程式碼，正執行著透過民主程序制定的法規政策。程式碼與政策這兩種形式的程式"
+"，都根據民主程序而確立的公共價值，設立出社會的運作環境；前者由機器執行，後者"
+"則是由人類執行。換句話說，軟體程式碼，已經越來越實質趨近於法律條文的地位。"
+
+#: ./foreword.md:block 17 (paragraph)
+msgid ""
+"Software should therefore be subject to the principles of democratic "
+"governance."
+msgstr "因此軟體也應該接受民主治理原則的約束。"
+
+#: ./foreword.md:block 18 (header)
+msgid "Traditional public software procurement"
+msgstr "傳統的公共軟體採購"
+
+#: ./foreword.md:block 19 (paragraph)
+msgid ""
+"Current public software production methods have not served public service "
+"delivery very well."
+msgstr "目前公共軟體的生產模式，在交付公共服務上的效率並不高。"
+
+#: ./foreword.md:block 20 (paragraph)
+msgid ""
+"In the last decade, public organizations that purchased complete software "
+"solutions have sometimes been surprised to discover that they:"
+msgstr "過去近十年來，購置完整軟體解決方案的公家機關，有時甚至會很訝異地發現："
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"can’t change their software to reflect changing policy or take advantage of "
+"new technology"
+msgstr "他們無法修改軟體來反映政策的變動，或是改變軟體來利用新科技"
+
+#: ./foreword.md:block 21 (unordered list)
+msgid ""
+"don’t have access to their data as it's locked into proprietary systems"
+msgstr "他們的資料都套牢在專有系統中，無法取用"
+
+#: ./foreword.md:block 21 (unordered list)
+msgid "are asked to pay ever increasing license fees"
+msgstr "他們所需繳交的授權費變得越來越貴"
+
+#: ./foreword.md:block 22 (header)
+msgid "Technological sovereignty and democratic accountability"
+msgstr "技術自主權與民主課責"
+
+#: ./foreword.md:block 23 (paragraph)
+msgid "Public institutions, civil servants and residents deserve better."
+msgstr "公家機關、公務員與居民都值得更好的。"
+
+#: ./foreword.md:block 24 (paragraph)
+msgid ""
+"We believe the software that runs our society can no longer be a black box, "
+"controlled by outside companies that keep the underlying logic on which "
+"their software operates hidden in proprietary codebases. Instead, "
+"governments and the people they serve need technological sovereignty. This "
+"allows them to set and control the functioning of public software, just like"
+" they are able to set and control policy that is legally formulated in laws."
+" Citizens and civil society actors need this software to be transparent and "
+"accountable."
+msgstr ""
+"我們相信支持社會運作的軟體，再也不能是黑箱，任由外部公司依隱藏在專有程式基底"
+"之下的秘密邏輯作控制。反過來說，政府，以及政府所要服務的人民，需要掌控技術自"
+"主權。技術自主讓他們能主導設定與控制公共軟體的運作，正如同他們能依法制定與調"
+"整政策一樣。人民與公民社會的參與者，都需要這類軟體能夠透明，且可以課責。"
+
+#: ./foreword.md:block 25 (paragraph)
+msgid ""
+"The design of software as essential civic infrastructure should honor "
+"digital citizens’ rights."
+msgstr "作為必要公民基礎建設的軟體，其設計應該尊重公民的數位權利。"
+
+#: ./foreword.md:block 26 (header)
+msgid "Designing truly public software"
+msgstr "設計真正的公共軟體"
+
+#: ./foreword.md:block 27 (paragraph)
+msgid ""
+"Public code is at the core of modern public institutions, shapes the work of"
+" civil servants and affects the lives of almost all residents."
+msgstr "公共程式是現代公家機構的核心，型塑了公務員的工作樣態，並且影響了幾乎所有居民"
+"的生活。"
+
+#: ./foreword.md:block 28 (paragraph)
+msgid "Public software must therefore be:"
+msgstr "因此公共軟體必須："
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "transparent"
+msgstr "透明"
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "accountable"
+msgstr "可課責"
+
+#: ./foreword.md:block 29 (unordered list)
+msgid "understandable for its constituents"
+msgstr "讓選民能夠理解"
+
+#: ./foreword.md:block 30 (paragraph)
+msgid ""
+"It must reflect the values of the society it serves, for example by being "
+"inclusive and non-discriminatory."
+msgstr "必須能反映其所服務的社會價值觀，像是涵容與不歧視。"
+
+#: ./foreword.md:block 31 (paragraph)
+msgid ""
+"Most proprietary software systems currently used by public organizations do "
+"not meet these requirements. Public code does."
+msgstr "目前公家機關使用的大多數專有軟體系統，都不符合這些要求；而公共程式能夠做到。"
+
+#: ./foreword.md:block 32 (header)
+msgid "Values of public code"
+msgstr "公共程式的價值"
+
+#: ./foreword.md:block 33 (paragraph)
+msgid "We consider public code to have these core values:"
+msgstr "我們認為公共程式應具有下列核心價值："
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Inclusive"
+msgstr "涵容"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Usable"
+msgstr "好用"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Open"
+msgstr "開放"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Legible"
+msgstr "易懂"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accountable"
+msgstr "課責"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Accessible"
+msgstr "近用"
+
+#: ./foreword.md:block 34 (unordered list)
+msgid "Sustainable"
+msgstr "永續"
+
+#: ./foreword.md:block 35 (header)
+msgid "How public code works"
+msgstr "公共程式運作方式"
+
+#: ./foreword.md:block 36 (paragraph)
+msgid ""
+"Public code is open source software meant for fulfilling the essential role "
+"of public organizations. Through use, other administrations contribute back "
+"to the software, so that its development and maintenance become truly "
+"collaborative."
+msgstr ""
+"公共程式是旨在協助公家機關，履行其必要職責時所採用的開放原始碼軟體。透過使用"
+"，其他行政單位也能為軟體做出貢獻，因此公共程式的開發與維護，可說是真正互相協"
+"作的成果。"
+
+#: ./foreword.md:block 37 (paragraph)
+msgid "Being open unlocks many other things."
+msgstr "開放的精神能開創許多可能性。"
+
+#: ./foreword.md:block 38 (paragraph)
+msgid ""
+"Local responsibility and democratic accountability are ensured when a public"
+" organization implements and maintains their own public code. By being open "
+"and with a broader contributor base, the software is more secure as it "
+"benefits from many eyes spotting potential flaws. Many contributors share "
+"the maintenance work to keep it functional and modern, which reduces future "
+"technical debt. The shared workload is more sustainable now and in the "
+"future. Its openness makes both the code and its data more easily adaptable "
+"in the future. The code will be easier to retool, repurpose or retire. This "
+"all results in lower risk public infrastructure."
+msgstr ""
+"公家機關在執行與維護其自身的公共程式時，就是在確保能為地方負責，並履行民主課"
+"責。開放且貢獻者眾多的軟體，得利於有許多人在看，更容易發現潛在缺陷，因此安全"
+"性會更高。許多貢獻者會分攤維護工作，讓公共程式能持續運作與更新，減少未來技術"
+"債的可能。因為能有多人分攤維護工作，使得現在與未來都會更加永續。而公共程式的"
+"開放性，代表其程式碼與資料，在未來也更容易改寫與調整。程式碼也更容易重新利用"
+"、重新調整目標，或甚至淘汰。這一切特性都讓公共基礎建設可能遭遇的風險降到更低"
+"。"
+
+#: ./foreword.md:block 39 (paragraph)
+msgid ""
+"This pooling of resources lets public administrations give extra attention "
+"to how to customize the software so it works best in each local context, "
+"creating better user experiences for their end users (residents or "
+"citizens)."
+msgstr ""
+"這種將資源集中的作法，能讓公共行政單位可以有額外心力關注如何客製化軟體，來使"
+"軟體最適合當地情境的需求，為終端使用者（居民或市民）創造更佳的使用體驗。"
+
+#: ./foreword.md:block 40 (header)
+msgid "Economics of public code"
+msgstr "公共程式的經濟效應"
+
+#: ./foreword.md:block 41 (paragraph)
+msgid ""
+"Public code offers a better economic model for public organizations as well "
+"as for commercial companies. It's an alternative to traditional software "
+"procurement which increases local control and economic opportunity."
+msgstr "公共程式為公家機關以及商業公司，提供更好的經濟模型。公共程式作為替代傳統軟體"
+"採購的方案，更能提升當地的掌控權並促進經濟機會。"
+
+#: ./foreword.md:block 42 (paragraph)
+msgid ""
+"Designed from the start to be open, adaptable and with data portability, it "
+"can be developed by in-house staff or trusted vendors. Because the code is "
+"open, the public administration can change vendors if they need to. Open "
+"code increases opportunities for public learning and scrutiny, allowing the "
+"public administration to procure smaller contracts. Smaller procurements are"
+" easier for local small and medium enterprises to bid upon. Public "
+"administrations can use their own software purchasing to stimulate "
+"innovation and competition in their local economy."
+msgstr ""
+"公共程式從設計之初，就是要開放、適應力強、資料可攜，能夠由內部員工或信任的供"
+"應商來開發。由於原始碼開放，公共行政單位在有需要時可以更換供應商。開放原始碼"
+"讓社會大眾更有機會瞭解與監督公共程式，使公共行政單位得以採購小規模的合約，而"
+"地方性的中小企業就更容易參與這些小型採購案的競標。如此一來，公共行政單位就可"
+"以透過他們所需的軟體採購案，刺激當地經濟的創新與競爭。"
+
+#: ./foreword.md:block 43 (paragraph)
+msgid ""
+"This can be seen as investment leading to future economic growth. More "
+"vendors will be necessary due to growing technology demand."
+msgstr "這可視為對未來經濟成長的投資。隨著科技需求成長，也將需要更多供應商。"
+
+#: ./foreword.md:block 44 (header)
+msgid "Procuring public code"
+msgstr "購置公共程式"
+
+#: ./foreword.md:block 45 (paragraph)
+msgid ""
+"Public code can be used and developed by permanent in-house development "
+"teams, contractors or outsourced suppliers. Vendors to public organizations "
+"can include public code in their bids for contracts."
+msgstr "公共程式可由常駐的內部研發團隊、承包商或外包供應商開發。公家機關的供應商，在"
+"投標時可以在標案中納入公共程式。"
+
+#: ./foreword.md:block 46 (paragraph)
+msgid ""
+"To use existing public code, you need to specify in your budget and project "
+"design that your new solution will use that codebase. To encourage an "
+"innovative approach to adapting the public code to your context, you could "
+"describe the service or outcome in your contract."
+msgstr ""
+"若要使用既有的公共程式，您將需要在預算以及專案設計中，明確指出新的解決方案將"
+"會使用該程式基底。為了鼓勵創新，將公共程式依據您的情境背景作調整，您可在合約"
+"中描述說明服務內容或預期成果。"
+
+#: ./foreword.md:block 47 (header)
+msgid "The goals for the Standard for Public Code"
+msgstr "《公共程式標準》目標"
+
+#: ./foreword.md:block 48 (paragraph)
+msgid ""
+"This Standard supports developers, designers, managers and public policy "
+"makers to:"
+msgstr "本標準在於支持開發人員、設計師、管理人員、公共政策制定者："
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop high quality software and policy for better public service delivery"
+msgstr "開發出高品質的軟體與政策，來改善公共服務的交付"
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"develop codebases that can be reused across contexts and collaboratively "
+"maintained"
+msgstr "開發出能在各種情境下重複使用，且以協作方式維護的程式基底"
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "reduce technical debt and project failure rate"
+msgstr "減少技術債與專案失敗率"
+
+#: ./foreword.md:block 49 (unordered list)
+msgid ""
+"have more granular control over, and ability to make decisions about, their "
+"IT systems"
+msgstr "更能精細控制其 IT 系統粒度，並做出系統相關決策"
+
+#: ./foreword.md:block 49 (unordered list)
+msgid "improve vendor relationships with a better economic model"
+msgstr "以更好的經濟模型改善供應商關係"
+
+#: ./foreword.md:block 50 (paragraph)
+msgid ""
+"Potential users of codebases tested against the Standard for Public Code can"
+" expect them to be highly reusable, easily maintainable and of high quality."
+msgstr "如果有潛在使用者想採用經由《公共程式標準》測試過的程式基底，便可以預期這些程"
+"式基底具有方便重複利用、容易維護、高品質的特性。"
+
+#: ./foreword.md:block 51 (paragraph)
+msgid "The Standard for Public Code does this by:"
+msgstr "《公共程式標準》能有此效果是基於："
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "setting out a common terminology for public code development"
+msgstr "為公共程式開發訂立通用術語"
+
+#: ./foreword.md:block 52 (unordered list)
+msgid "establishing measures to help develop high quality public code"
+msgstr "制定措施協助高品質公共程式的開發"
+
+#: ./foreword.md:block 52 (unordered list)
+msgid ""
+"providing guidance on how to fulfill its criteria and operationalize "
+"compliance"
+msgstr "提出該如何符合準則並實作遵循的指引"
+
+#: ./foreword.md:block 53 (paragraph)
+msgid ""
+"The Standard for Public Code is meant to be time and technology independent."
+msgstr "《公共程式標準》設計精神就是要跨越時間與科技，不受其限制。"
+
+#: ./foreword.md:block 54 (header)
+msgid "Who this is for"
+msgstr "適用對象"
+
+#: ./foreword.md:block 55 (paragraph)
+msgid ""
+"The Standard for Public Code is for the people who create and reuse public "
+"code:"
+msgstr "《公共程式標準》適用於開發與重複使用公共程式的人："
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "public policy makers"
+msgstr "公共政策制定者"
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "business and project managers"
+msgstr "業務與專案經理"
+
+#: ./foreword.md:block 56 (unordered list)
+msgid "developers and designers"
+msgstr "開發人員與設計師"
+
+#: ./foreword.md:block 57 (paragraph)
+msgid "These people work at:"
+msgstr "在以下單位服務的人："
+
+#: ./foreword.md:block 58 (unordered list)
+msgid "institutions, organizations and administrations in the public sector"
+msgstr "社會機構、公家機關的組織與行政單位"
+
+#: ./foreword.md:block 58 (unordered list)
+msgid ""
+"consultancies and vendors of information technology and policy services to "
+"public organizations"
+msgstr "公家機關在資訊科技與政策服務上的顧問與供應商"
+
+#: ./foreword.md:block 59 (paragraph)
+msgid ""
+"It is not aimed at public organizations' end users (residents or citizens), "
+"journalists or academics."
+msgstr "適用對象不含公家機關的終端使用者（居民或市民）、記者或學者等。"
+
+#: ./foreword.md:block 61 (unordered list)
+msgid ""
+"[\"Modernising Public Infrastructure with Free Software\" white "
+"paper](https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-"
+"Software.pdf) by the Free Software Foundation Europe."
+msgstr ""
+"歐洲自由軟體基金會所發表的[《透過自由軟體實現公共基礎設施現代化》白皮書](http"
+"s://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-with-Free-Software.pdf)"
+" 》。"
+
+#: ./foreword.md:block 62 (header)
+msgid "Videos on public code"
+msgstr "探討公共程式的影片"
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Collaborative Code is the Future of Cities @ DecidimFest "
+"2019](https://www.youtube.com/watch?v=cnJtnZ9Cx1o). Talk by Ben Cerveny on "
+"the background behind the Foundation for Public Code."
+msgstr ""
+"[「程式協作是城市的未來」@ DecidimFest 2019](https://www.youtube.com/"
+"watch?v=cnJtnZ9Cx1o)。主講人 Ben Cerveny，講述 Foundation for Public Code "
+"的背景。"
+
+#: ./foreword.md:block 63 (unordered list)
+msgid ""
+"[Public Money? Public Code! - Panel @ Nextcloud Conference "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c). Touches on topics like "
+"procurement, law and more."
+msgstr ""
+"[ 「用公共的納稅錢？做公共的程式吧！」專題討論 @ Nextcloud 大會 "
+"2019](https://youtube.com/watch?v=QHFkD4xfd6c)。討論採購、法律等主題。"
+
+#: ./foreword.md:block 64 (header)
+msgid "Get involved"
+msgstr "參與我們"
+
+#: ./foreword.md:block 65 (paragraph)
+msgid ""
+"This standard is a living document. [Read our contributor "
+"guide](/CONTRIBUTING.md) to learn how you can make it better."
+msgstr "本標準是持續成長的文件。[請讀我們的〈貢獻者指引〉](/CONTRIBUTING."
+"md)，瞭解您可以怎麼做來讓本標準變得更好。"
+
+#: ./foreword.md:block 66 (header)
+msgid "Contact"
+msgstr "聯絡方式"
+
+#: ./foreword.md:block 67 (paragraph)
+msgid ""
+"For questions and more information about the Foundation for Public Code you "
+"can find us at [our website](https://publiccode.net/), email us at "
+"info@publiccode.net, or call us at +31 20 2 444 500."
+msgstr ""
+"若有疑問，或想進一步瞭解 Foundation for Public "
+"Code，請造訪[我們的網站](https://publiccode.net/)，或是寄電子郵件到 "
+"info@publiccode.net，或撥打我們的電話 +31 20 2 444 500。"
+
+#: ./glossary.md:block 3 (header)
+msgid "Glossary"
+msgstr "詞彙表"
+
+#: ./glossary.md:block 4 (header)
+msgid "Code"
+msgstr "程式或程式碼 (Code)"
+
+#: ./glossary.md:block 5 (paragraph)
+msgid ""
+"Any explicitly described system of rules. This includes laws, policy and "
+"ordinances, as well as source code that is used to build software. Both of "
+"these are rules, some executed by humans and others by machines."
+msgstr ""
+"任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以"
+"及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是"
+"由機器執行。"
+
+#: ./glossary.md:block 6 (header)
+msgid "Codebase"
+msgstr "程式基底 (Codebase)"
+
+#: ./glossary.md:block 7 (paragraph)
+msgid ""
+"Any discrete package of code (both source and policy), the tests and the "
+"documentation required to implement a piece of policy or software."
+msgstr "任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、"
+"測試與文件等的整套內容。"
+
+#: ./glossary.md:block 8 (paragraph)
+msgid "This can be, for example, a document or a version-control repository."
+msgstr "舉例而言，這個具體形式可以是文件，或是版本控制的儲存庫。"
+
+#: ./glossary.md:block 9 (header)
+msgid "Continuous integration"
+msgstr "持續整合"
+
+#: ./glossary.md:block 10 (paragraph)
+msgid ""
+"In software engineering, continuous integration (CI) is the practice of "
+"merging all developers' working copies to a development branch of a codebase"
+" as frequently as reasonable."
+msgstr "在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回"
+"程式基底開發中分支的實務作法。"
+
+#: ./glossary.md:block 11 (header)
+msgid "Different contexts"
+msgstr "不同情境"
+
+#: ./glossary.md:block 12 (paragraph)
+msgid ""
+"Two contexts are different if they are different public organizations or "
+"different departments for which there is not one decision maker that could "
+"make collaboration happen naturally."
+msgstr "只要是不同的公家機關或不同的部門，無法透過同一個決策單位讓協作自然發生，那就"
+"算是兩個不同的情境。"
+
+#: ./glossary.md:block 13 (header)
+msgid "General public"
+msgstr "一般大眾"
+
+#: ./glossary.md:block 14 (paragraph)
+msgid ""
+"The public at large: end users of the code and the services based upon it."
+msgstr "整體民眾：程式碼與其所建立的服務的終端使用者。"
+
+#: ./glossary.md:block 15 (paragraph)
+msgid ""
+"For example, a city's residents are considered end users of a city's "
+"services and of all code that powers these services."
+msgstr "舉例而言，城市的居民即視為該城市的服務、以及驅動這些服務運作的程式碼的終端使"
+"用者。"
+
+#: ./glossary.md:block 16 (header)
+msgid "Open source"
+msgstr "開源或開放原始碼 (Open Source)"
+
+#: ./glossary.md:block 17 (paragraph)
+msgid ""
+"Open source is defined by the Open Source Initiative in their [Open Source "
+"Definition](https://opensource.org/osd-annotated)."
+msgstr ""
+"所謂「開源」或「開放原始碼」，是根據 OSI "
+"開放原始碼促進會發表的《[開放原始碼定義](https://opensource.org/osd-"
+"annotated)》而來。"
+
+#: ./glossary.md:block 18 (header)
+msgid "Open standard"
+msgstr "開放標準"
+
+#: ./glossary.md:block 19 (paragraph)
+msgid ""
+"An open standard is any standard that meets the Open Source Initiative's "
+"[Open Standard Requirements](https://opensource.org/osr)."
+msgstr "任何符合 OSI 開放原始碼促進會《[開放標準需求規範](https://opensource.org/"
+"osr)》的標準，就是開放標準。"
+
+#: ./glossary.md:block 20 (header)
+msgid "Policy"
+msgstr "政策"
+
+#: ./glossary.md:block 21 (paragraph)
+msgid ""
+"A policy is a deliberate system of principles to guide decisions and achieve"
+" rational outcomes. A policy is a statement of intent, and is implemented as"
+" a procedure or protocol. Policies are generally adopted by a governance "
+"body within an organization. Policies can assist in both subjective and "
+"objective decision making."
+msgstr ""
+"政策是一套謹慎設計的原則體系，用來引導決策並達成合理的成果。政策是一種意圖的"
+"聲明，並以程序或協定來執行。政策通常是由組織單位內的理事機構採用執行。政策能"
+"協助做出主觀與客觀的決策。"
+
+#: ./glossary.md:block 22 (paragraph)
+msgid ""
+"Public policy is the process by which governments translate their political "
+"vision into programs and actions to deliver outcomes."
+msgstr "公共政策是政府將其政治願景，轉化成計畫與行動來取得成果的程序。"
+
+#: ./glossary.md:block 23 (paragraph)
+msgid ""
+"At the national level, policy and legislation (the law) are usually "
+"separate. The distinction is often more blurred in local government."
+msgstr "在國家層級，政策與立法（法律）通常是分開的；而在地方政府中，這兩者之間的區別"
+"通常比較模糊。"
+
+#: ./glossary.md:block 24 (paragraph)
+msgid ""
+"In the Standard the word 'policy' refers to policy created and adopted by "
+"public organizations such as governments and municipalities."
+msgstr "在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的"
+"政策。"
+
+#: ./glossary.md:block 25 (header)
+msgid "Public code"
+msgstr "公共程式 (Public Code)"
+
+#: ./glossary.md:block 26 (paragraph)
+msgid ""
+"Public code is open source software developed by public organizations, "
+"together with the policy and guidance needed for collaboration and reuse."
+msgstr "公共程式，是由公家機關所開發的開放原始碼軟體，同時包含協作與重複利用所需的政"
+"策與指引。"
+
+#: ./glossary.md:block 27 (paragraph)
+msgid ""
+"Public code is both computer source code (such as software and algorithms) "
+"and public policy executed in a public context, by humans or machines."
+msgstr "公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以"
+"及公共政策兩者。"
+
+#: ./glossary.md:block 28 (paragraph)
+msgid ""
+"Public code serves the public interest, is open, legible, accountable, "
+"accessible and sustainable."
+msgstr "服務公眾利益的公共程式，具有開放、易懂、課責、近用、永續等特性。"
+
+#: ./glossary.md:block 29 (paragraph)
+msgid ""
+"By developing public code independently from but still implementable in the "
+"local context for which it was developed, as well as documenting the "
+"development process openly, public code can provide a building block for "
+"others to:"
+msgstr ""
+"透過獨立於當地情境，但仍可在當地情境下實作的方式，還有公開以文件記錄開發程序"
+"等作法，來開發公共程式。如此，公共程式能作為基礎組件提供給他人，使其得以："
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "re-implement in their local context"
+msgstr "根據其當地情境重新實作"
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "take as a starting point to continue development"
+msgstr "作為起點並繼續開發"
+
+#: ./glossary.md:block 30 (unordered list)
+msgid "use as a basis for learning"
+msgstr "當作學習時的基礎"
+
+#: ./glossary.md:block 31 (paragraph)
+msgid ""
+"To facilitate reuse, public code is either released into the public domain "
+"or licensed with an open license that permits others to view and reuse the "
+"work freely and to produce derivative works."
+msgstr "為了促進重複利用，公共程式通常放到公眾領域發行，或者採取允許他人能自由檢視、"
+"重複利用其成果，甚至產出衍生作品的開放授權。"
+
+#: ./glossary.md:block 32 (header)
+msgid "Repository"
+msgstr "儲存庫"
+
+#: ./glossary.md:block 33 (paragraph)
+msgid ""
+"A repository is a storage location used by version control tools for files "
+"and metadata of a codebase. Repositories allow multiple contributors to work"
+" on the same set of files. Repositories are able to store multiple versions "
+"of sets of files."
+msgstr ""
+"儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多"
+"位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。"
+
+#: ./glossary.md:block 34 (header)
+msgid "Source Code"
+msgstr "原始碼 (Source Code)"
+
+#: ./glossary.md:block 35 (paragraph)
+msgid ""
+"Human readable text of a computer program which can be translated into "
+"machine instructions."
+msgstr "人類可讀，並且能夠翻譯成機器指令的電腦程式文字。"
+
+#: ./glossary.md:block 36 (header)
+msgid "Version control"
+msgstr "版本控制"
+
+#: ./glossary.md:block 37 (paragraph)
+msgid ""
+"Version control is the management of changes to source code and the files "
+"associated with it. Changes are usually identified by a code, termed the "
+"*revision number* (or similar). Each revision is associated with the time it"
+" was made and the person making the change, thus making it easier to retrace"
+" the evolution of the code. Revision control systems can be used to compare "
+"different versions with each other and to see how content has changed over "
+"time."
+msgstr ""
+"版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱"
+"為「*修訂編號*」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間"
+"以及作者，方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以"
+"及查看內容隨著時間經歷的變動。"
+
+#: ./index.md:block 3 (header)
+msgid "toc: false"
+msgstr "toc: false"
+
+#: ./index.md:block 4 (header)
+msgid "Guidance for government open source collaboration"
+msgstr "政府開放原始碼協作指引"
+
+#: ./index.md:block 5 (paragraph)
+msgid ""
+"The Standard for Public Code is a set of criteria that supports public "
+"organizations in developing and maintaining software and policy together."
+msgstr "《公共程式標準》是一套支持公家機關一同協作開發軟體與政策，以及維護的準則。"
+
+#: ./index.md:block 6 (paragraph)
+msgid ""
+"The Standard for Public Code provides guidance to public organizations "
+"building their own open source solutions to enable successful future "
+"collaboration and reuse by similar organizations in the public sector in "
+"other places. It includes advice for policy makers, government managers, "
+"developers and vendors. The Standard for Public Code supports the "
+"collaborative creation of codebases that are usable, open, legible, "
+"accountable, accessible and sustainable. It is meant to be applicable to "
+"codebases for all levels of government, from supranational to municipal."
+msgstr ""
+"《公共程式標準》為那些在建構自身開放原始碼解決方案的公家機關提供指引，以便他"
+"們未來能成功與其他地方的類似公部門單位互相協作，並且重複使用各自的成果。這份"
+"標準涵蓋寫給政策制定者、政府管理人員、開發人員與供應商的建議。《公共程式標準"
+"》支持公家機關透過協作方式，創造出好用、開放、易懂、課責、近用、永續的程式基"
+"底。這份標準從設計之初，就是要用於各種不同政府層級的程式基底，小從市政府，大"
+"到超國家組織都行。"
+
+#: ./index.md:block 7 (paragraph)
+msgid ""
+"The Standard for Public Code defines ‘[public code](glossary.md#public-"
+"code)’ as open source software developed by public organizations, together "
+"with the policy and guidance needed for collaboration and reuse."
+msgstr ""
+"《公共程式標準》將「[公共程式](glossary.md#public-code)」定義為：由公家機關所"
+"開發的開放原始碼軟體，同時包含協作與重複使用所需的政策與指引。"
+
+#: ./index.md:block 8 (paragraph)
+msgid ""
+"The criteria of the Standard for Public Code are aligned with guidelines and"
+" best practices of open source software development."
+msgstr "《公共程式標準》當中的準則，符合開放原始碼軟體開發的指引與最佳實務。"
+
+#: ./index.md:block 9 (paragraph)
+msgid ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} Additional"
+" context and background can be found in the [foreword](foreword.md). {% "
+"endif%}{% endfor %}"
+msgstr ""
+"{% for page in site.pages %}{% if page.name == \"foreword.md\" %} "
+"其他情境與背景資訊請參閱[序文](foreword.md)。 {% endif%}{% endfor %}"
+
+#: ./index.md:block 10 (header)
+msgid "Contents"
+msgstr "目次"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Readers guide: how to interpret this standard](readers-guide.md)"
+msgstr "[讀者指引：如何解讀本標準](readers-guide.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Glossary](glossary.md)"
+msgstr "[詞彙表](glossary.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[Criteria](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for"
+" page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
+msgstr ""
+"[準則](criteria/){% assign sorted = site.pages | sort:\"order\" %}{% for "
+"page in sorted %}{% if page.dir == \"/criteria/\" %}{% if page.name != "
+"\"index.md\" %}{% if page.title %}"
+
+#: ./index.md:block 11 (unordered list)
+msgid ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
+msgstr ""
+"[{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Authors](AUTHORS.md)"
+msgstr "[作者群](AUTHORS.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Contributing guide](CONTRIBUTING.md)"
+msgstr "[貢獻指引](CONTRIBUTING.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Code of conduct](CODE_OF_CONDUCT.md)"
+msgstr "[行為守則](CODE_OF_CONDUCT.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Governance](GOVERNANCE.md)"
+msgstr "[治理方式](GOVERNANCE.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[Version history](CHANGELOG.md)"
+msgstr "[版本歷史](CHANGELOG.md)"
+
+#: ./index.md:block 11 (unordered list)
+msgid "[License](license.html)"
+msgstr "[授權](license.html)"
+
+#: ./index.md:block 12 (header)
+msgid "Community calls"
+msgstr "社群會議"
+
+#: ./index.md:block 13 (paragraph)
+msgid ""
+"We usually have a community call on the first Thursday of the month at 15:00"
+" (CET/CEST). [The agenda](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code) is updated roughly a week before the call. It is "
+"possible to [sign "
+"up](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842)"
+" to get a call invitation emailed to you."
+msgstr ""
+"我們通常在每月第一個週四的 15:00 (CET/CEST) "
+"舉辦社群會議。[議程](https://write.publiccode.net/pads/Community-Call-"
+"Standard-for-Public-Code)在會議前約一週的時間更新。您可以[註冊](https://odoo."
+"publiccode.net/survey/start/"
+"594b9243-c7e5-4bc1-8714-35137c971842)報名，會再寄送會議通話邀請函給您。"
+
+#: ./index.md:block 14 (header)
+msgid "Other resources"
+msgstr "其他資源"
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"Unofficial [community translations of the "
+"Standard](https://publiccodenet.github.io/community-translations-standard/) "
+"in other languages"
+msgstr ""
+"本標準非官方的其他語言[社群翻譯](https://publiccodenet.github.io/"
+"community-translations-standard/)"
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard compliance self "
+"assessment](https://publiccodenet.github.io/assessment-eligibility/) for "
+"public sector open source codebases"
+msgstr ""
+"公部門開放原始碼程式基底的《[標準遵循自我評估](https://publiccodenet.github."
+"io/assessment-eligibility/)》"
+
+#: ./index.md:block 15 (unordered list)
+msgid ""
+"[Standard criteria "
+"checklist](https://github.com/publiccodenet/standard/blob/develop/docs/review-"
+"template.html) used by Foundation for Public Code stewards for codebase "
+"review"
+msgstr ""
+"Foundation for Public Code "
+"執事人員審查程式基底時所使用的《[本標準準則檢查清單](https://github.com/"
+"publiccodenet/standard/blob/develop/docs/review-template.html)》"
+
+#: ./readers-guide.md:block 3 (header)
+msgid "Readers guide"
+msgstr "讀者指引"
+
+#: ./readers-guide.md:block 4 (paragraph)
+msgid ""
+"The Standard describes a number of criteria. All criteria have consistent "
+"sections that make it clear how to create great public code."
+msgstr "本標準描述說明許多準則。所有準則各小節結構維持一致，來讓讀者清楚明白如何開發"
+"良好的公共程式。"
+
+#: ./readers-guide.md:block 5 (paragraph)
+msgid ""
+"References to \"policy makers\", \"managers\", and \"developers and "
+"designers\" apply to anyone performing duties associated with these roles, "
+"regardless of their job title. It is common for individuals to have duties "
+"which span multiple roles."
+msgstr "「政策制定者」、「管理人員」以及「開發人員與設計師」的稱呼，係指任何履行這些"
+"角色職責的人，不受其職稱限制。常見同時承擔多個角色職責的人。"
+
+#: ./readers-guide.md:block 6 (paragraph)
+msgid ""
+"Below is a brief explanation of each of these sections and how they are used"
+" within the criteria of the Standard."
+msgstr "以下是各小節的簡要介紹，以及在本標準準則中的作用。"
+
+#: ./readers-guide.md:block 7 (header)
+msgid "Introduction"
+msgstr "前言"
+
+#: ./readers-guide.md:block 8 (paragraph)
+msgid ""
+"This section explains what the criterion aims to achieve and why it is "
+"important for a codebase's users and contributors."
+msgstr "本小節說明這些準則想達成的目的，以及為何會對程式基底使用者與貢獻者來說這麼重"
+"要的原因。"
+
+#: ./readers-guide.md:block 10 (paragraph)
+msgid ""
+"This section lists what needs to be done in order to comply with the "
+"standard."
+msgstr "這個小節列出如果要遵循本標準，需要完成哪些事項。"
+
+#: ./readers-guide.md:block 11 (paragraph)
+msgid ""
+"The following keywords in this document are to be interpreted as described "
+"in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119):"
+msgstr ""
+"本文件中的下列關鍵字，請以《[IETF RFC 2119](https://tools.ietf.org/html/"
+"rfc2119)》的描述作解釋："
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST"
+msgstr "必須"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MUST NOT"
+msgstr "禁止"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "REQUIRED"
+msgstr "要求"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL"
+msgstr "應當"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHALL NOT"
+msgstr "不得"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD"
+msgstr "應該"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "SHOULD NOT"
+msgstr "不該"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "RECOMMENDED"
+msgstr "建議"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "MAY"
+msgstr "得以"
+
+#: ./readers-guide.md:block 12 (unordered list)
+msgid "OPTIONAL"
+msgstr "可選擇"
+
+#: ./readers-guide.md:block 14 (paragraph)
+msgid ""
+"This section offers actions you can take to see if a contribution is "
+"compliant with the Standard. This is key if you want to operationalize the "
+"Standard."
+msgstr "本小節提供您可採取的行動，來確認貢獻內容是否遵循本標準。如果您想要務實操作本"
+"標準，這部分很關鍵。"
+
+#: ./readers-guide.md:block 15 (paragraph)
+msgid ""
+"We've tried to word it so that someone who is not intimately acquainted with"
+" the subject matter can still do a basic check for compliance."
+msgstr "我們已嘗試調整用字，讓即使是不熟悉這類主題內容的讀者，看完之後也能夠進行基本"
+"的遵循檢查。"
+
+#: ./readers-guide.md:block 17 (paragraph)
+msgid ""
+"This section tries to specifically speak to policy makers by offering them "
+"concrete actions they can perform in their role."
+msgstr "本小節主要對象是政策制定者，列出他們的角色所能採取的具體行動。"
+
+#: ./readers-guide.md:block 18 (paragraph)
+msgid ""
+"Public policy makers set the priorities and goals of projects and may be "
+"less technologically experienced."
+msgstr "公共政策制定者設定專案的優先順序與目標，而在科技上的經驗可能沒那麼多。"
+
+#: ./readers-guide.md:block 20 (paragraph)
+msgid ""
+"This section tries to specifically speak to managers by offering concrete "
+"actions they can perform in their role."
+msgstr "本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。"
+
+#: ./readers-guide.md:block 21 (paragraph)
+msgid ""
+"Managers are responsible for on-time project delivery, stakeholder "
+"management and continued delivery of the service. For this they are wholly "
+"reliant on both policy makers as well as developers and designers. They need"
+" to create the right culture, line up the right resources and provide the "
+"right structures to deliver great services."
+msgstr ""
+"管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他"
+"們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的"
+"資源、提供適當的架構等，才能交付優良的服務。"
+
+#: ./readers-guide.md:block 23 (paragraph)
+msgid ""
+"This section tries to specifically speak to developers and designers by "
+"offering them concrete actions they can perform in their role."
+msgstr "本小節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。"
+
+#: ./readers-guide.md:block 24 (paragraph)
+msgid ""
+"Developers are usually more technically aligned and have more impact on the "
+"delivery of services than the previous groups."
+msgstr "開發人員通常對技術比較在行，與其他角色類別相比，對服務交付的影響更大。"
+
+#: ./readers-guide.md:block 25 (header)
+msgid "Limitation of scope"
+msgstr "作用範圍限制"
+
+#: ./readers-guide.md:block 26 (paragraph)
+msgid ""
+"The Standard for Public Code is not meant to cover individual "
+"implementations of a codebase. This means the standard does not tell "
+"implementers how to comply with their organization's local technical "
+"infrastructure or legal framework."
+msgstr "《公共程式標準》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴"
+"實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。"
+
+#: ./readers-guide.md:block 27 (paragraph)
+msgid ""
+"Also, while the Standard for Public Code refers to several standards and has"
+" considerable overlap with others, its purpose is to enable collaboration. "
+"Therefore, it does not aim to replace quality standards, like the ISO 25000 "
+"series, or those focusing on security, like the [OpenSSF Best Practices "
+"Badge](https://github.com/coreinfrastructure/best-practices-badge), but to "
+"synergize well with them."
+msgstr ""
+"此外，雖然《公共程式標準》有引用一些標準，並且與其他標準有滿多重疊的部分，但"
+"本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，像是 ISO 25000 "
+"認證系列，或是取代那些聚焦於安全性的標準，例如 [OpenSSF "
+"最佳實務標章](https://github.com/coreinfrastructure/best-practices-"
+"badge)等，而是希望能與它們能良好協同搭配。"
+
+#: ./readers-guide.md:block 28 (paragraph)
+msgid ""
+"And while the purpose includes enabling collaboration, it will not guarantee"
+" that a community will spring into existence. That still requires "
+"proactiveness and ambition beyond making the codebase collaboration ready."
+msgstr ""
+"《公共程式標準》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社"
+"群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到超越協作以外"
+"的企圖心。"
+
+msgid ""
+"script/release-body.sh expects VERSION in the first second-level header"
+msgstr "script/release-body.sh 預期 VERSION 放在第一個第二層的標頭中"
+
+msgid "script/update-changelog-date.sh expects DATE-OF-RELEASE and a colon"
+msgstr "script/update-changelog-date.sh 預期 DATE-OF-RELEASE 與一個冒號「:」"
+
+msgid "Version 0.7.1"
+msgstr "0.7.1 版"
+
+msgid ""
+"July 31st 2023: 💄 The sixteenth draft change the name of a criterion and "
+"clarifies references to code."
+msgstr "2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。"
+
+msgid ""
+"The criterion \"Make the codebase reusable and portable\" was renamed from "
+"\"Create reusable and portable code\"."
+msgstr "〈程式碼要可重複使用且可攜〉準則改名為〈程式基底要可重複使用且可移植〉。"
+
+msgid "Added a glossary entry for \"Source Code\"."
+msgstr "新增詞彙條目「原始碼」。"
+
+msgid ""
+"References to \"code\" which only applied to \"source code\" now reference "
+"\"source code\" explicitly."
+msgstr "對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。"
+
+msgid "Clarification of \"running code\" as \"software\"."
+msgstr "將「運作的程式碼」釐清稱為「軟體」。"
+
+msgid "Minor changes to clarify \"code\" vs \"codebase\"."
+msgstr "細微修改以清楚區分「程式碼」與「程式基底」。"
+
+msgid "Simplify guidance to policy makers in Bundle policy and source code."
+msgstr "簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。"
+
+msgid ""
+"Clarify How to test sections of Make the codebase findable and Make the "
+"codebase reusable and portable."
+msgstr "釐清〈程式基底可查詢得到〉與〈程式基底要可重複使用且可移植〉的「測試方式」小"
+"節。"
+
+msgid "Add a criteria and requirements checklist to the release artifacts."
+msgstr "在發行成品前的要求中，加入準則與需求規定檢查清單。"
+
+msgid "Increase automation of the release process."
+msgstr "提升發行流程的自動化程度。"
+
+msgid ""
+"![version 0.7.1](assets/version-badge.svg) [![License: "
+"CC0-1.0](https://img.shields.io/badge/License-"
+"CC0_1.0-lightgrey.svg)](http://creativecommons.org/publicdomain/zero/1.0/) "
+"[![Standard commitment](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
+msgstr ""
+"![version 0.7.1](assets/version-badge.svg) [![License: CC0-1.0](https://img."
+"shields.io/badge/License-CC0_1.0-lightgrey.svg)](http://creativecommons.org/"
+"publicdomain/zero/1.0/) [![標準承諾](assets/standard-for-public-code-"
+"commitment.svg)](#help-improve-this-standard)"
+
+msgid ""
+"If you want to apply the Standard for Public Code to your codebase, just go "
+"ahead, it's an open standard and free for anyone to use. If you wish to "
+"advertise the codebase community's aspiration to meet the criteria of the "
+"Standard for Public Code, link the documentation of this commitment from the"
+" [standard-for-public-code-commitment badge](assets/standard-for-public-"
+"code-commitment.svg). To see how ready your codebase is, you can do a quick "
+"[eligibility self assessment](https://publiccodenet.github.io/assessment-"
+"eligibility) that will give you a rough idea of how much work you may need "
+"to do to meet all criteria."
+msgstr ""
+"若您想要將《公共程式標準》套用您的程式基底，就請放心去做，因為它是人人都能自"
+"由採用的開放標準。如果您希望宣傳程式基底社群達成《公共程式標準》準則要求時的"
+"熱誠，請使用 [standard-for-public-code-commitment 徽章](assets/standard-for-"
+"public-code-commitment.svg)連結到這份承諾文件。若要瞭解您程式基底所達成的程度"
+"，可以做[自我資格評估](https://publiccodenet.github.io/assessment-"
+"eligibility)；它能幫助您大略瞭解，如果想要滿足所有準則，還需要下多少功夫。"
+
+msgid "Update [`roadmap.md`](roadmap.md)"
+msgstr "更新 [`roadmap.md`](roadmap.md)"
+
+msgid ""
+"update `docs/standard-for-public-code.html` with the new text from the "
+"review template, updating any status changes as a result"
+msgstr "使用審查範本中的新文字來更新 `docs/standard-for-public-code."
+"html`，會將任何狀態變更作為結果更新"
+
+msgid ""
+"Push branch, compare with 'main' branch, i.e.: "
+"`https://github.com/publiccodenet/standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
+msgstr ""
+"推送分支，與「main」分支比較，範例：`https://github.com/publiccodenet/"
+"standard/compare/main...release-$MAJOR.$MINOR.$PATCH`"
+
+msgid "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr "`git tag trigger-$MAJOR.$MINOR.$PATCH`"
+
+msgid "delete local tag: `git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
+msgstr "移除本地端的 tag 標記：`git tag -d trigger-$MAJOR.$MINOR.$PATCH`"
+
+msgid "Separate executive summary (issue #302)"
+msgstr "分離執行摘要 (issue #302)"
+
+msgid ""
+"[Standard criteria checklist](/docs/review-template.html) used by Foundation"
+" for Public Code stewards for codebase review"
+msgstr ""
+"Foundation for Public Code 執事人員用於程式基底審查的《[標準準則檢查清單](/"
+"docs/review-template.html)》"
diff --git a/_site/package.json b/_site/package.json
new file mode 100644
index 00000000..fb24660f
--- /dev/null
+++ b/_site/package.json
@@ -0,0 +1,5 @@
+{
+  "dependencies": {
+    "badge-maker": "^3.3.1"
+  }
+}
diff --git a/_site/print-cover.html b/_site/print-cover.html
new file mode 100644
index 00000000..5c3f5c2f
--- /dev/null
+++ b/_site/print-cover.html
@@ -0,0 +1,308 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<html lang="en">
+
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <title>Standard for Public Code</title>
+  <style>
+    html {
+      font-family: Mulish;
+      font-size: 16pt;
+      margin: 0;
+      padding: 0;
+    }
+
+    *,
+    * {
+      box-sizing: border-box;
+      margin: 0;
+      padding: 0;
+    }
+
+    article {
+      position: relative;
+    }
+
+    article>section {
+      width: 21.6cm;
+      height: 30.3cm;
+      top: 0;
+      bottom: 0;
+      position: absolute;
+    }
+
+    #back {
+      left: 0;
+    }
+
+    #back>* {
+      position: absolute;
+      left: 2.3cm;
+      width: 16cm;
+    }
+
+    #front {
+      right: 0;
+    }
+
+    #front>* {
+      position: absolute;
+      left: 2cm;
+      width: 16cm;
+    }
+
+    /* Back */
+
+    #back-text {
+      position: absolute;
+      top: 2.3cm;
+    }
+
+    #back-text>p {
+      margin-bottom: 1em;
+    }
+
+    #back img[alt="hand pointing"] {
+      right: 0;
+      top: 18cm;
+      width: 18cm;
+      left: auto;
+    }
+
+    #logo {
+      bottom: 2cm;
+    }
+
+    #logo>img {
+      height: 2cm;
+    }
+
+    ol {
+      column-count: 2;
+      font-size: 12pt;
+      list-style-position: inside;
+    }
+
+    /* Front */
+
+    div#title-block {
+      position: absolute;
+      top: 2.3cm;
+    }
+
+    h1.title {
+      font-size: 3.5em;
+      font-weight: 700;
+    }
+
+    /* Audience blocks */
+
+    ul.audiences {
+      position: absolute;
+      top: 10cm;
+      list-style: none;
+      font-size: 1.25em;
+      padding-left: 0;
+    }
+
+    .audiences li,
+    .audiences lh {
+      display: block;
+      margin-bottom: .5cm;
+    }
+
+    .audiences lh {
+      margin-bottom: 1cm;
+    }
+
+    .audiences li {
+      padding-left: 1.2cm;
+    }
+
+    .audiences li::before {
+      margin-top: -.03cm;
+    }
+
+    [id$="public-policy-makers-what-you-need-to-do"]:before,
+    [id$="managers-what-you-need-to-do"]:before,
+    [id$="developers-and-designers-what-you-need-to-do"]:before {
+      display: block;
+      position: absolute;
+      content: 'A';
+      text-align: center;
+      width: 1cm;
+      height: 1cm;
+      color: white;
+      display: inline-block;
+      margin-left: -1.2cm;
+      box-sizing: border-box;
+      padding: 0.20cm;
+      font-size: .5cm;
+      font-weight: 900;
+    }
+
+    [id$="public-policy-makers-what-you-need-to-do"]:before {
+      background-color: #00EFB5;
+      content: 'P';
+    }
+
+    [id$="managers-what-you-need-to-do"]:before {
+      background-color: #FF6D1C;
+      content: 'M';
+    }
+
+    [id$="developers-and-designers-what-you-need-to-do"]:before {
+      background-color: #8626FF;
+      content: 'D';
+    }
+
+    /* Hands */
+
+    #front img[alt="hands shaking"] {
+      left: 0;
+      right: 0;
+      top: 18cm;
+      width: 21.6cm;
+    }
+
+    /* Version info */
+
+    #version-info {
+      bottom: 2cm;
+      font-size: .75em;
+    }
+
+    /* Print specific */
+
+    @media print {
+      @page {
+        /* A4 times 2 plus a back of about 6mm and a 3mm bleed on every side */
+        size: 43.2cm 30.3cm;
+        margin: 0;
+        padding: 0;
+        background-color: white;
+      }
+    }
+
+    /* Screen mock-up when using a browser */
+
+    @media screen {
+      body {
+        background-color: whitesmoke;
+      }
+
+      article {
+        display: block;
+        background-color: white;
+        min-height: 30.3cm;
+        max-height: 30.3cm;
+        min-width: 43.2cm;
+        max-width: 43.2cm;
+      }
+    }
+  </style>
+</head>
+
+<body>
+
+  <article>
+    <section id="back">
+      <div id="back-text">
+        <p>
+          The Standard for Public Code supports the collaborative creation of codebases that are usable, open, legible, accountable, accessible and sustainable.
+          The Standard includes guidance to policymakers, managers, designers and developers creating and managing codebases.
+        </p>
+        <p>
+          The standard specifies the criteria:
+          
+          <ol>
+            
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+              
+                
+            <li>原始碼要開放</li>
+              
+            <li>政策與原始碼要合捆</li>
+              
+            <li>程式基底要可重複使用且可移植</li>
+              
+            <li>歡迎貢獻者</li>
+              
+            <li>貢獻要容易</li>
+              
+            <li>維護版本控制</li>
+              
+            <li>要求審查貢獻內容</li>
+              
+            <li>程式基底要有目標文件</li>
+              
+            <li>程式碼要有文件</li>
+              
+            <li>使用白話的英語</li>
+              
+            <li>採用開放標準</li>
+              
+            <li>使用持續整合</li>
+              
+            <li>發行採用開放授權</li>
+              
+            <li>程式基底可查詢得到</li>
+              
+            <li>風格要前後一致</li>
+              
+            <li>記錄程式基底成熟度</li>
+              
+          </ol>
+        </p>
+      </div>
+
+      <img src="assets/hand-point.svg" alt="hand pointing">
+
+      <section id="logo">
+        <img src="https://brand.publiccode.net/logo/mark-and-name-over-two-lines.svg" alt="Foundation for Public Code logo">
+      </section>
+    </section>
+
+    <section id="front">
+      <div id="title-block">
+        <p>Request for contributions</p>
+        <h1 class="title">Standard for Public Code</h1>
+      </div>
+
+      <ul class="audiences">
+        <lh>What public code is and how to implement it for:</lh>
+        <li id="first-page-public-policy-makers-what-you-need-to-do">Public policy makers</li>
+        <li id="first-page-managers-what-you-need-to-do">Managers</li>
+        <li id="first-page-developers-and-designers-what-you-need-to-do">Developers and designers</li>
+      </ul>
+
+      <img src="assets/hands-shake.svg" alt="hands shaking">
+
+      <div id="version-info">
+        <p><strong>Draft</strong><br/>Version <span class="standard-version">0.7.1</span></p>
+        <p><img src="/assets/cc-zero-badge.svg" alt="Licensed CC0" height="46"> <img src="/assets/dpg-badge.svg" alt="Digital Public Goods approval badge" width="92" height="46"></p>
+        <p>https://standard.publiccode.net/</p>
+      </div>
+    </section>
+  </article>
+
+</body>
+
+</html>
diff --git a/_site/publiccode.yml b/_site/publiccode.yml
new file mode 100644
index 00000000..7a700c99
--- /dev/null
+++ b/_site/publiccode.yml
@@ -0,0 +1,74 @@
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+# This repository adheres to the publiccode.yml standard by including this
+# metadata file that makes public software easily discoverable.
+# More info at https://github.com/italia/publiccode.yml
+
+publiccodeYmlVersion: '0.2'
+categories:
+  - collaboration
+  - project-collaboration
+description:
+  en:
+    features:
+      - enables collaboration
+      - enables successful future reuse
+      - |-
+        gives public organizations a model for building their own open source
+        solutions
+      - |-
+        gives guidance for policy makers, city administrators, developers and
+        vendors
+    genericName: standard
+    localisedName: Standard for Public Code
+    longDescription: |
+      The Standard for Public Code gives public organizations a model for
+      preparing open source solutions to enable collaborations with similar
+      public organizations in other places. It includes guidance for policy
+      makers, city administrators, developers and vendors.
+
+
+      The Standard defines ‘public code’ as open source software developed by
+      public organizations, together with the policy and guidance needed for
+      collaboration and reuse.
+
+
+      The Standard is recognized as a [Digital Public
+      Good](https://digitalpublicgoods.net/registry/standard-for-public-code.html)
+      by the [Digital Public Goods Alliance](https://digitalpublicgoods.net/).
+    shortDescription: |-
+      It gives public organizations a model for preparing open source solutions
+      to enable collaborations with similar public organizations in other
+      places.
+    videos:
+      - 'https://www.youtube.com/watch?v=QWt6vB-cipE'
+developmentStatus: beta
+landingURL: 'https://standard.publiccode.net/'
+legal:
+  authorsFile: 'https://raw.githubusercontent.com/publiccodenet/standard/master/AUTHORS.md'
+  license: CC0-1.0
+  mainCopyrightOwner: Foundation for Public Code
+  repoOwner: Foundation for Public Code
+localisation:
+  availableLanguages:
+    - en
+  localisationReady: false
+maintenance:
+  contacts:
+    - affiliation: Foundation for Public Code
+      email: eric@publiccode.net
+      name: Eric Herman
+    - affiliation: Foundation for Public Code
+      email: jan@publiccode.net
+      name: Jan Ainali
+  type: internal
+name: Standard for Public Code
+platforms:
+  - web
+releaseDate: '2023-07-31'
+roadmap: 'https://github.com/publiccodenet/standard/blob/develop/docs/roadmap.md'
+softwareType: standalone/other
+softwareVersion: 0.7.1
+url: 'https://github.com/publiccodenet/standard/'
+usedBy:
+  - Provincie Zuid-Holland
diff --git a/_site/python/po2md.py b/_site/python/po2md.py
new file mode 100644
index 00000000..3cd0cd10
--- /dev/null
+++ b/_site/python/po2md.py
@@ -0,0 +1,102 @@
+import os
+import shutil
+import subprocess
+
+PROJECT_FOLDER = "./"
+SOURCE_FOLDER = "./origin_source"
+
+def main():
+    root_path = "./"
+    source_path = "./origin_source"
+
+    # 1. get all md file
+    md_files = find_md_files(PROJECT_FOLDER)
+
+    # 2. filter origin file
+    md_files = [file for file in md_files if not file.startswith(SOURCE_FOLDER)]
+
+    # 3A. backup md file (只有主程式更新的時候，才需要複製一次)
+    # backup_md_files(md_files)
+
+    # 3B. restore md file
+    restore_md_files(md_files)
+
+    # 4. run po2md
+    for file in md_files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        do_po2md(source_file=full_target_path, target_file=file)
+
+    # 4. update md file
+    update_md_file(SOURCE_FOLDER)
+
+
+
+
+def find_md_files(folder_path) -> list:
+    md_files = []
+    for root, dirs, files in os.walk(folder_path):
+        md_files += [os.path.join(root, file) for file in files if file.endswith('.md')]
+    return md_files
+
+# 複製原始檔案
+def backup_md_files(files):
+    if not os.path.exists(SOURCE_FOLDER):
+        os.makedirs(SOURCE_FOLDER)
+
+    for file in files:
+        # 建立目標資料夾的完整路徑
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        if not os.path.exists(os.path.dirname(full_target_path)):
+            os.makedirs(os.path.dirname(full_target_path))
+
+        # 複製檔案到目標資料夾
+        shutil.copy2(file, full_target_path)
+
+# 還原原始檔案
+def restore_md_files(files):
+    for file in files:
+        full_target_path = os.path.join(SOURCE_FOLDER, os.path.relpath(file, PROJECT_FOLDER))
+        shutil.copy2(full_target_path, file)
+
+
+def do_po2md(source_file, target_file):
+    locale_file = "locales/zh_Hant/LC_MESSAGES/messages.po"
+    cmd = f"po2md -p {locale_file} -s {target_file} {source_file}"
+    result = subprocess.run(cmd, shell=True, capture_output=True, text=True)
+    if result.returncode != 0:
+        print("錯誤訊息：")
+        print(result.stderr)
+        exit()
+
+def update_md_file(source_path):
+    source_marker = "---"
+    target_marker = "***"
+
+    source_files = find_md_files(source_path)
+    for file in source_files:
+        with open(file, 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(source_marker)
+        end_index = file_content.find(source_marker, start_index + len(source_marker))
+        copied_content = file_content[start_index:end_index + len(source_marker)]
+
+
+        with open(file[len(source_path) + 1:], 'r') as infile:
+            file_content = infile.read()
+
+        start_index = file_content.find(target_marker)
+        end_index = file_content.find(target_marker, start_index + len(target_marker))
+        if end_index == -1:
+            print(file)
+            continue
+
+        new_content = copied_content + file_content[end_index + len(target_marker):]
+
+        with open(file[len(source_path) + 1:], 'w') as outfile:
+            outfile.write(new_content)
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file
diff --git a/_site/python/update_po.py b/_site/python/update_po.py
new file mode 100644
index 00000000..b8df8924
--- /dev/null
+++ b/_site/python/update_po.py
@@ -0,0 +1,34 @@
+import os
+import shutil
+import subprocess
+import polib
+
+
+def main():
+    locals_en = 'locales/en/LC_MESSAGES/messages.po'
+    locals_zh = 'locales/zh_Hant/LC_MESSAGES/messages.po'
+    en_po = polib.pofile(locals_en)
+    zh_po = polib.pofile(locals_zh)
+
+    zh_msgids = set(entry.msgid for entry in zh_po)
+
+    # 遍歷 en.po 中的每一個 entry
+    for entry in en_po:
+        # 如果 en.po 中的 msgid 不在 zh.po 中
+        if entry.msgid not in zh_msgids:
+            # 創建一個新的 POEntry 對象
+            new_entry = polib.POEntry(
+                msgid=entry.msgid,
+                msgstr='',  # 初始為空字符串
+            )
+            # 將新的 entry 添加到 zh.po 中
+            zh_po.append(new_entry)
+
+    # 儲存更新後的 zh.po 檔案
+    zh_po.save(locals_zh)
+
+
+
+
+if __name__ == '__main__':
+    main()
\ No newline at end of file
diff --git a/_site/readers-guide.html b/_site/readers-guide.html
new file mode 100644
index 00000000..99ba11c0
--- /dev/null
+++ b/_site/readers-guide.html
@@ -0,0 +1,313 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+  <meta charset="utf-8">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+
+  <title>讀者指引, Standard for Public Code</title>
+  <meta name="description" content="A Foundation for Public Code jekyll theme for use with GitHub pages.">
+
+  <link rel="stylesheet" href="/assets/style.css">
+
+  
+  <link rel="canonical" href="/readers-guide.html">
+  
+
+  <link rel="icon" href="https://brand.publiccode.net/logo/mark-128w128h.png">
+
+  
+  
+
+  <script async defer data-domain="publiccode.net" src="https://plausible.io/js/plausible.js"></script>
+</head>
+
+
+  <body class="with-toc ">
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓" aria-hidden="true">
+    <p>Foundation&nbsp;for Public&nbsp;Code</p>
+  </a>
+  <ul>
+    <li><a href="https://publiccode.net/codebase-stewardship/" title="代碼基底盡職管理">代碼基底盡職管理</a></li>
+    <li><a href="https://projects.publiccode.net/" title="Project Resources">專案資源</a></li>
+    <li><a href="https://publiccode.net/team/">基金會簡介</a></li>
+    <li><a href="https://about.publiccode.net/CONTRIBUTING.html">加入我們</a></li>
+    <li><a href="https://floss.social/@publiccode"  title="Foundation for Public Code 的 Mastodon 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.mastodon-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path
+     style="stroke-width:1" class="mastodon-logo" d="m 15.48675,0.6259278 -0.338293,0.0286534 c -0.733449,0.4231435 -1.49511,0.8743875 -2.256768,1.2975314 -0.253885,0.1410477 -0.536093,0.2253467 -0.818189,0.3663943 -0.310304,0.141048 -0.620943,0.3105265 -0.903039,0.5079943 -0.141048,0.1128375 -0.281985,0.1972461 -0.451241,0.1972461 -0.197469,0 -0.366727,0.028653 -0.564194,0.028653 C 9.0830622,3.0241881 8.0396346,2.9958702 6.9676708,2.9394521 6.770204,2.9112396 6.6288248,2.967444 6.4877772,3.1366983 5.9800047,3.7291003 5.5007715,4.2931826 4.992999,4.8573741 4.0902924,5.872919 3.1309441,6.775849 2.0871896,7.6221359 1.8615135,7.7913931 1.7487846,7.9889719 1.7769942,8.2992766 c 0.084627,0.7334487 0.1693683,1.4666813 0.2539968,2.1719204 0.028213,0.394934 0.112617,0.790199 0.1972464,1.185134 0.056415,0.282096 0.028213,0.648491 0,0.930584 2.395e-4,9.61e-4 3.104e-4,0.0011 5.643e-4,0.0021 0.1410476,0.451352 0.5594538,3.823613 0.6440824,4.133918 0.225677,0.902707 0.4513542,1.833405 0.70524,2.736112 0.056415,0.169257 0.1977981,0.338846 0.3388459,0.479894 0.3385153,0.310304 0.7331199,0.563971 1.0716344,0.902486 0.8462876,0.846287 1.9789705,1.675056 2.7124202,2.634184 0.056415,0 0.084628,1.1e-4 0.1410475,-0.02811 1.0155455,-0.423145 2.0871811,-0.733119 3.1873559,-0.930585 0.282095,-0.05642 0.56452,-0.169479 0.62094,-0.507994 0.169259,-0.874498 0.338295,-1.720679 0.479343,-2.566965 -0.789869,-0.479564 -1.607948,-0.507994 -2.3978171,-0.507994 0.112842,0.592402 -0.1689258,1.071965 -0.3663931,1.551528 -0.056417,0.08464 -0.2260074,0.140939 -0.3388464,0.169148 -0.2256753,0.05642 -0.4795626,0.02831 -0.7052397,0.112956 C 8.067529,20.852246 7.898381,20.796042 7.7291228,20.570371 7.3623992,20.090863 6.9957835,19.639284 6.5726397,19.216143 6.3187538,18.962256 6.4034927,18.313325 6.4034927,18.256905 9.0220695,15.607439 9.5529675,15.821151 12.77874,15.097651 c 0.253886,0.197467 0.535761,0.366615 0.761438,0.592291 0.479562,0.423143 1.3826,1.636046 1.467232,1.720677 0.169255,0.169257 0.342453,-0.252332 0.229614,-0.02665 3.840633,-5.909872 4.736073,-7.17506 7.838222,-11.1161427 -1.015547,0 -2.059304,-0.027991 -3.103057,-0.056196 -0.122118,0.0131 -0.353847,0.028453 -0.423145,0.028097 C 19.136684,6.1920712 18.359917,6.1435607 18.068591,5.6362484 17.871124,5.3541522 15.768847,0.99266896 15.48675,0.6259441 Z"/></svg></a></li>
+    <li><a href="https://twitter.com/publiccodenet" title="Foundation for Public Code 的 Twitter 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" x="0px" y="0px" width="24" height="24" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">#path172{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path d="m 9.9653138,4.2421956 c -1.6089791,-1.989512 -5.260932,-1.871851 -7.3020383,0.793517 -0.3681602,0.480686 -0.656245,1.104014 -0.873826,1.811853 L 0.427,7.4162646 1.4938942,8.0795126 C 1.0031695,10.772662 1.2884528,14.095209 1.9757474,15.713059 4.0810541,20.668631 10.890267,22.078472 14.842211,20.519452 20.576825,18.256796 23.573,13.677089 23.573,13.677089 c 0,0 -6.694119,-0.0712 -13.6076862,-9.4348934 z m -4.71161,2.266391 c -0.078441,0.384969 -0.5117356,0.62613 -0.9679087,0.538117 -0.4561732,-0.08778 -0.7624675,-0.471348 -0.6840263,-0.856317 0.078208,-0.384969 0.5117357,-0.626129 0.9679088,-0.53835 0.4561731,0.08801 0.762234,0.471348 0.6840262,0.85655 z M 18.751666,15.522325 c -0.561696,1.484548 -3.161229,1.876987 -5.805352,0.876394 -2.644357,-1.000592 -4.3327107,-3.015318 -3.7710154,-4.500332 0.5616952,-1.48478 3.1609944,-1.87722 5.8055854,-0.876394 2.644123,1.000593 4.332477,3.015552 3.770782,4.500332 z" id="path172" style="stroke-width:1" /></svg></a></li>
+    <li><a href="https://github.com/publiccodenet/" title="Foundation for Public Code 的 Github 頁面"><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="24px" height="24px" viewBox="0 0 24 24" style="overflow:visible;enable-background:new 0 0 24 24;" xml:space="preserve"><style type="text/css">.github-logo{fill-rule:evenodd;clip-rule:evenodd;fill:#24292E;transform:translateY(6px);}</style><path class="github-logo" d="M12,0C5.4,0,0,5.5,0,12.3c0,5.4,3.5,10,8.2,11.7C8.8,24.1,9,23.7,9,23.4c0-0.3,0-1.1,0-2.1 c-3.3,0.8-4-1.7-4-1.7c-0.5-1.4-1.3-1.8-1.3-1.8c-1.1-0.8,0.1-0.8,0.1-0.8c1.2,0.1,1.8,1.3,1.8,1.3c1.1,1.9,2.8,1.4,3.5,1.1 c0.1-0.8,0.4-1.4,0.7-1.7c-2.7-0.3-5.4-1.4-5.4-6.1c0-1.4,0.4-2.4,1.3-3.3C5.4,8.1,5,6.8,5.7,5.1c0,0,1-0.3,3.3,1.3 c1-0.3,2-0.4,3-0.4s2.1,0.2,3,0.4c2.3-1.6,3.3-1.3,3.3-1.3c0.7,1.7,0.2,2.9,0.1,3.2c0.7,0.8,1.3,2,1.3,3.3c0,4.8-2.8,5.7-5.4,6 c0.4,0.4,0.8,1.1,0.8,2.3c0,1.7,0,2.9,0,3.4c0,0.3,0.2,0.7,0.8,0.6c4.8-1.7,8.2-6.3,8.2-11.7C24,5.5,18.6,0,12,0z"/></svg></a></li>
+  </ul>
+</nav>
+
+
+    <header>
+  
+    <section class="site-title ">
+      <a href="">Standard for Public Code</a>
+    </section>
+  
+
+  
+</header>
+
+
+<hr>
+
+<main>
+
+   
+
+  
+
+  
+
+  <section class="page-information">
+
+  
+
+
+
+
+
+
+  
+    
+
+    
+      <h3 id="page-table-of-contents">目次</h3>
+      <ol class="table-of-contents">
+  <li><a href="#前言">前言</a></li>
+  <li><a href="#需求規定">需求規定</a></li>
+  <li><a href="#測試方式">測試方式</a></li>
+  <li><a href="#公共政策制定者需要的工作">公共政策制定者：需要的工作</a></li>
+  <li><a href="#管理人員需要的工作">管理人員：需要的工作</a></li>
+  <li><a href="#開發人員與設計師需要的工作">開發人員與設計師：需要的工作</a></li>
+  <li><a href="#作用範圍限制">作用範圍限制</a></li>
+</ol>
+
+    
+  
+
+  
+
+  
+    <h3 id="page-edit-links">到 GitHub 貢獻</h3>
+    <ul class="edit-links">
+      <!-- The default branch is master, while site.github.source.branch is gh-pages -->
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/edit/master/readers-guide.md"><svg aria-hidden="true" class="octicon octicon-git-pull-request" height="16" version="1.1" viewBox="0 0 12 16" width="12"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
+ 編輯此頁面</a></li>
+      <li><a href="https://github.com/publiccodenet/jekyll-theme/issues/new?body=I'd like to report an issue in `readers-guide.md`"><svg aria-hidden="true" class="octicon octicon-issue-opened" height="16" version="1.1" viewBox="0 0 14 16" width="14"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg>
+ 通報問題</a></li>
+    </ul>
+  
+
+</section>
+
+  
+  <section class="content">
+  
+  <article class="markdown-body">
+    <h1 id="讀者指引">讀者指引</h1>
+
+<p>本標準描述說明許多準則。所有準則各小節結構維持一致，來讓讀者清楚明白如何開發良好的公共程式。</p>
+
+<p>「政策制定者」、「管理人員」以及「開發人員與設計師」的稱呼，係指任何履行這些角色職責的人，不受其職稱限制。常見同時承擔多個角色職責的人。</p>
+
+<p>以下是各小節的簡要介紹，以及在本標準準則中的作用。</p>
+
+<h2 id="前言">前言</h2>
+
+<p>本小節說明這些準則想達成的目的，以及為何會對程式基底使用者與貢獻者來說這麼重要的原因。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<p>這個小節列出如果要遵循本標準，需要完成哪些事項。</p>
+
+<p>本文件中的下列關鍵字，請以《<a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a>》的描述作解釋：</p>
+
+<ul>
+  <li>必須</li>
+  <li>禁止</li>
+  <li>要求</li>
+  <li>應當</li>
+  <li>不得</li>
+  <li>應該</li>
+  <li>不該</li>
+  <li>建議</li>
+  <li>得以</li>
+  <li>可選擇</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<p>本小節提供您可採取的行動，來確認貢獻內容是否遵循本標準。如果您想要務實操作本標準，這部分很關鍵。</p>
+
+<p>我們已嘗試調整用字，讓即使是不熟悉這類主題內容的讀者，看完之後也能夠進行基本的遵循檢查。</p>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<p>本小節主要對象是政策制定者，列出他們的角色所能採取的具體行動。</p>
+
+<p>公共政策制定者設定專案的優先順序與目標，而在科技上的經驗可能沒那麼多。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<p>本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。</p>
+
+<p>管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源、提供適
+當的架構等，才能交付優良的服務。</p>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>本小節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。</p>
+
+<p>開發人員通常對技術比較在行，與其他角色類別相比，對服務交付的影響更大。</p>
+
+<h2 id="作用範圍限制">作用範圍限制</h2>
+
+<p>《公共程式標準》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。</p>
+
+<p>此外，雖然《公共程式標準》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，像是 ISO 25000
+認證系列，或是取代那些聚焦於安全性的標準，例如 <a href="https://github.com/coreinfrastructure/best-practices-badge">OpenSSF 最佳實務標
+章</a>等，而是希望能與它們能良好協同搭
+配。</p>
+
+<p>《公共程式標準》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到超越協作以外的企圖
+心。</p>
+
+  </article>
+</section>
+
+
+</main>
+
+
+<hr>
+
+<footer id="site-footer">
+  <!-- Release information -->
+  
+
+  <!-- GitHub repository information -->
+  
+    <section>
+      <h3>本站在 GitHub 的頁面</h3>
+      <p>本站最近一次是在 15 November 2023 根據 <a href="https://github.com/publiccodenet/jekyll-theme">publiccodenet/jekyll-theme</a> GitHub 的儲存庫版本發表。</p>
+
+      <form id="search-repository" action="https://github.com/publiccodenet/jekyll-theme/search" method="GET">
+        <input name="q" type="text" placeholder="搜尋 GitHub 的原始碼">
+        <button type="Submit"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill-rule="evenodd" d="M11.5 7a4.499 4.499 0 11-8.998 0A4.499 4.499 0 0111.5 7zm-.82 4.74a6 6 0 111.06-1.06l3.04 3.04a.75.75 0 11-1.06 1.06l-3.04-3.04z"></path></svg> 搜尋</button>
+      </form>
+
+    </section>
+  
+
+  <!-- License information -->
+  
+    <section>
+      <h3>著作權與授權</h3>
+      <p>
+        © 2023
+        
+        <a href="https://publiccode.net/">
+          公共程式基金會
+        </a>
+        
+      </p>
+      <p>
+        
+        
+        European Union Public License 1.2
+        
+      </p>
+    </section>
+  
+</footer>
+
+
+    <nav class="theme-nav">
+  <a href="https://publiccode.net/" title="Foundation for Public Code 首頁" class="logo-mark">
+    <img src="https://brand.publiccode.net/logo/mark.svg" alt="Foundation for Public Code 的標誌，看起來像是小間的希臘神廟，或是六角形的政府大樓">
+    <p>公共程式基金會</p>
+  </a>
+</nav>
+
+
+    
+<footer id="foundation-footer">
+
+  <div class="footer-trio">
+    <section>
+      <div class="footer-section-content">
+        <h2>關於我們</h2>
+        <p>本基金會人員資訊、決策規則與流程。本基金會的員工手冊，是與社群協作共同編寫，任何人都可再利用。</p>
+        <p>深入瞭解我們的活動、組織、術語詞彙表與觀念等。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://about.publiccode.net">我們的運作方式</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>專案資源</h2>
+        <p>為了推動本基金會使命而研究或開發的開放成品。我們每天的工作都依靠這些資源。您也可以喔！</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://projects.publiccode.net">請自由使用與修改</a>
+        <a href="https://github.com/publiccodenet">到 Github 查看我們的成品</a>
+      </div>
+    </section>
+    <section>
+      <div class="footer-section-content">
+        <h2>徵才</h2>
+        <p>呼叫熱心公益的開源人才！瞭解與我們共事的樣貌，並且成為我們的一員。</p>
+      </div>
+      <div class="footer-links">
+        <a href="https://publiccode.net/careers/">職缺</a>
+      </div>
+    </section>
+  </div>
+
+  <div class="footer-duo">
+    <section class="footer-contact">
+      <h2>聯絡方式</h2>
+      <dl>
+          <dt>電子報：</dt>
+          <dd><a href="https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842">加入我們的郵遞論壇清單</a></dd>
+
+          <dt>電話號碼：</dt>
+          <dd><a href="tel:+31202444500">+31 20 2 444 500</a></dd>
+
+          <dt>電子信箱：</dt>
+          <dd><a href="mailto:info@publiccode.net">info@publiccode.net</a></dd>
+
+          <dt>地址：</dt>
+          <dd><address>Keizersgracht 617, 1017 DS, Amsterdam, the Netherlands</address>
+          <a href="https://www.openstreetmap.org/node/2736377676" title="OpenStreetMap">OpenStreetMap</a> | <a href="https://www.google.com/maps/place/Keizersgracht+617,+1017+DS+Amsterdam,+Netherlands" title="Google 地圖">Google</a>
+          </dd>
+      </dl>
+    </section>
+
+    <section class="footer-notes">
+      <h2>機構資訊</h2>
+      <p>Foundation for Public Code（法人）<a href="https://about.publiccode.net/organization/governance-model.html" title="治理模型">是由其成員所有的協會</a>，且在<a href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=74996452" title="荷蘭商會註冊">荷蘭商會 (KvK)</a> 底下註冊，註冊編號為 74996452，識別碼為 (RSIN) 860102294。</p>
+      <p>荷蘭稅務與海關管理局視本機構為 <a href="https://www.belastingdienst.nl/wps/wcm/connect/bldcontenten/belastingdienst/business/business-public-benefit-organisations/public_benefit_organisations/what_is_pbo/what_is_a_pbo" title="公益組織 (ANBI)">公益組織 (ANBI)</a>。請參見 <a href="https://about.publiccode.net/organization/" title="本基金會 ANBI 資訊">請參見本基金會 ANBI 資訊</a>. </p>
+      <div class="footer-note-cluster"></div>
+        <p class="footer-last-updated">上次更新時間： 15 November 2023</p>
+        <p class="footer-copyright">2023 <a href="https://publiccode.net">Foundation for Public Code</a></p>
+        <p class="footer-license">本網站所有內容，皆以<a href="https://creativecommons.org/publicdomain/zero/1.0/" title="創用 CC0 1.0 通用授權" rel="license">創用 CC0 1.0 通用授權</a>, 通用之公眾領域貢獻宣告給予授權，另有說明者除外</p>
+        </div>
+    </section>
+  </div>
+
+</footer>
+
+
+
+  </body>
+
+</html>
diff --git a/_site/redirects.json b/_site/redirects.json
new file mode 100644
index 00000000..52eb296a
--- /dev/null
+++ b/_site/redirects.json
@@ -0,0 +1 @@
+{"/license.html":"/CC0-1.0.html","/LICENSE.html":"/CC0-1.0.html","/criteria/bundle-policy-and-code":"/criteria/bundle-policy-and-source-code.html","/criteria/advertise-maturity":"/criteria/document-codebase-maturity.html","/criteria/document-maturity":"/criteria/document-codebase-maturity.html","/criteria/document-objectives":"/criteria/document-codebase-objectives.html","/criteria/documenting":"/criteria/document-the-code.html","/introduction":"/foreword.html","/criteria/version-control-and-history":"/criteria/maintain-version-control.html","/criteria/findability":"/criteria/make-the-codebase-findable.html","/criteria/reusable-and-portable-codebases":"/criteria/make-the-codebase-reusable-and-portable.html","/criteria/create-reusable-and-portable-code":"/criteria/make-the-codebase-reusable-and-portable.html","/criteria/open-licenses":"/criteria/publish-with-an-open-license.html","/criteria/require-review":"/criteria/require-review-of-contributions.html","/criteria/style":"/criteria/use-a-coherent-style.html","/criteria/continuous-integration":"/criteria/use-continuous-integration.html","/criteria/open-standards":"/criteria/use-open-standards.html","/criteria/understandable-english-first":"/criteria/use-plain-english.html","/criteria/open-to-contributions":"/criteria/welcome-contributors.html"}
\ No newline at end of file
diff --git a/_site/robots.txt b/_site/robots.txt
new file mode 100644
index 00000000..e087884e
--- /dev/null
+++ b/_site/robots.txt
@@ -0,0 +1 @@
+Sitemap: /sitemap.xml
diff --git a/_site/script/check-new-links.sh b/_site/script/check-new-links.sh
new file mode 100755
index 00000000..6a9b1668
--- /dev/null
+++ b/_site/script/check-new-links.sh
@@ -0,0 +1,61 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that new links are valid. This script is intended to aid in that process.
+# Rather than checking all links with an incoming contribution, only the links
+# added by that contribution should be checked.
+
+NOT_OK_COUNT=0
+SKIP_PATTERNS=(
+	'github\.com/.*/edit' # links may not exist yet
+	'twitter\.com' # twitter is broken
+	'http://127.0.0.1' # local host
+	'http://localhost' # local host
+)
+
+if [ "_${VERBOSE}_" == "__" ]; then VERBOSE=0; fi
+
+for URL in $(git diff develop |
+		grep '^+' |
+		grep -Eo '(http|https)://[^ )"><]+'); do
+	SKIP_URL=0
+	for PATTERN in "${SKIP_PATTERNS[@]}"; do
+		if echo "$URL" | grep --quiet --extended-regexp "$PATTERN"
+		then
+			if [ $VERBOSE -gt 0 ]; then
+				echo "'$URL' matches '$PATTERN'"
+			fi
+			SKIP_URL=1
+		fi
+	done
+	if [ $SKIP_URL -eq 1 ]
+	then
+		if [ $VERBOSE -gt 0 ]; then
+			echo "(ignoring '$URL')"
+		fi
+	elif curl --fail --show-error --silent --head --location $URL \
+		> url_head 2>&1
+	then
+		if [ $VERBOSE -gt 0 ]
+		then
+			echo "$URL"
+			head -n1 url_head
+		fi
+	else
+		let "NOT_OK_COUNT+=1"
+		echo $URL
+		head -n1 url_head
+	fi
+	rm -f url_head
+done
+
+if [ $NOT_OK_COUNT -gt 0 ]; then
+	echo "FAIL: $NOT_OK_COUNT new URLs were not OK"
+	EXIT_FAILURE=1
+	exit $EXIT_FAILURE
+fi
diff --git a/_site/script/ensure-font.sh b/_site/script/ensure-font.sh
new file mode 100755
index 00000000..224beb14
--- /dev/null
+++ b/_site/script/ensure-font.sh
@@ -0,0 +1,29 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# halt on error
+set -e
+
+# On Ubuntu (and Debian-like systems), fc-cache is in the fontconfig package
+# sudo apt-get install -y fontconfig
+
+FONT_NAME=Mulish
+FONT_URL="https://fonts.google.com/download?family=$FONT_NAME"
+FONT_DIR="${HOME}/.local/share/fonts"
+FONT_ZIP="/tmp/${FONT_NAME}.zip"
+
+if grep "$FONT_NAME" <<< "$(fc-match $FONT_NAME)"; then
+	echo "$FONT_NAME is installed"
+	exit 0;
+fi
+echo "installing $FONT_NAME from $FONT_URL"
+
+rm -fv "$FONT_ZIP"
+curl --output "$FONT_ZIP" "$FONT_URL"
+mkdir -pv "$FONT_DIR"
+cd "$FONT_DIR"
+unzip -o -d . "$FONT_ZIP"
+rm -fv "$FONT_ZIP"
+fc-cache -fv
+fc-match "$FONT_NAME"
diff --git a/_site/script/find-missing-spdx.sh b/_site/script/find-missing-spdx.sh
new file mode 100755
index 00000000..fe443095
--- /dev/null
+++ b/_site/script/find-missing-spdx.sh
@@ -0,0 +1,26 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+function git_list_files() {
+		# -r Recurse into sub-trees.
+	git ls-tree \
+		--full-tree \
+		-r \
+		--name-only \
+		HEAD
+}
+
+IGNORE_PATTERN='\.svg\|\.json\|CNAME\|Gemfile\|LICENSE\|jargon.txt'
+
+MISSING=0
+for FILE in $(git_list_files | grep --invert-match $IGNORE_PATTERN); do
+	if ! grep --quiet SPDX-License-Identifier $FILE; then
+		MISSING=$(( 1 + $MISSING ))
+		echo $FILE
+	fi
+done
+
+if [ $MISSING -ne 0 ]; then
+	exit 1
+fi
diff --git a/_site/script/generate-checklist.sh b/_site/script/generate-checklist.sh
new file mode 100755
index 00000000..632e4aef
--- /dev/null
+++ b/_site/script/generate-checklist.sh
@@ -0,0 +1,94 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+TEMPLATE=docs/checklist.html
+THIS_YEAR=$(date +%Y)
+STANDARD_VERSION="${1}"
+cat << EOF > $TEMPLATE
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: $THIS_YEAR by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<head>
+<meta charset="UTF-8">
+<title>Standard for Public Code Checklist</title>
+<style>
+html, body {
+font-family: Mulish;
+font-size: 8.5pt;
+}
+h1, h2 {
+font-weight: normal;
+position: relative;
+}
+h1 {
+margin-top: 0;
+font-size: 0.5cm;
+border-bottom: none;
+}
+h2 {
+font-size: 1.0em;
+}
+ul {
+list-style-type: "\2610";
+}
+@media print {
+  @page {
+    size: 14.8cm 21.0cm;
+    margin: 0.5cm 0.2cm;
+  }
+}
+</style>
+</head>
+<body>
+<h1>Standard for Public Code version <span class="standard-version">${STANDARD_VERSION}</span> checklist</h1>
+EOF
+
+# grep criteria files for "order: ", results in entries like:
+#   criteria/document-the-code.md:order: 9
+# ignoring the index.md
+# swap name and order (extract the order number put it ahead of the file name)
+# sort numerically
+# take only the file name
+CRITERIA_FILES=$(grep '^order: ' criteria/*.md \
+	| grep --invert-match 'index.md' \
+	| sed 's@\(criteria/[a-z\-]*.md\):order:\s*\([0-9]*\).*@\2 \1@g' \
+	| sort --numeric-sort \
+	| cut --fields=2 --delimiter=' ')
+
+for FILE in $CRITERIA_FILES; do
+	# echo $FILE
+	FILE_BASE=$(basename --suffix=.md $FILE)
+	# Strip the '#' off of the H1
+	CRITERION_TITLE=$(grep '^# [A-Z]' $FILE \
+		| grep --invert-match 'SPDX' \
+		| cut --fields=2- --delimiter=' ')
+	CRITERION_LINK=https://standard.publiccode.net/criteria/${FILE_BASE}.html
+	cat << EOF >> $TEMPLATE
+
+<h2>&#9744; $CRITERION_TITLE</h2>
+
+<ul id="$FILE_BASE">
+EOF
+	# awk will process each line of file
+	# set 'p' to 1 if we are in the "## Requirements" section, or skip line
+	# set 's' to be all the words except the leading "*" of requirement
+	# if not a blank line, print 's' and the column pipe delimiters
+	awk 'BEGIN {p=0}; /## Requirements/ {p=1 ; next}; /##/ {p=0 ; next}; \
+		p { s = ""; for (i = 2; i <= NF; i++) s = s $i " "; \
+		if (length(s) > 0) print \
+		"<li>" s "</li>"}' \
+		$FILE >> $TEMPLATE
+	echo "</ul>" >> $TEMPLATE
+done
+echo "</body>" >> $TEMPLATE
+echo "</html>" >> $TEMPLATE
+
+# remove trailing spaces at end of line
+sed -i -e's/\s\+$//g' $TEMPLATE
+
+# remove markdown links
+sed -i -e's@\[\([^]]*\)\](\([^)]*\))@\1@g' $TEMPLATE
+
+ls -l $TEMPLATE
diff --git a/_site/script/generate-review-template.sh b/_site/script/generate-review-template.sh
new file mode 100755
index 00000000..05029e89
--- /dev/null
+++ b/_site/script/generate-review-template.sh
@@ -0,0 +1,119 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+TEMPLATE=docs/review-template.html
+THIS_YEAR=$(date +%Y)
+STANDARD_VERSION="${1}"
+cat << EOF > $TEMPLATE
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2022-$THIS_YEAR by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<head>
+<meta charset="UTF-8">
+<title>________ and the Standard for Public Code</title>
+<style>
+html, body {
+font-family: Mulish;
+font-size: 11pt;
+}
+h1, h2 {
+font-weight: normal;
+position: relative;
+}
+h1 {
+margin-top: 0;
+font-size: 1.5cm;
+border-bottom: none;
+}
+h2 {
+font-size: 1.5em;
+}
+@media print {
+a {
+color: #111;
+text-decoration: none;
+}
+th {
+font-weight: 600;
+}
+td {
+padding: 6px 13px;
+border: 1px solid #dfe2e5;
+}
+tr {
+background-color: #fff;
+border-top: 1px solid #c6cbd1;
+}
+tr:nth-child(2n) {
+background-color: #f6f8fa;
+}
+}
+</style>
+</head>
+<body>
+<h1>________ and the Standard for Public Code version <span class="standard-version">${STANDARD_VERSION}</span></h1>
+
+Link to commitment to meet the Standard for Public Code:
+EOF
+
+# grep criteria files for "order: ", results in entries like:
+#   criteria/document-the-code.md:order: 9
+# ignoring the index.md
+# swap name and order (extract the order number put it ahead of the file name)
+# sort numerically
+# take only the file name
+CRITERIA_FILES=$(grep '^order: ' criteria/*.md \
+	| grep --invert-match 'index.md' \
+	| sed 's@\(criteria/[a-z\-]*.md\):order:\s*\([0-9]*\).*@\2 \1@g' \
+	| sort --numeric-sort \
+	| cut --fields=2 --delimiter=' ')
+
+for FILE in $CRITERIA_FILES; do
+	# echo $FILE
+	FILE_BASE=$(basename --suffix=.md $FILE)
+	# Strip the '#' off of the H1
+	CRITERION_TITLE=$(grep '^# [A-Z]' $FILE \
+		| grep --invert-match 'SPDX' \
+		| cut --fields=2- --delimiter=' ')
+	CRITERION_LINK=https://standard.publiccode.net/criteria/${FILE_BASE}.html
+	cat << EOF >> $TEMPLATE
+
+<h2><a href="$CRITERION_LINK">$CRITERION_TITLE</a></h2>
+
+&#9744;<!-- &#9745; --> criterion met.
+
+<table id="$FILE_BASE" style="width:100%">
+<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
+EOF
+	# awk will process each line of file
+	# set 'p' to 1 if we are in the "## Requirements" section, or skip line
+	# set 's' to be all the words except the leading "*" of requirement
+	# if not a blank line, print 's' and the column pipe delimiters
+	awk 'BEGIN {p=0}; /## Requirements/ {p=1 ; next}; /##/ {p=0 ; next}; \
+		p { s = ""; for (i = 2; i <= NF; i++) s = s $i " "; \
+		if (length(s) > 0) print \
+		"<tr>\n<td>\n\n</td>\n<td>\n" \
+		s \
+		"\n</td>\n<td>\n\n</td>\n</tr>\n"}' \
+		$FILE >> $TEMPLATE
+	echo "</table>" >> $TEMPLATE
+done
+echo "</body>" >> $TEMPLATE
+echo "</html>" >> $TEMPLATE
+
+# remove trailing spaces at end of line
+sed -i -e's/\s\+$//g' $TEMPLATE
+
+# unlink glossary local links in requirement lines
+sed -i -e's@\[\([^]]*\)\](../glossary.md\(#[a-z\-]*\))@\1@g' $TEMPLATE
+
+# fully qualify local criteria links in requirement lines
+# by looking for links lacking a colon
+sed -i -e's@\[\([^]]*\)\](\([^:)]*\).md)@[\1](https://standard.publiccode.net/criteria/\2.html)@g' $TEMPLATE
+
+# convert markdown links to html links
+sed -i -e's@\[\([^]]*\)\](\([^)]*\))@<a href="\2">\1</a>@g' $TEMPLATE
+
+ls -l $TEMPLATE
diff --git a/_site/script/make-version-badge.sh b/_site/script/make-version-badge.sh
new file mode 100755
index 00000000..91b0cd97
--- /dev/null
+++ b/_site/script/make-version-badge.sh
@@ -0,0 +1,61 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net>
+
+# $ help set | grep "\-e"
+#      -e  Exit immediately if a command exits with a non-zero status.
+set -e
+
+if [ "_${VERBOSE}_" == "__" ]; then VERBOSE=0; fi
+if [ $VERBOSE -gt 0 ]; then
+# $ help set | grep "\-x"
+#      -x  Print commands and their arguments as they are executed.
+	set -x
+fi
+
+VERSION=${1}
+if [ "_${VERSION}_" == "__" ]; then
+	echo "must supply a version"
+	exit 1
+fi
+
+BADGE_LABEL="version"
+BADGE_TEXT="$VERSION"
+BADGE_COLOR_NAME="yellow"
+BADGE_COLOR_CODE=":yellow"
+# BADGE_PATH=assets/${BADGE_LABEL}-${BADGE_TEXT}-${BADGE_COLOR_NAME}.svg
+BADGE_PATH=assets/version-badge.svg
+
+
+if ! [ -e ./node_modules/.bin/badge ]; then
+	npm install
+fi
+ls -l ./node_modules/.bin/badge
+
+rm -f $BADGE_PATH
+cat > ${BADGE_PATH}.head.svg <<EOF
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net> -->
+<!-- version-badge.svg ${VERSION} ${BADGE_COLOR_NAME} -->
+EOF
+
+# create the body
+./node_modules/.bin/badge \
+	"${BADGE_LABEL}" \
+	"${BADGE_TEXT}" \
+	"${BADGE_COLOR_CODE}" \
+	flat \
+	> ${BADGE_PATH}.body.svg
+
+# combine the unformatted contents
+cat	${BADGE_PATH}.head.svg \
+	${BADGE_PATH}.body.svg \
+	> ${BADGE_PATH}.tmp.svg
+
+# format for final output
+xmllint --format ${BADGE_PATH}.tmp.svg \
+	--output ${BADGE_PATH}
+
+rm ${BADGE_PATH}.{tmp,head,body}.svg
+ls -l ${BADGE_PATH}
diff --git a/_site/script/missing-glossary-links.sh b/_site/script/missing-glossary-links.sh
new file mode 100755
index 00000000..72740ab3
--- /dev/null
+++ b/_site/script/missing-glossary-links.sh
@@ -0,0 +1,101 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script extracts the glossary terms from glossary.md
+# for each file in the criteria directory, it looks for the use of a term
+# if the term is found, it checks to see if a link exists
+# if no link is found, it prints the TODO list
+
+if [ "_${VERBOSE}_" == "__" ]; then
+	VERBOSE=0
+fi
+
+if [ $VERBOSE -gt 1 ]; then
+	set -x
+fi
+
+MISSING=0;
+
+# grep for heading in glossary
+# strip the hashes off
+# strip off the leading space
+# convert space to hyphen
+# transform upper case to lower case
+GLOSSARY_ANCHORS=$( grep '## ' glossary.md \
+	| cut -f3- -d"#" \
+	| sed -e 's/^ //g' \
+	| sed -e 's/ /-/g' \
+	| tr A-Z a-z )
+
+function glossary_pass_list() {
+	GLOSSARY_ANCHOR=$1
+	FILE=$2
+
+	# "version control" correctly links to the criterion
+	# rather than the glossary entry
+	if [ "$GLOSSARY_ANCHOR" == "version-control" ] &&
+	   [ "$FILE" == "criteria/bundle-policy-and-source-code.md" ]; then
+		return 0
+	fi
+	if [ "$GLOSSARY_ANCHOR" == "version-control" ] &&
+	   [ "$FILE" == "criteria/use-continuous-integration.md" ]; then
+		return 0
+	fi
+
+	# "Open Source Initiative" would be a false positive
+	if [ "$GLOSSARY_ANCHOR" == "open-source" ] &&
+	   [ "$FILE" == "criteria/use-open-standards.md" ]; then
+		return 0
+	fi
+
+	# repository inside of a link would be a false positive
+	if [ "$GLOSSARY_ANCHOR" == "repository" ] &&
+	   [ "$FILE" == "criteria/require-review-of-contributions.md" ]; then
+		return 0
+	fi
+
+	# link to "bundle policy and source code" is a false positive
+	if [ "$GLOSSARY_ANCHOR" == "source-code" ] &&
+	   [ "$FILE" == "criteria/document-codebase-objectives.md" ]; then
+		return 0
+	fi
+
+	return 1
+}
+
+for GLOSSARY_ANCHOR in $GLOSSARY_ANCHORS; do
+	GLOSSARY_TERM=$(echo $GLOSSARY_ANCHOR | sed -e 's/-/ /g')
+
+	if [ $VERBOSE -gt 0 ]; then
+		echo GLOSSARY_ANCHOR: $GLOSSARY_ANCHOR
+		echo GLOSSARY_TERM:   $GLOSSARY_TERM
+	fi
+	if [ "_${GLOSSARY_TERM}_" == "_public code_" ]; then
+		GLOSSARY_TERM='Public code\|public code'
+		GREP="grep -lr"
+	else
+		GLOSSARY_TERM="$GLOSSARY_TERM"
+		#case insensitive
+		GREP="grep -ilr"
+	fi
+	for FILE in $( $GREP "$GLOSSARY_TERM" criteria/ | grep -v index); do
+		if glossary_pass_list "$GLOSSARY_ANCHOR" "$FILE"; then
+			continue
+		fi
+
+		if grep -q "glossary.md\#$GLOSSARY_ANCHOR" $FILE; then
+			if [ $VERBOSE -gt 0 ]; then
+				echo Found link $GLOSSARY_ANCHOR $FILE
+			fi
+		else
+			MISSING=$(( $MISSING + 1 ))
+			echo to-do: $GLOSSARY_ANCHOR $FILE
+		fi
+	done
+done
+
+if [ $MISSING -gt 0 ]; then
+	echo Missing $MISSING links
+	exit 1
+fi
diff --git a/_site/script/pdf.sh b/_site/script/pdf.sh
new file mode 100755
index 00000000..0d9925cf
--- /dev/null
+++ b/_site/script/pdf.sh
@@ -0,0 +1,160 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is used to generate a PDF from the html generated by Jekyll.
+# This script is used during the release process (see ../docs/releasing.md)
+
+if [ "_${1}_" == "__" ]; then
+	echo "must specify a VERSION"
+	exit 1
+fi
+VERSION="${1}"
+
+function weasyprint_version() {
+	weasyprint --version \
+		| sed -e's/[^0-9]*\([0-9\.]*\).*/\1/'
+}
+
+function temp_weasyprint_info() {
+	if [ $TMP_WEASYPRINT -gt 0 ]; then
+		WEASY_PRINT_VER=$(weasyprint_version)
+		echo "================================================="
+		echo "temp WeasyPrint installed, version $WEASY_PRINT_VER"
+		echo "to use this version outside of this script,"
+		echo "type the following command:"
+		echo
+		echo "$ source /tmp/weasyprint/venv/bin/activate"
+		echo "================================================="
+	fi
+}
+
+function ensure_good_weasyprint () {
+	WEASY_PRINT_VER=$(weasyprint_version)
+	echo "WEASY_PRINT_VER='$WEASY_PRINT_VER'"
+
+	if [ "_${WEASY_PRINT_VER}_" != "__" ]; then
+		WP_MAJOR_VERSION=$(echo "${WEASY_PRINT_VER}" | cut -f1 -d'.')
+		WP_MINOR_VERSION=$(echo "${WEASY_PRINT_VER}" | cut -f2 -d'.')
+	else
+		WP_MAJOR_VERSION=0
+		WP_MINOR_VERSION=0
+	fi
+
+	if [ "$WP_MAJOR_VERSION" -lt 57 ]; then
+		echo "WeasyPrint version: $WEASY_PRINT_VER less than 57"
+	        echo "installing new weasyprint"
+		pushd /tmp
+		rm -rf weasyprint
+		git clone https://github.com/Kozea/WeasyPrint.git weasyprint
+		cd weasyprint
+		python3 -m venv venv
+	        source venv/bin/activate
+	        pip install weasyprint
+		TMP_WEASYPRINT=1
+		echo
+		temp_weasyprint_info
+		echo
+		popd
+	fi
+	if [ "_${TMP_WEASYPRINT}_" == "__" ]; then
+		TMP_WEASYPRINT=0
+	fi
+}
+ensure_good_weasyprint
+
+JEKYLL_PDF_PORT=9000
+JEKYLL_PDF_DIR=_build_pdf
+rm -rf $JEKYLL_PDF_DIR
+
+PAGES_REPO_NWO=publiccodenet/standard \
+	bundle exec jekyll serve \
+		--port=$JEKYLL_PDF_PORT \
+		--destination=$JEKYLL_PDF_DIR &
+JEKYLL_PID=$!
+function cleanup() {
+	echo "Killing JEKYLL_PID: $JEKYLL_PID"
+	kill $JEKYLL_PID
+}
+trap cleanup EXIT # stop the jekyll serve
+
+MAX_LOOPS=100
+LOOPS=0
+while ! curl "http://localhost:$JEKYLL_PDF_PORT" >/dev/null 2>&1 ; do
+	LOOPS=$(( $LOOPS + 1 ));
+	echo "try $LOOPS, waiting to connect ..."
+	sleep 1;
+	if [ $LOOPS -gt $MAX_LOOPS ]; then
+		echo "exceeds MAX_LOOPS";
+		exit 1;
+	fi
+done
+
+# give it one more second
+sleep 1;
+
+echo
+weasyprint --presentational-hints \
+	"http://localhost:$JEKYLL_PDF_PORT/standard-print.html" \
+	standard-for-public-code-$VERSION.pdf
+ls -l	standard-for-public-code-$VERSION.pdf
+
+echo
+weasyprint --presentational-hints \
+	"http://localhost:$JEKYLL_PDF_PORT/foreword-print.html" \
+	standard-for-public-code-foreword-$VERSION.pdf
+ls -l	standard-for-public-code-foreword-$VERSION.pdf
+
+echo
+weasyprint --presentational-hints \
+	"http://localhost:$JEKYLL_PDF_PORT/print-cover.html" \
+	standard-cover-$VERSION.pdf
+ls -l	standard-cover-$VERSION.pdf
+
+echo
+weasyprint --presentational-hints \
+	"http://localhost:$JEKYLL_PDF_PORT/docs/review-template.html" \
+	standard-review-template-$VERSION.pdf
+ls -l	standard-review-template-$VERSION.pdf
+
+echo
+weasyprint --presentational-hints \
+	"http://localhost:$JEKYLL_PDF_PORT/docs/checklist.html" \
+	standard-checklist-$VERSION.pdf
+ls -l	standard-checklist-$VERSION.pdf
+
+echo
+if ! pandoc --version ; then
+	echo "'pandoc' not installed, skipping .epub version"
+	echo "'pandoc' should be available from the package manager, e.g.:"
+	echo
+	echo "        sudo apt install -y pandoc"
+	echo
+else
+	pandoc $JEKYLL_PDF_DIR/standard-print.html \
+		-o standard-for-public-code-$VERSION.epub
+	ls -l standard-for-public-code-$VERSION.epub
+fi
+
+echo
+if ! qpdf --version ; then
+	echo "'qpdf' not installed, skipping combined-for-print version"
+	echo "'qpdf' should be available from the package manager, e.g.:"
+	echo
+	echo "        sudo apt install -y qpdf"
+	echo
+else
+	qpdf --empty --pages \
+		standard-for-public-code-foreword-$VERSION.pdf \
+		standard-for-public-code-$VERSION.pdf \
+		-- \
+		standard-for-public-code-print-$VERSION.pdf
+	ls -l standard-for-public-code-print-$VERSION.pdf
+fi
+
+echo
+temp_weasyprint_info
+
+ls -l *.pdf *.epub
+
+echo "done"
diff --git a/_site/script/release-body.sh b/_site/script/release-body.sh
new file mode 100755
index 00000000..596b426b
--- /dev/null
+++ b/_site/script/release-body.sh
@@ -0,0 +1,36 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>
+
+# Create a 'release.body' file for the text describing a release
+
+if [ "_${VERBOSE}_" != "__" ] && [ "$VERBOSE" -gt 0 ]; then
+	set -x
+fi
+
+CODEBASE_NAME="Standard for Public Code"
+VERSION=$1
+if [ "_${VERSION}_" == "__" ]; then
+        echo "No version?"
+        exit 1
+fi
+echo "# $CODEBASE_NAME version $VERSION" > release.body
+
+# strip the trailing version info if exists, e.g: '1.2.3-rc2' becomes '1.2.3'
+BASE_VERSION=$( echo "$VERSION" | sed 's/^\([0-9]*\.[0-9]*\.[0-9]*\).*/\1/' )
+
+# pull out the top of the CHANGELOG
+START=$( grep "##" CHANGELOG.md | head -n1 )
+
+# if the first CHANGELOG entry (START) does not match the BASE_VERSION,
+# then print error and exit
+if ! grep -q "$BASE_VERSION" <<< "$START"; then
+	echo "Start of CHANGELOG.md does not match $BASE_VERSION"
+	exit 1
+fi
+
+#  add BASE_VERSION notes to release.body
+NEXT=$( grep '##' CHANGELOG.md | head -n2 | tail -n1 )
+sed -n "/$START/,/$NEXT/p" CHANGELOG.md \
+	| grep -v '^##' \
+	>> release.body
diff --git a/_site/script/serve.sh b/_site/script/serve.sh
new file mode 100755
index 00000000..49fff946
--- /dev/null
+++ b/_site/script/serve.sh
@@ -0,0 +1,15 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# The serve.sh script can be used to preview how Jekyll will build the site.
+# See also: pdf.sh
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+bundle exec jekyll serve --livereload
diff --git a/_site/script/spell-check.sh b/_site/script/spell-check.sh
new file mode 100755
index 00000000..bd841a4e
--- /dev/null
+++ b/_site/script/spell-check.sh
@@ -0,0 +1,44 @@
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net>
+
+# help set
+#       -e  Exit immediately if a command exits with a non-zero status.
+#       -x  Print commands and their arguments as they are executed.
+if [ "_${VERBOSE}_" != "__" ] && [ "${VERBOSE}" -gt 0 ]; then
+	set -x
+fi
+set -e
+
+
+function git_list_files() {
+		# -r Recurse into sub-trees.
+	git ls-tree \
+		--full-tree \
+		-r \
+		--name-only \
+		HEAD
+}
+
+IGNORE_PATTERN='\.css$\|\.svg$\|\.json$\|CNAME$\|Gemfile$\|LICENSE$\|\.sh$\|\.gitignore$\|.github.*\|jargon.txt$'
+
+ERRORS=0
+for FILE in $(git_list_files | grep --invert-match $IGNORE_PATTERN); do
+	name=$(basename -- "$FILE")
+	extension="${name##*.}"
+
+	if [ "$extension" == "html" ]; then
+		MODE=--mode=html
+	elif [ "$extension" == "md" ]; then
+		MODE=--mode=markdown
+	fi
+	WORDS=$( aspell $MODE --master=en \
+		--home-dir=.  --personal=jargon.txt \
+		list < $FILE )
+	if [ $(echo "$WORDS" | wc -w) -gt 0 ]; then
+		echo "FAIL: $FILE spell check: $WORDS"
+		ERRORS=$(( $ERRORS + 1 ))
+	fi
+done
+if [ $ERRORS -gt 0 ]; then
+	exit 1
+fi
diff --git a/_site/script/test-all.sh b/_site/script/test-all.sh
new file mode 100755
index 00000000..57dbedc2
--- /dev/null
+++ b/_site/script/test-all.sh
@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is provided for local development,
+# it is not used by continuous integration
+
+# $ help set
+#      -e  Exit immediately if a command exits with a non-zero status.
+#      -x  Print commands and their arguments as they are executed.
+set -x
+set -e
+
+./script/find-missing-spdx.sh
+./script/test-markdown.sh
+./script/spell-check.sh
+./script/missing-glossary-links.sh
+./script/check-new-links.sh
+./script/test-without-link-check.sh
+./script/test-with-link-check.sh
diff --git a/_site/script/test-markdown.sh b/_site/script/test-markdown.sh
new file mode 100755
index 00000000..eeaec428
--- /dev/null
+++ b/_site/script/test-markdown.sh
@@ -0,0 +1,13 @@
+#!/bin/sh
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that new Markdown is valid and conforms to the repository guidelines. This
+# script is intended to aid in that process.
+
+# Lint markdown using the rules loaded with .mdlrc, .mdl_style.rb
+bundle exec mdl -i -g '.'
diff --git a/_site/script/test-with-link-check.sh b/_site/script/test-with-link-check.sh
new file mode 100755
index 00000000..f94b36e7
--- /dev/null
+++ b/_site/script/test-with-link-check.sh
@@ -0,0 +1,60 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is referenced by .github/workflows/link-check.yml which
+# executes daily.
+
+# Failures reported by this script are addressed on a case-by-case basis.
+
+set -e # halt script on error
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+# Build the site
+bundle exec jekyll build
+
+# bundle exec htmlproofer --help | grep url-ignore
+#  --url-ignore link1,[link2,...]  A comma-separated list of
+#    Strings or RegExps containing URLs that are safe to ignore.
+# * github.com/foo/edit/ : may reference yet-to-exist pages
+# * docs.github.com/en : blocked by github DDoS protection
+# * plausible.io/js/plausible.js : does not serve to scripts
+# * opensource.org : gives "failed: 503 No error" when run as GitHub workflow
+# * belastingdienst.nl/wps/wcm/connect/bldcontenten : regular timeouts
+# * reclameland.nl : often "failed: 403 No error" when run as GitHub workflow
+# * www.dta.gov.au : often "failed: 403 No error" when run as GitHub workflow
+# * 127.0.0.1 : localhost does not need to be checked
+# * twitter.com : failed: 302 Number of redirects hit maximum amount
+#
+URL_IGNORE_REGEXES="\
+/github\.com\/.*\/edit\//\
+,/docs\.github\.com\/en\//\
+,/plausible\.io\/js\/plausible\.js/\
+,/opensource\.org/\
+,/belastingdienst\.nl\/wps\/wcm\/connect\/bldcontenten/\
+,/reclameland\.nl\/drukken\/softcover-boeken/\
+,/www\.dta\.gov\.au\/help-and-advice/\
+,/127\.0\.0\.1:/\
+,/twitter\.com\//\
+,/amsterdam\.nl\/en\//\
+"
+
+# ignore request rate limit errors (HTTP 429)
+# --http_status_ignore "429" \
+
+# Check for broken links and missing alt tags:
+# jekyll does not require extensions like HTML
+# ignoring problem urls (see above)
+# set an extra long timout for test-servers with poor connectivity
+# using the files in Jekylls build folder
+bundle exec htmlproofer \
+    --assume-extension \
+    --url-ignore $URL_IGNORE_REGEXES \
+    --typhoeus-config '{"timeout":60,"ssl_verifypeer":false,"ssl_verifyhost":"0"}' \
+    ./_site
diff --git a/_site/script/test-without-link-check.sh b/_site/script/test-without-link-check.sh
new file mode 100755
index 00000000..32d2277a
--- /dev/null
+++ b/_site/script/test-without-link-check.sh
@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS
+
+# This script is referenced by .github/workflows/test.yml which executes on
+# each pull request.
+
+# As part of reviewing a contribution, reviewers are responsible for checking
+# that html is valid and conforms to the repository guidelines. This script is
+# intended to aid in that process.
+
+set -e # halt script on error
+
+# if PAGES_REPO_NWO is not set then default to publiccodenet/standard
+# (jekyll defaults to "origin" if a remote of that name exists,
+# which makes sense for a true fork, but not for most contributors)
+if [ "_${PAGES_REPO_NWO}_" == "__" ]; then
+export PAGES_REPO_NWO=publiccodenet/standard
+fi
+
+# Build the site
+bundle exec jekyll build
+
+# Check for broken links and missing alt tags:
+# jekyll does not require extentions like HTML
+# run only "ScriptCheck" and "ImageCheck"; skip "LinkCheck"
+# set an extra long timout for test-servers with poor connectivity
+# ignore request rate limit errors (HTTP 429)
+# using the files in Jekylls build folder
+bundle exec htmlproofer \
+    --assume-extension \
+    --disable-external \
+    ./_site
diff --git a/_site/script/to-archive-org.sh b/_site/script/to-archive-org.sh
new file mode 100755
index 00000000..55c0f6eb
--- /dev/null
+++ b/_site/script/to-archive-org.sh
@@ -0,0 +1,84 @@
+#!/bin/bash
+# SPDX-License-Identifier: LGPL-2.1-or-later
+# to-archive-org.sh : send referenced URLs to the wayback machine
+# Copyright (C) 2020 Eric Herman <eric@freesa.org>
+
+# TODO FIXXXME: use something better than bash
+
+if [ "_${ARCHIVER_LOG_FILE}_" == "__" ]; then
+	NOW=$(date --utc +%Y%m%dT%H%M%SZ)
+	ARCHIVER_LOG_FILE=/tmp/to-archive-org.sh.${NOW}.log
+fi
+echo "ARCHIVER_LOG_FILE=$ARCHIVER_LOG_FILE"
+
+if [ "_${ARCHIVER_USER_AGENT}_" == "__" ]; then
+	GIT_USER_NAME=$(git config --get user.name)
+	GIT_USER_EMAIL=$(git config --get user.email)
+	RUN_BY="$GIT_USER_NAME ( $GIT_USER_EMAIL )"
+	REMOTE=$(git remote -v | head -n1 | cut -f1 -d$'\t')
+	REPO_URL=$(git config --get remote.${REMOTE}.url)
+	ARCHIVER_USER_AGENT="'url-archiver run by $RUN_BY for $REPO_URL'"
+fi
+echo "ARCHIVER_USER_AGENT=$ARCHIVER_USER_AGENT"
+
+rm -f urls.txt
+
+# find . -type f -name '*.md' -print0 |
+# while IFS= read -r -d '' FILE; do
+
+BRANCH_NAME=$(git branch | grep \* | cut -d ' ' -f2)
+for FILE in $(git ls-tree -r --name-only $BRANCH_NAME); do
+	# URLs inside parens
+	grep '(http[s]\?:' "$FILE" \
+		| sed -e's/.*[(]\(http[s]*:[^)]*\).*/\1/' \
+		>> urls.txt
+	# URLs inside angle brackets
+	grep '<http[s]\?:' "$FILE" \
+		| sed -e's/.*<\(http[s]*:[^>]*\).*/\1/' \
+		>> urls.txt
+	# URLs inside double-quotes
+	grep '"http[s]\?:' "$FILE" \
+		| sed -e's/.*"\(http[s]*:[^"]*\).*/\1/' \
+		>> urls.txt
+done
+
+# create a list of unique URLs, excluding archive.org and localhost
+cat urls.txt \
+	| cut -f1 -d'#' \
+	| grep -v '^http[s]\?://web.archive.org' \
+	| grep -v '^http[s]\?://localhost' \
+	| grep -v '^http[s]\?://127.0.0.1' \
+	| sort -u \
+	> urls-sorted.txt
+
+URLS_TOTAL=$(wc -l urls-sorted.txt | cut -f1 -d' ')
+
+# cat urls-sorted.txt
+
+MAX_PER_MINUTE=5
+echo "sending $URLS_TOTAL URLs to the wayback machine,"
+echo "        throttled to $MAX_PER_MINUTE per minute..."
+PAUSE_TIME=$(( 1 + (60 / $MAX_PER_MINUTE) ))
+URLS_COUNT=0
+for URL in $(cat urls-sorted.txt); do
+	echo sleeping for $PAUSE_TIME ....
+	sleep $PAUSE_TIME
+	# $ sudo apt-get install gridsite-clients
+	ENCODED=`urlencode $URL`
+	echo ""
+	URLS_COUNT=$(( $URLS_COUNT + 1 ))
+	echo "$URLS_COUNT of $URLS_TOTAL"
+	echo URL: $URL
+	echo encoded: $ENCODED
+
+	echo "" >> $ARCHIVER_LOG_FILE
+	echo "----------" >> $ARCHIVER_LOG_FILE
+	echo $URL >> $ARCHIVER_LOG_FILE
+	ARC_ORG_URL=https://web.archive.org/save/$ENCODED
+	echo $ARC_ORG_URL >> $ARCHIVER_LOG_FILE
+	curl --user-agent "$ARCHIVER_USER_AGENT" \
+		$ARC_ORG_URL >> $ARCHIVER_LOG_FILE
+	echo "" >> $ARCHIVER_LOG_FILE
+	echo "----------" >> $ARCHIVER_LOG_FILE
+done
+echo "done"
diff --git a/_site/script/update-changelog-date.sh b/_site/script/update-changelog-date.sh
new file mode 100755
index 00000000..828214f0
--- /dev/null
+++ b/_site/script/update-changelog-date.sh
@@ -0,0 +1,46 @@
+#!/bin/bash
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <info@publiccode.net>
+
+# help set | grep '\-e\|\-o'
+# -e  Exit immediately if a command exits with a non-zero status
+# -o option-name
+# help set | grep -A2 pipefail
+#              pipefail     the return value of a pipeline is the status of
+#                           the last command to exit with a non-zero status,
+#                           or zero if no command exited with a non-zero status
+set -e
+set -o pipefail
+
+function num_suffix() {
+	case "$1" in
+		# teens or numbers ending something other than 1,2,3
+		*1[0-9]|*[04-9])
+			echo "$1"th
+		;;
+		# non-teen numbers ending in 1
+		*1)
+			echo "$1"st
+		;;
+		# non-teen numbers ending in 2
+		*2)
+			echo "$1"nd
+		;;
+		# non-teen numbers ending in 3
+		*3)
+			echo "$1"rd
+		;;
+	esac
+}
+
+# The date(1) command uses the locale,
+# so we set it to C which is always installed
+# and is the same as US English in this particular case.
+# The formats %e %B %Y are documented in the man page:
+# https://www.man7.org/linux/man-pages/man1/date.1.html
+
+TODAYS_DOM=$(LC_ALL=C date +'%e')
+TODAYS_DOM_WITH_SUFFIX=$(num_suffix $TODAYS_DOM)
+TODAYS_DATE=$(LC_ALL=C date +"%B $TODAYS_DOM_WITH_SUFFIX %Y")
+
+sed -i -e"s/DATE-OF-RELEASE:/${TODAYS_DATE}:/" CHANGELOG.md
diff --git a/_site/sitemap.xml b/_site/sitemap.xml
new file mode 100644
index 00000000..db8a39d5
--- /dev/null
+++ b/_site/sitemap.xml
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+<url>
+<loc>/AUTHORS.html</loc>
+</url>
+<url>
+<loc>/CC0-1.0.html</loc>
+</url>
+<url>
+<loc>/CHANGELOG.html</loc>
+</url>
+<url>
+<loc>/GOVERNANCE.html</loc>
+</url>
+<url>
+<loc>/criteria/bundle-policy-and-source-code.html</loc>
+</url>
+<url>
+<loc>/criteria/code-in-the-open.html</loc>
+</url>
+<url>
+<loc>/criteria/document-codebase-maturity.html</loc>
+</url>
+<url>
+<loc>/criteria/document-codebase-objectives.html</loc>
+</url>
+<url>
+<loc>/criteria/document-the-code.html</loc>
+</url>
+<url>
+<loc>/foreword-print.html</loc>
+</url>
+<url>
+<loc>/foreword.html</loc>
+</url>
+<url>
+<loc>/glossary.html</loc>
+</url>
+<url>
+<loc>/criteria/</loc>
+</url>
+<url>
+<loc>/</loc>
+</url>
+<url>
+<loc>/criteria/maintain-version-control.html</loc>
+</url>
+<url>
+<loc>/criteria/make-contributing-easy.html</loc>
+</url>
+<url>
+<loc>/criteria/make-the-codebase-findable.html</loc>
+</url>
+<url>
+<loc>/criteria/make-the-codebase-reusable-and-portable.html</loc>
+</url>
+<url>
+<loc>/print-cover.html</loc>
+</url>
+<url>
+<loc>/criteria/publish-with-an-open-license.html</loc>
+</url>
+<url>
+<loc>/readers-guide.html</loc>
+</url>
+<url>
+<loc>/criteria/require-review-of-contributions.html</loc>
+</url>
+<url>
+<loc>/standard-print.html</loc>
+</url>
+<url>
+<loc>/criteria/use-a-coherent-style.html</loc>
+</url>
+<url>
+<loc>/criteria/use-continuous-integration.html</loc>
+</url>
+<url>
+<loc>/criteria/use-open-standards.html</loc>
+</url>
+<url>
+<loc>/criteria/use-plain-english.html</loc>
+</url>
+<url>
+<loc>/criteria/welcome-contributors.html</loc>
+</url>
+<url>
+<loc>/CODE_OF_CONDUCT.html</loc>
+</url>
+<url>
+<loc>/CONTRIBUTING.html</loc>
+</url>
+<url>
+<loc>/README.html</loc>
+</url>
+<url>
+<loc>/docs/printing.html</loc>
+</url>
+<url>
+<loc>/docs/releasing.html</loc>
+</url>
+<url>
+<loc>/docs/roadmap.html</loc>
+</url>
+<url>
+<loc>/docs/checklist.html</loc>
+<lastmod>2023-08-30T05:59:51+00:00</lastmod>
+</url>
+<url>
+<loc>/docs/review-template.html</loc>
+<lastmod>2023-08-30T05:59:51+00:00</lastmod>
+</url>
+<url>
+<loc>/docs/standard-for-public-code.html</loc>
+<lastmod>2023-08-30T05:59:51+00:00</lastmod>
+</url>
+</urlset>
diff --git a/_site/standard-print.html b/_site/standard-print.html
new file mode 100644
index 00000000..0bdd24ce
--- /dev/null
+++ b/_site/standard-print.html
@@ -0,0 +1,2078 @@
+<!DOCTYPE html>
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="ie=edge">
+  <link rel="stylesheet" href="assets/github-markdown.css">
+  <link rel="stylesheet" href="assets/print.css">
+  <title>Standard for Public Code</title>
+  <style>
+    /* Print specific */
+    @media print {
+      @page :left {
+        @top-left {
+          content: counter(page);
+        }
+      }
+      @page :right {
+        @top-right {
+          content: counter(page);
+        }
+      }
+    }
+  </style>
+</head>
+<body class="markdown-body">
+
+  <article id="section-first-page">
+    <p>Request for contributions</p>
+    <h1 class="title">Standard for Public Code</h1>
+
+    <ul class="first-page-audiences">
+      <lh>What public code is and how to implement it for:</lh>
+      <li id="first-page-public-policy-makers-what-you-need-to-do">Public policy makers</li>
+      <li id="first-page-managers-what-you-need-to-do">Managers</li>
+      <li id="first-page-developers-and-designers-what-you-need-to-do">Developers and designers</li>
+    </ul>
+
+    <img src="assets/hands-shake.svg" alt="hands shaking">
+
+    <p><strong>Draft</strong><br/>Version <span class="standard-version">0.7.1</span></p>
+    <p><img src="/assets/cc-zero-badge.svg" alt="Licensed CC0" height="46"> <img src="/assets/dpg-badge.svg" alt="Digital Public Goods approval badge" width="92" height="46"></p>
+    <p>github.com/publiccodenet/standard</p>
+  </article>
+
+  <article id="section-authors">
+
+    <h1 id="作者群">作者群</h1>
+
+<ul>
+  <li>Alba Roza，<a href="https://publiccode.net/">Foundation for Public Code</a></li>
+  <li>Arnout Engelen</li>
+  <li>Arnout Schuijff，Foundation for Public Code</li>
+  <li>唐鳳，<a href="https://digitalminister.tw/">數位發展部</a></li>
+  <li>Ben Cerveny，Foundation for Public Code</li>
+  <li>Bert Spaan</li>
+  <li>Boris van Hoytema，Foundation for Public Code</li>
+  <li>Charlotte Heikendorf</li>
+  <li>Claus Mullie，Foundation for Public Code</li>
+  <li>David Barberi</li>
+  <li>Edo Plantinga，<a href="https://codefor.nl/">Code For NL</a></li>
+  <li>Elena Findley-de Regt，Foundation for Public Code</li>
+  <li>Eric Herman，Foundation for Public Code</li>
+  <li>Felix Faassen，Foundation for Public Code</li>
+  <li>Floris Deerenberg</li>
+  <li>Jan Ainali，Foundation for Public Code</li>
+  <li>Johan Groenen，Code For NL</li>
+  <li>Marcus Klaas de Vries</li>
+  <li>Mark van der Net，<a href="https://www.amsterdam.nl/en/">阿姆斯特丹市政府</a></li>
+  <li>Martijn de Waal，<a href="https://www.amsterdamuas.com/">阿姆斯特丹應用科技大學 (AUAS)</a>，數位媒體與創意產業學院，
+戲劇與公民媒體系講師</li>
+  <li>Matti Schneider</li>
+  <li>Mauko Quiroga</li>
+  <li>Maurice Hendriks， 阿姆斯特丹市政府</li>
+  <li>Maurits van der Schee，阿姆斯特丹市政府</li>
+  <li>Mirjam van Tiel，Foundation for Public Code</li>
+  <li>Ngô Ngọc Đức Huy</li>
+  <li>Paul Keller</li>
+  <li>Petteri Kivimäki， <a href="https://niis.org">北歐互通性解決方案機構 (NIIS)</a></li>
+  <li>Sky Bristol</li>
+  <li>Tamas Erkelens，阿姆斯特丹市政府</li>
+  <li>Timo Slinger</li>
+</ul>
+
+
+  </article>
+
+  <article id="table-of-contents">
+
+    <h1>Table of Contents</h1>
+
+    <ol>
+      <li><a href="#section-authors" class="table-of-contents">Authors</a></li>
+      <li><a href="#section-readers-guide" class="table-of-contents">Readers guide</a></li>
+      <li><a href="#section-glossary" class="table-of-contents">Glossary</a></li>
+      <li><a href="#section-criteria" class="table-of-contents">Criteria</a>
+        
+        <ol>
+        
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+          
+            
+          <li><a href="#section-criteria-code-in-the-open.md" class="table-of-contents">原始碼要開放</a></li>
+          
+          <li><a href="#section-criteria-bundle-policy-and-source-code.md" class="table-of-contents">政策與原始碼要合捆</a></li>
+          
+          <li><a href="#section-criteria-make-the-codebase-reusable-and-portable.md" class="table-of-contents">程式基底要可重複使用且可移植</a></li>
+          
+          <li><a href="#section-criteria-welcome-contributors.md" class="table-of-contents">歡迎貢獻者</a></li>
+          
+          <li><a href="#section-criteria-make-contributing-easy.md" class="table-of-contents">貢獻要容易</a></li>
+          
+          <li><a href="#section-criteria-maintain-version-control.md" class="table-of-contents">維護版本控制</a></li>
+          
+          <li><a href="#section-criteria-require-review-of-contributions.md" class="table-of-contents">要求審查貢獻內容</a></li>
+          
+          <li><a href="#section-criteria-document-codebase-objectives.md" class="table-of-contents">程式基底要有目標文件</a></li>
+          
+          <li><a href="#section-criteria-document-the-code.md" class="table-of-contents">程式碼要有文件</a></li>
+          
+          <li><a href="#section-criteria-use-plain-english.md" class="table-of-contents">使用白話的英語</a></li>
+          
+          <li><a href="#section-criteria-use-open-standards.md" class="table-of-contents">採用開放標準</a></li>
+          
+          <li><a href="#section-criteria-use-continuous-integration.md" class="table-of-contents">使用持續整合</a></li>
+          
+          <li><a href="#section-criteria-publish-with-an-open-license.md" class="table-of-contents">發行採用開放授權</a></li>
+          
+          <li><a href="#section-criteria-make-the-codebase-findable.md" class="table-of-contents">程式基底可查詢得到</a></li>
+          
+          <li><a href="#section-criteria-use-a-coherent-style.md" class="table-of-contents">風格要前後一致</a></li>
+          
+          <li><a href="#section-criteria-document-codebase-maturity.md" class="table-of-contents">記錄程式基底成熟度</a></li>
+          
+        </ol>
+      </li>
+      <li><a href="#section-contributing" class="table-of-contents">Contributing guide</a></li>
+      <li><a href="#section-code-of-conduct" class="table-of-contents">Code of conduct</a></li>
+      <li><a href="#section-governance" class="table-of-contents">Governance</a></li>
+      <li><a href="#section-changelog" class="table-of-contents">Version history</a></li>
+      <li><a href="#section-license" class="table-of-contents">License</a></li>
+    </ol>
+
+  </article>
+
+  <figure>
+    <img src="/assets/codebase.svg" alt="codebase">
+  </figure>
+
+  <article id="section-readers-guide">
+
+    <h1 id="讀者指引">讀者指引</h1>
+
+<p>本標準描述說明許多準則。所有準則各小節結構維持一致，來讓讀者清楚明白如何開發良好的公共程式。</p>
+
+<p>「政策制定者」、「管理人員」以及「開發人員與設計師」的稱呼，係指任何履行這些角色職責的人，不受其職稱限制。常見同時承擔多個角色職責的人。</p>
+
+<p>以下是各小節的簡要介紹，以及在本標準準則中的作用。</p>
+
+<h2 id="前言">前言</h2>
+
+<p>本小節說明這些準則想達成的目的，以及為何會對程式基底使用者與貢獻者來說這麼重要的原因。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<p>這個小節列出如果要遵循本標準，需要完成哪些事項。</p>
+
+<p>本文件中的下列關鍵字，請以《<a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a>》的描述作解釋：</p>
+
+<ul>
+  <li>必須</li>
+  <li>禁止</li>
+  <li>要求</li>
+  <li>應當</li>
+  <li>不得</li>
+  <li>應該</li>
+  <li>不該</li>
+  <li>建議</li>
+  <li>得以</li>
+  <li>可選擇</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<p>本小節提供您可採取的行動，來確認貢獻內容是否遵循本標準。如果您想要務實操作本標準，這部分很關鍵。</p>
+
+<p>我們已嘗試調整用字，讓即使是不熟悉這類主題內容的讀者，看完之後也能夠進行基本的遵循檢查。</p>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<p>本小節主要對象是政策制定者，列出他們的角色所能採取的具體行動。</p>
+
+<p>公共政策制定者設定專案的優先順序與目標，而在科技上的經驗可能沒那麼多。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<p>本小節主要對象是管理人員，列出他們的角色所能採取的具體行動。</p>
+
+<p>管理人員負責監督專案的準時交付、利害關係人管理，以及服務的持續交付。因此，他們得完全依賴政策制定者、開發人員與設計師。他們需要塑造正確的文化、籌備合適的資源、提供適
+當的架構等，才能交付優良的服務。</p>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>本小節主要對象是開發人員與設計師，列出他們的角色能採取的具體行動。</p>
+
+<p>開發人員通常對技術比較在行，與其他角色類別相比，對服務交付的影響更大。</p>
+
+<h2 id="作用範圍限制">作用範圍限制</h2>
+
+<p>《公共程式標準》不是為了涵蓋程式基底的個別實作而撰寫。這代表本標準不是要告訴實作人員，該如何遵循其組織單位當地的技術性基礎建設或法律框架。</p>
+
+<p>此外，雖然《公共程式標準》有引用一些標準，並且與其他標準有滿多重疊的部分，但本標準的目的是要推動協作。因此，本標準目標不在於取代品質標準，像是 ISO 25000
+認證系列，或是取代那些聚焦於安全性的標準，例如 <a href="https://github.com/coreinfrastructure/best-practices-badge">OpenSSF 最佳實務標
+章</a>等，而是希望能與它們能良好協同搭
+配。</p>
+
+<p>《公共程式標準》的目在於促進協作，但也無法保證能夠催生出一個社群。若要建立社群，除了程式基底需要準備好進行協作以外，也需要積極主動，以及做到超越協作以外的企圖
+心。</p>
+
+
+  </article>
+
+  <article id="section-glossary">
+
+    <h1 id="詞彙表">詞彙表</h1>
+
+<h2 id="程式或程式碼-code">程式或程式碼 (Code)</h2>
+
+<p>任何明確的規則系統，包括法律、政策與規則條例（法規、法式，也可稱為程式），以及用來開發軟體的原始碼（程式碼）。兩者都是規則，有些是由人類來執行，其餘則是由機器執
+行。</p>
+
+<h2 id="程式基底-codebase">程式基底 (Codebase)</h2>
+
+<p>任何獨立分離的統合包，內含執行部分政策或軟體所需的程式（包含原始碼與政策）、測試與文件等的整套內容。</p>
+
+<p>舉例而言，這個具體形式可以是文件，或是版本控制的儲存庫。</p>
+
+<h2 id="持續整合">持續整合</h2>
+
+<p>在軟體工程中，持續整合 (CI) 是盡可能頻繁地將所有開發人員工作中的副本，合併回程式基底開發中分支的實務作法。</p>
+
+<h2 id="不同情境">不同情境</h2>
+
+<p>只要是不同的公家機關或不同的部門，無法透過同一個決策單位讓協作自然發生，那就算是兩個不同的情境。</p>
+
+<h2 id="一般大眾">一般大眾</h2>
+
+<p>整體民眾：程式碼與其所建立的服務的終端使用者。</p>
+
+<p>舉例而言，城市的居民即視為該城市的服務、以及驅動這些服務運作的程式碼的終端使用者。</p>
+
+<h2 id="開源或開放原始碼-open-source">開源或開放原始碼 (Open Source)</h2>
+
+<p>所謂「開源」或「開放原始碼」，是根據 OSI 開放原始碼促進會發表的《<a href="https://opensource.org/osd-annotated">開放原始碼定義</a>》而來。</p>
+
+<h2 id="開放標準">開放標準</h2>
+
+<p>任何符合 OSI 開放原始碼促進會《<a href="https://opensource.org/osr">開放標準需求規範</a>》的標準，就是開放標準。</p>
+
+<h2 id="政策">政策</h2>
+
+<p>政策是一套謹慎設計的原則體系，用來引導決策並達成合理的成果。政策是一種意圖的聲明，並以程序或協定來執行。政策通常是由組織單位內的理事機構採用執行。政策能協助做出主觀
+與客觀的決策。</p>
+
+<p>公共政策是政府將其政治願景，轉化成計畫與行動來取得成果的程序。</p>
+
+<p>在國家層級，政策與立法（法律）通常是分開的；而在地方政府中，這兩者之間的區別通常比較模糊。</p>
+
+<p>在本標準當中，「政策」一詞指的是公家機關，例如政府與自治市等，所制定與採用的政策。</p>
+
+<h2 id="公共程式-public-code">公共程式 (Public Code)</h2>
+
+<p>公共程式，是由公家機關所開發的開放原始碼軟體，同時包含協作與重複利用所需的政策與指引。</p>
+
+<p>公共程式是在公共情境下，由人類或機器所執行的電腦原始碼（例如軟體與演算法）以及公共政策兩者。</p>
+
+<p>服務公眾利益的公共程式，具有開放、易懂、課責、近用、永續等特性。</p>
+
+<p>透過獨立於當地情境，但仍可在當地情境下實作的方式，還有公開以文件記錄開發程序等作法，來開發公共程式。如此，公共程式能作為基礎組件提供給他人，使其得以：</p>
+
+<ul>
+  <li>根據其當地情境重新實作</li>
+  <li>作為起點並繼續開發</li>
+  <li>當作學習時的基礎</li>
+</ul>
+
+<p>為了促進重複利用，公共程式通常放到公眾領域發行，或者採取允許他人能自由檢視、重複利用其成果，甚至產出衍生作品的開放授權。</p>
+
+<h2 id="儲存庫">儲存庫</h2>
+
+<p>儲存庫是版本控制工具，用於存放程式基底的檔案與中介資料的儲存位置。儲存庫讓多位貢獻者，得以同時對同一組檔案作業。儲存庫可以儲存一組檔案的多個版本。</p>
+
+<h2 id="原始碼-source-code">原始碼 (Source Code)</h2>
+
+<p>人類可讀，並且能夠翻譯成機器指令的電腦程式文字。</p>
+
+<h2 id="版本控制">版本控制</h2>
+
+<p>版本控制，是對原始碼及其相關檔案的變動行為作管理的流程。變動行為，通常是以稱為「<em>修訂編號</em>」（或版次等類似名稱）的代號作識別。每次修訂都會標示其改動時間以及作者，
+方便追溯程式碼的演進。修訂控制系統可用來比較不同版本之間的差異，以及查看內容隨著時間經歷的變動。</p>
+
+
+  </article>
+
+  <article id="section-criteria">
+    <h1>Criteria</h1>
+    
+    <ol>
+    
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+        
+      <li><a href="#section-criteria-code-in-the-open.md" class="table-of-contents">原始碼要開放</a></li>
+      
+      <li><a href="#section-criteria-bundle-policy-and-source-code.md" class="table-of-contents">政策與原始碼要合捆</a></li>
+      
+      <li><a href="#section-criteria-make-the-codebase-reusable-and-portable.md" class="table-of-contents">程式基底要可重複使用且可移植</a></li>
+      
+      <li><a href="#section-criteria-welcome-contributors.md" class="table-of-contents">歡迎貢獻者</a></li>
+      
+      <li><a href="#section-criteria-make-contributing-easy.md" class="table-of-contents">貢獻要容易</a></li>
+      
+      <li><a href="#section-criteria-maintain-version-control.md" class="table-of-contents">維護版本控制</a></li>
+      
+      <li><a href="#section-criteria-require-review-of-contributions.md" class="table-of-contents">要求審查貢獻內容</a></li>
+      
+      <li><a href="#section-criteria-document-codebase-objectives.md" class="table-of-contents">程式基底要有目標文件</a></li>
+      
+      <li><a href="#section-criteria-document-the-code.md" class="table-of-contents">程式碼要有文件</a></li>
+      
+      <li><a href="#section-criteria-use-plain-english.md" class="table-of-contents">使用白話的英語</a></li>
+      
+      <li><a href="#section-criteria-use-open-standards.md" class="table-of-contents">採用開放標準</a></li>
+      
+      <li><a href="#section-criteria-use-continuous-integration.md" class="table-of-contents">使用持續整合</a></li>
+      
+      <li><a href="#section-criteria-publish-with-an-open-license.md" class="table-of-contents">發行採用開放授權</a></li>
+      
+      <li><a href="#section-criteria-make-the-codebase-findable.md" class="table-of-contents">程式基底可查詢得到</a></li>
+      
+      <li><a href="#section-criteria-use-a-coherent-style.md" class="table-of-contents">風格要前後一致</a></li>
+      
+      <li><a href="#section-criteria-document-codebase-maturity.md" class="table-of-contents">記錄程式基底成熟度</a></li>
+      
+    </ol>
+  </article>
+
+  <figure>
+    <img src="/assets/unlock.svg" alt="unlock">
+  </figure>
+
+  
+  
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+      
+    <article id="section-criteria-code-in-the-open.md">
+      <h1 id="原始碼要開放">原始碼要開放</h1>
+
+<p>以開放精神編寫原始碼，能改善資訊透明、提高<a href="/glossary.html#source-code">原始碼</a>品質、讓原始碼更容易稽核，也能促進互相協作。</p>
+
+<p>這些合在一起，讓公民更有機會瞭解軟體與<a href="/glossary.html#policy">政策</a>如何影響他們與公家機關的互動。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>任何使用中政策的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>任何使用中軟體的所有原始碼都「必須」要公開（用於偵測詐欺的原始碼除外），且能供民眾取用。</li>
+  <li>程式基底「禁止」包含與使用者及其組織單位，或與第三方相關的敏感性資訊。</li>
+  <li>目前非使用中的任何原始碼（像是新版本、提案版本，或較舊版本）都「應該」公開。</li>
+  <li>「可選擇」是否要以文件記錄<a href="/glossary.html#general-public">一般大眾</a>與組織單位之間可能發生的任何特定互動，其背後所採用的原始碼或
+支持的政策。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認目前使用中的每個版本都有公布原始碼在網際網路上，而且民眾不需要經過任何形式的身分核對或授權，就能在原始貢獻組織以外，查看這些原始碼。</li>
+  <li>確認<a href="/glossary.html#codebase">程式基底</a>檔案與送交版次歷史紀錄，不包含敏感性資訊。</li>
+  <li>檢查目前非使用中的原始碼是否有公開。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定合乎開放精神的政策。</li>
+  <li>以公開透明的政策為優先。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>孕育擁抱開放、重視學習、歡迎意見回饋的文化。</li>
+  <li>與外部供應商和自由工作者以開放精神的方式協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>審查人員在檢核每次的送交版次紀錄時，要確實核對內容沒有包含組態設定、使用者名稱或密碼、公開金鑰，或其他產品系統中使用的實名憑證等敏感性資訊。</li>
+  <li>為符合上述敏感性資訊的相關規定，請明確分開資料與原始碼。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2012/10/12/coding-in-the-open/">以開放精神編寫原始
+碼</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/when-code-should-be-open-or-closed">程式碼應該開放或封閉的時
+機</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/government/publications/open-source-guidance/security-considerations-when-coding-in-the-open">以開放精神編寫原始碼的資安考
+量</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/deploying-software-regularly">定期部署軟
+體</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gdstechnology.blog.gov.uk/2014/01/27/how-we-use-github/">政府數位服務團如何使用
+GitHub</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-bundle-policy-and-source-code.md">
+      <h1 id="政策與原始碼要合捆">政策與原始碼要合捆</h1>
+
+<p>對於想根據所在情境實作程式基底的人，或是想更進一步貢獻<a href="/glossary.html#codebase">程式基底</a>開發的人來說，能同時取用<a href="../glossary.md#source-code">原始
+碼</a>與<a href="/glossary.html#policy">政策</a>文件兩者，可作為建置成品時的基礎組件。</p>
+
+<p>瞭解作用範疇與該範疇的政策是基本原則，才能瞭解程式基底試圖想解決的問題是什麼，以及該如何解決這些問題的作法。</p>
+
+<p>為了評估是否需要在新的情境中實作程式基底，組織單位需要瞭解必須做出改變的程序有哪些，或是如何對現有解決方案付出額外調整設定，以適應新的情境背景。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」包含原始碼所根據的政策。</li>
+  <li>如果政策根據原始碼而來，則該原始碼「必須」包含在程式基底中，用於偵測詐騙的原始碼則可除外。</li>
+  <li>政策「應該」採用機器可讀且明確的格式。</li>
+  <li><a href="/glossary.html#continuous-integration">持續整合</a>測試「應該」驗證原始碼與政策是否有一致執行。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與公務人員確認原始碼所根據的所有政策內容都有收錄在內。</li>
+  <li>與公務人員確認政策所根據的所有原始碼都有收錄在內。</li>
+  <li>確認政策內容是否能在機器上解讀。</li>
+  <li>確認原始碼與政策間的執行一致性能通過持續整合測試。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>與開發人員及設計師合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>提供相關政策內文，以便收錄於<a href="/glossary.html#repository">儲存庫</a>中；如果政策內文沒有英文版，請提供英文版摘要。務必也同時包含貴組織單
+位所選擇遵守的各項標準，以及影響貴組織單位程式基底開發或部署情境的任何組織單位流程。</li>
+  <li>請提供政策相關參考資料與連結。</li>
+  <li>政策內容請使用明確且機器可讀的格式，像是<a href="https://www.omg.org/spec/">物件管理群體</a>所發表的格式。</li>
+  <li>追蹤政策時，請使用與追蹤原始碼<a href="/criteria/maintain-version-control.html">相同的版本控制</a>與文件。</li>
+  <li>定期檢查，瞭解程式基底中的原始碼如何變動，以及是否仍然符合<a href="/criteria/document-codebase-objectives.html">政策意圖</a>。</li>
+  <li>納入會影響社會群體、程式基底與開發目標的相關政策，包含 <a href="https://eur-lex.europa.eu/eli/reg/2016/679/oj">GDPR 一般資料保護規
+則</a>或是<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟網頁無障礙命
+令</a>等此類法律義務，或者是人權政
+策，例如公家機關對機會平等的承諾等。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>讓政策制定者、開發人員與設計師持續參與，並且在整個開發過程中保持聯繫溝通。</li>
+  <li>確保政策制定者、開發人員與設計師朝相同目標努力。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>熟悉並且學會貴組織單位政策制定者所使用的流程模型標記法。</li>
+  <li>與政策制定者一同合作，確保政策法規與原始碼之間沒有不相符之處。</li>
+  <li>針對如何讓政策文字更清楚提供意見。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>維基百科上的 <a href="https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation">BPMN 業務流程模型與標記
+法</a>。</li>
+  <li>Trisotech 提供的 <a href="https://www.bpmnquickguide.com/view-bpmn-quick-guide/">BPMN 快速指
+南</a>。</li>
+  <li>維基百科上的 <a href="https://en.wikipedia.org/wiki/Decision_Model_and_Notation">DMN 決策模型與標記
+法</a>。</li>
+  <li>維基百科上的<a href="https://en.wikipedia.org/wiki/CMMN"> CMMN 案例管理模型標記法</a>。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-make-the-codebase-reusable-and-portable.md">
+      <h1 id="程式基底要可重複使用且可移植">程式基底要可重複使用且可移植</h1>
+
+<p>編寫可重複使用且可移植的<a href="/glossary.html#code">程式碼</a>，讓政策制定者、開發人員與設計師等，能重複使用、測試與改善目前已開發的內容，並將改善貢獻
+回程式基底中，如此可提高品質、降低維護成本、增強可靠性。</p>
+
+<p>以重複利用為前提籌劃設計<a href="/glossary.html#codebase">程式基底</a>，更容易與多方共享程式基底的目標使命、願景與範圍等。多方開發與使用的程式基底，
+更可以從能自我運作的社群中獲益。</p>
+
+<p>以文件記錄周全的模組構成程式基底，能夠改善重複使用與維護的能力。以文件清楚記錄用途的模組，更容易在<a href="/glossary.html#different-contexts">另一種情境</a>中重複利用。</p>
+
+<p>原始碼不依賴任何貢獻者、供應商或部署底下的特定情況專用基礎架構，則其他任何貢獻者都能測試該原始碼。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」開發成能在不同情境中重複使用。</li>
+  <li>程式基底「必須」獨立於任何採用保密、無法揭露、專有或非開放式授權的軟體或服務，以供執行與瞭解。</li>
+  <li>程式基底「應該」有多方單位使用。</li>
+  <li>發展路線圖「應該」有多方單位的需求影響。</li>
+  <li>程式基底開發「應該」由多方單位協作。</li>
+  <li>「應該」使用組態設定方式以將<a href="/glossary.html#source-code">原始碼</a>調整成能適應各情境的特定需求。</li>
+  <li>程式基底「應該」能夠在地化。</li>
+  <li>原始碼與其文件「不應該」包含特定情況專用的資訊。</li>
+  <li>程式基底模組「應該」以使其能夠在其他情境中重複利用的模式撰寫文件。</li>
+  <li>軟體「不應該」要求僅有單一供應商能提供的服務或平台。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>與另一組織單位角色與您相似的人確認，看他們是否能利用程式基底，以及需要怎麼進行。</li>
+  <li>確認程式基底不需要用到任何專有或非開放式授權的軟體或服務，就能夠執行。</li>
+  <li>若程式基底處於早期開發階段，尚未準備好正式上線，則檢查是否有想要尋求協作者的意圖跡象。
+    <ul>
+      <li>或是如果程式基底非常成熟與穩定，鮮少需要修正、改善或貢獻：
+        <ul>
+          <li>檢查是否有多方單位，或是有在多種情境下正使用程式基底。</li>
+          <li>檢查是否有以文件記錄協作所做出的成果，以及有編列相關預算。</li>
+        </ul>
+      </li>
+      <li>若是沒有，則：
+        <ul>
+          <li>檢查是否有多方單位，或是有在多種情境下正使用程式基底。</li>
+          <li>檢查程式基底貢獻者是否來自多方單位。</li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>檢查程式基底檔案與送交版次歷史紀錄中，不包含特定情況專用的資料。</li>
+  <li>檢查軟體是否可以在不使用單一供應商服務或平台的情況下，正常部署與執行。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為您的<a href="/glossary.html#policy">政策</a>撰寫清楚且足夠詳細的文件，讓他人即使不是處於同個原始背景情境也能夠理解。</li>
+  <li>確保程式基底有將貴組織單位列為已知使用者。</li>
+  <li>找出貴團隊想要協作的其他組織單位。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確認利害關係人與業主能夠瞭解，程式基底是以重複利用為明確目標，因而得以減少程式碼技術債，並讓程式基底可以永續發展。</li>
+  <li>確認您的團隊與其他團隊能相互協作。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>原始碼應該設計成：</p>
+
+<ul>
+  <li>能讓其他使用者與組織單位可以重複利用，而不受地方環境影響，</li>
+  <li>能解決通用性質問題，而非特定問題，</li>
+  <li>以邏輯上具有意義且獨立的模組構成，</li>
+  <li>如此讓類似組織單位中要面對近似問題的人，都可以採用這套解決方案（或其中一部份）。</li>
+</ul>
+
+<p>確保程式基底文件中，有說明程式的組建日期與執行時期的依賴項目。如果您的情境需要部署至專有平臺上，或者要用到專有組件，則請確保協作者可以在不用到這兩者的情況下，就能進
+行開發、使用、測試、部署等。</p>
+
+<p>在每份送交版次中，審查人員要確認其中不含特定情況專用的資料，像是主機名稱、個人與組織單位資料、代符與密碼等。</p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable">讓原始碼開放且可重複利
+用</a>》。</li>
+  <li>W3C 全球資訊網協會《<a href="https://www.w3.org/International/questions/qa-i18n">在地化與國際化</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-welcome-contributors.md">
+      <h1 id="歡迎貢獻者">歡迎貢獻者</h1>
+
+<p><a href="/glossary.html#codebase">程式基底</a>社群的氛圍，會影響使用者選擇所要使用的程式基底。歡迎任何人成為貢獻者的社群，才能夠不斷茁壯並且持續自我
+運作。若貢獻者有明確的方法可以影響程式基底、社群目標與進展，則該社群分裂成分歧的社群的機率也較低。新參與者需要瞭解並信任程式基底社群的治理方式。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底必須「允許」任何人對程式基底提出修改建議。</li>
+  <li>程式基底「必須」包含貢獻指引，說明歡迎貢獻的內容類型，以及貢獻者可如何參與開發，例如以「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」檔案說明。</li>
+  <li>程式基底「必須」以文件記錄程式基底、貢獻內容與社群互動等的治理方式，例如以「<code class="language-plaintext highlighter-rouge">GOVERNANCE</code>」檔案來說明。</li>
+  <li>貢獻指引「應該」以文件記錄預期由何者負擔審查貢獻內容所需的開銷費用。</li>
+  <li>程式基底「應該」宣布投入其開發與維護工作的參與組織單位。</li>
+  <li>程式基底「應該」要有可公開取得的發展路線圖。</li>
+  <li>程式基底「應該」公布程式基底的活動統計數據。</li>
+  <li>「可選擇」是否為程式基底加入貢獻者的行為守則。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認可以提交修改建議給程式基底。</li>
+  <li>確認程式基底有貢獻指引。</li>
+  <li>確認程式基底有清楚解釋治理架構，並包含如何影響程式基底治理的方法。</li>
+  <li>確認貢獻指引是否有涵蓋預期由何者負擔審查貢獻內容的開銷費用。</li>
+  <li>檢查是否有參與的組織單位名單。</li>
+  <li>檢查是否有發展路線圖。</li>
+  <li>檢查是否有公布活動統計數據。</li>
+  <li>檢查是否有行為守則。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為程式基底加入其他資源的清單，而這些資源可幫助<a href="/glossary.html#policy">政策</a>專家、非政府組織、學者等，更能瞭解或可重複利用您的政策。</li>
+  <li>考慮放入聯絡資訊，讓其他考慮合作的政策制定者能徵詢您的意見。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保治理架構文件內容中，有包含目前如何改變治理狀態的流程。</li>
+  <li>如果社群對於治理架構應該如何改變有共識，則應該將這些構想宣告為願景寫入文件中。</li>
+  <li>若有需要，確認您有編列貢獻內容審查流程的預算，且經過程式基底社群同意。</li>
+  <li>確認文件有解釋每個參與組織單位所投入的內容，例如提供程式基底哪些資源，以及參與的時間長度等。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能長久參與社群。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>快速回應請求。</li>
+  <li>告知管理人員，您在支援其他貢獻者時所需的時間與資源。</li>
+  <li>清楚告知貢獻者他們該如何做，才能讓貢獻內容整合到程式基底中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼指引所提供的《<a href="https://opensource.guide/building-community/">營造友善的社群</a>》。</li>
+  <li>Mike McQuaid《<a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/">開放原始碼貢獻者瓶
+頸</a>》。</li>
+  <li>開放原始碼指引針對推動<a href="/glossary.html#open-source">開放原始碼</a>社群專案所寫的《<a href="https://opensource.guide/leadership-and-governance/">領導與治
+理</a>》。</li>
+  <li>Pieter Hintjens《<a href="http://hintjens.com/blog:117">打造網路社群</a>》(長篇文章！)。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-make-contributing-easy.md">
+      <h1 id="貢獻要容易">貢獻要容易</h1>
+
+<p>若要開發更好、更可靠且功能更豐富的軟體，使用者需要能夠為共享的<a href="/glossary.html#codebase">程式基底</a>修正問題、新增功能，以及提出安全性議題
+等。</p>
+
+<p>共享的數位基礎建設讓協作貢獻更容易。使用者讓程式基底接受貢獻時所需付出的心力越少，則使用者越可能成為貢獻者。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」有個可以公開接受任何人建議的議題追蹤器。</li>
+  <li>文件中「必須」同時有公開的議題追蹤器連結，以及已提交的程式基底變動的連結，例如記錄在「<code class="language-plaintext highlighter-rouge">README</code>」檔案中。</li>
+  <li>程式基底「必須」要有能與使用者以及開發人員溝通的管道，像是設立電子郵件列表（郵遞論壇）。</li>
+  <li>「必須」有透過封閉管道通報安全性問題的方法，來達成負責任的揭露。</li>
+  <li>文件「必須」說明，該如何通報潛在的安全性與敏感性問題。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有公開的議題追蹤器。</li>
+  <li>確認程式基底有公開的議題追蹤器連結，以及已提交的程式基底變動的連結。</li>
+  <li>確認可以使用程式基底中提到的管道，與其他使用者以及開發人員一同討論該軟體。</li>
+  <li>確認有封閉的管道可通報安全性問題。</li>
+  <li>確認有說明如何私下通報安全性問題。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>追蹤程式基底中的<a href="/glossary.html#policy">政策</a>問題，讓相關的外部政策專家如果自願也能夠協助。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>追蹤程式基底中的管理問題，讓有相關經驗的外部管理人員如果自願也能夠協助。</li>
+  <li>支持您經驗豐富的政策制定者、開發人員與設計師，使其盡可能為程式基底持續做出長久貢獻。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>與<a href="/criteria/require-review-of-contributions.html">審查</a>流程相同，務必迅速回應請求。</li>
+  <li>告知管理人員，您在支援其他貢獻者時所需的時間與資源。</li>
+  <li>確保人們可輕鬆找到合適的溝通管道，來詢問維護人員與利害關係人問題，例如寫在「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>確保中介資料包含合適的聯絡資訊，例如寫在 publiccode.yml 檔案中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Joel Hans《<a href="https://dev.to/joelhans/how-to-inspire-exceptional-contributions-to-your-open-source-project-1ebf">如何引發他人為您的開放原始碼專案做出優秀貢
+獻</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/">以開放精神編寫原始碼的好
+處</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-maintain-version-control.md">
+      <h1 id="維護版本控制">維護版本控制</h1>
+
+<p><a href="/glossary.html#version-control">版本控制</a>主要在追蹤<a href="/glossary.html#source-code">原始碼</a>以及其他<a href="../glossary.md#codebase">程
+式基底</a>檔案歷來的變動。這能讓您為程式基底維護有條理的變動歷史文件。這是大規模協作得以運作的要素，使開發人員可以
+針對修改變動平行作業，並幫助未來的開發人員瞭解做出修改的原因。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底中的所有檔案皆「必須」有版本控制。</li>
+  <li>所有決定皆「必須」記錄成送交版次訊息。</li>
+  <li>每份送交版次訊息皆「必須」盡可能附上討論與議題連結。</li>
+  <li>程式基底「應該」以分散式版本控制系統作維護。</li>
+  <li>貢獻守則「應該」要求貢獻者，將相關的修改變動以群組分類方式送交。</li>
+  <li>維護人員「應該」使用像是修訂版次標記，或文字標籤，來標示程式基底正式發行的版本。</li>
+  <li>貢獻守則「應該」鼓勵採用能在版本控制系統中，輕鬆檢視與瞭解檔案中何處有做出更動的檔案格式。</li>
+  <li>貢獻者「可選擇」是否對送交內容作簽章，並附上電子郵件信箱，以便當未來貢獻者對其內容有疑問時，可以與之前的貢獻者聯絡。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底維持在版本控制狀態中，像是使用 Git 之類的軟體。</li>
+  <li>審查送交版次歷史紀錄，確認所有的送交版次訊息，皆有解釋程式碼修改變動的原因。</li>
+  <li>審查送交版次歷史紀錄，確認所有送交版次訊息之中，盡可能在所有討論過修改變更的地方，包含變動內容以及連結位置（提供網址）。</li>
+  <li>檢查版本控制系統是否為分散式。</li>
+  <li>審查送交版次歷史紀錄，檢查是否有根據貢獻指引將相關的程式碼變動以群組分類。</li>
+  <li>檢查是否可能透過像是修訂版次標記，或文字標籤，來取用程式基底中的特定版本。</li>
+  <li>檢查程式基底在盡可能的情況下，檔案都是採用文字格式。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>如果因為<a href="/glossary.html#policy">政策</a>改變而在程式基底中有新的版本，則請確認有在文件中清楚說明：
+    <ul>
+      <li>政策改變的地方，</li>
+      <li>程式基底如何因應而改變。</li>
+    </ul>
+  </li>
+</ul>
+
+<p>舉例來說，為程式基底作權限管理時，如果要新增申請方類別來賦予取用權，應視為一種政策變動。</p>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>支持政策制定者、開發人員與設計師，使其能清楚表達他們對程式基底做出的改善。確保改善程式基底不會有公關風險。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>確認版本控制系統中，有瞭解程式碼、建置與部署所需要用到的所有檔案。</li>
+  <li>送交版次訊息要寫清楚，讓人一看就能瞭解送交修改的原因。</li>
+  <li>使用像是修訂版次標記，或文字標籤來標示不同版本，以方便取用特定版本。</li>
+  <li>送交版次訊息要寫清楚，方便之後比較各版本。</li>
+  <li>在政策改變以後，與政策制定者合作說明原始碼更新的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Karl Fogel《<a href="https://producingoss.com/en/vc.html#vc-vocabulary">製作開放原始碼軟體：版本控制字
+彙</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/maintaining-version-control-in-coding">維護程式碼的版本控
+制</a>》。</li>
+  <li>GitHub 提供的「<a href="https://skills.github.com/">GitHub 技能</a>」，可學習如何使用 GitHub，或是重溫您的技巧。</li>
+  <li>GitHub 提供的「<a href="https://education.github.com/git-cheat-sheet-education.pdf">Git 密技
+表</a>」，列出了最常用的 git 命
+令。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-require-review-of-contributions.md">
+      <h1 id="要求審查貢獻內容">要求審查貢獻內容</h1>
+
+<p>同儕審查貢獻是<a href="/glossary.html#source-code">原始碼</a>提升品質的關鍵，也能降低安全性風險與營運風險。</p>
+
+<p>要求仔細審查貢獻，能孕育出確保貢獻都是優質、完整且能帶來價值的文化。審查原始碼能提高在原始碼加入<a href="/glossary.html#codebase">程式基底</a>之前，
+就發現與修正潛在臭蟲與出錯的機率。得知所有原始碼都會被審查，就不會孕育出習慣怪罪他人的文化，反倒是鼓勵每個人都專注在解決方案上。</p>
+
+<p>快速審查<a href="/glossary.html#policy">政策</a>在於向貢獻者保證，必定在一段時間內提供意見回饋或是協作式改善，進而提高貢獻者交付貢獻內容的頻率，以及參
+與的熱度。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>所有被接受或是送交給程式基底正式發行版本中的貢獻內容，都「必須」經過另一位貢獻者審查。</li>
+  <li>審查「必須」包含原始碼、政策、測試、文件等。</li>
+  <li>如果不接受貢獻內容，審查人員「必須」提供意見回饋。</li>
+  <li>審查流程「應該」確認貢獻內容遵循程式基底的標準、架構、決策安排等，以通過審查。</li>
+  <li>審查內容「應該」包含執行軟體與執行程式基底測試。</li>
+  <li>貢獻內容「應該」由與貢獻者不同背景情境的人來審查。</li>
+  <li>版本控制系統「不應該」在程式基底的正式發行版本中，接受未經審查的貢獻內容。</li>
+  <li>審查「應該」在兩個工作天內進行。</li>
+  <li>「可選擇」是否由多位審查人員進行審查。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認歷史紀錄中，每個送交版次都有經過不同的貢獻者審查。</li>
+  <li>確認審查內容包含原始碼、政策、測試、文件等。</li>
+  <li>針對未被採用的貢獻內容，確認有適當解釋原因。</li>
+  <li>檢查審查人員指引中，有包含是否遵循標準、架構、程式基底指引等指示。</li>
+  <li>檢查審查人員在審查時是否有執行軟體與測試。</li>
+  <li>與審查人員確認，送交版次是否有經過不同情境背景的不同貢獻者審查。</li>
+  <li>檢查<a href="/glossary.html#version-control">版本控制</a>系統中是否有採用分支保護。</li>
+  <li>檢查貢獻提交與審查之間的時間間隔。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定進行任何審查時，含原始碼與其他一切事物，都要恪遵「四眼原則」的政策。</li>
+  <li>採用具有審查與意見回饋功能的版本控制系統，或作業流程。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將交付妥善軟體作為共同目標。</li>
+  <li>確保如原始碼、政策、文件、測試等的貢獻內容撰寫與審查，皆受到同等重視。</li>
+  <li>創造歡迎所有形式的貢獻，而且每個人都能夠審查貢獻內容的文化。</li>
+  <li>確保貢獻者在貢獻內容給程式基底時，不是獨自一人埋頭苦幹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>請程式基底的其他貢獻者，審查您在貴組織單位內外的工作成果。</li>
+  <li>當他人請求您審查時，請盡快回覆，並先給出需要修正之處背後的概念。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html#content">英國政府數位服務團程式碼審查程
+序</a>》。</li>
+  <li><a href="https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches">GitHub</a>
+與
+<a href="https://about.gitlab.com/blog/2014/11/26/keeping-your-code-protected/">GitLab</a> 平
+臺的分支保護說明。</li>
+  <li>Sage Sharp《<a href="https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/">程式修補審查的和善藝
+術</a>》。</li>
+  <li>Mozilla《<a href="https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177">參與度評測成
+果</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-document-codebase-objectives.md">
+      <h1 id="程式基底要有目標文件">程式基底要有目標文件</h1>
+
+<p>以文件清楚記錄<a href="/glossary.html#codebase">程式基底</a>目標，來傳達程式基底的用途目標。這能幫助利害關係人與貢獻者劃定程式基底的開發範圍。這些目
+標也能方便人們判斷，是否在當下或未來，會對此程式基底或其模組感興趣。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」包含描寫目標的文件，像是主旨、使命或目標陳述。開發人員與設計師需要能夠瞭解這些，他們才知道可以怎樣使用程式基底或協助貢獻。</li>
+  <li>程式基底文件「應該」清楚描述<a href="/glossary.html#policy">政策</a>目標與程式基底目標之間的關聯。</li>
+  <li>「可選擇」是否以文件記錄給<a href="/glossary.html#general-public">一般大眾</a>看的程式基底目標。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底文件有包含程式基底目標，或主旨、使命等。</li>
+  <li>查看政策目標與程式基底目標之間關聯的描述。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>將政策目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+  <li>確保所有程式基底目標，有連結或引用為了符合〈<a href="/criteria/bundle-policy-and-source-code.html">政策與原始碼要合捆</a>〉準則而加入的支持政策文
+件。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將單位目標、組織目標或業務目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將技術與設計目標加入程式基底文件中，例如「<code class="language-plaintext highlighter-rouge">README</code>」文件當中。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Marek Hajduczenia《<a href="http://grouper.ieee.org/groups/802/3/RTPGE/public/may12/hajduczenia_01_0512.pdf">如何撰寫專案目
+標</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-document-the-code.md">
+      <h1 id="程式碼要有文件">程式碼要有文件</h1>
+
+<p>文件記錄周全的<a href="/glossary.html#source-code">原始碼</a>能幫助人們瞭解該原始碼的作用與使用方式。文件紀錄是幫助人們快速上手如何使用<a href="../glossary.md#codebase">程式基
+底</a>，並做出貢獻的關鍵。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底的所有功能、<a href="/glossary.html#policy">政策</a>及原始碼，都「必須」以可清楚瞭解的用語描述，讓懂程式基底目的用途的人也能夠理解。</li>
+  <li>程式基底文件「必須」說明如何安裝與執行軟體。</li>
+  <li>程式基底文件「必須」為關鍵功能舉出範例。</li>
+  <li>程式基底文件「應該」包含精要的說明，讓<a href="/glossary.html#general-public">一般大眾</a>和記者等廣泛的利害關係人都能清楚明白。</li>
+  <li>程式基底文件「應該」有一部分用來說明，如何安裝與執行原始碼的單機版；如果有必要，也應該包含測試資料集。</li>
+  <li>程式基底文件「應該」包含所有功能的範例。</li>
+  <li>程式碼文件「應該」描述程式基底的主要組件或模組，以及其彼此之間的關係，例如以高層架構圖表示。</li>
+  <li>「應該」要有針對文件品質的<a href="/glossary.html#continuous-integration">持續整合</a>測試。</li>
+  <li>「可選擇」是否在程式基底文件中，包含讓使用者想要立即使用程式基底的範例。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認文件內容能讓其他利害關係人、其他公家機關的專業人士，以及一般大眾，都可以清楚明白。</li>
+  <li>確認文件有說明如何安裝與執行原始碼。</li>
+  <li>確認文件有包含主要功能的範例。</li>
+  <li>向一般大眾的成員以及記者確認，他們是否能明白文件當中的精要說明。</li>
+  <li>檢查單機版原始碼的安裝與執行的步驟說明，確認能順利執行系統。</li>
+  <li>檢查文件中列舉的所有功能都包含範例。</li>
+  <li>檢查文件中是否包含高層架構圖，或類似的組件關係圖表。</li>
+  <li>確認整合測試有包含到程式碼文件品質，例如確認生成的文件是否正確，並檢查連結與圖片等。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>定期查看程式基底中非政策程式碼的變動情況。</li>
+  <li>針對如何讓非政策文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>嘗試使用程式基底，並提供您的意見回饋來讓政策與原始碼文件改善得更加清楚。舉例來說，可以自問目前的文件是否足以說服另一個公家機關的管理人員使用這套程式基底？</li>
+  <li>確保您同時瞭解政策、原始碼以及文件內容。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>定期查看程式基底中非原始碼部分的變動情況。</li>
+  <li>針對如何讓非原始碼文件更清楚易懂提供意見回饋。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Write the Docs《<a href="https://www.writethedocs.org/guide/">文件指南</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-use-plain-english.md">
+      <h1 id="使用白話的英語">使用白話的英語</h1>
+
+<p>英語是軟體開發領域中的<i>實際</i> 協作語言。</p>
+
+<p>公家機關資訊需要讓所有選民都能取用。簡單且白話的語言，能讓更多人能瞭解<a href="/glossary.html#code">程式碼</a>與其功用。</p>
+
+<p>翻譯可以讓更多人有機會認識<a href="/glossary.html#codebase">程式基底</a>。用語越是簡單明暸，製作與維護翻譯的成本就越低。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底的所有文件都「必須」使用英語。</li>
+  <li>所有<a href="/glossary.html#source-code">原始碼</a>都「必須」使用英語編寫，其中<a href="/glossary.html#policy">政策</a>是由機器
+解讀當作程式碼的部分則除外。</li>
+  <li>任何合捆的政策如果沒有英語版本，則「必須」隨附英語版摘要。</li>
+  <li>任何翻譯版本皆「必須」跟隨英語版本更新，以維持在最新狀態，反之亦然。</li>
+  <li>程式基底中「不應該」使用首字母縮字、縮寫、雙關語，或法律/非英語/行業特定詞彙；如果有的話，則需要在這些用語出現之前先行解釋，或是附上解釋該用語的網頁連結。</li>
+  <li>根據《<a href="https://www.w3.org/WAI/WCAG21/quickref/?
+showtechniques=315#readable">網頁內容近用性無障礙指引 2</a>》的建議，文件內容「應該」以國中識讀程度為主。</li>
+  <li>「可選擇」是否提供任何程式碼、文件、測試等的翻譯版。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底文件有英語版本。</li>
+  <li>確認原始碼為英語，確認任何非英語內容都是政策，或確認術語在其前方有先行說明等。</li>
+  <li>確認任何非英語政策都有隨附英語版摘要。</li>
+  <li>確認翻譯版與英語版內容相同。</li>
+  <li>確認文件當中，沒有任何未說明的首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙等。</li>
+  <li>檢查文件的拼字、文法與易讀性等。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>在過程中經常與其他管理人員、開發人員與設計師測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在團隊內部與利害關係人之間的內部溝通中，試著限制首字母縮寫字、縮寫、雙關語，或法律/非英語/行業特定詞彙的使用。如果有使用到的話，則將這些用語加入詞彙表，並且在
+使用這些詞彙的地方加上詞彙表連結。</li>
+  <li>以批判性觀點看待提案與修改當中的文件與描述。如果有您看不懂的內容，很有可能其他人也同樣迷惘。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>經常與政策制定者和管理人員測試，確認他們是否瞭解您們正要交付的程式碼與其文件的內容。</li>
+  <li>詢問身處不同背景情境的人（像是另一個程式基底的開發人員）是否能瞭解內容。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>符合 W3C 全球資訊網協會《<a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容近用性無障礙指引 2.1、3.1 之可讀
+性</a>》要求，撰寫的文字內容要容易閱讀與理解。</li>
+  <li>歐盟委員會的《<a href="https://ec.europa.eu/digital-single-market/en/web-accessibility">歐盟無障礙環境命
+令</a>》，是高度要求無障礙環境
+的法規範例。</li>
+  <li>美國總務署《<a href="https://www.plainlanguage.gov/about/definitions/">白話語言定義</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-use-open-standards.md">
+      <h1 id="採用開放標準">採用開放標準</h1>
+
+<p><a href="/glossary.html#open-standard">開放標準</a>保證可以取得使用與貢獻<a href="/glossary.html#codebase">程式基底</a>所需的知
+識。不僅能為不同的系統之間建立互通性，更能降低廠商套牢的可能性。開放標準如果明確，不同方就可以各自獨立開發作資料交換。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底如要促進資料交換的特性，就「必須」採用符合 <a href="https://opensource.org/osr">OSI 開放原始碼促進會其《開放標準需求規範</a>》的
+開放標準。</li>
+  <li>如果有使用到任何非開放標準，則「必須」在文件中清楚記錄。</li>
+  <li>程式基底選擇採用的任何標準，皆「必須」在文件中列出，並且只要有的話，就附上該標準的連結。</li>
+  <li>程式基底選擇採用的任何非開放標準，皆「禁止」妨礙程式基底的協作與重複使用。</li>
+  <li>如果還沒有已存在的開放標準可採用，則「應該」投入開發新標準。</li>
+  <li>採用開放標準時，「應該」優先選擇可經機器測試的開放標準。</li>
+  <li>採用非開放標準時，「應該」優先選擇可經機器測試的非開放標準。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認資料交換遵守 OSI 開放原始碼促進會批准的開放標準。</li>
+  <li>確認若有採用任何的非開放標準，皆有清楚記錄在文件中。</li>
+  <li>確認文件有清單列出程式基底所採用的標準，其中各標準有對應的有效連結；或沒有採用任何標準時，則留下聲明。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>以政策要求盡可能在任何情況下採用開放標準。</li>
+  <li>禁止採購不採用開放標準的技術科技。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>考慮在<a href="/glossary.html#source-code">原始碼</a>審查中納入開放標準依循評估。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>將是否依循標準加入<a href="/glossary.html#continuous-integration">持續整合</a>測試中。</li>
+  <li>審查送交版次與<a href="/glossary.html#repository">儲存庫</a>其他資源是否有參考開放標準，並交叉檢查其中有列出標準的部分。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>英國內閣辦公室發表的《<a href="https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles">開放標準原
+則</a>》
+<a href="/glossary.html#policy">政策</a>報告。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-use-continuous-integration.md">
+      <h1 id="使用持續整合">使用持續整合</h1>
+
+<p>透過自動化測試驗證，開發人員能更頻繁地將其工作成果合併至共享的分支，達成非同步協作。合併的頻率越頻繁、貢獻的規模越小，在合併時所發生的衝突就越容易解決。</p>
+
+<p>自動化測試所有功能，使人更加信賴貢獻內容發揮其功用且沒有引發任何錯誤，同時讓審查人員專注在貢獻的結構與作法。測試越聚焦，就越容易辨識並瞭解所出現的問題。</p>
+
+<p>以文件記錄程式基底的<a href="/glossary.html#continuous-integration">持續整合</a>工作流程，能協助貢獻者瞭解對貢獻內容的期待。持續整合讓
+監管<a href="/glossary.html#codebase">程式基底</a>狀態變得更為簡單。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li><a href="/glossary.html#source-code">原始碼</a>中的所有功能，都「必須」有自動化測試。</li>
+  <li>所有貢獻內容都「必須」先通過自動化測試，才能上傳至程式基底。</li>
+  <li>程式基底「必須」有解說如何撰寫貢獻內容結構的相關指引。</li>
+  <li>程式基底「必須」有能夠審查貢獻內容的活躍貢獻者。</li>
+  <li>「應該」公開貢獻內容的自動化測試結果。</li>
+  <li>程式基底指引「應該」指出，每次的貢獻內容都只應聚焦在單一議題上。</li>
+  <li>「應該」監管原始碼測試與文件的涵蓋範圍。</li>
+  <li>「可選擇」是否測試<a href="/glossary.html#policy">政策</a>和文件，與原始碼之間有無一致性，或是反之亦然。</li>
+  <li>「可選擇」是否測試政策和文件所採用的樣式，以及連結有無失效。</li>
+  <li>「可選擇」是否使用文件中的範例來測試軟體。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認有測試可用。</li>
+  <li>確認原始碼覆蓋率工具能檢查到 100% 的原始碼。</li>
+  <li>確認貢獻內容只有在通過所有測試後，才會認可上傳至程式基底。</li>
+  <li>確認有貢獻指引解說如何撰寫貢獻內容的結構。</li>
+  <li>確認最近三個月內有貢獻內容上傳。</li>
+  <li>檢查是否可以查看測試結果。</li>
+  <li>檢查是否有公布原始碼覆蓋率數據。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>儘早讓管理人員、開發人員與設計師一同加入，並且讓他們持續參與您政策的制定程序。</li>
+  <li>確保政策文件也有設好自動化測試。</li>
+  <li>如果政策文件未能通過測試，請快速修正。</li>
+  <li>確保原始碼能反映出政策的任何變動（請參閱〈<a href="/criteria/maintain-version-control.html">維護版本控制</a>〉）。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>確保能儘快且經常給真正的終端使用者進行測試。</li>
+  <li>以頻繁整合少量部分內容的方式做專案規劃，而非久久一次繳交大量部分內容。</li>
+  <li>聘請有能力處理漸進式交付，並跟得上規劃進度的顧問服務。</li>
+  <li>發生重大失誤後，鼓勵公開事故報告，以及公開討論事後學到的教訓。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>協助管理人員擬定工作規劃，例如規劃成可以拆分成小部分逐次整合。</li>
+  <li>協助貢獻者聚焦其貢獻內容與功能請求，讓涵蓋範圍盡可能合理地縮小。</li>
+  <li>協助管理人員與政策制定者測試其貢獻內容，例如測試其貢獻內容中的失效連結或樣式。</li>
+  <li>編排原始碼結構時，要將難以在測試環境下創造出來的情況，得以在測試過程中模擬出來。例如硬碟空間不足、記憶體分配失敗等資源耗盡情況，都是難以創造的典型案例。</li>
+  <li>調整程式碼覆蓋率測試工具，避免在 inline 過程或其他最佳化處理時得到假警報。</li>
+  <li>經常部署。</li>
+  <li>至少每天整合工作內容一次。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Martin Fowler《<a href="https://www.martinfowler.com/articles/continuousIntegration.html">什麼是持續整
+合</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://gds-way.cloudapps.digital/standards/continuous-delivery.html">使用持續交
+付</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/technology/quality-assurance-testing-your-service-regularly">品質保證：定期測試您的服
+務</a>》。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-publish-with-an-open-license.md">
+      <h1 id="發行採用開放授權">發行採用開放授權</h1>
+
+<p>採用開放且為人熟知的授權，讓任何人都可以查看<a href="/glossary.html#source-code">原始碼</a>，使其能瞭解運作方式、自由使用，並且能為<a href="../glossary.md#codebase">程式基
+底</a>做出貢獻。這也能促進供應商建立出以程式基底為中心的生態系。</p>
+
+<p>明確指出程式基底中每一個檔案的授權，讓使用者能正確重複利用程式基底的部分內容，並表彰作者名稱。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>所有原始碼與文件，皆「必須」採用使其得以自由重複使用、自由修改、自由再次散布的授權條款。</li>
+  <li>軟體原始碼「必須」採用<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條
+款</a>。</li>
+  <li>所有原始碼皆「必須」搭配授權條款檔案一併發行。</li>
+  <li>「禁止」要求貢獻者將其貢獻的程式碼著作權轉讓給程式基底。</li>
+  <li>程式基底中所有原始碼檔案，皆「應該」包含機器可讀的著作權聲明與授權條款標頭內容。</li>
+  <li>「可選擇」是否為不同類型的原始碼與文件採用多重授權條款。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底有清楚給予授權條款。</li>
+  <li>確認原始碼的授權條款有列於<a href="https://spdx.org/licenses/">經 OSI 開放原始碼促進會所批准，或由 FSF 自由軟體基金會所發表的自由授權條款清
+單</a>，以及文件的授權條款有<a href="https://opendefinition.org/licenses/">符合「開放定
+義」</a>。</li>
+  <li>確認程式基底中有包含其採用的授權條款檔案。</li>
+  <li>確認貢獻指引中，以及<a href="/glossary.html#repository">儲存庫</a>的組態設定中，沒有要求貢獻者轉讓著作權。</li>
+  <li>在程式基底<a href="/glossary.html#continuous-integration">持續整合</a>測試中，確認是否有檢查授權內容為機器可讀的檢查項目。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定要求原始碼必須採用<a href="/glossary.html#open-source">開放原始碼</a>授權的<a href="/glossary.html#policy">政策</a>。</li>
+  <li>制定抑制採購非開放原始碼授權程式碼，與非開放科技的政策。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>只與能採用開放原始碼授權交付、與發行其原始碼的開放原始碼軟體供應商合作。</li>
+  <li>請注意，雖然<a href="https://creativecommons.org/licenses/">創用CC授權</a>適合用於文件作品，但其中指明「非商業性」或「禁止改作」
+的授權條款，代表「無法」自由重複使用、自由修改、自由再次散布等，因此未能符合規定。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>每當建立新的程式基底時，都要加入新的「<code class="language-plaintext highlighter-rouge">license</code>」授權條款檔案。</li>
+  <li>每當建立新的原始碼檔案時，都要加入著作權聲明與授權條款標頭內容。</li>
+  <li>每當程式基底重複利用原始碼時，都要確認原始碼的授權與程式基底的授權相容。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>開放原始碼促進會所發表的《<a href="https://opensource.org/osd">開放原始碼定義</a>》，所有開放原始碼授權條款皆符合這套定義。</li>
+  <li>紐西蘭CC Aotearoa《<a href="https://creativecommons.org/about/videos/creative-commons-kiwi">創用CC介紹動畫影
+片</a>》。</li>
+  <li>歐洲自由軟體基金會所發表的《<a href="https://reuse.software/spec/">REUSE 倡議規範</a>》，提供規範明確、人類可讀以及機器可讀的著作權與
+授權資訊。</li>
+  <li>Linux 基金會所發表的 <a href="https://spdx.org/licenses/">SPDX 授權條款清單</a>，提供經標準化、且機器可讀的大多數授權條款縮寫表示
+法。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-make-the-codebase-findable.md">
+      <h1 id="程式基底可查詢得到">程式基底可查詢得到</h1>
+
+<p>一旦<a href="/glossary.html#codebase">程式基底</a>越容易被發現，更多的潛在協作者也就找得到它。不能只是發表個程式基底，然後就盼望他人找得到這套程式基
+底，更需要主動積極。</p>
+
+<p>有中介資料說明檔的話，會讓程式基底更容易被發現。良好且包含永久唯一識別碼的中介資料，例如寫成 Wikidata 維基數據條目，或是放到 FSF 自由軟體基金會的軟體
+目錄列表之中（使程式基底成為語意網路中的一部份），他人就能更容易透過第三方工具參考、引用、辨別、發現程式基底。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底名稱「應該」要能描述說明其用途，且不包含任何首字母縮寫字、縮寫、雙關語，或組織單位品牌名稱或抬頭等。</li>
+  <li>程式基底說明「應該」要簡短，幫助他人瞭解程式基底的目的與作用。</li>
+  <li>維護人員「應該」將程式基底提交至相關的軟體目錄上。</li>
+  <li>程式基底「應該」要架設網站，內容中以程式基底各類潛在使用者（技術人員、政策專家、管理人員等）偏好的業內用語，描述程式基底所能解決的問題。</li>
+  <li>在搜尋引擎查找程式基底名稱時，「應該」能搜尋得到程式基底。</li>
+  <li>在使用搜尋引擎時，如果以自然語言描述程式基底所能解決的問題，「應該」能搜尋得到程式基底。</li>
+  <li>程式基底「應該」具備永久唯一識別碼，而且該項條目要提及主要貢獻者、<a href="/glossary.html#repository">儲存庫</a>、位置、網站等。</li>
+  <li>程式基底「應該」包含機器可讀的中介資料說明，例如採用
+<a href="https://github.com/publiccodeyml/publiccode.yml">publiccode.yml</a>格式的檔案。</li>
+  <li>「可選擇」是否為程式基底設置專用的網域名稱。</li>
+  <li>「可選擇」是否在社群舉辦的會議中定期進行簡報。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>檢查程式基底名稱是否描述說明其用途，且不包含雙關語。</li>
+  <li>檢查程式基底名稱是否不包含任何首字母縮寫字或縮寫，或是其首字母縮寫字或縮寫比完整名稱更熟為人知。</li>
+  <li>檢查程式基底是否不包含組織單位品牌名稱或抬頭等，除非該組織單位也是程式基底社群成員。</li>
+  <li>檢查程式基底儲存庫是否包含程式基底的簡短描述。</li>
+  <li>檢查程式基底有刊登在相關軟體型錄上。</li>
+  <li>檢查程式基底的網站有描述程式基底能夠解決的問題。</li>
+  <li>檢查以程式基底名稱來作搜尋時，有超過一個的常用主流搜尋引擎，都有將程式基底列在搜尋結果中。</li>
+  <li>檢查以自然語言來作搜尋，例如使用程式基底的簡短描述時，有超過一個的常用主流搜尋引擎，都將程式基底放在搜尋結果中。</li>
+  <li>檢查永久唯一識別碼條目有提及主要貢獻者。</li>
+  <li>檢查永久唯一識別碼條目中有包含儲存庫位置。</li>
+  <li>檢查永久唯一識別碼條目有列出程式基底網站。</li>
+  <li>檢查中介資料說明檔是機器可讀的格式。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>貢獻一段說明此程式基底作用的政策領域，或所處理問題的描述。</li>
+  <li>請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。</li>
+  <li>在相關會議上作簡報，介紹程式基底如何執行<a href="/glossary.html#policy">政策</a>。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>在決定專案名稱之前，先搜尋過商標資料庫，以避免名稱造成混淆或侵權的問題。</li>
+  <li>在引用到程式基底的地方，都使用簡短描述，例如放到社交媒體帳號中的說明。</li>
+  <li>為團隊編列內容設計與實作 SEO 搜尋引擎最佳化技能的預算。</li>
+  <li>確保專案參與人員出席相關會議，或作簡報介紹。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>實作搜尋引擎最佳化，例如加入<a href="https://www.sitemaps.org/protocol.html">網站地圖</a>。</li>
+  <li>在引用到程式基底的地方，都使用簡短描述，例如放到儲存庫中的說明。</li>
+  <li>請那些對程式基底不熟悉且不同領域背景的同事，來測試您的問題描述。</li>
+  <li>推薦適合出席或作簡報介紹的會議，並且在這些會議中出席或作簡報。</li>
+</ul>
+
+<p style="page-break-after: always;"></p>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>Wikidata 維基數據社群《<a href="https://www.wikidata.org/wiki/Wikidata:Introduction">維基數據簡
+介</a>》。</li>
+  <li>FSF 自由軟體基金會《<a href="https://directory.fsf.org/wiki/Main_Page">FSF 軟體目錄列表</a>》。</li>
+  <li>GO FAIR 國際支援與合作辦公室所撰寫的《<a href="https://www.go-fair.org/fair-principles/">FAIR 科學資料管理與監督指導原
+則</a>》，提供一份滿好的特性清單，解說哪些特性會讓資料（或中介資料）更容易讓
+機器採取行動（也因此更容易被找到）。其中的部分特性可直接套用到程式基底上，而其他無法直接套用的，我們還需要再研究程式基底與其對應的特性要怎麼處理。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-use-a-coherent-style.md">
+      <h1 id="風格要前後一致">風格要前後一致</h1>
+
+<p>採用前後一致的風格，讓不同環境的貢獻者能夠一同合作。用詞統一能減少貢獻者之間在溝通上的摩擦。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li><a href="/glossary.html#codebase">程式基底</a>「必須」遵守程式碼撰寫風格指引、或文件寫作風格指引，可以是程式基底社群自身的風格指引，或是程式基底
+有採用的既有風格。</li>
+  <li>貢獻內容「應該」通過自動化的風格測試。</li>
+  <li>風格指引「應該」描述對於較複雜的程式碼區段，如何作列內註解與為其寫下說明文件的期待。</li>
+  <li>「可選擇」是否將<a href="/criteria/use-plain-english.html">可理解的白話英語</a>期望加入風格指引之中。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認貢獻內容有遵循文件中指定的風格指引。</li>
+  <li>檢查是否有自動化的風格測試。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>為<a href="/glossary.html#policy">政策</a>與文件建立風格指引，遵守並且持續改善，同時記錄到程式基底文件中，像是「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或
+「<code class="language-plaintext highlighter-rouge">README</code>」檔案。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>將書面語言、原始碼、測試、政策標準等，包含在貴組織單位對品質的定義當中。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<p>如果程式基底還沒有工程指引，或其他貢獻者指引，則請先在<a href="/glossary.html#repository">儲存庫</a>中加入相關文件，像是
+「<code class="language-plaintext highlighter-rouge">CONTRIBUTING</code>」或「<code class="language-plaintext highlighter-rouge">README</code>」檔案，並描述目前在設立指引方面的進展。上述檔案的重要目的之一，在於宣達設計偏好、命名規則，以及機器不容易檢查
+的其他層面。指引應該包含貢獻的<a href="/glossary.html#source-code">原始碼</a>預期該符合哪些要求，才會被維護人員合併至程式基底中，包括原始碼、測
+試、文件等項目。請持續改善與擴充這份文件內容，目標讓文件朝向工程指引演進。</p>
+
+<p>此外：</p>
+
+<ul>
+  <li>使用 linter 程式碼品質梳理工具。</li>
+  <li>在程式基底中加入 linter 梳理工具的組態設定。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>維基百科上的《<a href="https://en.wikipedia.org/wiki/Programming_style">程式碼風格</a>》條目。</li>
+</ul>
+
+    </article>
+    
+    <article id="section-criteria-document-codebase-maturity.md">
+      <h1 id="記錄程式基底成熟度">記錄程式基底成熟度</h1>
+
+<p>清楚標示<a href="/glossary.html#codebase">程式基底</a>的成熟度，有助於他人決定是否要使用，或為該程式基底做出貢獻。程式基底版本的成熟度，包含其依賴項
+目的成熟度。瞭解程式基底演進到什麼程度，是理解該程式基底並知道如何做出貢獻的關鍵。</p>
+
+<h2 id="需求規定">需求規定</h2>
+
+<ul>
+  <li>程式基底「必須」註明版本編號。</li>
+  <li>程式基底「必須」明確以文件記錄，是否有已經準備好可供使用的版本。</li>
+  <li>準備好可供使用的程式基底版本，「必須」只能依賴其他也已經準備好可供使用的程式基底版本。</li>
+  <li>程式基底「應該」包含每次版本的變動紀錄，像是以「<code class="language-plaintext highlighter-rouge">CHANGELOG</code>」日誌格式檔記錄。</li>
+  <li>「應該」要以文件記錄分配版本識別碼的方法。</li>
+  <li>「可選擇」是否採用語意化版本控制編號。</li>
+</ul>
+
+<h2 id="測試方式">測試方式</h2>
+
+<ul>
+  <li>確認程式基底有版本編號策略，且有文件記載該策略。</li>
+  <li>確認政策制定者、管理人員、開發人員與設計師等，都能清楚知道程式基底是否有準備好可供使用的版本。</li>
+  <li>確認準備好可供使用的程式基底版本，並不依賴任何尚未準備好可供使用的其他程式基底的版本。</li>
+  <li>確認有文件記錄程式基底的版本編號方法，並且確實遵守。</li>
+  <li>確認是否有版本的變動紀錄。</li>
+</ul>
+
+<h2 id="公共政策制定者需要的工作">公共政策制定者：需要的工作</h2>
+
+<ul>
+  <li>制定<a href="/glossary.html#policy">政策</a>時，請記住任何開發出來的<a href="/glossary.html#source-code">原始碼</a>都必須先經過
+測試與改善，才能夠投入服務。</li>
+  <li>考慮將政策的變動註明版本編號，尤其是因而觸發新版本原始碼開發的情況。</li>
+</ul>
+
+<h2 id="管理人員需要的工作">管理人員：需要的工作</h2>
+
+<ul>
+  <li>要確認服務依賴的程式基底版本成熟度，等同或高於該服務本身。舉例來說，正式上線的服務不要使用 beta 公測版程式基底。</li>
+</ul>
+
+<h2 id="開發人員與設計師需要的工作">開發人員與設計師：需要的工作</h2>
+
+<ul>
+  <li>確認所有發行版，都有遵守程式基底的版本控制編號作法。</li>
+</ul>
+
+<h2 id="延伸閱讀">延伸閱讀</h2>
+
+<ul>
+  <li>許多程式基底使用「<a href="https://semver.org/">語意化版本編號規範</a>」來標示版本。</li>
+  <li><a href="https://en.wikipedia.org/wiki/Software_release_life_cycle">軟體發行生命週期</a></li>
+  <li>澳洲數位轉型局《<a href="https://www.dta.gov.au/help-and-advice/build-and-improve-services/service-design-and-delivery-process">服務設計與交付流
+程</a>》。</li>
+  <li>英國政府數位服務團《<a href="https://www.gov.uk/service-manual/agile-delivery">敏捷交付服務手冊</a>》。</li>
+</ul>
+
+    </article>
+    
+
+  <article id="section-contributing">
+
+    <h1 id="貢獻此標準">貢獻此標準</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>🙇‍♀️ 感謝您的貢獻！</p>
+
+<p>我們理解這樣的標準，只有在盡可能與公共技術人員、政策制定者，以及有興趣的人士協作下才能完成。因此，我們很感謝您的意見，樂意得到回饋，以及歡迎提供改善此專案的建議。我
+們非常開放任何合作的機會。</p>
+
+<p>我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件寄送到
+<a href="mailto:info@publiccode.net">info@publiccode.net</a>。</p>
+
+<h2 id="問題建議與議題等">問題、建議與議題等</h2>
+
+<p>在<a href="/docs/roadmap.html">發展路線圖</a>中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 <a href="https://github.com/publiccodenet/standard/issues">Standard
+for Public Code 的 GitHub
+Issue</a> 頁面中，為本專案<a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue">提出 GitHub 議
+題</a>。</p>
+
+<p>或者，註冊加入<a href="https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/">郵遞論壇列
+表</a>，
+並寄送電子郵件到<a href="mailto:standard@lists.publiccode.net">standard@lists.publiccode.net</a>。</p>
+
+<p>您不一定要修改我們的程式碼或文件，也能成為貢獻者！</p>
+
+<h2 id="為文件與程式碼提出拉取請求">為文件與程式碼提出拉取請求</h2>
+
+<p>如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull Request，亦可簡稱 PR)。</p>
+
+<p>若您從未使用過 GitHub，歡迎先<a href="https://docs.github.com/en/get-started/quickstart/github-flow">認識 GitHub 作業流
+程</a>，或是參加 <a href="https://skills.github.com/">GitHub
+Skills</a> 免費且優質的互動式課程，當中會介紹該如何使用 GitHub 以及 MarkDown 語法。
+MarkDown 是本專案文件所採用的撰寫語法。</p>
+
+<p>本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可以
+任意使用。</p>
+
+<h3 id="1-作出您的修改">1. 作出您的修改</h3>
+
+<p>貢獻內容應該<a href="/docs/standard-for-public-code.html">遵守</a>《公共程式標準》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合
+<a href="/foreword.html#values-of-public-code">公共程式的價值</a>。此外，他們也會審查貢獻是否遵循<a href="#standards-to-follow">標
+準</a>，且與整體作品有所連貫。</p>
+
+<p>本專案使用 <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow 分支與工作流程</a>。
+當您對此儲存庫作分支以後，請務必依照 GitFlow 模型建立新功能分支。</p>
+
+<p>將您所作的變更內容加入送交版次，<a href="https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message">並附上內容說
+明</a>。如果需要作
+出多種類型的變更，請將相關變更依據邏輯分類，不同類型各自放在不同的送交版次中。例如：修正空白、以及文字內容更動，兩者應該放在不同的送交版次中。當新增檔案時，請選用
+容易以「<code class="language-plaintext highlighter-rouge">diff</code> 」檢視的檔案格式，如「<code class="language-plaintext highlighter-rouge">.svg</code> 」格式就勝過二進位影像。在送交版次訊息中，請記錄您所作的選擇與決策，如此未來其他人都能知道您當時的抉
+擇。</p>
+
+<p>如果您是要新增程式碼，請確保您有新增與更新相關文件與測試項目，之後再提交您的拉取請求。請務必撰寫可以展示新增或修改後程式碼行為的測試項目。</p>
+
+<h4 id="適用政策">適用政策</h4>
+
+<p>就目前而言，《公共程式標準》並非在執行任何特定的公共政策。</p>
+
+<h4 id="風格">風格</h4>
+
+<p>《公共程式標準》目標<a href="/criteria/use-plain-english.html">使用白話的英語</a>，而拼字採用美式英文。文字內容基本上以每句一行為原則，沒有文繞圖
+換行，來讓「<code class="language-plaintext highlighter-rouge">diff</code>」輸出更容易檢視。然而，我們想要強調更重要的是，您應該專注在貢獻內容上，而不是擔心拼字與排版。我們的審查流程會協助修正這一部分，也會另外再次檢查品質才<a href="/docs/releasing.html">推出新發行版本</a>。</p>
+
+<h4 id="遵守的標準">遵守的標準</h4>
+
+<p>這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。</p>
+
+<ul>
+  <li><a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119</a> - 要求等級關鍵字</li>
+  <li><a href="https://www.w3.org/TR/WCAG21/#readable">網頁內容可近用無障礙指引 2.1</a> - 易讀性</li>
+</ul>
+
+<h3 id="2-拉取請求">2. 拉取請求</h3>
+
+<p>當您提出拉取請求時，請隨附描述您想要解決的問題，以及該拉取請求所能修正的議題編號。以一個拉取請求處理單一項議題為佳。若一組變動能同時解決多項議題，則請列出所有能一併
+修正的議題編號。</p>
+
+<h3 id="3-改善">3. 改善</h3>
+
+<p>所有貢獻都必須接受審查。Foundation for Public Code 致力於確保有維護人員能審查貢獻內容，目標是在兩個工作日內提供意見回饋。</p>
+
+<p>維護人員有時候可以立即合併您的貢獻內容。不過一般來說，新的拉取請求通常需要再經過改善後，才能夠合併。其他貢獻者（或是輔助用機器人）可能會提供意見回饋。若是如此，負責
+審查您貢獻內容的維護人員，將協助您改善文件與程式碼。</p>
+
+<p>一旦您的文件與程式碼通過人工審查，就會合併。</p>
+
+<h3 id="4-慶祝">4. 慶祝</h3>
+
+<p>您的構想、文件與程式碼，已成為本專案的一部份。您就是我們需要的開放原始碼英雄！</p>
+
+<p>誠摯歡迎您提出拉取請求，將您的名字加到 <a href="/AUTHORS.html"><code class="language-plaintext highlighter-rouge">AUTHORS</code></a> 檔案中，讓您所做的貢獻能銘記在本專案中。</p>
+
+<h2 id="翻譯成其他語言">翻譯成其他語言</h2>
+
+<p>《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的<a href="https://github.com/publiccodenet/community-translations-standard">社群翻譯</a>，或是新增翻譯。</p>
+
+<h2 id="發行版本">發行版本</h2>
+
+<p>我們有提供<a href="/docs/releasing.html">發行新版本</a>，與<a href="/docs/printing.html">訂購印刷版標準</a>的專用詳細文件。</p>
+
+<p>若要進一步瞭解如何使用，以及協助貢獻本專案，請參閱 <a href="/README.html"><code class="language-plaintext highlighter-rouge">README </code></a>。</p>
+
+
+  </article>
+
+  <figure>
+      <img src="/assets/collaborative-development.svg" alt="collaborative-development">
+    </figure>
+
+  <article id="section-code-of-conduct">
+
+    <h1 id="行為守則">行為守則</h1>
+
+<!-- SPDX-License-Identifier: CC0-1.0 -->
+<!-- SPDX-FileCopyrightText: 2021-2022 The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
+
+<p>社群很多成員來自有行為守則的公民社會或專業背景，但有些人並非如此。本文件表達基金會對於所有社群成員，以及所有互動間的期望，無論互動是透過何種溝通管道。</p>
+
+<p>來到這裡來是為了協作。</p>
+
+<p>請對彼此體貼、尊重，以及有耐心。</p>
+
+<p>努力做出有建設性的行為。</p>
+
+<p>若有問題需要提出，請寄送電子郵件到 directors@publiccode.net。</p>
+
+
+  </article>
+
+  <figure>
+    <img src="/assets/collaboration.svg" alt="collaboration">
+  </figure>
+
+  <article id="section-governance">
+
+    <h1 id="治理方式">治理方式</h1>
+
+<p>本標準是 <a href="https://publiccode.net/">Foundation for Public Code</a> 在為程式基底提供督導時的核心。我們依照這份文件來判斷，某個程式基底是否已經準備好讓社群共同參與開發。</p>
+
+<p>這份標準由 Foundation for Public Code 職員負責維護。</p>
+
+<p><a href="/CONTRIBUTING.html">我們歡迎任何人貢獻，例如提供修改建議，或是給予一般意見回饋等。</a></p>
+
+<p>由於《公共程式標準》在我們的核心流程中，扮演至關重要的角色，所以我們會以《公共程式標準》的最高標準作要求。</p>
+
+<p>我們會努力儘速回覆所有拉取請求。拉取請求使我們有機會一起合作，來改善我們的方法與這份標準。我們有可能不會接受貢獻者提出的所有修改，而我們會解釋背後的邏輯。</p>
+
+
+  </article>
+
+  <figure>
+    <img src="/assets/eco-system.svg" alt="ecosystem">
+  </figure>
+
+  <article id="section-changelog">
+
+    <h1 id="版本歷史">版本歷史</h1>
+
+<h2 id="071-版">0.7.1 版</h2>
+
+<p>2023/07/31: 💄 第十六版草稿修改準則名稱，並釐清程式 code 的稱呼。</p>
+
+<ul>
+  <li>〈程式碼要可重複使用且可攜〉準則改名為〈程式基底要可重複使用且可移植〉。</li>
+  <li>新增詞彙條目「原始碼」。</li>
+  <li>對於只適用於「原始碼」意義的「程式 (code)」，現在明確以「原始碼」稱呼。</li>
+  <li>將「運作的程式碼」釐清稱為「軟體」。</li>
+  <li>細微修改以清楚區分「程式碼」與「程式基底」。</li>
+  <li>簡化給政策制定者在〈政策與原始碼要合捆〉中的指引。</li>
+  <li>釐清〈程式基底可查詢得到〉與〈程式基底要可重複使用且可移植〉的「測試方式」小節。</li>
+  <li>在發行成品前的要求中，加入準則與需求規定檢查清單。</li>
+  <li>提升發行流程的自動化程度。</li>
+</ul>
+
+<h2 id="070-版">0.7.0 版</h2>
+
+<p>2023年5月31日：📑第十五版新增紀錄募資審查的新規定，並釐清審查流程規定。</p>
+
+<ul>
+  <li>新增規定，記錄預期由何者負擔審核貢獻內容所需的開銷費用。</li>
+  <li>新增規定，程式基底必須要有簡短說明。</li>
+  <li>原先專注在貢獻內容是否遵循標準，現在則改為注重貢獻內容的審查。</li>
+  <li>將〈程式基底可查詢得到〉中許多「必須」等級的規定，調降為「應該」等級。</li>
+  <li>審查範本現在有 HTML 格式。</li>
+  <li>「前言」轉換為「序文」。</li>
+  <li>改善貢獻指引。</li>
+  <li>改善命令稿文件紀錄。</li>
+</ul>
+
+<h2 id="060-版">0.6.0 版</h2>
+
+<p>2023年4月20日：🔀第十四版草稿新增可移植性與測試的規定，並且每個準則都有一段前言。</p>
+
+<ul>
+  <li>新增規定，在〈程式碼要可重複使用且可攜〉加入多方協作開發的內容。</li>
+  <li>新增規定，在〈程式碼要可重複使用且可攜〉中加入依賴單一供應商的內容。</li>
+  <li>新增規定，在〈使用持續整合〉中加入要發布自動化測試結果的內容。</li>
+  <li>對安全性區分出兩項規定，一是要有提供方法，另一個是要有文件紀錄。</li>
+  <li>重新撰寫規定，將焦點放在程式基底，而非貢獻者行為。</li>
+  <li>移除「此措施辦不到的事」以及「此措施為何重要」兩個小節，改換成在每項準則中加入前言。</li>
+  <li>在本標準前言中，加入通用的「此措施辦不到的事」小節。</li>
+  <li>為政策制定者加入相關政策與授權相容性的指引。</li>
+  <li>為開發人員與設計師新增檔案要有版本控制的相關指引。</li>
+  <li>為開發人員與設計師釐清有關快速回應，以及搜尋引擎最佳化的內容。</li>
+  <li>新增可近用性無障礙環境的「延伸閱讀」內容。</li>
+  <li>將各準則的連結與其名稱連動。</li>
+  <li>改善網頁版的導覽功能。</li>
+  <li>已將「延伸閱讀」小節的工具移到社群實踐指引。</li>
+  <li>將標準依循或認證相關流程移到 <a href="https://publiccode.net">publiccode.net</a>。</li>
+  <li>變更審查範本格式，讓範本在發行新版後更容易更新。</li>
+  <li>改善著陸引導頁文字，加入相關資源的連結。</li>
+  <li>新增拼字檢查自動化測試。</li>
+  <li>微調文字，讓內容更明確與一致。</li>
+  <li>將 SPDX 標頭換成 yaml 標頭。</li>
+</ul>
+
+<h2 id="050-版">0.5.0 版</h2>
+
+<p>2023年1月25日：🎨第十三版草稿焦點著重在文件紀錄風格指引。</p>
+
+<ul>
+  <li>調整程式碼撰寫風格要求，專注於程式基底上，而非貢獻者行為。</li>
+  <li>將程式基底名稱規定，從〈使用白話的英文〉移到〈程式基底可查詢得到〉。</li>
+  <li>將測試程式碼的規定，從〈程式碼要有文件〉移到〈使用持續整合〉。</li>
+  <li>劃分機器可讀的測試標準規定，指明程式碼的開放性比可測試性更重要。</li>
+  <li>調整可查找性的測試規定，降低對搜尋引擎演算法的依賴。</li>
+  <li>微調文字，讓內容更明確與一致。</li>
+</ul>
+
+<h2 id="041-版">0.4.1 版</h2>
+
+<p>2022年12月5日：📝第十二版草稿指出要以文件記錄成熟度。</p>
+
+<ul>
+  <li>寫下成熟度著重於程式基底是否已經可供使用，更甚於版本編號。</li>
+  <li>寫下成熟度不再需要為尚未準備好可供使用的程式基底加上特定標籤。</li>
+  <li>稽核流程圖現在以更容易轉譯的格式生成。</li>
+  <li>改善「測試方式」指引。</li>
+  <li>新增 publiccode.yml 檔案。</li>
+  <li>新增審查範本。</li>
+  <li>一致性連結詞彙表。</li>
+  <li>在「CONTRIBUTING」中加入要遵循的實務與標準。</li>
+  <li>將 Matti Schneider 加入作者群。</li>
+  <li>將剩餘 SPDX 標頭加入檔案中。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>更新部分超連結。</li>
+  <li>將範例移動到《<a href="https://publiccodenet.github.io/community-implementation-guide-standard/">社群實踐指
+引</a>》。</li>
+</ul>
+
+<h2 id="040-版">0.4.0 版</h2>
+
+<p>2022年9月7日：🔭第十一版草稿新增可查找性準則。</p>
+
+<ul>
+  <li>導入新準則：程式基底可查詢得到。</li>
+  <li>改善多數準則的「測試方式」小節。</li>
+  <li>在〈歡迎貢獻者〉中加入發布活動統計的新規定。</li>
+  <li>移除可重複使用與移植的程式碼中多餘的規定。</li>
+  <li>在開放授權的定義中，加入 OSI 與 FSF 所批准的授權。</li>
+  <li>重新編寫「得以」等級的相關規定，加入使用「可選擇」這個關鍵字，讓規定更明確。</li>
+  <li>表達《公共程式標準》應該盡可能符合其自身規定的立場，並加入評估措施。</li>
+  <li>將 SPDX 授權識別碼加入檔案中。</li>
+  <li>導入新的行為守則。</li>
+  <li>解釋原始碼與政策內文的差異。</li>
+  <li>將規定重新調整為項目要點清單格式。</li>
+  <li>告知程式基底成熟度對於重複使用時的重要性。</li>
+  <li>將可查找性相關規定移動到新準則中。</li>
+  <li>釐清非開放標準在程式基底中的角色。</li>
+  <li>加入組建日期與執行時期依賴項目的額外指引。</li>
+  <li>新增《公共程式標準》的發展路線圖。</li>
+  <li>更新 Authors 檔案的結構。</li>
+  <li>將唐鳳加入作者群。</li>
+  <li>將準則列表加到印刷版本中。</li>
+  <li>釐清標準對於政策制定者、管理人員、開發人員與設計師等不同身分間的意義。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>更新部分超連結。</li>
+</ul>
+
+<h2 id="030-版">0.3.0 版</h2>
+
+<p>2022年5月23日：🗎第十版草稿加強文件紀錄與在地化內容。</p>
+
+<ul>
+  <li>在〈程式碼要可重複使用且可攜〉中定下明確的在地化規定。</li>
+  <li>以文件記錄治理方式的規定，從「應該」等級調升為「必須」。</li>
+  <li>在貢獻指引中，將非常主觀（且難以驗證）的「貢獻內容『必須』小」的規定，改為必須紀錄貢獻所要完成的期待，並一次專注在單一議題上。</li>
+  <li>社群翻譯連結現在已放到頁尾中。</li>
+  <li>還原「用 Mermaid 流程圖取代業務流程 BPMN svg」。</li>
+  <li>細微調整用詞，讓句子更簡單。</li>
+  <li>更新部分超連結。</li>
+</ul>
+
+<h2 id="023-版">0.2.3 版</h2>
+
+<p>2022年3月15日：📜第九版草稿允許缺少官方翻譯的政策，改為提供政策的英文版摘要。</p>
+
+<ul>
+  <li>放寬〈使用白話的英文〉準則，加入新規定，允許合捆的政策內文如果沒有英文版，只需要加入英文版摘要，而不用翻譯全文。</li>
+  <li>同樣地，在〈政策與原始碼要合捆〉中，沒有英文版的政策內文可允許提供英文版摘要。</li>
+  <li>釐清〈政策與原始碼要合捆〉中，「政策」包含能影響開發與部署的流程。</li>
+  <li>在〈程式碼要可重複使用且可攜〉中強調解決方案部分內容的可重複使用性。</li>
+  <li>將〈程式碼要可重複使用且可攜〉當中的開發人員與設計師指引，加入部署到專有平台上的內容。</li>
+  <li>在〈使用白話的英文〉中，加入管理層在面對非英語詞彙時需要做的事的提點。</li>
+  <li>變更拉取請求流程圖，從業務流程 BPMN 改用 Mermaid，來讓<a href="https://github.com/publiccodenet/community-translations-standard">社群翻
+譯</a>更容易。</li>
+  <li>將 Maurice Hendriks 加入作者群。</li>
+  <li>將「OpenApi 規格」加入延伸閱讀。</li>
+  <li>將延伸閱讀小節的特性變得更明確。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="022-版">0.2.2 版</h2>
+
+<p>2021年11月29日：🏛第八版草稿認知程式碼所執行的政策，不一定是英文。</p>
+
+<ul>
+  <li>在「所有程式碼都必須使用英語編寫」規定中，雖然政策也算是一種程式 (code)，但可以保有例外。</li>
+  <li>在〈維護版本控制〉中，新增與送交者電子郵件相關的「得以」規定。</li>
+  <li>將政策制定者加入〈政策與原始碼要合捆〉指引中。</li>
+  <li>將開發人員與設計師加入「風格要前後一致」指引中。</li>
+  <li>新增「不同情境」到詞彙表中。</li>
+  <li>將 Mauko Quiroga 與 Charlotte Heikendorf 加入 AUTHORS。</li>
+  <li>新增「數位公共財」認可標章。</li>
+  <li>為「準則」頁面網頁版加入「上一頁」與「下一頁」連結。</li>
+  <li>將「開放標準」原則加入延伸閱讀。</li>
+  <li>將「白話語言定義」加入延伸閱讀。</li>
+  <li>將「語意化版本編號規範」移動為延伸閱讀參考內容。</li>
+  <li>指出 publiccode.yml 是機器可讀中介資料說明的範例之一。</li>
+  <li>將「您的程式基底」與「您的組織單位」改為較不具有所有格的寫法。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+  <li>新增印刷版的製作指示。</li>
+</ul>
+
+<h2 id="021-版">0.2.1 版</h2>
+
+<p>2021年3月1日：🧽第七版草稿是 0.2.0 版後的些微清理改善。</p>
+
+<ul>
+  <li>新增使用分散式版本控制系統的相關「應該」規定，並解釋分散式的重要性。</li>
+  <li>針對未被採用的貢獻需要給予回饋，規定要比被接受的貢獻更加嚴格。</li>
+  <li>明確指出著作權與授權聲明也應該要機器可讀。</li>
+  <li>聲明是否為機器可讀的測試方式建議。</li>
+  <li>釐清滾動發行的指引。</li>
+  <li>釐清詞彙表中「版本控制」的定義。</li>
+  <li>新增鼓勵貢獻、SPDX、Git 以及審查貢獻等的延伸閱讀項目。</li>
+  <li>新增有關公共程式概念的影片連結。</li>
+  <li>更新業務流程 BPMN 連結。</li>
+  <li>減少重複連結。</li>
+  <li>將 Alba Roza 與 Ngô Ngọc Đức Huy 加入作者群。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="020-版">0.2.0 版</h2>
+
+<p>2020年10月26日：🎊第六版草稿拆分出一項新規定並且釐清內容。</p>
+
+<ul>
+  <li>將〈歡迎貢獻〉準則拆分為〈貢獻要容易〉以及〈歡迎貢獻者〉。</li>
+  <li>將〈注意程式基底成熟度〉準則改名為〈記錄程式基底成熟度〉。</li>
+  <li>針對多方使用的程式基底，將「必須」等級規定調降為「應該」。</li>
+  <li>針對著作權轉讓，新增「禁止」規定。</li>
+  <li>在可重複使用程式碼的規定中，釐清組態設定的角色。</li>
+  <li>新增詞彙：持續整合、政策、儲存庫、版本控制等。</li>
+  <li>將「城市」替換成「公家機關」。</li>
+  <li>將貢獻者與審查人員規定分開為不同項目，以釐清程式碼中較敏感性的層面。</li>
+  <li>將政策制定者、開發人員與設計師加入延伸閱讀與指引中。</li>
+  <li>將 Felix Faassen 與 Arnout Engelen 加入作者群。</li>
+  <li>再稍微修改些文字，讓文字更明確。</li>
+</ul>
+
+<h2 id="014-版">0.1.4 版</h2>
+
+<p>2019年11月27日：🧹第五版草稿主要是一些細部修正。</p>
+
+<ul>
+  <li>連結 License.md 檔案。</li>
+  <li>將 Sky Bristol、Marcus Klaas de Vries 與 Jan Ainali 加入作者群。</li>
+  <li>讓標點符號使用更一致，特別是項目符號列表。</li>
+  <li>細部調整文字，讓內容更明確。</li>
+</ul>
+
+<h2 id="013-版">0.1.3 版</h2>
+
+<p>2019年10月8日：🍂第四版草稿僅針對秋季所作的清理修正一些小地方</p>
+
+<ul>
+  <li>將「持續交付」改名為「持續整合」。</li>
+  <li>在語言標準中引用無障礙指導原則。</li>
+  <li>改善一些樣式，與一致性修正。</li>
+</ul>
+
+<h2 id="012-版">0.1.2 版</h2>
+
+<p>2019年8月22日：🌠第三版草稿專注在提升文字品質，並且納入社群意見</p>
+
+<ul>
+  <li>有好幾位很棒的新貢獻者加入我們的作者群名單，讓氣象一新。</li>
+  <li>所有連結都是 HTTPS。</li>
+  <li>一般校對、釐清用字淺詞、修正拼字錯誤等。</li>
+  <li>更新準則：
+    <ul>
+      <li>在不同情境背景下重複使用的規定</li>
+      <li>明確的版本控制建議</li>
+      <li>多方部署的建議</li>
+      <li>檔案授權標頭的建議</li>
+      <li>漏洞回報的建議</li>
+      <li>明確以文件記錄治理方式的建議</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="011-版">0.1.1 版</h2>
+
+<p>2019年5月9日：🤔第二版草稿修正一些基本的疏漏，以及許多拼字錯誤</p>
+
+<ul>
+  <li>移除出現「Foundation for Public Code」的地方，我們之後可能必須改名才能成為協會。</li>
+  <li>更新簡介。</li>
+  <li>更新詞彙表。</li>
+  <li>新增行為守則。</li>
+  <li>我們建議使用 publiccode.yml 標準，方便重複使用。</li>
+</ul>
+
+<h2 id="010-版">0.1.0 版</h2>
+
+<p>2019年4月16日：🎉初版草稿已準備就緒，全新內容，而且有許多有趣的新穎理念</p>
+
+<ul>
+  <li>14 項準則，有各自的規定，以及相關的實施方式。</li>
+  <li>精要的背景介紹，例如本標準是什麼，以及 Foundation for Public Code 如何使用此標準。</li>
+</ul>
+
+<p>最初的版本是由阿姆斯特丹應用科學大學、阿姆斯特丹市政府，以及本基金會合作撰寫，取自 <a href="https://smartcities.publiccode.net/">Smart Cities? Public Code! 專
+案</a> 的部分內容。</p>
+
+
+  </article>
+
+  <article id="section-license">
+
+    <p>This license is the legal contract that allows anyone to do anything they like with the content in this entire document.</p>
+    <h1>CC0 1.0 Universal</h1>
+    <pre>Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
+</pre>
+
+  </article>
+
+</body>
+</html>

From 5be87a008de9e354b0f1f93ce5517bb6b55be159 Mon Sep 17 00:00:00 2001
From: Moda / L10n Project <147604016+moda-l10n@users.noreply.github.com>
Date: Thu, 7 Dec 2023 21:25:41 +0800
Subject: [PATCH 71/71] Update README.md

Add wiki refer link in README
---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index 46f2ac2c..6d346696 100644
--- a/README.md
+++ b/README.md
@@ -108,3 +108,7 @@ script/pdf.sh
 
 本標準採用 CC0 公眾領域貢獻宣告[給予授權](LICENSE)，該授權範圍涵蓋所有插圖與文件。CC0 代表任何人都能任意使用這些內容。如果您是貢獻者，代表您也將
 這些權利賦予他人。若要進一步瞭解如何協助本專案，請參閱〈[貢獻指引](CONTRIBUTING.md)〉。
+
+## 軟體中文化
+
+本專案為數位部開放原始碼軟體中文化專案項目之一，其中文化與專案應用可參考 [Wiki](https://github.com/moda-gov-tw/publiccodenet.standard/wiki)。