storage-backups/one-among-us-data
storage-backups/one-among-us-data
1
0
Fork 0
mirror of https://github.com/one-among-us/data.git synced 2024-11-23 11:37:37 +08:00
Code Releases Activity
Data repo for one-among.us
1,307 Commits 9 Branches 0 Tags 299 MiB
TypeScript 95.7%
Python 2.5%
Shell 1.5%
HTML 0.3%
60bcdad365
Go to file
One Among Us (Bot) 60bcdad365 [+] Comment added by Ast6034 for SS3B_0016
2024-01-13 13:58:16 -05:00
.github/workflows [F] Restore GitHub branch deploy 2023-01-21 12:20:25 +08:00
people [+] Comment added by Ast6034 for SS3B_0016 2024-01-13 13:58:16 -05:00
public [+] Meta image CDN 2023-01-05 06:27:05 -05:00
scripts [U] remove unused dependency 2024-01-05 23:46:54 +08:00
.gitattributes [O] Auto LF ending 2022-06-24 14:22:56 -04:00
.gitignore [M] serve english page data 2023-03-14 09:23:55 +00:00
info-i18n.yml [F] Fix info i18n mismatch between web and data 2023-07-15 08:33:29 +08:00
netlify.toml [U] Change netlify to build preview 2023-01-06 01:27:59 -05:00
package.json [U] remove unused dependency 2024-01-05 23:46:54 +08:00
README.md [F] Patch 15 minor formatting issues (#86) 2023-01-27 01:18:33 -05:00
tsconfig.json [+] Add yarn subcommands 2023-01-06 01:27:18 -05:00
yarn.lock [U] remove unused dependency 2024-01-05 23:46:54 +08:00

README.md

Our Data

这里存了 One Among Us 的条目，欢迎贡献！

在贡献之前请阅读我们的 文档和贡献指南。

Please read our How-We-Work before contributing.

GitHub Repo 结构

  • data - 条目内容存储
  • web - 网页前端源码
  • backend - 献花和编辑后端源码

文件结构

  • Directory /people/<userid>/: Data for a specific person

    • info.json5: Profile information
    • page.md: Profile page content
    • photos: Photo directory
    • comments: List of comments made by other users in the format of yyyy-mm-dd-{name}-{id}.txt

  • Branch gh-pages: Data that's automatically generated by Github Actions

    • people-list.json: A list of all people currently in the repository
    • Directory /people/<userid>/: Built data for a specific person
      • page.js: page.md built with MDX

多语言

我们正在尝试重新编写网站的多语言架构，以使其更通用，更新的方式更简洁。在这段过渡时期里，请大家尽量把简体中文作为底稿，并且用自动转换或者手动校对的方式生成繁体文稿。在新的多语言架构编写完成后，我们会重新校对所有繁体文稿。