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
派生
115
平均合并
4 天 13 小时
30 天内合并 PR
8

贡献指南

打开贡献指南

从这里开始

  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 摘要。