VERSION 1.4.0

v1.4.0

Feedback dashboard, Tooltip component, automated backend setup script, prose list/code-block styling fixes, and FlippingCard documentation.

February 23, 2026
·9 changes

New Features

5 new additions

  • Feedback Dashboard — admin dashboard at /feedback-dashboard/ for viewing and analyzing page-level feedback. Includes KPI metric cards (total, likes, dislikes, satisfaction rate), sortable page breakdown table with inline progress bars, option breakdown bar chart, and paginated recent feedback list with period filtering (all time, 30 days, 7 days)
  • Tooltip component — inline hover tooltip for defining terms, acronyms, and jargon in MDX content without interrupting reading flow. CSS-only (no JavaScript), adapts to dark mode, globally registered so no import is needed (<Tooltip content="definition">term</Tooltip>)
  • Feedback API setup scriptnpm run setup:feedback-api <database> scaffolds a ready-to-run Express backend in api/ with the correct server.js, package.json, .env.example, and schema.sql (PostgreSQL only) for the chosen database. Supports mongodb, cosmos, postgresql, and firebase
  • Feedback widget on every doc page<Feedback /> component added to the doc page layout (app/(docs)/[...slug]/page.tsx) with an <hr> separator, centered below the content
  • FlippingCard documentation — dedicated docs page at /components/flipping-card/ with accurate props reference, JSON data file pattern (recommended), wrapper component pattern, multi-card examples, and schema tables. Added to sidebar under Components

Improvements

1 enhancements

  • Using Components guide updated — added Tooltip usage section

Bug Fixes

3 issues resolved

  • Ordered and unordered lists missing markers — Tailwind preflight resets list-style: none on all lists; added .prose ol (list-style-type: decimal) and .prose ul (list-style-type: disc) with padding-left: 1.5em to restore list markers across all doc pages
  • Excessive code block spacing — reduced .prose pre margins from 2rem/1.5rem to 1rem/1rem for tighter vertical rhythm around fenced code blocks
  • MDX numbered lists after </details> — moved Azure Portal and Firebase Console prerequisite steps above the <details> manual-setup blocks to prevent the MDX parser from dropping list markers after HTML elements