đź“– Qwizz Admin jargon
Qwizz Admin is one continuous WordPress operations surface: onboarding yields to a full sticky dashboard, attached navigation selects the working domain, and focused workspaces manage settings, quizzes, questions, and contextual analytics.
Main path: WP shell → onboarding → dashboard → attached navigation → workspace → contextual detail
Prototype control plane: UI Lab → changes the experiment itself, never real Qwizz settings
How to read this page
This is design and interaction vocabulary, not executable truth. It defines what a word means and what it must not be confused with; it never asserts that a surface exists in the plugin. Code-level and bench terms with
file:linecitations live in 🗣️ QuizWizz shared language, the mined visual authority lives in 🎨 design board, and executable contracts live in 🧪 probe harness.“Qwizz” is this document’s own shorthand for the QuizWizz admin surface; the product and its bench evidence are named QuizWizz everywhere else in this wiki.
đź§ Whole-system decoder
| Layer | Plain meaning | Locked Qwizz rule |
|---|---|---|
| WordPress shell | The host environment surrounding Qwizz. | Look native and familiar without letting WP chrome dominate. |
| UI Lab | Controls for experimenting with the mock-up. | Owns layout, density, padding, dummy data, dark mode, failure simulation and arrangement—not plugin behavior. |
| Onboarding | Temporary first-run orientation. | Owns the opening viewport, then disappears once its job is done. |
| Stats dashboard | The four operational headline metrics. | Quizzes → Questions → Categories → Played W/L; remains complete when sticky. |
| Attached navigation | Chooses the main Qwizz working domain. | Remains immediately below the dashboard without jumping. |
| Workspace | Where actual administration happens. | Settings, Quiz List, Questions Workbench, builder, results, etc. |
| Context layer | Reveals deeper information without permanently cluttering the workspace. | Hover/focus previews; click/tap pins; inspectors support sustained work. |
đź§Ş Truth-status decoder
| Label | What it truthfully means | What it does not prove |
|---|---|---|
| Specified | Explicitly required or established behavior. | That code exists. |
| Proposed | A reasoned candidate awaiting selection or implementation. | Approval, deployment or working behavior. |
| Visual-only | A mock-up communicates appearance and hierarchy. | Interaction, accessibility, responsiveness or valid data processing. |
| Implemented prototype | Working behavior exists in the disposable Admin Lab. | Production-plugin readiness. |
| Verified | A particular implementation was exercised through named checks. | Every environment, device and edge case. |
| Production | Integrated into the real plugin and release lifecycle. | Automatic polish or regression safety. |
| Checkpoint | A known revision that passed the explicitly stated gates. | A formal versioned release or permanent download. |
| Packaged | Chosen artifacts were collected into PNG/ZIP deliverables. | That their contents were built, tested or production-integrated. |
Session truth: the Admin Lab was reported as an implemented prototype with automated checks, while the later header, hover-state, Quiz List and Questions sheets are primarily visual-only designs plus specified interaction contracts.
🎨 Visual grammar
| Term | Plain decoder | Picture it as | Don’t confuse it with |
|---|---|---|---|
| Contact sheet | One image containing many alternatives for comparison. | Numbered horizontal specimens stacked vertically. | A final production screen. |
| Specimen | One individual design inside a contact sheet. | One numbered dashboard or list treatment. | A complete product version. |
| Storyboard / multi-state sheet | Ordered frames showing one design changing state. | Rest → hover → pinned → editing → responsive. | Unrelated visual alternatives. |
| Hero master | Large, polished rendering of the chosen synthesis. | One decisive desktop/mobile design at useful scale. | Working code or implementation proof. |
| Ledger | Strictly aligned summary built for rapid scanning. | Equal baselines, thin dividers, little decoration. | A record table with sortable column semantics. |
| Precision Ledger | The authoritative high-density list for hundreds of records. | Checkbox, identity, status, coverage, performance and actions. | A spreadsheet or card wall. |
| Bento grid | Unequal modules whose sizes express importance. | One large block beside smaller supporting blocks. | Masonry, which packs items opportunistically. |
| Ribbon | Shallow, continuous information band. | Four stats across one horizontal strip. | A toolbar, whose primary job is commands. |
| Dashboard | Complete operational overview. | Full labels, values, context and meaningful grouping. | A ribbon that removes important information to become smaller. |
| Rail | Open linear track for navigation. | Labels along a baseline with an active underline. | A dock with a visible outer container. |
| Dock | Bounded tray holding navigation or contextual content. | Rounded container physically attached to another surface. | An open rail. |
| Pill / capsule | Fully rounded geometry. | Semicircular ends around a control. | A chip; “pill” describes shape, not purpose. |
| Chip / badge | Compact metadata, filter or status label. | Published, English, 30D, Science. | A primary action button. |
| Segmented control | Mutually exclusive choices sharing one housing. | Several adjoining options inside one bar. | Independent pills or semantic content tabs. |
| Icon well | Small tinted surface framing an icon. | A Lucide icon inside pale lavender. | An icon button; a well may be non-interactive. |
| Surface / card | Bounded visual group. | White block, border, radius and restrained shadow. | ”Box soup”: unnecessary containers around everything. |
| Attached navigation | Navigation visually and spatially joined to the dashboard. | Dashboard top, navigation directly beneath. | Breadcrumbs or unrelated local tabs. |
| Active state | Persistent indication of the current destination. | Underline, fill or shape plus stronger text. | Hover, which is temporary pointer feedback. |
| Design token | Named reusable visual decision. | --qwizz-violet, spacing, radius, border and shadow scales. | A duplicated raw CSS value. |
| Density | How tightly controls and information are packed. | Shorter rows and smaller gaps. | Shrinking fonts and targets. |
| Richness / detail | How much secondary information is visible. | Trends, explanations and breakdowns appearing or disappearing. | Density; information amount and physical spacing are separate axes. |
| Progressive disclosure | Show essentials first and deeper detail on demand. | Clean four-stat rest state opening Overview/Languages/Categories. | Omitting functionality entirely. |
| Responsive reflow | Components reorganize for available width. | Four columns becoming a full-size 2Ă—2 grid. | Uniformly shrinking the desktop layout. |
| Dark-mode stress test | Theme-luminance test using WP-nav-like dark surfaces. | Near-black surface with violet accents. | Automatic accessibility compliance. |
| High-contrast stress test | Test that boundaries, labels and focus remain unmistakable. | Strong outlines and text/shape redundancy. | Merely changing the background to dark. |
📌 Sticky, scroll and responsive lingo
| Term | Plain decoder | Qwizz rule | Don’t confuse it with |
|---|---|---|---|
| ”Glued to the top” | Conversational shorthand for becoming sticky during scrolling. | The dashboard docks beneath the WordPress Toolbar after reaching it. | Permanently fixed from page load. |
| ”Glued below” | Conversational shorthand for spatial attachment. | Navigation stays immediately beneath the dashboard. | Sticky positioning itself. |
| Sticky | Scrolls normally until reaching an offset, then remains visible. | The dashboard stays full-sized. | Fixed, which is viewport-bound immediately. |
| Sticky handoff | One component naturally changes from in-flow to sticky. | The onboarding-floor dashboard becomes the Settings ceiling. | Swapping between duplicate dashboard copies. |
| Sticky stack | Multiple sticky layers with cumulative offsets. | WP Toolbar → dashboard → attached navigation. | Pinned disclosure state. |
| Sticky offset | Space reserved above a sticky layer. | Must account for the WP Toolbar and preceding sticky layers. | Ordinary canvas padding. |
| Pinned | User explicitly keeps something open. | Click/tap/Enter/Space locks one expansion. | Sticky, which concerns scroll position. |
| Expanded | More content is visible. | A metric reveals grouped details. | Pinned; an expansion may still be temporary. |
| Layout invariant | A geometry promise interactions cannot break. | Pinning never slims the dashboard; insight panels never move the navigation. | Responsive reflow, which intentionally rearranges layout. |
| Overlay | Content appears above the document without moving it. | Expanded insights can appear beneath the nav without page jump. | Inline expansion, which pushes content downward. |
| Overflow navigation rail | Navigation scrolls horizontally inside its own region. | Preserve all labels on narrow screens without making the entire page scroll sideways. | Multi-row wrapping that changes sticky height. |
Stacking context / z-index | Browser rules controlling which layer paints above another. | Use a deliberate scale for WP bar, sticky shell, overlays and dragging. | Shadow/elevation, which only suggests depth visually. |
🕹️ Interaction-state decoder
| Term | Plain meaning | Practical contract | Nearest confusable |
|---|---|---|---|
| Interaction state machine | One model governing valid states and transitions. | idle → preview → pinned → editing; dragging remains separate. | Scattered booleans permitting impossible combinations. |
| Hover/focus preview | Temporary detail opened by pointer hover or keyboard focus. | Must stay open while the pointer/focus enters it and remain dismissible. WCAG guidance | Tooltip, which provides short non-interactive help. |
| Pinned expansion | Preview deliberately locked open. | One metric at a time; Escape, close or outside activation dismisses. | Sticky dashboard placement. |
| Disclosure | A control that shows/hides related content and exposes its state. | Real button with aria-expanded and aria-controls; Enter/Space works. ARIA pattern | Tabs, which select among peer panels. |
| Popover | Non-modal floating surface anchored to a trigger. | Useful for contextual insights with viewport-aware placement. WordPress component | Tooltip or blocking modal. |
| Inline editing | The displayed value becomes an input in the same location. | Click number → caret; Enter/blur commits; Escape cancels. | Quick Edit, which opens a separate form. |
| Frontend-feeling edit | Project shorthand for editing data where it is displayed. | No permanent pencil-button clutter around every value. | Making every surface unrestricted contenteditable. |
| Arrange mode | Temporary mode for editing the layout rather than plugin values. | Move, reparent, resize, fold, hide or pin controls/sections. | Normal settings mode. |
| Fold | Collapse details while preserving the section’s presence. | Heading/summary remains visible. | Hide, which removes it from the current view. |
| Drag-and-drop (DnD) | Directly move an item with pointer/touch interaction. | Real movement, feedback and destination logic—not arrow buttons wearing a grip. Dragging guidance | Reorder buttons, which are a valid alternative but not DnD. |
| Grab handle | Explicit target that begins dragging. | Protect row clicks, editing and disclosures from accidental drags. | Decorative grip icon. |
| Drop target | Logical container that may receive the dragged item. | Highlight the destination group. | Insertion marker. |
| Insertion marker | Exact before/after landing position. | Show the precise line or gap where the item will land. | Generic group highlighting. |
| Reorder | Change position within the same parent. | Update the sibling index. | Reparent. |
| Reparent | Move an item into another group or section. | Update parent identity and normalized sibling order. | Moving pixels without changing structure. |
| Pointer capture | Active pointer events continue reaching the dragged item outside its bounds. | Capture at drag start and release on drop/cancel. Pointer Events | CSS pointer-events, which controls hit testing. |
| Edge auto-scroll | Scroll container moves as a dragged item approaches its edge. | Capped proportional speed; stop on drop/cancel/exit. | Scroll snap. |
| Undo / redo | Move backward/forward through recent mutations. | Plugin settings and UI Lab layout require separate histories. | Save or persistence. |
| Save | Commit the current value/state through the relevant lifecycle. | May include validation or server persistence. | Undo history. |
| Persistence | State survives reload or reopening. | Plugin values and Lab layout use separate stores. | Saving, which may be temporary or fail. |
♿ Accessibility and input lingo
| Term | Plain decoder | Qwizz rule | Common mistake |
|---|---|---|---|
| Input parity | Mouse, keyboard and touch can reach the same essential result. | Gestures may differ; capability must not. | Requiring hover or dragging. |
| Target size | The clickable/tappable hit area—not icon dimensions. | Meet the 24×24px WCAG minimum; aim nearer 44px for primary controls. | A 16px icon inside a 16px button. |
| Focus visible | Keyboard users can see where focus is. | Strong focus ring using more than a faint color change. WCAG | Assuming hover highlight is enough. |
| Focus safety | Focus is visible and not hidden beneath sticky/overlay layers. | Match scroll-padding/scroll-margin to the full sticky stack. Focus Not Obscured | Correct focus ring hidden behind the dashboard. |
| Responsive-working | Real behavior survives resize, zoom, touch, overflow and long text. | Test 320px, large text, RTL and translated labels. | A narrow screenshot that merely looks plausible. |
| Forced colors | An OS/browser mode that replaces author colors with a user palette. | Never encode meaning in color alone; borders, labels, focus rings and state must survive when the palette is overridden. Forced Colors Mode | Dark mode, which is a theme you control rather than a palette imposed on you. |
📊 Measurement and analytics lingo
| Term | Plain decoder | Qwizz rule or example | Don’t confuse it with |
|---|---|---|---|
| Low-sample state | Not enough evidence for a stable comparison under an explicit rule. | 67% W · n=3 · Low sample. | Poor performance. |
| Performance | Umbrella concept that must name its actual metric. | 61% win rate · 30D, completion rate or accuracy. | Popularity, plays or an unexplained score. |
| Breakdown dimension | Axis splitting one parent metric. | Played by language, category or outcome. | Quietly changing the metric. |
| Additive partition | Exclusive groups that reconcile to the parent total. | 11,224 W + 7,176 L = 18,400. | Multi-select tags whose totals exceed 100%. |
| Primary-category attribution | Deterministically count each record under one category. | One attempt contributes once to one primary category. | Category reach/mentions. |
| Category utilization | Whether a category is assigned under the declared scope. | 48 total = 43 used + 5 empty. | Popularity or translation completeness. |
| Language axis | ”Language” has context-specific meanings. | Content language, delivered locale, interface locale or translation availability. | Treating all four as one field. |
| Localization coverage | Portion of required translatable entities available in a locale. | DE category labels: 46/48. | Merely enabling 12 languages. |
| Lifecycle partition | Exclusive current record statuses. | 248 published + 52 draft + 18 scheduled + 8 archived = 326. | Historical publishing events. |
🚨 Data locks
| Lock | Correct interpretation |
|---|---|
| 61% / 39% | Outcome shares. |
| 1.56:1 | Matching W:L ratio. |
| 2.1:1 | Would imply approximately 67.7% W / 32.3% L—not 61/39. |
| Distribution | Must reconcile to the parent total. Otherwise call it coverage, reach or mentions. |
| Languages in Categories | Means localized category-label coverage, not a fictional intrinsic category language. |
| Played | Must visibly state completion policy and reporting window. |
🗂️ Quiz List and Questions Workbench
| Term | Plain decoder | Use it for | Nearest confusable |
|---|---|---|---|
| Quiz | Assembled, playable experience containing questions and rules. | Product-level publishing, preview and performance. | Question, which is a reusable content unit. |
| Question | Reusable content unit that may appear in several quizzes. | Authoring, classification, localization and relationship management. | One quiz instance or answer attempt. |
| Quiz List | Workspace managing assembled quizzes. | Status, coverage, preview, plays and performance. | Questions Workbench. |
| Questions Workbench | Workspace managing reusable question inventory. | Search, preview, edit, bulk changes and quiz relationships. | Quiz builder, which arranges one quiz. |
| Query Rail | Compact search/filter/sort/view control zone. | Change visible records and ordering. | Main navigation or bulk actions. |
| Smart Search | Forgiving search across supported fields and relationships. | Titles, IDs, stems, categories, languages and quiz usage. | Mysterious AI recommendations. |
| Applied Filter Token | Visible, removable active constraint. | Explain and reverse the current query. | Passive record metadata chip. |
| Attention Strip | Slim rule-driven band surfacing records needing action. | Drafts, missing translations, low samples or broken links. | Stats dashboard or system alert. |
| Master–Detail | List remains visible while one selected item opens beside it. | Rapid repeated inspection without losing position. | Modal or inline row expansion. |
| Inspector | Stable secondary pane for the selected record. | Preview, edit, context and relationships. | Global settings sidebar. |
| Preview Dock | Reserved location where the inspector consistently appears. | Prevent layout jumps. | Temporary drawer. |
| Lifecycle Lanes | Alternate board grouped by Draft/Scheduled/Published/Archived. | Status-focused workflow review. | Authoritative large-scale ledger. |
| Taxonomy Groups | Rows grouped by category/language classifications. | Browse known content domains. | Filters, which remove nonmatches. |
| Responsive Tiles | Touch-friendly narrow-screen representation. | Mobile/tablet reflow. | Mandatory desktop card grid. |
| Bulk Mode | Temporary state after selecting records. | Apply actions to many records. | Ordinary query/filter mode. |
| Bulk Scope | Exact boundary reached by a bulk action. | Checked rows, current page or all matching results. | Selection count alone. |
| All-results selection | Explicit escalation from current-page rows to every query match. | Select all 10,248 matching questions. | Silently selecting hidden records. |
| Inline Preview | Compact read-only glimpse inside the list context. | Quick verification. | Frontend-faithful preview. |
| Frontend-faithful Preview | Read-only rendering matching the actual player. | Judge real player-facing appearance. | Builder or thumbnail. |
| Relationship Inspector | Shows where a question is used and how quizzes depend on it. | Safe editing, unlinking, archiving and deletion. | Category classification. |
| Performance Glance | Small scoped outcome signal in a row/inspector. | Identify items worth investigating. | Mini analytics dashboard. |
| Metric Context | Timeframe, denominator, exclusions and reliability around a value. | Make W/L interpretable. | The metric number alone. |
| Empty State | No records exist. | Create or import. | No-results state. |
| No-results State | Records exist but filters/search matched none. | Change or clear the query. | Empty dataset. |
| Loading State | Result is not known yet. | Preserve geometry with a skeleton. | Empty or error. |
| Recovery State | Failure UI preserving query, selection, target and scroll position. | Retry without losing work. | Reset, which deliberately discards context. |
đź§± WordPress and implementation lingo
| Term | Plain decoder | Qwizz meaning | Don’t confuse it with |
|---|---|---|---|
| WordPress Toolbar / admin bar | Signed-in strip at the very top. | Ceiling above the Qwizz sticky stack. | Qwizz navigation. |
| Admin chrome | Whole surrounding WP shell. | Toolbar, left menu, notices, margins and page frame. | Google Chrome or a color theme. |
| Administration menu / admin sidebar | Persistent left-side WP navigation. Plugin Handbook | Location of the Qwizz entry. | Gutenberg inspector sidebar. |
| Qwizz navigation | Horizontal sections inside the plugin. | Content, Builder, Player, Scoring, Results, Style, PDF, More. | WordPress’s left navigation. |
| UI Lab | Prototype-only control plane. | Adjust experiment mechanics and appearance. | Production plugin configuration. |
| Plugin settings | Administrator-owned values changing Qwizz behavior. | Real permissions, validation and persistence apply. | Dummy counts, simulated failures or layout play. |
| Throwaway mock-up | Disposable visual sandbox. | Cheaply discover placement and hierarchy. | Working behavior. |
| Throwaway prototype | Disposable but interactive sandbox. | Test DnD, sticky states, dependencies and persistence. | Production plugin. |
@wordpress/components | WordPress React UI primitives. | Candidate controls for native-feeling admin UI. | All of Gutenberg or an entire admin application. |
Popover | Anchored floating-content component. | Candidate placement shell for expanded insights. | Complete accessibility/state logic. |
DataViews | Dataset layouts plus search, filtering, sorting and actions. | Strong base for Quiz/Question lists. | Database, REST API or data fetching. |
DataViewsPicker | Dataset UI optimized for choosing records. | Add questions to quizzes or select relationships. | General master list. |
DataForm | Structured record-editing component. | Quick edits and inspector forms. | Free-form quiz builder. |
| Settings API | WordPress machinery for registering and rendering settings. | Possible production settings foundation. | Prototype-only local state. |
| Options API | WordPress key/value persistence used by many settings. | Stores deliberately saved configuration. | Transient UI state or undo history. |
| Gutenberg/React admin stack | WordPress’s modern component/package ecosystem. | Components can support Qwizz admin screens. | Requirement that Qwizz itself be a content block. |
| Tailwind-like tokens | Utility/token discipline resembling Tailwind. | Consistent spacing, colors and responsive rules. | Proof that Tailwind is actually installed. |
âś… QA, deployment and delivery proof
| Gate | What it proves | What it cannot prove |
|---|---|---|
| Lint | Configured static rules found no reported issues. | Runtime or visual correctness. |
| Production build | Source compiled/bundled successfully. | Usability, correct interactions or correct data. |
| Artifact validation | Expected output files and identifiers exist. | Successful WordPress installation or pixel quality. |
| Render contract | Required labels, sections, counts or structural invariants rendered. | Visual polish or real pointer behavior. |
| Smoke test | Critical surfaces and basic actions remain present/loadable. | Exhaustive regression coverage. |
| Live preview bridge | Makes a running preview available to an inspection browser. | Application correctness; bridge failure and app failure are different. |
| Visual QA | Rendered hierarchy, spacing, overflow and responsive layouts were inspected. | Backend or permission correctness. |
| Pointer/touch/keyboard QA | Actual interaction paths were exercised. | Full production integration. |
| Real WordPress integration test | Plugin survives genuine WP data, permissions and lifecycle constraints. | Every host/theme/plugin combination. |
| Regression test | A known failure is prevented from silently returning. | Novel failures outside its assertions. |
| Checkpoint | Named deployed revision passed stated gates. | Formal release/version permanence. |
| Packaging | Selected assets exist in the requested bundle. | Quality of what was packaged. |
Proof ladder:
lint → build → artifact validation → render/smoke tests → visual + input QA → real WordPress integration → packaged release
⚡ Ten-second Rosetta Stone
| If someone says… | Translate it to… |
|---|---|
| ”Glue the dashboard to the top.” | Use a full-size sticky dashboard after the scroll handoff. |
| ”Glue navigation below it.” | Keep navigation spatially attached beneath the dashboard. |
| ”Pin it.” | Persist an open/user-selected state; do not shrink it. |
| ”Expand on hover.” | Hover/focus preview with click/tap/keyboard pinning and Escape dismissal. |
| ”Make it responsive.” | Reflow structure; preserve meaning, type and targets. |
| ”Use fewer boxes.” | Reduce unnecessary surfaces; rely on alignment, spacing and hairlines. |
| ”Make it visual.” | Prefer hierarchy, icons and spatial grouping over explanatory prose. |
| ”Quiz List genius.” | Attention strip + precision ledger + stable preview dock. |
| ”Questions genius.” | Searchable reusable-content list + frontend preview + edit/relationship inspector. |
| ”It passed tests.” | Ask which gate; never translate that automatically into “it works perfectly.” |
Source integrity
This page reproduces the supplied decoder in full. Two regions of the source text arrived damaged and were reconstructed rather than dropped, and both reconstructions are structural or definitional, not new vocabulary:
- Forced colors — the row ended mid-sentence (
OS/browser s differ.). The definition, rule and confusable were completed to the standard meaning of forced-colors mode and this document’s own voice. - Measurement and analytics lingo — the section heading, its introduction and its table header row were missing, leaving nine orphaned rows (
Low-sample statethroughLifecycle partition) attached to the accessibility table. The heading and a four-column header matching the rows’ own shape were restored; no row was altered.
Related pages: 🗣️ QuizWizz shared language for code-cited bench terms, 🎨 design board for the mined visual authority, 🧪 probe harness for what the gates in the QA table actually assert on this bench.