Skip to content
Appifire
Docs
28 — Admin Screens Information Architecture (Blueprint §3)

28 — Admin Screens Information Architecture (Blueprint §3)

Cursor-ready master plan for implementing the full testimonial admin surface (screens 1–13) with navigation hierarchy, shared patterns, and cross-screen state contracts.

28 — Admin Screens Information Architecture (Blueprint §3)

Section titled “28 — Admin Screens Information Architecture (Blueprint §3)”

Source: 02-Implementation-Blueprint.md — §3) Admin Screens and Fields (Detailed).

Product alignment: 01-Post-Purchase-Video-Testimonial-Collector-Plan.md — merchant-facing control center for campaigns, moderation, publication, analytics, and billing.

This document is a build spec only. No code changes are implied until a task references this file.

Related: screen-specific plans 05 to 27.

0) Goal (one sentence)

Section titled “0) Goal (one sentence)”

Provide a single master architecture for all admin/public screens so implementation stays consistent in navigation, shared components, state flow, and ownership across screen-specific plans.

1) Blueprint §3 scope recap

Section titled “1) Blueprint §3 scope recap”

Blueprint recommends 13 screens:

  1. Dashboard
  2. Campaigns List
  3. Campaign Create/Edit
  4. Templates
  5. Submissions Inbox
  6. Submission Detail
  7. Published Content
  8. Widget Settings (+8.1 split)
  9. Moderation Settings
  10. Requests Log
  11. Analytics
  12. Billing & Usage
  13. Public Submission Page (/t/:token)

This file defines how they fit together as one coherent product.

2) Screen ownership map (single source)

Section titled “2) Screen ownership map (single source)”
ScreenRoutePlan file
1 Dashboard/app19-dashboard-screen-1.md
2 Campaigns List/app/testimonial-campaigns17-campaigns-list-screen-2.md
3 Campaign Create/Edit/app/testimonial-campaigns/:id18-campaign-create-edit-screen-3.md
4 Templates/app/testimonial-templates16-templates-screen-4.md
5 Submissions Inbox/app/testimonials09-submissions-inbox-screen-5.md
6 Submission Detail/app/testimonials/:id10-submission-detail-screen-6.md
7 Published Content/app/testimonials/published11-published-content-screen-7.md
8 Widget Settings (+8.1)/app/testimonials/widget05-storefront-widgets-and-read-api.md
9 Moderation Settings/app/testimonials/moderation12-moderation-settings-screen-9.md
10 Requests Log/app/testimonials/requests13-requests-log-blueprint-screen-10.md
11 Analytics/app/testimonials/analytics14-analytics-blueprint-screen-11.md
12 Billing & Usage/app/testimonials/billing15-billing-and-usage-blueprint-screen-12.md
13 Public Submission/t/:token06-public-submission-page-screen-13.md

Use this table to avoid duplicate or conflicting route implementations.

3) Navigation IA (merchant mental model)

Section titled “3) Navigation IA (merchant mental model)”

Group nav items by workflow stage:

3.1 Acquire

Section titled “3.1 Acquire”
  • Campaigns
  • Templates

3.2 Collect

Section titled “3.2 Collect”
  • Requests Log
  • Public submission is external-facing (not in admin nav)

3.3 Moderate

Section titled “3.3 Moderate”
  • Submissions
  • Moderation Settings

3.4 Publish

Section titled “3.4 Publish”
  • Published Content
  • Widget Settings

3.5 Optimize

Section titled “3.5 Optimize”
  • Dashboard
  • Analytics
  • Billing

This sequence matches real merchant lifecycle and reduces onboarding confusion.

4) Cross-screen state contracts

Section titled “4) Cross-screen state contracts”

Define consistent state ownership so screens do not fight each other.

4.1 Campaign state

Section titled “4.1 Campaign state”
  • Screen 2/3 own campaign status and targeting.
  • Screen 4 references campaign for templates but should not mutate campaign state implicitly.

4.2 Submission state

Section titled “4.2 Submission state”
  • Screen 5/6 own moderation states (pending/approved/rejected/archived).
  • Screen 7 owns visibility placement controls and live publication ordering.
  • Screen 6 may toggle publish, but if both screens can change it, behavior must be identical and logged.

4.3 Widget state

Section titled “4.3 Widget state”
  • Screen 8 owns storefront defaults and layout settings.
  • Screen 7 decides what content is eligible for display.

4.4 Analytics/Billing state

Section titled “4.4 Analytics/Billing state”
  • Screens 1, 10, 11, 12 are read-heavy and must derive from canonical request/submission/media data (not ad-hoc counters in UI memory).

5) Shared UI/interaction standards

Section titled “5) Shared UI/interaction standards”

