Content cardinality reduction via SSOT HTML for 'Edit' / 'View' contexts
Premise
Most projects uses two independent views for data: viewing and editing states. I believe there's an opportunity to unify HTML for both states. It has implications across multiple modules and would represent a major paradigm shift.
@lorin experimented with this a few years ago prior to project separation, but didn't have time to fully flesh it out, so it was removed #22 (closed).
Technical
-
contenteditable
only goes so far alone.
Questions
-
What's the accessibility impact? -
How does it limit design customization? -
How 'purely' can this be implemented? What are imposed opinionated limitations? -
How far can HTML elements be pushed, do any have vendor locked customizations? all:unset;
? -
What would context flag integration look like? -
Limit to specific edition?
Keywords
Single source of truth (SSOT), content cardinality, states, context
Edited by Lorin Halpert