concepts
Caveat: this is not a design system
This is not a design system. This is an architecture that can contribute to a well-formulated design system.
Latest
concepts
Using information architecture
Expert use of information architecture enables both insight and expert redesign. Information isn’t just the nodes we tend to pay attention to – the positive forms in the abstractions of data. Between the positive forms is connections. Those connections, combined, form connectome. That connectome forms patterns that can be used
concepts
Why riffpoints architecture
Riffpoints architecture is focused on deep information construction. All the concepts are/will-be to a degree, but this one barely gets out. There is very limited outward-facing effects, and even then it's only in the extended potentials. But: that's our information. Information is abstract. We have
information literacy
Learning is hard work
information literacy
Whataboutism and both-sides as information manipulation
concepts
Additional interface nuance
The big pieces of the interface – the ones users will focus on and likely conceptualize as the key experience – are further supported. These are objects that support the logic, but users are less likely to key into as characterizing the interface.
concepts
Offer as a substitute interface
People are used to advanced searches. In some sectors, it’s so expected that not having one is tantamount to hanging a sign, “we’re not serious or knowledgable”.
concepts
Focus inclusion to current use
The boxed sets are more information, which means a higher cognitive load. They also require more of a footprint.
concepts
Enable any available metadata
Once the logic for shifting from “Include” to “Prioritizable” is available, it’s another stemming search to add an unexposed filter.
concepts
More than just dropdown
There is absolutely nothing in the dropdown object that says it’s the only viable use case.
concepts
Non-dev interface management
One thing that has become very clear to me is that how we code to interface with data has patterns. They are complex. They have patterns based on broad use, and patterns tailored to specific use, and patterns to signal and help, and design patterns, all of which can be
concepts
Behind the user-facing artifacts
The logic shifts in here might feel intense, but: they are all explicable, none of them are new, and there's a good chance the team could reuse code and actually be able to touch it for optimization/update as part of the sprint. 🥰