TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/HNU-himematsu/HNU-TimeLetter/llms.txt
Use this file to discover all available pages before exploring further.
/api/contributors endpoint returns the full list of everyone who contributed to HNU-TimeLetter — community members, writers, developers, designers, and more. The data is synced from the Feishu 参与贡献名单 table and written to src/data/contributors.json. At runtime the endpoint reads that file directly, so the credits list updates the moment a sync completes, with no build step or server restart required. On the site, this data populates the Credits scrolling panel section on the home page.
Endpoint
Response — 200 OK
Returns a JSON object with a single top-level key,contributors, containing an array of Contributor objects.
Response schema
Ordered list of project contributors. The order matches the row order of the Feishu 参与贡献名单 table as it was at the time of the last sync.
TypeScript example
Usage on the home page
The contributors list is consumed by the Credits section that appears as part of the home page’s scrolling narrative panels. The component reads from this endpoint on page load and renders each contributor as a styled card, optionally displaying therole badge and message quote beneath the contributor’s name.
The
role and message fields are intentionally optional. Contributors who did not fill in those fields in the Feishu table will still appear in the credits — only their name is required. Frontend rendering should guard against undefined for both fields.Data source
The endpoint readssrc/data/contributors.json at request time. This file is written by the Feishu sync pipeline when the contributors table key is included in a sync job.
| Sync table key | Feishu source table | Output file |
|---|---|---|
contributors | 参与贡献名单 | src/data/contributors.json |
npm run sync locally or trigger a sync job from the admin dashboard that includes the contributors table. The endpoint will serve the updated data immediately on the next request — no build or server restart is required.