11–20 of 40 posts
I liked the Digital Garden Setup guide (needs login): https://learnawesome.org/digitalgardensetup
Uhhh... no.
(UI-wise it is not bad in general except when you want to select the topic it shows up a dropdown list of 2000 things. Also having fake comments auto-generated makes me feel like this is not a finished product but a POC.)
And not sure how but I ran into Error 500 quite a few times.
Overall I think the idea is great conceptually but as a product it is trying to do too many things at once. If OP intends to scale it up I think it would be nice to focus on fullfiling a particular niche first. Or in Paul Buchheit's words: it's better to make a few people really happy than to make a lot of people semi-happy i.e. at least from a product standpoint. Of course as a hobby project I think this is still pretty cool!
Haven't read the source so can't comment too much on the arch and code. I think it has the potential to be further developed into a very powerful CMS for domain-specific knowledge management, or a CRM, etc. B2C-wise as a content-discovery plaftorm I don't see how this is going to work, except becoming a haven for ads which is probably the last thing OP wants. Suppose it does become a social network as OP has intended, when it grows to a certain scale it will run into the same content moderation problem as hn, etc (https://news.ycombinator.com/item?id=23806426). On the other hand B2B-wise it may be able to become ramen profitable.
p.s. to OP: can you delete the duplicated entry for me? Thanks. Due to the crashes and the name not showing up properly I submitted my app https://archy.sh/ with mutiple entries.
If knowledge has dependencies on other knowledge, you could represent that (a la package managers). If something's general enough, you could have multiple virtual packages teaching it.
Yes, the topic/knowledge taxonomy is an important part of it. There are ideas from ConceptNets to Faceted classification. For now, I have taken a pragmatic call to have maximum two parent topics for every topic node here. This allows me to show the hierarchy here: https://learnawesome.org/topics This taxonomy design is being discussed here: https://github.com/learn-awesome/learn/issues/14 Feel free to suggest better…
Life-long learner myself as well, and I built this tool for maintaining and connecting the dots from disparate learning resources online: https://getrumin.com/
Thanks for building this!
How do you plan to scale this collection while also ensuring quality and up-to-date content/minus the link-rot?
Submitted contents are not editable and there is no way to change the title of the submitted content. And there is also no way to delete what you have submitted. From a UX point of view I think this is very none-intuitive. (UI-wise it is not bad in general except when you want to select the topic it shows up a dropdown list of 2000 things. Also having fake comments auto-generated makes me feel like this is not a fini…
Spam will have to be contained. One approach is to show users only those items which have been recommended by users they follow.
Building this as a CMS/CRM is a very interesting idea.
Earlier quoted context omitted.
Yes, the topic/knowledge taxonomy is an important part of it. There are ideas from ConceptNets to Faceted classification. For now, I have taken a pragmatic call to have maximum two parent topics for every topic node here. This allows me to show the hierarchy here: https://learnawesome.org/topics This taxonomy design is being discussed here: https://github.com/learn-awesome/learn/issues/14 Feel free to suggest better…
I've been thinking a lot on knowledge classification systems lately. It's surprisingly challenging to find the right balance between flexibility/comprehensiveness and simplicity/rigidity. Have you documented your research on this topic anywhere beyond that GitHub issue? I'd love to learn more about the strategies you considered.
Earlier quoted context omitted.
Yes, the topic/knowledge taxonomy is an important part of it. There are ideas from ConceptNets to Faceted classification. For now, I have taken a pragmatic call to have maximum two parent topics for every topic node here. This allows me to show the hierarchy here: https://learnawesome.org/topics This taxonomy design is being discussed here: https://github.com/learn-awesome/learn/issues/14 Feel free to suggest better…
Probably not directly applicable to your project but do you know about a project with much more granular skill dependencies? An example are this three skills: "juggling 3 balls" depends on "juggling 2 balls" depends on "throw 1 ball to your other hand without that hand moving much". I'm thinking of a big skill tree like Path of Exile: https://media.esportsedition.com/wp-content/uploads/2017/04/...
I'm not sure if a "tree" is the right data-structure. See this article called "The Spiral Approach to Thinking & Learning": https://learnawesome.org/items/1ef5ff78-7c37-4f5d-bbdd-1cd0b...
For this spiral approach, I think, for every skill we could have certain levels (beginner/intermediate/advanced/elite) and the dependencies could be to those levels.