Open willwade opened 3 years ago
I'm wondering..
This topic list might need to be re-organised for different needs..
e.g. Allowing for linking to topics (e.g. Transport -> Cars -> Car Parts , Car verbs ), Age related: 0-5,5-11,11-16, 16+,
How can we keep the good work if @imsky project but add such features to this list.
Maybe do it as a series of Markdown files with meta-data in a header file - or use syntax close to what we have in pasco to link to.. s
i've been thinking for a while of making the wordlists .txt files an output of an input file, like a JSON where the words have tags, for example:
{"cheese": {"tags": ["food"]}
this makes some future applications of wordlists easier, maybe it can help here, too
that would definitely help!
So this one is more of a vocab need really. Imagine you had an old school childs Picture dictionary. So you go to the chapter "Animals" and you find the page of "Farm Animals" and then find all those animals listed A-Z on that page. Thats the kind of thing we are thinking. A lot of symbol vocab packages do this kind of thing - but really hap hazardly - largely because they are limited about cell space on the page (or number of levels deep) - but we dont have to. The fun thing is how we categorise (and sub categorise items). - @willwade
@willwade What is the intended output of this issue?
Do we want to create a meta tag that integrates directly to https://github.com/imsky/wordlists? So like <meta data-list-topic="car">
?
Or do we just want to create a static topic list tree based on the wordlists that we ship with Pasco?
I would be more in favour of just building our own static tree based on the topic lists (that people can edit to remove useless topics to them). Then if it gets lots of use iterate and add a better deeper integration with a meta tag?
Yeah - I think I'm with you on the latter idea - its really just getting a good enough dictionary in place that as you say people could prune and organise themselves. if we do a really good UI and editor its then simple for people to do this
We want a tree that is shipped with the app that is an entire topic dictionary, probably based on: https://github.com/imsky/wordlists
Users can then edit the base tree to only include the topics they want
Original Issue
We have a draft topic dictionary that needs expanding
This https://github.com/AceCentre/pasco/blob/master/html/trees/Dictionary/en-GB-ManyThings.md
Needs incorporating with @whitmer https://github.com/CoughDrop/coughdrop/blob/master/lib/fringe_suggestions.json and @imsky https://github.com/imsky/wordlists
I think plan should be first to find anything missing from https://github.com/imsky/wordlists and do a PR. Then export to our format.
I'm wondering too about a child sub list using top fringe vocab