Replies: 3 comments 1 reply
-
The one danger of wikis is we would need enough active contributors to properly edit it from time to time and keep it DRY. It would be nice to integrate this collective knowledge into a PR-like process. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Do you think "notes for each resource" could be useful? |
Beta Was this translation helpful? Give feedback.
0 replies
-
There's two main ways I would imagine we are using this:
One is to look up topics, and the other is combining topics when doing a
specific project. For instance, there's knowledge we want to know about
Django and React independently, and then there's extra stuff we have to
know when combining those two into a single application.
The Arch distro wiki could give us good ideas for how to structure it:
https://wiki.archlinux.org/
…On Tue, Aug 25, 2020 at 10:31 PM Linda ***@***.***> wrote:
Do you think "notes for each resource" could be useful?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQU4TSCPLCHBOPOWS7SPJ3SCRXXLANCNFSM4QJDUBFA>
.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
A new section of the CodeBuddies platform that allows everyone to capture and share their notes
What:
Why:
My ideal version (yes, I'm checking my bias):
I chatted about it with @bengineerdavis
and in this CodeBuddies slack thread
Beta Was this translation helpful? Give feedback.
All reactions