bitsocialnet/bitsocial-web

最近记录的来源活动: 2026年10月6日 23:19

SkillsMP 收录数据更新: 2026年11月5日 19:57

已收集 skills: 37

GitHub 星标: 1
GitHub Forks: 1

用 AI 助手安装

复制这段 Prompt，发给你正在使用的 AI 助手。

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/bitsocialnet/bitsocial-web.

仓库 README

仓库 README 来源：README.md

查看 README 源文件

展开完整 README

[![License](https://img.shields.io/badge/license-AGPL--3.0--or--later-blue.svg)](https://github.com/bitsocialnet/bitsocial-web/blob/master/LICENSE) [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/) # Bitsocial Web Bitsocial Web is the public web monorepo for Bitsocial. It currently serves: - `https://bitsocial.net/` for the public Bitsocial landing/about site - `https://chain.bitsocial.net/` for the Bitsocial Chain landing site (BSO token and L2 appchain) - `https://docs.bitsocial.net/` for Docusaurus docs - `https://stats.bitsocial.net/` for the live network stats dashboard Chain, docs, and stats are served on their own subdomains while remaining in this monorepo. Legacy `/docs` and `/stats` paths on `bitsocial.net` redirect permanently to their dedicated subdomains. ## Repo Layout ```text about/ Public Bitsocial landing/about site chain/ Bitsocial Chain landing site (BSO token and L2 appchain) docs/ Docusaurus docs, i18n files, and contributor playbooks stats/ Stats dashboard, monitor, Prometheus, Grafana, Docker Compose, and deploy config scripts/ Shared repo scripts and agent hooks ``` Each top-level subproject has its own local documentation: - [`about/README.md`](./about/README.md) - [`chain/README.md`](./chain/README.md) - [`docs/README.md`](./docs/README.md) - [`stats/README.md`](./stats/README.md) The `chain/` workspace is a standalone Vite app for the Bitsocial Chain marketing site. Run it with `corepack yarn start:chain` or build it with `corepack yarn build:chain`. The repo root remains the orchestration layer for installs, verification, and cross-project commands. ## Getting Started Use the pinned Node.js version from [`.nvmrc`](./.nvmrc) and Yarn 4 via Corepack. ```bash nvm install && nvm use corepack enable corepack yarn install ``` The main local URL is: - `https://bitsocial.localhost` Portless keeps a stable named local URL. On non-`master` branches, the repo can fall back to a branch-scoped `*.bitsocial.localhost` route so parallel worktrees do not collide. ## Common Commands ```bash corepack yarn start corepack yarn start:stats corepack yarn start:stats-web corepack yarn start:android-usb corepack yarn start:ios-sim corepack yarn llms:generate corepack yarn build:verify corepack yarn build corepack yarn docs:build:verify corepack yarn lint corepack yarn typecheck corepack yarn format:check corepack yarn doctor corepack yarn build:stats-dashboards corepack yarn build:stats-web corepack yarn stats:up corepack yarn stats:down corepack yarn stats:logs ``` ## Verification Before committing code changes, run: ```bash corepack yarn build:verify corepack yarn lint corepack yarn typecheck corepack yarn format:check ``` Use `corepack yarn build` only when you intentionally need the full production build, including the multi-locale docs output. If you changed React UI logic in `about/src/**`, also run: ```bash corepack yarn doctor ``` If dependencies or manifests changed, also run: ```bash corepack yarn deps:check-pinned corepack yarn deps:check-hardened corepack yarn knip ``` If public-facing English content changed, regenerate the LLM indexes: ```bash corepack yarn llms:generate ``` This keeps `about/public/llms*.txt`, `chain/public/llms*.txt`, and `docs/static/llms*.txt` aligned with the landing pages, docs pages, project directory data, public README text, and the generator itself. ## Subproject Notes ### `chain/` - Contains the Bitsocial Chain landing site for BSO and the proposed L2 appchain - Standalone Vite app under `chain/`; served at `https://chain.bitsocial.net/` - Is translated into every supported language, including the Chain narrative and FAQ ### `about/` - Contains the Bitsocial landing/about site - Currently also contains the public `/projects` catalog and `/projects/:slug` app detail routes - Keeps static assets and translations in `about/public/` - Should not be treated as the long-term home for the project catalog or the blog ### `docs/` - Contains the canonical Docusaurus project - Translation source lives in `docs/i18n/` - Contributor playbooks and long-running agent state also live here ### `stats/` - Contains the stats dashboard (`stats/web/`), the monitor service (`stats/monitor/`), Prometheus, Grafana, and deployment files - Public traffic is served at `stats.bitsocial.net` by the dashboard on the VPS; Grafana stays on the VPS loopback for operators ### Future Splits - The existing project catalog at `/projects` is expected to be extracted from `about/` into its own subproject, and later may move to `apps.bitsocial.net`. - The blog is also expected to become its own subproject rather than continue to live under `about/`. - `about/` should stay focused on explaining Bitsocial as a whole. ## Translations Landing-site translations live under: - `about/public/translations/{lang}/default.json` The Chain site's strings, including its landing narrative and FAQ, live under: - `chain/public/translations/{lang}/default.json` English (`en`) is the source: the Chain components read it through i18next keys, and `scripts/generate-llms-files.mjs` builds the Chain `llms.txt` files from it. Docs translations live under: - `docs/i18n/{lang}/...` For translation workflow details, see [`docs/agent-playbooks/translations.md`](./docs/agent-playbooks/translations.md). ## AI Contributor Policy This repo uses tracked AI workflow files and instructions. Read [`AGENTS.md`](./AGENTS.md) before making changes. Relevant local rules also live in: - [`about/AGENTS.md`](./about/AGENTS.md) - [`about/src/AGENTS.md`](./about/src/AGENTS.md) - [`docs/AGENTS.md`](./docs/AGENTS.md) - [`stats/AGENTS.md`](./stats/AGENTS.md) - [`scripts/AGENTS.md`](./scripts/AGENTS.md) ## Deployment Shape - `bitsocial.net` is served by Vercel - `chain.bitsocial.net` is served from the standalone Chain app - `docs.bitsocial.net` is served from the docs build - `stats.bitsocial.net` routes to the VPS-hosted stats dashboard - Legacy `/docs` and `/stats` paths on `bitsocial.net` return permanent redirects to those subdomains - `newsletter.bitsocial.net` remains separate ### Verified App Mirror Deployments The `/apps` catalog can show a verified check next to app mirrors when a mirror serves the same HTML entrypoint hash as an official GitHub release artifact. This is meant to attest release parity, not domain ownership. For 5chan and Seedit verified web links, the Vercel `5chan` and `seedit` projects are configured so Git pushes do not automatically create deployments: ```text gitProviderOptions.createDeployments = "disabled" ``` Production domains such as `5chan.cc`, `5channel.org`, `5chan.app`, `seedit.app`, `www.seedit.app`, and `p2p.seedit.app` should only be updated from a GitHub release or tag deployment. Do not point those domains at a raw `master` deployment unless that deployment has first been promoted into an official release and its static HTML artifact hash has been checked. When adding or updating mirror verification metadata in `about/src/lib/apps-data.ts`, verify the live mirror HTML against the matching release ZIP before showing the badge. If the live hash does not match a GitHub release artifact, leave the mirror unverified until the mirror is redeployed from the release or a new release is cut for the served artifact. ## Commit Workflow This repo uses Commitizen for Conventional Commits. - Interactive: `corepack yarn commit` - Non-interactive: `git commit -m "type(scope): message"` The Husky Commitizen hook prompts only when a terminal is available. In non-interactive shells it skips the prompt and the commit uses the message you provided. Use `--no-verify` only when you explicitly need to bypass local hooks. ### React diagnostics and performance Run `yarn agent:verify` for affected builds, automatic Doctor diagnostics, and repeated real-app render budgets. Profiling uses sandboxed system Chrome. Check for Chrome with `yarn perf:install`. To install it system-wide, pass `--force`. `perf:check` includes the collector compatibility selftest, also available alone as `yarn perf:test`. `yarn perf:record --target about` (or `chain`/`docs`) saves JSON and Chrome trace evidence under `.react-perf/`. Scenarios live in `scripts/react-perf/config.mjs`. Development uses a bounded Bippy collector; normal production omits it. For production component timing, build with `yarn build:profile:about`, `build:profile:chain`, or `build:profile:docs` and record against that separate preview URL. See `.agents/skills/profile-browsing/references/measurement.md` for coverage and timing limits. The about `apps-search` scenario waits for each character to appear in both the `/projects` URL query and input before typing the next. It verifies a sequence of committed changes and does not test rapid-typing responsiveness or rule out lost characters during overlapping router navigation.

正在加载仓库 README…

这个仓库中的 skills

软件开发工程师软件质量保证分析师与测试员网页与数字界面设计师网络与计算机系统管理员

4 个职业分类 · 已分类 84%