Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Verify session: Repository Walkthrough: Offchain and SDK building (Q2 2026, 14-sdk-repo-walkthrough)

未关闭 适合新手
#357 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown
领域
documentation

调研方向

从 website/docs/working-group/sessions/q2-2026/14-sdk-repo-walkthrough/session-notes/readme.md 开始,按照 issue 中的描述检查正文、链接和图示。检查每个引用的链接、package、image tag 和 version;记录确切的失败以及所有必要的页面更新。完成的标准是所有检查都通过,或页面已修正,并且在此发布检查结果,同时更新 #301 中对应的 checklist 复选框。

由索引模型根据 Issue 内容生成。

描述

documentation

Part of the tutorial verification checklist in #301.

Page: website/docs/working-group/sessions/q2-2026/14-sdk-repo-walkthrough/session-notes/readme.md
Title on the site: Repository Walkthrough: Offchain and SDK building
Section: Q2 2026, 14-sdk-repo-walkthrough

How to follow along
  1. Open the page on the site and read it end to end before running anything.
  2. Work through it in a clean directory, as a new user. Do not skip setup steps because you already have the tooling; the point is to see what a newcomer sees.
  3. Run every command exactly as written, then compare the output with what the page claims it should be.
  4. Open every link, including links inside code comments and references.

Done when

  • Every command runs as written, or the page is updated so that it does
  • Every link resolves
  • Every package, image tag and version referenced still exists
  • The matching box in #301 is ticked and the findings are posted here
What to record when a step breaks
  • The exact command and the error text, copied rather than summarised
  • The heading or step number it sits under
  • What you changed to make it work

This page has no shell commands; verify prose, links and diagrams instead.

This page has no shell commands; verify prose, links and diagrams instead.

主要语言
TypeScript
星标
13
派生
22
平均合并
2 天 18 小时
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

IntersectMBO/developer-experience 的其他 Issue

查看 IntersectMBO/developer-experience 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。