Apply these across all admin screens:

  1. authenticate.admin(request) in loader/action.
  2. shopId tenant scoping on all queries/writes.
  3. URL search params for filters/pagination.
  4. Consistent status badges and terminology.
  5. Toast/banner feedback for all actions.
  6. Empty states with clear CTA to the next logical screen.

Reference 24-build-notes-execution-standards-blueprint-section-10.md.

6) Shared domain vocabulary (must stay consistent)

Section titled “6) Shared domain vocabulary (must stay consistent)”

Use exact terms consistently:

  • Request = outreach unit (TestimonialRequest)
  • Submission = customer-provided testimonial (TestimonialSubmission)
  • Published = storefront-visible flag (published=true)
  • Approved = moderation status
  • Featured/Pinned = merchandising weight

Avoid mixing “review”, “testimonial”, “request” interchangeably in action labels.

7) Global data contracts by screen type

Section titled “7) Global data contracts by screen type”

7.1 CRUD-heavy screens

Section titled “7.1 CRUD-heavy screens”
  • Screen 2,3,4,6,7,8,9
  • Need robust action validation and conflict-safe writes.

7.2 Operational monitoring screens

Section titled “7.2 Operational monitoring screens”
  • Screen 1,10,11,12
  • Need performant aggregate queries and date controls.

7.3 Public capture screen

Section titled “7.3 Public capture screen”
  • Screen 13
  • Needs token security, consent enforcement, and anti-abuse.

8) End-to-end merchant journeys mapped to screens

Section titled “8) End-to-end merchant journeys mapped to screens”

Journey A: Set up campaigns

Section titled “Journey A: Set up campaigns”
  1. Dashboard (see current state)
  2. Campaigns list
  3. Campaign create/edit
  4. Templates

Journey B: Process incoming content

Section titled “Journey B: Process incoming content”
  1. Requests log (delivery health)
  2. Submissions inbox
  3. Submission detail moderation
  4. Published content

Journey C: Improve outcomes

Section titled “Journey C: Improve outcomes”
  1. Widget settings
  2. Analytics
  3. Billing and usage

These journeys should guide onboarding hints and cross-links.

9) Cross-screen linking requirements

Section titled “9) Cross-screen linking requirements”

Required deep links:

  • Dashboard pending CTA -> Submissions tab=pending
  • Campaign row -> Campaign detail
  • Request row (submitted) -> Submission detail
  • Submission detail -> Published list (after publish)
  • Billing alerts -> upgrade flow

Optional:

  • Widget screen preview link to storefront page with app blocks.

10) Implementation sequencing (screen architecture level)

Section titled “10) Implementation sequencing (screen architecture level)”

Recommended order:

  1. Screen 2 + 3 + 4 (campaign setup)
  2. Screen 10 + backend send pipeline visibility
  3. Screen 13 (public capture)
  4. Screen 5 + 6 + 9 (moderation core)
  5. Screen 7 + 8 (publication and storefront)
  6. Screen 1 + 11 + 12 (optimization and reporting)

This order optimizes merchant value delivery and testability.

11) Architecture-level acceptance checklist

Section titled “11) Architecture-level acceptance checklist”
  • Every blueprint screen has an implemented route and owner plan.
  • Navigation is coherent and grouped by merchant workflow.
  • Cross-screen terminology and status semantics are consistent.
  • Shared filters/date handling patterns are reused.
  • Deep links between operational screens are working.
  • No duplicate ownership of the same business state without explicit contract.

12) References

Section titled “12) References”
  • 02-Implementation-Blueprint.md — Section 3
  • 21-route-and-file-map-blueprint-section-6.md
  • 24-build-notes-execution-standards-blueprint-section-10.md
  • Screen plans: 05–19

13) Note on numbering

Section titled “13) Note on numbering”

This folder already includes 05 through 27 plans. This file is 28-....

Home

01 Overview

AppiFire AI Chat — Product Plan & Architecture Options (A, B, C) Technology Overview & High-Level Tasks

01 Platform Foundation

Prerequisites (Detailed Plan) Shopify Setup — Partner Account, CLI, App, and Extension Shopify App Skeleton & Database (Detailed Plan)

02 Knowledge and RAG

Database Schema for RAG Product Sync & Ingestion RAG & Chat API RAG Data Sync (Products, Collections, Inventory, Blog Posts) + Order Lookup How the Codebase Uses Vector Information to Answer Users in Chat Website Knowledge from Web (GPT-4o Mini Search)

03 Billing and Usage

Billing & Usage Billing & Usage — Remaining Tasks Credits wallet: one-time purchases & subscription included credits Free Plan: Reply Cap and Monthly Reset Promo code functionality Shopify App Billing and Payments Tasks

04 Admin and Storefront

Admin Settings & Chat Widget Admin UI Design Plan — Bigger Font, Different Font, More Spacing, Styled Buttons AI Chats / Logs Screen Billing Screen Restructure Plan (Sales + Marketing Focus) Dashboard Plan — AppiFire AI Chat Design Guidelines and Styling System (Polaris + Tailwind Plan) Theme & Design System Timezone & Time Display Plan (Admin + Widget)

