# Write documentation PRs not blog posts

**URL:** <https://discourse.julialang.org/t/write-documentation-prs-not-blog-posts/100942>\
**Category:** Teaching & Outreach\
**Tags:** discussion\
**Created:** [June 28, 2023, 6:32pm UTC](https://discourse.julialang.org/t/write-documentation-prs-not-blog-posts/100942 "2023-06-28T18:32:11Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Nathan\_Boyer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nathan_boyer/32/14825_2.png) [@Nathan\_Boyer](https://discourse.julialang.org/u/Nathan_Boyer)\
**Post date:** [June 29, 2023, 1:57pm UTC](https://discourse.julialang.org/t/write-documentation-prs-not-blog-posts/100942/8 "2023-06-29T13:57:34Z")

</div>

This is a good reason why I think it makes more sense for the authors to interact with the core documentation directly, rather than involving a middle man.

Related:

> [@This month in Julia world - 2023-06](https://discourse.julialang.org/t/this-month-in-julia-world-2023-06/100906/4):
>
> Just to say that the discussion about saving knowledge from the slack hole has been had many times over on slack and the consensus was generally that people post on slack on the assumption that it is ephemeral, and content therefore shouldn’t be permanently published somewhere without consent.

---

_[View the full topic](https://discourse.julialang.org/t/write-documentation-prs-not-blog-posts/100942)._