18 |
19 | 
20 |
21 | 
22 |
23 |
24 | Your bookmarks are saved in localStorage so be assured that no personal data is being tracked or saved on this site.
25 |
26 | ## To contribute:
27 |
28 | This is a Wikipedia-scale project and we could use all kind of help:
29 |
30 | - Spread word about this project among your friends, family, colleagues and online followers
31 | - To donate funds, [visit our OpenCollective](https://opencollective.com/learnawesome)
32 | - To report bugs, [create an issue](https://github.com/learn-awesome/learndb/issues)
33 | - To improve the topic taxonomy or to add/modify the dataset, wait till we put together a public contribution workflow. You can always fork and create your own collection at any time.
34 | - To improve design and suggest features, [start a discussion](https://github.com/learn-awesome/learndb/discussions)
35 | - To fix technical bugs, [propose solutions on the issues](https://github.com/learn-awesome/learndb/issues)
36 | - For anything else, [start a discussion](https://github.com/learn-awesome/learndb/discussions)
37 |
38 |
39 |
40 | ## Architecture
41 |
42 | There are no user accounts, no social features like learning feeds or ActivityPub. Users' bookmarks are saved in browser's localStorage.
43 |
44 | The source data is in `db/*.json` files. The schema is described in [db/README.md](db/README.md).
45 | For the front-end, we write Svelte components in `src` and generate `bundle.js` and `bundle.css` via `npm run dev` / `npm run build`.
46 |
47 | For UI, we make use of TailwindCSS (currently loaded via CDN with some plugins) and Shoelace.Style. Whenever possible, we use Shoelace's existing components.
48 |
49 | ## Build
50 |
51 | We use Neutralino.js to generate native apps for Mac/Windows/Linux. Currently only the .app file (not .dmg) for Mac runs correctly.
52 |
53 | ```
54 | neu build
55 | mv dist/learndb/learndb-mac_x64 dist/learndb/learndb-mac_x64.app
56 | chmod +x dist/learndb/learndb-mac_x64.app
57 | appdmg ./appdmg.json dist/learndb/LearnDB.dmg
58 | ```
59 |
--------------------------------------------------------------------------------
/appdmg.json:
--------------------------------------------------------------------------------
1 | {
2 | "title": "LearnDB",
3 | "icon": "AppIcon.icns",
4 | "contents": [
5 | { "x": 448, "y": 344, "type": "link", "path": "/Applications" },
6 | { "x": 192, "y": 344, "type": "file", "path": "dist/learndb/learndb-mac_x64.app" }
7 | ]
8 | }
9 |
--------------------------------------------------------------------------------
/db/README.md:
--------------------------------------------------------------------------------
1 | # JSON format
2 |
3 | These JSON files can also be generated from a PostgreSQL database whose schema is defined in `schema.sql`.
4 |
5 | We have 3 top-level entities: [Topics](topics.json), [Creators](creators.json), [Items](items.json). Reviews are are nested within Items and have links to either another Item or a Creator.
6 |
7 | topis (name, hname, parent, rank)
8 | creators (name, hname, links)
9 | items (id, name, description, image, splinks, topics, creators, reviews, tags, difficulty, rating)
10 |
11 | spnames are topic names designed to fix many shortcomings of traditional names:
12 | - we want case-insensitive, unique, URL-safe, hashtag-compatible names as topic identifiers
13 | - but case-sensitive and including special characters for human display. Eg: "AT & T" or "C++ 20"
14 | - topics have a taxonomy, typically a hierarchy. For eg: comp.lang.python
15 | - within a parent, we usually want to preserve display order which is not alphabetical. This can be done with names like "100-physics", "200-chemistry", "300-biology" etc.
16 |
17 | Wikipedia handles it awkwardly (escape characters that are hard to type manually, no hierarchy):
18 | - https://en.wikipedia.org/wiki/Zorn%27s_lemma
19 | - https://en.wikipedia.org/wiki/C%2B%2B
20 |
21 | [Newsgroups](https://www.big-8.org/wiki/Big-8_Usenet_hierarchies) are quite nice, but the taxonomy is not granular enough for us to build a universal knowledge graph. For eg: there is [no name yet](https://news.novabbs.org/usenet/article-flat.php?id=34&group=news.announce.newgroups#34) for quadratic equations. Also, everything other than Big-8 (comp, humanities, misc, news, rec, sci, soc, and talk) is shoved into the alt.* hierarchy (the historical reason for that is European networks did not want to pay for groups like religion or racism)
22 |
23 | Taxonomy maintenance is not easy. When does a concept/subtopic deserve its own topic-name? What happens when topics get merged or retired? Should they be language-agnostic or English-first?
24 |
25 | Should names optimize for brevity or readability? What if names get really long?
26 | Should names always fully-specified like `math.algebra.quadratics` or just `quadratics`?
27 | If sort order is included in the name, do we expect the users to write "100-science.200-chemistry"?
28 | If sort order is NOT included in the name then it (and other attributes) needs to be looked up elsewhere.
29 | What if a topic belongs under two separate parent topics? statistics.machine_learning or computer_science.machine_learning?
30 | Can names be compatible with hashtags?
31 | How to handle disambiguation (a name that belongs to 2+ things or a thing that has 2+ names?
32 | How about nameless things or topics?
33 | Should names be meaningful or randomized?
34 | Are names properties (like DNS or ENS)? If not, who assigns them?
35 | How can a taxonomy keep up with expanding knowledge?
36 |
37 |
38 | splinks are HTTP URLs modified specially in a few ways:
39 | - Link should indicate the learning media type (eg: book/course/video/game/event etc)
40 | - Link should optionally include content-hash for integrity check and alternat fetch mechanism like IPFS
41 | - Link should optionally include enable easy lookup for its snapshot on places like Wayback machine
42 | - Link should optionally indicate its open-access status:
43 | - Does it require login?
44 | - Does it require payment?
45 | - Does it require ads?
46 | - Links should be backward-compatible and should navigate to primary location in the usual way
47 |
48 | ## topics.json
49 |
50 | `name` is used as primary key and therefore, must be unique and avoid uppercase and special characters other than hyphen and slash. Here are some examples: `physics`, `linear-algebra`, `nations/india`, `programming-languages/objective-c`.
51 |
52 | `hname` is used as human-readable name and can preserve uppercase. For eg: `ADHD`.
53 |
54 | `parent` should be the name of the parent topic. This makes it possible to show a hierarchical view. If a topic does not have `parent_name`, it would be at the top-level but if it doesn't have children topics of its own, it will be clubbed under a dummy top-level topic called `Misc`.
55 |
56 | `rank` is an integer that's used for controlling the ordering in which topics are displayed.
57 |
58 | ## creators.json
59 |
60 | A top-level table that lists well-known experts and their metadata like occupation, links etc. These are references from items and their reviews.
61 | `name` is unique, URL-safe.
62 | `hname` is case-sensitive, allows special characters and may not be unique.
63 |
64 | ## items.json
65 |
66 | `id` should be a unique UUID. It is needed because there is no other natural primary key. This might also be useful later for defining collections of items.
67 |
68 | `description` can contain markdown with multiple lines.
69 |
70 | `links` is an array of strings. Each item in this array is `format`, `url` and optional identifiers separated by `|`. For eg, one of the strings in `links` might: `summary|https://sivers.org/book/Decisive|ipfs:bafykbzaceaejt6z54qnwnl3ccvw2lsdfksbeuwuh4sv77ixj4c3ldeof2c5so?filename=Daniel%20Higginbotham%20-%20Clojure%20for%20the%20Brave%20and%20True-No%20Starch%20Press%20%282015%29.pdf`.
71 |
72 | The use-case for optional identifiers are things like `ipfs:`, `doi:`, `isbn:` or `isbn13:`.
73 |
74 | `topics` is an array of topic names. These should exactly match `topics` table's `name` column.
75 |
76 | `creators` is an array of strings which are references to the `creators` table's `name` column. For eg: `charles_darwin`.
77 |
78 | `difficulty` must be either `null` or one of these: `childlike`, `beginner`, `intermediate`, `advanced`, `research`.
79 |
80 | `rating` is an integer on 0-100 point scale. This is a curated value and should not be simply copied from external sources.
81 |
82 | `tags` can describe quality: `visual`, `entertaining`, `challenging`, `inspirational`, `interactive`, `oer`. `oer` stands for "Open Educational Resource" and can be used if the linked content does not require payment or user login.
83 |
84 | `reviews` is an array of JSON objects that must match this schema as you can see in `schema.sql`:
85 |
86 | ```
87 | {
88 | "type": "array",
89 | "items": {
90 | "type": "object",
91 | "properties": {
92 | "by_item": {"type": ["string", "null"]},
93 | "by_creator": {"type": ["string", "null"]},
94 | "rating": {"type": ["integer", "null"], "minimum": 0, "maximum": 100},
95 | "blurb": {"type": ["string", "null"]},
96 | "url": {"type": ["string", "null"]}
97 | }
98 | }
99 | }
100 | ```
101 |
--------------------------------------------------------------------------------
/db/creators.json:
--------------------------------------------------------------------------------
1 | [
2 | {"name":"first-round-capital","hname":"First Round Capital"},
3 | {"name":"hacker-news","hname":"Hacker News"},
4 | {"name":"farnam-street","hname":"Farnam Street"},
5 | {"name":"designer-news","hname":"Designer News"},
6 | {"name":"uxtools","hname":"UXTools"},
7 | {"name":"indie-hackers","hname":"Indie Hackers"},
8 | {"name":"reddit","hname":"Reddit"},
9 | {"name":"nobel-prize","hname":"Nobel Prize"},
10 | {"name":"booker-prize","hname":"Booker Prize"},
11 | {"name":"hugo-awards","hname":"Hugo Awards"},
12 | {"name":"elon-musk","hname":"Elon Musk"},
13 | {"name":"dustin-moskovitz","hname":"Dustin Moskovitz"},
14 | {"name":"jeff-bezos","hname":"Jeff Bezos"},
15 | {"name":"bill-gates","hname":"Bill Gates"},
16 | {"name":"mark-zuckerberg","hname":"Mark Zuckerberg"},
17 | {"name":"jack-dorsey","hname":"Jack Dorsey"},
18 | {"name":"tony-hsieh","hname":"Tony Hsieh"},
19 | {"name":"patrick-collison","hname":"Patrick Collison"},
20 | {"name":"larry-page","hname":"Larry Page"},
21 | {"name":"pavel-dunrov","hname":"Pavel Dunrov"},
22 | {"name":"max-levchin","hname":"Max Levchin"},
23 | {"name":"richard-branson","hname":"Richard Branson"},
24 | {"name":"salman-khan","hname":"Salman Khan"},
25 | {"name":"evan-williams","hname":"Evan Williams"},
26 | {"name":"mark-cuban","hname":"Mark Cuban"},
27 | {"name":"steve-jobs","hname":"Steve Jobs"},
28 | {"name":"kevin-rose","hname":"Kevin Rose"},
29 | {"name":"reid-hoffman","hname":"Reid Hoffman"},
30 | {"name":"travis-kalanick","hname":"Travis Kalanick"},
31 | {"name":"kevin-systrom","hname":"Kevin Systrom"},
32 | {"name":"daniel-ek","hname":"Daniel Ek"},
33 | {"name":"ashton-kutcher","hname":"Ashton Kutcher"},
34 | {"name":"austen-allred","hname":"Austen Allred"},
35 | {"name":"sheryl-sandberg","hname":"Sheryl Sandberg"},
36 | {"name":"satya-nadella","hname":"Satya Nadella"},
37 | {"name":"indra-nooyi","hname":"Indra Nooyi"},
38 | {"name":"arianna-huffington","hname":"Arianna Huffington"},
39 | {"name":"marissa-mayer","hname":"Marissa Mayer"},
40 | {"name":"daymond-john","hname":"Daymond John"},
41 | {"name":"eric-schmidt","hname":"Eric Schmidt"},
42 | {"name":"martha-stewart","hname":"Martha Stewart"},
43 | {"name":"tim-cook","hname":"Tim Cook"},
44 | {"name":"peter-thiel","hname":"Peter Thiel"},
45 | {"name":"sam-altman","hname":"Sam Altman"},
46 | {"name":"warren-buffett","hname":"Warren Buffett"},
47 | {"name":"marc-andreessen","hname":"Marc Andreessen"},
48 | {"name":"ben-horowitz","hname":"Ben Horowitz"},
49 | {"name":"bill-ackman","hname":"Bill Ackman"},
50 | {"name":"charlie-munger","hname":"Charlie Munger"},
51 | {"name":"whitney-tilson","hname":"Whitney Tilson"},
52 | {"name":"naval-ravikant","hname":"Naval Ravikant"},
53 | {"name":"ray-dalio","hname":"Ray Dalio"},
54 | {"name":"paul-graham","hname":"Paul Graham"},
55 | {"name":"keith-rabois","hname":"Keith Rabois"},
56 | {"name":"carl-sagan","hname":"Carl Sagan"},
57 | {"name":"albert-einstein","hname":"Albert Einstein"},
58 | {"name":"richard-dawkins","hname":"Richard Dawkins"},
59 | {"name":"neil-degrasse-tyson","hname":"Neil deGrasse Tyson"},
60 | {"name":"don-norman","hname":"Don Norman"},
61 | {"name":"jakob-nielsen","hname":"Jakob Nielsen"},
62 | {"name":"steve-krug","hname":"Steve Krug"},
63 | {"name":"alan-cooper","hname":"Alan Cooper"},
64 | {"name":"donald-trump","hname":"Donald Trump"},
65 | {"name":"barack-obama","hname":"Barack Obama"},
66 | {"name":"hillary-clinton","hname":"Hillary Clinton"},
67 | {"name":"angela-merkel","hname":"Angela Merkel"},
68 | {"name":"vladamir-putin","hname":"Vladamir Putin"},
69 | {"name":"george-bush","hname":"George Bush"},
70 | {"name":"tony-blair","hname":"Tony Blair"},
71 | {"name":"bill-clinton","hname":"Bill Clinton"},
72 | {"name":"tyler-cowen","hname":"Tyler Cowen"},
73 | {"name":"paul-krugman","hname":"Paul Krugman"},
74 | {"name":"ellen-degeneres","hname":"Ellen DeGeneres"},
75 | {"name":"oprah-winfrey","hname":"Oprah Winfrey"},
76 | {"name":"johnny-depp","hname":"Johnny Depp"},
77 | {"name":"woody-allen","hname":"Woody Allen"},
78 | {"name":"anthony-hopkins","hname":"Anthony Hopkins"},
79 | {"name":"morgan-freeman","hname":"Morgan Freeman"},
80 | {"name":"nassim-nicholas-taleb","hname":"Nassim Nicholas Taleb"},
81 | {"name":"seth-godin","hname":"Seth Godin"},
82 | {"name":"ryan-holiday","hname":"Ryan Holiday"},
83 | {"name":"jk-rowling","hname":"JK Rowling"},
84 | {"name":"george-rr-martin","hname":"George RR Martin"},
85 | {"name":"ernest-hemmingway","hname":"Ernest Hemmingway"},
86 | {"name":"paulo-coelho","hname":"Paulo Coelho"},
87 | {"name":"haruki-murakami","hname":"Haruki Murakami"},
88 | {"name":"chuck-palahniuk","hname":"Chuck Palahniuk"},
89 | {"name":"stephen-king","hname":"Stephen King"},
90 | {"name":"nelson-mandela","hname":"Nelson Mandela"},
91 | {"name":"mahatma-gandhi","hname":"Mahatma Gandhi"},
92 | {"name":"joseph-stalin","hname":"Joseph Stalin"},
93 | {"name":"martin-luther-king","hname":"Martin Luther King"},
94 | {"name":"kevin-kelly","hname":"Kevin Kelly"},
95 | {"name":"matthew-mcconaughey","hname":"Matthew McConaughey"}
96 | ]
--------------------------------------------------------------------------------
/db/export_json.rb:
--------------------------------------------------------------------------------
1 | # This script connects to postgres, and exports all data as JSON files that the app expects
2 |
3 | require './postgres.rb'
4 | require 'neatjson'
5 |
6 | # TODO: print one object on each line
7 | File.open("topics.json","w") do |f|
8 | f.write(
9 | JSON.neat_generate(
10 | JSON.parse(Topic.all.to_json),
11 | wrap: 120
12 | )
13 | )
14 | end
15 |
16 | File.open("creators.json","w") do |f|
17 | f.write(
18 | JSON.neat_generate(
19 | JSON.parse(Creator.all.to_json),
20 | wrap: 80
21 | )
22 | )
23 | end
24 |
25 | File.open("items.json","w") do |f|
26 | f.write(
27 | JSON.neat_generate(
28 | JSON.parse(Item.all.to_json),
29 | wrap: 80
30 | )
31 | )
32 | end
33 |
34 | puts "Everything saved as JSON!"
--------------------------------------------------------------------------------
/db/import_json.rb:
--------------------------------------------------------------------------------
1 | # This script imports all data from topics.json, creators.json and items.json into postgres tables
2 |
3 | require './postgres.rb'
4 |
5 | topics = JSON.parse(File.read('topics.json'))
6 | creators = JSON.parse(File.read('creators.json'))
7 | items = JSON.parse(File.read('items.json'))
8 |
9 | puts "import_json: Found #{topics.size} Topics, #{creators.size} Creators, #{items.size} Items in *.json files"
10 |
11 | # TODO: Replace create! calls with create_or_update!
12 |
13 | # TODO: insertion order of topics is important because of the self-referential foreign key parent_name
14 | topics.each do |t|
15 | Topic.create!(
16 | name: t['name'],
17 | hname: (t['hname'] == t['name'] ? nil : t['hname']),
18 | description: t['description'],
19 | image: t['image'],
20 | tags: t['tags'] || [],
21 |
22 | parent: t['parent'],
23 | rank: t['rank'],
24 | roadmap: nil
25 | )
26 | end
27 |
28 | creators.each do |c|
29 | Creator.create!(
30 | name: c['name'],
31 | hname: (c['hname'] == c['name'] ? nil : c['hname']),
32 | description: c['description'],
33 | image: c['image'],
34 | tags: c['tags'] || [],
35 | links: c['links'] || [],
36 | )
37 | end
38 |
39 | items.each do |i|
40 | Item.create!(
41 | name: i['name'],
42 | description: i['description'],
43 | image: i['image'],
44 | tags: i['tags'] || [],
45 |
46 | links: i['links'] || [],
47 |
48 | prereqs: i['prereqs'] || [],
49 | topics: i['topics'] || [],
50 | creators: i['creators'] || [],
51 |
52 | year: i['year'],
53 | level: i['level'],
54 | cost: i['cost'],
55 |
56 | rating: i['rating'],
57 | reviews: i['reviews'] || [],
58 | )
59 | end
60 |
61 | puts "Everything saved in database!"
--------------------------------------------------------------------------------
/db/jsonlines.js:
--------------------------------------------------------------------------------
1 | import items_db from './items.json' assert { type: 'json' };
2 | import topics_db from './topics.json' assert { type: 'json' };
3 | import creators_db from './creators.json' assert { type: 'json' };
4 |
5 | export const io_getTopicList = () => {
6 | return [...topics_db];
7 | }
8 |
9 | export const io_getRandomTopicName = () => {
10 | let randomId = Math.floor(Math.random() * topics_db.length);
11 | return topics_db[randomId].name;
12 | }
13 |
14 | export const io_getTopicByName = (name) => {
15 | return topics_db.filter(t => t.name === name)[0];
16 | }
17 |
18 | export const io_getRandomItemId = () => {
19 | let randomId = Math.floor(Math.random() * items_db.length);
20 | return items_db[randomId].id;
21 | }
22 |
23 | export const io_getItemsForTopic = (topicname) => {
24 | return items_db.filter(i => i.topics.includes(topicname))
25 | }
26 |
27 | export const io_getItem = (id) => {
28 | if(!id) return null;
29 | return items_db.filter(t => t.id === id)[0];
30 | }
31 |
32 | export const io_getItemsForTopicAndFormat = (format, topicname) => {
33 | let results = items_db.filter(i => !topicname || i.topics.includes(topicname)).filter(i => i.links?.join(' ').includes(format + "|"));
34 | return results.slice(0, 100);
35 | }
36 |
37 | export const io_getItemsWithIDs = (ids) => {
38 | let results = items_db.filter(i => ids.includes(i.id));
39 | // console.log({ids}, {results});
40 | return results;
41 | }
42 |
43 | export const io_search_items = (query) => {
44 | if(!query) return [];
45 | let items = items_db.filter(i => i.name.toLowerCase().includes(query.toLowerCase())).slice(0,6);
46 | return items;
47 | }
48 |
49 | export const io_search_topics = (query) => {
50 | if(!query) return [];
51 | let topics = topics_db.filter(t => (t.hname || t.name).toLowerCase().includes(query.toLowerCase())).slice(0,6);
52 | return topics;
53 | }
--------------------------------------------------------------------------------
/db/postgres.rb:
--------------------------------------------------------------------------------
1 | require 'pg'
2 | require 'active_record'
3 | require 'json'
4 |
5 | # see schema.sql
6 |
7 | # To minimize file size, don't export properties with value = null, '', [], false etc. Handle that in code.
8 | # skip hname if it is same as name
9 |
10 | module CleanJson
11 | def as_json(options={})
12 | super(options).tap do |json|
13 | json.delete_if{ |k,v|
14 | v.blank? || (k == :hname && v == json[:name])
15 | }.as_json unless options.try(:delete, :null)
16 | end
17 | end
18 | end
19 |
20 | class ApplicationRecord < ActiveRecord::Base
21 | include CleanJson
22 | self.abstract_class = true
23 | end
24 |
25 | class Topic < ApplicationRecord; end
26 | class Creator < ApplicationRecord; end
27 | class Item < ApplicationRecord
28 | def as_json(options={})
29 | hash = super(options)
30 | hash["reviews"] = hash["reviews"].map { |r|
31 | r.delete_if { |k,v| v.blank? }
32 | } if hash["reviews"]
33 | hash
34 | end
35 | end
36 |
37 | ActiveRecord::Base.logger = Logger.new(STDERR)
38 |
39 | ActiveRecord::Base.establish_connection(
40 | { adapter: 'postgresql',
41 | database: 'postgres',
42 | host: 'localhost',
43 | username: 'postgres',
44 | password: 'password',
45 | port: 5407
46 | }
47 | )
48 |
49 | puts "Postgres: Found #{Topic.count} Topics, #{Creator.count} Creators, #{Item.count} Items"
--------------------------------------------------------------------------------
/db/schema.sql:
--------------------------------------------------------------------------------
1 | DROP TABLE IF EXISTS items;
2 | DROP TABLE IF EXISTS topics;
3 | DROP TABLE IF EXISTS creators;
4 |
5 | CREATE EXTENSION IF NOT EXISTS pgcrypto;
6 | CREATE EXTENSION IF NOT EXISTS pg_jsonschema; -- made by supabase
7 |
8 | -- TODO: Can we store topics/creators/items images in-place (SVG/Base64) rather than as URLs?
9 |
10 | -- TODO: topics.parent_name creates a tree. What if we want a graph or a hypergraph?
11 | -- Should topics have prerequisites globally or only as part of a roadmap?
12 | -- TODO: schema validation for topics.roadmap
13 | CREATE TABLE topics (
14 | name VARCHAR(255) PRIMARY KEY, -- readable, but url-friendly unique slug, eg: abstract-algebra or nations/india
15 | hname VARCHAR(255), -- human-readable case-preserving name, allow null, can have special chars
16 | description TEXT, -- markdown, not in use currently
17 | image VARCHAR(1024), -- url, not in use currently
18 | tags TEXT[] NOT NULL, -- for future usage
19 |
20 | parent VARCHAR(255), -- create a hierarchy with self-reference on this table
21 | rank INTEGER, -- used for sorting children of a parent
22 |
23 | roadmap TEXT, -- A graph of sub-topics combined with recommended items for each sub-topic as a suggested pathway
24 |
25 | FOREIGN KEY (parent) REFERENCES topics(name)
26 | );
27 |
28 | CREATE TABLE creators (
29 | name VARCHAR(255) PRIMARY KEY, -- readable, but url-friendly unique slug eg: bill_gates_1
30 | hname VARCHAR(255), -- human-readable case-preserving name, allow null, can have special chars
31 | description TEXT, -- markdown
32 | image VARCHAR(1024), -- url
33 | tags TEXT[] NOT NULL, -- occupation (investor/author/scientist/celebrity/entrepreneur etc)
34 |
35 | links TEXT[] NOT NULL -- urls of blogs, twitter/activitypub profiles, homepages etc
36 | );
37 |
38 |
39 | -- items.id is not referenced from anywhere except as unique key for URLs directly linking to items
40 | -- reviews are now stored in-place in items table, so don't require items.id anymore
41 |
42 | -- TODO: How to better model items.topics, items.creators and items.prereqs for many-to-many relationship while enforcing foreign-key constraint?
43 | -- Currently, things will break if topics.name or creators.name is modified without updating items that refer to these
44 |
45 | -- TODO: How to model prerequisites? Are they topics or items or both?
46 | -- Should topics have prerequisites?
47 | -- items.prereqs is a array of free-form strings, expected to hold item IDs or topic names
48 |
49 | -- TODO: use even shorter uuid? 58^4 = 11.3m unique ids with just 4 characters
50 |
51 | CREATE TABLE items (
52 | id varchar(12) DEFAULT encode(gen_random_bytes(6), 'hex') PRIMARY KEY, -- keeping id so that name does not need to be a unique url-friendly slug
53 | name VARCHAR(1024) NOT NULL, -- human-readable string (like hname)
54 | description TEXT, -- markdown
55 | image VARCHAR(1024),
56 | tags TEXT[] NOT NULL, -- eg: inspirational, educational, challenging, entertaining, visual, interactive, oer, nsfw, isbn/isbn13
57 |
58 | links TEXT[] NOT NULL, -- array of strings of this format: {item.name}
21 | {#if item.creators} 22 |{item.creators}
23 | {/if} 24 |A Young Lady's Illustrated Primer (from Neal Stephenson's The Diamond Age) is an old dream of tech makers. SkillTree is a step towards building this and making it accessible to everyone.
13 | 14 |The Internet has amazing learning resources for anything you can imagine. However, search engines, edtech platforms, and even Wikipedia/Wikiversity don't do a good job of making them discoverable. Projects like Music Genome Project or Book Genome Project have demonstrated how rich metadata can significantly improve users' lives.
15 | 16 |This is a collection of high-quality learning resources organized by topics & formats and enriched by metadata like difficulty level, assumed prerequisites, reviews by experts and quality tags like visual, interactive, challenging etc. For many books or research papers, there are direct links thanks to projects like InternetArchive, LibGen, Arxiv, SciHub, IPFS etc.
17 | 18 |This is an open-source project. We collaborate with OpenLibrary, OpenSyllabus and leverage projects like Wikipedia, Arxiv, InternetArchive, IPFS, SciHub for topic taxonomy, standardization of metadata formats etc. There are no user accounts and all bookmarks etc are kept in users' browsers.
19 | 20 |{item.name}
117 | {#if item.creators} 118 |{item.creators}
119 | {/if} 120 |{item.description}
187 |loading...
280 | {/if} 281 | -------------------------------------------------------------------------------- /src/ItemList.svelte: -------------------------------------------------------------------------------- 1 | 15 | 16 | 17 |{review.blurb || ""}
16 |Coming soon.
322 | {/if} 323 |
6 | 
13 |