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-22 19:24:51 +08:00
Code Releases Activity
Data repo for one-among.us
435 Commits 9 Branches 0 Tags 299 MiB
TypeScript 95.7%
Python 2.5%
Shell 1.5%
HTML 0.3%
26b86abaf5
Go to file
Azalea Gui 26b86abaf5
Revert "[F] Fix suzuki's profile picture" 
This reverts commit 3333078de5.
2023-01-05 04:04:30 -05:00
.github/workflows [F] Fix gh permissions 2022-12-30 20:20:07 -05:00
people Revert "[F] Fix suzuki's profile picture" 2023-01-05 04:04:30 -05:00
public [+] .nojekyll - Faster github pages deploy speed 2022-04-08 22:37:05 -04:00
scripts [O] Copy page.md in build 2023-01-04 15:52:49 -05:00
.gitattributes [O] Auto LF ending 2022-06-24 14:22:56 -04:00
.gitignore [+] Telegram backup for 蛍 2022-12-23 16:26:41 -05:00
docker-compose.yml [U] dockerize 2022-12-03 02:37:04 -05:00
Dockerfile [F] Fix git config 2022-12-30 14:49:16 -05:00
info-i18n.yml [O] New format 2022-12-02 19:16:43 -05:00
package.json [+] Server-side autocorrect 2022-12-24 11:27:06 -05:00
README.md [U] dockerize 2022-12-03 02:37:04 -05:00
requirements.txt [+] zh-hant convert 2022-11-16 01:04:03 -05:00
tsconfig.json [U] Migrate to MDX 2022-03-21 00:55:53 +08:00
yarn.lock [+] Server-side autocorrect 2022-12-24 11:27:06 -05:00

README.md

Our Data

这里存了 one-among.us 的条目，欢迎贡献！

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

生成/更新繁体文稿

更新简体文稿之后请手动执行一个脚本生成繁体文稿。（因为 Github Actions 奇怪的问题太多了，还好难测试，还是换成本地构建啦）

构建环境需要安装 docker, 然后 docker-compose up 就可以更新繁体了!

这个脚本不会覆盖在已有的繁体文件上的更改，更新已经生成过繁体的简体文稿之后会自动合并，不过还是要手动检查一下哦。