Come up with a plan for using the TL blog effectively
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content
Research direction
The issue does not name files, tests, or entry points. Start by reviewing the existing blog and how contributions are currently coordinated, then define a practical publishing pipeline, collaboration support, and target cadence. Done means the project has an agreed written plan for producing and publishing more technical articles.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 115
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from typelevel/typelevel.github.com
-
Difficulty 3/5 Half a day Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
typelevel/typelevel.github.com#610 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
typelevel/typelevel.github.com#602 · 4 comments ·
-
typelevel/typelevel.github.com#590 · 3 comments · 2 reactions · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in typelevel/typelevel.github.com
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
a11y admissions.uiowa.edu needs grooming SiteImprove best practice
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100