05 Chat Experience and Safety

Chat Guardrails Inspection Full Conversation History in OpenRouter Chat Order Lookup Reliability Guide Order Status Conversational Chat Flow Pre-Chat User Identity Form

06 Merchant Lifecycle

Register / Identify App Users (Paying Merchants) Uninstall: Record & Goodbye Email

07 Ops and Release

Deploy: Cloudflare Tunnel + Your Domain & App to appifire-ai-chat.appifire.com Launch & Publishing Guide Links Scheduled jobs, privacy & shop analytics Testing Up to Phase 2 (Product Sync & Ingestion)

08 Research and Ideas

App Names 20 Paid Feature Gaps — AppiFire AI Chat Roadmap Templates Shortlisted Top 30 Shopify App Ideas — High Demand, Buildable, Revenue Potential

09 Archive

100 AI Questions User Can Ask App Embed Settings Plan Chat Thread Identity and History Plan Plan: Free reply monthly reset & paid included credits delivery Future Todo List Promo Code Module Plan Reorganize Documents Support Feature Plan Talk to Human Flow Plan Welcome Email Plan (Brevo API)

10 Marketing and SEO

Article Writing Prompt Appifire SEO Topical Map Topical Map Prompt Appifire VS Pages VS Pages Prompt

11 Video Testimonial Collector

Post-Purchase Video Testimonial Collector — Detailed Product Plan Video Testimonial Collector - Implementation Blueprint Video Testimonial Collector - Pricing & Billing Options Delete All Existing Code and DB Tables (Boilerplate Cleanup) 05 — Storefront Widgets + Public Read API (Screen 8 & 8.1) 06 — Public Submission Page (Screen 13, `/t/:token`) 07 — Email/SMS Request Delivery Pipeline (Blueprint §4) 08 — Security, Compliance & Privacy (Blueprint §8) 09 — Submissions Inbox (Screen 5, `/app/testimonials`) 10 — Submission Detail & Moderation (Screen 6, `/app/testimonials/:id`) 11 — Published Content Manager (Screen 7, `/app/testimonials/published`) 12 — Moderation Settings (Screen 9, `/app/testimonials/moderation`) 13 — Requests Log (Blueprint Screen 10, `/app/testimonials/requests`) 14 — Analytics (Blueprint Screen 11, `/app/testimonials/analytics`) 15 — Billing & Usage (Blueprint Screen 12, `/app/testimonials/billing`) 16 — Templates (Screen 4, `/app/testimonial-templates`) 17 — Campaigns List (Screen 2, `/app/testimonial-campaigns`) 18 — Campaign Create/Edit (Screen 3, `/app/testimonial-campaigns/:id`) 19 — Dashboard (Screen 1, `/app`) 20 — Database Design & Migrations (Blueprint §5) 21 — Route & File Map Execution Plan (Blueprint §6) 22 — Integration & Processing Orchestration (Blueprint §7) 23 — Release Plan & Milestones (Blueprint §9) 24 — Build Notes Execution Standards (Blueprint §10) 25 — Core Modules Breakdown (Blueprint §2.2) 26 — Project Conventions Execution Guide (Blueprint §2.1) 27 — Product Scope Recommendation Execution (Blueprint §1) 28 — Admin Screens Information Architecture (Blueprint §3) 29 — Milestone 1 Delivery Plan (Blueprint §9.1) 30 — Milestone 2 Delivery Plan (Blueprint §9.2) 31 — Milestone 3 Delivery Plan (Blueprint §9.3) 32 — Email/SMS Operational Detail (Blueprint §4) 33 — TestimonialModerationLog Model & Audit Workflow (Blueprint §5.10) 34 — TestimonialDailyAnalytics Model & Rollup Jobs (Blueprint §5.11) 35 — TestimonialProductLink Model & Multi-Product Merchandising (Blueprint §5.9) 36 — TestimonialMediaAsset Model & Processing Pipeline (Blueprint §5.8) 37 — TestimonialSubmission Model & Lifecycle (Blueprint §5.7) 38 — TestimonialRequestEvent Model & Delivery Event Stream (Blueprint §5.6) 39 — TestimonialRequest Model & Scheduling Lifecycle (Blueprint §5.5) 40 — TestimonialTemplate Model & Resolution Rules (Blueprint §5.4) 41 — TestimonialCampaignProduct Model & Targeting Rules (Blueprint §5.3) 42 — TestimonialCampaign Model & Automation Rules (Blueprint §5.2) 43 — Shop Model Extension for Testimonials (Blueprint §5.1) 44 — Per-Product Collection Rule (Required) Implementation Plan 45 — Two Storefront Widgets (v1 Requirement, Screen 8.1)