publiccodenet · moda-l10n · Nov 24, 2022 · Nov 24, 2022 · Dec 1, 2022 · Dec 1, 2022
diff --git a/.gitignore b/.gitignore
@@ -12,4 +12,4 @@ urls.txt
 release.body
 *.orig
 node_modules/
-package-lock.json
+package-lock.json
diff --git 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:[email protected]) so we'll be able to help you out, as well as correct our mistake.
+若網址正確，或您是按下連結或按鈕來的，請寫信給 [Foundation for Public Code 員
+工](mailto:[email protected])，讓我們協助您，並同時修正我們的錯誤。
diff --git a/AUTHORS.md b/AUTHORS.md
@@ -2,36 +2,38 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]>, https://standard.publiccode.net/AUTHORS
 ---
-# Authors
 
-* 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
-* Audrey Tang, [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
+* Edo Plantinga，[Code For NL](https://codefor.nl/)
+* 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
-* Johan Groenen, Code For NL
+* Jan Ainali，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，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, Gemeente Amsterdam
+* Tamas Erkelens，阿姆斯特丹市政府
 * Timo Slinger
diff --git a/CC0-1.0.md b/CC0-1.0.md
@@ -7,12 +7,12 @@ redirect_from:
     - LICENSE.html
 ---
 
-# Creative Commons 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>
 
-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
diff --git 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 <[email protected]>, 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 [email protected].
+若有問題需要提出，請寄送電子郵件到 [email protected]。
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,103 +1,100 @@
-# Contributing to this standard
+# 貢獻此標準
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2019-2022 The Foundation for Public Code <[email protected]>, 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 <[email protected]>.
+我們歡迎每個人提出的議題，以及拉取請求。如果您不大習慣 GitHub ，也歡迎將意見回饋用電子郵件寄送到
+[[email protected]](mailto:[email protected])。
 
-## 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)中可查看我們勾勒的精要概覽。歡迎回報問題、建議修改，以及發問等，來協助發展。您可以到 [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)。
 
-Or, sign up to the [mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) and send an email to
-[[email protected]](mailto:[email protected]).
+或者，註冊加入[郵遞論壇列
+表](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/)，
+並寄送電子郵件到[[email protected]](mailto:[email protected])。
 
-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.
+如果您想要在我們的專案中，為文件或程式碼加入新內容，您應該提出拉取請求 (Pull Request，亦可簡稱 PR)。
 
-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 作業流
+程](https://docs.github.com/en/get-started/quickstart/github-flow)，或是參加 [GitHub
+Skills](https://skills.github.com/) 免費且優質的互動式課程，當中會介紹該如何使用 GitHub 以及 MarkDown 語法。
+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.
+本專案採用創用CC 0 1.0 通用式公眾領域貢獻宣告給予授權；這本質上代表本專案，以及您所做出的貢獻，在無論何種司法管轄情況下，都屬於公眾領域，也就是任何人都可以
+任意使用。
 
-### 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)《公共程式標準》自身所列出的準則規定。審查人員同時也會確保貢獻內容，符合
+[公共程式的價值](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.
+就目前而言，《公共程式標準》並非在執行任何特定的公共政策。
 
-#### 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).
+《公共程式標準》目標[使用白話的英語](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.
+這些是《公共程式標準》所採用的標準。請確保您的貢獻內容也遵守這些標準，才會更容易合併。
 
-* [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.
+所有貢獻都必須接受審查。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).
+《公共程式標準》沒有官方版本的翻譯，您仍可以協助本標準維護已有的[社群翻譯](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/Dockerfile 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
+