How should we handle self-answered / today I learned / publications posts?

Occasionally we see threads of tools, tricks, and ideas the poster recently learned about and wanted to share. Often these posts are "Here's something useful I learned, what do you think?" Many include links to a blog the poster created detailing what they've learned.

There has been some push to better designate these posts.

  1. Partly, so they are easily distinguished from posts from people seeking help.
  2. And partly to better promote the best lessons learned.

I am leaning towards the following;

Creating a guide for posting self-answered questions and own-blog-publications. This would be pretty simple, but the guide would be incorporated into a helper-form so we help people stay consistent. This would include a special tag for these types of threads (hopefully solving issue 1).

A similar wizard-form for coding-questions.

These wizards (particularly the guide + form for new-user coding questions) would appear prominently on the homepage.

I am curious for your thoughts and advice on what a guide on this might look like?


Thank you @andresrcs for suggesting this idea!

3 Likes

About the structure of this kind of publications, I would suggest including a tag in the topic title (GitHub style e.g. Feature Request:) and separating the problem description and context from the actual solution (that would alow to mark it as solved)

Self-Answered: Here is how to do this interesting thing in R

<!-- 
    Description/context of the problem you are solving
-->
    
<!-- 
    Cool solution or link to a blog post, preferably on a subsequent post
-->
2 Likes

This topic was automatically closed 42 days after the last reply. New replies are no longer allowed.