đź“– 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:line citations 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

LayerPlain meaningLocked Qwizz rule
WordPress shellThe host environment surrounding Qwizz.Look native and familiar without letting WP chrome dominate.
UI LabControls for experimenting with the mock-up.Owns layout, density, padding, dummy data, dark mode, failure simulation and arrangement—not plugin behavior.
OnboardingTemporary first-run orientation.Owns the opening viewport, then disappears once its job is done.
Stats dashboardThe four operational headline metrics.Quizzes → Questions → Categories → Played W/L; remains complete when sticky.
Attached navigationChooses the main Qwizz working domain.Remains immediately below the dashboard without jumping.
WorkspaceWhere actual administration happens.Settings, Quiz List, Questions Workbench, builder, results, etc.
Context layerReveals deeper information without permanently cluttering the workspace.Hover/focus previews; click/tap pins; inspectors support sustained work.

đź§Ş Truth-status decoder

LabelWhat it truthfully meansWhat it does not prove
SpecifiedExplicitly required or established behavior.That code exists.
ProposedA reasoned candidate awaiting selection or implementation.Approval, deployment or working behavior.
Visual-onlyA mock-up communicates appearance and hierarchy.Interaction, accessibility, responsiveness or valid data processing.
Implemented prototypeWorking behavior exists in the disposable Admin Lab.Production-plugin readiness.
VerifiedA particular implementation was exercised through named checks.Every environment, device and edge case.
ProductionIntegrated into the real plugin and release lifecycle.Automatic polish or regression safety.
CheckpointA known revision that passed the explicitly stated gates.A formal versioned release or permanent download.
PackagedChosen 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

TermPlain decoderPicture it asDon’t confuse it with
Contact sheetOne image containing many alternatives for comparison.Numbered horizontal specimens stacked vertically.A final production screen.
SpecimenOne individual design inside a contact sheet.One numbered dashboard or list treatment.A complete product version.
Storyboard / multi-state sheetOrdered frames showing one design changing state.Rest → hover → pinned → editing → responsive.Unrelated visual alternatives.
Hero masterLarge, polished rendering of the chosen synthesis.One decisive desktop/mobile design at useful scale.Working code or implementation proof.
LedgerStrictly aligned summary built for rapid scanning.Equal baselines, thin dividers, little decoration.A record table with sortable column semantics.
Precision LedgerThe authoritative high-density list for hundreds of records.Checkbox, identity, status, coverage, performance and actions.A spreadsheet or card wall.
Bento gridUnequal modules whose sizes express importance.One large block beside smaller supporting blocks.Masonry, which packs items opportunistically.
RibbonShallow, continuous information band.Four stats across one horizontal strip.A toolbar, whose primary job is commands.
DashboardComplete operational overview.Full labels, values, context and meaningful grouping.A ribbon that removes important information to become smaller.
RailOpen linear track for navigation.Labels along a baseline with an active underline.A dock with a visible outer container.
DockBounded tray holding navigation or contextual content.Rounded container physically attached to another surface.An open rail.
Pill / capsuleFully rounded geometry.Semicircular ends around a control.A chip; “pill” describes shape, not purpose.
Chip / badgeCompact metadata, filter or status label.Published, English, 30D, Science.A primary action button.
Segmented controlMutually exclusive choices sharing one housing.Several adjoining options inside one bar.Independent pills or semantic content tabs.
Icon wellSmall tinted surface framing an icon.A Lucide icon inside pale lavender.An icon button; a well may be non-interactive.
Surface / cardBounded visual group.White block, border, radius and restrained shadow.”Box soup”: unnecessary containers around everything.
Attached navigationNavigation visually and spatially joined to the dashboard.Dashboard top, navigation directly beneath.Breadcrumbs or unrelated local tabs.
Active statePersistent indication of the current destination.Underline, fill or shape plus stronger text.Hover, which is temporary pointer feedback.
Design tokenNamed reusable visual decision.--qwizz-violet, spacing, radius, border and shadow scales.A duplicated raw CSS value.
DensityHow tightly controls and information are packed.Shorter rows and smaller gaps.Shrinking fonts and targets.
Richness / detailHow much secondary information is visible.Trends, explanations and breakdowns appearing or disappearing.Density; information amount and physical spacing are separate axes.
Progressive disclosureShow essentials first and deeper detail on demand.Clean four-stat rest state opening Overview/Languages/Categories.Omitting functionality entirely.
Responsive reflowComponents reorganize for available width.Four columns becoming a full-size 2Ă—2 grid.Uniformly shrinking the desktop layout.
Dark-mode stress testTheme-luminance test using WP-nav-like dark surfaces.Near-black surface with violet accents.Automatic accessibility compliance.
High-contrast stress testTest that boundaries, labels and focus remain unmistakable.Strong outlines and text/shape redundancy.Merely changing the background to dark.

