[PLUGIN][Reply] Separated replies from Note table.
[PLUGIN][Repeat] Deleted unnecessary card note template, info now to appended at the end of note. [PLUGIN][TreeNotes] WIP to accomodate reply plugin changes. [TWIG][Runtime] Removed getAdditionalTemplateVars event.
This commit is contained in:
@@ -5,7 +5,7 @@ to take advantage of such phenomena, which is sometimes taken to great effects i
|
||||
Patterns emerge when concepts and actions, interlinked, construct a predictable outcome. With a common design language,
|
||||
we hope to achieve such predictability, and supply an innate understanding of user interaction.
|
||||
|
||||
The goal isn't to have one and only design language, but to encourage new interfaces to take similar steps on their
|
||||
The goal isn't to have one and only design language, but to encourage new themes/interfaces to take similar steps on their
|
||||
design processes.
|
||||
|
||||
## Predictability and user experience
|
||||
@@ -18,10 +18,14 @@ Web technologies as a whole contain a set of constraints for organizing web page
|
||||
a common structural basis.
|
||||
|
||||
Users accustomed to surfing the Web know which user interactions are acceptable and which aren't.
|
||||
The key puzzle is how users come to know these restrictions of their Web UI.
|
||||
The key puzzle is how users come to know these restrictions of their Web UI. This is the crux of any
|
||||
accessible Web page, an hierarchy needs to be followed as well as common standards.
|
||||
|
||||
### Canons of page construction
|
||||
The aforementioned comparison between books and Web pages isn't just a coincidence, given the resemblance between the
|
||||
two mediums. From their presentation to fundamental theory, it's only natural to apply core book design ideas to the Web.
|
||||
|
||||
|
||||
### User customization
|
||||
|
||||
|
Reference in New Issue
Block a user