Description
What about having a community-tips repo, where people can raise issues or a new json file (ideally daily), with a small tip they learned that day to share with the community
Benefits:
Note: If a json file, then a GitHub action could update the README with each json file and avoids conflicts
Green squares π π© β π
Thank you @alrifay , I will update my description - I was going to tag you in the brackets where I wrote I know it is a circle .. @alrifay π
@eddiejaoude could we use markdown files for this? e.g. we could have a markdown file that would allow us to parse it like
n.b. I can't remember the syntax, but I believe this is how a lot of static site generators work........... something like this...
---
summary: I think EVERYONE should delete 5 lines of their code everyday to reduce bugs.
---
# Example bit of code WITH MARKDOWN SYNTAX HIGHLIGHTING *HOPEFULLY
```typescript
const steveTest = () => {
return true;
}
winning
@eddiejaoude @alrifay clearly this markdown inside a markdown wasn't gonna work very well above, but with markdown, we could parse the "tip" as a summary then you could embed code and references and whatever and click through straight to that MD file (e.g. it would be more like a blog!)
@stemount You can add markdown inside <pre><code></code></pre> or three ~ instead of three ` or indent the code block with 4 spacesπ
Example 1:
~~~markdown
const steveTest = () => {
return true;
}
~~~
Example 2:
`````markdown
~~~markdown
const steveTest = () => {
return true;
}
~~~
`````
Result:
const steveTest = () => {
return true;
}
winning
~~~
I think EVERYONE should stop being as lazy as I am blaming the markdown formatter ;) @alrifay
An update on this topic π. @AllanRegush started this development on EddieBot with tips about open source.
This idea can be iterated upon and moved to a different repo like @eddiejaoude suggested on the issue description. In EddieBot, I think we could add a fetch package, to make an HTTP request and get the tips data (JSON or Markdown format), but again this would change with our implementation decision.
In my opinion, I think we could evaluate how many tips and how frequent contributions this will have. My concern is that we overengineer these tips π , and the resulting code to make it work is harder for newcomers to reason about.
But please let me know your thoughts as well π.
Keeping it simple for contributors is important, finding that balance is always difficult - but we can make small tweaks and review, therefore if we feel it is getting to complex and no benefit, we can pivot.
I dont think we will know the right answer with trying different things, yes some might be more clear than others, I am all for discussing and trying some options π€
Stale issue message
Stalebot lets keep this for now π€
Stale issue message
This has been opened for quite a while. What does everyone think about the current state of this issue?
Maybe we could use GitHub Discussions on this repo, instead of a new repo (at least for starters). We have the Tips & tricks category so I'd say it fits very well in this topic (plus, we still get π© π).
We could use Discussions to get a feel of how this would work and it's something we can start using today, with markdown support π! The downsides IMO are:
^tips commandI think you are right @BOLT04 π . Discussions helps us to get moving forwards faster, then we can improve afterwards
What about a Twitter bot for this which automatically sends the tip of the day as twitter post? π€
hmm we could do multiple things with the data and link it to all sorts of fun bots and sites π .. I think there was a similar idea in discord chat about this
@kcoder63 has built a twitter bot, and is open to tweaking it - can you share a link to the repo?
Repo of the bot I made?
Yes please @kcoder63 π
[Repo] (https://github.com/kcoder63/Edbeepbot)
here's the link
I think there's still some discussion to be had on this stalebot :)
yes I agree @Vyvy-vi π
Most helpful comment
Repo of the bot I made?