📌 Sticky, scroll and responsive lingo

TermPlain decoderQwizz ruleDon’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.
StickyScrolls normally until reaching an offset, then remains visible.The dashboard stays full-sized.Fixed, which is viewport-bound immediately.
Sticky handoffOne component naturally changes from in-flow to sticky.The onboarding-floor dashboard becomes the Settings ceiling.Swapping between duplicate dashboard copies.
Sticky stackMultiple sticky layers with cumulative offsets.WP Toolbar → dashboard → attached navigation.Pinned disclosure state.
Sticky offsetSpace reserved above a sticky layer.Must account for the WP Toolbar and preceding sticky layers.Ordinary canvas padding.
PinnedUser explicitly keeps something open.Click/tap/Enter/Space locks one expansion.Sticky, which concerns scroll position.
ExpandedMore content is visible.A metric reveals grouped details.Pinned; an expansion may still be temporary.
Layout invariantA geometry promise interactions cannot break.Pinning never slims the dashboard; insight panels never move the navigation.Responsive reflow, which intentionally rearranges layout.
OverlayContent 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 railNavigation 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-indexBrowser 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

TermPlain meaningPractical contractNearest confusable
Interaction state machineOne model governing valid states and transitions.idle → preview → pinned → editing; dragging remains separate.Scattered booleans permitting impossible combinations.
Hover/focus previewTemporary detail opened by pointer hover or keyboard focus.Must stay open while the pointer/focus enters it and remain dismissible. WCAG guidanceTooltip, which provides short non-interactive help.
Pinned expansionPreview deliberately locked open.One metric at a time; Escape, close or outside activation dismisses.Sticky dashboard placement.
DisclosureA control that shows/hides related content and exposes its state.Real button with aria-expanded and aria-controls; Enter/Space works. ARIA patternTabs, which select among peer panels.
PopoverNon-modal floating surface anchored to a trigger.Useful for contextual insights with viewport-aware placement. WordPress componentTooltip or blocking modal.
Inline editingThe 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 editProject shorthand for editing data where it is displayed.No permanent pencil-button clutter around every value.Making every surface unrestricted contenteditable.
Arrange modeTemporary mode for editing the layout rather than plugin values.Move, reparent, resize, fold, hide or pin controls/sections.Normal settings mode.
FoldCollapse 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 guidanceReorder buttons, which are a valid alternative but not DnD.
Grab handleExplicit target that begins dragging.Protect row clicks, editing and disclosures from accidental drags.Decorative grip icon.
Drop targetLogical container that may receive the dragged item.Highlight the destination group.Insertion marker.
Insertion markerExact before/after landing position.Show the precise line or gap where the item will land.Generic group highlighting.
ReorderChange position within the same parent.Update the sibling index.Reparent.
ReparentMove an item into another group or section.Update parent identity and normalized sibling order.Moving pixels without changing structure.
Pointer captureActive pointer events continue reaching the dragged item outside its bounds.Capture at drag start and release on drop/cancel. Pointer EventsCSS pointer-events, which controls hit testing.
Edge auto-scrollScroll container moves as a dragged item approaches its edge.Capped proportional speed; stop on drop/cancel/exit.Scroll snap.
Undo / redoMove backward/forward through recent mutations.Plugin settings and UI Lab layout require separate histories.Save or persistence.
SaveCommit the current value/state through the relevant lifecycle.May include validation or server persistence.Undo history.
PersistenceState survives reload or reopening.Plugin values and Lab layout use separate stores.Saving, which may be temporary or fail.

♿ Accessibility and input lingo

