Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Come up with a plan for using the TL blog effectively

未關閉
#598 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
領域
content

研究方向

此 issue 未指定檔案、測試或進入點。先檢視現有的部落格以及目前如何協調貢獻,接著定義實用的發布流程、協作支援和目標發布頻率。當專案擁有一份經同意的書面計畫,用於製作和發布更多技術文章時,即表示完成。

由索引模型根據 Issue 內容生成。

描述

We have a blog, but don't post to it very often, and most of what we are saying is administrative. That's a wasted opportunity: we have so many great projects, and so many potentially interesting technical topics, that we can and should do a lot more technical posting.

For this to work, we have to pull in the TL community in a big way. Not even just the library authors, either: we would do well to host articles from folks using the ecosystem, describing cool things they are doing with it.

Ideally, we should target a regular cadence for the blog, preferably weekly, but step number one is to come up with a pipeline: that will probably take a few months, and we should post more occasionally as we build up that pipeline.

We should think about how to collaborate to help articles happen. Many engineers have great ideas, but aren't as comfortable or practiced at writing, so we may want to see whether we can provide some assistance there.

主要語言
HTML
星號
42
分支
114
平均合併
1 天 14 小時
30 天內合併 PR
5

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

typelevel/typelevel.github.com 的其他 Issue

查看 typelevel/typelevel.github.com 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。