To chunk information, a process by which individual pieces of an information set are bound together into a meaningful whole.
Basically adding relationships/views to markdown
For the live service go here -> chunk.anty.dev
- Redability (information is easy to zoom, pick apart, and digest, it should feel like an interactable Kurtzkezart video)
- Editability (editing is a click/tap away)
- Replicability (your devices should be able to cache this data for offline use, then synchronize at a later date)
It's easy to see the crucial thing is Chunk Data Visualization built on top of a solid Chunk Relationship Logic.
- Dead simple text markup
- Data relationships explicit in syntax
- Different visualization options
- CommonMark + Custom Data Relation Syntax
- Different visualization options
Chunk {
value: string
created: utc seconds since epoch
modified: utc seconds since epoch
}
User {
user: string
pass: string
salt: string (for brute force attacks)
}
A mockup of how chunks should be displayed under each view. This should give us an idea of how complex the system will be.
A chunk's header is defined by regex
^# *(?<title>(?: *[\w]+)+) *(?:[-=]> *(?<relations>(?:,? *[\w]+)+) *)?$
which extracts title and relations.
What advantage does relating chunks give me? Well that's the whole point, chunks relating to other chunks, but instead of putting it all in a big long list, this UI will nudge the user towards keeping their children list small 4-6 (green), 7-8 (yellow), 9+ (red). Yes, colors are important.
# Chores |
# Groceries -> Chores |
---|---|
# NYCTrip -> Groceries |
# Friday -> Groceries |
# Chores
Stuff I seriously don't like doing but I have to do anyways for my own well being and sanity.
## Groceries
## House Stuff
- Clean
- Do dishes
What would be the representation of the different views?
Basically a notes app
- Chunk Logic
- Views: Notes & Edit with 0 Children
Create release of project