TermPlain decoderQwizz ruleCommon mistake
Input parityMouse, keyboard and touch can reach the same essential result.Gestures may differ; capability must not.Requiring hover or dragging.
Target sizeThe 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 visibleKeyboard users can see where focus is.Strong focus ring using more than a faint color change. WCAGAssuming hover highlight is enough.
Focus safetyFocus is visible and not hidden beneath sticky/overlay layers.Match scroll-padding/scroll-margin to the full sticky stack. Focus Not ObscuredCorrect focus ring hidden behind the dashboard.
Responsive-workingReal 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 colorsAn 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 ModeDark mode, which is a theme you control rather than a palette imposed on you.

📊 Measurement and analytics lingo

TermPlain decoderQwizz rule or exampleDon’t confuse it with
Low-sample stateNot enough evidence for a stable comparison under an explicit rule.67% W · n=3 · Low sample.Poor performance.
PerformanceUmbrella concept that must name its actual metric.61% win rate · 30D, completion rate or accuracy.Popularity, plays or an unexplained score.
Breakdown dimensionAxis splitting one parent metric.Played by language, category or outcome.Quietly changing the metric.
Additive partitionExclusive groups that reconcile to the parent total.11,224 W + 7,176 L = 18,400.Multi-select tags whose totals exceed 100%.
Primary-category attributionDeterministically count each record under one category.One attempt contributes once to one primary category.Category reach/mentions.
Category utilizationWhether 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 coveragePortion of required translatable entities available in a locale.DE category labels: 46/48.Merely enabling 12 languages.
Lifecycle partitionExclusive current record statuses.248 published + 52 draft + 18 scheduled + 8 archived = 326.Historical publishing events.

🚨 Data locks

LockCorrect interpretation
61% / 39%Outcome shares.
1.56:1Matching W:L ratio.
2.1:1Would imply approximately 67.7% W / 32.3% L—not 61/39.
DistributionMust reconcile to the parent total. Otherwise call it coverage, reach or mentions.
Languages in CategoriesMeans localized category-label coverage, not a fictional intrinsic category language.
PlayedMust visibly state completion policy and reporting window.

🗂️ Quiz List and Questions Workbench

TermPlain decoderUse it forNearest confusable
QuizAssembled, playable experience containing questions and rules.Product-level publishing, preview and performance.Question, which is a reusable content unit.
QuestionReusable content unit that may appear in several quizzes.Authoring, classification, localization and relationship management.One quiz instance or answer attempt.
Quiz ListWorkspace managing assembled quizzes.Status, coverage, preview, plays and performance.Questions Workbench.
Questions WorkbenchWorkspace managing reusable question inventory.Search, preview, edit, bulk changes and quiz relationships.Quiz builder, which arranges one quiz.
Query RailCompact search/filter/sort/view control zone.Change visible records and ordering.Main navigation or bulk actions.
Smart SearchForgiving search across supported fields and relationships.Titles, IDs, stems, categories, languages and quiz usage.Mysterious AI recommendations.
Applied Filter TokenVisible, removable active constraint.Explain and reverse the current query.Passive record metadata chip.
Attention StripSlim rule-driven band surfacing records needing action.Drafts, missing translations, low samples or broken links.Stats dashboard or system alert.
Master–DetailList remains visible while one selected item opens beside it.Rapid repeated inspection without losing position.Modal or inline row expansion.
InspectorStable secondary pane for the selected record.Preview, edit, context and relationships.Global settings sidebar.
Preview DockReserved location where the inspector consistently appears.Prevent layout jumps.Temporary drawer.
Lifecycle LanesAlternate board grouped by Draft/Scheduled/Published/Archived.Status-focused workflow review.Authoritative large-scale ledger.
Taxonomy GroupsRows grouped by category/language classifications.Browse known content domains.Filters, which remove nonmatches.
Responsive TilesTouch-friendly narrow-screen representation.Mobile/tablet reflow.Mandatory desktop card grid.
Bulk ModeTemporary state after selecting records.Apply actions to many records.Ordinary query/filter mode.
Bulk ScopeExact boundary reached by a bulk action.Checked rows, current page or all matching results.Selection count alone.
All-results selectionExplicit escalation from current-page rows to every query match.Select all 10,248 matching questions.Silently selecting hidden records.
Inline PreviewCompact read-only glimpse inside the list context.Quick verification.Frontend-faithful preview.
Frontend-faithful PreviewRead-only rendering matching the actual player.Judge real player-facing appearance.Builder or thumbnail.
Relationship InspectorShows where a question is used and how quizzes depend on it.Safe editing, unlinking, archiving and deletion.Category classification.
Performance GlanceSmall scoped outcome signal in a row/inspector.Identify items worth investigating.Mini analytics dashboard.
Metric ContextTimeframe, denominator, exclusions and reliability around a value.Make W/L interpretable.The metric number alone.
Empty StateNo records exist.Create or import.No-results state.
No-results StateRecords exist but filters/search matched none.Change or clear the query.Empty dataset.
Loading StateResult is not known yet.Preserve geometry with a skeleton.Empty or error.
Recovery StateFailure UI preserving query, selection, target and scroll position.Retry without losing work.Reset, which deliberately discards context.

đź§± WordPress and implementation lingo

TermPlain decoderQwizz meaningDon’t confuse it with
WordPress Toolbar / admin barSigned-in strip at the very top.Ceiling above the Qwizz sticky stack.Qwizz navigation.
Admin chromeWhole surrounding WP shell.Toolbar, left menu, notices, margins and page frame.Google Chrome or a color theme.
Administration menu / admin sidebarPersistent left-side WP navigation. Plugin HandbookLocation of the Qwizz entry.Gutenberg inspector sidebar.
Qwizz navigationHorizontal sections inside the plugin.Content, Builder, Player, Scoring, Results, Style, PDF, More.WordPress’s left navigation.
UI LabPrototype-only control plane.Adjust experiment mechanics and appearance.Production plugin configuration.
Plugin settingsAdministrator-owned values changing Qwizz behavior.Real permissions, validation and persistence apply.Dummy counts, simulated failures or layout play.
Throwaway mock-upDisposable visual sandbox.Cheaply discover placement and hierarchy.Working behavior.
Throwaway prototypeDisposable but interactive sandbox.Test DnD, sticky states, dependencies and persistence.Production plugin.
@wordpress/componentsWordPress React UI primitives.Candidate controls for native-feeling admin UI.All of Gutenberg or an entire admin application.
PopoverAnchored floating-content component.Candidate placement shell for expanded insights.Complete accessibility/state logic.
DataViewsDataset layouts plus search, filtering, sorting and actions.Strong base for Quiz/Question lists.Database, REST API or data fetching.
DataViewsPickerDataset UI optimized for choosing records.Add questions to quizzes or select relationships.General master list.
DataFormStructured record-editing component.Quick edits and inspector forms.Free-form quiz builder.
Settings APIWordPress machinery for registering and rendering settings.Possible production settings foundation.Prototype-only local state.
Options APIWordPress key/value persistence used by many settings.Stores deliberately saved configuration.Transient UI state or undo history.
Gutenberg/React admin stackWordPress’s modern component/package ecosystem.Components can support Qwizz admin screens.Requirement that Qwizz itself be a content block.
Tailwind-like tokensUtility/token discipline resembling Tailwind.Consistent spacing, colors and responsive rules.Proof that Tailwind is actually installed.

âś… QA, deployment and delivery proof

GateWhat it provesWhat it cannot prove
LintConfigured static rules found no reported issues.Runtime or visual correctness.
Production buildSource compiled/bundled successfully.Usability, correct interactions or correct data.
Artifact validationExpected output files and identifiers exist.Successful WordPress installation or pixel quality.
Render contractRequired labels, sections, counts or structural invariants rendered.Visual polish or real pointer behavior.
Smoke testCritical surfaces and basic actions remain present/loadable.Exhaustive regression coverage.
Live preview bridgeMakes a running preview available to an inspection browser.Application correctness; bridge failure and app failure are different.
Visual QARendered hierarchy, spacing, overflow and responsive layouts were inspected.Backend or permission correctness.
Pointer/touch/keyboard QAActual interaction paths were exercised.Full production integration.
Real WordPress integration testPlugin survives genuine WP data, permissions and lifecycle constraints.Every host/theme/plugin combination.
Regression testA known failure is prevented from silently returning.Novel failures outside its assertions.
CheckpointNamed deployed revision passed stated gates.Formal release/version permanence.
PackagingSelected 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 state through Lifecycle 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.